ZXA10 C300V2.0.1P3 Patch Release Notes

Secret▲
ZXA10 C300 V2.0.1P3 Patch

Release Notes
ZXA10 C300v2.0.1 P3 Patch Release Notes Secret▲
Contents
1. version description...................................................................................................................5
2. patch description.......................................................................................................................7
2.1. SCTMB patch............................................................................................................7
2.1.1. SCTMB.BT(Entel)..............................................................................................7
2.1.2. SCTMBV201P3T17_R0.PAT.............................................................................7
2.1.3. SCTMBV201P3T17_R1.PAT.............................................................................7
2.1.4. SCTMBV201P3T17_R2.PAT.............................................................................8
2.1.5. SCTMBV201P3T17_R3.PAT.............................................................................9
2.1.6. SCTMBV201P3T17_R4.PAT...........................................................................10
2.1.7. SCTMBV201P3T17_R5.PAT...........................................................................11
2.1.8. SCTMBV201P3T17_R27.PAT(PTCL)............................................................11
2.1.9. SCTMBV201P3T17_R28.PAT(HKT)..............................................................11
2.2. SCXN patch.............................................................................................................12
2.2.1. SCXNV201P3T17_R0.PAT..............................................................................12
2.2.2. SCXNV201P3T17_R1.PAT..............................................................................12
2.2.3. SCXNV201P3T17_R2.PAT..............................................................................13
2.2.4. SCXNV201P3T17_R3.PAT..............................................................................14
2.2.5. SCXNV201P3T17_R4.PAT..............................................................................14
2.2.6. SCXNV201P3T17_R5.PAT..............................................................................15
2.3. SMXA patch.............................................................................................................16
2.3.1. SMXAV201P3T17_R0.PAT.............................................................................16
2.3.2. SMXAV201P3T17_R1.PAT.............................................................................16
2.3.3. SMXAV201P3T17_R2.PAT.............................................................................17
2.3.4. SMXAV201P3T17_R3.PAT.............................................................................18
2.3.5. SMXAV201P3T17_R4.PAT.............................................................................18
2.3.6. SMXAV201P3T17_R5.PAT.............................................................................19
2.3.7. SMXAV201P3T17_R27.PAT(PTCL)...............................................................19
2.3.8. SMXAV201P3T17_R28.PAT(RCOM).............................................................20
2.4. GTXOG patch.........................................................................................................20
2.4.1. GTXOGV201P3T17_R0.PAT..........................................................................20
2.4.2. GTXOGV201P3T17_R1.PAT..........................................................................20
2.4.3. GTXOGV201P3T17_R2.PAT..........................................................................20
2.4.4. GTXOGV201P3T17_R3.PAT..........................................................................21
2.4.5. GTXOGV201P3T17_R4.PAT..........................................................................21
2.4.6. GTXOGV201P3T17_R5.PAT..........................................................................21
2.4.7. GTXOGV201P3T17_R28.PAT(HKT).............................................................21
2.5. GTGOG patch.........................................................................................................22
2.5.1. GTGOGV201P3T17_R0.PAT..........................................................................22
2.5.2. GTGOGV201P3T17_R1.PAT..........................................................................22
2.5.3. GTGOGV201P3T17_R2.PAT..........................................................................22
2.5.4. GTGOGV201P3T17_R3.PAT..........................................................................22
2.5.5. GTGOGV201P3T17_R4.PAT..........................................................................23
2.5.6. GTGOGV201P3T17_R5.PAT..........................................................................23
2.5.7. GTGOGV201P3T17_R26.PAT(Antel).............................................................23
2.5.8. GTGOGV201P3T17_R27.PAT(NetTelecom)..................................................23
2.5.9. GTGOGV201P3T17_R28.PAT(HKT).............................................................23
2.6. GTGHG patch.........................................................................................................24
2.6.1. GTGHGV201P3T17_R0.PAT..........................................................................24
2.6.2. GTGHGV201P3T17_R1.PAT..........................................................................24
2.6.3. GTGHGV201P3T17_R2.PAT..........................................................................24
2.6.4. GTGHGV201P3T17_R3.PAT..........................................................................24
2.6.5. GTGHGV201P3T17_R4.PAT..........................................................................25
2.6.6. GTGHGV201P3T17_R5.PAT..........................................................................25
2.6.7. GTGHGV201P3T17_R26.PAT(Antel).............................................................25
2.6.8. GTGHGV201P3T17_R27.PAT(NetTelecom)..................................................25
2.7. GTGOE patch.........................................................................................................26
2.7.1. GTGOEV201P3T17_R0.PAT...........................................................................26
2.7.2. GTGOEV201P3T17_R1.PAT...........................................................................26
2.7.3. GTGOEV201P3T17_R2.PAT...........................................................................26
2.7.4. GTGOEV201P3T17_R3.PAT...........................................................................26
2.7.5. GTGOEV201P3T17_R4.PAT...........................................................................26
2.7.6. GTGOEV201P3T17_R5.PAT...........................................................................27
2.8. FTGKB patch..........................................................................................................27
2.8.1. FTGKBV201P3T17_R0.PAT...........................................................................27
2.8.2. FTGKBV201P3T17_R1.PAT...........................................................................27
2.8.3. FTGKBV201P3T17_R2.PAT...........................................................................27
2.9. GDFO patch............................................................................................................27
2.9.1. FTGHAV201P3T17_R0.PAT............................................................................27
2.10. GUFQ/GUSQ/GUTQ/HUGQ patch.....................................................................28
2.10.1. GUCDV201P3T17_R0.PAT.............................................................................28
2.10.2. GUCDV201P3T17_R1.PAT.............................................................................28
2.11. HUTQ patch............................................................................................................28
2.11.1. HUTQV201P3T17_R0.PAT.............................................................................28
2.11.2. HUTQV201P3T17_R1.PAT.............................................................................28
2.12. HUVQ patch............................................................................................................28
2.12.1. HUTQB.FW......................................................................................................28
2.12.2. HUTQBV201P3T17_R0.PAT...........................................................................29
2.12.3. HUTQBV201P3T17_R1.PAT...........................................................................29
2.12.4. HUTQBV201P3T17_R2.PAT...........................................................................29
2.13. XUTQ patch.............................................................................................................29
2.13.1. XUTQV201P3T17_R0.PAT.............................................................................29
2.14. XUVQ patch............................................................................................................29
2.14.1. XUVQ.FW........................................................................................................29
All Rights reserved, No Spreading abroad without Permission of ZTE
Page 3 of 36
2.14.2. XUVQV201P3T17_R0.PAT.............................................................................29
2.14.3. XUVQV201P3T17_R1.PAT.............................................................................30
2.15. CICG patch..............................................................................................................30
2.15.1. CICG.MVR(Entel)............................................................................................30
2.16. CICK patch..............................................................................................................30
2.16.1. CICK_LX.MVR(Indosat).................................................................................30
3. patch limitation..........................................................................................................................31
4. patch upgrade guide..................................................................................................................34
4.1. Download patch........................................................................................................34
4.2. Active patch..............................................................................................................34
4.3. Deactivate patch........................................................................................................34
4.4. Delete patch...............................................................................................................35

Page 4 of 36
1. version description
The detail information of C300V2.0.1P3T17 version is as follows:

card name file name version tag version length build time
CICG CICG.BT V4.0.7 207016 2015-04-03 15:16:00
CICG.FW V2.0.1P3 12748 2015-07-12 02:55:49
CICG.MVR V2.0.1P3 693646 2015-07-12 02:18:54
CICK CICK.BT V4.0.7 330092 2015-04-22 09:35:46
CICK.FW V2.0.1P3 59015 2015-07-12 02:55:49
CICK_LX.MVR V2.0.1P3 2435224 2015-07-12 02:55:49
CTLA CTLA.BT V4.0.7 374320 2015-04-03 15:16:00
CTLA.FW V2.0.1P3 32227 2015-07-12 02:55:49
CTLA.MVR V2.0.1P3 969721 2015-07-12 02:56:29
CTBB/CTTB CTTB.BT V4.0.7 391008 2015-04-03 15:16:00
CTTB.FW V2.0.1P3 35538 2015-07-12 02:55:49
CTTB.MVR V2.0.1P3 893055 2015-07-12 02:56:37
CTUB CTUB.BT V4.0.7 218820 2015-04-03 15:16:00
CTUB.FW V2.0.1P3 30797 2015-07-12 02:55:49
CTUB_LX.MVR V2.0.1P3 2664644 2015-07-12 02:56:01
GDFO FTGHA.BT V4.0.7 244948 2015-04-03 15:16:01
FTGHA.FW V2.0.1P3 391056 2015-07-12 02:55:58
FTGHA_LX.MVR V2.0.1P3 8570392 2015-07-12 02:55:56
FTGKB FTGKB.BT V4.0.7 524288 2015-04-03 15:16:01
FTGKB.FW V2.0.1P3 85188 2015-07-12 02:55:58
FTGKB.MVR V2.0.1P3 5378520 2015-07-12 02:55:53
GTGHG GTGHG.BT V4.0.7 524288 2015-04-03 15:16:01
GTGHG.FW V2.0.1P3 212070 2015-07-12 02:56:15
GTGHG_LX.MVR V2.0.1P3 6008372 2015-07-12 02:56:36
GTGOE GTGOE.BT V4.0.7 387072 2015-04-03 15:16:02
GTGOE.FW V2.0.1P3 4306150 2015-07-12 02:56:12
GTGOE_LX.MVR V2.0.1P3 5141068 2015-07-12 02:56:30
GTGOG GTGOG.BT V4.0.7 524288 2015-04-03 15:16:02
GTGOG.FW V2.0.1P3 139607 2015-07-12 02:56:15
GTGOG_LX.MVR V2.0.1P3 5980984 2015-07-12 02:57:23
GTXOG GTXOG.BT V4.0.7 524288 2015-04-03 15:16:02
GTXOG.FW V2.0.1P3 9214567 2015-07-12 02:56:25
GTXOG_LX.MVR V2.0.1P3 5918884 2015-07-12 03:00:03
GUFQ/ GUCD.BT V4.0.7 228176 2015-04-03 15:16:02
GUSQ/ GUCD.FW V2.0.1P3 170103 2015-07-12 02:56:33
GUTQ/HUGQ GUCD_LX.MVR V2.0.1P3 2275103 2015-07-12 02:55:48

Page 5 of 36
HUTQ HUTQ.B V4.0.7 190420 2015-04-03 15:16:02

HUTQ.FW V2.0.1P3 35846 2015-07-12 02:56:33
HUTQ_LX.MVR V2.0.1P3 2376680 2015-07-12 02:56:53
HUVQ HUTQB.BT V4.0.7 265068 2015-04-03 15:16:03
HUTQB.FW V2.0.1P3 130368 2015-07-12 02:56:33
HUTQB_LX.MVR V2.0.1P3 2568732 2015-07-12 02:56:12
SCTMB SCTMB.BT V4.0.7 324568 2015-04-03 15:16:03
SCTMB.FW V2.0.1P3 1300319 2015-07-12 02:55:40
SCTMB_LX.MVR V2.0.1P3 27845232 2015-07-12 03:00:49
SCXN SCXN.BT V4.0.7 524288 2015-04-03 15:16:03
SCXN.FW V2.0.1P3 10919855 2015-07-12 02:55:36
SCXN_LX.MVR V2.0.1P3 23351967 2015-07-12 02:59:52
SMXA SMXA.BT V4.0.7 524288 2015-07-14 02:13:18
SMXA.FW V2.0.1P3 735289 2015-07-12 02:55:41
SMXA_LX.MVR V2.0.1P3 22324636 2015-07-12 02:59:43
XUTQ XUTQ.BT V4.0.7 228176 2015-04-03 15:16:04
XUTQ.FW V2.0.1P3 15427 2015-07-12 02:56:52
XUTQ_LX.MVR V2.0.1P3 2275103 2015-07-12 03:23:24
XUVQ XUVQ.BT V4.0.7 265088 2015-07-02 02:02:50
XUVQ.FW V2.0.1P3 111632 2015-07-12 02:56:53
XUVQ_LX.MVR V2.0.1P3 2562476 2015-07-12 02:55:46
FAN.FW V3.0 61474 2015-05-15 14:08:46
PM.FW V2.0.1P3 934 2015-07-12 02:56:53

Page 6 of 36
2. patch description
2.1. SCTMB patch
2.1.1. SCTMB.BT(Entel)
The released patches are as follows:
released times patch description
1 Problems1 are solved, the patch date is 2016-2-22.
The problems solved by this patch are as follows:

No. problem description
1 There is a fan control problem in the startup procedure of SCTMB, which will cause the
SCTMB cannot work.
2.1.2. SCTMBV201P3T17_R0.PAT
1 Sometimes a software exception occurs when FFP rules are configured in SSP module,
and if the system reboot in this case, the standby main-control board will stay in
configuring state.
2 In some kind of unknown particular situation, unexpected loop-back happens in switch
chip ports, and that will cause the corresponding system uplink port down. It’s an
avoidance scheme.
3 The traffic statistics in the system uplink ports will not change in a long period, which is
found in Vietnam.
4 The temperature is added in the crash file when the system crash is caused by high
temperature.
5 Switch chip is busy caused by DHCPv4 server down.
6 There exists memory access violation in the GET function in the optical module MIB
table.
7 If the no.1 vport is not created in the onu, then the traffic template configured in other
vports will not occur when running the “show running” command.
8 If the self-adaptive port in GUSQ board is connected with an Ethernet switch and is used
as a in-band network management channel, then no packets can be sent from the port, and
the network management channel is broken.
9 There exists memory access violation in the getnext function in zxAnGponRmOnuEntry
table, which will cause the SNMP walk operation towards this table into endless loop.
10 The BOOT upgrade process is changed from “first upgrade, then verify” to “first verify,
then upgrade”.
11 The next hop could not be deleted when the subnet routing configuration is failed.

Page 7 of 36
1 When the system is fully configured, there exists a 10-seconds interruption in LACP
service in Jazztel.
2 In Shanxi, when the ARP proxy of OLT-1 is enable, the voice gateway MAC address of
OLT-2 turned into the in-band MAC address of OLT-1.
3 The value range of PATH-COST parameter should be changed from 0-65565 to 1-65565
according to the standards,
4 The CRC check mechanism is added in main control board.
5 If the 802.1x data is not configured in user ports, the operation will cause the system halt
for a few minutes.
6 There is some mistakes in the string handling logic of the telnet server code, which will
cause the telnet server crash.
7 The slice memory is destroyed when accessing the EPON MIB.
8 There are some mistakes in the compatible processing of “show gpon uncfg onu gpo-
onu_1/x/x” with version1.2.5 in RDS Romania.
9 A wrong vlan 0 has been added in IGMP report message when OLT working in IGMP
snooping mode.
10 RX frames for GEMport CTP History PM are not reported
11 When the ring network is upgraded in Pakistan, the power-off of one C320 OLT will
easily lead to the out of control problem of another C320 OLT.
12 When configuring with the SIP profile in network management software, the user name is
displayed null.
13 The “start viewing time” record in the CDR file uploaded by C300 is not correct, and the
time in the name of that file is not correct too.
14 There is a mistake in supporting SNMPv3.
15 The inner ports of CES cards turn down when the stand-by switch happens.
16 In Pakistan, the No. 5 port in SCTMB panel is found not supporting forced 100M mode
17 There is a mistake in SDK semaphore which will cause the system halt.
18 The telnet 9999 password function is added in SCTMB.
19 In some kind of unknown particular situation, unexpected loop-back happens in switch
chip ports, and that will cause the corresponding system uplink port down.
1 Problems1-21 are solved, the patch date is 2015-12-15.
3 Only for RDS，Problems1-21 are solved, the patch date is 2015-12-25.

Page 8 of 36

1 The alarm cannot be reported correctly through SNMPv1.
2 There exists an SNMP asynchronous operation error which will cause the system crash.
3 In the Turkey TurkNet, the SNMP Get operation of the non-leaf node will cause the
system crash.
4 In the Turkey TurkNet, a certain date-field is not supported which cause the TACACS
authentication is denied incorrectly.
5 There exists a LACP sudden break error in C300V2.0.2.
6 The software in main-control board is halted when the IGMP static item is added.
7 The system cannot switch in Vietnam.
8 There exists an error in CFM module which cause the low priority rule of packet filtering
to CPU loss when the Ethernet OAM function is configured.
9 The switch chip in the main control board cannot filter the packets with TTL 1 to the CPU.
10 In Jazztel, when the system standby switch, the user cannot get IP address, and "invalid ip
hash item" is printed.
11 The TX Packets Rate,RX Packets Rate,Tx Octets Peak Rate and Rx Octets Peak Rate are
showed inconsistently between the command line and the network management software.
12 There are several MIBs' indexes are used incorrectly in Ethernet historical performance
statistics.
13 The network management software will be in no response for several minutes when
opening the onu serviceport management GUI.
14 When the system standby switch happens, there exists some certain probability causing
the flow carrier in the layer3 interface.
15 When the "ff.f.ff.ff" source ip address is configured through the network management
software, a error will reported incorrectly.
16 There exists a MFF error which will cause the voice registration failure.
17 There exists an compatible problem of the blank character in SIP dialplan rule.
18 There exists a short break(less than 1s) in the data flow when the UAPS n*n protectiong
switchover between the panel ports of the master and slave main-control boards.
19 The SNMP walk operation to the "zxAnOpticalModuleGlobalObjects" table will cause a
endless loop problem.
20 The order of accessing the MUX interface is adjusted to solve the multicast flow break
problem in Jazztel.
21 There exists a problem in zxAnIgmpMgmtMVlanEntry table which cause the filter
configuration invalid when multi variables are binding.

Page 9 of 36

1 There is an sudden break error in LACP found in C300V2.0.2 version, and two
modifications should be made:(1)muxQ copy mechanism;(2)memory leak in
telnet.
2 The definition of mld mvlan query-max-response MIB entry is not the same
between the C300 and the network management system.
3 There is a 10s break in uplink-port when the system standby after the MAC anti-
drift is enabled.
4 There exists some certain probability that the switch task and the msanprot task
will concurrent conflict, which will cause the system crash.
5 There is an memory error in “show pon power” command which can cause the
system crash.
6 Photoelectric conversion module is not supported.
7 The port status is incorrect when the photoelectric conversion module is plugged
while not connected with wires.
8 There is an temperature display error in Viettel.
9 HUKQ is supported.

1 If the ERPS is disabled, the port will be blocked when the system restart.
2 When testing the NE using TELNET and SNMP alternately, the management channel will
break which is caused by lack of protection of Tlist.
3 All the alarm restore cannot be reported to SYSLOG.
4 When the FTGKB card is configured in slot 1, the corresponding commands are missed in
port 1 and 2.
5 There are over 1000 SFTP connects opened while not closed, which caused the
system resource is exhausted.
6 The GPONI-IP profile cannot be deleted.
7 When querying the optical-module parameters in some certain slots, an “N/A”
result will returned.
8 When the Octets reaches 4294967295 in ONU Ethernet statistics, “-1” will display in the
Network Management system.
9 Our equipment originally only supports domain 0, while domain 4 is expected in Turkey.

Page 10 of 36
10 The “grandmasterid” and “mastered” fields are added in “show time ptp” command.
11 ARP messages in the list will not be forwarded on the backboard.
12 All the cards are in HWONLINE status except SCTMB.
13 The inner port of SCTMB is down happened in Thailand True.

1 The password can be read when using “show cmdlog” command in Pakistan.
2 If there is type configuration in remote template, the operation of binding template will
fail.
3 The validity checking for SNMP operation of germport speed limiting is missing, which
will cause problem in service.
4 There is a sudden break in Ipv6 data flow.
5 There exists a daylight saving time problem in IPTV service.
6 If we run testing scripts in the initial stage of the system startup duration, it’s
possible to cause “mpnat” task hang up.
7 If we run testing scripts to delete and add card repeatedly, it’s possible to cause the card
crash.
8 When the ERPS mode changed from “non-revertive” to “revertive”, the ERPS state cannot
restore to “idle”.
9 If the 10GE port is forced to GE port, the service will break after the port is shutdown and
reopened.
2.1.8. SCTMBV201P3T17_R27.PAT(PTCL)
1 Problem1 are solved, the patch date is 2016-7-4.

1 There exists a service sudden break problem in XUTQ.
2.1.9. SCTMBV201P3T17_R28.PAT(HKT)

Page 11 of 36

1 The “restore WIFI” command line is added for Hong Kong HKT project.
2 Multi-PKG is supported under ONU for Hong Kong HKT project.
2.2. SCXN patch
2.2.1. SCXNV201P3T17_R0.PAT
configuring state.
found in Vietnam.
3 Switch chip is busy caused by DHCPv4 server down.
table.
then upgrade”.
service in Jazztel.
for a few minutes.

Page 12 of 36

snooping mode.
displayed null.
15 The inner ports of CES cards turn down when the stand-by switch happens.

system crash.
8 There exists an error in CFM module which cause the low priority rule of packet filtering
to CPU loss when the Ethernet OAM function is configured.
statistics.

Page 13 of 36
problem in Jazztel.

telnet.
drift is enabled.
system crash.

Page 14 of 36

port 1 and 2.

fail.

Page 15 of 36
crash.
2.3. SMXA patch
2.3.1. SMXAV201P3T17_R0.PAT
configuring state.
found in Vietnam.
3 Unknown unicast and broadcast speed limit will not take effect towards the ports in the
FTGKB borad when FTGKB is used together with SMXA.
table.
then upgrade”.
service in Jazztel.
for a few minutes.

Page 16 of 36
snooping mode.
displayed null.
15 The HIGIG port between the stand-by main-control boards will turn down when the stand-
by switch happens.

system crash.
statistics.

Page 17 of 36
problem in Jazztel.
21 The update of the BFD instance configuration will cause the system halted.

telnet.
drift is enabled.
system crash.

Page 18 of 36

port 1 and 2.
12 The software version cannot be read in the card manager in the Network Management
System.

fail.
crash.

Page 19 of 36
8 There exists a 1588 clock problem when using the slave uplink.
2.3.7. SMXAV201P3T17_R27.PAT(PTCL)
1 Problems1 is solved, the patch date is 2016-5-16.

1 In Pakistan PTCL, the Network Management System cannot connect to the C300 element.
It’s caused by the switch chip error.
2.3.8. SMXAV201P3T17_R28.PAT(RCOM)
1 Problems1 is solved, the patch date is 2016-5-26.

1 The neighbor relationship cannot be established in LLDP.
2.4. GTXOG patch
2.4.1. GTXOGV201P3T17_R0.PAT
1 The software access towards the damaged PON-MAC chip through PCIE interface will
cause system hung-up.
then upgrade”.
1 One-second recovery mechanism will be active even if the action-2 is not enabled.
2 There are many memory application errors in Hebei and Shanxi which is caused by OMCI

Page 20 of 36
code.
1 There exists an registration abnormal and a data mis-ordering problem when ONU is
authenticated by PW mode.
3 An error in list handling will cause the card halted.
4 There exists some mutual interactions between the unauthenticated onus and the
authenticated ones in LOID mode, which might cause some onus to a false working status.
5 The Huawei ONU cannot be in the online status in Dominican because of the self
negotiation problem in extended OMCI mechanism.
1 There are mistakes in statistics for oversize packets((including 4 byte CRC, more than
1518 bytes) found in Lithuania.
2 When deleting the receive port of an aggregation group, there exists an “out of memory”
error which may cause “mcasttask” task halt.
1 There is a black screen error when switching multicast service. The reason is that the static
MAC items can cover the dynamic MAC items.
2 The switch may be crash because its cache is overflow in the system startup
procedure.
3 The security port-protect cannot take in effect when the upward packets are double-
tagged.
1 There is a multicast service break in Portugal, which can only be restored by deleting and
reconfiguring the remote ONU parameters.
2 The downward traffic drops suddenly together with ONU offline in Singapore.
3 The DyingGasp inform is reported but actually the ONU is on power.

Page 21 of 36

5 In the Mexico Telmex GPON full configuration test, sometimes the GPON card stay in
“hwonline” state when the system standby.
2.4.7. GTXOGV201P3T17_R28.PAT(HKT)
2 When we change the password of ONU in ONU, the OLT doesn’t update it.
2.5. GTGOG patch
2.5.1. GTGOGV201P3T17_R0.PAT
2 New optical module is added to support OTDR operation.
3 The data flow in individual onus is broken in a 128-onus fully-configured PON interface,
and these individual onus will not go into online state after remote reboot through OMCI
interface.
then upgrade”.
code.

Page 22 of 36
2 There exists a logic problem in TM initialization which may cause the inner port down in
some certain slots.
tagged.
1 There is an error in WTD optical module happened in Thailand.
2.5.7. GTGOGV201P3T17_R26.PAT(Antel)
1 Solve the CIR-PIR problem in Antel.

Page 23 of 36
2.5.8. GTGOGV201P3T17_R27.PAT(NetTelecom)
1 The multicast service cannot work when xconnect is configured.
2.5.9. GTGOGV201P3T17_R28.PAT(HKT)
2 When we change the password of ONU in ONU, the OLT doesn’t update it.
2.6. GTGHG patch
2.6.1. GTGHGV201P3T17_R0.PAT
interface.
then upgrade”.
code.

Page 24 of 36

6 Prevent the CPLD upgrade to the newest version.
7 The timer of sn waiting for windows need to be enlarged to 20 ticks to avoid ONU offline
towards GTGHG card.
some certain slots.
tagged.
1 There is an error in WTD optical module happened in Thailand.

Page 25 of 36
2.6.7. GTGHGV201P3T17_R26.PAT(Antel)
1 Solve the CIR-PIR problem in Antel.
2.6.8. GTGHGV201P3T17_R27.PAT(NetTelecom)
1 The multicast service cannot work when xconnect is configured.
2.7. GTGOE patch
2.7.1. GTGOEV201P3T17_R0.PAT
interface.
then upgrade”.
code.

Page 26 of 36
1 There is an IPTV multicast service error when switching channels happened in Liaoning.
some certain slots.
1 An abnormal value will display when reading temperature of the “Zhengyuan” optical
module.
2.8. FTGKB patch
2.8.1. FTGKBV201P3T17_R0.PAT
then upgrade”.
2 There exists error in FTGKB no.1 port in PCCW Hong Kong.
1 The RX optical power of some optical modules cannot be read in Hong Kong.

Page 27 of 36

1 The downward rate of PTP port can only reach 100M in Lightspeed in USA.
2.9. GDFO patch
2.9.1. FTGHAV201P3T17_R0.PAT
then upgrade”.
2.10. GUFQ/GUSQ/GUTQ/HUGQ patch
2.10.1. GUCDV201P3T17_R0.PAT
service in Jazztel.
2.10.2. GUCDV201P3T17_R1.PAT
2.11. HUTQ patch
2.11.1. HUTQV201P3T17_R0.PAT
service in Jazztel.
2.11.2. HUTQV201P3T17_R1.PAT
1 When the system standbys or we restart the uplink card, the uplink port may be

Page 28 of 36
down.
2.12. HUVQ patch
2.12.1. HUTQB.FW
1 If the 10GE port is forced to GE port, the service will break after the system restart.
2.12.2. HUTQBV201P3T17_R0.PAT
module.
1 The Ethernet type field of the packet will be changed when sending the specific
MAC address “xx.xx.xx.xx.11.xx”.
reopened.
2.13. XUTQ patch
2.13.1. XUTQV201P3T17_R0.PAT
1 When the system standbys or we restart the uplink card, the uplink port may be

Page 29 of 36
down.
2.14. XUVQ patch
2.14.1. XUVQ.FW
1 If the 10GE port is forced to GE port, the service will break after the system restart.
2.14.2. XUVQV201P3T17_R0.PAT
module.
2.14.3. XUVQV201P3T17_R1.PAT
1 The Ethernet type field of the packet will be changed when sending the specific
MAC address “xx.xx.xx.xx.11.xx”.
reopened.
2.15. CICG patch
2.15.1. CICG.MVR(Entel)
1 A new power product(DU68) cannot be managed.
2.16. CICK patch
2.16.1. CICK_LX.MVR(Indosat)
1 A new power product(DU68) cannot be managed.

Page 30 of 36

Page 31 of 36
3. patch limitation
The patch limitation is described as follows:

No. patch limitation
1 SCTMB/SCXN/SMXA Need to restart system after activating the
R0/R1/R2/R3/R4 patch to eliminate the failure.
GTGHG/GTGOG/GTGOE R0/R2
FTGKB/HUTQB R2
XUVQ R1
2 SCTMB/SCXN/SMXA R1 For the following problem, if the system up-link
GUCD/HUTQ R0 port is configured as the GE optical port in
GUFQ/GUSQ/HUTQ, the
SCTMB/SCXN/SMXA R1 patch and the
GUCD/HUTQ R0 patch must be activated at
the same time to eliminate the failure.
（ 1 ） When the system is fully configured,
there exists a 10-seconds interruption in LACP
service in Jazztel.
3 SCTMB/SCXN/SMXA R2 For the problem “There exists an compatible
GTGHG/GTGOG/GTGOE R2 problem of the blank character in SIP
dialplan rule.”, please notice the following
items:
(1)the main-control board patch must be used
together with the gpon board patch;
(2)If this patch is used on the upgrade
occasion from 1.2.X to 2.0.1P3 and we want to
use the “segmentation method based on user
configuration” in 1.2.X, then we must first
upgrade the version, then active the patch,
and restart without saving the configuration.
(3)If this patch is used in 2.0.1P3 just for
compatible to the old-version ONUs, then we
just need to active the patch.
4 GTGHG/GTGOG/GTGOE R2 For the problem “There exists an registration
abnormal and a data mis-ordering problem
when ONU is authenticated by PW mode.”,
please notice the following items:
(1)we need to delete the old configuration
and configure again;
(2) If the fault phenomenon has emerged, do

Page 32 of 36
not perform reset command under PON port

before delete the configuration,, otherwise
all onus cannot work normally.
5 SCTMB/SCXN/SMXA R3 For the problem “There is a 10s break in
uplink-port when the system standby after
the MAC anti-drift is enabled..”, please
notice the following items:
Need to disable/enable the global MAC anti-
drift switch or restart the system after
activating the patch to eliminate the failure.
6 SCTMB/SCXN/SMXA R4 For the problem ”The GPONI-IP profile
cannot be deleted”, (1)in a master-slave
configuration environment, we must activate
the patch ,restart the slave and then
standby; (2)in a single-master configuration
environment, we must activate the patch
and restart the system.
7 GTGOG/GTGHG/GTXOG R4 For the problem ”The security port-protect
cannot take in effect when the upward
packets are double-tagged”, we must delete
the “arp anti spoofing” configuration before
activating the patch, and reconfigure it after
activating the patch.
8 GTGOG/GTGHG R26(Antel) Need to restart the GTGOG/GTGHG card
after activating the patch to eliminate the
failure.
9 SCTMB/GTXOG/GTGOG For the following problem, the main-control
R28(HKT) board patch and the gpon board patch must
be activated at the same time to eliminate the
failure.
（ 1 ） The “restore WIFI” command line is
added for Hong Kong HKT project.
10 SMXA R28(RCOM) The LLDP function should be closed before
activating the patch, and reopen LLDP again
after activating the patch.
11 SCTMB/SCXN/SMXA R5 For the following problem, the main-control
GTGHG/GTGOG/GTGOE/GTXOG board patch and the gpon board patch must
R5 be activated at the same time to eliminate the
failure.
（ 1 ） There exists a daylight saving time
problem in IPTV service.
12 HUTQB.FW/XUVQ.FW Need to restart after activating the patch to

Page 33 of 36
eliminate the failure.

Page 34 of 36
4. patch upgrade guide
4.1. Download patch
file download patch [patch name]
Configure FTP server just like version downloading. Then download the patch into C300.
For example:
ZXAN# file download patch sctmbV201p3t17_r0.pat
Downloading from host (10.63.196.193)
Transferring file sctmbV201p3t17_r0.pat..
......[Successfully]
ZXAN# file download patch gtxogV201p3t17_r0.pat

Downloading from host(10.63. 196.193)
Transferring file gtxogV201p3t17_r0.pat ...
.......[Successfully]
4.2. Active patch
patch active [patch name]
Active the patch downloaded. Then the patch will work, do not reset system or any cards.
For example:
ZXAN#patch active sctmbV201p3t17_r0.pat
Active patch in shelf 1 slot 10 success
Active patch finished
ZXAN#patch active gtxogV201p3t17_r0.pat

Active patch in shelf 1 slot 4 success
Active patch finished
4.3. Deactivate patch
Patch deactive [patch name]

Deactive a patch which is actived.
For example:
Page 35 of 36
ZXAN# patch deactive sctmbV201p3t17_r0.pat

Deactive patch in shelf 1 slot 10 success
Deactive patch finished
ZXAN#patch deactive gtxogV201p3t17_r0.pat

Deactive patch in shelf 1 slot 4 success
Deactive patch finished
4.4. Delete patch
file delete patch [patch name ]

Delete a patch from C300 permanently.
For example:
ZXAN# file delete patch sctmbV201p3t17_r0.pat
Confirm to delete?[yes/no]:y
Start deleting file
deleting sctmbV201p3t17_r0.pat.
[Successfully]
ZXAN# file delete patch gtxogV201p3t17_r0.pat

Confirm to delete?[yes/no]:y
Start deleting file
deleting gtxogV201p3t17_r0.pat..
[Successfully]

Page 36 of 36

ZXA10 C300V2.0.1P3 Patch Release Notes

Uploaded by

Copyright:

Available Formats

You might also like

ZXA10 C300V2.0.1P3 Patch Release Notes

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

ZXA10 C300V2.0.1P3 Patch Release Notes

Uploaded by

Copyright:

Available Formats

Secret▲

ZXA10 C300 V2.0.1P3 Patch

All Rights reserved, No Spreading abroad without Permission of ZTE

The detail information of C300V2.0.1P3T17 version is as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

HUTQ HUTQ.B V4.0.7 190420 2015-04-03 15:16:02

All Rights reserved, No Spreading abroad without Permission of ZTE

2.1. SCTMB patch

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

2 Problems1-9 are solved, the patch date is 2016-5-23.

The problems solved by this patch are as follows:

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

1 Problems1-2 are solved, the patch date is 2015-12-21.

The problems solved by this patch are as follows:

2.2. SCXN patch

All Rights reserved, No Spreading abroad without Permission of ZTE

7 The slice memory is destroyed when accessing the EPON MIB.

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

2.3. SMXA patch

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

1 Problems1-12 are solved, the patch date is 2016-5-10.

The problems solved by this patch are as follows:

The problems solved by this patch are as follows:

All Rights reserved, No Spreading abroad without Permission of ZTE

The problems solved by this patch are as follows:

The problems solved by this patch are as follows:

2.4. GTXOG patch

All Rights reserved, No Spreading abroad without Permission of ZTE

All Rights reserved, No Spreading abroad without Permission of ZTE

4 There exists a daylight saving time problem in IPTV service.

2.5. GTGOG patch

All Rights reserved, No Spreading abroad without Permission of ZTE

All Rights reserved, No Spreading abroad without Permission of ZTE

2.6. GTGHG patch

All Rights reserved, No Spreading abroad without Permission of ZTE

3 An error in list handling will cause the card halted.

All Rights reserved, No Spreading abroad without Permission of ZTE

2.7. GTGOE patch

All Rights reserved, No Spreading abroad without Permission of ZTE

2.8. FTGKB patch

All Rights reserved, No Spreading abroad without Permission of ZTE