V100R020C10SPH320 Patch Release Notes
V100R020C10SPH320 Patch Release Notes
Issue 02
Date 2022-10-19
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 express 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 a warranty of any kind, express or implied.
Email: support@huawei.com
Preface
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Issue Date Description
Contents
Preface.......................................................................................................................................... ii
1 Patch Overview......................................................................................................................... 1
1.1 Basic Information .................................................................................................................................................. 1
1.2 Patch Files............................................................................................................................................................. 2
1.3 Hardware Versions................................................................................................................................................. 3
1.4 Related Product Versions and Compatibility ........................................................................................................... 7
1.5 User Interface Updates........................................................................................................................................... 7
1.6 Impact of Patch Installation ................................................................................................................................... 7
1.7 Virus Scanning Result............................................................................................................................................ 8
3 Known Issues.......................................................................................................................... 80
4 List of Remediated Vulnerabilities...................................................................................... 83
1 Patch Overview
Huawei defines its product versions with the following convention: "V" stands for version; "R" stands
for release; "C" stands for customization.
You can run the following command to query the version information.
huawei(config)#display patch all
Software Version:MA5800V100R020C10
SPH320
------------------------------------------------------------------------
Command:
display io-packetfile information
Version of the board software packetfile:MA5800V100R020C10SPC303
Board software saved in mainboard:
---------------------------------------------------------------------------
Index File Type Version File Length
---------------------------------------------------------------------------
To prevent a software package from being maliciously tampered with during transmission or storage,
download the corresponding digital signature file for integrity verification when downloading the
software package.
After the software package is downloaded, verify its PGP digital signature according to the OpenPGP
Signature Verification Guide. If the software package fails the verification, do not use the software
package, and contact Huawei technical support engineers.
Before a software package is used in installation or upgrade, its digital signature also needs to be
verified according to the OpenPGP Signature Verification Guide to ensure that the software package is
not tampered with.
Visit either of the following websites to obtain the OpenPGP Signature Verification Guide:
Carriers: https://support.huawei.com/carrier/digitalSignatureAction
Enterprise customers: https://support.huawei.com/enterprise/zh/tool/pgp-verify-TL1000000054
You can run the display version frameid/slotid command to query the board version.
Matched: When the NE software is upgraded, the associated device and NMS do not need to be
upgraded or have patch files loaded and they can fully support existing and new functions of the NE.
Compatible: When the NE software is upgraded, the associated device and NMS do not need to be
upgraded or have patch files loaded and they can support existing functions of the NE. However,
they do not support or have limited support for new functions of the NE.
2 Resolved Issues
2.1 V100R020C10SPH320
2.1.1 General Issues
Trouble Ticket DTS2022090618681
Number
Severity Major
Root Cause The memory of the board is faulty. As a result, the user MAC
addresses cannot be learned, and packets sent to the users are
forwarded as unknown unicast packets but discarded due to
unknown unicast rate limiting on the ingress port.
Severity Minor
Root Cause If a password contains more than 15 characters, the verification fails
and an error message is returned. The subsequent HWTACACS
authentication process is not triggered.
Solution Increase the password length limit to 128 characters to reach the
maximum length allowed by HWTACACS.
Severity Minor
Problem Conditions:
Description 1. The igmp multicast-tag is configured.
2. There is a possibility that the igmp multicast-tag configuration
fails to be delivered to a board.
Symptom: The igmp multicast-tag command does not take effect on
the board.
Impact: Multicast black screen occurs.
Severity Minor
Root Cause During configuration restoration, the board fails to issue the igmp
multicast-tag configuration due to a hardware fault.
Problem Condition: When the standby control board is switched to the active
Description control board, a large number of multicast users go online and
offline at the same time. As a result, some multicast user status data
is not completely synchronized.
Symptom: During an active/standby switchover or an upgrade, the
standby control board resets unexpectedly.
Impact: The system resets.
Severity Minor
Root Cause The data type of the multicast user data is incorrect and is registered
as the system static data type. When the standby control board
becomes active, if there is static data not completely synchronized,
the standby control board resets for self-healing.
Solution The data type of the multicast user data is changed to status data (the
setting takes effect after the active and standby control boards are
reset). When the standby control board becomes active, the system
does not check whether the multicast user status data is
synchronized.
Severity Minor
Root Cause When a hardware fault occurs on the memory connected to the
CPU, no alarm is reported.
Solution Impact Modified the 0x02310018 alarm, and added an alarm parameter:
DDR fault for handling single-bit errors with cpu.
Severity Minor
Root Cause When the number of bytes to be converted is 4 bytes, the 2-byte
conversion function cannot be used. As a result, the bytes are
truncated.
Severity Minor
Root Cause After the board is reset, there is a 50 ms delay between the reset and
the disabling of optical signals. As a result, abnormal optical signals
are generated on some ports, and the ONT continuously triggers the
LOS and LOS clear alarms after receiving the abnormal optical
signals. If more than 1024 alarms are triggered within 1s, the ONT
cannot process the alarms in a timely manner and fails to go online.
Solution During the board reset process (before the delay introduction point),
optical signals on all ports are disabled.
Severity Minor
Root Cause The board CPU usage is high.As a result, the PMI result of the
power supply of the optical port is abnormal and the alarm is falsely
reported.
Solution The mechanism for detecting the power supply of the optical port
has been modified so that an alarm is reported only when the power
supply of the optical port is actually faulty.
Problem Condition: The LOS alarm (alarm ID: 0x2e11a001) is reported after
Description the optical module of the upstream port on the control board is
abnormal.
Symptom: The upstream port is displayed as down, but the peer
device is still online.
Impact: The device fails to be managed by the NMS when inband
management is used.
Severity Major
Root Cause The actual link status of the port does not reference the LOS status
of the optical module. When the optical module is abnormal, the
LOS alarm is reported, but the port is not down. As a result, the
Layer 3 forwarding entry is deleted.
Solution Configure the port to reference the LOS status to ensure that the port
status is consistent with the hardware status.
Problem Condition: When the system runs for a long time, a ring network on
Description the external network causes ultra-large traffic of protocol packets to
flood the CPU of the OLT.
Symptom: An active/standby switchover occurs on the OLT, and
the service boards reset temporarily.
Impact: Services are affected for a short period of time.
Severity Minor
Root Cause A ring network on the external network causes a large number of
protocol packets to flood the OLT CPU. As a result, the OLT
triggers a protective board reset.
Problem Condition: The dot1x DHCP trigger function is enabled. After the
Description ONT resets, the dot1x client performs DHCP dialup after passing
the authentication.
Symptom: The client fails to obtain an IP address during DHCP
dialup.
Impact: DHCP dialup fails.
Severity Minor
Root Cause The message mechanism between the dot1x cfg process and the srv
process is as follows: The interval between two consecutive
authentication mode and authentication status messages is too short.
As a result, the status synchronization message cannot be sent out,
the authentication status is not synchronized, and the dial-up fails.
Problem Conditions:
Description 1. The device is newly deployed, and the upstream port is online but
the peer end does not have remote software commissioning
configuration.
2. After an active/standby switchover, a user logs in to the device
during the restart of remote software commissioning. As a result, the
remote software commissioning stops, and there is a possibility that
residual VLAN data exists.
3. An LACP aggregation group is configured to have the same
upstream port as that for remote software commissioning. The
residual VLAN of the remote software commissioning is deleted,
and the save operation is performed.
Symptom: The manually configured LACP aggregation group is
deleted.
Impact: The device fails to be managed by the NMS and services
are interrupted. Services can be restored after the LACP aggregation
group is reconfigured.
Severity Minor
Root Cause During the login, the running flag bit of the remote software
commissioning restart is not updated. As a result, residual remote
software commissioning data exists. In the save phase, the residual
data is cleared, and the newly configured LACP aggregation group
with the same port is deleted by mistake.
Solution During the login, the running flag bit of the remote software
commissioning restart is updated to prevent residual data.
Severity Minor
Root Cause During the active/standby switchover, the standby control board is
removed, and the active control board takes over the forwarding
module of the standby control board. When the active control board
takes over the mirroring of the peer control board, an error is
returned. The logic returns a message in advance, and the MAC
address control is not restored to the user threshold. When the MAC
address threshold is 0, MAC address learning cannot be performed.
Severity Minor
Solution The following inspection items are added for abnormal board
interruption:
1) Counts the number of abnormal interrupts within a period (1
minute).
2) If the number of abnormal interrupts detected in 10 consecutive
periods is greater than 0, an alarm (alarm ID: 0x02310018) is
generated. If the number of interrupts detected is 0, the statistical
periods and the alarm are cleared.
Severity Minor
Root Cause The server IP address in the offer packet is different from that in the
ACK packet. As a result, the OLT authentication fails and the ACK
packet is discarded.
Solution Impact The dbwin send 172 0x4 0x2 4 0/1 command is added to disable or
enable server IP address verification, and the dbwin send cid
0xcc510000 300 5 command is added to query the function status.
Severity Minor
Root Cause After ARP entries are aged out, there are too many ARP packets. As
a result, backpressure occurs on ARP packets and the ARP entries
of the peer end cannot be learned in time.
Severity Major
Root Cause After the combo mode of a PON port on a board is changed, there is
a possibility that the ONT service flow is bound to the drop profile
when the OLT quickly deletes the ONT and reconfigures the ONT.
As a result, downstream packets are discarded and dialup fails.
Solution After the ONT goes online, the service flow bound to the drop
profile is bound to a profile again.
Severity Minor
Root Cause The system does not have the detection and repair mechanism for
the appconf.ini file.
Solution The function of detecting and repairing the appconf.ini file is added.
Number
Severity Minor
Root Cause A software error occurs on the board. As a result, the ONT
configuration fails to be recovered or the ONT optical power cannot
be obtained.
Solution A detection item is added to the board software error inspection task
to detect abnormal interrupts on the board. Software errors can be
queried.
Severity Minor
Root Cause This type of ONT supports query only in ITU-T mode and does not
support query in mode 4.
Solution In mode 4, the ITU-T mode is used to query the optical power.
2.2 V100R020C10HP3041
2.2.1 General Issues
Trouble Ticket DTS2022080412772
Number
Problem Condition: The customer uses the FTP tool to load a package file.
Description Symptom: The loading fails, and the system displays a message
indicating that the package file is too long.
Impact: The package file fails to be loaded.
Severity General
Root Cause The FTP server does not support resumable transmission, and the
process of loading the package file is defective.
Severity Major
Root Cause When the CLI and NMS operation is performed, the processing of
log recording is defective.
Severity Minor
Root Cause When a subrack is fully configured with PON boards, the OCM
queue is full. As a result, the PON board that starts up last cannot
load the DDMC file and cannot issue multicast configurations, and
third-party ONTs that depend on the DDMC file cannot work
properly.
Caution:
If the packetfile is used for an upgrade, there is no impact after the
upgrade to the version that solves the problem. If the problem occurs
during patch installation, the solution takes effect only after the
system is reset.
2.3 V100R020C10SPH315
2.3.1 General Issues
Trouble Ticket DTS202101150HVIRSP1200
Number
Problem Condition: The standby control board is removed during a hot reset.
Description Symptom: When the standby control board is replaced, the active
control board also resets.
Impact: The system resets.
Severity Major
Root Cause After the active/standby switchover, if the standby control board is
removed when it is not in the normal state, there is a possibility that
an error is returned when the host uninstalls the microcode jump
patch. As a result, the active control board resets.
Severity Minor
Root Cause When the SerDes data of the standby control board is obtained, the
input parameters are incorrect. As a result, the link status is
incorrectly registered.
Solution Parameters are correctly transmitted when the SerDes data of the
standby control board is obtained.
Severity Minor
Root Cause In the ISSU scenario, the prejoin function does not generate new
program ordering entries. As a result, the program stream cannot be
imported to the OLT when no user is watching a program. In
addition, after the prejoin function is disabled, the system displays a
message indicating that no user is watching the program.
Solution In the ISSU scenario, the prejoin function re-generates the ordering
entries.
Severity Minor
Problem Condition: The standby control board is in the config state, and a
Description service board is replaced with another service board with a different
number of ports.
Symptom: Services on some ports are unavailable.
Impact: User services are affected.
Severity Major
Root Cause During the system startup, there is a low probability that
active/standby synchronization and board replacement occur at the
same time. As a result, a time sequence error occurs during data
synchronization, and the port mapping relationship of the new board
is not synchronized to the standby control board, causing services on
some ports of the new service board to be unavailable.
Solution During board replacement, the system checks the topology. If the
number of ports changes and the standby control board is in the
config state, the system does not respond to the board registration
request until the standby control board is normal.
Severity Minor
Solution Impact 1. The periodical auto-save of the system may conflict with other
operations of the user.
2. It is recommended that the customer proactively plan
configuration auto-save.
Severity Minor
Root Cause When searching for an ONT by SN, the system needs to decrypt the
SN and password of the ONT. If the master key obtained is a special
key, the code process considers that the key is invalid and obtains
the master key again. As a result, it takes a long time to obtain the
master key.
Solution The code is modified so that a special key is considered valid and
does not need to be obtained again.
Severity Minor
Problem Condition: The board in-position signal jitters (usually because the
Severity Minor
Root Cause The board in-position signal jitters. As a result, when the
energy-saving shutdown polling is performed, the SerDes link is
shut down after the board in-position signal is detected as offline.
After the board in-position signal recovers, the SerDes link is not
recovered.
Severity Minor
Root Cause After the device runs for a long time, the low-end memory is
insufficient. As a result, the ONT data is not synchronized to the
standby control board. After the active/standby switchover, the ONT
data is missing, causing the PPPoE dialup failure.
Solution ONT data consistency is checked and the ONT data restoration
mechanism is optimized to prevent data loss.
Severity Minor
Severity Minor
Root Cause Correctly set the in-position status flag of the optical module on the
EPON board during the ISSU.
Solution Re-set the in-position flag of the optical module on the EPON
board.
Severity Minor
Root Cause After an optical module is inserted,the LOSi alarm is reported again
due to a processing error.
Number DTS2022041315718
Severity Minor
Root Cause During ONT loading, the system does not check the validity of
resources before resource occupation and release.
Solution During ONT loading, the system checks the validity of resources
before resource occupation and release.
Severity Minor
Root Cause The system incorrectly determines the GPON port type. As a
result,a failure message is returned.
Severity Major
Root Cause The ONT WAN information query through the TL1 NBI conflicts
with the XML loading task that does not respond. As a result,the
query fails.
Solution When a user queries the ONT WAN information through the TL1
NBI, the NMS stops an XML loading task if it does not respond.
Problem Condition: When residual ONT virtual port data exists in the
Description database, an ONT is added or the board resets.
Symptom: There is a possibility that the ONT fails to be added.
When the board is reset, the configuration recovery may fail and the
board cannot start up.
Impact: Service provisioning and board startup are affected..
Severity Minor
Root Cause When a board is in the configuration recovery state and ONTs fail to
be added in batches, there is a possibility that data in the ONT
virtual port table fails to be deleted during data rollback.
Solution Impact The current solution can prevent residual data in subsequent
operations. However, if residual data exists on a device before the
upgrade, you need to activate the configuration file to restore the
data.
Severity Minor
Root Cause When massive alarms are generated,there is a low probability that
the buffer queue of the control board discards messages. As a result,
the ONT power-off information is not updated in time, causing
inaccurate time.
Solution Expand the buffer queue of the control board to reduce the number
of discarded messages.
Severity Major
Root Cause When a large number of TypeB dual-homing protection groups are
configured on a device, a large number of protection group
handshake messages are sent between the protection groups every
second. As a result, there is a low probability that the
communication between the control board and service boards is
affected. As a result, the service boards are reset unexpectedly.
2.4 V100R020C10SPH312
2.4.1 General Issues
Trouble Ticket DTS2022040110280
Number
Severity Minor
Severity Minor
Root Cause The board does not support service flow creation and therefore does
not support service flow subscription. When KPI subscription is
normal, the board delivers service flow subscription and upper-layer
protocol messages to the board. Because the board does not support
service flow subscription, subscription reporting is disabled.
Problem Condition: The system is reset after the PIM multicast cascade port
Description is configured to statically join a multicast group.
Symptom: There is a possibility that the system resets for multiple
times.
Impact: Services are interrupted and the device cannot work
properly.
Severity Minor
Root Cause Messages between multicast processes are not reported in sequence.
The message indicating that the static program goes online is
received in advance. The component is not initialized and accesses a
null pointer. As a result, the system resets.
Severity Minor
Root Cause 30s after the NMS delivers the upgrade, the device does not reset
because it takes a long time to dump debug logs. Therefore, the
device can still respond to the NMS and returns the source version.
As a result, the NMS reports that the version is inconsistent with the
target version and the upgrade fails.
Solution After the device enters the reset process, it does not respond to the
version query message sent by the NMS after the upgrade.
Severity Minor
Root Cause The reliability of the alarm module is insufficient. As a result, the
abnormal alarm whose serial number is 0 is not processed.
Solution The system filters out the alarm with serial number 0 during an
active/standby switchover.
Severity Minor
Root Cause There is a low probability that an error occurs during ARP
initialization. As a result, ARP packets sent to the CPU are
incorrectly processed. As a result, the device fails to learn ARP
entries and becomes unreachable to the NMS.
Solution The ARP initialization process has been optimized to ensure that
ARP packets can be correctly processed.
Severity Minor
Root Cause When slave ports are added, the port VLAN data of the active port
is synchronized. After receiving a large number of messages, the
standby control board cannot process them in a timely manner. As a
result, message resources are exhausted and messages are lost, and
hardware entries are not correctly updated.
Severity Minor
Solution The LACP verification function is added to check the status of the
Severity Minor
Root Cause The CPU usage is high during telemetry service flow collection and
ONT rate collection.
Solution The collection process is optimized so that the secondary core of the
board is used for processing.
Solution Impact When a patch is activated or deactivated, the statistical period data
of telemetry service flow collection and ONT rate collection is
inaccurate.
Severity Critical
Root Cause The flash memory of the xPON component is damaged. As a result,
the standby control board fails to start after synchronization.
Solution Impact When the flash memory of the xPON component is damaged, the
time for area switching is shortened.
Severity Minor
Severity Minor
Root Cause The original eMDI process configures, deletes, and queries eMDI
monitoring instances by polling hardware ports. However, for the
H906CGHF and H907CGHF boards, only half of PON ports can be
polled.
Severity Minor
Root Cause During the startup, the system detects residual board data and starts
the deletion process. When deleting service flows, the system clears
QoS data. However, QoS data has not been initialized. As a result,
the system accesses a null pointer and resets.
Problem Condition: The U2000 issues the command for adding an ONT
Description through the TL1 NBI.
Symptom: The error message "The ONT does not exist" is
displayed, indicating that the ONT fails to be added.
Impact: There is a possibility that work orders fail to be processed.
Severity Minor
Root Cause When the U2000 issues an ONT adding command carrying ONT
description information through the TL1 NBI, the U2000 adds the
ONT and then modifies the ONT configuration description. The
modification operation depends on the result of an asynchronous
operation in the ONT adding process. There is a possibility that the
asynchronous operation is not complete when the description is
modified. In this case, an error message is returned.
Severity Minor
Root Cause When processing the upper-layer protocol response, the device
determines that the TLV length is different from that reported by the
board. As a result, an error occurs.
Solution In the response processing function for the upper-layer protocol, the
value for checking the TLV length is modified to be consistent with
that of the board.
Severity Minor
Root Cause When a large number of communities are powered off, the ONT
power-off alarms are processed after xPON messages are discarded.
Solution When a large number of communities are powered off, the ONT
power-off alarms are processed before xPON messages are
discarded.
Severity Minor
Root Cause The NMS saves only the database but does not issue the upper-layer
protocol to the board.
Severity Minor
Severity Minor
Root Cause No command is available to limit the number of ONTs that can be
added to a single PON port.
Solution A command is added to limit the number of ONTs that can be added
to a single PON port.
Problem Condition: The optical power of an EPON ONT is lower than the
Description preset threshold for the ONT to go online.
Symptom: An ONT whose optical power is lower than the
threshold cannot go online.
Impact: User requirements cannot be met.
Severity Minor
Root Cause The EPON and 10G EPON boards do not support the setting of the
optical power threshold for ONTs to go online.
Severity Major
Root Cause When the board queries the ONT Rx optical power, multiple OMCI
response messages have time sequence dependency. If the time
sequence is incorrect, the data cannot be parsed. As a result, the
ONT Rx optical power cannot be queried.
Problem Condition: When the ONT software loading progress reaches 20%
Description or higher, the board is reset.
Symptom: After the board is recovered, the loading fails.
Impact: There is a low probability that ONT loading fails when
certain conditions are met.
Severity Major
Root Cause When the error flag bit is cleared during the ONT loading, other
data is deleted by mistake, which causes ONT loading failures in
certain cases.
Solution A redundant operation is deleted when the error flag bit is cleared.
2.5 V100R020C10SPH311
2.5.1 General Issues
Trouble Ticket DTS2021122904228
Number
Problem Condition: The combined bin package file is loaded to the system
Description with a CP patch and the system resets.
Symptom: The board reports a hardware fault alarm (alarm ID:
0x02310018).
Impact: The board fails to be automatically loaded.
Severity Minor
Root Cause Failed to obtain the SP version number during automatic loading.
Solution The SP field of the app version number is obtained from the
self-check result of the automatic loading message reported by the
board.
Problem Condition: Boards are reversely installed in the subrack for the first
Description time.
Symptom: After the device is powered on, the board inserted
reversely cannot start up.
Impact: User deployment is affected.
Severity Major
Root Cause When multiple reversely inserted boards of the same type are
powered on at the same time, the control board takes a long time to
process different tasks. As a result, the boards do not respond to the
requests from the control board.
Problem Condition: The configuration file fails to be saved after the save
Description command is issued.
Symptom: The configuration file fails to be saved. As a result, the
database fails to be saved.
Impact: Database saving is affected.
Severity Minor
Root Cause Due to process restriction of the save command, after the
configuration file fails to be saved, the system returns and does not
continue to save the database.
Solution The save command is used to save the configuration file and
database. The configuration file is saved before the database. If the
configuration file fails to be saved, the system continues to save the
database. If the configuration file fails to be saved, the save
configuration failure is recorded in the user log. If the database fails
to be saved, the save data failure is recorded in the user log. If the
save operation is successful, no log is recorded.
The process of automatic saving is different from that of the save
command, but the specifications are the same. If the configuration
fails to be saved, a failure log is also recorded.
Severity Minor
Root Cause The normal operating range of the temperature sensor on the
H903CGHD board is changed to (10, 90).
Problem Condition: A board supporting secure boot shares the .bin file with
Description an old board, and the board software is reversely loaded.
Symptom: When the reversely loaded board software is pushed to
the board, the board verification fails and the push fails.
Impact: When a newly added board that supports secure boot shares
the .bin file with an old board, the board software reversely loaded to
the control board cannot be loaded to the board.
Severity Minor
Root Cause After the board software is reversely loaded, the EFS tail of the old
board is truncated.
Solution The EFS tail of the old board is not truncated during reverse loading.
Severity Minor
Root Cause The xPON app database is damaged due to DDR change.
Solution When the database is read, written, deleted, or modified, the table
header is based on the table header information provided by the
xPON.
Severity Minor
Root Cause After the device is started from the partition without board software,
an alarm is generated, indicating that important files are damaged.
Solution During the startup, the system checks whether the device starts from a
partition with board software. If not, the system sets the next startup
partition to the peer partition and resets the system.
Severity Major
Severity Minor
Root Cause When hwCliUserLevel is used to obtain the current user level, if the
obtained user level is super admin 4, the user level is directly set to
admin 3. As a result, the user level is 3, and the admin user cannot be
added.
Solution When hwCliUserLevel is used to obtain the current user level, the
mechanism of converting the super admin level to the admin level is
canceled. When the user level is read as super admin, the value is
directly returned.
Severity Minor
Root Cause The input parameter of the function for processing PLOAM packet
statistics on the PON port is incorrect. Specifically, oltId which is
always 0 is input where chId should be input. As a result, the
PLOAM packet statistics of the combo board are always invalid, and
the PLOAM packet statistics of the GPON board are incorrect.
Solution Modify the input parameters for calling the PLOAM API layer
function in the functions related to PLOAM packet statistics of the
PON port so that chId and the corresponding error record function
input parameters are passed.
Description ONTs, GPON ONTs in profile mode, and GPON ONTs in distributed
mode.
Symptom: The password in the reported trap is empty.
Impact: O&M personnel cannot view the password in the trap.
Severity Major
Root Cause When an ONT is added, the password filled in the trap is incorrectly
cleared.
Problem Condition: After an ISSU upgrade, the display epon llid alloc-record
Description command is executed to query LLID allocation records.
Symptom: The ONT ID and authentication mode corresponding to
the LLID cannot be queried.
Impact: The query of LLID allocation records is affected.
Severity Major
Root Cause After the ISSU upgrade, the LLID allocation record table is not
restored.
Solution The system regenerates the LLID allocation record table after an
ISSU upgrade.
Severity Major
Root Cause The issued OMCI does not meet the requirements of the third-party
ONT.
Severity Minor
Root Cause A large number of ONT power-off alarms are reported at the same
time. As a result, the alarm buffer queue of the control board is
discarded. In subsequent batch queries, the ONT DGi offline time is
updated to the batch query time.
Solution When DGi and ONT offline messages are reported, the device
updates the offline time based on the first-come principle.
Severity Major
Root Cause The system accesses invalid memory when processing the
community power-off alarms.
Problem Condition: The ONT is connected to the PON port and is being
Description automatically discovered.
Symptom: The ONT SN in the auto-find event and trap is displayed
in hexadecimal notation.
Impact: Integration with the third-party NMS is affected.
Severity Minor
Root Cause In the auto-find trap, SNs of Huawei and third-party ONTs are
displayed in hexadecimal notation.
Severity Minor
Root Cause Some data collection modes are not supported by third-party ONUs,
and some data cannot be collected in bulk mode.
Solution The following four Bulk GPON ONU collection items are added for
all ONUs:
pmp-gpon-nni-tran-frames(713)
pmp-gpon-nni-recv-frames(714)
pmp-gpon-nni-tran-discard-frames(715)
pmp-gpon-nni-recv-discard-frames(716)
2.6 V100R020C10SPH310
2.6.1 General Issues
Trouble Ticket DTS2022011710361
Number
Severity Major
Solution Each type of collection task applies for only one memory space.
Severity Major
Root Cause The extracted entries delivered by the NMS contain OIDs that do not
support data collection.
Solution After the collection is started, if a node that does not support the
collection is found, the node is deleted from the database that returns
the configuration entry.
Severity Minor
Root Cause Ports on the H901ACSA board are incorrectly added to VLAN 1. As
a result, the query of services in VLAN 1 is affected.
Severity Minor
Root Cause By default, the NAC channel is enabled for all device types.
Solution For devices that support the slave mode, the NAC channel function is
enabled by default, and a configuration file is generated when the
function is disabled. For devices that do not support the slave mode,
the NAC channel function is disabled by default, and a risk warning
message and configuration file are generated when the function is
enabled. If the user has made configurations, the user configurations
remain unchanged.
Solution Impact The default value of the NAC channel switch transparent remote is
modified.
Severity Minor
Solution Impact Added the command modify templetname level super command.
Severity Minor
Root Cause The default configuration of the SSH key exchange algorithm
contains an insecure algorithm.
Solution When the device starts from an empty database, the insecure key
exchange algorithm is disabled by default.
Note: SHA1 is disabled by default only when the device starts from
an empty database.
Severity Minor
Root Cause The processing flow of the board in slot 2 and the replacement flow
of the board in slot 1 operate the same queue at the same time. As a
result, queue messages fail to be read in the replacement flow, the
number of NPs fails to be updated, and the board configuration fails
to be restored.
Solution In the board primitive queue function, if the primitive check fails, the
board primitive check is performed again.
Problem Condition: Before an upgrade, the alarm function for system power
Description consumption protection or the power-off function is enabled.
Symptom: After the upgrade, the alarm function for system power
consumption protection or the power-off function is disabled.
Impact: User configurations are modified.
Severity Minor
Solution The alarm function for system power consumption protection or the
power-off function is disabled by default. In upgrade scenarios, the
user configuration is not modified.
Solution Impact This problem can be solved only by loading the bin file. The system
power-protect power-off and system power-protect alarm
commands are modified. Specifically, the default is changed from
enabled to disabled.
Severity Minor
Root Cause By default, the auto-save type is data. That is, only the database is
saved, and the configuration file is not saved.
Solution When the system starts from an empty database, the default auto-save
type is all, indicating that both the database and configuration file are
saved.
Solution Impact The default value of the autosave type {all | configuration | data}
command is changed from data to all.
1. In the new deployment scenario, the default value of the auto-save
type is changed to all.
2. In the upgrade scenario, the original configuration remains
unchanged. However, if the original configuration is data, the
autosave type data configuration is added.
Problem Condition: Two users go online in the same multicast group, and one
Description user goes offline for a period of time and then goes online again.
Symptom: The eMDI monitoring statistics contain abnormal packet
loss statistics.
Impact: eMDI quality monitoring deployment is affected.
Severity Minor
Root Cause After the user goes offline, the multicast ingress table is not deleted.
The eMDI table is bound to the ingress table and is not deleted either.
The slot for the offline user still has the eMDI entry. If a user in this
slot watches the program again, the RTP sequence number of the
received packet is re-collected, and the value differs greatly from the
last_SN value in the eMDI instance. The system determines that
packet loss occurs.
Solution When the first user goes online from a board, an eMDI instance is
added. When the last user goes offline from a board, an eMDI instance
is deleted.
Problem Condition: A large number of DHCP users exist on the device during
Description the upgrade.
Symptom: After the upgrade, the device runs slowly and a large
number of users fail to dial up.
Impact: DHCP dialup and device running are affected.
Severity Major
Solution The DHCP dialup process is optimized so that dialup packets are
processed as soon as possible and the user online rate is increased.
Problem Condition: The system starts from an empty database, and the save
Description operation is performed.
Symptom: The default value of the NAC channel switch is not saved
to the database.
Impact: The database does not match the configuration.
Severity Minor
Root Cause The default value of the NAC channel switch is not saved to the
database during initialization.
Solution When the patch is activated, the system sets the default status of the
NAC channel switch based on whether a device supports the slave
function and saves the setting to the database.
Severity Major
Root Cause The MIB upload next message reported by the part third-party ONT is
different from that defined in the Huawei proprietary protocol. As a
result, the OLT fails to process the message.
Solution The MIB upload next message reported by the part third-party ONT
can be correctly processed by the OLT.
Note: Affected online ONTs need to be reset or re-registered.
Severity Major
Root Cause An error occurs in smooth processing of port alarm resources during
active/standby synchronization.
Solution Ensure that port alarm resources are correctly processed during
active/standby synchronization.
Severity Major
Root Cause The system incorrectly processes the bandwidth of static multicast
programs issued to third-party ONTs.
Solution Ensure that the bandwidth of static multicast programs issued to the
third-party ONTs is normal.
Note: You need to reset the ONT for the patch to take effect.
Severity Major
2.7 V100R020C10SPH308
2.7.1 General Issues
Trouble DTS2021073010575
Ticket
Number
Severity Major
Root Cause In the DHCP remote software commissioning process, the Layer 3
interface fails to be obtained.
Solution The process of obtaining the Layer 3 interface in DHCP remote software
commissioning is optimized.
Solution None
Impact
Trouble DTS2021101324646
Ticket
Number
Severity Minor
Root Cause In the device recovery phase, the system selects a board based on the MAC
address. There is a low probability that the system fails to select a board.
As a result, the MAC address fails to be queried.
Solution None
Impact
Trouble DTS2021101811781
Ticket
Number
Description Condition: The NP IMS module of the SD5122 board has a hardware
error.
Severity Major
Root Cause When a hardware error occurs on the NP IMS module of the SD5122
board, the fault is not rectified.
Solution Fault recovery is supported for a hardware failure in the NP IMS module
on the SD5122 board.
Solution None
Impact
Trouble DTS2021090911592
Ticket
Number
Severity Minor
Root Cause The method to start the timer is incorrect when multicast traffic is obtained.
Solution A proxy thread is used to start the timer when multicast traffic is obtained.
Solution None
Impact
Trouble DTS2021101415452
Ticket
Number
Description Condition: After the system is upgraded or reset, a large number of DHCP
users dial up at the same time.
Symptom: A large number of users fail to go online.
Impact: DHCP dialup fails.
Severity Minor
Root Cause When a large number of users perform DHCP dialup at the same time, too
many messages are sent between the DHCP and UDM modules.
Congestion may occur and some messages are discarded. As a result, users
cannot dialup successfully.
Solution The message processing mechanism between the UDM and DHCP
modules has been optimized so that messages can be processed quickly.
Solution None
Impact
Trouble DTS2021101710262
Ticket
Number
Description Condition: The SD5122 board (such as H902CGHF) has been running for
137 days.
Symptom: The SD5122 board resets abnormally.
Impact: Services are interrupted for about 5 minutes.
Severity Major
Root Cause The array subscript is out of range. As a result, the board is reset.
Solution Check the array subscript. If the array subscript exceeds the maximum
value, record the array subscript cyclically.
Solution None
Impact
Trouble DTS2021092216204
Ticket
Number
Severity Suggestion
Root Cause Patch V100R020C10SPH307 registers the capability set of the H901FGHF
board. As a result, the board profile file and board software cannot be
reversely loaded.
Solution During automatic loading, if the H901FGHF board is used, the board
software can be reversely loaded. When the profile file is enabled, if the
H901FGHF board is used, the profile file needs to be saved to the database
instead of restoring only 10GE parameters. To enable the H901FGHF
board to support the GPON and combo modes, install
V100R020C10SPH308 or a later patch.
Solution None
Impact
Trouble DTS2021092724068
Ticket
Number
Severity Minor
Root Cause There is a low probability that multicast data fails to be synchronized in the
program recovery process during active/standby synchronization.
Solution The process of synchronizing data between the active and standby control
boards is optimized.
Solution None
Impact
Trouble DTS2021090726673
Ticket
Number
Description Condition: ZTP and DCN remote software commissioning are enabled
with an empty database.
Symptom: The port is blocked and services are unavailable.
Impact: Service functions are affected.
Severity Major
Root Cause Internal configurations are delivered when the DCN remote software
commissioning function is deleted. If the DHCP remote software
commissioning function also delivers internal configurations, the operation
times out and exits unexpectedly. As a result, residual configurations exist.
Solution None
Impact
Trouble DTS2021091014546
Ticket
Number
Description Condition: The active and standby SerDes links are faulty.
Symptom: No hardware fault alarm is reported(alarm ID: 0x02310018).
Impact: MAC address learning fails, and services are affected.
Severity Minor
Root Cause The chassis is damaged. As a result, all SerDes links between the active
and standby control boards are faulty.
Solution A suspension detection process is added for the SerDes links between the
SE(switching chip) on the standby control board and the NP(forwarding
mode) on the active control board.
Solution None
Impact
Trouble DTS2021093013558
Ticket
Number
Description Condition: When the system detects a reset reason that is not included in
the reset reason list that can be detected, the reason is displayed as
command line reset.
Symptom: The displayed reset reason is incorrect.
Impact: Users cannot determine the reset reason.
Severity Minor
Root Cause After the system starts, it reads the reset reason from the RAM and
determines the reset reason. If the reset reason is not in the reset reason list
that can be detected, the system considers that the reset is caused by
command lines by default.
Solution The character string indicating the unknown reset reason is changed from
the default command line reset to unknown.
Solution The value of the Reset Reason parameter in the event 0x023000f4 system
Impact startup is changed.
Trouble DTS2021091014432
Ticket
Number
Severity Minor
Root Cause The board reversely loads the profile file to the device. When the device
parses the profile file based on the buff, the byte order of the length
information is not converted. As a result, the length is incorrectly parsed
(AUTOLOAD_ReverseBackupFileByTftp). The parsed length is far
greater than the actual length, leading to overflow and device reset.
Solution None
Impact
Trouble DTS2021092313228
Ticket
Number
Severity Minor
Root Cause The bottom-layer hardware entries are not deleted, and the new entries fail
to be queried. As a result, the port traffic cannot be queried.
Solution None
Impact
Severity Minor
Root Cause The logic for clearing alarms in the batch query task of the board is
incorrect.
Solution The logic for clearing alarms in the batch query task is corrected.
Solution None
Impact
Trouble DTS2021091311698
Ticket
Number
Description Condition: Multiple XG-PON ONTs that do not support GEM port
encryption are connected to a GPON board, and GEM port encryption is
enabled.
Symptom: The CPU usage of the board remains high.
Impact: The board performance is affected.
Severity Minor
Root Cause After GEM port encryption is enabled for XG-PON ONTs, the OLT issues
OMCI messages to the ONTs to enable encryption. If an ONT does not
support the OMCI message, an error is returned and the OLT keeps trying
to issue the OMCI message. As a result, a large number of OMCI messages
are exchanged between the board and the ONT.
Solution If an XG-PON ONT does not support GEM port encryption, the OLT does
not keep issuing GEM port encryption commands.
Solution None
Impact
Trouble DTS2021090818177
Ticket
Number
Description Condition: The RSSI detection for a standby PON port on a board fails all
the time.
Symptom: The RSSI of other standby PON ports cannot be measured and
displayed.
Impact: RSSI detection for standby ports is affected.
Severity Major
Root Cause The RSSI detection for standby PON ports is performed on the board in
turn. If the RSSI detection for a PON port fails, the detection is performed
again. If the RSSI detection for the PON port fails all the time, the RSSI
detection of other PON ports cannot be scheduled.
Solution Each PON port is detected only once and no retry is performed.
Solution None
Impact
Trouble DTS2021073112419
Ticket
Number
Symptom: The query result is different from the actual number of ONTs
when the ifIndex is used as the leaf of mib walk
hwGponDeviceOntConfigInfoTable
and hwEponDeviceOntConfigInfoTable.
Impact: The MIB walk result is affected.
Severity Minor
Root Cause When the MIB walk operation is performed on the CLI with IfIndex as the
parameter, the query starts from VS ONT-ID 0. When the global ONT-ID
fails to be queried using VS ONT-ID, no special processing is performed
on the query result of the global ONT-ID. As a result, the invalid value of
Global ONT-ID is directly used for subsequent query operations.
Solution None
Impact
Trouble DTS2021082721648
Ticket
Number
Description Condition: The active port in a type B protection group is quickly removed
and re-inserted, triggering an LOS alarm (alarm ID: 0x2e11a001) but not
an alarm (alarm ID: 0x2e11a523) indicating that the standby port has no
optical signal.
Symptom: The LOS alarm cannot be cleared.
Impact: The alarm is falsely reported.
Severity Minor
Root Cause The LOS alarm on the standby port depends on the no optical signal alarm
on the standby port. Fast removal and re-insertion do not trigger the no
optical signal alarm on the standby port. Therefore, the no optical signal
clear alarm and LOS clear alarm are not generated on the standby port.
Solution A timer task is started during protection group switching. If the no optical
signal alarm is not generated for the standby port but an LOS alarm is
generated, a LOS clear alarm is generated.
Solution None
Impact
Trouble DTS2021082721799
Ticket
Number
Description Condition: An ONT version is loaded in SFTP mode and the SFTP
configuration is incorrect.
Symptom: After the SFTP server configuration is corrected, the loading
still fails.
Impact: The ONT fails to load the version software.
Severity Minor
Root Cause The status transition logic after an ONT loading failure is incorrect. As a
result, the loading task cannot be obtained.
Solution The status transition logic of the ONT loading task is modified to ensure
that the system can obtain the loading task again.
Solution None
Impact
Trouble DTS20210727038ZR5P0D00
Ticket
Number
Severity Major
Root Cause When an E2E service flow is created by running a command, there is a low
probability that the task is switched. As a result, the DDM task is executed
first and the GEM data is restored first. When the task is switched to the
CLI again, it is found that the GEM data already exists. As a result, the
service flow fails to be created.
Solution The delay and retry operations are added to ensure that data can be
successfully updated even if the task is switched.
Note: If this issue has occurred, it cannot be resolved by loading the
V100R020C10SPH308 patch. To resolve this issue, activate the
configuration file.
Solution None
Impact
Trouble DTS2021092417204
Ticket
Number
Severity Major
Root Cause In the ONT configuration recovery phase, the MAC address configuration
is queried. If the MAC address configuration does not exist, the MAC
address configuration is created.
Solution When the MAC address is queried, if the MAC address configuration does
not exist, a query failure message is returned.
Solution None
Impact
Trouble DTS2021091321128
Ticket
Number
Description Condition: Strict check for the ONT access type is enabled.
Symptom: The NMS fails to add ONTs to the GPON or XG-PON board.
Impact: Service functions are affected.
Severity Major
Root Cause The ONT access type issued by the NMS to the OLT is auto. When strict
ONT access type check is enabled, the ONT access type fails to pass the
check.
Solution The strict ONT access type check function is disabled by default.
Solution None
Impact
Trouble DTS2021092224062
Ticket
Number
Severity Major
Root Cause After the DDM quick query function of the optical module is enabled, the
cache value is obtained in SNMP mode. The cache value is updated every
hour.
Solution 1. The database upgrade tool is modified so that the function of quickly
querying the DDM status of an ONT optical module is disabled by default
Solution The default value of the xpon ont optical-ddm quick-query command is
Impact changed from enable to disable.
Trouble DTS2021092221937
Ticket
Number
Description Condition: The GPON board connects to a specified ONT, and the CUC
interoperation mode is configured.
Symptom: Configurations fail to be restored after the ONT is reset.
Impact: ONT services are affected.
Severity Minor
Root Cause The CUC interoperation mode is configured, but the ONT does not report
its capability set during its reset. As a result, the ONT configurations fail to
be restored.
Solution A retry mechanism is added for the scenario where ONT configurations
fail to be recovered due to the failure to obtain the ONT capability set. The
configurations fail to be recovered only after three consecutive trials.
Solution None
Impact
Trouble DTS2021080616820
Ticket
Number
Severity Major
Root Cause After a Flex-PON board is replaced with an XGS-PON board, the Alloc-ID
is not re-allocated and exceeds the valid range.
Solution After a Flex-PON board is replaced with an XGS-PON board, the Alloc-ID
is re-allocated to the valid range.
Solution None
Impact
2.8 V100R020C10SPH307
2.8.1 General Issues
Trouble DTS2021082019583
Ticket
Number
Problem Conditions:
Description 1. A third-party ONT is connected to a GPON board in controllable
multicast mode.
2. The multicast service is configured and the IGMP version of multicast
users is set to IGMPv2.
3. The IGMP packets sent from an ONT to the OLT are constructed by
the ONT.
Symptom: The multicast user fails to order programs.
Impact: The multicast service fails.
Severity Major
Root Cause The multicast user version configured on the OLT is IGMPv2, but the
ONT sends IGMPv3 Report packets to the OLT. As a result, the IGMP
version does not match, and IGMPv3 Report packets are discarded.
Solution The version configuration for multicast users is corrected for the ONT.
Solution None
Impact
Trouble DTS2021090210928
Ticket
Number
Problem Conditions:
Description 1. An earlier version is upgraded to V100R020C10.
2. The fan registration time is longer than 1 minute.
3. The fan software fails to be automatically loaded.
Symptom: The fan is faulty.
Impact: The fan upgrade fails and the fan is faulty.
Severity Major
Root Cause From EMU registration to load, the fault detection timer is in the polling
state and does not restart during the registration process. As a result, the
EMU does not send the reset message after the loading is complete.
Solution During fault timeout processing, the system restarts the timer after
determining that a fan is still in the registration process.
Solution None
Impact
Trouble DTS2021090928121
Ticket
Number
Problem Conditions:
Description 1. The version is V100R020C10.
2. The FGHF board is used.
Symptom: The FGHF board supports only the GPON mode.
Impact: The working mode cannot be switched to Combo.
Severity Minor
2.9 V100R020C10SPC303
2.9.1 General Issues
Trouble Ticket DTS202106020DYK1UP0G00
Number
Severity Minor
Root Cause The service board is powered off abnormally. As a result, the
master/slave channel and inter-board communication fail. The OLT
does not have a self-healing mechanism for this exception scenario.
Severity Minor
Root Cause The board is in poor contact but no alarm indicating that the board
cannot be detected is generated. The active SerDes between the
board and control board is disabled, the standby SerDes is available,
and multicast packets are lost.
Solution The system determines whether the SerDes link between the control
board and service board is normal after receiving a board offline
message. If the SerDes link is normal, check whether the forwarding
plane is normal. If services on the forwarding plane are normal, do
not trigger the faulty board process. If the SerDes link is abnormal,
the faulty board process is triggered and the board offline alarm
(alarm ID: 0x02310000) is reported.
Severity Minor
Root Cause The index field of the GPON port attribute table in the database is
abnormal due to byte change in the flash memory.
Severity Minor
Root Cause After the control board is replaced, no hardware fault alarm is
reported.
Solution The device can detect and report the hardware fault alarm (alarm ID:
0x02310018).
Problem Conditions:
Description 1. The version is R19C1XSPH219 or later.
2. The OLT is configured with the H906CGHF service board.
3. Multicast user prejoin is configured.
4. Multicast program streams are forwarded to the OLT upstream
board.
Symptom: The active and standby system control boards report an
(100, 86) hardware fault.
Impact: A false alarm indicating multicast service abnormality is
reported.
Severity Major
Root Cause The mechanism for detecting multicast packet loss on the
H906CGHF board has a bug, and a small number of historical lost
packets are considered as continuous packet loss. As a result, a false
alarm is reported.
Severity Minor
Root Cause Some devices in the configuration file do not support command lines.
Problem Condition: A large number of ONTs are powered off at the same
Description time and a large number of alarms are generated.
Symptom: Alarms are lost on the NMS GUI.
Impact: Some alarms may be lost or cannot be cleared.
Severity Minor
Root Cause When a large number of ONTs are powered off at the same time, a
large number of alarms are generated. As a result, the alarm
component on the host receives a large number of messages in a short
period of time. There is a possibility that messages overstock and
RPC messages cannot be processed within 10s. As a result, some
alarms are lost.
Solution The RPC mechanism is modified. In the earlier version, the app
directly sends an RPC request to the CFG. In this version, the app
writes the queue, reads the queue, and then sends an RPC request to
the CFG.
Problem Condition: The MAC address of the peer server of the service
Description network port starts with 0800.
Symptom: The OLT MPSA fails to ping the peer DHCP server.
Impact: Layer 3 services are affected.
Severity Minor
Root Cause When a packet is delivered, the system checks whether it is an IPv4
packet based on the fixed offset of the packet. A packet delivered by
the service network port carries a user-defined packet header, and the
first two bytes of the MAC address header are incorrectly matched.
As a result, the packet content is incorrect.
Solution The service network port does not match IPv4 packets and
transparently transmits packets.
Problem Condition: The hardware signals of the active and standby control
Description boards are abnormal, a hardware fault alarm is reported.
Symptom: The hardware signal is abnormal. A service board resets
repeatedly.
Impact: Services are unavailable.
Severity Minor
Root Cause The active/standby signals of the OLT are abnormal. The
management packets of a service board are filled with incorrect
information about the destination control board. As a result, the
management packets are discarded, the communication between the
service board and the control board is interrupted, and the service
board resets repeatedly.
Description online.
Symptom: Services are still normal after the ONT goes offline.
Impact: User management is affected.
Severity Minor
Root Cause Linkport forwarding entries are not completely deleted after an ONT
goes offline.
Solution Ensure that forwarding entries are deleted after an ONT goes offline.
Severity Major
Root Cause After the H902GPHF board is replaced with the H902CSHF board,
the topology of the bottom-layer ports changes, and the forwarding
entries created on the service board and upstream board are not
updated. As a result, the forwarding is incorrect and the service fails.
Solution When the H902GPHF board is replaced with the H902CSHF board,
MSC_SecNotifyNPIDChange re-issues the MAC address entries to
the board.
Severity Minor
Root Cause The connection between the device and NMS is not backed up to the
standby control board. As a result, the connection needs to be
re-established during ISSU.
Solution The connection between the device and the NMS needs to be backed
Severity Major
Root Cause When the IPv6 routing table is updated, there is a low probability that
the index is incorrectly calculated. As a result, the obtained reindex
value is incorrect, causing subsequent forwarding exceptions and
packet loss.
Solution The index calculation process during IPv6 routing table update is
optimized.
Problem Condition: The NMS remotely connects to an ONT on the web page.
Description Symptom: There is a possibility that the ONT fails to be connected.
Impact: The ONT cannot be connected.
Severity Minor
Root Cause When a socket is created, the socket detection range for received
packets is incorrectly set. As a result, a socket is not included in the
detection range.
Problem Condition: The device starts from an empty database, triggers DHCP
Description remote software commissioning, and DHCP remote software
commissioning is performed.
Symptom: All upstream ports change from up to down, and the
sysman server source ssh any-interface configuration remains.
Impact: The residual configurations do not affect services.
Severity Minor
Severity Major
Root Cause When a board is repeatedly added and deleted, the data in the UMAC
mapping table is not deleted. After multiple operations, the UMAC
mapping table has no remaining space. When DHCP dialup is
performed again, the CHADDR field in the DHCP packet is not
replaced with VMAC. As a result, the service fails.
Solution When deleting a PTP, the system finds the UMAC data of the PTP
and clears the data.
Severity Major
Solution The underlying driver has been modified to ensure that the operating
system data is consistent, preventing packet modification.
Severity Minor
Severity Minor
Root Cause An incorrect interface is used to obtain private data for the type B
dual-homing protection group.
Solution The interface for obtaining the private data of dual-homing type B
protection is modified.
Severity Minor
Root Cause When Telemetry collects RSSI and SD information about a Flex
board, the system does not check whether the optical module is a
combo optical module. As a result, when the optical module type is
XGS, an incorrect process is used.
Severity Minor
Root Cause After OMCI verification is enhanced, the messages reported by the
third-party ONT do not comply with the standard protocol. As a
result, an error is returned when the OLT checks the message, and
PQ-related capabilities cannot be detected when configurations are
issued. Consequently, ONT configurations fail to be restored.
Severity Major
Root Cause During bulk collection, a large number of OMCI messages are
exchanged in a short period of time. After componentization, the
message performance deteriorates.
Severity Minor
Root Cause During CTC version negotiation, the response message of the ONU is
abnormal and is discarded by the OLT. As a result, the ONU
go-online process is interrupted.
Problem Condition: A user queries the information about ONUs bound with
Description an abnormal SNMP profile.
Symptom: The information about the ONUs bound with the abnormal
SNMP profile cannot be queried, and the NMS cannot synchronize
certain information about ONUs bound with the abnormal SNMP
profile.
Impact: Users cannot obtain information about the ONUs bound with
the abnormal SNMP profile.
Severity Minor
Root Cause The SNMP profile data of the OLT is incorrect. As a result, the
SNMP profile fails to be parsed.
Solution After detecting incorrect data, the OLT proactively corrects the
incorrect data.
Severity Minor
Root Cause The SNMP profile data of the OLT is incorrect. As a result, the
SNMP profile fails to be parsed.
Solution After detecting incorrect data, the OLT proactively corrects the
incorrect data.
Problem Condition: The OLT continuously collects the peak rate of an ONU.
Description Symptom: There is a possibility that the periodic peak rate of the
ONU is abnormally high.
Impact: The periodic peak rate collected from the ONU is inaccurate.
Severity Minor
Root Cause An abnormal value is collected when the ONU calculates the peak
rate.
Solution Filter the data that exceeds the maximum port rate of the board.
Severity Minor
Root Cause When NCE delivers a subscription without a source port, telemetry
reports the source port as 0 by default. After NCE receives the
packets, it distributes the packets to random nodes for packet assembly
and processing. As a result, the parsing is incorrect.
If the source port is not configured in the subscription, the source port
is 0 by default during reporting, and the problem occurs in the
following two scenarios:
1. Some firewalls may identify these packets as invalid packets and
discard them.
2. 0 is considered as random packets in many operating systems. After
receiving the packets, NCE distributes the packets to random nodes
for packet assembly. As a result, the packets are incorrectly parsed.
2.10 V100R020C10SPH302
NMS Upgrade Health Check Fails After Upgrade to V100R020C10SPC301
Trouble Ticket DTS202104140FMCR7P1300
Number
Problem Conditions:
Description 1. An earlier version is upgraded to V100R020C10SPC301.
2. The EA5800 is used, and any EMU such as the power supply and
fan is installed on the EA5800.
3. The EMU (power supply or fan) is selected as the health check item
in the NMS upgrade tool.
All the preceding conditions are met.
Symptom:
The fan upgrade check items are inconsistent in the device upgrade
health check. Before the upgrade, the fan check item name is FAN.
After the upgrade, the fan check item name changes to Power (the
check item content is correct). The information is inconsistent, and the
check fails.
Impact:
During the upgrade, the physical status of the EMU (such as the EMU
normal status, fan speed, and temperature) is normal. Only the EMU
health check status collected by the Huawei NCE before and after
the upgrade is inconsistent. The Huawei NMS upgrade report displays
a message indicating that the health status is inconsistent before and
after the upgrade. Except the names, other EMU check items, such as
the fan, are correct. You can view other items without logging in to the
device.
Severity Minor
Root Cause A health check unit is an inherent attribute of each EMU and has a
corresponding global health check unit ID. Huawei NMS collects the
health check unit status before and after the upgrade, generates a
report, and uploads the report to the NMS. The V100R020C10SPC301
version does not verify the health check unit ID of the EMU. As a
result, the health check unit ID reported in the generated report is
incorrect.
Solution The logic for reporting the health check unit ID is corrected.
Solution The modification affects only the EMU report when the health check
report is generated.
Impact
NMS Fails to Deliver a Configuration File to ONTs After the ONT Configuration
File Fails to Be Loaded from NMS to the OLT for More Than 128 Times
Trouble Ticket DTS202104010OY06KP0G00
Number
Severity Major
Root Cause The OLT uses the server information and key specified by NMS to
download and decrypt the file. However, if the file fails to be
downloaded, the OLT does not delete the key entry. As a result, the
key table is full after 128 failures, and new loading cannot be started.
PON Port Traffic Data Collected by the PMI Task Is Invalid After OLT Upgrade
Trouble Ticket DTS202104160F262XP1I00
Number
Problem Condition: The PON Port Traffic check item is selected in the NMS
Description upgrade inspection task during upgrade using the involved version.
Symptom: In the preventive maintenance report generated by the OSS,
the value of PON Port Traffic is invalid.
Impact: The PON port traffic comparison before and after the upgrade
fails to pass the check.
Severity Minor
Root Cause The control board incorrectly checks the data reported by the service
board. As a result, the control board identifies the data as abnormal
data and reports an invalid value.
Solution The process for the control board to verify the PON port traffic data
reported by a service board is corrected.
Solution None
Impact
3 Known Issues
Problem Conditions:
Description The display statistics global command is run to query the downstream
traffic of the PON port.
Symptom:
There is a low probability that traffic is halved.
Impact:
There is a possibility that the queried downstream traffic of a PON
port is inaccurate.
Severity Minor
Preventive None
Measure and
Workaround
Severity Minor
Workaround None
and Emergency
Measure
Severity Minor
Severity Minor
Workaround None
and Emergency
Measure
Description Condition: After two consecutive ONTs are looped back, the first
ONT is undo, the second ONT is undo 10s later, and the ring check
function is enabled.
1. ont loopback ont1
2. ont loopback ont2
3. undo ont loopback ont1
4. undo ont loopback ont2 within 10s
5. ring check enable
Symptom: When the ring check function is enabled, loops cannot be
detected.
Impact: The ONT loop detection function does not take effect.
Severity Minor
Workaround and Run the undo command again to decrease the lock counter to 0.
Emergency
Measure
Description Condition: After the system is reset or upgraded, the save netconf
logfile command occasionally fails to be executed.
Symptom: The save netconf logfile command fails to be executed to
dump data into flash files.
Impact: NETCONF logs are lost after the device is reset.
Severity Minor
Workaround and Reload the V100R020C10SPC303 package and restart the device.
Emergency
Measure