OG For ONU NE Management - (V100R002C01 - 03)

iManager U2000 Unified Network Management
System
V100R002C01
Operation Guide for ONU NE
Management
Issue 03
Date 2010-11-19
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2010-11-19) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V100R002C01

Intended Audience
This document describes the functions and services provided by the ONU. After you read this
document, you should be able to know how to operate the ONU and configure services through
the U2000.
This document is intended for:
l Data Configuration Engineer
l Network Monitoring Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
DANGER
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
WARNING
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
CAUTION
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
iManager U2000 Unified Network Management System
Operation Guide for ONU NE Management About This Document
iii
Symbol Description
TIP
Indicates a tip that may help you solve a problem or save
time.
NOTE
Provides additional information to emphasize or supplement
important points of the main text.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

About This Document
Operation Guide for ONU NE Management
iv Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 03 (2010-11-19) Based on Product Version V100R002C01
The third commercial release has the following updates:
The following changes: 1.1.5 Configuring the xFTP File in the NAT Networking Mode.
The second commercial release has the following updates:
The parameter names and graphs are changed according to latest GUIs.
Initial release for V100R002C01 version.
Operation Guide for ONU NE Management About This Document
v
Contents
About This Document...................................................................................................................iii
1 Managing Network Elements..................................................................................................1-1
1.1 Configuring the xFTP Service.........................................................................................................................1-3
1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)....................................................................1-3
1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)........................................................................1-6
1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)..........................................................................1-9
1.1.4 Configuring the xFTP Watcher............................................................................................................1-11
1.1.5 Configuring the xFTP File in the NAT Networking Mode..................................................................1-13
1.2 Adding an ONU............................................................................................................................................1-14
1.3 Replacing an ONU........................................................................................................................................1-19
1.4 Moving an ONU............................................................................................................................................1-20
1.5 Managing the SRG Web Service..................................................................................................................1-20
1.6 Configuration Example of the Outband Management (Based on the SNMPv3 Protocol)............................1-21
1.7 Configuration Example of the Inband Management.....................................................................................1-27
2 Configuring the VLAN Stacking Wholesale Service..........................................................2-1
2.1 Introduction to the VLAN Stacking Wholesale Service.................................................................................2-2
2.2 Configuring the VLAN Stacking Wholesale Service......................................................................................2-2
2.3 Application Example: Configuring the VLAN Stacking Wholesale Service.................................................2-3
3 Configuring the QinQ VLAN Private Line Service............................................................3-1
3.1 Introduction to the QinQ VLAN Private Line Service....................................................................................3-2
3.2 Configuring the QinQ VLAN Leased Line Service........................................................................................3-2
3.3 Application Example: Configuration the QinQ VLAN Leased Line Service.................................................3-3
4 Configuring the Dual GE Link Aggregation Upstream Transmission...........................4-1
5 Configuring the VoIP ISDN BRA Service (H.248 Protocol) .............................................5-1
6 Configuring the PHS Service...................................................................................................6-1
7 Configuring the PPPoE or IPoE Access Service (GE Upstream Transmission).............7-1
8 Configuring the Triple Play Service.......................................................................................8-1
9 Configuring the Ethernet Port Access Service (GE Upstream Transmission)................9-1
10 Configuring the VLAN ID Extension Service..................................................................10-1
Operation Guide for ONU NE Management Contents
vii
11 Configuring the Ethernet OAM Diagnosis.......................................................................11-1
11.1 Introduction to the Ethernet OAM..............................................................................................................11-4
11.2 Configuring an MD.....................................................................................................................................11-5
11.3 Configuring an MA.....................................................................................................................................11-6
11.4 Configuring a Source MEP.........................................................................................................................11-8
11.5 Enabling the Global CFM Function..........................................................................................................11-10
11.6 Configuration Example of the Ethernet OAM Diagnosis.........................................................................11-11
12 Detecting the Network..........................................................................................................12-1
12.1 Telnet...........................................................................................................................................................12-2
12.2 Ping..............................................................................................................................................................12-2
12.3 Tracert.........................................................................................................................................................12-3
12.4 SSH..............................................................................................................................................................12-3
13 Saving the Data.......................................................................................................................13-1
13.1 Setting the Parameters for Saving the Data.................................................................................................13-2
13.2 Immediately Enabling Data Saving Function.............................................................................................13-2
14 Synchronization......................................................................................................................14-1
14.1 Synchronizing NE Data...............................................................................................................................14-2
14.2 Synchronizing the NE Time........................................................................................................................14-2
14.3 Synchronizing the NE Alarm......................................................................................................................14-2
14.4 Synchronizing the System Parameter Profile..............................................................................................14-3
15 File Operations.......................................................................................................................15-1
15.1 Saving the Records as a File.......................................................................................................................15-2
15.2 Previewing the File Printing Effect.............................................................................................................15-2
15.3 Printing........................................................................................................................................................15-3
16 Introduction to the PnP Solution to FTTx Devices..........................................................16-1
16.1 Introduction to the PnP Function ...............................................................................................................16-2
16.2 PnP Application Scenario............................................................................................................................16-2
16.2.1 Predeploying xPON MDUs................................................................................................................16-3
16.2.2 Replacing an MDU Quickly...............................................................................................................16-4
17 Predeploying xPON MDUs..................................................................................................17-1
17.1 Example Network of xPON MDU Pre-deployment...................................................................................17-4
17.2 Configuration Flow of xPON MDU Pre-deployment.................................................................................17-4
17.3 Preparation..................................................................................................................................................17-6
17.3.1 Upgrading MDUs in Batches Automatically.....................................................................................17-7
17.3.2 Adding an OLT to the U2000..........................................................................................................17-12
17.3.3 Creating a Global Profile Referenced in the Network Planning Sheet............................................17-13
17.4 Operations on Sheets.................................................................................................................................17-16
17.4.1 Filling In a Network Planning Sheet................................................................................................17-17
17.4.2 Importing a Network Planning Sheet...............................................................................................17-19
17.4.3 (Optional) Binding a MAC Address or SN to the MDU..................................................................17-20
Contents
viii Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
17.5 Acceptance................................................................................................................................................17-21
17.5.1 Viewing a Pre-deployment Task and the Result..............................................................................17-21
17.5.2 Predeploying an MDU or ONT Again.............................................................................................17-22
17.6 Configuration Example of xPON MDU Pre-deployment.........................................................................17-25
18 Predeploying xPON ONTs...................................................................................................18-1
18.1 Example Network of xPON ONT Pre-deployment.....................................................................................18-2
18.2 Configuration Flow of xPON ONT Pre-deployment..................................................................................18-3
18.3 Preparation..................................................................................................................................................18-4
18.3.1 Adding an OLT to the U2000............................................................................................................18-4
18.3.2 Configuring the Profile Referenced in a Network Planning Sheet....................................................18-5
18.4 Operations on Sheets...................................................................................................................................18-7
18.4.1 Filling In a Network Planning Sheet..................................................................................................18-7
18.4.2 Importing a Network Planning Sheet.................................................................................................18-8
18.5 Acceptance..................................................................................................................................................18-9
18.5.1 Viewing a Pre-deployment Task and the Result................................................................................18-9
18.5.2 Predeploying an MDU or ONT Again.............................................................................................18-11
18.6 Configuration Example of xPON ONT Pre-deployment..........................................................................18-13
19 Configuring the GPON FTTB Services..............................................................................19-1
19.1 Adding an MDU to the U2000 (OLT in Profile Mode)..............................................................................19-3
19.1.1 Configuring an MDU SNMP Profile.................................................................................................19-4
19.1.2 Configuring a DBA Profile................................................................................................................19-5
19.1.3 Configuring a GPON Line Profile.....................................................................................................19-7
19.1.4 Confirming an MDU........................................................................................................................19-11
19.1.5 Configuring a VLAN.......................................................................................................................19-14
19.1.6 Adding a Service Virtual Port..........................................................................................................19-16
19.1.7 Checking the Communication Between the OLT and MDU...........................................................19-18
19.2 Configuring Services on the OLT.............................................................................................................19-19
19.2.2 Configuring an MEF IP Traffic Profile............................................................................................19-23
19.2.3 Adding a Service Port......................................................................................................................19-25
19.2.4 Configuring Multicast System Parameters.......................................................................................19-27
19.2.5 Configuring the Virtual Multicast Upstream Port............................................................................19-31
19.2.6 Configuring a Preview Profile..........................................................................................................19-33
19.2.7 Configuring the Multicast VLAN....................................................................................................19-34
19.2.8 Configuring a Program Profile.........................................................................................................19-38
19.2.9 Adding a Multicast Rights Profile....................................................................................................19-39
19.2.10 Configuring a Multicast User.........................................................................................................19-40
19.3 Configuring Services on the MDU............................................................................................................19-42
19.3.2 Configuring an IP Interface..............................................................................................................19-47
19.3.3 Adding a Service Port......................................................................................................................19-47
19.3.4 Configuring an ADSL Line Profile..................................................................................................19-49
ix
19.3.5 Configuring an ADSL Alarm Profile...............................................................................................19-51
19.3.6 Configuring the Attributes of an ADSL Port...................................................................................19-52
19.3.7 Activating an ADSL Port.................................................................................................................19-53
19.3.8 Configuring a Static Route...............................................................................................................19-54
19.3.9 Adding an MGC Profile...................................................................................................................19-56
19.3.10 Configuring a UAS Profile.............................................................................................................19-57
19.3.11 Adding a TID Profile......................................................................................................................19-59
19.3.12 Adding an MG................................................................................................................................19-60
19.3.13 Binding an MGC Profile................................................................................................................19-64
19.3.14 Starting an MG...............................................................................................................................19-65
19.3.15 Configuring a VoIP PSTN Port......................................................................................................19-65
19.3.16 Adding an xPON FTTB Service Provisioning Profile...................................................................19-69
19.3.17 Configuring an xPON FTTB Service.............................................................................................19-74
19.4 Configuration Examples of the GPON FTTB Services............................................................................19-76
19.4.1 Data Plan for the GPON FTTB Services.........................................................................................19-76
19.4.2 Configuring the GPON FTTB Internet Service (LAN Access).......................................................19-83
19.4.3 Configuring the GPON FTTB Internet Service (ADSL2+ Access).................................................19-97
19.4.4 Configuring the GPON FTTB Internet Service (VDSL2 Access).................................................19-113
19.4.5 Configuring the GPON FTTB Multicast Service...........................................................................19-129
19.4.6 Configuring the GPON FTTB Voice Service (H.248 Protocol)....................................................19-150
19.4.7 Configuring the GPON FTTB Voice Service (SIP Protocol)........................................................19-167
19.4.8 Configuring the GPON FTTB Service by Using a Service Provisioning Profile..........................19-185
20 Configuring the GPON FTTH Services.............................................................................20-1
20.1 Adding an ONT to the U2000 (OLT in Profile Mode)...............................................................................20-3
20.1.1 Configuring a GPON Line Profile.....................................................................................................20-3
20.1.2 Configuring a GPON Service Profile.................................................................................................20-7
20.1.3 Confirming an ONT ........................................................................................................................20-10
20.2 Configuring Services.................................................................................................................................20-11
20.2.1 Configuring the ONT Value-Added Service Configuration Profile................................................20-13
20.2.2 Configuring the Voice Value-Added Service of an ONT................................................................20-14
20.2.3 Adding a GPON FTTH Service Provisioning Profile......................................................................20-16
20.2.4 Configuring the GPON FTTH Service.............................................................................................20-20
20.3 Configuration Examples of the GPON FTTH Services............................................................................20-21
20.3.1 Data Plan for the GPON FTTH Services.........................................................................................20-21
20.3.2 Configuring the GPON FTTH Internet Service...............................................................................20-26
20.3.3 Configuring the GPON FTTH Multicast Service............................................................................20-37
20.3.4 Configuring the GPON FTTH Voice Service (H.248 Protocol)......................................................20-51
20.3.5 Configuring the GPON FTTH Voice Service (SIP Protocol)..........................................................20-63
20.3.6 Configuring the GPON FTTH Service by Using a Service Provisioning Profile............................20-74
21 Configuring the GPON Private Line Access and FTTO Services (OT928G)..............21-1
21.2 Configuring Services...................................................................................................................................21-3
Contents
x Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
21.2.1 Setting Queue Scheduling Parameters...............................................................................................21-4
21.2.2 Configuring a VLAN Service Profile.................................................................................................21-6
21.2.3 Configuring a VLAN.........................................................................................................................21-7
21.2.4 Configuring a TDM Connection......................................................................................................21-10
21.2.5 Configuring a Clock Source.............................................................................................................21-11
21.3 Configuration Examples of the GPON Private Line Access and FTTO Services (OLT+OT928G)........21-12
21.3.1 Data Plan for the GPON Private Line Access and FTTO Services (OLT+OT928G)......................21-12
21.3.2 Configuring the Ethernet Private-Line Service of an Enterprise.....................................................21-18
21.3.3 Configuring the TDM PBX Access Service/Native TDM Mobile Bearer Service (Based on the SDH
Network)......................................................................................................................................................21-24
21.3.4 Configuring the Ethernet Mobile Bearer Service.............................................................................21-29
22 Configuring xPON Private Line Access and FTTO Services (MA5612)......................22-1
22.1 Adding an MDU to the U2000 When the OLT Works in Profile Mode.....................................................22-2
22.2 Configuring Services on an OLT................................................................................................................22-2
22.2.1 Configuring the Attributes of a TOPA Card......................................................................................22-3
22.2.2 Configuring a CESoP Connection......................................................................................................22-4
22.3 Configuring Services on an MDU...............................................................................................................22-5
22.3.2 Setting Telnet/STelnet Parameters.....................................................................................................22-9
22.3.3 Configuring the MPLS Capability.....................................................................................................22-9
22.3.4 Configuring an MPLS Tunnel..........................................................................................................22-11
22.3.5 Configuring a Static LSP Segment...................................................................................................22-12
22.3.6 Configuring a PW Profile.................................................................................................................22-13
22.3.7 Adding a TDM VCL........................................................................................................................22-15
22.3.8 Configuring the PWE3.....................................................................................................................22-16
22.4 Configuring Clock Synchronization..........................................................................................................22-18
22.4.1 Configuring E1/STM-1 Line Clock Synchronization......................................................................22-19
22.4.2 Configuring Ethernet Clock Synchronization..................................................................................22-20
22.4.3 Configuring BITS Clock Synchronization.......................................................................................22-22
22.4.4 Configuring IEEE 1588v2 Clock Synchronization..........................................................................22-24
22.5 Configuration Examples of xPON Private Line Access and FTTO Services (MA5612).........................22-26
22.5.1 Data Plan for xPON Private Line Access Services..........................................................................22-27
22.5.2 Configuring the TDM PWE3 Private Line Access Service (Based on the SDH Network).............22-31
22.5.3 Configuring the TDMoGEM Private Line Access Service (Based on the SDH Network).............22-39
22.5.4 Configuring the TDMoGEM-to-TDM PWE3 Conversion Private Line Access Service (Based on the
MPLS Network)..........................................................................................................................................22-45
22.5.5 Configuring the ETH PWE3 Private Line Access Service..............................................................22-53
22.5.6 Configuring the QinQ Private-Line Private Line Access Service....................................................22-62
22.5.7 Data Plan for xPON FTTO Services................................................................................................22-69
22.5.8 Configuring the TDM PBX Access Service....................................................................................22-72
22.5.9 Configuring the IP PBX Access Service..........................................................................................22-73
22.5.10 Configuring the Router Access Service of an Enterprise...............................................................22-74
xi
23 Configuring the EPON FTTB Services..............................................................................23-1
23.1 Adding an MDU to the U2000 (OLT in Profile Mode)..............................................................................23-2
23.1.1 Configuring an MDU SNMP Profile.................................................................................................23-3
23.1.2 Configuring a DBA Profile................................................................................................................23-4
23.1.3 Configuring a Line Profile.................................................................................................................23-5
23.1.4 Confirming an MDU..........................................................................................................................23-7
23.1.7 Verifying the Interoperability Between an OLT and an MDU........................................................23-14
23.2 Configuring Services on the OLT.............................................................................................................23-15
23.3 Configuring Services on the MDU............................................................................................................23-17
23.3.1 Configuring a Static Route...............................................................................................................23-18
23.4 Configuration Examples of the EPON FTTB Services.............................................................................23-19
23.4.1 Data Plan for the EPON FTTB Services..........................................................................................23-20
23.4.2 Configuring the EPON FTTB Internet Service (LAN Access)........................................................23-27
23.4.3 Configuring the EPON FTTB Internet Service (ADSL2+ Access).................................................23-38
23.4.4 Configuring the EPON FTTB Internet Service (VDSL2 Access)...................................................23-50
23.4.5 Configuring the EPON FTTB Multicast Service.............................................................................23-63
23.4.6 Configuring the EPON FTTB Voice Service (H.248 Protocol).......................................................23-82
23.4.7 Configuring the EPON FTTB Voice Service (SIP Protocol)...........................................................23-96
23.4.8 Configuring the EPON FTTB Service by Using a Service Provisioning Profile...........................23-110
24 Configuring the EPON FTTH Services..............................................................................24-1
24.1.1 Configuring a Line Profile.................................................................................................................24-2
24.1.2 Configuring a Service Profile.............................................................................................................24-4
24.1.3 Confirming an Auto-Discovered ONT...............................................................................................24-5
24.2 Configuring Services...................................................................................................................................24-7
24.3 Configuration Examples of the EPON FTTH Services..............................................................................24-8
24.3.1 Data Plan for the EPON FTTH Services............................................................................................24-8
24.3.2 Configuring the EPON FTTH Internet Service................................................................................24-12
24.3.3 Configuring the EPON FTTH Multicast Service.............................................................................24-20
24.3.4 Configuring the EPON FTTH Voice Service (H.248 Protocol)......................................................24-32
24.3.5 Configuring the EPON FTTH Voice Service (SIP Protocol)..........................................................24-42
25 Configuring the EPON FTTO Services (OT925E)............................................................25-1
25.2 Configuring Services on the OLT...............................................................................................................25-2
25.3 Configuring Services on the OT925E.........................................................................................................25-3
25.4 Configuration Examples of the EPON FTTO Services (OLT+OT925E)...................................................25-4
25.4.1 Data Plan for the EPON FTTO Services (OLT+OT925E)................................................................25-4
25.4.2 Configuring the TDM PBX Access Service......................................................................................25-6
Contents
xii Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
26 Remote MDU Acceptance.....................................................................................................26-1
26.1 Overview of Remote Acceptance................................................................................................................26-2
26.2 Application Scenario...................................................................................................................................26-3
26.3 Configuring a Remote Emulation Test for Broadband Services.................................................................26-3
26.4 Configuring a Remote Emulation Test for Narrowband Services..............................................................26-9
27 FTTx Redundancy Protection..............................................................................................27-1
27.1 Configuring Control Card Protection..........................................................................................................27-2
27.2 Configuring Uplink Protection....................................................................................................................27-3
27.3 Configuring PON Port Protection...............................................................................................................27-4
27.4 Type B Dual-Homing Protection................................................................................................................27-6
27.4.1 Introducing GPON Type B Dual-Homing.........................................................................................27-6
27.4.2 Configuring GPON Type B Dual-Homing Automatic Switching.....................................................27-9
27.4.3 Configuring GPON Type B Dual-Homing Forcible Switching.......................................................27-11
27.5 GPON Type C Protection..........................................................................................................................27-14
27.5.1 GPON Type C Protection.................................................................................................................27-14
27.5.2 Configuring GPON Type C Protection............................................................................................27-16
27.6 EPON Type D Protection..........................................................................................................................27-30
27.6.1 EPON Type D Protection.................................................................................................................27-30
27.6.2 Configuring EPON Type D Protection............................................................................................27-32
28 Replacing an MDU Quickly.................................................................................................28-1
29 Fault Locating Based on Alarms..........................................................................................29-1
29.1 Introduction to the Alarm Correlation Analysis of FTTx Services.............................................................29-2
29.2 Correlative Relationship Between FTTx Alarms........................................................................................29-4
29.3 Alarm Locating...........................................................................................................................................29-5
29.3.1 Alarm Locating Flow.........................................................................................................................29-5
29.3.2 Alarm Locating..................................................................................................................................29-7
30 FTTx Remote Fault Diagnosis.............................................................................................30-1
30.1 Diagnosing a Service Fault Through the Fault Diagnosis Platform............................................................30-2
30.1.1 Fault Diagnosis Platform....................................................................................................................30-2
30.1.2 Application Scope of Fault Diagnosis................................................................................................30-4
30.1.3 Objects of Fault Diagnosis.................................................................................................................30-5
30.1.4 Diagnosing the Faults of All Broadband Services.............................................................................30-5
30.1.5 Performing a Health Check on Broadband Services..........................................................................30-6
30.1.6 Diagnosing the Faults of All Voice Services.....................................................................................30-7
30.1.7 Performing a Health Check on Voice Services..................................................................................30-8
31 Monitoring Real-Time Performance..................................................................................31-1
32 Quick Cutover of FTTx Services.........................................................................................32-1
32.1 Cutting Over Services on a GPON Port......................................................................................................32-3
32.2 Cutting Over Services on EPON Ports........................................................................................................32-5
xiii
33 Bulk Configuring in Command Line Script Files and Sending the Script Files to NEs
.........................................................................................................................................................33-1
34 Remote Maintenance Guide................................................................................................34-1
34.1 Monitoring Critical and Major Alarms of NEs...........................................................................................34-3
34.2 Measuring the CPU Usage of a Board........................................................................................................34-5
34.3 Measuring the Performance of an Upstream Ethernet Port.........................................................................34-8
34.4 Measuring the Usage of NE Resources.....................................................................................................34-10
34.5 Checking the NE User Level.....................................................................................................................34-11
34.6 Changing the Password of an NE User.....................................................................................................34-12
34.7 Saving, Backing Up, and Restoring NE Data...........................................................................................34-14
34.7.1 Saving and Backing Up the NE Data Periodically...........................................................................34-14
34.7.2 Saving and Backing Up NE Data Immediately................................................................................34-20
34.7.3 Checking the Backup of the NE Configuration Data.......................................................................34-23
34.7.4 Restoring the NE Data Immediately................................................................................................34-25
A Acronyms and Abbreviations................................................................................................A-1
Contents
xiv Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
Figures
Figure 1-1 Example network of the outband management ...............................................................................1-22
Figure 1-2 Example network of the inband management .................................................................................1-28
Figure 2-1 Flowchart for configuring the VLAN Stacking Wholesale Service...................................................2-3
Figure 2-2 Example network of the VLAN Stacking Wholesale Service............................................................2-4
Figure 3-1 Flowchart for configuring the QinQ VLAN Leased Line Service.....................................................3-3
Figure 3-2 Example network of the QinQ VLAN Leased Line Service..............................................................3-4
Figure 4-1 Example network of the dual GE link aggregation upstream transmission .......................................4-1
Figure 5-1 Example network of the VoIP ISDN BRA service ...........................................................................5-1
Figure 6-1 Example network of the PHS service ................................................................................................6-1
Figure 7-1 Example network of the PPPoE or IPoE access service.....................................................................7-1
Figure 8-1 Example network of the triple play service .......................................................................................8-2
Figure 9-1 Example network of the Ethernet port access service........................................................................9-2
Figure 10-1 Example network of the VLAN ID extension service....................................................................10-1
Figure 11-1 Flowchart for configuring the Ethernet OAM diagnosis................................................................11-2
Figure 11-2 Example network of the Ethernet OAM.......................................................................................11-11
Figure 16-1 Flowchart for predeploying the MDU whose MAC address or SN is known................................16-3
Figure 16-2 Flowchart for predeploying the MDU whose MAC address or SN is unknown............................16-4
Figure 16-3 Flowchart for quickly replacing an MDU......................................................................................16-5
Figure 16-4 User-defined policy (1)...................................................................................................................16-6
Figure 17-1 Flowchart for predeploying the MDU whose MAC address or SN is known................................17-2
Figure 17-2 Flowchart for predeploying the MDU whose MAC address or SN is unknown............................17-2
Figure 17-3 Example network of xPON MDU pre-deployment........................................................................17-4
Figure 17-4 Flowchart for predeploying an xPON MDU..................................................................................17-6
Figure 18-1 Example network of xPON ONT pre-deployment.........................................................................18-2
Figure 18-2 Flowchart for predeploying an xPON ONT...................................................................................18-4
Figure 19-1 Configuring the GPON FTTB Internet service (LAN access).....................................................19-84
Figure 19-2 Configuring the GPON FTTB Internet service (ADSL2+ access)...............................................19-99
Figure 19-3 Configuring the GPON FTTB Internet service (VDSL2 access)...............................................19-114
Figure 19-4 Configuring the GPON FTTB multicast service........................................................................19-130
Figure 19-5 Configuring the GPON FTTB voice service (H.248 protocol)..................................................19-151
Figure 19-6 Configuring the GPON FTTB voice service (SIP protocol)......................................................19-168
Figure 19-7 Configuring the GPON FTTB service by using a service provisioning profile.........................19-186
Operation Guide for ONU NE Management Figures
xv
Figure 20-1 Configuring the GPON FTTH Internet service............................................................................20-27
Figure 20-2 Configuring the GPON FTTH multicast service..........................................................................20-38
Figure 20-3 Configuring the GPON FTTH voice service (H.248 protocol)....................................................20-53
Figure 20-4 Configuring the GPON FTTH voice service (SIP protocol)........................................................20-64
Figure 20-5 Configuring the GPON FTTH service by using a service provisioning profile...........................20-75
Figure 21-1 Configuring the Ethernet private-line service of the enterprise....................................................21-18
Figure 21-2 Configuring the TDM PBX access service...................................................................................21-24
Figure 21-3 Configuring the native TDM mobile bearer service (based on the SDH network)......................21-24
Figure 21-4 Configuring the Ethernet mobile bearer service...........................................................................21-30
Figure 22-1 Configuring the TDM PWE3 private line access service (based on the SDH network)..............22-31
Figure 22-2 Configuring the TDMoGEM private line access service (based on the SDH network)...............22-40
Figure 22-3 Configuring the TDMoGEM-to-TDM PWE3 conversion private line access service (based on the
MPLS network).................................................................................................................................................22-45
Figure 22-4 Configuring the ETH PWE3 private line access service..............................................................22-54
Figure 22-5 Configuring the QinQ private-line private line access service.....................................................22-63
Figure 22-6 Configuring the TDM PBX access service...................................................................................22-72
Figure 22-7 Configuring the IP PBX access service........................................................................................22-73
Figure 22-8 Configuring the router access service of an enterprise.................................................................22-74
Figure 23-1 Configuring the EPON FTTB Internet service (LAN access)......................................................23-28
Figure 23-2 Configuring the EPON FTTB Internet service (ADSL2+ access)...............................................23-39
Figure 23-3 Configuring the EPON FTTB Internet service (VDSL2 access)..................................................23-51
Figure 23-4 Configuring the EPON FTTB multicast service...........................................................................23-64
Figure 23-5 Configuring the EPON FTTB voice service (H.248 protocol).....................................................23-83
Figure 23-6 Configuring the EPON FTTB voice service (SIP protocol).........................................................23-97
Figure 23-7 Configuring the EPON FTTB service by using a service provisioning profile..........................23-111
Figure 24-1 Configuring the EPON FTTH Internet service.............................................................................24-13
Figure 24-2 Configuring the EPON FTTH multicast service..........................................................................24-21
Figure 24-3 Configuring the EPON FTTH voice service (H.248 protocol).....................................................24-34
Figure 24-4 Configuring the EPON FTTH voice service (SIP protocol).........................................................24-43
Figure 25-1 Configuring the TDM PBX access service.....................................................................................25-6
Figure 26-1 Flowchart of MDU remote acceptance ..........................................................................................26-3
Figure 27-1 Type B dual-homing protection switching mode...........................................................................27-7
Figure 27-2 Working principle of type B dual-homing automatic switching....................................................27-8
Figure 27-3 Working principle of type B dual-homing forced switching..........................................................27-8
Figure 27-4 Topology view of type B dual-homing...........................................................................................27-9
Figure 27-5 GPON type C protection switching model...................................................................................27-15
Figure 27-6 EPON type D protection switching model...................................................................................27-31
Figure 28-1 Flowchart for quickly replacing an MDU...................................................................................... 28-2
Figure 29-1 Diagram of the correlative relationship between GPON FTTx alarms..........................................29-4
Figure 29-2 Alarm locating flowchart................................................................................................................29-6
Figure 30-1 Fault locating topology view and its functions for broadband services......................................... 30-3
Figures
xvi Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
Figure 30-2 Service topology view and its functions for broadband services...................................................30-3
Figure 32-1 Flowchart for cutting over GPON port services.............................................................................32-3
Figure 32-2 Flowchart for cutting over EPON services.....................................................................................32-6
Operation Guide for ONU NE Management Figures
xvii
Tables
Table 1-1 Types and versions of NEs supporting data synchronization in xFTP mode.................................... 1-12
Table 1-2 Data plan for the outband network management in the standalone mode......................................... 1-22
Table 1-3 Data plan for the outband network management in the HA system...................................................1-23
Table 1-4 Data plan for the inband network management in the standalone mode........................................... 1-29
Table 1-5 Data plan for the inband network management in the HA system.....................................................1-30
Table 2-1 Data plan for configuring the VLAN Stacking Wholesale Service.....................................................2-5
Table 3-1 Data plan for configuring the QinQ VLAN Leased Line Service........................................................3-5
Table 4-1 Data plan for the dual GE link aggregation upstream transmission.....................................................4-2
Table 5-1 Data plan for the VoIP ISDN BRA service.........................................................................................5-2
Table 6-1 Data plan for the PHS service on the OLT..........................................................................................6-2
Table 6-2 Data plan for the PHS service on the UA5000 (on the convergence side)..........................................6-2
Table 6-3 Data plan for the PHS service on the MA5616....................................................................................6-3
Table 7-1 Data plan for the PPPoE or IPoE access service..................................................................................7-2
Table 8-1 Implementation mode of the triple play service...................................................................................8-1
Table 8-2 Data plan for the triple play service.....................................................................................................8-2
Table 9-1 Data plan for the Ethernet port access service.....................................................................................9-2
Table 10-1 Data plan for the VLAN ID extension service.................................................................................10-2
Table 11-1 Data plan for the Ethernet OAM....................................................................................................11-12
Table 17-1 The common problems and solutions to network planning sheets................................................17-23
Table 17-2 The common problems occurred when tasks are performed on the OLT and solutions to these problems
...........................................................................................................................................................................17-23
Table 17-3 The common problems occurred when tasks are performed on the MDU and solutions to these problems.
...........................................................................................................................................................................17-24
Table 17-4 Data plan in the preparation phase.................................................................................................17-25
Table 17-5 Data plan in a network planning sheet...........................................................................................17-27
Table 18-1 The common problems and solutions to network planning sheets................................................18-11
Table 18-2 The common problems occurred when tasks are performed on the OLT and solutions to these problems
...........................................................................................................................................................................18-12
Table 18-3 The common problems occurred when tasks are performed on the MDU and solutions to these problems.
...........................................................................................................................................................................18-12
Table 18-4 Data plan in the preparation phase.................................................................................................18-13
Table 18-5 Data plan in a network planning sheet...........................................................................................18-15
Table 19-1 Data plan for the GPON FTTB services........................................................................................19-77
Table 20-1 Data plan for the GPON FTTH services........................................................................................20-21
Operation Guide for ONU NE Management Tables
xix
Table 21-1 Data plan for the GPON Private Line Access and FTTO services................................................21-13
Table 22-1 xPON private line access services - device management..............................................................22-27
Table 22-2 GPON private line access services - TDM PWE3 private line access service (based on the SDH network)
...........................................................................................................................................................................22-28
Table 22-3 xPON FTTO services - device management..................................................................................22-69
Table 22-4 GPON FTTO services - router access service of an enterprise......................................................22-70
Table 23-1 Data plan for the EPON FTTB services.........................................................................................23-20
Table 24-1 Data plan for the EPON FTTH services..........................................................................................24-9
Table 25-1 Data plan for the EPON FTTO services..........................................................................................25-4
Table 26-1 Parameters required for configuring a remote emulation test for broadband services.....................26-5
Table 26-2 Parameters required for configuring a remote emulation test for narrowband services................26-10
Table 27-1 Key parameters required for adding a protection group..................................................................27-4
Table 27-2 Parameters required for adding a dual homing protection group...................................................27-10
Table 27-3 Parameters required for adding a dual homing protection group...................................................27-12
Table 27-4 Parameters required for adding an ONU........................................................................................27-18
Table 27-5 Key parameters required for adding a protection group................................................................27-28
Table 27-6 Parameters required for adding an ONU........................................................................................27-35
Table 27-7 Key parameters required for adding a protection group................................................................27-46
Table 29-1 Relevant alarms................................................................................................................................29-2
Table 32-1 Parameters required for modifying the attributes of a GPON UNI port..........................................32-4
Table 32-2 Parameters required for modifying the parameters of an EPON UNI port......................................32-7
Tables
xx Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
1 Managing Network Elements
About This Chapter
The U2000 provides device management functions through the graphical user interface (GUI).
The GUI displays the physical status of the devices in the topological view. Therefore, the
devices are managed in a centralized manner through the topology or view.
Context
Optical network units (ONUs) are classified into two types: multi-dwelling unit (MDU) and
optical network terminal (ONT).
l MDUs are deployed in corridors or by the road and used as ONUs in the fiber to the building
(FTTB) or fiber to the curb (FTTC) scenario. The MDUs provide voice, video, and data
services for multiple users through various ports, and the OLT at the CO implements
convergence of the services of multiple remote ONUs.
l ONTs are deployed in user homes and used as ONUs in the fiber to the home (FTTH)
scenario. An ONT provides voice, video, and data services for a single user, and the OLT
at the CO implements convergence of the services of multiple ONUs.
1.1 Configuring the xFTP Service
This topic describes how to configure the FTP, SFTP, or TFTP service on Windows, Solaris, or
Linux OS and how to check the xFTP service on the U2000.
1.2 Adding an ONU
This topic describes how to add an ONU to the U2000 so that the connection between the ONU
and the OLT can be set up in the L2 topological view. After the ONU is added, the U2000 can
maintain and manage the ONU and other devices in a centralized manner.
1.3 Replacing an ONU
This topic describes how to replace an ONU when it is faulty. In this case, connect the new ONU
that is of the same type as the faulty ONU to the corresponding port on the OLT, and then bind
the MAC address of the new ONU. After the new ONU goes online, service configuration data
is issued to the new ONU automatically. Therefore, you need not configure the data again.
1.4 Moving an ONU
This topic describes how to move an ONU so that the ONU is connected to another optical
splitter.
Operation Guide for ONU NE Management 1 Managing Network Elements
1-1
1.5 Managing the SRG Web Service
The SRG is a service router gateway developed by Huawei. The SRG is a cost-effective security
and access solution for small and medium-sized enterprise networks and the telecommunications
networks.
1.6 Configuration Example of the Outband Management (Based on the SNMPv3 Protocol)
This topic provides an example for configuring the outband management to manage and maintain
the ONU. In outband management the non-service channel is used to transmit the management
information. With the use of the non-service channel, the management channel and the service
channel are separated, which provides a more reliable management channel for the device
compared with the inband management.
1.7 Configuration Example of the Inband Management
This topic provides an example for configuring the inband management to manage and maintain
the ONU. The inband management transmits the management information through the service
channel of the device. The inband management features the flexible networking without any
adjunct device and low cost, but it is difficult to maintain.
1-2 Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
1.1 Configuring the xFTP Service
This topic describes how to configure the FTP, SFTP, or TFTP service on Windows, Solaris, or
Linux OS and how to check the xFTP service on the U2000.
1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)
This topic describes how to configure and start the FTP, SFTP, or TFTP service on Windows
OS. NE software communicates with the client or NEs through the FTP, SFTP, or TFTP protocol
for NE upgrade, data backup, and patch installation.
1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)
This topic describes how to configure and start the FTP, SFTP, or TFTP service on Solaris OS.
The DC communicates with clients or NEs by using the FTP, SFTP, or TFTP protocol to upgrade
NEs, back up data, and install patches.
1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)
This topic describes how to configure and start the FTP, SFTP, or TFTP service on Linux OS.
1.1.4 Configuring the xFTP Watcher
When NE data is synchronized to the U2000 server in FTP or SFTP mode, you need to configure
the xFTP watcher. If you configure the xFTP watcher correctly, the NE data is successfully
synchronized to the U2000 server and the U2000 successfully manages the NEs whose data is
synchronized in xFTP mode.
1.1.5 Configuring the xFTP File in the NAT Networking Mode
In the NAT networking mode, the xFTP must be configured to ensure that the device data can
be synchronized to the U2000 server automatically.
1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)
Context
l The third-party tool must be started after the FTP, SFTP, or TFTP server is configured.
l The file transfer parameters set on the U2000 must be the same as the parameters set on
the FTP, SFTP, or TFTP server.
Procedure
l Configuring the FTP server by using the third-party tool wftpd32.exe
1. Copy the wftpd32.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, choose Security > Users/rights and create a user;
choose Security > Host/net and enter the IP address of the FTP server.
1-3
l Configuring the SFTP server by using the third-party tool msftpsrvr.exe
1. Copy the msftpsrvr.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, create a user.
l Configuring the TFTP server by using the third-party tool tftpd32.exe
1. Copy the tftpd32.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, set the root directory and the IP address of the
TFTP server.
l Testing the communication between the FTP, SFTP, or TFTP service and the NE
software
Issue 03 (2010-11-19)
1. Choose Administration > NE Software Management > FTP Settings from the
main menu.
2. In the dialog box that is displayed, click the File Transfer Service Setting tab to
configure the parameters of the file transfer service.
NOTE
l File Transfer Service Root Directory configured on the U2000 must be the same as the
root directory configured on the FTP, SFTP, or TFTP server. In addition, the FTP, SFTP,
or TFTP server must be started.
l If the FTP protocol is used, ensure that the user name and password set in the last step are
the same as the user name and password set when the FTP server is configured.
l If the SFTP protocol is used, ensure that the user name, password, and port number set in
the last step are the same as the user name, password, and port number set when the SFTP
server is configured.
l Click Test FTP, Test SFTP, or Test TFTP to check the configuration of the file transfer
service.
3. Click the Transfer Protocol tab. Select a proper protocol from the Protocol drop-
down list for file transfer between NEs and the U2000 server.
1-5
4. Click OK.
----End
1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)
This topic describes how to configure and start the FTP, SFTP, or TFTP service on Solaris OS.
Prerequisite
You must be logged in to the Solaris OS as user root.
Context
l In the case of the Solaris- or Linux-based U2000, the FTP, SFTP, or TFTP function
provided by the Solaris or Linux OS is used.
l On Solaris OS, the FTP, SFTP, or TFTP server can be configured in the command line
interface (CLI). The configuration method varies with OS versions. The following section
describes the configuration processes on the Solaris 8 and Solaris 10 OSs in details.
l The root directory, user name, and password of the FTP, SFTP, or TFTP service must be
the same as those that are set on the U2000 client.
Procedure
l Configure the FTP server.
1. To start the FTP service, run the following commands:
Solaris 8:
# cd /etc/init.d
Issue 03 (2010-11-19)
# ./inetsvc start
Solaris 10:
# inetconv -i /etc/inet/inetd.conf 1>/dev/null 2>&1
# svcadm enable svc:/network/ftp
2. To check whether the FTP service is started, run the # netstat -a | grep ftp command.
NOTE
If the following message is displayed, it indicates that the FTP service is started.
*.tftp Idle
*.tftp
Idle
*.ftp *.* 0 0 49152 0
LISTEN
*.ftp *.*
0 0
49152 0 LISTEN
3. To create an FTP user and set its user name and password, run the following
commands:
# useradd -d /tftpboot -s /bin/bash ftpuser
# passwd ftpuser
New Password: ftp123
Re-enter new Password: ftp123
l Configure the SFTP server.
1. If the ssh service is not started, perform the following steps to start it:
(1) In the /etc/ssh/sshd_config file, change PasswordAuthentication no to
PasswordAuthentication yes and PermitRootLogin no to PermitRootLogin
yes.
(2) Run the svcadm refresh svc:/network/ssh:default command.
2. To check whether the ssh service is started on Solaris OS, run the svcs -a |grep ssh
command.
NOTE
If the following message is displayed, it indicates that the ssh service is started on Solaris OS.
online May_04 svc:/network/ssh:default
*.tftp
3. To create an SFTP user and set its user name and password, run the following
commands:
# useradd -d /tftpboot sftpuser
# passwd sftpuser
l Configure the TFTP server.
1. On the Common Desktop Environment (CDE) desktop, right-click and choose File >
File Manager from the shortcut menu.
2. Locate the inetd.conf file in the etc directory and double-click the file to open the file.
3. Search for the tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
command.
NOTE
If the command does not exist, add it to the file. If the command exists but is commented out
by the pound sign (#), delete the pound sign and save the file.
4. Start the TFTP service.
1-7
Solaris 8: Run the ./inetsvc start command in the /etc/init.d path to start the TFTP
service. After the service is started, the default TFTP file path is /tftpboot.
Solaris 10: Run the inetconv -i /etc/inet/inetd.conf 1>/dev/null 2>&1 command,
and then run the svcadm enable svc:/network/tftp/udp6:default command to
start the TFTP service. After the service is started, the default TFTP file path is /
tftpboot.
NOTE
If the /etc/inet/inetd.conf configuration file is modified, you need to stop the TFTP service
and then restart it. To stop the TFTP service, do as follows:
l Solaris 8: Run the ./inetsvc stop command in the /etc/init.d path.
l Solaris 10: Run the svcadm disable svc:/network/tftp/udp6:default command.
5. Run the #svcs |grep tftp command to check whether the TFTP service is started on
Solaris OS.
software
1. Choose Administration > NE Software Management > FTP Settings from the
main menu.
Issue 03 (2010-11-19)
NOTE
service.
4. Click OK.
----End
1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)
This topic describes how to configure and start the FTP, SFTP, or TFTP service on Linux OS.
Prerequisite
You must be logged in to the Linux OS as user root.
1-9
Context
l In the case of the Solaris- or Linux-based U2000, the FTP, SFTP, or TFTP function
provided by the Solaris or Linux OS is used.
l The root directory, user name, and password of the FTP, SFTP, or TFTP service must be
the same as those that are set on the U2000 client.
l In a distributed system, you need to configure the FTP or SFTP service on the master server
and the slave server that is deployed with the access NE management instance by following
the same procedure.
Procedure
l Configure the FTP server.
1. To create an FTP user and set its user name and password, run the following
commands:
# useradd -d /tftpboot -s /bin/bash ftpuser
# passwd ftpuser
New Password: ftp123
Re-enter new Password: ftp123
2. Restart the FTP service.
To stop the FTP service, run the following commands:
# cd /etc/init.d
# /xinetd stop
To start the FTP service, run the following commands:
# cd /etc/init.d
# ./xinetd start
l Configure the SFTP server.
1. In the terminal window, run the useradd -d /ftpboot -m -s /bin/bash ftpuser
command to create an SFTP user. ftpuser in the command indicates the SFTP user
name.
2. Restart the OS.
3. After the OS is restarted, run the passwd ftpuser command to change the password
of the SFTP user to ftpuser.
4. In the /etc/ssh/sshd_config file, change PasswordAuthentication no to
PasswordAuthentication yes to allow the SFTP user to log in to the Linux OS after
entering the password.
5. After the configuration file is modified, run the /etc/init.d/sshd stop command to stop
the SFTP service.
6. Run the /etc/init.d/sshd start command to start the SFTP service.
7. Run the sftp servername@localhost command to connect to the server.
l Configure the TFTP server.
1. To configure the TFTP server by using the YaST, do as follows:
(1) Click YaST. The administrator setting panel is displayed.
(2) Choose Network Services > TFTP Server. The TFTP Server Configuration
window is displayed, as shown in the following figure.
Issue 03 (2010-11-19)
2. To configure the TFTP server by using the Konsole, do as follows:
(1) In the terminal window, run the cd /etc/xinetd.d command to navigate to the /
etc/xinetd.d directory. Then, run the vi tftp command to open the tftp file.
(2) Set disable to no (that is, disable = no) to start the TFTP server.
NOTE
To stop the TFTP service, set disable to yes (that is, disable = yes) in the tftp file.
To restart the TFTP service, run the /etc/init.d/xinetd restart command.
----End
1.1.4 Configuring the xFTP Watcher
When NE data is synchronized to the U2000 server in FTP or SFTP mode, you need to configure
the xFTP watcher. If you configure the xFTP watcher correctly, the NE data is successfully
synchronized to the U2000 server and the U2000 successfully manages the NEs whose data is
synchronized in xFTP mode.
Prerequisite
The third-party software must be available for configuring the FTP server if more than 5,000
NEs are managed.
The FTP or SFTP server must be configured and the xFTP service must be enabled. For details,
see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the
FTP, SFTP, or TFTP Service (Solaris), and 1.1.3 Configuring the FTP, SFTP, or TFTP
Service (Linux).
Context
Data synchronization in xFTP mode is implemented based on the FTP or SFTP protocol. To
improve the efficiency of synchronizing NE data, NEs upload their data in the form of files to
the U2000 by using the FTP or SFTP protocol.
1-11
Table 1-1 Types and versions of NEs supporting data synchronization in xFTP mode
NE Type Applicable Version
MA5662 MA5662 V800R202C00
ATN910 ATN931 V800R202
MA5626E MA5626E V800R307C00
MA5620E MA5620E V800R307C00
MA5620G MA5620G V800R307C00
MA5626G MA5626G V800R307C00
MA5610 MA5610 V800R306C01
MA5610 V800R307C00
MA5616 MA5616 V800R306C01
MA5616 V800R307C00
MA5616 V800R308C00
MA5652G MA5652 V800R306C01
MA5652 V800R307C00
MA5620 MA5620 V800R307C00
MA5626 MA5626 V800R307C00
ATN930 ATN930 V800R307
MA5635 MA5635 V800R307C00
MA5612 MA5612 V800R307C00
MA5628 MA5628 V800R307C00

NOTE
l In the case of the NE whose data is synchronized in SNMP mode, you do not need to configure the
xFTP watcher.
l The U2000 synchronizes data in FTP or SFTP mode, not in TFTP mode.
l After the U2000 that is newly installed is started successfully, it automatically configures the xFTP
watcher. Therefore, you do not need to modify the default configuration unless it is necessary.
Procedure
1 Choose Administration > Settings > xFtpWatcher from the main menu.
2 In the xFtpWatcher dialog box, click Add.
3 In the dialog box that is displayed, set the parameters.
Issue 03 (2010-11-19)
NOTE
l The default values of Username, Password, and Root path of the U2000 FTP service are ftpuser,
u2000ftpuser, d: (Windows-based server) or /ftpboot ( Linux-based server or Solaris-based server for
single-server system) or /opt/sybase/data ( Solaris-based server for backup system) respectively.
l If the user password and path of the FTP service are changed, make sure that Password and Root
path in the xFtpWatcher dialog box are also changed.
l IP address cannot be set to 127.0.0.1.
l In the case of a single-server system, IP address is the IP address of the FTP server that can
communicate with NEs, that is, the IP address of the U2000 server. In the case of a distributed system,
IP address is the IP address that is configured by means of the network address translation (NAT).
l The value of Root path must be correct. In addition, Root path must be an absolute path and cannot
end with / or \ or contain a space.
----End
1.1.5 Configuring the xFTP File in the NAT Networking Mode
In the NAT networking mode, the xFTP must be configured to ensure that the device data can
be synchronized to the U2000 server automatically.
Prerequisite
The xFTP watcher of the U2000 must be configured, the FTP server must be configured
successfully, and the FTP service must be enabled. For details, see 1.1.4 Configuring the xFTP
Watcher.
Context
l If the NAT networking mode is adopted or the U2000 manages NEs in multiple separated
network segments, you need to create the iptable_ne2nms.cfg file manually and configure
it to ensure that the device data is synchronized to the U2000 server automatically.
l In the distributed NAT networking mode, the iptable_ne2nms.cfg file must be configured
on the master server.
1-13
Procedure
1 Open the iptable_ne2nms.cfg file in the installation directory $IMAPROOT/server/etc/
conf/ of the U2000 server.
2 Configure the iptable_ne2nms.cfg file.
Each line added to the configuration file indicates a mapping configuration. The format of the
mapping configurations is as follows:
NE start IP address NE end IP address U2000 IP address [the IP address of the U2000 after
NAT translation]
The parameters are separated with white spaces or tab spaces.
l NE start IP address and NE end IP address: Specify the IP address range of NEs.
l U2000 IP address: Indicates the external IP address that the U2000 at a site uses to
communicate with NEs. The IP address ranges of the NEs at different sites can overlap.
l The IP address of the U2000 after NAT translation: If the NAT networking mode is
adopted between the U2000 and NEs, this parameter must be specified. Otherwise, this
parameter does not need to be specified.
For example, if the NAT networking mode is not adopted, the mapping configuration is
10.71.226.1 10.71.226.255 10.71.221.153.
If the NAT networking mode is adopted, the mapping configuration is 10.71.227.1
10.71.227.255 10.71.221.152 10.10.10.10.
----End
Example
In the NAT networking mode, the IP address of the U2000 server is 136.12.36.2 and the IP
address changes to 198.168.23.25 after the mapping on the firewall. The IP addresses of certain
devices are in the 198.0.0.0 network and these devices can communicate with the U2000 through
the mapping address of the U2000 server. The IP addresses of other devices are in the 136.0.0.0
network and these devices can communicate with the U2000 server.
In this case, configure the iptable_ne2nms.cfg file as follows:
136.0.0.1 136.0.0.255 136.12.36.2
198.0.0.1 198.0.0.255 136.12.36.2 198.168.23.25
1.2 Adding an ONU
This topic describes how to add an ONU to the U2000 so that the connection between the ONU
and the OLT can be set up in the L2 topological view. After the ONU is added, the U2000 can
maintain and manage the ONU and other devices in a centralized manner.
Prerequisite
Before adding an ONU, make sure that the FTP server is configured correctly and the FTP service
starts. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows).
For the ONUs that support the EPON upstream mode:
Issue 03 (2010-11-19)
l When the OLT is set to work in the profile mode, you need to configure the EPON line
profile and the EPON service profile for it.
l The ONU that is discovered automatically must exist on the OLT.
For the ONUs that support the GPON upstream mode:
l When the OLT is set to work in the distributed mode, you need to configure the GPON
ONU capacity profile and the MDU SNMP profile for it.
l When the OLT is set to work in the profile mode, you need to configure the GPON line
profile and the GPON service profile for it.
l The ONU that is discovered automatically must exist on the OLT.
ONUs can be configured and managed remotely on the OLT through the OMCI or SNMP
protocol similarly. The difference is as follows:
l If an ONU is added through the OMCI protocol, the U2000 can discover the ONU
automatically when the ONU is online only after the OLT issues the SNMP parameters.
l If an ONU is added through the SNMP protocol, the U2000 can discover the ONU
automatically when the ONU is online.
Context
l When you add an ONU on the U2000 and do not set Alias, the U2000 obtains the system
name of the ONU and considers the system name as the ONU alias.
l When the U2000 discovers multiple ONUs automatically, it obtains the system names of
the ONUs and consider the system names as the ONU aliases.
NOTE
To set the system name of an ONU, run the sysname command. By default, the device name is the system
name. For details, see the command reference.
Procedure
l To add an MDU that supports xPON upstream transmission, do as follows:
1. On the topological navigation tree, select the required ODN under the OLT node.
Select the splitter under the ODN, right-click, and then choose New > ONU; or select
the splitter under the ODN, right-click the blank area on the Physical Root interface
on the right side, and then choose New > ONU.
2. On the interface that is displayed, set the parameters on the Basic Parameters and
Network Management Channel Parameters tab pages (on this interface, the ONU
that supports the GPON upstream mode is considered as an example).
1-15
Issue 03 (2010-11-19)
NOTE
l When the OLT works in the profile mode, the ONU that supports the EPON upstream mode
needs to be bound with the EPON line profile and the EPON service profile.
l When the OLT works in the profile mode, the ONU that supports the GPON upstream mode
needs to be bound with the GPON line profile and the GPON service profile.
l When the OLT works in the distributed mode, the ONU that supports the GPON upstream mode
needs to be bound with the ONU capacity profile.
l When the OLT sets network management channel parameters check box is cleared, ONUs
are configured and managed remotely on the OLT through the OMCI protocol.
l When the OLT sets network management channel parameters check box is selected, ONUs
are configured and managed remotely on the OLT through the SNMP protocol.
l Do not add the SNMP parameters on the ONU through the serial port, but issue the SNMP profile
from the OLT to the ONU only.
3. Click OK.
4. In the Main Topology, double-click the required OLT in the Physical Root navigation
tree; or right-click the required OLT and choose NE Explorer from the shortcut menu.
5. Choose VLAN from the navigation tree.
6. On the VLAN tab page, right-click and choose Add from the shortcut menu.
7. In the dialog box that is displayed, set the parameters.
VLAN ID: 4000
Type: Smart VLAN
8. Click Next.
Click the Upstream Port tab and add upstream port 0/19/0 as the upstream port
of the VLAN.
Click the L3 Interface tab and set the parameters.
Configure L3 Interface: selected
IP Address: 192.168.50.4
9. Click Finish.
10. Choose GPON > GPON ONU from the navigation tree.
11. On the GPON ONU tab page, set the filter criteria to display the required GPON
ONUs.
12. In the information list, select the record where the shelf, slot, port, and ONU IDs are
0, 2, 1, and 0 respectively and click the ServicePort Info tab in the lower pane.
13. On the ServicePort Info tab page, right-click and choose Add from the shortcut menu.
Connection Type: LAN-GPON
VLAN ID: 4000
Interface Selection: 0/2/1/0/0
Service Type: Multi-Service VLAN
User VLAN: 4000
Keep the upstream and downstream settings the same: selected
Upstream Traffic Name: ip-traffic-table_6 (it is recommended that you use the
default profile ip-traffic-table_6 because the OLT does not limit the rates of service
streams in the management VLAN)
1-17
15. Click OK.
l To add an MDU that supports GE upstream transmission, do as follows:
The MDU that supports GE upstream transmission supports the SNMPv3 protocol.
1. Choose Administration > NE Communicate Parameter > NE Access Protocol
Parameters from the main menu.
2. On the tab page, click Reset. In the dialog box that is displayed, click the SNMPv1
Parameters tab and then click Add.
3. In the dialog box that is displayed, set the name and SNMP parameters as follows:
NOTE
The SNMPv3 protocol supports three security levels: authentication, noauth, and privacy. To
implement successful communication through the SNMPv3 protocol, ensure that the
authentication and encryption modes of the SNMP user on the device, SNMP group, and the
SNMP parameters on the U2000 are the same.
4. Click OK.
5. Select the added SNMP parameters. Click OK.
6. In the dialog box that is displayed, click Yes. Test the set SNMP parameters.
7. The U2000 displays the Loading dialog box. After the testing is complete, click
OK.
8. In the physical root view page, right-click and then choose New > NE.
Issue 03 (2010-11-19)
10. Click OK.
----End
1.3 Replacing an ONU
This topic describes how to replace an ONU when it is faulty. In this case, connect the new ONU
that is of the same type as the faulty ONU to the corresponding port on the OLT, and then bind
the MAC address of the new ONU. After the new ONU goes online, service configuration data
is issued to the new ONU automatically. Therefore, you need not configure the data again.
Context
NOTE
You can replace the ONU with a new ONU if the ONU is not used any more. The data of the original ONU
is synchronized to the new ONU.
Procedure
1 On the Main Topology, choose the OLT that the ONU is connected to from the navigation tree,
select the ONU subnode, right-click, and then choose GPON Option > Replace ONU or EPON
Option > Replace ONU.
2 In the Replace ONU dialog box, modify the authentication information.
3 Click OK.
----End
Result
After the ONU is replaced, the new ONU is online, that is, the ONU icon in the Physical
Root navigation tree in Main Topology changes from gray to green.
The OLT reports a trap to the U2000, and the U2000 determines whether the ONU is the new
ONU according to the MAC address in the trap. If the ONU is the new ONU, the U2000 applies
1-19
the configuration data that is backed up to the new ONU. In addition, the DC automatically
creates an upgrade task. Choose Administration > NE Software Management > NE Upgrade
Task Management from the main menu. Then, view the task information on the NE Upgrade
Task Management tab page.
1.4 Moving an ONU
This topic describes how to move an ONU so that the ONU is connected to another optical
splitter.
Context
An ONU can be moved only between ODN submaps where the same PON port is located. It
cannot be moved to the ODN submap where another PON port is located.
Procedure
1 On the Main Topology, select the OLT to which the ONU is connected from the navigation
tree, select the ONU subnode, right-click, and then choose Move To.
2 On the Move ONU interface, select the required splitter.
3 Click OK.
----End
1.5 Managing the SRG Web Service
The SRG is a service router gateway developed by Huawei. The SRG is a cost-effective security
and access solution for small and medium-sized enterprise networks and the telecommunications
networks.
Context
The web-manager function provides users with a simple and friendly Web configuration
interface. Through this interface, users can operate and maintain the SRG conveniently.
The NE Explorer tab page is used to configure and manage the access services of the SRG, and
the Web LCT tab page is used to configure and manage other services of the SRG, such as route
configuration and security management.
Procedure
1 On the Physical Root navigation tree on the Main Topology tab page, double-click the required
SRG device; or select the required SRG device, right-click, and then choose NE Explorer, the
U2000 supports the automatic login of the Web interface of the SRG.
Issue 03 (2010-11-19)
NOTE
In certain circumstances, to log in to the WEB LCT, do as follows:
l Click the WEB LCT tab, set User name and Password, and then click Referring to log in to the Web
management interface.
l The initial account and password for logging in to the LCT Web management interface are admin and
Admin@123 respectively.
----End
1.6 Configuration Example of the Outband Management
(Based on the SNMPv3 Protocol)
This topic provides an example for configuring the outband management to manage and maintain
the ONU. In outband management the non-service channel is used to transmit the management
information. With the use of the non-service channel, the management channel and the service
channel are separated, which provides a more reliable management channel for the device
compared with the inband management.
Example Network
After you add a static route to the U2000 on the ONU and set the related SNMP parameters, the
U2000 manages and maintains the ONU in the outband management mode through the ETH
port.
1-21
Figure 1-1 Example network of the outband management

U2000
Router
ONU

Data Plan
Configuring the Data Plan for the Outband Management (U2000 Standalone System)
The IP address of the outband management interface on the ONU side and the IP address of the
gateway must be in the same subnet. When the IP address of the outband management interface
and the IP address of the U2000 are in different subnets, you need to configure the route
information for forwarding the IP packets. The IP address of the destination host for the traps is
the IP address of the U2000.
Table 1-2 Data plan for the outband network management in the standalone mode
Item Data
Outband network management interface on the
ONU
IP address: 10.10.21.2/24
U2000 IP address: 10.10.21.1/24
The IP address of the gateway of the ONU IP address: 10.10.20.254/24
SNMP User name: user1
Issue 03 (2010-11-19)
Item Data
Group name: group1
View user: hardy
Authentication method: MD5
Authentication password: auth12345678
Encryption method: DES
Encryption password: pri12345678
Version: V3

Configuring the Data Plan for the Outband Management (U2000 HA System)
l If the floating IP address allocation scheme is used, the active and standby U2000 servers
use the floating IP address to communicate with the device. That is, the IP address of the
destination host for the traps is the floating IP address. The IP address of the outband
management interface on the ONU side and the IP address of the gateway must be in the
same subnet. When the IP address of the outband management interface and the floating
IP address of the U2000 are in different subnets, you need to configure the route information
for forwarding the IP packets.
l If the floating IP address allocation scheme is not used, the IP addresses used for the
communication between the active and standby servers and the device are different. The
IP address of the outband management interface on the ONU side and the IP address of the
gateway must be in the same subnet. When the IP address of the outband management
interface and the IP addresses of the active and standby U2000 servers are in different
subnets, you need to configure the route information for forwarding the IP packets.
Table 1-3 Data plan for the outband network management in the HA system
Item Data
Outband network management interface on
the ONU
IP address: 10.10.20.2/24
U2000 (adopting the method of allocating
floating IP addresses)
Floating IP address: 10.10.21.1/24
U2000 (not adopting the method of allocating
IP address of the active server: 10.10.21.1/24
IP address of the standby server:
10.10.21.2/24
SNMP User name: user1
Group name: group1
View user: hardy
1-23
Item Data
Authentication method: MD5
Authentication password: auth12345678
Encryption method: DES
Encryption password: pri12345678
Version: V3

Procedure
1 Procedures for configuring the outband network management on the device
Procedures for configuring the outband network management on the device in the standalone
mode
1. Configure the IP address of the maintenance network port.
NOTE
By default, the IP address of the maintenance network port is 10.11.104.2, and the subnet mask is
255.255.255.0.
huawei(config)#interface meth 0
huawei(config-if-meth0)#ip address 10.10.20.2 255.255.255.0
huawei(config-if-meth0)#quit
2. Add a route for the outband network management.
huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254
3. Set the SNMP parameters.
l Set the SNMP user, group, and view.
huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode
md5 auth12345678 privacy-mode des56 pri12345678
huawei(config)#snmp-agent group v3 group1 authentication read-view hardy
write-view hardy
huawei(config)#snmp-agent mib-view hardy include ip
l (Optional) Set the administrator flag and contact.
huawei(config)#snmp-agent sys-info contact HW-075528780808
l (Optional) Set the location information about the device.
huawei(config)#snmp-agent sys-info location Shenzhen_China
l (Optional) Configure the engine ID of the SNMP entity.
huawei(config)#huawei(config)#snmp-agent local-engineid 0123456789
l Set the SNMP version.
NOTE
The SNMP version must be consistent with the SNMP version set on the U2000. The following
example assumes that the SNMP version on the U2000 is SNMP V3.
huawei(config)#snmp-agent sys-info version v3
4. Enable the sending of the trap packet.
Issue 03 (2010-11-19)
huawei(config)#snmp-agent trap enable standard
5. Configure the IP address of the destination device of the trap packet.
huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1
trap-paramsname ABC
huawei(config)#snmp-agent target-host trap-paramsname ABC v3 securityname
user1 privacy
6. Configure the IP address of the maintenance network port as the source IP address of the
trap packet.
huawei(config)#snmp-agent trap source meth 0
7. Save the data.
huawei(config)#save
Procedures for configuring the outband network management on the device in the HA system
l When the HA system adopts the method of allocating floating IP addresses, the procedures
for configuring the outband network management on the device in the HA system is the same
as the procedures for configuring the outband network management on the device in the
standalone mode.
l The following describes how to configure the outband network management on the device
when the HA system does not adopt the method of allocating floating IP addresses.
l Configure the IP address of the maintenance network port.
huawei(config)#interface meth 0
huawei(config-if-meth0)#ip address 10.10.20.2 255.255.255.0
l Add the route for the outband network management.
l Set the SNMP parameters.
Set the SNMP user, group, and view.
huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5
auth12345678 privacy-mode des56 pri12345678
huawei(config)#snmp-agent group v3 group1 authentication read-view hardy
write-view hardy
huawei(config)#snmp-agent mib-view hardy include ip
(Optional) Set the administrator flag and contact.
(Optional) Set the location information about the device.
(Optional) Configure the engine ID of the SNMP entity.
huawei(config)#huawei(config)#snmp-agent local-engineid 0123456789
Set the SNMP version.
NOTE
l Enable the sending of the trap packet.
huawei(config)#snmp-agent trap enable standard
1-25
l Configure the IP address of the destination device of the trap packet.
huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-
paramsname ABC1
huawei(config)#snmp-agent target-host trap-paramsname ABC1 v3 securityname
user1 privacy
huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.2 trap-
paramsname ABC2
user1 privacy
l Configure the IP address of the maintenance network port as the source address of the trap
packet.
huawei(config)#snmp-agent trap source meth 0
l Save the data.
huawei(config)#save
2 Procedure for configuring the outband management on the U2000 side
The MDU that supports GE upstream transmission supports the SNMPv3 protocol.
1. Choose Administration > NE Communicate Parameter > NE Access Protocol
Parameters from the main menu.
2. On the tab page, click Reset. In the dialog box that is displayed, click the SNMPv1
Parameters tab and then click Add.
3. In the dialog box that is displayed, set the name and SNMP parameters as follows:
NOTE
The SNMPv3 protocol supports three security levels: authentication, noauth, and privacy. To
implement successful communication through the SNMPv3 protocol, ensure that the authentication
and encryption modes of the SNMP user on the device, SNMP group, and the SNMP parameters on
the U2000 are the same.
4. Click OK.
Issue 03 (2010-11-19)
5. Select the added SNMP parameters. Click OK.
6. In the dialog box that is displayed, click Yes. Test the set SNMP parameters.
7. The U2000 displays the Loading dialog box. After the testing is complete, click OK.
8. In the physical root view page, right-click and then choose New > NE.
10. Click OK.
----End
Result
The U2000 can manage and maintain the ONU normally.
1.7 Configuration Example of the Inband Management
This topic provides an example for configuring the inband management to manage and maintain
the ONU. The inband management transmits the management information through the service
channel of the device. The inband management features the flexible networking without any
adjunct device and low cost, but it is difficult to maintain.
Example Network
After you add a static route to the U2000 on the ONU and set the related SNMP parameters, the
U2000 manages and maintains the ONU in the inband management through the upstream port.
NOTE
The procedure for configuring inband management by means of the SNMPv1 protocol is similar to that by
means of the SNMPv2c protocol. This topic considers the SNMPv1 protocol as an example.
1-27
Figure 1-2 Example network of the inband management
U2000
Router
ONU

Data Plan
Configuring the Data Plan for the Inband Management (U2000 Standalone System)
The IP address of the inband management interface on the ONU side and the IP address of the
gateway must be in the same subnet. When the IP address of the inband management interface
and the IP address of the U2000 are in different subnets, you need to configure the route
information for forwarding the IP packets. The IP address of the destination host for the traps is
the IP address of the U2000.
Issue 03 (2010-11-19)
Table 1-4 Data plan for the inband network management in the standalone mode
Item Data
ONU l SNMP Profile: snmpprofile
l Line Profile: lineprofile
l Service Profile: serviceprofile
l ONU Capacity Profile: ontprofile
l Affiliated Port: 0/2/0
l Name: 0/2/0
l ONU ID: 1
l Splitter Port ID: 1
l Auth Way: SN
l Key: 0123456789ABCDEF
l Manager VLAN: 100
l IP Address: 10.10.20.2
l IP Address Mask: 255.255.0.0
Inband network management interface on the
ONU
IP address: 10.10.21.2/24
U2000 IP address: 10.10.21.1/24
Get Community public
Set Community private
SNMP Version V1

Configuring the Data Plan for the Inband Management (U2000 HA System)
l If the floating IP address allocation scheme is used, the active and standby U2000 servers
use the floating IP address to communicate with the device. That is, the IP address of the
destination host for the traps is the floating IP address. The IP address of the inband
management interface on the ONU side and the IP address of the gateway must be in the
same subnet. When the IP address of the inband management interface and the floating IP
address of the U2000 are in different subnets, you need to configure the route information
for forwarding the IP packets.
l If the floating IP address allocation scheme is not used, the IP addresses used for the
communication between the active and standby servers and the device are different. The
IP address of the inband management interface on the ONU side and the IP address of the
gateway must be in the same subnet. When the IP address of the inband management
interface and the IP addresses of the active and standby U2000 servers are in different
subnets, you need to configure the route information for forwarding the IP packets.
1-29
Table 1-5 Data plan for the inband network management in the HA system
Item Data
ONU l SNMP Profile: snmpprofile
l Line Profile: lineprofile
l Service Profile: serviceprofile
l ONU Capacity Profile: ontprofile
l Affiliated Port: 0/2/0
l Name: 0/2/0
l ONU ID: 1
l Splitter Port ID: 1
l Auth Way: SN
l Key: 0123456789ABCDEF
l Manager VLAN: 100
l IP Address Mask: 255.255.0.0
Inband network management interface on the
ONU
IP address: 10.10.20.2/24
U2000 (adopting the method of allocating
Floating IP address: 10.10.21.1/24
U2000 (not adopting the method of allocating
IP address of the active server: 10.10.21.1/24
IP address of the standby server:
10.10.21.2/24
Get Community public
Set Community private
SNMP Version V1

Procedure
1 Procedures for configuring the inband network management on the device
Procedures for configuring the inband network management on the device in the standalone
mode
The SNMP parameters must be consistent with the SNMP parameters on the U2000. Configure
the parameters according to the actual requirements.
1. Configure the IP address of the inband network management port.
NOTE
If the packet transmitted from the upstream port is untagged, run the native-vlan command to
configure the native VLAN of the upstream port to be the same as the VLAN of the upstream port.
Issue 03 (2010-11-19)
a. Create the network management VLAN.
huawei(config)#vlan 1000 standard
b. Add the upstream ports.
huawei(config)#port vlan 1000 0/0 0
c. Enter the U2000 VLAN interface.
huawei(config)#interface vlanif 1000
d. Configure the IP address of the U2000 VLAN interface.
huawei(config-if-Vlanif1000)#ip address 10.10.20.2 255.255.255.0
huawei(config-if-vlanif1000)#quit
2. Add a route for the inband network management.
l Set the community name and access rights.
huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
NOTE
huawei(config)#snmp-agent trap enable
trap-paramsname ABC
huawei(config)#snmp-agent target-host trap-paramsname ABC v1 securityname
private
6. Set the source IP address of the trap packet.
huawei(config)#snmp-agent trap source vlanif 1000
7. Save the data.
huawei(config)#save
Procedures for configuring the inband network management on the device in the HA system
l When the HA system adopts the method of allocating floating IP addresses, the procedures
for configuring the inband network management on the device is the same as the procedure
for configuring the inband network management on the device in the standalone mode.
l The following describes how to configure the inband network management on the device
when the HA system does not adopt the method of allocating floating IP addresses.
1-31
1. Configure the IP address of the inband network management port.
NOTE
If the packet transmitted from the upstream port is untagged, run the native-vlan command to
configure the native VLAN of the upstream port to be the same as the VLAN of the upstream port.
a. Create the network management VLAN.
huawei(config)#vlan 1000 standard
b. Add the upstream ports.
huawei(config)#port vlan 1000 0/0 0
c. Enter the U2000 VLAN interface.
huawei(config)#interface vlanif 1000
d. Configure the IP address of the U2000 VLAN interface.
huawei(config-if-Vlanif1000)#ip address 10.10.20.2 255.255.255.0
huawei(config-if-vlanif1000)#quit
2. Add a route for the inband network management.
l Set the community name and access rights.
huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
NOTE
huawei(config)#snmp-agent trap enable
trap-paramsname ABC1
private
trap-paramsname ABC2
private
6. Set the source IP address of the trap packet.
huawei(config)#snmp-agent trap source vlanif 1000
7. Save the data.
Issue 03 (2010-11-19)
huawei(config)#save
2 Procedure for configuring the inband management on the U2000 side
The MDU that supports GPON upstream transmission is considered as an example.
1. Configuring an MDU SNMP Profile
a. Choose Configuration > Access Profile Management > MDU SNMP Profile from
the main menu.
b. Right-click and choose Add Global Profile from the shortcut menu.
c. In the dialog box that is displayed, set the parameters.
d. Click OK.
e. In the information list, right-click the record and choose Download to NE from the
shortcut menu.
f. In the dialog box that is displayed, select the required NE(s), and click OK.
2. Configuring a GPON Line Profile
a. Choose Configuration > Access Profile Management > GPON Profile from the
main menu.
b. Click the GPON Line Profile tab. Right-click and choose Add Global Profile from
the shortcut menu.
1) Choose Basic Info from the navigation tree, and then set the basic parameters of
the profile.
1-33
2) Choose T-CONT Info. from the navigation tree, right-click, and then choose
ADD T-CONT from the shortcut menu. In the dialog box that is displayed, set
T-CONT Index and DBA Profile.
CAUTION
It is recommended that you do not set T-CONT Index to 0. TCONT 0 is reserved
for the internal communication of the GPON protocol.
3) Choose T-CONTx from the navigation tree, right-click, and then choose ADD
GEM Port from the shortcut menu. In the dialog box that is displayed, set GEM
Port Index.
Issue 03 (2010-11-19)
NOTE
x indicates the T-CONT index.
4) Choose GEM Portx from the navigation tree, right-click, and then choose ADD
GEM Connection from the shortcut menu. In the dialog box that is displayed,
set the basic parameters of the GEM connection.
NOTE
x indicates the GEM port index.
d. Click OK.
e. In the information list, right-click the record and choose Download to NE from the
shortcut menu.
f. In the dialog box that is displayed, select the required NE(s), and click OK.
3. Adding the MDU That Supports GPON Upstream Transmission
a. On the topological navigation tree, select the required ODN under the OLT node.
Select the splitter under the ODN, right-click, and then choose New > ONU; or select
1-35
the splitter under the ODN, right-click the blank area on the Physical Root interface
on the right side, and then choose New > ONU.
b. On the interface that is displayed, set the parameters on the Basic Parameters and
Network Management Channel Parameters tab pages (on this interface, the ONU
that supports the GPON upstream mode is considered as an example).
Issue 03 (2010-11-19)
NOTE
l When the OLT works in the profile mode, the ONU that supports the EPON upstream mode
needs to be bound with the EPON line profile and the EPON service profile.
l When the OLT works in the profile mode, the ONU that supports the GPON upstream mode
needs to be bound with the GPON line profile and the GPON service profile.
l When the OLT works in the distributed mode, the ONU that supports the GPON upstream mode
needs to be bound with the ONU capacity profile.
l When the OLT sets network management channel parameters check box is cleared, ONUs
are configured and managed remotely on the OLT through the OMCI protocol.
l When the OLT sets network management channel parameters check box is selected, ONUs
are configured and managed remotely on the OLT through the SNMP protocol.
l Do not add the SNMP parameters on the ONU through the serial port, but issue the SNMP profile
from the OLT to the ONU only.
c. Click OK.
d. In the Main Topology, double-click the required OLT in the Physical Root navigation
e. Choose VLAN from the navigation tree.
f. On the VLAN tab page, right-click and choose Add from the shortcut menu.
g. In the dialog box that is displayed, set the parameters.
l VLAN ID: 4000
l Type: Smart VLAN
h. Click Next.
1-37
l Click the Upstream Port tab and add upstream port 0/19/0 as the upstream port
of the VLAN.
l Click the L3 Interface tab and set the parameters.
IP Address: 192.168.50.4
i. Click Finish.
j. Choose GPON > GPON ONU from the navigation tree.
k. On the GPON ONU tab page, set the filter criteria to display the required GPON
ONUs.
l. In the information list, select the record where the shelf, slot, port, and ONU IDs are
0, 2, 1, and 0 respectively and click the ServicePort Info tab in the lower pane.
m. On the ServicePort Info tab page, right-click and choose Add from the shortcut menu.
n. In the dialog box that is displayed, set the parameters.
l Connection Type: LAN-GPON
l VLAN ID: 4000
l Interface Selection: 0/2/1/0/0
l Service Type: Multi-Service VLAN
l User VLAN: 4000
l Keep the upstream and downstream settings the same: selected
l Upstream Traffic Name: ip-traffic-table_6 (it is recommended that you use the
default profile ip-traffic-table_6 because the OLT does not limit the rates of service
streams in the management VLAN)
o. Click OK.
----End
Result
After the parameters on the element management system (EMS) are configured successfully,
the U2000 can manage and maintain the ONU normally.
Issue 03 (2010-11-19)
2 Configuring the VLAN Stacking Wholesale
Service
About This Chapter
The VLAN stacking is a service by which the subscribers can access their corresponding ISP
service in batches based on some rules.
Context
The wholesale service allows the subscribers to access their own ISP service in batches based
on some rules when the L2 metropolitan area network has many ISPs.
The Stacking VLAN packets contain the inner and outer VLAN tags allocated by the ONU. The
packets can be applied to the upper BRAS for performing the dual VLAN authentication and
adding to the number of access subscribers.
2.1 Introduction to the VLAN Stacking Wholesale Service
VLAN stacking refers to the stacking of the 802.1Q tags. It allows the device to add two 802.1Q
VLAN tags to an untagged user packet or change a tagged user packet into a packet with two
802.1Q VLAN tags. The packet with two VLAN tags can then be transmitted over the backbone
network of the service provider. When the packet reaches the BRAS, the BRAS authenticates
the packet based on the two VLAN tags, or removes the outer VLAN tag and identifies the user
by the inner VLAN tag.
2.2 Configuring the VLAN Stacking Wholesale Service
This topic describes how to configure the VLAN stacking wholesale service on the ONU in the
FTTx networking scenario.
2.3 Application Example: Configuring the VLAN Stacking Wholesale Service
Based on the example network, this topic describes how to configure the VLAN Stacking
Wholesale Service.
Operation Guide for ONU NE Management 2 Configuring the VLAN Stacking Wholesale Service
2-1
2.1 Introduction to the VLAN Stacking Wholesale Service
VLAN stacking refers to the stacking of the 802.1Q tags. It allows the device to add two 802.1Q
VLAN tags to an untagged user packet or change a tagged user packet into a packet with two
802.1Q VLAN tags. The packet with two VLAN tags can then be transmitted over the backbone
network of the service provider. When the packet reaches the BRAS, the BRAS authenticates
the packet based on the two VLAN tags, or removes the outer VLAN tag and identifies the user
by the inner VLAN tag.
Background
The VLAN stacking feature allows the ONU to add an inner 802.1Q VLAN tag and an outer
802.1Q VLAN tag to an access user packet. The packet with two VLAN tags is transmitted to
the layer-2 switching network, and forwarded to the ISP network according to the outer VLAN
tag.
Wholesale service: In a layer-2 metropolitan area network, there may exist multiple Internet
service providers (ISPs). The services of these ISPs need to be delivered to their respective users
quickly. Therefore, the outer VALN tag is used to identify the ISP and the inner VLAN tag is
used to identify the user. In this way, different user groups with different outer VLAN tags can
access the specified ISP networks and obtain the services provided by the ISPs.
2.2 Configuring the VLAN Stacking Wholesale Service
This topic describes how to configure the VLAN stacking wholesale service on the ONU in the
Context
Figure 2-1 shows the flowchart for configuring the VLAN Stacking Wholesale Service.
2 Configuring the VLAN Stacking Wholesale Service
Issue 03 (2010-11-19)
Figure 2-1 Flowchart for configuring the VLAN Stacking Wholesale Service
End
Configure the traffic profile
Configure the VLAN
Start
Configure the service virtual port
Save the data
Configure an upstream port for
the VLAN
Configure the VLAN service
profile

2.3 Application Example: Configuring the VLAN Stacking
Wholesale Service
Based on the example network, this topic describes how to configure the VLAN Stacking
Wholesale Service.
Prerequisite
The devices are connected according to the example network as shown in the figure Figure
2-2 and the devices work in the normal state.
2-3
Context
Figure 2-2 shows an example network of the VLAN Stacking Wholesale Service.
Figure 2-2 Example network of the VLAN Stacking Wholesale Service
MA5610
BRAS
1 2 3 4
VLAN ID:20 VLAN ID:21
ISP1
BRAS
ISP2
0/0/1
Optical Splitter
OLT

Users 1 and 2 belong to one ISP, and users 3 and 4 belong to another ISP. Based on the VLAN
stacking feature, the ONU adds the outer VLAN tag to differentiate ISPs and inner VLAN tag
to differentiate users and forwards the user packet to the L2 network. Then the switch at the L2
forwards the user packets to the specified ISP BRAS based on the outer VLAN tag. The BRASs
Issue 03 (2010-11-19)
of the user's ISP remove the outer VLAN tag and identify the users based on the inner VLAN
tag. After passing the authentication, the users can obtain various services provided by the ISP.
Data Plan
Table 2-1 provides the data plan for configuring the VLAN Stacking Wholesale Service.
Table 2-1 Data plan for configuring the VLAN Stacking Wholesale Service
Item Data Data
Upstream port 0/0/1
ISP1 user group Upstream VLAN ID (outer VLAN tag): 20
VLAN type: Smart VLAN
VLAN attribute: Stacking VLAN
User 1:
l Inner VLAN tag: 11
User 2:
ISP2 user group Upstream VLAN ID (outer VLAN tag): 21
VLAN attribute: Stacking VLAN
User 3:
User 4:

Procedure
1 Configuring the VLAN Service Profile.
1. Choose Configuration > Access Profile Management > VLAN Service Profile from the
main menu.
2. Right-click and choose Add Global Profile from the shortcut menu.
l Name: Vservice_profile
l Forwarding Mode: vlan-mac
4. Click OK.
5. Select the VLAN Service Profile, right-click, and then choose Download to NE.
6. In the dialog box that is displayed, select the required MDU, and then click OK.
2 Configure the MEF IP traffic profile.
2-5
1. Choose Configuration > Access Profile Management > Traffic Profile from the main
menu.
2. Click the MEF IP Traffic Profile tab. Right-click and choose Add Global Profile from
the shortcut menu.
3. In the dialog box that is displayed, set the MEF IP traffic profile parameters Name to
ip_profile and CIR to 3072kbit/s.
4. Click OK.
5. Select the MEF IP traffic profile, right-click, and then choose Download to NE.
3 Adding a VLAN and configuring an Upstream Port.
1. In the Main Topology, double-click the required ONU in the Physical Root navigation
tree; or right-click the required ONU and choose NE Explorer from the shortcut menu.
2. Choose VLAN from the navigation tree. On the VLAN tab page, set the filter criteria or
click to display the VLANs.
3. Right-click the list, and then choose Batch Add.
4. In the dialog box that is displayed, select Base Info., set the parameters.
l Start VLAN ID: 20.
l End VLAN ID: 21.
l Type: Smart VLAN.
l Attribute: Stacking.
5. Click Next, configure an Upstream Port, set 0/0/1 as the upstream port of the VLAN.
6. Click Done.
4 Configure a service virtual port.
2. Choose Connection > Service Port from the navigation tree.
3. On the Service Port tab page, set the filter criteria to display the required service virtual
ports. Right-click the list, and then choose Add.
l In the Attribute field, set Port Type to ETHER and Service Type to Muti-Service
VLAN.
l In the Network Side field, set VLAN Choice to Stacking VLAN, Outer VLAN ID
to 20, and Inner VLAN ID to 11.
l In the User Side field, set Interface Selection to 0/2/0 and User VLAN to 11.
l Click OK.
5. Configure the service virtual ports for users 2, 3, and 4 according to the data plan.
5 Save the data.
1. On the tab page that is displayed, choose NE Properties > Auto Save Configuration from
the navigation tree.
2. In the right pane, set Save Type to All, select the Enable Auto Save check box, and then
select Absolute Period or Relative Period.
Issue 03 (2010-11-19)
3. Click Apply.
----End
2-7
3 Configuring the QinQ VLAN Private Line
Service
About This Chapter
QinQ VLAN is used in the private line services of enterprise private networks to provide safe
channels for the data transmission between the enterprise private networks.
Context
The private line service allows the private network services to be transparently transmitted to
the peer end, for example, on an intranet.
To communicate with each other, users that are on the same private network but at different
locations are connected to the public network through the ONU respectively. On the ONU,
configure the upstream VLAN for user packets from the private network to have the QinQ
attribute. In this way, the packet has two VLAN tags: an inner VLAN tag from the private
network and an outer VLAN tag from the public network. Through the outer VLAN tag, the
packet is transparently transmitted to the peer private network user. In this way, private network
users can communicate with each other.
3.1 Introduction to the QinQ VLAN Private Line Service
QinQ VLAN is a tunnel protocol based on the 802.1Q encapsulation. QinQ VLAN adds an
802.1Q tag to a VLAN packet that already has an 802.1Q tag from the private network so that
this VLAN packet can be transparently transmitted from the private network to the layer-2 VPN
through the public network.
3.2 Configuring the QinQ VLAN Leased Line Service
This topic describes how to configure the QinQ VLAN Leased Line Service on the ONU in the
3.3 Application Example: Configuration the QinQ VLAN Leased Line Service
Based on the example network, this topic describes how to configure the QinQ VLAN Leased
Line Service.
Operation Guide for ONU NE Management 3 Configuring the QinQ VLAN Private Line Service
3-1
3.1 Introduction to the QinQ VLAN Private Line Service
QinQ VLAN is a tunnel protocol based on the 802.1Q encapsulation. QinQ VLAN adds an
802.1Q tag to a VLAN packet that already has an 802.1Q tag from the private network so that
this VLAN packet can be transparently transmitted from the private network to the layer-2 VPN
through the public network.
Background
The ONU receives a packet with a private VLAN tag and uses the QinQ (802.1Q in 802.1Q)
feature to add a public VLAN tag (that is, the QinQ VLAN tag) to the packet. The packet with
the private VLAN tag is forwarded to the peer ONU over the public network according to its
outer public VLAN tag. The peer ONU removes the outer VLAN tag and transmits the packet
to the peer private network.
The ONU also supports the transparent transmission of BPDU packets from a private network
to its peer private network by using the QinQ VLAN private line service.
3.2 Configuring the QinQ VLAN Leased Line Service
This topic describes how to configure the QinQ VLAN Leased Line Service on the ONU in the
Context
Figure 3-1 shows the flowchart for configuring the QinQ VLAN Leased Line Service.
3 Configuring the QinQ VLAN Private Line Service
Issue 03 (2010-11-19)
Figure 3-1 Flowchart for configuring the QinQ VLAN Leased Line Service
Start
Add a Vlan Service Profile
Add a MEF IP traffic profile
Add a VLAN
Enable BPDU transparent
transmission(option)
Configure the service virtual port
Save the data
End
Configure an upstream port for
the VLAN

3.3 Application Example: Configuration the QinQ VLAN
Leased Line Service
Based on the example network, this topic describes how to configure the QinQ VLAN Leased
Line Service.
3-3
Prerequisite
The devices are connected according to the example network as shown in the figure Figure
3-2 and the devices work in the normal state.
Context
Figure 3-2 shows an example network of the QinQ VLAN Leased Line Service.
Figure 3-2 Example network of the QinQ VLAN Leased Line Service
L2/L3
Company A
LSW
LSW
L2/L3
MA5610_A
0/0/1
0/0/1
Optical Splitter
Optical Splitter
OLT OLT
MA5610_B
Company B

Two offices of the enterprise are connected to the metropolitan area network (MAN) through
ONU_A and ONU_B respectively. After the QinQ VLAN private line service is configured on
the ONU, the services can be transparently transmitted between the two offices within the
enterprise private network over the public network.
Data Plan
Table 3-1 provides the data plan for configuring the QinQ VLAN Leased Line Service.
Issue 03 (2010-11-19)
Table 3-1 Data plan for configuring the QinQ VLAN Leased Line Service
Item Data Data
ONU_A Upstream port: 0/0/1
Upstream VLAN ID: 10
VLAN attribute: QinQ
BPDU transparent transmission: enabled
Traffic profile: ip_profile, with the permitted access rate of
3072kbit/s
ONU_B The same as the data plan ofONU_A

Procedure
1 Configuring the VLAN Service Profile.
1. Choose Configuration > Access Profile Management > VLAN Service Profile from the
main menu.
3. In the dialog box that is displayed, set the Name of the VLAN Service Profile as
Vservice_profile, and then select Enable for the BPDU Tunnel.
4. Click OK.
5. Select the VLAN Service Profile, right-click, and then choose Download to NE.
2 Configure the MEF IP traffic profile.
1. Choose Configuration > Access Profile Management > Traffic Profile from the main
menu.
2. Click the MEF IP Traffic Profile tab. Right-click and choose Add Global Profile from
the shortcut menu.
3. In the dialog box that is displayed, set the MEF IP traffic profile parameters Name to
ip_profile and CIR to 3072kbit/s.
4. Click OK.
5. Select the MEF IP traffic profile, right-click, and then choose Download to NE.
3 Adding a VLAN and configuring an Upstream Port.
2. Choose VLAN from the navigation tree. On the VLAN tab page, set the filter criteria or
click to display the VLANs.
3. Right-click the list, and then choose Add.
4. In the dialog box that is displayed, select Base Info., set the parameters.
3-5
l VLANID: 10.
l Type: Smart VLAN.
l Attribute: QinQ.
5. Click Next, configure an Upstream Port, set 0/0/1 as the upstream port of the VLAN.
6. Click Done.
4 Configure a service virtual port.
ports. Right-click the list, and then choose Add.
l In the Attribute field, set Port Type to ETHER and Service Type to Muti-Service
VLAN.
l In the Network Side field, set VLAN Choice to Smart VLAN and VLAN ID to 10.
l In the User Side field, set Interface Selection to 0/2/0.
l Click OK.
5. Click OK.
5 Save the data.
1. On the tab page that is displayed, choose NE Properties > Auto Save Configuration from
the navigation tree.
2. In the right pane, set Save Type to All, select the Enable Auto Save check box, and then
select Absolute Period or Relative Period.
3. Click Apply.
----End
Issue 03 (2010-11-19)
4 Configuring the Dual GE Link Aggregation
Upstream Transmission
This topic describes how to configure the dual GE link aggregation upstream transmission. The
ONU supports the networking application of the dual GE link aggregation upstream transmission
and provides services for community users as a Mini DSLAM device. Port aggregation means
that two GE upstream ports of the ONU are aggregated to increase the bandwidth and balance
the input and output load between member ports. Currently, the MA5616 supports the dual
GE link aggregation upstream transmission.
Example Network
Figure 4-1 shows an example network of the dual GE link aggregation upstream transmission.
The PC is connected to the Ethernet access port of the ONU. The user packets are sent to the
ONU through the port and then sent upstream to the upper-layer network through the upstream
GE port on the control card of the device.
Figure 4-1 Example network of the dual GE link aggregation upstream transmission

Data Plan
Table 4-1 describes the data plan for the dual GE link aggregation upstream transmission.
4 Configuring the Dual GE Link Aggregation Upstream
Transmission
4-1
Table 4-1 Data plan for the dual GE link aggregation upstream transmission
Item Data Remarks
Traffic
profile
The default value: ip-traffic-table_3 The committed access rate (CAR),
priority, and priority policy are
configured in traffic profiles.
Therefore, when adding a service
virtual port, you can specify the CAR,
priority and priority policy by
choosing a specific traffic profile.
Service port 0/1/0 -
Upstream
port
0/0/0 and 0/0/1 The two Ethernet ports to be
aggregated.
Requirement
s for the
upper-layer
device
LAN Switch:
l The LAN switch transparently
transmits the service packets of an
MDU at Layer 2.
l A VLAN must be configured for
the service access of the MDU.
The VLAN ID must be the same
as that of the upstream VLAN of
the MDU.
For the configuration of the LAN
switch and the BRAS, see the related
configuration guides.
BRAS: Configure the BRAS
according to the authentication and
accounting requirements of users. For
example, configure the access user
domain (including the authentication
scheme, accounting scheme, and
authorization scheme that are bound
to the domain) and specify the
RADIUS server.

Procedure
1 Configure the Ethernet port aggregation.
NOTE
To perform the following operations in the navigation tree, you need to navigate to the NE Explorer of the
ONU. To navigate to the NE Explorer of the ONU, do as follows: In the Main Topology, double-click the
required ONU in the Physical Root navigation tree; or right-click the required ONU and choose NE
Explorer from the shortcut menu.
1. Choose ETH from the navigation tree.
2. Click the Aggregation Group tab, and set the filter criteria or click to display the
aggregation groups.
3. In the information list, right-click and choose Add from the shortcut menu.
Transmission
Issue 03 (2010-11-19)
5. Click OK.
2 Add a VLAN and configure an upstream port for the VLAN.
4. Click Next to configure the upstream port for the VLAN.
Transmission
4-3
5. Click Done.
3 Add a service virtual port.
ports.
5. Click OK.
----End
Transmission
Issue 03 (2010-11-19)
Result
The PC can still access the Internet through PPPoE dialup after you deactivate port 0/0/0 or
0/0/1.
Transmission
4-5
5 Configuring the VoIP ISDN BRA Service (H.
248 Protocol)
This topic describes how to configure the VoIP ISDN BRA service based on the H.248 protocol
for the ONU. Then, the service is sent upstream to the IP network through the control card. In
this way, the ISDN BRA service is configured successfully. Currently, the MA5616 supports
the ISDN BRA service.
Example Network
Figure 5-1 shows an example network of the VoIP ISDN BRA service.
Figure 5-1 Example network of the VoIP ISDN BRA service

Operation Guide for ONU NE Management 5 Configuring the VoIP ISDN BRA Service (H.248 Protocol)
5-1
Data Plan
Table 5-1 describes the data plan for the VoIP ISDN BRA service.
Table 5-1 Data plan for the VoIP ISDN BRA service
Item Data
Parameters of
the media
stream and
signaling
stream
IP address and mask of
the VLAN L3 interface
10.13.4.116/16
IP address of the media
stream and signaling
stream
10.13.4.116
Upstream interface of the
media stream and
signaling stream
0/0/0
Upstream VLAN of the
media stream and
signaling stream
VLAN ID: 10
Default media gateway
(MG) of the MG interface
10.13.1.1
TID profile Index of the TID profile
used by the ISDN BRA
user
2 (default, no configuration is required)
Prefix of the TID
terminal used by the
ISDN BRA user
A (default, no configuration is required)
Static route
from the MG to
the MGC
IP address of the
destination network
segment
10.14.0.0
IP address of the gateway 10.13.1.1
Attribute
parameters of
the MG
interface
MG interface ID 0
Encoding mode of the
MG interface
text
Protocol supported by the
MG interface
H.248
Signaling port ID of the
MG interface
2944
Media/Signaling IP
address of the MG
interface
10.13.4.116
Default MG of the MG
interface
10.13.1.1
5 Configuring the VoIP ISDN BRA Service (H.248 Protocol)
Issue 03 (2010-11-19)
Item Data
IP address of the primary
MGC to which the MG
interface belongs
10.14.1.2
Port ID of the primary
MGC to which the MG
interface belongs
2944
Transmission mode of
the MG interface
UDP
Start negotiation version
of the H.248 protocol of
the MG interface
2
domainname mdu.com

Association Association ID 0
Local port 1401
Local IP address 10.13.4.116/16
Remote port ID 1400
IP address of the primary
MGC at the remote end
10.14.1.2/16
BRA user data ISDN phone1 and ISDN
phone2
l Shelf/slot/port ID of the BRA user: 0/1/0
l Phone number: 83110001
l Working mode: point to multi-point
l Terminal ID: 2
l IUA interface ID: 0
l Priority of the user: Cat3 (default)
ISDN phone3 l Shelf/slot/port ID of the BRA user: 0/1/1
l Phone number: 83110002
l Working mode: point to point
l Terminal ID: 4
l IUA interface ID: 2
l Priority of the user: Cat1
NOTE
In the point to point mode, the terminal endpoint
identifier (TEI) of the ISDN BRA digital phone is
always 0.

5-3
Procedure
1 Add a VLAN and configure its upstream port, L3 interface, media IP address, and
signaling IP address.
NOTE
To perform the following operations in the navigation tree, you need to navigate to the NE Explorer of the
ONU. To navigate to the NE Explorer of the ONU, do as follows: In the Main Topology, double-click the
required ONU in the Physical Root navigation tree; or right-click the required ONU and choose NE
Explorer from the shortcut menu.
4. Click Next to configure the upstream port and L3 interface of the VLAN.
Issue 03 (2010-11-19)
5. Click Done.
6. In the VLAN list, select the newly added VLAN and click the IP Interface tab in the lower
pane.
8. In the dialog box that is displayed, configure the media IP address and signaling IP address.
2 Configure a static route.
1. Choose Static Route from the navigation tree.
5-5
4. Click OK.
3 Configure the MG.
1. Choose Voice Gateway > Media Gateway from the navigation tree.
2. On the Media Gateway tab page, set the filter criteria to display the required MGs.
5. Click OK.
6. In the MG list, select a record and click the MGC Attribute Info tab in the lower pane. In
the window that is displayed, right-click the record where MGC Index is set to 0 and choose
Modify from the shortcut menu.
Issue 03 (2010-11-19)
Click next to NMS MGC Profile. In the dialog box that is displayed, add an MGC
profile.
7. In the MG list, right-click a record and choose Cold Start from the shortcut menu.
8. In the confirmation dialog box, click Yes.
4 Configure a signaling gateway and an association.
1. Choose Voice Gateway > Signaling Gateway from the navigation tree.
2. On the Signaling Gateway tab page, set the filter criteria to display the required SGs.
5-7
5. Click OK.
6. On the Association tab page, set the filter criteria to display the required associations.
8. In the dialog box that is displayed, set parameters of the association.
Click next to NMS MGC Profile. In the dialog box that is displayed, add an MGC
profile.
Issue 03 (2010-11-19)
9. Click OK.
5 Configure the attributes of the VoIP ISDN BRA port.
1. Choose DSL > ISDN(BRA) Port from the navigation tree.
2. In the VoIP ISDN BRA port list, right-click a record and choose Configure Attribute from
the shortcut menu.
5-9
4. Click OK.
----End
Result
ISDN phone1 and ISDN phone2 can communicate with ISDN phone3 by dialing number
83110002.
When ISDN phone3 dials number 83110001, ISDN phone1 and ISDN phone2 can hear the
ringing tone. In addition, ISDN phone1 and ISDN phone2 can communicate with ISDN phone3
at the same time.
Issue 03 (2010-11-19)
6 Configuring the PHS Service
This topic describes how to configure the PHS service. The ONU connects to base stations of
the personal handyphone system (PHS) and transmits received signals to the UA5000
transparently. Then the UA5000 transmits the signals to the cell site controller (CSC) for
processing. In this way, the ONU carries and transmits the PHS service successfully. Currently,
the MA5616 supports the PHS service.
Example Network
Figure 6-1 shows an example network of the PHS service.
Figure 6-1 Example network of the PHS service

Data Plan
Table 6-1 describes the data plan for the PHS service on the OLT.
Table 6-2 describes the data plan for the PHS service on the UA5000.
Table 6-3 describes the data plan for the PHS service on the MA5616.
Operation Guide for ONU NE Management 6 Configuring the PHS Service
6-1
Table 6-1 Data plan for the PHS service on the OLT
Item Data
Clock VLAN 11
Service VLAN 10
IP address of the L3 interface 10.13.4.100/24
PON access port 0/4/0
GE access port 0/20/0

Table 6-2 Data plan for the PHS service on the UA5000 (on the convergence side)
Item Data
NE configuration
Service IP address 10.13.4.101/24
Upstream port 0/2/1 (GE port)
Association configuration
Association ID 0
Local port ID 11000
Local IP address 10.13.4.101
Remote port ID 12000
Remote IP address 10.13.4.116
SPC configuration
Shelf/slot/port/timeslot of the DSLD card 0/6/0/0
0/6/1/0
0/6/2/0
0/6/3/0
Local port ID 16400, 16408, 16416, and 16424
Remote port ID 57600, 57608, 57616, and 57624
Type of the SPC starting port MNT
Encoding type of the DSP channel 5
RTP (UDP) packetization interval of the DSP
channel
10 ms
Issue 03 (2010-11-19)
Item Data
Clock configuration
Clock VLAN 11
IP address of the L3 interface of the clock
VLAN
20.20.20.10/24
Remote IP address of the L3 interface for
receiving clock packets
20.20.20.20/24

Table 6-3 Data plan for the PHS service on the MA5616
Item Data
NE configuration
Service VLAN 10
IP address of the L3 interface 10.13.4.102/24
Upstream port 0/0/1 (PON port)
Association configuration
Association ID 0
Local port ID 12000
Remote port ID 11000
SPC configuration
Shelf/slot/port/timeslot of the DSLD card 0/2/0/0
0/2/1/0
0/2/2/0
0/2/3/0
Remote port ID 16400, 16408, 16416, and 16424
Local port ID 57600, 57608, 57616, and 57624
Type of the SPC starting port MLT
Encoding/Decoding type of a DSP clearmode coding mode
Clock configuration
6-3
Clock VLAN 11
Card where the adaptive clock source is
located
0/2
IP address of the L3 interface for receiving
ACM clock packets
20.20.20.20/24
Remote IP address of the L3 interface for
sending clock packets
20.20.20.10/24

Procedure
l Configure the PHS service on the OLT side.
NOTE
In addition to forwarding services, the OLT also forwards clock packets from the UA5000 to the
ONU.
To perform the following operations in the navigation tree, you need to navigate to the NE Explorer
of the OLT as follows: In the Main Topology, double-click the required OLT in the Physical Root
navigation tree; or right-click the required OLT and choose NE Explorer from the shortcut menu.
1. Configure the ONU data on the OLT side.
(1) Add a PHS service VLAN and clock VLAN.
a. Choose VLAN from the navigation tree.
b. Right-click the list, and then choose Batch Add from the shortcut menu.
d. Click Done.
e. In the information list, right-click VLAN 10 and choose Configure from
the shortcut menu. In the dialog box that is displayed, set the IP address of
the L3 interface to 10.13.4.100.
f. Click Done.
(2) Add a service virtual port.
NOTE
Service virtual ports are required for both the service VLAN and the clock VLAN.
Issue 03 (2010-11-19)
a. Choose Connection > Service Port from the navigation tree.
b. On the Service Port tab page, set the filter criteria to display the required
service virtual ports.
c. In the information list, right-click and choose Add from the shortcut menu.
d. In the dialog box that is displayed, set the parameters.
e. Click OK.
2. Configure the UA5000 data on the OLT side.
(1) Configure the attributes of an Ethernet port.
NOTE
You need to disable the unicast suppression function of the upstream Ethernet port and
set the service VLAN as the default VLAN of the upstream Ethernet port, because clock
packets are unidirectionally transmitted from the UA5000 to the ONU. If the VLAN ID
of the upstream Ethernet port is the same as the default VLAN ID, the packets of the
upstream Ethernet port do not contain VLAN tags. Specifically, the packets are untagged.
a. Choose ETH from the navigation tree.
b. Click the Ethernet Port tab, and set the filter criteria or click to display
the Ethernet ports.
c. In the Ethernet port list, right-click the port 0/20/0 and choose Configure
Attributes from the shortcut menu.
6-5
e. Click OK.
(2) Configure an upstream port for the clock VLAN.
NOTE
To transmit user packets tagged with clock VLAN IDs upstream through an Ethernet
port, you need to add the Ethernet port to the clock VLAN.
a. Choose VLAN from the navigation tree.
b. In the information list, right-click VLAN 10 and choose Configure from
the shortcut menu.
Issue 03 (2010-11-19)
d. Click Done.
l Configure the PHS service on the ONU side.
NOTE
To perform the following operations, you need to navigate to the NE Explorer of the ONU as follows:
In the Main Topology, double-click the required ONU in the Physical Root navigation tree; or right-
click the required ONU and choose NE Explorer from the shortcut menu.
1. Add a VLAN and configure its upstream port, L3 interface, media IP address, and
signaling IP address.
(1) Choose VLAN from the navigation tree.
(2) In the information list, right-click and choose Add from the shortcut menu.
(3) In the dialog box that is displayed, set the parameters.
(4) Click Next to configure the upstream port and L3 interface of the VLAN.
6-7
(5) Click Done.
(6) In the VLAN list, select the newly added VLAN and click the IP Interface tab
in the lower pane.
(8) In the dialog box that is displayed, configure the media IP address and signaling
IP address.
Issue 03 (2010-11-19)
2. Configure the MG.
(1) Choose Voice Gateway > Media Gateway from the navigation tree.
(2) On the Media Gateway tab page, set the filter criteria to display the required
MGs.
(5) Click OK.
(6) In the MG list, select a record and click the MGC Attribute Info tab in the lower
pane. In the window that is displayed, right-click the record where MGC
Index is set to 0 and choose Modify from the shortcut menu.
6-9
Click next to NMS MGC Profile. In the dialog box that is displayed, add an
MGC profile.
(7) In the MG list, right-click a record and choose Cold Start from the shortcut
menu.
(8) In the confirmation dialog box, click Yes.
3. Configure a signaling gateway (SG) and an association.
(1) Choose Voice Gateway > Signaling Gateway from the navigation tree.
(2) On the Signaling Gateway tab page, set the filter criteria to display the required
SGs.
Issue 03 (2010-11-19)
(5) Click OK.
(6) On the Association tab page, set the filter criteria to display the required
associations.
(8) In the dialog box that is displayed, set parameters of the association. Click
next to NMS MGC Profile. In the dialog box that is displayed, add an MGC
profile by setting the parameters as follows:
Name: iua1
Protocol Type: xUA
IP Address 1: 10.13.4.101
UDP/SCTP Port Number: 11000
6-11
(9) Click OK.
4. Configure SPCs.
NOTE
You need to configure four SPCs according to the data plans.
(1) Choose Connection > SPC from the navigation tree.
(4) Click OK.
Issue 03 (2010-11-19)
5. Configure a clock VLAN.
(3) In the dialog box that is displayed, add VLAN 11.
(4) Click Next, set the IP address of the L3 interface of the VLAN 11 to
20.20.20.20, and then set the port 0/0/0 as the upstream port of the VLAN 11.
(5) Click Done.
6. Configure an ACM IP address.
NOTE
An ACM IP address is used to receive ACM clock packets. You need to set the IP address of
the L3 interface of the clock VLAN to the ACM IP address.
(1) Choose NE Properties > ACM IP Address from the navigation tree.
(4) Click OK.
7. Configure a clock source.
(1) Choose NE Properties > Clock Management > Clock Source from the
navigation tree.
(2) Click the Frequency Clock Source (SYSCLK) tab.
(3) Right-click the list and choose Add Clock Source from the shortcut menu.
6-13
(5) Click OK.
l Configure the PHS service on the UA5000 side.
1. Configure the attributes of an Ethernet port.
(1) Choose ETH from the navigation tree.
(2) Click the Ethernet Port tab, and set the filter criteria or click to display the
Ethernet ports.
(3) In the Ethernet port list, select a record and click the IP Interface Info. tab in
the lower pane. On the IP Interface Info. tab page, right-click and choose
Add from the shortcut menu.
NOTE
You need to configure the service IP address and the IP address of the clock interface
separately. For information about the IP address of the clock interface, see section "Data
Plan."
(4) Click OK.
2. Configure an SG and an association.
Issue 03 (2010-11-19)
(1) Choose Voice Gateway > Signaling Gateway from the navigation tree.
(2) On the Signaling Gateway tab page, set the filter criteria to display the required
SGs.
(4) In the dialog box that is displayed, set SG ID to 0.
(5) Click OK.
(6) On the Association tab page, set the filter criteria to display the required
associations.
(8) In the dialog box that is displayed, set parameters of the association. Click
next to NMS MGC Profile. In the dialog box that is displayed, add an MGC
profile by setting the parameters as follows:
Association ID: 0
SG ID: 0
Local IP Address: 10.13.4.101
Local Port: 1401
NMS MGC Profile: iua1
MGC profile:
Protocol Type: xUA
IP Address 1: 10.13.4.116
UDP/SCTP Port Number: 12000
(9) Click OK.
3. Configure SPCs.
NOTE
You need to configure four SPCs according to the data plans.
(1) Choose Connection > SPC from the navigation tree.
Name: spc1
Service Type: Normal
Connection Type: IP SPC
Total Channels: 1
Start Frame: 0
Start Slot: 6
Start Port: 0
Start Channel: 0
Local IP Address: 10.13.4.101
Remote IP Address: 10.13.4.116
Local Port: 16400
Remote Port: 57600
Start Port Subtype: MNT Subtype
6-15
End Port Subtype: MNT Subtype
(4) Click OK.
4. Configure a clock source and a clock channel.
(1) Choose NE Properties > Clock Management > Clock Source from the
navigation tree.
(2) Click the Frequency Clock Source (TDM) tab.
(3) Right-click the list and choose Add Clock Source.
Index: 0
Frame: 2
Slot: 0
Port: 0
(5) Click Finish.
(6) Choose NE Properties > Clock Management > Clock Channel from the
navigation tree.
(9) Click OK.
----End
Result
The local fixed-line call, local mobile call, long-distance call, and certain special telecom call
services (such as 114 and 10000), are available through PHS phones and the communication
quality is good. In addition, text messages can be sent between PHS phones and mobile phones.
Issue 03 (2010-11-19)
7 Configuring the PPPoE or IPoE Access
Service (GE Upstream Transmission)
This topic describes how to configure the PPPoE or IPoE service. The ONU supports PPPoE
and IPoE services by using the xDSL access technology and thus enables users to access the
Internet in PPPoE or IPoE mode. Currently, the MA5616 supports the PPPoE or IPoE access
service.
Example Network
Figure 7-1 shows an example network of the PPPoE or IPoE access service.
User data packets are transmitted to the ONU in PPPoE or IPoE mode. Then, the ONU transmits
the user data packets upstream to upper layer devices through a GE port. In this way, users can
access the Internet in PPPoE or IPoE mode.
Figure 7-1 Example network of the PPPoE or IPoE access service

7 Configuring the PPPoE or IPoE Access Service (GE
Upstream Transmission)
7-1
Data Plan
Table 7-1 describes the data plan for the PPPoE or IPoE access service.
NOTE
After an xDSL port is bound to an xDSL profile and activated, the xDSL port can transmit services. This
topic focus more on the relationships between xDSL profiles than on the data plan of these services. In
actual applications, you need to plan the profile data according to actual requirements.
Table 7-1 Data plan for the PPPoE or IPoE access service
Item Data
Traffic profile CIR: 1024 kbit/s
Outer Priority: 1
Priority policy: Local-Setting
Network-side
VLAN
10
Upstream port ID 0/0/0
Encapsulation
mode
PPPoE

Procedure
l Configure the Internet service stream.
NOTE
of the ONU. To navigate to the NE Explorer of the ONU, do as follows: In the Main Topology,
double-click the required ONU in the Physical Root navigation tree; or right-click the required
ONU and choose NE Explorer from the shortcut menu.
1. Add a VLAN and configure its upstream port.
Issue 03 (2010-11-19)
(4) Click Next to configure its upstream port.
(5) Click Done.
2. Configure an MEF IP traffic profile.
(1) Choose Configuration > Access Profile Management > Traffic Profile from
the main menu.
(2) Click the MEF IP Traffic Profile tab.
(3) Right-click and choose Add Global Profile from the shortcut menu.
7-3
(5) Click OK.
(6) In the information list, right-click the record and choose Download to NE from
the shortcut menu.
(7) In the dialog box that is displayed, select the required NE(s), and click OK.
3. Add a service virtual port.
(1) Choose Connection > Service Port from the navigation tree.
(2) On the Service Port tab page, set the filter criteria to display the required service
virtual ports.
Issue 03 (2010-11-19)
(5) Click OK.
l Configure an ADSL port.
1. Configure an ADSL or NGADSL profile.
NOTE
The ONU supports two ADSL modes, that is, ADSL mode and NGADSL mode. You can
switch the mode by running the related command. The default mode is the ADSL mode.
Configure an ADSL profile.
(1) Choose Configuration > Access Profile Management > ADSL Profile from
the main menu.
(2) Click the ADSL Line Profile tab, and select MA56T&MDU from the Device
Type drop-down list.
(4) In the dialog box that is displayed, set the parameters and click OK. In the
profile list, right-click the newly configured profile and choose Download to
NE from the shortcut menu to apply the ADSL line profile to the NE.
(5) Click the ADSL Alarm Profile tab, and select MA56T&MDU from the
Device Type drop-down list.
(7) In the dialog box that is displayed, set the parameters and click OK. In the
profile list, right-click the newly configured profile and choose Download to
NE from the shortcut menu to apply the ADSL alarm profile to the NE.
Configure an NGADSL profile.
(1) Choose Configuration > Access Profile Management > NGADSL
Profile from the main menu.
(2) Click the ADSL Line Profile tab.
(3) On the ADSL Line Profile tab page, configure the line spectrum
configuration profile, line configuration profile, channel configuration
7-5
profile, and line profile in sequence. The line configuration profile is
dependent on the line spectrum configuration profile, and the line profile is
dependent on the line configuration profile and the channel configuration
profile.
a. On the Line Spectrum Configuration Profile tab page, add a line
spectrum configuration profile.
b. On the Line Configuration Profile tab page, add a line configuration
profile.
c. On the Channel Configuration Profile tab page, add a channel
configuration profile.
d. On the Line Template tab page, add a line profile and apply it to the
ONU.
(4) Click the ADSL Alarm Profile tab.
(5) On the ADSL Alarm Profile tab page, configure the line alarm configuration
profile, channel alarm configuration profile, and alarm profile in sequence.
The alarm profile is dependent on the line alarm configuration profile and the
channel alarm configuration profile.
a. On the Line Alarm Configuration Profile tab page, add a line alarm
b. On the Channel Alarm Configuration Profile tab page, add a channel
alarm configuration profile.
c. On the Alarm Template tab page, add an alarm profile and apply it to
the ONU.
2. Configure and activate an ADSL port.
NOTE
An ADSL port is activated by default. To bind it to a profile, you need to deactivate it first.
(1) Choose DSL > ADSL from the navigation tree.
(2) On the ADSL tab page, set the filter criteria or click to display the ADSL
ports.
Issue 03 (2010-11-19)
(3) In the ADSL port list, right-click a record and choose Configure Attributes from
the shortcut menu.
(4) In the ADSL port list, right-click the record and choose Activate from the
shortcut menu.
l Configure a VDSL2 port.
1. Configure a VDSL2 profile.
(1) Choose Configuration > Access Profile Management > VDSL2 Profile from
the main menu.
(2) Click the VDSL2 Line Profile tab.
(3) On the VDSL2 Line Profile tab page, configure the line spectrum configuration
profile, line configuration profile, channel configuration profile, and line profile
in sequence. The line configuration profile is dependent on the line spectrum
configuration profile, and the line profile is dependent on the line configuration
profile and the channel configuration profile.
a. On the Line Spectrum Configuration Profile tab page, add a line spectrum
b. On the Line Configuration Profile tab page, add a line configuration
profile.
c. On the Channel Configuration Profile tab page, add a channel
d. On the Line Template tab page, add a line profile and apply it to the
ONU.
(4) Click the VDSL2 Alarm Profile tab.
7-7
(5) On the VDSL2 Alarm Profile tab page, configure the line alarm configuration
profile, channel alarm configuration profile, and alarm profile in sequence. The
alarm profile is dependent on the line alarm configuration profile and the channel
a. On the Line Alarm Configuration Profile tab page, add a line alarm
b. On the Channel Alarm Configuration Profile tab page, add a channel
c. On the Alarm Template tab page, add an alarm profile and apply it to the
ONU.
2. Configure and activate a VDSL2 port.
NOTE
A VDSL2 port is activated by default. To bind it to a profile, you need to deactivate it first.
(1) Choose DSL > VDSL2 from the navigation tree.
(2) On the VDSL2 tab page, set the filter criteria or click to display the VDSL2
ports.
(3) In the VDSL2 port list, right-click a record and choose Configure Attributes
from the shortcut menu. In the dialog box that is displayed, select a configured
line profile and alarm profile.
(4) In the VDSL2 port list, right-click a record and choose Activate from the shortcut
menu.
l Configure a G.SHDSL port.
1. Configure a G.SHDSL profile.
(1) Choose Configuration > Access Profile Management > G.SHDSL Profile
from the main menu.
(2) Click the G.SHDSL Line Profile tab, and select from the Device Type drop-
down list.
(3) In the dialog box that is displayed, set the parameters and click OK. In the profile
list, right-click the newly configured profile and choose Download to NE from
the shortcut menu to apply the G.SHDSL line profile to the NE.
(4) Click the G.SHDSL Alarm Profile tab, and select from the Device Type drop-
down list.
(5) In the dialog box that is displayed, set the parameters and click OK. In the profile
list, right-click the newly configured profile and choose Download to NE from
the shortcut menu to apply the G.SHDSL alarm profile to the NE.
Issue 03 (2010-11-19)
2. Configure and activate a G.SHDSL port.
NOTE
A G.SHDSL port is activated by default. To bind it to a profile, you need to deactivate it first.
(1) Choose DSL from the navigation tree.
(2) On the tab page, set the filter criteria or click to display the G.SHDSL ports.
(3) In the G.SHDSL port list, right-click a record and choose Configure
Attributes from the shortcut menu. In the dialog box that is displayed, select a
configured line profile and alarm profile.
(4) In the G.SHDSL port list, right-click a record and choose Activate from the
shortcut menu.
----End
Result
After the configuration, the PC can access the Internet in PPPoE or IPoE mode.
7-9
8 Configuring the Triple Play Service
With the rapid development of broadband services, more and more users demand abundant
services to be carried on broadband, such as video services and voice services. In the triple play
network, the VoIP, IPTV, and Internet services are transmitted over one cable to the ONU
through the home gateway or the optical access modem in a centralized manner. Currently, the
MA5616 supports the triple play service.
The triple play network supports multiple service stream configuration modes as shown in Table
8-1. This topic considers the single-PVC multi-service mode (based on user-side VLANs) as an
example to describe how to configure the triple play service.
Table 8-1 Implementation mode of the triple play service
Implementati
on Mode
Feature
Single PVC Internet, VoIP, and IPTV service streams are carried by the one PVC. After
the service streams reach the ONU, the ONU distinguishes the services
according to the user-side VLANs or user-side 802.1p priorities of the
services.
The existing modem needs to be re-configured to save PVC resources.
Multiple PVCs Internet, VoIP, and IPTV service streams are carried by three different
PVCs.
The existing modem needs to be re-configured.

Example Network
Figure 8-1 shows an example network of the triple play service.
Operation Guide for ONU NE Management 8 Configuring the Triple Play Service
8-1
Figure 8-1 Example network of the triple play service

Data Plan
Table 8-2 describes the data plan for the triple play service.
Table 8-2 Data plan for the triple play service
Item Data
Traffic
profile
parameters
Internet service: 1 Mbit/s
VoIP service: 64 Mbit/s
IPTV service: no limit
Upstream
port ID
0/0/0
Upstream
VLANs
Internet service: smart VLAN 10
VoIP service: smart VLAN 11
IPTV service: smart VLAN 12
User-side
VLANs
Internet service: smart VLAN 2
VoIP service: smart VLAN 3
IPTV service: smart VLAN 4
IGMP
version
IGMP v3 (default IGMP version in the multicast VLAN mode)
Multicast
source
ISP 1 (IP address is 10.10.10.10 and the multicast program with the IP address
of 224.1.1.1 are provided.)
Issue 03 (2010-11-19)
Item Data
Multicast
program
library
Program 1 (IP address is 224.1.1.1 and the program source IP address is
10.10.10.10, the IP address of ISP 1.)
Upstream
priority
802.1p priority: 6 for VoIP services, 5 for IPTV services, and 1 for Internet
services.

Procedure
l Configure the Internet, VoIP, and IPTV service streams.
NOTE
A service stream is a service channel connecting the user side to the network side. Service streams
are a must for service provisioning. The procedures for configuring Internet, VoIP, and IPTV service
streams are similar. This topic considers the Internet service as an example to describe how to
configure a service stream. Then you can follow this procedure to configure the VoIP and IPTV
service streams according to the corresponding data plans.
8-3
(5) Click Done.
2. Configure an MEF IP traffic profile.
NOTE
Because the VoIP, IPTV, and Internet services are provided through the same port, you need
to set the 802.1p priority for each service.
Generally, the priorities for the VoIP service, IPTV service, and Internet service are in a
descending order.
the main menu.
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
NOTE
l In multi-PVC mode, VoIP, IPTV, and Internet services are carried by different PVCs on
the user side. Thus, each port is configured with at least three PVCs. The Service Type is
set to Single and the value of VLAN ID on the network side differs with service types. In
this way, multiple services can be carried by different PVCs.
l In single-PVC mode, a unique PVC is used to carry services of different types between the
access device and user terminals. The Service Type parameter is set to distinguish the
services.
virtual ports.
8-5
(5) Click OK.
After the preceding steps, the configurations of the Internet and VoIP service streams are
complete. When a user successfully dials up on a PC by using the PPPoE dialup software,
the user can access the Internet. In addition, VoIP users can communicate with each other
successfully.
l Configure multicast data.
NOTE
To provision an IPTV service, you also need to configure the IGMP proxy and multicast programs.
1. Add a multicast VLAN and configure the multicast mode.
(1) Choose Multicast > Multicast VLAN from the navigation tree.
Issue 03 (2010-11-19)
(4) Click Finish.
2. Add a virtual upstream port.
(1) Choose Multicast > Virtual Uplink Port from the navigation tree.
8-7
(4) Click Finish.
3. Configure a program profile.
(1) Choose Configuration > Access Profile Management > IGMP Profile from
the main menu.
(2) Click the Program Profile tab, and select the required device type from the
(5) Click OK.
the shortcut menu.
(7) In the dialog box that is displayed, select the required device and click Next.
(8) In the dialog box that is displayed, set VLAN ID to 12 and click Done.
4. Configure multicast users.
Issue 03 (2010-11-19)
(1) Choose Multicast > Multicast User from the navigation tree.
(4) Click Finish.
IPTV users can watch program 1.
----End
8-9
9 Configuring the Ethernet Port Access Service
(GE Upstream Transmission)
This topic describes how to configure the Ethernet port access service. TheONU supports the
access of one or multiple video and data services through a single Ethernet port in multi-service
mode. Currently, the MA5612 supports the Ethernet port access service.
Example Network
Figure 9-1 shows an example network of the Ethernet port access service.
The PC and STB are connected to the Ethernet port on the ONU through the LAN switch,
implementing the Ethernet access in the single-port for multi-service mode and transmitting data
upstream to the router through the GE upstream port 0/0/0. Then, the data is transmitted to the
Internet.
9 Configuring the Ethernet Port Access Service (GE
9-1
Figure 9-1 Example network of the Ethernet port access service

Data Plan
Table 9-1 describes the data plan for the Ethernet port access service.
Table 9-1 Data plan for the Ethernet port access service
Item Data
Service port ID 0/4/1
Upstream port ID 0/0/0
Upstream VLANs l Internet service: VLAN 10
l IPTV service: VLAN 12
User-side VLAN l Internet service: VLAN 2
l IPTV service: VLAN 3
Internet mode PPPoE
Program library Program 1 (multicast IP address: 224.1.1.1, program source IP
address: 10.10.10.10)
Priority 802.1p priority: 4 for IPTV services and 1 for Internet services.
Issue 03 (2010-11-19)
Item Data
Requirements for the
LAN switch of the
upper-layer device
l The LAN switch transparently transmits the service packets of
the ONU.
l A VLAN must be configured for the service access of the
ONU. The VLAN ID must be the same as that of the upstream
VLAN of the ONU.
For detailed configuration of the LAN switch, see the related
configuration guide.

Procedure
l Configure Internet and IPTV service streams.
NOTE
A service stream is a service channel connecting the user side to the network side. Service streams
are a must for service provisioning. The procedures for configuring Internet and IPTV service streams
are similar. Therefore, this topic considers the Internet service as an example to describe how to
configure the service stream. Then you can follow this procedure to configure the IPTV service
streams according to the corresponding data plan.
9-3
(5) Click Done.
2. Configure a traffic profile.
the main menu.
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
virtual ports.
9-5
(5) Click OK.
The configuration of Internet service stream is complete and users can access the Internet
by using the PPPoE dialup software successfully on a PC.
l Configure the multicast data.
NOTE
To provision an IPTV service, you also need to configure the IGMP proxy and multicast programs.
1. Add a multicast VLAN and configure the multicast mode.
Issue 03 (2010-11-19)
(4) Click Finish.
2. Add a virtual upstream port.
9-7
(4) Click Finish.
3. Configure a program profile.
the main menu.
(5) Click OK.
the shortcut menu.
(7) In the dialog box that is displayed, select the required device and click Next.
(8) In the dialog box that is displayed, set VLAN ID to 12 and click Done.
4. Configure multicast users.
Issue 03 (2010-11-19)
(4) Click Finish.
IPTV users can watch program 1.
----End
9-9
10 Configuring the VLAN ID Extension
Service
This topic describes how to configure the VLAN ID extension service. Broadband users of
multiple ONUs are authenticated on a BRAS to obtain broadband services provided by carriers.
The BRAS can identify users according to L2 VLANs. Therefore, the number of supported
VLANs is extended. Currently, the MA5616, MA5612, MA5620, and MA5626 support the
VLAN ID extension service.
Example Network
Figure 10-1 shows an example network of the VLAN ID extension service.
Broadband users of multiple ONUs are authenticated on a BRAS to obtain broadband services
provided by carriers. The BRAS supports the user identification through L2 VLAN. Specifically,
the outer VLAN tag identifies the ONU that connects to users, and the inner VLAN tag identifies
the users that are connected to the device.
Figure 10-1 Example network of the VLAN ID extension service
Operation Guide for ONU NE Management 10 Configuring the VLAN ID Extension Service
10-1

Data Plan
Table 10-1 describes the data plan for the VLAN ID extension service.
Table 10-1 Data plan for the VLAN ID extension service
Item Data
ONU_A
Upstream port ID: 0/0/0
Upstream VLAN ID (outer VLAN tag): 100
VLAN attribute: stacking VLAN
User 1: inner VLAN tag 11
ONU_B
Upstream port ID: 0/0/0
Upstream VLAN ID (outer VLAN tag): 101
VLAN attribute: stacking VLAN

Procedure
l Configure the VLAN ID extension service on the ONU_A side.
NOTE
10 Configuring the VLAN ID Extension Service
Issue 03 (2010-11-19)
(5) Click Done.
NOTE
The operations for adding a service virtual port for user 1 are similar to those for user 2. This
topic considers user 1 as an example to describe how to add a service virtual port.
virtual ports.
Operation Guide for ONU NE Management 10 Configuring the VLAN ID Extension Service
10-3
(5) Click OK.
l Configure the VLAN ID extension service on the ONU_B side. (See the procedure for
configuring the VLAN ID extension service on the ONU_A side).
----End
Result
After being authenticated by the BRAS, the users connected to the ONU_A and ONU_B can
access the Internet.
Two users of the ONU can be identified by one outer VLAN tag. In this manner, the number of
access users based on one VLAN tag is increased.
10 Configuring the VLAN ID Extension Service
Issue 03 (2010-11-19)
11 Configuring the Ethernet OAM
Diagnosis
About This Chapter
This topic describes the principles, configuration procedure, and configuration example of the
Ethernet OAM diagnosis.
Prerequisite
l The corresponding VLAN must exist.
l The VLAN must be configured with an upstream port.
Context
With the extension of the Ethernet technology from the carrier network to MAN and WAN,
carriers are more concerned about the maintainability of devices. Therefore, the maintenance of
Ethernet devices becomes more and more important. The operations, administration and
maintenance (OAM) issue of the transmission network is pressing. The 802.1ag connectivity
fault management (CFM) provides an end-to-end method for detecting faults. The Ethernet
OAM mechanism supported by the 802.1ag CFM covers connectivity check (CC), loopback
(LB), link trace (LT), and forward AIS alarms.
Figure 11-1 shows the flowchart for configuring the Ethernet OAM diagnosis on the ONU.
Operation Guide for ONU NE Management 11 Configuring the Ethernet OAM Diagnosis
11-1
Figure 11-1 Flowchart for configuring the Ethernet OAM diagnosis

11.1 Introduction to the Ethernet OAM
This topic describes the basic concepts and principles of the Ethernet connectivity fault
management (CFM) and the example network of the Ethernet OAM. The Ethernet OAM
mechanism supported by the 802.1ag covers the connectivity check (CC), link trace (LT), and
loopback (LB).
11.2 Configuring an MD
This topic describes how to configure an MD. Different MDs are maintained by different
management entities.
11.3 Configuring an MA
This topic describes how to add an MA, add devices to the MA, configure the interval for sending
CCM packets and the function of checking remote MEPs, check the remote MEPs configured
in the MA, and report alarms of detected faults.
11.4 Configuring a Source MEP
This topic describes how to create a source MEP to detect the connectivity of a channel in an
MA, and how to configure the administrative status, CCM and LTM priority, and CCM sending
status for the MEP.
11.5 Enabling the Global CFM Function
This topic describes how to configure the Ethernet OAM global parameters on the U2000 and
issue the parameters to the specified devices. You can configure the Ethernet OAM global
parameters in the System Parameter Profile of the U2000. Devices can detect and locate
Ethernet faults through the bound System Parameter Profile.
11.6 Configuration Example of the Ethernet OAM Diagnosis
11 Configuring the Ethernet OAM Diagnosis
Issue 03 (2010-11-19)
This topic provides an example for configuring the Ethernet OAM on the ONU.
11-3
11.1 Introduction to the Ethernet OAM
This topic describes the basic concepts and principles of the Ethernet connectivity fault
management (CFM) and the example network of the Ethernet OAM. The Ethernet OAM
mechanism supported by the 802.1ag covers the connectivity check (CC), link trace (LT), and
loopback (LB).
Context
The basic concepts and principles of the Ethernet CFM are described as follows.
1. Basic concepts:
l Maintenance domain (MD): The Ethernet CFM divides a network into a maximum of
eight layers. A bridge can have different layers to manage different MDs. A CFM MD
consists of bridges, and is a combination of bridges and maintenance levels. MDs come
under three layers: user domain (levels 7-5), service provider domain (levels 4-3), and
carrier domain (levels 2-0). Different MDs are maintained by different management
entities.
l Maintenance association (MA): An MD can be divided into multiple MAs. Each MA
maps with a service instance (SI) identified by a VLAN in the MD. That is, the MA can
be understood as a combination of an MD and a VLAN. (According to the standard,
multiple VLANs can map with one SI, and one SI maps with one MA.)
l Maintenance point (MP): An MA consists of maintenance points (MPs) that are defined
on the ports of bridges. That is, an MP is a combination of a bridge port, a VLAN, and
a maintenance level. MPs are classified into two types: maintenance association end
point (MEP) and maintenance association intermediate point (MIP). An MEP initiates
and responds to CFM messages. An MIP does not initiate CFM messages. It only
transparently transmits or responds to CFM messages.
2. Principles of fault detection:
l Continuity check messages (CCMs) are used to detect Ethernet faults. Each MEP
actively sends CCM packets at regular intervals. The CCM packets are copied to the
multicast addresses. All the MIPs and MEPs in the MD can receive the CCM packets
but need not respond. When an MEP receives CCM packets from other MEPs, it sets
up and maintains an MEP CCM database. The database records the MEP IDs, MAC
addresses of the MEPs, and the mappings between the MEPs and the receiving ports.
The database also records the information about other MEPs in the MA. If the MEP
does not receive CCM packets from another MEP for three successive times, the MEP
reports a fault.
l Loss of CCM packets may be caused by a link fault, a switched network fault, or wrong
configurations between two MEPs. The NMS can use other methods, such as loss of
physical layer signals, instead of CCM packets, to detect the link faults. But in this case,
the NMS cannot detect the non-link faults, such as switched network faults or wrong
configurations. After a fault is discovered through CCM packets, you can use LB or LT
to locate the fault (for example, in the switched network).
l CCM packets can detect not only the link faults and switched network faults, but also
the service configuration errors (such as unmatched MA names), repeated MEP
configurations (such as repeated MEP names), undesired MEPs, loopback (repeated
serial numbers), data loss, and data corruption (such as wrong checksum).
3. Alarm mechanism: There are four types of alarms.
Issue 03 (2010-11-19)
l Cross-connection alarm: After an MEP on a bridge receives a CCM packet, the MEP
checks whether certain configuration (including the type and length of the MD name;
the MD name; the type and length of the MA name; and the MA name) of the peer MEP
as carried by the CCM packet is completely the same as the local configuration. If the
configurations are different, the MEP reports a cross-connection alarm.
l Loss-of-CCM alarm: If an MEP on a bridge does not receive a CCM packet from a
remote MEP in a specific period (3.5 times the sending interval), the MEP reports a
loss-of-CCM alarm.
l Error alarm: After an MEP on a bridge receives a CCM packet, the MEP compares the
MEP information in the received CCM packet with the configuration information about
the remote MEP, including the interval for sending CCM packets. If the information
does not match, the MEP reports an error alarm.
l RDI alarm: If a local MEP does not receive CCM packets from its remote MEP, the
local MEP sends a CCM packet with an RDI bit. When another MEP receives the CCM
packet with the RDI bit, the MEP reports an RDI alarm.
4. LT principle:
l The LT helps to check the MIP path between two MEPs. A link trace message (LTM)
contains a known multicast address, but is not multicasted. The LTM contains additional
information indicating the MAC address of the destination MEP. When the LTM is
forwarded by MIPs to the destination MEP in unicast mode, each MIP sends a link trace
reply (LTR) to the source MEP. In this way, the source MEP learns the MIPs along the
path to the destination MEP and records their MAC addresses.
5. LB principle:
l LB helps an MEP to locate faults in an MA. LB uses the unicast MAC address of an
MEP or MIP that is discovered by the CC or LT. The source MEP creates a loopback
message (LBM) containing the index of the destination MEP, sends the LBM, and starts
the timer. After receiving the LBM, the destination MEP sends an LBR to the source
MEP. The loopback test succeeds. If the timer of the source MEP expires, the loopback
test fails.
11.2 Configuring an MD
This topic describes how to configure an MD. Different MDs are maintained by different
management entities.
Prerequisite
l You can perform this operation only after the CFM function is enabled globally.
Context
l The system supports three MDs.
l MDs with the same name format and the same name cannot be created on the same device,
but can be created on different devices.
l MDs of the same level cannot be created on the same device, but can be created on different
devices.
11-5
l The total length of the names of an MA and the corresponding MD must be less than or
equal to 43 characters.
Procedure
1 In the Main Topology, double-click the required ONU in the Physical Root navigation tree; or
right-click the required ONU and choose NE Explorer from the shortcut menu.
2 Choose ETH OAM from the navigation tree.
3 Click the Maintenance Domain tab, right-click the list, and then choose Add.
4 In the dialog box that is displayed, set MD Name Format, MD Name, Level and MHF Creation
Rule as follows.
5 Click OK.
----End
11.3 Configuring an MA
This topic describes how to add an MA, add devices to the MA, configure the interval for sending
CCM packets and the function of checking remote MEPs, check the remote MEPs configured
in the MA, and report alarms of detected faults.
Prerequisite
l The MD must be configured.
Context
l You can perform this operation only after the CFM function is enabled globally.
l Each MD can be configured with up to 48 MAs. The system supports up to 48 MAs. That
is, if you configure 48 MAs in an MD, you cannot configure MAs in other MDs.
Issue 03 (2010-11-19)
l The MA must belong to an MD. Do not create an MA that is consistent with an existing
one.
l The MAs in the same MD cannot be associated with the same VLAN.
l The total length of the names of an MA and the corresponding MD must be less than or
equal to 43 characters.
Procedure
3 Click the Maintenance Association tab, right-click the list, and then choose Add.
4 In the dialog box that is displayed, set MD Name, MA Name Format, MA Name, and CC
Interval as follows.
5 Click OK.
6 Select the added MA1, right-click, and then choose Configure.
7 In the dialog box that is displayed, set MHF Creation Rule, Remote MEP Detection
Function and Associated VLAN as follows.
11-7
8 Click OK.
----End
11.4 Configuring a Source MEP
This topic describes how to create a source MEP to detect the connectivity of a channel in an
MA, and how to configure the administrative status, CCM and LTM priority, and CCM sending
status for the MEP.
Prerequisite
l The MD must be configured. For details, see 11.2 Configuring an MD.
l The MA must be configured. For details, see 11.3 Configuring an MA.
Context
An MEP is the end point of a maintenance channel. Ethernet OAM depends on the MEPs at both
ends of a channel to check the connectivity. Therefore, the MEPs must be created. After creating
the MEPs, you can use them to check the connectivity of a channel in an MA.
l The MEP takes effect only after the administrative function is enabled.
l The MEP can send CCM packets at regular intervals to check the connectivity of a channel
only after the CCM packet sending function is enabled successfully.
l After the CCM and LTM priority is successfully configured, the system discards the packets
with lower priority in case of congestion.
Issue 03 (2010-11-19)
Procedure
3 Click the Maintenance Association tab, set the querying criteria or click to display the
records.
4 Select a record from the list, and then click the Source MEP ID Info tab in the lower pane.
Right-click the list, and then choose Add.
5 In the dialog box that is displayed, set MEP ID, Interface Info, Interface Direction, VLAN
TAG1, VLAN TAG2 and CCM And LTM Priorityas follows.
6 Click OK.
7 Select the added source MEP, right-click, and then choose Configure.
8 In the dialog box that is displayed, enable the Administrative Status and CC Sending Status
of the MEP, and then set CCM And LTM Priority, Alarm Waiting Time and Alarm Recovery
Time as follows.
11-9
9 Click OK.
----End
11.5 Enabling the Global CFM Function
This topic describes how to configure the Ethernet OAM global parameters on the U2000 and
issue the parameters to the specified devices. You can configure the Ethernet OAM global
parameters in the System Parameter Profile of the U2000. Devices can detect and locate
Ethernet faults through the bound System Parameter Profile.
Context
When the global CFM function is enabled, the CFM packets are captured, and the functions of
CC, LB and LT are enabled. When the global CFM function is disabled, the CFM packets are
not captured, and the functions of CC, LB, and LT are disabled.
The system parameter profile is a collection of system parameters, such as ETH OAM parameters
and other parameters. After a system parameter profile is issued to a device successfully, the
parameters in the profile overwrite the original parameters on the device. This may affect the
services of the device. Therefore, the system parameter profile must be issued to the device
before service provisioning.
Procedure
2 On the navigation tree of the tab page that is displayed, choose NE Properties > Protocol >
ETH OAM.
3 In the parameter configuration area in the right pane, configure the global parameters of the
Ethernet OAM devices, including the multicast MAC base address that is used to send CC/LT
packets, and then set Global remote MEP test and Global CFM switch.
Issue 03 (2010-11-19)
4 Click Apply.
----End
11.6 Configuration Example of the Ethernet OAM Diagnosis
This topic provides an example for configuring the Ethernet OAM on the ONU.
Prerequisite
l The example network as shown in Figure 11-2 must be complete.
l The network devices and lines must be in the normal state.
Example Network
Figure 11-2 shows the example network of the Ethernet OAM on the ONU. The link between
ONU_A and ONU_B uses the Ethernet OAM mechanism to detect link faults. Both ONU_A
and ONU_B are configured with a local MEP and a remote MEP. The local MEP ID of
ONU_B is the same as the remote MEP ID of ONU_A. The remote MEP ID of ONU_B is the
same as the local MEP ID of ONU_A.
Figure 11-2 Example network of the Ethernet OAM

ONU_A ONU_B
Router

Data Plan
Table 11-1 provides the data plan for the Ethernet OAM on the ONU.
11-11
Table 11-1 Data plan for the Ethernet OAM
Item Data
ONU_A l Port: 0/1/0
l Smart VLAN: 100
l MD Name Format: character string type
l MD Name: MD1
l Level: 3
l MA Name Format: character string type
l MA Name: MA1
l Remote MEP check: Enable
l Associated VLAN: 100
l MEP ID: 2
l Interface Direction: UP
l CCM and LTM Priority: 7
l Administrative Status: enable
l CC Sending Status: enable
l Alarm Waiting Time: 2500
l Alarm Recovery Time: 10000
ONU_B l Port: 0/0/1
l Smart VLAN: 100
l MD Name: MD2
l Level: 3
l MA Name: MA2
l MEP ID: 2

NOTE
l Configure the remote MEP of ONU_A on ONU_B in the same way as configuring the MEP of ONU_A.
l This topic considers the configuration on ONU_A as an example.
Issue 03 (2010-11-19)
Procedure
1 Add a VLAN and configure the upstream port of the VLAN.
3. Right-click the list, and then choose Add. In the dialog box that is displayed, set the related
parameters.
Parameter settings:
l VLAN ID: 100
l Type: Smart VLAN
l Attribute: Common
4. Click Next, and then select port 0/1/0 as the upstream port. Click Done.
2 Configure the MD.
1. Choose ETH OAM from the navigation tree.
2. Click the Maintenance Domain tab, right-click the list, and then choose Add.
3. In the dialog box that is displayed, set the device name and the name format, name, and
level of the MD as follows, and then click OK.
l MD Name: MD1
l Level: 3
3 Configure the MA.
1. Click the Maintenance Association tab, right-click the list, and then choose Add.
2. In the dialog box that is displayed, set the parameters as follows, and then click OK.
l MD Name: MD1
l MA Name: MA1
3. Select the added MA1, right-click, and then choose Configure.
4 Configure the MEP ID.
1. Click the Maintenance Association tab, set the querying criteria or click to display the
records.
2. Select the added MA1, and then click the MEP ID Info tab in the lower pane. Right-click
the list, and then choose Add.
3. In the dialog box that is displayed, set MEP ID to 2.
5 Configure the MEP.
1. Click the Maintenance Association tab, set the querying criteria or click to display the
records.
11-13
2. Select the added MA1, and then click the Source MEP ID Info tab in the lower pane.
Right-click the list, and then choose Add.
l MEP ID: 2
l Interface Info: 0/1/0
4. Select the added MEP1, right-click, and then choose Configure.
----End
Result
After successful configuration, you can query the statistics of the packets on ONU_A or
ONU_B. The number of the transmitted CCM packets and the number of the received CCM
packets are not zero.
Issue 03 (2010-11-19)
12 Detecting the Network
About This Chapter
This topic describes how to check the connectivity of a network and whether the host is reachable,
and how to check all gateways passed by data packets sent from a source host to the destination
host. In addition, this operation helps you to locate network faults and log in to the device through
the network remotely to configure and maintain the device.
12.1 Telnet
This topic describes how to log in to the device through the network remotely to configure and
maintain the device.
12.2 Ping
This topic describes how to send ping packets to a remote host to check whether it is reachable.
To check the network connectivity or the line quality, perform this operation.
12.3 Tracert
This topic descries how to test the route that is passed by data packets sent from a source host
to the destination host. To track the route that is passed by data packets and locate the network
fault, perform this operation. After running the ping command to test the network and detect a
fault, you can run the tracert command to locate the fault on the network.
12.4 SSH
The secure shell (SSH) guarantees the security of the network communications by providing
authentication, encryption, and authorization. When users telnet the router through an insecure
network, SSH offers secure information guarantee and powerful authentication to protect the
device against attacks such as IP address spoofing and interception of the plain text password.
Operation Guide for ONU NE Management 12 Detecting the Network
12-1
12.1 Telnet
This topic describes how to log in to the device through the network remotely to configure and
maintain the device.
Prerequisite
Make sure that port 9811 between the U2000 server and clients is enabled before you telnet a
device.
Procedure
1 On the navigation tree or in the topological view, select a required device.
2 Right-click, and then choose Tool > Telnet. When you successfully telnet to the remote server
or device through the network, you can operate the device through command lines.
----End
12.2 Ping
This topic describes how to send ping packets to a remote host to check whether it is reachable.
To check the network connectivity or the line quality, perform this operation.
Context
During the ping process, the source host sends the ICMP ECHO-REQUEST packets to the
destination host. If the network connection between the source host and the destination host is
normal, after receiving the ICMP ECHO-REQUEST packets, the destination host responds to
the source host with the ICMP ECHO-REPLY packets.
Procedure
2 Right-click, and then choose Tool > Ping.
3 In the dialog box that is displayed, select the Ping or Continual Ping parameter, and then click
Start.
NOTE
l If the operation is successful, it indicates that the destination host is reachable. In the Result area, the
system displays the information indicating that the network connectivity is in the normal state. The
displayed information includes the number of sent packets, number of received response packets, packet
loss ratio, and minimum, maximum, and average values of the response time.
l If the operation fails, it indicates that the destination host is not reachable. The system fails to check
the network connectivity or line failure. The system displays the message Request time out.
----End
12 Detecting the Network
Issue 03 (2010-11-19)
12.3 Tracert
This topic descries how to test the route that is passed by data packets sent from a source host
to the destination host. To track the route that is passed by data packets and locate the network
fault, perform this operation. After running the ping command to test the network and detect a
fault, you can run the tracert command to locate the fault on the network.
Context
The execution process of the tracert command is as follows:
l The source host sends a packet with TTL 1. TTL times out. The first hop sends back an
ICMP error message to indicate that this packet cannot be sent.
l The source host sends a packet with TTL 2. TTL times out. The second hop sends back an
l The source host sends a packet with TTL 3. TTL times out. The third hop sends back an
l The process continues in this manner until the packet reaches the destination host.
l The purpose of performing these operations is to record the source address of each ICMP
TTL time-out message, so as to provide the route that an IP packet passes to reach the
destination host.
Procedure
2 Right-click, and then choose Tool > Tracert.
----End
12.4 SSH
The secure shell (SSH) guarantees the security of the network communications by providing
authentication, encryption, and authorization. When users telnet the router through an insecure
network, SSH offers secure information guarantee and powerful authentication to protect the
device against attacks such as IP address spoofing and interception of the plain text password.
Procedure
2 Right-click, and then choose Tool > SSH.
4 Click OK.
----End
Operation Guide for ONU NE Management 12 Detecting the Network
12-3
13 Saving the Data
About This Chapter
After saving the data to the flash memory of the device, you can query the data information to
maintain and manage the device.
13.1 Setting the Parameters for Saving the Data
You can configure the auto save period of the data through enabling the auto save function of
the device. The U2000 automatically saves the data to the flash memory of the device according
to the configured period. Through the U2000, you can periodically maintain and manage the
device according to the saved data information.
13.2 Immediately Enabling Data Saving Function
This topic describes how to immediately enable the auto save function of the device to save the
current data of the device in time.
Operation Guide for ONU NE Management 13 Saving the Data
13-1
13.1 Setting the Parameters for Saving the Data
You can configure the auto save period of the data through enabling the auto save function of
the device. The U2000 automatically saves the data to the flash memory of the device according
to the configured period. Through the U2000, you can periodically maintain and manage the
device according to the saved data information.
Context
NOTE
The absolute period and relative period of the device are based on the time of the site where the device is
located.
Procedure
2 Choose NE Properties > Auto Save Configuration from the navigation tree on the tab page
that is displayed.
3 In the right pane, set the Absolute Period or Relative Period parameter for saving the data.
NOTE
l Absolute Period: The data is automatically saved at a specified time. For example, if the Absolute
Period parameter is set to 01h 05m 31s, the data is automatically saved at the preset time.
l Relative Period: The data is automatically saved at an interval. For example, if the Relative Period
parameter is set to 00d 05h 31m, the data is automatically saved every other 331 minutes.
4 Click Apply.
----End
13.2 Immediately Enabling Data Saving Function
This topic describes how to immediately enable the auto save function of the device to save the
current data of the device in time.
Context
CAUTION
l This operation is applicable to only the device that supports the SNMP protocol.
l After being enabled immediately, the automatic saving function cannot be manually stopped.
Do not power off or reset the device before the data is saved. Otherwise, the data saved to
the flash memory is damaged.
13 Saving the Data
Issue 03 (2010-11-19)
Procedure
1 On the Physical Root navigation tree on the Main Topology tab page, select the required , right-
click, and then choose Save Data Immediately.
2 In the dialog box that is displayed, Click OK.
----End
Operation Guide for ONU NE Management 13 Saving the Data
13-3
14 Synchronization
About This Chapter
This topic describes how to synchronize the NE data, NE time, NE alarms and system parameter
profile so that the data of the NE and the data on the U2000 are the same.
14.1 Synchronizing NE Data
This topic describes how to synchronize the device panel data and service data on the U2000
with that of NEs. The synchronization facilitates centralized maintenance and management.
14.2 Synchronizing the NE Time
This topic describes how to synchronize the NE time with the U2000 time to ensure that the time
when the NE reports the information is correct.
14.3 Synchronizing the NE Alarm
This topic describes how to synchronize the NE alarm. After the communication between the
U2000 and the device recovers or the U2000 restarts, the alarms generated on the device side
are not reported to the U2000 in time. This results in the inconsistency of the alarm status between
the U2000 and the device. In this case, you need to synchronize the alarms. You can synchronize
the alarms manually, or set the automatic synchronization function. This ensures that the U2000
monitors the actual running status of the device.
14.4 Synchronizing the System Parameter Profile
You can perform this operation to synchronize the system parameter profile that is modified at
the global side to the device to maintain the consistency of the parameters in the system parameter
profile.
Operation Guide for ONU NE Management 14 Synchronization
14-1
14.1 Synchronizing NE Data
This topic describes how to synchronize the device panel data and service data on the U2000
with that of NEs. The synchronization facilitates centralized maintenance and management.
Prerequisite
The FTP, SFTP, or TFTP server must be configured and the FTP, SFTP, or TFTP service must
be started.
In the physical topology, the gear on the upper left of an MDU icon indicates that the MDU is
in the pre-deployment state. If the U2000 and NEs communicate in the normal state, the MDU
state changes from pre-deployment to running after the data of the MDU is synchronized.
Context
l During the operation of the U2000, the data of NEs and the data on the U2000 must be the
same.
l After the data of an NE is configured and the NE runs in the normal state, synchronize the
data on the U2000 with that of the NE manually. When an error occurs to the NE data,
check whether the NE data saved on the U2000 is correct. If it is correct, download the data
from the U2000 to the NE. In this case, the data of the NE is restored.
Procedure
l In the Physical Root navigation tree on the Main Topology tab page, right-click the
required ONU and choose Synchronize NE Data from the shortcut menu.
----End
14.2 Synchronizing the NE Time
This topic describes how to synchronize the NE time with the U2000 time to ensure that the time
when the NE reports the information is correct.
Context
l The U2000 delivers the system time automatically when a device gets online.
l After synchronizing the NE time, do not change the system time of the U2000 frequently.
Procedure
l On the Physical Root navigation tree on the Main Topology tab page, select the required
ONU, right-click, and then choose Set NE Time.
----End
14.3 Synchronizing the NE Alarm
This topic describes how to synchronize the NE alarm. After the communication between the
U2000 and the device recovers or the U2000 restarts, the alarms generated on the device side
14 Synchronization
Issue 03 (2010-11-19)
are not reported to the U2000 in time. This results in the inconsistency of the alarm status between
the U2000 and the device. In this case, you need to synchronize the alarms. You can synchronize
the alarms manually, or set the automatic synchronization function. This ensures that the U2000
monitors the actual running status of the device.
Procedure
l By manual alarm synchronization, all alarms generated by NE are synchronized.
1. On the Physical Root navigation tree on the Main Topology tab page, select the
required ONU, right-click, and then choose Synchronize Current Alarms.
----End
14.4 Synchronizing the System Parameter Profile
You can perform this operation to synchronize the system parameter profile that is modified at
the global side to the device to maintain the consistency of the parameters in the system parameter
profile.
Procedure
1 On the Physical Root navigation tree on the Main Topology tab page, select the required
ONU, right-click, and then choose Synchronize System Parameter Profile.
----End
Operation Guide for ONU NE Management 14 Synchronization
14-3
15 File Operations
About This Chapter
By file operation, you can save the records as a file, preview the file printing effect, and print
the file. In this case, you can save and analyze the related information of the U2000.
15.1 Saving the Records as a File
This topic describes how to save the records as a text file, an Excel file, and an HTM (HTML)
file. In this case, you can use the records in different file formats.
15.2 Previewing the File Printing Effect
This topic describes how to preview the file printing effect so that you can adjust the page settings
before printing.
15.3 Printing
You can print out the records in the U2000 information list to keep the related information of
the U2000 and analyze it.
Operation Guide for ONU NE Management 15 File Operations
15-1
15.1 Saving the Records as a File
This topic describes how to save the records as a text file, an Excel file, and an HTM (HTML)
file. In this case, you can use the records in different file formats.
Context
This topic uses VLAN as an example. For other subjects, the steps are the same except that the
navigation path is different.
Procedure
2 Choose VLAN from the navigation tree.
3 On the VLAN tab page, set the filter criteria or click to display the VLANs.
4 In the information list, right-click, and then choose File > Save As.
l Set Start Row and End Row.
l Click for File Name, and then set the file saving location, file name, file type and
encoding.
6 Click OK.
----End
15.2 Previewing the File Printing Effect
This topic describes how to preview the file printing effect so that you can adjust the page settings
before printing.
Context
Procedure
4 Right-click the list, and then choose File > Print Preview.
15 File Operations
Issue 03 (2010-11-19)
5 In the dialog box that is displayed, preview the file printing effect, or adjust the page settings
according to the requirements. Click Close to close the current dialog box, or click Print to print
the file.
----End
15.3 Printing
You can print out the records in the U2000 information list to keep the related information of
the U2000 and analyze it.
Context
Procedure
4 Right-click the list, and then choose File > Print.
6 Click OK.
----End
Operation Guide for ONU NE Management 15 File Operations
15-3
16 Introduction to the PnP Solution to FTTx
Devices
About This Chapter
This topic describes the plug and play (PnP) solution to FTTx devices.
16.1 Introduction to the PnP Function
This topic describes the application background, plug-and-play (PnP) function, and benefits of
the PnP function.
16.2 PnP Application Scenario
This topic describes the PnP application scenario.
Operation Guide for ONU NE Management 16 Introduction to the PnP Solution to FTTx Devices
16-1
16.1 Introduction to the PnP Function
This topic describes the application background, plug-and-play (PnP) function, and benefits of
the PnP function.
Background
Currently, FTTx network construction is in full swing. Box-shape devices with a small capacity
are not deployed only in the telecommunications room. They are widely deployed in street racks,
corridors of communities, business buildings, and houses of users. Therefore, access points are
closer to users. Nevertheless, though better user experience is provided, a lot of problems appear,
such as an exponential increase in the number of access devices, complex deployment
environment, and a rapid increase in the software commissioning workload.
Function
Concerning different challenges, the U2000 provides a PnP function during MDU engineering
installation, maintenance, and parts replacement.
Before installing the MDU, you can import the sheet into the U2000 to implement not only the
pre-deployment of NE and NE services, but also the in-batch and offline deployment of MDU.
After the MDU is installed and powered on, the U2000 automatically applies the configuration
data to the MDU and field software commissioning is not required. The offline deployment and
PnP function greatly improves the deployment efficiency and lowers the skill requirements for
installation engineers. The construction is simple and thus the number of site visits is reduced,
which saves the deployment costs.
When the MDU is faulty and needs to be replaced, the MDU is reported to the U2000. After the
MDU is powered on, the previous configuration data and the device version are automatically
recovered and do not need to be reconfigured. The PnP solution provides fast replacement of
MDUs, which simplifies the procedures and lowers the skill requirements for installation
engineers.
16.2 PnP Application Scenario
This topic describes the PnP application scenario.
xPON upstream MDUs support the PnP function during pre-deployment and fast replacement.
l Pre-deployment: In deployment, a present pre-deployment sheet is imported into the
U2000. After an MDU is installed and powered on, the U2000 automatically applies the
previous configuration data and device version to the MDU. In this case, you do not need
to configure the MDU again and the PnP function and fast replacement of the MDU are
achieved.
l Fast replacement: When an MDU is faulty, you need to replace the MDU and power it on.
After the MDU is reported to the U2000, the previous configuration data and the device
version are automatically recovered and do not need to be reconfigured.
16.2.1 Predeploying xPON MDUs
Predeploying xPON MDUs achieves the plug and play (PnP) function in the engineering and
installation phase. In a fiber to the building (FTTB) network, a large number of dispersed remote
network elements (NEs) are far away from the telecommunications room at the central office
16 Introduction to the PnP Solution to FTTx Devices
Issue 03 (2010-11-19)
(CO). To configure the NEs in batches and implement the PnP feature of the NEs, the U2000
supports NE pre-deployment and NE service pre-deployment by importing sheets.
16.2.2 Replacing an MDU Quickly
In the FTTX network, a large number of optical network units (ONUs) work. If a faulty ONU
is replaced with a new one, you need to only enter the authentication information, after which
the previous configuration data will be applied automatically. The following considers the
MA5620E as an example to describe how to quickly replace an MDU.
16.2.1 Predeploying xPON MDUs
Context
xPON MDUs are classified into GPON MDUs and EPON MDUs. Generally, GPON MDUs use
SNs for authentication and EPON MDUs use MAC addresses for authentication.
Predeploying an xPON MDU is applicable to the following scenarios:
l In one scenario, the MAC address or SN of the MDU is known. Specifically, the mapping
between the MAC address or SN and the IP address of the MDU is planned. Then,
installation engineers must comply with the plan to install the MDU in a specified place.
Figure 16-1 shows the flowchart for predeploying the MDU whose MAC address or SN
is known.
Figure 16-1 Flowchart for predeploying the MDU whose MAC address or SN is known

16-3
l In the other scenario, the MAC address or SN of the MDU is unknown. Specifically, the
IP address is planned but the mapping between the IP address and the MAC address or SN
of the MDU is unknown. Then, installation engineers need to write down the MAC address
or SN of the MDU after installing the MDU and provide the MAC address or SN to the
network management center (NMC). In this case, an NMC engineer binds the IP address
and the MAC address or SN. Figure 16-2 shows the flowchart for predeploying the MDU
whose MAC address or SN is unknown.
Figure 16-2 Flowchart for predeploying the MDU whose MAC address or SN is unknown

16.2.2 Replacing an MDU Quickly
Context
When a faulty ONU is replaced with a new one, you need to connect the new ONU to the relevant
port of the OLT through an optical fiber and bind the authentication information of the new
ONU. After the new ONU goes online, the U2000 automatically applies service configuration
data to the new ONU. Therefore, you need not reconfigure the data.
Advantages:
l An MDU is replaced easily and the OSS need not reapply configuration data.
l The MAC address and SN of the MDU are displayed only on the OLT and U2000. MDUs
are differentiated according to their IP addresses in the OSS.
l The on-site construction is simple and no configuration data is required.
l The version and configuration data can be restored automatically.
Issue 03 (2010-11-19)
Figure 16-3 shows the flowchart for quickly replacing an MDU.
Figure 16-3 Flowchart for quickly replacing an MDU

CAUTION
Make sure that any of the FTP, TFTP, and SFTP services are running.
16-5
Procedure
1 Set the automatic backup policy.
1. Choose Administration > NE Software Management > User-Defined Policy from the
main menu.
2. In the User-Defined Policy dialog box, set NE Type and NE Version, and click Next, as
shown in Figure 16-4.
Figure 16-4 User-defined policy (1)

3. In the User-Defined Policy dialog box, set parameters on the Backup Policy and Save
Policy tab pages as required, and click Finish, as shown in Figure 16-5.
Issue 03 (2010-11-19)

2 (Optional) Set the automatic upgrade policy.
For details, see 17.3.1 Upgrading MDUs in Batches Automatically.
3 On-site engineers replace the ONU.
4 In the U2000 window, right-click the new ONU that is used to replace the faulty ONU, such as
MA5620E, and choose EPON Option > Replace ONU from the shortcut menu.
5 In the Replace ONU dialog box, click the Basic Info tab, set Auth Way to MAC Address in
the Auth Info field, and then click next to MAC.
6 In the MAC Address List dialog box, select a record and click OK.
7 In the Replace ONU dialog box, click the Basic Info tab and click OK.
CAUTION
After the MDU is powered on, the U2000 automatically registers the MDU, and restores the
version and configuration data of the MDU.
----End
16-7
17 Predeploying xPON MDUs
About This Chapter
Context
xPON MDUs are classified into GPON MDUs and EPON MDUs. Generally, GPON MDUs use
SNs for authentication and EPON MDUs use MAC addresses for authentication.
Predeploying an xPON MDU is applicable to the following scenarios:
l In one scenario, the MAC address or SN of the MDU is known. Specifically, the mapping
between the MAC address or SN and the IP address of the MDU is planned. Then,
installation engineers must comply with the plan to install the MDU in a specified place.
Figure 17-1 shows the flowchart for predeploying the MDU whose MAC address or SN
is known.
Operation Guide for ONU NE Management 17 Predeploying xPON MDUs
17-1
Figure 17-1 Flowchart for predeploying the MDU whose MAC address or SN is known

l In the other scenario, the MAC address or SN of the MDU is unknown. Specifically, the
IP address is planned but the mapping between the IP address and the MAC address or SN
of the MDU is unknown. Then, installation engineers need to write down the MAC address
or SN of the MDU after installing the MDU and provide the MAC address or SN to the
network management center (NMC). In this case, an NMC engineer binds the IP address
and the MAC address or SN. Figure 17-2 shows the flowchart for predeploying the MDU
whose MAC address or SN is unknown.
Figure 17-2 Flowchart for predeploying the MDU whose MAC address or SN is unknown
Issue 03 (2010-11-19)

17-3
17.1 Example Network of xPON MDU Pre-deployment
When predeploying an xPON MDU, ensure that the OLT applies channel configurations to the
MDU after the optical path between the OLT and the MDU is enabled. In this case, the U2000
can manage the MDU.
Context
Figure 17-3 shows an example network of xPON MDU pre-deployment.
Figure 17-3 Example network of xPON MDU pre-deployment
17.2 Configuration Flow of xPON MDU Pre-deployment
This topic describes how to predeploy an xPON MDU. Predeploying an xPON MDU is divided
into two phases: MDU auto-discovery and MDU auto-configuration. Basic parameters are set
in the MDU auto-discovery phase to meet the requirements for MDU auto-configuration. By
using the MDU auto-configuration function, the upgrade and service data configuration of the
MDU are automatically configured after the MDU is powered on. In this case, the MDU can
carry services immediately after power-on.
Issue 03 (2010-11-19)
Context
The following section describes the flow of how to predeploy an xPON MDU for the first time.
In addition, the flow for expanding MDUs is included in this flow. You can select the steps
according to the requirements.
1. Import the software file of an MDU to the NE software and configure the MDU upgrade
policy. A large number of MDUs of different versions can be upgraded to the specified
version automatically according to the specified area and type during the deployment after
the MDU upgrade policy is configured. For details, see 17.3.1 Upgrading MDUs in
Batches Automatically.
2. Add an OLT to the U2000. The prerequisite for predeploying an MDU is that an OLT must
be added to the U2000 and the OLT data configured on the U2000 is the same as the data
configured on the OLT. For details, see 17.3.2 Adding an OLT to the U2000.
3. Create the global profile referenced in the network planning sheet. For details, see 17.3.3
Creating a Global Profile Referenced in the Network Planning Sheet. The global profile
can be created by
l Adding the global profile manually.
l Generating the global profile based on an NE profile.
4. Fill in the network planning sheet according to the data plan and import the sheet into the
U2000. For details, see 17.4.1 Filling In a Network Planning Sheet and 17.4.2 Importing
a Network Planning Sheet.
5. Bind the MAC address or SN reported by the MDU to the IP address of the MDU. For
information on how to predeploy an MDU whose MAC address or SN is unknown, see
17.4.3 (Optional) Binding a MAC Address or SN to the MDU.
6. Check whether the MDU is predeployed successfully after the MDU is powered on. For
details, see 17.5.1 Viewing a Pre-deployment Task and the Result.
7. Predeploy the MDU again if the pre-deployment fails. For details, see 17.5.2 Predeploying
an MDU or ONT Again.
Figure 17-4 shows the flowchart for predeploying an xPON MDU.
17-5
Figure 17-4 Flowchart for predeploying an xPON MDU
Configure the profile
referenced in the network
planning sheet
Fill in the network planning
sheet
Start
Configure an automatic
MDU upgrade
Add the OLT to the U2000
Check whether the MDU is
predeployed successfully
Import the network planning
sheet
End
Yes
Predeploy the MDU again
No
(Optional) Bind the MAC
address or SN of the MDU
and the IP address of the
MDU

17.3 Preparation
During this phase, you need to make sure that the devices run in the normal state and configure
the profiles that the predeployment profile references.
17.3.1 Upgrading MDUs in Batches Automatically
This topic describes how to upgrade an MDU remotely on the U2000. After an MDU is powered
on, the U2000 compares the type and version of the MDU with those in the configured policy
for automatic MDU upgrade. If the MDU version is different from the target version in the
automatic upgrade policy, the U2000 creates an automatic upgrade task to automatically upgrade
the MDU. If the MDU is new to the U2000 (the information about the vendor and type of the
MDU does not exist on the U2000), the U2000 automatically creates a null upgrade policy.
17.3.2 Adding an OLT to the U2000
Issue 03 (2010-11-19)
This topic describes how to add an OLT to the U2000 before importing the MDU network
planning sheet.
17.3.3 Creating a Global Profile Referenced in the Network Planning Sheet
You can select a global profile in the Default Value Policy worksheet of the network planning
sheet only after the global profile is configured on the U2000.
17.3.1 Upgrading MDUs in Batches Automatically
This topic describes how to upgrade an MDU remotely on the U2000. After an MDU is powered
on, the U2000 compares the type and version of the MDU with those in the configured policy
for automatic MDU upgrade. If the MDU version is different from the target version in the
automatic upgrade policy, the U2000 creates an automatic upgrade task to automatically upgrade
the MDU. If the MDU is new to the U2000 (the information about the vendor and type of the
MDU does not exist on the U2000), the U2000 automatically creates a null upgrade policy.
Configuring the FTP, SFTP, or TFTP Service (Windows)
Context
l The third-party tool must be started after the FTP, SFTP, or TFTP server is configured.
l The file transfer parameters set on the U2000 must be the same as the parameters set on
the FTP, SFTP, or TFTP server.
Procedure
l Configuring the FTP server by using the third-party tool wftpd32.exe
1. Copy the wftpd32.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, choose Security > Users/rights and create a user;
choose Security > Host/net and enter the IP address of the FTP server.
l Configuring the SFTP server by using the third-party tool msftpsrvr.exe
1. Copy the msftpsrvr.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, create a user.
17-7
l Configuring the TFTP server by using the third-party tool tftpd32.exe
1. Copy the tftpd32.exe file to the U2000 server and double-click the file.
2. In the dialog box that is displayed, set the root directory and the IP address of the
TFTP server.
software
1. Choose Administration > Software Management > FTP Settings from the main
menu.
Issue 03 (2010-11-19)
NOTE
service.
17-9
4. Click OK.
----End
Command Reference
To... Run the Command... In...
Configure
the file server
file-server Privilege mode

Importing the MDU Software File
This topic describes how to import the MDU software file from the U2000 server or client to
the NE software library for management. The MDU software files that the upgrade policy is
applicable to include the software package file, upgrade file, and voice file (including the
Voice file, Profile file, and digitmap file).
Prerequisite
The FTP, SFTP, or TFTP service must be configured and the xFTP service must be started and
be running. For details, see Configuring the FTP, SFTP, or TFTP Service (Windows).
Procedure
1 Choose Administration > NE Software Management > NE Software Library
Management from the main menu.
2 In the list, right-click and choose Import from the shortcut menu.
3 In the dialog box that is displayed, configure the target software upgrade package of the MDU.
Issue 03 (2010-11-19)
NOTE
If a patch needs to be installed for the device of the corresponding version, import the patch file first. For details,
see the release notes for the patch.
In the Version field, enter the target version. Ensure that the target version is the same as the target version of
the MDU.
4 Click OK.
----End
Command Reference
Query the language and
current version of the MDU
display language Common user mode

Configuring the ONU Upgrade Policy
When a plug-in/plug-out MDU is powered on, or a faulty MDU is replaced with a new one, you
can configure the MDU policy to upgrade the NE(s) automatically. When an ONU is powered
on, the U2000 automatically compares the current version of the ONU with the target version
in the ONU upgrade policy. If the current version of the ONU is different from the target version
in the ONU upgrade policy, the U2000 automatically upgrades the ONU to the target version.
If a voice file exists in the software library, the U2000 also loads the voice file when upgrading
the ONU.
Prerequisite
l The NE software must work in the normal state and the NE software process must be started.
l The U2000 must work in the normal state.
l The software package has been imported to the software library.
17-11
Procedure
l Path one:
1. Choose Administration > NE Software Management > Auto Upgrade Policy from
the main menu.
2. In the window that is displayed, choose the required branch according to the type of
the NE to be upgraded from the navigation tree in the left pane. Then, select the
required NE type from the NE list in the right pane.
3. Click Configure Upgrade Version next to the selected NE type. In the dialog box
that is displayed, select the required version from the Upgrade Version drop-down
list and select the load file. Click OK.
NOTE
After you select the required version from the Upgrade Version drop-down list, the NE software
management module automatically imports the patch or package file that matches the version from
the software library.
4. Click OK.
5. After the ONU upgrade policy is configured, the NE software automatically creates
an upgrade task. Choose Administration > NE Software Management > NE
Upgrade Task Management from the main menu. On the NE Upgrade Task
Management tab page, view the task information.
l Path two:
1. Choose Configuration > FTTx Service Pre-Deployment > Configure MDU
Upgrade Policy from the main menu.
2. In the dialog box that is displayed, choose the type of the NE to be upgraded. Then,
select the required NE from the list, right-click, and then choose Modify Policy.
3. In the dialog box that is displayed, set Policy Status to Run, select the required version
from the Target Version drop-down list and the load file.
NOTE
After you select the required version from the Target Version drop-down list, the NE software
management module automatically imports the patch or package file that matches the version from
the software library.
4. Click OK.
----End
Result
After the configuration, the upgrade policy is automatically run in the following circumstances:
l When a plug and play MDU is powered on, the U2000 automatically upgrades it to the
target version according to the policy.
l After a faulty MDU is replaced with a new one, the U2000 automatically rolls back it to
the original version before the fault occurs according to the policy.
Choose Administration > Task Schedule > Scheduling Center from the main menu. On the
Scheduling Center tab page, view the execution status of the task.
planning sheet.
Issue 03 (2010-11-19)
Prerequisite
l The inband or outband IP address and SNMP parameters of the OLT and the route between
the OLT and the U2000 must be set.
l The FTP service of the U2000 server must be started in the normal state. For details, see
Configuring the FTP, SFTP, or TFTP Service (Windows).
Context
If the OLT has been added to the U2000, to ensure that the data on the U2000 is the same as the
data on the OLT, right-click the OLT in the Main Topology and choose Synchronize NE
Data from the shortcut menu.
Procedure
1 In the Main Topology, choose Physical Root or an NE from the navigation tree, right-click in
the topology view in the right pane, and then choose New > NE from the shortcut menu.
2 In the dialog box that is displayed, set the parameters such as the IP address and name of the
NE.
3 Click OK.
----End
17.3.3 Creating a Global Profile Referenced in the Network
Planning Sheet
17-13
Context
You can create a global profile that is referenced in the network planning sheet by
l Adding the global profile manually.
l Generating the global profile based on an NE profile.
Procedure
l Adding a global profile manually
Function Global Profile Remarks
Profiles to be added in
GPON profile mode
l 19.1.1 Configuring an
MDU SNMP Profile
l 19.1.2 Configuring a DBA
Profile
l 19.1.3 Configuring a
GPON Line Profile
These profiles must be
applied to the OLT.
MEF IP Traffic Profile
Program Profile
l 19.2.9 Adding a Multicast
Rights Profile
l 19.3.9 Adding an MGC
Profile
UAS Profile
l 19.3.11 Adding a TID
Profile
-
Issue 03 (2010-11-19)
GPON discrete mode
MDU SNMP Profile
l Configuring an ONT
Capability Profile
Profile
An ONT capability
profile must match the
hardware capability of
the ONT to which the
profile is bound.
Otherwise, certain
configuration data
cannot be applied.
The global profile of the
ONT capability profile
must be configured on
the U2000. In addition,
the same ONT capability
profile must be created
on the U2000 and OLT.
Otherwise, the network
planning sheet cannot be
imported into the U2000.
applied to the OLT.
Program Profile
Rights Profile
Profile
UAS Profile
Profile
-
EPON profile mode
MDU SNMP Profile
Profile
l 23.1.3 Configuring a Line
Profile
applied to the OLT.
17-15
Program Profile
Rights Profile
Profile
UAS Profile
Profile
-

l Generating a global profile based on an NE profile
This section considers the EPON DBA profile as an example to describe how to generate
a global profile based on an NE profile. The procedures for operating all profiles are the
same but differ in the navigation path.
2. Choose Configuration > Access Profile Management > EPON Profile from the
main menu.
3. Click the DBA Profile tab.
4. Right-click the required profile in the list and choose Generate Global Profile from
the shortcut menu.
5. In the dialog box that is displayed, click OK.
----End
17.4 Operations on Sheets
During this phase, you need to perform relevant operations on sheets.
17.4.1 Filling In a Network Planning Sheet
This topic describes how to obtain and fill in a network planning sheet. In addition, this topic
describes the contents of the sheet. A network planning sheet can be imported into the U2000
after you fill in the sheet correctly.
17.4.2 Importing a Network Planning Sheet
The predeployed NE is generated on the U2000 after you import a network planning sheet into
the U2000.
17.4.3 (Optional) Binding a MAC Address or SN to the MDU
The Authentication Information parameter is optional in the network planning sheet. If the
MAC address or SN of an MDU is unknown, you need to bind the MAC address or SN and the
IP address of the MDU after the MDU goes online and is auto-discovered. Then, you can apply
the predeployed data to the MDU on the U2000.
Issue 03 (2010-11-19)
Prerequisite
The global profile that has the same name as the profile whose name is filled in the sheet must
exist on the U2000. For information on how to configure the profile, see 17.3.3 Creating a
Global Profile Referenced in the Network Planning Sheet.
Procedure
1 Obtain the network planning sheet from the installation path of the U2000.
The name of the network planning sheet is Networking Planning Sheet (xPON).xls, where x
represents G or E. The paths to the network planning sheet vary with the types of the operating
systems (OSs), as follows:
l Windows-based server: X:\U2000\client\template\MDU Pre-Deploy\en\, where x
indicates the name of the disk, such as D, E, and F.
l Solaris-based server: /opt/U2000/client/template/MDU Pre-Deploy/en
NOTE
The network planning sheet is forward compatible. To learn the instructions on how to use the network planning
sheet and the precautions, open the network planning sheet and read the contents in Instructions.
2 Double-click a blank network planning sheet and fill in the sheet.
NOTE
Configure IPTV services instead of broadband services in the Data Plan worksheet if the broadband
services and IPTV services use the same service stream.
l The Data Plan worksheet contains parameters particular to an MDU to be predeployed.
These parameters can be classified into two parts: ONU Management Information and
E2E Service Channel Data.
NOTE
Parameter settings in ONU Management Information of an ONU must be unique and
cannot conflict with other ONUs. The parameters include ONU ID, ONU Description
(ONU name displayed on the U2000), ONU Management IP Address, and
Authentication Information. If the MAC address or SN of the ONU is unknown, the
authentication information can be blank.
An E2E service channel is used by the U2000 to manage the MDU. You can deploy
services such as broadband and IPTV services after the E2E service channel is set up and
the MDU goes online and becomes stable.
l The Default Value Policy worksheet defines Management Channel Parameters, GEM
Port Channel Parameters, OLT Service Channel, ONU Service Channel, Voice IP
Address Pool, Voice Service (H.248, SIP, and MGCP), and Multicast User. These
parameters are effective in the entire network.
l In the Data Plan worksheet of the network planning sheet, select an ONU type from the
ONU Type drop-down list. In the dialog box that is displayed, click OK. Then, a worksheet
17-17
is automatically generated for the ONU in the network planning sheet. This is the worksheet
of the common command configuration script.
NOTE
The contents in the common command configuration script are the same as the commands on the ONU. This
worksheet collects certain common scripts for editing and then applying to the ONU. You can copy the
edited commands to the common command configuration script.
By default, some prepositive common commands and postpositive common commands are generated when
you generate the resource planning sheet.
Key
Parameter
Description
the execute
mode of
command
configurati
on script
Indicates that the command configuration script is run in file loading mode
or Telnet mode in the network planning sheet.
the
prepositive
common
command
configurati
on script
Specifies the operations contained in the command prescript. For example,
the creation of an ADSL line profile can be specified in the prescript because
the creation is not supported in the network planning sheet.
Such as the commands that are used to configure security policies and access
control list (ACL), are saved in the prepositive common command
configuration script.
NOTE
By default, some prepositive common commands are generated when you edit the
network planning sheet.
the
postpositiv
e common
command
configurati
on script
Specifies the commands that must be executed after data configuration.
NOTE
By default, some postpositive common commands are generated when you edit the
network planning sheet.

3 After filling in the network planning sheet, click Verify Data in the Data Plan worksheet to
verify the contents in the worksheet.
Issue 03 (2010-11-19)
NOTE
If an error exists in the network planning sheet, the cause of the error is provided in the blank area at the end of
the line.
The data verification performed by the network planning sheet is not complete. To ensure data accuracy, it is
recommended that you check the contents carefully.
----End
Other Operations on the Planning Sheet
Button Description
Generate Network Deployment Sheets for
Deployment
Generate Network Deployment Sheets for
Service Capacity Expansion
Exports the data plan to Resource
Deployment Sheet.
User Define Sheetform Displays the customized operations on the
U2000 and broadband, IPTV, VoIP, and
reserved services. If you select certain
parameters, these parameters are displayed in
the Data Plan and Default Value Policy
worksheets. In addition, the parameters that
are not selected are hidden after you
customize the operations.
Clear Form Clears the data in the current worksheet.
Add a Row Adds an empty row above the row where the
cursor points in the current worksheet.
Delete a Row Deletes the row where the cursor points from
the current worksheet.
Show Comments/Hide Comments Displays or hides remarks. In the Data Plan
worksheet, the remarks, including the
definition, range, navigation path of each
parameter and the information about whether
the parameter is mandatory or not, are
provided in the cell above the parameter. You
can click View Remarks or Hide Remarks
to display or hide the remarks.
Chinese/English Switches the language of the descriptions in
the table between Chinese and English.

the U2000.
17-19
Prerequisite
l The preparations must be complete. For details, see 17.3.1 Upgrading MDUs in Batches
Automatically, 17.3.2 Adding an OLT to the U2000, and 17.3.3 Creating a Global
Profile Referenced in the Network Planning Sheet.
l The dependent processes of subtasks must be started. The names of the relevant processes
are Access Device Common Service, Access Device Manager, Profile Manager, and
xFtpWatcher Process.
Procedure
1 Choose Configuration > FTTx Service Pre-Deployment > Import Network Deployment
Sheets from the main menu.
2 In the dialog box that is displayed, select the network planning sheet to be deployed and click
Open.
3 After importing the network planning sheet, click OK.
4 The U2000 automatically performs the pre-deployment task after the MDU is powered on.
Choose Administration > Task Schedule > Scheduling Center from the main menu. Then,
you can view the execution status of the pre-deployment task.
NOTE
Two types of pre-deployment tasks are displayed in the scheduling center, that is, OLT tasks and ONU tasks.
For example, when two MDUs are deployed on an OLT, three tasks are displayed in the scheduling center, that
is, one deployment task of the OLT and two deployment tasks of the MDUs.
----End
17.4.3 (Optional) Binding a MAC Address or SN to the MDU
The Authentication Information parameter is optional in the network planning sheet. If the
MAC address or SN of an MDU is unknown, you need to bind the MAC address or SN and the
IP address of the MDU after the MDU goes online and is auto-discovered. Then, you can apply
the predeployed data to the MDU on the U2000.
Prerequisite
l The auto-discovery of the xPON port must be enabled. For details, see Confirming a
GPON MDU or Confirming an EPON MDU.
Procedure
l Binding the SN and IP address of a GPON MDU if the MDU uses the SN for
authentication
1. Choose Configuration > FTTx Service Pre-Deployment > GPON MDU Batch
Bind SN from the main menu.
2. In the dialog box that is displayed, enter the IP address of the MDU to which the SN
is bound in the IP field, and select SN that the construction engineer on site provides
from the SN drop-down list.
3. Click OK.
l Binding the MAC address and IP address of an EPON MDU if the MDU uses the
MAC address for authentication.
Issue 03 (2010-11-19)
1. Choose Configuration > FTTx Service Pre-Deployment > EPON MDU Batch
Bind MAC from the main menu.
2. In the dialog box that is displayed, enter the IP address of the MDU to which the MAC
address is bound in the MDU Management IP field, and select the MAC address that
the construction engineer on site provides from the MAC drop-down list.
3. Click OK.
----End
17.5 Acceptance
During this phase, you need to perform an acceptance test on the predeployment task.
17.5.1 Viewing a Pre-deployment Task and the Result
Viewing a pre-deployment task and the service data of the predeployed MDU helps you
determine whether the MDU is predeployed successfully.
17.5.2 Predeploying an MDU or ONT Again
You need to find out the failure cause if an MDU or ONT fails to be predeployed. Then, import
the network planning sheet into the U2000 again. Then, the U2000 automatically performs the
MDU pre-deployment task.
Viewing a pre-deployment task and the service data of the predeployed MDU helps you
determine whether the MDU is predeployed successfully.
Procedure
l Viewing a pre-deployment task in the scheduling center
1. Choose Administration > Task Schedule > Scheduling Center from the main menu.
2. On the tab page that is displayed, choose Deployment Task from the navigation tree.
In the task list, select a task and view the details.
3. If the scheduling of a pre-deployment task fails, click the Log Info tab, right-click the
failed task and choose Log Details from the shortcut menu. Then, you can view the
details in logs.
17-21
l Viewing the service data of the predeployed MDU
Navigate to the MDU NE to view the application status of service data and determine
whether the MDU is predeployed successfully. Only the NE management data of the MDU
will be synchronized in the MDU pre-deployment to improve upgrade efficiency.
Therefore, the NE data of the predeployed MDU must be synchronized before you view
the service data of the MDU.
1. In the Main Topology, right-click the required MDU in the Physical Root navigation
tree and choose Synchronize NE Data from the shortcut menu.
2. Double-click the MDU node to verify the service data after the NE data is
synchronized.
----End
Context
l The data of previously predeployed OLT, MDU, or ONT will be deleted automatically
when you predeploy them again.
Issue 03 (2010-11-19)
l Predeploying an OLT, MDU, or ONT again will be slow because the data of the previously
previous deployed data needs to be deleted when you predeploy them again.
Table 17-1 describes the common problems and solutions to network planning sheets.
Table 17-1 The common problems and solutions to network planning sheets
Common Problem Solution
The system displays an error
message "Name of the ONT
capability profile repeats the
default profile name ranging
from ont-profile_1 to ont-
profile_128" when you import
the network planning sheet into
the U2000.
This problem can be resolved by changing the profile
name.
The MDU does not allow the U2000 to apply a profile
named by following the default naming rules, such as the
ONT capability profile and DBA profile, to the MDU. If
you need to use the profile named by following the default
naming rules, create this profile on the MDU directly,
synchronize the profile to the U2000, and then generate a
global profile from the NE profile.
The system displays the message
"Network transmission times out.
Please try again later" when you
import the network planning
sheet to the U2000 and verify the
service data of the MDU.
This problem can be resolved by importing the network
planning sheet again into the U2000.
You need to check the memory usage of the server.
Increase the memory to prevent this problem from
occurring again if the available memory is less than 4 GB.
"Device name contains invalid
characters" when you import the
network planning sheet into the
U2000 and verify the service data
of the MDU.
You need to check and ensure that the device name in the
network planning sheet does not contain any unsupported
special characters.

Table 17-2 describes the common problems occurred when tasks are performed on the OLT and
solutions to these problems.
Table 17-2 The common problems occurred when tasks are performed on the OLT and solutions
to these problems
"The subitem resource is
insufficient so that the task
stopped" when the tasks are
performed on the OLT. After you
click the Log Info tab and
double-click the failed task to
view the failure cause, the
message "VLAN already exists"
is displayed.
To resolve this problem, change the type and attribute of
this VLAN on the OLT and ensure that the VLAN type
and attribute are the same as those of the predeployed
VLAN.
This problem occurs because the OLT already has a
VLAN that has the same VLAN ID but different VLAN
type and attribute from the VLAN preset in the network
planning sheet.
17-23
When performing the subtask of
deploying service virtual ports in
the process of MDU pre-
deployment, the system displays
the message "Database operation
failed."
This problem occurs because the data on the U2000 and
MDU is different. If the system displays this message
when performing an OLT task, synchronize the service
virtual port data of the OLT and import the network
planning sheet into the U2000 again; if the system
displays this message when performing an MDU task,
delete the MDU and import the network planning sheet
again.
"The message transmitted by
MDP failed" in the process of
performing an OLT task when
you predeploy an MDU again.
To resolve this problem, check and ensure that the
processes relevant to the subtasks of the pre-deployment
are started.

Table 17-3 describes the common problems occurred when tasks are performed on the MDU
and solutions to these problems.
Table 17-3 The common problems occurred when tasks are performed on the MDU and
stopped" when the Synchronize
physical resource data of NE
task is performed.
To resolve this problem, choose Administration >
Settings > xFtpWatcher from the main menu and ensure
that the status indicator is green.
The system displays a failure and
the message "Incorrect
parameter" is recorded in logs
when the Import network
planning sheet of service
virtual ports task is performed.
To resolve the problem, ensure that the service virtual
ports of xDSL ports are configured with VPIs and VCIs.

Procedure
2 In the dialog box that is displayed, select the modified network planning sheet and click
Open.
3 Click Finish after the network planning sheet is imported into the U2000.
----End
Issue 03 (2010-11-19)
17.6 Configuration Example of xPON MDU Pre-deployment
This topic considers the scenario wherein a GPON MDU (MA5620G) is connected to an OLT
as an example to describe how to predeploy an xPON MDU.
Prerequisite
l This configuration example describes only how to predeploy an xPON MDU. For
information about MDU automatic upgrade, see 17.3.1 Upgrading MDUs in Batches
Automatically.
l The OLT must be in profile mode.
l This topic considers the scenario wherein the SN of the xPON MDU is unknown as an
example.
l This topic considers the Windows-based server as an example.
l This topic considers broadband and narrowband services as examples.
NOTE
Context
Table 17-4 and Table 17-5 provide the data that must be planned in the network planning sheet.
Table 17-4 Data plan in the preparation phase
Configura
tion Item
Data Plan Remarks
U2000
server
192.168.50.17 The U2000 server needs to use ports
23, 8080, 9801, and 9803. Therefore,
ensure that these ports are enabled on
the firewall so that the U2000 server
can communicate with NEs
successfully.
OLT l IP Address: 192.168.20.100
l Management mode: inband
l Upstream port: 0/0/1
l Upstream VLAN: 1000
l GPON port: 0/5/0
The upstream VLAN is the same as
the native VLAN of the upstream
port.
Profile
referenced
in a network
planning
sheet
DBA profile
l Name: dba-profile_mdu
l Bandwidth Compensation: Yes
l Accept the default values for other
parameters.
-
17-25
Configura
tion Item
Data Plan Remarks
Line profile
l Name: line-profile_mdu
l Mapping Mode: VLAN
l Qos Mode: Priority Queue
l T-CONT Index: 1
l DBA Profile Name: dba-
profile_mdu
l GEM Port Index: 1
parameters.
-
MDU SNMP profile
l Name: snmpprofile
l SNMP Version: v1
l Read Name: public
l Write Name: private
l Trap Host IP: 192.168.50.17
l Trap UDP Port: 162
l SNMP Security Name: public
-
MEF IP traffic profile
l Name: traffic-profile_1
l CIR: 64Kbit/s
l Outer Priority: 1
parameters.
-
MGC Profile
l Name: mgcprofile1
l Protocol Type: H.248
l IP Address1: 200.200.200.200 (IP
address of the MGC)
l UTP/SCTP Port Number: 2944
-
TID Profile
l Name: tid-profile_1
l Format: %u
l Parameter List: r
A TID profile must be used when
termination IDs are configured
hierarchically.

Issue 03 (2010-11-19)
Table 17-5 Data plan in a network planning sheet
Configura
tion Item
Data Plan Remarks
Data Plan l OLT IP Address: 192.168.20.100
l PON Port: 0/5/0
l ONU ID: 0
l ONU Description: Building F in
company B, City S
l ONU Type: MA5620G
l ONU Management IP Address:
192.168.20.10
l ONU Management IP Mask: 24
l ONU Gateway: 192.168.20.1
l Network Management
GEMPORT: 1
CVLAN: 100
SVLAN: 100
l Boardband
GEMPORT: 1
CVLAN: 1001
SVLAN: 1001
l VoIP
GEMPORT: 1
CVLAN: 2000
SVLAN: 2000
Voice Address Mode: static IP
Voice IP Address:
10.121.68.28
Voice IP Mask: 24
Voice Gateway: 10.121.68.1
MGC Domain Name:
001882D4C6FE-BGW
-
17-27
Configura
tion Item
Data Plan Remarks
Default
Value
Policy
l Management Channel Parameters
ONU Type: MA5620G
Authentication Mode: SN
Line Profile Name: line-
profile_mdu
MxU SNMP Profile Name:
snmpprofile
IP Address of the U2000 Static
Route: 192.168.20.17
IP Mask of the U2000 Static
Route: 24
Management Mode: SNMP
Mapping Mode: VLAN
l GEM Port Channel Parameters:
Create a GEM port whose Service
Name is Broadband and a GEM
port whose Service Name is
Voice in the same way.
Service Name: Network
Management
Service Type: ETH
Encryption Switch: off
Subtending Switch: off
T-CONT ID: 1
DBA Profile Name: dba-
profile_mdu
l OLT Service Channel: Create an
OLT service channel whose
Service Name is Broadband and
an OLT service channel whose
Service Name is Voice in the
same way. Do not set the names of
the upstream traffic profile and
downstream traffic profile for the
OLT service channel of voice
services.
Service Name: Network
Management
SVLAN Type: smart
SVLAN Attribute: Common
SVLAN Upstream Port: 0/19/0
Upstream Traffic Control
Profile: traffile_profile_1
-
Issue 03 (2010-11-19)
Configura
tion Item
Data Plan Remarks
Downstream Traffic Control
l ONU Service Channel: Create an
ONU service channel whose
Service Name is Voice in the
same way. Do not set the names of
the upstream traffic profile and
downstream traffic profile, VPI,
and VCI for the OLT service
channel of voice services.
ONU Type: MA5620G
Service Name: Broadband
CVLAN Type: smart
CVLAN Attribute: Common
CVLAN Upstream Port: 0/0/1
VPI: 8
VCI: 35
l VoIP IP Address Pool
ONU Type: MA5620G
IP Type: Media
QoS Policy: TOS
IP Priority: 0
TOS: 0
l H.248 Voice Service
ONU Type: MA5620G
MID Type: MG Domain Name
Protocol Port Number: 2944
Transmission Mode: UDP
Name of the Active MGC
Profile: mgcprofile1
Profile Index: 5
Start Negotiation Version
Number: Depend on profile
RTP Terminal Prefix: A
Name of the TID Profile Used
by the RTP: tidprofile1
17-29
Configura
tion Item
Data Plan Remarks
MA5620G the execute mode of command
configuration script: File
-

Procedure
1 Adding an OLT to the U2000 (For details, see 17.3.2 Adding an OLT to the U2000.)
1. In the Main Topology, choose Physical Root or an NE from the navigation tree, right-click
in the topology view in the right pane, and then choose New > NE from the shortcut menu.
l IP Address: 192.168.20.100
l Device Name: 192.168.20.100-MA5680T
3. Click OK.
2 Configuring the profile referenced in the network planning sheet (For details, see 17.3.3
Creating a Global Profile Referenced in the Network Planning Sheet.)
1. Configuring a DBA profile. (For details, see 19.1.2 Configuring a DBA Profile.)
main menu.
b. Click the DBA Profile tab.
c. Right-click and choose Add Global Profile from the shortcut menu.
l Name: dba-profile_mdu
l Accept the default values for other parameters.
e. Click OK.
f. In the information list, right-click the record and choose Download to NE from the
shortcut menu.
g. In the dialog box that is displayed, select the required NE(s), and click OK.
2. Configuring a line profile (For details, see 19.1.3 Configuring a GPON Line Profile.)
In this example, the mapping between GEM ports and MDU-side services is implemented
through VLANs, and the service streams of each service are mapped to GEM port 1. In
addition, different GEM connections are set up for the management VLAN and the VLANs
for the Internet, multicast, and voice services.
main menu.
b. Click the Line Profile tab.
l Set Name to FTTx.
Issue 03 (2010-11-19)
l Choose Base Info. from the navigation tree and set the parameters.
Mapping Mode: VLAN
Qos Mode: Priority Queue
l Right-click T-CONT Info. in the navigation tree and choose ADD T-CONT from
the shortcut menu. In the dialog box that is displayed, set the parameters.
T-CONT Index: 1
DBA Profile: dba-profile_mdu
l Right-click T-CONT1 in the navigation tree and choose Add GEM Port from the
shortcut menu. In the dialog box that is displayed, set the parameters.
GEM Port Index: 1
Priority Queue: 1
l Right-click GEM Port1 in the navigation tree and choose Add GEM
Connection from the shortcut menu. In the dialog box that is displayed, set the
parameters.
GEM Connection Index: 0 (this parameter is set to 0 automatically)
VLAN ID: 4000 (management VLAN ID)
Priority: 1
parameters.
VLAN ID: 1001 (VLAN ID of the Internet service)
Priority: 2
parameters.
VLAN ID: 2000(VLAN ID of the voice service)
Priority: 1
e. Click OK.
shortcut menu.
3. Configuring an MDU SNMP profile (For details, see 19.1.1 Configuring an MDU
SNMP Profile.)
a. Choose Configuration > Access Profile Management > MDU SNMP Profile from
the main menu.
b. Click the MDU SNMP Profile tab.
l Name: snmpprofile
l SNMP Version: v1
l Read Name: public
17-31
l Trap Host IP: 192.168.50.17 (IP address of the U2000 server)
l SNMP Security Name: public
e. Click OK.
shortcut menu.
4. Configuring an MEF IP traffic profile (For details, see 19.2.2 Configuring an MEF IP
Traffic Profile.)
a. Choose Configuration > Access Profile Management > Traffic Profile from the
main menu.
b. Click the MEF IP Traffic Profile tab.
l Name: traffile_profile_1
l CIR: 20480
l Outer Priority: 1
e. Click OK.
5. Configuring an MGC profile (For details, see 19.3.9 Adding an MGC Profile.)
a. Choose Configuration > Access Profile Management > MGC Profile from the main
menu.
l Name: mgcprofile1
l IP Address1: 200.200.200.200 (IP address of the MGC)
l UTP/SCTP Port Number: 2944
d. Click OK.
6. Configuring a TID profile (For details, see 19.3.11 Adding a TID Profile.)
a. Choose Configuration > Access Profile Management > TID Profile from the main
menu.
l Name: tid-profile_1
l Format: %u
l Parameter List: r
d. Click OK.
3 Filling in the network planning sheet (For details, see 17.4.1 Filling In a Network Planning
Sheet.)
Issue 03 (2010-11-19)
1. Navigate to the path X:\U2000\client\template\MDU Pre-Deploy\en\ on the Windows-
based server, and double-click the Network Planning Sheet(GPON).xls file.
2. In the Data Plan sheet, set the parameters as follows:
l OLT IP Address: 192.168.20.100
l PON Port: 0/5/0
l ONU ID: 0
l ONU Description: Building F in company B, block L, City S
l ONU Type: MA5620G
l ONU Management IP Address: 192.168.20.10
l ONU Management IP Mask: 24
l ONU Gateway: 192.168.20.1
l Network Management
GEMPORT: 1
CVLAN: 100
SVLAN: 100
l Broadband
GEMPORT: 1
CVLAN: 1001
SVLAN: 1001
l VoIP
GEMPORT: 1
CVLAN: 2000
SVLAN: 2000
Voice IP Address: 10.121.68.28
Voice IP Mask: 24
MGC Domain Name: 001882D4C6FE-BGW
3. In the Default Value Policy sheet, set the parameters as follows:
l Management Channel Parameters
ONU Type: MA5620G
Line Profile Name: line-profile_mdu
MxU SNMP Profile Name: snmpprofile
IP Address of the U2000 Static Route: 192.168.20.17
IP Mask of the U2000 Static Route: 24
Management Mode: SNMP
Mapping Mode: VLAN
l GEM Port Channel Parameters: Create a GEM port whose Service Name is
Broadband and a GEM port whose Service Name is Voice in the same way.
17-33
Service Name: Network Management
Service Type: ETH
Encryption Switch: off
Subtending Switch: off
T-CONT ID: 1
DBA Profile Name: dba-profile_mdu
l OLT Service Channel: Create an OLT service channel whose Service Name is
Broadband and an OLT service channel whose Service Name is Voice in the same
way. Do not set the names of the upstream traffic profile and downstream traffic profile
for the OLT service channel of voice services.
Service Name: Network Management
SVLAN Type: smart
Upstream Traffic Control Profile: traffile_profile_1
Downstream Traffic Control Profile: traffile_profile_1
l ONU Service Channel: Create an ONU service channel whose Service Name is
Voice in the same way. Do not set the names of the upstream traffic profile and
downstream traffic profile, VPI, and VCI for the OLT service channel of voice services.
ONU Type: MA5620G
CVLAN Type: smart
CVLAN Attribute: Common
CVLAN Upstream Port: 0/0/1
VPI: 8
VCI: 35
l VoIP IP Address Pool
ONU Type: MA5620G
IP Type: Media
QoS Policy: TOS
IP Priority: 0
TOS: 0
l H.248 Voice Service
ONU Type: MA5620G
MID Type: MG Domain Name
Protocol Port Number: 2944
Name of the Active MGC Profile: mgcprofile1
Profile Index: 5
Issue 03 (2010-11-19)
Start Negotiation Version Number: Depend on profile
RTP Terminal Prefix: A
Name of the TID Profile Used by the RTP: tidprofile1
4. In the MA5620G sheet, set the execute mode of command configuration script to
File.
5. Choose File > Save from the main menu to save the sheet.
4 Importing the network planning sheet (For details, see 17.4.2 Importing a Network
Planning Sheet.)
1. Choose Configuration > FTTx Service Pre-Deployment > Import Network
Deployment Sheets from the main menu.
2. In the dialog box that is displayed, select Network Planning Sheet(GPON).xls and click
Open.
3. After importing the network planning sheet, click OK.
5 Binding the MDU and its SN (For details, see 17.4.3 (Optional) Binding a MAC Address or
SN to the MDU.)
1. Choose Configuration > FTTx Service Pre-Deployment > GPON MDU Batch Bind
SN from the main menu.
2. In the dialog box that is displayed, enter the IP address of the MDU that is to be bound to
the SN in the MDU Management IP field, and select the SN provided by installation
engineers from the SN drop-down list.
3. Click OK.
----End
Result
See 17.5.1 Viewing a Pre-deployment Task and the Result to determine whether the
MA5626G is predeployed successfully.
17-35
18 Predeploying xPON ONTs
About This Chapter
A large number of ONTs need to be deployed in the xPON FTTH network. ONTs can be bulk
imported into the U2000 by means of a network planning sheet. The bulk operation simplifies
and speeds up the ONT deployment so that the costs of building networks are reduced.
Context
xPON ONTs are classified into GPON ONTs and EPON ONTs.
18.1 Example Network of xPON ONT Pre-deployment
When predeploying an xPON ONT, ensure that the OLT applies channel configurations to the
ONT after the optical path between the OLT and the ONT is enabled. In this case, the U2000
can manage the ONT.
18.2 Configuration Flow of xPON ONT Pre-deployment
This topic describes how to predeploy an xPON ONT. Predeploying an xPON ONT is divided
into two phases: ONT auto-discovery and ONT auto-configuration. Basic parameters are set in
the ONT auto-discovery phase to meet the requirements for ONT auto-configuration. By using
the ONT auto-configuration function, the upgrade and service data configuration of the ONT
are automatically configured after the ONT is powered on. In this case, the ONT can carry
services immediately after power-on.
18.3 Preparation
18.5 Acceptance
18.6 Configuration Example of xPON ONT Pre-deployment
This topic considers the scenario wherein an EPON ONT (850e) is connected to an OLT as an
example to describe how to predeploy an xPON ONT.
Operation Guide for ONU NE Management 18 Predeploying xPON ONTs
18-1
18.1 Example Network of xPON ONT Pre-deployment
When predeploying an xPON ONT, ensure that the OLT applies channel configurations to the
ONT after the optical path between the OLT and the ONT is enabled. In this case, the U2000
can manage the ONT.
Context
Figure 18-1 shows the example network of xPON ONT pre-deployment.
Figure 18-1 Example network of xPON ONT pre-deployment

ONT1
Optical Splitter
LSW
TG
IPTV DHCP Server
U2000
BRAS
VoIP DHCP Server
Router
Multicast source
ONTn
OLT
...
Issue 03 (2010-11-19)
18.2 Configuration Flow of xPON ONT Pre-deployment
This topic describes how to predeploy an xPON ONT. Predeploying an xPON ONT is divided
into two phases: ONT auto-discovery and ONT auto-configuration. Basic parameters are set in
the ONT auto-discovery phase to meet the requirements for ONT auto-configuration. By using
the ONT auto-configuration function, the upgrade and service data configuration of the ONT
are automatically configured after the ONT is powered on. In this case, the ONT can carry
services immediately after power-on.
Context
The following section describes the flow of how to predeploy an xPON ONT for the first time.
In addition, the flow for expanding ONTs is included in this flow. You can select the steps
according to the requirements.
1. Ensure that the OLT is added to the U2000 and the OLT data on the U2000 is the same as
the OLT data on the ONT. For details, see 18.3.1 Adding an OLT to the U2000.
2. You can add a global profile or generate a global profile based on the NE profile. For details,
see 17.3.3 Creating a Global Profile Referenced in the Network Planning Sheet.
3. Fill in the network planning sheet according to the data plan and import the sheet to the
U2000. For details, see 17.4.1 Filling In a Network Planning Sheet and 17.4.2 Importing
a Network Planning Sheet.
4. Check whether the ONT is predeployed successfully after the ONT is powered on. For
details, see 17.5.1 Viewing a Pre-deployment Task and the Result.
5. Predeploy the ONT again if the pre-deployment fails. For details, see 18.5.2 Predeploying
an MDU or ONT Again.
Figure 18-2 shows the flowchart for predeploying an xPON ONT.
18-3
Figure 18-2 Flowchart for predeploying an xPON ONT
Configure the profile
referenced in the network
planning sheet
Fill in the network planning
sheet
Start
Add the OLT to the U2000
Check whether the xPON
ONT is predeployed
successfully
Import the network planning
sheet
End
Yes
Predeploy the xPON ONT
again
No

18.3 Preparation
planning sheet.
18.3.2 Configuring the Profile Referenced in a Network Planning Sheet
planning sheet.
Prerequisite
Issue 03 (2010-11-19)
l The inband or outband IP address and SNMP parameters of the OLT and the route between
the OLT and the U2000 must be set.
l The FTP service of the U2000 server must be started in the normal state. For details, see
Configuring the FTP, SFTP, or TFTP Service (Windows).
Context
If the OLT has been added to the U2000, to ensure that the data on the U2000 is the same as the
data on the OLT, right-click the OLT in the Main Topology and choose Synchronize NE
Data from the shortcut menu.
Procedure
1 In the Main Topology, choose Physical Root or an NE from the navigation tree, right-click in
the topology view in the right pane, and then choose New > NE from the shortcut menu.
2 In the dialog box that is displayed, set the parameters such as the IP address and name of the
NE.
3 Click OK.
----End
18.3.2 Configuring the Profile Referenced in a Network Planning
Sheet
18-5
Context
You can configure a global profile referenced in a network planning sheet by
l Adding a global profile manually.
l Generating a global profile based on an NE profile.
Procedure
l Adding a global profile manually
GPON profile mode
GPON Line Profile
GPON Service Profile
Profile
applied to the OLT.
l 20.2.1 Configuring the
ONT Value-Added
Service Configuration
Profile
-
GPON discrete mode
l Configuring a GPON ONT
Capability Profile
Profile
An ONT capability
profile must match the
hardware capability of
the ONT to which profile
is bound. Otherwise,
certain configuration
data cannot be applied.
The global profile of the
ONT capability profile
must be configured on
the U2000. In addition,
the same ONT capability
profile must be created
on the U2000 and OLT.
Otherwise, the network
planning sheet cannot be
imported into the U2000.
applied to the OLT.
ONT Value-Added
Profile
-
Issue 03 (2010-11-19)
EPON profile mode
l 23.1.3 Configuring a Line
Profile
Service Profile
Profile
applied to the OLT.
ONT Value-Added
Profile
-

l Generating a global profile based on an NE profile
This section considers the EPON DBA profile as an example to describe how to generate
a global profile based on an NE profile. The procedures for operating all profiles are the
same but differ in the navigation path.
2. Choose Configuration > Access Profile Management > EPON Profile from the
main menu.
3. Click the DBA Profile tab.
4. Right-click the required profile in the list and choose Generate Global Profile from
the shortcut menu.
5. In the dialog box that is displayed, click OK.
----End
the U2000.
18-7
Prerequisite
A global profile that has the same name as the profile used in the network planning sheet must
exist on the U2000. For information on how to configure the profile, see 18.3.2 Configuring
the Profile Referenced in a Network Planning Sheet.
Procedure
1 Obtain a network planning sheet from the installation path of the U2000.
The name of the network planning sheet is Networking Planning Sheet (xPON).xls, where x
represents G or E. The paths to the network planning sheet vary with the types of the operating
systems (OSs), as follows:
l Windows-based server: X:\U2000\client\template\MDU Pre-Deploy\en\, where x
indicates the name of the disk, such as D, E, and F.
l Solaris-based server: /opt/U2000/client/template/MDU Pre-Deploy/en
2 Double-click a blank network planning sheet and fill in the sheet.
l The Data Plan worksheet contains parameters particular to an ONT to be predeployed. These
parameters can be classified into two parts: ONU Management Information and E2E
Service Channel Data.
Parameter settings in ONU Management Information of an ONU must be unique and
cannot conflict with other ONUs. The parameters include ONU ID, ONU Description
(ONU name displayed on the U2000), and Authentication Information. If the MAC
address or SN of the ONU is unknown, the authentication information can be blank.
An E2E service channel is used by the U2000 to manage the ONT. You can deploy
services such as the broadband and IPTV services after the E2E service channel is set up
and the ONT goes online and becomes stable.
l The Default Value Policy worksheet defines Management Channel Parameters, GEM
Port Channel Parameters, OLT Service Channel, ONU Service Channel, Voice IP
Address Pool, Voice Service (H.248, SIP, and MGCP), and Multicast User. These
parameters are effective in the entire network.
3 After filling in the network planning sheet, click Verify Data in the Data Plan worksheet to
verify the contents in the worksheet.
NOTE
If an error exists in the network planning sheet, the cause of the error is provided in the blank area at the end of
the line.
The data verification performed by the network planning sheet is not complete. To ensure data accuracy, it is
recommended that you check the contents carefully.
----End
the U2000.
Prerequisite
l The preparations must be complete. For details, see 18.3.1 Adding an OLT to the
U2000 and 18.3.2 Configuring the Profile Referenced in a Network Planning Sheet.
Issue 03 (2010-11-19)
l The dependent processes of subtasks must be started. The names of the relevant processes
are Access Device Common Service, Access Device Manager, Profile Manager, and
xFtpWatcher Process.
Procedure
2 In the dialog box that is displayed, select the network planning sheet to be deployed and click
Open.
3 After importing the network planning sheet, click OK.
4 The U2000 automatically performs the pre-deployment task after the ONT is powered on.
Choose Administration > Task Schedule > Scheduling Center from the main menu. Then,
you can view the execution status of the pre-deployment task.
----End
18.5 Acceptance
Viewing a pre-deployment task and the service data of the predeployed ONT helps you determine
whether the ONT is predeployed successfully.
Viewing a pre-deployment task and the service data of the predeployed ONT helps you determine
whether the ONT is predeployed successfully.
Procedure
l Viewing a pre-deployment task in the scheduling center
1. Choose Administration > Task Schedule > Scheduling Center from the main menu.
2. On the tab page that is displayed, choose Deployment Task from the navigation tree.
In the task list, select a task and view the details.
18-9
3. If the scheduling of a pre-deployment task fails, click the Log Info tab, right-click the
failed task and choose Log Details from the shortcut menu. Then, you can view the
details in logs.
l Viewing an ONT loading task
1. Choose Administration > Task Schedule > ONT Task List from the main menu.
2. In the ONT Load Task dialog box, an ONT loading task is generated on the Current
Task tab page. The ONT loading task is started and completed successfully after the
ONT is powered on and works in the normal state. In this case, you can view the task
on the History Task tab page.
l Viewing the service data of the predeployed ONT
2. Choose EPON > EPON ONU from the navigation tree.
3. On the EPON ONU tab page, set the filter criteria or click to display the EPON
ONUs.
4. In the ONT list, right-click an ONT and choose Configure Value-Added Service
from the shortcut menu.
5. In the dialog box that is displayed, check and ensure that the configuration is the same
as the predeployed configuration, and then click OK.
----End
Issue 03 (2010-11-19)
Context
l The data of previously predeployed OLT, MDU, or ONT will be deleted automatically
when you predeploy them again.
l Predeploying an OLT, MDU, or ONT again will be slow because the data of the previously
previous deployed data needs to be deleted when you predeploy them again.
Table 18-1 describes the common problems and solutions to network planning sheets.
Table 18-1 The common problems and solutions to network planning sheets
The system displays an error
message "Name of the ONT
capability profile repeats the
default profile name ranging
from ont-profile_1 to ont-
profile_128" when you import
the network planning sheet into
the U2000.
This problem can be resolved by changing the profile
name.
The MDU does not allow the U2000 to apply a profile
named by following the default naming rules, such as the
ONT capability profile and DBA profile, to the MDU. If
you need to use the profile named by following the default
naming rules, create this profile on the MDU directly,
synchronize the profile to the U2000, and then generate a
global profile from the NE profile.
"Network transmission times out.
Please try again later" when you
import the network planning
sheet to the U2000 and verify the
service data of the MDU.
This problem can be resolved by importing the network
planning sheet again into the U2000.
You need to check the memory usage of the server.
Increase the memory to prevent this problem from
occurring again if the available memory is less than 4 GB.
"Device name contains invalid
characters" when you import the
network planning sheet into the
U2000 and verify the service data
of the MDU.
You need to check and ensure that the device name in the
network planning sheet does not contain any unsupported
special characters.

Table 18-2 describes the common problems occurred when tasks are performed on the OLT and
18-11
Table 18-2 The common problems occurred when tasks are performed on the OLT and solutions
to these problems
stopped" when the tasks are
performed on the OLT. After you
click the Log Info tab and
double-click the failed task to
view the failure cause, the
message "VLAN already exists"
is displayed.
To resolve this problem, change the type and attribute of
this VLAN on the OLT and ensure that the VLAN type
and attribute are the same as those of the predeployed
VLAN.
This problem occurs because the OLT already has a
VLAN that has the same VLAN ID but different VLAN
type and attribute from the VLAN preset in the network
planning sheet.
When performing the subtask of
deploying service virtual ports in
the process of MDU pre-
deployment, the system displays
the message "Database operation
failed."
This problem occurs because the data on the U2000 and
MDU is different. If the system displays this message
when performing an OLT task, synchronize the service
virtual port data of the OLT and import the network
planning sheet into the U2000 again; if the system
displays this message when performing an MDU task,
delete the MDU and import the network planning sheet
again.
"The message transmitted by
MDP failed" in the process of
performing an OLT task when
you predeploy an MDU again.
To resolve this problem, check and ensure that the
processes relevant to the subtasks of the pre-deployment
are started.

Table 18-3 describes the common problems occurred when tasks are performed on the MDU
and solutions to these problems.
Table 18-3 The common problems occurred when tasks are performed on the MDU and
stopped" when the Synchronize
physical resource data of NE
task is performed.
To resolve this problem, choose Administration >
Settings > xFtpWatcher from the main menu and ensure
that the status indicator is green.
The system displays a failure and
the message "Incorrect
parameter" is recorded in logs
when the Import network
planning sheet of service
virtual ports task is performed.
To resolve the problem, ensure that the service virtual
ports of xDSL ports are configured with VPIs and VCIs.

Issue 03 (2010-11-19)
Procedure
2 In the dialog box that is displayed, select the modified network planning sheet and click
Open.
3 Click Finish after the network planning sheet is imported into the U2000.
----End
18.6 Configuration Example of xPON ONT Pre-deployment
This topic considers the scenario wherein an EPON ONT (850e) is connected to an OLT as an
example to describe how to predeploy an xPON ONT.
Prerequisite
l The OLT must be in profile mode.
l This topic considers the Windows-based server as an example.
Context
Table 18-4 and Table 18-5 provide the data that must be planned in the network planning sheet.
Table 18-4 Data plan in the preparation phase
Configura
tion Item
Data Plan Remarks
U2000
server
192.168.50.17 The U2000 server needs to use ports
23, 8080, 9801, and 9803. Therefore,
ensure that these ports are enabled on
the firewall so that the U2000 server
can communicate with NEs
successfully.
OLT l IP Address: 192.168.20.100
l Management mode: inband
l Upstream port: 0/0/1
l Upstream VLAN: 1000
l GPON port: 0/5/0
The upstream VLAN is the same as
the native VLAN of the upstream
port.
Profile
referenced
in the
network
planning
sheet
DBA profile
l Name: dba-profile_ont
parameters.
-
18-13
Configura
tion Item
Data Plan Remarks
Line profile
l Name: line-profile_ont
l T-CONT Index: 1
l DBA Profile: dba-profile_ont
l GEM Port Index: 1
parameters.
-
Service profile
l Name: service-profile_ont
l Number of Pots Ports: 2
l Number of ETH Ports: 4
l Default VLAN ID: 1001
-
MEF IP traffic profile
l Name: traffic-profile_1
l CIR: 64Kbit/s
l Outer Priority: 1
parameters.
-
ONT VAS configuration profile
l Profile Name: VOIPHG850a
l Vendor ID: HWTC(2011)
l Terminal Type: 850e
l Version: V1R1C02B010~Later
l Signal Protocol: H248
l Digitmap: x.T
l MGC Port: 2944
l MGC domain name: MGC.com
-

Issue 03 (2010-11-19)
Table 18-5 Data plan in a network planning sheet
Configura
tion Item
Data Plan Remarks
Data Plan l OLT IP Address: 192.168.20.100
l PON Port: 0/5/0
l ONU ID: 0
l ONU Name: Building F in
residential section B, block L, City
S
l Authentication Mode: 00-1E-
E3-22-A9-93
l ONU Type: 850e
l Broadband
CVLAN: 1001
SVLAN: 1001
l VoIP
CVLAN: 2000
SVLAN: 2000
Voice IP Address:
10.121.68.28
Voice IP Mask: 24
PSTN Terminal ID Prefix: A8
RTP Terminal ID Prefix: A8
Telephone No.: 28971111
-
18-15
Configura
tion Item
Data Plan Remarks
Default
Value
Policy
l PON Channel Parameters
ONU Type: 850e
Authentication Mode: MAC
Line Profile Name: line-
profile_ont
Service Profile Name: service-
profile_ont
ONT VAS Configuration
Profile: VOIP850e
Enable DHCP: Enable
Enable PITP: Enable
l Service Channel: Create a service
channel whose Service Name is
Voice in the same way. Do not set
the names of the upstream traffic
profile and downstream traffic
profile for the service channel of
voice services.
SVLAN Type: smart
-

Procedure
1 Adding an OLT to the U2000 (For details, see 18.3.1 Adding an OLT to the U2000.)
1. In the Main Topology, choose Physical Root or an NE in the navigation tree, right-click
in the topology view in the right pane, and then choose New > NE from the shortcut menu.
l IP Address: 192.168.20.100
l Device Name: 192.168.20.100-MA5680T
3. Click OK.
2 Configuring the profile referenced in the network planning sheet (For details, see 18.3.2
Configuring the Profile Referenced in a Network Planning Sheet.)
1. Configuring a DBA profile (For details, see 23.1.2 Configuring a DBA Profile.)
Issue 03 (2010-11-19)
a. Choose Configuration > Access Profile Management > EPON Profile from the
main menu.
b. Click the DBA Profile tab.
l Name: dba-profile_ont
l Accept the default values for other parameters.
e. Click OK.
shortcut menu.
2. Configuring a line profile (For details, see 23.1.3 Configuring a Line Profile.)
main menu.
b. Click the Line Profile tab.
l Set Name to line-profile_ont.
l DBA Profile: dba-profile_ont
e. Click OK.
shortcut menu.
3. Configuring a service profile (For details, see 24.1.2 Configuring a Service Profile.)
main menu.
b. Click the Service Profile tab.
l Set Name to service-profile_ont.
l Choose Base Info. from the navigation tree and set the parameters.
Number of Pots Ports: 2
Number of ETH Ports: 4
l Choose UNI Port from the navigation tree. In the window that is displayed, right-
click the record where Port Type is ETH Port and Port ID is 1, and choose
Config VLAN of UNI Port from the shortcut menu. In the dialog box that is
displayed, set the parameters.
VLAN Type: Translation
Default VLAN ID: 1001 (VLAN ID of the Internet service)
e. Click OK.
18-17
shortcut menu.
4. Configuring an MEF IP traffic profile (For details, see 19.2.2 Configuring an MEF IP
Traffic Profile.)
a. Choose Configuration > Access Profile Management > Traffic Profile from the
main menu.
b. Click the MEF IP Traffic Profile tab.
l Name: traffile_profile_1
l CIR: 20480
l Outer Priority: 1
e. Click OK.
5. Configuring the VAS configuration profile of the ONT (For details, see 20.2.1
Configuring the ONT Value-Added Service Configuration Profile.)
a. Choose Configuration > Access Profile Management > ONT VAS Profile from
the main menu.
b. In the information list, right-click and choose Add from the shortcut menu.
l Set Profile Name to VOIP850e.
l Set Vendor ID to HWTC(2011).
l Set Terminal Type to 850e.
l Set Version to V100R001C02B010~Later.
l Choose Country code and signaling protocol from the navigation tree and set
Signal Protocol to H248.
l Choose H.248 protocol basic configure > H.248 Global digitmap configure >
Global digitmap configure 1 from the navigation tree and set Digitmap to x.T.
l Choose H.248MGC > H.248 MGC configure 1 from the navigation tree and set
MGC port to 2944 and MGC domain name to MGC.com.
d. Click OK.
3 Filling in the network planning sheet (For details, see 18.4.1 Filling In a Network Planning
Sheet.)
1. Navigate to the path X:\U2000\client\template\MDU Pre-Deploy\en\ on the Windows-
based server, and double-click the Network_Planning_Sheet(EPON_FTTH).xls file.
2. In the Data Plan worksheet, set the parameters as follows:
l OLT IP Address: 192.168.20.100
l PON Port: 0/5/0
l ONU ID: 0
l ONU Name: Building F in residential section B, block L, City S
l Authentication Mode: 00-1E-E3-22-A9-93
l ONU Type: 850e
Issue 03 (2010-11-19)
l Broadband
CVLAN: 1001
SVLAN: 1001
l VoIP
CVLAN: 2000
SVLAN: 2000
Voice IP Address: 10.121.68.28
Voice IP Mask: 24
PSTN Terminal ID Prefix: A8
RTP Terminal ID Prefix: A8
Telephone No.: 28971111
3. In the Default Value Policy worksheet, set the parameters as follows:
l PON Channel Parameters
ONU Type: 850e
Line Profile Name: line-profile_ont
Service Profile Name: service-profile_ont
ONT VAS Configuration Profile: VOIP850e
Enable DHCP: Enable
Enable PITP: Enable
l Service Channel: Create a service channel whose Service Name is Voice in the same
way. Do not set the names of the upstream traffic profile and downstream traffic profile
for the service channel of voice services.
SVLAN Type: smart
4. Choose File > Save from the main menu to save the sheet.
4 Importing the network planning sheet (For details, see 18.4.2 Importing a Network
Planning Sheet.)
1. Choose Configuration > FTTx Service Pre-Deployment > Import Network
Deployment Sheets from the main menu.
2. In the dialog box that is displayed, select Network_Planning_Sheet(EPON_FTTH).xls
and click Open.
3. After importing the network planning sheet, click OK.
----End
18-19
Result
See 18.5.1 Viewing a Pre-deployment Task and the Result to determine whether the 850e is
predeployed successfully.
Issue 03 (2010-11-19)
19 Configuring the GPON FTTB Services
About This Chapter
An FTTB network consisting of an OLT in profile mode and a number of MDUs provides users
with Internet, multicast, and voice services.
Context
The MDU configuration is simplified when the OLT is in profile mode.
To query the current xPON configuration mode, run the diagnose command to enter the
diagnosis mode, and then run the display xpon mode command.
CAUTION
l In the diagnosis mode, you must be a user with operator rights or higher to query the current
xPON configuration mode.
l If you switch the xPON configuration mode in the diagnosis mode, the system saves data
and restarts automatically.
huawei(config)#diagnose
huawei(diagnose)%%display xpon mode
---------------------------------------------------
Current config mode: Profile-mode
---------------------------------------------------
You can run the xpon mode switch-to command in the diagnosis mode to switch the xPON
mode of the current system, for example, from discrete mode to profile mode.
huawei(config)#diagnose huawei(diagnose)%%xpon mode switch-to profile-mode
Warning: The operation will automatically save and reboot system. Are you sure to
proceed? (y/n)[n]:
19.1 Adding an MDU to the U2000 (OLT in Profile Mode)
This topic describes how to add an MDU to the U2000 when the OLT is in the profile mode.
After the MDU is successfully added to the U2000, you can configure the FTTB service for the
MDU on the U2000.
Operation Guide for ONU NE Management 19 Configuring the GPON FTTB Services
19-1
19.2 Configuring Services on the OLT
An FTTB network consisting of OLTs and MDUs provides users with Internet services,
multicast services, and voice services.
19.3 Configuring Services on the MDU
19.4 Configuration Examples of the GPON FTTB Services
This topic provides examples to describe how to configure the Internet, voice, and multicast
services in a GPON FTTB network.
Issue 03 (2010-11-19)
After the MDU is successfully added to the U2000, you can configure the FTTB service for the
MDU on the U2000.
Context
You can add an MDU on the device side in the following two scenarios: online MDU
confirmation and offline MDU deployment. The profile bound to an MDU and the authentication
information of the MDU must be the same as those configured on the MDU on the user side.
l Online MDU confirmation: When an MDU is online, the MDU can be managed
immediately after it is added to the U2000. This topic considers the online MDU
confirmation as an example to describe how to add an MDU to the U2000.
l Offline MDU deployment: When an MDU is offline, you need to add the MDU and
configure the FTTB service for the MDU offline. After the MDU goes online, the
configuration data is applied to the MDU through the optical network termination
management and control interface (OMCI) message to complete the service configuration
on the MDU.
19.1.1 Configuring an MDU SNMP Profile
The MDU Simple Network Management Protocol (SNMP) profile is a collection of SNMP
parameters. You can configure the information about an MDU management channel to OLT to
implement the remote deployment and maintenance for the MDU.
19.1.2 Configuring a DBA Profile
The GPON DBA profile is a collection of traffic parameters of a T-CONT. DBA is used to
control the upstream bandwidth of the services on the ONU. DBA profiles are bound to T-
CONTs. Different T-CONTs are planned for different bandwidth assurance types. After a GPON
DBA profile is successfully configured and bound to a T-CONT, the system controls the traffic
of the T-CONT based on the traffic parameters specified in the GPON DBA profile. In this case,
the GPON DBA profile implements the flexible dynamic bandwidth allocation.
19.1.3 Configuring a GPON Line Profile
The GPON line profile is a collection of parameters required for setting up channels for GPON
lines. You need to bind the ONU and line profile when the ONU management mode is OMCI
or SNMP.
19.1.4 Confirming an MDU
This topic describes how to confirm the auto-discovered ONU that is connected to a GPON port.
The auto-discovered ONU can work in the normal state only after it is confirmed.
19.1.5 Configuring a VLAN
The MDU is connected to the xPON port of the OLT through an optical fiber. You can perform
the service configuration only after adding an MDU successfully on the OLT. To configure the
MDU from the U2000, you must configure the inband management VLAN and IP address for
the OLT and the MDU on the OLT.
19.1.6 Adding a Service Virtual Port
After an ONT is successfully added, the control channel is set up, but the data channel is not set
up yet. In this case, you need to add a service virtual port on the OLT to manage ONU data.
19.1.7 Checking the Communication Between the OLT and MDU
19-3
After the parameters on the U2000 are set successfully, you need to check whether the U2000
can manage and maintain the ONUs successfully.
Context
You can configure the SNMP parameter profile of the MDU on the U2000, and configure the
information about an MDU management channel to the OLT. Then, the OLT manages the MDU
through the SNMP mode so that the remote deployment and maintenance for the MDU can be
implemented.
Procedure
1 Choose Configuration > Access Profile Management > MDU SNMP Profile from the main
menu.
2 Right-click and choose Add Global Profile from the shortcut menu.
Key
Parameter
Description
SNMP
Version
Ensure that the SNMP version of the U2000 server is the same as the
corresponding SNMP version configured on the device.
Generally, the SNMP Version of the U2000 server is set to v1.
Trap Host
IP
Specifies the IP address of the destination device for traps. The trap packets of
the device are sent to the U2000 server that maps the IP address.
NOTE
Generally, the IP address of the U2000 server is set to the IP address of the destination
device for traps.
Trap UDP
Port
Specifies the ID of the UDP port that is used to receive the traps that the device
reports to the U2000.
Issue 03 (2010-11-19)

4 Click OK.
5 In the information list, right-click the record and choose Download to NE from the shortcut
menu.
6 In the dialog box that is displayed, select the required NE(s), and click OK.
NOTE
The MDU SNMP profile that is generated by the U2000 can be referenced by the OLT only after the profile is
applied to the corresponding OLT.
----End
Command Reference
Add an
MDU
SNMP
managemen
t profile
snmp-profile add Global config mode

The GPON DBA profile is a collection of traffic parameters of a T-CONT. DBA is used to
control the upstream bandwidth of the services on the ONU. DBA profiles are bound to T-
CONTs. Different T-CONTs are planned for different bandwidth assurance types. After a GPON
DBA profile is successfully configured and bound to a T-CONT, the system controls the traffic
of the T-CONT based on the traffic parameters specified in the GPON DBA profile. In this case,
the GPON DBA profile implements the flexible dynamic bandwidth allocation.
Context
l The traffic configured in the GPON DBA profile is specified as the traffic after the data is
encapsulated to the GPON encapsulation mode (GEM) frames. Hence, the actual traffic of
packets is slightly lighter than the traffic specified in the GPON DBA profile.
l The GPON DBA profile that is added on the U2000 exists only in the database of the U2000,
but it is not applied to the device. The GPON DBA profile can be created on the device
only after it is bound to the T-CONT.
NOTE
l The profiles with the Name ranging from dba-profile_1 to dba-profile_9 are the default GPON DBA
profiles of the system. The traffic parameters in the profiles are assigned with typical values. You can
query the default GPON DBA profiles but cannot add or delete them.
l Generally, the service with a high priority adopts a fixed bandwidth or an assured bandwidth, and the
service with a low priority adopts the maximum bandwidth or a mix of fixed bandwidth, assured
bandwidth, and maximum bandwidth.
19-5
Procedure
1 Choose Configuration > Access Profile Management > GPON Profile from the main menu.
2 Click the DBA Profile tab. Right-click and choose Add Global Profile from the shortcut menu.
Key Parameter Description
Name Indicates the name of a GPON DBA profile. It uniquely identifies
a GPON DBA profile. The GPON DBA name must be unique.
T-CONT type Indicates the type of a GPON DBA profile. It is defined according
to the bandwidth requirement of the services carried on the T-
CONT. You can allocate the bandwidth for T-CONTs of different
types to control the traffic of the T-CONT.
Assured Bandwidth
Fixed Bandwidth
Maximum Bandwidth
Generally, the service with a high priority adopts a fixed
bandwidth and an assured bandwidth, and the service with a low
priority adopts the maximum bandwidth. The VoIP service always
has the highest priority.

4 Click OK.
----End
Command Reference
Query the DBA
profiles in the system
display DBA-profile Privilege mode
Add a DBA profile DBA-profile add Global config mode

Issue 03 (2010-11-19)
or SNMP.
Prerequisite
The DBA profile must be already configured in the system. For details, see 19.1.2 Configuring
a DBA Profile.
Context
l The flow mapping mode configured in the GPON line profile must match the flow mapping
mode of the flow (such as the GEM connection flow) specified in the GPON line profile.
l The flow control mode configured in the GPON line profile must match the flow control
mode of the GEM port specified in the GPON line profile.
l When adding a GPON line profile, you can use or reference the four default line profiles,
lineprofile_1 to lineprofile_4, provided by the NE.
Procedure
2 Click the GPON Line Profile tab. Right-click and choose Add Global Profile from the shortcut
menu.
1. Choose Basic Info from the navigation tree, and then set the basic parameters of the profile.
19-7
Key
Paramete
r
Description
Upstream
FEC
Switch
Specifies whether to enable the upstream forward error correction (FEC)
function of the ONT line profile. To improve the reliability of data
transmission between the OLT and the ONT, enable the FEC function.
After the upstream FEC function is enabled, the system inserts the
redundancy data into normal packets. In this manner, the line has the error
tolerance capability, but certain bandwidth is wasted.
Mapping
Mode
Flow mapping manages the service streams on the ONU, namely, manages
the mapping between GEM ports and the upstream data flows on the ONT
service ports. After the mapping is established, the ONU service streams
are carried and transmitted upstream through the specified GEM ports.
Each ONT can be configured with only one mapping mode.
Qos Mode l When the Qos Mode of the GEM port is set to Priority Queue, users
can specify the transmit queue of the GEM port packets in a T-CONT.
When transmitting the upstream data, the T-CONT transmits the data
strictly according to the priority of the queue.
l When the Qos Mode of the GEM port is set to GEM Port CAR, the
ONU limits the rate of the data packets carried on the GEM port
according to the CAR setting of the GEM port. Currently, the GEM
port CAR is set by binding the CAR profile to the ONU, and only the
average rate and maximum rate can be set. When several service
streams exist on the GEM port, the service streams are schedule in PQ,
WRR, or PQ+WRR mode, depending on the default scheduling mode
of the ONU. Currently, the scheduling mode cannot be set on the OLT.
When a T-CONT consists of multiple GEM ports, the scheduling mode
of the data packets between the GEM ports also depends on the default
scheduling mode of the ONU.
l When the flow control mode of the GEM port is set to Flow CAR, the
ONU performs CAR on the service streams of the GEM port. The
controlling is more specific than the GEM port CAR. After being
performed with CAR, the service streams are scheduled in the T-CONT
queue. The scheduling mode is the default scheduling mode of the
ONU.

2. Choose T-CONT Info. from the navigation tree, right-click, and then choose ADD T-
CONT from the shortcut menu. In the dialog box that is displayed, set T-CONT Index
and DBA Profile.
Issue 03 (2010-11-19)
CAUTION
It is recommended that you do not set T-CONT Index to 0. TCONT 0 is reserved for the
internal communication of the GPON protocol.
3. Choose T-CONTx from the navigation tree, right-click, and then choose ADD GEM
Port from the shortcut menu. In the dialog box that is displayed, set GEM Port Index.
NOTE
19-9
4. Choose GEM Portx from the navigation tree, right-click, and then choose ADD GEM
Connection from the shortcut menu. In the dialog box that is displayed, set the basic
parameters of the GEM connection.
NOTE
4 Click OK.
menu.
----End
Command Reference
Enter the ONT line profile mode ont-lineprofile gpon Global config mode
Bind a DBA profile to a T-CONT tcont ONT line profile mode
Bind a GEM index to a T-CONT
and configure the related attributes
in an ONT line profile
gem add ONT line profile mode
Set up the mapping relationship
between the upstream data flow on
the ONT service ports and the
GEM ports
gem mapping ONT line profile mode
Configure the QoS mode in the
ONT line profile
qos-mode ONT line profile mode

Issue 03 (2010-11-19)
This topic describes how to confirm the auto-discovered ONU that is connected to a GPON port.
The auto-discovered ONU can work in the normal state only after it is confirmed.
Prerequisite
The Line profile must be already configured in the system. For details, see 19.1.3 Configuring
a GPON Line Profile.
The MDU SNMP profile must be already configured in the system. For details, see 19.1.1
Configuring an MDU SNMP Profile.
Context
When the ONU auto-discovery function is enabled, the OLT can periodically check whether
there are new online ONUs. If new online ONUs are discovered, the OLT reports a group of
ONUs to be confirmed to the U2000 for user confirmation.
Procedure
1 In the Main Topology, double-click the required OLT in the Physical Root navigation tree; or
right-click the required OLT and choose NE Explorer from the shortcut menu.
2 Choose GPON > GPON UNI Port from the navigation tree.
3 On the GPON UNI Port tab page, set the filter criteria to display the required GPON UNI ports.
4 Select the GPON UNI port to be enabled with the auto-discovery function, right-click and choose
Enable ONU Auto Find from the shortcut menu.
5 Select a record from the GPON UNI ports list, and click the Auto-Discovered ONU Info tab
in the lower part of the tab page.
6 Select an ONU to be confirmed, right-click, and then choose Confirm ONU from the shortcut
menu.
7 In the dialog box that is displayed, configure the basic parameters and network management
channel parameters for confirming the ONU, and then click OK.
NOTE
This section considers the GUIs in profile mode as an example.
19-11
Issue 03 (2010-11-19)
Key
Parameter
Description
ONU ID Indicates the ONU ID. It always ranges from 0.
ONU Type Indicates the ONU type and needs to be set to MDU.
Line Profile Indicates the line profile of the port to which the ONU is connected. After a
line profile is bound to a port, the system can directly reference the line profile
when activating a port. During the activation, the system checks the line
distance and conditions and performs a negotiation between the CO and CPE
to determine whether the port can work under the conditions as preset in the
line profile, such as upstream and downstream line rates and noise margin.
Authenticat
ion Mode
Indicates the mode in which the OLT authenticates the ONU.

When adding the ONU of the SNMP management mode, you must set the Authentication
Mode and Line Profile parameters. When adding the ONU of the OAM management mode,
you must set the Authentication Mode, Line Profile, and Service Profile parameters.
----End
19-13
Command Reference
Confirm the ONT that is in the
auto-discovery mode
ont confirm GPON mode
Enter the GPON mode from the
global configuration mode
interface gpon Global config mode
Enable the ONT auto-discovery
function of a GPON port
port ont-auto-find enable GPON mode
Query the auto-discovery ONTs in
the system or the settings for the
ONT auto-discovery time
display ont autofind Privilege mode, GPON
mode

Procedure
1 In the Main Topology, double-click the required NE in the Physical Root navigation tree; or
right-click the required NE and choose NE Explorer from the shortcut menu.
4 In the information list, right-click and choose Add from the shortcut menu.
Issue 03 (2010-11-19)
19-15
VLAN ID Indicates the VLAN ID. The VLAN ID uniquely identifies a
VLAN.
NOTE
Add VLANs according to data plan.
Type Indicates the VLAN type.
NOTE
Usually, Smart is selected.
Attribute Indicates the VLAN attribute.
NOTE
For xPON FTTB, QinQ is usually selected.
VLAN Priority Indicates the VLAN priority. This parameter is applicable to the
VLANs for an OLT.

6 Click Done.
----End
Command Reference
Query the information about the VLAN display vlan Privilege mode
Add one VLAN or more VLANs of a
same type in batches
vlan Global config mode
Set the VLAN attribute vlan attrib Global config mode

After an ONT is successfully added, the control channel is set up, but the data channel is not set
up yet. In this case, you need to add a service virtual port on the OLT to manage ONU data.
Prerequisite
The management VLAN where the service virtual port belongs must be configured. The
upstream port of the VLAN must be configured. For details, see 19.1.5 Configuring a VLAN.
Procedure
2 Choose GPON > GPON ONU from the navigation tree.
3 On the GPON ONU tab page, set the filter criteria to display the required GPON ONUs.
Issue 03 (2010-11-19)
4 Select the required record from the GPON ONU list, and click the ServicePort Info tab in the
lower pane.
5 On the ServicePort Info tab page, right-click and choose Add from the shortcut menu.
NOTE
Key
Parameter
Description
VLAN ID Indicates the management VLAN ID of the OLT. It is used to uniquely
identify a VLAN.

7 Click OK.
----End
Command Reference
Add a service virtual port service-port Global config mode
19-17

19.1.7 Checking the Communication Between the OLT and MDU
After the parameters on the U2000 are set successfully, you need to check whether the U2000
can manage and maintain the ONUs successfully.
Context
When an MDU is in the predeployed state, you can right-click the MDU in Physical Root and
choose Synchronize NE Data from the shortcut menu to synchronize the data of the MDU
manually.
Procedure
1 To check the status of the ONU, do as follows:
1. In the Main Topology, double-click the required NE in the Physical Root navigation tree;
or right-click the required NE and choose NE Explorer from the shortcut menu.
3. On the GPON ONU tab page, set the filter criteria to display the required GPON ONUs.
4. Select a record according to the shelf/slot/port number and ONT ID from the GPON ONU
list. If the Status indicator is green, it indicates that the ONU is activated.
2 To check whether the ONU can ping the OLT successfully, do as follows:
1. In the Main Topology, choose the ONU from the Physical Root navigation tree, right-
click, and then choose Tool > Ping from the shortcut menu.
2. In the dialog box that is displayed, select Ping and click Start. If a reply message is
displayed, it indicates that the connection between the OLT and ONU is successfully set
up.
Issue 03 (2010-11-19)
----End
Command Reference
Query the
information
about the
device
when it
functions as
an ONU
display onu info Global config mode

Context
Several operations are required when you configure a service. The following lists the services
configured at the OLT side and the service configuration steps.
Services Steps
Internet access service l 19.2.1 Configuring a VLAN
l 19.2.3 Adding a Service Port
19-19
Services Steps
Multicast service l 19.2.1 Configuring a VLAN
l 19.2.7 Configuring the Multicast VLAN
l 19.2.5 Configuring the Virtual Multicast Upstream
Port
l 19.2.6 Configuring a Preview Profile
l 19.2.8 Configuring a Program Profile
l 19.2.10 Configuring a Multicast User
Voice service l 19.2.1 Configuring a VLAN

Virtual local area network (VLAN) is a technology used to form virtual workgroups by grouping
the devices of a LAN logically.
19.2.2 Configuring an MEF IP Traffic Profile
An MEF IP traffic profile defines a series of traffic parameters. It is referenced by the device
and the port to monitor and manage the traffic. After an MEF IP traffic profile is created, you
can directly reference it when creating a traffic stream and setting the port rate limit.
19.2.3 Adding a Service Port
After being configured successfully, the service port can carry service streams of various types.
19.2.4 Configuring Multicast System Parameters
Before you provision multicast services, you need to configure multicast system parameters
according to the global data plan. The parameters include the Internet Group Management
Protocol (IGMP) parameters and NTV mode.
19.2.5 Configuring the Virtual Multicast Upstream Port
To provide demand services when the upstream port is not working in the MSTP mode, you
need to configure a virtual multicast upstream port to transmit and receive the multicast packets
(including the protocol packets and data packets). After the virtual multicast upstream port is
added, the multicast packets are transmitted and received through this port.
19.2.6 Configuring a Preview Profile
This topic describes how to deliver a configured preview profile to a device and make the preview
profile take effect on the device.
19.2.7 Configuring the Multicast VLAN
One or more multicast VLANs are used to separate the multicast service from other services.
After configuring the multicast user, you need to add the user to a multicast VLAN so that the
user can watch the programs in the multicast VLAN.
19.2.8 Configuring a Program Profile
This topic describes how to deliver a configured program profile to a device and make the
program profile take effect on the device.
19.2.9 Adding a Multicast Rights Profile
A rights profile is used to manage the rights to a series of programs. In the rights profile, you
can set the rights to different programs and then bind the rights profile to the users that need to
Issue 03 (2010-11-19)
be authenticated. The users that need not be authenticated can watch all the programs provided
by the NE.
19.2.10 Configuring a Multicast User
This topic describes how to add a multicast user. Only multicast users can watch multicast
programs.
Procedure
19-21
Start ID
End ID
Indicates the start and end IDs when you add VLANs in batches.
VLANs for an OLT.

6 Click Done.
----End
Command Reference

Issue 03 (2010-11-19)
19.2.2 Configuring an MEF IP Traffic Profile
An MEF IP traffic profile defines a series of traffic parameters. It is referenced by the device
and the port to monitor and manage the traffic. After an MEF IP traffic profile is created, you
can directly reference it when creating a traffic stream and setting the port rate limit.
Context
The MEF IP traffic profile that is added through the U2000 exists only in the database of the
U2000, but it is not applied to the device. The MEF IP traffic profile is created on the device
only when the device references the MEF IP traffic profile to create a service virtual port or the
MEF IP traffic profile is successfully applied to the device manually.
Procedure
1 Choose Configuration > Access Profile Management > Traffic Profile from the main menu.
2 Click the MEF IP Traffic Profile tab.
19-23
Key
Parameter
Description
CIR Indicates the committed information rate. It ranges from 1 to 8192. The rate
must be an integer multiple of 64 kbit/s, namely, the rate must rage from 64
kbit/s to 524288 kbit/s.
If this parameter is set, the CBS, PIR, and PBS parameters are available.
Issue 03 (2010-11-19)
Key
Parameter
Description
Outer
Priority
Inner
Priority
Indicates the keywords of scheduling priority. The larger the value, the higher
the scheduling priority ranks. It ranges from 0 to 7.

5 Click OK.
menu.
----End
Command Reference
Query an
existing
traffic
profile in
the system
display traffic table ip Privilege mode
Create an
MEF IP
traffic
profile
traffic table ip Global config mode

Procedure
2 Choose Connection > Service Port from the navigation tree.
19-25
NOTE
The parameter of port selection used when a service virtual port is added in the profile mode is different
from that used when a service virtual port is added in the distributed mode.
Key
Parameter
Description
Vlan ID Indicates the VLAN ID of the service virtual port. The VLAN ID uniquely
identifies a VLAN.
Interface
Selection
l In the discrete mode, this parameter is displayed in the format shelf ID/slot
ID/port ID/GEM port ID.
l In the profile mode, this parameter is displayed in the format shelf ID/slot
ID/port ID/ONT ID/GEM port ID.
Traffic
Profile Info
Selects only the traffic profile that exists on the device. Otherwise, an error is
reported.

5 Click OK.
----End
Issue 03 (2010-11-19)
Command Reference
Query the 802.1x
configuration of a service
virtual port
display dot1x service-port Privilege mode
Bind a service virtual port
with 802.1x authentication
dot1x service-port Global config
mode

19.2.4 Configuring Multicast System Parameters
Before you provision multicast services, you need to configure multicast system parameters
according to the global data plan. The parameters include the Internet Group Management
Protocol (IGMP) parameters and NTV mode.
Procedure
l Configure IGMP parameters.
IGMP defines the mechanism used to set up and maintain the relationship of multicast
group members between the device and the router. By setting IGMP parameters, you can
effectively control the IGMP parameters of multicast packets, including the relevant
parameters defined in IGMP.
1. Choose Configuration > Access Profile Management > System Parameter
2. On the System Parameter Profile tab page, select the required device type from the
4. In the dialog box that is displayed, enter the name of the system parameter profile.
Choose all parameters from the Parameters for Selection navigation tree, click
to add the parameters to the Selected Parameters navigation tree, and then
click Next.
19-27
5. Choose Protocol > IGMP from the System Parameter Settings navigation tree.
NOTE
During configuration, use the default IGMP parameters.
7. Click Finish.
l Configure NTV parameters.
Configure the multicast video service mode.
Issue 03 (2010-11-19)
1. Choose Configuration > Access Profile Management > System Parameter
2. On the System Parameter Profile tab page, select the required device type from the
4. In the dialog box that is displayed, enter the name of the system parameter profile.
Choose all parameters from the Parameters for Selection navigation tree, click
to add the parameters to the Selected Parameters navigation tree, and then
click Next.
5. Choose NTV from the System Parameter Settings navigation tree.
19-29
Key
Paramete
r
Description
Enable
bandwidth
managem
ent switch
Specifies whether the system performs bandwidth management. If the
switch for bandwidth management is enabled, the system limits the
bandwidth for multicast programs on the upstream port or the user
port. If the switch for bandwidth management is disabled, the system
does not perform multicast bandwidth management on the upstream
port or the user port, and the system does not guarantee the bandwidth
for multicast programs.
l When the bandwidth management switch is disabled, the
bandwidth for the program that is added is automatically adjusted
to 0.
l In the MSTP mode, if users are online, this switch cannot be
enabled after it is disabled. To enable the switch, change the mode
of the upstream port or force all the users to log out first.
NOTE
Choose Open.

7. Click Finish.
----End
Issue 03 (2010-11-19)
Command Reference
Query the
configuratio
n of IGMP
global
parameters
display igmp config global Privilege mode, BTV mode, MVLAN
mode
Set the
current
IGMP
version of a
multicast
VLAN to
V2 or V3
igmp version
NOTE
Choose v3 version.
MVLAN mode
Enable the
call detailed
record
(CDR)
function of
the system
igmp cdr enable BTV mode
Set the
multicast
log
reporting
igmp log report BTV mode
Set the
IGMP mode
of a
multicast
VLAN
igmp mode
NOTE
Choose proxy mode.
MVLAN mode

19.2.5 Configuring the Virtual Multicast Upstream Port
To provide demand services when the upstream port is not working in the MSTP mode, you
need to configure a virtual multicast upstream port to transmit and receive the multicast packets
(including the protocol packets and data packets). After the virtual multicast upstream port is
added, the multicast packets are transmitted and received through this port.
Prerequisite
The Uplink port mode parameter cannot be configured with MSTP. For details, see 19.2.4
Configuring Multicast System Parameters.
Procedure
19-31
2 Choose Multicast > Virtual Uplink Port from the navigation tree.
4 In the dialog box that is displayed, configure the shelf, slot, and port of the upstream port.
5 Click OK.
----End
Command Reference
Query the
information
about a
multicast
upstream
port
display igmp uplink-port Privilege mode, BTV mode, MVLAN
mode
Query
isolation of
upstream
ports and
subtended
cards
display isolate Privilege mode
Query all
the VLANs
of a
specified
upstream
port
display port vlan Privilege mode
Issue 03 (2010-11-19)
Configure
the default
upstream
port of a
multicast
VLAN
igmp default uplink-port MVLAN mode
Add a
multicast
upstream
port to a
multicast
VLAN
igmp uplink-port MVLAN mode
Set the port
to function
as an
upstream
port or a
subtended
port
network-role SCU mode, GIU mode, ETH mode
Add an
upstream
port to a
VLAN
port vlan Global config mode

19.2.6 Configuring a Preview Profile
This topic describes how to deliver a configured preview profile to a device and make the preview
profile take effect on the device.
Procedure
1 Choose Configuration > Access Profile Management > IGMP Profile from the main menu.
2 Click the Preview Profile tab, and select the required device type from the Device Type drop-
down list.
19-33
5 Click OK.
menu.
----End
Command Reference
Enable the
function of
multicast
preview
igmp preview BTV mode
Add a
program
preview
profile
igmp preview-profile add BTV mode

19.2.7 Configuring the Multicast VLAN
One or more multicast VLANs are used to separate the multicast service from other services.
After configuring the multicast user, you need to add the user to a multicast VLAN so that the
user can watch the programs in the multicast VLAN.
Prerequisite
The corresponding VLAN must exist. For details, see 19.2.1 Configuring a VLAN.
Procedure
Issue 03 (2010-11-19)
2 Choose Multicast > Multicast VLAN from the navigation tree.
3 Click Find. In the dialog box that is displayed, set the filtering criteria and display the multicast
VLANs that meet the requirement.
4 On the Multicast VLAN interface, right-click, and then choose Add.
Key
Parameter
Description
IGMP
Work Mode
Indicates the working mode of the multicast VLAN.
l igmp_proxy: In this mode, the system processes multicast packets as a
proxy. For a user, the system functions as a multicast server. For the upper-
layer device, the system functions as a multicast user.
l igmp_snooping: The system transmits multicast packets transparently. In
this mode, the functions of hosting, pre-adding, reporting in an unsolicited
manner, and statically adding multicast programs do not take effect.
l tv_off: disables the IGMP function. In this mode, multicast users cannot
watch programs.

6 Click Next.
19-35
Key
Parameter
Description
Report
Interval
Indicates the interval at which the system reports IGMP Report packets to the
upper-layer device in an unsolicited manner.

8 Click Next.
9 Select the required VLAN from the list, and then click Finish.
Issue 03 (2010-11-19)
----End
Command Reference
Query the
configuratio
n of a
specific
multicast
VLAN
display igmp config vlan Privilege mode, BTV mode, MVLAN
mode
Create a
multicast
VLAN and
enter the
multicast
VLAN
mode
multicast-vlan Global config mode, BTV mode

19-37
19.2.8 Configuring a Program Profile
This topic describes how to deliver a configured program profile to a device and make the
program profile take effect on the device.
Prerequisite
The multicast preview profile must be configured.
Context
The MA5620E, MA5626E, MA5620G, and MA5626G do not support program profiles.
Procedure
2 Click the Program Profile tab, and select the required device type from the Device Type drop-
down list.
Issue 03 (2010-11-19)
5 Click OK.
menu.
7 In the dialog box, select the required devices in the left pane, and then click Next.
8 In the dialog box that is displayed, set the VLAN ID and click Finish.
----End
Command Reference
Query the information
about a multicast
program
display igmp program Privilege mode, BTV mode,
MVLAN mode
Add a static multicast
program to a multicast
VLAN
igmp program add MVLAN mode

19.2.9 Adding a Multicast Rights Profile
A rights profile is used to manage the rights to a series of programs. In the rights profile, you
can set the rights to different programs and then bind the rights profile to the users that need to
be authenticated. The users that need not be authenticated can watch all the programs provided
by the NE.
Prerequisite
l The required program profile must be configured on the MDU.
Context
The MA5620E, MA5626E, MA5620G, and MA5626G do not support rights profiles.
Procedure
2 Click the Right Profile tab and select MA56T&MDU from the Device Type drop-down list.
4 In the Add Right Profile dialog box, set Name to right_profile. In the Selected Program
Profile area, right-click and choose Select Profile from the shortcut menu. In the Right column,
set the required program profile.
19-39
5 Click OK.
----End
Command Reference
Add program rights to a
multicast rights profile.
igmp profile add BTV mode

19.2.10 Configuring a Multicast User
This topic describes how to add a multicast user. Only multicast users can watch multicast
programs.
Issue 03 (2010-11-19)
Prerequisite
The corresponding service virtual port must exist.
Context
l When adding a multicast user, you must specify a service virtual port.
l An authentication user must be bound to a rights profile to obtain relevant rights. A non-
authentication user can watch all the programs configured on the device. You need not
configure the rights for a non-authentication user.
Procedure
2 Choose Multicast > Multicast User from the navigation tree.
3 On the Multicast User tab page, set the filter criteria to display the required multicast users.
19-41
Key
Parameter
Description
Quick
Leave mode
Indicates the mode of multicast users for leaving multicast groups.
Max.
Programs
NO.
Each multicast user can watch up to 32 programs online simultaneously. By
default, each multicast user can watch eight programs online simultaneously.
User Max
Band Width
This parameter and Unlimited Band Width are mutually exclusive. If you
select Unlimited Band Width, the setting of this parameter is invalid.

NOTE
After selecting Enable Authorization, click Next. In the dialog box that is displayed, configure the rights
profile that is delivered to the multicast user.
6 Click Finish.
7 In the information list, select the multicast user and click the User Multicast VLAN tab in the
lower pane. Right-click the list and choose Add from the shortcut menu.
8 In the dialog box that is displayed, select the multicast VLAN to be bound, and click OK.
----End
Command Reference
Query the
information
about a
multicast
user
display igmp user Privilege mode, BTV mode, MVLAN
mode
Add a
multicast
user
igmp user add BTV mode

Context
configured at the MDU side and the service configuration steps.
Issue 03 (2010-11-19)
Services Steps
l 19.3.4 Configuring an ADSL Line Profile
l 19.3.5 Configuring an ADSL Alarm Profile
l 19.3.6 Configuring the Attributes of an ADSL Port
l 19.3.7 Activating an ADSL Port
Port
l 19.3.2 Configuring an IP Interface
l 19.3.8 Configuring a Static Route
l 19.3.9 Adding an MGC Profile
l 19.3.10 Configuring a UAS Profile
l 19.3.12 Adding an MG
l 19.3.13 Binding an MGC Profile
l 19.3.14 Starting an MG
l 19.3.15 Configuring a VoIP PSTN Port

19.3.2 Configuring an IP Interface
The IP interface is mainly used to forward IP packets at layer 3. The configured IP address is
placed into the IP address pool and functions as the signaling IP address of the MG or the media
IP address, which is used to communicate with the MGC.
19.3.4 Configuring an ADSL Line Profile
An ADSL line profile provides parameters that are required for activating an ADSL port. After
the ADSL line profile is configured successfully, when you configure the attributes of the ADSL
port, you can directly reference the ADSL line profile to limit the port rate and noise margin to
improve the service quality.
19.3.5 Configuring an ADSL Alarm Profile
19-43
When the ADSL port is activated, it directly references the ADSL alarm profile to monitor the
performance of the port. When the actual parameter value of the port exceeds the threshold, the
system generates an alarm.
19.3.6 Configuring the Attributes of an ADSL Port
This topic describes how to configure a line profile, an alarm profile, extended profile (optional)
of an ADSL port. These attributes can be used after the ADSL port is activated.
19.3.7 Activating an ADSL Port
The ADSL port can transmit the service in the normal state only when it is activated successfully.
19.3.8 Configuring a Static Route
This topic describes how to configure the static route between the U2000 server and an ONU.
When the ONU is managed through the SNMP protocol, you can manage and maintain the ONU
by performing this operation.
19.3.9 Adding an MGC Profile
An MGC profile defines the peer parameters of an MG port. To configure the MG port and
enable it to communicate with the MGC, you only need to bind the pre-configured MGC profile
to the MG port. The data of an MG port provides the information about the ports and connections
between the MG and the MGC. Various services are provided through an MG port only when
the MG port is configured properly. Ensure that the data configured on the MG port is the same
as the corresponding data configured on the MGC.
19.3.10 Configuring a UAS Profile
A UAS profile is added when an MG that supports the SIP protocol is added. The SIP protocol
is a control-layer protocol of the IMS and it is one of the framework protocols designed by the
IETF for the multimedia communication system. The SIP protocol is also an application-layer
protocol for creating, modifying, and terminating multimedia sessions. It is used with other
protocols, such as RTP, RTCP, SDP, RTSP, and DNS, to complete session establishment and
media negotiation.
19.3.11 Adding a TID Profile
A terminal ID (TID) is the prefix that a terminal carries when it registers with an MG. A terminal
is a logical entity on the MG and it initiates and receives media streams or control streams. When
creating a terminal, the MG allocates a unique TID to identify the terminal.
19.3.12 Adding an MG
Before provisioning services for network elements, you can add an MG according to the global
data plan to enable the MG port to communicate with the upper layer MGC.
19.3.13 Binding an MGC Profile
This topic describes how to bind a configured MGC profile to an MG interface to configure the
MG interface and interconnect the MG interface with an MGC.
19.3.14 Starting an MG
For the MG that supports the MGCP and H.248 protocols, cold start the MG port so that the MG
port can negotiate with the MGC through the specified MGC protocol. In this case, the MG port
can register with the MGC so that the configured data can take effect. For the MG that supports
the SIP protocol, you also need to restart the MG to make the configuration data to take effect
after the configuration
19.3.15 Configuring a VoIP PSTN Port
This topic describes how to access and configure the VoIP PSTN voice service.
19.3.16 Adding an xPON FTTB Service Provisioning Profile
The U2000 of the latest version plans to use the service provisioning profile to provision services
to users. The service provisioning profile encapsulates common attributes of the service channel
Issue 03 (2010-11-19)
to a profile. To provision services to users, bind this profile to the port, and then set user-defined
service parameters, thus implementing service provisioning at one step.
19.3.17 Configuring an xPON FTTB Service
You can directly configure and provision an xPON FTTB service by binding the configured
xPON FTTB service provision profile with a certain physical port on the ONU.
Context
Before you provision services for network elements, you can add a VLAN or add VLANs in
batches according to the global data plan. When VLANs with continuous IDs and the VLAN
type is consistent with the VLAN attribute, these VLANs can be added in batches. In addition,
the names of the VLANs that are added in batches are generated automatically.
Procedure
19-45
VLAN.
NOTE
NOTE
NOTE
802.1 Priority Indicates the VLAN 802.1 priority. This parameter is applicable
to the VLANs for an ONU.

6 Click Done.
----End
Command Reference
Issue 03 (2010-11-19)

19.3.2 Configuring an IP Interface
The IP interface is mainly used to forward IP packets at layer 3. The configured IP address is
placed into the IP address pool and functions as the signaling IP address of the MG or the media
IP address, which is used to communicate with the MGC.
Prerequisite
An IP interface can be added only after the L3 interface of the VLAN is configured.
Procedure
3 Click the VLAN tab. On the VLAN tab page, set the filter criteria or click to display the
VLANs. Select a record from the VLAN list, and then click the IP Interface tab in the lower
pane.
4 On the IP Interface tab page, right-click, and then choose Add.
5 In the dialog box that is displayed, set the parameters of the IP interface.
6 Click OK.
----End
Procedure
19-47
Key
Parameter
Description
Vlan ID Indicates the VLAN ID of the service virtual port. The VLAN ID uniquely
identifies a VLAN.

NOTE
Select only the MEF IP Traffic Profile that exists on the device. Otherwise, the system reports an error.
5 Click OK.
----End
Command Reference
Query the 802.1x
configuration of a
service virtual port
Issue 03 (2010-11-19)
Bind a service
virtual port with
802.1x
authentication
dot1x service-port Global config mode

19.3.4 Configuring an ADSL Line Profile
An ADSL line profile provides parameters that are required for activating an ADSL port. After
the ADSL line profile is configured successfully, when you configure the attributes of the ADSL
port, you can directly reference the ADSL line profile to limit the port rate and noise margin to
improve the service quality.
Context
l A profile name uniquely identifies a profile. Therefore, the profile name must be specified
and it must be unique. Otherwise, the profile cannot be added.
l You can add profiles that have the same parameters but different names.
Procedure
1 Choose Configuration > Access Profile Management > ADSL Profile from the main menu.
2 Click the ADSL Line Profile tab, and select the required device type from the Device Type
drop-down list.
19-49
5 Click Next.
Issue 03 (2010-11-19)
7 Click Finish.
----End
Command Reference
Add an
ADSL2+
line profile
adsl line-profile add Global config mode, ADSL mode

19.3.5 Configuring an ADSL Alarm Profile
When the ADSL port is activated, it directly references the ADSL alarm profile to monitor the
performance of the port. When the actual parameter value of the port exceeds the threshold, the
system generates an alarm.
Context
l A profile name uniquely identifies a profile. Therefore, the profile name must be specified
and it must be unique. Otherwise, the profile cannot be added.
l You can add profiles that have the same parameters but different names.
19-51
Procedure
1 Choose Configuration > Access Profile Management > ADSL Profile from the main menu.
2 Click the ADSL Alarm Profile tab, and select the required device type from the Device Type
drop-down list.
5 Click OK.
----End
Command Reference
Add an
ADSL2+
alarm
profile
adsl alarm-profile add Global config mode, ADSL mode

19.3.6 Configuring the Attributes of an ADSL Port
This topic describes how to configure a line profile, an alarm profile, extended profile (optional)
of an ADSL port. These attributes can be used after the ADSL port is activated.
Context
You can modify the attributes of a port when the port is in the activated, activating, or deactivated
state. If the port is in the deactivated state, modify the port attributes directly. If the port is in
the activated or activating state, deactivate it before modifying the port attributes.
Issue 03 (2010-11-19)
Procedure
2 Choose DSL > ADSL from the navigation tree.
3 On the ADSL tab page, set the filter criteria or click to display the ADSL ports.
4 In the information list, select an ADSL port record, right-click, and then choose Configure
Attributes.
5 In the dialog box that is displayed, bind the ADSL port to the corresponding profile.
6 Click OK.
----End
Command Reference
Query the
status of
ADSL2+
ports and
the
information
about their
activation
profiles
display adsl port state Privilege mode

19.3.7 Activating an ADSL Port
The ADSL port can transmit the service in the normal state only when it is activated successfully.
19-53
Context
l The ADSL port must be activated and then it can transmit the service.
l Before configuring new parameters to an activated port, you need to deactivate the port,
configure the port with a profile with the new parameters, and then activate the port.
l When you activate a port:
If the ATU-R is online (powered on), the activating process is complete after the training
is successful.
If the ATU-R is offline (powered off), the connection set up during the activating process
is interrupted, and the ATU-C is in the detection state. When the ATU-R is powered on
again, the training automatically initiates. If the training is successful, the port is
activated.
Procedure
2 Choose DSL > ADSL from the navigation tree.
3 On the ADSL tab page, set the filter criteria or click to display the ADSL ports.
4 In the information list, select an ADSL port to be activated, right-click, and then choose
Activate.
----End
Command Reference
Activate an
ADSL2+
port
activate ADSL mode

This topic describes how to configure the static route between the U2000 server and an ONU.
When the ONU is managed through the SNMP protocol, you can manage and maintain the ONU
by performing this operation.
Prerequisite
The ONU must be managed through the SNMP protocol.
Procedure
2 Choose Static Route from the navigation tree.
Issue 03 (2010-11-19)
Key
Parameter
Description
Target IP
Address
Indicates the destination IP address. It is used to identify the destination IP
address or destination network of IP packets.
Target Mask Indicates the subnet mask of the IP address. A subnet mask consists of
consecutive 1s and can be represented in dotted decimal notation when it is
written in the text format. The subnet mask and the destination IP address
identify the address of the network segment where the destination host or
router is located. You can obtain the address of the network segment by
performing a logical AND operation on the destination IP address and the
subnet mask.
Next Hop IP
Address
Indicates the next hop IP address, which is used to identify the next router
on the route of IP packets. Latest configuration of the next hop IP address
automatically overwrites the previous one and becomes the next hop IP
address in the current route information.

5 Click OK.
----End
Command Reference
Query the
static route
between the
U2000 server
and an ONT
display ont snmp-route GPON mode
Set the static
route between
the U2000
server and an
ONT
ont snmp-route Privilege mode, BTV mode,
MVLAN mode

19-55
19.3.9 Adding an MGC Profile
An MGC profile defines the peer parameters of an MG port. To configure the MG port and
enable it to communicate with the MGC, you only need to bind the pre-configured MGC profile
to the MG port. The data of an MG port provides the information about the ports and connections
between the MG and the MGC. Various services are provided through an MG port only when
the MG port is configured properly. Ensure that the data configured on the MG port is the same
as the corresponding data configured on the MGC.
Procedure
1 Choose Configuration > Access Profile Management > MGC Profile from the main menu.
Key
Parameter
Description
Name Indicates the name of an MGC profile. It is used to uniquely identify an MGC
profile.
Protocol
Type
When you configure the MGC, set Protocol Type to H.248 or MGCP
according to the system protocol. When you configure the association, set
Protocol Type to xUA.
DNS Name Specifies the domain name of the MGC. The domain name is used to identify
the MGC.
NOTE
l You must set both or either of DNS Name and IP Address. If DNS Name and IP
Address are set, the system analyzes the domain name to obtain the IP address of
the MGC. If the analysis fails, the system uses the pre-configured IP address.
l This parameter is available when the Protocol Type is set to H.248 or MGCP.
Issue 03 (2010-11-19)
Key
Parameter
Description
IP Address
1/IP
Address
Indicates peer end IP address 1.
If you set Protocol Type to H.248 or xUA, the name of this parameter is IP
Address 1.
If you set Protocol Type to MGCP, the name of this parameter is IP
Address.
IP Address 2 Indicates peer end IP address 2. This parameter is used to implement SCTP
multi-homing. Therefore, this parameter takes effects only when the
transmission protocol of the MG port is set to the SCTP protocol.

4 Click OK.
----End
Command Reference
Configure the attributes of an
MG port that supports the H.
248 protocol
if-h248 attribute H.248 mode
MG port that supports the
MGCP protocol
if-mgcp attribute MGCP mode

NOTE
The MGC profile is encapsulated by the U2000. No command is available for the MGC profile in the CLI
of the device.
19.3.10 Configuring a UAS Profile
A UAS profile is added when an MG that supports the SIP protocol is added. The SIP protocol
is a control-layer protocol of the IMS and it is one of the framework protocols designed by the
IETF for the multimedia communication system. The SIP protocol is also an application-layer
protocol for creating, modifying, and terminating multimedia sessions. It is used with other
protocols, such as RTP, RTCP, SDP, RTSP, and DNS, to complete session establishment and
media negotiation.
Procedure
1 Choose Configuration > Access Profile Management > UAS Profile from the main menu.
19-57
Key
Parameter
Description
Address
Mode
Indicates the address mode of the SIP MG.
Enumerated type. The options are Fix mode and DNS-A query mode.
IP Address 1 Indicates the IP address of the proxy server of the SIP MG.
This parameter is available only when Address Mode is set to Fix mode.
IP Address 2 Indicates the standby IP address of the proxy server of the SIP MG.
This parameter is available only when Address Mode is set to Fix mode.
Proxy Port Indicates the port ID of the proxy server of the SIP MG.
Domain
Name
Indicates the name of the home domain of the SIP MG.
This parameter is available only when Address Mode is set to DNS-A query
mode.

4 Click OK.
----End
Command Reference
Configure the mandatory
attributes of an SIP interface
if-sip attribute basic STP mode

NOTE
The MGC profile is encapsulated by the U2000. No command is available for the MGC profile in the CLI
of the device.
Issue 03 (2010-11-19)
19.3.11 Adding a TID Profile
A terminal ID (TID) is the prefix that a terminal carries when it registers with an MG. A terminal
is a logical entity on the MG and it initiates and receives media streams or control streams. When
creating a terminal, the MG allocates a unique TID to identify the terminal.
Prerequisite
The U2000 must work in the normal state.
Procedure
1 Choose Configuration > Access Profile Management > TID Profile from the main menu.
3 In the New TID Profile dialog box, set Name to tid-profile_1 and set other parameters.
Format Indicates the format character string. It
defines the format of the character string
generated by the parameter list.
Parameter List Indicates the parameters to be converted to a
character string. The number of parameters
must be the same as that defined in the format
character string.
19-59

4 Click OK.
----End
Command Reference
Add a user-defined TID
profile.
tid-template add Global config mode

19.3.12 Adding an MG
Before provisioning services for network elements, you can add an MG according to the global
data plan to enable the MG port to communicate with the upper layer MGC.
Prerequisite
The signaling IP address and media IP address must exist in the corresponding IP address pool.
Context
l The MG ID must be unique on a device.
l The MG parameters must be set to be the same as the corresponding MGC parameters.
l You can configure up to eight MGs on an OLT.
l After the MG is added, you must perform the cold starting or recovering operation so that
the MG can work in the normal state.
l After the MG is added successfully, the system adds two MGCs concurrently. This MG
can provide services for the user when the MG communicates with only one MGC.
l The H.248 protocol separates the signaling stream and the media stream and uses different
QoS policies for the two types of streams.
NOTE
The procedure for adding the MG supporting the H.248, MGCP, and SIP protocols are the same. The
difference only lies in the parameter settings. The following figure considers only the procedures for adding
the MG supporting the H.248 and SIP protocols as an example.
Procedure
2 Choose Voice Gateway > Media Gateway from the navigation tree.
3 On the Media Gateway tab page, set the filter criteria to display the required MGs.
Adding the MG supporting the H.248 protocol:
Issue 03 (2010-11-19)
Key
Parameter
Description
MG ID Indicates the ID of the MG. It uniquely identifies an MG.
MG Message
MID Type
Indicates the message ID (MID) type of the H.248 message. The MID exists
in the header of a message and identifies the message sender.
Relation to other parameters:
After an MID type is selected, you must configure its attributes.
l If the MID type is selected as signaling IP address, you must set
Signaling IP Address.
l If the MID type is selected as MG domain name, you must set MG
Domain Name.
l If the MID type is selected as MG device name, you must set MG Device
Name.
Signaling IP
Address
Indicates the signaling IP address of the MG.
NOTE
The signaling IP address must exist in the IP address pool. It can be the same as the
media IP address.
Transmission
Mode
Indicates the transmission mode that the MG uses.
19-61
Key
Parameter
Description
Profile Name Indicates the name and version of the profile used by the MG.
After this parameter is set, the H.248 protocol can adapt certain parameters
between the MG and the MGC through the profile negotiation. If the
negotiation fails, the MG fails to register with the MGC. Hence, the device
defines profiles according to customers' requirements.
NOTE
l The values of the Profile Name parameter displayed in the interface are the preset
profile names provided by the device. Therefore, they cannot be modified through
the U2000.
l In the case of the customized profile named CustomizingProfileTemplet, you
can modify the profile name through the CLI on the device. Then, the U2000
obtains the profile name that is used by the device port by querying the details of
the device port.

Adding the MG supporting the SIP protocol:
Key
Parameter
Description
MG ID Indicates the ID of the MG. It is used to uniquely identify the MG.
Signaling IP
Address
Indicates the signaling IP address of the MG.
Issue 03 (2010-11-19)
Key
Parameter
Description
Signaling
Port No.
Indicates the number of the signaling port that the MG uses.
Media IP
Address 1
Indicates the IP address of the media traffic that is controlled by the signaling.
Profile Name Indicates the name and version of the profile used by the MG.
NOTE
l The values of the Profile Name parameter displayed in the interface are the preset
profile names provided by the device. Therefore, they cannot be modified through
the U2000.
l In the case of the customized profile named CustomizingProfileTemplet, you can
modify the profile name through the CLI on the device. Then, the U2000 obtains
the profile name that is used by the device port by querying the details of the device
port.

6 Click OK.
----End
Command Reference
Query the running status and
basic configuration of all the
MG ports that support the H.
248 protocol in the current
system
display if-h248 all Common user level
Query the running status of all
the MG ports that support the
SIP protocol in the current
system
display if-sip all Common user level
Query the running status and
basic configuration of all the
MG ports that support the
MGCP protocol in the current
system.
display if-mgcp all Common user level
Configure the attributes of the
MG ports that support the H.
248 protocol
Configure the attributes of the
MG ports that support the
MGCP protocol
if-mgcp attribute MGCP mode
Configure the mandatory
attributes of the SIP interface
if-sip attribute basic STP mode
19-63

NOTE
In the CLI of the device, the configuration of the MG ports that support the H.248, MGCP, and SIP protocols
consists of a series of command lines. For details, see the command reference manuals of the device.
19.3.13 Binding an MGC Profile
This topic describes how to bind a configured MGC profile to an MG interface to configure the
MG interface and interconnect the MG interface with an MGC.
Procedure
1 In the Main Topology, double-click the required MDU in the Physical Root navigation tree; or
right-click the required MDU and choose NE Explorer from the shortcut menu.
4 In the information list, select a record and click the MGC Attribute Info tab in the lower pane.
In the list, right-click a record and choose Bind Profile from the shortcut menu.
Key
Parameter
Description
MGC Index When the H.248 protocol is used, an MG interface can initiate the
registration with two MGCs but the MG interface registers with only one
MGC at the same time. When an MGC is faulty and cannot communicate
with MGs, the MG interface registers with the other MGC automatically.
The MGC indexes are 0 to 1 and the priority of index 0 is higher than the
priority of index 1.

6 Click OK.
----End
Issue 03 (2010-11-19)
Command Reference
MG interface when the H.248
protocol is used.

19.3.14 Starting an MG
For the MG that supports the MGCP and H.248 protocols, cold start the MG port so that the MG
port can negotiate with the MGC through the specified MGC protocol. In this case, the MG port
can register with the MGC so that the configured data can take effect. For the MG that supports
the SIP protocol, you also need to restart the MG to make the configuration data to take effect
after the configuration
Procedure
4 Select a record to be configured from the MG list, right-click, and then choose Recover (H.248)
or Reset (MGCP/SIP) from the shortcut menu.
5 In the dialog box that is displayed, click Yes.
----End
Command Reference
Reset the specified MG port
that supports the H.248,
MGCP, and SIP protocols
reset H.248 mode
MGCP mode
SIP mode

19.3.15 Configuring a VoIP PSTN Port
This topic describes how to access and configure the VoIP PSTN voice service.
Prerequisite
l The network devices and lines must be in the normal state.
19-65
l A proper MGC profile that supports the H.248 and MGCP protocols or UAS profile that
supports the SIP protocol must be configured. For details, see 19.3.9 Adding an MGC
Profile or 19.3.10 Configuring a UAS Profile.
l The MG port that supports the H.248 and MGCP protocols or the SIP interface that supports
the SIP protocol must be configured. Foe details, see 19.3.12 Adding an MG.
l The OLT can interconnect with the MGC or IMS port (that supports the SIP protocol).
Context
The OLT accesses the VoIP PSTN service stream through the voice service profile and transmits
the service stream upstream to the IP network through the control board, thus providing the VoIP
PSTN service.
Procedure
2 Choose ASL > POTS Port from the navigation tree.
3 Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN
ports.
4 Select a record from the VoIP PSTN port list, right-click, and then choose Configure
Attribute from the shortcut menu.
NOTE
If selecting multiple records, you can configure the attributes in batches.
5 In the dialog box that is displayed, click the Service Details tab. Configure the attributes of the
VoIP PSTN port, including MG ID and Telephone No.
Issue 03 (2010-11-19)
Key
Parameter
Description
MG ID Definition:
Indicates the MG ID corresponding to the VoIP PSTN port.
Telephone No Definition:
Indicates the telephone number bound to the VoIP PSTN user.
l The telephone number that is set here is invalid. The valid telephone
numbers are set on the MGC.
l The telephone number that is set here is used for standalone paging only
when the standalone function is configured and enabled.
l If this parameter is not set, the telephone number is empty by default.
Terminal ID Definition:
Indicates the ID of the physical terminal corresponding to the VoIP PSTN
user.
One VoIP PSTN user occupies only one terminal ID.
NOTE
l This parameter is available only when the TID profile bound with the ISDN PSTN
user on the MG is configured to not support the terminal layering function.
l This parameter is mandatory if the Terminal ID Auto Selected check box is not
selected.

6 Click the Physical Details tab. Configure the physical attributes of the VoIP PSTN port,
including High Level Width, Reversed Polarity, and Dial Mode.
19-67
Key
Parameter
Description
Dial Mode Indicates the dial mode of the VoIP PSTN port.
NOTE
l DTMT: It is the dual tone multi-frequency mode. The dial tones of common fixed-
line phones adopt two high and low frequency groups and 16 frequency
combinations to represent the keys, such as keys 0 to 9, the * key, and the # key,
and transmit the user dialing signaling.
l Pulse: During the dialing, each digit is represented by a group of pulses. These
pulses connect or disconnect the current in the telephone lines in an instant.

7 Click OK.
----End
Command Reference
Query the status
of one or more
PSTN ports
display pstn state
NOTE
l If the system currently supports are the H.248,
MGCP, or SIP protocol, the command format
is different.
l If you need to query the status in ESL user
mode, run the config command to enter global
config mode, run the esl user command to
enter ESL user mode, and then run the display
pstn state command.
l If you need to query the status in PSTN port
mode, run the config command to enter global
config mode, run the pstnport command to
enter PSTN port mode, and then run the
display pstn state command.
Privilege mode, ESL user
mode, PSTN port mode
Configure the
attributes of an
existing PSTN
user
mgpstnuser attribute set
NOTE
l Before running this command, run the
config command to enter the global config
mode, and then run the esl user command to
enter the ESL user mode.
l You can configure the attributes of a PSTN
user only after the PSTN user is added.
l You can configure the attributes of a PSTN
user by specific physical position (the shelf
ID, slot ID, and port ID) or by "MG port ID +
terminal ID". When the TID profile bound
with the ISDN PSTN user on the MG port is
configured to support the terminal layering
function, you can configure the attributes only
by physical position.
ESL user mode
Issue 03 (2010-11-19)
Configure the
attributes of the
existing PSTN
users in batches
mgpstnuser attribute batset
NOTE
See the precaution of the mgpstnuser attribute set
command.
ESL user mode

19.3.16 Adding an xPON FTTB Service Provisioning Profile
Prerequisite
l If the ports on an ONU are ADSL ports, perform the operations in 19.3.4 Configuring an
ADSL Line Profile and 19.3.5 Configuring an ADSL Alarm Profile before configuring
the Basic Info branch.
l Perform the operations in 19.2.1 Configuring a VLAN and 19.2.2 Configuring an MEF
IP Traffic Profile before configuring the Service Port branch.
l Perform the operations in 19.2.7 Configuring the Multicast VLAN before configuring
the Multicast User branch.
Procedure
1 Choose Configuration > Access Profile Management > Service Provisioning Profile from
the main menu.
2 Click the xPON FTTB Service Provisioning Profile tab.
19-69
Issue 03 (2010-11-19)
19-71
Key
Parameter
Description
Basic Info
Name Indicates the name of the xPON FTTB service provisioning profile.
ONU Port Information
Port Type Indicates the type of an ONU port.
NOTE
You can set the port type according to different ONUs.
Port Mode Indicates the mode of ONU port.
Enumerated type. The options are ATM and PTM.
This parameter is available when Port Type is set to VDSL2 or
G.SHDSL.
ServicePort
Service
Priority
Definition:
Specifies the service priorities for different services.
NOTE
The voice service has the highest priority, the multicast server has the medium priority,
and the Internet service has the lowest priority.
ONU Side Configuration
Issue 03 (2010-11-19)
Key
Parameter
Description
Service Type Indicates the type of services carried on the service virtual port.
The port can work in the following modes:
l Single: Each service virtual port maps a service stream. Different service
streams can be distinguished by different service virtual ports.
l Multi-Service VLAN: Each service virtual port carries multiple service
streams. You need to set User-Side VLAN to distinguish the service
streams. The services are distinguished based on the VLAN ID contained
in the packets from the service virtual ports. You can label the packets
with different upstream VLAN IDs.
l Multi-Service Encapsulation: Each service port carries multiple service
streams. You need to set User-Side Encapsulation to distinguish the
service streams. The services are distinguished based on the
encapsulation types (IPoE/PPPoE) of the packets from the subscriber
ports. You can label the packets with different upstream VLAN IDs.
l Multi-Service VLAN+802.1p: Each service virtual port carries multiple
service streams. You need to set User-Side VLAN and 802.1p
Priority to distinguish the service streams. The services are
distinguished according to the VLAN IDs and the 802.1p priorities of
the packets from the subscriber ports.
NOTE
This parameter is available only when the Service Priority is set.
l Multi-Service VLAN+Encapsulation: Each service virtual port carries
multiple service streams. You need to set User-Side VLAN and User-
Side Encapsulation to distinguish the service stream.
OLT Side Configuration
19-73
Key
Parameter
Description
VLAN Switch
Mode
Specifies the mode of switching the VLAN tag of the packets of the service
virtual port.
Enumerated type. The options are as follows:
l Default: Indicates that a VLAN tag is added to the upstream packet of
the service virtual port and the VLAN tag is deleted from the downstream
packets of the service virtual port.
l Transparent: Indicates that the upstream packet of the service virtual port
is transmitted transparently and the VLAN tag is not switched.
l Translate: Indicates that the VLAN tag in the upstream packet is
transmitted upstream after being switched to the specified VLAN tag.
The VLAN tag is then switched back to the original VLAN tag in the
downstream direction.
l Translate_And_Add: Indicates that the VLAN tag of the upstream
packet of the service virtual port is switched and another VLAN tag is
added to the packet. In the downstream direction, the added VLAN tag
is deleted from the downstream packets and switched back to the original
VLAN tag.
l Add_Double: Indicates that two VLAN tags are added to the upstream
packets of the service virtual port and then the VLAN tags are deleted
from the downstream packets of the service virtual port.
NOTE
This parameter is available when VLAN Attribute is set to QinQ.
Multicast User
IGMP Flow
Channel
Specifies the protocol traffic channel of the multicast service.
Enumerated type. Select a protocol traffic channel by setting the Service
Port parameter.
Multicast
VLAN
Specifies the multicast VLAN ID.

4 Click OK.
----End
19.3.17 Configuring an xPON FTTB Service
You can directly configure and provision an xPON FTTB service by binding the configured
xPON FTTB service provision profile with a certain physical port on the ONU.
Prerequisite
l The OLT that the ONU is connected to must be in the profile mode.
l The configured xPON FTTB service profile must be applied to the ONU. For details, see
19.3.16 Adding an xPON FTTB Service Provisioning Profile.
Issue 03 (2010-11-19)
Context
The physical ports that can be configured on the ONU include the Ethernet port, ADSL port,
and VDSL2 port. This section considers the Ethernet port as an example.
Procedure
2 Choose ETH from the navigation tree.
3 Click the Ethernet Port tab, and set the filter criteria or click to display the Ethernet ports.
4 Select a record from the Ethernet port list, right-click, and then choose Add Service from the
shortcut menu.
NOTE
You can modify the parameters in the selected service provisioning profile.
In the Add Service dialog box that is displayed, click next to Service Provisioning
Profile, In the Add Service dialog box that is displayed, click Find to display the required
service provisioning profiles that meet the filtering criteria. Select a record from the profile list,
and click OK.
6 Click OK.
----End
19-75
19.4 Configuration Examples of the GPON FTTB Services
services in a GPON FTTB network.
19.4.1 Data Plan for the GPON FTTB Services
This topic provides the data plan for the configuration examples of the GPON FTTB services.
You can configure the services according to the data plan.
19.4.2 Configuring the GPON FTTB Internet Service (LAN Access)
This topic describes how to configure the high-speed Internet service when a user is connected
to an MDU in LAN access mode and the MDU is connected to an OLT through a GPON port.
19.4.3 Configuring the GPON FTTB Internet Service (ADSL2+ Access)
to an MDU in ADSL2+ access mode and the MDU is connected to an OLT through a GPON
port.
19.4.4 Configuring the GPON FTTB Internet Service (VDSL2 Access)
to an MDU in VDSL2 access mode and the MDU is connected to an OLT through a GPON port.
19.4.5 Configuring the GPON FTTB Multicast Service
This topic describes how to configure the multicast service when an MDU is connected to an
OLT through a GPON port.
19.4.6 Configuring the GPON FTTB Voice Service (H.248 Protocol)
This topic describes how to configure the voice service when an MDU is connected to an OLT
through a GPON port.
19.4.7 Configuring the GPON FTTB Voice Service (SIP Protocol)
19.4.8 Configuring the GPON FTTB Service by Using a Service Provisioning Profile
This topic describes how to configure various services when a user is connected to an MDU in
LAN access mode and the MDU is connected to an OLT through a GPON port.
19.4.1 Data Plan for the GPON FTTB Services
This topic provides the data plan for the configuration examples of the GPON FTTB services.
Issue 03 (2010-11-19)
Data Plan
Table 19-1 Data plan for the GPON FTTB services
Service
Type
Item Settings Remarks
Device
managemen
t
Management
VLAN of an OLT
l VLAN ID: 8
l Type: Smart VLAN
The management
VLAN of an OLT is
the management
VLAN between the
OLT and an MDU.
Upstream port of the
OLT
0/19/0 -
Layer 3 interface IP Address: 192.168.50.4 The IP address of the
Layer 3 interface of
the management
VLAN of the OLT
functions as the IP
address of the OLT
for inband network
management.
GPON port of the
OLT
0/2/1 -
MDU
0/0/1 -
Service port of the
MDU
0/1/1 -
19-77
Service
Type
MDU l Name: MDU
l ONU ID: 0
l ONU Type: MDU
l Authentication Mode: SN
l SN: 485754438E1CDE42
l Manager VLAN: 8
l IP Address: 192.168.50.2
l IP Address Mask:
255.255.255.0
To configure the
MDU on the OLT in
Telnet mode, ensure
that the management
VLANs of the OLT
and the MDU are the
same and the
management IP
addresses of the
OLT and the MDU
are in the same
network segment.
When the MDU is
connected to the
OLT through a
GPON port, the
MDU uses the
SNMP protocol as
the network
management
protocol and does
not require service
profiles.
MDU SNMP profile l Name: snmpprofile
l SNMP Version: v1
l Read Name: public
l Trap Host IP: 192.168.50.3
l SNMP Security Name:
public
-
Service virtual port
(based on the
management
VLAN)
l VLAN ID: 8
l Interface Selection:
0/2/1/0/0
l Service Type: Multi-
Service VLAN
l User VLAN: 8
l Upstream Traffic Name:
FTTx
After the MDU is
added to the U2000
successfully, a
control channel has
been established but
no data channel is
established. In this
case, you need to
create a service
virtual port on the
OLT to help the
OLT manage the
MDU.
Issue 03 (2010-11-19)
Service
Type
MEF IP traffic
profile
l Name: FTTx
l CIR: 20480
l Outer Priority: 1
The MEF IP traffic
profile is used on the
OLT or MDU to
control upstream
and downstream
traffic.
DBA profile l Name: FTTx
l T-CONT type: Maximum
Bandwidth
l Maximum Bandwidth:
32768
-
Line profile l Name: FTTx
l Mapping Mode:VLAN
l Qos Mode:Priority Queue
l T-CONT Index: 1
l DBA Profile: FTTx
l GEM Port Index: 1
l Priority Queue:1
Different services
have different GEM
port IDs, and the
GEM port IDs map
VLAN IDs.
Internet
service
VLAN l VLAN ID: 1001
l Type: Smart VLAN
l Attribute: QinQ
l In the case of the
Internet service,
users are
identified by
QinQ VLANs. A
CVLAN is
allocated to each
user on the MDU
and an SVLAN
is allocated to
each slot, port, or
OLT according
to networking
scenarios.
l Plan VLANs for
the MDUs that
are connected to
the same OLT in
a centralized
manner and
ensure that each
VLAN is unique
to an MDU.
19-79
Service
Type
on the OLT side
l Name: HSI
l VLAN ID: 1001
0/2/1/0/0
Service VLAN
l User VLAN: 1001
l Upstream Traffic Name: ip-
traffic-table_6
-
on the MDU side
l Name: HSI
l Vlan ID: 1001
l Interface Selection: 0/1/1
l User VLAN: untagged
FTTx
-
IPTV
service
VLAN l VLAN ID: 1000, 3000
l Type: Smart VLAN
-
on the OLT side
l Name:IGMP
l Vlan ID: 1000
0/2/1/0/0
Service VLAN
l User VLAN: 1000
l Keep the upstream and
downstream settings the
same: selected
FTTx
-
Multicast VLAN on
the OLT side
l IGMP Version: IGMP V3
l Work Mode: igmp_proxy
l VLAN ID: 1000
-
Program profile l Name: program1
l Start IP Address: 224.0.1.1
l End IP Address: 224.0.1.1
l Source IP Address:
10.10.10.20
l Preview Profile: 0 (the
default value)
-
Issue 03 (2010-11-19)
Service
Type
Multicast user l Alias: IGMPUserA
l Unlimited Band Width:
selected
l Select Service Port: service
virtual port named IGMP
-
Multicast VLAN on
the MDU side
l Work Mode:
igmp_snooping
l VLAN ID: 1000
-
on the MDU side
l Name: IGMP
l Vlan ID: 1000
Service VLAN
same: selected
FTTx
-
VoIP
service
l Type: Smart VLAN
-
on the OLT side
l Name: VOIP
l Vlan ID: 2000
0/2/1/0/0
Service VLAN
l User VLAN: 2000
same: selected
FTTx
-
19-81
Service
Type
Signaling IP address
Media IP address
17.10.10.10 The H.248 and SIP
protocols support
separation of media
and signaling
streams. The media
and signaling IP
addresses can be the
same or different.
Gateway 17.10.10.1 -
Parameters of the
MG interface (H.
248 protocol)
NOTE
The parameters of the
MG interface must be
the same as the
parameters on the
media gateway
controller (MGC).
There are many
negotiation
parameters in the H.
248 protocol. This
table provides the
mandatory
248 protocol.
l MG ID: 0
l Name: mg1
l Signaling Port No.:2944
l Transmission Mode: UDP
The ID of the MG
interface used for
the VoIP service
determines the
virtual access
gateway (VAG) that
a service user is
assigned to.
MGC profile l Name: mgcprofile1
l IP Address 1:
200.200.200.200
l Port Number: 2944
-
Issue 03 (2010-11-19)
Service
Type
Parameters of the
SIP interface (SIP
protocol)
NOTE
SIP interface must be
the same as the
parameters on the IP
multimedia
subsystem (IMS).
There are many
negotiation
parameters in the SIP
protocol. This table
provides the
mandatory
protocol.
l MG ID: 0
l Name: mg1
l Signaling IP Address:
17.10.10.10
l Signaling Port No.: 5060
l Media IP Address 1:
17.10.10.10
l MG Domain Name:
huawei.com
l Active NMS UAS Profile:
uasprofile1
The ID of the SIP
interface used for
the VoIP service
determines the VAG
that a service user is
assigned to.
UAS profile l Name: uasprofile1
l Address Mode: Fix mode
l IP Address 1:
200.200.200.200
l Proxy Port: 5060
-
PSTN user Phone 1-Phone 2:
83110000-83110001
-

19.4.2 Configuring the GPON FTTB Internet Service (LAN Access)
to an MDU in LAN access mode and the MDU is connected to an OLT through a GPON port.
Prerequisite
The OLT must be added to the U2000.
Context
For details of the data plan, see 19.4.1 Data Plan for the GPON FTTB Services.
Example Network
MA5620, MA5626, MA5610, and MA5612 support LAN access. The configuration procedure
in this topic is applicable to the MA5620 V800R308, MA5626 V800R308, MA5612 V800R308,
and MA5610 V800R308.
19-83
l The PC that gains access to the network by means of PPPoE dialup is connected to an FE
port on the MDU and the MDU is connected to the OLT and then to the upper layer network
through a GPON port. In this case, the high-speed Internet service is available for the PC.
l The high-speed Internet service is identified by two VLANs that are accurately bound. A
user VLAN is allocated to each user on the MDU and a service VLAN is allocated to each
slot on the OLT.
l The following two profiles are used for the high-speed Internet service:
DBA profile in which T-CONT type is set to Assured Bandwidth/Maximum
Bandwidth and Maximum Bandwidth is set to 32768Kbit/s
MEF IP traffic profile in which CIR is set to 20480Kbit/s
Figure 19-1 Configuring the GPON FTTB Internet service (LAN access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
l Add the MDU to the U2000 in profile mode.
1. Configure a management VLAN on the OLT side. For details, see 19.2.1
Configuring a VLAN.
Issue 03 (2010-11-19)
A management VLAN is the VLAN through which the OLT manages the MDU. The
OLT manages the MDU through the SNMP protocol. The IP address of the Layer 3
interface of the management VLAN must be in the same network segment as the
management IP address of the MDU.
(1) In the Main Topology, double-click the required OLT in the Physical Root
navigation tree; or right-click the required OLT and choose NE Explorer from
the shortcut menu.
(3) On the VLAN tab page, right-click and choose Add from the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
Click the Upstream Port tab and add upstream port 0/19/0 as the upstream
port of the VLAN.
19-85
IP Address: 192.168.50.4
(6) Click Done.
2. Configure an MDU SNMP profile. For details, see 19.1.1 Configuring an MDU
SNMP Profile.
(1) Choose Configuration > Access Profile Management > MDU SNMP
(2) Click the MDU SNMP Profile tab.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap Host IP: 192.168.50.3 (IP address of the U2000 server)
Trap UDP Port: 162
SNMP Security Name: public
(5) Click OK.
the shortcut menu.
3. Configure a DBA profile. For details, see 19.1.2 Configuring a DBA Profile.
Issue 03 (2010-11-19)
(1) Choose Configuration > Access Profile Management > GPON Profile from
the main menu.
(2) Click the DBA Profile tab.
Name: FTTx
T-CONT type: Maximum Bandwidth
Maximum Bandwidth: 32768
(5) Click OK.
the shortcut menu.
4. Configure a line profile. For details, see 19.1.3 Configuring a GPON Line
Profile.
In a line profile, a GEM port can be bound to up to eight service streams. In a GEM
port, different GEM connections need to be set up for different service streams.
In this example, the mapping between GEM ports and MDU-side services is
implemented through VLANs, and the service streams of each service are mapped to
GEM port 1. In addition, different GEM connections are set up for the management
VLAN and the VLANs for the Internet, multicast, and voice services.
the main menu.
(2) Click the Line Profile tab.
Set Name to FTTx.
Choose Base Info. from the navigation tree and set the parameters.
Mapping Mode: VLAN
19-87
Right-click T-CONT Info. in the navigation tree and choose ADD T-
CONT from the shortcut menu. In the dialog box that is displayed, set the
parameters.
T-CONT Index: 1
DBA Profile: FTTx
Right-click T-CONT1 in the navigation tree and choose Add GEM Port
from the shortcut menu. In the dialog box that is displayed, set the parameters.
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
Right-click GEM Port1 in the navigation tree and choose Add GEM
Connection from the shortcut menu. In the dialog box that is displayed, set
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
19-89
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
5. Confirm the MDU on the OLT side. For details, see 19.1.4 Confirming an
MDU.
the shortcut menu.
(2) Choose GPON > GPON UNI Port from the navigation tree.
(3) On the GPON UNI Port tab page, set the filter criteria to display the required
GPON UNI ports.
(4) In the information list, right-click GPON UNI port 0/2/1 and choose Enable
ONU Auto Find from the shortcut menu.
(5) Click the Auto-Discovered ONU Info tab in the lower pane, right-click the ONU
with SN 485754438E1CDE42, and then choose Confirm ONU from the shortcut
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
On the Basic Parameters tab page, set the parameters.
Line Profile: FTTx (click next to Line Profile and select the line profile
named FTTx in the dialog box that is displayed)
SN: 485754438E1CDE42
On the Network Management Channel Parameters tab page, set the
parameters.
OLT sets network management channel parameters: selected
19-91
SNMP Profile: snmpprofile (click next to SNMP Profile and select
the MDU SNMP profile named snmpprofile in the dialog box that is
displayed)
Manager VLAN: 8
IP Address: 192.168.50.2 (this IP address is in the same network segment
as the IP address of the L3 interface of the management VLAN)
IP Address Mask: 255.255.255.0
(6) Click OK.
6. Add a service virtual port on the OLT side. For details, see 19.1.6 Adding a
Service Virtual Port and 19.1.7 Checking the Communication Between the OLT
and MDU.
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
(4) In the information list, right-click GPON UNI port 0/2/1 and click the
ServicePort Info tab in the lower pane.
(5) On the ServicePort Info tab page, right-click and choose Add from the shortcut
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
Upstream Traffic Name: ip-traffic-table_6 (it is recommended that you use
the default profile ip-traffic-table_6 because the OLT does not limit the rates
of service streams in the management VLAN)
(7) Click OK.
l Configure the Internet service on the OLT side.
The prerequisite for performing operations in the navigation tree is to navigate to the NE
Explorer of the OLT. To navigate to the NE Explorer of the OLT, do as follows: In the
Main Topology, double-click the required OLT in the Physical Root navigation tree; or
1. Configure a service VLAN on the OLT side. For details, see 19.2.1 Configuring
a VLAN.
19-93
A service VLAN is the VLAN used for the Internet service.
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(4) Click Next. Click the Upstream Port tab and add upstream port 0/19/0 as the
upstream port of the VLAN.
(5) Click Done.
Service Port.
(1) On the VLAN tab page, select the record where VLAN ID is set to 1001 and
click the ServicePort tab in the lower pane.
Name: HSI
Issue 03 (2010-11-19)
Connection Type: LAN-GPON (when the physical port is a GPON port) or
LAN-EPON (when the physical port is an EPON port)
Interface Selection: 0/2/1/0/0 (when the connection type is LAN-GPON) or
0/2/1/0 (when the connection type is LAN-EPON)
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
l Configure the Internet service on the MDU side.
Explorer of the MDU. To navigate to the NE Explorer of the MDU, do as follows: In the
Main Topology, double-click the required MDU in the Physical Root navigation tree; or
1. Configure an MEF IP traffic profile. For details, see 19.2.2 Configuring an MEF
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
19-95
the shortcut menu.
2. Configure a service VLAN on the MDU side. For details, see 19.2.1 Configuring
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
(4) Click Next.
(5) Click the Upstream Port tab and add upstream port 0/0/1 as the upstream port
of the VLAN.
(6) Click Done.
3. Add a service virtual port on the MDU side. For details, see 19.3.3 Adding a
Service Port.
Issue 03 (2010-11-19)
Name:HSI
Connection Type: LAN-ADSL (when the physical port is an ADSL port) or
LAN-VDSL2 (when the physical port is a VDSL2 port) or LAN-ETHER
(when the physical port is an Ethernet port)
Vlan ID: 1001
Interface Selection: 0/1/1
VPI: 0 (when the physical port is an ADSL or VDSL2 port)
VCI: 0 (when the physical port is an ADSL or VDSL2 port)
User VLAN: untagged
Upstream Traffic Name: FTTx
(4) Click OK.
----End
Result
The user gains access to the Internet after the dialup is performed successfully by the PPPoE
dialup software on the PC.
19.4.3 Configuring the GPON FTTB Internet Service (ADSL2+
Access)
to an MDU in ADSL2+ access mode and the MDU is connected to an OLT through a GPON
port.
19-97
Prerequisite
Context
Example Network
The MA5616 supports ADSL2+ access. The configuration procedure in this topic is applicable
to the MA5616 V800R308.
l The PC is connected to an ADSL2+ port on the MDU. The data frames from the PC are
transmitted to separate service channels according to user-side VLANs. Then, the OLT
switches VLAN tags (that is, switches user-side VLANs to upstream VLANs) and transmits
the data frames through an upstream port.
l The PC gains access to the Internet in PPPoE access mode. If the access mode is set to
IPoA or PPPoA, you need to configure protocol conversion and encapsulation modes.
Issue 03 (2010-11-19)
Figure 19-2 Configuring the GPON FTTB Internet service (ADSL2+ access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000
Modem

Procedure
Configuring a VLAN.
the shortcut menu.
19-99
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
19-101
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
Issue 03 (2010-11-19)
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
19-103
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
19-105
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Issue 03 (2010-11-19)
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
19-107
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
a VLAN.
Issue 03 (2010-11-19)
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
19-109
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name:HSI
Vlan ID: 1001
19-111
User VLAN: untagged
(4) Click OK.
3. Configure an ADSL line profile. For details, see 19.3.4 Configuring an ADSL
Line Profile.
the main menu.
(2) Click the ADSL Line Profile tab, and select the required device type from the
Name: adsl_profile
Other parameters: default settings
(5) Click OK.
the shortcut menu.
(7) In the dialog box that is displayed, select the required NE and click OK.
4. Configure the attributes of an ADSL port and activate the ADSL port. For
details, see 19.3.6 Configuring the Attributes of an ADSL Port and 19.3.7
Activating an ADSL Port.
(2) On the ADSL tab page, enter the filter criteria or click to display the required
ADSL ports.
(3) In the information list, right-click port 0/1/1 and choose Configure Attributes
Issue 03 (2010-11-19)
Line Profile: adsl_profile
(5) Click OK.
(6) In the information list, right-click port 0/1/1 and choose Activate from the
shortcut menu.
----End
Result
19.4.4 Configuring the GPON FTTB Internet Service (VDSL2
Access)
to an MDU in VDSL2 access mode and the MDU is connected to an OLT through a GPON port.
Prerequisite
Context
Example Network
The MA5616 and MA5652 support VDSL2 access. The configuration procedure in this topic is
applicable to the MA5616 V800R308 and MA5652 V800R308.
l The PC is connected to a VDSL2 port on the MDU. The data frames from the PC are
19-113
Figure 19-3 Configuring the GPON FTTB Internet service (VDSL2 access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000
Modem

Procedure
Configuring a VLAN.
the shortcut menu.
Issue 03 (2010-11-19)
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
19-115
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
Issue 03 (2010-11-19)
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
19-117
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
19-119
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
19-121
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
a VLAN.
19-123
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
Issue 03 (2010-11-19)
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
19-125
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name:HSI
Vlan ID: 1001
Issue 03 (2010-11-19)
User VLAN: untagged
(4) Click OK.
3. Configure a VDSL2 line profile.
The VDSL2 line profile needs to be bound to a line configuration profile and channel
configuration profile, and the line configuration profile needs to be bound to a line
the main menu.
(3) Click the Line Spectrum Configuration Profile tab, and select the required
device type from the Device Type drop-down list.
Name: vdsl_profile1
(6) Click OK.
(7) Click the Line Configuration Profile tab, and select the required device type
from the Device Type drop-down list.
Name: vdsl_profile2
Transmission Mode: G.992.5 POTS overlapped, G.992.5 Annex I All-Digital
overlapped
Line Spectrum Configuration Profile: vdsl_profile1
19-127
(10) Click Finish.
the shortcut menu.
(12) In the dialog box that is displayed, select the required MDU and click OK.
(13) Click the Channel Configuration Profile tab, and select the required device
type from the Device Type drop-down list.
Name: vdsl_profile3
(16) Click OK.
the shortcut menu.
(19) Click the Line Template tab, and select the required device type from the Device
Name: vdsl_profile
Line Configuration Profile: vdsl_profile2
Channel1 Configuration Profile: vdsl_profile3
(22) Click OK.
the shortcut menu.
4. Configure the attributes of a VDSL2 port and activate the VDSL2 port.
(2) On the VDSL2 tab page, enter the filter criteria or click to display the required
VDSL2 ports.
Line Profile: vdsl_profile
(5) Click OK.
shortcut menu.
----End
Issue 03 (2010-11-19)
Result
19.4.5 Configuring the GPON FTTB Multicast Service
Prerequisite
l The OLT must be added to the U2000.
l The licenses of multicast programs or users must have been applied for and installed.
Context
Example Network
l The set-top box (STB) is connected to port 0/0/1 on the MDU, and data frames are
transmitted through an upstream port of the MDU to the OLT. The OLT transmits the data
frames to separate service channels according to user-side VLANs, switches VLAN tags
(that is, switches user-side VLANs to upstream VLANs), and then transmits the data frames
through an upstream port.
l The OLT uses IGMP proxy, and the MDU uses IGMP snooping. IGMP proxy and IGMP
snooping are Layer 2 multicast protocols.
l Multicast programs are configured statically.
l Multicast logs are reported to the log server as CDR files.
19-129
Figure 19-4 Configuring the GPON FTTB multicast service
OLT
MDU
Multicast Source
LAN Switch
Optical splitter
U2000
STB
TV
BRAS

Procedure
Configuring a VLAN.
Issue 03 (2010-11-19)
the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
19-131
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
Issue 03 (2010-11-19)
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
19-133
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
19-135
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
19-137
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the multicast service on the OLT side.
1. Add a VLAN. For details, see 19.2.1 Configuring a VLAN.
19-139
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
A service VLAN is the VLAN used for the multicast service.
VLAN ID: 1000
Type: Smart VLAN
Issue 03 (2010-11-19)
(5) Click Done.
Service Port.
Name:IGMP
Vlan ID: 1000
User VLAN: 1000
of service streams)
(4) Click OK.
4. Add a multicast VLAN on the OLT side. For details, see 19.2.7 Configuring the
Multicast VLAN.
(2) On the Multicast VLAN tab page, set the filter criteria to display the required
multicast VLANs.
IGMP Version: IGMP V3
19-141
Work Mode: igmp_proxy
VLAN ID: 3000
(5) Click Finish.
5. Add a virtual upstream port for the multicast service on the OLT side. For details,
see 19.2.5 Configuring the Virtual Multicast Upstream Port.
Issue 03 (2010-11-19)
(2) On the Virtual Uplink Port tab page, set the filter criteria to display the required
virtual upstream ports.
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
(5) Click Done.
6. Configure a program profile on the OLT side. For details, see 19.2.8 Configuring
a Program Profile.
the main menu.
Name: program1
Start IP Address: 224.0.1.1 (IP address of the multicast program)
End IP Address: 224.0.1.1
Source IP Address: 10.10.10.20 (IP address of the multicast server)
Preview Profile: 0 (the default value)
19-143
(5) Click OK.
the shortcut menu.
(7) In the dialog box that is displayed, select the required OLT and click Next. Then,
set VLAN ID to 3000.
(8) Click OK.
7. Configure a multicast user on the OLT side. For details, see 19.2.10 Configuring
a Multicast User.
To enable user authentication, select Enable Authorization. To add a rights profile
and apply it to NEs, choose Configuration > Access Profile Management > IGMP
Profile from the main menu and click the Right Profile tab.
Alias: IGMPUserA
Unlimited Band Width: selected
Select Service Port: service virtual port named IGMP
Issue 03 (2010-11-19)
(4) Click Finish.
(5) Select the multicast user, click the User Multicast VLAN tab in the lower pane,
right-click, and then choose Add from the shortcut menu.
(6) In the dialog box that is displayed, select the record where Multicast VLAN
ID is set to 3000 and click OK.
l Configure the multicast service on the MDU side.
a VLAN.
19-145
VLAN ID: 1000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
NOTE
If the access port of MDU is xDSL port, ensure that the xDSL port is activated.
Issue 03 (2010-11-19)
Name: IGMP
Vlan ID: 1000
User VLAN: untagged
(4) Click OK.
3. Add a multicast VLAN on the MDU side. For details, see 19.2.7 Configuring the
Multicast VLAN.
Work Mode: igmp_snooping
VLAN ID: 1000
19-147
(4) Click Done.
4. Add a virtual upstream port for the multicast service on the MDU side. For
details, see 19.2.5 Configuring the Virtual Multicast Upstream Port.
multicast VLANs.
VLAN ID: 1000
Frame: 0
Slot: 0
Port: 1
Issue 03 (2010-11-19)
(5) Click OK.
5. Configure a program profile on the MDU side. For details, see 19.2.8 Configuring
a Program Profile.
the main menu.
(3) Right-click the program profile whose IP Address is set to 224.0.1.1 and choose
Download to NE from the shortcut menu.
(4) In the dialog box that is displayed, select the required MDU and click Next. Then,
(5) Click OK.
6. Configure a multicast user on the MDU side. For details, see 19.2.10 Configuring
a Multicast User.
Alias: IGMPUserA
(4) Click Finish.
19-149
----End
Result
The user can watch program1 on TV.
19.4.6 Configuring the GPON FTTB Voice Service (H.248 Protocol)
Prerequisite
The data of the MGC interface and PSTN user corresponding to the MG interface must be
configured on the MGC.
Context
H.248 is the Media Gateway Control Protocol. In the MG separation architecture, H.248 is the
communication protocol between an MGC and an MG, and it is used for the MGC to control
the MG.
The MDU functions as an MG and the SoftX3000 functions as an MGC if the softswitch that
matches the MDU is SoftX3000.
Example Network
MA5620, MA5626, MA5616, and MA5612 support H.248 Protocol. The configuration
procedure in this topic is applicable to the MA5620 V800R308, MA5626 V800R308, MA5612
V800R308, and MA5616 V800R308.
The MDU is connected to a GPON port on the OLT, and phone 1 and phone 2 are connected to
voice service ports on the MDU.
Issue 03 (2010-11-19)
Figure 19-5 Configuring the GPON FTTB voice service (H.248 protocol)
SoftX 3000
OLT
MDU
Phone2
Phone1
LAN Switch
U2000

Procedure
Configuring a VLAN.
the shortcut menu.
VLAN ID: 8
19-151
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
19-153
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
Issue 03 (2010-11-19)
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
19-155
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
19-157
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Issue 03 (2010-11-19)
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
19-159
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the voice service on the OLT side.
a VLAN.
Issue 03 (2010-11-19)
A service VLAN is the VLAN used for the voice service.
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
19-161
Vlan ID: 2000
User VLAN: 2000
(4) Click OK.
l Configure the voice service on the MDU side.
1. Add an MGC profile. For details, see 19.3.9 Adding an MGC Profile.
(1) Choose Configuration > Access Profile Management > MGC Profile from
the main menu.
Name: mgcprofile1
Protocol Type: H.248
IP Address 1: 200.200.200.200 (IP address of the MGC)
Port Number: 2944
Issue 03 (2010-11-19)
(4) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
port of the VLAN.
19-163
IP Address: 17.10.10.10
(5) Click Done.
3. Add an IP interface on the MDU side. For details, see 19.3.2 Configuring an IP
Interface.
The procedure for adding a signaling IP interface is similar to the procedure for adding
a media IP interface. The IP interface of the VLAN can be configured only when the
L3 interface of the VLAN is configured with an IP address. According to the
networking plan, the media IP address and the signaling IP address can be different.
(1) In the information list, select the record where VLAN ID is set to 2000 and click
the IP Interface tab in the lower pane.
(2) On the IP Interface tab page, right-click and choose Add from the shortcut menu.
IP Address: 17.10.10.10
IP Type: Media
Gateway: 17.10.10.1
Issue 03 (2010-11-19)
(4) Click OK.
4. Configure a static route. For details, see 19.3.8 Configuring a Static Route.
If the IP address of the VLAN IP interface is not in the same network segment as the
IP address of the MGC, you need to configure a static route.
(1) Choose Static Route from the navigation tree.
Target IP Address: 200.200.200.200 (IP address of the MGC or IMS)
Target Mask: 255.255.255.0
Next Hop IP Address: 17.10.10.1
(4) Click OK.
5. Configure the MG. For details, see 19.3.12 Adding an MG, 19.3.13 Binding an
MGC Profile, and 19.3.14 Starting an MG.
MGs.
MG ID: 0
Name: mg1
Signaling IP Address: 17.10.10.10
Signaling Port No.: 2944
Media IP Address 1: 17.10.10.10
19-165
(5) Click OK.
(6) In the information list, select the record where MG ID is set to 0, and click the
MGC Attribute Info tab in the lower pane. In the list, right-click the record
where MGC Index is set to 0 and choose Bind Profile from the shortcut menu.
(7) In the dialog box that is displayed, set NMS MGC Profile to mgcprofile1 and
click OK.
(8) In the information list, right-click the record where MG ID is set to 0 and choose
Cold Start from the shortcut menu.
(9) In the dialog box that is displayed, click Yes.
6. Configure the attributes of a VoIP PSTN port. For details, see 19.3.15
Configuring a VoIP PSTN Port.
(1) Choose ASL > POTS Port from the navigation tree.
(2) Click the VoIP PSTN Port tab, and set the filter criteria to display the required
VoIP PSTN ports.
(3) In the information list, select ports 0/1/0 and 0/1/1 by holding down the Shift
key, right-click, and then choose Configure Attributes from the shortcut menu.
Issue 03 (2010-11-19)
Parameter Value Step
MG ID 0 -
Terminal ID 0 1
Telephone No. 83110000 1

(5) Click OK.
----End
Result
Phone 1 and phone 2 can communicate with each other after the configuration is complete.
l The caller hears the dialing tone after taking the phone off the hook.
l When the caller dials the telephone number of the callee, the phone of the callee rings
successfully and the caller hears the ringback tone.
l The caller and the callee communicate with each other successfully.
l After the callee hangs up, the caller hears the busy tone.
19.4.7 Configuring the GPON FTTB Voice Service (SIP Protocol)
Prerequisite
l The PSTN user data corresponding to the SIP interface must be configured on the IMS.
Context
The IMS is an IP-based subsystem for controlling multimedia sessions on the next generation
network (NGN). The IMS includes all the core network elements that control multimedia
services such as audio, video, text, and instant message services.
The Session Initiation Protocol (SIP) is a control-layer protocol of the IMS and it is one of the
framework protocols designed by the Internet Engineering Task Force (IETF) for the multimedia
19-167
communication system. The SIP protocol is also an application-layer protocol for creating,
modifying, and terminating multimedia sessions. It is used with other protocols to complete
session establishment and media negotiation. These protocols include the Real-time Transport
Protocol (RTP), RTP Control Protocol (RTCP), Session Description Protocol (SDP), Real Time
Streaming Protocol (RTSP), and Domain Name System (DNS).
Example Network
MA5620, MA5626, MA5616, and MA5612 support SIP Protocol. The configuration procedure
and MA5616 V800R308.
The MDU is connected to a GPON port on the OLT, and phone 1 and phone 2 are connected to
voice service ports on the MDU.
Figure 19-6 Configuring the GPON FTTB voice service (SIP protocol)
OLT
MDU
Phone2
Phone1
LAN Switch
U2000

Issue 03 (2010-11-19)
Procedure
Configuring a VLAN.
the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
19-169
IP Address: 192.168.50.4
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Issue 03 (2010-11-19)
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
19-171
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
Issue 03 (2010-11-19)
GEM Port Index: 1
Priority Queue: 1
the parameter.
VLAN ID: 8
19-173
the parameter.
VLAN ID: 1001
the parameter.
VLAN ID: 1000
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 2000
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
19-175
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
displayed)
Manager VLAN: 8
Issue 03 (2010-11-19)
(6) Click OK.
and MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
19-177
(7) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Vlan ID: 2000
User VLAN: 2000
19-179
(4) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
port of the VLAN.
IP Address: 17.10.10.10
(5) Click Done.
Interface.
19-181
IP Address: 17.10.10.10
IP Type: Media
Gateway: 17.10.10.1
(4) Click OK.
Target Mask: 255.255.255.0
(4) Click OK.
4. Add a UAS profile. For details, see 19.3.10 Configuring a UAS Profile.
(1) Choose Configuration > Access Profile > UAS Profile from the main menu.
Name: uasprofile1
Address Mode: Fix mode
IP Address 1: 200.200.200.200 (IP address of the IMS)
Proxy Port: 5060
Issue 03 (2010-11-19)
(4) Click OK.
5. Add a SIP interface. For details, see 19.3.12 Adding an MG.
MGs.
MG ID: 0
Name: mg1
MG Domain Name: huawei.com
Active NMS UAS Profile: uasprofile1
19-183
(5) Click OK.
VoIP PSTN ports.
MG ID 0 -

(5) Click OK.
----End
Result
Issue 03 (2010-11-19)
19.4.8 Configuring the GPON FTTB Service by Using a Service
Provisioning Profile
LAN access mode and the MDU is connected to an OLT through a GPON port.
Prerequisite
Context
Example Network
A service provisioning profile provides common parameters that need to be set for services. To
provision a service quickly, set a service provisioning profile, bind it to a service port, and
customize service parameters.
19-185
Figure 19-7 Configuring the GPON FTTB service by using a service provisioning profile
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
Configuring a VLAN.
the shortcut menu.
Issue 03 (2010-11-19)
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
19-187
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
Issue 03 (2010-11-19)
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
19-189
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
19-191
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
19-193
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
a VLAN.
19-195
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
Issue 03 (2010-11-19)
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
19-197
VLAN ID: 1000
Type: Smart VLAN
(5) Click Done.
Service Port.
Name:IGMP
Issue 03 (2010-11-19)
Vlan ID: 1000
User VLAN: 1000
of service streams)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
19-199
(5) Click Finish.
Issue 03 (2010-11-19)
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
19-201
(5) Click OK.
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
Issue 03 (2010-11-19)
(4) Click Finish.
a VLAN.
19-203
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Issue 03 (2010-11-19)
Vlan ID: 2000
User VLAN: 2000
(4) Click OK.
l Configure the service on the MDU side.
1. Add a service provisioning profile.
(1) Choose Configuration > Access Profile Management > Service Provisioning
(2) Click the xPON FTTB Service Provisioning Profile tab.
Set Name to serviceprofile.
Right-click ServicePort in the navigation tree and choose Add serviceport
from the shortcut menu. In the right pane, set the parameters of the service
virtual port.
In the case of the Internet service:
ServicePort Name: pppoe
Service Priority: 1
19-205
VLAN Attribute: Common
Network Side VLAN: 1001
VPI: auto
Service Type: Multi-service VLAN
User VLAN: untagged
Keep traffic the same: selected
Downstream Traffic Name: FTTx
In the case of the multicast service:
ServicePort Name: multicast
Service Priority: 4
VPI: auto
User VLAN: untagged
Right-click Multicast User in the navigation tree and choose Add multicast
user from the shortcut menu. In the right pane, set the parameters of the
multicast user.
IGMP Flow Channel: multicast
Multicast VLAN: 1000
(5) Click OK.
2. Add a service.
The steps for configuring an xDSL port are similar to the steps for configuring an
Ethernet port.
Ethernet ports.
(3) In the information list, right-click port 0/1/1 and choose Add Service from the
shortcut menu.
(4) In the dialog box that is displayed, click next to Service Provisioning
Profile. In the dialog box that is displayed, select the service provisioning profile
whose Name is set to serviceprofile.
(5) Click OK.
----End
Issue 03 (2010-11-19)
Result
19-207
20 Configuring the GPON FTTH Services
About This Chapter
An FTTH network consisting of an OLT in profile mode and a number of ONTs provides users
with Internet services, multicast services, and voice services.
Context
The ONT configuration is simplified when the OLT is in profile mode.
To query the xPON mode of the current system, run the diagnose command to enter the diagnosis
mode and then run the display xpon mode command.
CAUTION
l In the diagnosis mode, the user with the rights higher than operator can perform this operation.
l Switching the xPON mode of the system enables the system to automatically save data and
restart.
huawei(diagnose)%%display xpon mode
---------------------------------------------------
Current config mode: Profile-mode
---------------------------------------------------
You can run the xpon mode switch-to command in the diagnosis mode to switch the xPON
mode of the current system, for example, from discrete mode to profile mode.
huawei(diagnose)%%xpon mode switch-to profile-mode
Warning: The operation will automatically save and reboot system. Are you sure
to proceed? (y/n)[n]:
20.1 Adding an ONT to the U2000 (OLT in Profile Mode)
This topic describes how to add an ONT to the U2000 when the OLT is in the profile mode.
After an ONT is added successfully, you can configure FTTH services for the ONT on the U2000.
20.2 Configuring Services
Operation Guide for ONU NE Management 20 Configuring the GPON FTTH Services
20-1
An FTTH network consisting of an OLT and a number of MDUs provides users with Internet,
multicast, and voice services.
20.3 Configuration Examples of the GPON FTTH Services
services in a GPON FTTH network.
Issue 03 (2010-11-19)
After an ONT is added successfully, you can configure FTTH services for the ONT on the U2000.
Context
After an ONT is added on the NE side, it supports online confirmation and offline deployment.
The information about the profile bound to an ONT and the authentication information must be
the same as those configured for the actual ONT on the user side.
l Online confirmation: If you add an ONT after the ONT is powered on, it goes online
immediately.
l Offline deployment: If an ONT is not online, you need to add it offline and configure
services for the ONT. After the ONT goes online, the configuration is applied to the ONT
through the optical network termination management and control interface (OMCI). Then,
service configuration for the ONT is complete.
or SNMP.
20.1.2 Configuring a GPON Service Profile
The GPON service profile consolidates the parameters related to the ONU service into a profile.
20.1.3 Confirming an ONT
This topic describes how to confirm the auto-find ONU connected to a port. An auto-find ONU
is in the auto-find state before it is confirmed. The auto-find ONU can start to work only after
it is confirmed.
or SNMP.
Prerequisite
a DBA Profile.
Context
l The flow mapping mode configured in the GPON line profile must match the flow mapping
mode of the flow (such as the GEM connection flow) specified in the GPON line profile.
l The flow control mode configured in the GPON line profile must match the flow control
mode of the GEM port specified in the GPON line profile.
l When adding a GPON line profile, you can use or reference the four default line profiles,
lineprofile_1 to lineprofile_4, provided by the NE.
20-3
Procedure
2 Click the GPON Line Profile tab. Right-click and choose Add Global Profile from the shortcut
menu.
Key
Paramete
r
Description
Upstream
FEC
Switch
Specifies whether to enable the upstream forward error correction (FEC)
function of the ONT line profile. To improve the reliability of data
transmission between the OLT and the ONT, enable the FEC function.
After the upstream FEC function is enabled, the system inserts the
redundancy data into normal packets. In this manner, the line has the error
tolerance capability, but certain bandwidth is wasted.
Mapping
Mode
Flow mapping manages the service streams on the ONU, namely, manages
the mapping between GEM ports and the upstream data flows on the ONT
service ports. After the mapping is established, the ONU service streams
are carried and transmitted upstream through the specified GEM ports.
Each ONT can be configured with only one mapping mode.
Issue 03 (2010-11-19)
Key
Paramete
r
Description
Qos Mode l When the Qos Mode of the GEM port is set to Priority Queue, users
can specify the transmit queue of the GEM port packets in a T-CONT.
When transmitting the upstream data, the T-CONT transmits the data
strictly according to the priority of the queue.
l When the Qos Mode of the GEM port is set to GEM Port CAR, the
ONU limits the rate of the data packets carried on the GEM port
according to the CAR setting of the GEM port. Currently, the GEM
port CAR is set by binding the CAR profile to the ONU, and only the
average rate and maximum rate can be set. When several service
streams exist on the GEM port, the service streams are schedule in PQ,
WRR, or PQ+WRR mode, depending on the default scheduling mode
of the ONU. Currently, the scheduling mode cannot be set on the OLT.
When a T-CONT consists of multiple GEM ports, the scheduling mode
of the data packets between the GEM ports also depends on the default
scheduling mode of the ONU.
l When the flow control mode of the GEM port is set to Flow CAR, the
ONU performs CAR on the service streams of the GEM port. The
controlling is more specific than the GEM port CAR. After being
performed with CAR, the service streams are scheduled in the T-CONT
queue. The scheduling mode is the default scheduling mode of the
ONU.

2. Choose T-CONT Info. from the navigation tree, right-click, and then choose ADD T-
CONT from the shortcut menu. In the dialog box that is displayed, set T-CONT Index
and DBA Profile.
20-5
CAUTION
It is recommended that you do not set T-CONT Index to 0. TCONT 0 is reserved for the
internal communication of the GPON protocol.
3. Choose T-CONTx from the navigation tree, right-click, and then choose ADD GEM
Port from the shortcut menu. In the dialog box that is displayed, set GEM Port Index.
NOTE
4. Choose GEM Portx from the navigation tree, right-click, and then choose ADD GEM
Connection from the shortcut menu. In the dialog box that is displayed, set the basic
parameters of the GEM connection.
NOTE
Issue 03 (2010-11-19)
4 Click OK.
menu.
----End
Command Reference
Enter the ONT line profile mode ont-lineprofile gpon Global config mode
Bind a DBA profile to a T-CONT tcont ONT line profile mode
Bind a GEM index to a T-CONT
and configure the related attributes
in an ONT line profile
gem add ONT line profile mode
Set up the mapping relationship
between the upstream data flow on
the ONT service ports and the
GEM ports
gem mapping ONT line profile mode
Configure the QoS mode in the
ONT line profile
qos-mode ONT line profile mode

20.1.2 Configuring a GPON Service Profile
The GPON service profile consolidates the parameters related to the ONU service into a profile.
20-7
Procedure
2 Click the GPON Service Profile tab. Right-click and choose Add Global Profile from the
shortcut menu.
Issue 03 (2010-11-19)
2. Choose UNI Port from the navigation tree. In the right pane, select the record from the
ETH port list, right-click, and then choose UNI Port Configuration Properties and set
the relevant parameters in the dialog box that is displayed.
menu.
6 Click OK.
----End
Command Reference
Query the
information about
the ONT service
profile
display ont-srvprofile Privilege mode
Enter the ONT line
profile mode
ont-srvprofile Global config mode

20-9
20.1.3 Confirming an ONT
This topic describes how to confirm the auto-find ONU connected to a port. An auto-find ONU
is in the auto-find state before it is confirmed. The auto-find ONU can start to work only after
it is confirmed.
Procedure
2 Choose GPON > GPON UNI Port from the navigation tree.
3 On the GPON UNI Port tab page, set the filter criteria to display the required GPON UNI ports.
4 Select a GPON UNI port for which you want to enable the function of automatically discovered
ONU, right-click and choose Enable ONU Auto Find from the shortcut menu.
5 Select the GPON UNI port from the list with ONUs to be confirmed, and click the Auto-
Discovered ONU Info tab in the lower part of the page.
6 Select an ONU that needs to be confirmed, right-click, and then choose Confirm ONU.
7 In the dialog box that is displayed, configure the basic parameters for confirming the ONU, and
click OK.
NOTE
Issue 03 (2010-11-19)
Key
Parameter
Description
ONU ID Indicates the ID that identifies an ONU. Usually, it starts from 0.
ONU Type Specifies ONTs.
Line Profile Indicates the line profile bound to the port to which the ONU belongs. You can
bind a port with the line profile. When the port is activated, it can reference
the profile. According to the upstream and downstream line rates and the noise
tolerance set in the profile, the port detects the line distance and line status,
negotiates between the local and remote devices, and determines whether it
can work under the conditions.
Service
Profile
Indicates the service profile bound to the ONU. A service profile contains the
parameters relevant to the ONU service.
Authenticat
ion Mode
Indicates the mode used when the OLT authenticates an ONU. By default, the
GPON ONU uses the SN-based authentication mode.

When you add an ONU in the SNMP management mode, the management mode and line profile
are mandatory. When you add an ONU in the OAM management mode, the parameters of
management mode, line profile, and service profile are mandatory.
----End
Command Reference
Confirm an ONT in the auto-
discovery state
ont confirm GPON mode
Switch to the GPON mode from
the global config mode
interface gpon Global config mode
Enable the function of
automatically discovered ONU
connected to a GPON port
port ont-auto-find enable GPON mode
Query the current ONTs
automatically discovered or time
set for automatically discovering
ONTs from the system
display ont autofind Privilege mode, GPON
mode

20-11
Context
Services Steps
Port
l 20.2.1 Configuring the ONT Value-Added Service
Configuration Profile
l 20.2.2 Configuring the Voice Value-Added Service
of an ONT

20.2.1 Configuring the ONT Value-Added Service Configuration Profile
After configuring an ONT value-added service configuration profile and binding it to an ONT
successfully, you can activate the ONT and directly deliver the value-added service defined by
the profile to the subscribers of the ONT. Each ONT can be bound to only one value-added
service configuration profile.
20.2.2 Configuring the Voice Value-Added Service of an ONT
The ONT value-added service (VAS) is used to support the function of provisioning the VoIP
service on the ONT, and to set the parameters for the VASs on the ONT, such as the VoIP service.
After an ONT is upgraded, the XML parameters of the ONT must be set again. Therefore,
upgrade the ONT before configuring the VAS for the ONT.
20.2.3 Adding a GPON FTTH Service Provisioning Profile
20.2.4 Configuring the GPON FTTH Service
You can directly configure and provision the GPON FTTH service by binding the configured
GPON FTTH service provisioning profile with a certain physical port on the ONT.
Issue 03 (2010-11-19)
20.2.1 Configuring the ONT Value-Added Service Configuration
Profile
After configuring an ONT value-added service configuration profile and binding it to an ONT
successfully, you can activate the ONT and directly deliver the value-added service defined by
the profile to the subscribers of the ONT. Each ONT can be bound to only one value-added
service configuration profile.
Context
The value-added service configuration profiles vary with the types of the ONTs and the software
versions. This section considers the Echolife:HG850a profile as an example.
Procedure
1 Choose Configuration > Access Profile Management > ONT VAS Profile from the main
menu.
4 Click OK.
----End
20-13
Command Reference
- - -

20.2.2 Configuring the Voice Value-Added Service of an ONT
The ONT value-added service (VAS) is used to support the function of provisioning the VoIP
service on the ONT, and to set the parameters for the VASs on the ONT, such as the VoIP service.
After an ONT is upgraded, the XML parameters of the ONT must be set again. Therefore,
upgrade the ONT before configuring the VAS for the ONT.
Prerequisite
l The FTP service must be enabled.
l An ONT value-added service template must be configured in the system.
l The ONT must be upgraded.
Procedure
4 In the case of the parameters that cannot be obtained from the ONT VAS to function as the
parameters of the ONT VAS profile, you can customize the configuration for a single ONT VAS.
l Configuring the VAS for a single ONT:
1. Select a record from the ONT list, right-click, and then choose Configure Value-Added
Service from the shortcut menu.
2. In the dialog box that is displayed, set the parameter associated with the VoIP service.
Issue 03 (2010-11-19)
l Configuring the VAS for multiple ONTs:
1. Select multiple ONTs by pressing Ctrl or Shift, right-click, and then choose Bind VAS
Profile from the shortcut menu.
2. In the dialog box that is displayed, select the required ONT value-added service profile,
and then click OK.
5 Click OK.
----End
20-15
20.2.3 Adding a GPON FTTH Service Provisioning Profile
Prerequisite
l Perform the operations in 20.1.1 Configuring a GPON Line Profile and 20.1.2
Configuring a GPON Service Profile before configuring the Basic Info branch.
l Perform the operations in 19.2.1 Configuring a VLAN and 19.2.2 Configuring an MEF
IP Traffic Profile before configuring the Service Port branch.
l Perform the operations in 19.2.7 Configuring the Multicast VLAN before configuring
the Multicast User branch.
Procedure
1 Choose Configuration > Access Profile Management > Service Provisioning Profile from
the main menu.
2 Click the GPON FTTH Service Provisioning Profile tab.
Issue 03 (2010-11-19)
20-17
Issue 03 (2010-11-19)
Key
Parameter
Description
Basic Info
Name Indicates the name of the GPON FTTH service provisioning profile.
ONU Port Info
Port Type Indicates the ONU port type.
NOTE
You can set the port type according to different ONUs.
Port Mode Indicates the ONU port type. Enumerated type. The options are ATM and
PTM.
NOTE
This parameter is available when Port Type is set to VDSL2 or G.SHDSL.
ONU side
Service Type Indicates the type of services carried on the service virtual port.
The port can work in the following modes:
l Single: Each service port maps a service stream. Different service
streams can be distinguished by service ports.
l Multi-Service VLAN: Each service port carries multiple service streams.
You need to set User-Side VLAN to distinguish the service streams. The
services are distinguished based on the VLAN ID contained in the
packets subscriber ports. You can label the packets with different
upstream VLAN IDs.
l Multi-Service Encapsulation: Each service port carries multiple service
streams. You need to set User-Side Encapsulation to distinguish the
service streams. The services are distinguished based on the
encapsulation types (IPoE/PPPoE) of the packets from the subscriber
port. You can label the packets with different upstream VLAN IDs.
l Multi-Service VLAN+802.1p: Each service port carries multiple service
streams. You need to set User-Side VLAN and 802.1p Priority to
distinguish the service streams. The services are distinguished according
to the VLAN IDs and the 802.1p priorities of the packets from the
subscriber port.
NOTE
This parameter is available only when the Service Priority is set.
l Multi-Service VLAN+Encapsulation: Each service port carries multiple
service streams. You need to set User-Side VLAN and User-Side
Encapsulation to distinguish the service streams.
OLT Side
Multicast User
IGMP Flow
Channel
Specifies the protocol traffic channel of the multicast service.
Enumerated type. Select a protocol traffic channel by setting the Service
Port parameter.
20-19
Key
Parameter
Description
Multicast
VLAN
Specifies the multicast VLAN ID.

4 Click OK.
----End
20.2.4 Configuring the GPON FTTH Service
You can directly configure and provision the GPON FTTH service by binding the configured
GPON FTTH service provisioning profile with a certain physical port on the ONT.
Prerequisite
l The OLT that the ONU is connected to must be in the profile mode.
l The configured GPON FTTH service provisioning profile must be applied to the ONT. For
details, see 20.2.3 Adding a GPON FTTH Service Provisioning Profile.
Procedure
4 Select a record from the Ethernet port list, right-click, and then choose Add Service from the
shortcut menu.
Issue 03 (2010-11-19)
In the Add Service dialog box, click next to Service Provisioning Profile. In the Add
Service dialog box, click Find to display the required service provisioning profiles that meet
the filtering criteria. Select a record from the profile list, and click OK.
5 Click OK.
----End
20.3 Configuration Examples of the GPON FTTH Services
services in a GPON FTTH network.
20.3.1 Data Plan for the GPON FTTH Services
This topic provides the data plan for the configuration examples of the GPON FTTH services.
20.3.2 Configuring the GPON FTTH Internet Service
This topic describes how to configure the high-speed Internet service when an ONT is connected
to an OLT through a GPON port.
20.3.3 Configuring the GPON FTTH Multicast Service
This topic describes how to configure the multicast service when an ONT is connected to an
20.3.4 Configuring the GPON FTTH Voice Service (H.248 Protocol)
This topic describes how to configure the voice service when an ONT is connected to an OLT
20.3.5 Configuring the GPON FTTH Voice Service (SIP Protocol)
20.3.6 Configuring the GPON FTTH Service by Using a Service Provisioning Profile
This topic describes how to configure various services when an ONT is connected to an OLT
20.3.1 Data Plan for the GPON FTTH Services
This topic provides the data plan for the configuration examples of the GPON FTTH services.
Data Plan
Table 20-1 Data plan for the GPON FTTH services
Service
Type
Device
managemen
t
Upstream port of an
OLT
0/19/0 -
20-21
Service
Type
the management
VLAN of the OLT
functions as the IP
address of the OLT
for inband network
management.
GPON port of the
OLT
0/2/1 -
ONT SN: 32303131B39FD641
Name: ONT
ONU Type: ONT
ONU ID: 0
Terminal Type:
EchoLife:HG850a
Software Version:
V1R1C03B030
-
MEF IP traffic
profile
l Name: FTTx
l CIR: 20480
l Outer Priority: 1
The MEF IP traffic
MDU to control
upstream and
downstream traffic.
l T-CONT type: Maximum
Bandwidth
32768
-
l Mapping Mode:VLAN
l Qos Mode:Priority Queue
l T-CONT Index: 1
l DBA Profile: FTTx
l GEM Port Index: 1
l Priority Queue:1
-
Issue 03 (2010-11-19)
Service
Type
Service profile Name: FTTx
Vlan Type: Translation
C-VLAN: 1001,1000
S-VLAN: 1001,1000
-
Internet
service
l Type: Smart VLAN
l Attribute: QinQ
-
Service virtual port l Name: HSI
l VLAN ID: 1001
0/2/1/0/0
Service VLAN
l User VLAN: 1001
same: selected
FTTx
-
ONT VAS
configuration
profile
l Profile Name:
VOIPHG850a
l Terminal Type:
EchoLife:HG850a
l Version:
V1R1C01B010~Later
l WAN VLAN ID: 1001
l IP get mode: pppoe
l PPPoE Account Enable:
enable
l WAN Service Type:
INTERNET
-
IPTV
service
l Type: Smart VLAN
-
20-23
Service
Type
Service virtual port l Name: IGMP
l Vlan ID: 1000
0/2/1/0/0
Service VLAN
l User VLAN: 1000
same: selected
FTTx
-
Multicast VLAN l IGMP Version: IGMP V3
l VLAN ID: 3000
-
10.10.10.20
default value)
-
selected
-
VoIP
service
l Type: Smart VLAN
-
Issue 03 (2010-11-19)
Service
Type
Service virtual port l Name: VOIP
l Vlan ID: 2000
0/2/1/0/0
Service VLAN
l User VLAN: 2000
same: selected
FTTx
-
ONT VAS
configuration
profile (H.248
protocol)
l Profile Name:
VOIPHG850a
l Terminal Type:
EchoLife:HG850a
l Version:
V1R1C01B010~Later
l Digitmap: x.T
l MGC Port: 2944
l MGC domain name:
MGC.com
-
20-25
Service
Type
ONT VAS
configuration
profile (SIP
protocol)
l Profile Name:
VOIPHG850a
l Terminal Type:
EchoLife:HG850a
l Version:
V1R1C01B010~Later
l Signal Protocol: SIP
l SIP server port: 5060
l SIP server IP:
200.200.200.200
l SIP digitmap: x.T
l WAN VLAN ID: 2000
l IP get mode: dhcp
l WAN Service Type: VOIP
l User1 phone number:
87650001, User1 password:
test1234
test1234
-

20.3.2 Configuring the GPON FTTH Internet Service
to an OLT through a GPON port.
Prerequisite
Context
For details of the data plan, see 20.3.1 Data Plan for the GPON FTTH Services.
Example Network
This topic considers the ONT whose Terminal Type is set to EchoLife:HG850a as an example.
The configuration procedure of the ONTs of other types is similar to the configuration procedure
described in this topic.
l The PC gains access to the Internet in PPPoE dialup mode.
l The ONT is connected to the GPBC card of the OLT through an optical fiber.
Issue 03 (2010-11-19)
l The broadband remote access server (BRAS) provides the authentication, authorization,
and accounting (AAA) functions.
Figure 20-1 Configuring the GPON FTTH Internet service
OLT
ONT
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
l Add the ONT to the U2000 in profile mode.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
20-27
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Issue 03 (2010-11-19)
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
20-29
the parameter.
VLAN ID: 1001
the parameter.
VLAN ID: 1000
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 2000
(5) Click OK.
the shortcut menu.
4. Configure a service profile. For details, see 20.1.2 Configuring a GPON Service
Profile.
the main menu.
(2) Click the Service Profile tab.
20-31
Set Name to FTTx.
Choose UNI Port from the navigation tree. In the window that is displayed,
right-click the record where Port Type is set to ETH and Port ID is set to
1, and choose UNI Port Configuration Properties from the shortcut menu.
In the dialog box that is displayed, set the parameters.
In the dialog box that is displayed, right-click and choose Add, and
configure the parameters of VLAN switch.
Service Type: Translation
S-VLAN: 1001 (VLAN ID of the Internet service)
C-VLAN: 1001(user VLAN ID of the ONT)
Issue 03 (2010-11-19)
S-VLAN: 1000 (VLAN ID of the multicast service)
C-VLAN: 1000 (user VLAN ID of the ONT)
(5) Click OK.
the shortcut menu.
5. Confirm the ONT. For details, see 20.1.3 Confirming an ONT .
the shortcut menu.
GPON UNI ports.
with SN 32303131B39FD641, and then choose Confirm ONU from the shortcut
menu.
Name: ONT
ONU ID: 0
ONU Type: ONT
Service Profile: FTTx (click next to Service Profile and select the
service profile named FTTx in the dialog box that is displayed)
Terminal Type: EchoLife:HG850a
Software Version: V1R1C03B030
20-33
(6) Click OK.
l Configure the Internet service.
1. Configuring the Information About the ETH Port of a GPON ONU
(1) Choose GPON > GPON ONU from the navigation tree.
(2) On the GPON ONU tab page, set the filter criteria to display the required GPON
ONUs.
(3) In the information list, right-click the ONT record where Frame, Slot, Port, and
ONU ID are set to 0, 2, 1, and 0 respectively and click the The Ont's UNI Port
Info tab in the lower pane.
(4) On the The Ont's UNI Port Info tab page, right-click the record where UNI
Type is set to ETH and UNI ID is set to 1, and choose Modifyfrom the shortcut
menu.
(5) In the dialog box that is displayed, set Default VLAN ID to 1001.
(6) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Issue 03 (2010-11-19)
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
VLAN ID: 1001
20-35
User VLAN: 1001
(4) Click OK.
4. Configure the VAS configuration profile of the ONT.
(1) Choose Configuration > Access Profile Management > ONT VAS Profile
from the main menu.
Set Profile Name to VOIPHG850a.
Set Vendor ID to HWTC(2011).
Set Terminal Type to EchoLife:HG850a.
Set Version to V1R1C01B010~Later.
Choose Layer3 > WAN Interface from the navigation tree, right-click the
list, and then choose Add. Choose WAN property configuration 1
protocol from the navigation tree and set the parameters.
WAN VLAN ID: 1001
IP get mode: pppoe
PPPoE Account Enable: enable
WAN Service Type: INTERNET
(4) Click OK.
5. Bind the VAS profile.
ONUs.
Issue 03 (2010-11-19)
ONU ID are set to 0, 2, 1, and 0 respectively and choose Bind VAS Profile from
the shortcut menu.
(4) In the dialog box that is displayed, select the VAS profile whose Profile Name
is set to VOIPHG850a and click OK.
6. Configure Value-Added Service.
ONUs.
ONU ID are set to 0, 2, 1, and 0 respectively and choose Configure Value-
Added Service from the shortcut menu.
Choose WAN Interface from the navigation tree and choose Add from the
shortcut menu.
Choose WAN property configuration 1 from the navigation tree and set
PPPoE username to 1@pppoe and PPPoE password to test1234.
(5) Click OK.
----End
Result
Check whether the user successfully gains access to the Internet through dialup on the PC.
1. The FE port of the ONT is connected to the Ethernet port of the PC properly.
2. Dial up on the PC using the PPPoE dialup software.
3. The user gains access to the Internet on the PC after the dialup is successful.
20.3.3 Configuring the GPON FTTH Multicast Service
Prerequisite
Context
Example Network
l The OLT uses IGMP proxy, which is a Layer 2 multicast protocol.
l The IGMP version of the multicast VLAN is IGMPv3.
20-37
Figure 20-2 Configuring the GPON FTTH multicast service
Multicast Source
OLT
LAN Switch
Optical splitter
U2000
STB
TV
BRAS
ONT

Procedure
IP Traffic Profile.
the main menu.
Issue 03 (2010-11-19)
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
20-39
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1001
the parameter.
VLAN ID: 1000
20-41
the parameter.
VLAN ID: 2000
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Issue 03 (2010-11-19)
Set Name to FTTx.
20-43
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Name: ONT
ONU ID: 0
ONU Type: ONT
Issue 03 (2010-11-19)
(6) Click OK.
l Configure the multicast service.
ONUs.
menu.
(6) Click OK.
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
20-45
VLAN ID: 1000
Type: Smart VLAN
(5) Click Done.
Service Port.
Name:IGMP
Issue 03 (2010-11-19)
Vlan ID: 1000
User VLAN: 1000
of service streams)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
20-47
(5) Click Finish.
Issue 03 (2010-11-19)
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
20-49
(5) Click OK.
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
Issue 03 (2010-11-19)
(4) Click Finish.
----End
Result
20.3.4 Configuring the GPON FTTH Voice Service (H.248 Protocol)
20-51
Prerequisite
Context
Example Network
l Phone 1 and phone 2 are connected to TEL ports on the ONT separately and can
communicate with each other.
l The ONT obtains an IP address in Dynamic Host Configuration Protocol (DHCP) mode.
Issue 03 (2010-11-19)
Figure 20-3 Configuring the GPON FTTH voice service (H.248 protocol)
Phone1
SoftX 3000
OLT
Phone2
LAN Switch
U2000
ONT
Optical splitter

Procedure
IP Traffic Profile.
the main menu.
Name: FTTx
20-53
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Issue 03 (2010-11-19)
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
20-55
the parameter.
VLAN ID: 1001
the parameter.
VLAN ID: 1000
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 2000
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
20-57
Set Name to FTTx.
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Name: ONT
ONU ID: 0
ONU Type: ONT
20-59
(6) Click OK.
l Configure the voice service.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Vlan ID: 2000
20-61
User VLAN: 2000
(4) Click OK.
3. Configure the value-added service (VAS) configuration profile of the ONT.
from the main menu.
Choose Country code and signaling protocol from the navigation tree and
set Signal Protocol to H248.
Choose H.248 Global digitmap configure from the navigation tree and set
Digitmap to x.T.
Choose H.248MGC > H.248 MGC configure 1 from the navigation tree and
set MGC port to 2944 and MGC domain name to MGC.com.
(4) Click OK.
ONUs.
the shortcut menu.
Issue 03 (2010-11-19)
----End
Result
20.3.5 Configuring the GPON FTTH Voice Service (SIP Protocol)
Prerequisite
Context
Example Network
l The ONT obtains an IP address in DHCP mode.
20-63
Figure 20-4 Configuring the GPON FTTH voice service (SIP protocol)
Phone1
OLT
Phone2
LAN Switch
U2000
ONT
Optical splitter

Procedure
IP Traffic Profile.
the main menu.
Name: FTTx
Issue 03 (2010-11-19)
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
20-65
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1001
the parameter.
VLAN ID: 1000
20-67
the parameter.
VLAN ID: 2000
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Issue 03 (2010-11-19)
Set Name to FTTx.
20-69
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Name: ONT
ONU ID: 0
ONU Type: ONT
Issue 03 (2010-11-19)
(6) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
20-71
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Vlan ID: 2000
Issue 03 (2010-11-19)
User VLAN: 2000
(4) Click OK.
from the main menu.
set Signal Protocol to SIP.
Choose SIP protocol configure > SIP protocol configure 1 from the
navigation tree and set SIP server port to 5060 and SIP server IP to
200.200.200.200.
Choose SIP digitmap configure from the navigation tree and set SIP
digitmap to x.T.
Choose Layer3 > WAN Interface from the navigation tree, right-click the
list, and then choose Add. Choose WAN property configuration 1
protocol from the navigation tree and set the parameters.
WAN VLAN ID: 2000
IP get mode: dhcp
WAN Service Type: VOIP
(4) Click OK.
20-73
ONUs.
the shortcut menu.
ONUs.
Choose SIP user configure from the navigation tree and choose Add from the
shortcut menu.
Choose User port number 1 from the navigation tree and set User phone
number to 87650001 and User password to test1234.
Choose User port number 2 from the navigation tree and set User phone
number to 87650002 and User password to test1234.
(5) Click OK.
----End
Result
Check whether the telephone functions properly. Connect two common telephones phone 1 and
phone 2 to two TEL ports on the ONT and test the dialing between phone 1 and phone 2. In
normal cases,
successfully, and the caller hears the ringback tone.
20.3.6 Configuring the GPON FTTH Service by Using a Service
This topic describes how to configure various services when an ONT is connected to an OLT
Prerequisite
Issue 03 (2010-11-19)
Context
Example Network
Figure 20-5 Configuring the GPON FTTH service by using a service provisioning profile
TV Ephone PC
STB
ONT
LSW
IPTV DHCP Server
U2000
OSS & RADIUS Server/RADIUS Proxy
BRAS
VoIP DHCP Server
Router
Multicast source
Optical splitter
OLT

Procedure
20-75
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
Issue 03 (2010-11-19)
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
20-77
GEM Port Index: 1
Priority Queue: 1
the parameter.
VLAN ID: 1001
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
20-79
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Issue 03 (2010-11-19)
(5) Click OK.
20-81
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Name: ONT
ONU ID: 0
ONU Type: ONT
(6) Click OK.
Issue 03 (2010-11-19)
ONUs.
menu.
(6) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
20-83
(5) Click Done.
Service Port.
Name: HSI
VLAN ID: 1001
User VLAN: 1001
Issue 03 (2010-11-19)
(4) Click OK.
ONUs.
menu.
(6) Click OK.
a VLAN.
VLAN ID: 1000
Type: Smart VLAN
20-85
(5) Click Done.
Service Port.
Name:IGMP
Vlan ID: 1000
User VLAN: 1000
Issue 03 (2010-11-19)
of service streams)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
20-87
(5) Click Finish.
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
Issue 03 (2010-11-19)
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
(5) Click OK.
20-89
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
(4) Click Finish.
Issue 03 (2010-11-19)
l Configure the VAS configuration profile of the ONT.
1. Choose Configuration > Access Profile Management > ONT VAS Profile from
the main menu.
Choose Country code and signaling protocol from the navigation tree and set
Signal Protocol to SIP.
Choose SIP protocol configure > SIP protocol configure 1 from the navigation
tree and set SIP server port to 5060 and SIP server IP to 200.200.200.200.
Choose SIP digitmap configure from the navigation tree and set SIP digitmap
to x.T.
Choose Layer3 > WAN Interface from the navigation tree, right-click the list,
and then choose Add. Choose WAN property configuration 1 protocol from the
navigation tree and set the parameters.
WAN VLAN ID: 20
IP get mode: dhcp
WAN Service Type: VOIP
4. Click OK.
l Add a service provisioning profile.
1. Choose Configuration > Access Profile Management > Service Provisioning
2. Click the GPON FTTH Service Provisioning Profile tab.
20-91
Deploy and ONU and provision its service for the first time option button:
clicked
ONU device type: EchoLife:HG850a
ONU Device Version: V1R1C03B030
Line Profile: FTTx
Service Profile: FTTx
ONU VAS Profile: VOIPHG850a
Right-click ServicePort in the navigation tree and choose Add serviceport from
the shortcut menu. In the right pane, set the parameters of the service virtual port.
GemPort: 1
User VLAN: untagged
GemPort: 1
User VLAN: untagged
user from the shortcut menu. In the right pane, set the parameters of the multicast
user.
5. Click OK.
l Configure the service.
2. On the GPON ONU tab page, set the filter criteria to display the required GPON
ONUs.
Issue 03 (2010-11-19)
3. In the information list, right-click the ONT record where Frame, Slot, Port, and ONU
ID are set to 0, 2, 1, and 0 respectively and choose Config Service from the shortcut
menu.
4. In the dialog box that is displayed, click next to Service Provisioning Profile. In
the dialog box that is displayed, select the service provisioning profile whose Name
is set to serviceprofile.
5. Click OK.
----End
Result
normal cases,
20-93
21 Configuring the GPON Private Line
Access and FTTO Services (OT928G)
About This Chapter
The deployment of an OLT and OT928G in a network provides the private line access and fiber
to the office (FTTO) solutions.
Context
In an private line access network, the OT928G functions as a cellular backhaul unit (CBU) and
is connected to 2G or 3G base stations in various modes to carry 2G or 3G services over the
FTTM network.
l The GPON native TDM solution is used to carry wireless 2G services and services in the
wireless 3G CS domain. It is mainly used to carry voice services.
l The GPON Ethernet solution is used to carry services in the 3G PS domain and mainly
used to carry data services.
In an FTTO network, the OT928G functions as a single business unit (SBU), provides multiple
types of ports, and supports various networking modes to meet network requirements of
enterprise users for different environments and services.
l Eight POTS ports are used to connect to telephones inside enterprises and provide the high-
quality and low-cost VoIP service on the IP network.
l Eight E1 ports are used to connect to TDM PBXs of enterprises.
l Four FE electrical ports and one FE/GE adaptive electrical port are used to connect to LAN
switches of enterprises and provide Ethernet private-line services.
After an ONT is added successfully, you can configure FTTM or FTTO services for the ONT
on the U2000.
An FTTO or FTTM network with an OLT and OT928G provides various services for users.
21.3 Configuration Examples of the GPON Private Line Access and FTTO Services (OLT
+OT928G)
21 Configuring the GPON Private Line Access and FTTO
Services (OT928G)
21-1
This topic provides examples to describe how to configure various services in a GPON private
line access or FTTO network.
Services (OT928G)
Issue 03 (2010-11-19)
After an ONT is added successfully, you can configure FTTM or FTTO services for the ONT
on the U2000.
Context
The OT928G supports five ETH ports, eight E1 ports, and eight POTS ports.
Procedure
1 20.1.1 Configuring a GPON Line Profile.
2 20.1.2 Configuring a GPON Service Profile.
NOTE
In the dialog box that is displayed, click the Base Info. tab. Set Number of Pots Ports to 8, Number of
ETH Ports to 5, and Number of TDM Ports to 8.
3 20.1.3 Confirming an ONT .
NOTE
In the dialog box that is displayed, click the Basic Parameters tab. Set Terminal Type to SmartAX
OT928G.
----End
An FTTO or FTTM network with an OLT and OT928G provides various services for users.
Context
Services Steps
Ethernet Private-Line Service
of an Enterprise
l 21.2.2 Configuring a VLAN Service Profile
l 21.2.3 Configuring a VLAN
l 21.2.1 Setting Queue Scheduling Parameters
TDM PBX Access Service/
Native TDM Mobile Bearer
Service (Based on the SDH
Network)
l 21.2.4 Configuring a TDM Connection
l 21.2.5 Configuring a Clock Source
Services (OT928G)
21-3
Services Steps
Ethernet Mobile Bearer Service l 19.2.1 Configuring a VLAN

21.2.1 Setting Queue Scheduling Parameters
To ensure the QoS of important services in case of network congestion, you need to select
different queue scheduling modes according to the priorities of the services. You need to set the
queue scheduling parameters on the OLT only once. Then, the parameters are globally valid.
21.2.2 Configuring a VLAN Service Profile
The parameters related to services in VLAN attributes are combined to form a profile. The profile
can be referenced by a VLAN on a device after the profile is applied to the device.
21.2.4 Configuring a TDM Connection
This topic describes how to add a TDM E1 connection and set up the mapping between E1 ports
and GEM ports.
21.2.5 Configuring a Clock Source
This topic describes how to set the clock signal of a specified port as the reference clock source
of the system.
21.2.1 Setting Queue Scheduling Parameters
To ensure the QoS of important services in case of network congestion, you need to select
different queue scheduling modes according to the priorities of the services. You need to set the
queue scheduling parameters on the OLT only once. Then, the parameters are globally valid.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the
main menu.
2 On the System Parameter Profile tab page, select the required OLT type from the Device
4 In the dialog box that is displayed, set the name of the system parameter profile to FTTx. Choose
QoS > Queue scheduler mode from the Parameters for Selection navigation tree, click
to add the parameter to the Selected Parameters navigation tree, and then click Next.
5 Choose QoS > Queue scheduler mode from the navigation tree to configure the queue
scheduling mode.
Services (OT928G)
Issue 03 (2010-11-19)
Queue scheduler mode Distributes the packets that are transmitted from the same port to
multiple queues and schedules the queues to determine the
sequence of transmitting the packets.
It is recommended that you use both the weighted round robin
(WRR) and priority queuing (PQ) scheduling modes. In this case,
the system schedules the queue with weight 0 in the PQ mode, and
then schedules the queues with the weights other than 0 in the
WRR mode.
Queue-weight Indicates the percentage of the bandwidth occupied by each queue.
The sum of the weights of the queues must be 0 or 100.

6 Click OK.
menu.
----End
Services (OT928G)
21-5
Command Reference
Configure the queue
scheduling mode of
Ethernet ports
queue-scheduler Global config mode

21.2.2 Configuring a VLAN Service Profile
The parameters related to services in VLAN attributes are combined to form a profile. The profile
can be referenced by a VLAN on a device after the profile is applied to the device.
Procedure
1 Choose Configuration > Access Profile Management > VLAN Service Profile from the main
menu.
Services (OT928G)
Issue 03 (2010-11-19)
Enable BPDU Tunnel Enables the BPDU transparent transmission. After this function is
enabled, the layer 2 protocol packets in the private network can be
transmitted transparently in the public network.
This function is applicable to QinQ VLANs.

4 Click OK.
menu.
----End
Command Reference
Create a VLAN
service profile
vlan service-profile Global config mode

Procedure
Services (OT928G)
21-7
Services (OT928G)
Issue 03 (2010-11-19)
Start ID
End ID
VLANs for an OLT.

6 Click Done.
----End
Command Reference

Services (OT928G)
21-9
21.2.4 Configuring a TDM Connection
This topic describes how to add a TDM E1 connection and set up the mapping between E1 ports
and GEM ports.
Procedure
1 Choose Connection > Native TDM Connection from the navigation tree.
Network Interface Type The upstream port on the TOPA card is an E1 or STM-1 port.
If the upstream port is an STM-1 port, configure a VC12 tributary.
The VC12 tributary likes a virtual container that carries E1 frames.
Sixty-three VC12 virtual containers exist because an STM-1 port
supports 63 channels of E1 frames.

Services (OT928G)
Issue 03 (2010-11-19)
4 Click OK.
----End
Command Reference
Add a native TDM
service stream
tdm-connect Global config mode

21.2.5 Configuring a Clock Source
This topic describes how to set the clock signal of a specified port as the reference clock source
of the system.
Procedure
2 On the tab page that is displayed, choose NE Properties > Clock Management > Frequency
Clock from the navigation tree.
3 In the the Frequency Clock Source(8K) tab, right-click and choose Add Clock Source from
the shortcut menu.
Clock Type Indicates the clock type. The line clock is an E1 clock source and
is provided by an upper layer node.
The BITS clock is provided by the BITS clock device.
Services (OT928G)
21-11
Frame/Slot/Port Indicates the shelf ID, slot ID, and port ID of the clock source,
which must be the same as the actual shelf ID, slot ID, and port
ID.

5 Click OK.
----End
Command Reference
Set a port on a card in
a slot of a shelf as the
reference clock
source
clock source Global config mode

21.3 Configuration Examples of the GPON Private Line
Access and FTTO Services (OLT+OT928G)
This topic provides examples to describe how to configure various services in a GPON private
line access or FTTO network.
21.3.1 Data Plan for the GPON Private Line Access and FTTO Services (OLT+OT928G)
This topic provides the data plan for the configuration examples of the GPON private line access
or FTTO services. You can configure the services according to the data plan.
21.3.2 Configuring the Ethernet Private-Line Service of an Enterprise
In this configuration example, the OT928G gains access to the data of the Ethernet switch of an
enterprise through an FE or a GE port and transparently transmits the data in the enterprise
intranet over the public network in the QinQ VLAN private-line mode.
21.3.3 Configuring the TDM PBX Access Service/Native TDM Mobile Bearer Service (Based
on the SDH Network)
In this configuration example, the OT928G is connected to the TDM PBX of an enterprise or a
base station through an E1 port to carry the PBX fixed-line telephone service or traditional circuit
switching service in a GPON network.
21.3.4 Configuring the Ethernet Mobile Bearer Service
In this configuration example, the OT928G is connected to the 3G NodeB base station through
an FE or a GE port and the data is transmitted by the OLT to the packet switch network (PSN),
which implements IP-based wireless network.
21.3.1 Data Plan for the GPON Private Line Access and FTTO
Services (OLT+OT928G)
This topic provides the data plan for the configuration examples of the GPON private line access
or FTTO services. You can configure the services according to the data plan.
Services (OT928G)
Issue 03 (2010-11-19)
Data Plan
Table 21-1 Data plan for the GPON Private Line Access and FTTO services
Service
Type
Device
managemen
t
OLT
0/19/0 -
GPON port of the
OLT
0/2/1 -
ONT SN: 32303131B39FD641
Name: ONT
ONU Type: ONT
ONU ID: 0
Terminal Type: SmartAX
OT928G
Software Version:
V1R3C03B062
-
Ethernet
private-line
service of an
enterprise
l T-CONT Type: Assured
Bandwidth/Maximum
Bandwidth
l Assured Bandwidth: 20480
51200
-
GPON line profile l Name: FTTx
l T-CONT Index: 1
l DBA Profile: FTTx
l GEM Port Index: 1, 2
l Priority Queue: 0
l VLAN ID: 50, 60
-
Services (OT928G)
21-13
Service
Type
GPON service
profile
l Name: FTTx
l Number of TDM Ports: 8
l TDM Port Type: E1
l Service Type: Translation
l Default VLAN ID: 50, 60
l S-VLAN: 50, 60
l C-VLAN: 3000
-
VLAN service
profile
l Name: FTTx
l Enable BPDU Tunnel:
selected
-
User VLAN l VLAN ID: 2001
l Type: Smart VLAN
l Attribute: QinQ
-
Service virtual port l Name: intranet1, intranet2
l Connection Type: LAN-
GPON
l VLAN ID: 2001 (service
VLAN ID)
0/2/1/0/0
Service VLAN
l User VLAN: 50, 60 (VLAN
IDs of the enterprise
intranet)
same: selected
l Upstream/Downstream
Traffic Name: ip-traffic-
table_6
-
Services (OT928G)
Issue 03 (2010-11-19)
Service
Type
Queue scheduler
mode
l Queue scheduler mode:
WRR
l Queue0-weight: 10
l Queue1-weight: 10
l Queue2-weight: 20
l Queue3-weight: 20
l Queue4-weight: 40
-
TDM PBX
access
service/
Native TDM
private line
access
service
(based on
the SDH
network)
l T-CONT Type: Fixed
Bandwidth
l Fixed Bandwidth: 44800
l Bandwidth Compensation:
Yes
-
l Mapping Mode: E1T1
l T-CONT Index: 1
l DBA Profile: FTTx
l GEM Port Index: 1
l Service Type: TDM
l Priority Queue: 0
l Port Type: E1
l Port ID: 1
-
GPON service
profile
l Name: FTTx
l TDM Port Type: E1
-
TDM E1 connection l Name: FTTx
l Network Interface Type: E1
l Network Interface Info:
0/6/0
l User Interface Info:
0/2/1/1/0
-
Services (OT928G)
21-15
Service
Type
Clock source l Clock Type: Line clock
l Working Mode: SYSLINE
l Index: 0
l Frame: 0
l Slot: 6
l Port: 0
l Clock Type: Bit clock
l BITS Type: 2MHz
l BITS Impedance: 75ohm
l Index: 1
l Frame: 0
l Slot: 0
l Port: 0
-
Queue scheduler
mode
WRR
l Queue0-weight: 10
l Queue1-weight: 10
l Queue2-weight: 20
l Queue3-weight: 20
l Queue4-weight: 40
-
Ethernet
private line
access
service
l T-CONT Type: Assured
Bandwidth/Maximum
Bandwidth
l Assured Bandwidth: 20480
51200
-
l T-CONT Index: 1
l DBA Profile: FTTx
l GEM Port Index: 1
l Priority Queue: 0
l VLAN ID: 10
-
Services (OT928G)
Issue 03 (2010-11-19)
Service
Type
GPON service
profile
l Name: FTTx
l TDM Port Type: E1
l Vlan Type: Translation
l Default VLAN ID: 10
-
VLAN service
profile
l Name: FTTx
selected
-
Service VLAN l VLAN ID: 2000
l Type: Smart VLAN
-
Service virtual port l Name: Eth_Fttm
GPON
l VLAN ID: 2000 (service
VLAN ID)
0/2/1/0/0
Service VLAN
l User VLAN: 10 (user-side
VLAN ID)
same: selected
table_6
-
Queue scheduler
mode
WRR
l Queue0-weight: 10
l Queue1-weight: 10
l Queue2-weight: 20
l Queue3-weight: 20
l Queue4-weight: 40
-

Services (OT928G)
21-17
21.3.2 Configuring the Ethernet Private-Line Service of an
Enterprise
In this configuration example, the OT928G gains access to the data of the Ethernet switch of an
enterprise through an FE or a GE port and transparently transmits the data in the enterprise
intranet over the public network in the QinQ VLAN private-line mode.
Context
For details of the data plan, see 21.3.1 Data Plan for the GPON Private Line Access and
FTTO Services (OLT+OT928G).
The OT928G need not be configured directly and all configurations are completed on the OLT
and applied to the OT928G through the OMCI protocol.
Example Network
Figure 21-1 Configuring the Ethernet private-line service of the enterprise
NOTE
The OT928G devices gain access to the data of the intranets of enterprise branches A and B through an
Ethernet switch. Therefore, configure the QinQ VLAN private lines on the OT928G devices of the two
branches separately. Then, the service data and BPDU packets between the enterprise intranets can be
transmitted upstream to the OLT through a GPON port and the OLT transmits the signals upstream to the
IP network. In this manner, a transparent and secure data transmission channel is provided for the enterprise
branches in different areas.

Procedure
the main menu.
Services (OT928G)
Issue 03 (2010-11-19)
Name: FTTx
T-CONT Type: Assured Bandwidth/Maximum Bandwidth
Assured Bandwidth: 20480
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
(2) Click the GPON Line Profile tab.
Set Name to FTTx.
Choose Base Info from the navigation tree and set the parameters.
Mapping Mode: VLAN
Right-click T-CONT Info. in the navigation tree and choose Add T-
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 0
GEM Port Index: 2
Priority Queue: 0
the parameter.
GEM Connection Index: 0 (default value)
VLAN ID: 50 (VLAN ID of the enterprise intranet)
the parameter.
VLAN ID: 60 (VLAN ID of the enterprise intranet)
Services (OT928G)
21-19
(5) Click OK.
the shortcut menu.
Profile.
The service profile must match the ONT type. This section considers the OT928G as
an example to describe how to configure a service profile. The OT928G has five
Ethernet ports, eight E1 ports, and eight POTS ports.
the main menu.
(2) Click the GPON Service Profile tab.
Set Name to FTTx.
Number of TDM Ports: 8
TDM Port Type: E1
right-click the record where Port Type is ETH Port and Port ID is 1, and
choose UNI Port Configuration Properties from the shortcut menu. In the
dialog box that is displayed, set the parameters.
Default VLAN ID: 50 (VLAN ID of the enterprise intranet)
S-VLAN: 50 (VLAN ID of the enterprise intranet)
Services (OT928G)
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Set Name to ONT.
Set ONU ID to 0.
Set ONU Type to ONT.
On the Base Info tab page, set the parameters.
Terminal Type: SmartAX OT928G
Services (OT928G)
21-21
(6) Click OK.
l Configure the Ethernet private-line service of the enterprise on the OLT.
1. Configure a VLAN service profile. For details, see 21.2.2 Configuring a VLAN
Service Profile.
(1) Choose Configuration > Access Profile Management > VLAN Service
Name: FTTx
Enable BPDU Tunnel: selected
(4) Click OK.
the shortcut menu.
2. Configure a service VLAN on the OLT. For details, see 19.2.1 Configuring a
VLAN.
VLAN ID: 2001
Type: Smart VLAN
Attribute: QinQ
(4) Click Next.
Click the Sub Port tab and add upstream port 0/19/0 as the upstream port of
the VLAN.
Click the Extended Info tab and select the VLAN service profile named
FTTx.
(5) Click Finish.
3. Add a service virtual port on the OLT. For details, see 19.2.3 Adding a Service
Port.
(1) On the VLAN tab page, select VLAN 2001 and click the ServicePort tab in the
lower pane.
Name: intranet1
VLAN ID: 2001 (service VLAN ID)
Services (OT928G)
Issue 03 (2010-11-19)
User VLAN: 50 (VLAN ID of the enterprise intranet)
Upstream/Downstream Traffic Name: ip-traffic-table_6 (The OLT does not
restrict the rate of service streams in the management VLAN. Therefore, it is
recommended that you use the default profile ip-traffic-table_6.)
(4) Click OK.
(5) Repeat the preceding operations to add another service virtual port.
Name: intranet2
User VLAN: 60 (VLAN ID of the enterprise intranet)
4. Set queue scheduling parameters.
You need to set the queue scheduling parameters on the OLT only once. Then, the
parameters are globally valid.
The WRR mode is used for queues 0-4 and their weights are 10, 10, 20, 20, and 40
respectively. The PQ mode is used for queues 5-7.
(1) Choose Configuration > Access Profile Management > System Parameter
(2) On the System Parameter Profile tab page, select the required device type from
the Device Type drop-down list.
(4) In the dialog box that is displayed, set the name of the system parameter profile
to FTTx. Choose QoS > Queue scheduler mode from the Parameters for
Selection navigation tree, click to add the parameter to the Selected
Parameters navigation tree, and then click Next.
(5) Choose QoS > Queue scheduler mode from the navigation tree to set the queue
scheduling mode.
Queue scheduler mode: WRR
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click OK.
----End
Services (OT928G)
21-23
Result
The enterprise users in different areas of the same intranet (VLAN 50 or 60) can communicate
with each other.
21.3.3 Configuring the TDM PBX Access Service/Native TDM
Mobile Bearer Service (Based on the SDH Network)
In this configuration example, the OT928G is connected to the TDM PBX of an enterprise or a
base station through an E1 port to carry the PBX fixed-line telephone service or traditional circuit
switching service in a GPON network.
Context
Example Network
Figure 21-2 Configuring the TDM PBX access service
NOTE
The OT928G is connected to the TDM PBX of the enterprise through an E1 port and then is connected to
the OLT through a GPON upstream port. The OLT provides E1 or STM-1 ports to transmit the TDM
service to the SDH network.

Figure 21-3 Configuring the native TDM mobile bearer service (based on the SDH network)
Services (OT928G)
Issue 03 (2010-11-19)
NOTE
The OT928G gains access to the TDM service data of the base station through an E1 port, encapsulates
service packets to GEM frames in the native TDM encapsulation mode, and then transmits the GEM frames
to the OLT through a GPON port. The TOPA card on the OLT transmits E1 or STM-1 signals, depending
on the daughter card that is attached to the TOPA card.
l If E1 signals are transmitted upstream, the NH1A daughter card performs TDM packet decapsulation,
de-jitter buffer, and clock synchronization. After the NH1A card obtains the VC12, it converts the
TDM data packets to E1 frames according to the mapping and transmits the E1 frames to upper layer
SDH equipment through the corresponding E1 port.
l If STM-1 signals are transmitted upstream, the O2CE daughter card performs TDM packet
decapsulation, de-jitter buffer, and clock synchronization. After the O2CE card obtains the VC12, it
maps the VC12 to VC4 and then to the STM-1 port for transmission to upper layer SDH equipment.
l Native TDM refers to encapsulating TDM frames to GPON GEM frames (TDMoGEM) and
transmitting the frames over the GPON network. This mode features simple encapsulation, low
network overhead, and good link quality.

Procedure
The bandwidth of each E1 port on the OT928G is 4416 kbit/s. If the OT928G works
in the native TDM mode, however, you need to enable the bandwidth compensation
function because of the following:
Packets in the TDMoEoGEM encapsulation mode contain the information about
the Ethernet, GEM frames, and TDM payloads.
Packet fragmentation and queue buffer cause more overheads.
The recommended formula for calculating the TDM bandwidth is Bandwidth = 4416
x N + 640 kbit/s, where N equals the number of E1 ports.
the main menu.
Name: FTTx
T-CONT Type: Fixed Bandwidth
Fixed Bandwidth: 44800
Bandwidth Compensation: Yes
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Services (OT928G)
21-25
Set Name to FTTx.
Mapping Mode: E1T1
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
Service Type: TDM
the parameter.
Port Type: E1
Port ID: 1
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Services (OT928G)
Issue 03 (2010-11-19)
TDM Port Type: E1
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Set Name to ONT.
Set ONU ID to 0.
(6) Click OK.
l Configure the native TDM service on the OLT.
1. Set queue scheduling parameters. For details, see 21.2.1 Setting Queue Scheduling
Parameters.
Services (OT928G)
21-27
(2) On the System Parameter Profile tab page, select the required OLT type from
to FTTx. Choose QoS > 802.1p PRI queue and QoS > Queue scheduler
mode from the Parameters for Selection navigation tree, click to add
the parameters to the Selected Parameters navigation tree, and then click
Next.
(5) Choose 802.1p PRI queue from the navigation tree and configure the mapping
between queues and 802.1p priorities. It is recommended that you use the default
values. Choose Queue scheduler mode from the navigation tree and configure
the queue scheduling mode.
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click Finish.
the shortcut menu.
2. Configure a TDM connection.
Set up a native TDM service stream between the GEM port and the upstream port on
the TPOA card.
(1) Choose Connection > Native TDM Connection from the navigation tree.
(3) If the upstream port is an E1 port, set the parameters as follows:
Name: FTTx
Network Interface Type: E1
Network Interface Info: 0/6/0
User Interface Info: 0/2/1/1/1
(4) If the upstream port is an STM-1 port, set the parameters of the VC12 tributary
as follows:
Name: FTTx
Network Interface Type: VC12
Network Interface Info: 0/6/0
User Interface Info: 0/2/1/1/1
(5) Click OK.
Services (OT928G)
Issue 03 (2010-11-19)
CAUTION
In the case of the TDM service, ensure that the clock source is unique in the entire
SDH network. Otherwise, error codes are generated and affect service quality, and
services may be interrupted if a large number of error codes are generated.
(1) On the tab page that is displayed, choose NE Properties > Clock
Management > Frequency Clock from the navigation tree.
(2) On the Frequency Clock Source(8K) tab page, right-click and choose Add
Clock Source from the shortcut menu.
(3) In the information list, click the Frequency Clock Source(8K) tab, right-click
and choose Add Clock Source from the shortcut menu.
Clock Type: Line clock
Working Mode: SYSLINE
Index: 0
Frame: 0
Slot: 6
Port: 0
(4) Click OK.
(5) Repeat the preceding operations to add a BITS clock (provided by the BIUA
card).
Clock Type: Bit clock
BITS Type: 2MHz
BITS Impedance: 75ohm
Index: 1
Frame: 0
Slot: 0
Port: 0
----End
Result
The mobile terminals (such as mobile phones) near the base station gain the information about
the network that they belong to and make calls or send short messages successfully.
21.3.4 Configuring the Ethernet Mobile Bearer Service
In this configuration example, the OT928G is connected to the 3G NodeB base station through
an FE or a GE port and the data is transmitted by the OLT to the packet switch network (PSN),
which implements IP-based wireless network.
Context
Services (OT928G)
21-29
Example Network
Figure 21-4 Configuring the Ethernet mobile bearer service
NOTE
The data of the 3G base station is transmitted to the OT928G through an FE or a GE port and encapsulated
to GEM frames on the OT928G. Then, the GEM frames are transmitted upstream to the OLT through a
GPON port, and the data is restored by the OLT and then transmitted to the PSN network through an FE,
a GE, or a 10GE port.

Procedure
the main menu.
Name: FTTx
T-CONT Type: Assured Bandwidth/Maximum Bandwidth
Assured Bandwidth: 20480
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Services (OT928G)
Issue 03 (2010-11-19)
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 0
the parameters.
VLAN ID: 10 (user-side VLAN ID)
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
TDM Port Type: E1
Default VLAN ID: 10 (user-side VLAN ID)
Services (OT928G)
21-31
S-VLAN: 10 (user-side VLAN ID)
(5) Click OK.
the shortcut menu.
the shortcut menu.
GPON UNI ports.
menu.
Set Name to ONT.
Set ONU ID to 0.
(6) Click OK.
l Configure the Ethernet mobile bearer service on the OLT.
VLAN.
Services (OT928G)
Issue 03 (2010-11-19)
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next. Click the Sub Port tab and add upstream port 0/19/0 as the upstream
port of the VLAN.
(5) Click Finish.
Port.
lower pane.
Name: Eth_Fttm
User VLAN: 10 (user-side VLAN ID)
(4) Click OK.
Parameters.
Next.
Services (OT928G)
21-33
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click Finish.
the shortcut menu.
----End
Result
The mobile terminals (such as mobile phones) near the 3G base station gain the information
about the network that they belong to and make calls or send short messages successfully.
Services (OT928G)
Issue 03 (2010-11-19)
22 Configuring xPON Private Line Access
and FTTO Services (MA5612)
About This Chapter
The deployment of an optical line terminal (OLT) and MA5612 in a network provides the private
line access and fiber to the office (FTTO) solutions.
Context
l In the private line access solution, a cellular backhaul unit (CBU) is connected to the OLT
in PON mode to implement private line access.
l In the FTTO solution, a single business unit (SBU) is connected to the OLT in PON mode
to implement FTTO. In this way, the TDM PBX, IP PBX, and private line services of
enterprise Intranets are provided.
22.1 Adding an MDU to the U2000 When the OLT Works in Profile Mode
This topic describes how to add the MA5612 to the U2000 when the OLT works in profile mode.
After the MA5612 is successfully added to the U2000, you can configure the private line access
service for the MA5612 on the U2000.
22.2 Configuring Services on an OLT
A private line access network with an OLT and MA5612 provides various services for users.
22.3 Configuring Services on an MDU
A private line access network with an OLT and the MA5612 provides various services for users.
22.4 Configuring Clock Synchronization
This topic describes how to configure clock synchronization, which ensures that data is
transmitted and processed correctly in a communications network and a telecommunications
network runs efficiently with high quality.
22.5 Configuration Examples of xPON Private Line Access and FTTO Services (MA5612)
This topic provides examples for configuring various services in an xPON private line access
or FTTO network.
22 Configuring xPON Private Line Access and FTTO
Services (MA5612)
22-1
22.1 Adding an MDU to the U2000 When the OLT Works in
Profile Mode
This topic describes how to add the MA5612 to the U2000 when the OLT works in profile mode.
After the MA5612 is successfully added to the U2000, you can configure the private line access
service for the MA5612 on the U2000.
Procedure
l Adding a GPON MDU
1. 19.1.1 Configuring an MDU SNMP Profile
2. 19.1.2 Configuring a DBA Profile
3. 20.1.1 Configuring a GPON Line Profile
4. 19.1.4 Confirming an MDU
5. 19.1.5 Configuring a VLAN
6. 19.1.6 Adding a Service Virtual Port
7. 19.1.7 Checking the Communication Between the OLT and MDU
l Adding an EPON MDU
1. 19.1.1 Configuring an MDU SNMP Profile
2. 23.1.2 Configuring a DBA Profile
3. 23.1.3 Configuring a Line Profile
4. 23.1.4 Confirming an MDU
5. 19.1.5 Configuring a VLAN
6. 23.1.6 Adding a Service Virtual Port
7. 23.1.7 Verifying the Interoperability Between an OLT and an MDU
----End
22.2 Configuring Services on an OLT
Context
Several operations are required to configure a service. The following table lists the services
configured and the steps for configuring the services.
Services Steps
TDM PWE3 private line access
service
l 22.2.1 Configuring the Attributes of a TOPA Card
l 22.2.2 Configuring a CESoP Connection
Services (MA5612)
Issue 03 (2010-11-19)
Services Steps
Router access service of an
enterprise

22.2.1 Configuring the Attributes of a TOPA Card
This topic describes how to set the IP address of a TOPA card. The CESoP connection can be
created only on a TOPA card that is configured with an IP address.
22.2.2 Configuring a CESoP Connection
After a CESoP connection and the service virtual port of the CESoP connection are added
successfully, the CESoP E1 line can be used for communication.
22.2.1 Configuring the Attributes of a TOPA Card
This topic describes how to set the IP address of a TOPA card. The CESoP connection can be
created only on a TOPA card that is configured with an IP address.
Procedure
2 Choose NE Panel from the navigation tree.
3 Right-click the TOPA card and choose Config Board from the shortcut menu.
4 In the dialog box that is displayed, set IP Address.
IP Address Indicates the IP address of a TOPA card. The TOPA card supports
two types of daughter cards: CSSA and EH1A.

5 Click OK.
----End
Command Reference
Set the IP address of
a TOPA card
set ip-address TOP interface configuration
mode
Set the IP address of
a TOPA card
ip-address TOPA STM-1 mode

Services (MA5612)
22-3
22.2.2 Configuring a CESoP Connection
After a CESoP connection and the service virtual port of the CESoP connection are added
successfully, the CESoP E1 line can be used for communication.
Procedure
2 Choose E1/T1 > CES E1/T1 Port from the navigation tree.
3 On the CES E1 Port tab page, select a port and click the CESoP Info tab in the lower pane.
4 In the information list, right-click and choose Add CESoP Connection from the shortcut menu.
Remote MAC Indicates the remote MAC address of a CESoP connection.
Remote IP Indicates the destination IP address of a CESoP connection.
Remote UDP Label Indicates the UDP label of the local address of a CESoP
connection.
Local UDP Label Indicates the UDP label of the remote address of a CESoP
connection. This parameter is used to set up mapping between
UDP labels and E1 ports. Therefore, the CESoP connections of a
TOPA card (with the EH1A daughter card) must be configured
with different UDP port numbers.

6 Click OK.
----End
Services (MA5612)
Issue 03 (2010-11-19)
Command Reference
Add a CESoP
connection
cesop-connect Global config mode

22.3 Configuring Services on an MDU
A private line access network with an OLT and the MA5612 provides various services for users.
Context
Several operations are required to configure a service. The following table lists the services
configured and the steps for configuring the services.
Services Steps
TDM PWE3 private line access
service
l 22.3.3 Configuring the MPLS Capability
l 22.3.4 Configuring an MPLS Tunnel
l 22.3.5 Configuring a Static LSP Segment
l 22.3.6 Configuring a PW Profile
l 22.3.7 Adding a TDM VCL
l 22.3.8 Configuring the PWE3
Router access service of an
enterprise
l 21.2.2 Configuring a VLAN Service Profile

22.3.2 Setting Telnet/STelnet Parameters
The U2000 communicates with devices successfully based on the preset Telnet or STelnet
parameters.
22.3.3 Configuring the MPLS Capability
This topic describes how to configure a label switch router (LSR) ID for a device and enable the
multiprotocol label switching (MPLS) capability of the device.
22.3.4 Configuring an MPLS Tunnel
This topic describes how to configure the name, ID, and destination of an MPLS TE tunnel.
Services (MA5612)
22-5
22.3.5 Configuring a Static LSP Segment
This topic describes how to configure a static label switched path (LSP). LSP is a unidirectional
path from an ingress node to egress node, in which each node is an LSR. When you need to
create an LSP on an ingress node to identify the path in the MPLS network that a forwarding
equivalence class (FEC) passes, perform this operation.
22.3.6 Configuring a PW Profile
A pseudo wire (PW) profile is a set of feature parameters related to the PW and can be bound
to PWs of the same type. A PW profile can be bound to a PW only after the PW type and the
peer address are set, and the PW profile that is bound to a PW cannot be deleted.
22.3.7 Adding a TDM VCL
The TDM virtual channel link (VCL) is an attachment circuit (AC). When creating a TDM PW
service, you need to set up a communication channel between ACs to implement transparent
transmission of Layer 2 data of users.
22.3.8 Configuring the PWE3
This topic describes how to set up PWs of different types to emulate end-to-end services.
Procedure
Services (MA5612)
Issue 03 (2010-11-19)
Services (MA5612)
22-7
Start ID
End ID

6 Click Done.
----End
Command Reference

Services (MA5612)
Issue 03 (2010-11-19)
22.3.2 Setting Telnet/STelnet Parameters
The U2000 communicates with devices successfully based on the preset Telnet or STelnet
parameters.
Procedure
1 In Main Topology, right-click the required MA5612 in the Physical Root navigation tree and
choose MPLS Management > Telnet Configuration from the shortcut menu.
Auth. Mode Indicates the authentication mode. The options are No Auth,
Password Auth, and User Auth.
User Name Indicates the user name for login. It consists of letters (A to Z and
a to z), numbers, and symbols.

3 Click OK.
----End
Result
After the parameters are set, click Test. If a dialog box is displayed indicating that the operation
is successful, the U2000 can communicate with devices successfully based on the Telnet
parameters.
22.3.3 Configuring the MPLS Capability
This topic describes how to configure a label switch router (LSR) ID for a device and enable the
multiprotocol label switching (MPLS) capability of the device.
Services (MA5612)
22-9
Prerequisite
The Telnet parameters must be set to ensure that the U2000 communicates with devices
successfully. For details, see 22.3.2 Setting Telnet/STelnet Parameters.
Procedure
1 In the Main Topology, right-click the required NE in the Physical Root navigation tree and
choose MPLS Management > MPLS Configuration from the shortcut menu.
2 On the tab page that is displayed, click the MPLS Capability Configuration tab and set the
parameters.
LSR ID Indicates an LSR ID. It can be the IP address of a loopback
interface on an LSR. The LSR ID is an IPv4 address and must be
unique in the MPLS domain.
Enable MPLS Enables MPLS. You can enable MPLS only after setting the LSR
ID.
Enable MPLS L2VPN Enables MPLS L2VPN of a device. You can enable MPLS L2VPN
of a device only after enabling the MPLS capability of the device.

3 Click Apply.
----End
Command Reference
Configure the ID of
an LSR
mpls lsr-id Global config mode
Enable MPLS mpls Global config mode, VLANIF
mode
Enable MPLS
L2VPN
mpls l2vpn Global config mode
Services (MA5612)
Issue 03 (2010-11-19)

22.3.4 Configuring an MPLS Tunnel
This topic describes how to configure the name, ID, and destination of an MPLS TE tunnel.
Procedure
choose MPLS Management > Tunnel Configuration from the shortcut menu.
2 On the tab page that is displayed, click the Tunnel Configuration tab. In the information list,
right-click and choose Create from the shortcut menu.
Tunnel ID Indicates the ID of a tunnel. The tunnel ID must be unique on the
same device.
Destination Indicates the LSR ID of an egress node.

3 Click OK.
----End
Services (MA5612)
22-11
Command Reference
Enter the tunnel
mode from the
global config mode
interface tunnel Global config mode
Configure the
encapsulation
protocol at the data
link layer for a tunnel
interface
tunnel-protocol Tunnel mode
Configure the
destination IP
address of an MPLS
TE tunnel
destination Tunnel mode

22.3.5 Configuring a Static LSP Segment
This topic describes how to configure a static label switched path (LSP). LSP is a unidirectional
path from an ingress node to egress node, in which each node is an LSR. When you need to
create an LSP on an ingress node to identify the path in the MPLS network that a forwarding
equivalence class (FEC) passes, perform this operation.
Procedure
choose MPLS Management > Static LSP Segment from the shortcut menu.
2 On the tab page that is displayed, click the Static LSP Segment Configuration tab, right-click,
and choose Create from the shortcut menu. In the dialog box that is displayed, set the parameters
of the ingress node in the static LSP.
Services (MA5612)
Issue 03 (2010-11-19)
Protocol Type Indicates the protocol type of the static LSP service.
Destination Indicates the LSR ID of an egress node.
Next Hop Indicates the IP address of the next-hop interface of an ingress
node.

3 Click OK.
----End
Command Reference
Configure the LSP
where the ingress
LSR is located
static-lsp ingress Global config mode
Configure the LSP
where the egress
LSR is located
static-lsp egress Global config mode

22.3.6 Configuring a PW Profile
A pseudo wire (PW) profile is a set of feature parameters related to the PW and can be bound
to PWs of the same type. A PW profile can be bound to a PW only after the PW type and the
peer address are set, and the PW profile that is bound to a PW cannot be deleted.
Procedure
choose MPLS Management > PW Template Configuration from the shortcut menu.
2 On the tab page that is displayed, right-click and choose Create from the shortcut menu.
Services (MA5612)
22-13
Control Word Indicates a control word. Packets may be out of order when load
balancing is adopted. In this case, you can use the control word to
reorder the packets.
You must enable the control word of a PW profile if the PW type
is set to TDM.
Peer IP Address Indicates the IP address of the peer PW.
Rtp Header Enable Specifies whether an RTP header is added during encapsulation
for TDM transparent transmission.

Services (MA5612)
Issue 03 (2010-11-19)
4 Click OK.
----End
Command Reference
Create a PW profile PW-para Global config mode

22.3.7 Adding a TDM VCL
The TDM virtual channel link (VCL) is an attachment circuit (AC). When creating a TDM PW
service, you need to set up a communication channel between ACs to implement transparent
transmission of Layer 2 data of users.
Procedure
2 Choose Connection > TDM VCL from the navigation tree.
Connection Type Indicates the PW type. You need to set this parameter when data
packets are transmitted over a TDM network.
When data packets are transmitted over a TDM network, a TDM
connection ID identifies a service stream. In the case of
unstructured TDM data, set the PW type to TDM SAToP. In the
case of structured TDM data, set the PW type to TDM CESoP.

5 Click OK.
----End
Services (MA5612)
22-15
Command Reference
Bind a TDM
connection and a PW
and create the PW
service of the TDM
type
pw-ac-binding tdm Global config mode
Configure the type of
a PW
pw-type PW-template mode

22.3.8 Configuring the PWE3
This topic describes how to set up PWs of different types to emulate end-to-end services.
Procedure
2 Choose PW Management from the navigation tree.
Services (MA5612)
Issue 03 (2010-11-19)
PW Type Create a PW service of the ETH, TDM, or ATM type
Signal Protocol l Idp: Indicates that a PW is set up through the signaling
protocol.
l static or udp: Indicates that parameters are not negotiated
through the signaling protocol and but are specified manually
to set up a PW.
AC Indicates the AC that is used for forwarding Layer 2 packets.
Select different ACs according to PW types.

5 Click OK.
----End
Services (MA5612)
22-17
Command Reference
Bind a TDM connection and
a PW and create the PW
service of the TDM type
pw-ac-binding tdm Global config mode
Bind a VLAN and a PW and
create the PW service of the
ETH type
pw-ac-binding vlan Global config mode
Bind a PVC and a PW and
create the PW service of the
ATM type
pw-ac-binding pvc Global config mode
Create a PW profile pw-template Global config mode

22.4 Configuring Clock Synchronization
This topic describes how to configure clock synchronization, which ensures that data is
transmitted and processed correctly in a communications network and a telecommunications
network runs efficiently with high quality.
Context
In a private line access network, the system clock of an OLT is transmitted to an ONU through
an xPON line. Then, the system clock of the ONT is synchronized with the system clock of the
OLT. The ONU transmits the clock to a base transceiver station (BTS) through an E1 or Ethernet
port.
22.4.1 Configuring E1/STM-1 Line Clock Synchronization
This topic describes how to configure clock synchronization. After the line clock
synchronization is configured, the clock is synchronized to the E1/STM-1 line clock when the
OLT accesses the SDH network through an upstream E1 or STM-1 port.
22.4.2 Configuring Ethernet Clock Synchronization
This topic describes how to configure Ethernet clock synchronization. After Ethernet clock
synchronization is configured, the technology of recovering the clock from bit streams on the
Ethernet link is applied to implement synchronization between Ethernets when the OLT accesses
the packet switched network (PSN) through a GE port.
22.4.3 Configuring BITS Clock Synchronization
This topic describes how to configure Building Integrated Timing Supply (BITS) clock
synchronization. After the BITS clock synchronization is configured, the OLT receives the clock
through BITS and transmits the clock signals to the cellular backhaul unit (CBU) through the
PON line and then to the base transceiver station (BTS). In this manner, the clock synchronization
is achieved for the entire network.
22.4.4 Configuring IEEE 1588v2 Clock Synchronization
This topic describes how to configure IEEE 1588v2 clock synchronization. After this
configuration is complete, the OLT obtains the IEEE 1588v2 clock signals from the upper-layer
network and transmits the signals to the CBU through the GPON line and then to the base
Services (MA5612)
Issue 03 (2010-11-19)
transceiver station (BTS). In this manner, the clock synchronization is achieved for the entire
network.
22.4.1 Configuring E1/STM-1 Line Clock Synchronization
This topic describes how to configure clock synchronization. After the line clock
synchronization is configured, the clock is synchronized to the E1/STM-1 line clock when the
OLT accesses the SDH network through an upstream E1 or STM-1 port.
Prerequisite
The SCU control card must be configured with the clock daughter card CKMC.
Context
The configuration concept is as follows:
1. The OLT traces the upstream E1/STM-1 line clock of the TOPA card as the system clock.
2. Signals of the system clock are transmitted to the MA5612 through the optical channel
provided by the GPON service card.
3. The MA5612 uses the line clock of the GPON upstream port as the system clock.
4. The transmit clock of the E1 port of the MA5612 is synchronized to the system clock of
the MA5612.
To configure clock synchronization for an NE, you need to navigate to the NE Explorer of the
NE. For details, see In the Main Topology, double-click the required NE in the Physical Root
navigation tree; or right-click the required NE and choose NE Explorer from the shortcut
menu. .
Procedure
l Configure the clock on the OLT.
NOTE
Set the line clock of the upstream E1 or STM-1 port on the TOPA card as the system clock source with
the highest priority.
1. On the tab page that is displayed, choose NE Properties > Clock Management >
Frequency Clock from the navigation tree.
2. On the Frequency Clock Source(8K) tab page, right-click and choose Add Clock
Source from the shortcut menu.
3. In the dialog box that is displayed, set the parameters as follows:
Index: 0
Frame: 0
Slot: 5
Port: 0
4. Click OK.
5. In the information list, right-click the new clock source and choose Set Clock Source
Priority from the shortcut menu.
6. In the dialog box that is displayed, set Priority to 0.
7. Click OK.
Services (MA5612)
22-19
l Configure the clock on the MA5612.
1. Configure the system clock and its priority.
NOTE
Set the clock recovered from the GPON upstream port as the system clock of the MA5612 with the
highest priority.
(2) On the Frequency Clock Source(SYSCLK) tab page, right-click and choose
Add Clock Source from the shortcut menu.
(3) In the dialog box that is displayed, set the parameters as follows:
Index: 0
Frame: 0
Slot: 0
Port: 0
(4) Click OK.
(5) In the information list, right-click the new clock source and choose Set Clock
Source Priority from the shortcut menu.
(6) In the dialog box that is displayed, set Priority to 0.
(7) Click OK.
2. Set the system clock as the transmit clock of the E1 port.
(1) Choose E1/T1 > CES E1/T1 Port from the navigation tree.
(2) In the information list, right-click the record whose name is Frame:0/Slot:1/
Port:0 and choose Modify from the shortcut menu.
(3) In the dialog box that is displayed, set Working Mode to UDT and Clock
Type to System.
(4) Click OK.
----End
22.4.2 Configuring Ethernet Clock Synchronization
This topic describes how to configure Ethernet clock synchronization. After Ethernet clock
synchronization is configured, the technology of recovering the clock from bit streams on the
Ethernet link is applied to implement synchronization between Ethernets when the OLT accesses
the packet switched network (PSN) through a GE port.
Prerequisite
The GIU upstream card must be the GICK or GSCA card with GE ports.
The upstream MAN PSN network of the OLT must have the capability of synchronizing the
Ethernet clock.
Context
Services (MA5612)
Issue 03 (2010-11-19)
1. The OLT uses the synchronous Ethernet clock of the upstream slot as the system clock.
4. The transmit clock of the E1, FE, or GE port of the MA5612 is synchronized to the system
clock of the MA5612.
menu. .
Procedure
NOTE
Set the line clock of the GE port on the GIU card as the system clock source with the highest priority.
Index: 0
Frame: 0
Slot: 19
Port: 0
4. Click OK.
7. Click OK.
NOTE
highest priority.
Index: 0
Frame: 0
Slot: 0
Services (MA5612)
22-21
Port: 0
(4) Click OK.
(7) Click OK.
2. (Optional) Set the system clock as the transmit clock of the E1 port.
NOTE
This operation is required only when the base transceiver station (BTS) accesses the
MA5612 through an E1 port. When the BTS accesses the MA5612 through an FE or GE port,
you can skip this step. By default, the system clock is irreplaceably set as the transmit clock of
the E1 port.
Type to System.
(4) Click OK.
----End
22.4.3 Configuring BITS Clock Synchronization
This topic describes how to configure Building Integrated Timing Supply (BITS) clock
synchronization. After the BITS clock synchronization is configured, the OLT receives the clock
through BITS and transmits the clock signals to the cellular backhaul unit (CBU) through the
PON line and then to the base transceiver station (BTS). In this manner, the clock synchronization
is achieved for the entire network.
Prerequisite
The OLT must have the BITS clock input resource.
The CITD card must be configured with the BITS clock daughter card and work in the normal
state.
Context
1. The OLT uses the BITS line clock as the system clock.
4. The transmit clock of the E1 port of the MA5612 is synchronized to the system clock of
the MA5612.
Services (MA5612)
Issue 03 (2010-11-19)
menu. .
Procedure
NOTE
Set the line clock of two BITS_IN ports on the CITD card as the system clock with the highest priority.
Index: 0
Frame: 0
Slot: 0
Port: 0
4. Click OK.
7. Click OK.
8. Repeat the preceding steps to add a clock source whose Frame is 0, Slot is 0, and
Port is 1 and set its Priority to 1.
NOTE
highest priority.
Index: 0
Frame: 0
Slot: 0
Port: 0
(4) Click OK.
(7) Click OK.
Services (MA5612)
22-23
NOTE
the E1 port.
Type to System.
(4) Click OK.
----End
22.4.4 Configuring IEEE 1588v2 Clock Synchronization
This topic describes how to configure IEEE 1588v2 clock synchronization. After this
configuration is complete, the OLT obtains the IEEE 1588v2 clock signals from the upper-layer
network and transmits the signals to the CBU through the GPON line and then to the base
transceiver station (BTS). In this manner, the clock synchronization is achieved for the entire
network.
Prerequisite
The GICK card must exist.
The GPON service card must be the GPBD card.
Context
1. The OLT uses the clock recovered from IEEE 1588v2 packets as the system clock.
4. The transmit clock of the E1 or FE/GE port of the MA5612 is synchronized to the system
clock of the MA5612.
menu. .
Procedure
1. Set the IEEE 1588v2 clock source and its priority.
Services (MA5612)
Issue 03 (2010-11-19)
Working Mode: 1588
Index: 0
Frame: 0
Slot: 19
Port: 0
(4) Click OK.
(7) Click OK.
(8) Repeat the preceding steps to add a clock source whose Frame is 0, Slot is 19,
and Port is 1 and set its Priority to 1.
NOTE
highest priority.
Index: 0
Frame: 0
Slot: 0
Port: 0
(4) Click OK.
(7) Click OK.
NOTE
the E1 port.
Services (MA5612)
22-25
Type to System.
(4) Click OK.
----End
22.5 Configuration Examples of xPON Private Line Access
and FTTO Services (MA5612)
This topic provides examples for configuring various services in an xPON private line access
or FTTO network.
22.5.1 Data Plan for xPON Private Line Access Services
This topic describes the data plan for the configuration examples of xPON private line access
services. You can configure the services according to the data plan.
22.5.2 Configuring the TDM PWE3 Private Line Access Service (Based on the SDH Network)
In this configuration example, the MA5612 is connected to a 2G or 3G base transceiver station
(BIS) through an E1 port to carry traditional circuit switching services over an xPON network.
This topic considers a GPON network as an example.
22.5.3 Configuring the TDMoGEM Private Line Access Service (Based on the SDH Network)
(BIS) through an E1 port to carry traditional circuit switching services over a GPON network.
22.5.4 Configuring the TDMoGEM-to-TDM PWE3 Conversion Private Line Access Service
(Based on the MPLS Network)
22.5.5 Configuring the ETH PWE3 Private Line Access Service
(BIS) through an Ethernet port to carry Ethernet services over an xPON network. This topic
considers a GPON network as an example.
22.5.6 Configuring the QinQ Private-Line Private Line Access Service
In this configuration example, the MA5612 is connected to an IP base transceiver station (BIS)
through an FE or a GE port and the OLT transmits QinQ private line services to Metro equipment
to implement the private line access service. This topic considers a GPON network as an
example.
22.5.7 Data Plan for xPON FTTO Services
This topic provides the data plan for the configuration examples of xPON FTTO services. You
can configure the services according to the data plan.
22.5.8 Configuring the TDM PBX Access Service
In this configuration example, the MA5612 is connected to the TDM PBX of an enterprise
through an E1 port and the OLT transmits signals upstream to the SDH or PSN network.
22.5.9 Configuring the IP PBX Access Service
In this configuration example, the MA5612 is connected to the IP PBX of an enterprise through
an FE or a GE port and the OLT transmits signals upstream to the PSN network.
Services (MA5612)
Issue 03 (2010-11-19)
22.5.10 Configuring the Router Access Service of an Enterprise
In this configuration example, the MA5612 is connected to the router or Layer 3 switch of an
enterprise through an FE or a GE port and the OLT transmits signals upstream to the IP network.
22.5.1 Data Plan for xPON Private Line Access Services
This topic describes the data plan for the configuration examples of xPON private line access
services. You can configure the services according to the data plan.
Data Plan
Table 22-1 xPON private line access services - device management
Service
Type
Device
managemen
t
Upstream port of an
OLT
0/19/0 -
Management
VLAN
l VLAN ID: 4000
l Type: Smart VLAN
-
MDU l Name: MDU
l ONU Type: MDU
l ONU ID: 0
l SN: 32303131B39FD641
l Manager VLAN: 4000
l IP Address: 192.168.50.2
l IP Address Mask:
255.255.255.0
-
l T-CONT type: Fixed
Bandwidth
Yes
-
MDU SNMP Profile l Name: snmpprofile
l SNMP Version: v1
l Read Name: public
l Trap Host IP: 192.168.50.3
public
-
Services (MA5612)
22-27
Service
Type
l T-CONT Index: 1
l DBA Profile: FTTx
l Priority Queue: 1
l VLAN ID: 4000, 500
-
(based on the
management
VLAN)
l VLAN ID: 4000
0/2/1/0/0
Service VLAN
l User VLAN: 4000
-

Table 22-2 GPON private line access services - TDM PWE3 private line access service (based
on the SDH network)
Service
Type
Data of an
OLT
TOPA card l Port: 0/6/0
-
l Type: Smart VLAN
-
Service virtual port l Name: tdmpwe3
GPON
l VLAN ID: 500
0/2/1/0/0
Service VLAN
l User VLAN: 500
same: selected
table_6
-
Services (MA5612)
Issue 03 (2010-11-19)
Service
Type
Queue scheduling
mode
WRR
l Queue0-weight: 10
l Queue1-weight: 10
l Queue2-weight: 20
l Queue3-weight: 20
l Queue4-weight: 40
-
CESoP connection l Remote MAC: 00-e0-
fc-01-04-50
l Remote IP: 5.5.5.5
l Remote UDP Label: 50050
l Local UDP Label: 50050
l VLAN: 500
-
Data of the
MA5612
GPON upstream
port
0/0/0 -
l Type: Smart VLAN
l IP Address of L3 Interface:
10.50.50.50
l IP Mask of L3 Interface:
255.255.255.0
-
MPLS capability l LSR ID: 5.5.5.5
l Enable MPLS: selected
l Enable MPLS L2VPN:
selected
-
MPLS tunnel l Tunnel Name: Tunnel10
l Tunnel ID: 10
l Encap. Protocol: MPLS TE
l Destination: 20.20.20.20
-
Static route l IP Address: 20.20.20.20
l IP Address Mask:
255.255.255.255
l Next Hop IP Address:
10.50.50.1
-
Services (MA5612)
22-29
Service
Type
PW profile l Name: pwt
l Control Word: control-
word
l Tunnel Policy: Tunnel10
l Peer IP Address:
20.20.20.20
l Rtp Header Enable:
selected
l Load Time: 125
-
PWE3 l PW ID: 1
l Name: pw1
l PW Type: TDM
l PW Profile: pwt
l Port Type: UDT
l Port: 0/3/0
l Signal Protocol: udp
l DST UDP: 50050
TDM VCL
l ID: 10
l Connection Type: SAToP
-
Clock source Adaptive clock
l Working mode: Adapt
l Index: 0
l Frame: 0
l Slot: 0
Line clock
l Working mode: SYSLINE
l Index: 1
l Frame: 0
l Slot: 0
l Port: 0
-

Services (MA5612)
Issue 03 (2010-11-19)
22.5.2 Configuring the TDM PWE3 Private Line Access Service
(Based on the SDH Network)
(BIS) through an E1 port to carry traditional circuit switching services over an xPON network.
This topic considers a GPON network as an example.
Context
For details of the data plan, see 22.5.1 Data Plan for xPON Private Line Access Services.
This topic is applicable to the scenario wherein an OLT terminates the data of the
MA5612 and then transmits signals to the SDH network.
If you need to configure clock synchronization of the entire network, see 22.4.1 Configuring
E1/STM-1 Line Clock Synchronization.
Example Network
Figure 22-1 Configuring the TDM PWE3 private line access service (based on the SDH
network)
NOTE
The MA5612 receives the TDM service data of the 2G or 3G BTS through an E1 port and then transmits
the data upstream to the GPON service card on the OLT through a GPON port after SAToP emulation.
The OLT terminates the emulated data and restores TDM signals, and then transmits the signals to the SDH
network through the E1 port provided by the EH1A daughter card on the TOPA card. In this way, the 2G
or 3G mobile bearer service is implemented between the MA5612 and the OLT in TDM PW mode.

Procedure
l Add the MA5612 to the U2000 in profile mode.
1. Configure a management VLAN on the OLT. For details, see 19.1.5 Configuring
a VLAN.
A management VLAN is the VLAN through which an OLT manages an MDU. The
OLT manages the MDU by using the SNMP protocol. The IP address of the L3
Services (MA5612)
22-31
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
the main menu.
Name: FTTx
T-CONT type: Fixed bandwidth
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
Services (MA5612)
Issue 03 (2010-11-19)
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Priority: 2
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Services (MA5612)
22-33
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Services (MA5612)
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the TDM PWE3 private line access service on the OLT.
VLAN.
Services (MA5612)
22-35
VLAN ID: 500
Type: Smart VLAN
port of the VLAN.
(5) Click Finish.
Port.
lower pane.
Name: tdmpwe3
VLAN ID: 500
User VLAN: 500
Upstream Traffic Name/Downstream Traffic Name: ip-traffic-table_6 (It is
(4) Click OK.
Parameters.
Next.
Services (MA5612)
Issue 03 (2010-11-19)
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click Finish.
the shortcut menu.
4. Configure the attributes of the TOPA card. For details, see 22.2.1 Configuring
the Attributes of a TOPA Card.
(1) Choose NE Panel from the navigation tree.
(2) Right-click the TOPA card and choose Config Board from the shortcut menu.
(3) In the dialog box that is displayed, set IP Address to 20.20.20.20.
(4) Click OK.
5. Configure a CESoP connection. For details, see 22.2.2 Configuring a CESoP
Connection.
NOTE
Perform this step only after configuring the MA5612 because certain parameters are obtained
from the MA5612.
(2) On the CES E1 Port tab page, select port 0/6/0 and click the CESoP Info tab in
the lower pane.
(3) In the information list, right-click and choose Add CESoP Connection from the
shortcut menu.
Remote MAC: 00-e0-fc-01-04-50 (MAC address of VLAN interface 500 of
the MA5612)
Remote IP: 5.5.5.5 (IP address of the loopback interface that the LSR ID of
the MA5612 corresponds to)
Remote UDP Label: 50050
Local UDP Label: 50050
VLAN: 500 (service VLAN ID)
(5) Click OK.
l Configure the TDM PWE3 private line access service on the ONU.
1. Configure an MPLS VLAN. For details, see 19.3.1 Configuring a VLAN.
(2) In the informational list, right-click and choose Add from the shortcut menu.
VLAN ID: 500
Type: Smart VLAN
Services (MA5612)
22-37
(4) Click Next.
Management Status: UP
IP Address: 10.50.50.50 (next-hop IP address of the ingress node)
IP Mask: 255.255.255.0
the VLAN.
(5) Click Done.
2. Configure the MPLS capability. For details, see 22.3.3 Configuring the MPLS
Capability.
(1) In the Main Topology, right-click the required NE in the Physical Root
navigation tree and choose MPLS Management > MPLS Configuration from
the shortcut menu.
(2) On the tab page that is displayed, click the MPLS Capability Configuration
tab and set the parameters.
LSR ID: 5.5.5.5 (ID of the local LSR)
Enable MPLS: selected
Enable MPLS L2VPN: selected
(3) Click Apply.
3. Configure an MPLS tunnel. For details, see 22.3.4 Configuring an MPLS
Tunnel.
navigation tree and choose MPLS Management > Tunnel Configuration from
the shortcut menu.
(2) Click the Tunnel Configuration tab. In the information list, right-click and
choose Create from the shortcut menu. In the dialog box that is displayed, set
the parameters.
Tunnel Name: Tunnel10
Tunnel ID: 10
Encap. Protocol: MPLS TE
Destination: 20.20.20.20 (LSR ID of the egress node in the LSP)
(3) Click OK.
(1) Choose Route from the navigation tree.
IP Address: 20.20.20.20 (IP address of the TOPA card on the OLT)
(4) Click OK.
5. Configure a PW profile. For details, see 22.3.6 Configuring a PW Profile.
Services (MA5612)
Issue 03 (2010-11-19)
navigation tree and choose MPLS Management > PW Template
Configuration from the shortcut menu.
(2) On the tab page that is displayed, right-click and choose Create from the shortcut
menu.
Name: pwt
Control Word: control-word
Tunnel Policy: Tunnel10
Peer IP Address: 20.20.20.20 (IP address of the TOPA card on the peer
device)
Rtp Header Enable: selected
PW Type: TDM Satop
Load Time: 125
(4) Click OK.
6. Configure the PWE3. For details, see 22.3.8 Configuring the PWE3 and 22.3.7
Adding a TDM VCL.
(1) Choose PW Management from the navigation tree.
PW ID: 1
Name: pw1
PW Type: TDM
PW Profile: pwt
Port Type: UDT
Port: 0/3/0
Signal Protocol: udp
DST UDP: 50050
In the Please Select AC:TDM VCL area, right-click and choose Add from
the shortcut menu. In the dialog box that is displayed, set the parameters.
ID: 10
Connection Type: SAToP
(4) Click OK.
----End
22.5.3 Configuring the TDMoGEM Private Line Access Service
(Based on the SDH Network)
Services (MA5612)
22-39
Example Network
If you need to configure clock synchronization of the entire network, see 22.4.1 Configuring
E1/STM-1 Line Clock Synchronization.
Figure 22-2 Configuring the TDMoGEM private line access service (based on the SDH network)

NOTE
The MA5612 receives the TDM service data of the 2G or 3G BTS through an E1 port and then transmits
the data upstream to the GPON service card on the OLT in TDMoGEM mode. The OLT terminates the
emulated data and restores TDM signals, and then transmits the signals to the SDH network through the
E1 port provided by the NH1A daughter card on the TOPA card. In this way, the 2G or 3G mobile bearer
service is implemented between the MA5612 and the OLT in TDMoGEM mode.
Procedure
a VLAN.
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
Services (MA5612)
Issue 03 (2010-11-19)
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Services (MA5612)
22-41
Priority: 2
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
displayed)
Manager VLAN: 8
Services (MA5612)
Issue 03 (2010-11-19)
(6) Click OK.
and MDU.
the shortcut menu.
GPON UNI ports.
Services (MA5612)
22-43
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the TDMoGEM private line access service on the OLT.
1. Configure a TDM E1 connection. For details, see 21.2.4 Configuring a TDM
Connection.
(1) Choose Connection > Native TDM Connection from the navigation tree.
Network Interface Type: E1
E1 Port: Frame: 00, Slot: 06, and Port: 00 are selected
GPON Port: Frame: 00, Slot: 02, Port: 00, ONT: 01, GEM Port: 01, and
E1 Port: 00 are selected
Services (MA5612)
Issue 03 (2010-11-19)
(4) Click OK.
----End
22.5.4 Configuring the TDMoGEM-to-TDM PWE3 Conversion
Private Line Access Service (Based on the MPLS Network)
Example Network
If you need to configure Ethernet clock synchronization of the entire network, see 22.4.2
Configuring Ethernet Clock Synchronization.
If you need to configure BITS clock synchronization of the entire network, see 22.4.3
Configuring BITS Clock Synchronization.
If you need to configure IEEE 1588v2 clock synchronization of the entire network, see 22.4.4
Configuring IEEE 1588v2 Clock Synchronization.
Figure 22-3 Configuring the TDMoGEM-to-TDM PWE3 conversion private line access service
(based on the MPLS network)

NOTE
The MA5612 receives the TDM service data from the 2G/3G BTS through an E1 port, encapsulates the
TDM service packets into GEM frames in TDMoGEM mode, and then sends them to the OLT. The OLT
restores the TDM signals, starts the TDM PWE3, and then sends the TDM signals to the MPLS network
and peer PTN NE through a GE port. Finally, the PTN NE terminates the emulation data and restores the
TDM signals.
Procedure
a VLAN.
Services (MA5612)
22-45
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
Services (MA5612)
Issue 03 (2010-11-19)
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Priority: 2
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Services (MA5612)
22-47
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Services (MA5612)
Issue 03 (2010-11-19)
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the TDMoGEM-to-TDM PWE3 conversion private line access service on
the OLT.
Services (MA5612)
22-49
VLAN.
VLAN ID: 500
Type: Smart VLAN
port of the VLAN.
(5) Click Finish.
Port.
lower pane.
Name: tdmpwe3
VLAN ID: 500
User VLAN: 500
(4) Click OK.
Parameters.
Next.
Services (MA5612)
Issue 03 (2010-11-19)
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click Finish.
the shortcut menu.
VLAN ID: 500
Type: Smart VLAN
(4) Click Next.
IP Mask: 255.255.255.0
the VLAN.
(5) Click Done.
Capability.
the shortcut menu.
(2) In the window that is displayed, click the MPLS Capability Configuration tab
and set the parameters.
(3) Click Apply.
Services (MA5612)
22-51
navigation tree and choose MPLS Management > MPLS TE Configuration
(5) On the MPLS TE Capability Configuration tab page, set the parameters.
Enable MPLS TE: selected
Enable CSPF: selected
Enable RSVP-TE: selected
(6) Click Apply.
Tunnel.
the shortcut menu.
the parameters.
On the Basic tab page, set the parameters as follows:
Tunnel ID: 10
Destination: 30.30.30.30 (The destination address of the tunnel is the sink
LSR ID of the tunnel. If there are no other LSRs between the MA5612 and
the PTN NE, the destination address is the LSR ID of the PTN NE.)
Signal Protocol: RSVP TE
On the Application tab page, select Reserved for binding.
(3) Click OK.
menu.
Name: pwt
Control Word: control-word
Peer IP Address: 30.30.30.30 (LSR ID of the PTN NE)
Rtp Header Enable: selected
PW Type: Tdm Satop
Load Time: 125
(4) Click OK.
Adding a TDM VCL.
Services (MA5612)
Issue 03 (2010-11-19)
PW ID: 1
Name: pw1
PW Type: TDM
PW Profile: pwt
Port Type: GPON
Port: 0/2/0
Deployment Status: Deploy
Signal Protocol: static
In Label: 8848
Out Label: 8849
In the Please Select AC:TDM Connection area, right-click and choose
Add from the shortcut menu. In the dialog box that is displayed, set the
parameters.
ID: 1
CSPA Board: Frame: 00 and Slot: 06 are selected
GPON Port: Frame: 00, Slot: 02, Port: 00, ONT: 01, and GEM Port:
01 are selected
(4) Click OK.
----End
22.5.5 Configuring the ETH PWE3 Private Line Access Service
(BIS) through an Ethernet port to carry Ethernet services over an xPON network. This topic
considers a GPON network as an example.
Example Network
If you need to configure Ethernet clock synchronization of the entire network, see 22.4.2
Configuring Ethernet Clock Synchronization.
If you need to configure BITS clock synchronization of the entire network, see 22.4.3
Configuring BITS Clock Synchronization.
If you need to configure IEEE 1588v2 clock synchronization of the entire network, see 22.4.4
Configuring IEEE 1588v2 Clock Synchronization.
Services (MA5612)
22-53
Figure 22-4 Configuring the ETH PWE3 private line access service

NOTE
The MA5612 receives the Ethernet service data from the 3G BTS through an Ethernet port, encapsulates
the Ethernet service packets into GEM frames, and then sends them to the OLT through a GPON upstream
port. The OLT restores the Ethernet signals, starts the ETH PWE3, and then sends the Ethernet signals to
the MPLS network and peer PTN NE through an Ethernet port. Finally, the PTN NE terminates the
emulation data and restores the Ethernet signals.
Procedure
a VLAN.
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
the main menu.
Services (MA5612)
Issue 03 (2010-11-19)
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Priority: 2
(5) Click OK.
Services (MA5612)
22-55
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
displayed)
Manager VLAN: 8
Services (MA5612)
Issue 03 (2010-11-19)
(6) Click OK.
and MDU.
the shortcut menu.
GPON UNI ports.
Services (MA5612)
22-57
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the ETH PWE3 private line access service on the OLT.
VLAN.
VLAN ID: 500
Type: Smart VLAN
port of the VLAN.
Services (MA5612)
Issue 03 (2010-11-19)
(5) Click Finish.
Port.
lower pane.
Name: tdmpwe3
VLAN ID: 500
User VLAN: 500
(4) Click OK.
Parameters.
Next.
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
Services (MA5612)
22-59
(6) Click Finish.
the shortcut menu.
VLAN ID: 500
Type: Smart VLAN
(4) Click Next.
IP Mask: 255.255.255.0
the VLAN.
(5) Click Done.
Capability.
the shortcut menu.
(2) In the window that is displayed, click the MPLS Capability Configuration tab
and set the parameters.
(3) Click Apply.
navigation tree and choose MPLS Management > MPLS TE Configuration
(5) On the MPLS TE Capability Configuration tab page, set the parameters.
Enable MPLS TE: selected
Enable CSPF: selected
Enable RSVP-TE: selected
(6) Click Apply.
Tunnel.
Services (MA5612)
Issue 03 (2010-11-19)
the shortcut menu.
the parameters.
On the Basic tab page, set the parameters as follows:
Tunnel ID: 10
Destination: 30.30.30.30 (The destination address of the tunnel is the sink
LSR ID of the tunnel. If there are no other LSRs between the MA5612 and
the PTN NE, the destination address is the LSR ID of the PTN NE.)
Signal Protocol: RSVP TE
On the Application tab page, select Reserved for binding.
(3) Click OK.
menu.
Name: pwt
Peer IP Address: 30.30.30.30 (LSR ID of the PTN NE)
PW Type: Ethernet Tagged
(4) Click OK.
Adding a TDM VCL.
PW ID: 1
Name: pw1
PW Type: ETH
PW Profile: pwt
Deployment Status: Deploy
Signal Protocol: static
In Label: 8848
Out Label: 8849
Please Select AC:VLAN: VLAN 500 selected
Services (MA5612)
22-61
(4) Click OK.
l Configure the ETH PWE3 private line access service on the ONU.
1. Add an Ethernet access service VLAN. For details, see 19.3.1 Configuring a
VLAN.
VLAN ID: 800
Type: Smart VLAN
(4) Click Finish.
2. Add a service virtual port on the ONU. For details, see 19.2.3 Adding a Service
Port.
lower pane.
Name: FTTM
Connection Type: LAN-ETHER
VLAN Choice: Smart VLAN
User VLAN: 20
Upstream Traffic Name/Downstream Traffic Name: ip-traffic-table_6
(4) Click OK.
----End
22.5.6 Configuring the QinQ Private-Line Private Line Access
Service
In this configuration example, the MA5612 is connected to an IP base transceiver station (BIS)
through an FE or a GE port and the OLT transmits QinQ private line services to Metro equipment
to implement the private line access service. This topic considers a GPON network as an
example.
Example Network
Services (MA5612)
Issue 03 (2010-11-19)
Figure 22-5 Configuring the QinQ private-line private line access service

NOTE
The MA5612 receives the Ethernet service data from the 3G BTS through an FE or a GE port, encapsulates
the Ethernet service packets into GEM frames, and then sends them to the OLT through a GPON upstream
port. The OLT restores the Ethernet signals and configures the QinQ VLAN encapsulation mode so that
the BTS data can be transparently transmitted to the peer PTN NE through the public network. Finally, the
PTN NE restores the original Ethernet signals.
Procedure
a VLAN.
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
the main menu.
Services (MA5612)
22-63
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Priority: 2
(5) Click OK.
Services (MA5612)
Issue 03 (2010-11-19)
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
displayed)
Manager VLAN: 8
Services (MA5612)
22-65
(6) Click OK.
and MDU.
the shortcut menu.
GPON UNI ports.
Services (MA5612)
Issue 03 (2010-11-19)
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the QinQ private-line private line access service on the OLT.
VLAN.
VLAN ID: 500
Type: Smart VLAN
port of the VLAN.
Services (MA5612)
22-67
(5) Click Finish.
Port.
lower pane.
Name: tdmpwe3
VLAN ID: 500
User VLAN: 500
(4) Click OK.
l Configure the QinQ private-line private line access service on the ONU.
1. Add a service VLAN. For details, see 19.3.1 Configuring a VLAN.
NOTE
l If the MA5612 transparently transmits BTS data, the service VLAN is the same as the
VLAN of the BTS.
l If the MA5612 adds a VLAN tag to BTS data, the service VLAN is different from the
VLAN of the BTS.
l The service VLAN of the MA5612 must be the same as the user-side VLAN on the OLT.
VLAN ID: 800
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Finish.
Port.
lower pane.
Name: FTTM
Services (MA5612)
Issue 03 (2010-11-19)
User VLAN: 20
VLAN Choice: Transparent VLAN (BTS packets received by the Ethernet
port are transparently transmitted to the OLT)
Upstream Traffic Name/Downstream Traffic Name: ip-traffic-table_4
(4) Click OK.
----End
22.5.7 Data Plan for xPON FTTO Services
This topic provides the data plan for the configuration examples of xPON FTTO services. You
can configure the services according to the data plan.
Data Plan
Table 22-3 xPON FTTO services - device management
Service
Type
Device
managemen
t
Upstream port of an
OLT
0/19/0 -
Management
VLAN
l VLAN ID: 4000
l Type: Smart VLAN
-
MDU l Name: MDU
l ONU Type: MDU
l ONU ID: 0
l SN: 32303131B39FD641
l IP Address: 192.168.50.2
l IP Address Mask:
255.255.255.0
-
l T-CONT type: Fixed
Bandwidth
Yes
-
Services (MA5612)
22-69
Service
Type
l SNMP Version: v1
l Read Name: public
l Trap Host IP: 192.168.50.3
public
-
l T-CONT Index: 1
l DBA Profile: FTTx
l Priority Queue: 1
l VLAN ID: 4000, 500
-
(based on the
management
VLAN)
l VLAN ID: 4000
0/2/1/0/0
Service VLAN
l User VLAN: 4000
-

Table 22-4 GPON FTTO services - router access service of an enterprise
Service
Type
Data of an
OLT
l Type: Smart VLAN
l Attribute: QinQ
-
Services (MA5612)
Issue 03 (2010-11-19)
Service
Type
Service Port l Name: intranet
GPON
l VLAN ID: 500
0/2/1/0/0
Service VLAN
l User VLAN: 500
same: selected
table_6
-
Queue scheduling
mode
WRR
l Queue0-weight: 10
l Queue1-weight: 10
l Queue2-weight: 20
l Queue3-weight: 20
l Queue4-weight: 40
-
Data of the
MA5612
GPON upstream
port
0/0/0 -
VLAN service
profile
l Name: FTTx
selected
-
l Type: Smart VLAN
l Attribute: QinQ
-
Services (MA5612)
22-71
Service
Type
Service Port l Name: intranet1
ETHER
l VLAN ID: 500
Service VLAN
l User VLAN: 50
same: selected
table_6
l Name: intranet2
ETHER
l VLAN ID: 500
Service VLAN
l User VLAN: 60
same: selected
table_6
-

In this configuration example, the MA5612 is connected to the TDM PBX of an enterprise
through an E1 port and the OLT transmits signals upstream to the SDH or PSN network.
Example Network
Services (MA5612)
Issue 03 (2010-11-19)
NOTE
The MA5612 is connected to the TDM PBX of the enterprise through an E1 port and then is connected to
the OLT through a GPON upstream port. The OLT provides E1 or STM-1 ports to transmit the TDM
service to the SDH or PSN network.
The TDM PBX access service can be transmitted upstream to the SDH or PSN network. In these two
networking scenarios, service configurations are different.

Procedure
l The MA5612 is connected to the PBX and the OLT transmits the service upstream to the
SDH network through an E1 or STM-1 port. For details about the configuration, see 22.5.2
Configuring the TDM PWE3 Private Line Access Service (Based on the SDH
Network).
----End
22.5.9 Configuring the IP PBX Access Service
In this configuration example, the MA5612 is connected to the IP PBX of an enterprise through
an FE or a GE port and the OLT transmits signals upstream to the PSN network.
Example Network
Figure 22-7 Configuring the IP PBX access service
NOTE
The MA5612 is connected to the IP PBX of the enterprise through an FE or a GE port and then connected
to the OLT through a GPON upstream port. The OLT transmits signals upstream to the IP or MPLS network.
The IP PBX access service can be transmitted upstream to the IP or MPLS network. In these two networking
scenarios, service configurations are different.
IP PBX is an IP network-based company telephone system. It can integrate voice communication into the
data network of a company, thereby setting up an integrated voice and data network that connects all offices
and employees in different areas in the world. For example, the SoftCo series IP voice integrated switch
of Huawei can function as a mini NGN system and an IP PBX.

Procedure
l The MA5612 is connected to the IP PBX and the OLT transmits data transparently to the
IP network through a QinQ VLAN. For details about the configuration, see 22.5.10
Configuring the Router Access Service of an Enterprise.
Services (MA5612)
22-73
l The MA5612 is connected to the IP PBX and the OLT transmits data transparently to the
MPLS network through the ETH PWE3. For details about the configuration, see 22.5.5
Configuring the ETH PWE3 Private Line Access Service.
----End
22.5.10 Configuring the Router Access Service of an Enterprise
In this configuration example, the MA5612 is connected to the router or Layer 3 switch of an
enterprise through an FE or a GE port and the OLT transmits signals upstream to the IP network.
Context
For details of the data plan, see 22.5.7 Data Plan for xPON FTTO Services.
Example Network
Figure 22-8 Configuring the router access service of an enterprise
NOTE
The data on the enterprise intranet is transmitted to the MA5612 through a Layer 3 switch or router of the
enterprise. Therefore, configure the QinQ VLAN private lines on both MA5612_1 and MA5612_2. Then,
the service data and BPDU packets between enterprise intranets can be transmitted transparently over the
public network. This provides a transparent and secure data channel for the enterprise intranets in different
areas.

Procedure
a VLAN.
Services (MA5612)
Issue 03 (2010-11-19)
the shortcut menu.
VLAN ID: 4000
Type: Smart VLAN
(5) Click Next.
the VLAN.
(6) Click Finish.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
parameters.
T-CONT Index: 1
DBA Profile: FTTx
Services (MA5612)
22-75
GEM Port Index: 1
Priority Queue: 1
the parameters.
Priority: 1
the parameters.
Priority: 2
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Services (MA5612)
Issue 03 (2010-11-19)
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
Services (MA5612)
22-77
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
l Configure the router access service of the enterprise on the OLT.
VLAN.
Services (MA5612)
Issue 03 (2010-11-19)
VLAN ID: 500
Type: Smart VLAN
Attribute: QinQ
port of the VLAN.
(5) Click Finish.
Port.
lower pane.
Name: intranet
User VLAN: 500 (service VLAN ID of the ONU)
Upstream Traffic Name/Downstream Traffic Name: ip-traffic-table_6 (The
OLT does not restrict the rate of service streams in the management VLAN.
Therefore, it is recommended that you use the default profile ip-traffic-
table_6.)
(4) Click OK.
Parameters.
Next.
Services (MA5612)
22-79
Queue0-weight: 10
Queue1-weight: 10
Queue2-weight: 20
Queue3-weight: 20
Queue4-weight: 40
(6) Click Finish.
the shortcut menu.
l Configure the router access service of the enterprise on the ONU.
This section considers MA5612_1 as an example to describe how to configure the router
access service of the enterprise on the ONU. The configuration process on MA5612_2 is
similar to the configuration process on MA5612_1.
1. Configure a VLAN service profile. For details, see 21.2.2 Configuring a VLAN
Service Profile.
(1) Choose Configuration > Access Profile Management > VLAN Service
Set Name to FTTx.
Enable BPDU Tunnel: selected
(4) Click OK.
the shortcut menu.
2. Configure a service VLAN on the ONU. For details, see 19.1.5 Configuring a
VLAN.
VLAN ID: 500
Type: Smart VLAN
Attribute: QinQ
Services (MA5612)
Issue 03 (2010-11-19)
(4) Click Next.
the VLAN.
Click the Extended Info tab and select the VLAN service profile named
FTTx.
(5) Click Finish.
Port.
lower pane.
Name: intranet1
Interface Selection: 0/4/0 (GE port through which the router or Layer 3 switch
of enterprise A is connected to the MA5612)
User VLAN: 50 (VLAN tag carried in the packets on the intranet of enterprise
A)
table_6.)
(4) Click OK.
(5) Repeat the preceding operations to add another service virtual port.
Name: intranet2
Interface Selection: 0/4/1 (GE port through which the router or Layer 3 switch
of enterprise B is connected to the MA5612)
User VLAN: 60 (VLAN tag carried in the packets on the intranet of enterprise
B)
table_6.)
----End
Services (MA5612)
22-81
Result
The communications between intranets in two different areas are successful, implementing
various services between the intranets.
Services (MA5612)
Issue 03 (2010-11-19)
23 Configuring the EPON FTTB Services
About This Chapter
An FTTB network consisting of an OLT and a number of MDUs provides users with Internet,
After an MDU is added successfully, you can configure FTTB services for the MDU on the
U2000.
23.4 Configuration Examples of the EPON FTTB Services
services in an EPON FTTB network.
Operation Guide for ONU NE Management 23 Configuring the EPON FTTB Services
23-1
After an MDU is added successfully, you can configure FTTB services for the MDU on the
U2000.
Context
After an MDU is added on the NE side, it supports online confirmation and offline deployment.
The information about the profile bound to an MDU and the authentication information on the
U2000 must be the same as those configured for the actual MDU on the user side.
l Online confirmation: If you add an MDU after the MDU is powered on, it goes online
immediately. This topic considers MDU online confirmation as an example.
l Offline deployment: If an MDU is not online, you need to add it offline and configure
services for the MDU. After the MDU goes online, the configuration is applied to the MDU
through the optical network termination management and control interface (OMCI). Then,
service configuration for the MDU is complete.
An EPON DBA profile contains the traffic parameters of LLID. DBA is used to control the
upstream bandwidth of ONU services. A DBA profile is bound with an LLID, and different
bandwidth assurance types are provided based on different LLID plans. After an EPON DBA
profile is configured and bound with an LLID, the system controls the traffic of the LLID
according to the traffic parameters contained in the DBA profile. This provides flexible schemes
for dynamic bandwidth allocation and improves the usage of upstream bandwidth.
23.1.3 Configuring a Line Profile
An EPON line profile contains the parameters relevant to the EPON line. The parameters are
required for setting up channels for the EPON line.
This topic describes how to confirm an automatically discovered ONU connected to an EPON
port. Only after the ONU is confirmed, it can work in the normal state.
After an ONU is successfully added, the control channel is already set up but the data channel
is not set up. In this case, you need to add a service virtual port on the OLT to manage ONU
data.
23.1.7 Verifying the Interoperability Between an OLT and an MDU
After configuring the relevant parameters on the U2000, you need to verify whether an ONU
can be managed and maintained on the U2000.
Issue 03 (2010-11-19)
Context
You can configure the SNMP parameter profile of the MDU on the U2000, and configure the
information about an MDU management channel to the OLT. Then, the OLT manages the MDU
through the SNMP mode so that the remote deployment and maintenance for the MDU can be
implemented.
Procedure
1 Choose Configuration > Access Profile Management > MDU SNMP Profile from the main
menu.
Key
Parameter
Description
SNMP
Version
Ensure that the SNMP version of the U2000 server is the same as the
corresponding SNMP version configured on the device.
Generally, the SNMP Version of the U2000 server is set to v1.
Trap Host
IP
Specifies the IP address of the destination device for traps. The trap packets of
the device are sent to the U2000 server that maps the IP address.
NOTE
Generally, the IP address of the U2000 server is set to the IP address of the destination
device for traps.
Trap UDP
Port
Specifies the ID of the UDP port that is used to receive the traps that the device
reports to the U2000.

4 Click OK.
23-3
menu.
NOTE
The MDU SNMP profile that is generated by the U2000 can be referenced by the OLT only after the profile is
applied to the corresponding OLT.
----End
Command Reference
Add an
MDU
SNMP
managemen
t profile
snmp-profile add Global config mode

An EPON DBA profile contains the traffic parameters of LLID. DBA is used to control the
upstream bandwidth of ONU services. A DBA profile is bound with an LLID, and different
bandwidth assurance types are provided based on different LLID plans. After an EPON DBA
profile is configured and bound with an LLID, the system controls the traffic of the LLID
according to the traffic parameters contained in the DBA profile. This provides flexible schemes
for dynamic bandwidth allocation and improves the usage of upstream bandwidth.
Context
The EPON DBA profile added through the U2000 exists only in the database of the U2000, but
is not applied to the device. The EPON DBA profile can be created on the device only when the
EPON DBA profile is bound with an LLID.
NOTE
l The EPON DBA profiles with Name ranging from dba-profile_1 to dba-profile_9 are default profiles
of the system. These profiles provide typical traffic parameters. You can query the default EPON DBA
profiles but cannot modify or delete them.
l Usually, the services with higher priority use fixed bandwidth or assured bandwidth but the services
with lower priority use maximum bandwidth or a combination of bandwidth assurance types.
Procedure
1 Choose Configuration > Access Profile Management > EPON Profile from the main menu.
2 Click the DBA Profile tab. Right-click and choose Add Global Profile from the shortcut menu.
Issue 03 (2010-11-19)
Name Indicates the name of the EPON DBA profile. It uniquely
identifies an EPON DBA profile and cannot be the same as an
existing profile name.
DBA type Indicates the type of the EPON DBA profile. EPON DBA profiles
are classified according to the bandwidth requirement of the
services distinguished by LLIDs. You can configure bandwidth
for different LLID types to control the traffic based on LLIDs.
Fixed bandwidth rate
Assured bandwidth rate
Maximum bandwidth
rate
Usually, the services with higher priority use fixed bandwidth or
assured bandwidth but the services with lower priority use
maximum bandwidth. VoIP services have the highest priority.

4 Click OK.
----End
Command Reference
Query DBA profiles
in the system
display DBA-profile Privilege mode
Add a DBA profile DBA-profile add Global config mode

23-5
Prerequisite
a DBA Profile.
Procedure
2 Click the EPON Line Profile tab. Right-click and choose Add Global Profile from the shortcut
menu.
3 In the dialog box that is displayed, set Name and relevant parameters of the line profile.
1. Choose Base Info. from the navigation tree and configure the basic parameters of the
profile.
Key
Paramete
r
Description
FEC
Switch
Indicates the status of upstream forward error correction (FEC) switch of
the ONU line profile. To ensure the reliability of data transmission
between the OLT and ONU, enable the FEC function. After the FEC
function is enabled, the system inserts redundancy data into normal
packets. In this way, the line has the error tolerance function, but certain
bandwidth resources are wasted.

2. Choose DBA Threshold from the navigation tree and set the relevant parameters.
Issue 03 (2010-11-19)
4 Click OK.
5 In the information list, right-click a record and choose Download to NE from the shortcut menu.
6 In the dialog box that is displayed, select the required OLT, and click OK.
----End
Command Reference
Enter the ONU line profile mode ONU-lineprofile EPON Global config mode

This topic describes how to confirm an automatically discovered ONU connected to an EPON
port. Only after the ONU is confirmed, it can work in the normal state.
Prerequisite
The Line profile must be already configured in the system. For details, see 23.1.3 Configuring
a Line Profile.
The MDU SNMP profile must be already configured in the system. For details, see 23.1.1
Configuring an MDU SNMP Profile.
Context
After the function of automatically discovering an ONU is enabled, the OLT periodically detects
whether a new ONU is online. When an ONU is online, the OLT reports a group of information
about the ONU to the U2000 for confirmation.
23-7
Procedure
2 Choose EPON > EPON UNI Port from the navigation tree.
3 On the EPON UNI Port tab page, set the filter criteria or click to display the EPON UNI
ports.
4 Select the EPON UNI port for which you want to enable the function of automatically
discovering an ONU, right-click and choose Enable Auto Find ONU Switch from the shortcut
menu.
5 In the information list, select the required EPON UNI port and click the AutoFind ONU
Info. tab in the lower pane.
6 In the information list, right-click an ONT to be confirmed and choose Confirm ONU from the
shortcut menu.
7 In the dialog box that is displayed, set the basic parameters and NMS management channel
parameters of the ONU, and then click OK.
Issue 03 (2010-11-19)
ONU ID Indicates the ID that identifies an ONU. Usually, it starts from 0.
ONU Type Specifies MDUs.
Line Profile Indicates the line profile bound to the port to which the ONU belongs.
You can bind a port with the line profile. When the port is activated, it
can reference the profile. According to the upstream and downstream
line rates and the noise tolerance set in the profile, the port detects the
line distance and line status, negotiates between the local and remote
devices, and determines whether it can work under the conditions.
Service Profile Indicates the service profile bound to the ONU. A service profile
contains the parameters relevant to the ONU service.
For FTTB services, a service profile is not required.
Auth Way Indicates the mode used when the OLT authenticates an ONU. By
default, the EPON ONU uses the SN-based authentication mode.

When you add an ONU in the SNMP management mode, the management mode and line profile
are mandatory. When you add an ONU in the OAM management mode, the parameters of
management mode, line profile, and service profile are mandatory.
----End
Command Reference
Confirm an ONU in the auto-
discovery state
ont confirm EPON mode
Enter the EPON mode from the
global config mode
interface EPON Global config mode
Enable the function of auto-
discovery ONU
ont-auto-find enable EPON mode
Query the current ONUs
automatically discovered or time
for automatically discovering
ONUs from the system
display ont autofind Privilege mode, EPON
mode

23-9
Procedure
Issue 03 (2010-11-19)
VLAN.
NOTE
NOTE
NOTE
VLANs for an OLT.

6 Click Done.
----End
Command Reference
23-11

After an ONU is successfully added, the control channel is already set up but the data channel
is not set up. In this case, you need to add a service virtual port on the OLT to manage ONU
data.
Prerequisite
The management VLAN where the service virtual port belongs must be configured. The
upstream port of the VLAN must be configured. For details, see 23.1.5 Configuring a VLAN.
Procedure
2 Choose EPON > EPON ONU from the navigation tree.
3 On the EPON ONU tab page, set the filter criteria or click to display the EPON ONUs.
4 In the information list, select an EPON ONU and click the ServicePort Info. tab in the lower
pane.
5 On the ServicePort Info. tab page, right-click and choose Add from the shortcut menu.
6 In the dialog box that is displayed, set the parameters as follows.
Issue 03 (2010-11-19)
Key
Parameter
Description
User VLAN Indicates the management VLAN ID of the ONU.
Service Type Indicates the type of the services carried on the service virtual port. Usually,
the multi-service VLAN mode is selected. Each service virtual port can
carry multiple types of service streams. You need to set the user VLAN to
distinguish the service streams. The services are distinguished based on the
VLAN ID contained in the user packets. The user packets are labeled with
different upstream VLAN IDs, and the original VLAN IDs in the user
packets are removed.

7 Click OK.
----End
Command Reference
Add a service virtual port service-port Global config mode

23-13
23.1.7 Verifying the Interoperability Between an OLT and an MDU
After configuring the relevant parameters on the U2000, you need to verify whether an ONU
can be managed and maintained on the U2000.
Procedure
1 Query the status of the ONU.
1. In the Main Topology, double-click the required NE in the Physical Root navigation tree;
3. On the EPON ONU tab page, set the filter criteria or click to display the EPON ONUs.
4. In the information list, select an EPON ONU with the required shelf/slot/port and ONT ID.
If the indicator of Status is in green, it indicates that the ONU is in the activated and online
state.
2 Check whether the ONU can ping through the OLT.
1. On the Physical Root navigation tree in Main Topology, right-click the ONU and choose
Tool > Ping from the shortcut menu.
2. In the dialog box that is displayed, click Ping to view the result. If the reply information is
displayed, it indicates that the connection between the OLT and the ONU is successfully
set up.
----End
Issue 03 (2010-11-19)
Command Reference
Query the
information
about the
device
when it is
used as an
ONT
display ont info GPON mode, EPON mode

Context
Services Steps
l 23.2.1 Adding a Service Virtual Port
Port

After a service virtual port is successfully added, it can carry various types of service streams.
After a service virtual port is successfully added, it can carry various types of service streams.
23-15
Procedure
Key
Parameter
Description
VLAN ID Indicates the VLAN ID of the service virtual port. The VLAN ID uniquely
identifies a VLAN.

NOTE
You can select only the traffic profiles that exist on devices. Otherwise, the system reports an error.
5 Click OK.
----End
Issue 03 (2010-11-19)
Command Reference
Query the
802.1x
configuratio
n of a
service
virtual port
Bind a
service
virtual port
with 802.1x
authenticati
on
dot1x service-port Global config mode

Context
configured at the MDU side and the service configuration steps.
Services Steps
l 19.3.4 Configuring an ADSL Line Profile
l 19.3.5 Configuring an ADSL Alarm Profile
l 19.3.6 Configuring the Attributes of an ADSL Port
l 19.3.7 Activating an ADSL Port
Port
23-17
Services Steps
l 19.3.2 Configuring an IP Interface
l 19.3.9 Adding an MGC Profile
l 19.3.10 Configuring a UAS Profile
l 19.3.12 Adding an MG
l 19.3.13 Binding an MGC Profile
l 19.3.14 Starting an MG
l 19.3.15 Configuring a VoIP PSTN Port

This topic describes how to configure a static route to the U2000 for an ONU. When the
management mode of the ONU is SNMP, to maintain or manage an ONU, configure a static
route to the U2000 for the ONU.
This topic describes how to configure a static route to the U2000 for an ONU. When the
management mode of the ONU is SNMP, to maintain or manage an ONU, configure a static
route to the U2000 for the ONU.
Prerequisite
The management mode of the ONU must be SNMP.
Context
When the IP addresses of the VLAN interface and the MGC are in different network segments,
you need to configure a route from the MG to the MGC.
Procedure
2 Choose EPON > EPON ONU from the navigation tree.
3 On the EPON ONU tab page, set the filter criteria or click to display the EPON ONUs.
4 In the information list, select a record and click the Static Route Info. tab in the lower pane.
Right-click the information list and choose Add from the shortcut menu.
Issue 03 (2010-11-19)
Key
Parameter
Description
IP Address Indicates the destination IP address. It identifies the destination IP address
or destination network of the IP packet.
IP Address
Mask
Indicates the subnet mask of the IP address. A subnet mask consists of
consecutive 1s and can be represented in dotted decimal notation when
written in the text format. The subnet mask and the destination IP address
together identify the address of the network segment where the destination
host or router is located. To be specific, you can get the address of this
network segment by performing the logical AND operation on the destination
IP address and the subnet mask.
Next Hop IP
Address
Indicates the next hop address. It is used to identify the next router that the
IP packet passes. Latest configuration for the next hop address will
automatically overwrite the previous configuration and become the next hop
address in the current route information.

NOTE
To configure the static route, you can also perform operations on the NE Explorer of the MDU. The first
two steps are as follows:
1. In the Main Topology, double-click the required MDU in the Physical Root navigation tree; or right-
click the required MDU and choose NE Explorer from the shortcut menu.
2. Choose Static Route from the navigation tree.
The other steps are the same as the corresponding steps in the procedure for performing operations on the
NE Explorer of the OLT.
6 Click OK.
----End
Command Reference
Query static
routes to the
U2000 from
the ONT
display ont snmp-route EPON mode
Configure a
static route to
the U2000 for
the ONT
ont snmp-route Privilege mode, BTV mode,
MVLAN mode

23.4 Configuration Examples of the EPON FTTB Services
services in an EPON FTTB network.
23-19
23.4.1 Data Plan for the EPON FTTB Services
This topic provides the data plan for the configuration examples of the EPON FTTB services.
23.4.2 Configuring the EPON FTTB Internet Service (LAN Access)
to an MDU in LAN access mode and the MDU is connected to an OLT through an EPON port.
23.4.3 Configuring the EPON FTTB Internet Service (ADSL2+ Access)
to an MDU in ADSL2+ access mode and the MDU is connected to an OLT through an EPON
port.
23.4.4 Configuring the EPON FTTB Internet Service (VDSL2 Access)
to an MDU in VDSL2 access mode and the MDU is connected to an OLT through an EPON
port.
23.4.5 Configuring the EPON FTTB Multicast Service
OLT through an EPON port.
23.4.6 Configuring the EPON FTTB Voice Service (H.248 Protocol)
through an EPON port.
23.4.7 Configuring the EPON FTTB Voice Service (SIP Protocol)
23.4.8 Configuring the EPON FTTB Service by Using a Service Provisioning Profile
LAN access mode and the MDU is connected to an OLT through an EPON port.
23.4.1 Data Plan for the EPON FTTB Services
This topic provides the data plan for the configuration examples of the EPON FTTB services.
Data Plan
Table 23-1 Data plan for the EPON FTTB services
Service
Type
Device
managemen
t
Management
VLAN of an OLT
VLAN ID: 8
Type: Smart VLAN
The management
VLAN of an OLT is
the management
VLAN between the
OLT and an MDU.
OLT
0/19/0 -
Issue 03 (2010-11-19)
Service
Type
the management
VLAN of the OLT
functions as the IP
address of the OLT
for inband network
management.
EPON port of the
OLT
0/2/1 -
MDU
0/0/1 -
Service port of the
MDU
0/1/1 -
MDU l Name: MDU
l ONU ID: 0
l ONU Type: MDU
l Authentication Mode:
MAC
l MAC Address: 001E-
E3F4-0471
l IP Address: 192.168.50.2
l IP Address Mask:
255.255.255.0
To configure the
MDU on the OLT in
Telnet mode, ensure
that the management
VLANs of the OLT
and the MDU are the
same and the
management IP
addresses of the
OLT and the MDU
are in the same
network segment.
When the MDU is
connected to the
OLT through an
EPON port, the
MDU uses the
SNMP protocol as
the network
management
protocol and does
not require service
profiles.
23-21
Service
Type
l SNMP Version: v1
l Read Name: public
l Trap Host IP: 192.168.50.3
public
-
(based on the
management
VLAN)
l VLAN ID: 8
0/2/1/0/0
Service VLAN
l User VLAN: 8
FTTx
After the MDU is
added to the U2000
successfully, a
control channel has
been established but
no data channel is
established. In this
case, you need to
create a service
virtual port on the
OLT to help the
OLT manage the
MDU.
MEF IP traffic
profile
l Name: FTTx
l CIR: 20480
l Outer Priority: 1
The MEF IP traffic
OLT or MDU to
control upstream
and downstream
traffic.
l DBA type: Maximum
Bandwidth
32768
-
Line profile Name: FTTx
DBA Profile: FTTx
-
Issue 03 (2010-11-19)
Service
Type
Internet
service
l Type: Smart VLAN
l Attribute: QinQ
l In the case of the
Internet service,
users are
identified by
QinQ VLANs. A
CVLAN is
allocated to each
user on the MDU
and an SVLAN
is allocated to
each slot, port, or
OLT according
to networking
scenarios.
l Plan VLANs for
the MDUs that
are connected to
the same OLT in
a centralized
manner and
ensure that each
VLAN is unique
to an MDU.
on the OLT side
l Name: HSI
l VLAN ID: 1001
l Interface Selection: 0/2/1/0
Service VLAN
l User VLAN: 1001
same: selected
FTTx
-
on the MDU side
l Name: HSI
l Vlan ID: 1001
same: selected
FTTx
-
23-23
Service
Type
IPTV
service
l Type: Smart VLAN
-
on the OLT side
l Name: IGMP
l Vlan ID: 1000
Service VLAN
l User VLAN: 1000
same: selected
FTTx
-
Multicast VLAN on
the OLT side
l VLAN ID: 1000
-
10.10.10.20
default value)
-
selected
-
Multicast VLAN on
the MDU side
l Work Mode:
igmp_snooping
l VLAN ID: 1000
-
Issue 03 (2010-11-19)
Service
Type
on the MDU side
l Name: multicast
l Vlan ID: 1000
Service VLAN
same: selected
FTTx
-
VoIP
service
VLAN on the OLT
side
l VLAN ID: 2000
l Type: Smart VLAN
-
on the OLT side
l Name: VOIP
l Vlan ID: 2000
Service VLAN
l User VLAN: 2000
same: selected
FTTx
-
Signaling IP address
Media IP address
17.10.10.10 The H.248 and SIP
protocols support
separation of media
and signaling
streams. The media
and signaling IP
addresses can be the
same or different.
Gateway 17.10.10.1 -
23-25
Service
Type
Parameters of the
MG interface (H.
248 protocol)
NOTE
MG interface must be
the same as the
parameters on the
MGC. There are
many negotiation
248 protocol. This
table provides the
mandatory
248 protocol.
l MG ID: 0
l Name: mg1
17.10.10.10
17.10.10.10
The ID of the MG
interface used for
the VoIP service
determines the VAG
assigned to.
MGC profile l Name: mgcprofile1
l IP Address 1:
200.200.200.200
l Port Number: 2944
-
Parameters of the
SIP interface (SIP
protocol)
NOTE
SIP interface must be
the same as the
parameters on the
IMS. There are many
negotiation
protocol. This table
provides the
mandatory
protocol.
l MG ID: 0
l Name: mg1
17.10.10.10
l Signaling Port No.: 5060
17.10.10.10
l MG Domain Name:
huawei.com
l Active NMS UAS Profile:
uasprofile1
The ID of the SIP
interface used for
the VoIP service
determines the VAG
assigned to.
UAS profile l Name: uasprofile1
l Address Mode: Fix mode
l IP Address 1:
200.200.200.200
l Proxy Port: 5060
-
PSTN user Phone 1-Phone2:
83110000-83110001
-

Issue 03 (2010-11-19)
23.4.2 Configuring the EPON FTTB Internet Service (LAN Access)
to an MDU in LAN access mode and the MDU is connected to an OLT through an EPON port.
Prerequisite
Context
For details of the data plan, see 23.4.1 Data Plan for the EPON FTTB Services.
Example Network
MA5620, MA5626, MA5610, and MA5612 support LAN access. The configuration procedure
and MA5610 V800R308.
l The PC that gains access to the network by means of PPPoE dialup is connected to an FE
port on the MDU and the MDU is connected to the OLT and then to the upper layer network
through a GPON port. In this case, the high-speed Internet service is available for the PC.
l The high-speed Internet service is identified by two VLANs that are accurately bound. A
user VLAN is allocated to each user on the MDU and a service VLAN is allocated to each
slot on the OLT.
l The following two profiles are used for the high-speed Internet service:
DBA profile in which T-CONT type is set to Assured Bandwidth/Maximum
Bandwidth and Maximum Bandwidth is set to 32768Kbit/s
MEF IP traffic profile in which CIR is set to 20480Kbit/s
23-27
Figure 23-1 Configuring the EPON FTTB Internet service (LAN access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
Configuring a VLAN.
the shortcut menu.
Issue 03 (2010-11-19)
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
23-29
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
(1) Choose Configuration > Access Profile Management > EPON Profile from
the main menu.
Name: FTTx
DBA Type: Maximum Bandwidth
(5) Click OK.
the shortcut menu.
5. Configure a line profile. For details, see 23.1.3 Configuring a Line Profile.
the main menu.
Name: FTTx
DBA Profile: FTTx
23-31
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
(2) Choose EPON > EPON UNI Port from the navigation tree.
(3) On the EPON UNI Port tab page, set the filter criteria or click to display the
EPON UNI ports.
(4) In the information list, right-click EPON UNI port 0/2/1 and choose Enable ONU
Auto Find from the shortcut menu.
with the MAC address 0018-8256-3E47, and then choose Confirm ONU from
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
displayed)
Issue 03 (2010-11-19)
Manager VLAN: 8
(6) Click OK.
Service Virtual Port and 23.1.7 Verifying the Interoperability Between an OLT
and an MDU.
23-33
the shortcut menu.
(2) Choose EPON > EPON ONU from the navigation tree.
(3) On the EPON ONU tab page, set the filter criteria or click to display the
EPON ONUs.
(4) In the information list, select the record where the shelf, slot, port, and ONU IDs
are 0, 2, 1, and 0 respectively and click the ServicePort Info tab in the lower
pane.
menu.
Name: FTTx_MDU
Connection Type: LAN-EPON
VLAN ID: 8
Interface Selection: 0/2/1/0
User VLAN: 8
(7) Click OK.
Issue 03 (2010-11-19)
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
23-35
Name: HSI
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name:HSI
Vlan ID: 1001
23-37
User VLAN: untagged
(4) Click OK.
----End
Result
23.4.3 Configuring the EPON FTTB Internet Service (ADSL2+
Access)
to an MDU in ADSL2+ access mode and the MDU is connected to an OLT through an EPON
port.
Prerequisite
Context
Example Network
The MA5616 supports ADSL2+ access. The configuration procedure in this topic is applicable
to the MA5616 V800R308.
l The PC is connected to an ADSL2+ port on the MDU. The data frames from the PC are
Issue 03 (2010-11-19)
Figure 23-2 Configuring the EPON FTTB Internet service (ADSL2+ access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000
Modem

Procedure
Configuring a VLAN.
23-39
the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
23-41
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
displayed)
23-43
Manager VLAN: 8
(6) Click OK.
and an MDU.
Issue 03 (2010-11-19)
the shortcut menu.
EPON ONUs.
pane.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
23-45
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Issue 03 (2010-11-19)
Name: HSI
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
23-47
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name:HSI
Vlan ID: 1001
Issue 03 (2010-11-19)
User VLAN: untagged
(4) Click OK.
3. Configure an ADSL line profile. For details, see 19.3.4 Configuring an ADSL
Line Profile.
the main menu.
(2) Click the ADSL Line Profile tab, and select the required device type from the
Name: adsl_profile
(5) Click OK.
the shortcut menu.
(7) In the dialog box that is displayed, select the required NE and click OK.
4. Configure the attributes of an ADSL port and activate the ADSL port. For
details, see 19.3.6 Configuring the Attributes of an ADSL Port and 19.3.7
Activating an ADSL Port.
(2) On the ADSL tab page, enter the filter criteria or click to display the required
ADSL ports.
23-49
Line Profile: adsl_profile
(5) Click OK.
shortcut menu.
----End
Result
23.4.4 Configuring the EPON FTTB Internet Service (VDSL2
Access)
to an MDU in VDSL2 access mode and the MDU is connected to an OLT through an EPON
port.
Prerequisite
Context
Example Network
The MA5616 and MA5652 support VDSL2 access. The configuration procedure in this topic is
applicable to the MA5616 V800R308 and MA5652 V800R308.
l The PC is connected to a VDSL2 port on the MDU. The data frames from the PC are
Issue 03 (2010-11-19)
Figure 23-3 Configuring the EPON FTTB Internet service (VDSL2 access)
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000
Modem

Procedure
Configuring a VLAN.
the shortcut menu.
23-51
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
23-53
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
displayed)
23-55
Manager VLAN: 8
(6) Click OK.
and an MDU.
Issue 03 (2010-11-19)
the shortcut menu.
EPON ONUs.
pane.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
23-57
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Issue 03 (2010-11-19)
Name: HSI
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
23-59
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name:HSI
Vlan ID: 1001
Issue 03 (2010-11-19)
User VLAN: untagged
(4) Click OK.
3. Configure a VDSL2 line profile.
The VDSL2 line profile needs to be bound to a line configuration profile and channel
configuration profile, and the line configuration profile needs to be bound to a line
the main menu.
(3) Click the Line Spectrum Configuration Profile tab, and select the required
device type from the Device Type drop-down list.
Name: vdsl_profile1
(6) Click OK.
(7) Click the Line Configuration Profile tab, and select the required device type
from the Device Type drop-down list.
Name: vdsl_profile2
Transmission Mode: G.992.5 POTS overlapped, G.992.5 Annex I All-Digital
overlapped
Line Spectrum Configuration Profile: vdsl_profile1
23-61
(10) Click Finish.
the shortcut menu.
(13) Click the Channel Configuration Profile tab, and select the required device
type from the Device Type drop-down list.
Name: vdsl_profile3
(16) Click OK.
the shortcut menu.
(19) Click the Line Template tab, and select the required device type from the Device
Name: vdsl_profile
Line Configuration Profile: vdsl_profile2
Channel1 Configuration Profile: vdsl_profile3
(22) Click OK.
the shortcut menu.
4. Configure the attributes of a VDSL2 port and activate the VDSL2 port.
(2) On the VDSL2 tab page, enter the filter criteria or click to display the required
VDSL2 ports.
Line Profile: vdsl_profile
(5) Click OK.
shortcut menu.
----End
Issue 03 (2010-11-19)
Result
23.4.5 Configuring the EPON FTTB Multicast Service
Prerequisite
l The licenses of multicast programs or users must have been applied for and installed.
Context
Example Network
l The STB is connected to port 0/0/1 on the MDU, and data frames are transmitted through
an upstream port of the MDU to the OLT. The OLT transmits the data frames to separate
service channels according to user-side VLANs, switches VLAN tags (that is, switches
user-side VLANs to upstream VLANs), and then transmits the data frames through an
upstream port.
l The OLT uses IGMP proxy, and the MDU uses IGMP snooping. IGMP proxy and IGMP
snooping are Layer 2 multicast protocols.
l Multicast logs are reported to the log server as CDR files.
23-63
Figure 23-4 Configuring the EPON FTTB multicast service
OLT
MDU
Multicast Source
LAN Switch
Optical splitter
U2000
STB
TV
BRAS

Procedure
Configuring a VLAN.
Issue 03 (2010-11-19)
the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
23-65
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
23-67
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
displayed)
Issue 03 (2010-11-19)
Manager VLAN: 8
(6) Click OK.
and an MDU.
23-69
the shortcut menu.
EPON ONUs.
pane.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
Issue 03 (2010-11-19)
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
VLAN ID: 1000
Type: Smart VLAN
23-71
(5) Click Done.
Service Port.
Name:IGMP
Vlan ID: 1000
User VLAN: 1000
of service streams)
Issue 03 (2010-11-19)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
23-73
(5) Click Finish.
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
Issue 03 (2010-11-19)
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
(5) Click OK.
23-75
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
(4) Click Finish.
Issue 03 (2010-11-19)
l Configure the multicast service on the MDU side.
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
VLAN ID: 1000
Type: Smart VLAN
23-77
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
NOTE
If the access port of MDU is xDSL port, ensure that the xDSL port is activated.
Name: IGMP
Vlan ID: 1000
Issue 03 (2010-11-19)
User VLAN: untagged
(4) Click OK.
4. Add a multicast VLAN on the MDU side. For details, see 19.2.7 Configuring the
Multicast VLAN.
Work Mode: igmp_snooping
VLAN ID: 1000
23-79
(4) Click Done.
5. Add a virtual upstream port for the multicast service on the MDU side. For
details, see 19.2.5 Configuring the Virtual Multicast Upstream Port.
multicast VLANs.
VLAN ID: 1000
Frame: 0
Slot: 0
Port: 1
(5) Click OK.
6. Configure a program profile on the MDU side. For details, see 19.2.8 Configuring
a Program Profile.
Issue 03 (2010-11-19)
the main menu.
(3) Right-click the program profile whose IP Address is set to 224.0.1.1 and choose
Download to NE from the shortcut menu.
(4) In the dialog box that is displayed, select the required MDU and click Next. Then,
(5) Click OK.
7. Configure a multicast user on the MDU side. For details, see 19.2.10 Configuring
a Multicast User.
Alias: IGMPUserA
(4) Click Finish.
23-81
----End
Result
23.4.6 Configuring the EPON FTTB Voice Service (H.248 Protocol)
Prerequisite
l The data of the MGC interface and PSTN user corresponding to the MG interface must be
configured on the MGC.
Context
H.248 is the Media Gateway Control Protocol. In the MG separation architecture, H.248 is the
communication protocol between an MGC and an MG, and it is used for the MGC to control
the MG.
The MDU functions as an MG and the SoftX3000 functions as an MGC if the softswitch that
matches the MDU is SoftX3000.
Example Network
MA5620, MA5626, MA5616, and MA5612 support H.248 Protocol. The configuration
procedure in this topic is applicable to the MA5620 V800R308, MA5626 V800R308, MA5612
V800R308, and MA5616 V800R308.
The MDU is connected to an EPON port on the OLT, and phone 1 and phone 2 are connected
to voice service ports on the MDU.
Issue 03 (2010-11-19)
Figure 23-5 Configuring the EPON FTTB voice service (H.248 protocol)
SoftX 3000
OLT
MDU
Phone2
Phone1
LAN Switch
U2000

Procedure
Configuring a VLAN.
the shortcut menu.
VLAN ID: 8
23-83
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
23-85
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
displayed)
23-87
Manager VLAN: 8
(6) Click OK.
and an MDU.
Issue 03 (2010-11-19)
the shortcut menu.
EPON ONUs.
pane.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
23-89
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Issue 03 (2010-11-19)
Name: VOIP
Vlan ID: 2000
User VLAN: 2000
(4) Click OK.
1. Add an MGC profile. For details, see 19.3.9 Adding an MGC Profile.
(1) Choose Configuration > Access Profile Management > MGC Profile from
the main menu.
Name: mgcprofile1
Protocol Type: H.248
IP Address 1: 200.200.200.200 (IP address of the MGC)
Port Number: 2944
23-91
(4) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
port of the VLAN.
Issue 03 (2010-11-19)
IP Address: 17.10.10.10
(5) Click Done.
Interface.
IP Address: 17.10.10.10
IP Type: Media
Gateway: 17.10.10.1
23-93
(4) Click OK.
Target Mask: 255.255.255.0
(4) Click OK.
5. Configure the MG. For details, see 19.3.12 Adding an MG, 19.3.13 Binding an
MGC Profile, and 19.3.14 Starting an MG.
MGs.
MG ID: 0
Name: mg1
Issue 03 (2010-11-19)
(5) Click OK.
(6) In the information list, select the record where MG ID is set to 0, and click the
MGC Attribute Info tab in the lower pane. In the list, right-click the record
where MGC Index is set to 0 and choose Bind Profile from the shortcut menu.
(7) In the dialog box that is displayed, set NMS MGC Profile to mgcprofile1 and
click OK.
(8) In the information list, right-click the record where MG ID is set to 0 and choose
Cold Start from the shortcut menu.
(9) In the dialog box that is displayed, click Yes.
VoIP PSTN ports.
23-95
MG ID 0 -
Terminal ID 0 1

(5) Click OK.
----End
Result
23.4.7 Configuring the EPON FTTB Voice Service (SIP Protocol)
Prerequisite
l The PSTN user data corresponding to the SIP interface must be configured on the IMS.
Context
The IMS is an IP-based subsystem for controlling multimedia sessions on the NGN. The IMS
includes all the core network elements that control multimedia services such as audio, video,
text, and instant message services.
The SIP protocol is a control-layer protocol of the IMS and it is one of the framework protocols
designed by the IETF for the multimedia communication system. The SIP protocol is also an
Issue 03 (2010-11-19)
application-layer protocol for creating, modifying, and terminating multimedia sessions. It is
used with other protocols, such as RTP, RTCP, SDP, RTSP, and DNS, to complete session
establishment and media negotiation.
Example Network
MA5620, MA5626, MA5616, and MA5612 support SIP Protocol. The configuration procedure
and MA5616 V800R308.
The MDU is connected to an EPON port on the OLT, and phone 1 and phone 2 are connected
to voice service ports on the MDU.
Figure 23-6 Configuring the EPON FTTB voice service (SIP protocol)
OLT
MDU
Phone2
Phone1
LAN Switch
U2000

Procedure
23-97
Configuring a VLAN.
the shortcut menu.
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
Issue 03 (2010-11-19)
IP Address: 192.168.50.4
(6) Click Done.
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
23-99
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Issue 03 (2010-11-19)
Name: FTTx
DBA Profile: FTTx
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
parameters.
23-101
displayed)
Manager VLAN: 8
(6) Click OK.
and an MDU.
Issue 03 (2010-11-19)
the shortcut menu.
EPON ONUs.
pane.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
23-103
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Issue 03 (2010-11-19)
Name: VOIP
Vlan ID: 2000
User VLAN: 2000
(4) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
23-105
(4) Click Next.
port of the VLAN.
IP Address: 17.10.10.10
Issue 03 (2010-11-19)
(5) Click Done.
Interface.
IP Address: 17.10.10.10
IP Type: Media
Gateway: 17.10.10.1
(4) Click OK.
23-107
Target Mask: 255.255.255.0
(4) Click OK.
4. Add a UAS profile. For details, see 19.3.10 Configuring a UAS Profile.
(1) Choose Configuration > Access Profile > UAS Profile from the main menu.
Name: uasprofile1
Address Mode: Fix mode
IP Address 1: 200.200.200.200 (IP address of the IMS)
Proxy Port: 5060
(4) Click OK.
5. Add a SIP interface. For details, see 19.3.12 Adding an MG.
MGs.
MG ID: 0
Name: mg1
Issue 03 (2010-11-19)
MG Domain Name: huawei.com
Active NMS UAS Profile: uasprofile1
(5) Click OK.
VoIP PSTN ports.
MG ID 0 -

23-109
(5) Click OK.
----End
Result
23.4.8 Configuring the EPON FTTB Service by Using a Service
LAN access mode and the MDU is connected to an OLT through an EPON port.
Prerequisite
Context
Example Network
Issue 03 (2010-11-19)
Figure 23-7 Configuring the EPON FTTB service by using a service provisioning profile
OLT
MDU
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
Configuring a VLAN.
the shortcut menu.
23-111
VLAN ID: 8
Type: Smart VLAN
(5) Click Next.
port of the VLAN.
IP Address: 192.168.50.4
Issue 03 (2010-11-19)
(6) Click Done.
SNMP Profile.
Name: snmpprofile
SNMP Version: v1
Read Name: public
Write Name: private
Trap UDP Port: 162
(5) Click OK.
the shortcut menu.
the main menu.
23-113
Name: FTTx
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Mapping Mode: VLAN
Issue 03 (2010-11-19)
parameters.
T-CONT Index: 1
DBA Profile: FTTx
GEM Port Index: 1
Priority Queue: 1
23-115
the parameter.
VLAN ID: 8
the parameter.
VLAN ID: 1001
Issue 03 (2010-11-19)
the parameter.
VLAN ID: 1000
the parameter.
VLAN ID: 2000
23-117
(5) Click OK.
the shortcut menu.
MDU.
the shortcut menu.
GPON UNI ports.
menu.
Name: MDU
ONU ID: 0
ONU Type: MDU
SN: 485754438E1CDE42
parameters.
Issue 03 (2010-11-19)
displayed)
Manager VLAN: 8
(6) Click OK.
and MDU.
23-119
the shortcut menu.
GPON UNI ports.
menu.
Name: FTTx_MDU
VLAN ID: 8
User VLAN: 8
(7) Click OK.
a VLAN.
Issue 03 (2010-11-19)
VLAN ID: 1001
Type: Smart VLAN
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
23-121
VLAN ID: 1001
User VLAN: 1001
(4) Click OK.
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
Issue 03 (2010-11-19)
VLAN ID: 1000
Type: Smart VLAN
(5) Click Done.
Service Port.
Name:IGMP
23-123
Vlan ID: 1000
User VLAN: 1000
of service streams)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
Issue 03 (2010-11-19)
(5) Click Finish.
23-125
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
23-127
(4) Click Finish.
a VLAN.
Issue 03 (2010-11-19)
VLAN ID: 2000
Type: Smart VLAN
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
23-129
Vlan ID: 2000
User VLAN: 2000
(4) Click OK.
l Configure the service on the MDU side.
1. Add a service provisioning profile.
(1) Choose Configuration > Access Profile Management > Service Provisioning
(2) Click the xPON FTTB Service Provisioning Profile tab.
Right-click ServicePort in the navigation tree and choose Add serviceport
from the shortcut menu. In the right pane, set the parameters of the service
virtual port.
Service Priority: 1
Issue 03 (2010-11-19)
VPI: auto
User VLAN: untagged
Service Priority: 4
VPI: auto
User VLAN: untagged
user from the shortcut menu. In the right pane, set the parameters of the
multicast user.
(5) Click OK.
2. Add a service.
The steps for configuring an xDSL port are similar to the steps for configuring an
Ethernet port.
Ethernet ports.
(3) In the information list, right-click port 0/1/1 and choose Add Service from the
shortcut menu.
(4) In the dialog box that is displayed, click next to Service Provisioning
Profile. In the dialog box that is displayed, select the service provisioning profile
whose Name is set to serviceprofile.
(5) Click OK.
----End
23-131
Result
Issue 03 (2010-11-19)
24 Configuring the EPON FTTH Services
About This Chapter
After the ONT is added successfully to the U2000, the U2000 uses the OLT as an agent to manage
the ONT (the OLT manages the ONT in OAM mode). In this case, you can configure the FTTH
service for the ONT on the U2000.
An FTTH network consisting of an OLT and a number of ONTs provides users with Internet,
24.3 Configuration Examples of the EPON FTTH Services
services in an EPON FTTH network.
Operation Guide for ONU NE Management 24 Configuring the EPON FTTH Services
24-1
After the ONT is added successfully to the U2000, the U2000 uses the OLT as an agent to manage
the ONT (the OLT manages the ONT in OAM mode). In this case, you can configure the FTTH
service for the ONT on the U2000.
Context
You can add an ONT on the device side in the following two scenarios: online ONT confirmation
and offline ONT deployment. The profile bound to an ONT and the authentication information
of the ONT must be the same as those configured on the ONT on the user side.
l Online ONT confirmation: When an ONT is online, the ONT can be managed immediately
after it is added to the U2000. This topic considers the online ONT confirmation as an
example to describe how to add an ONT to the U2000.
l Offline ONT deployment: When an ONT is offline, you need to add the ONT and configure
the FTTH service for the ONT offline. After the ONT goes online, the configuration data
is applied to the ONT through the OAM extension protocol. The service configuration on
the ONT is complete.
24.1.2 Configuring a Service Profile
The service profile is a collection of parameters associated with the ONT service.
24.1.3 Confirming an Auto-Discovered ONT
This topic describes how to confirm the auto-discovered ONU that is connected to an EPON
port. The auto-discovered ONU can work in the normal state only after it is confirmed.
Prerequisite
a DBA Profile.
Procedure
2 Click the EPON Line Profile tab. Right-click and choose Add Global Profile from the shortcut
menu.
3 In the dialog box that is displayed, set Name and relevant parameters of the line profile.
1. Choose Base Info. from the navigation tree and configure the basic parameters of the
profile.
Issue 03 (2010-11-19)
Key
Paramete
r
Description
FEC
Switch
Indicates the status of upstream forward error correction (FEC) switch of
the ONU line profile. To ensure the reliability of data transmission
between the OLT and ONU, enable the FEC function. After the FEC
function is enabled, the system inserts redundancy data into normal
packets. In this way, the line has the error tolerance function, but certain
bandwidth resources are wasted.

2. Choose DBA Threshold from the navigation tree and set the relevant parameters.
24-3
4 Click OK.
5 In the information list, right-click a record and choose Download to NE from the shortcut menu.
6 In the dialog box that is displayed, select the required OLT, and click OK.
----End
Command Reference
Enter the ONU line profile mode ONU-lineprofile EPON Global config mode

24.1.2 Configuring a Service Profile
The service profile is a collection of parameters associated with the ONT service.
Procedure
2 Click the EPON Service Profile tab. Right-click and choose Add Global Profile from the
shortcut menu.
NOTE
The parameter settings must be the same as the actual settings on the port of the ONT.
2. Choose UNI Port from the navigation tree. Select a record from the UNI port list in the
right pane, right-click, and then choose Config UNI Port from the shortcut menu. In the
Issue 03 (2010-11-19)
4 Click OK.
menu.
----End
Command Reference
Query the
information about
the ONT service
profile
display ont-srvprofile Privilege mode
Enter the ONT line
profile mode
ont-srvprofile Global config mode

24.1.3 Confirming an Auto-Discovered ONT
This topic describes how to confirm the auto-discovered ONU that is connected to an EPON
port. The auto-discovered ONU can work in the normal state only after it is confirmed.
Context
When the ONU auto-discovery function is enabled, the OLT can periodically check whether
there are new online ONUs. If new online ONUs are discovered, the OLT reports a group of
ONUs to be confirmed to the U2000 for user confirmation.
24-5
Procedure
3 On the EPON UNI Port tab page, set the filter criteria or click to display the EPON UNI
ports.
4 Select a record from the EPON UNI list, and click the AutoFind ONU Info tab in the lower
pane.
5 Select a record from the ONU list, right-click, and then choose Confirm ONU from the shortcut
menu.
6 In the dialog box that is displayed, set the basic parameters for confirming the ONT and network
management channel parameters, and then click OK.
Key
Parameter
Description
ONU ID Indicates the ONU ID. It always ranges from 0.
ONU Type Indicates the ONU type and needs to be set to ONT.
Issue 03 (2010-11-19)
Key
Parameter
Description
Line Profile Indicates the line profile bound to the port to which the ONU is connected.
After a line profile is bound to a port, the system can directly reference the line
profile when activating a port. During the activation, the system checks the
line distance and status and performs a negotiation between the CO and CPE
to determine whether the port can work under the conditions as preset in the
line profile, such as upstream and downstream line rates and noise margin.
Service
Profile
Indicates the service profile bound to the ONU. The service profile is a
collection of parameters that are associated with the ONU service.
You need not configure the service profile for the FTTB service.
Authenticat
ion Mode
Indicates the mode in which the OLT authenticates the ONU. The OLT
authenticates the EPON ONU in the MAC authorization mode by default.

When adding the ONU of the SNMP management mode, you must set the Authentication
Mode and Line Profile parameters. When adding the ONU of the OAM management mode,
you must set the Authentication Mode, Line Profile, and Service Profile parameters.
----End
Command Reference
Confirm the ONT that is in the
auto-discovery mode
ont confirm EPON mode
Enter the EPON mode from the
global configuration mode
interface EPON Global config mode
Enable the ONT auto-discovery
function of an EPON port
port ont-auto-find enable EPON mode
Query the auto-discovered ONTs
in the system or the settings for the
ONT auto-discovery time
display ont autofind Privilege mode, EPON
mode

An FTTH network consisting of an OLT and a number of ONTs provides users with Internet,
Context
24-7
Services Steps
Port
l 20.2.1 Configuring the ONT Value-Added Service
Configuration Profile
l 20.2.2 Configuring the Voice Value-Added Service
of an ONT

24.3 Configuration Examples of the EPON FTTH Services
services in an EPON FTTH network.
24.3.1 Data Plan for the EPON FTTH Services
This topic provides the data plan for the configuration examples of the EPON FTTH services.
24.3.2 Configuring the EPON FTTH Internet Service
to an OLT through an EPON port.
24.3.3 Configuring the EPON FTTH Multicast Service
24.3.4 Configuring the EPON FTTH Voice Service (H.248 Protocol)
24.3.5 Configuring the EPON FTTH Voice Service (SIP Protocol)
24.3.1 Data Plan for the EPON FTTH Services
This topic provides the data plan for the configuration examples of the EPON FTTH services.
Issue 03 (2010-11-19)
Data Plan
Table 24-1 Data plan for the EPON FTTH services
Service
Type
Device
managemen
t
Upstream port of an
OLT
0/19/0 -
the management
VLAN of the OLT
functions as the IP
address of the OLT
for inband network
management.
EPON port of the
OLT
0/2/1 -
ONT MAC: 001E-E3F4-0471
Name: ONT
ONU Type: ONT
ONU ID: 0
Terminal Type: 850e
Software Version:
V100R001C05B031
-
MEF IP traffic
profile
l Name: FTTx
l CIR: 20480
l Outer Priority: 1
The MEF IP traffic
MDU to control
upstream and
downstream traffic.
l DBA type: Maximum
Bandwidth
32768
-
Line profile Name: FTTx
DBA Profile: FTTx
-
24-9
Service
Type
Service profile Name: FTTx
VLAN Type: Translation
C-VLAN: 1001,1000
S-VLAN: 1001,1000
-
Internet
service
l Type: Smart VLAN
l Attribute: QinQ
-
Service virtual port l Name: HSI
l VLAN ID: 1001
Service VLAN
l User VLAN: 1001
same: selected
FTTx
-
IPTV
service
l Type: Smart VLAN
-
Service virtual port l Name: IGMP
l Vlan ID: 1000
0/2/1/0/0
Service VLAN
l User VLAN: 1000
same: selected
FTTx
-
Multicast VLAN l IGMP Version: IGMP V3
l VLAN ID: 3000
-
Issue 03 (2010-11-19)
Service
Type
10.10.10.20
default value)
-
selected
-
VoIP
service
l Type: Smart VLAN
-
Service virtual port l Name: VOIP
l Vlan ID: 2000
Service VLAN
l User VLAN: 2000
same: selected
FTTx
-
ONT VAS
configuration
profile (H.248
protocol)
l Profile Name: VOIP850e
l Version:
V100R001C02B010~Later
l Digitmap: x.T
l MGC Port: 2944
l MGC domain name:
MGC.com
-
24-11
Service
Type
ONT VAS
configuration
profile (SIP
protocol)
l Profile Name: VOIP850e
l Version:
V100R001C02B010~Later
l Signal Protocol: SIP
l SIP server port: 5060
l SIP server IP:
200.200.200.200
l SIP digitmap: x.T
l Voice service VLAN ID:
2000
l IP get mode: dhcp
l WAN Service Type: VOIP
test1234
test1234
-

24.3.2 Configuring the EPON FTTH Internet Service
to an OLT through an EPON port.
Prerequisite
Context
For details of the data plan, see 24.3.1 Data Plan for the EPON FTTH Services.
Example Network
This topic considers the ONT whose Terminal Type is set to HG850e as an example. The
configuration procedure of the ONTs of other types is similar to the configuration procedure
l The PC gains access to the Internet in PPPoE dialup mode.
l The ONT is connected to the EPBD card of the OLT through an optical fiber.
l The BRAS provides the AAA functions.
Issue 03 (2010-11-19)
Figure 24-1 Configuring the EPON FTTH Internet service
OLT
ONT
PC
BRAS
LAN Switch
Optical splitter
U2000

Procedure
IP Traffic Profile.
the main menu.
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
24-13
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
4. Configure a service profile. For details, see 24.1.2 Configuring a Service
Profile.
the main menu.
Set Name to FTTx.
Number of POTS Ports: 2
24-15
1, and choose Config VLAN Switch of UNI Port from the shortcut menu.
S-VLAN: 1001
C-VLAN: 1001
S-VLAN: 1000
C-VLAN: 1000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
5. Confirm the ONT. For details, see 24.1.3 Confirming an Auto-Discovered
ONT.
the shortcut menu.
EPON UNI ports.
with the MAC address 001E-E3F4-0471, and then choose Confirm ONU from
the shortcut menu.
Set Name to ONT.
Set ONU ID to 0.
Terminal Type: 850e
24-17
(6) Click OK.
1. Configuring the Information About the ETH Port of an EPON ONU
EPON ONUs.
menu.
(6) Click OK.
a VLAN.
VLAN ID: 1001
Type: Smart VLAN
Issue 03 (2010-11-19)
Attribute: QinQ
(5) Click Done.
Service Port.
Name: HSI
VLAN ID: 1001
24-19
User VLAN: 1001
(4) Click OK.
----End
Result
24.3.3 Configuring the EPON FTTH Multicast Service
Prerequisite
Context
Example Network
This topic considers the ONT whose Terminal Type is set to 850e as an example. The
Issue 03 (2010-11-19)
l The OLT uses IGMP proxy, which is a Layer 2 multicast protocol.
l The IGMP version of the multicast VLAN is IGMPv3.
Figure 24-2 Configuring the EPON FTTH multicast service
Multicast Source
OLT
LAN Switch
Optical splitter
U2000
STB
TV
BRAS
ONT

Procedure
IP Traffic Profile.
the main menu.
24-21
Name: FTTx
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
24-23
S-VLAN: 1001
C-VLAN: 1001
S-VLAN: 1000
C-VLAN: 1000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
ONT.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Set Name to ONT.
Set ONU ID to 0.
Terminal Type: 850e
24-25
(6) Click OK.
1. Configuring the Information About the ETH Port of an EPON ONU
EPON ONUs.
menu.
(6) Click OK.
VLAN ID: 3000
Type: Smart VLAN
(4) Click Done.
a VLAN.
Issue 03 (2010-11-19)
VLAN ID: 1000
Type: Smart VLAN
(5) Click Done.
Service Port.
Name:IGMP
24-27
Vlan ID: 1000
User VLAN: 1000
of service streams)
(4) Click OK.
Multicast VLAN.
multicast VLANs.
VLAN ID: 3000
Issue 03 (2010-11-19)
(5) Click Finish.
24-29
VLAN ID: 3000
Frame: 0
Slot: 19
Port: 0
(5) Click Done.
a Program Profile.
the main menu.
Name: program1
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
(8) Click OK.
a Multicast User.
Alias: IGMPUserA
24-31
(4) Click Finish.
----End
Result
24.3.4 Configuring the EPON FTTH Voice Service (H.248 Protocol)
Issue 03 (2010-11-19)
Prerequisite
Context
Example Network
24-33
Figure 24-3 Configuring the EPON FTTH voice service (H.248 protocol)
Phone1
SoftX 3000
OLT
Phone2
LAN Switch
U2000
ONT
Optical splitter

Procedure
IP Traffic Profile.
the main menu.
Name: FTTx
Issue 03 (2010-11-19)
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
24-35
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
Issue 03 (2010-11-19)
S-VLAN: 1001
C-VLAN: 1001
S-VLAN: 1000
C-VLAN: 1000
24-37
(5) Click OK.
the shortcut menu.
ONT.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Set Name to ONT.
Set ONU ID to 0.
Terminal Type: 850e
Issue 03 (2010-11-19)
(6) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
24-39
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Vlan ID: 2000
Issue 03 (2010-11-19)
User VLAN: 2000
(4) Click OK.
from the main menu.
Set Profile Name to VOIP850e.
Set Terminal Type to 850e.
Choose IP configure > IP property configure from the navigation tree and
set IP get mode to DHCP.
set Signal Protocol to H248.
Choose H.248 protocol basic configure > H.248 Global digitmap
configure > Global digitmap configure 1 from the navigation tree and set
Digitmap to x.T.
Choose Voice > Voice service VLAN and priority configure from the
navigation tree and set Voice service VLAN ID to 2000.
Choose H.248MGC > H.248 MGC configure 1 from the navigation tree and
set MGC port to 2944 and MGC domain name to MGC.com.
(4) Click OK.
24-41
EPON ONUs.
the shortcut menu.
is set to VOIP850e and click OK.
----End
Result
24.3.5 Configuring the EPON FTTH Voice Service (SIP Protocol)
Prerequisite
Context
Example Network
Issue 03 (2010-11-19)
Figure 24-4 Configuring the EPON FTTH voice service (SIP protocol)
Phone1
OLT
Phone2
LAN Switch
U2000
ONT
Optical splitter

Procedure
IP Traffic Profile.
the main menu.
Name: FTTx
24-43
CIR: 20480
Outer Priority: 1
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
(5) Click OK.
the shortcut menu.
the main menu.
Name: FTTx
DBA Profile: FTTx
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
Profile.
the main menu.
Set Name to FTTx.
24-45
S-VLAN: 1001
C-VLAN: 1001
S-VLAN: 1000
C-VLAN: 1000
Issue 03 (2010-11-19)
(5) Click OK.
the shortcut menu.
ONT.
the shortcut menu.
EPON UNI ports.
the shortcut menu.
Set Name to ONT.
Set ONU ID to 0.
Terminal Type: 850e
24-47
(6) Click OK.
a VLAN.
VLAN ID: 2000
Type: Smart VLAN
Issue 03 (2010-11-19)
(4) Click Next.
of the VLAN.
(6) Click Done.
Service Port.
Name: VOIP
Vlan ID: 2000
24-49
User VLAN: 2000
(4) Click OK.
from the main menu.
Set Profile Name to VOIP850e.
Set Terminal Type to 850e.
Choose IP configure > IP property configure from the navigation tree and
set IP get mode to DHCP.
set Signal Protocol to SIP.
Choose Voice > Voice service VLAN and priority configure from the
navigation tree and set Voice service VLAN ID to 2000.
Choose SIP protocol configure > SIP protocol configure 1 from the
navigation tree and set SIP server port to 5060 and SIP server IP to
200.200.200.200.
Choose SIP digitmap configure > Digit Map 1 from the navigation tree and
set SIP digitmap to x.T.
(4) Click OK.
Issue 03 (2010-11-19)
EPON ONUs.
the shortcut menu.
is set to VOIP850e and click OK.
EPON ONUs.
Choose SIP user configure from the navigation tree and choose Add from the
shortcut menu.
Choose User 1 from the navigation tree and set User phone number to
87650001 and User password to test1234.
Choose User 2 from the navigation tree and set User phone number to
87650002 and User password to test1234.
(5) Click OK.
----End
Result
normal cases,
24-51
25 Configuring the EPON FTTO Services
(OT925E)
About This Chapter
The deployment of an OLT and OT925E in a network provides the fiber to the office (FTTO)
solutions.
After an ONT is added successfully, you can configure private line access or FTTO services for
the ONT on the U2000.
25.3 Configuring Services on the OT925E
This topic describes how to set parameters related to CESoP on the OT925E to maintain
consistency between these parameters and the corresponding data on the OLT.
25.4 Configuration Examples of the EPON FTTO Services (OLT+OT925E)
This topic provides examples to describe how to configure various services in an EPON FTTO
network.
Operation Guide for ONU NE Management 25 Configuring the EPON FTTO Services (OT925E)
25-1
After an ONT is added successfully, you can configure private line access or FTTO services for
the ONT on the U2000.
Context
The OT925E supports five ETH ports and four E1 portss.
Procedure
1 24.1.1 Configuring a Line Profile.
2 24.1.2 Configuring a Service Profile.
3 24.1.3 Confirming an Auto-Discovered ONT.
----End
Context
Services Steps
TDM PWE3 Private Line
Access Service
l 22.2.1 Configuring the Attributes of a TOPA Card
l 22.2.2 Configuring a CESoP Connection
ATM PWE3 Private Line
Access Service
ETH PWE3 Private Line
Access Service
Router Access Service of an
Enterprise

25 Configuring the EPON FTTO Services (OT925E)
Issue 03 (2010-11-19)
25.3 Configuring Services on the OT925E
This topic describes how to set parameters related to CESoP on the OT925E to maintain
consistency between these parameters and the corresponding data on the OLT.
Context
l You can log in to the OT925E through the serial port or in Web mode. This topic considers
the login through the serial port as an example. For information on how to log in to the
OT925E in Web mode, see the operation manual of the OT925E.
l Set the baud rate to 115200 bit/s if you log in to the OT925E through the serial port.
Procedure
l To log in to the OT925E through the serial port, run the following commands:
PAS6ONU > //Prompt that is displayed after the OT925E is successfully started
PAS6ONU > exit //To enter the /# mode
/ # e1shell //To enter the CLI mode
CLI#
CLI# config //To enter the config mode
CLI(config)#
CLI(config)# zlset //To enter the zarlink chip
CLI(zlset)# source //To query and configure local parameters, including the UDP
port ID, IP address, and MAC address
CLI(source)# mac //To query or configure the MAC address (if you do not enter
a value, the MAC address is queried; if you enter a MAC address, the MAC
address is set to the entered value)
Source mac address: 8E:C0:A8:02:8E:08
CLI(source)# ip //To query or configure the local IP address (if you do not
enter a value, the local IP address is queried; if you enter a value, the local
IP address is set to the entered value)
Source ip address: 20.20.20.10
CLI(source)# port //To query local UDP port IDs (if you do not enter values,
the local UDP port IDs are queried; if you enter values, the local UDP port IDs
are set to the entered values)
source udp port[1] = 6010
CLI(source)# exit
CLI(zlset)# dest //To query or configure the parameters on the peer end,
including the UDP port ID, IP address, and MAC address (the parameters must be
the same as the corresponding parameters on the OLT)
CLI(dest)# mac
Destination mac address[1]: 00:E0:FC:10:00:03
Destination mac address[2]: 08:00:3E:32:53:10
CLI(dest)# ip
Destination ip address[1]: 20.20.20.20
CLI(dest)# port
destination udp port[1] = 6001
CLI(dest)# exit
CLI(zlset)# vlanid //To query and configure VLANs
E1[1] vlan id = 500
E1[2] vlan id = 200
25-3
E1[3] vlan id = 200
E1[4] vlan id = 200
----End
25.4 Configuration Examples of the EPON FTTO Services
(OLT+OT925E)
This topic provides examples to describe how to configure various services in an EPON FTTO
network.
25.4.1 Data Plan for the EPON FTTO Services (OLT+OT925E)
This topic provides the data plan for the configuration examples of the EPON FTTO services.
In this configuration example, the OT925E is connected to the TDM PBX of an enterprise
through an E1 port to carry the PBX fixed-line telephone service in an EPON network.
25.4.1 Data Plan for the EPON FTTO Services (OLT+OT925E)
This topic provides the data plan for the configuration examples of the EPON FTTO services.
Data Plan
Table 25-1 Data plan for the EPON FTTO services
Service
Type
Device
managemen
t
OLT
0/19/0 -
EPON port of the
OLT
0/2/1 -
l T-CONT Type: Fixed
Bandwidth
Yes
-
EPON line profile l Name: FTTx
l DBA Profile: FTTx
-
EPON service
profile
l Name: FTTx
l TDM Port Type: E1
-
Issue 03 (2010-11-19)
Service
Type
ONT Name: ONT
ONU Type: ONT
ONU ID: 0
Address
MAC: 001E-E3F4-0471
Terminal Type: 925e
Software Version:
V100R001C01B025
-
TDM PBX
access
service
l Type: Smart VLAN
-
Service virtual port l Connection Type: LAN-
EPON
l VLAN ID: 500
0/2/1/0/0
Service VLAN
l User VLAN: 500
same: selected
table_6
-
CESoP Connection l Remote MAC: 8e-c0-
a8-02-8e-08
l Remote IP: 20.20.20.10
l Remote UDP Label: 6010
l Local UDP Label: 6001
l VLAN: 500
-
25-5
Service
Type
Clock source l Clock Type: Line clock
l Working Mode: SYSLINE
l Index: 0
l Frame: 0
l Slot: 6
l Port: 0
l Clock Type: Bit clock
l BITS Type: 2MHz
l BITS Impedance: 75ohm
l Index: 1
l Frame: 0
l Slot: 0
l Port: 0
-

In this configuration example, the OT925E is connected to the TDM PBX of an enterprise
through an E1 port to carry the PBX fixed-line telephone service in an EPON network.
Context
For details of the data plan, see 25.4.1 Data Plan for the EPON FTTO Services (OLT
+OT925E).
Example Network
NOTE
The OT925E is connected to the TDM PBX of the enterprise through an E1 port and then is connected to
the OLT through an EPON upstream port. The OLT provides E1 ports to transmit the TDM service to the
SDH network.

Issue 03 (2010-11-19)
Procedure
the main menu.
Name: FTTx
T-CONT Type: Fixed Bandwidth
(5) Click OK.
the shortcut menu.
the main menu.
(2) Click the EPON Line Profile tab.
Name: FTTx
DBA Profile: FTTx
(5) Click OK.
the shortcut menu.
3. Configure a service profile. For details, see 24.1.2 Configuring a Service Profile.
The service profile must match the ONT type. This section considers the OT925E as
an example to describe how to configure a service profile. The OT925E has five
the main menu.
(2) Click the EPON Service Profile tab.
Set Name to FTTx.
25-7
TDM Port Type: E1
(5) Click OK.
the shortcut menu.
4. Confirm the ONT. For details, see 24.1.3 Confirming an Auto-Discovered ONT.
the shortcut menu.
EPON UNI ports.
menu.
Set Name to ONT.
Set ONU ID to 0.
Authentication Mode: MAC Address
Terminal Type: 925e
(6) Click OK.
l Configure the TDM PBX service on the OLT.
VLAN.
VLAN ID: 500
Type: Smart VLAN
Issue 03 (2010-11-19)
port of the VLAN.
(5) Click Finish.
and an MDU.
EPON ONUs.
pane.
menu.
Vlan ID: 500
User VLAN: 500
Upstream Traffic Name: ip-traffic-table_6
(6) Click OK.
3. Configure a CESoP connection. For details, see 22.2.2 Configuring a CESoP
Connection.
(2) On the CES E1 Port tab page, select a port and click the CESoP Info tab in the
lower pane.
(3) In the information list, right-click and choose Add CESoP Connection from the
shortcut menu.
Remote MAC: 8e-c0-a8-02-8e-08
Remote IP: 20.20.20.10
Remote UDP Label: 6010
Local UDP Label: 6001
VLAN: 500
(5) Click OK.
CAUTION
In the case of the TDM service, ensure that the clock source is unique in the entire
SDH network. Otherwise, error codes are generated and affect service quality, and
services may be interrupted if a large number of error codes are generated.
25-9
(3) In the dialog box that is displayed, set the parameters to add a line clock (provided
by the TOPA card).
Clock Type: Line clock
Working Mode: SYSLINE
Index: 0
Frame: 0
Slot: 6
Port: 0
(4) Click OK.
(5) Repeat the preceding operations to add a BITS clock (provided by the BIUA
card).
Clock Type: Bit clock
BITS Type: 2MHz
BITS Impedance: 75ohm
Index: 1
Frame: 0
Slot: 0
Port: 0
l Configure the TDM PBX service on the ONU. For details, see 25.3 Configuring
Services on the OT925E.
----End
Result
PBX users of the enterprise can make phone calls successfully by dialing internal or external
numbers.
Issue 03 (2010-11-19)
26 Remote MDU Acceptance
About This Chapter
This topic describes the application scenarios, working principles, and operations of remote
MDU acceptance.
26.1 Overview of Remote Acceptance
This topic describes the background, PnP function and benefits of remote acceptance.
26.2 Application Scenario
This topic describes the application scenario of remote acceptance.
26.3 Configuring a Remote Emulation Test for Broadband Services
This topic describes how to create a task for broadband remote acceptance and how to query the
acceptance results.
26.4 Configuring a Remote Emulation Test for Narrowband Services
This topic describes how to create a task for narrowband remote acceptance and how to query
the acceptance results.
Operation Guide for ONU NE Management 26 Remote MDU Acceptance
26-1
26.1 Overview of Remote Acceptance
This topic describes the background, PnP function and benefits of remote acceptance.
Background
A huge number of ONUs work in FTTx networks. To accept the ONUs, software commissioning
engineers have to carry commissioning equipment and travel to a site for several times. As a
result, the acceptance is not efficient.
The U2000 provides a remote acceptance function for the MDU.
PnP Function
After FTTx services are deployed and MDUs are powered on, the MDUs and service
configuration are accepted remotely so that only one visit to a site is required and the O&M costs
are reduced, thus implementing one site visit and reducing the O&M costs.
The following items are accepted remotely:
l Configuring the equipment
Check whether cards are in the normal state and whether the device version is correct. The
remote acceptance also allows you to query equipment alarms.
l Broadband service
Check whether the links of Internet access services work in the normal state by performing
a PPPoE emulation test.
l Narrowband service
Check whether voice links work in the normal state by performing a voice emulation test.
Benefits
l Remote acceptance is automatic. Specifically, the result is automatically reported after you
create an acceptance task.
l MDUs are accepted in batches.
l Acceptance efficiency increases and the O&M costs decrease.
Process of Remote Acceptance
Figure 26-1 shows the flowchart for accepting MDUs remotely.
Issue 03 (2010-11-19)
Figure 26-1 Flowchart of MDU remote acceptance

26.2 Application Scenario
This topic describes the application scenario of remote acceptance.
In the engineering acceptance period, software commissioning engineers do not need to visit the
site again because MDUs, Internet services, and voice service configuration are accepted
remotely.
26.3 Configuring a Remote Emulation Test for Broadband
Services
This topic describes how to create a task for broadband remote acceptance and how to query the
acceptance results.
Procedure
1 Choose Configuration > Fttx Service Pre-Deployment > Create Remote Acceptance Task
from the main menu.
2 In the NE Remote Acceptance dialog box, choose the required object from the Physical
Root navigation tree and specify the test items to create a remote acceptance task.
26-3
l Select the Implement broadband remote emulation test check box for a remote PPPoE
emulation test.
l Service Parameter Profile is used to filter service streams. If you specify a service parameter
profile, the PPPoE emulation test will be performed on the service streams that are filtered
out according to the parameter settings defined in the service parameter profile. If you do not
specify a service parameter profile, the PPPoE emulation test will be performed on all service
streams of specified ports. If the test is successful on one service stream, the operation is
considered successful.
l You can select a service parameter profile from the Service Parameter Profile drop-down
list, and click Advantage to edit the profile. As shown in the following figure. Then, click
OK.
Issue 03 (2010-11-19)
Table 26-1 Parameters required for configuring a remote emulation test for broadband services
Parameter Description Settings
PPPoE User
Name
Definition:
Indicates the name of the user that is used in
PPPoE access.
Range:
Character string type. It
consists of up to 65
characters.
PPPoE Password Definition:
Indicates the password of the user in PPPoE
access.
Range:
characters.
Authentication
Mode
Definition:
Indicates the mode in which the OLT
authenticates the ONU.
Range:
Enumerated type. The
options are as follows:
l CHAP: Challenge-
Handshake
Authentication
Protocol (the security
is high)
l PAP: Password
Authentication
Protocol (the security
is low because user
names and passwords
are transmitted in
plain texts over
networks)
Test Object Definition:
Indicates the test object of the remote
acceptance.
Setting method:
Enter a value or select a
software version from
the drop-down list.
Service Parameter
Profile
Definition:
Service Parameter Profile is used to filter
service streams. If you specify a service
parameter profile, the PPPoE emulation test
will be performed on the service streams that
are filtered out according to the parameter
settings defined in the service parameter
profile. If you do not specify a service
parameter profile, the PPPoE emulation test
will be performed on all service streams of
specified ports. If the test is successful on
one service stream, the operation is
considered successful.
Setting method:
Select a service
parameter profile from
the Service Parameter
Profile drop-down list,
and click Advantage to
edit the profile.
Advantage
ATM Mode and ETH/PTM Mode
26-5
Service Parameter
Profile
Definition:
Indicates the name of the service parameter
profile.
characters.
Port Type Definition:
Indicates the type of the port.
-
Issue 03 (2010-11-19)
Service Type Definition: Range:
l Single: Each service
port maps a traffic
stream. Different
traffic streams can be
distinguished by
service ports.
l Multi-Service
VLAN: Each service
port bears multiple
traffic streams. You
need to set User-Side
VLAN to distinguish
the traffic streams.
The services are
distinguished based
on the VLAN ID
contained in the user
packets. The user
packets are labeled
with different
upstream VLAN IDs,
and the original
VLAN IDs in the user
packets are removed.
l Multi-Service
Encapsulation: Each
service port bears
multiple traffic
streams. You need to
set User-Side
Encapsulation to
distinguish the traffic
streams. The services
are distinguished
based on the
encapsulation types
(IPoE/PPPoE) of the
user packets. You can
label the user packets
with different
upstream VLAN IDs.
l Multi-Service VLAN
+802.1p: Each
service port bears
multiple traffic
26-7
Indicates the upstream service type of the
service stream.
set User-Side
VLAN and 802.1p
Priority to
distinguish the traffic
streams. The services
are distinguished
according to the
VLAN IDs and the
802.1p priorities of
the packets from the
service ports.
l Multi-Service VLAN
+Encapsulation:
Each service port
bears multiple traffic
set User-Side
VLAN and User-
Side Encapsulation
to distinguish the
traffic streams.
VPI Definition:
Indicates the VPI/VCI of the service virtual
port. The VPI/VCI values are used to
identify a user.
VPI: It is located in the header of an ATM
cell. The VPI occupies 8 bits in a UNI header
and 12 bits in an NNI header.
VCI: It occupies 16 bits and identifies a
virtual channel in the VP. The VPI/VCI
values are used to identify a virtual
connection. The VPI and the VCI in the
header of an ATM cell provide the routing
information about the cell.
NOTE
This parameter is available only for the ATM
mode.
Range:
Numeral type.
l The VPI ranges from
0 to 4095.
l The VCI ranges from
32 to 65535.
VCI

3 After that, click OK in the NE Remote Acceptance dialog box. The Information dialog box
is displayed, indicating that the task is created successfully.
4 In the Scheduling Center window, view the acceptance task.
NOTE
l You can also choose Configuration > Fttx Service Pre-Deployment > View Remote Acceptance Task
from the main menu. The Scheduling Center window is displayed.
l In the Scheduling Center window, you can see that the task is always in the running state if an NE is offline.
The task can be performed only when the NE is online.
Issue 03 (2010-11-19)
5 In the Scheduling Center window, select the new acceptance task, click the Detail Info, Log
Info, or Task Info tab to view information about the task.
----End
26.4 Configuring a Remote Emulation Test for Narrowband
Services
This topic describes how to create a task for narrowband remote acceptance and how to query
the acceptance results.
Procedure
1 Choose Configuration > Fttx Service Pre-Deployment > Create Remote Acceptance Task
from the main menu.
2 In the NE Remote Acceptance dialog box, choose the required object from the Physical
Root navigation tree, specify the test items, and create a remote acceptance task.
26-9
Table 26-2 Parameters required for configuring a remote emulation test for narrowband services

l Select the Implement narrowband remote call test check box for a narrowband remote
call test.
l Select the Auto switch emulation test check box. Then, you can set Test Port for a hardware
connectivity test.
l Select the Service Emulation Test, Caller port and Callee port check boxes for a call
emulation test.
3 After that, click OK in the NE Remote Acceptance dialog box. The Information dialog box
is displayed, indicating that the task is created successfully.
4 In the Scheduling Center window, view the acceptance task.
l You can also choose Configuration > Fttx Service Pre-Deployment > View Remote
Acceptance Task from the main menu. The Scheduling Center window is displayed.
l In the Scheduling Center window, you can see that the task is always in the running state
if an NE is offline. The task can be performed only when the NE is online.
Issue 03 (2010-11-19)
5 In the Scheduling Center window, select the new acceptance task, click the Detail Info, Log
Info, or Task Info tab to view the information about the task.
----End
26-11
27 FTTx Redundancy Protection
About This Chapter
This topic describes the redundancy protection including the FTTx control card protection,
uplink protection, PON port protection, and dual-homing protection.
27.1 Configuring Control Card Protection
This topic describes how to configure redundancy backup for control cards. When control cards
are switched over in a redundancy backup system due to the control card fault or upgrade,
services are not affected.
27.2 Configuring Uplink Protection
This topic describes how to configure the uplink aggregation group or uplink protection group
to enhance the reliability of service transmission.
27.3 Configuring PON Port Protection
This topic describes how to configure PON ports as a protection group. A protection group is
used to manage members who have protection switching relationship with others. In a protection
group, you can manage the relationship between the members involved in the protection
switching, record the status of members, and manage the configuration data and status that are
relevant to the protection relationship between members.
27.4 Type B Dual-Homing Protection
This topic describes the GPON type B dual-homing protection and how to configure dual-
homing switching.
27.5 GPON Type C Protection
This topic describes GPON type C protection and how to configure the protection.
27.6 EPON Type D Protection
This topic describes EPON type D protection and how to configure the protection.
Operation Guide for ONU NE Management 27 FTTx Redundancy Protection
27-1
27.1 Configuring Control Card Protection
This topic describes how to configure redundancy backup for control cards. When control cards
are switched over in a redundancy backup system due to the control card fault or upgrade,
services are not affected.
Configuring Active and Standby GIU Control Cards for Services to Go Upstream
The SCUB, SCUN and SCUI control cards support redundancy backup.
Control cards control service cards, and converge and process broadband and narrowband
services. They are classified into active control cards and standby control cards. The control
cards support HA hot backup and they are hot swappable.
When the active control card is faulty whereas the standby control card is normal, the active and
standby GIU control cards are switched for services to go upstream, thus ensuring uninterrupted
services.
Procedure
1. In the Main Topology, double-click the required device in the Physical Root navigation
tree, or right-click the required device and choose NE Explorer from the shortcut menu.
2. Choose NE Panel from the navigation tree.
3. In the information list, right-click the required card and choose GIU Protect Group from
the shortcut menu.
4. In the dialog box that is displayed, click Add.
6. Click OK.
Configuring the Active and Control Cards as a Protection Group
Only the GE upstream interface cards can be configured as a protection group.
A protection group is used to manage members who have protection switching relationship with
others. In a protection group, you can manage the relationship between the members involved
in the protection switching, record the status of members, and manage the configuration data
and status that are relevant to the protection relationship between members.
You are required to back up the important card recourses and port recourses to enhance the
system reliability. If a fault occurs on the working member, perform the protection switching to
transfer services to the protection member that can afford the services. After the protection
switching, the services are switched from the working member to the protection member.
Procedure
2. Choose Protection Group Management from the navigation tree..
4. In the dialog box that is displayed, set the parameters. Set Protection Object to Active
main board and standby main board.
Issue 03 (2010-11-19)
5. Click OK.
27.2 Configuring Uplink Protection
This topic describes how to configure the uplink aggregation group or uplink protection group
to enhance the reliability of service transmission.
Context
Uplink protection covers two aspects:
l Uplink aggregation group: Aggregate multiple Ethernet ports as an aggregation group to
expand the bandwidth and balance the input and output load among member ports. In
addition, the ports in an aggregation group back up each other, which enhances the link
security.
NOTE
l The ETH and SCU boards support the configuration of the aggregation group.
l The ETH board and the GIU slot support the aggregation group.
l An aggregation group can implement inter-board aggregation between two GIU slots.
l An aggregation group can implement inter-board aggregation between two SPUA boards.
l When only one control board is configured, inter-board aggregation is supported between the SCUN
board and the GIU slot.
l Upstream port protection group: An upstream port protection group contains a working
port and a protection port. In the normal state, the working port carries services. When the
link of the working port fails, the system automatically switches the service on the working
port to the protection port to ensure normal service transmission, thus protecting the uplink.
Configuring an Uplink Aggregation Group
2. Choose ETH from the navigation tree.
3. On the Aggregation Group tab page, right-click and choose Add from the shortcut menu.
5. Click OK.
Configuring an Upstream Port Protection Group
2. Choose Protection Group Management from the navigation tree.
4. In the dialog box that is displayed, set the parameters. Set Protection Object to Port of
ETH NNI.
5. Click OK.
27-3
27.3 Configuring PON Port Protection
This topic describes how to configure PON ports as a protection group. A protection group is
used to manage members who have protection switching relationship with others. In a protection
group, you can manage the relationship between the members involved in the protection
switching, record the status of members, and manage the configuration data and status that are
relevant to the protection relationship between members.
Procedure
5. Click OK.
Parameter Description
Table 27-1 Key parameters required for adding a protection group
Basic Information
Group ID Definition:
Indicates the ID of the PG. It
is used to uniquely identify a
PG.
Range:
Numeral type. It ranges from
0 to 63.
Issue 03 (2010-11-19)
Protection Object Definition:
Indicates the type of
protection objects in a
protection group.
Range:
l Active main board and
standby main board
l LAG of active main board
and standby main board
l Port of active main board
l Port of ETH NNI
l LAG member of ETH
NNI
l Port of EPON UNI
l Port of GPON UNI
l STM-1 network port
l EPON ONU
l GPON ONU
Description Definition:
Specifies the descriptions for
a PG. It is easy to understand
and remember.
Range:
characters.
Working Mode Definition:
Indicates the working mode
for PG testing.
Relation to other
parameters:
When Protection Object is
Port of active main board
and standby main board or
Port of ETH NNI, Working
Mode can be set.
Range:
l Status Detection
l Time Delay Detection
l Undirection Detection
l Smart link
l Smart link load-balance
Working ONU
Frame/Slot/Port Definition:
Indicates the shelf number,
slot number, and port number
on the device, to which the
working ONU is connected.
-
ONU ID Definition:
Indicates the ID of the
working ONU. It is used to
identify an ONU.
-
27-5
Protection ONU
slot number, and port number
on the device, to which the
protection ONU is
connected.
-
ONU ID Definition:
protection ONU. It is used to
identify an ONU.
-

27.4 Type B Dual-Homing Protection
This topic describes the GPON type B dual-homing protection and how to configure dual-
homing switching.
27.4.1 Introducing GPON Type B Dual-Homing
This topic describes the GPON type B dual-homing protection.
27.4.2 Configuring GPON Type B Dual-Homing Automatic Switching
This topic describes how to configure GPON type B dual-homing automatic switching.
27.4.3 Configuring GPON Type B Dual-Homing Forcible Switching
This topic describes how to configure GPON type B dual-homing forcible switching.
27.4.1 Introducing GPON Type B Dual-Homing
This topic describes the GPON type B dual-homing protection.
Definition
Type B protection refers to the protection implemented by the system when the optical fiber
between the OLT and the ODN is faulty or the card hardware of the OLT is faulty.
l Type B protection switching mode of GPON ports
Two GPON ports on the same OLT protect each other. When one of the GPON ports fails,
the system automatically switches the services to the other GPON port. Based on this
protection mode, the protection in case of failure of the active port on one OLT is
implemented.
l Type B dual-homing protection switching mode of GPON ports
GPON ports on two different OLTs protect each other. When the GPON port on one OLT
fails, the system automatically switches the services to the GPON port on the other OLT.
Based on this protection mode, the protection in case of failure of the active port on two
OLTs is implemented.
Issue 03 (2010-11-19)
Purpose
A large number of users can be connected to one GPON port because of the high access
bandwidth provided by the GPON technology. GPON ports need to be protected to improve the
security of the OLT so that services can be recovered quickly in the case of failure of backbone
optical fibers.
Type B dual-homing protection switching can improve the disaster recovery capability of the
OLT. In the Type B dual-homing protection switching mode, the active and standby upstream
optical fibers of the ODN are connected to two OLTs respectively, and the two OLTs can be
distributed in two regions. When the OLT connected to the active optical fiber fails, the system
automatically switches services to the OLT connected to the standby optical fiber.
Principles
Type B dual-homing protection refers to the protection between two GPON ports on two OLTs.
When the GPON port on one OLT fails, the system automatically switches the services to the
GPON port on the other OLT. Figure 27-1 shows the implementation model.
Figure 27-1 Type B dual-homing protection switching mode

The implementation of the Type B dual-homing protection switching of GPON ports includes
the automatic switching mode and the forced switching mode.
l 1. Working principles of automatic switching
Automatic switching is determined and initiated by the OLT.
During the protection switching, the OLT initiates automatic detection, determines whether
to perform switching according to the actual status of the PON port, and updates the
protection status of the members in the protection group by reporting alarms.
Figure 27-2 shows the implementation model.
27-7
Figure 27-2 Working principle of type B dual-homing automatic switching

l 2. Working principles of forced switching
Forced switching is initiated by the U2000.
When the U2000 issues the forced switching command, the active OLT serves as the
standby OLT whereas the standby OLT serves as the active OLT.
Figure 27-3 Working principle of type B dual-homing forced switching

Topology View
Figure 27-4 shows the topology view of type B dual-homing.
Issue 03 (2010-11-19)
Figure 27-4 Topology view of type B dual-homing

27.4.2 Configuring GPON Type B Dual-Homing Automatic
Switching
This topic describes how to configure GPON type B dual-homing automatic switching.
Prerequisite
Member ports that can be configured as dual-homing protection groups must meet the following
requirements:
l The device version is later than V800R007C00.
l The device uses the template mode.
l The device types of two OLTs must be the same.
l The types of cards where the member ports are located must be the same. Only GPON cards
are supported.
l The active and standby GPON ports are connected to the same optical splitter.
Context
To implement dual-homing protection of two GPON ports, you need to only create a dual-
homing protection group on the U2000. After the creation, the two members in the dual-homing
protection group support the protection switching function.
the automatic switching mode and the forced switching mode. The differences between the two
modes are as follows:
l Automatic switching is determined and initiated by the OLT. During the protection
switching, the OLT initiates automatic detection (detects the availability of optical signals
on the optical fiber), determines whether to perform switching according to the actual status
of the PON port, and updates the protection status of the members in the protection group
by reporting alarms.
27-9
l Forced switching is initiated by the U2000. The U2000 issues the forced switching
command to both the active and standby OLTs. Then, the active OLT changes to the standby
OLT, and the standby OLT changes to the active OLT.
Procedure
1 Add a dual-homing protection group.
1. Choose Configuration > Access Service Management > Dual Homing from the main
menu.
3. In the Adding Dual Homing Protection Group dialog box, enter the name and description
in the Name and Description fields respectively, and choose the working member and
protection member from the Work Member and Protection Member drop-down list.
Table 27-2 Parameters required for adding a dual homing protection group
Name Definition:
Indicates the name of the
dual homing protection
group.
Range:
characters.
Indicates the brief
description of the dual
homing protection group.
Range:
characters.
Work Member Definition:
Indicates the protection
member that is being used.
Setting method:
Select the active OLT PON
port for connecting to the
ONU from the Work
Member drop-down list.
Issue 03 (2010-11-19)
Protection Member Definition:
Indicates the standby
protection group member.
Setting method:
Select the standby OLT
PON port for connecting to
the ONU from the
Protection Member drop-
down list.

4. Click OK.
NOTE
After a dual-homing protection group is created successfully,
l the GPON port that serves as Work Member is in the forcible active state. The GPON port that serves
as Protection Member is in the forcible standby state and the automatic detection is disabled.
l In the Main Topology, a connection to the standby port is added for the active port of the OLT. After
the optical splitter is disconnected from the standby port, you can double-click the standby port to
switch to the active port.
2 Enable automatic detection for the dual-homing protection group.
Right-click the new dual-homing protection group and choose Enable Automatic Detection
In this case, Work Status is set to Automatic Switchover and Automatic Detection is set to
Enable.
NOTE
When Automatic Detection is enabled for a protection group, Freeze and Unfreeze are available. In normal
cases, a protection group is in the Unfrozen state. A protection group can also be set to the Frozen mode
according to the requirements. In this case, automatic switching is disabled. After automatic detection is enabled
for the dual-homing protection group, the protection group function is enabled at the same time.
3 Query the details of the protection group. Select the created dual-homing protection group, and
click the Member tab in the lower part of the window to view the details.
----End
27.4.3 Configuring GPON Type B Dual-Homing Forcible Switching
This topic describes how to configure GPON type B dual-homing forcible switching.
Prerequisite
Member ports that can be configured as dual-homing protection groups must meet the following
requirements:
l The device version is later than V800R007C00.
l The device uses the template mode.
l The device types of two OLTs must be the same.
l The types of cards where the member ports are located must be the same. Only GPON cards
are supported.
l The active and standby GPON ports are connected to the same optical splitter.
27-11
Context
To implement dual-homing protection of two GPON ports, you need to only create a dual-
homing protection group on the U2000. After the creation, the two members in the dual-homing
protection group support the protection switching function.
the automatic switching mode and the forcible switching mode. The differences between the
two modes are as follows:
l Automatic switching is determined and initiated by the OLT. During the protection
switching, the OLT initiates automatic detection (detects the availability of optical signals
on the optical fiber), determines whether to perform switching according to the actual status
of the PON port, and updates the protection status of the members in the protection group
by reporting alarms.
l Forcible switching is initiated by the U2000. The U2000 issues the forcible switching
command to both the active and standby OLTs. Then, the active OLT changes to the standby
OLT, and the standby OLT changes to the active OLT.
Procedure
1 Add a dual-homing protection group.
1. Choose Configuration > Access Service Management > Dual Homing from the main
menu.
3. In the Adding Dual Homing Protection Group dialog box, enter the name and description
in the Name and Description fields respectively, and choose the working member and
protection member from the Work Member and Protection Member drop-down lists.
Table 27-3 Parameters required for adding a dual homing protection group
Name Definition:
dual homing protection
group.
Range:
characters.
Issue 03 (2010-11-19)
Indicates the brief
description of the dual
homing protection group.
Range:
characters.
Work Member Definition:
Indicates the protection
member that is being used.
Setting method:
Select the active OLT PON
port for connecting to the
ONU from the Work
Member drop-down list.
Protection Member Definition:
Indicates the standby
protection group member.
Setting method:
Select the standby OLT
PON port for connecting to
the ONU from the
Protection Member drop-
down list.

4. Click OK.
2 The attributes of the dual-homing protection group that you added are as follows: the working
GPON port is in the forcible active state, the protection GPON port is in the forcible standby
state, Automatic Detection is Disable, and Work Status is Non Automatic Switchover. To
switch the GPON port forcibly, right-click the protection group and choose Switchover from
the shortcut menu.
3 In the information list, right-click the dual-homing protection group and choose Compare
Member Configuration from the shortcut menu to compare the data configuration of Work
Member and Protection Member in the dual-homing protection group.
NOTE
l The data configuration can be compared only when Configure Status of a dual-homing protection group
is Normal.
l Before comparing the data configuration of the members in a dual-homing protection group, ensure that the
data on the U2000 is the same as the data on the NE. Otherwise, synchronize the data of the NE first.
l You can view the data comparison result and the difference details in the data comparison window.
4 If the data configuration is different, select the node to synchronize in the data comparison
window and click to replicate data from the active port of the OLT to the standby port.
NOTE
Before replicating data from the active port to the standby port, ensure that the resources such as templates and
VLANs exist on the standby port and these resources are the same as the resources on the active port. Otherwise,
data replication fails.
5 To switch the GPON port forcibly, right-click the protection group and choose Switchover from
the shortcut menu.
6 In the Confirm dialog box, click OK.
27-13
7 Query the details of the protection group. Select the created dual-homing protection group, and
click the Member tab in the lower part of the window to view the details.
----End
27.5 GPON Type C Protection
This topic describes GPON type C protection and how to configure the protection.
27.5.1 GPON Type C Protection
This topic describes the definition, purpose, unique benefits, and principles of GPON type C
protection.
27.5.2 Configuring GPON Type C Protection
This topic describes how to configure GPON type C protection.
27.5.1 GPON Type C Protection
This topic describes the definition, purpose, unique benefits, and principles of GPON type C
protection.
Definition
The GPON type C protection is implemented through the redundancy configuration of the PON
ports on the OLT, PON ports on the ONU, backbone optical fibers, optical splitters, and tributary
optical fibers. That is, each item is in a dual configuration.
Purpose
Type C protection switching ensures higher reliability of devices. The PON ports on the OLT,
PON ports on the ONU, backbone optical fibers, optical splitters, and tributary optical fibers are
in redundancy protection. When a component is faulty, the system can automatically switch the
service to the other optical path, thus implementing automatic or manual protection switching.
Unique Benefits
l GPON type C protection ensures higher reliability. When any part on the line fails, the
system can automatically detect the fault and switch to the other optical fiber, thus
implementing automatic service recovery.
l It serves as a basic for implementing load balancing in the future, which achieves better
bandwidth usage of the lines and at the same time the ONU can provide higher upstream
bandwidth.
Issue 03 (2010-11-19)
Principles
GPON type C protection switching is implemented through the redundancy configuration of the
PON ports on the OLT, PON ports on the ONU, backbone optical fibers, optical splitters, and
tributary optical fibers. That is, each item is in a dual configuration. The protection of two PON
ports on the OLT can be implemented in two modes: between two PON MAC chips of the same
PON card and between two PON ports on two PON cards.
Figure 27-5 GPON type C protection switching model

l OLT: The active and standby PON ports on the OLT are both in the working state. The
OLT ensures that the service information of the active PON port can be synchronized and
backed up to the standby PON port. Thus, during the protection switching, the standby
PON port can retain the service attributes for the ONU.
l Optical splitter: Two 1:N optical splitters are used.
l ONU: The ONU uses different PON MAC chips and different optical transceivers. The
ONU ensures that the service information of the active PON port can be synchronized and
backed up to the standby PON port. Thus, during the protection switching of the PON ports,
the ONU can retain the local service attributes.
The switching process is as follows:
l The active and standby PON ports on the OLT are both in the working state. That is, the
ONU registers with both PON ports on the OLT and processes the standard and extended
PLOAM messages. During the protection switching of the PON ports, the initialization
parameters and the service attributes of the ONU are not configured on the standby PON
port.
l The ONU and OLT check the link status, and determine whether to perform the switching
according to the link status. If the OLT detects that the uplink of the active PON port is
faulty, the OLT automatically switches to the standby optical link and sends the PST
message through the standby optical link to inform the ONU and request the ONU to switch.
27-15
If the ONU detects that the downlink of the active PON port is faulty, the ONU
automatically switches to the standby optical link and sends a PST message to inform the
OLT of the switching and cause of switching and requests the OLT to switch.
G.984.1 specifies two types of conditions for triggering the switching of a protection group:
1. External commands
2. Automatic switching
The conditions triggering an automatic switching include the quality degradation alarm on the
upstream/downstream line, hardware fault, or the LOS, LOF, SF, SD, LCDG, or TF alarm on
the ONU. The protection group supports automatic recovery and automatic recovery hold time.
Automatic recovery means that the system automatically switches back to the original working
member line after the original working member line recovers from the fault.
27.5.2 Configuring GPON Type C Protection
This topic describes how to configure GPON type C protection.
Prerequisite
l The ONU that is connected to the GPON port in the protection group must provide two
PON ports for upstream transmission.
l The cards that support inter-card type C protection switching are H801GPBC and
H802GPBD.
l PON ports in a protection group can reside in the cards of different types. For example,
when one PON port is configured on the H801GPBC card, the other can be configured on
the H802GPBD card. The features supported by the ONU, however, must be supported by
both of the two cards.
l The MA5600T functions as an OLT and supported ONUs are the MA5620 with the
H822EPUB control card, MA5626 with H822EPUB control card, MA5612 with the
H832CCFE control card, MA5616 with the H832CCUB control card, and MA5628 of the
R308 version. Currenctly, other devices do not support GPON type C protection switching.
l After an ONU connected to a GPON port is added to a type C protection group, the GPON
port cannot be added to a type B protection group or a type B dual-homing protection group.
If an ONU connected to a GPON port is added to a type B protection group or a type B
dual-homing protection group, the GPON port cannot be added to a type B protection group.
Context
The OLT needs to work with the ONU to implement the GPON type C protection switching.
The two members of a protection group can be in the intra-card protection or the inter-card
protection. A maximum of 64 protection groups can be configured.
Procedure
1 Configure the working ONU.
1. In the Main Topology, double-click the required NE in the Physical Root navigation tree,
or right-click the required device and choose NE Explorer from the shortcut menu.
Issue 03 (2010-11-19)
3. On the GPON ONU tab page, specify the filter criteria or click to display GPON ONU
records.
5. In the dialog box that is displayed, configure the required ONT parameters and bind Line
Profile and Service Profile. Clear Protection Role so that the ONU works as a working
ONU.
27-17
Table 27-4 Parameters required for adding an ONU
Affiliated Port Definition:
slot number, and port
number on the device to
which the ONU is
connected.
Setting method:
Select an affiliated port
from the drop-down list.
Splitter Definition:
Indicates the splitter to
which the ONU is
connected.
A splitter is a passive
device connecting the OLT
and ONU. It is mainly used
to distribute downstream
data and gather upstream
data.
Setting method:
Select a splitter ID from the
drop-down list.
Name Definition:
ONU. The name is used to
identify the ONU.
Range:
characters.
Alias Definition:
Indicates the alias of the
ONU. You can customize
an alias, which is easy to
understand and remember.
The alias is used to identify
the ONU.
Range:
characters.
NOTE
l If you do not set this
parameter, the U2000
obtains the system name
of the ONU and considers
the system name as the
ONU alias.
l You can set this
parameter to non-English
characters only when the
device supports all non-
English characters.
l Enter only English
characters when the
device does not support
all non-English
characters.
ONU ID Definition:
ONU. The ONU ID is used
to identify the ONU.
Range:
Numeral type. It ranges
from 0 to 127.
Issue 03 (2010-11-19)
Auto Assign Definition:
Indicates the ONU ID that
is automatically allocated
by the device.
Setting method:
Select Auto Assign.
Splitter Port ID Definition:
Indicates the number of the
port on the splitter to which
the ONU is connected.
Range:
from 1 to 128.
ONU Type Definition:
Indicates the type of the
ONU.
Setting method:
Select a terminal type from
the drop-down list.
Protection Role Definition:
Specifies whether to add a
protection ONU. If the
Protection Role check box
is selected, it indicates that
a virtual ONU is added on
the OLT.
Relation to other
parameters:
If the Protection Role
check box is selected, the
parameters on the Basic
Parameters and Network
Management Channel
Parameters tab pages are
unavailable.
Setting method:
Select the Protection Role
check box.
Basic Parameters
Line Profile Definition:
Indicates the line profile
bound to the ONU. The line
profiles contain the
parameters required for
setting up channels for the
GPON lines.
NOTE
This parameter is displayed in
the profiles of the profile
mode.
Setting method:
Click next to Line
Profile, and then select the
required line profile in the
dialog box that is displayed.
27-19
Service Profile Definition:
Indicates the traffic profile
bound to the ONU. The
traffic profiles contain the
parameters related to the
ONU service.
NOTE
This parameter is displayed in
the profiles of the profile
mode.
Setting method:
Click next to Service
required line profile in the
Alarm Profile Definition:
Indicates the GPON alarm
profile bound to the ONU.
The GPON alarm profile
contains a series of alarm
threshold parameters that
are used for performance
measurement and
monitoring of the activated
ONU lines.
Setting method:
Click next to Alarm
required alarm profile in the
ONU VAS Profile Definition:
Indicates the ONU value-
added service profile bound
to the ONU. The purpose of
the ONU value-added
service is to support the
function of provisioning the
VoIP service on the ONU,
and to set the parameters for
the value-added services on
the ONU, such as the VoIP
service.
Setting method:
Click next to ONU VAS
Optic Alarm Profile Definition:
Indicates the optical power
alarm template that is
bound to the ONU. The
ONU optical power alarm
template is used to manage
the alarm thresholds of the
optical transceiver in a
centralized manner.
Setting method:
Click next to Optic
Alarm Profile, and then
select the required alarm
profile in the dialog box
that is displayed.
Authentication Info
Issue 03 (2010-11-19)
Authentication Method Definition:
Indicates the mode in which
the OLT authenticates the
ONU.
Relation to other
parameters:
Password is available if the
authentication mode is set
to SN+Password,
Password(Once_on), or
Password.
SN is available if the
to SN+Password or SN.
Range:
l SN: Indicates that the
ONU authentication
mode is the serial
number (SN)
authentication mode. In
the SN authentication
mode, the OLT
determines whether the
SN reported by an ONU
is the same as the SN
that is configured. If
they are the same, the
ONU passes the
authentication and gets
online normally.
l SN+Password:
Indicates that the ONU
authentication mode is
SN+ Password
the SN+Password
authentication mode,
the OLT determines
whether the SN and
password reported by an
ONU are the same as the
configured SN and
password. If they are the
same, the ONU passes
the authentication and
gets online normally.
l Password(Once_on):
Indicates that the ONU
authentication mode is a
password
this mode, the ONU is
allowed to get online
only once. After the
ONU gets online, the
ONU cannot be
replaced. In addition,
the timeout duration is
specified, if the ONU
does not get online
within the duration, the
27-21
Time Out is available if the
to Password(Once_on).
ONU is not allowed to
get online.
l Password: Indicates that
the ONU authentication
mode is a password
this mode, the OLT
determines whether the
password reported by
the ONU is the same as
the configured
password. If the
passwords are the same,
the ONU passes the
online normally. You
can replace the ONU
with another ONU. If
the passwords of the two
ONUs are the same, the
ONU can get online.
Timeout Duration Definition:
Indicates the timeout period
for the ONU to be online. If
the authentication mode of
the ONU is set to Password
(Once_on), the ONU is
required to pass the
password authentication
within the specified timeout
period. After timeout, the
authentication is not
allowed.
Relation to other
parameters:
This parameter can be
configured if the
to Password(Once_on).
Range:
from 1 to 168.
Unit: h.
Setting Method:
If you click No Limit, the
ONU can start password
authentication at any time.
In this case, the timeout
period cannot be set.
Issue 03 (2010-11-19)
SN Definition:
Indicates the SN of the
ONU for authentication.
The value of the parameter
must be the same as the
actual SN of the ONU.
Relation to other
parameters:
configured if the
to SN or SN+Password.
Range:
characters.
The following characters
are supported:
l English letters: A-F and
a-f
l Numbers: 0-9
Password Definition:
Indicates the password of
the ONU for
authentication.
Relation to other
parameters:
configured if the
authentication mode is SN
+Password.
Range:
characters.
ONU Type
Verdor ID Definition:
vendor.
Setting method:
terminal type from the
drop-down list.
Terminal Type Definition:
Indicates the equipment
type, and especially refers
to the terminal type of the
third-party GPON ONT
and EPON ONT.
Setting method:
terminal type from the
drop-down list.
NOTE
If the third-party GPON ONT
and EPON ONT comply with
the CTC 2.1 standard, you can
enter the terminal type and
software version to manage
the third-party GPON ONT
and EPON ONT.
27-23
Software Version Definition:
Indicates software version
of the ONU, and especially
refers to the software
version of the third-party
GPON ONT and EPON
ONT.
Relation to other
parameters:
Corresponding software
version is displayed based
on the specified terminal
type.
Setting method:
software version from the
drop-down list.
NOTE
If the third-party GPON ONT
and EPON ONT comply with
the CTC 2.1 standard, you can
enter the terminal type and
software version to manage
the third-party GPON ONT
and EPON ONT.
Network Management Channel Parameters
OLT sets network
management channel
parameters
Definition:
Indicates the mode adopted
by the ONU to control and
manage ONUs in a
centralized manner.
Relation to other
parameters:
configured if the Terminal
Type is set to MDU.
Setting method:
Select OLT sets network
management channel
parameters.
SNMP Profile Name Definition:
After the SNMP profile is
added and issued to ONUs,
the ONUs are managed in a
centralized manner.
Relation to other
parameters:
Type is set to MDU.
Setting method:
Click next to the SNMP
Profile Name parameter.
In the dialog box that is
displayed, select the
required SNMP profile.
SNMP Parameters Info
Issue 03 (2010-11-19)
Manager VLAN Definition:
Indicates the VLAN
adopted by the ONU to
control and manage ONUs
in a centralized manner.
Relation to other
parameters:
Type is set to MDU and the
OLT sets network
management channel
parameters check box is
selected.
Range:
from 1 to 4095.
Priority Definition:
Indicates the priority of the
VLAN.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:
from 0 to 7.
IP Address Definition:
Indicates the management
IP address of the ONU. It is
usually set to the IP address
of the Layer 3 interface of
the VLAN.
Relation to other
parameters:
Type is set to MDU.
Range:
It is an IPv4 address in
dotted decimal notation.
27-25
IP Address Mask Definition:
Indicates the subnet mask
of the IP address. It consists
of multiple consecutive 1s
and can be represented in
dotted decimal notation
when written in the text
format. This parameter and
the destination IP address
identify the address of the
network segment where a
destination host or router is
located. To implement this
function, set the destination
IP address and the subnet
mask in the logical
conjunction (AND)
relation. Then, you can
obtain the address of the
located.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:
Gateway IP Address Definition:
Indicates the gateway IP
address of the network
segment where the ONU is
located.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:
Static Route Parameters
Issue 03 (2010-11-19)
Indicates the destination IP
address. It identifies the
destination IP address or
destination network of an
IP packet.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:
Indicates the subnet mask
of the IP address. It consists
of multiple consecutive 1s
and can be represented in
dotted decimal notation
when written in the text
format. This parameter and
the destination IP address
identify the address of the
function, set the destination
IP address and the subnet
mask in the logical
conjunction (AND)
relation, and then you can
located.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:
27-27
Next Hop IP Address Definition:
Indicates the IP address of
the next hop of the route.
Relation to other
parameters:
OLT sets network
management channel
selected.
Range:

6. Click OK.
2 Configure the protection ONU.
The procedure for configuring the protection ONU is similar to the procedure for configuring
the working ONU. The difference is that Protection Role must be selected so that ONU works
as a protection ONU.
3 Add the working ONU and protection ONU to the same protection group.
Basic Information
Issue 03 (2010-11-19)
Indicates the ID of the PG.
It is used to uniquely
identify a PG.
Range:
from 0 to 63.
protection group.
Range:
standby main board
l LAG of active main
board and standby main
board
l Port of active main
board
l Port of ETH NNI
l LAG member of ETH
NNI
l Port of EPON UNI
l Port of GPON UNI
l EPON ONU
l GPON ONU
Specifies the descriptions
for a PG. It is easy to
Range:
characters.
for PG testing.
Relation to other
parameters:
or Port of ETH NNI,
Working Mode can be set.
Range:
l Status Detection
l Smart link
Working ONU
27-29
number on the device, to
which the working ONU is
connected.
-
ONU ID Definition:
identify an ONU.
-
Protection ONU
which the protection ONU
is connected.
-
ONU ID Definition:
protection ONU. It is used
to identify an ONU.
-

5. Click OK.
----End
27.6 EPON Type D Protection
This topic describes EPON type D protection and how to configure the protection.
27.6.1 EPON Type D Protection
This topic describes the definition, purpose, unique benefits, and principles of EPON type D
protection.
27.6.2 Configuring EPON Type D Protection
This topic describes how to configure EPON type D protection.
27.6.1 EPON Type D Protection
This topic describes the definition, purpose, unique benefits, and principles of EPON type D
protection.
Issue 03 (2010-11-19)
Definition
The EPON type D protection switching is implemented through the redundancy configuration
of the PON ports on the OLT, PON ports on the ONU, backbone optical fibers, optical splitters,
and tributary optical fibers. That is, each item is in a dual configuration.
Purpose
With the increasingly wider application of the EPON technology, FTTB, FTTC, FTTH, and
especially FTTM raise a higher requirement for system reliability. Full protection is required
for PON optical lines. Type B protection covers only the backbone optical fiber, but type D
protection covers the backbone optical fiber, optical splitter, and tributary optical fiber. When
any part of the PON line is faulty, the system can automatically switch to the other optical fiber.
The protection switching can be implemented automatically or manually.
Unique Benefits
l It ensures higher reliability. When any part on the line fails, the system can automatically
detect the fault and switch the service to the other optical path, thus implementing automatic
service recovery.
l It serves as a basic for implementing load balancing in the future, which achieves better
bandwidth usage of the lines and at the same time the ONU can provide higher upstream
bandwidth.
Principles
The EPON type D protection switching is implemented through the redundancy configuration
of the PON ports on the OLT, PON ports on the ONU, backbone optical fibers, optical splitters,
and tributary optical fibers. That is, each item is in a dual configuration.
Figure 27-6 EPON type D protection switching model

27-31
On the OLT, the implementation has two modes:
1. Protection between two PON MAC chips of the same PON card
2. Protection between two PON ports of two PON cards
To implement the protection, each device works in the following status:
l OLT: The active and standby PON ports on the OLT are both in the working state. The
OLT ensures that the service information of the active PON port can be synchronized and
backed up to the standby PON port. Thus, during the protection switching, the standby
PON port can retain the service attributes for the ONU.
l Optical splitter: Two 1:N optical splitters are used.
l ONU: The ONU uses different PON MAC chips and different optical transceivers. The
ONU ensures that the service information of the active PON port can be synchronized and
backed up to the standby PON port. Thus, during the protection switching of the PON ports,
the ONU can maintain the same local service attributes.
The switching process is as follows:
l The active and standby PON ports on the OLT are both in the working state (the ONU
registers with both PON ports on the OLT, and the OLT and the ONU can negotiate through
the standard and extended PLOAM messages). During the protection switching of the PON
ports, the initialization parameters and the service attributes of the ONU are not configured
on the standby PON port.
l The ONU and the OLT check the link status, and determine whether to perform the
switching according to the link status.
l If the OLT detects that the uplink of the active PON port is faulty, the OLT automatically
switches to the standby optical link and sends the extended OAM message (with the Active
PON_IF Administrate attribute) through the standby optical link to configure the active
PON port of the ONU.
l If the ONU detects that the downlink of the active PON port is faulty, the ONU
automatically switches to the standby optical link and sends the extended OAM message
(with Alarm ID = 0x000C and PON_IF Switch attribute) through the standby optical link
to inform the OLT of the switching on the ONU PON port and the cause of switching.
When any of the following conditions occurs in a protection group, the optical link protection
switching is triggered:
l Loss of optical signal (LOS)
l Input channel degradation
l Over low or over high input optical signal power
l BER threshold violation
During the device running, a hardware fault can also trigger the protection switching. In addition,
the protection switching can also be performed forcibly through commands.
27.6.2 Configuring EPON Type D Protection
This topic describes how to configure EPON type D protection.
Issue 03 (2010-11-19)
Prerequisite
l Cards that support inter-card type D protection switching are H801EPBA, H802EPBA, and
H802EPBD.
l The members of an inter-card protection group must reside in the cards of the same type.
For example, when one member is configured on the H801EPBD card, the other member
must also be configured on the H801EPBD card.
l Currently, the ONUs of version R308, such as the MA5620 with the H822EPUB control
card, MA5626 with H822EPUB control card, MA5612 with the H832CCFE control card,
MA5616 with the H832CCUB control card, and MA5628 support the EPON type D
protection switching.
l If an ONU connected to an EPON port is added to a type D protection group, the EPON
port cannot be added to a type B protection group or a type B dual-homing protection group.
If an ONU connected to an EPON port is added to a type B protection group or a type B
dual-homing protection group, the EPON port cannot be added to a type B protection group.
Context
The OLT needs to work with the ONU to implement the GPON type D protection switching.
The two members of a protection group can be in the intra-card protection or the inter-card
protection. A maximum of 64 protection groups can be configured.
Procedure
1 Configure the working ONU.
3. On the EPON ONU tab page, specify the filter criteria or click to display EPON ONU
records.
5. In the dialog box that is displayed, configure the required ONT parameters and bind Line
Profile and Service Profile. Clear Protection Role so that the ONU works as a working
ONU.
27-33
Issue 03 (2010-11-19)
Table 27-6 Parameters required for adding an ONU
Affiliated Port Definition:
Indicates the shelf number, slot
number, and port number of the
port to which the ONU is
connected.
Range:
Numeral type. Its range varies
with the shelf type and the
board type.
Splitter ID Definition:
Indicates the splitter to which
the ONU is connected.
A splitter is a passive device
connecting the OLT and ONU.
It is mainly used to distribute
downstream data and gather
upstream data.
Setting method:
Select a splitter ID from the
drop-down list.
Name Definition:
Indicates the ONU ID. The ID
uniquely identifies an ONU.
Range:
consists of up to 255 characters.
Alias Definition:
Indicates the ONU alias, which
is easy to understand and
remember.
Range:
NOTE
l If you do not set this
parameter, the U2000 obtains
the system name of the ONU
and considers the system
name as the ONU alias.
l You can set this parameter to
non-English characters only
when the device supports all
non-English characters.
l Enter only English characters
when the device does not
support all non-English
characters.
ONU ID Definition:
Indicates the ID of the ONU.
The ID is used to identify an
ONU.
Range:
Numeral type. It ranges from 0
to 127.
Auto Assign Definition:
Indicates the ONU ID that is
automatically allocated by the
device.
Setting method:
Select Auto Assign.
27-35
Splitter Port ID Definition:
Indicates the number of the
port on the splitter to which the
ONU is connected.
Range:
to 128.
ONU Type Definition:
Indicates the type of the ONU.
Setting method:
Select a terminal type from the
drop-down list.
Protection Role Definition:
Specifies whether to add a
protection ONU. If the
Protection Role check box is
selected, it indicates that a
virtual ONU is added on the
OLT.
Relation to other
parameters:
If the Protection Role check
box is selected, the parameters
on the Basic Parameters and
Network Management
Channel Parameters tab
pages are unavailable.
Setting method:
Select the Protection Role
check box.
Basic Parameters
Line Profile Definition:
Indicates the line profile bound
to the ONU. The line profiles
contain the parameters
required for setting up channels
for the EPON lines.
NOTE
This parameter is displayed in the
profiles of the profile mode.
Setting method:
Click next to Line Profile,
and then select the required line
profile in the dialog box that is
displayed.
Service Profile Definition:
Indicates the service profile
bound to the ONU. The service
profiles contain the parameters
related to the ONU service.
NOTE
profiles of the profile mode.
Setting method:
Click next to Service
required service profile in the
Issue 03 (2010-11-19)
ONU VAS Profile Definition:
Indicates the ONU value-
added service profile bound to
the ONU. The purpose of the
ONU value-added service is to
support the function of
provisioning the VoIP service
on the ONU, and to set the
parameters for the value-added
services on the ONU, such as
the VoIP service.
Setting method:
Click next to ONU VAS
EPON ONU
Capacity Profile
Definition:
Indicates the capacity profile
bound to the ONU.
NOTE
profiles of the distributed mode.
Setting method:
Click next to EPON ONU
Capacity Profile, and then
select the required alarm profile
in the dialog box that is
displayed.
EPON DBA Profile Definition:
Indicates the DBA profile
bound to the ONU.
NOTE
profiles of the distributed mode.
Setting method:
Click next to EPON DBA
Optic Alarm Profile Definition:
Indicates the optical power
alarm template that is bound to
the ONU. The ONU optical
power alarm template is used to
manage the alarm thresholds of
the optical transceiver in a
centralized manner.
Setting method:
Click next to Optic Alarm
Auth Info.
27-37
Auth Way Definition:
Indicates the mode in which the
OLT authenticates the ONU.
Range:
Enumerated type. The options
are as follows:
l MAC Address: Specifies
the ONU authentication
mode as the MAC address
authentication mode. In this
mode, the OLT determines
whether the MAC address
reported by the ONU is the
same as the configuration. If
yes, the ONU passes the
online.
l Key: Specifies the ONU
authentication mode as the
key authentication mode.
l LOID: Specifies the ONU
LOID authentication mode.
This mode can be used in
the FTTB application
scenario.
l LOID+CHECKCODE:
Specifies the ONU
LOID+CHECKCODE
authentication mode. In the
FTTH application scenario,
the random character string
CHECKCODE is added to
the LOID character string to
enable the OLT to
authenticate the ONU.
Default: MAC Address.
MAC Address Definition:
Indicates the MAC address
used by the ONU for
authentication.
Relation to other
parameters:
When Auth Way is set to
MAC Address, this parameter
is mandatory.
Range:
Character string type. The
format is FF-FF-FF-FF-FF-FF.
Where, F represents a
hexadecimal number.
Issue 03 (2010-11-19)
KEY Definition:
Indicates the password used by
the ONU for authentication.
Relation to other
parameters:
Key, this parameter is
mandatory.
Range:
The following characters are
supported:
l English letters: case
sensitive.
l Numbers: 0, 1, 2, 3, 4, 5, 6,
7, 8, and 9.
l Symbols: symbols on the
keyboard of a PC.
l All the non-English
characters, including
Chinese, Korean, Japanese,
and French characters.
LOID Definition:
Relation to other
parameters:
LOID or LOID
+CHECKCODE, this
parameter is mandatory.
Range:
supported:
sensitive.
l Numbers: 0, 1, 2, 3, 4, 5, 6,
7, 8, and 9.
keyboard of a PC.
27-39
CHECKCODE Definition:
Relation to other
parameters:
LOID+CHECKCODE, this
parameter is mandatory.
Range:
supported:
sensitive.
l Numbers: 0, 1, 2, 3, 4, 5, 6,
7, 8, and 9.
keyboard of a PC.
Auth Mode Definition:
Indicates the mode in which the
OLT authenticates the ONU.
Range:
are as follows:
l Always_on: Specifies the
ONU authentication mode
as the password
mode, the OLT determines
whether the password
reported by the ONU is the
same as the configuration. If
yes, the ONU passes the
online.
l Once On: Specifies the
ONU authentication mode
as the password
mode, the ONU can get
online only once. After the
ONU gets online, the ONU
cannot be replaced. After
the timeout time is set, if the
ONU does not get online
within the timeout time, the
ONU is forbidden to get
online.
Issue 03 (2010-11-19)
Time Out Definition:
Indicates the timeout time for
the ONU to be online.
Relation to other
parameters:
When Auth Way is set to Once
On, this parameter is
mandatory.
Range:
to 168.
Unit: h.
ONU Type
Verdor ID Definition:
Indicates the ID of the vendor.
Setting method:
terminal type from the drop-
down list.
Terminal Type Definition:
Indicates the equipment type,
and especially refers to the
terminal type of the third-party
GPON ONT and EPON ONT.
Setting method:
down list.
NOTE
If the third-party GPON ONT and
EPON ONT comply with the CTC
2.1 standard, you can enter the
terminal type and software
version to manage the third-party
Software Version Definition:
Indicates software version of
the ONU, and especially refers
to the software version of the
third-party GPON ONT and
EPON ONT.
Relation to other
parameters:
Corresponding software
version is displayed based on
the specified terminal type.
Setting method:
down list.
NOTE
If the third-party GPON ONT and
EPON ONT comply with the CTC
2.1 standard, you can enter the
terminal type and software
version to manage the third-party
Extended Info.
27-41
DHCP Status Definition:
Enables the ONU to
dynamically request the
configuration information
from the Dynamic Host
Configuration Protocol
(DHCP) server, or disables the
ONU from dynamically
request the configuration
information from the DHCP
server.
DHCP works in the client-
server mode. The DHCP client
dynamically sends
configuration requests to the
DHCP server, and the DHCP
server provides configuration
information to the DHCP
client.
Setting method:
Select the DHCP Status check
box.
PITP Status Definition:
Enables or disables Policy
Information Transfer Protocol
(PITP) of the ONU. After PITP
is enabled, the system binds the
user account to the ONU port
for authentication. This
prevents theft and roaming of
the user account.
PITP is used to provide the
physical port information of
the access subscriber. After a
BRAS obtains the ONU port
information, the BRAS
authenticates the binding
between the user account and
ONU port. This prevents theft
and roaming of the user
account.
Setting method:
Select the PITP Status check
box.
Issue 03 (2010-11-19)
Multicast Mode Definition:
Indicates the multicast mode of
the ONU.
Setting method:
are as follows:
l CTC: Uses the China
Telecom standard.
l IGMP snooping: Indicates a
multicast technology
running at the link layer. It
can implement L2 multicast
management to effectively
suppress the broadcast of
the multicast data at layer 2.
l Transparent: Transparently
transmits the IGMP
packets.
Network Management Channel Parameters
OLT sets network
management
channel parameters
Definition:
Indicates the mode adopted by
the ONU to control and
manage ONUs in a centralized
manner.
Setting method:
Select OLT sets network
management channel
parameters.
EPON SNMP
Profile
Definition:
After the SNMP profile is
added and issued to ONUs, the
ONUs are managed in a
centralized manner.
Setting method:
Click next to the EPON
SNMP Profile parameter. In
the dialog box that is displayed,
select the required SNMP
profile.
Net Para
Manager VLAN Definition:
Indicates the VLAN adopted
by the ONU to control and
manage ONUs in a centralized
manner.
Range:
to 4095.
Gateway IP
Address
Definition:
Indicates the gateway IP
address of the network segment
where the ONU is located.
Range:
It is an IPv4 address in dotted
decimal notation.
27-43
Indicates the management IP
address of the ONU. It is
usually set to the IP address of
the Layer 3 interface of the
VLAN.
Range:
decimal notation.
Indicates the subnet mask of
the IP address. It consists of
multiple consecutive 1s and
can be represented in dotted
decimal notation when written
in the text format. This
parameter and the destination
IP address identify the address
of the network segment where
a destination host or router is
function, set the destination IP
address and the subnet mask in
the logical conjunction (AND)
relation. Then, you can obtain
the address of the network
segment where a destination
host or router is located.
Range:
decimal notation.
Priority Definition:
Indicates the priority of the
VLAN.
Range:
to 7.
Static Route Parameters
Target IP Address Definition:
Indicates the destination IP
address. It identifies the
destination IP address or
destination network of an IP
packet.
Range:
decimal notation.
Issue 03 (2010-11-19)
Target Mask Definition:
Indicates the subnet mask of
the IP address. It consists of
multiple consecutive 1s and
can be represented in dotted
decimal notation when written
in the text format. This
parameter and the destination
IP address identify the address
of the network segment where
a destination host or router is
function, set the destination IP
address and the subnet mask in
the logical conjunction (AND)
relation, and then you can
located.
Range:
decimal notation.
Next Hop IP
Address
Definition:
Indicates the IP address of the
next hop of the route.
Range:
decimal notation.

6. Click OK.
2 Configure the protection ONU.
The procedure for configuring the protection ONU is similar to the procedure for configuring
the working ONU. The difference is that Protection Role must be selected so that the ONU
works as a protection ONU.
3 Add the working ONU and protection ONU to the same protection group.
1. In the Main Topology, double-click the required NE in the Physical Root navigation tree,
27-45
Basic Information
Indicates the ID of the PG.
It is used to uniquely
identify a PG.
Range:
from 0 to 63.
protection group.
Range:
standby main board
l LAG of active main
board
l Port of active main
board
l Port of ETH NNI
l LAG member of ETH
NNI
l Port of EPON UNI
l Port of GPON UNI
l EPON ONU
l GPON ONU
Specifies the descriptions
for a PG. It is easy to
Range:
characters.
for PG testing.
Relation to other
parameters:
or Port of ETH NNI,
Working Mode can be set.
Range:
l Status Detection
l Smart link
Working ONU
Issue 03 (2010-11-19)
which the working ONU is
connected.
-
ONU ID Definition:
identify an ONU.
-
Protection ONU
which the protection ONU
is connected.
-
ONU ID Definition:
protection ONU. It is used
to identify an ONU.
-

5. Click OK.
----End
27-47
28 Replacing an MDU Quickly
Context
When a faulty ONU is replaced with a new one, you need to connect the new ONU to the relevant
port of the OLT through an optical fiber and bind the authentication information of the new
ONU. After the new ONU goes online, the U2000 automatically applies service configuration
data to the new ONU. Therefore, you need not reconfigure the data.
Advantages:
l An MDU is replaced easily and the OSS need not reapply configuration data.
l The MAC address and SN of the MDU are displayed only on the OLT and U2000. MDUs
are differentiated according to their IP addresses in the OSS.
l The on-site construction is simple and no configuration data is required.
l The version and configuration data can be restored automatically.
Figure 28-1 shows the flowchart for quickly replacing an MDU.
Operation Guide for ONU NE Management 28 Replacing an MDU Quickly
28-1
Figure 28-1 Flowchart for quickly replacing an MDU

CAUTION
Make sure that any of the FTP, TFTP, and SFTP services are running.
Procedure
1 Set the automatic backup policy.
Issue 03 (2010-11-19)
1. Choose Administration > NE Software Management > User-Defined Policy from the
main menu.
2. In the User-Defined Policy dialog box, set NE Type and NE Version, and click Next, as
shown in Figure 28-2.

3. In the User-Defined Policy dialog box, set parameters on the Backup Policy and Save
Policy tab pages as required, and click Finish, as shown in Figure 28-3.
Operation Guide for ONU NE Management 28 Replacing an MDU Quickly
28-3

2 (Optional) Set the automatic upgrade policy.
For details, see 17.3.1 Upgrading MDUs in Batches Automatically.
3 On-site engineers replace the ONU.
4 In the U2000 window, right-click the new ONU that is used to replace the faulty ONU, such as
MA5620E, and choose EPON Option > Replace ONU from the shortcut menu.
5 In the Replace ONU dialog box, click the Basic Info tab, set Auth Way to MAC Address in
the Auth Info field, and then click next to MAC.
6 In the MAC Address List dialog box, select a record and click OK.
7 In the Replace ONU dialog box, click the Basic Info tab and click OK.
CAUTION
After the MDU is powered on, the U2000 automatically registers the MDU, and restores the
version and configuration data of the MDU.
----End
Issue 03 (2010-11-19)
29 Fault Locating Based on Alarms
About This Chapter
This topic describes how to mask a large number of correlative alarms of low severity, and
discard or combine invalid intermittent alarms or repeated events by means of alarm correlation
analysis in FTTx scenarios. In this way, you can focus on root alarms and locate faults quickly
and accurately.
29.1 Introduction to the Alarm Correlation Analysis of FTTx Services
This topic describes the background and means of alarm correlation analysis.
29.2 Correlative Relationship Between FTTx Alarms
This topic considers the diagram of the correlative relationship between GPON FTTx alarms as
an example to describe the relationship between root alarms and correlative alarms.
29.3 Alarm Locating
This topic describes the alarm locating flow and how to analyze alarms according to alarm
correlation rules.
Operation Guide for ONU NE Management 29 Fault Locating Based on Alarms
29-1
29.1 Introduction to the Alarm Correlation Analysis of FTTx
Services
This topic describes the background and means of alarm correlation analysis.
Background
A large number of ONTs are widely distributed in harsh environments in FTTx scenarios. As a
result, many alarms are generated and most of them are insignificant alarms that users do not
concern. Therefore, how to effectively report faults and accurately rectify the faults is a top
concern of carriers.
The U2000 provides various analysis means including alarm/event correlation analysis,
intermittent alarm analysis, repeated event analysis, alarm/event frequency analysis, and time
analysis of acknowledged and uncleared alarms. These means can analyze and suppress alarms
from different aspects to help users focus on root alarms and locate faults quickly.
Alarm Correlation Analysis
According to configured correlation rules, the U2000 automatically handles relevant alarms or
events, thus improving the handling efficiency. For information on how to configure correlation
rules, choose Working with the NMS > Alarm Management > Analyzing the Root Alarm
of a Fault from the navigation tree in the Help and view relevant contents in the right pane.
l Correlation analysis
In relevant alarms, the causes of the alarms are associated with each other and one alarm
is the root cause of other alarms. Table 29-1 provides relevant alarms predefined for FTTx
services.
Table 29-1 Relevant alarms
Service Type Root Alarm Correlative Alarm
GPON The communication
between the service
board and the control
board fails.
The feed fiber is broken or OLT
can not receive any expected
optical signals(LOS).
The feed fiber is broken
or OLT can not receive
any expected optical
signals(LOS).
The distribute fiber is broken or
OLT can not receive expected
optical signals from ONT(LOSi).
The GPON ONT gets offline.
The distribute fiber is
broken or OLT can not
receive expected optical
signals from ONT
(LOSi).
The GPON ONT gets offline.
The loss of GEM channel
delineation (LCDGi) occurs.
Issue 03 (2010-11-19)
Service Type Root Alarm Correlative Alarm
The dying-gasp of
ONTi (DGi) is
generated.
EPON The communication
between the service
board fails.
The feed fiber is broken
or OLT can not receive
any expected optical
signals(LOS).
The EPON ONT gets offline.
signals from ONT
(LOSi).
The EPON ONT gets offline.
The dying-gasp of
ONTi (DGi) is
generated.

You can define more relevant alarms by using the correlation analysis function.
Maintenance engineers cannot locate and analyze a fault quickly if too many correlative
alarms of low severity exist. Thus, you can configure correlation rules on the U2000 so that
the U2000 directly discards non-root alarms that match the correlation rules, marks alarms
as correlative alarms (saves them to the suppression library) or lowers their severity levels,
and raises the severity levels of root alarms to draw the attention of maintenance engineers.
l Intermittent alarm/repeated event analysis
According to configured intermittent alarm/repeated event analysis rules, the U2000
discards intermittent alarms or repeated events that match the rules, and displays only the
first repeated event or cleared intermittent alarm.
If intermittent alarms are reported continuously within a short period of time, the cause
may be that an NE or a service switches between the normal state and the abnormal state
repeatedly. To handle these alarms in time, you can configure intermittent alarm analysis
rules to raise their severity levels, thus drawing the attention of maintenance engineers.
In addition, if you double-click the required OLT device on the Physical Root navigation
tree on the Main Topology tab page, choose NE Properties > Security > Trap from the
29-3
navigation tree, enable the Alarm anti-jitter switch and set Alarm anti-jitter interval,
intermittent alarms are periodically masked on NEs.
l Alarm/Event frequency analysis
According to configured alarm/event frequency analysis rules, when the number of
different alarms or events that are generated within a period of time exceeds the threshold,
it is considered that these alarms or events are related to each other. Then, the U2000
redefines the alarm severity level, generates a local U2000 alarm, or masks these alarms
and generates a local U2000 alarm according to the configured rules.
l Time analysis of acknowledged and uncleared alarms
For acknowledged alarms that are not cleared for a long time, the U2000 can raise the alarm
severity level by using the acknowledged and uncleared alarm analysis function. In this
way, maintenance engineers pay attention to and handle these alarms in time.
29.2 Correlative Relationship Between FTTx Alarms
This topic considers the diagram of the correlative relationship between GPON FTTx alarms as
an example to describe the relationship between root alarms and correlative alarms.
Figure 29-1 shows the diagram of the correlative relationship between GPON FTTx alarms.
Figure 29-1 Diagram of the correlative relationship between GPON FTTx alarms
Root alarms
The feed fiber is broken or
OLT can not receive any
expected optical
signals(LOS)
The GPON ONT
gets offline
Root alarms
Correlative alarms
The backbone optical fiber is broken, the
optical port is disabled, or the last online
ONT connected to the PON port goes offline
The tributary optical
fiber is broken
signals from ONT(LOSi)
The last online ONT
connected to the PON port
is powered off.
The dying-gasp of
ONTi (DGi) is
generated
The ONT is powered off. A card is faulty or removed.
The communication
between the service
board fails
Root alarms
Root causes
of alarms
The feed fiber is broken or
OLT can not receive any
expected optical
signals(LOS)
signals from ONT(LOSi)
Figure 29-1 shows a group of relevant alarms identified in different colors of lines. For example,
in the diagram, the correlative alarms connected in red lines indicate that the root alarm "The
feed fiber is broken or OLT can not receive any expected optical signals(LOS)" will be generated
when the backbone optical fiber is broken, the optical port is disabled, or the only online ONT
connected to the PON port goes offline. This root alarm will trigger a correlative alarm "The
distribute fiber is broken or OLT cannot receive expected optical signals from ONT(LOSi)",
and the correlative alarm will trigger another correlative alarm "The GPON ONT gets offline".
The alarm triggers another correlative alarm and functions as the root alarm of the correlative
alarm.
One correlative alarm may be triggered by different root alarms. When a root alarm is cleared,
the correlative alarm will not be cleared. For example, the alarms "The feed fiber is broken or
Issue 03 (2010-11-19)
OLT can not receive any expected optical signals(LOS)" and "The dying-gasp of ONTi (DGi)
is generated" trigger the alarm "The distribute fiber is broken or OLT can not receive expected
optical signals from ONT(LOSi). When the alarm "The feed fiber is broken or OLT can not
receive any expected optical signals(LOS)" is cleared, the alarm "The distribute fiber is broken
or OLT can not receive expected optical signals from ONT(LOSi)" may not be cleared.
If the check box next to Display correlative alarms is selected during alarm filtering on the
U2000, is displayed in the first line of the root alarm list and is displayed in the first line
of the correlative alarm list in the Browse Current Alarm window. Right-click a root or
correlative alarm and choose Query Correlative Alarms/Query Root Alarms from the
shortcut menu to view the correlative alarm or root alarm of the selected alarm.
You can focus on only root alarms during alarm analysis and handle major alarms to locate and
rectify faults quickly.
29.3 Alarm Locating
correlation rules.
29.3.1 Alarm Locating Flow
This topic describes the alarm locating flow and related handling policies.
29.3 Alarm Locating
correlation rules.
Alarm Locating
This topic describes how to locate an alarm according to the alarm correlation rules.
29.3.1 Alarm Locating Flow
This topic describes the alarm locating flow and related handling policies.
Figure 29-2 shows the alarm locating flowchart.
29-5
Figure 29-2 Alarm locating flowchart

Acknowledge the alarm
Collect fault symptom and other
information
Analyze the fault cause
Work out a troubleshooting
scheme according to the
suggestions and experience
Rectify the fault
Clear the alarm
Is the fault rectified?
Record the alarm handling
process in the experience
library
End
Yes
No
Fault
locating
Fault
rectification
Information
collection
Start
View the current alarm
Set alarm masking and
correlation rules
Discard the alarm, save the alarm
to the suppression library, or lower
the severity level of the alarm
Is the alarm a root alarm?
Yes
(Optional) Configure automatic
alarm synchronization rules

(1) Configure automatic alarm synchronization rules. These rules enable the U2000 to
automatically synchronize alarms after the communication between the U2000 and an NE
resumes or the U2000 is restarted. The synchronization ensures that alarms on the U2000 and
NEs are the same.
Issue 03 (2010-11-19)
(2) Set alarm handling policies by means of alarm masking and correlation rules.
l Alarm masking: Masks unimportant alarms to prevent a large amount of redundant
information.
l Correlation analysis: Sets the policies of handling root alarms and correlative alarms, such
as raising the severity levels of root alarms, and discarding correlative alarms, marking
alarms as correlative alarms (saving to the suppression library) or reducing their severity
levels.
l Intermittent alarm/event analysis: Reserves only the first repeated alarm or discards
intermittent alarms.
l Alarm/Event frequency analysis: Sets the policy of handling alarms when the number of
alarms that are generated within a certain period of time exceeds the threshold.
l Time analysis of acknowledged and uncleared alarms: Raises the severity level of
acknowledged alarms that are not cleared for a long time so that the alarms can be handled
in time.
(3) View important alarms that are filtered by alarm source, alarm severity, type, or status. You
can query correlative alarms only after you select the check box next to Display correlative
alarms.
(4) and (5) Focus on the root alarm. According to configured rules, correlative alarms are
discarded or marked as correlative alarms (saved to the suppression library), or their severity
levels are lowered.
(6) Determine whether the fault that triggers the alarm can be rectified according to the alarm
details. If yes, properly handle and acknowledge this alarm.
(7) In the Browse Current Alarm window, select the alarm and view the Details area and
Reason, Alarm Description, and Experience in the Handling Suggestion area in the lower
pane to analyze the cause of the alarm. In the case of the MA5600T or MA5680T, click Click
here to show detail Information. The alarm reference window in the Help is displayed and you
can view the alarm details in this window.
(8) Rectify the fault according to the handling suggestions and experience in the Handling
Suggestion area. In the case of the MA5600T or MA5680T, click Click here to show detail
Information. The alarm reference window in the Help is displayed and you can view the alarm
handling process in this window.
(9) Manually clear the alarm if the U2000 cannot automatically clear the alarm or this alarm
does not exist on an NE. If the alarm is cleared, it indicates that the fault that triggers the alarm
is rectified.
(10) Record the handling process of the alarm or event in the maintenance experience library so
that other engineers can refer to the handling process when handling alarms or events of the
same type.
29.3.2 Alarm Locating
correlation rules.
Alarm Locating
This topic describes how to locate an alarm according to the alarm correlation rules.
29-7
Prerequisite
When configuring alarm correlation rules by importing a configuration file, make sure that the
CorRuleForNemgrAccess.xml configuration file that stores alarm correlation rules is saved in
the \U2000\server\etc\conf directory.
Context
You can import the configuration file or configure Correlation Analysis on the U2000 client
to configure alarm correlation rules. By importing a configuration file, you can configure
correlation rules in batches.
Procedure
1 Do as follows to configure alarm correlation rules.
l Method 1: Importing a configuration file
1. Do as follows to import the configuration file that stores alarm correlation rules:
On a Windows-based U2000 server, run the >svc_fm_import_internal_corRule
CorRuleForNemgrAccess.xml command in the command line interface (CLI).
On a Solaris- or Linux-based U2000 server, log in to the OS as user root and run
the following commands:
#. /export/home/nmsuser/.profile
#svc_fm_import_internal_corRule CorRuleForNemgrAccess.xml
NOTE
l These commands take effect only when Fault Process is running.
l The imported configuration file, CorRuleForNemgrAccess.xml, defines relevant alarms
provided in Table 29-1.
2. Do as follows to enable the default correlation analysis function of the U2000 server:
On a Windows-based U2000 server, run the >SettingTool -cmd setparam -path /
imap/ifms/UsingHeatMan -value "true" command in the CLI.
On a Solaris- or Linux-based U2000 server, run the #SettingTool -cmd setparam
-path /imap/ifms/UsingHeatMan -value "true" command.
3. Log in to the System Monitor client and restart Fault Process.
4. Log in to the U2000 client and choose Fault > Settings > Correlation from the main
menu.
5. Click the Default Correlation tab. Clear the Enable check box next to a correlation
rule that does not need to be enabled.
Issue 03 (2010-11-19)
l Method 2: Configuring correlation analysis on the U2000 client
1. Choose Fault > Settings > Correlation from the main menu.
2. In the Correlation window, click the Correlation Analysis tab.
3. On the Correlation Analysis tab page, click Add to set relevant parameters.
a. Configure root or relevant alarms and their handling policies. For example, select
Import to suppressed library for a relevant alarm to define the alarm as the
correlative alarm of a root alarm.
NOTE
You can select any of the following handling policies for relevant alarms from the Action
drop-down list:
l Redefine Level: Redefines the severity levels of relevant alarms to lower the severity levels
of alarms that do not need to be concerned.
l Import to suppressed library: Defines a relevant alarm as the correlative alarm of a root
alarm.
l Discard: Discards relevant alarms.
b. Click Next to set the attributes of root alarms and correlative alarms. Specifically,
set the generation time of correlative alarms to be later than that of root alarms
and set the locating information of correlative alarms to be the same as that of
root alarms.
29-9
c. Click Next. Then, set the analysis period and priority, and select the check box
next to Enable the correlation rule.
d. Click Finish.
2 Query relevant alarms.
1. Choose Fault > Browse Current Alarm from the main menu.
2. In the dialog box that is displayed, specify the filter criteria and select the check box next
to Display correlative alarms on the Basic Setting tab page. Click the Alarm Source tab
page to select required alarm sources.
Issue 03 (2010-11-19)
3. Right-click a root or correlative alarm and choose Query Correlative Alarms/Query Root
Alarms from the shortcut menu. The correlative or root alarm of this alarm is displayed.
3 Handle relevant alarms.
l Perform any of the following operations to handle root alarms in the Browse Current
Alarm window.
Right-click a root alarm and choose Details from the shortcut menu. The information
about the generation cause, handling suggestions, and additional information of this alarm
is displayed.
View information in the Handling Suggestion area in the lower pane and locate a fault
according to the handling suggestions and experience.
In the case of the MA5600T or MA5680T, click Click here to show detail
Information to view the information about alarm reference in the Help. Rectify the fault
in a step by step manner.
l Do as follows to handle correlative alarms.
29-11
Right-click a correlative alarm and choose Modify Severity from the shortcut menu.
Then, change the severity level of the alarm to a lower severity level.
If a large number of insignificant alarms are generated, choose Fault > Settings > Mask
Rule from the main menu. Then, set alarm masking policies to reduce redundant alarms.
----End
Issue 03 (2010-11-19)
30 FTTx Remote Fault Diagnosis
About This Chapter
This topic describes the scheme of FTTx remote fault diagnosis implemented through the fault
diagnosis platform of the U2000.
30.1 Diagnosing a Service Fault Through the Fault Diagnosis Platform
This topic describes how to diagnose a service fault through the fault diagnosis platform of the
U2000.
Operation Guide for ONU NE Management 30 FTTx Remote Fault Diagnosis
30-1
30.1 Diagnosing a Service Fault Through the Fault
Diagnosis Platform
This topic describes how to diagnose a service fault through the fault diagnosis platform of the
U2000.
30.1.1 Fault Diagnosis Platform
This topic introduces the fault diagnosis platform.
30.1.2 Application Scope of Fault Diagnosis
This topic provides information about the application scope of the fault diagnosis platform.
30.1.3 Objects of Fault Diagnosis
This topic provides information about the diagnosed objects supported by the fault diagnosis
platform.
30.1.4 Diagnosing the Faults of All Broadband Services
This topic describes how to diagnose the faults of all broadband services.
30.1.5 Performing a Health Check on Broadband Services
This topic describes how to perform a health check on broadband services.
30.1.6 Diagnosing the Faults of All Voice Services
This topic describes how to diagnose the faults of all voice services.
30.1.7 Performing a Health Check on Voice Services
This topic describes how to perform a health check on voice services.
30.1.1 Fault Diagnosis Platform
This topic introduces the fault diagnosis platform.
In the case of a fault, you need to locate the fault point. To make it, you need to check relevant
parts one by one to locate the fault in the past. Locating a particular fault is implemented in a
particular function module. Therefore, you need to switch between GUIs since these GUIs are
not logically organized but independent of each other.
As the FTTx is applied in more and more situations, diagnosing access faults plays a crucial
role.
The fault diagnosis platform is a U2000-based platform for locating and diagnosing the faults
in access devices. The platform depends on the service modules of the U2000, including the test
module, alarm management module, and performance measurement module.
This topic considers the fault diagnosis for broadband services as an example to describe the
functions of the fault locating topology view and the service topology, as shown in Figure
30-1 and Figure 30-2.
Issue 03 (2010-11-19)
Figure 30-1 Fault locating topology view and its functions for broadband services

Figure 30-2 Service topology view and its functions for broadband services
Fault locating topology view: It directly displays the location of a fault, that is, OLT or MDU.
The icon indicates the fault and helps you to quickly and accurately locate the fault source.
You can perform the following operations in this view:
30-3
l Right-click the fault source and choose Locate from the shortcut menu to switch to the NE
Explorer to locate and rectify the fault further.
l Click Switch View to switch to the service topology view.
Service topology view: It directly displays the information about the diagnosed object, such as
the service streams, VLANs, and physical resources. Red indicates that an object is faulty and
green indicates that an object is in the normal state. Therefore, you can quickly and accurately
locate the faulty object. You can perform the following operations in this view:
l Right-click the faulty port and choose Locate from the shortcut menu to switch to the related
port in the NE Explorer. Then, check the port information to locate and rectify the fault
further.
l Click Switch View to switch to the fault locating topology view.
Diagnosed object: A port of the MDU, service flag, and diagnosis type are selected in this area
to reduce the diagnosis scope and improve diagnosis efficiency.
Diagnosis process: The start time and description of each operation in the diagnosis process are
provided in this area.
Diagnosis result and suggestion: You can query the diagnosis result in this area and rectify faults
according to the suggestion. To check whether the fault is rectified, click Restart.
30.1.2 Application Scope of Fault Diagnosis
This topic provides information about the application scope of the fault diagnosis platform.
The fault diagnosis platform can locate and diagnose the faults of the following services:
l Diagnosing the faults of all broadband services
l Performing a health check on broadband services
l Diagnosing the faults of all voice services
l Performing a health check on voice services
Broadband services also support dual ended loop testing (DELT) and single ended loop testing
(SELT).
l SELT is used to locating the faults of a CO, line, or terminal separately and to provide
reliable data for rectifying the faults. SELT is applicable to the scenario wherein the line
quality needs to be simply tested and analyzed when a terminal is not installed but the line
is available.
l DELT is used to locate performance problems of a line, such as low rate, noise, and
attenuation. DELT is used for fault location after services are provisioned or used as a
means of evaluating line quality to check whether the line quality meets the upgrade
requirements during equipment upgrade.
Voice services also support call emulation. Performing tests on voice lines of remote MDUs at
a CO facilitates maintenance on the voice lines. Call emulation is applicable to the following
two scenarios:
l During service provisioning, the call test is performed on all ports to check whether all
ports are in the normal state.
l During fault location, the call or callee emulation test is performed on the test port to locate
the port fault.
Issue 03 (2010-11-19)
30.1.3 Objects of Fault Diagnosis
This topic provides information about the diagnosed objects supported by the fault diagnosis
platform.
The fault diagnosis platform can locate and diagnose the faults in the FTTB networks.
l OLT supported: MA5600T, MA5680T, and MA5603T
l MDU supported: all MDUs supported by NMSs
30.1.4 Diagnosing the Faults of All Broadband Services
This topic describes how to diagnose the faults of all broadband services.
Procedure
1 Choose Fault > FTTx Fault Diagnosis from the main menu.
2 In the left pane of the Fault Diagnosis window, set Device Name, Diagnosed object, and
Service flag. In addition, choose the corresponding fault symptom from the navigation tree.
3 Click Start Diagnosis.
----End
Result
The diagnosis result is displayed after the diagnosis is complete.
30-5
30.1.5 Performing a Health Check on Broadband Services
This topic describes how to perform a health check on broadband services.
Procedure
----End
Issue 03 (2010-11-19)
Result
CAUTION
A health check on broadband services is to collect data. During the check, the diagnosis continues
even if a fault is detected.
30.1.6 Diagnosing the Faults of All Voice Services
This topic describes how to diagnose the faults of all voice services.
Procedure
30-7
----End
Result
30.1.7 Performing a Health Check on Voice Services
This topic describes how to perform a health check on voice services.
Issue 03 (2010-11-19)
Procedure
----End
Result
CAUTION
A health check on voice services is to collect data. During the check, the diagnosis continues
even if a fault is detected.
30-9
Issue 03 (2010-11-19)
31 Monitoring Real-Time Performance
This topic describes how to view real-time performance data and comprehensively manage
performance, thus monitoring the real-time performance of each NE.
Context
The following considers the EPON UNI port as an example to describe how to monitor the real-
time performance.
Procedure
1 In the Main Topology, double-click the required device in the Physical Root navigation tree,
or right-click the required device and choose NE Explorer from the shortcut menu.
3 In the dialog box that is displayed, click Find to display the records of specified EPON UNI
ports.
4 Right-click an EPON UNI port and choose Performance > Real time monitoring from the
shortcut menu.
5 In the Configure Real Time Performance window, select the indicator to be collected and click
OK.
NOTE
A maximum of 20 indicators can be selected at a time.
Operation Guide for ONU NE Management 31 Monitoring Real-Time Performance
31-1
6 In the window that is displayed, view the real-time performance statistics of the EPON UNI
port.
----End
31 Monitoring Real-Time Performance
Issue 03 (2010-11-19)
32 Quick Cutover of FTTx Services
About This Chapter
This topic describes the solution to quick cutover of FTTx services.
Background
xPON ports on the existing network are not pluggable. When an xPON port or xPON card is
faulty, or the network is adjusted, batch migration is implemented only by deleting the xPON
port or adding all MDU data to the new xPON port (or new xPON card). This results in complex
configuration data and long interruption of services.
To deal with this problem, the U2000 provides a service cutover mode, where MDUs connected
to the faulty xPON port of a device are cut over to another xPON port of the same device in
batches. This implements simple and quick cutover.
Unique Benefits
l The service cutover is simple and quick. User services can be recovered rapidly after an
interruption.
l The on-site construction is simple. Only the optical fiber connected to the source xPON
port needs to be migrated to the destination xPON port.
Range and Restrictions
1. Only the service cutover inside a device is supported.
2. Only the port-level service cutover is supported and the card-level service cutover is not
supported.
3. Different cards support different service configurations. Therefore, make sure that the cards
where the source port and destination port reside are of the same type before the service
cutover.
4. The service port ID changes after cutover.
5. The configuration of the source port is cleared after cutover.
32.1 Cutting Over Services on a GPON Port
This topic describes the flowchart and procedure for cutting over services on a GPON port.
Operation Guide for ONU NE Management 32 Quick Cutover of FTTx Services
32-1
32.2 Cutting Over Services on EPON Ports
This topic describes the flowchart and procedure for cutting over services on EPON ports.
Issue 03 (2010-11-19)
32.1 Cutting Over Services on a GPON Port
This topic describes the flowchart and procedure for cutting over services on a GPON port.
Guideline
When backing up a GPON port on the OLT, you need to cut over services on the GPON port.
If the working GPON port is faulty, you can cut over ONU services to a specified backup GPON
port.
l The service cutover menu is not required for an activated and online GPON port.
l A particular service card may support a particular service. Hence, the source port and
destination port in service cutover must be on the cards of the same type. In addition, you
need to ensure that card configuration such as the CAR mode must be the same.
l Multicast services of cascading ports can be cut over.
l ONU names can be cut over. Rules for cutting over an ONU name are as follows:
1. If a source ONU name is generated by default, do not copy the name. The destination
ONU name is also generated by default.
2. If a source ONU name is not generated by default or you add characters to a source
ONU name generated by default, copy the source ONU name in cutover.
Cutover Flowchart
Figure 32-1 shows the flowchart for cutting over GPON port services.
Figure 32-1 Flowchart for cutting over GPON port services

32-3
Procedure
1. Insert one end of an optical fiber into the destination GPON port. The other end of the fiber
is connected to the source GPON port.
3. Choose GPON > GPON UNI Port from the navigation tree.
4. On the GPON UNI Port tab page, specify the filter criteria or click to display the
required GPON UNI ports.
5. In the information list, right-click the required port and choose Service Handover from
the shortcut menu.
6. In the Service Handover dialog box, select the destination port, to which services are cut
over.
Table 32-1 Parameters required for modifying the attributes of a GPON UNI port
Name Definition:
device to which the port
belongs.
-
Destination Port Definition:
Indicates the backup GPON
port.
-

CAUTION
This operation is irreversible. The operation is successful only when the data on the NE is
the same as the NE data on the U2000. It is recommended that you synchronize the NE
data before performing this operation.
7. Click OK.
8. In the Confirm dialog box, click Yes.
Issue 03 (2010-11-19)
9. Wait until service data replication is complete.
32.2 Cutting Over Services on EPON Ports
This topic describes the flowchart and procedure for cutting over services on EPON ports.
Guideline
When backing up an EPON port on the OLT, you need to cut over services on the EPON port.
If the working EPON port is faulty, you can cut over ONU services to a specified backup EPON
port.
l The service cutover menu is not required for an activated and online EPON port.
l A particular service card may support a particular service. Hence, the source port and
destination port in service cutover must be on the cards of the same type. In addition, you
need to ensure that card configuration such as the CAR mode must be the same.
l Multicast services of cascading ports can be cut over.
l ONU names can be cut over. Rules for cutting over an ONU name are as follows:
1. If a source ONU name is generated by default, do not copy the name. The destination
ONU name is also generated by default.
2. If a source ONU name is not generated by default or you add characters to a source
ONU name generated by default, copy the source ONU name in cutover.
Cutover Flowchart
Figure 32-2 shows the flowchart for cutting over EPON services.
32-5
Figure 32-2 Flowchart for cutting over EPON services

Procedure
1. Insert one end of an optical fiber into the destination EPON port. The other end of the fiber
is connected to the source EPON port.
2. In the Main Topology, double-click the required device in the Physical Root, or right-click
the required device and choose NE Explorer from the shortcut menu.
3. Choose EPON > EPON UNI Port from the navigation tree.
4. On the EPON UNI Port tab page, enter the query condition or click to display the
required EPON UNI ports.
5. In the information list, right-click the required port and choose Service Handover from
the shortcut menu.
6. In the Service Handover dialog box, select the destination port for service cutover.
Issue 03 (2010-11-19)
Table 32-2 Parameters required for modifying the parameters of an EPON UNI port
Name Definition:
device to which the port
belongs.
-
Destination Port Definition:
Indicates the standby EPON
port.
-

CAUTION
Service cutover is irreversible. Ensure the consistency in the NE data and the U2000 data
so that you can cut over services successfully. It is recommended that you synchronize NEs
before service cutover.
7. Click OK.
8. In the Confirm dialog box, click Yes.
9. Wait until the duplication of service data is complete.
32-7
33 Bulk Configuring in Command Line
Script Files and Sending the Script Files to NEs
During the maintenance of NEs, the NMS supports the bulk configuration of NE services in a
command line script file. In this manner, service data of multiple NEs can be modified quickly,
which improves the operation and maintenance efficiency. The bulk configuration of services
in a command line script can be achieved with two methods: importing the command line
configuration script sheet or using the configuration script management function. With the
former method, you need to import the Command Line Configuration Script Sheet
Profile.xls to the NMS. With the latter 2, you need to add configuration scripts on the NMS and
send the scripts to NEs.
Context
l The command script profiles transferred in the File mode and Telnet mode have the same
format but different contents.
l The File mode is preferred when lots of commands are contained in the command line script
profiles. In this manner, the interactions between the NMS and NEs is reduced, which
improves the execution efficiency.
l Currently, the MA5600V800R008 and MxUV800R308 support the File mode.
Procedure
l Method 1: Importing configuration script sheet.
NOTE
The path to the sheet is as follows:
l Windows-based server: X:\U2000\client\template\MDU Pre-Deploy\zh\Command Line
Configuration Script Sheet Profile.xls, where x indicates the disk name, such as D, E, and F.
l Solaris-based server: /opt/U2000/client/template/MDU Pre-Deploy/zh/Command Line
Configuration Script Sheet Profile.xls
When the NEs need to load different script files, do as follows:
1. Fill in Command Line Configuration Script Sheet Profile.xls, including Device IP
Address, Execute Mode, User Name, Password, and Command Line
Configuration Script Filename.
33 Bulk Configuring in Command Line Script Files and
Sending the Script Files to NEs
33-1
2. Choose Configuration > FTTx Service Pre-Deployment > Import Configuration
Script Sheet from the main menu.
3. In the dialog box that is displayed, select Command Line Configuration Script
Sheet Profile.xls and click OK.
l Method 2: Using the configuration script management function.
NOTE
When the same script profiles are loaded to NEs with the same user name and password, or when
Execute is set to SSH, you are recommended to do as follows:
1. Choose Configuration > FTTx Service Pre-Deployment > Configuration Script
Management from the main menu.
3. In the Add Configuration Script dialog box, click add. In the Select Configuration
Script dialog box, select the required command line script profile and click OK.
Issue 03 (2010-11-19)
4. Click OK.
5. Right-click a configuration script and choose Send To Device from the shortcut menu.
6. In the dialog box that is displayed, select the required NEs and click Next.
7. In the dialog box that is displayed, enter the user name and password of the NEs.
8. Click OK.
----End
Result
On the Scheduling Center tab page, select a task and click the Job Information tab. On the
Job Information tab page, right-click the result of the task and choose Show Config Data from
the shortcut menu. The configuration data is displayed.
33-3
34 Remote Maintenance Guide
About This Chapter
This topic describes the tasks of maintaining the ONU software through the U2000, and the
reference standard, operation guide, exception handling, and command reference of the tasks.
34.1 Monitoring Critical and Major Alarms of NEs
It is recommended that you check whether unhandled critical and major alarms persist in the
system every day. This operation helps timely detect and solve the problems that may occur
when the NEs are running.
34.2 Measuring the CPU Usage of a Board
It is recommended that you measure the CPU usage rat of each board once ever week to rectify
the fault of the board whose CPU usage is not in the normal range. This helps you to learn the
running status of the boards in time, rectify the capacity fault, and prevent the potential security
risks (such as the DoS attack) during the running of the boards.
34.3 Measuring the Performance of an Upstream Ethernet Port
It is recommended that you measure the performance of the upstream Ethernet port once every
week. This operation ensures that the services on the upstream Ethernet port are normal and
reliable.
34.4 Measuring the Usage of NE Resources
This topic describes how to measure the resource usage of the NE. You can query the NE
information, such as the number, software version, type, MAC address, physical location, and
running status.
34.5 Checking the NE User Level
It is recommended that you check whether the allocation of the level of the user who configures
NEs is correct once every month. This operation ensures that the allocated user level can be the
same as the user level that is planned and deployed, and that the user level meets the requirement
of NE maintenance.
34.6 Changing the Password of an NE User
To ensure the security of an account, it is recommended that you change the password of an NE
user periodically instead of using the same password for a long period during maintenance.
34.7 Saving, Backing Up, and Restoring NE Data
Operation Guide for ONU NE Management 34 Remote Maintenance Guide
34-1
The topic describes how to save and back up NE data and restore NE data when an NE fails to
be upgraded.
Issue 03 (2010-11-19)
34.1 Monitoring Critical and Major Alarms of NEs
It is recommended that you check whether unhandled critical and major alarms persist in the
system every day. This operation helps timely detect and solve the problems that may occur
when the NEs are running.
Prerequisite
The hardware for monitoring NE alarms must be configured, such as an environment monitoring
unit (EMU) and sensors.
Context
l After setting the default profile, choose Fault > Browse Current Alarm from the main
menu to display the required alarm information directly. For information on how to set and
change the default profile, see Setting the Default Profile.
l You can set the policies for defining alarms according to the extent that the alarms are
concerned and the actual requirement, including setting alarm names, function
classifications, and alarm severity. For details, see Configuring the Policy of Redefining
Alarms and Events.
l A great number of alarms may be generated during the repair, test, and deployment of
devices. In this case, you can mask the alarms that are irrelevant. In this manner, the alarms
are not displayed or saved on the U2000. For details, see Configuring the Policy of Masking
Alarms and Events.
Reference Standard
You can determine the alarm severity according to colors of the alarm legends. Generally, the
critical and major alarms should not persist in the system. The following table lists the alarm
legends and provides the meanings of the legends.
Legend Color Alarm Severity
Red Critical
Orange Major
Yellow Minor
Blue Warning

Procedure
1 Choose Fault > Browse Current Alarm from the main menu. Then, the Filter dialog box is
displayed.
34-3
NOTE
l If you already set the default template for the current alarms, the alarms that meet the default template
criteria are directly displayed, without the displaying of the Filter dialog box.
l You can choose Template > New in the lower pane to create an alarm profile and set the device alarm
parameters. You can also choose Template > Open to query the device alarms by selecting the new
alarm profile.
2 On the Basic Setting tab, set the parameters required for querying alarms, such as the alarm
name, severity, status, and type. These parameters are optional.
3 On the Alarm Source tab, set the alarm source information for querying alarms. In the Select
Mode area, set the mode for filtering alarms.
l If All objects is selected, it indicates that alarms are not filtered and all alarms of the alarm
source are queried.
l If Custom is selected, click Add to filter the concerned alarm source according to Object
below NE and Object Group.
4 Click OK to display the required critical and major alarms.
----End
Exception Handling
l Select a fault alarm that is not recovered. The alarm information is displayed in Alarm
Details in the lower pane and the cause of the alarm and handling suggestions are displayed
in Handling Suggestion. Handle the alarm according to the suggestions.
Issue 03 (2010-11-19)
l Record the critical alarms that occur frequently at recent time and their recovery
information. Handle the alarms according to the cause and handling suggestions, and
analyze potential risks that may exist in the system.
l If the fault persists, contact Huawei technical support engineers. For details, see How to
Obtain Technical Support from Huawei.
NOTE
For an alarm that is handled successfully, it is recommended that you record the detailed handling measures,
which helps locate and troubleshoot the similar faults that occur. To enter the maintenance experience, select
the alarm, right-click, and then choose Experience.
Related Commands
Query the
alarm history
display alarm history User mode
Query the
basic
information
about alarms
display alarm list User mode
Query the
alarm
configuratio
n
display alarm configuration User mode
Query the
alarm
statistics
display alarm statistics User mode
Query the
information
about the
existing
alarms in the
system
display alarm active Privilege mode

34.2 Measuring the CPU Usage of a Board
It is recommended that you measure the CPU usage rat of each board once ever week to rectify
the fault of the board whose CPU usage is not in the normal range. This helps you to learn the
running status of the boards in time, rectify the capacity fault, and prevent the potential security
risks (such as the DoS attack) during the running of the boards.
Prerequisite
l You must have Create a Performance Measurement Task.
l If the attributes of NE resources change, you need to perform synchronize to keep the data
of the NE and performance management module the same and then perform query .
Otherwise , the collection of performance data is abnormal. The procedure of synchronizing
information is as follows:
34-5
1. On the Main Topology tab, select an NE from the Physical Root navigation tree,
right-click, and then choose Synchronize NE Data.
2. Choose Performance > Performance Monitor Management from the main
menu. In the Performance Monitoring Management tab, right-click the monitoring
instance, and select Synchronization Resource.
Context
Only the control boards and service boards support this operation.
Reference Standard
l The CPU usage ranges from 0% to 100%. The CPU usage of a board that runs normally
does not exceed 70%.
l The high CPU usage of a board occurs only when the board data is being written to the
flash memory of the control board or is being saved. The high CPU usage usually lasts less
than 60s.
Procedure
1 Choose Performance > Browse History Performance Data from the main menu.
2 Choose Performance Management > Card > Access NE Card > Board Health from the
navigation tree.
3 Click Filter. The dialog is displayed. The resources and the corresponding indicators associated
with the selected resources is displayed.
NOTE
If the query profile is created, click Template > Query by Template. In the dialog box that is displayed, select
the required profile, and then import the profile to query the performance statistics.
4 In the Show Type drop-down list, select the graph type as Single Resource Graph.
5 In the area, select the NE type. In the Available Resources area in the right pane, select the
resource name.
6 Click , to move the resources to the Selected Resources area.
7 Click in the right side of the window to expand the Option area box.
8 In the buttom of the pane, select the indicators for the selected resources.
NOTE
Maximum 10 indicators can be selected at a time.
9 Select the Option check box and in the Time drop-down list, select the time period.
Time period can be set as Recent 1 hour, Recent 12 hours, Recent 1 day, Recent 1 week, Recent
1 month, Recent 1 year, or Custom Define.
1. Select Custom Define, and click to select the start and end time period. The maximum
time period can be 1 year.
2. Click OK.
Issue 03 (2010-11-19)
NOTE
Start time period should be earlier than end time period.
10 In the Granularity drop-down list, select the granularity period.
Based on the time period, granularity can be one of the following:
l Recent 1 hour: 5 minutes, 10 minutes, 15 minutes, and 30 minutes.
l Recent 12 hours: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour.
l Recent 1 day: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour.
l Recent 1 week: 1 hour, 1 day.
l Recent 1 month: 1 day.
l Recent 1 year: 1 day.
l Custom Define: 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour and 1 day.
NOTE
For custom define, the granularity can be selected based on the time period selected.
11 Optional: Click Advance, and set the filter conditions for the indicators.
1. In the Logic Type drop-down list, select the logic type as AND or OR.
2. Select the Operator and set the Value for the corresponding indicators.
Operator can be set as =, <, >, <=, >=, or !=.
3. Click OK.
12 Optional: Click Save as Query Template to save a new or an existing template as a new
template.
13 Optional: Click Cancel to cancel the operation.
14 Click OK to get the performance data based on the filter conditions set for one graph one
resource.
----End
Exception Handling
l If the CPU usage of a board is temporarily over-high, there is no need to proceed.
l If the CPU usage of a board is frequently over-high, check the following items:
Whether the data configuration of the device is proper. If the data configuration is
improper, it is recommended that you decrease the number of users or increase the
capacity of the system.
Whether the networking is proper and whether a larger number of broadcast packets are
generated due to the existing loop networks.
Whether the DoS attack exists, which may lead to the high CPU usage. The solution is
to enable the anti-DoS attack function.
34-7
Related Commands
Query the
CPU usage of
a board
display cpu Privilege mode

34.3 Measuring the Performance of an Upstream Ethernet
Port
It is recommended that you measure the performance of the upstream Ethernet port once every
week. This operation ensures that the services on the upstream Ethernet port are normal and
reliable.
Prerequisite
l You must have Create a Performance Measurement Task.
l If the attributes of NE resources change, you need to perform synchronize to keep the data
of the NE and performance management module the same and then perform query .
Otherwise , the collection of performance data is abnormal. The procedure of synchronizing
information is as follows:
1. On the Main Topology tab, select an NE from the Physical Root navigation tree,
right-click, and then choose Synchronize NE Data.
2. Choose Performance > Performance Monitor Management from the main
menu. In the Performance Monitoring Management tab, right-click the monitoring
instance, and select Synchronization Resource.
Reference Standard
In the statistics of the upstream Ethernet port, a small number of frames with cyclical redundancy
check (CRC) errors and a few packet loss errors exist and the traffic transmission is stable.
Procedure
1 Choose Performance > Browse History Performance Data from the main menu.
2 Choose Performance Management > Port > Access Ethernet Port > Ethernet Port from the
navigation tree.
3 Click Filter. The dialog is displayed. The resources and the corresponding indicators associated
with the selected resources is displayed.
NOTE
If the query profile is created, click Template > Query by Template. In the dialog box that is displayed, select
the required profile, and then import the profile to query the performance statistics.
4 In the Show Type drop-down list, select the graph type as Single Resource Graph.
Issue 03 (2010-11-19)
5 Click in the right side of the window to expand the Available Resources area box.
6 In the area, select the NE type. In the Available Resources area in the right pane, select the
resource name.
7 Click , to move the resources to the Selected Resources area.
8 Click in the right side of the window to expand the Option area box.
9 In the buttom of the pane, select the indicators for the selected resources.
NOTE
Maximum 10 indicators can be selected at a time.
10 Select the Option check box and in the Time drop-down list, select the time period.
Time period can be set as Recent 1 hour, Recent 12 hours, Recent 1 day, Recent 1 week, Recent
1 month, Recent 1 year, or Custom Define.
1. Select Custom Define, and click to select the start and end time period. The maximum
time period can be 1 year.
2. Click OK.
NOTE
Start time period should be earlier than end time period.
11 In the Granularity drop-down list, select the granularity period.
Based on the time period, granularity can be one of the following:
l Recent 1 hour: 5 minutes, 10 minutes, 15 minutes, and 30 minutes.
l Recent 12 hours: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour.
l Recent 1 day: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour.
l Recent 1 week: 1 hour, 1 day.
l Recent 1 month: 1 day.
l Recent 1 year: 1 day.
l Custom Define: 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour and 1 day.
NOTE
For custom define, the granularity can be selected based on the time period selected.
12 Optional: Click Advance, and set the filter conditions for the indicators.
1. In the Logic Type drop-down list, select the logic type as AND or OR.
2. Select the Operator and set the Value for the corresponding indicators.
Operator can be set as =, <, >, <=, >=, or !=.
3. Click OK.
13 Optional: Click Save as Query Template to save a new or an existing template as a new
template.
14 Optional: Click Cancel to cancel the operation.
34-9
15 Click OK to get the performance data based on the filter conditions set for one graph one
resource.
----End
Exception Handling
l If a large number of frames with CRC errors exist or the traffic on an Ethernet port is low
in a certain period, check whether the line quality is poor or whether any Ethernet port of
the device is faulty.
l If a large number of packets are lost, check whether the traffic suppression function is
enabled.
l If the fault persists, replace the port to prevent the communication failure caused by the
port fault.
Related Commands
Query the statistics of an
Ethernet port
display port statistics
ETH mode, GIU mode, SCU
mode

34.4 Measuring the Usage of NE Resources
This topic describes how to measure the resource usage of the NE. You can query the NE
information, such as the number, software version, type, MAC address, physical location, and
running status.
Prerequisite
The NE must be added to the U2000 successfully.
Procedure
1 Choose Inventory > Physical Inventory > NE from the main menu.
2 Click the NE Statistics tab. Select NE Type, Software Version, NE Type+Software
Version, or Customize from the Statistics Type drop-down list.
1. Select NE Type from the Statistics Type drop-down list and click Count. The number of
NEs of different types is displayed in the information list in the lower pane.
2. Select Software Version from the Statistics Type drop-down list, and click Count. The
number of NEs of different software versions is displayed in the information list in the
lower pane.
3. Select NE Type+Software Version from the Statistics Type drop-down list and click
Count. The number of NEs of different software versions corresponding to different NE
types is displayed in the information list in the lower pane.
4. Select Customize. In the Customize NE Statistics Type dialog box, click New. In the
New Customize NE Statistics Type dialog box, enter the name of the measurement item
Issue 03 (2010-11-19)
to be customized in the Custom Name text box in the Customize NE Statistics Type area.
In the Basic Item area, select the measurement item to be customized, click to
add the selected measurement item to the Combined Item area. Then, click OK.
5. Click OK.
3 Click next to Statistics Scope. In the dialog box that is displayed, select the NE to be
measured, and then click OK.
4 Select the required record from the NE list, and then you can perform the following operations:
l Choose Save As. In the dialog box that is displayed, set Start Row and End Row, and then
click next to File Name. In the dialog box that is displayed, set File Name, File
Type and Encoding, and then click Save. Click OK in the Save Options dialog box to
save the report to the specified path.
NOTE
The reports can be saved as txt, xls, html and xls files.
l Choose Print. In the dialog box that is displayed, set Start Row and End Row, and then
click OK to print the report.
----End
Command Reference
Query the details of a board
(After performing an
operation on a board, you can
query the details of the board,
such as the slot number,
name, status, daughter board
information, port
information and online
status.)
display board User mode

34.5 Checking the NE User Level
It is recommended that you check whether the allocation of the level of the user who configures
NEs is correct once every month. This operation ensures that the allocated user level can be the
same as the user level that is planned and deployed, and that the user level meets the requirement
of NE maintenance.
Context
Users are divided into four levels by rights, that is, the common user, operator, administrator,
and superuser.
l A common user can perform basic system operations and simple query operations.
l An operator can perform basic configurations for the device and services.
34-11
l An administrator can perform all configurations. The administrator is responsible for
maintaining the device, user account, and rights to manage devices.
l The superuser is unique in the system. Being the top-level user in the system, the superuser
can add an administrator and has all the rights of the administrator.
Reference Standard
The level of the user who configures NEs is the same as the level that is planned and deployed,
and can meet the requirement of NE maintenance. The user rights are allocated properly.
Procedure
1 Choose Administration > NE Security Management > LCT User Management from the
main menu.
2 In the LCT Management window, click the NE User tab.
3 Select the required device type from the Device Type drop-down list. The information about all
the users of the selected device type is displayed in the list. Then, click Filter to display the NE
users that meet the filtering criteria.
4 Query the level of the NE user in the Level column in the list.
----End
Exception Handling
l If the allocation of the NE user level is improper, right-click the record to be queried in the
list on the NE User tab, and then select Configure to modify the NE user level.
NOTE
Only the user with the administrator or higher-level right can modify the NE user level.
Related Commands
Query the NE
user level
display terminal user User mode
Modify the NE
user level
terminal user level Privilege mode

34.6 Changing the Password of an NE User
To ensure the security of an account, it is recommended that you change the password of an NE
user periodically instead of using the same password for a long period during maintenance.
Prerequisite
You must be an NMS user with the Security Manager User authority or higher.
Issue 03 (2010-11-19)
Reference Standard
You can log in to an NE by using the new password.
Procedure
1 Choose Administration > NE Security Management > LCT User Management from the
main menu.
2 Click the NE User tab, and then select the required device type from the Device Type drop-
down list. All the users on this type of devices are displayed in the user list. Click Find to display
the required users.
3 Select one or more records from the user list, right-click, and then choose Set Password.
4 In the Set Password dialog box as shown in the following figure, set a new password.
NOTE
The password consists of 1 to 15 characters.
5 Click OK.
----End
Exception Handling
l If the password fails to be changed, the U2000 displays a message indicating the failure.
In this case, check whether the password is correct according to the message.
l If the problem persists, contact Huawei technical support engineers. For information on
how to contact Huawei technical support engineers, see How to Obtain Technical Support
from Huawei.
Related Commands
Change the password of
an NE user
terminal user password Privilege mode

34-13
34.7 Saving, Backing Up, and Restoring NE Data
The topic describes how to save and back up NE data and restore NE data when an NE fails to
be upgraded.
34.7.1 Saving and Backing Up the NE Data Periodically
The DC saves and backs up data periodically according to the default policy or user-defined
policy and thus helps to restore and load the data in future.
34.7.2 Saving and Backing Up NE Data Immediately
The DC can save and back up NE data periodically or immediately to meet the requirements in
different scenarios.
34.7.3 Checking the Backup of the NE Configuration Data
It is recommended that you check whether the NE configuration data is backed up successfully
once every week. This operation helps you to restore the recent system data in time in the case
that an expected fault occurs in the system. Thus, the impact on users is minimized.
34.7.4 Restoring the NE Data Immediately
The DC can restore the history backup data after a NE is selected. This operation ensures that
the NE data can be restored if the system upgrade fails or any problems occur. Thus, the system
can be restored to the normal state.
34.7.1 Saving and Backing Up the NE Data Periodically
The DC saves and backs up data periodically according to the default policy or user-defined
policy and thus helps to restore and load the data in future.
Saving and Backing Up the NE Data by Using the Default Policy
This topic describes how to save and back up the NE data periodically by using the default policy.
Hence, you can save and back up the NE data at a fixed time, which facilitates the restoring and
loading of the NE data.
Impact on the System
The backup has certain impact on the running rate of the NE. Therefore, it is recommended that
you back up the NE data when the NE carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
l The DCServer process runs in the normal state.
l The communication between the NE and the U2000 must be in the normal state.
l The TFTP/FTP/SFTP service must be configured and run in the normal state. For details,
see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring
the FTP, SFTP, or TFTP Service (Solaris) and 1.1.3 Configuring the FTP, SFTP, or
TFTP Service (Linux).
Procedure
1 Choose Administration > NE Software Management > Default Policy from the main menu.
Issue 03 (2010-11-19)
2 Click the Backup Policy tab, and then configure the backup policy of the NE, as shown in the
following figure.
NOTE
l If Policy Status is set to Running, the DC backs up NEs at the specified time.
l If Policy Status is set to Suspended. the DC does not back up NEs even if the policy period reaches the
specified time, and the policy is still suspended.
3 Click the Save Policy tab, and then configure the save policy of the NE, as shown in the following
figure.
34-15
NOTE
l If Policy Status is set to Running, the DC saves NEs at the specified time.
l If Policy Status is set to Suspended, the DC does not save NEs even if the policy period reaches the specified
time, and the policy is still suspended.
4 Click OK to complete the configurations of the save and backup policies.
5 In the Operation Result dialog box, click OK.
----End
Related Commands
Configure the
conditional backup
function of the
automatic backup
auto-backup condition Global config mode
Configure the
periodical backup
function of the
automatic backup
auto-backup period Global config mode

Issue 03 (2010-11-19)
Saving and Backing Up the NE Data by Using the Customized Policy
This topic describes how to save and back up the NE data periodically by using the customized
policy. Hence, you can save and back up the required NE data at a fixed time, which facilitates
the restoring and loading of the NE data.
The backup has certain impact on the running rate of the NE, therefore, it is recommended that
you back up the NE data when the NE carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
Context
You can configure the save and backup policies for a single NE or for multiple NEs
simultaneously.
Procedure
1 Choose Administration > NE Software Management > User-Defined Policy from the main
menu. The User-Defined Policy dialog box is displayed.
2 Select the NE type and NE version to be configured with the save and backup policies as required.
1. Select the required NE type from the NE Type drop-down list.
2. Optional: Select the required NE version from the NE Version drop-down list.
3. Choose one or multiple NEs to be configured with the save and backup policies from the
navigation tree under the NE Version drop-down list.
3 Click Next and the User-Defined Policy dialog box is displayed.
4 Click the Backup Policy tab, and then configure the backup policy of the NE, as shown in the
following figure.
34-17
NOTE
l If Policy Status is set to Running, the DC backs up NEs at the specified time.
l If Policy Status is set to Suspended, the DC does not back up NEs even if the policy period reaches the
specified time, and the policy is still suspended.
5 Click the Save Policy tab, and then configure the save policy of the NE, as shown in the following
figure.
Issue 03 (2010-11-19)
NOTE
l If Policy Status is set to Running, the DC save NEs at the specified time.
l If Policy Status is set to Suspended, the DC does not save NEs even if the policy period reaches the specified
time, and the policy is still suspended.
6 Click Finish to complete the configurations of the save and backup policies.
7 In the Operation Result dialog box, click OK.
----End
Related Commands
Configure the
conditional backup
function of the
automatic backup
auto-backup condition Global config mode
34-19
Configure the
periodical backup
function of the
automatic backup
auto-backup period Global config mode

34.7.2 Saving and Backing Up NE Data Immediately
The DC can save and back up NE data periodically or immediately to meet the requirements in
different scenarios.
Saving the NE Data Immediately
Through the DC, you can save the related NE data periodically. You can also save the NE data
immediately. This meets the requirements of different application scenarios.
Prerequisite
Context
NOTE
The manual saving task cannot be interrupted after it is started.
Procedure
1 Choose Administration > NE Software Management > NE Data Backup/Restoration from
the main menu.
2 Click , and expand the ONU NE node from the NE navigation tree.
l If a certain NE type is selected, all the NEs of this type are displayed in the NE list in the
NE View window in the right pane.
l If a NE version is selected in a certain NE type node, all the NEs of this version are displayed
in the NE list in the NE View window in the right pane.
3 Optional: To locate a specific NE, click Find in the NE View window in the right pane.
4 Select one or multiple records from the NE list in the NE View window in the right pane, right-
click, and then choose Save.
NOTE
You can save the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box that is displayed, select one or multiple records need to be saved, and then click
Start to save the NE data.
6 The saving process and the operation results are displayed in the Operation Status of the list.
----End
Issue 03 (2010-11-19)
Related Commands
Save the current
database file and
configuration file of the
system
save Privilege mode
Save the current
database file of the
system
save data Privilege mode
Save the current
configuration file of the
system
save configuration Privilege mode

Backing Up the NE Data Immediately
Through the DC, you can back up the NE data periodically. You can also back up the NE data
immediately. This meets the requirements of different application scenarios.
The backup has certain impact on the running rate of the NE. Therefore, it is recommended that
you back up the NE data when the device carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
l The communication between the device and the U2000 must be in the normal state.
l To back up the NE data to the U2000 client, the SFTP server must be configured and the
SFTP service must be in the running state.
Context
NOTE
After a manual backup task is started, it cannot be stopped.
Procedure
the main menu.
34-21
4 Select one or more records from the NE list in the NE View window in the right pane, right-
click, and then choose Backup or click Backup in the lower pane.
NOTE
You can back up the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box as shown in the following figure, set the parameters related to backing up the
NE data immediately.
NOTE
To back up the data for multiple NEs of the same type, click Same as first Content Type in the upper
right corner of the Backup dialog box. In this manner, you can configure the backup file with the same
content for multiple NEs at a time rather than configure the backup files one by one.
6 Click Start to back up the NE data.
7 The backup process and the operation results are displayed in the Operation Status of the list.
If the backup is successful, the information about the backup file is displayed on the Backup
Information tab.
----End
Related Commands
Back up the
database file
manually
backup data Privilege mode
Issue 03 (2010-11-19)
Back up the
configuratio
n file
manually
backup configuration Privilege mode
Back up the
data to the
backup
server
manually
auto-backup manual Global config mode

34.7.3 Checking the Backup of the NE Configuration Data
It is recommended that you check whether the NE configuration data is backed up successfully
once every week. This operation helps you to restore the recent system data in time in the case
that an expected fault occurs in the system. Thus, the impact on users is minimized.
Prerequisite
The parameters for periodically backing up the NE data must be set.
NOTE
After the backup policy is configured successfully, you need not manually back up data every day and need
only to check the backup once every week.
Context
l The ONU supports the saving and backing up of the database file. This ensures that the
system can be restored in the case that an expected fault occurs in the system. For
information on how to restore the NE data, see Restoring the NE Data Immediately.
l The U2000 supports the function of transferring the database file of the ONU in the FTP/
TFTP/SFTP mode. To back up the data, you can upload the file saved on the ONU to a
specified file server. To restore the data, you can download the file saved on the specified
file server to the ONU.
Reference Standard
No backup failure is recorded in the log, and the backup database file exists in the specified path.
Procedure
1 Choose Administration > NE Software Management > NE Software Log Management from
the main menu.
2 In the NE Software Log Management window, click Filter. The Filter Log dialog box is
displayed.
3 In the Filter Log dialog box, select Backup from the Operation Type drop-down list, and then
set other filtering criteria to display the required log that records backup operations (the filtering
criteria items are optional), as shown in the following figure.
34-23
4 Click OK. The information about the backup operation logs is displayed in the information list.
You can determine whether the database is backed up successfully by viewing the Result column
in the information list. If Success is displayed in the Result column, view the directory for saving
backup files in the File Path column.
----End
Exception Handling
l If Failure is displayed in the Result column, take measures according to the information
displayed in the Details column. If the data is backed up in the FTP/TFTP/SFTP mode,
check the following items:
Whether you can ping through the IP address of the maintenance network port on the
control board or the IP address of a layer 3 interface of a VLAN from the FTP/TFTP/
SFTP server. That is, check whether the communication between the ONU and the
U2000 is normal.
Whether the entered IP address of the FTP/TFTP/SFTP server is correct.
Whether the FTP/TFTP/SFTP program is running on the backup server.
Whether the path in the FTP/TFTP/SFTP program is set correctly.
l If the automatic backup fails, back up the data manually. In addition, locate the cause of
the backup failure and modify the settings according to the cause.
Related Commands
Query user
logs
display log User mode
Issue 03 (2010-11-19)
Query the file
server
display file-server Privilege mode
Configure the
file server
file-server Privilege mode

34.7.4 Restoring the NE Data Immediately
The DC can restore the history backup data after a NE is selected. This operation ensures that
the NE data can be restored if the system upgrade fails or any problems occur. Thus, the system
can be restored to the normal state.
Prerequisite
l The communication between the NE and the U2000 must be in the normal state, and there
must be no packet loss in the network.
l The NE data must be backed up to the NMS server.
NOTE
To copy the backup files that contain the NE data to another path, copy the directory where the backup
files exist. If you copy only a certain backup file, the file is invalid when the NE data is recovered.
l To restore the NE data by selecting the history file on the U2000 client, the SFTP server
must be configured and the SFTP service must be in the running state.
Context
NOTE
After a manual restoring task is started, it cannot be stopped.
Procedure
the main menu.
4 Select one or multiple records from the NE list in the NE View window in the right pane, right-
click, and then choose Recover or click Recover in the lower pane.
34-25
NOTE
You can restore the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box that is displayed, set the parameters related to restoring the NE data
immediately.
NOTE
l The activation types are No Reboot and With Service Interruption.
l No Reboot: Start the recover operation without rebooting the NE.
l With Service Interruption: If the operation is successful, the service of the selected NE(s) is
interrupted.
l The activation types of the SRG devices are No Reboot, Immediate Reboot and Scheduled Reboot
With Service Interruption.
l To restore the data for multiple NEs of the same type, click Same as first Activate Type in the upper
right corner of the Recover dialog box. In this manner, you can configure multiple NEs with the same
activation type at a time rather than restore the NE data one by one.
6 Click Start to restore the history backup data of the selected NE.
7 In the Operation Confirmation dialog box, click Yes.
8 In the Operation Status column of the NE list, the restoring process and result are displayed.
----End
Related Commands
Load the
configuratio
n file
load configuration Privilege mode
Load the
database file
load data Privilege mode

Issue 03 (2010-11-19)
A Acronyms and Abbreviations
The following table describes the acronyms and abbreviations used in the ONU Configuration
Guide.
A
AAA Authentication, Authorization and Accounting
AAL1 ATM Adaptation Layer Type 1
AAL5 ATM Adaptation Layer Type 5
ABR Available Bit Rate
ADSL Asymmetric Digital Subscriber Line
ANSI American National Standard Institute
ATM Asynchronous Transfer Mode
ATU-C ADSL Transceiver Unit, Central office end
ATU-R ADSL Transceiver Unit, Remote end

B
BRAS Broadband Remote Access Server
BRA Basic Rate Access
BRI Basic Rate Interface

C
CAR Committed Access Rate
CAS Channel Associated Signaling
CBR Constant Bit Rate
CES Circuit Emulation Service
Operation Guide for ONU NE Management A Acronyms and Abbreviations
A-1
CDVT Cell Delay Variation Tolerance
CLP Cell Loss Priority
CLR Cell Loss Rate
CS Convergence Sub layer
CTC Common Transmit Clock
CTD Cell Transfer Delay

D
DCE Data Communications Equipment
DDN Digital Data Network
DSLAM Digital Subscriber Line Access Multiplexer
DTE Digital Terminal Equipment

E
EMU Environment Monitor Unit
EPD Early Packet Discard
ESC Environment Supervision Circuit

F
FE Far End
FEBE Far End Bit Error
FR Frame Relay
FTP File Transfer Protocol

G
GMII Gigabit Media Independent Interface

H
HDLC Highspeed Data link Control
HEC Header Error Control

I
A-2 Huawei Proprietary and Confidential
Issue 03 (2010-11-19)
IAD Integrated Access Device
ICMP Internet Control Message Protocol
IMA Inverse Multiplexing over ATM
IPoA Internet Protocols Over ATM
ISDN Integrated Service Digital Network
ISP Internet Service Provider
IWF Inter working function

L
LAN Local Area Network
LOF Loss Of Frame
LOS Loss Of Signal

M
MA Media Service Access
MAC Media Access Control
MBS Maximum Burst Size
MIB Management Information Base
MMX Main Multiplexer Card
MTU Maximum Transmission Unit

N
NE Network Element
NMS Network Management Station
NNI Network Node Interface
nrt-VBR non-real time Variable Bit Rate

O
OAM Operations And Maintenance
OC-3 Optical Carrier Level 3
OLT Optical Line Terminal
ONU Optical Network Unit
A-3

P
PBX Private Branch Exchange
PCM Pulse Code Modulation
PCR Peak Cell Rate
POTS Plain Old Telephone Service
PPD Partial Packet Discard
PPP Point-to-Point Protocol
PPPoE PPP Over Ethernet
PRA Primary Rate Access
PRI Primary Rate Interface
PSTN Public Switched Telephone Network
PVC Permanent Virtual Connection
PVP Permanent Virtual Path

Q
QoS Quality of Service

R
RADIUS Remote Authentication Dial In User Service
RTU Remote Terminal Unit
rt-VBR real time Variable Bit Rate

S
SAR Segmentation And Reassembly
SCR Sustainable Cell Rate
SDH Synchronous Digital Hierarchy
SNMP Simple Network Management Protocol
SRA Seamless Rate Adaptive
STM-1 Synchronous Transmission Module Data Rates:155.52Mbit/s
STM-4 Synchronous Transmission Module Data Rates:622.08Mbit/s
STS-3 Synchronous Transport Signal Level 3
A-4 Huawei Proprietary and Confidential
Issue 03 (2010-11-19)

T
TDM Time Division Multiplex
TFTP Trivial File Transfer Protocol

U
UBR Unspecified Bit Rate
UDT Unstructured Data Transfer
UNI User Network Interface
UPC Usage Parameter Control
UTOPIA Universal Test&Operations PHY Interface for ATM

V
VBR Variable Bit Rate
VCI Virtual Channel Identifier
VCL Virtual Channel Link
VLAN Virtual Local Area Network
VPDN Virtual Private Data Network
VPI Virtual Path Identifier
A-5

OG For ONU NE Management - (V100R002C01 - 03)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OG For ONU NE Management - (V100R002C01 - 03)

Încărcat de

Drepturi de autor:

Formate disponibile

iManager U2000 Unified Network Management

S-ar putea să vă placă și