AN6000 International 2022 Q3 Project Version 202210 Software Release Notes

Long-term Business Confidential Information
AN6000 International 2022Q3

Project Version 202210 Software
Release Notes
EQUIPMENT AN6000-17 / AN6000-15 / AN6000-7

TYPE:
PRODUCT 2.202.093R2A / 2.202.093R2B /

CODE: 2.202.802R1A / 2.202.802R2A /
2.202.802R3A / 2.203.140R1A /
2.203.622R1A
PROJECT D-BS-201808-YF-01-07
NO.:
DEPT: Broadband and Service Application

Business Unit of FiberHome
Telecommunication Technologies Co., Ltd.
DRAFT: Zhang Bo November 21, 2022
CHKD: Chen Zhixin November 21, 2022
APPD: Huwei November 21, 2022

Contents
0 REVISION HISTORY ................................................................................................................................ 3
1 EQUIPMENT INVOLVED ........................................................................................................................ 3
1.1 EQUIPMENT VERSIONS......................................................................................................................... 3
1.2 SOFTWARE VERSION MD5 VALUE (REQUIRED ONLY FOR TERMINAL PRODUCTS OF THE
BROADBAND AND SERVICE APPLICATION BUSINESS UNIT).............................................................. 4
1.3 MATCHING EMS VERSION .................................................................................................................. 6
1.4 APPLICATION SCOPE ............................................................................................................................ 6
1.5 SUPPLEMENTARY INFORMATION (OPTIONAL).................................................................................... 6
2 ADDED / MODIFIED FUNCTIONS ........................................................................................................ 6
2.1 ISSUES RESOLVED ................................................................................................................................ 6
2.2 NEW FUNCTIONS .................................................................................................................................. 7
2.3 MODIFIED FUNCTIONS ....................................................................................................................... 11
2.4 NEW CARDS........................................................................................................................................ 13
2.5 NEW / MODIFIED OPERATIONS ON PROJECT MAINTENANCE .......................................................... 13
3 COMPATIBILITY..................................................................................................................................... 14
3.1 COMPATIBILITY BETWEEN CARDS OF AN OLT ................................................................................ 14
3.2 COMPATIBILITY BETWEEN OLTS AND ONUS.................................................................................. 14
3.3 COMPATIBILITY WITH THE UNM2000 .............................................................................................. 14
4 PENDING ISSUES AND HOW TO AVOID THEM ............................................................................. 14
5 OPERATIONS FOR UPGRADE / ROLLBACK.................................................................................... 14
5.1 PREPARATIONS BEFORE UPGRADE ................................................................................................... 14
5.2 HOW TO UPGRADE REMOTELY.......................................................................................................... 14
5.3 HOW TO UPGRADE LOCALLY ............................................................................................................ 15
5.4 SERVICE VERIFICATION ..................................................................................................................... 15
5.5 ROLLBACK .......................................................................................................................................... 15
5.6 HISTORICAL VERSION UPGRADE (OPTIONAL).................................................................................. 16
6 RELEASE CHANGES .............................................................................................................................. 16
7 CAUTIONS ................................................................................................................................................ 16
(Rev.M-20220607) 2(17)
Template version marker

0 Revision History
No. REV Date Description of Changes Author Remark
1 RA 7/29/2022 Initial version Zhang Bo
2 RB 11/21/2022 Release after pilot scale experiment Zhang Bo
1 Equipment Involved
1.1 Equipment Versions

Equipment Models: AN6000-17 / AN6000-15 / AN6000-7
Communic
Product Card
ations Compilation Software Object Code /
No. Name Product Code Software
Service Time Project Package Filename
(Abbr.) Version
Provider
hb_hsca_RP1400_
GENERAL.bin/
hb_hsca_RP1404_
GENERAL.bin/
hb_hsca_RP1405_
RP1400/
GENERAL.bin/
RP1404/
hb_hsca_RP1500_
RP1405/
GENERAL.bin/
RP1500/
hb_hsca_RP1501_
RP1501/
GENERAL.bin/
2.202.093R2A/2.20 RP1510/ Nov 16 2022
1 HSCA General hb_hsca_RP1510_
2.093R2B RP2000/ 13:21:30
GENERAL.bin/
RP2000RM/
hb_hsca_RP2000_
RP2001/
GENERAL.bin/
RP2001RM
hb_hsca_RP2000RM_
GENERAL.bin/
hb_hsca_RP2001_
GENERAL.bin/
hb_hsca_RP2001RM_
GENERAL.bin
hb_hsca_RP1405_CHILE
.bin/
RP1405/
2.202.093R2A/2.20 Nov 16 2022 hb_hsca_RP1500_CHILE
2 HSCA Chile RP1500/
2.093R2B 13:21:30 .bin/
RP1501/
hb_hsca_RP1501_CHILE
.bin
RP1405/ hb_hsca_RP1405_PS.bin/
2.202.093R2A/2.20 Nov 16 2022
3 HSCA Palestine RP1500/ hb_hsca_RP1500_PS.bin/
2.093R2B 13:21:30
RP1501/ hb_hsca_RP1501_PS.bin
RP1400/ GPOA_RP1400.gz/
2.202.802R1A /
RP1404/ Nov 15 2022 GPOA_RP1404.gz /
4 GPOA 2.202.802R2A / General
RP1405/ 09:09:55 GPOA_RP1405.gz /
2.202.802R3A
(Rev.M-20220607) 3(17)

Communic
Product Card
ations Compilation Software Object Code /
No. Name Product Code Software
Service Time Project Package Filename
(Abbr.) Version
Provider
RP2000RM/ GPOA_RP2000RM.gz/
RP2001RM GPOA_RP2001RM.gz
RP1400/
GNOA_RP1400.gz/
RP1404/
GNOA_RP1404.gz/
RP1405/
GNOA_RP1405.gz/
RP1500/
GNOA_RP1500.gz/
RP1501/
Nov 15 2022 GNOA_RP1501.gz/
5 GNOA 2.203.140R1A General RP1510/
09:48:24 GNOA_RP1510.gz/
RP2000/
GNOA_RP2000.gz/
RP2000RM/
GNOA_RP2000RM.gz/
RP2001/
GNOA_RP2001.gz/
RP2001RM
GNOA_RP2001RM.gz
RP1400/
GFOA_RP1400.gz/
RP1404/
GFOA_RP1404.gz/
RP1405/
GFOA_RP1405.gz/
RP1500/
GFOA_RP1500.gz/
RP1501/
Nov 15 2022 GFOA_RP1501.gz/
6 GFOA 2.203.622R1A General RP1510/
10:16:54 GFOA_RP1510.gz/
RP2000/
GFOA_RP2000.gz/
RP2000RM/
GFOA_RP2000RM.gz/
RP2001/
GFOA_RP2001.gz/
RP2001RM
GFOA_RP2001RM.gz
1.2 Software Version md5 Value (Required Only for Terminal Products of the Broadband and
Service Application Business Unit)
Product Name Software Object Code

Product Code MD5
(Abbr.) Filename
2.202.093R2A/2.2 hb_hsca_RP1400_ 39C1376EDE1591EF8EF4355819E1
HSCA
02.093R2B GENERAL.bin 5C9B
2.202.093R2A/2.2 hb_hsca_RP1404_ 0861C0E10FA64F8B115E3A963FD
HSCA
02.093R2B GENERAL.bin 75DCE
2.202.093R2A/2.2 hb_hsca_RP1405_ 33EF43DBA0319EC4BD799D0E78
HSCA
02.093R2B GENERAL.bin 390BB6
2.202.093R2A/2.2 hb_hsca_RP1500_ 0AED27954552C5A455BBA1AA3C
HSCA
02.093R2B GENERAL.bin B16002
2.202.093R2A/2.2 hb_hsca_RP1501_ 3BC18107B5224E1C207E196FD6D
HSCA
02.093R2B GENERAL.bin C4044
2.202.093R2A/2.2 hb_hsca_RP1510_ 1CA5324E78D8CF075F6317571BB
HSCA
02.093R2B GENERAL.bin EA3F2
2.202.093R2A/2.2 hb_hsca_RP2000_ FD51F592EA45475B40461C3C6ED
HSCA
02.093R2B GENERAL.bin 0CD48
2.202.093R2A/2.2 hb_hsca_RP2000RM_ A8EA29B106A9A0F42CD12D9A19
HSCA
02.093R2B GENERAL.bin 823D76
(Rev.M-20220607) 4(17)

Product Code MD5
(Abbr.) Filename
2.202.093R2A/2.2 hb_hsca_RP2001_ 0FB54FF34DD7CB776B7B96540F1
HSCA
02.093R2B GENERAL.bin F9550
2.202.093R2A/2.2 hb_hsca_RP2001RM_ A9B44717564B5F1C30A9C68BDA
HSCA
02.093R2B GENERAL.bin 46918E
2.202.093R2A/2.2 hb_hsca_RP1405_CHIL 2B0801AA82325A950770D2DC83C
HSCA
02.093R2B E.bin BE835
2.202.093R2A/2.2 hb_hsca_RP1500_CHIL 7DD01D46E60B9ED14F84E7C98F7
HSCA
02.093R2B E.bin 481FB
2.202.093R2A/2.2 hb_hsca_RP1501_CHIL 2241174E3EF165D6F9DE277752C0
HSCA
02.093R2B E.bin 0F20
2.202.093R2A/2.2 7FACA6DAF875981A0FFBD34DD
HSCA hb_hsca_RP1405_PS.bin
02.093R2B 82C087E
2.202.093R2A/2.2 B0760CECCE9E614CEED378A802
02.093R2B FF3031
2.202.093R2A/2.2 325F0832887F9DD7CD5198471008
02.093R2B DA62
2.202.802R1A /
71C7B8E804FDCC7B891D5BAB96
GPOA 2.202.802R2A / GPOA_RP1400.gz
01F110
2.202.802R3A
2.202.802R1A /
2300F63FD3DF92F6BA477E63107
C99A1
2.202.802R3A
2.202.802R1A /
9A41C06F0CB6F4A0C0FDFD003F
DF66BF
2.202.802R3A
2.202.802R1A /
34F15673095371A67FFC96E6B357
A8FC
2.202.802R3A
2.202.802R1A /
171AFC465B6F3819F4D540BACB7
F2488
2.202.802R3A
2.202.802R1A /
E62DF921ABE0D6E5B045143B74F
C3BE4
2.202.802R3A
2.202.802R1A /
6AEED6535B6BF850E9D87E96B1
FCBDCF
2.202.802R3A
2.202.802R1A /
3D5C962BB3194FB17DA741D38E
GPOA 2.202.802R2A / GPOA_RP2000RM.gz
89FBCD
2.202.802R3A
2.202.802R1A /
2E7380E0DF8B6A6BFD92E4B3CB
9042ED
2.202.802R3A
2.202.802R1A /
14131FB099F25CA4BBAB25384E8
GPOA 2.202.802R2A / GPOA_RP2001RM.gz
410BA
2.202.802R3A
4458BDB71502FE8273639C819279
GNOA 2.203.140R1A GNOA_RP1400.gz
395E
39B490E08001EB9661578FEDF71B
041C
2A26FB6B3229E6D8CA6FDD9138
A565C9
F5F4FEEA65E4CAF85FD4AFABE
D6B44E9
(Rev.M-20220607) 5(17)

Product Code MD5
(Abbr.) Filename
EC141CC17B3548B70E4616539AC
19883
6660198F9FFC151A325D52248623
DB69
9882B98A22577971D26BC4888C30
D873
17F0FC70D7773D417881CEBDF3F
GNOA 2.203.140R1A GNOA_RP2000RM.gz
6BCED
CF7F5B5432104D7B7AFC941CB72
885EE
0CE8C4F1A4D6A814B6FF3905CF3
GNOA 2.203.140R1A GNOA_RP2001RM.gz
A273D
CE785EC009FC2B86A127FF50909
GFOA 2.203.622R1A GFOA_RP1400.gz
CA81D
143B55CEAC750C6AE1C93913CB
45A7EB
535F8A1D10685CB70CDA9E452B
11E4E2
B4714389F6C89600A9EF699C81D
E01DA
FB601BA909734907361D564A6BE
86C0A
8BA1370ADE023AA27177F655F29
37328
EEC2749B637617F3236AAB2FB33
5FA31
DF41C41552C7AD6ABAA56C1C3
GFOA 2.203.622R1A GFOA_RP2000RM.gz
CDA5CDC
7C5C8307E13C217D87C99F19D86
EEF09
A61D47F59B66D90B0191CA6E0A
GFOA 2.203.622R1A GFOA_RP2001RM.gz
DE4A9B
1.3 Matching EMS Version

Matching EMS version for this release: UNM2000V2R7
1.4 Application Scope

International general version for the AN6000 series
1.5 Supplementary Information (Optional)

None
2 Added / Modified Functions
2.1 Issues Resolved
(Rev.M-20220607) 6(17)

In this release, the following issues have been resolved.
2.1.1 Upstream Port MAC Address Not Being Aged
The aforesaid issue occurred occasionally in the previous release, and is resolved in this release.
2.1.2 Inconsistency Between Soft and Hard MAC Address Tables for the Standby Core Switch
Card (VQ, Singapore)
In the previous version, the MAC address table recorded by software is inconsistent with that
recorded by the switch chip. The issue is resolved in this release.
2.1.3 Failure in Querying ONU GEM Ports

The aforesaid issue is resolved in this release.
2.1.4 Failure to Refresh ONU DBA Settings After a Switch Between DBA-SR and DBA-NSR
In this release, the ONU DBA settings will be refreshed automatically after a switch between
DBA-SR and DBA-NSR.
2.1.5 Failure of Multicast Service on a FiberHome SFU Configured with VEIP (Totalplay,
Mexico)
This SFU has special application scenarios in Totalplay Mexico. The issue is resolved in this
release through modification of the VEIP configuration process for line cards.
Cautions:
The SFU needs to be updated as well. Please contact with the person in charge to obtain the right
SFU version.
2.1.6 System Time Oscillation Subsequent to NTP Time Calibration

2.1.7 Failure in Stopping Automatic ONU Upgrade

2.1.8 Large Bias in Rx Optical Power at OLT PON Ports Where the Optical Module Is Replaced
2.2 New Functions
The following functions are introduced to this release.

2.2.1 Protection Against Attacks in Telnet to ONUs
Unsuccessful telnet to an ONU for three successive times will trigger the
TELNET_ONU_AUTH_FAIL event, and further attempts are denied in the subsequent five
minutes.
(Rev.M-20220607) 7(17)

Cautions:
Not all the ONUs or their versions support this function. Contact with the personnel in charge of
ONUs to confirm the ONU models and their versions supporting this function.
2.2.2 Collaborating with the HG6245D to Implement Ping Operations

An OLT delivers a ping command to the HG6245D, and the latter pings the IP address specified
by the OLT, as shown in the figure below:
2.2.3 Automatically Sending a Trap to the UNM2000 When an ONU Is Deployed

When an ONU is deployed, a trap will be generated and sent to the UNM2000 automatically.
(Rev.M-20220607) 8(17)

2.2.4 Generating the ONU Reset Alarm Instead of the LOS Alarm When HG62 and HG65 Series
ONUs Are Rebooted
The aforesaid function is introduced to this release.
Cautions:
To avoid generation of the LOS alarm together with the ONU reset alarm, run the following
command on core switch cards:
pon-los-filter manual-operation enable time 60
2.2.5 Configuring the PPPoE+ Function to Report the GEMPORT ID Field Information
The PPPoE+ function can be configured to report the GEMPORT ID filed information, where %g
represents gemport. Currently, this cannot be configured through the UNM2000, but through
command lines on core switch cards.
2.2.6 Querying Real-time Downstream Available Bandwidth at a PON Port Through OIDs for the
AN6000-17
The following two nodes are added to the local end interface traffic table:
1.3.6.1.4.1.58 Real-time remained

fhOltPortTraffInRe
75.800.3.54.7 Counter64 Read-only bandwidth for Unit: 0.01 Mbps
mainBwReal
.1.87 incoming traffic
1.3.6.1.4.1.58 Real-time remained
fhOltPortTraffOut
75.800.3.54.7 Counter64 Read-only bandwidth for Unit: 0.01 Mbps
RemainBwReal
.1.88 outgoing bandwidth
The query result is displayed as follows:
2.2.7 Collecting Physical Password of Unauthorized ONUs Through a MIB Node

In the previous release, a MIB node (1.3.6.1.4.1.5875.800.3.11.1) was designed to read
information of unauthorized ONUs. In this release, another MIB node is introduced, as shown in
the table below:
1.3.6.1.4.1.5875.800.3.11.1.1.14 Display String Read-only Physic Password 0-10 bytes
The information is collected as follows:
2.2.8 Applying DHCP Relay to Cascade Scenarios

In this release, DHCP Relay can be applied to cascade scenarios.
2.2.9 Selecting VRF for Syslog, Automatic ONU Upgrade, Tacas, Radius, and PON Traffic
Through the UNM2000
The aforesaid function is introduced to this release. The UNM2000 needs to be upgraded
accordingly.
(Rev.M-20220607) 9(17)

2.2.10 Prompt Messages for ONU Description Exceeding 50 Characters on the UNM2000 and CLI
In this release, prompt messages are provided for ONU description exceeding 50 characters on the
UNM2000 and CLI respectively.
2.2.11 Batch Switching of Authentication Mode for PON Ports Through CLI
In this release, authentication mode can be switched for PON ports in a batch manner through CLI,
as shown in the figure below:
2.2.12 Protection Against PLOAM Attacks

Protection against PLOAM attacks is enabled for line cards by default. This function is
implemented as follows:
1. A line card periodically (once a second) counts PLOAM packets received by each ONU.
2. If the count of received PLOAM packets crosses the threshold (100 unicast packets or 1000
broadcast packets per second) in five consecutive test cycles, the PLOAM packets from the
corresponding ONU will be suppressed (to no more than 32 unicast packets or no more than
128 broadcast packets per second).
3. If the count of received PLOAM packets is lower than the threshold for suppression (32 unicast
packets or 128 broadcast packets per second) in 60 consecutive test cycles, the threshold for
received PLOAM packets will be reset to 100 unicast packets or 1000 broadcast packets per
second.
Cautions:
1. The unicast PLOAM packet threshold is based on ONUs, while the broadcast PLOAM packet
threshold is based on line cards.
2. Broadcast PLOAM packets are SN PLOAM packets received from ONUs not assigned with
IDs. The ONUs sending the packets cannot be identified. Therefore, in case of attacks by
broadcast PLOAM packets, even when the threshold for broadcast PLOAM packets is set to
128 packets per second, registration of ONUs under the line card may fail as well.
2.2.13 Reading ONU CATV Port Status

2.2.14 Protection Against DoS Attacks on Line Cards

(Rev.M-20220607) 10(17)

2.2.15 Reporting the Power Recovery Event for an OLT Getting Restarted After a Power Failure
2.2.16 Reporting an OLT’s Management IP Address Through Syslog

2.2.17 Verifying Multicast IP Addresses During Multicast Upgrade Configuration

2.2.18 Deleting ONU Description Information

The aforesaid function is introduced to this release, as shown in the example below:
2.3 Modified Functions
The following functions are modified in this release.

2.3.1 Default Settings of “ONU Local Manage Interface Configure” Parameters Being “Disable”
for Newly Authorized ONUs
In the previous version, default settings of “ONU Local Manage Interface Configure” parameters
are “Enable”, while in this release, they are “Disable”.
2.3.2 ONU Voice Status Being Included in the Additional Information for the MGC Link
Disconnection Alarm
In this release, ONU voice status is added to the additional information for the MGC link
disconnection alarm.
Cautions:
This function requires support of ONUs. Contact with the personnel in charge of ONUs to confirm
the ONU models and their versions supporting this function.
(Rev.M-20220607) 11(17)

2.3.3 Global Configuration Page Being Added for ONU Remote Management
In this release, a global configuration page is added to the ONU remote management configuration
module.
2.3.4 Reading Standby Software Versions of ONUs

In this release, the “show onu version” command is extended to read standby software versions of
ONUs.
2.3.5 VLAN-specific Traffic Statistics for OLTs / Line Cards / PON Ports / ONUs
The previous version allows VLAN-specific traffic statistics as follows:
1. VLAN-specific traffic statistics via a core switch card: A global VLAN white list needs to be
configured; configuration and reading statistics via the UNM2000 is allowed.
2. Traffic statistics based on VLANs and upstream ports via a core switch card: A port VLAN
white list needs to be configured (only one port is supported).
This release involves the following modifications:

1. VLAN-specific traffic statistics via a core switch card: A small change is made to the
UNM2000, with the upstream and downstream rate fields added to the reading page (these two
fields have already been introduced to the CLI in the previous version).
2. Traffic statistics based on VLANs and upstream ports via a core switch card: a global VLAN
white list, instead of a port VLAN white list, is adopted. Ports are added or deleted
automatically.
3. When traffic statistics on a port are read via the UNM2000 / CLI for the first time, the OLT
automatically creates a collection object, and the backend executes a roll polling to collect data
on the port.
4. If the UNM2000 / CLI stops reading statistics on a port for a certain period of time, the
collection object will get aged and be deleted.
5. When the real-time collection page of the UNM2000 is closed down, a command for stopping
collection will be automatically issued, without waiting for aging of the object.
6. The global VLAN white list configuration is delivered to line cards. VLAN traffic statistics on
PON ports of the line cards and connected ONUs are then based on this white list.
7. Traffic statistics based on VLANs and PON ports are introduced to this release.
8. Line cards perform roll polling on PON ports to obtain VLAN performance data.
9. Core switch cards deliver a command to line cards through the UNM2000 or CLI, requiring line
cards to reading statistics.
10. Traffic statistics based on VLANs and ONUs are introduced to this release.
11. Traffic statistics within line cards are disallowed. The ONU collection objects must be created
or deleted through commands issued by core switch cards. Therefore, the ONU collection
object creation and aging mechanism on upstream ports is applied to line cards.
The following commands are introduced to this release:

1. show port vlan-traffic statistics <frameid/slotid/portid>: read upstream / PON port VLAN
performance statistics (for an upstream port, the collection object will age automatically if
statistics reading stops for a certain period of time).
2. show onu vlan-traffic statistics <frameid/slotid/portid> <onuid>: read ONU VLAN
performance statistics (the collection object will age automatically if statistics reading stops for
a certain period of time).
(Rev.M-20220607) 12(17)

3. no port vlan-traffic statistics <frameid/slotid/portid>: stop collecting VLAN performance data
on an upstream port (acting similarly as automatic aging).
4. no onu vlan-traffic statistics <frameid/slotid/portid> <onuid>: stop collecting ONU VLAN
performance data (This command functions similarly as automatic aging).
5. port vlan-traffic statistics [auto-aging-value] [<10-3600>]: configure time-to-wait for automatic
aging.
6. show port vlan-traffic statistics config: show port VLAN performance statistics settings
(currently only the setting of automatic aging can be displayed).
Cautions:
1. When multicast VLAN is added to the VLAN performance statistics white list, query of
multicast traffic based on multicast addresses will be disabled. To enable such query, delete the
multicast VLAN from the VLAN performance statistics white list.
2. Port traffic statistics is disallowed for a translated multicast VLAN.
2.3.6 Adding SSH, SNMP and Telnet Protocol Control to Access Control Based on ACL
In the previous release, access control cannot be implemented as per protocols but IP addresses. In
this release, access control through SSH, SNMP and Telnet is added.
The following commands are added:

Command for configuration:
{[telnet|ssh|snmp]}*1 acl <id> {[ip] <ipaddr>}*1 {[mask] <value>}*1 {[enable|disable]}*1
Command for showing configuration:
show {[telnet|ssh|snmp]}*1 acl {[entryId] <id>}*1
Command for deleting configuration:

no {[telnet|ssh|snmp]}*1 acl [<id>|all]
Cautions:
If access control as in the previous release has been configured, disable it before enab ling access
control based on protocols
.
2.3.7 No Verification of Device Management IP Address for an XGS-PON License
In the previous version, an XGS-PON license needs to be bound with the management IP address
of the OLT. In this release, an XGS-PON license needs only to be bound with the core switch
card’s MAC address.
2.4 New Cards

None
2.5 New / Modified Operations on Project Maintenance

2.5.1 New Operations
None
2.5.2 Modified Operations

(Rev.M-20220607) 13(17)

None
2.5.3 Default Configuration & Parameter Modification

None
3 Compatibility
3.1 Compatibility Between Cards of an OLT

Both core switch cards and line cards of the AN6000-17 / AN6000-5 / AN6000-7 need to be
upgraded to the latest versions.
3.2 Compatibility Between OLTs and ONUs

The OLTs in this release are compatible with previously released ONUs.
3.3 Compatibility with the UNM2000

Matching EMS version for this release: UNM2000V2R7
4 Pending Issues and How to Avoid Them

Defect Analysis and Counter
Mantis No. Severity Frequency Defect Description
Measures
In a simulation test, when the
Users may feel confused about the value read
GPOA card reads the PON port
from the PON port MAC address table.
74112 Minor Always MAC address table, it is found that
However, services are not affected. This issue
the MAC addresses correspond to
is to be resolved in the 2022Q4 version.
the ONU ID 255.
Type C protection and mac-move cannot be

Services with Type C protection
76014 Minor Always enabled simultaneously. This issue is to be
fail after mac-move is enabled.
resolved in the 2022Q4 version.
5 Operations for Upgrade / Rollback
5.1 Preparations Before Upgrade

1) Check current configuration data of the AN6000 series equipment to be upgraded, making sure it
is correct and consistent with the saved configuration data. Save the current configuration data to
the equipment’s Flash, and export the backup configuration file.
2) Identify the hardware versions of the cards to be upgraded through the UNM2000, and back up
the card software.
3) Check the online / offline status of all the ONUs connected to the AN6000 series equipment to be
upgraded, and record the versions of the OLT and the UNM2000.
4) Check that different parts of the AN6000 series equipment to be upgraded can commun icate with
each other smoothly.
5.2 How to Upgrade Remotely

Remotely upgrade existing cards to the new version in this release through the UNM2000 or CLI:
load program backup [system|patch|cpld|boot] <filename> [tftp|ftp|sftp] <filename> [ftp|sftp|tftp]
(Rev.M-20220607) 14(17)

<server_ipaddr> {<username> <password>}*1 (upgrade the standby core switch card)
load program [system|config|script|ver-file|boot|patch|cpld] <filename> [tftp|ftp|sftp] <ipaddr>

{<username> <password>}*1 (upgrade the active core switch card)
load program card [<frameid/slotid>|all] <filename> [tftp|ftp|sftp] <ipaddr> {<username>

<password>}*1 (upgrade the line card)
Run the command “show version {<frameid/slotid>}*1” in the config directory to check whether
the core switch cards and line cards have been upgraded to desired versions. If not, redo the
upgrade.
Notes:
1) Core switch cards and line cards will not be reset automatically after their software is upgraded
successfully. Therefore, they need to be reset manually.
2) Core switch cards and line cards will not be reset automatically after their CPLDs are upgraded
successfully. Therefore, they need to be reset manually. Make sure power is not cut off and the
cards are not unplugged during the reset; otherwise, the cards will not be started. (This release
does not cover CPLD; therefore, CPLD needs not be upgraded.)
3) Each time after a file is upgraded, run the command “show load program state” to check its
upgrade status. Proceed to the next file only when the upgrade state of the current file is
“success”.
Upgrade Procedures
1) Upgrade software of the standby core switch card, and then that of the active core switch card (no
active-standby switching is required).
2) Upgrade software of line cards.
3) Restart the OLT.
4) Check that software of core switch cards and line cards has been updated.
5.3 How to Upgrade Locally

This release does not involve local upgrade files, so local upgrade will not be discussed here.
5.4 Service Verification

1) After the upgrade, check whether the equipment performs well. That is, check whether its cards
are functioning properly, whether communication between different parts is smooth; whether the
ONUs connected to the OLT are in normal state, and whether alarm indicators are in expected
status.
2) Obtain configuration data of ONUs from the UNM2000, and check whether it is consistent with
the configuration data before the upgrade.
3) Check whether users can access Internet service (check web pages and file download through
FTP), voice service (make a five-minute phone call), and IPTV service (check switching between
program channels and watching programs in a channel for 10 minutes) as expected.
5.5 Rollback
This release can be rolled back to previous versions. The rollback procedures are similar to those for
upgrade, as described in Section 5.2.
(Rev.M-20220607) 15(17)

Run the following commands to upgrade cards:
load program backup [system|patch|cpld|boot] <filename> [tftp|ftp|sftp] <filename> [ftp|sftp|tftp]
<server_ipaddr> {<username> <password>}*1 (upgrade the standby core switch card)
load program [system|config|script|ver-file|boot|patch|cpld] <filename> [tftp|ftp|sftp] <ipaddr>

{<username> <password>}*1 (upgrade the active core switch card)
load program card [<frameid/slotid>|all] <filename> [tftp|ftp|sftp] <ipaddr> {<username>

<password>}*1 (upgrade line cards)
load program config <filename> [tftp|ftp|sftp] <server_ipaddr> {<username> <password>}*1

(import configuration data)
Run the command “show version {<frameid/slotid>}*1” in the config directory to check whether
the core switch cards and line cards have been upgraded to desired versions. If not, redo the
upgrade.
Cautions:
To roll back from this new version to a previous version, you need to import the configuration file
backed up before upgrade.
Upgrade Procedures
1) Upgrade software of the standby core switch card, and then that of the active core switch card (no
active-standby switching is required).
2) Upgrade software of line cards.
3) Import the configuration file backed up before upgrade.
4) Restart the OLT.
5) Check that software of core switch cards and line cards has been updated.
5.6 Historical Version Upgrade (Optional)
No. Device Project Version Upgrade Description Remarks
Note:
6 Release Changes
Initial Release Date Version Compilation Time Process for Initial Release
November 2022 RP1400 Nov 16 2022 13:21:30 Engineering version release process
7 Cautions
No. Risk Description Risk Influence Measures
When a command is issued When multicast upgrade is disabled
to disable multicast upgrade for core switch cards but enabled for
during the process of line cards, ONUs set to upgrade in Disable multicast upgrade
1 multicast upgrade for common mode are actually upgraded after ONU upgrade
ONUs, it is found that in multicast upgrade mode. finishes.
multicast upgrade remains Accordingly, ONUs not supporting
enabled for line cards. multicast upgrade will fail in
(Rev.M-20220607) 16(17)

No. Risk Description Risk Influence Measures
upgrade.
There is no command for This causes risks in O&M. If a user The password can be found
2 restoring default password forgets the password, he / she will be in the OLT configuration
for telnet to an ONU. unable to telnet to the ONU. file.
The configuration file
containing modified ONU There is a risk of telnet password Keep the configuration file
3
telnet password is saved in leakage. safe to prevent leakage.
open text.
(Rev.M-20220607) 17(17)

AN6000 International 2022 Q3 Project Version 202210 Software Release Notes

Uploaded by

Document Information

Original Description:

Original Title

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

AN6000 International 2022 Q3 Project Version 202210 Software Release Notes

Uploaded by

Copyright:

Available Formats

Long-term Business Confidential Information

AN6000 International 2022Q3

EQUIPMENT AN6000-17 / AN6000-15 / AN6000-7

PRODUCT 2.202.093R2A / 2.202.093R2B /

DEPT: Broadband and Service Application

DRAFT: Zhang Bo November 21, 2022

CHKD: Chen Zhixin November 21, 2022

APPD: Huwei November 21, 2022

Template version marker

1 RA 7/29/2022 Initial version Zhang Bo

2 RB 11/21/2022 Release after pilot scale experiment Zhang Bo

1.1 Equipment Versions

Template version marker

Product Name Software Object Code

Template version marker

Template version marker

1.3 Matching EMS Version

1.4 Application Scope

1.5 Supplementary Information (Optional)

2 Added / Modified Functions

2.1 Issues Resolved

Template version marker

2.1.3 Failure in Querying ONU GEM Ports

2.1.6 System Time Oscillation Subsequent to NTP Time Calibration

2.1.7 Failure in Stopping Automatic ONU Upgrade

2.2 New Functions

The following functions are introduced to this release.

Template version marker

2.2.2 Collaborating with the HG6245D to Implement Ping Operations

2.2.3 Automatically Sending a Trap to the UNM2000 When an ONU Is Deployed

Template version marker

1.3.6.1.4.1.58 Real-time remained

The query result is displayed as follows:

2.2.7 Collecting Physical Password of Unauthorized ONUs Through a MIB Node

1.3.6.1.4.1.5875.800.3.11.1.1.14 Display String Read-only Physic Password 0-10 bytes

The information is collected as follows:

2.2.8 Applying DHCP Relay to Cascade Scenarios

Template version marker

2.2.12 Protection Against PLOAM Attacks

2.2.13 Reading ONU CATV Port Status

2.2.14 Protection Against DoS Attacks on Line Cards

Template version marker

2.2.16 Reporting an OLT’s Management IP Address Through Syslog

2.2.17 Verifying Multicast IP Addresses During Multicast Upgrade Configuration

2.2.18 Deleting ONU Description Information

2.3 Modified Functions

The following functions are modified in this release.

Template version marker

2.3.4 Reading Standby Software Versions of ONUs

This release involves the following modifications:

The following commands are introduced to this release:

Template version marker

The following commands are added:

Command for deleting configuration:

2.4 New Cards

2.5 New / Modified Operations on Project Maintenance

2.5.2 Modified Operations

Template version marker

2.5.3 Default Configuration & Parameter Modification

3.1 Compatibility Between Cards of an OLT

3.2 Compatibility Between OLTs and ONUs

3.3 Compatibility with the UNM2000