Professional Documents
Culture Documents
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
ZTE CORPORATION
Contents
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.1. 2013-10-22
1.2. 2013-10-28
1.3. 2013-11-15
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.1. SMXAV125P2T6_r1.pat
None
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.
show patch-running
Loc FileName PatchTag OperateTime PatchState
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
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: 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.
None
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:
“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
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
None
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
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.
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.
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.
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 ()
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
None
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.
Flexible-Syntax Format:
SlotPort/Onu-ID/Access_Node_ID/SN/
None
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.
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
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: The patch needs to be loaded together with the main control card’s patch 2, the
problem could be solved.
None
2.9. ETGOV125P2T6_r1.pat
None
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.
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
None
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
None
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
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.
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
V1.2.5P2T6’s HUTQ.BT didn’t support the FT test of the product line, so make the cold patch
once again.
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.
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
Command Format:
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