Вы находитесь на странице: 1из 23

Confidential▲

Technical Document
Technical Document Name: ZXA10 C300 V1.2.5P2 Patch Release
Specification
Technical Document No.:
Version:

Totally 23 Pages
(Cover Included)

Prepared by / Date
Reviewed by / Date
Approved by / Date

Wireline R & D Institute

ZTE CORPORATION

Contents
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

1. Release Records of Each V1.2.5 Cold / Hot Patch.....................................................................4


1.1. 2013-10-22..................................................................................................................4
1.2. 2013-10-28..................................................................................................................4
GTGOC.FW, GTGOA.FW (V1.2.5P2T7)..................................................................................4
1.3. 2013-11-15..................................................................................................................4
1.4. SCXN.BT (2013.12.5) and SMXA.BT (2013.12.18), ETGHG_LX.MVR (P2T7)...4
2. Specification on Each V1.2.5 Hot Patch.....................................................................................4
2.1. SMXAV125P2T6_r1.pat.............................................................................................4
2.1.1. Brief Introduction of the Patch...........................................................................4
2.1.2. Fault Specification..............................................................................................4
2.2. SCXLV125P2T6_r2.pat, SCXMV125P2T6_r2.pat, SCXNV125P2T6_r2.pat,
SMXAV125P2T6_r2.pat.............................................................................................................5
2.2.1. Brief Introduction of the Patch...........................................................................5
2.2.2. Fault Specification..............................................................................................5
2.3. SCXLV125P2T6_r3.pat, SCXMV125P2T6_r3.pat, SCXNV125P2T6_r3.pat,
SMXAV125P2T6_r3.pat.............................................................................................................7
2.3.1. Brief Introduction of the Patch...........................................................................7
2.3.2. Fault Specification..............................................................................................7
2.4. SCXLV125P2T6_r4.pat, SCXMV125P2T6_r4.pat, SCXNV125P2T6_r4.pat,
SMXAV125P2T6_r4.pat.............................................................................................................9
2.4.1. Brief Introduction of the Patch...........................................................................9
2.4.2. Fault Specification..............................................................................................9
2.5. GTGOGV125P2T6_r1.pat........................................................................................12
2.5.1. Brief Introduction of the Patch.........................................................................12
2.5.2. Fault Specification............................................................................................12
2.6. GTGOAV125P2T6_r2.pat, GTGOCV125P2T6_r2.pat, GTGOEV125P2T6_r2.pat,
GTGOGV125P2T6_r2.pat, GTGHGV125P2T6_r2.pat...........................................................13
2.6.1. Brief Introduction of the Patch.........................................................................13
2.6.2. Fault Specification............................................................................................13
2.7. GTGOGV125P2T6_r3.pat, GTGHG V125P2T6_r3.pat..........................................14
2.7.1. Brief Introduction of the Patch.........................................................................14
2.7.2. Fault Specification............................................................................................14
2.8. GTGOAV125P2T6_r1.pat, GTGOCV125P2T6_r1.pat...........................................16
2.8.1. Brief Introduction of the Patch.........................................................................16
2.8.2. Fault Specification............................................................................................16
2.9. ETGOV125P2T6_r1.pat...........................................................................................16
2.9.1. Brief Introduction of the Patch.........................................................................16
2.9.2. Fault Specification............................................................................................16
2.10. ETGOV125P2T6_r8.pat...........................................................................................17
2.10.1. Brief Introduction of the Patch.........................................................................17
2.10.2. Fault Specification............................................................................................17
2.11. ETXDCV125P2T6_r1.pat, ETTOV125P2T6_r1.pat...............................................18
2.11.1. Brief Introduction of the Patch.........................................................................18
All Rights reserved, No Spreading abroad without Permission of ZTE
Totally 23 Pages Page 2
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

2.11.2. Fault Specification............................................................................................18


3. Specifications on Each V1.2.5 Cold Patch...............................................................................19
3.1. HUTQB.FW, SCXN.FW (V1.2.5P2T7)...................................................................19
3.2. GTGOC.FW, GTGOA.FW (V1.2.5P2T7)................................................................19
3.3. HUTQ.BT (V1.2.5P2T7)..........................................................................................19
3.4. GTGOE.FW (V1.2.5P2T7).......................................................................................19
4. V1.2.5 Patches to be Released..................................................................................................19
5. Patch Upgrading Guide.............................................................................................................19
5.1. Upgrading Preparation..............................................................................................19
5.2. Upgrading Steps........................................................................................................20
5.3. Rollback Steps...........................................................................................................21
5.4. Upgrading Confirmation...........................................................................................22
5.5. Update Precautions...................................................................................................23

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 3
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

The version that each patch is applicable to is comprised in the patch name, such as
SCXMV123T6_r0.pat, of which, T6 is the internal tag of R & D. Internal tags of each card may be
different, so you only need to pay attention to external tags during engineering commissioning.

1. Release Records of Each V1.2.5 Cold / Hot Patch

1.1. 2013-10-22

Release the hot patch SMXAV125P2T6_r1.pat.

1.2. 2013-10-28

GTGOC.FW, GTGOA.FW (V1.2.5P2T7)

1.3. 2013-11-15

1. HUTQB.FW, SCXN.FW (V1.2.5P2T7), HUTQ.BT (V1.2.5P2T7), GTGOE.FW


(V1.2.5P2T7).
2. GTGOGV125P2T6_r1.pat, GTGOAV125P2T6_r1.pat, GTGOCV125P2T6_r1.pat
(November 15), SCXLV125P2T6_r2.pat (November 13), ETGOV125P2T6_r1.pat
(November 5), ETXDCV125P2T6_r1.pat, ETTOV125P2T6_r1.pat (November 14)

1.4. SCXN.BT (2013.12.5) and SMXA.BT (2013.12.18), ETGHG_LX.MVR (P2T7)

1. To solve the compatibility problem of the new DDR, update the SCXN.BT and SMXA.BT.
2. The ETGHG firmware considered less for ONU OAM abnormal processing, which caused
F401 using PMC MAC to have abnormal registration possibly. Change ETGHG firmware to
modify the problem.

2. Specification on Each V1.2.5 Hot Patch

2.1. SMXAV125P2T6_r1.pat

2.1.1. Brief Introduction of the Patch

None

2.1.2. Fault Specification

1. SN problem in Slot 3
Fault Description: C320 main control card SMXA inserted in Slot 3 failed to perform Read / Write
SN operation. Execute the “show card slotno 3” command, it showed that the SN of the main control
card was null (actually it has already been written). When executing “Write” operation for the main
control card in Slot 3, it would fail.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 4
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Modification Specification: None


Precaution: None

2、 Rebooting the card caused SMXA L3 services interrupted


Fault Description: For the services which needed SMXA to perform L3 forwarding, after the card
was rebooted, it would cause L3 services interrupted until the user side initiated the ARP request after
the card completed rebooting.
Modification Specification: Disable the CPU packet capturing function.
Precaution: None

2.2. SCXLV125P2T6_r2.pat, SCXMV125P2T6_r2.pat, SCXNV125P2T6_r2.pat,


SMXAV125P2T6_r2.pat

2.2.1. Brief Introduction of the Patch

1. 2013-11-13 SCXLV125P2T6_r2.pat has solved Problem 1.


2. 2014-1-16 SCXLV125P2T6_r2.pat, SCXMV125P2T6_r2.pat,
SCXNV125P2T6_r2.pat, SMXAV125P2T6_r2.pat have solved Problem 1 to 8.

2.2.2. Fault Specification

1. Query problem after the patch was activated


Fault Description: After activated, use “show patch-running” but there was nothing shown.

show patch-running
Loc FileName PatchTag OperateTime PatchState

HUVQ and ETGO patches have the problem.


Modification Specification: None
Precaution: None

2. The linkstar show system-group problem


Fault Description: After you set the customized version as linkstar, execute the “show system-
group” command, ZTE-related information was still shown.
Modification Specification: Modify to make it can perform related records.
Precaution: There is no this modification on the SCXM.

3. The problem of linkstar ZTE’s default template


Fault Description: After you set the customized version as linkstar, you could inquire the default
template type of GPON ZTE.
Modification Specification: None
Precaution: There is no this modification on the SCXM.

4. Executing del patch * would cause the suspension of MsanCfg


Fault Description: Executing del patch * would cause the suspension of MsanCfg.
Modification Specification: None

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 5
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Precaution: SCXM, SCXL and SMXA have the problem, while SCXN doesn’t have the problem.

5. Reboot the NE after the patch was activated, patches from r5 to r9 would show “inactive” on
the NMS
Fault Description: Reboot the NE after the patch was activated, the activation status of the patches
from r5 to r9 would show “inactive” on the NMS, and inquire correctly via CLI.
Modification Specification: None
Precaution: None

6. GTGOG uplink interface statistics didn’t support bytes


Fault Description: Due to the chip restriction of the GTGOG, uplink byte-related statistics wasn’t
supported on the PON port.

show interface gpon-olt_1/8/1


gpon-olt_1/8/1 is activate,line protocol is down.
Description is none.
The port link up/down notification is trap disable.
Max onu number: 128. Registered onu number: 41.

OLT statistic:
Input rate : N/A Bps 0 pps
Output rate: 0 Bps 0 pps
Input instantaneous bandwidth throughput : N/A
Output instantaneous bandwidth throughput: 0.0%
Input average bandwidth throughput : N/A
Output average bandwidth throughput: 0.0%
Output multicast instantaneous rate: 0 Bps 0 pps
Interface peak rate:
Input peak rate : N/A Bps 91333 pps
Output peak rate: 5361192 Bps 16825 pps
Total statistic:
Input :
PassPackets :119982764 DropPackets :8
PassBytes : N/A UnicastsPkts :119820612
MulticastsPkts:161900 BroadcastsPkts:252
CRCAlignErrors:6 OversizePkts :2
UndersizePkts :0 CollisionPkts : N/A
Fragments : N/A Jabbers : N/A
64B :334208 65-127B :1
128-255B :0 256-511B :0
512-1023B :251 1024-1518B:119648304
Output :
PassPackets :9952925 DropPackets : N/A
PassBytes :2940008128 UnicastsPkts :976788

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 6
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

MulticastsPkts:0 BroadcastsPkts:8641445
64B :334599 65-127B :141
128-255B :0 256-511B :9618185
512-1023B :0 1024-1518B:0

Modification Specification: Approximately calculate related byte statistics via the median in the
packet length’s interval  the quantity in the corresponding packet length’s interval.
Precaution: The SMXA didn’t comprise this modification. The patch needs to be loaded together
with the line card’s patch 2, the problem could be solved. After de-activated, you need to restart
the system to make the patch invalid.

7. MPNAT FTP processing problem


Fault Description: The FTP server’s passive response on some linux servers transmitted one more
‘.’, the MPNAT module processed incorrectly, causing the corresponding FTP session unable to
continue.
Modification Specification: None
Precaution: None

8. AC power alarm problem of the C320 PRAM card


Fault Description: When the C320 PRAM card was connected with backup battery, it still failed
to report AC power-related alarms.
Modification Specification: None
Precaution: Only SMXA has the problem.

2.3. SCXLV125P2T6_r3.pat, SCXMV125P2T6_r3.pat, SCXNV125P2T6_r3.pat,


SMXAV125P2T6_r3.pat

2.3.1. Brief Introduction of the Patch

None

2.3.2. Fault Specification

1. After you deleted the GTGOG card and then added it back, it would cause flows blocked
Fault Description: The VLAN of the inline port’s aggregation group wouldn’t be deleted when
you deleted the GTGOG card, which would cause flows to be blocked after you added the GTGOG
card back.
Modification Specification: None
Precaution: None

2. After the GTGOG switchport default vlan configuration was rebooted, it would lose efficacy
Fault Description: After GTGOG switchport default vlan configuration was rebooted, it would
lose efficacy.
For example:

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 7
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

switchport default vlan 101 vport 1

Modification Specification: None


Precaution: None
3. The rate limit CIR of VPORTs under the PON port had a problem during overall check
Fault Description: When the total value of rate limit traffic profile cir configured by all VPORTs
under the PON port was larger than 2.5G, the system had no error prompt, and the configured
traffic profile would not take effect, either, while there was error reporting in V1.2.0p1 version:

“Code 48699: MsTrafficPrf – Cir of the traffic profile is larger than the available cir of the pon
port”;
Modification Specification: Restore relevant judgment.
Precaution: None

4. The receiving optical power of the OLT couldn’t be queried on the NMS
Fault Description: The receiving optical power of the OLT couldn’t be queried on the NMS. The
name of the object was zxAnOLTRxOpticalPower, and the OID was .
1.3.6.1.4.1.3902.1015.1010.11.2.1.2
Modification Specification: None
Precaution: None

5. Memory leakage problem of telnet and SSH


Fault Description: After telnet and SSH users were full when logging in, memory leakage would
happen.
Modification Specification: None
Precaution: If memory had already been insufficient seriously, after patched, it also needs active /
standby changeover.

6. Adopting SSH clone mode would cause memory leakage


Fault Description: Do not support SSH’s clone mode, which would cause memory leakage.
Modification Specification: None
Precaution: If memory had already been insufficient seriously, after patched, it also needs active /
standby changeover. It didn’t support the clone mode yet, but just had solved memory leakage
problem.

7. CLI snmp log and sys log didn’t support GET-NEXT and GET-BULK problems
Fault Description: CLI snmp log and sys log didn’t support GET-NEXT and GET-BULK
problems, which would cause many problems unable to be well located in engineering.
Modification Specification: Modify to make it can perform related records.
Precaution: None

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 8
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

2.4. SCXLV125P2T6_r4.pat, SCXMV125P2T6_r4.pat, SCXNV125P2T6_r4.pat,


SMXAV125P2T6_r4.pat

2.4.1. Brief Introduction of the Patch

None

2.4.2. Fault Specification

1. EPON didn’t support SNMP to inquire the last off-line time of the ONU
Fault Description: Previously, EPON didn’t support SNMP to inquire the last off-line time of the
ONU. Modify it as Support.
Modification Specification: None
Precaution: None

2. “show customer-xconnect summary” caused the command busy


Fault Description: After you configured customer-xconnect,

interface gpon-onu_1/7/1:100
name XCONNECT-3000-200
sn-bind disable
tcont 4 name DATAVPN_TCONT profile DataVPN_EVC_010
gemport 4 name DataVPN unicast tcont 4 dir both
gemport 4 traffic-limit upstream DataVPN_EVC_010 downstream DataVPN_EVC_010
service-port 4 vport 4 user-vlan 106 vlan 200 svlan 4000 xconnect
ip access-group datavpn out vport 4
!

vlan 4000
customer-xconnect enable cvlan 200

“show customer-xconnect summary” caused the command busy, because there existed endless
loop inside the code.
Modification Specification: None
Precaution: If the problem appears before being patched, please re-patch after the active /
standby changeover.

3. GTGOG uplink interface statistics didn’t support bytes


Fault Description: Due to the chip restriction of the GTGOG, uplink byte-related statistics
wasn’t supported on the PON port.
show interface gpon-olt_1/8/1
gpon-olt_1/8/1 is activate,line protocol is down.
Description is none.
The port link up/down notification is trap disable.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 9
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Max onu number: 128. Registered onu number: 41.

OLT statistic:
Input rate : N/A Bps 0 pps
Output rate: 0 Bps 0 pps
Input instantaneous bandwidth throughput : N/A
Output instantaneous bandwidth throughput: 0.0%
Input average bandwidth throughput : N/A
Output average bandwidth throughput: 0.0%
Output multicast instantaneous rate: 0 Bps 0 pps
Interface peak rate:
Input peak rate : N/A Bps 91333 pps
Output peak rate: 5361192 Bps 16825 pps
Total statistic:
Input :
PassPackets :119982764 DropPackets :8
PassBytes : N/A UnicastsPkts :119820612
MulticastsPkts:161900 BroadcastsPkts:252
CRCAlignErrors:6 OversizePkts :2
UndersizePkts :0 CollisionPkts : N/A
Fragments : N/A Jabbers : N/A
64B :334208 65-127B :1
128-255B :0 256-511B :0
512-1023B :251 1024-1518B:119648304
Output :
PassPackets :9952925 DropPackets : N/A
PassBytes :2940008128 UnicastsPkts :976788
MulticastsPkts:0 BroadcastsPkts:8641445
64B :334599 65-127B :141
128-255B :0 256-511B :9618185
512-1023B :0 1024-1518B:0

Modification Specification: Approximately calculate related byte statistics via the median in the
packet length’s interval  the quantity in the corresponding packet length’s interval.
Precaution: Only SMXA had this modification.

4. RADIUS suspension problem


Fault Description: C300 had the problem that the aggregation group was down, which affected
the NMS and services. The printing of the files down displayed that the Radius module was
faulty.

The files down were listed as below:


Stack chain:

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 10
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Layer 0 addr:[0x1bd31a4]bfill + 0x4c


Layer 1 addr:[0x3f202879]0x3f202879
Layer 2 addr:[0x1d28c9c]radius_recv_check_authenticator+ 0xc8
Layer 3 addr:[0x1d2cfdc]radius_recv_from_server + 0x54c
Layer 4 addr:[0x1d2d270]radius_recv_from_authserver + 0x94
Layer 5 addr:[0x1da1f44]udp_rcv + 0x38c
Layer 6 addr:[0x1e6e4f0]ip_rcv_demux + 0x7c
Layer 7 addr:[0x1e6e6e0]ipv4_rcv_internal_local + 0x15c

Through locating via dissembling, we found the fault happened in the MEMSET line in
radius_recv_check_authenticator function, of them, MEMSET’s first actual parameter was
UserAttr->eap_info.message_auth, when Radius Server returned an Access-Challenge type
message, and the message didn’t comprise MESSAGE_AUTHENTICATOR’s Attribute member,
above message_auth pointer was null, which caused MEMSET operation to have null pointer,
leading to the equipment down.

Modification Specification: Add protection.


Precaution: If the problem appears before being patched, please perform active / standby
changeover first.

5. Inquiring the quantity of SMXA ports had a problem


Fault Description: Use MIB to inquire the quantity of SMXA ports was 0, while use command
line to inquire that, it was shown as N/A.
Modification Specification: None
Precaution: Only SMXA had this modification.

6. Protocol task was suspended, causing the system abnormal


Fault Description: Protocol task was suspended, causing the NMS detached.

tt 0x8f216a8
1c26984 vxTaskEntry +68 : 1350c60 ()
1350c60 ScheEntry +6cc: 134fb84 (8f216a8)
134fd80 InitSchedule +a2c: 2882f0 ()
2882f0 ProtocolEntry +1854: drv_rx_pkt ()
1d01520 drv_rx_pkt +d4 : drv_rx_ether_pkt ()
1d017e0 drv_rx_ether_pkt+bc : ieee_rcv ()
1db3808 ieee_rcv +1c : 1ec4a74 ()
1ec4a74 ieee_pkt_dispatch+904: switch_et_rcv ()
2352804 switch_et_rcv +158: et_rcv ()
1db1df0 et_rcv +2b4: trunk_rcv ()
1db1fac trunk_rcv +134: ip_rcv ()
1d931e4 ip_rcv +30 : 1d930ac ()
1d930ac ipv4_rcv +7a0: ipv4_rcv_internal ()
1d92728 ipv4_rcv_internal+2d0: RcvPkt_Disp ()

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 11
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

1d00b94 RcvPkt_Disp +d0 : ipv4_rcv_internal_local ()


1d928a4 ipv4_rcv_internal_local+168: ip_rcv_demux ()
1d93284 ip_rcv_demux +7c : 1deb610 ()
1deb610 tcp_rcv +1200: 1dec990 ()
1decbc8 tcp_lfap_kill +788: ssh_receive_upcall (19389ee0, b3e2c70)
1ee4398 ssh_receive_upcall+1c4: ssh_tcp_text_upcall (19a63168, b43c13a, 110)
1ee4aa4 ssh_tcp_text_upcall+d4 : dispatch_v2_server_msg (46f227c, b43c13a, 110)
1e6bb90 dispatch_v2_server_msg+44 : 1e7e3d4 ()
1e7e3d4 session_main_entry+7fc: process_packet (46f227c)
1e7bae4 process_packet +218: 1e75770 ()
1e75770 recv_msg_kexinit+5d4: buf_putstring (19b44588, 4526a08e, 4420000)
1e74d88 buf_putstring +5c : memcpy ()
1c8df34 memcpy +28 : bcopy ()

Modification Specification: Add protection on the SSH module.


Precaution: If it has suspended before patched, please perform active / standby changeover
before you patch.

7. The standby card would be started slowly after the smxa card performed swap in Shenzhen
Fault Description: After the version upgrading was completed, when it performed swap for the
first time after the NE was started for the first time, the standby card would be started slowly,
which affected the production & delivery of the product line. Causes: the mac address of the
network port communicating between cards configured on the starting process as the active card
in the kuboot was inconsistent with that in the vxworks version. Therefore, after the NE was
started for the first time and UP, the active card’s mac address learned in the standby card’s arp
entries was the corresponding mac in the vxwrosk version, at the time, if active / standby cards
were swapping, the original standby card changed into the new active card, the original active
card was rebooted, the mac address configured in the kuboot and the mac address learned in the
arp entries of the new active card were inconsistent, which finally caused the FTP failure within a
period of time. The FTP didn’t succeed until the mac address passed the aging time. The old boot
would be started from the local version directly without any judgment because of the FTP failure,
therefore, the problem was avoided, but in the new boot, the FTP would reboot the new version
after it exceeded trying times, the problem was exposed.
Modification Specification: None
Precaution: Only SMXA had this modification.

2.5. GTGOGV125P2T6_r1.pat

2.5.1. Brief Introduction of the Patch

None

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 12
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

2.5.2. Fault Specification

1. Default value problem of GTGOG DBA PERIOD


Fault Description: By default, the GTGOG’s underlying driver DBA PERIOD adopted 4-frame
scheduling (0.5ms), while the default DBA PERIOD value of other GPON cards and GPON service
layers were still 8 frames. Because the main control card was configured as “Not Deliver”, actually, the
underlying of the GTGOG was 4-frame scheduling all the time.
Modification Specification: Modify the driver’s default value into 8 frames.
Precaution: None

2.6. GTGOAV125P2T6_r2.pat, GTGOCV125P2T6_r2.pat, GTGOEV125P2T6_r2.pat,


GTGOGV125P2T6_r2.pat, GTGHGV125P2T6_r2.pat

2.6.1. Brief Introduction of the Patch

None

2.6.2. Fault Specification

1. Port location problem in Georgia


Fault Description: In the V1.2.3 version, the VLAN ID encapsulated by the “request” message
was internal VLAN ID, after upgraded to the 1.2.5 version, it was external VLAN ID that was
encapsulated. The contents of the DHCP request message had a No., so the DHCP server’s “reply”
failed to find the ONU, and couldn’t allocate with an IP address, seen from the ONU, it failed to
acquire an IP address.
Modification Specification: None
Precaution: None

2. When port location adopted flexible syntax, the SN information would be acquired
incorrectly
Fault Description: When port location adopted flexible syntax, the SN information would be
acquired incorrectly. For example, when the following configuration is used, the SN field in the port
location information will be incomplete.

show port-location flexible-syntax


ItemIndex VariableType Variable Name Width
1 Standard-Var Slot 0
2 Standard-Var Port 0
3 Delimiter / 1
4 Custom-Var Onu-ID 0
5 Delimiter / 1
6 Standard-Var Access_Node_ID 0
7 Delimiter / 1
8 Custom-Var SN 0
9 Delimiter / 1

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 13
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Flexible-Syntax Format:
SlotPort/Onu-ID/Access_Node_ID/SN/

Modification Specification: None


Precaution: The GTGOE, GTGOG and GTGHG provide the patch.

3. BER interval delivered to the ONU had a problem


Fault Description: When the GPON card using ZTE-developed MAC chip was interconnected
with ZTE-F621 ONU, we found that it was a certain probability that the delivered BER INTERVAL
value was 0 when the ONU initialized, F621 would adopt the value as internal timer’s initial value,
causing the ONU to register abnormally and unable to be on-line. Although there was no problem if
interconnected with other ONUs, the hidden risks still existed.
Modification Specification: None
Precaution: The GTGOC, GTGOE, GTGOG and GTGHG provide the patch.

4. MsanProt task suspension problem of the card


Fault Description: MsanProt task suspension problem of the card, causing services abnormal.
Modification Specification: The public module of the platform added abnormality protection and
collect the debugging information.
Precaution: None

2.7. GTGOGV125P2T6_r3.pat, GTGHG V125P2T6_r3.pat

2.7.1. Brief Introduction of the Patch

None

2.7.2. Fault Specification

1. The problem that the flooding multicast traffic affected controllable multicast traffic
Fault Description:
1) Downlink transmitted one flooding multicast VLAN 200: COS 0 100M (multicast-packet: led
downwards via flood-all mode).
2) Downlink transmitted IGMP-controlled MVLAN 100: COS 3 multicast 10M was led
downwards by message adding via IGMP.
3) OLT PON port’s rate limit, 100M, in this case, the IGMP MVLAN 100 multicast couldn’t be
led downwards, while flooding VLAN 200 data could.
Modification Specification: None
Precaution: You need to reboot the line card to be able to make the activation and de-activation of
the patch effective.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 14
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

2. The service was blocked after rebooted


Fault Description: After the system performed active / standby changeover twice, and then
rebooted the system, the downlink unicast service was blocked.
Modification Specification: None
Precaution: None

3. Interworking problem between the line card using GPP chip and F820
Fault Description: When the line card using GPP chip was interconnected with F820’s old sub-
card GPUA, because after the GPUA entered O4, 37 ACK messages (ACKs responding to ASSIGN
ONUID messages, which didn’t meet the protocol) would be reported before reporting the SN. Because
there would be a 1TICK delay each time when the GPP line card processed uplink PLOAM message, it
would be time-out and failed to range if all ACKs were received before processing the SN message. For
the GTGOE line cards, there was no such delay and they could process these 37 ACK messages in time
and then process the SN message, so it wouldn’t fail to range.
Modification Specification: Delete the delay.
Precaution: None

4. UNCFG ONU caused the registered ONUs cut out intermittently at downlink
Fault Description: Enable the encryption on the PON port and ONUs, if there were ONUs
unregistered at the time, it would cause the registered ONUs cut out intermittently at downlink.
Modification Specification: None
Precaution: None

5. GTGOG uplink interface statistics didn’t support bytes


Fault Description: Due to the chip restriction of the GTGOG, uplink byte-related statistics wasn’t
supported on the PON port.

show interface gpon-olt_1/8/1


gpon-olt_1/8/1 is activate,line protocol is down.
Description is none.
The port link up/down notification is trap disable.
Max onu number: 128. Registered onu number: 41.

OLT statistic:
Input rate : N/A Bps 0 pps
Output rate: 0 Bps 0 pps
Input instantaneous bandwidth throughput : N/A
Output instantaneous bandwidth throughput: 0.0%
Input average bandwidth throughput : N/A
Output average bandwidth throughput: 0.0%
Output multicast instantaneous rate: 0 Bps 0 pps
Interface peak rate:
Input peak rate : N/A Bps 91333 pps
Output peak rate: 5361192 Bps 16825 pps

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 15
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Total statistic:
Input :
PassPackets :119982764 DropPackets :8
PassBytes : N/A UnicastsPkts :119820612
MulticastsPkts:161900 BroadcastsPkts:252
CRCAlignErrors:6 OversizePkts :2
UndersizePkts :0 CollisionPkts : N/A
Fragments : N/A Jabbers : N/A
64B :334208 65-127B :1
128-255B :0 256-511B :0
512-1023B :251 1024-1518B:119648304
Output :
PassPackets :9952925 DropPackets : N/A
PassBytes :2940008128 UnicastsPkts :976788
MulticastsPkts:0 BroadcastsPkts:8641445
64B :334599 65-127B :141
128-255B :0 256-511B :9618185
512-1023B :0 1024-1518B:0

Modification Specification: Approximately calculate related byte statistics via the median in the
packet length’s interval  the quantity in the corresponding packet length’s interval.
Precaution: The patch needs to be loaded together with the main control card’s patch 2, the
problem could be solved.

2.8. GTGOAV125P2T6_r1.pat, GTGOCV125P2T6_r1.pat

2.8.1. Brief Introduction of the Patch

None

2.8.2. Fault Specification

1. The number of IP source guard’s entries had the problem


Fault Description: There was too little IP source guard entries supported in the version, but it
could be modified into maximum 2k via the patch (it was possible to have hash conflicts).
Modification Specification: None
Precaution: Before patched, you need to disable the IP source guard function, after the patch was
activated, enable the IP source guard function once again.

2.9. ETGOV125P2T6_r1.pat

2.9.1. Brief Introduction of the Patch

None

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 16
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

2.9.2. Fault Specification

1. Alarm filtering caused suspension of tasks


Fault Description: The implementation problem of ONU remote alarm filtering caused suspension
of the line card’s tasks.
Symptoms:
-> 0x77afe90 (SysCtrlProcess): Check task id=0x5f1b888, name=tkRecv1 suspend!
0x77afe90 (SysCtrlProcess): MP check task id=0x5f1b888, name=tkRecv1 suspend!
0x77afe90 (SysCtrlProcess): Check task id=0x5f1b888, name=tkRecv1 suspend!
0x77afe90 (SysCtrlProcess): MP check task id=0x5f1b888, name=tkRecv1 suspend!
Warning,Wait RecvMsgCb(Tag=16479,ChipId:2,MsgType:312) Timeout!
Warning,Wait RecvMsgCb(Tag=16480,ChipId:3,MsgType:312) Timeout!

Confirm following remote management alarm would trigger relevant problems: fault alarm of the
ONU equipment, fault alarm of the ONU power, no battery alarm of the ONU, battery failure alarm of
the ONU, low voltage alarm of the ONU’s battery, physical errors of the ONU, self-detection failure of
the ONU, high temperature alarm of the ONU, low temperature alarm of the ONU, failure alarm of
IAD configuration and ONU PON IF switching notification.

Modification Specification: None


Precaution: None

2. For ETGOD card, when “show mac” was used, it would cause MACs to be shown cyclically
and endlessly
Fault Description: The ETGOD chip would learn full-0 MAC in individual cases, with reasons
unknown. The problem wouldn’t affect services, but when “show mac” was used, it would cause
MACs to be shown cyclically and endlessly.
Modification Specification: Add relevant process to avoid showing cyclically.
Precaution: None

2.10. ETGOV125P2T6_r8.pat

2.10.1. Brief Introduction of the Patch

None

2.10.2. Fault Specification

1. Compatibility registration demand of Shanghai Telecom SN and LOID


Fault Description: For Shanghai Telecom, Hua Wei 8245C family gateway failed to register. Later,
we found that SN authentication registration was configured at the OLT side, while that
configured on the family gateway was LOID, so the hot patch of SN and LOID compatibility
registration needed to be loaded on the OLT. During registration process, the OLT initiated a
request, Hua Wei’s family gateway responded, and then the OLT would directly deliver

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 17
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

configuration. It had no problem according to the SN authentication mode process, but Hua Wei’s
family gateway was reported via LOID, and the process specification used was LOID
authentication. This process needs the OLT to re-deliver a response of whether the authentication
Succeed or Fail to the terminal, but the OLT was realized based on SN authentication process,
which wouldn’t give a response to the terminal, so the terminal was automatically off-line after it
didn’t wait for the registration response from the OLT for a long time.
It needs to realize via modifying at the OLT side, whether it was SN mode to authenticate or
LOID mode, it should give a response to the terminal according to LOID authentication mode.
Modification Specification: None
Precaution: None

2. CRC problem of the ETGOD’s some PON ports


Fault Description: In the product line and engineering, a great amount of CRC errors happened on
the ONUs under the ETGOD’s some PON ports successively. Through analysis, we thought that
the modification of the PON port’s serdes parameter caused it.
Modification Specification: Restore to V1.2.0P1-related parameters.
Precaution: After patched, you need to reboot the system.

3. ETGOD port isolation problem


Fault Description: By default, the ETGOD didn’t support port isolation between the ONU and
the PON port, the broadcast flood packets of one ONU would be received by other ONUs under
the same PON card.
Modification Specification: Add isolation again.

4. ETGOB IPTV was buffering


Fault Description: When controllable multicast traffic was large, more than 200M, the IPTV under
one PON port under C300-1 in Hangzhou Telecom Jian Qiao was buffering all the time.
Modification Specification: Adjust the switching chip’s buffering strategy.
Precaution: None

2.11. ETXDCV125P2T6_r1.pat, ETTOV125P2T6_r1.pat

2.11.1. Brief Introduction of the Patch

None

2.11.2. Fault Specification

1. Alarm filtering caused suspension of tasks


Fault Description: The implementation problem of ONU remote alarm filtering caused suspension
of the line card’s tasks. Symptoms:

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 18
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

-> 0x77afe90 (SysCtrlProcess): Check task id=0x5f1b888, name=tkRecv1 suspend!


0x77afe90 (SysCtrlProcess): MP check task id=0x5f1b888, name=tkRecv1 suspend!
0x77afe90 (SysCtrlProcess): Check task id=0x5f1b888, name=tkRecv1 suspend!
0x77afe90 (SysCtrlProcess): MP check task id=0x5f1b888, name=tkRecv1 suspend!
Warning,Wait RecvMsgCb(Tag=16479,ChipId:2,MsgType:312) Timeout!
Warning,Wait RecvMsgCb(Tag=16480,ChipId:3,MsgType:312) Timeout!

Confirm following remote management alarm would trigger relevant problems: fault alarm of the
ONU equipment, fault alarm of the ONU power, no battery alarm of the ONU, battery failure alarm of
the ONU, low voltage alarm of the ONU’s battery, physical errors of the ONU, self-detection failure of
the ONU, high temperature alarm of the ONU, low temperature alarm of the ONU, failure alarm of
IAD configuration and ONU PON IF switching notification

Modification Specification: None


Precaution: None

3. Specifications on Each V1.2.5 Cold Patch

3.1. HUTQB.FW, SCXN.FW (V1.2.5P2T7)

V1.2.5P2T6 version was found that the HUVQ card’s indicators were abnormal in the production
line. Change the main control card and line card CPLD to solve related problems.

3.2. GTGOC.FW, GTGOA.FW (V1.2.5P2T7)

When TM3.0 FPGA version was used in Belarus, we found that the packet extracting of the line
card was abnormal, causing the related services which need packet extracting interrupted. To solve the
problem, roll back the FPGA version to V1.2.0P1-related version, and make the cold patch once again

3.3. HUTQ.BT (V1.2.5P2T7)

V1.2.5P2T6’s HUTQ.BT didn’t support the FT test of the product line, so make the cold patch
once again.

3.4. GTGOE.FW (V1.2.5P2T7)

Solve the problems found in other FPGA versions.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 19
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

4. V1.2.5 Patches to be Released

5. Patch Upgrading Guide

5.1. Upgrading Preparation


Confirm the version of the NE and which patches you need to load.
Study related patch specifications carefully, to view whether there are special requirements.

5.2. Upgrading Steps


i. Configure related FTP server, and the configuring process is the same as NE version
upgrading.
ii. Download a patch.
Command Format:
download patch [patchname]
Command Function:
Download the specified patch file into the main control card. The status of the patch
downloaded successfully is deactivated, of them, patchname is the name of the patch file,
with its value range as 1-32 characters. After downloaded successfully, you can view the
patch information via show patch-saved
Active / standby synchronization: The command is executed on the active card first, after
executed successfully, it will continue to be executed on the standby card automatically.
Execution results:
Examples
1. Download the patch of the main control card
ZXAN#download patch scxlv10t7_r0.pat
Downloading from host(10.63.196.193)
Transfering file SCXLV10T7_r0.pat ...
......[Successfully]

2. Download the patch of the line card


ZXAN#download patch ctlav10t7_r0.pat
Downloading from host(10.63.196.193)
Transfering file CTLAV10T7_r0.pat ...
.......[Successfully]

iii. Activate a patch. After the patch is activated, it can work normally.
Command Format:
patch activate [patchname]
Command Function:
Activate the patch downloaded successfully to make it effective; of them, patchname is the
name of the patch file, with its value range as 1-32 characters. After activated successfully,
you can view the information of the running patch via show patch running.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 20
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Activate the patch of the main control card: The main control card activates the specified
patch to make it effective, if there is a standby one, activate the specified patch of the standby
one at the same time;
Activate the patch of the line card: Specify the patch name, and activate all the line cards
supporting the patch inside the shelf.

Active / standby synchronization: The command is executed on the active card first, after
executed successfully, it will continue to be executed on the standby card automatically.
Execution results:
1. Activate the patch of the main control card
ZXAN#patch active scxlv10t7_r0.pat
Active patch in shelf 1 slot 10 success
Active patch finished
2. Activate the patch of the line card
ZXAN#patch active ctlav10t7_r0.pat
Active patch in shelf 1 slot 13 success
Active patch finished s

5.3. Rollback Steps


You can roll back via de-activating and deleting patches.
i. De-activate a patch.
Command Format:
patch deactivate patchname
Command Function:
De-activate the patch which has been effective. Of them, patchname is the name of the
patch file, with its value range as 1-32 characters.
De-activate the patch of the main control card: The main control card de-activates the
specified patch to make it effective, if there is a standby one, de-activate the specified patch
of the standby one at the same time;
De-activate the patch of the line card: Specify the patch name, and de-activate all the line
cards supporting the patch inside the shelf.
After you de-activate a patch, use “show patch-running” command to clear corresponding
information.
Active / standby synchronization: The command is executed on the active card first, after
executed successfully, it will continue to be executed on the standby card automatically.
Execution results:
1. De-activate the patch of the main control card
ZXAN#patch deactive scxlv10t7_r0.pat
Deactive patch in shelf 1 slot 10 success
Deactive patch finished
2. De-activate the patch of the line card
ZXAN#patch deactive ctlav10t7_r0.pat

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 21
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

Deactive patch in shelf 1 slot 13 success


Deactive patch finished

ii. Delete a patch


Command Format:
delete patch [patchname]
Command Function:
Delete the specified patch file, if the status of the patch is Activated, it is not allowed to
delete. Of them, patchname is the name of the patch file, with its value range as 1-32
characters.
Active / standby synchronization: The command is executed on the active card first, after
executed successfully, it will continue to be executed on the standby card automatically.
Execution results:
1. Delete the patch of the main control card
ZXAN#delete patch scxlv10t7_r0.pat
Confirm to delete?[yes/no]:y
Start deleting file
deleting scxlv10t7_r0.pat ..
[Successfully]
2. Delete the patch of the line card
ZXAN#delete patch ctlav10t7_r0.pat
Confirm to delete?[yes/no]:y
Start deleting file
deleting ctlav10t7_r0.pat..
[Successfully]

5.4. Upgrading Confirmation


After upgrade, you can judge whether the patch is upgraded successfully via inquiring the
status of the patch.
Command Format:
show patch-saved
Command Function:
Show the patch files saved on the active equipment, including patches of the main control
card and the line card. If there is a standby one, show the patch information saved on the
standby one at the same time.
Active / standby synchronization: The command is executed on the active card first, after
executed successfully, it will continue to be executed on the standby card automatically.
Execution results:
ZXAN#sho patch-saved
Patch infomation on master board
Loc FileName PatchTag BuildTime PatchLen
-------------------------------------------------------------------------------

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 22
ZXA10 C300 V1.2.5P2 Patch Release Specifications Confidential▲

1/1/10 scxlv10t7_r0.pat 2.0 2010-05-24 09:29:09 645


1/1/10 ctlav10t7_r0.pat 2.0 2010-05-24 09:29:57 645
1/1/10 ctlav10t7_r1.pat 2.0 2010-05-24 09:30:04 645

Command Format:

show patch-running [rackno rackno] [shelfno shelfno] [slotno slotno]

Command Function:
Show the status of patches which have been activated already, including the main control
card and the line card.
rackno rackno Rack No. 1~3 (Differentiate with projects)
shelfno shelfno Shelf No. 1~3 (Differentiate with projects)
slotno slotno Slot No. 2-22 (Differentiate with projects)
Do not specify parameters, show the information of all activated patches,
specify the slot No., and show the activated patches in this slot.
Active / standby synchronization:
Execution results:

ZXAN#sho patch-running
Loc FileName PatchTag OperateTime PatchState
-------------------------------------------------------------------------------
1/1/10 scxlv10t7_r0.pat 2.0 2001-01-01 02:08:51 ACTIVE

5.5. Update Precautions

1. Before patched, please read relevant patch specifications carefully.


2. In V1.2.3 version, if there are multiple patches on the card, and the patches with small
SN are not activated, the patches with large SN can not be activated either after the card
is rebooted.
So in V1.2.3, the patches downloaded to the NE’s card must be activated, otherwise,
some patches may be unable to take effect after the card is rebooted.
For the patches which have already been unable to take effect, you only need to re-
activate them.

All Rights reserved, No Spreading abroad without Permission of ZTE


Totally 23 Pages Page 23