MA5600T&MA5603T&MA5608T V800R017C00 Commissioning and Configuration Guide 01 PDF

SmartAX MA5600T/MA5603T/MA5608T Multiservice Access Module
V800R017C00
Commissioning and Configuration

Guide
Issue
01
Date
2016-04-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2016. 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 a 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 01 (2016-04-29)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SmartAX MA5600T/MA5603T/MA5608T Multi-service

Access Module
Commissioning and Configuration Guide
About This Document
About This Document

Intended Audience
This document describes the commissioning of the basic functions provided by the device in
terms of hardware, software, interconnection, and maintenance and management to ensure
that the device runs in a stable and reliable state. This document describes the configuration
procedures of various services supported by the MA5600T/MA5603T/MA5608T in terms of
configuration method and configuration example.
This document helps to learn the commissioning flows, commissioning methods, and
configuration procedures of various services of the MA5600T/MA5603T/MA5608T.
This document is intended for:
l
Installation and commissioning engineers
System maintenance engineers
Data configuration engineers
Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol
Description
DANGER indicates a hazard with a high level or medium
level of risk which, if not avoided, could result in death or
serious injury.
WARNING indicates a hazard with a low level of risk
which, if not avoided, could result in minor or moderate
injury.
CAUTION indicates a potentially hazardous situation
that, if not avoided, could result in equipment damage,
data loss, performance deterioration, or unanticipated
results.
TIP indicates a tip that may help you solve a problem or
save time.
Issue 01 (2016-04-29)

ii

Access Module
Symbol
About This Document
Description
NOTE provides additional information to emphasize or
supplement important points of the main text.
Command Conventions
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in square brackets [ ] are

optional.
{ x | y | ... }
Alternative items are grouped in braces and separated by

vertical bars. One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } *
Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
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
Update History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.
Updates in Issue 01 (2016-04-29)

This is the first release. Compared with issue 02 (2015-12-30) of V800R016C10, the
document has no changes.
Issue 01 (2016-04-29)

iii

Access Module
Contents
Contents
About This Document.....................................................................................................................ii
1 Commissioning.............................................................................................................................. 1
1.1 Commissioning Introduction.......................................................................................................................................... 2
1.1.1 Commissioning Definition.......................................................................................................................................... 2
1.1.2 Commissioning Procedure...........................................................................................................................................2
1.2 Commissioning Preparations.......................................................................................................................................... 3
1.2.1 Checking Hardware..................................................................................................................................................... 3
1.2.2 Preparing Software...................................................................................................................................................... 4
1.2.3 Preparing Tools............................................................................................................................................................5
1.2.4 Planning Data.............................................................................................................................................................. 6
1.3 Stand-Alone Commissioning..........................................................................................................................................7
1.3.1 Checking the Settings of DIP Switches....................................................................................................................... 7
1.3.2 Powering On the Device............................................................................................................................................16
1.3.3 Commissioning the Power Supply System................................................................................................................17
1.3.4 Configuring the Maintenance Terminal.....................................................................................................................18
1.3.5 Logging In to the System...........................................................................................................................................20
1.3.6 Checking the Software State......................................................................................................................................61
1.3.7 Loading a Configuration Script................................................................................................................................. 63
1.3.8 Changing the System Name...................................................................................................................................... 64
1.3.9 Configuring the System Time....................................................................................................................................64
1.3.10 Configuring a System User......................................................................................................................................66
1.3.11 Configuring a Board................................................................................................................................................ 71
1.3.12 Checking the Status of the Upstream Port...............................................................................................................74
1.3.13 Checking the Status of the Service Port.................................................................................................................. 75
1.3.14 Enabling the ONT Automatic Discovery function.................................................................................................. 75
1.3.15 Testing the Optical Power of an Optical Port.......................................................................................................... 76
1.3.16 Commissioning the EMU........................................................................................................................................ 82
1.3.17 Saving and Backing Up Data.................................................................................................................................126
1.4 Interconnection Commissioning.................................................................................................................................135
1.4.1 Commissioning the Interconnection with the NMS................................................................................................ 135
1.4.2 Commissioning the Interconnection with the Router.............................................................................................. 160
1.4.3 Commissioning the Interconnection with the BRAS.............................................................................................. 161
1.4.4 Interconnection Commissioning of the MG Interface............................................................................................. 163
Issue 01 (2016-04-29)

iv

Access Module
Contents
1.4.5 Commissioning the Interconnection with the SIP Interface.................................................................................... 169

1.4.6 Commissioning the Management Channel Between the OLT and the GPON MDU..............................................172
1.4.7 Commissioning the Management Channel Between the OLT and the GPON ONT...............................................177
1.4.8 Commissioning the Management Channel to the xDSL CPE................................................................................. 180
1.4.9 Configuring Triple-Plane Isolation..........................................................................................................................182
1.5 Maintenance and Management Commissioning.........................................................................................................184
1.5.1 Configuring the System Energy-Saving Function...................................................................................................185
1.5.2 Checking Alarms and Events.................................................................................................................................. 186
1.5.3 Checking the Log.....................................................................................................................................................190
1.5.4 Checking the System Switchover............................................................................................................................ 191
1.6 Supplementary Information........................................................................................................................................ 193
1.6.1 Script Making.......................................................................................................................................................... 193
1.6.2 Configuring the File Transfer Mode .......................................................................................................................194
1.6.3 Software Package Settings.......................................................................................................................................201
2 Basic Configuration...................................................................................................................218
2.1 Configuring Alarms.................................................................................................................................................... 219
2.2 Adding Port Description............................................................................................................................................. 222
2.3 Configuring the Attributes of an Upstream Ethernet Port.......................................................................................... 223
2.4 Configuring DOCSIS Event Reporting...................................................................................................................... 226
3 Configuration Example of DSLAM Services....................................................................... 228

3.1 Example of the xDSL Internet Access Service...........................................................................................................229
3.1.1 Configuring the xDSL Service in PPPoE Mode......................................................................................................229
3.1.2 Configuring the xDSL Service in IPoE Mode.........................................................................................................235
3.1.3 Configuring the xDSL Service In PPPoA Mode..................................................................................................... 242
3.1.4 Configuring the xDSL Service in IPoA Mode........................................................................................................ 249
3.1.5 Configuring the xDSL Service in 802.1X Mode..................................................................................................... 255
3.1.6 Changing ADSL Service to VDSL Service (VDSL2 Boards)................................................................................ 263
3.2 Example of the xDSL Multicast Service.................................................................................................................... 267
3.2.1 Configuring the Multicast Video Service (Static)................................................................................................... 267
3.2.2 Configuring the Multicast Video Service (Dynamic)..............................................................................................272
3.3 Example of the VoIP Service......................................................................................................................................276
3.3.1 Configuring the VoIP Service (H.248).................................................................................................................... 276
3.3.2 Configuring the VoIP Service (MGCP)...................................................................................................................284
3.3.3 Configuring the VoIP PSTN Service (SIP)..............................................................................................................291
3.3.4 Configuring the VoIP Service (H.248 and SIP).......................................................................................................298
3.3.5 Configuring the P2P ISDN BRA Service................................................................................................................303
3.3.6 Configuring the P2P ISDN BRA Service (SIP)...................................................................................................... 307
3.3.7 Configuring the P2MP ISDN BRA Service............................................................................................................ 310
3.3.8 Configuring the P2MP ISDN BRA Service (SIP)...................................................................................................313
3.3.9 Configuring the ISDN PRA Service........................................................................................................................315
3.3.10 Configuring the ISDN PRA Service (SIP)............................................................................................................ 318
3.3.11 Configuring TDM SHDSL for Carrying the PRA Service (H.248)...................................................................... 320
Issue 01 (2016-04-29)


Access Module
Contents
3.3.12 Configuring TDM SHDSL for Carrying the PRA Service (SIP).......................................................................... 323
3.3.13 Configuring VAGs................................................................................................................................................. 325
3.4 Example of the Triple Play......................................................................................................................................... 337
3.4.1 Configuring the Triple Play (Multi-PVC)............................................................................................................... 339
3.4.2 Configuring the Triple Play (Single-PVC, Stream-based Rate Limitation)............................................................ 346
3.4.3 Configuring the Triple Play Service (Single-PVC, User-based Rate Limitation)................................................... 353
4 Configuration Example of the Private Line Service........................................................... 362

4.1 Example of the QinQ VLAN......................................................................................................................................364
4.2 Example of the VLAN Stacking Multi-ISP Wholesale Access..................................................................................368
4.3 Example of the PWE3 Private Line Service...............................................................................................................372
4.3.1 Configuring ATM PWE3 to Implement Migration (IP).......................................................................................... 373
4.3.2 Configuring the ATM PWE3 to Achieve emulated Services(MPLS)..................................................................... 382
4.3.3 Configuring the ETH PWE3 to Emulate Ethernet Services (MPLS)...................................................................... 387
4.3.4 Configuring the TDM PWE3 to Emulate Services (IP).......................................................................................... 392
4.3.5 Configuring the TDM PWE3 to Emulate Services (MPLS)................................................................................... 398
4.4 Example of the TDM SHDSL Service for Narrowband Data.................................................................................... 403
4.5 Example of the Private Line Service Leasing E1 Timeslots...................................................................................... 406
5 Configuration Example of the MSTP Subtending Network............................................ 412

5.1 MSTP Networking......................................................................................................................................................413
5.2 MSTP Dataplan.......................................................................................................................................................... 414
5.3 Configuring MA5600T/MA5603T/MA5608T-1....................................................................................................... 418
5.8 Verification................................................................................................................................................................. 459
6 Configuration Example of the VPLS..................................................................................... 460

6.1 Example of the VPLS Service.................................................................................................................................... 462
6.2 Example of the VPLS Multicast Service.................................................................................................................... 466
6.3 Example of the VPLS Enterprise Private Line Service.............................................................................................. 471
7 Configuration Example of the Subtending Networking .................................................. 477

7.1 Subtended Network.................................................................................................................................................... 478
7.2 Data Plan for Subtended Network.............................................................................................................................. 479
7.3 Configuring MA5600T-1........................................................................................................................................... 482
7.4 Configuring MA5600T-2........................................................................................................................................... 491
7.5 Configuring MA5600T-3........................................................................................................................................... 500
7.6 Configuring MA5600T-4........................................................................................................................................... 508
7.7 Verification................................................................................................................................................................. 512
8 FTTx Configuration Summary................................................................................................513

9 FTTH Configuration................................................................................................................. 515
Issue 01 (2016-04-29)

vi

Access Module
Contents
9.1 Basic Concepts........................................................................................................................................................... 516

9.2 Principle of FTTH Data Plan......................................................................................................................................518
9.2.1 Data Plan Principles for IP Addresses..................................................................................................................... 518
9.2.2 Principle of QoS Planning....................................................................................................................................... 520
9.2.3 Principles of Internet and Wi-Fi Access Services Data Planning............................................................................522
9.2.4 Principle of Voice Service Data Plan.......................................................................................................................524
9.2.5 Principle of IPTV Service Data Plan....................................................................................................................... 529
9.2.6 Principle of Security Data Plan............................................................................................................................... 531
9.3 Bridging + Voice ONT Network Scenario (GPON Access).......................................................................................533
9.3.1 Service Requirements and Application Scenario.................................................................................................... 534
9.3.2 Configuration Process..............................................................................................................................................535
9.3.3 Adding an ONT to an OLT...................................................................................................................................... 537
9.3.4 Configuring the Internet Access Service................................................................................................................. 541
9.3.5 Configuring the H.248-based Voice Service (on a Web Page or the U2000).......................................................... 543
9.3.6 Configuring the H.248-based Voice Service (Through the CLI).............................................................................550
9.3.7 Configuring the SIP-based Voice Service (on a Web Page or the U2000).............................................................. 554
9.3.8 Configuring the SIP-based Voice Service (Through the CLI).................................................................................562
9.3.9 Configuring the BTV Service..................................................................................................................................567
9.3.10 Configuring the VoD Service.................................................................................................................................570
9.3.11 Configuring Link Aggregation, Congestion Control, and Security Policies......................................................... 572
9.3.12 Verifying Services..................................................................................................................................................575
9.4 Bridging ONT + HGW Network Scenario (GPON Access)...................................................................................... 580
9.4.4 Configuring the Internet Access Service................................................................................................................. 586
9.4.5 Configuring the Voice Service.................................................................................................................................589
9.4.6 Configuring the BTV Service..................................................................................................................................593
9.4.7 Configuring the VoD Service...................................................................................................................................597
9.4.8 Configuring Link Aggregation, Congestion Control, and Security Policy............................................................. 600
9.4.9 Verifying Services....................................................................................................................................................603
9.5 Gateway ONT Network Scenario (GPON Access).................................................................................................... 608
9.5.4 Configuring the Internet Access Service (on a Web Page or the U2000)................................................................616
9.5.5 Configuring the Wi-Fi Access Service (on a Web Page).........................................................................................620
9.5.6 Configuring the H.248-based Voice Service (on a Web Page or the U2000) ......................................................... 625
9.5.7 Configuring the H.248-based Voice Service (Through the CLI).............................................................................632
9.5.8 Configuring the SIP-based Voice Service (on a Web Page or the U2000).............................................................. 636
9.5.9 Configuring the SIP-based Voice Service (Through the CLI).................................................................................644
9.5.10 Configuring the BTV Service................................................................................................................................649
Issue 01 (2016-04-29)

vii

Access Module
Contents

9.5.12 Configuring Any Port Any Service (on the Web Page).........................................................................................656
9.5.13 Configuring Link Aggregation, Congestion Control, and Security Policy........................................................... 663
9.6 Configuring Triple Play Service (GPON Access in Simplified Mode)......................................................................671
9.7 Configuring FTTH Service (P2P Access).................................................................................................................. 677
10 FTTB and FTTC Configuration.............................................................................................683

10.1 FTTB and FTTC Configuration Summary............................................................................................................... 685
10.2 Basic Concept........................................................................................................................................................... 686
10.3 Principle of FTTB and FTTC Data Plan.................................................................................................................. 689
10.3.1 Principle of Device Management Data Plan..........................................................................................................689
10.3.2 QoS Planning Principles........................................................................................................................................ 690
10.3.3 Principle of Internet Access Service Data Plan..................................................................................................... 692
10.3.4 (Optional) Principle of Vectoring Data Plan..........................................................................................................695
10.3.5 Principle of VoIP Service Data Plan......................................................................................................................697
10.3.6 Principle of IPTV Service Data Plan..................................................................................................................... 701
10.3.7 Principle of Security Data Plan............................................................................................................................. 709
10.4 FTTB Networking (GPON Networking, LAN Access, Without HGW)..................................................................711
10.4.1 Service Requirements and Application Scenarios.................................................................................................712
10.4.2 Configuration Procedure........................................................................................................................................713
10.4.3 Adding an ONU to an OLT....................................................................................................................................714
10.4.4 Configuring the Management Channel Between the OLT and the ONU.............................................................. 719
10.4.5 Configuring the Service Channel Between the OLT and the ONU.......................................................................720
10.4.6 Configuring LAN Internet Access Service (On the ONU)....................................................................................722
10.4.7 Configuring H.248 Voice Service (on the ONU)...................................................................................................724
10.4.8 Configuring SIP Voice Service (on the ONU).......................................................................................................727
10.4.10 Verifying Services................................................................................................................................................734
10.5 FTTB/C Networking (GPON Networking, xDSL Access, Without HGW).............................................................735
10.5.1 Service Requirements and Application Scenario.................................................................................................. 736
10.5.6 Configuring the Internet Access Service (ADSL2+ Access, on the ONU)...........................................................746
10.5.7 Configuring the Internet Access Service (VDSL2 Access, on the ONU)............................................................. 749
10.5.8 Configuring the Internet Access Service (G.fast Access, on the ONU)................................................................755
10.5.9 (Optional) Configuring Vectoring......................................................................................................................... 758
10.5.10 Configuring H.248 Voice Service (on the ONU).................................................................................................769
10.5.11 Configuring SIP Voice Service (on the ONU).....................................................................................................773
10.5.12 Configuring Link Aggregation, Congestion Control, and Security Policy......................................................... 776
Issue 01 (2016-04-29)

viii

Access Module
Contents
10.6 FTTB/FTTC+HGW Networking (GPON Networking, Voice Service Provided by ONU).....................................781

10.6.6 Configuring the Internet Access Service (LAN Access, on the ONU)................................................................. 795
10.6.10 Configuring H.248 Voice Service (on the ONU).................................................................................................816
10.6.11 Configuring SIP Voice Service (on the ONU).....................................................................................................820
10.6.12 Configuring the IPTV Service (on the ONU)......................................................................................................823
10.6.13 Configuring Link Aggregation, Congestion Control, and Security Policy......................................................... 826
10.6.14 Configuring the Internet Access Service (on the HGW)..................................................................................... 829
10.6.15 Configuring the IPTV Service (on the HGW).....................................................................................................831
10.7 FTTB/FTTC+HGW Networking (GPON Networking, HGW Providing the VoIP Service)...................................834
10.7.5 Configuring Service Channels Between an OLT and an ONU............................................................................. 845
10.7.6 Configuring the Internet Access Service (LAN Access, on the ONU)................................................................. 848
10.7.9 Configuring the Internet Access Service (G.fast Access, on the ONU)................................................................858
10.7.10 (Optional) Configuring Vectoring....................................................................................................................... 861
10.7.11 Configuring the Voice Service Channel (on the ONU)....................................................................................... 872
10.7.12 Configuring the IPTV Service (on the ONU)......................................................................................................874
10.7.13 Configuring Link Aggregation, Congestion Control, and Security Policies....................................................... 877
10.7.14 Configuring the Internet Access Service (on the HGW)..................................................................................... 880
10.7.16 Configuring the VoIP Service (on the HGW)......................................................................................................882
10.8 FTTB and FTTC Ethernet Cascade Networking (ONU Works as an Independent NE).......................................... 885
10.8.1 Service Requirements and Usage Scenario........................................................................................................... 886
10.8.3 Configuring the Working Mode of an Ethernet Cascading Board........................................................................ 889
10.8.4 Configuring the Management Channel Between an OLT and an ONU................................................................ 890
10.8.5 Configuring the Service Channel Between an OLT and an ONU......................................................................... 895
10.8.6 Configuring the Service Flow on an ONU or HGW............................................................................................. 900
Issue 01 (2016-04-29)

ix

Access Module
Contents
10.9 FTTB and FTTC Ethernet Cascade Networking (ONU works as a GE remote extended subrack)........................ 907
10.9.1 Service Requirements and Application Scenarios for GE Remote Extended Subrack......................................... 907
10.9.2 Principle of Data Planning for GE Remote Extended Subrack............................................................................. 909
10.9.3 Configuration Procedure for GE Remote Extended Subrack................................................................................ 910
10.9.4 Adding GE Remote Extended Subracks................................................................................................................912
10.9.5 Configuring VDSL2 User Ports............................................................................................................................ 914
10.9.6 Configuring VDSL2 Service Flows...................................................................................................................... 914
10.9.8 Configuring Link Aggregation, Congestion Control, and Security Policies......................................................... 923
10.9.9 Configuring the Internet Access Service (on the HGW)....................................................................................... 927
10.9.11 Configuring the VoIP Service (on the HGW)...................................................................................................... 929
11 FTTO Configuration (SOHO and SME)............................................................................. 933

11.1 Basic Concept........................................................................................................................................................... 935
11.2 Principles of Planning Data for FTTO Services (SOHO and SME).........................................................................937
11.2.1 Principles of Planing Device Management Data................................................................................................... 937
11.2.2 Principle of QoS Planning..................................................................................................................................... 938
11.2.3 Principle of Internet Access Service Data Plan..................................................................................................... 941
11.2.4 Principles of Planning Voice Service Data............................................................................................................ 942
11.2.5 Principle of IPTV Service Data Plan..................................................................................................................... 946
11.2.6 Principle of Security Data Plan..............................................................................................................................948
11.3 Bridging Networking(GPON)...................................................................................................................................950
11.3.4 Configuring the Internet Access Service............................................................................................................... 956
11.3.5 Configuring the BTV Service................................................................................................................................ 959
11.3.7 Configuring Link Aggregation, Congestion Control, and Security Policy ...........................................................964
11.4 Gateway Networking(GPON)...................................................................................................................................971
11.4.4 Configuring the Internet Access Service............................................................................................................... 978
11.4.5 Configuring the Wi-Fi Service (Web Pages)......................................................................................................... 982
11.4.6 Configuring Soft GRE Tunnel-based Wi-Fi Sharing (U2000).............................................................................. 987
11.4.7 Configuring VLAN Tunnel-based Wi-Fi Sharing (U2000)...................................................................................993
11.4.8 Configuring the H.248-based Voice Service (on a Web Page).............................................................................. 999
Issue 01 (2016-04-29)


Access Module
Contents
11.4.9 Configuring the H.248-based Voice Service (Through the CLI).........................................................................1006

11.4.10 Configuring the SIP-based Voice Service (on a Web Page).............................................................................. 1011
11.4.11 Configuring the SIP-based Voice Service (Through the CLI)........................................................................... 1017
11.4.12 Configuring the BTV Service............................................................................................................................ 1023
11.4.13 Configuring the VoD Service.............................................................................................................................1025
11.4.14 Configuring L2TP Services............................................................................................................................... 1027
11.4.15 Configuring Link Aggregation, Congestion Control, and Security Policy........................................................1030
11.4.16 Verifying Services..............................................................................................................................................1032
11.5 Layer 2 Interoperation Service Between Enterprise Branches .............................................................................. 1037
11.5.1 Service Requirement and Application Scenario.................................................................................................. 1037
11.5.2 Configuration Procedure......................................................................................................................................1039
11.5.3 Adding ONUs to OLT..........................................................................................................................................1040
11.5.4 Configuring Layer 2 Interoperation Service Ports on OLT................................................................................. 1044
11.5.5 Configuring Congestion Control and Security Policies.......................................................................................1045
11.6 Configuring FTTO SOHO and SME Services (GE Optical Port).......................................................................... 1049
11.7 Configuring FTTO SOHO and SME Services (GE Electrical Port)...................................................................... 1065
12 FTTO Configuration (Large-sized Enterprise Access)................................................... 1080

12.1 FTTO (Large-sized Enterprise Access) Configuration Summary.......................................................................... 1082
12.2 Overview of Enterprise Access Service................................................................................................................. 1082
12.3 Principle of Planning Data for Enterprise Access Service..................................................................................... 1084
12.3.1 Principle of Equipment Management Data Plan................................................................................................. 1084
12.3.2 Principle of VLAN Data Plan..............................................................................................................................1085
12.3.3 Principle of QoS Data Plan..................................................................................................................................1088
12.3.4 Principle of Protocol Transparent Transmission Data Plan.................................................................................1090
12.3.5 Principle of Security Data Plan........................................................................................................................... 1092
12.3.6 Principle of Reliability Data Plan........................................................................................................................ 1093
12.4 Configuring Layer 2 Interoperation Service Between Enterprise Branches (GPON)............................................1096
12.4.2 Configuration Process..........................................................................................................................................1097
12.4.4 Configuring Management Service Ports on OLT and ONUs.............................................................................. 1102
12.4.5 Configuring Layer 2 Interoperation Service Ports on OLT................................................................................. 1103
12.4.6 Configuring Ethernet Access Service Ports on ONUs.........................................................................................1105
12.4.8 Configuring E2E Reliability................................................................................................................................ 1108
12.5 Configuring Enterprise DDN Private Line Access Service (GPON)..................................................................... 1114
Issue 01 (2016-04-29)

xi

Access Module
Contents
12.5.5 Configuring TDM Connections........................................................................................................................... 1119

12.5.6 Configuring Clock Synchronization.................................................................................................................... 1120
12.6 Configuring Enterprise IP PBX Private Line Access Service (GPON)..................................................................1125
12.6.5 Configuring OLT QinQ Service Ports................................................................................................................. 1131
12.6.6 Configuring Ethernet Access Service Ports on ONUs.........................................................................................1132
12.7 Configuring Enterprise PRA PBX Private Line Access Service (GPON)............................................................. 1139
12.7.5 Configuring Service Ports for Voice Transparent Transmission..........................................................................1145
12.7.6 Configuring VoIP PRA Access............................................................................................................................1146
12.8 Configuring Enterprise E1 Unified Access Service (GPON).................................................................................1155
12.8.5 Configuring SAToP Connections and Service Ports............................................................................................1160
12.8.6 Configuring ONU SAToP Connections............................................................................................................... 1162
12.8.9 Configuring Network Protectio........................................................................................................................... 1167
12.8.10 Verifying Services..............................................................................................................................................1169
12.9 Configuring Enterprise E1 Unified Access Service (OLT Cascading, GPON)......................................................1172
12.9.3 Configure OLT_A cascading with OLT_B.......................................................................................................... 1174
12.9.4 Configuring SAToP Connections between OLT_A and ONU.............................................................................1175
12.9.5 Adding ONUs to OLT_B..................................................................................................................................... 1176
12.9.6 Configuring Management and Service Channel on OLT_B and ONU............................................................... 1179
12.9.7 Configuring ONU SAToP Connections............................................................................................................... 1180
Issue 01 (2016-04-29)

xii

Access Module
Contents

13 FTTM Configuration (Base Station Access)..................................................................... 1187

13.1 Basic Concepts........................................................................................................................................................1188
13.2 Prinpicle of Planning Data for Base Station Access Service..................................................................................1189
13.2.1 Principle of Equipment Management Data Plan..................................................................................................1189
13.2.2 Principle of VLAN Data Plan..............................................................................................................................1190
13.2.3 Principle of QoS Data Plan..................................................................................................................................1192
13.2.4 Principle of Clock Synchronization Data Plan.................................................................................................... 1193
13.2.5 Principle of Security Data Plan............................................................................................................................1195
13.2.6 Planning Reliability Data.....................................................................................................................................1196
13.3 Configuring Base station access Clock Synchronization ...................................................................................... 1199
13.3.1 Overview of Base station access Clock/Time Synchronization.......................................................................... 1199
13.3.2 Configuring BITS Clock Synchronization.......................................................................................................... 1204
13.3.3 Configuring E1/STM-1 Line Clock Synchronization......................................................................................... 1207
13.3.4 Configuring Ethernet Clock Synchronization..................................................................................................... 1209
13.3.5 Configuring "1PPS+ToD" Clock Synchronization..............................................................................................1212
13.3.6 Configuring 1588v2 Clock Synchronization....................................................................................................... 1216
13.4 Configuring Base Station Access Service (GPON)................................................................................................1222
13.4.1 Configuring E1 Base Station Access Service (in Native TDM Mode, GPON).................................................. 1222
13.4.2 E1 Base Station Access Service (in SAToP Mode, GPON)................................................................................ 1237
13.4.3 Configuring Ethernet Base Station Access Service (in QinQ VLAN Mode, GPON).........................................1254
13.4.4 Configuring Symmetrical TDM PWE3 Access for OLTs on Both Sides (GPON)............................................. 1271
13.4.5 GPON Access for the OLT one Side and E1 or SHDSL access for the OLT on the Peer Side...........................1287
13.4.6 Symmetrical E1 or SHDSL Access for OLTs on Both Sides.............................................................................. 1301
13.4.7 Configuring E1 Access for the ONU and Creating TDM PWE3 Between the ONU and Peer PE (GPON)...... 1307
13.4.8 Configuring Small-Cell Base Station Access Service (through CLI Configuration, GPON)............................. 1318
13.4.9 Configuring Small-Cell Base Station Access Service (through GUI Pre-Deployment, GPON)........................ 1331
14 D-CCAP Service Configuration (Centralized Management)........................................1351

14.1 D-CCAP Service Overview....................................................................................................................................1353
14.1.1 Basic Concepts.................................................................................................................................................... 1353
14.1.2 Networking Scenarios and Hardware Configurations (GPON)...........................................................................1356
14.1.3 Networking Scenarios and Hardware Configurations (GE)................................................................................ 1359
14.2 D-CCAP Data Plan Rules.......................................................................................................................................1362
14.2.1 Frequency Spectrum Management...................................................................................................................... 1362
14.2.2 Device Management............................................................................................................................................ 1364
14.2.3 QoS...................................................................................................................................................................... 1364
14.2.4 VLAN.................................................................................................................................................................. 1367
14.2.5 Multiple Services in Multiple VLANs................................................................................................................ 1370
14.3 Home Service Networking..................................................................................................................................... 1374
14.3.1 Configuring Home Services (Centralized Management, GPON)........................................................................1374
14.3.2 Configuring Home Services (Centralized Management, GE)............................................................................. 1407
Issue 01 (2016-04-29)

xiii

Access Module
Contents
14.4 L2VPN Enterprise Service Networking................................................................................................................. 1439

14.4.1 Overview of the L2VPN BSoD Service.............................................................................................................. 1439
14.4.2 Configuring the Dot1Q-based L2VPN BSoD Service (GPON)..........................................................................1441
14.4.3 WLAN Hotspot Radio Backhaul Service Networking (GPON)......................................................................... 1464
14.4.4 Configuring the Dot1Q-based L2VPN BSoD Service (GE)............................................................................... 1465
14.4.5 WLAN Hotspot Radio Backhaul Service Networking (GE)...............................................................................1487
14.5 Multiple services in multiple VLANs Service Networking (GPON).....................................................................1488
14.5.1 Service Requirements and Usage Scenario......................................................................................................... 1488
14.5.3 Adding a Remote Extended Frame to an OLT.................................................................................................... 1491
14.5.4 Configuring RF Port Parameters......................................................................................................................... 1494
14.5.5 Configuring the HSI Service............................................................................................................................... 1499
14.5.6 Configuring the DOCSIS VoD Service............................................................................................................... 1500
15 D-CCAP Service Configuration (Standalone NE)...........................................................1506

15.1 D-CCAP Service Overview....................................................................................................................................1507
15.1.1 Basic Concepts.................................................................................................................................................... 1507
15.1.2 Networking Scenarios and Hardware Configurations......................................................................................... 1511
15.2 Configuring Services on an MA5633 (GE)............................................................................................................ 1512
15.2.1 Home Service Networking.................................................................................................................................. 1513
15.2.2 L2VPN Enterprise Service Networking.............................................................................................................. 1543
15.2.3 WLAN Hotspot Radio Backhaul Service Networking........................................................................................1562
15.3 Configuring Services on a D-CCAP ()................................................................................................................... 1563
15.3.1 Home Service Networking.................................................................................................................................. 1564
15.3.2 L2VPN Enterprise Service Networking.............................................................................................................. 1599
15.3.3 WLAN Hotspot Radio Backhaul Service Networking........................................................................................1623
16 Electrical Service Configuration......................................................................................... 1625

16.1 Configuration Example of the FTTx Service (GPON Access).............................................................................. 1626
16.1.1 Configuration Example of Transmitting Video Monitoring Data over Ethernet Access.................................... 1626
16.1.2 Configuration Example of Intelligently Collecting Power Consumption Information over Ethernet Access.... 1635
16.1.3 Configuration Example of Automatically Transmitting Site Information over Ethernet (Single Homing)........1644
16.1.4 Configuration Example of Automatically Transmitting Site Information over Ethernet (Dual Homing).......... 1657
16.1.5 Configuration Example of Intelligently Collecting Power Consumption Information over a Serial Port.......... 1671
17 OptiCable EoC Bandwidth Configuration....................................................................... 1682

17.1 Configuring Example of EoC Services (OLTs Use GPON Access).......................................................................1683
18 IPv6 Configuration................................................................................................................ 1694

18.1 IPv6 Networking.....................................................................................................................................................1695
18.2 Configuration Difference Between IPv6 and IPv4................................................................................................. 1697
18.2.1 Configuration Differences Between IPv6 and IPv4 on the OLT......................................................................... 1697
18.2.2 Configuration Differences Between IPv6 and IPv4 on the ONU........................................................................1702
18.2.3 Configuration Difference Between IPv6 and IPv4 on the ONT..........................................................................1706
Issue 01 (2016-04-29)

xiv

Access Module
Contents
18.3 Configuring IPv6 Services in the FTTB/C (No HGWs) Scenario......................................................................... 1707
18.3.1 Application Scenarios..........................................................................................................................................1708
18.3.2 Data Planning...................................................................................................................................................... 1708
18.3.4 Configuration Example........................................................................................................................................1712
18.4 Configuring IPv6 Services in the FTTB+HGW Scenario...................................................................................... 1720
18.4.1 Application Scenario........................................................................................................................................... 1720
18.4.2 Data Planning...................................................................................................................................................... 1721
18.5 Configuring IPv6 Services in the FTTH (Bridging ONT) Scenario...................................................................... 1738
18.5.2 Data Planning...................................................................................................................................................... 1739
18.6 Configuring IPv6 Services in the FTTH (Gateway ONT) Scenario.......................................................................1757
18.6.2 Data Plan..............................................................................................................................................................1758
Issue 01 (2016-04-29)

xv

Access Module
1 Commissioning
Commissioning
About This Chapter

This document describes the commissioning of the basic functions provided by the device in
terms of hardware, software, interconnection, and maintenance and management to ensure
that the device runs in a stable and reliable state.
1.1 Commissioning Introduction
The topic describes the commissioning definition and procedure.
1.2 Commissioning Preparations
This topic describes the hardware, software, and tool preparations for the commissioning.
1.3 Stand-Alone Commissioning
After the hardware installation, a stand-alone MA5600T/MA5603T/MA5608T should be
commissioned to ensure that the stand-alone MA5600T/MA5603T/MA5608T works in the
normal state. The following recommended commissioning tasks and sequences are for
reference only. Different offices have different conditions; therefore, it is recommended that
customers, with the assistance of Huawei engineers, modify commissioning tasks according
to actual requirements.
1.4 Interconnection Commissioning
The MA5600T/MA5603T/MA5608T provides multiple interfaces for interconnection. This
topic describes the interconnection commissioning of the MA5600T/MA5603T/MA5608T.
The following recommended commissioning tasks and sequences are for reference only.
Different offices have different conditions; therefore, it is recommended that customers, with
the assistance of Huawei engineers, modify commissioning tasks according to actual
requirements.
1.5 Maintenance and Management Commissioning
To ensure the stability of the MA5600T/MA5603T/MA5608T, you need to verify the
maintainability and reliability of the device after completing the stand-alone commissioning
and interconnection commissioning.
1.6 Supplementary Information
This topic provides the commissioning supplementary information, including script making,
transmission mode setting, and default software settings.
Issue 01 (2016-04-29)


Access Module
1 Commissioning
1.1 Commissioning Introduction

The topic describes the commissioning definition and procedure.
1.1.1 Commissioning Definition

Commissioning refers to the stand-alone commissioning, the interconnection commissioning,
and the maintenance and management commissioning after the hardware installation. This
ensures that the device works in the normal state according to the design specifications.
1.1.2 Commissioning Procedure

This topic describes the procedure for commissioning the device.
Flowchart
Perform the commissioning according to the flowchart.
Figure 1-1 shows the commissioning procedure.
Figure 1-1 Commissioning procedure
Commissioning Item
The commissioning items in the commissioning procedure are described as follows:
Commissioning Preparations
Stand-Alone Commissioning
Issue 01 (2016-04-29)


Access Module
1 Commissioning

normal state.
Interconnection Commissioning
Maintenance and Management Commissioning
1.2 Commissioning Preparations

1.2.1 Checking Hardware

This topic describes how to prepare the hardware required before the commissioning. This
facilitates the subsequent commissioning.
Context
Table 1-1 lists the hardware to be checked before the commissioning.
Table 1-1 Hardware checklist
SN
Item
Description
Power supply
and
grounding
Ensure that the power cable and the grounding meet the
following requirements:
l The power cable and the ground cable are connected
properly and are in good contact.
l The labels of the power cable, ground cable, and power
distribution switch are correct, legible and complete.
l The connectors of the external ground cables and protection
ground cables of the cabinet are connected properly, without
any damage.
l The power supply for the device is in the normal state.
Cables and
connectors
Check the local maintenance serial port cable, network cable,

optical fiber, subscriber cable, and connectors, and ensure that
they meet the following requirements:
l The connectors are tight and firm.
l The cable jacket is intact.
l Cable labels are legible.
l Cables are bundled properly.
Issue 01 (2016-04-29)


Access Module
1 Commissioning
SN
Item
Description
Upper-layer
device
Ensure that the upper-layer device meets the following

requirements:
l The position of the interconnection port of the upper-layer
device is correct.
l The upper-layer device works in the normal state and can be
used for the commissioning.
Board
(daughter
board)
The board (daughter board) selected should meet the

requirements for the external ports.
NOTE
l Different boards (daughter boards) provide different external ports.
For details about the boards and their external ports on the
MA5600T/MA5603T/MA5608T, see Board Overview of the
MA5600T/MA5603T/MA5608T Hardware Description.
l During the system startup, you are not allowed to install or remove
any boards.
1.2.2 Preparing Software

This topic describes how to prepare the software required before the commissioning. This
Table 1-2 shows the software checklist before the commissioning.
Table 1-2 Software checklist
SN
Item
Description
Software
package
Ensure that files in the software package for the

commissioning are complete and the software version is
correct.
Software
commissioning
tools
Ensure that all the commissioning tools are available. The

common commissioning tools are as follows:
l HyperTerminal (provided by the Windows OS): used for
logging in to the MA5600T/MA5603T/MA5608T
through the CLI.
l TFTP, SFTP, and FTP tools: used for loading software.
They can be downloaded from http://
support.huawei.com. You are advised to use SFTP tools.
l Client software key generator Puttygen.exe, client
software key convertor sshkey.exe and SSH client
software putty.exe: used for logging in to the MA5600T/
MA5603T/MA5608T through the SSH.
Issue 01 (2016-04-29)


Access Module
1 Commissioning
1.2.3 Preparing Tools

This topic describes how to prepare the tools required before the commissioning. This
Table 1-3 lists the tools to be prepared for the commissioning.
Table 1-3 Tool checklist
Issue 01 (2016-04-29)
SN
Item
Description
Remarks
Cables
One RS-232 serial port cable (One

end with an RJ-45 connector used to
connect to the board and the other end
with a DB-9 or DB-25 female
connector used to connect to the
maintenance terminal)
Used to connect the

maintenance terminal to the
MA5600T/MA5603T/
MA5608T for maintenance
through the serial port.
One crossover cable
Used to connect the

maintenance terminal to the
MA5600T/MA5603T/
MA5608T for maintenance
through telnet.
Some optical fibers and patch cords

with different connectors
Used for the upstream

transmission and optical
power test.
Maintena
nce
terminal
One maintenance terminal configured

with a HyperTerminal application,
such as a laptop
Used to log in to the

MA5600T/MA5603T/
MA5608T to commission the
MA5600T/MA5603T/
MA5608T.
Auxiliary
device
and meter
One optical power meter
Used to test the mean

launched power and the input
optical power of an optical
port.
One optical attenuator
Used to attenuate the input

optical signal. It is used to
protect the optical port from
being damaged by intense
optical signals during the
device commissioning.
One multimeter
Used to measure the voltage,

resistance and current
intensity during the power
commissioning.


Access Module
SN
Item
1 Commissioning
Description
Remarks
One optical multiplexer/demultiplexer
Used to test the input optical

power of a single-fiber bidirectional optical port. It is a
meter with the multiplexing
and demultiplexing
functions.
One data network performance

analyzer
Used to test the input optical

power. It is used to transmit
data to simulate the
networking environment.
1.2.4 Planning Data

This topic describes the information to be collected about the hardware configuration,
networking, and data plan before the commissioning based on the engineering document. This
facilitates the data configuration.
Table 1-4 lists the data collected for the commissioning.
Table 1-4 Data checklist
SN
Item
Description
Hardware
configuration
This includes but is not limited to the following:

l Types and slot distribution of the control board and
service boards
l Types and physical positions of the upstream ports
and the service ports
Networking and data

plan
This includes but is not limited to the following:

l Networking mode
l IP address assignment
l VLAN planning
DIP Switches
configuration
l For details about the default settings of DIP

switches on the ESC board on the MA5600T, see
Checking the Settings of DIP Switches on the
H801ESC Board.
l For details about the default settings of DIP
switches on the fan monitoring board on the
MA5600T, see Checking the Settings of DIP
Switches on the Fan Monitoring Board.
Issue 01 (2016-04-29)


Access Module
1 Commissioning
NOTE
l A commissioning script can be made based on the actual networking and the data plan. For how to
make a script, see 1.6.1 Script Making.
l For details about the default settings of the main software on the MA5600T/MA5603T/MA5608T,
see 1.6.3 Software Package Settings.
1.3 Stand-Alone Commissioning

normal state. The following recommended commissioning tasks and sequences are for
reference only. Different offices have different conditions; therefore, it is recommended that
customers, with the assistance of Huawei engineers, modify commissioning tasks according
1.3.1 Checking the Settings of DIP Switches

This topic describes how to check the settings of the DIP switches on the environment
monitoring board (ESC board) and the fan monitoring board. This ensures the consistency
between the settings of DIP switches and the application of DIP switches.
Checking the Settings of DIP Switches on the H801ESC Board

This topic describes how to check the settings of DIP switches on the H801ESC board.
Checking the settings of DIP switches helps ensure that the settings meets actual
requirements.
Prerequisites
The device must be powered off.
Description of DIP Switches

The H801ESCA board resides in the I-type PDU and provides two DIP switches, namely, S5
and S6. Figure 1-2 shows the layout of the DIP switches on the H801ESCA board.
Figure 1-2 Layout of the DIP switches (in default settings) on the H801ESCA board
Table 1-5 describes the usage of DIP switches S5 and S6.

Issue 01 (2016-04-29)


Access Module
1 Commissioning
Table 1-5 Usage of the DIP switches

Electric
Switch
S5-1
S5-2
S5-3
Usage
Used to set the external sensor type of JTA1-JTA4. For detailed information,
see Table 1-6.
l ON: The external sensors are of the current type.
l OFF: The external sensors are of the voltage type.
S5-4
S6-1
S6-2
S6-3
S6-4
Used to set the sub-node ID. This value must correspond with the configured
ESC sub-node ID in the system and cannot be identical to the address value of
the sub-node. Such restrictions ensure that the H801ESC board can
communicate with the control board. For detailed information, see Table 1-7.
l ON: The mapping address bit is 0.
l OFF: The mapping address bit is 1.
S6-5
S6-6
Reserved.
S6-7
S6-8
Used to set the baud rate of the communication between the H801ESCA
board and the control board.
l ON: The baud rate is 19200 bit/s (default).
l OFF: The baud rate is 9600 bit/s.
Table 1-6 describes the mapping between S5-1 to S5-4 and sensor ports.
Table 1-6 Mapping between S5-1 to S5-4 and sensor ports
Electric Switch
OFF
ON
S5-1
The external sensor of JTA1 is of the

voltage type.
The external sensor of

JTA1 is of the current type.
S5-2

voltage type.

S5-3

voltage type.

S5-4

voltage type.

S6-1 to S6-5 are used to set the sub-node IDs of the H801ESC board. Table 1-7 lists the
mapping between S6-1 to S6-5 and sub-node IDs.
Issue 01 (2016-04-29)


Access Module
1 Commissioning
Table 1-7 Mapping between S6-1 to S6-5 and sub-node IDs
Issue 01 (2016-04-29)
S6-5
S6-4
S6-3
S6-2
S6-1
Address
Value of
Sub-nodes
00000 ( 0 )
00001(1)
00010(2)
00011(3)
00100(4)
00101(5)
00110(6)
00111(7)
01000(8)
01001(9)
01010(10)
01011(11)
01100(12)
01101(13)
01110(14)
01111(15)
(default)
10000(16)
10001(17)
10010(18)
10011(19)
10100(20)
10101(21)
10110(22)
10111(23)
11000(24)
11001(25)
11010(26)


Access Module
1 Commissioning
S6-5
S6-4
S6-3
S6-2
S6-1
Address
Value of
Sub-nodes
11011(27)
11100(28)
11101(29)
11110(30) is
used by the
ESC board,
and the
H801ESC
board cannot
be set to this
value.
11111(31)
Procedure
Step 1 Remove the cable connector if the H801ESC board is connected to an environment
monitoring cable.
Step 2 Loosen the screws on the H801ESC board anticlockwise by using the Phillips screwdriver, as
shown in (1) of Figure 1-3.
Figure 1-3 Removing the H801ESC board
Step 3 Hold the ejector lever of the front panel and remove the H801ESC board from the PDU, as
Issue 01 (2016-04-29)

10

Access Module
1 Commissioning
Step 4 Check whether settings of DIP switches on the H801ESC board are consistent with the
application. If the settings are inconsistent with the application, set the DIP switches again
according to "Description of DIP Switches".
Step 5 Insert the H801ESC board into the PDU, as shown in (1) of Figure 1-4.
Figure 1-4 Inserting the H801ESC board
Step 6 Fasten the screws on the H801ESC board clockwise by using the Phillips screwdriver, as
Step 7 Reconnect the environment monitoring cable to the H801ESC board.
----End
Result
The settings of DIP switches on the H801ESC board are consistent with the actual
requirements.
Checking the Settings of DIP Switches on the Fan Monitoring Board

This topic describes how to check the settings of DIP switches on the fan monitoring board.
Checking the settings of DIP switches helps ensure that the settings meet the application of
DIP switches.
Prerequisites
NOTE
Do not change the DIP switch setting on the fan monitoring board of the MA5603T. The DIP switches
on the fan monitoring board of the MA5608T does not support the DIP switch.
The device must be powered off.

Issue 01 (2016-04-29)

11

Access Module
1 Commissioning
Description of DIP Switches

The ESTI fan tray uses the FCBI fan monitoring board, and the 19-inch fan tray uses the
FCBH fan monitoring board.
The fan monitoring board provides a set of DIP switches named SW2. Figure 1-5 and Figure
1-6 show the layout of the DIP switches of the ESTI and the 19-inch fan trays respectively.
Figure 1-5 Layout of the DIP switches (in default settings) of the ESTI fan tray
Figure 1-6 Layout of the DIP switches (in default settings) of the 19-inch fan tray
Table 1-8 lists the usage of the SW2.

Table 1-8 usage of the SW2
DIP Switch
Usage
SW2-1
Used to set the sub-node address. This value must correspond with
the configured sub-node address of the fan in the system and
cannot be identical to the address value of the ESC sub-node. Such
restrictions ensure that the fan tray can communicate with the
control board. For detailed information, see Table 1-9.
l ON: The mapping address bit is 0.
l OFF: The mapping address bit is 1.
SW2-2
SW2-3
SW2-4
Used to set the baud rate of the communication between the fan
tray and the control board.
l ON: The baud rate is 19200 bit/s (default).
l OFF: The baud rate is 9600 bit/s.
Issue 01 (2016-04-29)

12

Access Module
1 Commissioning
DIP Switch
Usage
SW2-5
Used to set the number of fans. This value must correspond with
the system data configuration. For detailed information, see Table
1-10.
SW2-6
SW2-7
SW2-8
Used to set the fan speed adjustment mode. This value must
correspond with the system data configuration. For detailed
information, see Table 1-11.
Table 1-9, Table 1-10, and Table 1-11 list the settings of each DIP switch of SW2.
Table 1-9 Settings of SW2-1 to SW2-3
SW2-3
SW2-2
SW2-1
Address Value
ON
ON
ON
000(0)
ON
ON
OFF
001(1) (default
setting)
ON
OFF
ON
010(2)
ON
OFF
OFF
011(3)
OFF
ON
ON
100(4)
OFF
ON
OFF
101(5)
OFF
OFF
ON
110(6)
OFF
OFF
OFF
111(7)
Table 1-10 Settings of SW2-5 and SW2-6
Issue 01 (2016-04-29)
SW2-6
SW2-5
Quantity of Fans
Remarks
ON
ON
ON
OFF
The unique and

default setting of
the 19-inch fan
tray
OFF
ON
The unique and

default setting of
the ETSI fan tray
OFF
OFF
10

13

Access Module
1 Commissioning
Table 1-11 Settings of SW2-7 and SW2-8

SW2-8
SW2-7
Speed
Adjustment
Mode
Speed Adjustment Policy
Remar
ks
ON
ON
Measure the
temperature at
the air intake
vent (reserved)
Policy 1
l If the temperature is lower than 25C,

the fans rotate at 50% of the full
speed.
l If the temperature ranges from 25C
to 35C, the fans rotate at 50% to
100% of the full speed.
l If the temperature is higher than
35C, the fans rotate at full speed.
ON
OFF
Measure the
temperature at
the air exhaust
vent
Policy 2

speed.
65C, the fans rotate at the full speed.
OFF
ON
Measure the
temperature at
the air intake
vent
Policy 3
speed.
Issue 01 (2016-04-29)

The
ESTI
and the
19-inch
fan
trays
support
only
policy
3.
Therefo
re, only
this
setting
can be
adopted.
14

Access Module
1 Commissioning
SW2-8
SW2-7
Speed
Adjustment
Mode
Speed Adjustment Policy
Remar
ks
OFF
OFF
Stop fan
rotating and
measure the
temperature at
the air intake
vent
Policy 4

the fans stop rotating.
to 45C, the fans rotate at 50% of the
full speed.
Procedure
Step 1 Loosen the screws on the front panel of the fan tray anticlockwise by using the Phillips
screwdriver, as shown in (1) of Figure 1-7.
Figure 1-7 Removing/Inserting the fan tray
Step 2 Hold the ejector lever of the fan tray and remove the fan tray from the service shelf, as shown
in (2) of Figure 1-7.
Issue 01 (2016-04-29)

15

Access Module
1 Commissioning
Step 3 Check whether the settings of DIP switches on the fan monitoring board are consistent with
the application. If settings of DIP switches on the fan monitoring board are not consistent with
the application, set the DIP switches again according to "Description of DIP Switches".
Step 4 Insert the fan tray into the slot, as shown in (3) of Figure 1-7.
Step 5 Use the Phillips screwdriver to fasten the panel screws clockwise on the fan tray, as shown in
(4) of the Figure 1-7.
----End
Result
The settings of DIP switches on the fan monitoring board are consistent with the application.
1.3.2 Powering On the Device

This topic describes how to power on the device to ensure that all the boards can be normally
powered on.
Prerequisites
The after-installation check and the power-on check must be performed on the device.
Context
NOTICE
Inserting or removing boards is prohibited during startup.
Procedure
l
There are two kinds of devices: the indoor device and the outdoor device.
Powering on the indoor device

i.
Connect the input power supply of the DC PDU.
ii.
Turn on the output control switch of the DC PDU.
Powering on the outdoor device

i.
Connect the input power supply of the AC PDU.
ii.
Turn on the output control switch of the AC PDU.
iii. Turn on the output control switch of the power system.

iv.
Turn on the output control switch of the DC PDU.
----End
Result
The device can be normally powered on, and the STATUS indicator on the fan tray is on for
1s and off for 1s repeatedly, and so is the RUN ALM indicator on the board.
Issue 01 (2016-04-29)

16

Access Module
1 Commissioning
1.3.3 Commissioning the Power Supply System

This topic describes how to commission the power supply to ensure the reliable and stable
power supply provided for the device.
Checking the Power Supply of the DC PDU

This topic describes how to verify that either of the two independent power supplies can
supply power to the cabinet.
Prerequisites
The two independent power supplies of the DC power distribution unit (PDU) supply power
to the cabinet concurrently.
Procedure
Step 1 Disconnect the first power supply, and check the power supply of the cabinet.
Step 2 Restore the first power supply to power the cabinet.
Step 3 Disconnect the second power supply, and check the power supply of the cabinet.
Step 4 Restore the second power supply to power the cabinet.
----End
Result
After either of the two independent power supplies is disconnected, the power supply of the
cabinet is in the normal state, and the power supply of the boards is not affected, that is, the
RUN LED on the board is on for 1s and off for 1s repeatedly.
Checking the Power Supply of the Power Board

This topic describes how to check the redundancy backup function of the power boards.
Prerequisites
The two power boards configured must work in the normal state.
Context
In the normal state, the two power boards work in the load balancing mode and provide power
for all the service boards in the shelf. When one power board is faulty, the other power board
provides power for all the service boards in the shelf.
When checking the power supply of the power board, pay attention to the following points:
l
Wear an ESD wrist strap during the operation.
Turn off the -48 V input switch on the PDU that corresponds to the power board before
replacing the board. In addition, when the board is powered on, do not remove or insert
the power connector.
If one power board is faulty, replace the board in time to prevent the shelf from working
for a long time when only one power board supplies power.
Issue 01 (2016-04-29)

17

Access Module
1 Commissioning
Procedure
Step 1 Turn off the switch on the PDU that corresponds to one power board, and check the power
supply for the service board.
Step 2 Turn on the switch again.
Step 3 Repeat steps 1 and 2 to check the other power board.
----End
Result
The boards in the shelf work in the normal state after the switch on the PDU that corresponds
to either power board is turned off, that is, the RUN LED on the board is on for 1s and off for
1s repeatedly.
1.3.4 Configuring the Maintenance Terminal

During the commissioning, you need to maintain the device through the maintenance
terminal. This topic describes how to start the maintenance terminal and configure the IP
address of the maintenance terminal to meet the commissioning requirements.
Context
A maintenance terminal is usually a laptop installed with a HyperTerminal application.
Procedure
l
Issue 01 (2016-04-29)
Starting the Maintenance Terminal.

a.
Power on the maintenance terminal. The Windows OS starts automatically, and the
Log In dialog box is displayed.
b.
Power on the maintenance terminal. The Windows OS starts automatically, and the
Log In dialog box is displayed.
c.
Click OK to enter the Windows OS.
Configuring the IP address of the maintenance terminal to ensure that you can log in to
the MA5600T/MA5603T/MA5608T in the telnet or SSH mode through the maintenance
terminal. You are advised to use SSH mode.
a.
Right-click My Network Places and choose Properties. The Network

Connections window is displayed.
b.
In the Network Connections window, right-click Local Area Connection, and

choose Properties. The Local Area Connection Properties dialog box is
displayed.
c.
Click the General tab, and then select Internet Protocol (TCP/IP) in Components
checked are used by this connection, as shown in the following figure.

18

Access Module
1 Commissioning
Figure 1-8 Configure the local area connection properties
Issue 01 (2016-04-29)
d.
Click Properties to display the Internet Protocol (TCP/IP) Properties dialog box.
e.
Click General, and then select Use the following IP address: to configure the IP
address and the subnet mask, as shown in the following figure.

19

Access Module
1 Commissioning
Figure 1-9 Configure the IP address and the subnet mask
NOTE
The IP address of the maintenance terminal and the IP address of the maintenance Ethernet
port of the device must be in the same network segment.
f.
Click OK to return to the Local Area Connection Properties dialog box.
g.
Click OK.
----End
Result
The IP address of the maintenance terminal and the IP address of the maintenance Ethernet
port of the device are in the same network segment.
NOTE
By default, the IP address of the maintenance network port (ETH port on the control board) is
10.11.104.2, and the subnet mask is 255.255.255.0.
1.3.5 Logging In to the System

You must log in to the MA5600T/MA5603T/MA5608T before commissioning the MA5600T/
MA5603T/MA5608T through the maintenance terminal. The following describes three login
modes, namely, local serial port mode, telnet mode, and SSH mode. SSH with high priority is
recommended.
Issue 01 (2016-04-29)

20

Access Module
1 Commissioning
Login Through the Local Serial Port

When you need to maintain and manage the MA5600T/MA5603T/MA5608T locally, you can
log in to the system through the local serial port.
Prerequisites
l
A maintenance terminal (generally a laptop configured with a HyperTerminal

application) must be available.
An RS-232 serial port cable (one end with an RJ45 connector and the other end with a
DB-9 or DB-25 female connector) must be available.
Networking
Figure 1-10 shows the networking for logging in to the MA5600T/MA5603T/MA5608T
through the local serial port.
Figure 1-10 Logging in to the MA5600T/MA5603T/MA5608T through the local serial port
Serial port
PC
RS-232 cable
Access node
Flowchart
Figure 1-11 shows the flowchart for logging in to the system through the local serial port.
Issue 01 (2016-04-29)

21

Access Module
1 Commissioning
Figure 1-11 Flowchart for logging in to the system through the local serial port
Procedure
Step 1 Connect the serial port cable.
Use an RS-232 serial port cable to connect a serial port of the PC to the CON port of the SCU
control board, as shown in Figure 1-10.
Step 2 Set the HyperTerminal communication parameters.
NOTE
This section uses the HyperTerminal of the Windows XP OS as an example.

By default, the Windows 7 operating system does not provide the HyperTerminal. To perform this
operation, copy the hypertrm.dll and hypertrm.exe files from the Windows XP operating system to C:
\windows\system32. Then, run hypertrm.exe to have the HyperTerminal take effect. The other steps are
similar to those performed on the Windows XP operating system.
1.
Set up a connection.
Click Start. Choose All Programs > Accessories > Communications > Hyper
Terminal to display the Connection Description dialog box. Input the connection name,
and click OK, as shown in the following figure.
Issue 01 (2016-04-29)

22

Access Module
2.
1 Commissioning
Set the serial port.

Select the serial port that is connected to the MA5600T/MA5603T/MA5608T. You can
select COM1 or COM2 (here, use COM2 as an example), and click OK, as shown in
the following figure.
3.
Issue 01 (2016-04-29)
Set the HyperTerminal communication parameters. For details, see the following figure.

23

Access Module
1 Commissioning
NOTE
4.
The baud rate of the HyperTerminal must be the same as the baud rate of the serial port on the
MA5600T/MA5603T/MA5608T. By default, the baud rate of the serial port is 9600 bit/s.
If illegible characters are displayed on the HyperTerminal interface after you log in to the
system, it is generally because the baud rate of the HyperTerminal is different from the baud
rate of the MA5600T/MA5603T/MA5608T. In this case, set the consistent baud rate for the
HyperTerminal to log in to the system. The system supports the baud rates of 9600 bit/s, 19200
bit/s, 38400 bit/s, 57600 bit/s, and 115200 bit/s.
Click OK to display the HyperTerminal interface.
Step 3 (Optional) Set the properties of the HyperTerminal.

1.
Set the emulation type of the HyperTerminal.

Choose File > Properties on the HyperTerminal interface. In the dialog box that is
displayed, click the Settings tab, and set Emulation to VT100 or Auto Detect, as shown
in the following figure. It is Auto Detect by default.
Issue 01 (2016-04-29)

24

Access Module
2.
1 Commissioning
Set the line delay and the character delay of the ASCII code.
Click ASCII Setup. In the dialog box that is displayed, set line delay to 200 and
Character delay to 200, and then click OK, as shown in the following figure. By
default, Line delay is 0, and Character delay is 0.
Issue 01 (2016-04-29)

25

Access Module
1 Commissioning
NOTE
When you paste a text to the HyperTerminal, the character delay controls the character transmit
speed, and the line delay controls the interval of transmitting every line. If a delay is very short,
loss of characters occurs. When the pasted text is displayed abnormally, modify the delay.
----End
Result
On the Hyper Terminal interface, press Enter, and the system prompts you to input the user
name. Input the user name and the password for user registration (by default, the super user
name is root and the password is admin123), and wait until the CLI prompt character is
displayed.
NOTE
To improve the system security, please modify your password after first login. You can run the terminal
user password command to modify your password.
If the login fails, click

and then click
on the operation interface. If the login still fails,
return to step 1 to check the parameter settings and the physical connections, and then try
again.
Follow-up Procedure
l
You can run the idle-timeout command to set the terminal timeout time. if you do not
input commands within the specified timeout time, the system disconnects the terminal.
By default, the terminal timeout time is set to 5 minutes. If you do not run any
commands within 5 minutes, the system disconnects with the terminal. To perform any
operation, you must have to log in to the system again.
In the commissioning procedure, you must use the command, It is recommended that
you know well the command modes first.Figure 1-12 shows how to switch command
modes.
Figure 1-12
Login
quit
User mode
huawei>
enable
disable
Privilege mode
huawei#
config
quit
Global config mode

huawei(config)#
interface
quit
Interface/config mode
huawei(config-if-...)
return
Login Through Telnet (Outband Management)

This topic describes how to log in to the MA5600T/MA5603T/MA5608T using the local
maintenance Ethernet port (outband management port) in the telnet mode to maintain and
manage the MA5600T/MA5603T/MA5608T. You are advised to use SSH mode.
Prerequisites
Engineers are logged in to the MA5600T/MA5603T/MA5608T by using the local serial port
or the ETH port.
Issue 01 (2016-04-29)

26

Access Module
1 Commissioning
NOTE
The default IP address of the maintenance Ethernet port (ETH port on the control board) is 10.11.104.2,
and the subnet mask is 255.255.255.0.
For details about how to log in to the MA5600T/MA5603T/MA5608T by using the local
serial port, see Login Through the Local Serial Port.
For details about how to log in to the MA5600T/MA5603T/MA5608T by using the ETH
port, see the following:
Configure the IP address of the PC that is used for logging in to the MA5600T/
MA5603T/MA5608T. This IP address is on the same subnet as the IP address of the
maintenance Ethernet port but is not the IP address of the maintenance Ethernet
port. For example, configure the IP address to 10.11.104.6.
After logging in to the MA5600T/MA5603T/MA5608T, run the ip address

command to change the IP address of the device to 10.50.1.10/24.
Change the IP address of the PC to be on the same subnet as the IP address of the
port. For example, change the IP address of the device to 10.50.1.11/24.
Networking
Figure 1-13 shows an example network for outband management through telnet in a LAN,
and Figure 1-14 shows an example network for outband management through telnet in a
WAN.
Figure 1-13 Example network for outband management through telnet in a LAN
Access node
LSW
LAN
PC
Issue 01 (2016-04-29)
PC
PC

27

Access Module
1 Commissioning
NOTE
The MA5600T/MA5603T/MA5608T is connected to the LAN using the straight using cable, and the IP
address of the maintenance Ethernet port of the MA5600T/MA5603T/MA5608T is in the same network
segment as the IP address of the maintenance terminal. Alternatively, the Ethernet port of the
maintenance terminal can be directly connected to the maintenance Ethernet port of the MA5600T/
MA5603T/MA5608T to manage the MA5600T/MA5603T/MA5608T in the outband management
mode. In such a condition, if the MA5600T/MA5603T/MA5608T uses SCUL/SCUB control board, and
the peer device does not support the cable autosensing function, a crossover cable must be used.
Figure 1-14 Network example for outband management through telnet in a WAN
PC
LAN
Router
PC
PC
Access node
Data Plan
Table 1-12 and Table 1-13 provide the data plan for the outband management through telnet
in a LAN and in a WAN respectively.
Table 1-12 Data plan for the outband management through telnet in a LAN
Issue 01 (2016-04-29)
Item
Data
Maintenance Ethernet port of the

MA5600T/MA5603T/MA5608T
IP address: 10.50.1.10/24
Maintenance terminal
IP address: 10.50.1.20/24 (in the same

subnet as the IP address of the maintenance
Ethernet port)
NOTE
By default, the IP address of the maintenance
Ethernet port (ETH port on the control board) is
10.11.104.2, and the subnet mask is
255.255.255.0.

28

Access Module
1 Commissioning
Table 1-13 Data plan for the outband management through telnet in a WAN
Item
Data

MA5600T/MA5603T/MA5608T
IP address: 10.50.1.10/24
IP address: 10.10.1.10/24
Router port connecting to the MA5600T/

MA5603T/MA5608T
IP address: 10.50.1.1/24
NOTE
255.255.255.0.
Flowchart
Figure 1-15 shows the flowchart for logging in to the MA5600T/MA5603T/MA5608T
through telnet (outband management).
Figure 1-15 Flowchart for logging in to the MA5600T/MA5603T/MA5608T through telnet
(outband management)
Issue 01 (2016-04-29)

29

Access Module
1 Commissioning
Procedure
Step 1 Set up the network environment.
l
If you log in to the MA5600T/MA5603T/MA5608T in the LAN outband management

mode through telnet, set up a network environment according to Figure 1-13.
If you log in to the MA5600T/MA5603T/MA5608T in the MAN outband management

Step 2 Configure the IP address of the maintenance Ethernet port.

In the MEth mode, run the ip address command to configure the IP address of the
maintenance Ethernet port.
huawei(config)#interface meth 0
huawei(config-if-meth0)#ip address 10.50.1.10 24
Step 3 Add a route for the outband management.

l
If the network environment is set up as shown in Figure 1-13, you need not add a route.
If the network environment is set up as shown in Figure 1-14, run the ip route-static
command to add a route from the maintenance Ethernet port of the MA5600T/
MA5603T/MA5608T to the maintenance terminal.
huawei(config-if-meth0)#quit
huawei(config)#ip route-static 10.10.1.0 24 10.50.1.1
Step 4 Run the telnet application.

On the maintenance terminal, choose Start > Run. On the Run window, input "telnet
10.50.1.10" in the Open field as shown in Figure 1-16 (considering the Windows OS as an
example), and click OK. Then, the telnet dialog box is displayed.
Figure 1-16 Running the telnet application
Step 5 Log in to the system.

In the telnet dialog box, input the user name and the password. By default, the user name is
root, and the password is admin. When the login is successful, the system displays the
following information:
>>User name:root
>>User password:
Huawei Integrated Access SoftwareMA5600T/MA5603T/MA5608T.
Copyright(C) Huawei Technologies Co., Ltd. 2002-2012. All rights reserved.
Issue 01 (2016-04-29)

30

Access Module
1 Commissioning
----------------------------------------------------------------------------User last login information:

----------------------------------------------------------------------------Access Type : Telnet
IP-Address : 10.10.10.122
Login Time : 2011-03-29 16:03:20+08:00
Logout Time : 2011-03-29 16:08:40+08:00
--------------------------------------------------------------------------------------------------------------------------------------------------------User fail login information:
----------------------------------------------------------------------------Last Access Type
: Telnet
Last IP-Address
: 10.10.10.74
Last Login Time
: 2011-03-29 16:11:10+08:00
Login Failure Times : 2
--------------------------------------------------------------------------------------------------------------------------------------------------------All user fail login information:
----------------------------------------------------------------------------Access Type IP-Address
Time
Login Times
----------------------------------------------------------------------------Telnet
10.10.10.74
2011-03-29 16:11:10+08:00
1
Telnet
10.10.10.122
2011-03-29 15:37:05+08:00
3
Telnet
10.10.10.193
2011-03-25 18:19:04+08:00
1
-----------------------------------------------------------------------------
The following table describes the parameters in response to this login.
Issue 01 (2016-04-29)
Parameter
Description
User name
Indicates the user name.
User password
Indicates the user password that is not displayed on the

maintenance terminal.
User last login

information
Indicates the information about the latest successful login.
Access Type
Indicates the access type of the latest successful login.
IP-Address
Indicates the IP address of the latest successful login.
Login Time
Indicates the time of the latest successful login.
Logout Time
Indicates the time of the latest successful logout. If the user

does not log out, it displays as "--".
User fail login

information
Indicates the information about the failed login.
Last Access Type
Indicates the access type of the latest failed login.
Last IP-Address
Indicates the IP address of the latest failed login.
Last Login Time
Indicates the time of the latest failed login.
Login Failure Times
Indicates the failed login times. It is the times of login

failures between two login successes, but not the
accumulative login failures.
All user fail login

information
Indicates the information about failed login of all users,

which can be viewed only by user root or security
administrator.

31

Access Module
1 Commissioning
Parameter
Description
Access Type
Indicates the access type of the login.
IP-Address
Indicates the IP address of the login.
Time
Indicates the time of the login.
Login Times
Indicates the login times.
----End
Result
After logging in to the system, you can maintain and manage the MA5600T/MA5603T/
MA5608T.
NOTE
Follow-up Procedure
l
modes.
Figure 1-17
Login
quit
User mode
huawei>
enable
disable
Privilege mode
huawei#
config
quit
Global config mode

huawei(config)#
interface
quit
return
Login Through Telnet (Inband Management)

This topic describes how to log in to the MA5600T/MA5603T/MA5608T using the upstream
port (inband management port) in the telnet mode to maintain and manage the MA5600T/
MA5603T/MA5608T. You are advised to use SSH mode.
Prerequisites
or the ETH port.
Issue 01 (2016-04-29)

32

Access Module
1 Commissioning
NOTE

Networking
Figure 1-18 shows an example network for inband management through telnet in a LAN, and
Figure 1-19 shows an example network for inband management through telnet in a WAN.
NOTE
In this network, the SCUB control board (in slot 9 or 10) is used for upstream transmission, and the
upstream port is 0/19/0. In addition, the GIU upstream interface board (in slot 19 or 20) can be used for
upstream transmission. Alternatively, you need to run the electro-switch0 location-1 command to
switch the electronic switch to the GIU upstream interface board for upstream transmission. By default,
the electronic switch is in the location-0 state, which indicates that the control board is used for
upstream transmission.
Figure 1-18 Example network for inband management through telnet in a LAN
LAN
PC
LSW
PC
Access node
PC
Issue 01 (2016-04-29)

33

Access Module
1 Commissioning
Figure 1-19 Example network for inband management through telnet in a WAN
Access node
PC
Router
Data Plan
Table 1-14 and Table 1-15 provide the data plan for the inband management through telnet in
a LAN and in a WAN respectively.
Table 1-14 Data plan for the inband management through telnet in a LAN
Item
Data
Upstream port of the MA5600T/MA5603T/

MA5608T
l VLAN ID: 30
l Port: 0/19/0
l IP address: 10.50.1.10/24

Ethernet port)
Table 1-15 Data plan for the inband management through telnet in a WAN
Item
Data

MA5608T
l VLAN ID: 30
l Port: 0/19/0
l IP address: 10.50.1.10/24
IP address: 10.10.1.10/24

MA5603T/MA5608T
IP address: 10.50.1.1/24
Flowchart
through telnet (inband management).
Issue 01 (2016-04-29)

34

Access Module
1 Commissioning
Figure 1-20 Flowchart for logging in to the MA5600T/MA5603T/MA5608T through telnet

(inband management)
Procedure
l
If you log in to the MA5600T/MA5603T/MA5608T in the LAN inband management

If you log in to the MA5600T/MA5603T/MA5608T in the WAN inband management

Step 2 Configure the IP address of the VLAN Layer 3 interface.

1.
Run the vlan command to create a management VLAN.

huawei(config)#vlan 30 standard
2.
Run the port vlan command to add an upstream port to the VLAN.
huawei(config)#port vlan 30 0/19 0
3.
In the VLANIF mode, run the ip address command to configure the IP address of the
VLAN Layer 3 interface.
huawei(config)#interface vlanif 30
huawei(config-if-vlanif30)#ip address 10.50.1.10 24
huawei(config-if-vlanif30)#quit
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.
Step 3 Add a route for the inband management.

Issue 01 (2016-04-29)

35

Access Module
1 Commissioning
Step 4 Run the telnet application.

On the maintenance terminal, choose Start > Run. On the Run window, input "telnet
10.50.1.10" in the Open field as shown in Figure 1-21 (considering the Windows OS as an
example), and click OK. Then, the telnet dialog box is displayed.
Figure 1-21 Running the telnet application

In the telnet dialog box, input the user name and the password. By default, the user name is
root, and the password is admin. When the login is successful, the system displays the
following information:
>>User name:root
>>User password:
Huawei Integrated Access SoftwareMA5600T/MA5603T/MA5608T.
Copyright(C) Huawei Technologies Co., Ltd. 2002-2012. All rights reserved.
----------------------------------------------------------------------------User last login information:
----------------------------------------------------------------------------Access Type : Telnet
IP-Address : 10.10.10.122
Login Time : 2011-03-29 16:03:20+08:00
Logout Time : 2011-03-29 16:08:40+08:00
--------------------------------------------------------------------------------------------------------------------------------------------------------User fail login information:
----------------------------------------------------------------------------Last Access Type
: Telnet
Last IP-Address
: 10.10.10.74
Last Login Time
: 2011-03-29 16:11:10+08:00
Login Failure Times : 2
--------------------------------------------------------------------------------------------------------------------------------------------------------All user fail login information:
----------------------------------------------------------------------------Access Type IP-Address
Time
Login Times
-----------------------------------------------------------------------------
Issue 01 (2016-04-29)

36

Access Module
1 Commissioning
Telnet
10.10.10.74
2011-03-29 16:11:10+08:00
1
Telnet
10.10.10.122
2011-03-29 15:37:05+08:00
3
Telnet
10.10.10.193
2011-03-25 18:19:04+08:00
1
-----------------------------------------------------------------------------
The following table describes the parameters in response to this login.

Parameter
Description
User name
Indicates the user name.
User password
Indicates the user password that is not displayed on the

User last login

information
Indicates the information about the latest successful login.
Access Type
Indicates the access type of the latest successful login.
IP-Address
Indicates the IP address of the latest successful login.
Login Time
Indicates the time of the latest successful login.
Logout Time
Indicates the time of the latest successful logout. If the user

does not log out, it displays as "--".
User fail login

information
Indicates the information about the failed login.
Last Access Type
Indicates the access type of the latest failed login.
Last IP-Address
Indicates the IP address of the latest failed login.
Last Login Time
Indicates the time of the latest failed login.
Login Failure Times
Indicates the failed login times. It is the times of login

failures between two login successes, but not the
accumulative login failures.
All user fail login

information
Indicates the information about failed login of all users,

which can be viewed only by user root or security
administrator.
Access Type
Indicates the access type of the login.
IP-Address
Indicates the IP address of the login.
Time
Indicates the time of the login.
Login Times
Indicates the login times.
----End
Result
MA5608T.
Issue 01 (2016-04-29)

37

Access Module
1 Commissioning
NOTE
Follow-up Procedure
l
modes.
Figure 1-22
Login
quit
User mode
huawei>
enable
disable
Privilege mode
huawei#
config
quit
Global config mode

huawei(config)#
interface
quit
return
Login Through SSH (Outband Management)

This topic describes how to log in to the MA5600T/MA5603T/MA5608T using the local
maintenance Ethernet port (outband management port) in the secure shell (SSH) mode to
maintain and manage the MA5600T/MA5603T/MA5608T. The SSH provides authentication,
encryption, and authorization to ensure the network communication security. When a user
logs in to the MA5600T/MA5603T/MA5608T remotely over an insecure network, SSH
provides security guarantee and powerful authentication to protect the MA5600T/MA5603T/
MA5608T against attacks such as IP address spoofing and interception of plain text password.
Prerequisites
or the ETH port.
NOTE
Issue 01 (2016-04-29)

38

Access Module
1 Commissioning
Networking
Figure 1-23 shows an example network for outband management through SSH in a LAN, and
Figure 1-24 shows an example network for outband management through SSH in a WAN.
Figure 1-23 Example network for outband management through SSH in a LAN
Access node
LSW
LAN
PC
PC
PC
NOTE
The MA5600T/MA5603T/MA5608T is connected to the LAN using the straight using cable, and the IP
address of the maintenance Ethernet port of the MA5600T/MA5603T/MA5608T is in the same network
segment as the IP address of the maintenance terminal. Alternatively, the Ethernet port of the
maintenance terminal can be directly connected to the maintenance Ethernet port of the MA5600T/
MA5603T/MA5608T to manage the MA5600T/MA5603T/MA5608T in the outband management
mode. In such a condition, if the MA5600T/MA5603T/MA5608T uses SCUL/SCUB control board, and
the peer device does not support the cable autosensing function, a crossover cable must be used.
Figure 1-24 Example network for outband management through SSH in a WAN
PC
LAN
Router
PC
Issue 01 (2016-04-29)
PC

Access node
39

Access Module
1 Commissioning
Data Plan
Table 1-16 and Table 1-17 provide the data plan for the outband management through SSH in
Table 1-16 Data plan for the outband management through SSH in a LAN
Item
Data

MA5600T/MA5603T/MA5608T
l IP address: 10.50.1.10/24
l User authentication mode: RSA public
key authentication
l RSA key name: key
NOTE
255.255.255.0.
l User name/Password: huawei/test01
New user
l Authority: Operator
l Permitted reenter number: 4

Ethernet port)
Table 1-17 Data plan for the outband management through SSH in a WAN
Item
Data

MA5600T/MA5603T/MA5608T
l IP address: 10.50.1.10/24
key authentication
l RSA key name: key
NOTE
255.255.255.0.
New user
Issue 01 (2016-04-29)
IP address: 10.10.1.10/24

MA5603T/MA5608T
IP address: 10.50.1.1/24

40

Access Module
1 Commissioning
Flowchart
through SSH.
Issue 01 (2016-04-29)

41

Access Module
1 Commissioning
Figure 1-25 Flowchart for logging in to the MA5600T/MA5603T/MA5608T through SSH

(Outband Management)
Issue 01 (2016-04-29)

42

Access Module
1 Commissioning
Procedure
l
If you log in to the MA5600T/MA5603T/MA5608T in the LAN outband management

mode through SSH, set up a network environment according to Figure 1-23.
If you log in to the MA5600T/MA5603T/MA5608T in the WAN outband management

Step 2 Configure the IP address of the maintenance Ethernet port.

In the MEth mode, run the ip address command to configure the IP address of the
maintenance Ethernet port.
huawei(config-if-meth0)#ip address 10.50.1.10 24
Step 3 Add a route for the outband management.

l
Step 4 Create a user.

Run the terminal user name command to create a user.
huawei(config)#terminal user name
User Name(length<6,15>):huawei
User Password(length<6,15>):test01 //The password is not displayed on the
Confirm Password(length<6,15>):test01 //The password is not displayed on the
User profile name(<=15 chars)[root]:
User's Level:
1. Common User 2. Operator:2
Permitted Reenter Number(0--4):4
User's Appended Info(<=30 chars):
Adding user succeeds
Repeat this operation? (y/n)[n]:n
Step 5 Create the local RSA key pair.

Run the rsa local-key-pair create command to create the local RSA key pair.
NOTICE
The prerequisite for the login through SSH is that the local RSA key pair must be configured
and generated. Therefore, before performing other SSH configurations, make sure that the
local RSA key pair is generated.
huawei(config)#rsa local-key-pair create
The key name will be: Host
The range of public key size is (512 ~ 2048).
NOTES: If the key modulus is greater than 512,
It will take a few minutes.
Input the bits in the modulus[default = 512]:
Generating keys...
..++++++++++++
....................++++++++++++
Issue 01 (2016-04-29)

43

Access Module
1 Commissioning
...............................++++++++
...........++++++++
Step 6 Set the SSH user authentication mode.

Run the ssh user huawei authentication-type rsa command to choose the authentication
mode of the SSH user.
There are four authentication modes for SSH users, as shown in the following. In this topic,
authentication mode rsa is considered as an example.
l
password: authentication based on a password.
rsa: authentication based on an RSA public key.
all: authentication based on a password or an RSA public key. The user can log in to the
device either by the password or the RSA public key.
password-publickey: authentication based on a password and a public key. The user can
log in to the device only after both the password and the RSA public key authentication.
huawei(config)#ssh user huawei authentication-type

{ all<K>|password-publickey<K>|password<K>|rsa<K> }:rsa
Command:
ssh user huawei authentication-type rsa
%Authentication type setted, and will be in effect next time.
Step 7 Generate the RSA public key.

1.
Run the key generator.

Run the client software key generator Puttygen.exe. Figure 1-26 shows the interface of
the key generator.
Figure 1-26 Interface of the key generator
Issue 01 (2016-04-29)

44

Access Module
2.
1 Commissioning
Generate the client key.

Select SSH-2 RSA as the key type under Parameters, click Generate, and move the
cursor according to the prompt on the interface to generate the client key, as shown in
Figure 1-27.
Click Save public key and Save private key to save the public key and the private key
respectively after they are generated, as shown in Figure 1-28.
Issue 01 (2016-04-29)

45

Access Module
1 Commissioning
Figure 1-28 Save the public key and the private key
3.
Generate the RSA public key.

Open sshkey.exe, click Browse, and choose the public key file saved in the preceding
step. Then, click Convert to change the client public key to the RSA public key, as
shown in Figure 1-29.
Issue 01 (2016-04-29)

46

Access Module
1 Commissioning
Figure 1-29 Interface of converting the client public key to the RSA public key
Step 8 Generate the public key for the SSH user.

Create RSA public key. Copy the RSA public key to the server in the config-rsa-key-code
command line mode.
huawei(config)#rsa peer-public-key key
Enter "RSA public key" view, return system view with "peer-public-key end".
NOTE: The number of the bits of public key must be between 769 and 2048.
huawei(config-rsa-public-key)#public-key-code begin
Enter "RSA key code" view, return last view with "public-key-code end".
huawei(config-rsa-key-code)#30818702 81810098 933744B6 7C864EC7 A86A84CC 198BAC1
5
huawei(config-rsa-key-code)#D32834F7 365CFD17 E7FE4041 3266E416 710D13ED 22BD4D5
9
huawei(config-rsa-key-code)#DF0C3E46 A995CC61 DC4CB179 F6888B8C 3F8A3085 51EDB5C
7
huawei(config-rsa-key-code)#5DEBDBE1 3AB4A256 0D0B9AA8 9A419D85 35C0E562 AE0BBFA
B
huawei(config-rsa-key-code)#515299F9 D2803E84 3AE36C20 949367EA 0697EB20 2594A77
4
huawei(config-rsa-key-code)#9A0EFF04 26928874 FF9124C4 D28F0702 0125
huawei(config-rsa-key-code)#public-key-code end
Issue 01 (2016-04-29)

47

Access Module
1 Commissioning
huawei(config-rsa-public-key)#peer-public-key end
Step 9 Assign the public key to the SSH user.

Run the ssh user assign rsa-key command to assign the RSA public key to the SSH user.
huawei(config)#ssh user huawei assign rsa-key key

1.
Run the client software.

Run the SSH client software putty.exe, choose SSH > Auth from the navigation tree, and
assign a file for the RSA private key, as shown in Figure 1-30. Click Browse to display
the window for selecting the file. In the window, select the file for the private key, and
click OK.
Figure 1-30 Interface of the SSH client software
2.
Log in to the system.

Choose Session from the navigation tree, and then input the IP address of the MA5600T/
MA5603T/MA5608T in the Host Name (or IP address) field, as shown in Figure 1-31.
Then, click Open to log in to the system.
Issue 01 (2016-04-29)

48

Access Module
1 Commissioning
Figure 1-31 Interface for logging in to the system using the SSH client software
The user authentication mode is set to the RSA authentication mode, and the system
therefore displays the prompt, as shown in Figure 1-32. Input the user name to log in to
the system (here, the user name is huawei).
----End
Issue 01 (2016-04-29)

49

Access Module
1 Commissioning
Result
MA5608T.
NOTE
Follow-up Procedure
l
modes.
Figure 1-33
Login
quit
User mode
huawei>
enable
disable
Privilege mode
huawei#
config
quit
Global config mode

huawei(config)#
interface
quit
return
Login Through SSH (Inband Management)

This topic describes how to log in to the MA5600T/MA5603T/MA5608T using the upstream
port (inband management port) in the secure shell (SSH) mode to maintain and manage the
MA5600T/MA5603T/MA5608T. The SSH provides authentication, encryption, and
authorization to ensure the network communication security. When a user logs in to the
MA5600T/MA5603T/MA5608T remotely over an insecure network, SSH provides security
guarantee and powerful authentication to protect the MA5600T/MA5603T/MA5608T against
attacks such as IP address spoofing and interception of plain text password.
Prerequisites
or the ETH port.
NOTE
Issue 01 (2016-04-29)
50

Access Module
1 Commissioning

Networking
Figure 1-34 shows an example network for inband management through SSH in a LAN, and
Figure 1-35 shows an example network for inband management through SSH in a WAN.
NOTE
In this network, the SCUB control board (in slot 9 or 10) is used for upstream transmission, and the
upstream port is 0/9/0. Alternatively, the GIU upstream interface board (in slot 19 or 20) can be used for
upstream transmission. In this case, you need to run the electro-switch0 location-1 command to switch
the electronic switch to the GIU upstream interface board for upstream transmission. By default, the
electronic switch is in the location-0 state, which indicates the control board is used for upstream
transmission.
Figure 1-34 Example network for inband management through SSH in a LAN
LAN
PC
LSW
PC
Access node
PC
Figure 1-35 Example network for inband management through SSH in a WAN
Access node
Issue 01 (2016-04-29)
Router

PC
51

Access Module
1 Commissioning
Data Plan
Table 1-18 and Table 1-19 provide the data plan for the inband management through SSH in
Table 1-18 Data plan for the inband management through SSH in a LAN
Item
Data

MA5608T
l VLAN ID: 30
l Port: 0/9/0
l IP address: 10.50.1.10/24
key authentication
l RSA key name: key
New user

Ethernet port)
Table 1-19 Data plan for the inband management through SSH in a WAN
Item
Data

MA5608T
l VLAN ID: 30
l Port: 0/9/0
l IP address: 10.50.1.10/24
key authentication
l RSA key name: key
New user
IP address: 10.10.1.10/24

MA5603T/MA5608T
IP address: 10.50.1.1/24
Flowchart
through SSH.
Issue 01 (2016-04-29)

52

Access Module
1 Commissioning
Figure 1-36 Flowchart for logging in to the MA5600T/MA5603T/MA5608T through SSH

(Inband Management)
Issue 01 (2016-04-29)

53

Access Module
1 Commissioning
Procedure
l
If you log in to the MA5600T/MA5603T/MA5608T in the LAN inband management

If you log in to the MA5600T/MA5603T/MA5608T in the WAN inband management


1.
Run the vlan command to create a management VLAN.

2.
Run the port vlan command to add an upstream port to the VLAN.
3.
In the VLANIF mode, run the ip address command to configure the IP address of the
VLAN Layer 3 interface.
NOTE
Step 3 Add a route for the inband management.

l
Step 4 Create a user.

Run the terminal user name command to create a user.
User Password(length<6,15>):test01 //The password is not displayed on the
Confirm Password(length<6,15>):test01 //The password is not displayed on the
User's Level:
User's Appended Info(<=30 chars):
Step 5 Create the local RSA key pair.

Run the rsa local-key-pair create command to create the local RSA key pair.
NOTICE
The prerequisite for the login through SSH is that the local RSA key pair must be configured
and generated. Therefore, before performing other SSH configurations, make sure that the
local RSA key pair is generated.
Issue 01 (2016-04-29)

54

Access Module
1 Commissioning
huawei(config)#rsa local-key-pair create

The key name will be: Host
The range of public key size is (512 ~ 2048).
NOTES: If the key modulus is greater than 512,
It will take a few minutes.
Input the bits in the modulus[default = 512]:
Generating keys...
..++++++++++++
....................++++++++++++
...............................++++++++
...........++++++++
Step 6 Set the SSH user authentication mode.

Run the ssh user huawei authentication-type rsa command to choose the authentication
mode of the SSH user.
There are four authentication modes for SSH users, as shown in the following. In this topic,
authentication mode rsa is considered as an example.
l
password: authentication based on a password.
rsa: authentication based on an RSA public key.
all: authentication based on a password or an RSA public key. The user can log in to the
device either by the password or the RSA public key.
password-publickey: authentication based on a password and a public key. The user can
log in to the device only after both the password and the RSA public key authentication.
huawei(config)#ssh user huawei authentication-type

{ all<K>|password-publickey<K>|password<K>|rsa<K> }:rsa
Command:
ssh user huawei authentication-type rsa
%Authentication type setted, and will be in effect next time.
Step 7 Generate the RSA public key.

1.
Run the key generator.

Run the client software key generator Puttygen.exe. Figure 1-37 shows the interface of
the key generator.
Issue 01 (2016-04-29)

55

Access Module
1 Commissioning
2.
Generate the client key.

Select SSH-2 RSA as the key type under Parameters, click Generate, and move the
cursor according to the prompt on the interface to generate the client key, as shown in
Figure 1-38.
Issue 01 (2016-04-29)

56

Access Module
1 Commissioning
Click Save public key and Save private key to save the public key and the private key
respectively after they are generated, as shown in Figure 1-39.
Figure 1-39 Save the public key and the private key
Issue 01 (2016-04-29)

57

Access Module
3.
1 Commissioning
Generate the RSA public key.

Open sshkey.exe, click Browse, and choose the public key file saved in the preceding
step. Then, click Convert to change the client public key to the RSA public key, as
Figure 1-40 Interface of converting the client public key to the RSA public key
Step 8 Generate the public key for the SSH user.

Create RSA public key. Copy the RSA public key to the server in the config-rsa-key-code
command line mode.
huawei(config)#rsa peer-public-key key
Enter "RSA public key" view, return system view with "peer-public-key end".
NOTE: The number of the bits of public key must be between 769 and 2048.
huawei(config-rsa-public-key)#public-key-code begin
Enter "RSA key code" view, return last view with "public-key-code end".
huawei(config-rsa-key-code)#30818702 81810098 933744B6 7C864EC7 A86A84CC 198BAC1
5
huawei(config-rsa-key-code)#D32834F7 365CFD17 E7FE4041 3266E416 710D13ED 22BD4D5
9
huawei(config-rsa-key-code)#DF0C3E46 A995CC61 DC4CB179 F6888B8C 3F8A3085 51EDB5C
7
Issue 01 (2016-04-29)

58

Access Module
1 Commissioning
huawei(config-rsa-key-code)#5DEBDBE1 3AB4A256 0D0B9AA8 9A419D85 35C0E562 AE0BBFA

B
huawei(config-rsa-key-code)#515299F9 D2803E84 3AE36C20 949367EA 0697EB20 2594A77
4
huawei(config-rsa-key-code)#9A0EFF04 26928874 FF9124C4 D28F0702 0125
huawei(config-rsa-key-code)#public-key-code end
huawei(config-rsa-public-key)#peer-public-key end
Step 9 Assign the public key to the SSH user.

Run the ssh user assign rsa-key command to assign the RSA public key to the SSH user.
huawei(config)#ssh user huawei assign rsa-key key

1.
Run the client software.

Run the SSH client software putty.exe, choose SSH > Auth from the navigation tree, and
assign a file for the RSA private key, as shown in Figure 1-41. Click Browse to display
the window for selecting the file. In the window, select the file for the private key, and
click OK.
Figure 1-41 Interface of the SSH client software
2.
Log in to the system.

Choose Session from the navigation tree, and then input the IP address of the MA5600T/
MA5603T/MA5608T in the Host Name (or IP address) field, as shown in Figure 1-42.
Then, click Open to log in to the system.
Issue 01 (2016-04-29)

59

Access Module
1 Commissioning
The user authentication mode is set to the RSA authentication mode, and the system
therefore displays the prompt, as shown in Figure 1-43. Input the user name to log in to
the system (here, the user name is huawei).
----End
Issue 01 (2016-04-29)

60

Access Module
1 Commissioning
Result
MA5608T.
NOTE
Follow-up Procedure
l
modes.
Figure 1-44
Login
quit
User mode
huawei>
enable
disable
Privilege mode
huawei#
config
quit
Global config mode

huawei(config)#
interface
quit
return
1.3.6 Checking the Software State

This topic describes how to verify that current software state meets the deployment
requirement.
Procedure
Step 1 Run the display language command to check whether the version of the host software meets
the deployment requirement.
Step 2 Run the display patch command to check whether the version of the patch meets the
deployment requirement.
Step 3 Run the display version command to check whether the version of the board software meets
the deployment requirement.
Step 4 Run the display board command to check whether the state of the boards meets the
deployment requirement.
l
In the integrated access scenario (involving optical, xDSL, and voice access), use the
default configurations.
In the broadband access scenario (involving only optical and xDSL access), use the
system workscene command to switch the scenario mode of the SCUN board to the
OLT mode, ensuring that the memory is allocated properly and services are processed
smoothly.
----End
Issue 01 (2016-04-29)

61

Access Module
1 Commissioning
Result
l
The version of the host software, the version of the patch, the version of the boards and
the state of the board software meet the deployment requirement.
If the version of the host software and the version of the board software do not meet the
deployment requirement, contact the Huawei Customer Service Center. Upgrade the host
software if necessary.
Example
To query the host software state that is running in the system, do as follows:
huawei>display language
Local:
Description: CHINESE SIMPLIFIED (DEFAULT LANGUAGE)
Version:
MA5600V800R0012C00
Encoding:
GBK
General:
Description: ENGLISH (DEFAULT LANGUAGE)
Version:
MA5600V800R012C00
Encoding:
ANSI
huawei(config)#display patch all
Software Version:MA5600V800R012C00
-----------------------------------------------------------------------Current Patch State:
-----------------------------------------------------------------------Patch Name
Patch State
Delivery
Attribute
Dependency
----------------------------------------------------------------------------------------------------------------------------------------------Total:0
Patches in the system cannot be rolled back
huawei>display version
{ <cr>|backplane<K>|frameid/slotid<S><Length 1-15> }:
Command:
display version
VERSION : MA5600V800R012C00
PRODUCT :
Active Mainboard Running Area Information:
-------------------------------------------------Current Program Area : Area A
Current Data Area : Area A
Program Area A Version : MA5600V800R012C00
Program Area B Version : MA5600V800R012C00
Data Area A Version : MA5600V800R012C00
Data Area B Version : MA5600V800R012C00
-------------------------------------------------Uptime is 0 day(s), 0 hour(s), 0 minute(s), 50 second(s)
huawei#display version
Main Board: H801SCUN
--------------------------------------PCB
Version: H801SCUN VER B
Base
BIOS Version: 216
Extended BIOS Version: 222
Software
Version: MA5600V800R012C00
Logic
Version: (U48)115
MAB
Version: 0002
huawei#display board 0
------------------------------------------------------------------------SlotID BoardName Status
SubType0 SubType1
Online/Offline
Issue 01 (2016-04-29)

62

Access Module
1 Commissioning
------------------------------------------------------------------------0
1
H802ADPD
Normal
2
H805ADPD
Normal
3
H801EPBA
Normal
4
5
6
7
H801GPBC
Normal
8
H802SHLB
Normal
9
H801SCUN
Active_normal
10
11
H802EDTB
Normal
12
---- More ( Press 'Q' to break ) ----
1.3.7 Loading a Configuration Script

You can run the commands in the configuration script in batches by loading the configuration
script instead of running the commands one by one. This shortens the commissioning duration
and improves the commissioning efficiency. If you do not use the configuration script to
perform the commissioning, skip this operation, and follow the commissioning procedure to
perform the subsequent operations.
Prerequisites
l
The hardware must be installed and checked.
The configuration script must be prepared. For details about how to prepare a
configuration script, see 1.6.1 Script Making.
The TFTP/FTP/SFTP server can normally communicate with the device, and the file
path on the server is set correctly before you load the configuration script. For the
detailed operation procedure, see 1.6.2 Configuring the File Transfer Mode .
The operator is in the privilege mode.
There are two methods for loading the configuration script. You can select one of them.
Procedure
Importing the configuration script

i.
Run the load configuration command to load the configuration script on the
file server (TFTP/FTP/SFTP server) to the control board of the device.
ii.
Run the active configuration system command to activate the configuration.
iii. Log in to the system using the default user name and password after the system
restarts.
iv.
Run the save command to save the configuration file and make the new
configuration take effect.
Copying commands in the configuration script

i.
Open the configuration script, and copy the commands in the configuration
script to the command line interface (CLI). However, the following contents
must be deleted. Otherwise, the script loading will fail.
Delete the following tags.

#
[global-config]
<global-config>
Issue 01 (2016-04-29)
Delete all the commands related to terminal user name.

63

Access Module
1 Commissioning
NOTICE
If you use this method to load the configuration script, you must enter the
global config mode. The user level must be operation level at least. The
administrator level is recommended.
----End
Result
The loaded configuration script takes effect.
1.3.8 Changing the System Name

This topic describes how to customize the useful system name to differentiate MA5600T/
MA5603T/MA5608Ts. This facilitates the management of the MA5600T/MA5603T/
MA5608T.
Context
l
By default, the system name is device name.
The system name takes effect immediately after change.
After the system name is changed, the CLI prompt character changes to the new name
accordingly.
Procedure
Step 1 Run the sysname command to set the system name.
----End
Result
The CLI prompt character changes to the system name that is set after the command is
executed successfully.
Example
To name the first MA5600T/MA5603T/MA5608T at Longgang (a district in Shenzhen,
Guangdong, China) guangdong_shenzhen_longgang_MA5600T/MA5603T/MA5608T_A
based on the rule province_city_district_device name_SN, do as follows:
huawei(config)#sysname guangdong_shenzhen_longgang_MA5600T/MA5603T/MA5608T_A
guangdong_shenzhen_longgang_MA5600T/MA5603T/MA5608T_A(config)#
1.3.9 Configuring the System Time

This topic describes how to configure the system time, time zone, time stamp, NTP (Network
Time Protocol), and start/end time of the daylight saving time (DST) of the MA5600T/
MA5603T/MA5608T to ensure that they are consistent with those in the actual condition.
Issue 01 (2016-04-29)

64

Access Module
1 Commissioning
Procedure
Step 1 Configure the system time.
Run the display time command to query the current system time. If the system time is
consistent with the local standard time, you need not change it. If the system time is
inconsistent with the local standard time, run the time command to change the system time.
Step 2 Configure the system time zone.
Run the display timezone command to query the current system time zone. If the system time
zone is consistent with the local standard time zone, you need not change it. If the system time
zone is inconsistent with the local standard time zone, run the timezone command to change
the system time zone.
NOTE
l The system time zone include the eastern time zone and the western time zone. "GMT+" indicates
the eastern time zone, that is, the local time is ahead of the Greenwich time. "GMT-" indicates the
western time zone, that is, the local time is behind the Greenwich time.
l By default, the system time zone is GMT+8:00.
Step 3 Configure the system time stamp.

Run the display time time-stamp command to query the time stamp between the NMS and
the NE, namely the displayed time format of the SNMP interface. If the system time stamp is
consistent with the actual data plan, you need not change it. If the system time stamp is
inconsistent with the actual data plan, run the time time-stamp command to change the
system time stamp.
NOTE
The time type of the SNMP interface between the NMS and the NE are categorized as UTC time and NE
local time. By default, the time type is the NE local time.
Step 4 Configure NTP to ensure that the clock of all devices in the network is the same.
l
(Optional) Run the ntp-service refclock-master command to configure the NTP master
clock.
Run the ntp-service unicast-server command to configure the NTP unicast server
mode, and specify the IP address of the remote server that functions as the local time
server and the interface for transmitting and receiving NTP packets.
NOTE
l The NTP protocol supports the client/server, peer, broadcast, and multicast working modes. The
following uses the client/server mode as an example.
l The L3 interface and the interface IP address must be available for the client and the server to
communicate with each other.
l In the client/server mode, you need to configure only the client and the NTP master clock of the
server.
l In the client/server mode, the client is synchronized to the server but the server will not be
synchronized to the client.
l The clock stratum of the synchronizing device must be smaller than that of the synchronized device.
Otherwise, the clock synchronization fails.
l The device that runs the NTP protocol can be synchronized to other clock sources or function as the
clock source for synchronizing other clocks. In addition, this device and other devices can be set to
synchronized from each other. When the device works in the client mode, you need not set the
system time and the device is automatically synchronized to the remote server.
Step 5 Configure the start/end time of the DST.

Issue 01 (2016-04-29)

65

Access Module
1 Commissioning
Run the display time dst command to query the current start/end time of the DST of the
system. If the start/end time of the DST is consistent with the actual start/end time of the DST,
you need not change it. If the start/end time of the DST is inconsistent with the actual
start/end time of the DST, run the time dst command to change the start/end time of the DST.
----End
Result
The system time, time zone, time stamp, NTP, and start/end time of the DST are consistent
with those in the actual condition.
Example
To set the time stamp between the NMS and the NE to use the UTC time, do as follows:
huawei#time time-stamp
{ local<K>|utc<K> }:utc
Command:
time time-stamp utc
Assume that the current time zone of MA5600T/MA5603T/MA5608T A is GMT+7:00, the

device uses the network clock to adjust the time, and VLAN interface 2 is used to sent a clock
synchronization request packet to MA5600T/MA5603T/MA5608T B (the IP address is
10.20.20.20/24 and the device works at layer 4) that functions as the NTP server. The start
time is 00:00:00 on May 1, the end time is 00:00:00 on September 30, and the adjust time is
1:00. That is, if the local time is 5:00, the time is adjusted to 6:00. To set the DST, do as
follows:
huawei(config)A#timezone GMT+ 7:00
huawei(config)B#ntp-service refclock-master 4
huawei(config)A#ntp-service unicast-server 10.20.20.20 source-interface vlanif 2
huawei(config)A#time dst start 5-1 00:00:00 end 9-30 00:00:00 adjust 1:00
Assume that the current time zone of MA5600T/MA5603T/MA5608T A is GMT- 4:00, the
local time is used, the current time is 2010-01-01 12:10:10. The start time is 00:00:00 on May
1, the end time is 00:00:00 on September 30, and the adjust time is 2:00. That is, if the local
time is 5:00, the time is adjusted to 7:00. To set the DST, do as follows:
huawei(config)A#timezone GMT- 4:00
huawei(config)A#time 2010-01-01 12:10:10
huawei(config)A#time dst start 5-1 00:00:00 end 9-30 00:00:00 adjust 2:00
1.3.10 Configuring a System User

For logging in to, configuring, and managing the MA5600T/MA5603T/MA5608T, system
users of different attributes need to be added. This topic describes how to add a system user
and modify the user attributes.
Adding a System User

This topic describes how to add system users of different attributes for logging in to,
configuring, and managing the MA5600T/MA5603T/MA5608T. This facilitates the
management of the MA5600T/MA5603T/MA5608T.
Prerequisites
You must have the administrator authority or higher authority.
Issue 01 (2016-04-29)

66

Access Module
1 Commissioning
Context
l
The super user and the administrator have the authority to add a user at a lower level,
that is:
The super user can add an administrator, an operator, or a common user.
The administrator can add only an operator or a common user.
By default, the system has a super user with the name of root and password of admin123.
The super user cannot be added or deleted. To enhance system security, run the terminal
user password command to change the password to meet the requirement after the first
successful login. It is recommended that you change the password periodically.
The user name must be unique, and cannot be all or online.
The super user and the administrator can add multiple users consecutively. Up to 127
(total 128 including the root user) users can be added to the system.
The terminal session max-number command is used to set the maximum number of users
who are permitted to log in through the CLI at a time. The default value is 22.
When adding a user, you must configure the user attributes, including the user account,
password, profile, authority, permitted reenter number, and appended information. Table 1-20
lists the user attributes.
Table 1-20 User attributes
Issue 01 (2016-04-29)
User Attribute
Description
Account
An account is also called a user name and consists of 6-15 printable

characters. The user name is unique in the system. It cannot contain
any space and is case insensitive.
Password
A password consists of 6-15 characters. It must contain at least one

digit and one letter, and is case-sensitive.
User profile
The name of a user profile consists of 1-15 printable characters. A

user profile includes the validity period of the user name, validity
period of the password, login time, and logout time.

67

Access Module
1 Commissioning
User Attribute
Description
Authority
Users are classified into three levels: common user, operator, and
administrator.
NOTE
According to the operation authority, users of the MA5600T/MA5603T/
MA5608T are classified into four levels: common user, operator, administrator,
and super user. The user at one level can add only the user at a lower level. The
following lists the authority of all users.
l Common users can perform basic system operations and simple query
operations.
l Operators can configure the device and the services.
l For the administrator and the super user, they have the following
similarities and differences:
l Similarities:
l Perform all configurations.
l Maintain and manage the device, user account, and user authority.
l Differences:
l Only one super user exists in the system; however, multiple
administrators can coexist in the system.
l The super user can add an administrator, but an administrator has
no authority to add the super user.
Permitted reenter
number
The permitted reenter number determines whether a user name can be

used to log in to the system from several terminals at the same time.
The permitted reenter number ranges from 0 to 4, and is generally set
to 1.
Appended
information
Appended information is a type of additional information about the

user. It consists of a string of 0-30 characters. It can be the telephone
number or the address of a user.
Procedure
Step 1 Run the terminal user name command to add a user that is consistent with the actual data
plan.
Step 2 Run the display terminal user command to query the user information.
----End
Result
The queried user information is the same as the actual data plan.
Example
With the administrator authority, to add a common user with the account as huawei, password
as test01, user profile as the default root user profile, user level as Common User, permitted
reenter number as 3, and appended information as user, do as follows:
Issue 01 (2016-04-29)

68

Access Module
1 Commissioning
User Password(length<6,15>):test01//The password is not displayed on the

console.
Confirm Password(length<6,15>):test01//The password is not displayed on the
console.
User's Level:
User's Appended Info(<=30 chars):user
huawei(config)#display terminal user name huawei
---------------------------------------------------------------------------Name
Level
Status Reenter Profile
Append
Num
Info
--------------------------------------------------------------------------huawei
User
Offline
3 root
user
----------------------------------------------------------------------------
Modifying the System User Attributes

This topic describes how to modify the attributes of a system user, including the password,
user profile, authority, permitted reenter number, and appended information in the case that
the user attributes are not consistent with the current data plan.
Prerequisites
For details about the user authority, see "Context".
Context
Table 1-21 lists the user attributes that can be modified and the related restrictions.
Table 1-21 Modifying the user attributes
User Attribute
Restriction
Password
l The super user and the administrator can change their own
passwords and the passwords of users at lower levels. When
changing the password of a user at a lower level, the super user
and the administrator need not input the old password.
l The common user and the operator can change only their own
passwords, but they must input their old passwords for this
purpose.
User profile
l The super user and the administrator can modify the profiles
bound to them and the profiles bound to users at lower levels.
l The user name and the password must meet the specifications
described in the user profile to be bound. Otherwise, the binding
operation fails.
Authority
Issue 01 (2016-04-29)
The super user and the administrator can modify the authority of users
at lower levels. In addition, the super user and the administrator can
modify the user authority only to a level lower than them.

69

Access Module
1 Commissioning
User Attribute
Restriction
Permitted reenter
number
l The super user and the administrator can change the permitted
reenter number of a user at a lower level.
l The permitted reenter number of the super user cannot be changed.
Appended
information
l The super user and the administrator can modify their own
appended information and the appended information about users at
lower levels.
l The common user and the operator can modify only their own
appended information.
Procedure
Step 1 Modify the system user attributes.
NOTE
Before modifying the user attributes, run the display terminal user command to query the user
attributes to be modified.
Run the terminal user password command to change the password of a user.
The password of a user consists of 6-15 characters, in which at least one digit and one
letter must be contained. The password is case sensitive.
Run the terminal user user-profile command to modify the profile bound to a user.
Run the terminal user level command to modify the authority of a user.
Run the terminal user reenter command to change the permitted reenter number of a
user.
Run the terminal user apdinfo command to modify the appended information about a
user.
When the system has any problem, you can contact the user after querying the user
appended information. It is recommended that the user appended information be
modified into the information that has the actual meaning, such as the contact means and
the user address.
Step 2 Check the user information.

Run the display terminal user command to query the user information.
----End
Result
The queried user information is consistent with the user attributes that are modified, and login
to the MA5600T/MA5603T/MA5608T by using the original user name and password is
successful.
Example
To modify the attributes of user huawei, including changing the password to test02, user
profile to operator profile, user level to operator, permitted reenter number to 4, and
appended information to operator, do as follows:
huawei(config)#terminal user password
User Name(<=15 chars):huawei
Issue 01 (2016-04-29)

70

Access Module
1 Commissioning
New Password(length<6,15>):test02//The password is not displayed on the console.

Confirm Password(length<6,15>):test02//The password is not displayed on the
console.
Information takes effect
huawei(config)#terminal user user-profile
Permitted user-profile[root]:operator
Confirm user-profile:operator
Configuration will take effect when the user logs on next time.
huawei(config)#terminal user level
1. Common User 2. Operator:
User's Level:2
Confirm Level:2
Information will take effect when this user logs on next time
huawei(config)#terminal user reenter
Confirm Reenter Number(0--4):4
Information will take effect when this user logs on next time
huawei(config)#terminal user apdinfo
User's Appended Info(<=30 chars):operator
Information takes effect
huawei(config)#display terminal user name huawei
---------------------------------------------------------------------------Name
Level
Status Reenter Profile
Append
Num
Info
--------------------------------------------------------------------------huawei
Operator Offline
4 operator
operator
----------------------------------------------------------------------------
1.3.11 Configuring a Board

Specific services require specific boards. To use a board, you need to first confirm the
automatically discovered board or add the board offline.
Adding a Board Offline

This topic describes how to add a board to an idle slot that is consistent with the board
actually planned beforehand to ensure that the board runs immediately the board is installed in
the slot.
Prerequisites
The slot to which a board is added must be idle.
Context
l
The boards other than the control board can be added offline.
After a board is added offline, the board status is displayed as Failed. The board status
becomes normal only when a board of the same type as the board added offline is
installed in the slot. If a board of a different type is installed, the board resets repeatedly
due to the board type mismatch.
Issue 01 (2016-04-29)

71

Access Module
1 Commissioning
Procedure
Step 1 Run the board add command to add a board offline.
NOTE
l The shelf ID and the slot ID of the board added offline must be the same as the actual position.
Otherwise, when the board is installed, the board status cannot be changed to normal.
l The type of the board added offline must be the same as the type of the board installed. Otherwise,
when the board is installed, the board status cannot be changed to normal.
Step 2 Run the display board frameid [ /slotid ] command to query the type of the added board.
----End
Result
The type of the added board is the same as the board type that is planned. When a board is
installed in the slot in which the board is added, the board status is displayed as Normal.
Example
To add a service board GPBD offline in slot 0/2, do as follows:
huawei(config)#board add 0/2 h802gpbd
0 frame 2 slot board added successfully
huawei(config)#display board 0/2
--------------------------------------Board Name
: H802GPBD
Board Status
: Failed
--------------------------------------------------------------------------------------------------Port
Port
min-distance
max-distance
Optical-module
type
(km)
(km)
status
------------------------------------------------------------0
GPON
0
20
1
GPON
0
20
2
GPON
0
20
3
GPON
0
20
4
GPON
0
20
5
GPON
0
20
6
GPON
0
20
7
GPON
0
20
------------------------------------------------------------In port 0, the total of ONTs are: 0
In port 1, the total of ONTs are: 0
Confirming a Board
This topic describes how to confirm a board after the board installed in an idle slot is
automatically discovered. This ensures that the auto-discovered board runs in the normal
state.
Issue 01 (2016-04-29)

72

Access Module
1 Commissioning
Prerequisites
A board must be installed in an idle slot or all the boards in the shelf must be installed. After
that, the system automatically identifies the board type, and the board status is Auto_find.
Procedure
Step 1 Run the board confirm command to confirm an Auto_find board.
NOTE
l To confirm only one board, run the board confirm frameid/slotid command.
l To confirm all the boards in a shelf, run the board confirm frameid command.
Step 2 Run the display board frameid [ /slotid ] command to query the board status.
----End
Result
The board status is displayed as Normal.
Example
To confirm the service board in slot 0/2, do as follows:
huawei(config)#board confirm 0/2
0 frame 2 slot board confirms successfully
huawei(config)#display board 0/2
--------------------------------------Board Name
: ADL
Board Status
: Normal
------------------------------------------------------------------------------------------------------------------Port
Port Type
Port Status
Line Profile Alarm Profile Ext Profile
----------------------------------------------------------------------------0
ADSL
Activating
1002
1
-1
ADSL
Activating
1002
1
-2
ADSL
Activating
1002
1
-3
ADSL
Activating
1002
1
-4
ADSL
Activating
1002
1
-5
ADSL
Activating
1002
1
-6
ADSL
Activating
1002
1
-7
ADSL
Activating
1002
1
-8
ADSL
Activating
1002
1
-9
ADSL
Activating
1002
1
-10
ADSL
Activating
1002
1
-11
ADSL
Activating
1002
1
-12
ADSL
Activating
1002
1
-13
ADSL
Activating
1002
1
-14
ADSL
Activating
1002
1
----- More ( Press 'Q' to break ) ----
Checking the Board Status

This topic describes how to check whether the board works in the normal state.
Issue 01 (2016-04-29)

73

Access Module
1 Commissioning
Procedure
Step 1 Run the display board frameid command to query the status of all the boards.
----End
Result
All the boards work in the normal state. That is, all of the service board status is displayed as
Normal, the active control board status is displayed as Active_normal, and the standby
control board status is displayed as Standby_normal.
Example
To query the information about all the boards of shelf 0, do as follows:
huawei(config)#display board 0
------------------------------------------------------------------------SlotID BoardName Status
SubType0 SubType1
Online/Offline
------------------------------------------------------------------------0
1
2
3
4
H802GPBD
Normal
5
6
H802GPBD
Normal
7
8
9
H801SCUL
Active_normal FLBA
10
11
12
H802GPBD
Normal
13
14
H802GPBD
Normal
15
16
17
H802GPBD
Normal
18
19
H801GICG
Normal
20
21
22
-------------------------------------------------------------------------
1.3.12 Checking the Status of the Upstream Port

This topic describes how to check whether the upstream port is in the normal state.
Procedure
Step 1 Follow the steps below to check the status of the upstream port.
l
l
Issue 01 (2016-04-29)
If the control board is adopted for upstream transmission, do as follows:

a.
For the MCU control board, run the interface mcu command to enter the MCU
mode. For other control boards, run the interface scu command to enter the SCU
mode.
b.
Run the display port state all command to check whether the upstream port is in
the normal state.
If the upstream board is adopted for upstream transmission, do as follows:

74

Access Module
1 Commissioning
a.
Run the interface giu command to enter the GIU mode.
b.
Run the display port state all command to check whether the upstream port is in
the normal state.
----End
Result
The upstream port is in the normal state. That is, the upstream port is in the active state and
the link is in the online state. If the optical port is adopted for upstream transmission, Optic
Status is displayed as normal.
1.3.13 Checking the Status of the Service Port

This topic describes how to check whether the service port is in the normal state.
Prerequisites
NOTE
The MA5600T/MA5603T/MA5608T provides various service ports. The following only describes how
to check the status of an ADSL2+ port and a GPON port.
Procedure
Step 1 Follow the steps below to check the status of the service port.
l
If the user port is an ADSL2+ port:

a.
Run the interface adsl command to enter the ADSL mode.
b.
Run the display port state command to check whether the service port is in the
normal state.
If the user port is a GPON port:

a.
Run the interface gpon command to enter the GPON mode.
b.
Run the display port state command to check whether the service port is in the
normal state.
----End
Result
All the service ports are in the normal state. That is :
l
If the user port is an ADSL2+ port: Status is displayed as Activated.
If the user port is a GPON port: Status is displayed as Activated, and Laser state is
displayed as Normal.
1.3.14 Enabling the ONT Automatic Discovery function

After the ONT automatic discovery function is enabled, online ONTs can be automatically
displayed on the OLT.
Procedure
Step 1 Run the port portid ont-auto-find command to enable the auto discovery function of the
ONT.
Issue 01 (2016-04-29)

75

Access Module
1 Commissioning
Step 2 Run the port fec(gpon)command to enable the forward error correction (FEC) function.
NOTE
Only GPON port and 10G GPON port support this operation.
----End
Result
Run the display port info command to query the configuration.
huawei(config-if-gpon-0/3)#display port info
{ portid<0,7> }:0
Command:
display port info 0
-------------------------------------------------------F/S/P
0/3/0
Min distance(km)
0
Max distance(km)
20
Left guaranteed bandwidth(kbps)
1240576
Number of T-CONTs
0
Autofind
Enable
FEC check
Enable
Laser switch
On
ONT encryption key switching interval(m)
Disable
--------------------------------------------------------
1.3.15 Testing the Optical Power of an Optical Port

This topic describes how to check whether the optical signal transmit and receive modules are
normal by testing the mean launched power and the actual input power.
Measuring the Transmit Optical Power of an OLT PON Port

Check whether the optical module on a PON port of the OLT works properly by measuring
the transmit optical power.
Prerequisites
l
The OLT is powered on.
The PON board is in the normal state.
The PON port is enabled.
Tools, Meters and Materials

l
Single-mode fiber jumper with the SC/PC connector. No longer than 1 m. Best to use
new jumper.
Burst optical power meter or ordinary optical power meter.
Impact on the System

When the transmit optical power of a PON port on the OLT is measured, the PON port will
fail to transmit any service.
Issue 01 (2016-04-29)

76

Access Module
1 Commissioning
Precautions
DANGER
Do not look into the optical port or the optical fiber connector without eye protection.
Before or after measuring the optical power, you need to clean the connector of the optical
fiber. This is because if a contaminated optical fiber is connected to a normal optical fiber
connector, the connector will be contaminated, which leads to abnormal attenuation and
reflection and thus affecting optical path quality.
Procedure
Step 1 Configuring the measure parameters of the optical power meter.
l
Unit of optical power: dBm
Wavelength: 1490 nm
Step 2 Connect the optical power meter directly to the optical module on the OLT PON port using
optical fiber jumper, as shown in Figure 1-45. The value on the optical power meter is the
transmit optical power of the OLT PON port.
Figure 1-45 Measuring the Transmit Optical Power of an OLT PON Port
NOTE
l If the value on the optical power meter changes within a range of 0.2 dBm, take the average value.
l If the value on the optical power meter changes in a range wider than 0.2 dBm, then it is possible
that the fiber is not properly connected, the fiber is excessively bent, or the fiber connector has dust.
l Do not bend the fiber. A bent fiber may affect the test result.
Step 3 Compare the test result with the optical module parameters of the corresponding board in the
hardware description.
----End
Result
l
If the test result is between the maximum and minimum output optical power of the
optical module of the board, it indicates that the optical module works properly.
If the test result is no between the maximum and minimum output optical power of the
optical module of the board, it indicates that the optical module does not work properly.
Issue 01 (2016-04-29)

77

Access Module
1 Commissioning
Measuring the Receive Optical Power of an OLT PON Port

Determine whether there are continuous mode ONUs or rogue ONUs by measuring the
optical power of the OLT PON port.
Prerequisites
l
The ONU is powered on.
The ONU PON port is enabled.
The optical fiber between the OLT and the ONU is properly connected.
Tools, Meters and Materials

Burst optical power meter
Impact on System
When the receive optical power of a PON port on the OLT is measured, corresponding PON
port will fail to transmit any service.
Precautions
DANGER
Procedure
Step 1 Configuring the measure parameters of the optical power meter.
l
Unit of optical power: dBm
Wavelength: 1310 nm
Step 2 Remove the fiber from the OLT PON port and connect it to the optical power meter, as shown
in Figure 1-46.
Figure 1-46 Measuring the Receive Optical Power of an OLT PON Port
Issue 01 (2016-04-29)

78

Access Module
1 Commissioning
Step 3 Wait for 10s and read the value. Check the value on the optical power meter for one minute.
Step 4 After measuring the transmit optical power, insert the optical fiber removed in step 2 to
restore the connection between the ONU and the OLT.
----End
Result
l
If no value can be read or the value is lower than -40 dBm on the optical power meter,
there is no rogue ONU or continuous mode ONU connected to the PON port.
If a value can always be read and is higher than -28 dBm on the optical power meter,
there are ONUs in continuous mode connected to the PON port.
If a value can be read at one time and cannot be read at another time and the value is
higher than -28 dBm, there are rogue ONUs connected to the PON port (that is, an ONU
that transmits data in the timeslot that is not allocated by the OLT to it).
Measuring the Transmit Optical Power of an ONU PON Port

Measuring the transmit optical power of a PON port on the ONU helps you check whether the
optical module of the PON port functions properly and whether the ONU is a continuousmode ONU or a rogue ONU.
Prerequisites
l
The ONU is powered on.
The PON port is enabled.
Tools and Meters

l
Single-mode optical jumper no longer than 1 m whose connector matches the ONU's
interface specifications. A new jumper is recommended.
Burst optical power meter

When the transmit optical power of a PON port on the ONU is measured, the PON port is not
able to carry any service.
Precautions
DANGER
Issue 01 (2016-04-29)

79

Access Module
1 Commissioning
Procedure
Step 1 Configure the measuring parameters of the optical power meter.
l
Optical power unit: dBm
Wavelength (nm): 1310
Step 2 Remove all optical fibers connected to the PON ports on the ONU and ensure that the ONU is
not connected to any optical splitters or OLTs.
NOTE
When certain ONUs support network protection in the case that multiple PON ports are used for
upstream transmission, you need to remove all the optical cables of the ONU PON ports. This is because
the continuous mode of the ONU needs to be enabled when you measure the ONU transmit power. If the
ONU is connected to a splitter or OLT, the other ONUs that are connected to the same PON port fail to
go online.
Step 3 Connect the optical power meter directly to the optical module on the ONU PON port using
an optical jumper, as shown in Figure 1-47.
Figure 1-47 Measuring the transmit optical power of an ONU PON port
Step 4 Wait 10s and then read the value. Check the value on the optical power meter in one minute.
Step 5 Enable the continuous-mode ONU function. The value read on the optical power meter is the
transmit optical power of the ONU PON port. Compare the result as tested with the PON
optical module parameter in the ONU product manual.
NOTE
l Generally, an ONU does no transmit optical signals when it is not connected to the OLT. In this case,
enable the continuous-mode ONU function to make the ONU transmit optical signals. For how to
enable the continuous-mode ONU function, see the ONU product manual.
l If the value on the optical power meter changes in a range wider than 0.2 dBm, there is a probability
that the optical fiber is not properly connected, the optical fiber is excessively bent, or the optical
fiber connector is not clean.
l Do not bend the optical fiber. A bent optical fiber may affect the test result.
Step 6 After measuring the transmit optical power, disable the continuous-mode ONU function.
NOTE
After measuring the transmit optical power, you must disable the continuous-mode ONU function.
Otherwise, other ONUs cannot go online after the ONU is connected to the OLT.
Step 7 Insert the optical fiber removed in step 1 to restore the connection between the ONU and the
OLT.
----End
Issue 01 (2016-04-29)

80

Access Module
1 Commissioning
Result
l
The test result in step 4 helps to determine whether the ONU is a continuous-mode ONU
or a rogue ONU.
If no value can be read or the value is smaller than -40 dBm on the optical power
meter, there is no rogue ONU or continuous-mode ONU connected to the PON port.
If a value can always be read and is larger than -28 dBm on the optical power meter,
there are continuous-mode ONUs connected to the PON port.
If a value can be read at one time and cannot be read at another time and the value
is larger than -28 dBm, there are rogue ONUs (that is, ONUs that transmit data in
the timeslot that is not allocated by the OLT to them) connected to the PON port.
The test result in step 5 helps to determine whether the optical module of the PON port
on the ONU works properly.
If the test result is between the maximum and minimum output optical power of the
ONU optical module, the optical module works properly.
If the test result is not between the maximum and minimum output optical power of
the ONU optical module, the optical module does not work properly.
Measuring the Receive Optical Power of an ONU PON Port

Measuring the receive optical power of an ONU PON port helps to check the optical path
quality.
Prerequisites
l
The OLT is powered on.
The OLT PON port is enabled.
The optical fiber between the OLT and the ONU is properly connected.
Tools and Meters

Burst optical power meter or ordinary optical power meter

When the receive optical power of a PON port on the ONU is measured, the PON port is not
able to carry any service.
Precautions
DANGER
Issue 01 (2016-04-29)

81

Access Module
1 Commissioning
Procedure
Step 1 Configure the measuring parameters of the optical power meter.
l
Optical power unit: dBm
Wavelength (nm): 1490
Step 2 Remove the optical fiber from the ONU PON port and connect it to the optical power meter,
as shown in Figure 1-48. The value read on the optical power meter is the receive optical
power of the ONU PON port.
Figure 1-48 Measuring the Receive Optical Power of an ONU PON Port
NOTE
l If the value on the optical power meter changes in a range wider than 0.2 dBm, there is a probability
that the optical fiber is not properly connected, the optical fiber is excessively bent, or the optical
fiber connector is not clean.
l Do not bend the optical fiber. A bent optical fiber may affect the test result.
----End
Result
Compare the result as tested with the theoretical value of the ONU receive optical power in
the ODN plan. If the difference between the actual value and the theoretical value is larger
than 2 dBm, the line may be faulty.
NOTE
Generally, the normal range of the receive optical power of a GPON port on the ONU is from -27 dBm
to -8 dBm.
1.3.16 Commissioning the EMU

The MA5600T/MA5603T/MA5608T monitors various environment parameters (including
the temperature, humidity, and voltage of the power supply) to ensure that the MA5600T/
MA5603T/MA5608T can work stably in a proper environment. This topic describes how to
commission the environment monitoring unit (EMU).
Environment Monitoring Application

This topic describes the environment monitoring applications in different cabinets.
Issue 01 (2016-04-29)

82

Access Module
1 Commissioning
Table 1-22 lists the environment monitoring applications in different cabinets.

Table 1-22 Environment monitoring applications in different cabinets
Monitoring Solution
Cabinet Type
Typical Configuration
H801ESC Monitoring
Solution
N63E-22
l Two MA5600T shelves
ESCM Monitoring Solution
Use this program when you

need to monitor the ESCM
EPS75-4815AF Monitoring
Solution (PMIB01)
F01D500
One MA5600T(MA5603T)
shelf
EPS30-4815AF Monitoring
Solution (PMIB01)
F01S300
One MA5603T shelf
GEPS4845 Monitoring
Solution
F01D500
shelf
ETP4830 Monitoring
Solution
F01S300
One MA5603T shelf
ETP4890 Monitoring
Solution
F01D500 and F01T500
shelf
ETP48150 Monitoring
Solution
F01D2000 and F01T500
l Two
MA5600T(MA5603T)
shelves
l One MA5600T shelf +

one SPL shelf
l One
MA5600T(MA5603T)
shelves
CCU Monitoring Solution
F01T500
shelf
Power3000 Monitoring
Solution
Use this program when you

need to monitor the external
power supply Power 3000
Heat Exchanger Monitoring

Solution
Heat Exchanger
Fan Tray Monitoring

Solution
Fan Tray
Commissioning the EMU_ESC

This topic describes how to commission the H801ESC board to ensure that it monitors the
environmental conditions of the device according to the actual conditions.
Issue 01 (2016-04-29)

83

Access Module
1 Commissioning
Context
ESC stands for the environment and power monitoring board. The H801ESC board monitors
environment parameters such as temperature, humidity, smoke, water, fire, voltage, and power
supply through various sensors.
When commissioning the H801ESC board, pay attention to the following points:
l
The EMU sub-nodes are numbered from 0 to 31.
When the system is configured with multiple EMUs simultaneously, make sure that the
sub-nodes do not conflict with each other.
Table 1-23 lists the default configuration of the H801ESC board.

Table 1-23 Default configuration of the H801ESC board
Parameter
Default Value
Sub-node
15
Analog parameters
ESC analog parameter IDs:

l 0: allocated to the board temperature sensor by default (unable to
be changed by the user).
l 1-4: allocated to the voltage sensor by default.
1 indicates -48 V input of channel 0.
l 5-8: user-defined analog parameters allocated to other extended
analog sensors, such as the temperature sensor and the humidity
sensor.
Upper and lower alarm thresholds
l Temperature: 5C to 55C
l Humidity: 0% RH to 80% RH
Issue 01 (2016-04-29)

84

Access Module
Parameter
Default Value
Digital parameters
ESC digital parameter IDs
1 Commissioning
l Allocated by default (unable to be changed by the user)

0: MDF
1: door status sensor 0
9: water
10-13: lightning arresters 0-3
14-15: switches 11 and 12
22: external sensor power
l User-defined IDs
2-8: allocated to other extended digital sensors.
Procedure
Step 1 Set the DIP switch of the sub-node for the H801ESC board. By default, the sub-node ID is 15.
The H801ESC board communicates with the MA5600T/MA5603T/MA5608T in the master
node and sub-node mode. Therefore, the DIP switch of the sub-node for the H801ESC board
must be consistent with that for the MA5600T/MA5603T/MA5608T. For details about how to
configure the DIP switches of the H801ESC board, see the Description of DIP Switches in
Checking the Settings of DIP Switches on the H801ESC Board.
Step 2 Insert the H801ESC board into the corresponding slot of the PDU, and make sure that the
MA5600T/MA5603T/MA5608T and the H801ESC board are connected through the RS-485
serial port cable.
When the device is delivered, the H801ESC board is correctly connected to the shelf. The
connection need not be changed for the device commissioning. The COM2 of the H801ESC
board is connected to the ESC of the MA5600T/MA5603T/MA5608T. In this case, the
H801ESC collects and reports the environment information to the control board.
Step 3 Run the emu add command to add an H801ESC board. By default, the sub-node ID is 15.
Step 4 Run the interface emu command to enter the H801ESC mode.
Step 5 Run the esc analog command to configure the ESC analog parameters. By default, the upper
and lower alarm thresholds of the temperature are 55C and 5C respectively; the upper and
lower alarm thresholds of the humidity are 80% RH and 0% RH respectively.
Step 6 Run the esc digital command to set the ESC digital parameters.
Step 7 Run the save command to save the data.
----End
Issue 01 (2016-04-29)

85

Access Module
1 Commissioning
Result
l
In step 2, you can confirm that the RUN ALM LED on the H801ESC board is orange
and blinks repeatedly once in every 300 ms, which indicates that the board is registering.
After a while, the RUN ALM LED on the H801ESC board turns orange and is on for 1s
and off for 1s repeatedly, which indicates that an alarm is generated. Certain EMU
parameters have the initial configurations (namely, default alarm thresholds); therefore,
if any parameter reaches the threshold, an alarm is generated.
After the configuration, the RUN ALM LED on the H801ESC board turns green and is
on for 1s and off for 1s repeatedly, which indicates that the H801ESC board monitors the
environment normally.
In the H801ESC mode, run the display esc system parameter command to check
whether the ESC information is the same as the data plan.
Close doors of the cabinet, and query alarms. Ensure that no alarm of the monitoring
parameters is generated.
Example
Add an H801ESC board, set the analog and digital parameters of the H801ESC board, and
save the data.
To set the ESC analog parameters (set the user-defined analog parameter ID to 5, upper alarm
threshold to 70, lower alarm threshold to -30, analog parameter name to Temperature_1 with
the unit of C) and the ESC digital parameters (set the user-defined digital parameter ID to 7,
set the door status alarm whose ID is 8, set the alarm name to Door_1 and the available level
of the alarm to high level), do as follows:
huawei(config)#emu add 1 H801ESC 0 15 H801ESC
huawei(config)#interface emu 1
huawei(config-if-h801esc-1)#esc analog 5 alarm-upper-limit 70 alarm-lower-limit
-30 name Temperature_1 unit C
huawei(config-if-h801esc-1)#esc digital 7 digital-alarm 8 name Door_1 availablelevel high-level
huawei(config-if-h801esc-1)#display esc system parameter
huawei(config-if-h801esc-1)#quit
huawei(config)#save
Configuring H801VESC Environment Monitoring Parameters

The MA5608T can monitor the environment status through its built-in virtual environment
monitoring unit (EMU) H801VESC. This topic describes how to configure the H801VESC.
Context
l
The H801VESC is a built-in virtual EMU of the control board on the MA5608T, and the
ALARM port on the control board is connected to the external sensor through an
environment monitoring cable.
You need to manually add the H801VESC. The recommended subnode ID is 25.
The H801VESC supports seven digital parameters, all of which can be defined by users.
In an F01S200 cabinet, only four digital parameters are used.
By default, the valid levels of default digital parameters are all high levels.
Issue 01 (2016-04-29)

86

Access Module
1 Commissioning
Procedure
Step 1 Add the H801VESC.
Run the emu add command to add the H801VESC.
Step 2 Query the status of the H801VESC.
Run the display emu command to query the status of the H801VESC. Ensure that it is
running properly.
Step 3 Configure the digital parameters.
Run the interface emu command to enter the EMU mode.
Run the vesc digitalcommand to configure the valid level, name, and alarm ID of the digital
parameters.
Step 4 Query the environment information about the H801VESC.
Run the display vesc environment info command to query the environment information
about the H801VESC.
----End
Result
After the configuration, the H801VESC works in the normal state and monitors the digital
parameters set on the MA5608T. When the actual level of a monitored digital parameter is
different from the valid level preset in the system, the MA5608T reports an alarm.
Example
To configure the H801VESC of the MA5608T in an F01S200 cabinet, do as follows (Table
1-24 lists the data plan for configuring the H801VESC of the MA5608T in the F01S200
cabinet):
Table 1-24 Data plan for configuring the H801VESC
Item
Data
Remarks
EMU
EMU ID: 2
Subnode ID: 25
The ID and subnode ID of the H801VESC cannot

conflict with those of the existing EMUs.
Digital parameter ID: 0
Valid level of digital

parameter 0: low level
When the low level represents the valid level, the

MA5608T does not report an alarm in the case of
low level.
Name of digital
parameter 0:
Temperature
This digital parameter is set according to the

actual requirements. The monitoring digital
parameter of the temperature sensor is set to
monitor the temperature.
Digital
parameters
Issue 01 (2016-04-29)

87

Access Module
Item
1 Commissioning
Data
Remarks


low level.
Name of digital
parameter 1: Door

parameter of the door sensor is set to monitor the
door status.


low level.
Name of digital
parameter 2: Arrester

parameter of the lightning arrester status sensor is
set to monitor the arrester status.

hen the low level represents the valid level, the

low level.
Name of digital
parameter 3: Fan

parameter of the fan status sensor is set to monitor
the fan status.
NOTE
The enhanced heat dissipation module is an optional
module. The fan monitoring digital parameter is
required only when the enhanced heat dissipation
module is configured. Otherwise, the system will report
an alarm.
huawei(config)#emu add 2 H801VESC 0 25 H801VESC

huawei(config)#display emu 2
EMU ID: 2
---------------------------------------------------------------------------EMU name
: H801VESC
EMU type
: H801VESC
Used or not : Used
EMU state
: Normal
Frame ID
: 0
Subnode
: 25
---------------------------------------------------------------------------huawei(config)#interface emu 2
huawei(config-if-h801vesc-2)#vesc digital 0 available-level low-level name
Temperature
huawei(config-if-h801vesc-2)#vesc digital 1 available-level low-level name Door
huawei(config-if-h801vesc-2)#vesc digital 2 available-level low-level name
Arrester
huawei(config-if-h801vesc-2)#vesc digital 3 available-level low-level name Fan
Issue 01 (2016-04-29)

88

Access Module
1 Commissioning
huawei(config-if-h801vesc-2)#display vesc environment info

EMU ID: 2
VESC environment state
---------------------------Digital environment info------------------------ID Name
State Value |ID Name
State Value
0 Temperature
Normal 0
|1 Door
Alarm 1
2 Arrester
Normal 0
|3 Fan
Normal 0
4 Normal 1
|5 Normal 1
6 Normal 1
---------------------------------------------------------------------------huawei(config-if-h801vesc-2)#quit
huawei(config)#save
Configuring the Environment Monitoring Parameters of the EPS30-4815AF

This topic describes how to configure the environment monitoring parameters of the
EPS30-4815AF through the CLI.
Mapping Between Monitoring Parameters and Device Ports

Table 1-25 describes the mapping between the monitoring parameters displayed on the sensor
transfer box.
Table 1-25 Mapping between the monitoring parameters displayed on the host and the ports
on the sensor transfer box
Monitoring Parameter Displayed on the
Host
Device Port
Temperature
TEM-HU
Humidity
TEM-HU
Digital 0
JTD1
Digital 1
JTD2
Digital 2
JTD3
Digital 3
JTD4
Digital 4
JTD5
Digital 5
JTD6
Digital 6
JTD7
NOTE
Before adding a user-defined analog or monitoring digital parameter, make sure that the port
corresponding to this parameter is properly connected to an environment monitoring cable.
Configuration Process
The monitoring parameters can be reported to the control system only when the data for the
EPS30-4815AF is configured correctly in the system.
Table 1-26 lists the commands used during the configuration.
Issue 01 (2016-04-29)

89

Access Module
1 Commissioning
Table 1-26 Commands for configuring the EPS30-4815AF

To...
Run the Command...
Add an EMU
emu add
Query the configuration

parameters of the power system
display power system parameter
Query the power environment

parameters
display power environment parameter
Query the alarm information of

the power supply
display power alarm
Configure the battery charging

parameters
power charge
Configure the battery

management parameters
power battery parameter
Configure the upper/lower

temperature alarm limits or the
upper/lower temperature test
limits
power battery temperature
Configure the battery set

power-off parameters
power off
Configure the power

distribution parameters
power supply-parameter

discharging test parameters
power battery-test
Configure the parameters for

the power rectifier module
power module-num
Configure the battery hightemperature power-off

parameters
power temperature-off
Configure the environment

monitoring parameters
power environment
Configure the external extended

digital parameters
power outside-digital
1.
Log in to the device through the maintenance terminal and add an EMU.
2.
Query the status of the EPS30-4815AF.
3.
Enter the environment monitoring configuration mode and query the default
configuration.
4.
Configure the battery management parameters.
5.
Configure the battery discharging test parameters.
Issue 01 (2016-04-29)

90

Access Module
1 Commissioning
6.
Configure the battery high-temperature power-off parameters.
7.
Configure the environment parameters.
8.
Configure the extended digital parameters.
9.
Query the information about the configured parameters and environment parameters of
the power system.
10. Query the alarms, and confirm that the door status alarm other than alarms for other
monitoring parameters is generated. The door status sensors of the device compartment
and the temperature control compartment are in serial connection, and are monitored as a
variable.
11. Save the data.
12. Close all doors of the cabinet. Then, query the alarm information again, and confirm that
there is no alarm for any monitoring parameter.
Data Plan
In this topic, the application in the F01S300 cabinet is considered as an example. Table 1-27
provides the data plan for configuring the monitoring parameters of the EPS30-4815AF.
Table 1-27 Data plan for configuring the monitoring parameters of the EPS30-4815AF
Item
Data Plan for the F01S300 Cabinet
EMU
Type: POWER4830L
SN: 0
Subnode ID: 0
The subnode ID must be the same as the subnode setting of the
corresponding DIP switches on the EMU, but the subnode ID must
be different from IDs of the other subnodes on the same bus.
Charging
parameters of the
battery
Charging mode of the battery: automatic
Battery
management
parameters
Current-limiting coefficient for battery charging: 0.15
Equalized charging voltage of the battery: 56.5 V

Float charging voltage of the battery: 53.5 V
Interval of battery equalized charging: 60 days

Number of battery sets: 1
Capacity of the battery set: 92 AH
The battery capacity is configured according to the actual value. the
F01S300 cabinet uses the 50 AH or 92 AH batteries.
Issue 01 (2016-04-29)
The upper/lower
temperature alarm
limits or the upper/
lower temperature
test limits
Upper temperature threshold of the battery set: 80C
Battery set poweroff parameters
Battery set power-off permission status: permit
Lower temperature threshold of the battery set: -20C

Temperature compensation coefficient of the battery set: 80 mV
Battery set power-off voltage: 43 V

91

Access Module
1 Commissioning
Item
Power distribution
parameters
AC overvoltage alarm threshold of the power supply: 280 V

AC undervoltage alarm threshold of the power supply: 180 V
DC overvoltage alarm threshold of the power supply: 58 V
DC undervoltage alarm threshold of the power supply: 45 V
Battery
discharging test
parameters
Battery auto-discharging test: auto-test
Power rectifier
module parameters
The number of the power rectifier modules: 0
Battery hightemperature
power-off
parameters
Battery high-temperature power-off permission status: permit
Battery set auto-discharging test permission status: permit

Battery auto-discharging test period: 60d
The number of the power rectifier modules is configured according to

the actual value. EPS30-4815AF supports up to 2 rectifier modules.
Temperature for battery high-temperature power-off: 53C
Environment
monitoring
parameters
Upper alarm threshold of the temperature: 68C

Lower alarm threshold of the temperature: -5C
Upper test threshold of the humidity: 80C
Lower test threshold of the humidity: -20C
External extended
digital parameters

This digital parameter is set according to the actual requirements.
The monitoring digital parameter of the external fan tray is set here to
monitor the fan tray. When the fan tray is faulty, the host reports an
alarm.
Valid level of digital parameter 0: low level
When the low level represents the valid level, the host does not report
an alarm in the case of low level.
The monitoring digital parameter of the external fan tray is set here to
monitor the fan tray. When the fan tray is faulty, the host reports an
alarm.
Issue 01 (2016-04-29)

92

Access Module
Item
1 Commissioning

The monitoring digital parameter of the surge protector is set here to
monitor the status of the surge protector. When the surge protector is
faulty, the host reports an alarm.
The monitoring digital parameter of the smoke sensor is set here to
monitor whether there is smoke in the actual environment. When
there is smoke, the host reports an alarm.
Valid level of digital parameter 4: high level
When the high level represents the valid level, the host does not
report an alarm in the case of high level.
The monitoring digital parameter of the heat exchanger is set here to
monitor the status of the heat exchanger. When the heat exchanger is
The digital monitoring parameter of the MDF door status sensor is
set here to monitor the MDF door status. When the door of the MDF
compartment is open, the host reports an alarm.
NOTE
The preceding data is configured according to the actual requirements. When the actually planned value
of a parameter is the same as the default value, it is not necessary to configure the parameter.
Configuration Example
The following considers the configuration in the F01S300 cabinet as an example to describe
the process of configuring the environment monitoring parameters of the EPS30-4815AF.
huawei(config)#emu add 0 POWER4830L 0 0 POWER4830L
Issue 01 (2016-04-29)

93

Access Module
1 Commissioning
huawei(config-if-power4830l-0)#display power system parameter
huawei(config-if-power4830l-0)#display power environment parameter
huawei(config-if-power4830l-0)#power battery parameter 1 0.15 60 92
huawei(config-if-power4830l-0)#power battery-test auto-test permit 60
huawei(config-if-power4830l-0)#power temperature-off battery-off-state permit
battery-off-temperature 53
huawei(config-if-power4830l-0)#power environment temperature 68 -5 80 -20
huawei(config-if-power4830l-0)#power outside-digital 3 available-level low-level
name SPD digital-alarm 20
huawei(config-if-power4830l-0)#power outside-digital 4 available-level high-level
name Smoke digital-alarm 15
name HEX digital-alarm 13
name MDF-door digital-alarm 9
huawei(config-if-power4830l-0)#display power alarm
huawei(config-if-power4830l-0)#quit
huawei(config)#save
Configuring the Environment Monitoring Parameters of the EPS75-4815AF

EPS75-4815AF through the CLI.

transfer box.
Issue 01 (2016-04-29)
Monitoring
Parameter
Displayed on
the Host
Device Port
Application in the N66

Cabinet
Application in the
F01D500 Cabinet
Digital 0
JTD1
Not connected by default,

used to add a user-defined
monitoring digital
parameter
Not connected by
default, used to add a
user-defined
monitoring digital
parameter
Digital 1
JTD2

monitoring digital
parameter
Not connected by
user-defined
monitoring digital
parameter
Digital 2
JTD3

monitoring digital
parameter
Not connected by
user-defined
monitoring digital
parameter

94

Access Module
1 Commissioning
Monitoring
Parameter
Displayed on
the Host
Device Port
Application in the N66

Cabinet
Application in the
F01D500 Cabinet
Digital 3
JTD4

monitoring digital
parameter
surge protector
Digital 4
JTD5

monitoring digital
parameter
Smoke sensor
Digital 5
JTD6

monitoring digital
parameter
Heat exchanger
Digital 6
JTD7

monitoring digital
parameter
Door status sensor of

the MDF compartment
Door alarm
JTM1

used to monitor a door
status sensor
Door status sensors of

the device
compartment and heat
exchanger
compartment
Wiring alarm
JTP1

used to monitor a MDF
sensor
MDF
Battery Tem
BAT_WE
Battery temperature sensor
Battery temperature
sensor
environment
Tem/environment
Hum
TEM-HU
Not connected by default.
Temperature and
humidity sensor
NOTE
EPS75-4815AF is configured correctly in the system.
Issue 01 (2016-04-29)

95

Access Module
1 Commissioning
Table 1-29 Commands for configuring the EPS75-4815AF

To...
Run the Command...
Add an EMU
emu add


parameters

the power supply
display power alarm

parameters
power charge


limits

power off
Configure the power


power battery-test

power module-num

parameters

power environment

digital parameters
1.
2.
Query the status of the EPS75-4815AF.
3.
configuration.
4.
5.
Issue 01 (2016-04-29)

96

Access Module
1 Commissioning
6.
7.
8.
9.
the power system.
variable.
11. Save the data.
Data Plan
The data plan of the EPS75-4815AF in the N66 cabinet is the same as that in the F01D500
cabinets. In this topic, the application in the F01D500 cabinet is considered as an example.
Table 1-30 provides the data plan for configuring the monitoring parameters of the
EPS75-4815AF.
Table 1-30 Data plan for configuring the monitoring parameters of the EPS75-4815AF
Item
Data Plan for the F01D500

Cabinet
Data Plan for the N66 Cabinet
EMU
Type: POWER4875L
Type: POWER4875L
SN: 0
SN: 0
Subnode ID: 0
Subnode ID: 0
The subnode ID must be the same

as the subnode setting of the
corresponding DIP switches on
the EMU, but the subnode ID
must be different from IDs of the
other subnodes on the same bus.
The subnode ID must be the same as

the subnode setting of the
corresponding DIP switches on the
EMU, but the subnode ID must be
different from IDs of the other
subnodes on the same bus.
Charging mode of the battery:

automatic
Charging mode of the battery:

automatic
Equalized charging voltage of the

battery: 56.5 V
Equalized charging voltage of the

battery: 56.5 V
Float charging voltage of the

battery: 53.5 V
Float charging voltage of the battery:

53.5 V
Charging
parameters
of the
battery
Issue 01 (2016-04-29)

97

Access Module
1 Commissioning
Item

Cabinet
Battery
management
parameters
Current-limiting coefficient for

battery charging: 0.15
Current-limiting coefficient for battery

charging: 0.15
Interval of battery equalized

charging: 60 days
Interval of battery equalized charging:

60 days
Capacity of the battery set: 150

AH
The battery capacity is configured

according to the actual value.
The battery capacity is configured

according to the actual value. the
F01D500 cabinet uses the 2 * 75
AH or 2 * 92 AH batteries.
The upper/
lower
temperature
alarm limits
or the upper/
lower
temperature
test limits
Upper temperature threshold of

the battery set: 80C
Upper temperature threshold of the

battery set: 80C
Lower temperature threshold of

the battery set: -20C
Lower temperature threshold of the

battery set: -20C
Temperature compensation
coefficient of the battery set: 80
mV
Temperature compensation coefficient

of the battery set: 80 mV
Battery set
power-off
parameters
Battery set power-off permission

status: permit
Battery set power-off permission

status: permit
Battery set power-off voltage: 43

V
Power
distribution
parameters
AC overvoltage alarm threshold

of the power supply: 280 V
AC overvoltage alarm threshold of the

power supply: 280 V
AC undervoltage alarm threshold

AC undervoltage alarm threshold of

the power supply: 180 V
DC overvoltage alarm threshold

DC overvoltage alarm threshold of the

power supply: 58 V
DC undervoltage alarm threshold

DC undervoltage alarm threshold of

the power supply: 45 V
Battery auto-discharging test:

auto-test
Battery
discharging
test
parameters
Battery set auto-discharging test

permission status: permit
Battery auto-discharging test
period: 60d
Issue 01 (2016-04-29)
Battery set auto-discharging test

Battery auto-discharging test period:
60d

98

Access Module
Item

Cabinet
Power
rectifier
module
parameters
The number of the power rectifier

modules: 0

modules: 0

modules is configured according
to the actual value.
EPS75-4815AF supports up to 5
rectifier modules.

modules is configured according to
the actual value. EPS75-4815AF
supports up to 5 rectifier modules.
Battery hightemperature
power-off
parameters
Battery high-temperature poweroff permission status: permit
Battery high-temperature power-off

Temperature for battery hightemperature power-off: 53C
Temperature for battery hightemperature power-off: 53C
Environment
monitoring
parameters
Upper alarm threshold of the

temperature: 68C
Upper alarm threshold of the

temperature: 68C
Lower alarm threshold of the

temperature: -5C
Lower alarm threshold of the

temperature: -5C
Upper test threshold of the

humidity: 80C
Upper test threshold of the humidity:

80C
Lower test threshold of the

humidity: -20C
Lower test threshold of the humidity:

-20C
This digital parameter is set

according to the actual
requirements. The monitoring
digital parameter of the external
fan tray is set here to monitor the
fan tray. When the fan tray is
This digital parameter is set according

to the actual requirements. The
monitoring digital parameter of the
external fan tray is set here to monitor
the fan tray. When the fan tray is
External
extended
digital
parameters
Valid level of digital parameter 0:

low level
When the low level represents the
valid level, the host does not
report an alarm in the case of low
level.
Issue 01 (2016-04-29)
1 Commissioning
Valid level of digital parameter 0: low

level
valid level, the host does not report an
alarm in the case of low level.

99

Access Module
Item

Cabinet

digital parameter of the external
fan tray is set here to monitor the
fan tray. When the fan tray is

external fan tray is set here to monitor
the fan tray. When the fan tray is

low level
level.

level

requirements.

to the actual requirements.

low level
level.

level

digital parameter of the surge
protector is set here to monitor the
status of the surge protector.
When the surge protector is faulty,
the host reports an alarm.

surge protector is set here to monitor
the status of the surge protector. When
the surge protector is faulty, the host
reports an alarm.

low level
level.
Issue 01 (2016-04-29)
1 Commissioning

level

100

Access Module
Item

Cabinet

digital parameter of the smoke
sensor is set here to monitor
whether there is smoke in the
actual environment. When there is
smoke, the host reports an alarm.

smoke sensor is set here to monitor
whether there is smoke in the actual
environment. When there is smoke,

high level
When the high level represents the
report an alarm in the case of high
level.
Valid level of digital parameter 4: high

level
When the high level represents the
alarm in the case of high level.

digital parameter of the heat
exchanger is set here to monitor
the status of the heat exchanger.
When the heat exchanger is faulty,

heat exchanger is set here to monitor
the status of the heat exchanger. When
the heat exchanger is faulty, the host
reports an alarm.

low level
level.
Issue 01 (2016-04-29)
1 Commissioning

level

101

Access Module
Item
1 Commissioning

Cabinet

requirements. The digital
monitoring parameter of the MDF
door status sensor is set here to
monitor the MDF door status.
When the door of the MDF
compartment is open, the host
reports an alarm.

to the actual requirements. The digital
monitoring parameter of the MDF
door status sensor is set here to
monitor the MDF door status. When
the door of the MDF compartment is
open, the host reports an alarm.

low level


level.

level
NOTE
The following considers the configuration in the F01D500 cabinet as an example to describe
the process of configuring the environment monitoring parameters of the EPS75-4815AF.
huawei(config)#emu add 0 POWER4875L 0 0 POWER4875L
huawei(config-if-power4875l-0)#power battery parameter 1 0.15 60 150
huawei(config-if-power4875l-0)#power battery-test auto-test permit 60
huawei(config-if-power4875l-0)#power temperature-off battery-off-state permit
huawei(config-if-power4875l-0)#power environment temperature 68 -5 80 -20
huawei(config-if-power4875l-0)#power outside-digital 4 available-level high-level
huawei(config-if-power4875l-0)#display power alarm
huawei(config)#save
Issue 01 (2016-04-29)

102

Access Module
1 Commissioning
Configuring the Environment Monitoring Parameters of the GEPS4845

GEPS4845 through the CLI.

transfer box.
Monitoring Parameter
Displayed on the Host
Device Port
Application in the F01D500

Cabinet
Digital 0
JTD1
Not connected by default, used to

add a user-defined monitoring
digital parameter
Digital 1
JTD2

digital parameter
Digital 2
JTD3

digital parameter
Digital 3
JTD4
surge protector (SPD)
Digital 4
JTD5
Smoke sensor
Digital 5
JTD6
Heat exchanger
Digital 6
JTD7
Door status sensor of the MDF

compartment
Door alarm
JTM1
Door status sensors of the device

compartment and heat exchanger
compartment
Wiring alarm
JTP1
MDF
Battery Tem
BAT_WE
environment Tem/
environment Hum
TEM-HU
Temperature and humidity sensor
NOTE
Issue 01 (2016-04-29)

103

Access Module
1 Commissioning
GEPS4845 is configured correctly in the system.
Table 1-32 Commands for configuring the GEPS4845
Issue 01 (2016-04-29)
To...
Run the Command...
Add an EMU
emu add


parameters

the power supply
display power alarm

parameters
power charge


limits
Configure the power supply

load power-off and battery set
power off
Configure the power


power battery-test

power module-num

power environment
Configure the load and battery

high-temperature power-off
parameters

digital parameters

104

Access Module
1 Commissioning
1.
2.
Query the status of the GEPS4845.
3.
configuration.
4.
5.
6.
7.
Configure the load and battery high-temperature power-off parameters.
8.
9.
the power system.
variable.
11. Save the data.
Data Plan
In this topic, the application in the F01D500 cabinet is considered as an example. Table 1-33
provides the data plan for configuring the monitoring parameters of the GEPS4845.
Table 1-33 Data plan for configuring the monitoring parameters of the GEPS4845
Item
Data Plan for the F01D500 Cabinet
EMU
Type: POWER4845
SN: 0
Subnode ID: 0
corresponding DIP switches on the EMU, but the subnode ID
must be different from IDs of the other subnodes on the same
bus.
Charging parameters of
the battery

Battery management
parameters

The battery capacity is configured according to the actual
value. the F01D500 cabinet uses the 2 * 75 AH or 2 * 92 AH
batteries.
Issue 01 (2016-04-29)

105

Access Module
1 Commissioning
Item
The upper/lower
temperature alarm limits
or the upper/lower
temperature test limits
Power supply load

power-off and battery set
Load power-off permission status: forbid

Temperature compensation coefficient of the battery set: 100
mV

Load power-off voltage: 44 V
Power distribution
parameters

Battery discharging test

parameters

Power rectifier module

parameters
Environment monitoring
parameters

The number of the power rectifier modules is configured
according to the actual value. GEPS4845 supports up to 3
rectifier modules.
Load and battery hightemperature power-off

parameters
Load high-temperature power-off permission status: forbid

Temperature for load high-temperature power-off: 70C
External extended digital

parameters

This digital parameter is set according to the actual
requirements. The monitoring digital parameter of the external
fan tray is set here to monitor the fan tray. When the fan tray is
When the low level represents the valid level, the host does not
report an alarm in the case of low level.
Issue 01 (2016-04-29)

106

Access Module
Item
1 Commissioning

requirements. The monitoring digital parameter of the external
fan tray is set here to monitor the fan tray. When the fan tray is
requirements.
requirements. The monitoring digital parameter of the surge
protector is set here to monitor the status of the surge protector.
When the surge protector is faulty, the host reports an alarm.
requirements. The monitoring digital parameter of the smoke
sensor is set here to monitor whether there is smoke in the
actual environment. When there is smoke, the host reports an
alarm.
Valid level of digital parameter 4: high level
When the high level represents the valid level, the host does
not report an alarm in the case of high level.
requirements. The monitoring digital parameter of the heat
exchanger is set here to monitor the status of the heat
exchanger. When the heat exchanger is faulty, the host reports
an alarm.
Issue 01 (2016-04-29)

107

Access Module
Item
1 Commissioning

requirements. The digital monitoring parameter of the MDF
door status sensor is set here to monitor the MDF door status.
When the door of the MDF compartment is open, the host
reports an alarm.
NOTE
The following considers the configuration in the F01D500 cabinet as an example to describe
the process of configuring the environment monitoring parameters of the GEPS4845.
huawei(config)#emu add 0 POWER4845 0 0 POWER4845
huawei(config-if-power4845-0)#display power system parameter
huawei(config-if-power4845-0)#display power environment parameter
huawei(config-if-power4845-0)#power battery parameter 1 0.15 60 150
huawei(config-if-power4845-0)#power battery-test auto-test permit 60
huawei(config-if-power4845-0)#power environment temperature 68 -5 80 -20
huawei(config-if-power4845-0)#power temperature-off load-off-state forbid loadoff-temperature 70 battery-off-state permit battery-off-temperature 53
huawei(config-if-power4845-0)#power outside-digital 3 available-level low-level
huawei(config-if-power4845-0)#power outside-digital 4 available-level high-level
huawei(config-if-power4845-0)#display power alarm
huawei(config-if-power4845-0)#quit
huawei(config)#save
Configuring the Environment Monitoring Parameters of the ETP4830

This topic describes how to configure the environment monitoring parameters of the ETP4830
through the CLI.

The ETP4830 monitoring scheme can be used in the F01S300 cabinet. Table 1-34 describes
the mapping between the monitoring parameters displayed
Issue 01 (2016-04-29)

108

Access Module
1 Commissioning
NOTE
Monitoring
Parameter
Displayed on
the Host
Device Port
Application in the F01S300 Cabinet
Digital 0
JTD1
Not connected by default, used to add a userdefined monitoring digital parameter
Digital 1
JTD2
Battery compartment heater (optional

configuration)
Digital 2
JTD3
Device compartment heater (optional

configuration)
Digital 3
JTD4
Surge protector
Digital 4
JTD5
Not connected by default, used to add a userdefined monitoring digital parameter
Digital 5
JTD6
Heat exchanger
Digital 6
JTD7
Door status sensor of the MDF compartment
Door alarm
JTM1
Door status sensors of the device compartment

and heat exchanger compartment
Wiring alarm
JTP1
MDF
Battery Tem
VBTEM2
Environment
Tem
VTEM2
Environment temperature sensor
Smoke
SMOKE
Smoke sensor (optional configuration)
Water
WATER
Water sensor (optional configuration)
Procedure
Step 1 Log in to the device through the maintenance terminal and add an ETP4830 (SMU).
Run the emu add command to add the SMU.
Step 2 Check the default configurations of the power system.
Run the interface emu command to enter environment monitoring mode and then run the
display power system parameter and display power environment parameter commands
to query the default configurations.
Issue 01 (2016-04-29)

109

Access Module
1 Commissioning
Step 3 Configure parameters required for lead-acid batteries.

Run the power battery parameter command to configure parameters required for batteries,
including the management parameters, charging parameters, power-off parameters, and hightemperature power-off parameters. You can use default values of these parameters for
configuration.
Step 4 Run the power battery temperature command to configure the upper/lower temperature test
limits, temperature compensation coefficient, and the upper/lower alarm temperature limits of
the battery set.
Step 5 (Optional) Configure discharging testing parameters.
l
Run the power battery-test command to configure the discharging testing parameters,
including the automatic power-off test, scheduled automatic test, test interval for
automatic discharging, test time for delayed discharging, voltage at the stop of the test,
number of batteries in a battery set, time limit for the discharging test, time limit for
simplified discharging test, alarm thresholds for discharging efficiencies. You can use
default values of these parameters for configuration.
Run the display power battery-test info command to query the discharge testing
information about the batteries.
Step 6 Run the power off command to configure the load power-off and battery set power-off
voltage parameters
Step 7 Run the power temperature-off command to configure the battery high-temperature poweroff parameters.
Step 8 Configure the environment monitoring parameters of the SMU system.
Run the power environment command to configure the upper alarm threshold and the upper
and lower test thresholds for the temperatures and humidity. After these parameters are set,
the system reports alarms if the working environment of the power system does not meet
requirements.
Step 9 Configure required parameters for the rectifier module.
Run the power module-num command to configure the required parameters for the rectifier
module.
Step 10 Configure the external extended digital variables of the power system.
Run the power outside-digital command to configure the external extended digital variables
of the power system.
Step 11 Query the information about the configuration parameters and environment parameters of the
power system.
Run the display power system parameter and display power environment parameter
commands to query the configuration parameters and environment parameters of the power
system.
Step 12 Run the display power alarm command to query the alarm information, and ensure that no
alarm is generated for the monitored objects except the door status.
Step 13 Save the data.
Run the quit command to exit the SMU mode, and run the save command to save the data.
----End
Issue 01 (2016-04-29)

110

Access Module
1 Commissioning
Result
After the configuration, the ETP4830 power system works properly and monitors the
configured parameters. If the status of a monitored parameter becomes abnormal, an alarm is
generated on the device.
Data Plan
Table 1-35 provides the data plan for configuring the monitoring parameters of the ETP4830.
Table 1-35 Data plan for configuring the power monitoring using the ETP4830
Item
EMU
Type: SMU
SN: 1
Subnode ID: 0
NOTE
The subnode ID must be the same as the subnode setting of the corresponding
DIP switches on the EMU, but the subnode ID must be different from IDs of
the other subnodes on the same bus.
Charging
parameters of the
battery
Battery
management
parameters

Equalized charging voltage of the battery (V): 56.5
Float charging voltage of the battery (V): 53.5
Current-limiting coefficient for battery charging:
l One 50 AH battery set: 0.15
l One 92 AH battery set: 0.1
Interval of battery equalized charging (day): 60
Capacity of the battery set:
l One 50 AH battery set: 50
l One 92 AH battery set: 92
The upper/lower
temperature test
limits or
temperature
compensation
coefficient of the
battery set
Upper temperature threshold of the battery set (C): 80
The upper/lower
temperature alarm
limits of the battery
set
Upper temperature alarm limit of the battery set (C): 50
Battery discharging
test parameters
Lower temperature threshold of the battery set (C): -20

Temperature compensation coefficient of the battery set (mV): 80
Lower temperature alarm limit of the battery set (C): -15

Battery auto-discharging test period (day): 120
Issue 01 (2016-04-29)

111

Access Module
1 Commissioning
Item
Load power-off and

battery set poweroff voltage
parameters
Battery hightemperature poweroff parameters
Environment
temperature
parameters
Battery set power-off voltage (V): 43
Temperature for battery high-temperature power-off (C): 53

Upper alarm threshold of the temperature (C): 68
Lower alarm threshold of the temperature (C): -20
Upper test threshold of the temperature (C): 80
Lower test threshold of the temperature (C): -20
Environment
humidity
parameters
Upper alarm threshold of the humidity (% RH): 80

Lower alarm threshold of the humidity (% RH): 0
Upper test threshold of the humidity (% RH): 100
Lower test threshold of the humidity (% RH): 0
Power rectifier
module parameters
The number of the power rectifier modules is configured according

to the actual value. ETP4830 supports up to 2 rectifier modules.
External extended
digital parameters

Available-level: low level
Name: Batt-heater
NOTE
The monitoring digital parameter of the battery compartment heater (optional
configuration) is set here to monitor the battery compartment heater. When
the battery compartment heater is faulty, the device reports an alarm. The
battery compartment heater has the low level when working properly and the
device does not report an alarm.

Name: Eqiup-heater
NOTE
The monitoring digital parameter of the equipment compartment heater
(optional configuration) is set here to monitor the equipment compartment
heater. When the equipment compartment heater is faulty, the device reports
an alarm. The equipment compartment heater has the low level when working
properly and the device does not report an alarm.
Issue 01 (2016-04-29)

112

Access Module
Item
1 Commissioning

Name: SPD
Digital-alarm-index: 20
NOTE
The monitoring digital parameter of the surge protector is set here to monitor
the surge protector. When the surge protector is faulty, the device reports an
alarm. The surge protector has the low level when working properly and the
device does not report an alarm.

Name: HEX
NOTE
The monitoring digital parameter of the heat exchanger is set here to monitor
the status of the heat exchanger. When the heat exchanger is faulty, the device
reports an alarm. The heat exchanger has the low level when working
properly and the device does not report an alarm.

Name: MDF-door
NOTE
The digital monitoring parameter of the MDF door status sensor is set here to
monitor the MDF door status. When the door of the MDF compartment is
open, the device reports an alarm. The MDF compartment has the low level
when its door is closed and the device does not report an alarm.
NOTE
Example
Assume that the F01S300 cabinet is configured with one 50 AH battery set, the ETP4830 is
configured with 2 rectifier modules, and battery compartment heater and equipment
compartment heater are configured. To configure the environment monitoring parameters of
the ETP4830, do as follows:
huawei(config)#emu add 1 SMU 0 0 SMU
huawei(config-if-smu-1)#display power
huawei(config-if-smu-1)#display power
huawei(config-if-smu-1)#power battery
alarm_lower-limit -15
Issue 01 (2016-04-29)
system parameter
environment parameter
parameter 1 0.15 60 50
temperature 80 -20 80
temperature alarm_upper-limit 50

113

Access Module
1 Commissioning
huawei(config-if-smu-1)#power battery-test auto-test permit 120

huawei(config-if-smu-1)#display power battery-test info 1
huawei(config-if-smu-1)#power off battery-off-state permit battery-off-voltage 43
huawei(config-if-smu-1)#power temperature-off battery-off-state permit batteryoff-temperature 53
huawei(config-if-smu-1)#power environment temperature 68 -20 80 -20
This command is invalid unless in the contition of install the sensor, would
you continue? (y/n)[n]:y
huawei(config-if-smu-1)#power environment humidity 80 0 100 0
huawei(config-if-smu-1)#power module-num 2 1 2
huawei(config-if-smu-1)#power outside-digital 2 available-level low-level name
Batt-heater
Equip-heater
SPD digital-alarm 20
HEX digital-alarm 13
MDF-door digital-alarm 9
huawei(config-if-smu-1)#display power system parameter
huawei(config-if-smu-1)#display power environment parameter
huawei(config-if-smu-1)#display power alarm
huawei(config-if-smu-1)#quit
huawei(config)#save
Configuring the Environment Monitoring Parameters of the ETP4890

This topic describes how to configure the environment monitoring parameters of the ETP4890
through the CLI.

The ETP4890 monitoring scheme can be used in the F01D500 and F01T500 cabinet. Table
1-36 describes the mapping between the monitoring parameters displayed
NOTE
Issue 01 (2016-04-29)
Monitoring
Parameter
Displayed on
the Host
Device Port
Application in the
F01D500 Cabinet
Application in the
F01T500 Cabinet
Digital 0
JTD1
Not connected by
user-defined monitoring
digital parameter
Equipment
compartment heater
Digital 1
JTD2
Not connected by
digital parameter
Battery compartment
heater (left)

114

Access Module
1 Commissioning
Monitoring
Parameter
Displayed on
the Host
Device Port
Application in the
F01D500 Cabinet
Application in the
F01T500 Cabinet
Digital 2
JTD3
Not connected by
digital parameter
Battery compartment
heater (right)
Digital 3
JTD4
Surge protector (SPD)
Surge protector (SPD)
Digital 4
JTD5
Not connected by
digital parameter
Battery compartment
door status sensor
Digital 5
JTD6
Heat exchanger
Heat exchanger
Digital 6
JTD7

the MDF compartment

the MDF compartment
Door alarm
JTM1

the device compartment
and heat exchanger
compartment

the device compartment
and heat exchanger
compartment
Wiring alarm
JTP1
MDF
Water alarm
WATER
Water sensor
Battery Tem
VBTEM2
Battery temperature
sensor
Battery temperature
sensor
environment Tem
VTEM2
Environment
temperature sensor
Environment
temperature sensor
Smoke
SMOKE
Smoke sensor
Smoke sensor
Procedure
Step 1 Log in to the device through the maintenance terminal and add an ETP4890 (SMU).
Run the emu add command to add the SMU.
Step 2 Check the default configurations of the power system.
Run the interface emu command to enter environment monitoring mode and then run the
display power system parameter and display power environment parameter commands
to query the default configurations.
Step 3 Configure parameters required for lead-acid batteries.
Run the power battery parameter command to configure parameters required for batteries,
including the management parameters, charging parameters, power-off parameters, and highIssue 01 (2016-04-29)

115

Access Module
1 Commissioning
temperature power-off parameters. You can use default values of these parameters for
configuration.
Step 4 Run the power battery temperature command to configure the upper/lower temperature test
limits, temperature compensation coefficient, and the upper/lower alarm temperature limits of
the battery set.
Step 5 (Optional) Configure discharging testing parameters.
l
Run the power battery-test command to configure the discharging testing parameters,
including the automatic power-off test, scheduled automatic test, test interval for
automatic discharging, test time for delayed discharging, voltage at the stop of the test,
number of batteries in a battery set, time limit for the discharging test, time limit for
simplified discharging test, alarm thresholds for discharging efficiencies. You can use
default values of these parameters for configuration.
Run the display power battery-test info command to query the discharge testing
information about the batteries.
Step 6 Run the power off command to configure the load power-off and battery set power-off
voltage parameters
Step 7 Run the power temperature-off command to configure the battery high-temperature poweroff parameters.
Step 8 Configure the environment monitoring parameters of the SMU system.
Run the power environment command to configure the upper alarm threshold and the upper
and lower test thresholds for the temperatures and humidity. After these parameters are set,
the system reports alarms if the working environment of the power system does not meet
requirements.
Step 9 Configure required parameters for the rectifier module.
Run the power module-num command to configure the required parameters for the rectifier
module.
Step 10 Configure the external extended digital variables of the power system.
Run the power outside-digital command to configure the external extended digital variables
of the power system.
Step 11 Query the information about the configuration parameters and environment parameters of the
power system.
Run the display power system parameter and display power environment parameter
commands to query the configuration parameters and environment parameters of the power
system.
Step 12 Run the display power alarm command to query the alarm information, and ensure that no
alarm is generated for the monitored objects except the door status.
Run the quit command to exit the SMU mode, and run the save command to save the data.
----End
Issue 01 (2016-04-29)

116

Access Module
1 Commissioning
Result
After the configuration, the ETP4890 power system works properly and monitors the
configured parameters. If the status of a monitored parameter becomes abnormal, an alarm is
generated on the device.
Data Plan
Table 1-37 provides the data plan for configuring the monitoring parameters of the ETP4890.
Table 1-37 Data plan for configuring the power monitoring using the ETP4890
Item
Data Plan for the F01D500/F01T500 Cabinet
EMU
Type: SMU
SN: 0
Subnode ID: 0
NOTE
corresponding DIP switches on the EMU, but the subnode ID must be
different from IDs of the other subnodes on the same bus.
the battery

Equalized charging voltage of the battery (V): 56.5
Float charging voltage of the battery (V): 53.5
Battery management
parameters

Interval of battery equalized charging (day): 60
Number of battery sets:
l F01D500: 1
l F01T500: 2
Capacity of the battery set:
F01D500:
l Two 75 AH battery sets: 150
l Two 92 AH battery sets: 184
F01T500:
Two 100 AH battery sets: 200
Issue 01 (2016-04-29)
The upper/lower
temperature test limits or
temperature
compensation coefficient
of the battery set
Upper temperature threshold of the battery set (C): 80
The upper/lower
of the battery set
Upper temperature alarm limit of the battery set (C): 50
Lower temperature threshold of the battery set (C): -20

Temperature compensation coefficient of the battery set (mV):
80
Lower temperature alarm limit of the battery set (C): -15

117

Access Module
1 Commissioning
Item

parameters

Battery auto-discharging test period (day):
l F01D500: 180
l F01T500: 120
Load power-off and

battery set power-off
voltage parameters
Load power-off status: forbid

Load power-off voltage (V): 44
Battery set power-off voltage (V): 43
Battery high-temperature
Environment temperature
parameters

Temperature for battery high-temperature power-off (C): 53
Upper alarm threshold of the temperature (C):
l F01D500: 68
l F01T500: 72
Lower alarm threshold of the temperature (C): -5
Upper test threshold of the temperature (C): 80
Lower test threshold of the temperature (C): -20
Environment humidity
parameters
Upper alarm threshold of the humidity (% RH): 80

Lower alarm threshold of the humidity (% RH): 0
Upper test threshold of the humidity (% RH): 100
Lower test threshold of the humidity (% RH): 0

parameters

according to the actual value. ETP4890 supports up to 3
rectifier modules.

parameters

Name: SPD
NOTE
The monitoring digital parameter of the surge protector is set here to
monitor the surge protector. When the surge protector is faulty, the
device reports an alarm. The surge protector has the low level when
working properly and the device does not report an alarm.
Issue 01 (2016-04-29)

118

Access Module
Item
1 Commissioning

Name: HEX
NOTE
The monitoring digital parameter of the heat exchanger is set here to
monitor the status of the heat exchanger. When the heat exchanger is
faulty, the device reports an alarm. The heat exchanger has the low
level when working properly and the device does not report an alarm.

Name: MDF-door
NOTE
The digital monitoring parameter of the MDF door status sensor is set
here to monitor the MDF door status. When the door of the MDF
compartment is open, the device reports an alarm. The MDF
compartment has the low level when its door is closed and the device
does not report an alarm.
NOTE
Example
Assume that the F01D500 cabinet is configured with two 75 AH battery sets, the ETP4890 is
configured with 3 rectifier modules. To configure the environment monitoring parameters of
the ETP4890, do as follows:
huawei(config)#emu add 1 SMU 0 0 ETP4890
huawei(config-if-smu-1)#power battery parameter 0.15 60 1 150
huawei(config-if-smu-1)#power battery temperature 80 -20 80
huawei(config-if-smu-1)#power battery temperature alarm_upper-limit 50
alarm_lower-limit -15
huawei(config-if-smu-1)#power battery-test auto-test permit 180
huawei(config-if-smu-1)#display power battery-test info 1
huawei(config-if-smu-1)#power off load-off-state forbid load-off-voltage 44
battery-off-state permit battery-off-voltage 43
huawei(config-if-smu-1)#power temperature-off battery-off-state permit batteryoff-temperature 53
huawei(config-if-smu-1)#power environment temperature 68 -5 80 -20
huawei(config-if-smu-1)#power environment humidity 80 0 100 0
huawei(config-if-smu-1)#power module-num 3 1 2 3
Issue 01 (2016-04-29)

119

Access Module
1 Commissioning
SPD digital-alarm 20
HEX digital-alarm 13
MDF-door digital-alarm 9
huawei(config-if-smu-1)#display power alarm
huawei(config-if-smu-1)#quit
huawei(config)#save
Configuring the Power3000 Environment Monitoring Mode

This topic describes how to configure environment monitoring parameters by using the CLI.
Power3000 is configured correctly in the system.
Table 1-38 Commands for configuring the Power3000
Issue 01 (2016-04-29)
To...
Run the Command...
Add an EMU
emu add


parameters

parameters
power charge


limits

power off
Configure the power


power battery-test

power module-num

120

Access Module
1 Commissioning
To...
Run the Command...

parameters

power environment

digital parameters
1.
2.
Query the status of the Power3000.
3.
configuration.
4.
5.
6.
7.
8.
9.
the power system.
10. Save the data.
Data Plan
Table 1-39 provides the data plan for configuring the monitoring parameters of the
Power3000.
Table 1-39 Data plan for configuring the monitoring parameters of the Power3000
Item
Data Plan
EMU
Type: POWER3000
SN: 0
Subnode ID: 0
corresponding DIP switches on the EMU, but the subnode ID
must be different from IDs of the other subnodes on the same
bus.
the battery

Issue 01 (2016-04-29)

121

Access Module
1 Commissioning
Item
Data Plan
Battery management
parameters

The battery capacity is configured according to the actual
value.
The upper/lower
or the upper/lower
temperature test limits
Battery set power-off

parameters
Power distribution
parameters

Temperature compensation coefficient of the battery set: 80
mV


parameters


parameters
Battery high-temperature
Environment monitoring
parameters

according to the actual value. POWER3000 supports up to 12
rectifier modules.

parameters
Digital parameter ID: 0-6

requirements.
NOTE
Issue 01 (2016-04-29)

122

Access Module
1 Commissioning
The following considers the configuration plan of the Power3000 as an example to describe
the process of configuring the environment monitoring parameters of the Power3000.
huawei(config)#emu add 0 POWER3000 0 0 POWER3000
huawei(config-if-power3000-0)#power battery parameter 1 0.15 60 65
huawei(config-if-power3000-0)#power battery-test auto-test permit 60
huawei(config-if-power3000-0)#power temperature-off battery-off-state permit
huawei(config-if-power3000-0)#power environment temperature 68 -5 80 -20
huawei(config-if-power3000-0)#quit
huawei(config)#save
Commissioning the EMU_TCU

This topic describes how to commission the TCU to ensure that it monitors and controls the
temperature conditions of the heat exchanger according to the actual conditions.
Context
NOTE
Commissioning the TCU only when the device is installed in the outdoor cabinet scenario.
The TCU is used to monitor the running status of the heat exchanger and to set the heating
start temperature or the heating stop temperature according to actual conditions to ensure the
normal heat dissipation of the device.
When commissioning the TCU, pay attention to the following points:
l
The TCU sub-nodes are numbered from 0 to 31.
Table 1-40 lists the default configuration of the TCU.

Table 1-40 Default configuration of the TCU
Parameter
Default Value
Sub-node
Procedure
Step 1 Run the emu add command to add a TCU. By default, the sub-node ID is 7.
NOTE
The TCU communicates with the MA5600T/MA5603T/MA5608T in the master node and sub-node
mode. the DIP switches of the sub-nodes for the TCU not need to be set on site.
Step 2 Run the interface emu command to enter the TCU mode.
Issue 01 (2016-04-29)

123

Access Module
1 Commissioning
Step 3 Run the tcu heat temperature command to set the heating start temperature and the heating
stop temperature of the heat exchanger.
l
When the current temperature is lower than the heating start temperature, the heater
starts heating. The default value of the heating start temperature is 5 C.
When the temperature after heating reaches the heating stop temperature, the heater
automatically stops heating. The default value of the heating stop temperature is 25 C.
When setting the heating start/stop temperature for the heat exchanger, ensure that the
heating start temperature is lower than the heating stop temperature.
Step 4 Run the tcu temperature command to set the high-temperature alarm threshold and the lowtemperature alarm threshold of the heat exchanger.
l
When the current temperature of the heat exchanger is higher than the high-temperature
threshold, the excessively high temperature alarm is reported. The default value of the
high-temperature threshold is 68 C.
When the current temperature of the heat exchanger is lower than the low-temperature
threshold, the excessively low temperature alarm is reported. The default value of the
low-temperature threshold is -20C.

----End
Result
l
In the TCU mode, run the display tcu system parameter command to query the
parameter configuration of the heat exchanger and ensure that the configuration is the
same as the data plan.
In the TCU mode, run the display tcu environment info command to query the running
status of the heat exchanger and ensure that it is the same as the data plan.
In the TCU mode, run the display tcu alarm command to query the alarm information
reported by the TCU. The status of all the heat exchanger alarms is normal.
Example
To add a TCU (emuid: 2; sub-node: 7), and set the heating start temperature to -10C and the
heating stop temperature to 30C for heat exchanger 2, do as follows:
huawei(config)#emu add 2 TCU 0 7 tcu
huawei(config-if-tcu-2)#tcu heat temperature
{ start-temperature<F><-90,40> }:-10
{ end-temperature<F><-90,40> }:30
Command:
tcu heat temperature -10 30
Send command to environment monitor board ,please wait for a moment
huawei(config-if-tcu-2)#
Execute command successful
Commissioning the EMU_FAN

This topic describes how to commission the FAN to ensure that it monitors the environmental
conditions of the fans of the device according to the actual conditions.
Issue 01 (2016-04-29)

124

Access Module
1 Commissioning
Context
NOTE
When the device is delivered, the EMU_FAN is correctly connected to the shelf. The connection need
not be changed for the device commissioning. In certain cases, if the EMU needs to be configured in
other shelves, reconnect the EMU. For details, see this topic.
The FAN is used to monitor the running status of the fans and to set the fan rotation speed
according to actual conditions to ensure the normal heat dissipation of the device.
When commissioning the FAN, pay attention to the following points:
l
The EMU sub-nodes are numbered from 0 to 31.
It is recommended that you use the auto mode as the fan speed adjustment mode.
Table 1-41 lists the default configuration of the FAN.

Table 1-41 Default configuration of the FAN
Parameter
Default Value
Sub-node
Fan speed
adjustment mode
Automatic
Whether to report
the fan alarm
Permit
Procedure
Step 1 Set the DIP switches of the sub-nodes for the FAN. By default, the sub-node ID is 1.
NOTE
The FAN communicates with the MA5600T/MA5603T/MA5608T in the master node and sub-node
mode. Therefore, the DIP switches of the sub-nodes for the FAN must be consistent with those for the
MA5600T/MA5603T/MA5608T. For details about how to configure the DIP switches of the FAN, see
the Description of DIP Switches in Checking the Settings of DIP Switches on the Fan Monitoring
Board. The Description of DIP Switches in Checking the Settings of DIP Switches on the Fan
Monitoring Board applies only to the MA5600T/MA5603T/MA5608T, but does not apply to the
MA5608T.
Step 2 Insert the fan tray into the corresponding slot of the service shelf.
Step 3 Run the emu add command to add a FAN. By default, the sub-node ID is 1.
Step 4 Run the interface emu command to enter the FAN mode.
Step 5 Run the fan speed mode auto or fan speed mode manual command to set the fan speed
adjustment mode. By default, the fan speed adjustment mode is automatic.
NOTE
When the fan speed adjustment mode is the manual mode, you can run the fan speed mode manual
command to set the fan speed. The speed level can be 0, 1, 2, 3, 4, 5 or 6. Here, 6 stands for the highest
level, and 0 stands for the lowest level.
Issue 01 (2016-04-29)

125

Access Module
1 Commissioning
Step 6 Run the fan alarmset command to configure the fan alarm reporting function. The fan alarms
are read temperature failure alarm, fan block alarm, over temperature alarm, and power fault
alarm. By default, the fan alarm reporting is permitted.
----End
Result
l
In the FAN mode, run the display fan system parameter command to query the
parameter configuration of the fan tray and ensure that the configuration is the same as
the data plan.
In the FAN mode, run the display fan environment info command to query the running
status of the fan tray and ensure that it is the same as the data plan.
In the FAN mode, run the display fan alarm command to query the alarm information
reported by the fan tray. The status of all the fan alarms is normal.
Example
To add a FAN, and adopt the default settings for the speed adjustment mode and alarm
function, do as follows:
huawei(config)#emu add 0 FAN 0 1 FAN
huawei(config-if-fan-0)#display fan system parameter
EMU ID: 0
FAN configration parameter:
---------------------------------------------------------------------------FAN timing mode: Auto timing by temperature
---------------------------------------------------------------------------Alarm_name
Permit/Forbid
Read temperature fault
Permit
Fan block
Permit
Temperature high
Permit
Power fault
Permit
----------------------------------------------------------------------------
1.3.17 Saving and Backing Up Data

The MA5600T/MA5603T/MA5608T supports data saving and backup to upgrade the system
or to recover the system in case of an upgrade failure or any other critical events.
Manually Saving and Backing Up Data

This topic describes how to manually save data to the flash memory or back up data to the
server in case of data loss caused by an unexpected system restart.
Prerequisites
The file transfer mode is configured. For detailed configurations, see
l
Configuring the FTP Transfer Mode
Configuring the SFTP Transfer Mode
Configuring the TFTP Transfer Mode
Issue 01 (2016-04-29)

126

Access Module
1 Commissioning
NOTE
You need to configure only one of the above-mentioned three file transfer modes. You are advised to use
SFTP mode.
Procedure
l
Manually save data.

System data files are saved manually.
The system data files include the database file and the configuration file. Table 1-42 lists
the commands for manually saving the data files and describes command functions.
Table 1-42 List of commands for manually saving the data files
Operation
Command
Function
Manually save the

database file
save data
Saves only the database

file but not the
configuration file.
Manually save the

configuration file
save configuration
Saves only the

configuration file but not
the database file.
Manually save the

database file and the
configuration file
save
Saves the database file and

the configuration file.
Select one of the saving modes in Table 1-42 to manually save the system data files
according to the actual requirements.
Manually back up data.

System data files are backed up manually.
Prerequisite
Data is saved. For detailed configurations, see Manually save data.
The system data files include the database file and the configuration file. Table 1-43 lists
the commands for manually backing up the data files and describes command functions.
Issue 01 (2016-04-29)

127

Access Module
1 Commissioning
Table 1-43 List of commands for manually backing up the data files
Operation
Command
Function
Manually back up the

database file
backup data
l Manually backs up the

database file to the
server.
l The IP address of the
server where the
backup files are stored
must be identical to the
one configured in the
FTP/SFTP/TFTP tool.
The file name must be
specified.
Manually back up the

configuration file
backup configuration
l Manually backs up the

configuration file to the
server.
l The IP address of the
server where the
backup files are stored
must be identical to the
one configured in the
FTP/SFTP/TFTP tool.
The file name must be
specified.
Select one of the backup modes in Table 1-43 to manually back up the system data
according to the actual requirements.
----End
Result
1.
The system displays a message indicating that the database file and the configuration file
have been saved successfully.
2.
After the backup is completed, you can locate the file backed up in the path that you set
in the FTP tool.
Example
Manually saving data
Select one of the following modes to save the database file or the configuration file.
l
To save the database file in the system, do as follows:

huawei(config)#save data
The data is being saved, please wait a moment...
huawei(config)#
1 [2010-07-12 14:32:00+08:00]:The percentage of saved data on 9 slot's main
control board is: 21%
Issue 01 (2016-04-29)

128

Access Module
1 Commissioning
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
1 [2010-07-12 14:32:19+08:00]:The data of 9 slot's main control board is
saved
completely
To save the configuration file in the system, do as follows:

huawei#save configuration
huawei#
It will take several minutes to save configuration file, please wait...
huawei#
Configuration file had been saved successfully
Note: The configuration file will take effect after being activated
To save the database file and the configuration file in the system, do as follows:
WS6803(config)#save
{ <cr>|configuration<K>|data<K> }:
Command:
save
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
Issue 01 (2016-04-29)

129

Access Module
1 Commissioning
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
huawei(config)#
1 [2010-07-12 14:35:25+08:00]:The data of 9 slot's main control board is
saved
completely
Manually backing up data

1.
For configuring and enabling the FTP tool on the backup sever, see Configuring the
FTP Transfer Mode.
2.
Select one of the following modes to back up the database file or the configuration file to
the server.
Assume that the IP address of the backup server is 10.10.10.1 and the database file
name is data0.dat. To back up the database file to the backup server through FTP, do
as follows:
huawei(config)#backup data ftp 10.10.10.1 data0.dat
Command:
backup data tftp 10.10.10.1
data0.dat
Please save database file before backup, or the database file that is
backed
up may be not the lastest one. Are you sure to continue? (y/n)[n]: y
Load(backup,duplicate,...) begins, please wait and notice the rate of
progress
Any operation such as reboot or switchover will cause failure and
unpredictable result
Backing up files starts from the host to the maintenance terminal
PARAMETERS :FrameID: 0, SlotID: 9, Position: -1, Backup type: Host
data,
Backup Object: Active control board
huawei(config)#
huawei(config)#
Backing up files is successful from the host to the maintenance
terminal
PARAMETERS :FrameID: 0, SlotID: 9, Position: -1, Backup type: Host
data,
Backup Object: Active control board
Assume that the IP address of the backup server is 10.10.10.1 and the configuration
file name is config0.txt. To back up the configuration file to the backup server
through FTP, do as follows:
huawei(config)#backup configuration ftp 10.10.10.1 config0.txt
Please save configuration file before backup, or the configuration
file
backuped may be not the lastest. Are you sure to continue? (y/n)[n]:
y
Issue 01 (2016-04-29)

130

Access Module
1 Commissioning
Load(backup,duplicate,...) begins, please wait and notice the rate of

progress
Any operation such as reboot or switchover will cause failure and
unpredictable result
Backing up files starts from the host to the maintenance terminal
PARAMETERS :FrameID: 0, SlotID: 9, Position: -1, Backup type:
Configuration
file, Backup Object: Active control board
huawei#
huawei#
Backing up files is successful from the host to the maintenance
terminal
PARAMETERS :FrameID: 0, SlotID: 9, Position: -1, Backup type:
Configuration
file, Backup Object: Active control board
Configuring the Auto-save and Auto-backup Functions

This topic describes how to configure the auto-save and auto-backup functions so that data is
automatically saved in the flash memory or backed up to the server. These functions ensure
that data or configuration files are not lost after emergency restart.
Prerequisites
The file transfer mode is configured. For details, see the following descriptions.
l
Configuring the FTP File Transfer Mode
Configuring the FTP File Transfer Mode
Configuring the TFTP File Transfer Mode

NOTE
You need to configure only one of the above-mentioned three file transfer modes. You are advised to use
SFTP mode.
Procedure
Step 1 Configure the auto-save function and an auto-backup server.
l
Configure the auto-save function

If the auto-save function is enabled, the system periodically checks whether data is
modified at the preset time or at a preset interval. If data is modified, the system
automatically saves the modified data. Otherwise, the system does not perform the autosave operation.
Data to be saved includes database files and configuration files. Table 1-44 lists the
commands and functions of auto-save operations.
Issue 01 (2016-04-29)

131

Access Module
1 Commissioning
Table 1-44 Auto-save operations

Auto-save
Command
Function
Set the auto-save file type.
autosave type { all |

configuration | data }
data: Saves only

database files.
configuration: Saves
only configuration
files.
all: Saves both
database files and
configuration files.
Save database files

automatically at the preset
time.
autosave time
Save database files

automatically at an
interval.
autosave interval
The system saves data

at the preset time.
By default, the system
automatically saves
data at 00:00:00 every
day.
The system
automatically saves
data at a preset interval.
By default, the system
saves database files at
an interval of 30
minutes.
NOTE
By default, the autosave interval function is disabled in the system. That is, the system does not
automatically save data. Hence, you need to manually save data.
When the autosave interval function is enabled, you still can manually save data.
If data is saved frequently, the system will be affected. Therefore, it is suggested that you set the
auto-save interval to longer than 60 minutes. It is better to set the auto-save interval to equal to or
longer than one day.
Before upgrading the system, run the autosave intervaloff or autosave timeoff command to disable
the auto-save function to prevent upgrade failure due to the conflict between upgrade and auto-save
operations.
NOTICE
After the system upgrade is complete, you must re-enable the auto-save function if the auto-save
function is required.
Configure an auto-backup server.

An auto-backup server backs up data, configuration, and logs of a device to an external
server. After an auto-backup server is configured, you can configure the auto-backup
function.
Auto-backup servers are classified into an active auto-backup server and standby autobackup server.
Issue 01 (2016-04-29)

132

Access Module
1 Commissioning
You can configure only an active auto-backup server or you can configure active
and standby auto-backup servers to ensure that data is backed up.
When the active auto-backup server does not work properly, data is automatically
backed up to the standby auto-backup server.
Run the file-server autobakup command to configure the active and standby autobackup servers for backing up data, configuration, and logs.
NOTE
The file transfer mode, user name, and password configured must be the same as those of xFTP.
Step 2 Configure the auto-backup function.

The database files, configuration files, and logs in the system are automatically backed up to a
specified external server.
Table 1-45 lists the commands and functions of auto-backup operations.
Table 1-45 Auto-backup operations
Auto-backup
Command
Function
Back up database files

automatically.
auto-backup manual data
Immediately and automatically

back up database files to the
auto-backup server.
l auto-backup period data

interval
l Automatically back up
database files to the autobackup server at an interval.
l auto-backup period data

enable
Back up configuration
files automatically.
l Set the interval and start

time of automatically
backing up database files
and then enable the autobackup function for
database files.
auto-backup manual
configuration
Immediately and automatically

back up configuration files to
the auto-backup server.
l auto-backup period
configuration interval
l Automatically back up
configuration files to the
auto-backup server at an
interval.
l auto-backup period
configuration enable
l Set the interval and start

time of automatically
backing up configuration
files and then enable the
auto-backup function for
configuration files.
Back up logs.
l auto-backup period log

interval
l auto-backup period log
enable
Issue 01 (2016-04-29)

Set the interval and start time of

automatically backing up logs
and then enable the autobackup function for logs.
133

Access Module
1 Commissioning
----End
Result
1.
After the auto-save function is configured, run the display autosave configuration
command to query the preset time and preset interval.
2.
After the auto-backup server is configured, run the display file-server auto-backup
command to query configuration information about the file server, including server type,
file transfer mode, IP address, user name, and password (the last three parameters are for
only FTP and SFTP).
3.
After the auto-backup function is configured, you can browse backup files in the path
that files configured in xFTP are saved to. The file names are assigned by the system.
Example
Configure the auto-save function.
1.
Configure the type of auto-save data, including database files and configuration files.
huawei(config)#autosave
type
{ all<K>|configuration<K>|
data<K> }:all
Command:
autosave type all
2.
Configure the auto-save function at a specified time or at a preset interval.
Set the auto-save time at 02:00:00 and enable the auto-save function.
huawei(config)#autosave time
02:00:00
System autosave time switch:
off
Autosave time:
02:00:00
Autosave type: data and configuration file
huawei(config)#autosave time
on
System autosave time switch:
on
Autosave time:
02:00:00
Set the auto-save interval to 1440 minutes and enable the autosave interval
function. The system checks whether the configuration data is modified every 1440
minutes. If the configuration data is modified, the system automatically saves the
modified configuration. Otherwise, the system does not perform the auto-save
operation.
NOTICE
The autosave interval command conflicts with the autosave time command. You
can use either of the commands to enable the auto-save function. To switch from
one function to the other one, you need to disable the enabled function first.
Issue 01 (2016-04-29)

134

Access Module
1 Commissioning
huawei(config)#autosave interval
1440
System autosave interval switch:
off
Autosave interval: 1440
minutes
huawei(config)#autosave interval
on
System autosave interval switch:
on
minutes
Autosave type: data and configuration
file
System autosave modified configuration switch:
on
minutes
Configure the auto-backup function.

1.
Select any of the following modes to back up database files, configuration files, and logs
to the backup server.
To enable the auto-backup function for the database file, and set the auto-backup
interval to one day and the start time to 02:30, do as follows:
huawei(config)#auto-backup period data interval 1 time 02:30
huawei(config)#auto-backup period data enable
To enable the auto-backup function for the configuration file, and set the autobackup interval to one day and the start time to 03:30, do as follows:
huawei(config)#auto-backup period configuration interval 1 time 03:00
huawei(config)#auto-backup period configuration enable
To enable the auto-backup function for the logs, and set the auto-backup interval to
one day and the start time to 06:00, do as follows:
huawei(config)#auto-backup period log interval 1 time 06:00
huawei(config)#auto-backup period log enable
1.4 Interconnection Commissioning

The following recommended commissioning tasks and sequences are for reference only.
Different offices have different conditions; therefore, it is recommended that customers, with
the assistance of Huawei engineers, modify commissioning tasks according to actual
requirements.
1.4.1 Commissioning the Interconnection with the NMS

The MA5600T/MA5603T/MA5608T provides the function of interconnecting with the
network management system, with which the administrator can maintain and manage the
MA5600T/MA5603T/MA5608T through the NMS. This topic considers the iManager U2000
Network Management System (hereinafter referred to as the U2000) as an example to
describe how to perform the interconnection commissioning between the U2000 and the
MA5600T/MA5603T/MA5608T in the inband mode and the outband mode. SNMPv3 has
higher security than SNMPv1 and SNMPv2c. Therefore, it is recommended.
Issue 01 (2016-04-29)

135

Access Module
1 Commissioning
Commissioning Outband Network Management (SNMP V1 and V2)

This topic describes how to implement the outband network management on the MA5600T/
MA5603T/MA5608T using the local maintenance Ethernet port (outband network
management port). This enables the U2000 to maintain the MA5600T/MA5603T/MA5608T
using this management channel. In the outband network management mode, a non-service
channel is used to transmit the management information. With the use of the non-service
channel, the management channel is separated from the service channel, which is more
reliable than in the inband network management mode.
Service Requirements
In the network as shown in Figure 1-49, the service requirements are as follows:
l
The MA5600T/MA5603T/MA5608T provides the outband network management

channel using the local maintenance Ethernet port.
A static route is used between the MA5600T/MA5603T/MA5608T and the U2000.
Figure 1-49 Example network for the outband network management
Access node
10.50.1.10/24
Router
10.50.1.1/24
U2000
10.10.1.10/24
Figure 1-50 shows the flowchart for commissioning the outband network management on the
device.
Issue 01 (2016-04-29)

136

Access Module
1 Commissioning
Figure 1-50 Flowchart for commissioning the outband network management on the device
Procedure
l
Commission the outband network management on the device.

a.
Configure the IP address of the maintenance Ethernet port.

The IP address of the local maintenance Ethernet port (outband network
management port) of the MA5600T/MA5603T/MA5608T is 10.50.1.10/24.
NOTE
By default, the IP address of the maintenance Ethernet port (ETH port on the control board)
is 10.11.104.2, and the subnet mask is 255.255.255.0.
huawei(config-if-meth0)#ip address 10.50.1.10 255.255.255.0
b.
Add a route for the outband network management.

Use the static route. The destination IP address is 10.10.1.0/24 (the network
segment to which the U2000 belongs), and the gateway IP address is 10.50.1.1/24
(the IP address of the gateway of the MA5600T/MA5603T/MA5608T).
c.
Set the SNMP parameters.

i.
Configure the community name and the access authority.

The read community name is public123, and the write community name is
private123.
Issue 01 (2016-04-29)

137

Access Module
1 Commissioning
NOTE
The configurations of the read community name and the write community name must
be the same as the configurations on the U2000.
huawei(config)#snmp-agent community read public123
huawei(config)#snmp-agent community write private123
ii.
(Optional) Set the ID and the contact means of the administrator.

The contact means of the administrator is HW-075528780808.
huawei(config)#snmp-agent sys-info contact HW-075528780808
iii. (Optional) Set the location of the device.

The location of the device is Shenzhen_China.
huawei(config)#snmp-agent sys-info location Shenzhen_China
iv.
Set the SNMP version.
The SNMP version is SNMP V1.

huawei(config)#snmp-agent sys-info version v1

huawei(config)#snmp-agent sys-info version v2c
NOTE
The SNMP version must be the same as the SNMP version set on the U2000.
d.
Enable the function of sending traps.

On the MA5600T/MA5603T/MA5608T, enable the function of sending traps to the
U2000.
huawei(config)#snmp-agent trap enable standard
e.
Configure the IP address of the destination host for the traps.

n
When the SNMP V1 is used, the host name is huawei, the IP address of the
host is 10.10.1.10/24 (IP address of the U2000), the trap parameter name is
ABC, SNMP version is V1, and the parameter security name is private (the
parameter security name is the SNMP community name).
huawei(config)#snmp-agent target-host trap-hostname huawei address
10.10.1.10
trap-paramsname ABC
huawei(config)#snmp-agent target-host trap-paramsname
ABC v1 securityname private
10.10.1.10 trap-paramsname ABC
huawei(config)#snmp-agent target-host trap-paramsname ABC
v2c securityname private
f.
Set the IP address of the maintenance Ethernet port as the source IP address for
sending traps.
Set the SNMP packets to be forwarded from the maintenance Ethernet port of the
MA5600T/MA5603T/MA5608T. That is, the source address of the traps is meth 0.
huawei(config)#snmp-agent trap source meth 0
g.
Save the data.

huawei(config)#save
Commission the outband network management on the U2000.

a.
Issue 01 (2016-04-29)
Configure the gateway of the route from the U2000 to network segment
10.50.1.0/24 to 10.10.1.1.
138

Access Module
n
1 Commissioning
In the Solaris OS, do as follows:

Run the route add 10.50.1.0 10.10.1.1 command to add a route.
Run the netstat -r command to query the information about the current routing
table.
In the Windows OS, do as follows:

Run the route add 10.50.1.0 mask 255.255.255.0 10.10.1.1 command to add a
route.
Run the route print command to query the information about the current
routing table.
NOTE
If the IP address of the outband network management port and the IP address of the U2000
are in the same network segment, you need not configure the routing information.
b.
Log in to the U2000.
c.
Set the SNMP parameters. A default SNMP profile exists in the system. Use the
default profile in this service. If a new profile is required, do as follows:
i.
Choose Administration > NE Communicate Parameter > Default Access

Protocol Parameters from the main menu.
ii.
When the SNMP V1 is used, choose SNMP v1 Parameter on the

Default Access Protocol Parameters tab page. Then click Add and set
the SNMP parameters, as shown in the following figure (the other
parameters except Profile name use the default settings).
Figure 1-51 Set the SNMP parameters

Issue 01 (2016-04-29)

139

Access Module
1 Commissioning
NOTE
The configurations of Get Community and Set Community are the same as the
configurations on the MA5600T/MA5603T/MA5608T.
iii. Click OK.

iv.
Select the added SNMP parameters. Click OK.
v.
In the dialog box that is displayed, click Yes to test the set SNMP parameters.
vi. The U2000 displays the Loading dialog box. After the testing is complete,
click OK.
d.
Add a device.
i.
In the Physical Root navigation tree on the Main Topology tab page, rightclick and choose New > NE from the shortcut menu.
ii.
In the dialog box that is displayed, choose Access NE > Access NE from the
main menu.
iii. In the right pane, set the parameters.
When the SNMP V1 is used, In the dialog box that is displayed, set the
required parameters, as shown in the following figure.
IP Address is 10.50.1.10, Device Name is huawei, and SNMP
Parameters is SNMP V1:default.
Figure 1-53 Add device
Issue 01 (2016-04-29)

140

Access Module
1 Commissioning
iv.
Click OK. The system displays a message indicating that several seconds or
some 10 minutes are required for uploading the device data. After the related
data is read, the system automatically refreshes and displays the device icon.
----End
Result
You can maintain and manage the MA5600T/MA5603T/MA5608T using the U2000.
Configuration File
The following describes the script for commissioning the outband network management on
the device (SNMP V1).
interface meth 0
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent community read public
snmp-agent community write private
snmp-agent sys-info contact HW-075528780808
snmp-agent sys-info location Shenzhen_China
snmp-agent sys-info version v1
snmp-agent trap enable standard
snmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABC
snmp-agent target-host trap-paramsname ABC v1 securityname private
snmp-agent trap source meth 0
save
Issue 01 (2016-04-29)

141

Access Module
1 Commissioning
the device (SNMP V2).
interface meth 0
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent sys-info version v2c
snmp-agent target-host trap-paramsname ABC v2c securityname private
save
Commissioning Outband Management (SNMP V3)

This topic describes how to implement the outband network management on the MA5600T/
MA5603T/MA5608T using the local maintenance Ethernet port (outband network
management port). This enables the U2000 to maintain the MA5600T/MA5603T/MA5608T
using this management channel. In the outband network management mode, a non-service
channel is used to transmit the management information. With the use of the non-service
channel, the management channel is separated from the service channel, which is more
reliable than in the inband network management mode.
l
The MA5600T/MA5603T/MA5608T provides the outband network management

channel through the local maintenance Ethernet port.
SNMP V3 is used (more reliable than V1 and V2, providing network security and access
control management functions).
Figure 1-55 Example network for the outband network management
Access node
10.50.1.10/24
Router
10.50.1.1/24
U2000
10.10.1.10/24
Figure 1-56 shows the flowchart for commissioning the outband network management on the
device.
Issue 01 (2016-04-29)

142

Access Module
1 Commissioning
Figure 1-56 Flowchart for commissioning the outband network management on the device
Procedure
l
Commission the outband network management on the device.

a.
Configure the IP address of the maintenance Ethernet port.

The IP address of the local maintenance Ethernet port (outband network
management port) of the MA5600T/MA5603T/MA5608T is 10.50.1.10/24.
NOTE
By default, the IP address of the maintenance Ethernet port (ETH port on the control board)
is 10.11.104.2, and the subnet mask is 255.255.255.0.
b.
Add a route for the outband network management.

c.

i.
Configure the SNMP user, group, and view.

The user name is user1, the group name is group1, the user authentication
mode is SHA, the authentication password is authkey123, the user encryption
Issue 01 (2016-04-29)

143

Access Module
1 Commissioning
mode is aes128, the encryption password is prikey123, the read, write and
notify view names are hardy, and the view includes the internet subtree.
huawei(config)#snmp-agent usm-user
authentication-mode sha authkey123
huawei(config)#snmp-agent group v3
write-view hardy notify-view hardy
huawei(config)#snmp-agent mib-view
v3 user1 group1
privacy-mode aes128 prikey123
group1 privacy read-view hardy
hardy include internet
NOTE
AES128 is recommended because it has higher security than DES56.
ii.
(Optional) Set the ID and contact means of the administrator.


iv.
(Optional) Configure the engine ID of the SNMP entity.

The engine ID of the SNMP entity is set to 0123456789.
NOTE
The context engine ID of the SNMP must be the same as that on the U2000.
huawei(config)#snmp-agent local-engineid 0123456789
v.

NOTE
d.

U2000.
e.

The host name is huawei, the IP address of the host is 10.10.1.10/24 (IP address of
the U2000), the trap parameter name is ABC, the SNMP version is V3, the
parameter security name is user1 (when the SNMP V3 is used, the parameter
security name is the USM user name), and the traps are authenticated and
encrypted.
huawei(config)#snmp-agent target-host trap-hostname huawei
address 10.10.1.10 trap-paramsname ABC
ABC v3 securityname user1 privacy
f.
Set the IP address of the maintenance Ethernet port as the source IP address for
sending traps.
Set the SNMP packets to be forwarded from the maintenance Ethernet port of the
MA5600T/MA5603T/MA5608T. That is, the source address of the traps is meth 0.
huawei(config)#snmp-agent trap source meth 0
g.
Save the data.

huawei(config)#save
Commission the outband network management on the U2000.

a.
Issue 01 (2016-04-29)
Configure the gateway of the route from the U2000 server to network segment
10.50.1.0/24 to 10.10.1.1.
144

Access Module
n
1 Commissioning

table.

route.
routing table.
NOTE
When the IP address of the network management port and the IP address of the U2000 are in
the same network segment, you need not configure the routing information.
b.

i.

ii.
Choose SNMP v3 Parameter on the Default Access Protocol Parameters

tab page. Then click Add and set the SNMP parameters, as shown in Figure
1-57.
After selecting corresponding protocols in Priv Protocol and Auth Protocol,

click
next to the parameter, and set the passwords of data encryption
protocol and authentication protocol, as shown in Figure 1-58.
Figure 1-58 Set the password
Issue 01 (2016-04-29)

145

Access Module
1 Commissioning
NOTE
NE User, Context Engine ID, Priv Protocol and password, and Auth Protocol and
password must be the same as those configured on the MA5600T/MA5603T/
MA5608T. You can run the display snmp-agent usm-user command to query the
device user, data encryption protocol, and authentication protocol on the MA5600T/
MA5603T/MA5608T and run the display snmp-agent local-engineid command to
query the context engine ID on the MA5600T/MA5603T/MA5608T.
iii. Click OK.

iv.
v.
click OK.
c.
Add a device.
i.
ii.
main menu.
iii. In the dialog box that is displayed, set the required parameters, as shown in
Figure 1-59.
IP address is 10.50.1.10, Device Name is huawei, SNMP Parameters is
SNMP V3:default.
d.
Click OK. The system prompts a message indicating that several seconds or some
10 minutes are required for uploading the device data. After the related data is read,
the system automatically refreshes and displays the device icon.
----End
Issue 01 (2016-04-29)

146

Access Module
1 Commissioning
Result
You can maintain and manage the MA5600T/MA5603T/MA5608T through the U2000.
Configuration File
the device.
interface meth 0
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent usm-user v3 user1 group1 authentication-mode sha authkey123 privacymode aes128 prikey123
snmp-agent group v3 group1 privacy read-view hardy write-view hardy notify-view
hardy
snmp-agent mib-view hardy include internet
snmp-agent target-host trap-paramsname ABC v3 securityname user1 privacy
save
Commissioning Inband Management (SNMP V1 and V2)

This topic describes how to implement the inband network management on the MA5600T/
MA5603T/MA5608T through the upstream port (inband network management port). This
enables the U2000 to maintain the MA5600T/MA5603T/MA5608T through this management
channel. In the inband network management mode, the service channel of the device is used
to transmit the management information. The network is flexible and requires no additional
devices, which helps save the cost for carriers. This network, however, is difficult to maintain.
l
The MA5600T/MA5603T/MA5608T provides the inband network management through

the upstream port.
The upstream port of the GIU board on the MA5600T/MA5603T/MA5608T is used as

the inband network management port.
Figure 1-60 Example network for the inband network management

=
Issue 01 (2016-04-29)

147

Access Module
Access node
VLAN:1000
10.50.1.10/24
Router
10.50.1.1/24
1 Commissioning
U2000
10.10.1.10/24
Figure 1-61 shows the flowchart for commissioning the inband network management.
Figure 1-61 Flowchart for commissioning the inband network management
Procedure
l
Commission the inband network management on the device.

a.
Configure the IP address of the inband network management port.

The upstream port (inband network management port) is 0/19/0, the VLAN ID is
1000, the VLAN type is standard VLAN, and the IP address is 10.50.1.10/24.
Issue 01 (2016-04-29)

148

Access Module
1 Commissioning
huawei(config-if-vlanif1000)#ip address 10.50.1.10 255.255.255.0

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.
b.
Add a route for the inband network management.

c.

i.

The read community name is public123, and the write community name is
private123.
NOTE
The configurations of the read community name and the write community name must
be the same as the configurations on the U2000.
huawei(config)#snmp-agent community read public123
huawei(config)#snmp-agent community write private123
ii.
(Optional) Set the ID and the contact means of the administrator.


iv.


NOTE
d.

U2000.
e.

n
10.10.1.10
trap-paramsname ABC
ABC v1 securityname private
Issue 01 (2016-04-29)
149

Access Module
1 Commissioning
10.10.1.10 trap-paramsname ABC
huawei(config)#snmp-agent target-host trap-paramsname ABC
v2c securityname private
f.
Configure the IP address of the VLAN interface as the source address for sending
traps.
Enable the forwarding of the SNMP packets from the L3 interface of VLAN 1000
of the MA5600T/MA5603T/MA5608T.
huawei(config)#snmp-agent trap source vlanif 1000
g.
Save the data.

huawei(config)#save
Commission the inband network management on the U2000.

a.
Configure the gateway of the route from the U2000 to network segment
10.50.1.0/24 to 10.10.1.1.
n

table.

route.
routing table.
NOTE
If the IP address of the outband network management port and the IP address of the U2000
are in the same network segment, you need not configure the routing information.
b.
c.
Set the SNMP parameters. A default SNMP profile exists in the system. Use the
default profile in this service. If a new profile is required, do as follows:
i.

ii.

Issue 01 (2016-04-29)

150

Access Module
1 Commissioning

NOTE
The configurations of Get Community and Set Community are the same as the
configurations on the MA5600T/MA5603T/MA5608T.
iii. Click OK.

iv.
v.
click OK.
d.
Add a device.
i.
ii.
main menu.
iii. In the right pane, set the parameters.
Issue 01 (2016-04-29)

151

Access Module
1 Commissioning
Issue 01 (2016-04-29)

152

Access Module
iv.
1 Commissioning
Click OK. The system displays a message indicating that several seconds or
some 10 minutes are required for uploading the device data. After the related
data is read, the system automatically refreshes and displays the device icon.
----End
Result
Configuration File
The following describes the script for commissioning the inband network management on the
device (SNMP V1).
vlan 1000 standard
port vlan 1000 0/19 0
interface vlanif 1000
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent target-host trap-paramsname ABC v1 securityname private
snmp-agent trap source vlanif 1000
save
device (SNMP V2).
vlan 1000 standard
port vlan 1000 0/19 0
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent sys-info version v2c
snmp-agent target-host trap-paramsname ABC v2c securityname private
save
Issue 01 (2016-04-29)

153

Access Module
1 Commissioning
Commissioning Inband Network Management (SNMP V3)

This topic describes how to implement the inband network management on the MA5600T/
MA5603T/MA5608T through the upstream port (inband network management port). This
enables the U2000 to maintain the MA5600T/MA5603T/MA5608T through this management
channel. In the inband network management mode, the service channel of the device is used
to transmit the management information. The network is flexible and requires no additional
devices, which helps save the cost for carriers. This network, however, is difficult to maintain.
l
The MA5600T/MA5603T/MA5608T provides the inband network management through

the upstream port.
The upstream port of the GIU board on the MA5600T/MA5603T/MA5608T is used as

the inband network management port.
SNMP V3 is used (more reliable than V1 and V2, providing network security and access
control management functions).
Figure 1-66 Example network for the inband network management

=
Access node
VLAN:1000
10.50.1.10/24
Router
10.50.1.1/24
U2000
10.10.1.10/24
Figure 1-67 shows the flowchart for commissioning the inband network management.
Issue 01 (2016-04-29)

154

Access Module
1 Commissioning
Figure 1-67 Flowchart for commissioning the inband network management
Procedure
l
Commission the inband network management on the device.

a.
Configure the IP address of the inband network management port.

The upstream port (inband network management port) is 0/19/0, the VLAN ID is
1000, the VLAN type is standard VLAN, and the IP address is 10.50.1.10/24.
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.
b.
Add a route for the inband network management.

Issue 01 (2016-04-29)
c.
d.

155

Access Module
i.
1 Commissioning
Configure the SNMP user, group, and view.

The user name is user1, the group name is group1, the user authentication
mode is SHA, the authentication password is authkey123, the user encryption
mode is aes128, the encryption password is prikey123, the read, write and
notify view names are hardy, and the view includes the internet subtree.
huawei(config)#snmp-agent usm-user
authentication-mode sha authkey123
huawei(config)#snmp-agent group v3
write-view hardy notify-view hardy
huawei(config)#snmp-agent mib-view
v3 user1 group1
privacy-mode aes128 prikey123
group1 privacy read-view hardy
hardy include internet
NOTE
AES128 is recommended because it has higher security than DES56.
ii.
(Optional) Set the ID and contact means of the administrator.


iv.
(Optional) Configure the engine ID of the SNMP entity.

The engine ID of the SNMP entity is set to 0123456789.
NOTE
The context engine ID of the SNMP must be the same as that on the U2000.
huawei(config)#snmp-agent local-engineid 0123456789
v.

NOTE
e.

U2000.
f.

The host name is huawei, the IP address of the host is 10.10.1.10/24 (IP address of
the U2000), the trap parameter name is ABC, the SNMP version is V3, the
parameter security name is user1 (when the SNMP V3 is used, the parameter
security name is the USM user name), and the traps are authenticated and
encrypted.
huawei(config)#snmp-agent target-host trap-hostname huawei
address 10.10.1.10 trap-paramsname ABC
ABC v3 securityname user1 privacy
g.
Configure the IP address of the VLAN interface as the source address for sending
traps.
Enable the forwarding of the SNMP packets from the L3 interface of VLAN 1000
of the MA5600T/MA5603T/MA5608T.
h.
Save the data.

huawei(config)#save
Issue 01 (2016-04-29)

156

Access Module
1 Commissioning
Commission the inband network management on the U2000.

a.
Configure the gateway of the route from the U2000 server to network segment
10.50.1.0/24 to 10.10.1.1.
n

table.

route.
routing table.
NOTE
When the IP address of the network management port and the IP address of the U2000 are in
the same network segment, you need not configure the routing information.
b.

i.

ii.
Choose SNMP v3 Parameter on the Default Access Protocol Parameters

tab page. Then click Add and set the SNMP parameters, as shown in Figure
1-68.
After selecting corresponding protocols in Priv Protocol and Auth Protocol,

next to the parameter, and set the passwords of data encryption
click
protocol and authentication protocol, as shown in Figure 1-69.
Issue 01 (2016-04-29)

157

Access Module
1 Commissioning
Figure 1-69 Set the password
NOTE
NE User, Context Engine ID, Priv Protocol and password, and Auth Protocol and
password must be the same as those configured on the MA5600T/MA5603T/
MA5608T. You can run the display snmp-agent usm-user command to query the
device user, data encryption protocol, and authentication protocol on the MA5600T/
MA5603T/MA5608T and run the display snmp-agent local-engineid command to
query the context engine ID on the MA5600T/MA5603T/MA5608T.
iii. Click OK.

iv.
v.
click OK.
c.
Add a device.
i.
ii.
main menu.
iii. In the dialog box that is displayed, set the required parameters, as shown in
Figure 1-70.
IP address is 10.50.1.10, Device Name is huawei, SNMP Parameters is
SNMP V3:default.
Issue 01 (2016-04-29)

158

Access Module
1 Commissioning
d.
Click OK. The system prompts a message indicating that several seconds or some
10 minutes are required for uploading the device data. After the related data is read,
the system automatically refreshes and displays the device icon.
----End
Result
Configuration File
device.
vlan 1000 standard
port vlan 1000 0/19 0
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
snmp-agent usm-user v3 user1 group1 authentication-mode sha authkey123 privacymode aes128 prikey123
snmp-agent group v3 group1 privacy read-view hardy write-view hardy notify-view
hardy
snmp-agent mib-view hardy include internet
Issue 01 (2016-04-29)

159

Access Module
1 Commissioning

snmp-agent target-host trap-paramsname ABC v3 securityname user1 privacy
save
1.4.2 Commissioning the Interconnection with the Router

This topic describes how to check whether the MA5600T/MA5603T/MA5608T can normally
communicate with the router and whether the MA5600T/MA5603T/MA5608T can access the
upper-layer device through the router.
l
The MA5600T/MA5603T/MA5608T uses the GIU board for upstream transmission.
By interconnecting with the router, the MA5600T/MA5603T/MA5608T can be

interconnected with the upper-layer device through configuring a static route on the
MA5600T/MA5603T/MA5608T.
NOTE
For details about how to configure a router, see the related configuration guide.
Figure 1-71 Example network for commissioning the interconnection with the router
PC
10.10.1.12/24
LAN
Router
10.50.1.1/24
Access node
VLAN:2
10.50.1.10/24
PC
PC
Procedure
Step 1 Configure a VLAN.
The VLAN ID is 2, and the VLAN type is smart VLAN.
huawei(config)#vlan 2 smart
Step 2 Add an upstream port to the VLAN.

Upstream port 0/19/0 is added to VLAN 2.
NOTE
Step 3 Configure the IP address of the L3 interface.

Issue 01 (2016-04-29)

160

Access Module
1 Commissioning
The L3 interface IP address is 10.50.1.10/24, and this IP address must be in the same network
segment as the gateway IP address (IP address of the router port that is connected to the
MA5600T/MA5603T/MA5608T).
Step 4 Add a static route.

The destination IP address is 10.10.1.0/24, and the next-hop IP address is gateway IP address
10.50.1.1.

huawei(config)#save
----End
Result
After the MA5600T/MA5603T/MA5608T is interconnected with the router successfully, you
can ping IP address 10.10.1.12 from the MA5600T/MA5603T/MA5608T.
Configuration File
vlan 2 smart
port vlan 2 0/19 0
interface vlanif 2
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
save
1.4.3 Commissioning the Interconnection with the BRAS

This topic describes how to check whether the MA5600T/MA5603T/MA5608T can normally
communicate with the BRAS. Working with the BRAS, the MA5600T/MA5603T/MA5608T
can implement the authentication, accounting, and authorization (AAA) service.
l
The MA5600T/MA5603T/MA5608T uses the GIU board for upstream transmission.
A static route is configured on the MA5600T/MA5603T/MA5608T for communicating

with the BRAS.
The requirements on the BRAS are as follows:
Issue 01 (2016-04-29)
According to the authentication and accounting requirements for the users, you
need to perform related configurations on the BRAS. 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.
If the BRAS is used to authenticate users, you need to configure the user name and
the password for each user on the BRAS. If the BRAS is used to allocate IP
addresses, you must configure the corresponding IP address pool on the BRAS.
161

Access Module
1 Commissioning
NOTE
For details about how to configure a LAN switch or the BRAS, see related configuration guides.
Figure 1-72 Example network for commissioning the interconnection with the BRAS
Procedure

Upstream port 0/19/0 is added to VLAN 2.
NOTE
Step 3 Configure the IP address of the L3 interface.

The L3 interface IP address is 10.50.1.10/24, and this IP address must be in the same network
segment as the gateway IP address (IP address of the router port that is connected to the
MA5600T/MA5603T/MA5608T).
Step 4 Add a static route.

The destination IP address is 10.10.1.0/24 (the network segment of the BRAS), and the nexthop IP address is gateway IP address 10.50.1.1.

huawei(config)#save
----End
Result
After the MA5600T/MA5603T/MA5608T is interconnected with the BRAS successfully, you
can ping IP address 10.10.1.1 from the MA5600T/MA5603T/MA5608T. After services are
configured on the MA5600T/MA5603T/MA5608T, the authentication and accounting
functions of the BRAS can be implemented.
Configuration File
vlan 2 smart
port vlan 2 0/19 0
Issue 01 (2016-04-29)

162

Access Module
1 Commissioning
interface vlanif 2
ip address 10.50.1.10 255.255.255.0
quit
ip route-static 10.10.1.0 24 10.50.1.1
save
1.4.4 Interconnection Commissioning of the MG Interface

The MG interface is a communication interface between the MA5600T/MA5603T/MA5608T
and the MGC. Based on different control protocols between the MA5600T/MA5603T/
MA5608T and the MGC, the MG interface can adopt the H.248 protocol or the MGCP
protocol. The communication between the MA5600T/MA5603T/MA5608T and the MGC can
be in the normal state and the services and functions can be implemented, only when the MG
interface is in the normal state. This topic describes how to commission the interconnection
between the MA5600T/MA5603T/MA5608T and the MGC.
Commissioning the Interconnection with the MG Interface(H.248)

This topic describes how to check whether the MG interface can normally communicate with
the MGC through the H.248 protocol.
l
The MA5600T/MA5603T/MA5608T uses the H.248 protocol.
The media IP address is the same as the signaling IP address, and the media stream and
the signaling stream are transmitted upstream through the same Ethernet port on the GIU
board.
The media stream and the signaling stream use the default QoS policy for upstream
transmission.
Various terminals connected to the MG interface use the default TID profile, and the
software parameters of the MG interface use the default settings.
The MGC identifies the MG through the signaling IP address (IP address of the MG
interface), and their communication packets do not contain any VLAN tag.
Figure 1-73 Example network for commissioning the interconnection with the MG interface
(H.248)
Access node
H.248
Phone
VLAN:50
10.50.1.10/24
Router
10.50.1.1/24
MGC
10.10.1.4/24
Figure 1-74 shows the flowchart for commissioning the interconnection with the MG
interface (H.248).
Issue 01 (2016-04-29)

163

Access Module
1 Commissioning
Figure 1-74 Flowchart for commissioning the interconnection with the MG interface(H.248)
Prerequisites
l
The data configuration on the MGC side (corresponding to the data configuration on the
MG side) must be correct.
The current system must use the H.248 protocol.

NOTE
Run the display protocol support command to query the current voice protocol. If the voice
protocol is not H.248, run the protocol support h248 command to change it to H.248.
Procedure
Step 1 Configure the upstream VLAN interface for the media stream and the signaling stream.
The VLAN ID is 50, the VLAN type is smart VLAN, the upstream port is 0/19/0, and the IP
address of the VLAN interface is 10.50.1.10/24.
NOTE
Issue 01 (2016-04-29)

164

Access Module
1 Commissioning
Step 2 Configure the media and signaling IP address pools.

The media and signaling IP addresses are 10.50.1.10/24, and the gateway IP address is
10.50.1.1.
huawei(config)#voip
huawei(config-voip)#ip address media 10.50.1.10 10.50.1.1
huawei(config-voip)#ip address signaling 10.50.1.10
huawei(config-voip)#quit
NOTE
When configuring the MG interface attributes, ensure that the media and signaling IP addresses exist in
the corresponding address pools.
Step 3 Configure a static route to the MGC.

The IP address of the destination network segment of the static route to the MGC is
10.10.1.0/24, and the gateway IP address is 10.50.1.1.
huawei(config)#ip route-static 10.10.1.0 255.255.255.0 10.50.1.1
Step 4 Add an MG interface.

MG interface 0 that supports the H.248 protocol is added.
huawei(config)#interface h248 0
Are you sure to add MG interface?(y/n)[n]:y
Step 5 Configure the attributes of the MG interface.

The media and signaling IP addresses of the MG interface are 10.50.1.10/24, the MG port ID
is 2944, the coding mode is text, the transmission mode is UDP, the MG domain name is
MA5600T/MA5603T/MA5608T.com, the IP address of the primary MGC is 10.10.1.4/24, the
MGC port ID is 2944, and the start negotiation version of the H.248 is V2.
huawei(config-if-h248-0)#if-h248 attribute mgip 10.50.1.10 mgport 2944 code text
transfer udp domainName
MA5600T/MA5603T/MA5608T.com primary-mgc-ip1 10.14.1.4 primary-mgc-port 2944 mgmedia-ip1 10.50.1.10 start-negotiate-version 2
NOTE
The start negotiation version of the H.248 protocol for the MG interface must be the same as that on the
MGC side.
Step 6 Reset the MG interface.

The MG interface is reset through cold start.
huawei(config-if-h248-0)#reset coldstart
Are you sure to reset MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#quit

huawei(config)#save
----End
Result
After the MG is interconnected with the MGC successfully, you can run the display if-h248
all command to confirm that the MG interface is in the normal state.
huawei(config)#display if-h248 all
------------------------------------------------------------------------MGID
TransMode State
MGPort MGIP/DomainName MGCPort MGCIP/DomainName
------------------------------------------------------------------------0
UDP
Normal
2944
10.50.1.10
2944
10.10.1.4
-------------------------------------------------------------------------
Issue 01 (2016-04-29)

165

Access Module
1 Commissioning
Configuration File
vlan 50 smart
port vlan 50 0/19 0
interface vlanif 50
ip address 10.50.1.10 24
quit
voip
ip address media 10.50.1.10 10.50.1.1
ip address signaling 10.50.1.10
quit
ip route-static 10.10.1.0 255.255.255.0 10.50.1.1
interface h248 0
y
if-h248 attribute mgip 10.50.1.10 mgport 2944 code text transfer udp domainName
MA5600T/MA5603T/MA5608T.com primary-mgc-ip1 10.14.1.4 primary-mgc-port 2944 mgmedia-ip1 10.50.1.10 start-negotiate-version 2
reset coldstart
y
quit
save
Commissioning the Interconnection with the MG Interface (MGCP)

This topic describes how to check whether the MG interface can normally communicate with
the MGC through the MGCP protocol.
l
The MA5600T/MA5603T/MA5608T uses the MGCP protocol.
The media IP address is the same as the signaling IP address (when the MGCP protocol
is used, the media IP address must be the same as the signaling IP address), and the
media stream and the signaling stream use the same Ethernet port on the GIU board for
transmission.
Various terminals connected to the MG interface use the default TID profile, and the
software parameters of the MG interface use the default settings.
The MGC identifies the MG through the signaling IP address (IP address of the MG
interface), and their communication packets do not contain any VLAN tag.
Figure 1-75 Example network for the commissioning the interconnection with the MG
interface (MGCP)
Acdess node
MGCP
Phone
Issue 01 (2016-04-29)
VLAN:50
10.50.1.10/24
Router
10.50.1.1/24

MGC
10.10.1.4/24
166

Access Module
1 Commissioning
Figure 1-76 shows the flowchart for commissioning the interconnection with the MG
interface (MGCP).
Figure 1-76 Flowchart for commissioning the interconnection with the MG interface (MGCP)
Prerequisites
l
The data configuration on the MGC side (corresponding to the data configuration on the
MG side) must be correct.
The current system must use the MGCP protocol.

NOTE
protocol is not MGCP, run the protocol support mgcp command to change it to MGCP.
Procedure
The VLAN ID is 50, the VLAN type is smart VLAN, and the upstream port is 0/19/0, and the
IP address of the VLAN interface is 10.50.1.10/24.
Issue 01 (2016-04-29)

167

Access Module
1 Commissioning

NOTE

10.50.1.1.
huawei(config)#voip
NOTE
When configuring the MG interface attributes, ensure that the media and signaling IP addresses exist in
Step 3 Configure a static route to the MGC.

The IP address of the destination network segment of the static route to the MGC is

MG interface 0 that supports the MGCP protocol is added.
huawei(config)#interface mgcp 0

The IP addresses of the MG interface is 10.50.1.10/24, the MG port ID is 2727, the coding
mode is text (default setting), the transmission mode is UDP (default setting), the MG domain
name is MA5600T/MA5603T/MA5608T.com, the IP address of the primary MGC is
10.10.1.4/24, and the MGC port ID is 2727.
huawei(config-if-mgcp-0)#if-mgcp attribute mgip 10.50.1.10 mgport 2727 domainName
MA5600T/MA5603T/MA5608T.com mgcip_1 10.10.1.4 mgcport_1 2727

huawei(config-if-mgcp-0)#reset
huawei(config-if-mgcp-0)#quit

huawei(config)#save
----End
Result
After the MG is interconnected with the MGC successfully, you can run the display if-mgcp
all command to confirm that the MG interface is in the normal state.
huawei(config)#display if-mgcp all
-------------------------------------------------------------------------MGID
State
MGPort MGIP
MGCPort MGCIP/DomainName
-------------------------------------------------------------------------0
Normal
2727
10.50.1.10
2727
10.14.1.4
--------------------------------------------------------------------------
Issue 01 (2016-04-29)

168

Access Module
1 Commissioning
Configuration File
vlan 50 smart
port vlan 50 0/19 0
interface vlanif 50
ip address 10.50.1.10 24
quit
voip
ip address media 10.50.1.10 10.50.1.1
quit
ip route-static 10.10.1.0 255.255.255.0 10.50.1.1
interface mgcp 0
y
if-mgcp attribute mgip 10.50.1.10 mgport 2727 domainName MA5600T/MA5603T/
MA5608T.com mgcip_1 10.14.1.4 mgcport_1 2727
reset
y
quit
save
1.4.5 Commissioning the Interconnection with the SIP Interface

This topic describes how to check whether the SIP interface can normally communicate with
the IP multimedia subsystem (IMS) through the SIP protocol.
l
The MA5600T/MA5603T/MA5608T uses the SIP protocol.
The media IP address is the same as the signaling IP address, and the media stream and
the signaling stream are transmitted upstream through the same Ethernet port on the GIU
board.
transmission.
The IMS identifies the SIP interface through the signaling IP address (IP address of the
SIP interface), and their communication packets do not contain any VLAN tag.
Figure 1-77 Example network for commissioning the interconnection with the SIP interface
Access node
SIP
Phone
VLAN:50
10.50.1.10/24
Router
10.50.1.1/24
IMS
IP1:10.10.1.1/24
IP2:10.10.1.2/24
Figure 1-78 shows the flowchart for commissioning the interconnection with the SIP
interface.
Issue 01 (2016-04-29)

169

Access Module
1 Commissioning
Figure 1-78 Flowchart for commissioning the interconnection with the SIP interface
Prerequisites
l
The data configuration on the IMS side (corresponding to the data configuration on the
MA5600T/MA5603T/MA5608T side) must be correct.
The current system must use the SIP protocol.

NOTE
protocol is not SIP, run the protocol support sip command to change it to SIP.
Procedure
The VLAN ID is 50, the VLAN type is smart VLAN, the upstream port is 0/19/0, and the IP
address of the VLAN interface is 10.50.1.10/24.
NOTE

10.50.1.1.
Issue 01 (2016-04-29)

170

Access Module
1 Commissioning
huawei(config)#voip
NOTE
When configuring the SIP interface attributes, ensure that the media and signaling IP addresses exist in
Step 3 Configure a static route to the IMS.

The IP address of the destination network segment of the static route to the IMS is
Step 4 Add a SIP interface.

SIP interface 0 is added.
huawei(config)#interface sip 0
Are you sure to add the SIP interface?(y/n)[n]:y
Step 5 Configure the basic attributes of the SIP interface.

The media and signaling IP addresses of the SIP interface are 10.50.1.10/24, the signaling
port ID is 5555, the transmission protocol is UDP (default setting), the IP address 1 of the
primary proxy server is 10.10.1.1/24, the port ID of the primary proxy server is 5555, the IP
address 1 of the secondary proxy server is 10.10.1.2/24, the port ID of the secondary proxy
server is 5555, the home domain name is MA5600T/MA5603T/MA5608T.com, and the
profile index is 0.
huawei(config-if-sip-0)#if-sip attribute basic media-ip 10.50.1.10 signal-ip
10.50.1.10 signal-port 5555 transfer udp primary-proxy-ip1 10.10.1.1 primaryproxy-port 5555
secondary-proxy-ip1 10.10.1.2 secondary-proxy-port 5555 home-domain MA5600T/
MA5603T/MA5608T.com sipprofile-index 0
Step 6 Configure the optional attributes of the SIP interface.

The domain name of the SIP interface is huawei.com, and the phone context is +86755.
huawei(config-if-sip-0)#if-sip attribute optional mg-domain huawei.com phonecontext +86755
Step 7 Reset the SIP interface.

huawei(config-if-sip-0)#reset
Are you sure to reset SIP interface?(y/n)[n]:y
huawei(config-if-sip-0)#quit

huawei(config)#save
----End
Result
After the SIP interface is interconnected with the IMS successfully, you can run the display
if-sip all command to confirm that the SIP interface is in the normal state.
huawei(config)#display if-sip all
-------------------------------------------------------MGID
TransMode State
SignalPort SignalIP
-------------------------------------------------------0
UDP
Normal
5555
10.50.1.10
--------------------------------------------------------
Issue 01 (2016-04-29)

171

Access Module
1 Commissioning
Configuration File
vlan 50 smart
port vlan 50 0/19 0
interface vlanif 50
ip address 10.50.1.10 24
quit
voip
ip address media 10.50.1.10 10.50.1.1
quit
ip route-static 10.10.1.0 255.255.255.0 10.50.1.1
interface sip 0
y
if-sip attribute basic media-ip 10.50.1.10 signal-ip
10.50.1.10 signal-port 5555 transfer udp primary-proxy-ip1 10.10.1.1 primaryproxy-port 5555
secondary-proxy-ip1 10.10.1.2 secondary-proxy-port 5555 home-domain MA5600T/
MA5603T/MA5608T.com sipprofile-index 0
if-sip attribute optional mg-domain huawei.com phone-context +86755
reset
y
quit
save
1.4.6 Commissioning the Management Channel Between the OLT

and the GPON MDU
This topic describes how to commission the management channel between the MA5600T/
MA5603T/MA5608T and the GPON MDU to ensure that you can log in to the GPON MDU
using the MA5600T/MA5603T/MA5608T at the CO to remotely maintain and manage the
GPON MDU.
l
A GPON port on the MA5600T/MA5603T/MA5608T is connected to 128 MDUs using

an optical splitter.
NOTE
The following considers MDU 0 as an example for commissioning the management channel
between the OLT and the GPON MDU.
After the management channel between the MA5600T/MA5603T/MA5608T and the

GPON MDU is set up, you can log in to the MDU using port 0/2/0 connected to the
MDU to remotely maintain and manage the MDU.
The DBA profile is used to limit the user rate to the fixed 10 Mbit/s bandwidth.
Issue 01 (2016-04-29)

172

Access Module
1 Commissioning
Figure 1-79 Example network for commissioning the management channel between the OLT
and the GPON MDU
BRAS
LSW
Access node
VLAN: 20
192.168.1.100/24
Optical
splitter
192.168.1.200/24
MDU
PC
Figure 1-80 shows the flowchart for commissioning the management channel between the
OLT and the GPON MDU.
Issue 01 (2016-04-29)

173

Access Module
1 Commissioning
Figure 1-80 Flowchart for commissioning the management channel between the OLT and the
GPON MDU
Procedure
Step 1 Create a VLAN.
Issue 01 (2016-04-29)

174

Access Module
1 Commissioning

Upstream port 0/19/0 on the GIU board is added to VLAN 20.
Step 3 Configure the IP address of the Layer 3 interface.

The Layer 3 IP address is 192.168.1.100/24.
Step 4 Add a DBA profile.

The DBA profile ID is 12, the DBA profile uses the default name DBA-profile_12, the
bandwidth type is type1 (fixed bandwidth), and the user rate is the fixed 10 Mbit/s bandwidth.
NOTE
l The bandwidth type and the attribute of the DBA profile must be compatible with the service to be
carried.
l The system supports five DBA profile types, namely, type1 (fixed bandwidth), type2 (assured
bandwidth), type3 (assured bandwidth+maximum bandwidth), type4 (maximum bandwidth), and
type5 (fixed bandwidth+assured bandwidth+maximum bandwidth).
l By default, the system provides DBA profiles 1 to 9, each of which provides typical values for
traffic parameters. By default, T-CONT 0 is bound with DBA profile 1.
l The value of the bandwidth you input when adding the DBA profile rounds down to the nearest
integer multiple of 64. For example, if the input bandwidth value is 1022 kbit/s, the actual
bandwidth is 960 kbit/s.
l You can run the display dba-profile command to query the information about the DBA profile.
huawei(config)#dba-profile add profile-id 12 type1 fix 10240
Step 5 Configure an MDU line profile.

The MDU line profile ID is 5, T-CONT 1 is bound with DBA profile 12, GEM port 0 is
bound to T-CONT 1, the service type is ETH, and the mapping mode is VLAN mapping.
huawei(config)#ont-lineprofile gpon profile-id 5
huawei(config-gpon-lineprofile-5)#tcont 1 dba-profile-id 12
huawei(config-gpon-lineprofile-5)#gem add 0 eth tcont 1
huawei(config-gpon-lineprofile-5)#gem mapping 0 0 vlan 20
huawei(config-gpon-lineprofile-5)#commit
huawei(config-gpon-lineprofile-5)#quit
Step 6 Add an MDU.

MDU 0 is connected to GPON port 0, the MDU authentication mode is the SN authentication,
the SN is 32303131B39FD641, the management protocol is SNMP, and MDU profile 5 is
bound to MDU 0.
NOTE
You can add an MDU in the following two ways: confirming an auto-discovered MDU and adding an
MDU offline. Here, the method of adding an MDU offline is considered as an example.
You can also run the port ont-auto-find command to enable the function of auto-discovering an MDU,
and then run the ont confirm command to confirm the auto-discovered MDU.
huawei(config)#interface gpon 0/2
huawei(config-if-gpon-0/2)#ont add 0 0 sn-auth 32303131B39FD641 snmp ontlineprofile-id 5
Step 7 Configure the management IP address of the MDU.

The management IP address is 192.168.1.200/24, and the ID of the native VLAN to which the
MDU port belongs is 20.
Issue 01 (2016-04-29)

175

Access Module
1 Commissioning
huawei(config-if-gpon-0/2)#ont ipconfig 0 0 static ip-address 192.168.1.200 mask

255.255.255.0 vlan 20
huawei(config-if-gpon-0/2)#quit
Step 8 Set the SNMP parameters.

Configure the SNMP profile 10. That, the SNMP version is SNMP V2C, the read community
name is public, and the write community name is private, the IP address of the U2000 is
10.10.1.10/24, the port is 162, the parameter security name is user1 (the parameter security
name is the write community name), the gateway IP address is 192.168.1.101.
huawei(config)#snmp-profile add profile-id 10 v2c public
private 10.10.1.10 162 private
huawei(config-if-gpon-0/2)#ont snmp-profile 0 0 profile-id 10
huawei(config-if-gpon-0/2)#ont snmp-route 0 0 ip-address 10.10.1.10 mask
255.255.255.0 next-hop 192.168.1.101
Step 9 Add a service port to the VLAN.

huawei(config)#service-port vlan 20 gpon 0/2/0 ont 0 gemport 0 multi-service uservlan 20

huawei(config)#save
----End
Result
After the commissioning is complete, you can remotely maintain and manage the MDU using
telnet 192.168.1.200.
Configuration File
vlan 20 smart
port vlan 20 0/19 0
interface vlanif 20
ip address 192.168.1.100 255.255.255.0
quit
dba-profile add profile-id 12 type1 fix 10240
ont-lineprofile gpon profile-id 5
tcont 1 dba-profile-id 12
gem add 0 eth tcont 1
gem mapping 0 0 vlan 20
commit
quit
interface gpon 0/2
ont add 0 0 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 5
ont ipconfig 0 0 static ip-address 192.168.1.200 mask 255.255.255.0 vlan 20
quit
snmp-profile add profile-id 10 v2c public private 10.10.1.10 162 private
interface gpon 0/2
ont snmp-profile 0 0 profile-id 10
ont snmp-route 0 0 ip-address 10.10.1.10 mask 255.255.255.0 next-hop 192.168.1.101
quit
service-port vlan 20 gpon 0/2/0 ont 0 gemport 0 multi-service user-vlan 20
save
Issue 01 (2016-04-29)

176

Access Module
1 Commissioning
1.4.7 Commissioning the Management Channel Between the OLT

and the GPON ONT
This topic describes how to commission the GPON OLT to ensure that the service
configuration and centralized management of the GPON ONTs are performed on the GPON
OLT using the ONT Management and Control Interface (OMCI) protocol.
l
A GPON port on the MA5600T/MA5603T/MA5608T is connected to 128 ONTs using

an optical splitter.
NOTE
The following considers ONT 0 as an example for commissioning the management channel
between the OLT and the GPON ONT.
On the MA5600T/MA5603T/MA5608T, you can configure ONTs at different locations

in a centralized manner.
The DBA profile is used to limit the user rate to the fixed 10 Mbit/s bandwidth.
Figure 1-81 Example network for commissioning the management channel between the OLT
and the GPON ONT
BRAS
LSW
Access node
VLAN: 20
192.168.1.100/24
Splitter
192.168.1.200/24
ONT
PC
Issue 01 (2016-04-29)

177

Access Module
1 Commissioning
Figure 1-82 shows the flowchart for commissioning the management channel between the
OLT and the GPON ONT.
Figure 1-82 Flowchart for commissioning the management channel between the OLT and the
GPON ONT
Procedure
Step 1 Add a DBA profile.
The DBA profile ID is 12, the DBA profile uses the default name DBA-profile_12, the
bandwidth type is type1 (fixed bandwidth), and the user rate is the fixed 10 Mbit/s bandwidth.
NOTE
l The bandwidth type and the attribute of the DBA profile must be compatible with the service to be
carried.
l The system supports five DBA profile types, namely, type1 (fixed bandwidth), type2 (assured
bandwidth), type3 (assured bandwidth+maximum bandwidth), type4 (maximum bandwidth), and
type5 (fixed bandwidth+assured bandwidth+maximum bandwidth).
l By default, the system provides DBA profiles 1 to 9, each of which provides typical values for
traffic parameters. By default, T-CONT 0 is bound with DBA profile 1.
l The value of the bandwidth you input when adding the DBA profile rounds down to the nearest
integer multiple of 64. For example, if the input bandwidth value is 1022 kbit/s, the actual
bandwidth is 960 kbit/s.
l You can run the display dba-profile command to query the information about the DBA profile.
Issue 01 (2016-04-29)

178

Access Module
1 Commissioning
Step 2 Add an ONT line profile.

The ONT line profile ID is 5, T-CONT 1 is bound with DBA profile 12, GEM port 0 is bound
to T-CONT 1, the service type is ETH, and the mapping mode is VLAN mapping.
Step 3 Add an ONT service profile.

The ONT service profile ID is 10, the quantity of Ethernet ports on the ONT is 4, the quantity
of POTS ports on the ONT is 2, and Ethernet ports 1-4 are added to VLAN 20.
NOTE
The port capability set in the ONT service profile must be the same as the actual ONT capability set.
huawei(config)#ont-srvprofile gpon profile-id 10
huawei(config-gpon-srvprofile-10)#ont-port eth 4 pots 2
huawei(config-gpon-srvprofile-10)#port vlan eth 1-4 20
huawei(config-gpon-srvprofile-10)#commit
huawei(config-gpon-srvprofile-10)#quit
Step 4 Add an ONT.

ONT 0 is connected to GPON port 0, the ONT authentication mode is the SN authentication,
the SN is 323031314D4B2041, the management protocol is OMCI, and ONT line profile 5
and ONT service profile 10 are bound to ONT 0.
NOTE
You can add an ONT in the following two ways: confirming an auto-discovered ONT and adding an
ONT offline. Here, the method of adding an ONT offline is considered as an example.
You can also run the port ont-auto-find command to enable the function of auto-discovering an ONT,
and then run the ont confirm command to confirm the auto-discovered ONT.
huawei(config-if-gpon-0/2)#ont add 0 0 sn-auth 323031314D4B2041 omci ontlineprofile-id 5 ont-srvprofile-id 10

huawei(config)#save
----End
Result
After the commissioning is complete, you can maintain and manage the ONT on the
MA5600T/MA5603T/MA5608T (For example, run the ont deactivate command to
deactivate the ONT that is in the activated state).
Configuration File
vlan 20 smart
port vlan 20 0/19 0
interface vlanif 20
ip address 192.168.1.100 255.255.255.0
quit
dba-profile add profile-id 12 type1 fix 10240
Issue 01 (2016-04-29)

179

Access Module
1 Commissioning

tcont 1 dba-profile-id 12
gem add 0 eth tcont 1
commit
quit
interface gpon 0/2
ont add 0 0 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 5
quit
service-port vlan 20 gpon 0/2/0 ont 0 gemport 0 multi-service user-vlan 20
save
1.4.8 Commissioning the Management Channel to the xDSL CPE

This topic describes how to commission the CPE management function of the MA5600T/
MA5603T/MA5608T to ensure that you can log in to the CPE from the DSLAM at the CO to
remotely maintain and manage the CPE.
l
The maintenance terminal is connected to the maintenance Ethernet port of the

MA5600T/MA5603T/MA5608T.
After the management channel between the DSLAM and the CPE is set up, you can log
in to the CPE using port 0/2/0 connected to the CPE to remotely maintain and manage
the CPE.
The user access mode is IPoA.
Figure 1-83 Example network for managing the CPE
PC
Access node
VLAN:30
192.168.10.11/24
Modem
VPI:0 VCI:35
192.168.10.10/24
Figure 1-84 shows the flowchart for commissioning the management channel to the CPE.
Issue 01 (2016-04-29)

180

Access Module
1 Commissioning
Figure 1-84 Flowchart for commissioning the management channel to the CPE
Prerequisites
You must be logged in to the MA5600T/MA5603T/MA5608T using the maintenance
terminal.
Procedure
Step 1 Configure the management IP address of the CPE.
The management IP address of the CPE is 192.168.10.10/24.
huawei(config)#cpe-management ip-address 192.168.10.10
Step 2 Configure the management VLAN of the CPE.

The VLAN ID is 30, the VLAN type is smart VLAN, and the IP address of the VLAN L3
interface is 192.168.10.11/24.
huawei(config)#cpe-management vlan 30
Step 3 Configure the management VPI and VCI of the CPE.

The management VPI ID is 0, and the management VCI ID is 35.
huawei(config)#cpe-management vpi 0 vci 35
Step 4 Configure the management flow type of the CPE.

The management flow type is vlan-ethertype ipoe.
huawei(config)#cpe-management flow-type vlan-ethertype ipoe
Issue 01 (2016-04-29)

181

Access Module
1 Commissioning
Step 5 Configure IPoA.

Configure MAC address pool 0 with the start address 0000-0000-0001.
huawei(config)#mac-pool 0 0000-0000-0001
Enable the IPoA protocol conversion function.

huawei(config)#ipoa enable
Set the IPoA default gateway.

huawei(config)#ipoa default gateway 10.1.1.1
Step 6 Log in to the CPE.

huawei(config)#cpe-management telnet 0/2/0
----End
Result
You can log in to the CPE from the MA5600T/MA5603T/MA5608T using the maintenance
terminal to maintain and manage the CPE.
Configuration File
cpe-management ip-address 192.168.10.10
vlan 30 smart
cpe-management vlan 30
interface vlanif 30
ip address 192.168.10.11 24
quit
cpe-management vpi 0 vci 35
cpe-management flow-type vlan-ethertype ipoe
mac-pool 0 0000-0000-0001
ipoa enable
ipoa default gateway 10.1.1.1
cpe-management telnet 0/2/0
1.4.9 Configuring Triple-Plane Isolation

The MA5600T/MA5603T/MA5608T supports the configuration of triple-plane (the control
plane, user plane, and management plane) isolation to ensure system security.
The MA5600T/MA5603T/MA5608T can be configured to allow users to log in through the
service port to manage devices, which facilitates device management. When the device is
improperly configured, the device may be exposed to attacks. Attackers can attack the
management plane through the service port. To eliminate this risk, you are recommended to
configure triple-plane isolation to isolate the control plane, user plane, and management plane,
protecting the management plane from external attacks.
By default, the control plane, user plane, and management plane of the MA5600T/MA5603T/
MA5608T are isolated from each other.
The device supports out-of-band network management and in-band network management.
Out-of-band network management is recommended. In out-of-band network management, a
dedicated network management channel is used to manage the device. In this way, network
management data and service data are separated so that the management network is not
affected when the service network is faulty or when attacks are initiated from the service
network.
Issue 01 (2016-04-29)

182

Access Module
1 Commissioning
Configuring Three-Plane Isolation (Outband NMS)

Outband network management achieves triple-plane (management plane, control plane, and
user plane) isolation through configuration of the maintenance network port.
Procedure
Step 1 Configure the maintenance network port.
Set the IP address of the local maintenance Ethernet port (outband network management port)
of the MA5600T/MA5603T/MA5608T to 10.50.1.10 and the subnet mask to 255.255.255.0.
NOTE
----End
Configuring Three-Plane Isolation (VPN-Based Inband Network Management)

VPN-based inband network management achieves triple-plane (user plane, management
plane, and control plane) isolation through the VPN.
NOTE
After maintenance VPN is configured successfully, the server-end protocols such as Telnet (SSH, CLI),
SNMP and Trace receive only the connection requests from the user-specified management and maintenance
VPN network.
Procedure
Step 1 Create a VPN instance.
Create a VPN instance named huawei.
huawei(config)#ip vpn-instance huawei
Step 2 Configure VPN instance huawei as the system-level management and maintenance VPN
instance.
huawei(config)#sysman vpn-instance
{ vpn-instance-name<S><Length 1-31> }:huawei
Command:
sysman vpn-instance huawei
Step 3 Create a VLANIF interface and enter the VLANIF mode.

After VLAN 2 is created, create a VLANIF interface for VLAN 2 and enter the VLANIF
mode.
huawei(config)#interface vlanif
{ <1-4093> }:2
huawei(config-if-vlanif2)#
Step 4 Configure the IP address of the inband management interface.

Set the IP address of the inband management interface to 10.50.1.10 and subnet mask to
255.255.255.0.
Step 5 Bind the VPN instance.

Issue 01 (2016-04-29)

183

Access Module
1 Commissioning
Bind VPN instance huawei to the VLANIF interface of VLAN 2.

huawei(config-if-vlanif2)#ip binding vpn-instance huawei
----End
Configuring Triple-Plane Isolation (Public-Network-Based Inband Network

Management)
Public-network-based inband network management achieves triple-plane (management plane,
control plane, and user plane) isolation by prohibiting the service VLANIF interface from
sending management protocol packets.
Procedure
Step 1 Create a VLANIF interface and enter the VLANIF mode.
After VLAN 2 is created, create a VLANIF interface for VLAN 2 and enter the VLANIF
mode.
huawei(config)#interface vlanif
{ <1-4093> }:2
huawei(config-if-vlanif2)#
Step 2 Configure the IP address of the inband management interface.

Set the IP address of the inband management interface to 10.50.1.10 and subnet mask to
255.255.255.0.
Step 3 Configuring the firewall.

Create ACL 3000 and enable the firewall.
huawei(config)#acl 3000
huawei(config-acl-adv-3000)#rule deny tcp destination-port 23
TELNET protocol packets.
protocol packets.
protocol packets.
huawei(config-acl-adv-3000)#quit
huawei(config)#firewall enable
//Prohibit
//Prohibit SSH
//Prohibit SNMP
Step 4 Configure the firewall packet filtering rules for the service VLANIF interface.
NOTE
All service VLANIF interfaces must be configured with firewall packet filtering rules.
Configure the firewall packet filtering rules for the VLANIF interface of service VLAN 10.
huawei(config-if-vlanif10)#firewall packet-filter 3000 inbound
----End
1.5 Maintenance and Management Commissioning

Issue 01 (2016-04-29)

184

Access Module
1 Commissioning
1.5.1 Configuring the System Energy-Saving Function

This topic describes how to power off a board that is not configured with any services for a
long time to reduce the system power and therefore to reduce the system energy consumption.
Prerequisites
The board must support the power-off mode and the energy-saving mode.
Context
Energy-saving modes include the manual energy-saving mode and automatic energy-saving
mode.
l
Manual energy-saving mode (powering off a board manually). You can manually power
off an unused board in the subrack according to the plan for the energy-saving purpose.
When the service is provisioned from the OSS server to a board that is powered off, the
system prompts that the board is currently powered off. In this case, you can manually
power on the board according to the prompt.
Automatic energy-saving mode (automatically powering off a board). When the

automatic energy-saving mode is enabled, the system supports a series of energy-saving
measures according to the referenced energy-saving profile. These measures include the
following: battery energy saving, shutting down unused boards, putting unused xDSL
ports to sleep mode and shutting down the laser on unused xPON ports. An energysaving profile is a set of energy-saving measures. The system provides three typical
energy-saving profiles. You can query the profiles but cannot modify, rename, or delete
them. The three typical profiles are as follows:
Standard energy-saving profile standard, with ID 1. It is the default energy-saving

profile in the system. In this profile, all the energy-saving measures are disabled.
Basic energy-saving profile basic, with ID 2. In this profile, some energy-saving

measures that do not affect the current services are enabled, such as:
Shutting down unused boards
Shutting down the laser on unused xPON ports and putting unused xDSL ports
to sleep mode
Deep energy-saving profile deep, with ID 3. In this profile, all the energy-saving
measures are enabled, and the battery energy saving may affect the service running.
To power on a board that is powered off manually, you must run the board power-on
command to manually power it on.
You can recover the power supply of the board that is automatically powered off in the
following three ways:
Issue 01 (2016-04-29)
Run the board power-on command to power on the board.
Remove the board from the slot that is automatically powered off, and the system
determines that the board is offline and then recovers the power supply of the slot.
After the power supply is recovered, reinstall the board.
The system periodically (every 15 minutes) polls all boards that are automatically
powered off, and determines whether the boards can be powered on. If the boards
meet the power-on requirements, the system automatically powers on the boards.

185

Access Module
1 Commissioning
Procedure
l
Set the manual energy-saving mode.

a.
Run the board power-off command to manually power off a board.
Set the automatic energy-saving mode.

a.
Run the spm-profile command to create an energy-saving profile. By default, the

system uses the standard energy-saving profile. That is, the energy-saving mode is
disabled by default. You can enable the required energy-saving measure according
n
Run the battery energy-saving command to set the status of the mains
monitoring module and battery energy saving.
Run the unused-port shutdown command to set energy saving for unused ports.
Run the unused-slot shutdown command to set energy saving for unused
boards.
b.
Run the system energy-saving mode command to set the used energy-saving
profile.
c.
Run the display system energy-saving mode command to query the used energysaving profile.
----End
Result
The system is referenced to an energy-saving profile (that is, the unused board is shut down).
If a board is not used 15 minutes after it is confirmed and functions properly, the board is
powered off automatically.
Example
To reference energy-saving profile 4 to enable the system energy-saving function, do as
follows: Assume that battery energy saving is enabled and energy saving for unused boards is
enabled.
huawei(config)#spm-profile profile-id 4
huawei(config-spm-prof-4)#unused-slot shutdown enable
huawei(config-spm-prof-4)#battery energy-saving ac-monitor emuid 1 digitalid 6
huawei(config-spm-prof-4)#battery energy-saving enable
huawei(config-spm-prof-4)#quit
huawei(config)#system energy-saving mode profile-id 4
huawei(config)#display system energy-saving mode
Current spm-profile id : 4
Current spm-profile name: spm_profile_4
1.5.2 Checking Alarms and Events

This topic describes how to check the alarm and event reporting function of the device.
Verifying the Alarm and Event Function

This topic describes how to verify the alarm and event function by triggering various alarms
and events through the related operations.
Issue 01 (2016-04-29)

186

Access Module
1 Commissioning
Verifying Operation
Table 1-46 lists the operations for verifying the alarm and event function.
Table 1-46 Operations for verifying the alarm and event function
Operation
Description
Remove a service board.
Check whether the corresponding alarm or event

is generated on the maintenance terminal.
Insert the service board back into the

slot.
Check whether the corresponding recovery alarm

or event is generated on the maintenance terminal.
Remove the optical fiber connected to

an optical port.

Insert the optical fiber back into the

optical port.

Remove the optical fiber connected to

an optical port when an ONT is
online.

Insert the optical fiber back into the

optical port.

Open the cabinet door.

Close the cabinet door.

Remove the fan tray from the shelf.

Insert the fan tray back into the shelf.

Perform the active/standby

switchover of the control boards.
Log in to the system, and run the display event

history command to check whether the active/
standby switchover event history exists.
Querying Alarms and Events

This topic describes how to query history alarms and events through the maintenance
terminal.
Context
Up to 1001 latest fault alarms and recovery alarms, and 901 event alarms can be saved in the
system. If the record table is full, and a new alarm or event is generated, the new alarm or
event overwrites the oldest record in the record table. You can query the records that have
been overwritten in the NMS database.
The CLI provides multiple ways to query history alarms and events.
Issue 01 (2016-04-29)

187

Access Module
1 Commissioning
Table 1-47 lists the commands for querying history alarms.

Table 1-47 Commands for querying history alarms
To...
Run the Command...
Query alarms by
alarm SN
display alarm history alarmsn sn [ detail | list ]
Query alarms by
alarm ID
display alarm history alarmid id [ detail | list | start-number

number]
Query alarms by
alarm type
display alarm history alarmtype type [ detail | list | startnumber number]
Query alarms by
alarm class
display alarm history alarmclass class [ detail | list | startnumber number]
Query alarms by
alarm level
display alarm history alarmlevel level [ detail | list | startnumber number]
Query alarms by
alarm time
display alarm history alarmtime start start-date start-time end

end-date end-time [ start-number number ] [ detail | list | startnumber number]
Query alarms by
alarm parameter
display alarm history alarmparameter { frameid/slotid/portid |

frameid/slotid | frameid | vlanif vlanif } [ detail | list ]
Query all the latest

alarms
display alarm history all [ detail | list ]
Table 1-48 lists the commands for querying history events.

Table 1-48 Commands for querying history events
Issue 01 (2016-04-29)
To...
Run the Command...
Query events by
event SN
display event history eventsn sn [ detail | list ]
Query events by
event ID
display event history eventid id [ detail | list | start-number

number]
Query events by
event type
display event history eventtype type [ detail | list | start-number

number]
Query events by
event class
display event history eventclass class [ detail | list | startnumber number]
Query events by
event level
display event history eventlevel level [ detail | list | startnumber number]
Query events by
event time
display event history eventtime start start-date start-time end

end-date end-time [ start-number number ] [ detail | list | startnumber number]

188

Access Module
1 Commissioning
To...
Run the Command...
Query events by
event parameter
display event history eventparameter { frameid/slotid/portid |

frameid/slotid | frameid | vlanif vlanif } [ detail | list ]
Query all the latest

events
display event history all [ detail | list ]
Procedure
Step 1 Perform an operation (such as inserting and removing a board) to generate an alarm or event.
Step 2 Run the display alarm history command to query history alarms.
Step 3 Run the display event history command to query history events.
----End
Result
You can query the alarm or event triggered by the operation you have performed.
Example
To query the history environment alarms by alarm type, do as follows:
huawei>display alarm history alarmtype
{ type<E><communication,service,process,equipment,environment> }:environment
{ <cr>|detail<K>|list<K>|start-number<1,1900>||<K> }:list
{ <cr>||<K> }:
Command:
display alarm history alarmtype environment list
-----------------------------------------------------------------------AlarmSN Date&Time
Alarm Name/Para
-----------------------------------------------------------------------777
2009-08-21 10:18:29
The system resources usage recovers from
the overload state to the normal state
Resource Name: CPU, Current Percent: 70
765
2009-08-21 10:17:29
The system resources usage exceeds the
threshold
764
2009-08-21 10:17:29
714
2009-08-20 15:04:35
705
2009-08-20 15:03:35
The system resources usage exceeds the
threshold
704
2009-08-20 15:03:35
To query the history events by event date, and the start date is 2009-08-24, the star time is
16:00:00, the end date is 2009-08-24, and the end time is 18:00:00, do as follows:
huawei>display event history
{ all<K>|eventclass<K>|eventid<K>|eventlevel<K>|eventparameter<K>|eventsn<K>|eve
nttime<K>|eventtype<K> }:eventtime
Issue 01 (2016-04-29)

189

Access Module
{
{
{
{
{
{
{
{
1 Commissioning
start<K> }:start
start-date<D><yyyy-mm-dd> }:2009-08-24
start-time<T><hh:mm:ss> }:16:00:00
end<K> }:end
end-date<D><yyyy-mm-dd> }:2009-08-24
end-time<T><hh:mm:ss> }:18:00:00
<cr>|detail<K>|list<K>|start-number<1,1900>||<K> }:list
<cr>||<K> }:
Command:
display event history eventtime start 2009-08-24 16:00:00 end 2009-0824 18:00:00 list
-----------------------------------------------------------------------EventSN Date&Time
Event Name/Para
-----------------------------------------------------------------------35346
2009-08-24 17:59:40
Backing up files fails from the host to
the maintenance terminal
FrameID: 0, SlotID: 9, Position: -1,
Backup type: Host data, Backup Object:
Active control board, Failure cause: Failed
to transfer the file
35345
2009-08-24 17:58:52
Change of Maintenance User's State
User name: test01, Log mode: Telnet, IP:
10.71.42.55, State: Log on
35344
2009-08-24 17:58:47
Change of Maintenance User's State
User name: test01, Log mode: Telnet, IP:
10.71.42.55, State: Log off
35343
2009-08-24 17:58:24
Backing up files starts from the host to
the maintenance terminal
FrameID: 0, SlotID: 9, Position: -1,
Backup type: Host data, Backup Object:
1.5.3 Checking the Log

If a fault occurs on the device, you can locate the fault by querying the log.
Procedure
Step 1 Perform an operation (such as adding a board) through the CLI.
Step 2 In the user mode, run the display log command to query the records in the log.
----End
Result
You can query the log record generated by the operation you have performed.
Example
To query the log records of all users within the period from 10:00:00 on 2009-08-24 to
18:00:00 on 2009-08-24, do as follows:
huawei>display log
{ all<K>|cli<K>|failure<K>|index<K>|memory<K>|name<K>|snmp<K> }:all
{ <cr>|start-date<D><yyyy-mm-dd> }:2009-08-24
{ -<K>|<cr>|start-time<T><hh:mm:ss> }:10:00:00
{ -<K>|<cr> }:{ end-date<D><yyyy-mm-dd> }:2009-08-24
{ <cr>|end-time<T><hh:mm:ss> }:18:00:00
Command:
display log all 2009-08-24 10:00:00 - 2009-08-24 18:00:00
--------------------------------------------------------------------------No.
UserName
Domain
IP-Address
Issue 01 (2016-04-29)

190

Access Module
1 Commissioning
65 test03
-10.71.42.55
Time: 2009-08-24 17:14:48
Cmd: switch language-mode
--------------------------------------------------------------------------No.
UserName
Domain
IP-Address
64 private
-10.78.217.35
Time: 2009-08-24 17:08:08
Cmd:
Index1: hwFrameIndex: 0
Index2: hwSlotIndex: 9
hwBackupServerIpAddr: 10.78.217.35
hwBackupMode: 3
hwBackupFileName: /bmsuser/7341374.poz
hwBackupContent: 68
hwBackupUserNam ...
--------------------------------------------------------------------------No.
UserName
Domain
IP-Address
63 private
-10.78.217.35
1.5.4 Checking the System Switchover

After the active/standby switchover is performed, the services of the active control board are
switched to the standby control board. This ensures that the services run in the normal state.
Prerequisites
l
An active control board and a standby control board must be configured on the device,
and the cables must be connected correctly on the boards.
The patch status of the active and standby control boards must be consistent with the
hardware environment.
If the data of the active and standby control boards is not completely synchronized, the
system prohibits the active/standby switchover.
Precautions
NOTE
Run the display data sync state command to query the data synchronization status of the active
and standby control boards.
When the communication between the active and standby control boards fails or the
standby control board is faulty, the system prohibits the active/standby switchover.
When the data is being loaded, saved, or backed up, the system prohibits the active/
standby switchover.
Context
Classification of the active/standby switchover:
According to the status of the data synchronization, the active/standby switchover is classified
into the normal switchover and forced switchover.
l
Normal switchover: Refers to the active/standby switchover that is performed when the
data is synchronized sufficiently. A normal switchover does not cause links to break or
boards to reset.
Forced switchover: Refers to the active/standby switchover that is performed when the
data is not synchronized sufficiently.
The following data might be synchronized insufficiently:
Issue 01 (2016-04-29)

191

Access Module
1 Commissioning
Configuration data.
When the configuration data is not fully synchronized, the system prohibits
performing forced switchover by running the active/standby switchover command.
Other forced switching methods, such as manually resetting the active control board
or removing the active control board, cause loss of basic data or the system to reset.
Therefore, when the configuration data is not fully synchronized, it is recommended
that you do not perform the forced switchover. You can choose to reset the system.
In this manner, the system can return to the normal state in a short period.
Basic data.
When the basic data is not fully synchronized, the system prohibits performing
forced switchover by running the active/standby switchover command. Other forced
switching methods, such as manually resetting the active board or removing the
active control board, neither reset the system nor affect the database, but they may
cause service boards to reset.
Dynamic data.
When certain dynamic data is not fully synchronized, the system permits
performing forced switchover by running the active/standby switchover command.
After the switchover, the on-going services continue to run in the normal state, and
the original connections, alarms, and logs are not lost.
Procedure
Step 2 Run the system switch-over command to perform the active/standby switchover.
----End
Result
When the ACT LED on the original standby control board is on, log in to the system through
this control board. It is found that the system runs in the normal state.
Example
After the data is saved, perform the active/standby switchover.
huawei#save
{ <cr>|configuration<K>|data<K> }:
Command:
save
huawei#
huawei#
huawei#
huawei(config)#system switch-over
Are you sure to switch over? (y/n)[n]:y
Issue 01 (2016-04-29)

192

Access Module
1 Commissioning
1.6 Supplementary Information

This topic provides the commissioning supplementary information, including script making,
transmission mode setting, and default software settings.
1.6.1 Script Making

Before the commissioning, you can collect the information such as the data plan to make a
commissioning script. Then, configure the basic data of the device by loading the script. This
ensures that the device works in the normal state, which facilitates the commissioning of the
basic functions and services of the device.
Script Overview
The basic configuration through the script includes but is not limited to the following items:
l
Adding the power board
Configuring the environment monitoring unit (including the FAN and the ESC)
Configuring the route protocol

NOTE
For details about how to load the script, see 1.3.7 Loading a Configuration Script.
Example Script
Table 1-49 lists the data plan of an example script. After the example script is configured, you
can log in to the MA5600T/MA5603T/MA5608T through the maintenance terminal in the
management center to commission the basic functions of the device.
Table 1-49 Script data plan
Item
Data
PRTE power board
Slot IDs: 0/21 and 0/22
FAN
l SN: 0
l Sub-node ID: 1 (default)
l Name: FAN
l Fan speed adjustment mode: automatic
ESC
l SN: 1
l Sub-node ID: 15 (default)
l Name: H801ESC
Issue 01 (2016-04-29)

193

Access Module
Item
Data
Route protocol
l Upstream port: 0/19/0
1 Commissioning
l Management VLAN ID: 100; type: Standard VLAN

l IP address of the L3 interface of the management VLAN:
10.50.1.10/24
l Gateway address: 10.50.1.1/24
l IP address of the target network segment: 10.10.1.10/24
The following displays the commands that need to be included in the script according to the
preceding data plan.
NOTICE
Each command in the script must end with a carriage return (CR).
enable
config
board add 0/21 H801PRTE
board add 0/22 H801PRTE
emu add 0 FAN 0 1 FAN
interface emu 0
fan speed mode automatic
quit
emu add 1 H801ESC 0 15 H801ESC
vlan 100 standard
port vlan 100 0/19 0
ip address 10.50.1.10 24
quit
ip route-static 10.10.1.0 24 10.50.1.1
save
1.6.2 Configuring the File Transfer Mode

This topic describes how to configure the file transfer mode of the FTP,SFTP, Xmodem and
TFTP. SFTP with high security is recommended.
Configuring the FTP Transfer Mode

The File Transfer Protocol (FTP) transfer the file through the network port. In this mode, you
need to enter the user name and password. This topic describes how to configure the FTP
transfer mode for transferring (uploading or downloading) files through the inband or outband
Ethernet port of the MA5600T/MA5603T/MA5608T. After the configuration, the FTP server
and the MA5600T/MA5603T/MA5608T can communicate to transfer files in the FTP mode.
Prerequisites
l
Issue 01 (2016-04-29)
The Ethernet port of the FTP server is directly connected to the inband or outband
Ethernet port of the MA5600T/MA5603T/MA5608T.
194

Access Module
1 Commissioning
Connect to the inband Ethernet port (Upstream port) through the crossover cable.
Connect to the outband Ethernet port (Maintenance port) through the direct cable.
You have logged in to the MA5600T/MA5603T/MA5608T remotely from the console

(maintenance terminal), and have entered the global config mode.
Tools, Meters, and Materials

l
Crossover cable
Direct cable
Impact on System
None
Precautions
Make sure that the crossover cable is used to directly connect the FTP server to the
MA5600T/MA5603T/MA5608T. In other cases, a straight-through cable is used.
Procedure
Step 1 On the FTP server, configure the IP address of its Ethernet port.
Configure the Ethernet port IP address of the FTP server according to the IP address planning
in the specific networking, and ensure that the Ethernet port of the FTP server and the inband
or outband Ethernet port of the MA5600T/MA5603T/MA5608T can ping each other.
For example, if the Ethernet port of the FTP server is directly connected to the MA5600T/
MA5603T/MA5608T, the IP address of this Ethernet port and the IP address of the inband or
outband Ethernet port of the MA5600T/MA5603T/MA5608T must be in the same subnet.
Step 2 On the FTP server, run the FTP application and set related parameters.
After running the FTP application, set the path for saving the file, FTP user name, and
password.
Step 3 (This is step is used for setting the FTP user attributes for the manual file transfer.) On the
MA5600T/MA5603T/MA5608T, run the ftp set command to set the FTP user name and
password.
huawei(config)#ftp set
User Password(<=40 chars):huawei//The input is not displayed on the CLI.
NOTE
By default, the FTP user name is anonymous and the password is anonymous@huawei.com in the
MA5600T/MA5603T/MA5608T system.
Step 4 (Optional; this step is required when the function of database file auto-backup is used.) On the
MA5600T/MA5603T/MA5608T, run the file-server auto-backup data command to
configure the FTP user name, password, and port ID.
huawei(config)#file-server auto-backup data primary 10.10.20.1 ftp path test user
----End
Issue 01 (2016-04-29)

195

Access Module
1 Commissioning
Reference
l
Any PC that runs the FTP software can serve as an FTP server.
In the FTP file transfer mode, the user name and the password must be authenticated.
Apart from setting the user name and password on the FTP server, you also need to set
the FTP user name and password on the FTP client (such as the MA5600T/MA5603T/
MA5608T), and make sure that the settings at both ends are the same.
Configuring the SFTP Transfer Mode

The Secure File Transfer Protocol (SFTP) transfer the file through the network port. In this
mode, the instruction and data are encrypted during the transmission process. This topic
describes how to configure the SFTP transfer mode for transferring (uploading or
downloading) files through the inband or outband Ethernet port of the MA5600T/MA5603T/
MA5608T. After the configuration, the SFTP server and the MA5600T/MA5603T/MA5608T
can communicate to transfer files in the SFTP mode.
Prerequisites
l
The Ethernet port of the SFTP server is directly connected to the inband or outband
Connect to the inband Ethernet port (Maintenance port) through the crossover
cable.
Connect to the outband Ethernet port (Upstream port) through the direct cable.


l
Crossover cable
Direct cable
Impact on System
None
Precautions
Make sure that the crossover cable is used to directly connect the SFTP server to the
Procedure
Step 1 On the SFTP server, configure the IP address of its Ethernet port.
Configure the Ethernet port IP address of the SFTP server according to the IP address
planning in the specific networking, and ensure that the Ethernet port of the SFTP server and
the inband or outband Ethernet port of the MA5600T/MA5603T/MA5608T can ping each
other.
For example, if the Ethernet port of the SFTP server is directly connected to the MA5600T/
Issue 01 (2016-04-29)

196

Access Module
1 Commissioning
Step 2 On the SFTP server, run the SFTP application and set related parameters.
After running the SFTP application, set the path for saving the file, SFTP user name,
password, and port ID. The port ID is 22 by default.
Step 3 (This is step is used for setting the SFTP user attributes for the manual file transfer.) On the
MA5600T/MA5603T/MA5608T, run the ssh sftp set command to set the SFTP user name,
password, and port ID.
huawei(config)#ssh sftp set
Listening Port(0--65535):22
NOTE
The MA5600T/MA5603T/MA5608T system does not have default SFTP user name, password, or port
ID.
Step 4 (Optional; this step is required when the function of database file auto-backup is used.) On the
MA5600T/MA5603T/MA5608T, run the file-server auto-backup data command to
configure the SFTP user name, password, and port ID.
huawei(config)#file-server auto-backup data primary 10.10.20.1 sftp path test
port 22 user
NOTE
The MA5600T/MA5603T/MA5608T system does not have default SFTP user name, password, or port
ID.
----End
Reference
l
Any PC that runs the SFTP software can serve as an SFTP server.
In the SFTP file transfer mode, the user name and the password must be authenticated.
Apart from setting the user name, password, and port ID on the SFTP server, you also
need to set the SFTP user name, password, and port ID on the SFTP client (such as the
MA5600T/MA5603T/MA5608T), and make sure that the settings at both ends are the
same.
Configuring Xmodem File Transfer Mode

Xmodem protocol transfer the file through the serial port. In this mode does not require any
networking, but he loading speed is slow. This topic describes how to configure the Xmodem
file transfer mode. To upload or download files through the maintenance serial port on the
MA5600T/MA5603T/MA5608T, configure the Xmodem file transfer mode according to this
operation guide. Then, the console and the MA5600T/MA5603T/MA5608T can communicate
with each other normally and transfer files in Xmodem mode.
Prerequisites
You must be logged in to the MA5600T/MA5603T/MA5608T from the console (also called
maintenance terminal) through the serial port, and must enter the global config mode.
Issue 01 (2016-04-29)

197

Access Module
1 Commissioning

RS-232 serial port cable (used for logging in to the MA5600T/MA5603T/MA5608T from the
console through the serial port)

None
Precautions
NOTE
l The speed of transferring files in Xmodem mode through the serial port is limited. Therefore, the
system does not support file transfer in the Xmodem mode for large-size files such as program
packet files and configuration files.
l It is recommended to transfer files through other modes as much as possible, such as TFTP, even if
file transfer in the Xmodem mode is supported.
The baud rate of the serial port on the MA5600T/MA5603T/MA5608T must be the same
as the baud rate of the serial port on the console.
The Xmodem transfer mode is applicable to only the active control board.
Users who log in to the system remotely are prohibited from transferring files in
Xmodem mode.
Procedure
Step 1 Query the baud rate of the serial port on the MA5600T/MA5603T/MA5608T.
huawei(config)#display baudrate
Current active serial baudrate: 9600 bps
Step 2 (This step is optional but is required when you reconfigure the baud rate of the serial port.)
Run the baudrate command on the MA5600T/MA5603T/MA5608T to configure the baud
rate of the serial port on the MA5600T/MA5603T/MA5608T. The high baud rate can increase
the transmission speed.
For example, reconfigure the baud rate on the MA5600T/MA5603T/MA5608T to 9600 bit/s:
huawei(config)#baudrate 9600
Step 3 Open the HyperTerminal on the console to configure the baud rate of the serial port on the
console to be the same as the baud rate on the MA5600T/MA5603T/MA5608T.
Issue 01 (2016-04-29)

198

Access Module
1 Commissioning
----End
Configuring the TFTP Transfer Mode

This topic describes how to configure the TFTP transfer mode for transferring (uploading or
downloading) files through the inband or outband Ethernet port of the MA5600T/MA5603T/
MA5608T. After the configuration, the TFTP server and the MA5600T/MA5603T/MA5608T
can communicate to transfer files in the TFTP mode.
Prerequisites
l
The Ethernet port of the TFTP server is directly connected to the inband or outband
Connect to the inband Ethernet port (Maintenance port) through the crossover
cable.
Connect to the outband Ethernet port (Upstream port) through the direct cable.


l
Crossover cable
Direct cable
Issue 01 (2016-04-29)

199

Access Module
1 Commissioning
Impact on System
None
Precautions
Make sure that the crossover cable is used to directly connect the TFTP server to the
Procedure
Step 1 On the TFTP server, configure the IP address of its Ethernet port.
Configure the Ethernet port IP address of the TFTP server according to the IP address
planning in the specific networking, and ensure that the Ethernet port of the TFTP server and
the inband or outband Ethernet port of the MA5600T/MA5603T/MA5608T can ping each
other.
For example, if the Ethernet port of the TFTP server is directly connected to the MA5600T/
Step 2 On the TFTP server, run the TFTP application and set related parameters.
1.
After the TFTP application is run on the TFTP server, an interface as shown in Figure
1-85 is displayed. In the Server interfaces drop-down list, select the IP address that is
set in step 1.
Figure 1-85 TFTP main interface
2.
In the interface as shown in Figure 1-85, click Settings.
3.
In the dialog box that is displayed, click Browse to select the path for saving the file, as
Issue 01 (2016-04-29)

200

Access Module
1 Commissioning
Figure 1-86 Setting TFTP parameters
----End
Reference
l
Any PC that runs the TFTP software can serve as a TFTP server.
The IP address in the Server interfaces drop-down list is the IP address of the TFTP
server. The TFTP application can identify the IP address automatically. If the TFTP
server has multiple IP addresses, select the correct one.
If the TFTP file transfer fails, check the following items:
Whether the selected IP address of the TFTP server is correct.
Whether the TFTP server can ping the inband or outband Ethernet port of the
MA5600T/MA5603T/MA5608T (run the Ping command).
Whether the TFTP application is run on the TFTP server.
Whether the path is correctly set in the TFTP application.
Whether the TFTP file transfer function has been enabled through the command.
Whether the entered name of the file to be transferred is correct.
1.6.3 Software Package Settings

This topic provides the default software package settings of the MA5600T/MA5603T/
MA5608T.
Issue 01 (2016-04-29)

201

Access Module
1 Commissioning
Factory Default of the xDSL Line Profile

The following Table 1-50, Table 1-51, Table 1-52 list the factory defaults of the xDSL line
profile on the MA5600T/MA5603T/MA5608T.
Table 1-50 ADSL line profile
Profile
Index
Profile
Parameter
Factory Default
DEFVA
L
Transmission mode
T1.413
ETSI
G.992.1(Annex A/B/C)
G.992.2(Annex A/C)
G.992.3(Annex A/B/I/J/L/M)
G.992.4(Annex A/I)
G.992.5(Annex A/B/I/J/M)
Issue 01 (2016-04-29)
Trellis mode
Enable
Bit swap downstream
Enable
Bit swap upstream
Enable
Form of transmit rate adaptation

downstream
AdaptAtStartup

upstream
AdaptAtStartup
Target SNR margin

downstream(0.1dB)
60
Minimum SNR margin

downstream(0.1dB)
Maximum SNR margin

downstream(0.1dB)
160
Target SNR margin

upstream(0.1dB)
60
Minimum SNR margin

upstream(0.1dB)
Maximum SNR margin

upstream(0.1dB)
160
Allow transition to idle
not allowed
Allow transition to low power
not allowed
L0 time(second)
255
Layer 2 time(second)
30

202

Access Module
Profile
Index
Profile
1 Commissioning
Parameter
Factory Default
255
Maximum aggregate transmit

power reduction(dB)
Total maximum aggregate transmit

power reduction(dB)
INM inter arrival time offset

downstream(symbol):
INM inter arrival time step

downstream
INM cluster continuation value

downstream(symbol)
INM equivalent INP mode

downstream
<defm
ode>
Maximum nominal
transmit PSD
downstream(-0.1dBm)
400
Maximum nominal
transmit PSD
upstream(-0.1dBm)
380
Maximum nominal
aggregate transmit power
downstream(0.1dBm)
200
Maximum nominal
aggregate transmit power
upstream(0.1dBm)
125
Upstream PSD mask

selection
ADLU-32/EU-32
Network timing reference clock

mode
Issue 01 (2016-04-29)

FreeRun
203

Access Module
1 Commissioning
Table 1-51 VDSL line profile

Profile
Index
Profile
Parameter
Factory Default
DEFVAL
Transmission mode
T1.413
G.992.1(Annex
A/B/C)
G.992.2(Annex A/C)
G.992.3(Annex
A/B/I/J/L/M)
G.992.4(Annex A/I)
G.992.5(Annex
A/B/I/J/M)
G.993.2(Annex
A/B/C)
Issue 01 (2016-04-29)
Bit swap downstream
Enable
Bit swap upstream
Enable

downstream
AdaptAtStartup
Form of transmit rate adaptation upstream
AdaptAtStartup
Target SNR margin downstream(0.1dB)
60
Minimum SNR margin

downstream(0.1dB)
Maximum SNR margin

downstream(0.1dB)
300
Target SNR margin upstream(0.1dB)
60
Minimum SNR margin upstream(0.1dB)
Maximum SNR margin upstream(0.1dB)
300
UPBO US1 band reference PSD

parameters[a, b]
1650,1020

parameters[a, b]
1650,615

parameters[a, b]
0,0

parameters[a, b]
0,0
UPBO Boost Mode
Enable
UPBO US1 band reference electrical

length

204

Access Module
Profile
Index
Issue 01 (2016-04-29)
Profile
1 Commissioning
Parameter
Factory Default

length

length

length
UPBO use of electrical length to compute

UPBO
Auto
Allow transition to idle
not allowed
Allow transition to low power
not allowed
L0 time(second)
255
30
255
Maximum aggregate transmit power

reduction(dB)
Total maximum aggregate transmit power

reduction(dB)
<defm
ode>
G.993.2 profile
Profile12a
VDSL2 PSD class mask
AnnexB998-M2xB(B8-6)
VDSL2 link use of U0
Unused
Maximum nominal aggregate

transmit power
downstream(0.1dBm)
145
Maximum nominal aggregate

transmit power
upstream(0.1dBm)
145
Upstream PSD mask selection
ADLU-32/EU-32
Virtual noise mode downstream
Disable
Virtual noise mode upstream
Disable
Network timing reference clock mode
FreeRun

downstream(symbol)
INM inter arrival time step downstream

205

Access Module
Profile
Index
Profile
1 Commissioning
Parameter
Factory Default

downstream (symbol)
INM equivalent INP mode downstream

upstream(symbol)
INM inter arrival time step upstream

upstream(symbol)
INM equivalent INP mode upstream
SOS time Window downstream(64ms)
Minimum percentage of degraded tones

downstream
Minimum number of normalized CRC

anomalies downstream(0.02)
65535
Maximum number of SOS downstream
SNR margin offset of ROC

downstream(0.1dB)
Minimum impulse noise protection of

ROC downstream
SOS time Window upstream(64ms)
Minimum percentage of degraded tones

upstream
Minimum number of normalized CRC

anomalies upstream(0.02)
65535
Maximum number of SOS upstream
SNR margin offset of ROC

upstream(0.1dB)
Minimum impulse noise protection of

ROC upstream
Table 1-52 SHDSL line profile
Issue 01 (2016-04-29)
Profile
Index
Profile
Parameter
Factory Default
DEFVAL
Path mode
ATM

206

Access Module
Profile
Index
Profile
1 Commissioning
Parameter
Factory Default
G.SHDSL interface mode of line
two wire
G.SHDSL minimum line

rate(unit:kbps)
2048
G.SHDSL maximum line

rate(unit:kbps)
2048
PSD
symmetric
Transmission mode
all
Remote enable
enabled
Probe enable
disabled
Downstream current target SNR

margin
Downstream worst target SNR margin
Upstream current target SNR margin
Upstream worst target SNR margin
Target SNR margin used bitmap
0x5
Reference times
Factory Defaults of the xDSL Alarm Profile

The following Table 1-53, Table 1-54, Table 1-55 list the factory defaults of the xDSL alarm
profile on the MA5600T/MA5603T/MA5608T.
Table 1-53 ADSL alarm profile
Profil
e
Index
Profile
Parameter
DEFV
AL
CO
CPE
Issue 01 (2016-04-29)
Factory
Default
The number of forward error correction
seconds
The number of errored seconds
The number of severely errored seconds
The number of loss of signal seconds
The number of unavailable seconds

seconds

207

Access Module
Profil
e
Index
Profile
Parameter
1 Commissioning
Factory
Default
The number of failed full initialization
The number of failed short initialization
Table 1-54 VDSL alarm profile

Profil
e
Index
Profile
Parameter
DEFV
AL
CO
CPE
Issue 01 (2016-04-29)
Factory
Default
seconds

seconds
The number of failed full initialization
The number of full initialization

208

Access Module
1 Commissioning
Table 1-55 SHDSL alarm profile

Profil
e
Index
Profile
Parameter
Factory Default
DEFV
AL
Loop attenuation threshold (unit:dB)
SNR margin threshold (unit:dB)
ES threshold (unit:second)
SES threshold (unit:second)
CRC anomaly threshold
LOSWS threshold (unit:second)
UAS threshold (unit:second)
Dying gasp alarm switch
Enable
Reference status
Unused
Default settings of the system parameters

The following table lists the default settings of the system parameters on the MA5600T/
MA5603T/MA5608T.
Table 1-56 System parameters
Index
Description
Default
Sending howler tone flag, 0:not send, 1:send
Overseas version flag, 0:China, 1:HongKong, 2:Brazil,

3:Egypt, 4:Singapore, 5:Thailand, 6:France, 7:Britain
MSFUK, 8:Britain ETSI, 9:Bulgaria
Stop initial ringing flag, 0:not send, 1:send
The mode of voicemail, 0:high voltage, 1:FSK and ring,

2:FSK no ring
Global digitmap support flag 0:Not support, 1:Support
Transfer mode of media stream in a device, 0:Device

internal forwarding, 1:Device external forwarding
RTP 2833 Payload Type
97
Default settings of the overseas parameters

The following table lists the default settings of the overseas parameters on the MA5600T/
MA5603T/MA5608T.
Issue 01 (2016-04-29)

209

Access Module
1 Commissioning
Table 1-57 Overseas parameters

Index
Description
Default
Hooking upper threshold(ms), reference: China:350,

HongKong:800
350
Hooking lower threshold(ms), reference: China:100,

HongKong:100
100
Flag of applying PARKED LINE FEED or not when

user port is locked, 0:not apply, 1:apply
Factory Defaults of a DBA Profile

The following table lists the factory defaults of a DBA profile on the MA5600T/MA5603T/
MA5608T.
Table 1-58 DBA profile 1
Profile Name
Default
Profile-name
dba-profile_1
Profile-ID
Type
Bandwidth compensation
No
Fix bandwidth(kbps)
5120
Assure bandwidth(kbps)
Maximum bandwidth(kbps)
Issue 01 (2016-04-29)
Profile Name
Default
Profile-name
dba-profile_2
Profile-ID
Type
No
Fix bandwidth(kbps)
1024

210

Access Module
1 Commissioning

Profile Name
Default
Profile-name
dba-profile_3
Profile-ID
Type
No
Fix bandwidth(kbps)
32768

Profile Name
Default
Profile-name
dba-profile_4
Profile-ID
Type
No
Fix bandwidth(kbps)
1024000
Issue 01 (2016-04-29)
Profile Name
Default
Profile-name
dba-profile_5
Profile-ID
Type
No
Fix bandwidth(kbps)
32768

211

Access Module
1 Commissioning

Profile Name
Default
Profile-name
dba-profile_6
Profile-ID
Type
No
Fix bandwidth(kbps)
102400

Profile Name
Default
Profile-name
dba-profile_7
Profile-ID
Type
No
Fix bandwidth(kbps)
32768
Issue 01 (2016-04-29)
Profile
Index
Profile Name
Default
Profile-name
dba-profile_8
Profile-ID
Type
No
Fix bandwidth(kbps)
102400

212

Access Module
1 Commissioning

Profile Name
Default
Profile-name
dba-profile_9
Profile-ID
Type
No
Fix bandwidth(kbps)
32768
65536
Default settings of the GPON ONT line profile

The following table lists the default settings of the GPON ONT line profile on the MA5600T/
MA5603T/MA5608T.
Table 1-67 GPON ONT line profile
Parameter Name
Default
FEC upstream switch
Disable
Qos mode
PQ
Mapping mode
VLAN
<T-CONT 0>
DBA Profile-ID:1
Default settings of the GPON ONT service profile

The following table lists the default settings of the GPON ONT service profile on the
MA5600T/MA5603T/MA5608T.
Table 1-68 GPON ONT service profile
Parameter Name
Default
Port-type
Portnumber
POTS
ETH
Issue 01 (2016-04-29)
adaptive
0
TDM
MOCA
CATV

213

Access Module
1 Commissioning
Parameter Name
Default
TDM port type
E1
TDM service type
TDMoGem
MAC learning function switch
Enable
ONT transparent function

switch
Disable
Multicast forward mode
Unconcern
Multicast forward VLAN
Multicast mode
Unconcern
Upstream IGMP packet

forward mode
Unconcern
Upstream IGMP packet

forward VLAN
Factory Defaults of a GPON ONT Alarm Profile

The following table lists the factory defaults of a GPON ONT alarm profile on the MA5600T/
MA5603T/MA5608T.
Table 1-69 GPON ONT alarm profile
Issue 01 (2016-04-29)
Profile
Index
Profile
Parameter
Factory Default
alarmprofile_
1
GEM port loss of packets threshold
GEM port misinserted packets

threshold
GEM port impaired blocks threshold
Ethernet FCS errors threshold
Ethernet excessive collision count

threshold
Ethernet late collision count

threshold
Too long Ethernet frames threshold
Ethernet buffer (Rx) overflows

threshold
Ethernet buffer (Tx) overflows

threshold

214

Access Module
Profile
Index
Issue 01 (2016-04-29)
Profile
1 Commissioning
Parameter
Factory Default
Ethernet single collision frame count

threshold
Ethernet multiple collisions frame

count threshold
Ethernet SQE count threshold
Ethernet deferred transmission count

threshold
Ethernet internal MAC Tx errors

threshold
Ethernet carrier sense errors

threshold
Ethernet alignment errors threshold
Ethernet internal MAC Rx errors

threshold
PPPOE filtered frames threshold
MAC bridge port discarded frames

due to delay threshold
MAC bridge port MTU exceeded

discard frames threshold
MAC bridge port received incorrect

frames threshold
CES general error time threshold
CES severely time threshold
CES bursty time threshold
CES controlled slip time threshold
CES unavailable time threshold
Drop events threshold
Undersize packets threshold
Fragments threshold
Jabbers threshold
Failed signal of ONU threshold

(Format:1e-x)
Degraded signal of ONU threshold

(Format:1e-x)

215

Access Module
1 Commissioning
Default settings of the environment monitoring units

Tables Table 1-70, Table 1-71 list the default settings of the environment monitoring units on
the MA5600T/MA5603T/MA5608T.
Table 1-70 Default settings of the H801ESC board
Parameter
Default
Sub-node
15
Analog parameters
ESC analog parameter IDs

l 0: allocated to the temperature sensor by default (unable to be
changed by the user).
l 1-4: allocated to the voltage sensor by default.
l 5-8: user-defined analog parameters allocated to other extended
analog sensors, such as the humidity sensor.
Upper and lower alarm thresholds
l Temperature: 5C to 55C
l Humidity: 0% RH to 80% RH
Digital parameters
ESC digital parameter IDs

l Allocated by default (unable to be changed by the user)
0: MDF
1: door status sensor 0
9: water
10-13: lightning arresters 0-3
22: external sensor power
l User-defined IDs
2-8: allocated to other extended digital sensors.
Issue 01 (2016-04-29)

216

Access Module
Parameter
1 Commissioning
Default
Definition of user-defined alarm indexes
1: AC voltage; 2: AC switch; 3: battery voltage; 4: battery fuse; 5:
load fuse; 6: rectifier unit; 7: secondary power supply; 8: door status
of the cabinet; 9: door status of the equipment room; 10: window; 11:
theft; 12: MDF; 13: fan; 14: fire; 15: smoke; 16: water; 17: diesel;
18: abnormal smell 19: air conditioner; 20: lightning arrester; 21:
user-defined alarms of digital parameters
Table 1-71 Default settings of the FAN

Parameter
Default
Sub-node
Fan speed
adjustment mode
Automatic
Whether to report
the fan alarm
Permit
Table 1-72 Default settings of the TCU
Issue 01 (2016-04-29)
Parameter
Default
Sub-node

217

Access Module
2 Basic Configuration
Basic Configuration
About This Chapter

Basic configuration mainly includes certain common configurations, public configurations,
and pre-configurations in service configurations. There is no obvious logical relation between
basic configurations. You can perform basic configurations according to actual requirements.
2.1 Configuring Alarms
Alarm management includes the following functions: alarm record, alarm setting, and alarm
statistics. These functions help you to maintain the device and ensure that the device works
efficiently.
2.2 Adding Port Description
This topic describes how to add port description.
2.3 Configuring the Attributes of an Upstream Ethernet Port
This topic describes how to configure the attributes of a specified Ethernet port so that the
system communicates with the upstream device in the normal state.
2.4 Configuring DOCSIS Event Reporting
DOCSIS 3.0 defines various DOCSIS events, such as authentication failure and CM
certificate error events. Configuring DOCSIS event reporting helps you obtain MA5600T/
MA5603T/MA5608T and CM running status.
Issue 01 (2016-04-29)

218

Access Module
2.1 Configuring Alarms

Alarm management includes the following functions: alarm record, alarm setting, and alarm
statistics. These functions help you to maintain the device and ensure that the device works
efficiently.
Context
An alarm refers to the notification of the system after a fault is detected. After an alarm is
generated, the system broadcasts the alarm to the terminals, mainly including the NMS and
command line interface (CLI) terminals.
Alarms are classified into fault alarm and recovery alarm. After a fault alarm is generated at a
certain time, the fault alarm lasts till the fault is rectified to clear the alarm.
You can modify the alarm settings according to your requirements. The settings are alarm
severity, alarm output mode through the CLI and alarm statistics switch.
When managing alarms on the GUI through the NMS, you can set filtering criteria to mask
unimportant alarms and events. Such filtering function facilitates the focus of the important
alarms and eliminates the load of the NMS.
Procedure
l
Clear alarms.
You can run the alarm active clear command to clear the alarms that are not recovered
in the system.
When an active alarm lasts a long time, you can run this command to clear the
alarm.
Before clearing an alarm, you can run the display alarm active command to query
the currently active alarms.
Configure alarm level.

Run the alarm alarmlevel command to configure the alarm level.
Alarm levels are critical, major, minor, and warning.
Parameter default indicates restoring the alarm level to the default setting.
You can run the display alarm list command to query the alarm level.
The system specifies the default (also recommended) alarm level for each alarm.
Use the default alarm level unless otherwise required.
Configure alarm jitter-proof.

Run the alarm jitter-proof command to configure the alarm jitter-proof function and the
jitter-proof period.
Issue 01 (2016-04-29)
To prevent a fault alarm and its recovery alarm from being displayed frequently,
you can enable the alarm jitter-proof function to filter alarms in the system.
After the alarm jitter-proof function is enabled, the alarm in the system is not
reported to the NMS immediately but is reported to the NMS after an alarm jitterproof period.
If an alarm is recovered in an alarm jitter-proof period, the alarm is not reported to

the NMS.
219

Access Module
You can run the display alarm jitter-proof command to check whether the alarm
jitter-proof function is enabled and whether the alarm jitter-proof period is set.
By default, the alarm jitter-proof function is disabled. You can determine whether to
enable the function according to the running of the device.
Set or shield the output of alarms.

Run the (undo) alarm output command to set or shield the output of alarms to the CLI
terminal.
Setting the output mode of alarms does not affect the generating of alarms. The
alarms generated by the system are still recorded. You can run the display alarm
history command to query the alarms that are shielded.
When the new output mode of an alarm conflicts with the previous mode, the new
output mode takes effect.
The output mode of the recovery alarm is the same as the output mode of the fault
alarm. When the output mode of the fault alarm is set, the system automatically
synchronizes the output mode of its recovery alarm. The reverse is also applicable.
Set alarm statistics period.

Run the alarm-event statistics period command to set the alarm statistics collection
period.
You can use the statistical result of alarms and events to locate a problem in the
system.
You can run the display alarm statistics command to query the alarm statistical
record.
Filter alarms reporting to NMS.

Run the trap filter alarm condition command to filter alarms that the device reports to
the NMS through traps.
The filtering criteria can be alarm ID, alarm severity, alarm type, subrack ID, subrack ID/
slot ID, subrack ID/slot ID/port ID, VLAN interface, and NE.
To reduce alarms and avoid alarm storms, the system does not send alarms of some
ONTs to the NMS. To query the filtering criteria of alarms and events in the system, run
the display trap filter command.
Query alarm configuration and alarm statistics.

Run the display alarm configuration command to query the alarm configuration
according to the alarm ID. The alarm configuration that you can query includes the alarm
ID, alarm name, alarm class, alarm type, alarm level, default alarm level, number of
parameters, CLI output flag, conversion flag, and detailed alarm description.
Run the display alarm statistics command to query the alarm statistical record.
When you need to know the frequency in which one alarm occurs within a time
range, and to know the working conditions of the device and analyze the fault that
may exist, run this command.
Currently, you can query the alarm statistics in the current period and previous
period in the system.
(Optional) Configure alarm policy for ONT.

In FTTH scenarios, you can configure the ONT alarm policy profile to configure alarms
for different service policies.
a.
Issue 01 (2016-04-29)
Create an ONT alarm policy profile.

220

Access Module
Run the ont-alarm-policy command to create an ONT alarm policy profile.

The system supports a maximum number of 16 alarm policy profiles. The default
alarm policy profile is profile 0.
It is recommended that you configure different alarm policies for VIP and common
users.
b.
Configure attributes of the ONT alarm policy profile.

Run the alarm filter command to configure the control function of each alarm of
the profile.
Run the commit command to save the configuration.
Run the display ont-alarm-policy command to query attributes of the ONT alarm
policy profile.
c.
Bind the ONT to the ONT alarm policy profile.

Run the ont alarm-policy command to bind the ONT to the ONT alarm policy
profile so that the PON board can control whether to send the ONT alarm
information.
During ONT adding or confirmation, the system binds the ONT to the default ONT
alarm policy profile 0.
----End
Example
Assume the following configurations: The output of all alarms at level warning is shielded to
the CLI terminal, the alarm jitter-proof function is enabled, the alarm jitter-proof period is set
to 15s, the level of alarms with IDs 0x0a310021 and 0x2e314021 are modified to critical, do
as follows:
huawei(config)#undo alarm output alarmlevel warning
huawei(config)#alarm jitter-proof on
huawei(config)#alarm jitter-proof 15
huawei(config)#alarm alarmlevel 0x0a310021 critical
huawei(config)#alarm alarmlevel 0x2e314021 critical
To mask the activation and deactivation alarm events of the ADSL port (event IDs
0x0a300013 and 0x0a300015) so that normal operations are not affected by too many alarms,
do as follows:
huawei(config)#undo event output eventid 0x0a300013
huawei(config)#undo event output eventid 0x0a300015
To create ONT alarm policy profile 10, filter the following alarms, and bind this profile to
GPON ONT 1 connected to port 0/3/0, do as follows:
l
0x2e112003 (The signal degrade of ONTi (SDi) occurs)
0x2e112004 (The signal fail of ONTi (SFi) occurs)
0x2e112006 (The loss of frame of ONTi (LOFi) occurs)
0x2e313015 (The hardware of the ONT is faulty)
0x2e313016 (The ONT switches to the standby battery)
0x2e313017 (The standby battery of the ONT is lost)
0x2e313018 (The standby battery of the ONT cannot be charged)
Issue 01 (2016-04-29)

221

Access Module
0x2e313019 (The voltage of the standby battery of the ONT is too low)
0x2e31301a (The shell of the ONT is opened)
0x2e313024 (The loss of signals occurs on the ethernet port of the ONT)
0x2e313025 (No signal is received in the video UNI of the ONT)
0x2e31302a (The E1/T1 port loss of signal (LOS) occurs at the ONT)
huawei(config)#ont-alarm-policy policy-id 10
huawei(config-ont-alarm-policy-10)#alarm filter
huawei(config-ont-alarm-policy-10)#commit
huawei(config-ont-alarm-policy-10)#quit
huawei(config-if-gpon-0/3)#ont alarm-policy 0 1
0x2e112003
0x2e112004
0x2e112006
0x2e313015
0x2e313016
0x2e313017
0x2e313018
0x2e313019
0x2e31301a
0x2e313024
0x2e313025
0x2e31302a
policy-id 10
2.2 Adding Port Description

This topic describes how to add port description.
Prerequisites
A board must be added to the system.
Context
After the description of a physical port on the board is added, the description facilitates
information query in system maintenance.
Procedure
Step 1 In the global config mode, run the port desc command to add port description.
Port description is a character string, used to identify a port on a board in a slot of a subrack.
Step 2 Run the display port desc command to query port description.
----End
Example
Plan the format of user port description as "community ID-building ID-floor ID/subrack IDslot ID-port ID". "Community ID-building ID-floor ID" indicates the physical location where
the user terminal is deployed, and subrack ID-slot ID-port ID" indicates the physical port on
the local device that is connected to the user terminal. This plan can present the user terminal
location and the connection between the user terminal and the device, which facilitates query
in maintenance. Assume that the user terminal that is connected to port 0/2/0 of the
MA5600T/MA5603T/MA5608T is deployed in floor 1, building 01 of community A. To add
port description according to the plan, do as follows:
Issue 01 (2016-04-29)

222

Access Module
huawei(config)#port desc 0/2/0 description A-01-01/0-2-0

huawei(config)#display port desc 0/2/0
-----------------------------------------------------------F/ S/ P
IMA Group
Port Description
-----------------------------------------------------------0/ 2/ 0
A-01-01/0-2-0
------------------------------------------------------------
2.3 Configuring the Attributes of an Upstream Ethernet

Port
This topic describes how to configure the attributes of a specified Ethernet port so that the
system communicates with the upstream device in the normal state.
Prerequisites
The board in the GIU slot must be in position and must work in the normal state.
Context
The MA5600T/MA5603T/MA5608T should be interconnected with the upstream device
through the Ethernet port. Therefore, pay attention to the consistency of port attributes.
Default Configuration
Table 2-1 lists the default settings of the attributes of an Ethernet port.
Table 2-1 Default settings of the attributes of an Ethernet port
Parame
ter
Autonegotiation
mode of the
port
Port rate
Duplex
mode
Network
cable
adaptation
mode
Flow
control
Default
Setting
(Optical
Port)
l GICD/
GICF/
GICK:
enabled
l FE
optical
port: 100
Mbit/s
Full-duplex,
read only
Not
supported
Disabled
l Other GIU
board:
disabled
l GE
optical
port:
1000
Mbit/s
l 10GE
optical
port:
10000
Mbit/s
Issue 01 (2016-04-29)

223

Access Module
Parame
ter
Autonegotiation
mode of the
port
Port rate
Duplex
mode
Network
cable
adaptation
mode
Flow
control
Default
Setting
(Electric
al Port)
Enabled
NA
NA
Disabled
NOTE
After the
autonegotiation
mode of the
port is
disabled, you
can
configure the
port rate.
NOTE
After the
autonegotiation
mode of the
port is
disabled, you
can
configure the
duplex
mode.
l FE
electrical
port: auto
l GE
electrical
port:
normal
Procedure
l
Configure the physical attributes of an Ethernet port.

a.
(Optional) Set the auto-negotiation mode of the Ethernet port.

Run the auto-neg command to set the auto-negotiation mode of the Ethernet port.
You can enable or disable the auto-negotiation mode:
n
After the auto-negotiation mode is enabled, the port automatically negotiates

with the peer port for the rate and working mode of the Ethernet port.
After the auto-negotiation mode is disabled, the rate and working mode of the
port are in the forced mode (adopt default values or are set through command
lines).
NOTICE
The mode (auto-negotiation mode or forced mode) of the OLT port must be
consistent with that of the interworking port. Otherwise, the communication fails.
b.
(Optional) Set the rate of the Ethernet port.

Run the speed command to set the rate of the Ethernet port. After the port rate is set
successfully, the port works at the set rate. Pay attention to the following points:
c.
Make sure that the rate of the Ethernet port is the same as that of the
interconnected port on the peer device. This prevents communication failure.
The auto-negotiation mode should be disabled.
(Optional) Set the duplex mode of the Ethernet port.

Run the duplex command to set the duplex mode of the Ethernet port. The duplex
mode of an Ethernet port can be full-duplex, half-duplex, or auto negotiation. Pay
attention to the following points:
n
Issue 01 (2016-04-29)
Make sure that the ports of two interconnected devices work in the same
duplex modes. This prevents communication failure.
224

Access Module
d.
The auto-negotiation mode should be disabled.
The duplex mode of optical ports does not support configuration.
(Optional) Configure the network cable adaptation mode of the Ethernet port.
Run the mdi command to configure the network cable adaptation mode of the
Ethernet port to match the actual network cable. The network adaptation modes are
as follows:
n
normal: Specifies the adaptation mode of the network cable as straightthrough cable. In this case, the network cable connecting to the Ethernet port
must be a straight-through cable.
across: Specifies the adaptation mode of the network cable as crossover cable.
In this case, the network cable connecting to the Ethernet port must be a
crossover cable.
auto: Specifies the adaptation mode of the network cable as auto-sensing. The
network cable can be a straight-through cable or crossover cable.
Pay attention to the following points:
The Ethernet optical port does not support the network cable adaptation mode.
If the Ethernet electrical port works in forced mode (auto-negotiation mode

disabled), the network cable type of the port cannot be configured to auto.
Configure flow control on the Ethernet port.

Run the flow-control command to enable flow control on the Ethernet port. When the
flow of an Ethernet port is heavy, run this command to control the flow to prevent
network congestion, which may cause the loss of data packets. Flow control should be
supported on both the local and peer devices. Pay attention to the following points:
If the peer device does not support flow control, generally, enable flow control on
the local device.
If the peer device supports flow control, generally, disable flow control on the local
device.
By default, flow control is disabled.

l
Mirror the Ethernet port.

Run the mirror port command to mirror the Ethernet port. When the system is faulty,
copy the traffic of a certain port to the other port and output the traffic for traffic
observation, network fault diagnosis, and data analysis.
----End
Example
Ethernet port 0/19/0 is an electrical port. The attribute is as follows: The port rate is 1000
Mbit/s in duplex mode, with supporting flow control, not supporting auto-negotiation
function. Do as follows:
huawei(config)#interface giu 0/19
huawei(config-if-giu-0/19)#auto-neg 0 disable
huawei(config-if-giu-0/19)#speed 0 1000
huawei(config-if-giu-0/19)#duplex 0 full
huawei(config-if-giu-0/19)#flow-control 0
Issue 01 (2016-04-29)

225

Access Module
2.4 Configuring DOCSIS Event Reporting

DOCSIS 3.0 defines various DOCSIS events, such as authentication failure and CM
certificate error events. Configuring DOCSIS event reporting helps you obtain MA5600T/
MA5603T/MA5608T and CM running status.
Procedure
Step 1 Run the cable event loghost ipServerIpAddress command to set the IP address of a log host
to which DOCSIS events are reported.
Step 2 Run the cable event level report { localVolatile | trap | syslog } command to configure the
mode and priority of reporting DOCSIS events.
The modes of reporting DOCSIS events include localVolatile, trap, and syslog.
l
localVolatile: indicates that the DOCSIS events are saved to MA5600T/MA5603T/

MA5608T local logs but not to the buffer. The MA5600T/MA5603T/MA5608T does not
save the DOCSIS events and clears them after being reset. Configure the localVolatile
mode before setting the mode of reporting DOCSIS events to trap or syslog.
trap: reports DOCSIS events to a log host, which is generally the U2000, as traps. After
setting this mode, run the snmp-agent target-host trap-hostname command to
configure the log host.
syslog: reports DOCSIS events to a log host as system logs, which are displayed after the
log host software parses them.
The mode of reporting DOCSIS events varies depending on the priorities of the DOCSIS
events.
l
Default mode of reporting DOCSIS events with emergency or alert priorities:

localVolatile
Default mode of reporting DOCSIS events with critical, error, warning, or notice
priorities: trap, syslog, and localVolatile
Default mode of reporting DOCSIS events with information or debugging priorities: not
reported
Step 3 (Optional)Run the cable cm-status event command to set parameters for a CM to report
events.
----End
Example
The following is an example of the configurations used to enable the CM management
feature:
l
Priority of DOCSIS events: alert
Mode of reporting DOCSIS events to the U2000: trap
Mode of reporting DOCSIS events to the log host: syslog
IP address of the U2000: 10.10.10.10
IP address of the log host: 10.10.20.10
huawei(config)#cable event alert report trap

huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.10.10
Issue 01 (2016-04-29)

226

Access Module
trap-paramsname docsis
huawei(config)#cable event alert report syslog
huawei(config)#cable event loghost ip 10.10.20.10
Issue 01 (2016-04-29)

227

Access Module
3 Configuration Example of DSLAM Services
Configuration Example of DSLAM Services
About This Chapter

This topic describes how to configure the typical services such as Internet access, multicast,
voice, and triple play services on the MA5600T/MA5603T/MA5608T.
3.1 Example of the xDSL Internet Access Service
This topic describes how to configure the xDSL Internet access service in the PPPoE, IPoE,
PPPoA, IPoA and 802.1X modes.
3.2 Example of the xDSL Multicast Service
This topic describes how to configure the multicast video service.
3.3 Example of the VoIP Service
This topic describes how to configure the H.248-based, MGCP-based, and SIP-based VoIP
services respectively.
3.4 Example of the Triple Play
This topic describes how to configure the Triple Play on the MA5600T/MA5603T/MA5608T.
Issue 01 (2016-04-29)

228

Access Module
3.1 Example of the xDSL Internet Access Service

This topic describes how to configure the xDSL Internet access service in the PPPoE, IPoE,
PPPoA, IPoA and 802.1X modes.
3.1.1 Configuring the xDSL Service in PPPoE Mode

On a fiber to the x (FTTx) network, if the MA5600T/MA5603T/MA5608T provides x digital
subscriber line (xDSL) services for broadband users and the users connect to the Internet in
Point-to-Point Protocol over Ethernet (PPPoE) dialup mode, you can configure the
MA5600T/MA5603T/MA5608T by referring to this topic to provide users with high-speed
Internet (HIS) services. The MA5600T/MA5603T/MA5608T functions as an optical network
unit (ONU) in this service. PPPoE is a commonly used Internet access mode currently. In this
mode, broadband users are authenticated, authorized, and charged in Authentication,
Authorization and Accounting (AAA) method.
l
The user accesses the Internet through the PPPoE dialup.
The user packet goes upstream carrying two VLAN tags. The outer VLAN tag identifies
the service and the inner VLAN tag identifies the user. The service of each user is
identified by unique S-VLAN+C-VLAN, that is, this is a 1:1 access scenario.
A traffic profile is adopted for rate limitation. The user access rate is 2048 kbit/s.
To ensure reliability, dual GE ports are adopted for upstream transmission, and link
aggregation is configured for the two upstream ports.
Figure 3-1 shows an example network of the xDSL Internet access service through the
PPPoE dialup.
Figure 3-1 Example network of the xDSL Internet access service through the PPPoE dialup
Modem
Access node
PC
Add SVLAN and CVLAN,
Forwarding by S+C
SVLAN=50
CVLAN=10
Prerequisite
l
The AAA function must be configured.
Issue 01 (2016-04-29)
To enable the AAA function on the device, see Configuring the Local AAA.
229

Access Module
If the AAA function is implemented by the BRAS, a connection to the BRAS must
be established. The BRAS should be capable of identifying the VLAN tag of the
MA5600T/MA5603T/MA5608T in the upstream direction. For the identification
purpose, the user name and password for dial-up Internet access must be configured
on the BRAS.
Procedure
Configure S-VLAN 50 with the stacking attribute. The user packet goes upstream carrying
two VLAN tags. The outer VLAN tag identifies the service and the inner VLAN tag identifies
the user. The service of each user is identified by unique S-VLAN+C-VLAN, and the VLAN
forwarding mode is the S-VLAN+C-VLAN mode.
huawei(config)#vlan attrib 50 stacking
huawei(config)#vlan forwarding 50 vlan-connect
Step 2 Configure upstream ports.

Add upstream ports 0/19/0 and 0/19/1 to VLAN 50. Two ports are added for the purpose of
port aggregation.
To aggregate the two upstream ports as one aggregation group, set the packet forwarding
mode of the aggregation group to egress-ingress, and set the aggregation group to work in the
LACP static mode, do as follows:
huawei(config)#link-aggregation 0/19 0 0/19 1 egress-ingress workmode lacp-static
NOTE
The aggregated ports must meet the following requirements: The ports must work in the full-duplex mode;
the port rates must be the same and the rate of an electrical port must not be of the auto-negotiation type; the
attributes of the ports, such as the default VLAN ID (PVID) and VLAN, must be the same; one port can
belong to only one aggregation group; the port must not be a mirroring destination port; the port must not be
in the auto-negotiation mode; the start port ID must be smaller than the end port ID.
Step 3 In the ADSL access mode, follow this procedure.

1.
Configure an ADSL2+ profile. For details, see Overview of Configuring ADSL2+

Templates and Profiles. The default ADSL2+ line template (line template 1) and the
default ADSL2+ alarm template (alarm template 1) are used as an example.
2.
Activate the ADSL port, and bind the ADSL2+ templates.

NOTE
By default, an ADSL port is in the activated state. Before binding a template to the port, you must
deactivate the port.
In the ADSL access mode, bind the default ADSL2+ line template 1 and ADSL2+ alarm
template 1 to ADSL port 0/2/0.
huawei(config)#interface adsl 0/2
huawei(config-if-adsl-0/2)#deactivate 0
huawei(config-if-adsl-0/2)#activate 0 profile-index 1
huawei(config-if-adsl-0/2)#alarm-config 0 1
huawei(config-if-adsl-0/2)#quit
3.
Run the display traffic table command to query the existing traffic profiles in the
system.
huawei(config)#display traffic table ip from-index 0
{ <cr>|to-index<K> }:
Issue 01 (2016-04-29)

230

Access Module
Command:
display traffic table ip from-index 0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
According to service requirements, the user access rate is 2048 kbit/s. The query result
shows that traffic profile 5 (for inbound and outbound rate limitation) meets the
requirements.
NOTE
4.
If a matched traffic profile is not available in the system, run the traffic table ip command to
configure a new traffic profile.
On the MA5600T/MA5603T/MA5608T, the user access rate can be limited by either a traffic
profile or an ADSL line profile. When both profiles are configured, the smaller one of the two rates
configured in the profiles is adopted as the user bandwidth. In this example, the traffic profile is
used to limit the user access rate.
Run the service-port command to create a service port, adopt traffic profile 5, and set
the S-VLAN ID to 50. The index of the service port is 1, and the VPI and VCI of the
service port must be the same as the management VPI and VCI of the peer modem.
Assume that the management VPI and VCI of the modem are 1 and 39, and the access
port ID is 0/2/0. To facilitate the maintenance of the service port, also configure the
service port description.
huawei(config)#service-port 1 vlan 50 adsl 0/2/0 vpi 1 vci 39 inbound traffictable index 5 outbound traffic-table index 5
huawei(config)#service-port desc 1 description Vlanid:50/adsl/vpi:1vci:39/
stacking
5.
Set the C-VLAN ID of the preset service port 1 to 10 for identifying the user. Configure
the important user packet with a higher priority so that the user packet can be processed
with precedence, and set the priority of the inner VLAN to 4.
huawei(config)#stacking label service-port 1 10
huawei(config)#stacking inner-priority service-port 1 4
Step 4 In the SHDSL access mode, follow this procedure.

1.
Configure an SHDSL profile. For details, see Configuring SHDSL Profiles. Add SHDSL
line profile 3 of the PTM type, with the maximum line rate 2048 kbit/s.
huawei(config)#shdsl line-profile quickadd 3 ptm rate 512 2048
2.
Activate SHDSL port 0/3/1, and bind the preset SHDSL line profile 3 and the default
SHDSL alarm template (alarm template 1) to the port.
NOTE
By default, an SHDSL port is in the activated state. Before binding a profile or template to the port, you
must deactivate the port.
huawei(config)#interface shl 0/3
huawei(config-if-shl-0/3)#deactivate 1
huawei(config-if-shl-0/3)#activate 1 3
huawei(config-if-shl-0/3)#alarm-config 1 1
huawei(config-if-shl-0/3)#quit
Issue 01 (2016-04-29)

231

Access Module
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
profile or an SHDSL line profile. When both profiles are configured, the smaller one of the two
rates configured in the profiles is adopted as the user bandwidth. In this example, the traffic profile
is used to limit the user access rate.
the S-VLAN ID to 50. Set the SHDSL channel mode to PTM, and create service port 2
on SHDSL port 0/3/1. To facilitate the maintenance of the service port, also configure
the service port description.
huawei(config)#service-port 2 vlan 50 shdsl mode ptm 0/3/1 inbound traffictable
index 5 outbound traffic-table index 5
huawei(config)#service-port desc 2 description Vlanid:50/shdsl/vpi:1vci:39/
stacking
5.
Step 5 In the VDSL access mode, follow this procedure.

In this example, the VDSL normal mode is used as an example.
1.
Configure a VDSL profile. For details, see Overview of Configuring VDSL2 Templates
and Profiles. Assume that the VDSL profile ID is 3, downstream rate is 2048 kbit/s,
channel mode is the interleave mode, maximum downstream interleave delay is 8 ms,
maximum upstream interleave delay is 2 ms, SNR margin is 6 dB, minimum
downstream INP is 4, and minimum upstream INP is 2.
huawei(config)#vdsl line-profile quickadd 3 snr 60 0 300 60 0 300
huawei(config)#vdsl channel-profile quickadd 3 path-mode ptm interleaveddelay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
huawei(config)#vdsl line-template quickadd 3 line 3 channel1 3 100 100
Issue 01 (2016-04-29)

232

Access Module
2.
Activate VDSL port 0/4/1, and bind the preset VDSL line template 3 and the default
VDSL alarm template (alarm template 1) to the port.
NOTE
By default, a VDSL port is in the activated state. Before binding a template to the port, you must
huawei(config)#interface vdsl 0/4
huawei(config-if-vdsl-0/4)#deactivate 1
huawei(config-if-vdsl-0/4)#activate 1 template-index 3
huawei(config-if-vdsl-0/4)#alarm-config 1 1
huawei(config-if-vdsl-0/4)#quit
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
profile or a VDSL line profile. When both profiles are configured, the smaller one of the two rates
the S-VLAN ID to 50. Set the VDSL channel mode to PTM, and create service port 3 on
VDSL port 0/4/1. To facilitate the maintenance of the service port, also configure the
huawei(config)#service-port 3 vlan 50 vdsl mode ptm 0/4/1 inbound traffictable
huawei(config)#service-port desc 3 description Vlanid:50/vdsl/vpi:1vci:39/
stacking
5.
Step 6 Configure the user account security.

Issue 01 (2016-04-29)

233

Access Module
The PITP P mode can be enabled to protect the user account against theft and roaming. The
RAIO mode can be customized according to actual requirements. The encoding format
required by China Telecom is considered as an example. The encoding format required by
China Telecom is a customized format, corresponding to the cntel option.
huawei(config)#pitp enable pmode
huawei(config)#raio-mode cntel pitp-pmode
NOTE
For details about the PITP configuration for the user account security, see Configuring Anti-theft and
Roaming of User Accounts Using PITP.

huawei(config)#save
----End
Verification
l
Dialing verification on the user side:
Step 1: Configure the user name and password for the dialup on the modem (the
user name and password must be the same as those configured on the BRAS).
Step 2: Dial up on the PC by using the PPPoE dialup software. After the dialup is
successful, the user can access the Internet.
Step 3: When FTP is used to download files, after the dialup is performed on the
PPPoE dialup software, the PPPoE dialup software prompts that the dialup is
successful. Then, the PC can access the Internet in the PPPoE mode.
Step 4: When downloading files through FTP, you can open Task Manager in
Windows and click Networking to check the link speed. Then, you can calculate
the Internet access rate by the following formula: Attainable Internet access rate =
Computer network adapter rate/48 x 53 x 8. The calculation result approximates to
the planned 2048 kbit/s.
Remote emulation dialing verification:
Step 1: On the MA5600T/MA5603T/MA5608T, run the pppoe simulate start

command to start the PPPoE emulation dialer (the entered user name, password,
and authentication mode must be the same as those configured on the BRAS).
Step 2: Run the display pppoe simulate info command to query status of PPPoE
emulation dialing. If the PPPoE emulation dialing result is success, that is,
simulating interaction between the user and the BRAS is successful, the user can
access the Internet in the PPPoE access mode.
After the emulation verification is completed, run the pppoe simulate stop
command to stop the PPPoE emulation dialing task initiated by the user.
Configuration File
Configuration File in the ADSL access mode:
vlan 50 smart
vlan attrib 50 stacking
vlan forwarding 50 vlan-connect
port vlan 50 0/19 0
port vlan 50 0/19 1
link-aggregation 0/19 0 0/19 1 egress-ingress workmode lacp-static
interface adsl 0/2
deactivate 0
activate 0 profile-index 1
Issue 01 (2016-04-29)

234

Access Module
alarm-config 0 1
quit
service-port 1 vlan 50 adsl 0/2/0 vpi 1 vci 39 inbound traffic-table index 5
outbound traffic-table index 5
service-port desc 1 description Vlanid:50/adsl/vpi:1vci:39/stacking
stacking label service-port 1 10
stacking inner-priority service-port 1 4
pitp enable pmode
raio-mode cntel pitp-pmode
save
Configuration File in the SHDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
shdsl line-profile quickadd 3 ptm rate 512 2048
interface shl 0/3
deactivate 1
activate 1 3
alarm-config 1 1
quit
service-port 2 vlan 50 shdsl mode ptm 0/3/1 inbound traffic-table index 5
service-port desc 2 description Vlanid:50/shdsl/vpi:1vci:39/stacking
pitp enable pmode
save
Configuration File in the VDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
vdsl line-profile quickadd 3 snr 60 0 300 60 0 300
vdsl channel-profile quickadd 3 path-mode ptm interleaved-delay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
interface vdsl 0/4
deactivate 1
activate 1 template-index 3
alarm-config 1 1
quit
service-port 3 vlan 50 vdsl mode ptm 0/4/1 inbound traffic-table index 5 outbound
traffic-table index 5
service-port desc 3 description Vlanid:50/vdsl/vpi:1vci:39/stacking
pitp enable pmode
save
3.1.2 Configuring the xDSL Service in IPoE Mode

subscriber line (xDSL) services for broadband users and the users connect to the Internet in IP
over Ethernet (IPoE) mode, you can configure the MA5600T/MA5603T/MA5608T by
referring to this topic to provide users with high-speed Internet (HIS) services. The
MA5600T/MA5603T/MA5608T functions as an optical network unit (ONU) in this service.
Issue 01 (2016-04-29)

235

Access Module
IPoE is mainly used for private line IP access services. IPoE users are generally authenticated
in Dynamic Host Configuration Protocol (DHCP) option 82 mode.
l
The OLT provides services for users in xDSL modes, including the asymmetric digital
subscriber line 2 plus (ADSL2+), single-pair high-speed digital subscriber line
(SHDSL), and very-high-speed digital subscriber line 2 (VDSL2) mode.
Private line users connect to the Internet in IPoE mode. To prevent unauthorized access,
user accounts are authenticated in DHCP option 82 mode.
To trace service sources of users and control and manage quality of service (QoS) based
on user and service, the Internet service is planned in per user per service per VLAN
(PUPSPV) mode. To differentiate users, the MA5600T/MA5603T/MA5608T allocates a
virtual local area network (VLAN) for each user. Double VLAN tags are added to user
packets for upstream transmission, where the outer VLAN tag identifies the service and
the inner VLAN tag identifies the user. The service of each user is identified by a unique
S-VLAN+C-VLAN. This is called the 1:1 access.
The user access rate is 2048 kbit/s.
Dual GE ports are adopted for upstream transmission to ensure reliability. Link
Figure 3-2 shows an example network of the xDSL IPoE Internet access service.
Figure 3-2 Example network of the xDSL IPoE Internet access service
Modem
Access node
PC
Forwarding by S+C
SVLAN=50
CVLAN=10
Prerequisite
The user PC can obtain an IP address from the DHCP server.
Procedure
Issue 01 (2016-04-29)

236

Access Module

port aggregation.
NOTE

1.

2.

NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
Issue 01 (2016-04-29)

237

Access Module
requirements.
NOTE
4.
stacking
5.

1.
2.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
Issue 01 (2016-04-29)

238

Access Module
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
stacking
5.

1.
128 10000 128 10000 2048 2048
2.
NOTE
3.
Issue 01 (2016-04-29)
system.
239

Access Module

Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
stacking
5.
Step 6 Configure the security of user accounts.

NOTE
l In this example, the MA5600T/MA5603T/MA5608T works in the Layer 2 DHCP mode. Therefore, the
DHCP-related configurations are not required. If the MA5600T/MA5603T/MA5608T works in the Layer
3 DHCP mode, the DHCP-related configurations on the MA5600T/MA5603T/MA5608T are required.
For details, see Configuring DHCP Relay.
l For the details about the security of DHCP accounts, see Configuring Anti-Theft and Roaming of
DHCPv4 User Accounts Using DHCP Option 82.
Assume that the RAIO mode is the user-defined mode, the CID is the access node name
frame/slot/port:vlanid, the RID is the label of the service port where the user is connected. To
enable the DHCP option 82 function with these parameters, do as follows:
huawei(config)#dhcp option82 enable
huawei(config)#raio-mode user-defined dhcp-option82
Issue 01 (2016-04-29)

240

Access Module
huawei(config)#raio-format dhcp-option82 cid anid frame/slot/port:vlanid

huawei(config)#raio-format dhcp-option82 rid splabel

huawei(config)#save
----End
Verification
l
Internet access verification on the user side:
Step 1: After the PC NIC automatically obtains an IP address and a connection to

the Internet is set up, the user can access the Internet.
Step 2: To download a file through FTP, open Windows Task Manager and then
click Networking to observe the link rate. Calculate the Internet access rate by the
formula: attainable Internet access rate = computer NIC rate/48 x 53 x 8. The
calculated result approximates to the planned 2048 kbit/s.
DHCP emulation verification:
Step 1: On the MA5600T/MA5603T/MA5608T run the dhcp simulation start

command to start DHCP emulation.
Step 2: Run the display dhcp simulation command to query the DHCP emulation
status.
After emulation is verified, run the dhcp simulation stop command to stop DHCP
emulation.
Configuration File
Configuration File for the ADSL access mode:
vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
interface adsl 0/2
deactivate 0
alarm-config 0 1
quit
dhcp option82 enable
raio-mode user-defined dhcp-option82
raio-format dhcp-option82 cid anid frame/slot/port:vlanid
raio-format dhcp-option82 rid splabel
save
Configuration File for the SHDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
interface shl 0/3
Issue 01 (2016-04-29)

241

Access Module
deactivate 1
activate 1 3
alarm-config 1 1
quit
save
Configuration File for the VDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
128 10000 128 10000 2048 2048
128 10000 128 10000 2048 2048
interface vdsl 0/4
deactivate 0
alarm-config 0 1
quit
save
3.1.3 Configuring the xDSL Service In PPPoA Mode

This topic describes how to configure a user so that the user can access the MA5600T/
MA5603T/MA5608T in the xDSL mode, and then access the Internet in the PPPoA mode at a
rate of 2048 kbit/s.
l
The user accesses the Internet in the PPPoA mode.
User packets, which carry a single VLAN tag, are transmitted in the upstream direction,
and the services of multiple users are converged into one VLAN. This is called the N:1
access.
PITP is enabled to protect user accounts from theft and roaming.
A traffic profile is adopted for rate limitation. The user access rate is 2048 kbit/s.
Figure 3-3 shows an example network of the xDSL PPPoA Internet access service.
Issue 01 (2016-04-29)

242

Access Module
Figure 3-3 Example network of the xDSL PPPoA Internet access service
Modem
Access node
PC
Modem
Add SVLAN
SVLAN=50
PC
Prerequisite
l
To enable the AAA function on the device, see Configuring the Local AAA.
If the AAA function is implemented by the BRAS, a connection to the BRAS must
be established. The BRAS should be capable of identifying the VLAN tag of the
purpose, the user name and password for dial-up Internet access must be configured
on the BRAS.
Procedure
Create smart VLAN 50.

port aggregation.
NOTE
Step 3 In the case of the ADSL access mode, follow this procedure.
1.
Issue 01 (2016-04-29)

Templates and Profiles. The ID of the ADSL2+ line profile is 3, the downstream rate is
243

Access Module
2048 kbit/s, the channel mode is the interleave mode, the maximum interleave delay is
10 ms, and the SNR margin is 6 dB.
huawei(config)#adsl line-profile quickadd 3 snr 60 30 120 60 30 120
huawei(config)#adsl channel-profile quickadd 3 interleaved-delay 10 10 rate
1024
2048 3096 1024 2048
3096
huawei(config)#adsl line-template quickadd 3 line 3 channel1 3 60 70 channel2
3
2.
Activate the ADSL port. The port is port 0/2/0, and ADSL line template 3 and the default
alarm template (alarm template 1) are bound to the port.
NOTE
huawei(config-if-adsl-0/2)#activate 0 template-index 3
3.
Run the display traffic table ip command to query the traffic profiles that exist in the
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
According to service requirement, the user access rate is 2048 kbit/s. The query result
shows that traffic profile 5 meets the requirement.
NOTE
4.
If no traffic profile in the system meets the service requirement, run the traffic table ip command to
profile or an ADSL line profile. When both profiles are configured, the user bandwidth adopts the
minimum value in the two profiles. In this example, the traffic profile is used to limit the user
access rate.
Run the service-port command to create a service port. The index of the new service
port is 1, the access port is port 0/2/0, traffic profile 5 meets the service requirement, and
the S-VLAN is VLAN 50. The VPI and VCI must be the same as the management VPI
and VCI of the peer modem. Assume that the management VPI and VCI of the modem
are 1 and 39. To facilitate the maintenance of the service port, also configure the service
port description.
huawei(config)#service-port 1 vlan 50 adsl 0/2/0 vpi 1 vci 39 inbound traffictable
huawei(config)#service-port desc 1 description MA5600T/MA5603T/MA5608THW/
Vlanid:50/adsl/smart
Issue 01 (2016-04-29)

244

Access Module
5.
Set the maximum number of MAC addresses that can be learned by the service port is
16. This parameter is to limit the maximum number of the MAC addresses that can be
learned by one account, namely the maximum number of the PCs that can access the
Internet through one account.
huawei(config)#mac-address max-mac-count service-port 1 16
Step 4 In the case of the SHDSL access mode, follow this procedure.
1.
Configure an SHDSL profile. For details, see Configuring SHDSL Profiles. The ID of
the SHDSL line profile is 3, the line rate is 2048 kbit/s, and the profile is used to activate
4-wire ports.
huawei(config)#shdsl line-profile quickadd 3 line four-wire rate 2048
2.
Activate the SHDSL port. The port is port 0/3/1, and SHDSL line profile 3 and the
default alarm profile (alarm profile 1) are bound to the port.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
Issue 01 (2016-04-29)
profile or an SHDSL line profile. When both profiles are configured, the user bandwidth adopts the
access rate.
virtual port is 2, the access port is port 0/3/1, traffic profile 5 meets the service
requirement, and the S-VLAN is VLAN 50. The VPI and VCI must be the same as the
management VPI and VCI of the peer modem. Assume that the management VPI and
VCI of the modem are 1 and 39. To facilitate the maintenance of the service port, also
configure the service port description.
245

Access Module
huawei(config)#service-port 2 vlan 50 shdsl mode atm 0/3/1 vpi 1 vci 39

inbound traffic-table
Vlanid:50/shdsl/smart
5.
Step 5 In the case of the VDSL access mode, follow this procedure.
1.
Configure a VDSL profile. For details, see Overview of Configuring VDSL2

Templates and Profiles. Assume that the VDSL profile ID is 3, downstream rate is 2048
kbit/s, channel mode is the interleave mode, maximum downstream interleave delay is 8
ms, maximum upstream interleave delay is 2 ms, SNR margin is 6 dB, minimum
huawei(config)#vdsl channel-profile quickadd 3 path-mode atm interleaveddelay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
2.
Activate the VDSL port. The access port is port 0/4/1, and VDSL line template 3 and the
default VDSL alarm template (alarm template 1) are bound to the port.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
Issue 01 (2016-04-29)

246

Access Module
NOTE
4.
profile or a VDSL line profile. When both profiles are configured, the user bandwidth adopts the
access rate.
huawei(config)#service-port 3 vlan 50 vdsl mode atm 0/4/1 vpi 1 vci 39
inbound traffic-table index 5 outbound
Vlanid:50/vdsl/smart
5.
Step 6 Configure the PPPoA-PPPoE protocol conversion.

This step is to configure the PPPoA MAC address pool. The start MAC address in the MAC
address pool is 0000-1111-1010, and the maximum number of the MAC addresses in the
MAC address pool is 300. The PPPoA-PPPoE protocol conversion is enabled and the service
encapsulation mode is LLC.
huawei(config)#mac-pool xpoa
huawei(config)#pppoa enable
huawei(config)#encapsulation
0000-1111-1010 300
0/2/0 vpi 1 vci 39 type pppoa llc
Step 7 Configure the user account security.

The PITP P mode can be enabled to protect the user account against theft and roaming. The
RAIO mode can be customized according to actual requirements. The encoding format
required by China Telecom is considered as an example. The encoding format required by
China Telecom is a customized format, corresponding to the cntel option.
huawei(config)#raio-mode cntel pitp-pmode
NOTE
For details about the PITP configuration for the user account security, see Configuring Anti-theft and
Roaming of User Accounts Using PITP.

huawei(config)#save
----End
Verification
l
Issue 01 (2016-04-29)
Step 1: Set the VPI/VCI of the modem to 1/39 and encapsulation mode to llc-pppoa.
Configure the user name and password used for dialing (the user name and password
must be the same as those configured on the BRAS.)
247

Access Module
Step 2: After the settings on the modem are completed, dialing is initialized, a network
connection is automatically set up, and the user can access the Internet.
Step 3: To download a file through FTP, open Windows Task Manager and then click
Networking to observe the link rate. Calculate the Internet access rate by the formula:
attainable Internet access rate = computer NIC rate/48 x 53 x 8. The calculated result
approximates to the planned 2048 kbit/s.
Configuration File
Configuration File for the ADSL access mode:
vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
adsl line-profile quickadd 3 2 snr 60 30 120 60 30 120
adsl channel-profile quickadd 3 interleaved-delay 10 10 rate 1024 2048 3096 1024
2048 3096
adsl line-template quickadd 3 line 3 channel1 3 60 70 channel2 3
interface adsl 0/2
deactivate 0
alarm-config 0 1
quit
service-port desc 1 description MA5600T/MA5603T/MA5608THW/Vlanid:50/adsl/smart
mac-address max-mac-count service-port 1 16
mac-pool xpoa 0000-1111-1010 300
pppoa enable
encapsulation 0/2/0 vpi 1 vci 39 type pppoa llc
pitp enable pmode
save
Configuration File for the SHDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
shdsl line-profile quickadd 3 line four-wire rate 2048
interface shl 0/3
deactivate 1
activate 1 3
alarm-config 1 1
quit
service-port 2 vlan 50 shdsl mode atm 0/3/1 vpi 1 vci 39 inbound traffic-table
service-port desc 2 description MA5600T/MA5603T/MA5608THW/Vlanid:50/shdsl/smart
mac-pool xpoa 0000-1111-1010 300
pppoa enable
pitp enable pmode
save
Configuration File for the VDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
vdsl channel-profile quickadd 3 path-mode atm interleaved-delay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
Issue 01 (2016-04-29)

248

Access Module
interface vdsl 0/4

deactivate 1
alarm-config 1 1
quit
service-port 3 vlan 50 vdsl mode atm 0/4/1 vpi 1 vci 39 inbound traffic-table
service-port desc 3 description MA5600T/MA5603T/MA5608THW/Vlanid:50/vdsl/smart
mac-pool xpoa 0000-1111-1010 300
pppoa enable
pitp enable pmode
save
3.1.4 Configuring the xDSL Service in IPoA Mode

subscriber line (xDSL) services for broadband users and the users connect to the Internet in IP
over ATM (IPoA) mode, you can configure the MA5600T/MA5603T/MA5608T by referring
to this topic to provide users with high-speed Internet (HIS) services. The MA5600T/
MA5603T/MA5608T functions as an optical network unit in this service. IPoA is generally
used on a private line network to meet operators' requirements for transferring from an
asynchronous transfer mode (ATM) network to the IP network. An authentication is generally
not required for IPoA users.
l
The user accesses the Internet in the IPoA mode.
To trace service sources of users and control and manage quality of service (QoS) based
on user and service, the Internet service is planned in per user per service per VLAN
(PUPSPV) mode. To differentiate users, the MA5600T/MA5603T/MA5608T allocates a
virtual local area network (VLAN) for each user. On the OLT, use dual VLANs (SVLAN+C-VLAN) to differentiate users for the Internet access service.
The user access rate is 2048 kbit/s.
Figure 3-4 shows an example network of the xDSL IPoA Internet access service.
Figure 3-4 Example network of the xDSL IPoA Internet access service
Modem
Access node
PC
Modem
PC
Issue 01 (2016-04-29)
Add SVLAN
SVLAN=50

249

Access Module
Procedure
Create smart VLAN 50.

port aggregation.
NOTE
Step 3 In the case of the ADSL access mode, follow this procedure.
1.

Templates and Profiles. The ID of the ADSL2+ line profile is 3, the downstream rate is
2048 kbit/s, the channel mode is the interleave mode, the maximum interleave delay is
10 ms, and the SNR margin is 6 dB.
huawei(config)#adsl line-profile quickadd 3 snr 60 30 120 60 30 120
huawei(config)#adsl channel-profile quickadd 3 interleaved-delay 10 10 rate
1024
2048 3096 1024 2048
3096
huawei(config)#adsl line-template quickadd 3 line 3 channel1 3 60 70 channel2
3
2.
Activate the ADSL port. The port is port 0/2/0, and ADSL line template 3 and the default
alarm template (alarm template 1) are bound to the port.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
---------------------------------------------------------------------------
Issue 01 (2016-04-29)

250

Access Module
0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
profile or an ADSL line profile. When both profiles are configured, the user bandwidth adopts the
access rate.
port is 1, the access port is port 0/2/0, traffic profile 5 meets the service requirement, and
the S-VLAN is VLAN 50. The VPI and VCI must be the same as the management VPI
and VCI of the peer modem. Assume that the management VPI and VCI of the modem
are 1 and 39. To facilitate the maintenance of the service port, also configure the service
port description.
huawei(config)#service-port 1 vlan 50 adsl 0/2/0 vpi 1 vci 39 inbound traffictable
Vlanid:50/adsl/smart
5.
Step 4 In the case of the SHDSL access mode, follow this procedure.
1.
Configure an SHDSL profile. For details, see Configuring SHDSL Profiles. The ID of
the SHDSL line profile is 3, the line rate is 2048 kbit/s, and the profile is used to activate
4-wire ports.
huawei(config)#shdsl line-profile quickadd 3 line four-wire rate 2048
2.
Activate the SHDSL port. The port is port 0/3/1, and SHDSL line profile 3 and the
default alarm profile (alarm profile 1) are bound to the port.
NOTE
3.
system.
Issue 01 (2016-04-29)

251

Access Module
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
profile or an SHDSL line profile. When both profiles are configured, the user bandwidth adopts the
access rate.
huawei(config)#service-port 2 vlan 50 shdsl mode atm 0/3/1 vpi 1 vci 39
inbound traffic-table
Vlanid:50/shdsl/smart
5.
Step 5 In the case of the VDSL access mode, follow this procedure.
1.
Configure a VDSL profile. For details, see Overview of Configuring VDSL2

Templates and Profiles. Assume that the VDSL profile ID is 3, downstream rate is 2048
kbit/s, channel mode is the interleave mode, maximum downstream interleave delay is 8
ms, maximum upstream interleave delay is 2 ms, SNR margin is 6 dB, minimum
huawei(config)#vdsl channel-profile quickadd 3 path-mode atm interleaveddelay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
2.
Issue 01 (2016-04-29)
Activate the VDSL port. The access port is port 0/4/1, and VDSL line template 3 and the
default VDSL alarm template (alarm template 1) are bound to the port.
252

Access Module
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
profile or a VDSL line profile. When both profiles are configured, the user bandwidth adopts the
access rate.
huawei(config)#service-port 3 vlan 50 vdsl mode atm 0/4/1 vpi 1 vci 39
inbound traffic-table index 5 outbound
Vlanid:50/vdsl/smart
5.
Step 6 Enable the IPoA-IPoE protocol conversion.

This step is to configure the IPoA MAC address pool. The start MAC address in the MAC
address pool is 0000-1111-1010, and the maximum number of the MAC addresses in the
Issue 01 (2016-04-29)

253

Access Module
MAC address pool is 300. The IPoA-IPoE protocol conversion is enabled, the default
gateway is the same as the IP address (192.168.1.20) of the upper-layer router, and the service
encapsulation mode is LLC-IPoA. The IP address of the modem is 192.168.1.1.
huawei(config)#mac-pool xpoa 0000-1111-1010 300
huawei(config)#ipoa enable
huawei(config)#ipoa default gateway 192.168.1.20
huawei(config)#encapsulation 0/2/0 vpi 1 vci 39 type ipoa llc srcIP 192.168.1.1

huawei(config)#save
----End
Verification
l
Step 1: Set the VPI/VCI of the modem to 1/39, encapsulation mode to llc-ipoa, and IP
address to 192.168.1.1.
Step 2: After the settings on the modem are completed, the network connection is
automatically set up and the user can access the Internet.
Step 3: When downloading files through FTP, you can open Task Manager in Windows
and click Networking to check the link rate. Calculate the Internet access rate by the
formula: Attainable Internet access rate = Computer NIC rate/48 x 53 x 8. The calculated
result approximates to the planned 2048 kbit/s.
Configuration File
Configuration File of the ADSL access mode:
vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
adsl line-profile quickadd 3 2 snr 60 30 120 60 30 120
adsl channel-profile quickadd 3 interleaved-delay 10 10 rate 1024 2048 3096 1024
2048 3096
adsl line-template quickadd 3 line 3 channel1 3 60 70 channel2 3
interface adsl 0/2
deactivate 0
alarm-config 0 1
quit
service-port desc 1 description MA5600T/MA5603T/MA5608THW/Vlanid:50/adsl/smart
mac-pool xpoa 0000-1111-1010 300
ipoa enable
encapsulation 0/2/0 vpi 1 vci 39 type ipoa llc srcIP 192.168.1.1
save
Configuration File of the SHDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
shdsl line-profile quickadd 3 line four-wire rate 2048
interface shl 0/3
deactivate 1
activate 1 3
Issue 01 (2016-04-29)

254

Access Module
alarm-config 1 1
quit
service-port 2 vlan 50 shdsl mode atm 0/3/1 vpi 1 vci 39 inbound traffic-table
service-port desc 2 description MA5600T/MA5603T/MA5608THW/Vlanid:50/shdsl/smart
mac-pool xpoa 0000-1111-1010 300
ipoa enable
save
Configuration File of the VDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
vdsl channel-profile quickadd 3 path-mode atm interleaved-delay 8 2 inp 4 2 rate
128 10000 128 10000 2048 2048
interface vdsl 0/4
deactivate 1
alarm-config 1 1
quit
service-port 3 vlan 50 vdsl mode atm 0/4/1 vpi 1 vci 39 inbound traffic-table
service-port desc 3 description MA5600T/MA5603T/MA5608THW/Vlanid:50/vdsl/smart
mac-pool xpoa 0000-1111-1010 300
ipoa enable
save
3.1.5 Configuring the xDSL Service in 802.1X Mode

This topic describes how to configure a user to access the MA5600T/MA5603T/MA5608T in
the xDSL mode, and then access the Internet in the 802.1X authentication mode at a rate of
2048 kbit/s.
l
The user accesses the Internet in the 802.1X authentication mode and is authenticated
locally.
User packets are tagged with two VLAN tags and then transmitted upstream. The outer
VLAN tag is used to identify the service. The inner VLAN tag is used to identify the
user. The service of each user is identified by S+C, which is a 1:1 access scenario.
The user access rate is 2048 kbit/s, which is restricted by the traffic profile.
Figure 3-5 shows an example network of the Internet access service in the xDSL 802.1X
mode.
Issue 01 (2016-04-29)

255

Access Module
Figure 3-5 Example network of the Internet access service in the xDSL IPoE mode
Access node
Modem
PC
Forwarding by S+C
SVLAN=50
CVLAN=10
Prerequisite
l
The user already installs the client software that supports 802.1X.
The user name and the password for authentication are already configured properly on
the RADIUS server.
Procedure

port aggregation.
NOTE

Issue 01 (2016-04-29)

256

Access Module
1.

2.

NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
stacking
Issue 01 (2016-04-29)

257

Access Module
5.

1.
2.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
NOTE
4.
Issue 01 (2016-04-29)

258

Access Module

stacking
5.

1.
128 10000 128 10000 2048 2048
2.
NOTE
3.
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
requirements.
Issue 01 (2016-04-29)

259

Access Module
NOTE
4.
stacking
5.
Step 6 Configure the 802.1X authentication.

1.
Enable the 802.1X global switch. Enable the 802.1X authentication for ports 1, 2, and 3.
The 802.1X needs to be triggered by DHCP. Therefore, the DHCP-trigger authentication
must be enabled.
huawei(config)#dot1x
2.
1
2
3
enable
Configure an 802.1X parameters. In the local termination authentication, the 802.1X

parameters should be configured to be in the EAP termination mode. The count of
allowed handshake failure is 1 and the handshake interval is 20s.
3.
enable
service-port
service-port
service-port
dhcp-trigger
keepalive retransmit
eap-end service-port
1 interval 20 service-port 1
1
2
3
Name the AAA authentication scheme huawei and name the AAA accounting scheme
huawei. During the local authentication, the AAA authentication scheme is a local
authentication. Therefore, you do not need to configure the RADIUS server profile;
however, you need to configure the accounting mode in the accounting scheme to none.
huawei(config)#aaa
huawei(config-aaa)#authentication-scheme huawei
huawei(config-aaa-authen-huawei)#authentication-mode local
huawei(config-aaa-authen-huawei)#quit
huawei(config-aaa)#accounting-scheme huawei
huawei(config-aaa-accounting-huawei)#accounting-mode none
huawei(config-aaa-accounting-huawei)#quit
4.
Create a local user with the user name shenzhen and the password shenzhen.
huawei(config-aaa)#local-user shenzhen@huawei service-type terminal password
shenzhen
5.
Issue 01 (2016-04-29)
Name the AAA domain huawei. Bind the domain with the accounting scheme named
huawei, authentication scheme named huawei.
260

Access Module
huawei(config-aaa)#domain huawei
huawei(config-aaa-domain-huawei)#authentication-scheme huawei
huawei(config-aaa-domain-huawei)#accounting-scheme huawei
huawei(config-aaa-domain-huawei)#quit
huawei(config-aaa)#quit

huawei(config)#save
----End
Verification
The procedure for triggering the 802.1X client by DHCP in the Windows XP OS is as
follows:
l
Step 1: Choose Start > Control Panel > Network Connections. Right-click Local
Area Connection and then choose Properties.
Step 2: In the dialog box that is displayed,

a.
On the General tab page, set Internet Protocol (TCP/IP) to Obtain an IP address
automatically.
b.
On the Authentication tab page, select Enable IEEE 802.1x authentication for
this network.
c.
Click OK.
Step 3: Right-click Local Area Connection and then choose Disable.
Step 4: Right-click Local Area Connection and then choose Enable.
After a while, the modem2 prompt icon will be displayed in the lower right corner on
the PC desktop. Click the icon. In the dialog box that is displayed, enter the user name
shenzhen and the password shenzhen, and then click OK to start the actual service
authentication. After passing the authentication, you can access the Internet.
When a file is downloaded through FTP, you can open Windows Task Manager and then
click Networking to observe the link speed. Calculate the Internet access rate by the
formula: Attainable Internet access rate = Computer network adapter rate/48 x 53 x 8.
The calculated result approximates to the planned 2048 kbit/s.
Configuration File
Configuration File of the ADSL access mode:
vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
interface adsl 0/2
deactivate 0
alarm-config 0 1
quit
dot1x enable
dot1x service-port 1
Issue 01 (2016-04-29)

261

Access Module
dot1x dhcp-trigger enable

dot1x keepalive retransmit 1 interval 20 service-port 1
dot1x eap-end service-port 1
aaa
authentication-scheme huawei
authentication-mode local
quit
accounting-scheme huawei
accounting-mode none
quit
local-user shenzhen@huawei service-type terminal password shenzhen
domain huawei
quit
quit
save
Configuration File of the SHDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
interface shl 0/3
deactivate 1
activate 1 3
alarm-config 1 1
quit
dot1x enable
aaa
quit
quit
domain huawei
quit
quit
save
Configuration File of the VDSL access mode:

vlan 50 smart
port vlan 50 0/19 0
port vlan 50 0/19 1
128 10000 128 10000 2048 2048
interface vdsl 0/4
deactivate 0
Issue 01 (2016-04-29)

262

Access Module
alarm-config 0 1
quit
dot1x enable
aaa
quit
quit
domain huawei
quit
quit
save
3.1.6 Changing ADSL Service to VDSL Service (VDSL2 Boards)

Driven by customer demands for higher bandwidth, the ADSL Internet access service of the
VDSL2 board needs to change to the VDSL2 Internet access service. This topic describes
how to achieve so.
l
During network restructuring, the ADSL Internet access service of the VDSL2 board
needs to change to the VDSL2 Internet access service.
Users request a higher bandwidth of 8192 kbit/s.
The VDSL modem is a PTM-mode modem that uses the G993.2 profile 12a.
Users expect that new requirements are met by modifying certain configurations of the
original ADSL service alone. PITP (protecting user accounts from theft), roaming, and
upstream link aggregation are configured.
Figure 3-6 shows an example network of the Internet access service through PPPoE dialup.
Figure 3-6 Example network of the Internet access service through PPPoE dialup
ADSL Modem
VDSL Modem
Issue 01 (2016-04-29)

263

Access Module
Prerequisite
l
To enable the AAA function on the device, see Configuring AAA.
If the AAA function is implemented by the BRAS, a connection to the BRAS must be
established. The BRAS should be capable of identifying the VLAN tag of the
purpose, the user name and password for dial-up Internet access must be configured on
the BRAS.
Procedure
Step 1 Confirm the line template bound to a port that needs such service modifications, for example,
port 0/2/4.
Run the display port state command to query the line template bound to the port.
huawei(config-if-vdsl-0/2)#display port state 4
-----------------------------------------------------------------------------Port
Status
Loopback
Line Template Alarm Template Bonding-group
-----------------------------------------------------------------------------4
Activated
Disable
10
1
------------------------------------------------------------------------------
The query result shows that line template 10 is bound to port 4. Run the display vdsl linetemplate command to query the channel profile and line profile in the line template.
huawei(config-if-vdsl-0/2)#display vdsl line-template 10
-----------------------------------------------------------------------------Template index: 10
Name: VDSL LINE TEMPLATE 10
Line profile index
: 1
Channel1 profile index
: 10
Channel1 rate adaptation ratio downstream
: 100
Channel1 rate adaptation ratio upstream
: 100
------------------------------------------------------------------------------
Step 2 Confirm whether to change the transmission mode and signal noise ratio (SNR).
The query result shows that line profile 1 and channel profile 10 are in line template 10. Run
the display vdsl line-profile command to query the transmission mode and SNR configured
in the line profile.
huawei(config-if-vdsl-0/2)#display vdsl line-profile
1
-----------------------------------------------------------------------------Profile index: 1
Name: DEFVAL
Transmission mode:
T1.413
G.992.2(Annex A/C)
G.992.3(Annex A/B/I/J/L/M)
G.992.4(Annex A/I)
G.992.5(Annex A/B/I/J/M)
Bit swap downstream
: Enable
Bit swap upstream
: Enable
Form of transmit rate adaptation downstream
: AdaptAtStartup
Form of transmit rate adaptation upstream
: AdaptAtStartup
Target SNR margin downstream(0.1dB)
: 60
Minimum SNR margin downstream(0.1dB)
: 0
Maximum SNR margin downstream(0.1dB)
: 300
Target SNR margin upstream(0.1dB)
: 60
Minimum SNR margin upstream(0.1dB)
: 0
Issue 01 (2016-04-29)

264

Access Module
Maximum SNR margin upstream(0.1dB)
UPBO US1 band reference PSD parameters[a,
b]
b]
b]
b]
:
:
:
:
:
300
1650,1020
1650,615
0,0
0,0
If the transmission mode is ADSL, change the transmission mode to VDSL or ALL. To
do so, proceed to Step 3.
If the SNR value does not meet actual requirements over the live network, change it
according to actual conditions. To do so, proceed to Step 3.
If the transmission mode is VDSL or ALL and the SNR value also meets actual
conditions over the live network, go to Step 4.
Step 3 Run the vdsl line-profile quickadd command to reconfigure the transmission mode and SNR.
In addition, configure exclusive VDSL parameters.
1.
According to actual conditions over the live network, SNR is planned to 7 dB,
transmission mode to all (its value is 1), and line profile index to 11.
huawei(config-if-vdsl-0/2)#vdsl line-profile quickadd 11 transmode 1 snr 70 0
300 70 0 300
2.
All parameters following vdsl-parameter are VDSL parameters in contrast to ADSL.

These parameters do not need to be configured in the case of the ADSL Internet access
service. However, in the case of the VDSL Internet access service, these parameters need
to be configured according to actual conditions. The default G993.2 profile is profile
12a, which is consistent with the required profile in this example. Hence, no
modification is required.
Step 4 Run the display vdsl channel-profile command to query the data path mode and line rate in
the channel profile.
huawei(config-if-vdsl-0/2)#display vdsl channel-profile
10
-----------------------------------------------------------------------------Profile index: 10
Name: VDSL CHANNEL PROFILE 10
Data path mode
: ATM
Minimum impulse noise protection downstream
: NoProtection
Minimum impulse noise protection upstream
: NoProtection
Maximum interleaving delay downstream(ms)
: 20
Maximum interleaving delay upstream(ms)
: 20
Minimum transmit rate downstream(Kbps)
: 32
Minimum reserved transmit rate downstream(Kbps) : 32
Maximum transmit rate downstream(Kbps)
: 200000
Minimum transmit rate upstream(Kbps)
: 32
Minimum reserved transmit rate upstream(Kbps)
: 32
Maximum transmit rate upstream(Kbps)
: 200000
If the line rate does not meet the requirements of users, change it. To do so, proceed to Step 5.
Step 5 Run the vdsl channel-profile quickadd command to reconfigure the data path mode and line
rate.
To meet customer demands, increase bandwidth to 8192 kbit/s, set the data path mode to both
and add a new channel profile (channel profile 11).
huawei(config-if-vdsl-0/2)#vdsl channel-profile quickadd 11 path-mode both rat
e 32 81920 32 2048
Step 6 Bind the required VDSL2 line template 11 to port 0/2/4.

NOTE
By default, a port is in the activated state. Before binding a template to the port, you must deactivate the port.
Issue 01 (2016-04-29)

265

Access Module
huawei(config-if-vdsl-0/2)#vdsl line-template quickadd 11 line 11 channel1 11 100

100
Step 7 Add a traffic profile.

1.
Run the display traffic table ip command to query the existing traffic profiles in the
system.
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 1024
34768
2048
69536
6 tag-pri
1 2496
81872
4992
163744
6 tag-pri
2 512
18384
1024
36768
0 tag-pri
3 576
20432
1152
40864
2 tag-pri
4 64
4048
128
8096
4 tag-pri
5 2048
67536
4096
135072
0 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
According to customer requirements, the user access rate is 8192 kbit/s. The query result
shows that no traffic profile meets customer requirements. Therefore, run the traffic
table ip command to configure a new traffic profile (traffic profile 7) and set the rate to
8192 kbit/s in the new traffic profile.
NOTE
You can configure the traffic profile or the VDSL2 line profile on the MA5600T/MA5603T/MA5608T
to limit the user access rate. When both profiles are configured, the bandwidth of the user is the
minimum value of the two profiles. In this example, the traffic profile is used to limit the user access
rate.
huawei(config)#traffic table ip index 7 cir 8192 priority 6 priority-policy
local-Setting
Step 8 Configure a service port.

Run the display service-port command to query the original service port.
huawei(config)#display service-port port 0/2/4
{ <cr>|autosense<K>|ont<K>|sort-by<K> }:
Command:
display service-port port 0/2/4
Switch-Oriented Flow List
---------------------------------------------------------------------------INDEX VLAN VLAN
PORT F/ S/ P VPI VCI
FLOW FLOW
RX
TX
STATE
ID
ATTR
TYPE
TYPE PARA
---------------------------------------------------------------------------5 101 common
vdl 0/2/4 0
35
vlan untag
6
6
up
---------------------------------------------------------------------------Total : 1 (Up/Down :
1/0)
The query result shows that VPI and VCI are configured, which indicate that VDSL is in the
ATM mode. In this example, however, the VDSL is in the PTM mode. Run the service-port
command to create a service port, adopt traffic profile 7, and set the S-VLAN ID to 101. Set
the index of the service port to 3 (the index must be different from the original index) and the
access port to 0/2/4. To facilitate maintenance of the service port, configure the service port
description.
Issue 01 (2016-04-29)

266

Access Module
NOTE
Generally, the ADSL is in the ATM mode and the VDSL is in the PTM mode. If an ATM service port only is
configured, a PTM service port needs to be added.
huawei(config)#service-port 3 vlan 101 vdsl mode ptm 0/2/4 rx-cttr 7 tx-cttr 7
huawei(config)#service-port desc 3 description Vlanid:101/vdsl/ptm

huawei(config)#save
----End
Verification
l
Step 1: Configure the user name and password for the dialup on the modem (the user
name and password must be the same as those configured on the BRAS).
Step 2: Dial up on the PC by using the PPPoE dialup software. After the dialup is
successful, the user can access the Internet.
Step 3: When FTP is used to download files and after the dialup is performed on the
PPPoE dialup software, the PPPoE dialup software prompts that the dialup is successful.
Then, the PC can access the Internet in the PPPoE mode.
Step 4: When downloading files through FTP, you can open Task Manager in Windows
and click Networking to check the link speed. Then, you can calculate the Internet access
rate by the following formula: Attainable Internet access rate = Computer network
adapter rate/48 x 53 x 8. The calculated result approximates to the planned 8192 kbit/s.
3.2 Example of the xDSL Multicast Service

This topic describes how to configure the multicast video service.
3.2.1 Configuring the Multicast Video Service (Static)

Static program configuration for multicast services is fine-grained program configuration and
management, with functions of program/user multicast bandwidth management, program
preview, and program prejoin. This configuration mode applies to multicast services that have
strict requirements on program and user management.
l
ISP 1 has two popular music programs, and ISP 2 has one popular music program and
one popular video program. These programs can be ordered continuously and in time.
The program ordering status can be recorded, collected, and reported for monitoring and
charging.
User 1 has purchased only the music program package from ISP 1, while user 2 has
purchased only the video program package from ISP 2. Rights management is required
for the two users.
The package purchased by user 1 limits the maximum available multicast bandwidth to
10 Mbit/s, and the package purchased by user 2 limits the maximum available multicast
bandwidth to 5 Mbit/s. Bandwidth restriction is required for the two users.
Figure 3-7 shows an example network of the multicast service.

User 1 and user 2 are connected to the access device in VDSL IPoE mode.
Issue 01 (2016-04-29)

267

Access Module
Figure 3-7 Example network of the multicast service
Data Plan
Table 3-1 lists the data plan for configuring the multicast video service with static program
configuration.
Table 3-1 Data plan for configuring the multicast video service with static program
configuration
Item
Data
Multicast VLAN
Multicast domain of ISP 1: VLAN 10

NOTE
It is recommended that different multicast VLANs be planned for
different ISPs.
Issue 01 (2016-04-29)
Multicast upstream port
0/19/0
Multicast mode
IGMP proxy
Multicast protocol
IGMPv3

268

Access Module
Item
Data
Multicast program
ISP 1
l Program source address: 10.10.10.10

l program1: 224.1.1.1
l program2: 224.1.1.2
l Maximum program bandwidth: 3500 kbit/s
l Program log reporting: enabled
ISP 2
l Program source address: 10.10.10.11
l program3: 224.1.1.3
l program4: 224.1.1.4
l Maximum program bandwidth: 5000 kbit/s
l Program log reporting: enabled
Right profile
Music program
l Profile name: music
l Program right: watch
Video program
l Profile name: movie
l Program right: watch
VDSL port attribute
Working mode: PTM

Bound line profile and alarm profile: default profiles (profile
ID: 1)
Port connected to user 1: 0/2/1
Multicast user
User 1:
l Name of the bound right profile: music
l Maximum multicast bandwidth: 10 Mbit/s
l Multicast user log recording: enabled
User 2:
l Name of the bound right profile: movie
l Maximum multicast bandwidth: 5 Mbit/s
l Multicast user log recording: enabled
Procedure
Step 1 Configure multicast VLANs and programs.
Configure smart VLAN 10 as the multicast domain of ISP 1, and smart VLAN 20 as the
multicast domain of ISP 2.
1.
Issue 01 (2016-04-29)
Configure the protocol, multicast upstream port, and program list of multicast VLAN 10.
269

Access Module
Set the multicast VLAN to VLAN 10, multicast mode to IGMP proxy, multicast protocol
to IGMPv3 (system default), multicast upstream port to port 0/19/0, statically configured
programs to 224.1.1.1 and 224.1.1.2, program source address to 10.10.10.10, and
program bandwidth to 3500 kbit/s, and enable program log reporting.
huawei(config)#multicast-vlan 10
huawei(config-mvlan10)#igmp mode proxy
huawei(config-mvlan10)#igmp uplink-port 0/19/0
huawei(config-mvlan10)#igmp program add name program1 ip 224.1.1.1 sourceip
10.10.10.10
bandwidth 3500 log enable
10.10.10.10
huawei(config-mvlan10)#quit
2.
Configure the multicast protocol, multicast upstream port, and program list of multicast
VLAN 20.
Set the multicast VLAN to VLAN 20, multicast mode to IGMP proxy, multicast protocol
to IGMPv3 (system default), multicast upstream port to port 0/19/0, statically configured
programs to 224.1.1.3 and 224.1.1.4, program source address to 10.10.10.11, and
program bandwidth to 5000 kbit/s, and enable program log reporting.
10.10.10.11
10.10.10.11
Step 2 Configure right profiles named music and movie with the watch right, and bind the right
profiles to the programs.
huawei(config-mvlan20)#btv
huawei(config-btv)#igmp profile add profile-name music
huawei(config-btv)#igmp profile profile-name music program-name
huawei(config-btv)# igmp profile add profile-name movie
huawei(config-btv)#igmp profile profile-name movie program-name
huawei(config-btv)#quit
program1 watch
program2 watch
program3 watch
program4 watch
Step 3 Activate the VDSL ports, and bind the ports to the line profile and alarm profile.
Bind VDSL port 0/2/1 and VDSL port 0/4/1 to the default line profile (line profile 1) and the
default alarm profile (alarm profile 1).
Step 4 Configure multicast users.

1.
Create the service channels of the multicast users.

Create service port 100 on VDSL port 0/2/1, and service port 101 on VDSL port 0/4/1.
Issue 01 (2016-04-29)

270

Access Module
huawei(config)#port vlan 10
huawei(config)#service-port
2
2
2.

0/19 0
0/19 0
100 vlan 10 vdsl mode ptm 0/2/1 rx-cttr 2 tx-cttr
Configure the attributes of the multicast users.

Configure multicast user 0/2/1 as the authentication type, with log reporting enabled, and
with the maximum bandwidth 10 Mbit/s. Configure multicast user 0/4/1 as the
authentication type, with log reporting enabled, and with the maximum bandwidth 5
Mbit/s.
huawei(config)#btv
huawei(config-btv)#igmp user add service-port 100 auth log enable maxbandwidth 10240
huawei(config-btv)#igmp user add service-port 101 auth log enable maxbandwidth 5120
3.
Bind the multicast users to the right profiles.

Bind VDSL user 0/2/1 to right profile music, and VDSL user 0/4/1 to right profile
movie.
huawei(config-btv)#igmp user bind-profile service-port 100 profile-name music
huawei(config-btv)#igmp user bind-profile service-port 101 profile-name movie
4.
Add the VDSL users to the multicast VLANs so that the VDSL users are multicast
members.
huawei(config-btv)#multicast-vlan 10
huawei(config-mvlan10)#igmp multicast-vlan member service-port 100
huawei(config-mvlan10)#multicast-vlan 20
Step 5 Save the configuration.

huawei(config)#save
----End
Result
l
VDSL user 0/1/0 can watch the programs with IP addresses 224.1.1.1 and 224.1.1.2 that
are provided by ISP 1, but VDSL user 0/1/0 cannot watch the program with IP address
224.1.1.3.
VDSL user 0/2/0 can watch the program with IP address 224.1.1.4 that is provided by
ISP 2.
Configuration File
vlan 10 smart
multicast-vlan 10
igmp mode proxy
igmp uplink-port 0/19/0
igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10
quit
vlan 20 smart
igmp mode proxy
Issue 01 (2016-04-29)

271

Access Module

btv
igmp profile add profile-name music
igmp profile profile-name music program-name program1 watch
igmp profile add profile-name movie
igmp profile profile-name movie program-name program4 watch
quit
interface vdsl 0/2
deactivate 1
alarm-config 1 1
quit
interface vdsl 0/4
deactivate 1
alarm-config 1 1
quit
port vlan 10 0/19 0
port vlan 20 0/19 0
service-port 100 vlan 10 vdsl mode ptm 0/2/1 rx-cttr 2 tx-cttr 2
btv
igmp user add service-port 100 auth log enable max-bandwidth 10240
igmp user add service-port 101 auth log enable max-bandwidth 5120
igmp user bind-profile service-port 100 profile-name music
igmp user bind-profile service-port 101 profile-name movie
multicast-vlan 10
igmp multicast-vlan member service-port 100
multicast-vlan 20
quit
save
3.2.2 Configuring the Multicast Video Service (Dynamic)

Dynamic program generation simplifies multicast service configuration and reduces
maintenance cost, but does not support functions of program/user multicast bandwidth
management, program preview, and program prejoin. This configuration mode applies to
multicast services that do not have strict requirements on program and user management or to
those having programs and users managed on the upper-layer device.
l
ISP 1 and ISP 2 each have an address segment corresponding to multicast programs,
which do not require strict management and are dynamically updated according to the
ordering situation.
The service package purchased by user 1 allows user 1 to watch programs of ISP 1 only.
The service package purchased by user 2 allows user 2 to watch programs of ISP 2 only.
The ordering information about users can be recorded for monitoring and charging.
Figure 3-8 shows an example network of the multicast service.

User 1 and user 2 are connected to the access device in VDSL IPoE mode.
Issue 01 (2016-04-29)

272

Access Module
Figure 3-8 Example network of the multicast service
Data Plan
Table 3-2 lists the data plan for configuring the multicast video service with dynamic program
generation.
Table 3-2 Data plan for configuring the multicast video service with dynamic program
generation
Item
Data
Multicast VLAN

NOTE
It is recommended that different multicast VLANs be planned for
different ISPs.
Issue 01 (2016-04-29)
Multicast upstream port
0/19/0
Multicast mode
IGMP proxy
Multicast protocol
IGMPv3

273

Access Module
Item
Data
Multicast program
Dynamic generation
Program address range of ISP 1: 224.1.1.1-224.1.1.2
Program address range of ISP 2: 224.1.1.3-224.1.1.4
VDSL port attribute
Working mode: PTM

Bound line profile and alarm profile: default profiles (profile
ID: 1)
Multicast user
Multicast user log recording: enabled
Procedure
Step 1 Configure multicast VLANs and programs.
Configure smart VLAN 10 as the multicast domain of ISP 1, and smart VLAN 20 as the
multicast domain of ISP 2.
1.
Configure multicast VLAN 10 with the dynamic program generation mode, and specify
the range of the IP addresses of the programs that can be requested by the users in
multicast VLAN 10 as 224.1.1.1 to 224.1.1.2. Multicast VLAN 10 adopts IGMP proxy,
IGMP v3 (system default value), and multicast upstream port 0/19/0.
NOTICE
The multicast program configuration mode can be changed only when igmp match
mode is set to off. However, setting igmp match mode to off will cause users to go
offline. Therefore, it is recommended that the program configuration mode be planned
beforehand.
huawei(config-mvlan10)#igmp match mode disable
huawei(config-mvlan10)#igmp match group ip 224.1.1.1 to-ip 224.1.1.2
2.
Configure multicast VLAN 20 with the dynamic program generation mode, and specify
the range of the IP addresses of the programs that can be requested by the users in
multicast VLAN 10 as 224.1.1.3 to 224.1.1.4. Multicast VLAN 20 adopts IGMP proxy,
IGMP v3 (system default value), and multicast upstream port 0/19/0.
Issue 01 (2016-04-29)

274

Access Module

Step 2 Activate the VDSL ports, and bind the ports to the line profile and alarm profile.
Bind VDSL port 0/2/1 and VDSL port 0/4/1 to the default line profile (line profile 1) and the
default alarm profile (alarm profile 1).

1.
Create the service channels of the multicast users.

Create service port 100 on VDSL port 0/2/1, and service port 101 on VDSL port 0/4/1.
2
2
2.
0/19 0
0/19 0
Configure the attributes of the multicast users.

Enable the log reporting for multicast users 0/2/1 and 0/4/1. The authentication status
and multicast bandwidth of the multicast users do not need to be configured.
huawei(config)#btv
huawei(config-btv)#igmp user add service-port 100 log enable
huawei(config-btv)#igmp user add service-port 101 log enable
3.
Add the VDSL users to the multicast VLANs so that the VDSL users are multicast
members.
Step 4 Save the configuration.

huawei(config)#save
----End
Result
l
are provided by ISP 1.
are provided by ISP 2.
Configuration File
vlan 10 smart
multicast-vlan 10
Issue 01 (2016-04-29)

275

Access Module
igmp match mode disable

igmp match group ip 224.1.1.1 to-ip 224.1.1.2
igmp mode proxy
quit
vlan 20 smart
igmp match mode disable
igmp match group ip 224.1.1.3 to-ip 224.1.1.4
igmp mode proxy
quit
interface vdsl 0/2
deactivate 1
alarm-config 1 1
quit
interface vdsl 0/4
deactivate 1
alarm-config 1 1
quit
port vlan 10 0/19 0
port vlan 20 0/19 0
btv
igmp user add service-port 100 auth log enable
igmp user add service-port 101 auth log enable
multicast-vlan 10
multicast-vlan 20
quit
save
3.3 Example of the VoIP Service

This topic describes how to configure the H.248-based, MGCP-based, and SIP-based VoIP
services respectively.
3.3.1 Configuring the VoIP Service (H.248)

This topic describes an example for configuring the H.248-based VoIP service.
In an office located in China, the MA5600T/MA5603T/MA5608T that adopts the H.248
protocol is newly deployed. Data plan and configuration, however, are not performed on the
MGC (softswitch) connected to the MA5600T/MA5603T/MA5608T. The MA5600T/
MA5603T/MA5608T is required to provide the following VoIP services:
l
The common phone services are provisioned to 32 users (phones 0-31).
The polarity-reversal accounting is adopted.
Figure 3-9 shows an example network for configuring the H.248-based VoIP service.
Issue 01 (2016-04-29)

276

Access Module
Figure 3-9 Example network for configuring the H.248-based VoIP service
Prerequisite
l
According to the actual network, a route from the MA5600T/MA5603T/MA5608T to the

MGC must be configured to ensure that the MA5600T/MA5603T/MA5608T and the
MGC are reachable from each other.
Electronic switch 0 must be in location-1 (indicating that the system goes upstream
through only the upstream board). Electronic switch 1 must be in location-0 (indicating
that the VoIP service is supported). For details about how to configure the electronic
switch, see electro-switch.
NOTE
l The SCUN and SCUH control boards do not support electronic switch.
l The control board SCUL does not provide the upstream port and the system goes upstream
through only the upstream board.
Data Plan
After the service requirements are further confirmed and analyzed with the service provider,
the data plan is made by considering the interconnection with the MGC and according to the
data plan described in Configuring the VoIP PSTN Service (H.248-based or MGCP-based).
Table 3-3 provides the data plan for configuring the H.248-based VoIP service.
Issue 01 (2016-04-29)

277

Access Module
Table 3-3 Data plan for configuring the H.248-based VoIP service
Item
MG interface
data
(The data
configuration
on the MG
interface must
be the same as
the data
configuration
on the MGC.)
Data
Media and
signaling
parameter
s
Parameter
s of the
MG
interface
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
MG
interface
fails to be
enabled if
these
parameter
s are not
configure
d.
Media and
signaling
upstream VLAN
Standard VLAN is recommended as

the upstream VLAN of the VoIP
service. Standard VLAN 20 is
adopted.
Media and
signaling
upstream port
In this office, all the services are

transmitted upstream through the
upstream interface board. Therefore,
port 0/19/0 is used as the upstream
port of the VoIP service.
Media and
signaling IP
addresses
These two IP addresses are both

10.10.10.10.
Default IP
address of the
MG
Confirmed with the engineers of this

service provider, the next hop IP
address from MA5600T/MA5603T/
MA5608T to the MGC is 10.10.10.1.
MG interface ID

service provider, the 32 users to be
provisioned with the services are the
first batch of users in the community
named huawei, and later other users in
this community will be provisioned
with the same services gradually. The
number of users in this community is
10,000. Considering that the number
of users is large, the office assigns a
VAG (VAG 0) to this community for
better management. Therefore, the
MG interface ID is 0
Signaling port ID
of the MG
interface
The signaling port ID is 2944.
IP address of the
primary MGC to
which the MG
interface belongs
The service provider does not provide

dual homing for its network.
Port ID of the
primary MGC to
which the MG
interface belongs
Coding mode of
the MG interface
Issue 01 (2016-04-29)
According to the network topology,

the IP address of the primary MGC is
10.10.20.20, and the port ID is 2944,
the same as the port ID on the
MA5600T/MA5603T/MA5608T.
The text coding mode is adopted.

278

Access Module
Item
Data
Transmission
mode of the MG
interface
UDP is adopted.
Domain name of
the MG interface
The message ID (MID) adopts the IP

address (default), and may not be
configured with the domain name.
Digitmap of the MG interface
Special applications such as

emergency calls and emergency
standalone are not configured, and
therefore the digitmap is not
configured here.
Software parameters of the MG

interface
According to the Background

Information in (Optional) Configuring
the Software Parameters of an MG
Interface and confirmed with the
service provider, the default settings
can meet the service requirements.
Therefore, the software parameters are
not configured here.
Ringing mode of the MG

interface
Confirmed with the service provider,

the value of the ringing parameter
(corresponding to the users) defined
on the MGC is 0 (value of mgcpara),
and the users have no special
requirements for the ringing mode.
Therefore, the normal ringing with the
break-make ratio of 1:4 is adopted.
Terminal ID (TID) format of

the MG interface
To differentiate users according to the

TID, the service provider requires that
the terminal prefix uses the
community name huawei and the TID
is automatically generated by the
system according to the slot ID/
subrack ID/port ID of the user.
Run the display tid-template
command to query the default TID
template. It is found that default TID
template (template 6) can meet the
requirements.
VoIP user data

(The data
configuration
must be the
same as the
data
Issue 01 (2016-04-29)
Slot for the voice service board
User access is implemented by the

ASPB board in slot 0/3.

279

Access Module
Item
configuration
on the MGC.)
Data
User data
Phone number
The emergency standalone is not

supported, and therefore the
configuration of phone numbers is not
required when the users are added.
The MGC assigns phone numbers
83110000-83110031 to phones 0-31
respectively.
TID
The terminal layering is supported,

and therefore the manual allocation of
TIDs is not required.
User priority
The users are common users, and the

user priority uses the default cat3.
User type

users are of the default DEL type.
System parameters

the System Parameters and confirmed
with the service provider, the default
settings can meet the service
requirements. Therefore, the system
parameters are not configured here.
Overseas parameters

the Overseas Parameters and
confirmed with the service provider,
the default settings can meet the
service requirements. Therefore, the
overseas parameters are not
configured here.
PSTN port attributes
The polarity reversal accounting is

adopted, and therefore the PSTN port
to which the users belong needs to
support the polarity reversal pulse.
The other attributes of the PSTN port
do not need to be modified.
Ringing current attributes
There is no special requirement, and

the configuration of the ringing
current attributes is not required.
Procedure
Step 1 Add the upstream VLAN interface.
According to the data plan, configure standard VLAN 20 as the media and signaling upstream
VLAN, add upstream port 0/19/0 to the VLAN, and configure the IP address of the Layer 3
Issue 01 (2016-04-29)

280

Access Module
interface to 10.10.10.10, which facilitates the configuration of the media and signaling IP
address pools.

Add the IP address of the VLAN Layer 3 interface configured in the previous step to the
media and signaling IP address pools respectively, which facilitates the selection of media and
signaling IP addresses used for the services from the IP address pools. According to the data
plan, IP address 10.10.10.10 is added to the media and signaling IP address pools, and the
gateway IP address corresponding to the media IP address is 10.10.10.1.
huawei(config)#voip
NOTE
You can configure the attributes of the H248 or MG interface only when the media IP address and
the signaling IP address exist in the media and signaling IP address pools.
The media IP address and the signaling IP address can be different. You can plan the IP addresses
according to the actual network.

Add an MG interface to communicate with the MGC, which ensures that the MGC can
control the call connection through the MG interface. According to the data plan, add MG
interface 0, and configure the interface attributes.
huawei(config-if-h248-0)#if-h248 attribute mg-media-ip1 10.10.10.10 mgip
10.10.10.10 mgport 2944 primary-mgc-ip1 10.10.20.20
primary-mgc-port 2944 code text transfer udp
Step 4 Configure the ringing mapping of MG interface 0.

Configure the user ringing mode. According to the data plan, the break-make ratios of the
cadence ringing and the initial ringing are both 1:4. Therefore, the value of parameter cadence
is 0, and the value of parameter initialring is 4.
huawei(config-if-h248-0)#mg-ringmode add 0 0 4
Step 5 Configure the TID format of PSTN users on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix of PSTN
users needs to be huawei, and the TID template adopts layering template 6.
NOTICE
The MA5600T/MA5603T/MA5608T requires that the terminal prefixes of PSTN users, ISDN
BRA users, and ISDN PRA users on the same H.248 interface are either the same or different.
Note this when configuring the terminal prefix.
huawei(config-if-h248-0)#tid-format pstn prefix huawei template 6
Issue 01 (2016-04-29)

281

Access Module
Step 6 Enable the MG interface.

Reset the MG interface to make the MG interface register with the MGC (or to make the
attributes of the MG interface take effect), so that the MG interface can work in the normal
state. The MG interface can be enabled in different ways (see Parameters of the reset
command). For a newly configure MG interface, enable the MG interface through cold start.
Step 7 Query the running status of the MG interface.

After the MG interface is interconnected with the MGC, the MG interface should be in the
normal state, indicating that the MG interface can work in the normal state.
------------------------------------------------------------------------MGID
TransMode State
MGPort MGIP/DomainName MGCPort MGCIP/DomainName
------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.10
2944
10.10.20.20
-------------------------------------------------------------------------
Step 8 Confirm the service board.

Confirm the ASPB board that carries services to ensure that the board can work in the normal
state.
Step 9 Configure the PSTN user data.

Add POTS users (phones 0-31) to ensure that users can go online.
huawei(config)#esl user
huawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/31 0
huawei(config-esl-user)#quit
Step 10 Configure the polarity reversal accounting function.

Configure the physical attributes of the PSTN port to which the users belong to support the
polarity reversal pulse, so that the users can support the polarity reversal accounting.
huawei(config)#pstnport
huawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/31 reverse-pole-pulse
enable
huawei(config-pstnport)#quit

huawei(config)#save
----End
Result
After the interface data and the PSTN user data corresponding to the MG interface are
configured on the MGC, check whether the VoIP services can be provisioned normally. In the
normal state, phones 0-31 can make phone calls to each other:
l
The caller can hear the dial tone after picking up the phone.
When the caller dials the phone number of the callee, the phone of the callee can ring
normally, and the caller can hear the ring back tone.
Issue 01 (2016-04-29)

282

Access Module
The caller and the callee can communicate with each other successfully.
After the callee hangs up the phone, the caller can hear the busy tone.
Configuration File
The following describes the configuration file of this configuration example. Note that certain
steps must be performed manually and the configuration file cannot be imported directly.
Configure the upstream VLAN interface.
vlan 20 standard
port vlan 20 0/19 0
interface vlanif 20
ip address 10.10.10.10 24
quit
Configure the media and signaling IP address pools.

voip
ip address media 10.10.10.10 10.10.10.1
quit
Add an MG interface and configure the attributes of the MG interface. The MG interface must
be configured manually, and the configuration profile cannot be directly imported.
interface h248 0
if-h248 attribute mg-media-ip1 10.10.10.10 mgip 10.10.10.10 mgport 2944 primarymgc-ip1 10.10.20.20
Configure the ringing mapping of the MG interface.

mg-ringmode add 0 0 4
Configure the TID format of the PSTN user on the MG interface.

tid-format pstn prefix huawei template 6
Enable the MG interface. The MG interface must be enabled manually, and the configuration
profile cannot be directly imported.
reset coldstart
quit
Query the running status of the MG interface.

display if-h248 all
Confirm the service board.

board confirm 0/3
Configure the PSTN user data.

esl user
mgpstnuser batadd 0/3/0 0/3/31 0
quit
Configure the polarity reversal accounting function.

pstnport
pstnport attribute batset 0/3/0 0/3/31 reverse-pole-pulse enable
quit
Save the data.

Issue 01 (2016-04-29)

283

Access Module
save
3.3.2 Configuring the VoIP Service (MGCP)

This topic describes how to configure the MGCP-based VoIP service.
In an office located in China, the MA5600T/MA5603T/MA5608T that adopts the MGCP
MGC (softswitch) connected to the MA5600T/MA5603T/MA5608T. The MA5600T/
l
After the service requirements are further confirmed and analyzed with the service provider,
the data plan is made by considering the interconnection with the MGC and according to the
data plan described in Configuring the VoIP PSTN Service (H.248-based or MGCP-based).
Table 3-4 provides the data plan for configuring the MGCP-based VoIP service.
Table 3-4 Data plan for configuring the MGCP-based VoIP service
Item
MG interface
data
(The data
configuration
must be the
same as the
data
configuration
on the MGC.)
Issue 01 (2016-04-29)
Data
Media and
signaling
parameter
s
Media and
signaling
upstream VLAN

adopted.
Media and
signaling
upstream port

port of the VoIP service.
Media and
signaling IP
address

10.10.10.10/24.
Default IP address
of the gateway

service provider, the next hop IP
address from MA5600T/MA5603T/
MA5608T to the MGC is 10.10.10.1.
NOTICE
The MGCP interface on the MA5600T/
MA5603T/MA5608T does not support
the isolation of media streams and
signaling flows. Therefore, when the
MGCP protocol is used, the media IP
address pool and the signaling IP address
pool must be the same. When the H.248
or SIP protocol is used, the media IP
address pool and the signaling IP address
pool can be the same or different.

284

Access Module
Item
Data
Parameter
s of the
MG
interface
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
MG
interface
fails to be
enabled if
these
parameter
s are not
configure
d.
MG interface ID

service provider, the 32 users to be
provisioned with the services are the
first batch of users in the community
named huawei, and later other users
will be provisioned with the same
services gradually. The number of
users in this community is 10,000.
Considering that the number of users
is large, the service provider assigns a
VAG (VAG 0) to this community for
better management. Therefore, the
MG interface ID is 0.
Signaling port ID
of the MG
interface
The signaling port ID is 2727.
IP address of the
primary MGC to
which the MG
interface belongs
The service provider does not provide

dual homing for its network.
Port ID of the
primary MGC to
which the MG
interface belongs
Coding mode of
the MG interface
For the MG interface that supports

MGCP, the default coding mode is the
text coding mode. This parameter can
be queried, but cannot be configured.
Transmission
mode of the MG
interface
For the MG interface that supports

MGCP, the default transmission mode
is UDP. This parameter can be
queried, but cannot be configured.
Domain name of
the MG interface
The community name huawei is

adopted.
Digitmap of the MG interface
Issue 01 (2016-04-29)
According to the network topology,

the IP address of the primary MGC is
10.10.20.20, and the port ID is 2727,
MA5600T/MA5603T/MA5608T.
Special applications such as

emergency calls and emergency
standalone are not configured, and
therefore the digitmap is not
configured.

285

Access Module
Item
Data
Software parameters of the MG
interface

the Software Parameters of an MG
Interface and confirmed with the
service provider, the default settings
can meet the service requirements.
Therefore, the software parameters
are not configured here.
Ringing mode of the MG

interface
Confirmed with the service provider,

the value of the ringing parameter
(corresponding to the users) defined
on the MGC is 0 (value of mgcpara),
and the users have no special
requirements for the ringing mode.
Therefore, the normal ringing with the
break-make ratio of 1:4 is adopted.
Terminal ID (TID) format of

the MG interface

TID, the service provider requires that
the terminal prefix uses the
community name huawei and the TID
is automatically generated by the
system according to the slot ID/
subrack ID/port ID of the user.
template 6 can meet the requirements.
VoIP user data

(The data
configuration
must be the
same as the
data
configuration
on the MGC.)
Issue 01 (2016-04-29)
Slot of the voice service board

ASPB board in slot 0/3.
User data
MGCP does not support emergency

standalone, and therefore the phone
number does not need to be
configured when the user is added.
Phone number

83110000-83110031 to phones 0-31
respectively.
TID

and therefore the manual allocation of
TIDs is not required.
User priority

user priority uses default cat3.
User type

users are of the default DEL type.

286

Access Module
Item
Data
System parameters

the System Parameters and confirmed
with the service provider, the default
settings can meet the service
requirements. Therefore, the system
parameters are not configured here.
Overseas parameters

the Overseas Parameters and
confirmed with the service provider,
the default settings can meet the
service requirements. Therefore, the
overseas parameters are not
configured here.
The polarity reversal accounting is

adopted, and therefore the PSTN port
to which the users belong needs to
support the polarity reversal pulse.
The other attributes of the PSTN port
do not need to be modified.
There is no special requirement, and

the configuration of the ringing
current attributes is not required.
Figure 3-10 shows an example network for configuring the MGCP-based VoIP service.
Issue 01 (2016-04-29)

287

Access Module
Figure 3-10 Example network for configuring the MGCP-based VoIP service
Prerequisite
l

MGC must be configured to ensure that the MA5600T/MA5603T/MA5608T and the
MGC are reachable from each other.
NOTE
Issue 01 (2016-04-29)
The POTS service board, namely the ASPB board, must be inserted into the planned slot,
and the RUN ALM LED of the board must be green and must be on for 1s and off for 1s
repeatedly.

288

Access Module
Procedure
address pools.

According to the data plan, IP address 10.10.10.10 is added to the media and signaling IP
address pools, and the gateway IP address corresponding to the media IP address is
10.10.10.1.
huawei(config)#voip

control the call connection through the MG interface. According to the data plan, add MG
interface 0, and configure the interface attributes.
huawei(config)#interface mgcp 0
huawei(config-if-mgcp-0)#if-mgcp attribute mgip 10.10.10.10 mgport 2727 mgcip_1
10.10.20.20 mgcport_1 2727 domainName huawei
Step 4 Configure the ringing mapping of MG interface 0.

Configure the ringing mode of the MG interface. According to the data plan, the break-make
ratios of the cadence ringing and the initial ringing are both 1:4. Therefore, the value of
parameter cadence is 0, and the value of parameter initialring is 4.
huawei(config-if-mgcp-0)#mg-ringmode add 0 0 4
Step 5 Configure the TID format of PSTN users on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix of PSTN
users needs to be huawei, and the TID template adopts layering template 6.
huawei(config-if-mgcp-0)#tid-format pstn prefix huawei template 6
Step 6 Enable the MG interface.

Reset the MG interface to make the MG interface register with the MGC (or to make the
attributes of the MG interface take effect), so that the MG interface can work in the normal
state.
huawei(config-if-mgcp-0)#reset
huawei(config-if-mgcp-0)#quit
Step 7 Query the running status of the MG interface.

Issue 01 (2016-04-29)

289

Access Module
After the MG interface is interconnected with the MGC, the MG interface should be in the
normal state, indicating that the MG interface can work in the normal state.
huawei(config)#display if-mgcp all
-------------------------------------------------------------------------MGID
State
MGPort MGIP
-------------------------------------------------------------------------0
Normal
2727
10.10.10.10
2727
10.10.20.20
--------------------------------------------------------------------------

Add POTS users (phones 0-31) to ensure that users can go online.
Step 9 Configure the polarity reversal accounting function.

Configure the physical attributes of the PSTN port to which the users belong to support the
polarity reversal pulse, so that the users can support the polarity reversal accounting.
enable

huawei(config)#save
----End
Result
After the interface data and the PSTN user data corresponding to the MG interface are
configured on the MGC, check whether the VoIP services can be provisioned normally. In the
normal state, phones 0-31 can make phone calls to each other:
l
The caller can hear the dial tone after picking up the phone.
When the caller dials the phone number of the callee, the phone of the callee can ring
normally, and the caller can hear the ring back tone.
The caller and the callee can communicate with each other successfully.
After the callee hangs up the phone, the caller can hear the busy tone.
Configuration File
vlan 20 standard
port vlan 20 0/19 0
interface vlanif 20
ip address 10.10.10.10 24
quit

voip
ip address media 10.10.10.10 10.10.10.1
Issue 01 (2016-04-29)

290

Access Module

quit
Add an MG interface and configure the attributes of the MG interface. The MG interface must
be configured manually, and the configuration profile cannot be directly imported.
interface mgcp 0
if-mgcp attribute mgip 10.10.10.10 mgport 2727 mgcip_1 10.10.20.20 mgcport_1 2727
domainName huawei
Configure the ringing mapping of the MG interface.

mg-ringmode add 0 0 4
Configure the TID format of the PSTN user on the MG interface.

tid-format pstn prefix huawei template 6
quit
Enable the MG interface. The MG interface must be enabled manually, and the configuration
profile cannot be directly imported.
reset

display if-mgcp all

board confirm 0/3

esl user
mgpstnuser batadd 0/3/0 0/3/31 0
quit

pstnport
Save the data.

quit
save
3.3.3 Configuring the VoIP PSTN Service (SIP)

This topic describes the configuration example of the VoIP PSTN service based on sip
protocol.
In an office located in China, the MA5600T/MA5603T/MA5608T that adopts the SIP
IMS (softswitch) connected to the MA5600T/MA5603T/MA5608T. The MA5600T/
l
After the service requirements are further confirmed and analyzed with the office, the data
plan is made by considering the interconnection with the IMS and according to the data plan
Issue 01 (2016-04-29)

291

Access Module
described in Configuring the VoIP PSTN Service (SIP-based). Table 3-5 provides the data
plan for configuring the SIP-based VoIP service.
In this example, the device runs in China. The default configurations of system parameters
and the overseas feature parameters meet the standard and the application requirements.
Therefore, you do not need to configure these parameters.
Table 3-5 provides the data plan for configuring the VoIP PSTN service (SIP).
Table 3-5 Data plan for configuring the VoIP PSTN service (SIP)
Data
Item
SIP interface
data
(The data
configuration
on the SIP
interface must
be the same as
the data
configuration
on the IMS.)
Media and
signaling
parameter
s
Media and
signaling
upstream VLAN

adopted.
Media and
signaling
upstream port

transmitted upstream through the GIU
board. Therefore, port 0/19/0 is used
as the upstream port of the VoIP
service.
Media and
signaling IP
addresses
Next hop address from the MA5600T/

MA5603T/MA5608T to the IMS core
network device.
NOTICE
If the media IP address and the signaling
IP address are different and the media and
the signaling are transmitted upstream
through different gateways, ensure that
they correspond to correct gateways.
Otherwise, normal calls may not be made.
SIP
interface
(SIP)
The SIP interface

ID
Signaling port ID
of the SIP
interface
5060
IP address of the
primary
softswitch to
which the SIP
interface belongs
IP address: 10.10.10.20/24
Port ID of the
primary
softswitch to
which the SIP
interface belongs
Issue 01 (2016-04-29)
It is the SIP interface ID used for the

VoIP service to be configured, which
determines the virtual access gateway
(VAG) specified for the user.
Port ID: 5060

When dual homing is configured, the
IP address and the port ID of the
secondary softswitch must also be
configured.

292

Access Module
Item
Data
NOTE
The
parameter
s of the
SIP
interface
must be
the same
as the
parameter
s on the
softswitc
h. SIP has
many
negotiatio
n
parameter
s, and the
parameter
s here are
mandator
y.
VoIP user data

(The data
configuration
must be the
same as the
data
configuration
on the IMS.)
Transmission
mode of the SIP
interface
UDP
Home domain of
the SIP interface
huawei
Index of the
profile used by
the SIP interface
(optional)
Slots that the boards reside in

Voice service board (ASPB)
PSTN
user data
in slot 0/2
The transmission mode is selected

according to the requirements on the
softswitch. Generally, UDP is adopted.

ASPB board in slot 0/2, 0/3.
Numbers of
Phone 0-Phone
63
83110000-83110063
User priority
Phone 0: Cat2; Phone 1-Phone 63:

Cat3 (default)
User
authentication
PSTN user whose port is 0/2/0, and

telephone number is 83110000.
l Username: user83110000
l Password: password mode, value:
pwd83110000
PSTN
user data
in slot 0/3
Numbers of
Phone 64-Phone
127
88110000-88110063
User type
Payphone
PSTN port
attributes
Polarity reversal pulse supported
Figure 3-11 shows an example network of the VoIP PSTN service (SIP).
Issue 01 (2016-04-29)

293

Access Module
Figure 3-11 Example network for configuring the VoIP PSTN service (SIP)
Prerequisite
l

IMS must be configured to ensure that the MA5600T/MA5603T/MA5608T and the IMS
are reachable from each other.
NOTE
Procedure
address pools.
Issue 01 (2016-04-29)

294

Access Module

Add the IP address of the VLAN Layer 3 interface configured in the previous step to the
media and signaling IP address pools respectively, which facilitates the selection of media and
signaling IP addresses used for the services from the IP address pools. According to the data
plan, IP address 10.10.10.10 is added to the media and signaling IP address pools, and the
gateway IP address corresponding to the media IP address is 10.10.10.1.
huawei(config)#voip
NOTE
You can configure the attributes of the H248 or MG interface only when the media IP address and
the signaling IP address exist in the media and signaling IP address pools.
The media IP address and the signaling IP address can be different. You can plan the IP addresses
according to the actual network.
Step 3 Add an SIP interface.

Add an SIP interface to communicate with the IMS, which ensures that the IMS can control
the call connection through the SIP interface. According to the data plan, add SIP interface 0,
and configure the interface attributes.
l
Signaling/Media IP address: 10.10.10.10
Signaling port ID: 5060
Transfer mode: UDP
IP address of the primary IMS: 10.10.10.20
Signaling port ID of the primary IMS: 5060
Homing domain name of SIP interface: huawei
SIP profile ID: 1
Are you sure to add SIP interface?(y/n)[n]:y
huawei(config-if-sip-0)#if-sip attribute basic media-ip 10.10.10.10
signal-ip 10.10.10.10 signal-port 5060 transfer udp primary-proxy-ip1
10.10.10.20 primary-proxy-port
5060 home-domain huawei sipprofile-index 1
Step 4 Configure the ringing mapping of SIP interface 0.

Configure the user ringing mode. The break-make ratios of the cadence ringing and the initial
ringing are both 1:4. Therefore, the value of parameter cadence is 0, and the value of
parameter initialring is 4.
huawei(config-if-sip-0)#ringmode add 0 ringname cadencering 0 initialring 4
Step 5 Enable the SIP interface.

Reset the SIP interface to make the SIP interface register with the IMS (or to make the
attributes of the SIP interface take effect), so that the SIP interface can work in the normal
state.
Are you sure to reset the SIP interface?(y/n)[n]:y
Issue 01 (2016-04-29)

295

Access Module
Step 6 Query the running status of the SIP interface.

After the SIP interface is interconnected with the IMS, the SIP interface should be in the
normal state, indicating that the SIP interface can work in the normal state.
huawei>display if-sip all
-----------------------------------------------------------MGID
0
Transfer Mode
UDP
State
Normal
Signalling IP
192.168.0.170
Signalling Port
5068
Primary Proxy IP 1/DomainName
192.168.0.171
Primary Proxy Port
5060
Primary Proxy State
Up
Secondary Proxy IP 1/DomainName
192.168.0.172
Secondary Proxy Port
5061
Secondary Proxy State
Up
Current Proxy
Primary Proxy
------------------------------------------------------------
Step 7 Configure the PSTN subscriber data.

1.
Configure the PSTN user data (Phone 0-Phone 63) in slot 0/2.
huawei(config-esl-user)#sippstnuser batadd 0/2/0 0/2/63 0 telno 83110000
2.
Configure the calling priority of the PSTN user in port 0/2/0 as Cat2.
huawei(config-esl-user)#sippstnuser attribute set 0/2/0 priority cat2
3.
Configure the PSTN user data (Phone 64-Phone 127) in slot 0/3.
4.
Configure the authentication data of the PSTN user in port 0/2/0.

huawei(config-esl-user)#sippstnuser auth set 0/2/0 telno 83110000 passwordmode password
User Name(<=64 characters, "-" indicates deletion):user83110000
User Password(<=64 characters, "-" indicates deletion):
//Input the
password pwd8311000
NOTE
Considering users safety, the IMS may require user authentication. You can run the sippstnuser auth
set command to configure the user authentication data, including user name, password mode and
password. The authentication data should be consistent with that of IMS side.
5.
Configure the PSTN user type in slot 0/3.

huawei(config-esl-user)#sippstnuser attribute batset 0/3/0 0/3/63
potslinetype PayPhone
Step 8 Configure the PSTN port attributes.

Configure the PSTN port in slot 0/3 so that the port supports the polarity reversal.
enable

huawei(config)#save
----End
Issue 01 (2016-04-29)

296

Access Module
Result
After the interface data and the PSTN user data corresponding to the SIP interface are
configured on the IMS, check whether the VoIP services can be provisioned normally. In the
normal state, users of Phone 0-Phone 127 can communicate with each other successfully.
l
The calling party can hear the dialing tone after picking up the phone.
When the calling party dials the phone number of the called party, the phone of the
called party can ring normally, and the calling party can hear the ring-back tone.
The calling party and the called party can communicate in the normal state.
After the called party hooks on, the calling party can hear the busy tone.
Configuration File
vlan 20 standard
port vlan 20 0/19 0
interface vlanif 20
ip address 10.10.10.10 24
quit

voip
ip address media 10.10.10.10 10.10.10.1
Add an SIP interface and configure the attributes of the SIP interface.
if-sip attribute basic media-ip 10.10.10.10
signal-ip 10.10.10.10 signal-port 5060 transfer udp primary-proxy-ip1 10.10.10.20
primary-proxy-port 5060 home-domain huawei sipprofile-index 1
Configure the ringing mapping of the SIP interface.

ringmode add 0 ringname cadencering 0 initialring 4
Enable the SIP interface.

reset
quit
Query the running status of the SIP interface.

display if-sip all

board confirm 0/2
board confirm 0/3

esl user
sippstnuser
sippstnuser
sippstnuser
sippstnuser
sippstnuser
quit
Issue 01 (2016-04-29)
batadd 0/2/00/2/63 0 telno 83110000

attribute set 0/2/0 priority cat2
auth set 0/2/0 telno 83110000 password-mode password
batadd 0/3/0 0/3/63 0 telno 88110000
attribute batset 0/3/0 0/3/63 potslinetype PayPhone

297

Access Module

pstnport
quit
Save the data.

save
3.3.4 Configuring the VoIP Service (H.248 and SIP)

This topic describes an example for configuring the H.248-based and SIP-based VoIP service.
The MA5600T/MA5603T/MA5608T supports the H.248-based VoIP service and the SIPbased VoIP service at the same time.
l
The MA5600T/MA5603T/MA5608T upstream to NGN network for ISDN service by

adopting the H.248 protocol. The MA5600T/MA5603T/MA5608T upstream to IMS
network for PSTN service by adopting the SIP protocol.
ISDN Phone A is connected to the MA5600T/MA5603T/MA5608T through the NT1,

and the ISDN digital phone supports the P2P function.
Basic rate interface (BRI) is adopted between the NT1 and the MA5600T/MA5603T/
MA5608T to provide a rate of 144 kbit/s, including two B channels and one D channel.
The Phone B and Phone C are PSTN users, the user priority is Cat2.
After the configuration is completed, normal calls can be made between two phone sets.
Figure 3-12 shows an example network of the VoIP service that based the SIP protocol and
H.248 protocol.
Issue 01 (2016-04-29)

298

Access Module
Figure 3-12 the network of the VoIP service that based the SIP protocol and H.248 protocol.
MGC
IMS
Router
H.248
SIP
Access node
NT1
ISDN phone A
PSTN phone B
PSTN phone C
Prerequisite
l
The MA5600T/MA5603T must use the H.248 protocol to communicate with the MGC
and use the SIP protocol to communicate with the IMS.
The H.248 interface and the system parameters must be configured. For the related
operations, see Configuring an MG Interface and (Optional) Configuring the System
Parameters. The H.248 interface must be in the normal state.
The SIP interface and the system parameters must be configured. For the related
operations, see Configuring an SIP Interface and (Optional) Configuring the System
Parameters. The SIP interface must be in the normal state.
The system must be configured with the ISDN service board, that is, the DSRD board or
DSRE board.
Issue 01 (2016-04-29)

299

Access Module
The system must be configured with the PSTN service board, that is, the ASRB board or
ASPB board.
The ISDN digital phone must support the P2P function.
The terminal endpoint identifier of the ISDN digital phone must be 0.
Data Plan
Table 3-6 provides the data plan .
Table 3-6 Data plan
Data
Item
The data plan of the ISDN BRA service based H.248 protocol
H.248 interface ID
IUA link set
parameter
IUA link
parameter
Issue 01 (2016-04-29)
0
IUA link set ID
Working mode
of a link set
override
Pending time
10s
Mode of
generating the
interface ID
Whether the
link in the link
set supports the
interlocking
enable
Service
environment
corresponding
to the IUA link
set
client
IUA link ID
15
Local port ID
1401
Local IP
address
10.13.4.116/16 (It must exist in the signaling IP

address pool.)
Remote port ID
1400
IP address of
the primary
MGC
10.14.1.2/16 (IP address of the primary MGC)
MGC that is
bound to the
IUA link
primary-mgc

300

Access Module
Item
Data
ISDN BRA port
Priority of the
IUA link.
Subrack ID/
Slot ID/Port ID
0/2/0
IUA interface
ID
Working mode
P2P
TID
100, 110
Phone number
12345601, 12345602
Automatic
deactivation
Disabled
Activation
mode
Stable activation
The data plan of the PSTN service based SIP protocol

SIP interface ID
PSTN port
(The data
configuration
must be the same
as the data
configuration on
the IMS.)
0
Frame/slot/port
0/3/0, 0/3/1.
Numbers of
Phone
83110000, 83110001
User priority
Cat2
User type
Payphone
PSTN port
attributes
Polarity reversal pulse supported
Procedure
l
Configure the H.248-based ISDN service

a.
Configure the working mode of the ISDN BRA port.

In the BRA port mode, configure the working mode of the ISDN BRA port to P2P,
configure the activation mode to stable activation, and disable automatic activation.
huawei(config)#braport
huawei(config-braport)#braport attribute set 0/2/0 workmode p2p
activemode stable-active autodeactive disable
huawei(config-braport)#quit
b.
Add an IUA link set and IUA links.

In the SIGTRAN mode, configure the SIGTRAN protocol stack. Add an IUA link
set, and then add IUA links.
huawei(config)#sigtran
huawei(config-sigtran)#iua-linkset add 1 mgid 0 jointly-work enable
trafficmode override
iid-map 2 pendingtime 1 cs-mode client
Issue 01 (2016-04-29)

301

Access Module
huawei(config-sigtran)#iua-link add 15 1 1401 10.13.4.116 1400 10.14.1.2

jointly-work-with primary-mgc priority 3
huawei(config-sigtran)#quit
NOTE
All the ISDN call control messages are sent from the IUA link to the softswitch, whereas the
system uses the bearer control messages to communicate with the softswitch through H.248.
c.
Configure the ISDN BRA user data.

huawei(config-esl-user)#mgbrauser add 0/2/0 0 1 interfaceid 8 terminalid
100 telno 12345601
NOTICE
Each ISDN BRA user occupies two TIDs. You need to input only the first TID
when adding an ISDN BRA user.
l When the TID profile to which the ISDN BRA user of the MG interface is
bound is not a layering profile, the TID must be configured and must differ from
the TID of the existing ISDN BRA user by an integer multiple of 2.
l When the TID profile to which the ISDN BRA user of the MG interface is
bound is a layering profile, the configuration of the TID is optional because the
system automatically allocates the TID.
l
Configure the SIP-based PSTN service

a.
Add the ASPB service board.

According to the data plan, add a ASPB board to slot0/3.
huawei(config)#board add 0/3 ASP
b.
Configure the PSTN subscriber data.

According to the data plan, configure a telephone number and priority of the PSTN
user.
c.
Configure the PSTN port attributes.

huawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/1 reversepole-pulse enable
d.
Save the data.

huawei(config)#save
----End
Result
After the configuration is completed, users of ports 0/2/0, 0/3/0, and 0/3/1 can call each other
successfully.
Issue 01 (2016-04-29)

302

Access Module
Configuration File
board add 0/2 H802DSRD
board confirm 0/2
braport
braport attribute set 0/2/0 workmode p2p activemode stable-active autodeactive
disable
quit
sigtran
iua-linkset add 1 mgid 0 jointly-work enable trafficmode override
iid-map 2 pendingtime 1 cs-mode client
iua-link add 15 1 1401 10.13.4.116 1400 10.14.1.2
quit
esl user
mgbrauser add 0/2/0 0 1 interfaceid 8 terminalid 100 telno 12345601
quit
board add 0/3 ASP
board confirm 0/3
esl user
sippstnuser batadd 0/3/00/3/1 0 telno 83110000
sippstnuser attribute set 0/3/0 priority cat2
sippstnuser attribute set 0/3/1 priority cat2
quit
pstnport
quit
save
3.3.5 Configuring the P2P ISDN BRA Service

This topic describes how to configure the P2P ISDN BRA service on the MA5600T/
MA5603T/MA5608T, which is applicable to the scenario where one NT1 is connected to only
one terminal.
l

ISDN Phone B is connected to the MA5600T/MA5603T/MA5608T through the NT1,

Figure 3-13 shows an example network of the P2P ISDN BRA service.
Issue 01 (2016-04-29)

303

Access Module
Figure 3-13 Example network of the P2P ISDN BRA service
Prerequisite
l
The MG interface and the system parameters must be configured. For the related
Parameters. The MG interface must be in the normal state.
The system must be configured with the ISDN service board, that is, the DSRD or DSRE
board.
Data Plan
Table 3-7 provides the data plan for configuring the P2P ISDN BRA service.
Table 3-7 Data plan for configuring the P2P ISDN BRA service
Item
Data
MG interface ID
IUA link set

parameter
Issue 01 (2016-04-29)
IUA link set ID

304

Access Module
Item
Data
IUA link
parameter
ISDN BRA port
Issue 01 (2016-04-29)
Working mode
of a link set
override
Pending time
10s
Mode of
generating the
interface ID
Whether the
link in the link
set supports the
interlocking
enable
Service
environment
corresponding
to the IUA link
set
client
IUA link ID
15
Local port ID
1401
Local IP
address

address pool.)
Remote port ID
1400
IP address of
the primary
MGC
MGC that is
bound to the
IUA link
primary-mgc
Priority of the
IUA link.
IP address of
the primary
MGC
Subrack ID/
Slot ID/Port ID
0/2/0, 0/3/0
IUA interface
ID
8, 9
Working mode
P2P
TID
100, 110
Phone number
12345601, 12345602

305

Access Module
Item
Data
Automatic
deactivation
Disabled
Activation
mode
Stable activation
Procedure
Step 1 Configure the working mode of the ISDN BRA port.
In the BRA port mode, configure the working mode of the ISDN BRA port to P2P, configure
the activation mode to stable activation, and disable automatic activation.
huawei(config-braport)#braport attribute set 0/2/0 workmode p2p activemode stableactive autodeactive disable
Step 2 Add an IUA link set and IUA links.

In the SIGTRAN mode, configure the SIGTRAN protocol stack. Add an IUA link set, and
then add IUA links.
huawei(config-sigtran)#iua-linkset add 1 mgid 0 jointly-work enable trafficmode
override
iid-map 2 pendingtime cs-mode client
NOTE
All the ISDN call control messages are sent from the IUA link to the softswitch, whereas the system
uses the bearer control messages to communicate with the softswitch through H.248.
Step 3 Configure the ISDN BRA user data.

huawei(config-esl-user)#mgbrauser add 0/2/0 0 1 interfaceid 8 terminalid 100
telno 12345601
telno 12345602
NOTICE
Each ISDN BRA user occupies two TIDs. You need to input only the first TID when adding
an ISDN BRA user.
l When the TID profile to which the ISDN BRA user of the MG interface is bound is not a
layering profile, the TID must be configured and must differ from the TID of the existing
ISDN BRA user by an integer multiple of 2.
l When the TID profile to which the ISDN BRA user of the MG interface is bound is a
layering profile, the configuration of the TID is optional because the system automatically
allocates the TID.
Issue 01 (2016-04-29)

306

Access Module

huawei(config)#save
----End
Result
After the configuration is completed, two ISDN BRA users of ports 0/2/0 and 0/3/0 can call
each other successfully.
Configuration File
board confirm 0/2
board confirm 0/3
braport
disable
disable
quit
sigtran
iua-link add 15 1 1401 10.13.4.116 1400 10.14.1.2
jointly-work-with primary-mgc priority 3quit
esl user
quit
save
3.3.6 Configuring the P2P ISDN BRA Service (SIP)

This topic describes how to configure the P2P ISDN BRA service on the MA5600T/
MA5603T/MA5608T, which is applicable to the scenario where one NT1 is connected to only
one terminal.
l

ISDN Phone B is connected to the MA5600T/MA5603T/MA5608T through the NT1,

Figure 3-14 shows an example network of the P2P ISDN BRA service.
Issue 01 (2016-04-29)

307

Access Module
Figure 3-14 Example network of the P2P ISDN BRA service
Prerequisite
l
The MA5600T/MA5603T/MA5608T must use the SIP protocol to communicate with the
IMS.
the DSRE board .
Data Plan
Table 3-8 provides the data plan for configuring the P2P ISDN BRA service.
Table 3-8 Data plan for configuring the P2P ISDN BRA service
Issue 01 (2016-04-29)
Item
Data
MG interface ID

308

Access Module
Item
Data
ISDN BRA port
Subrack ID/
Slot ID/Port ID
0/2/0, 0/3/0
Working mode
P2P
Phone number
12345601, 12345602
Automatic
deactivation
Disabled
Activation
mode
Stable activation
Procedure
In the BRA port mode, configure the working mode of the ISDN BRA port to P2P, configure
the activation mode to stable activation, and disable automatic activation.

huawei(config-esl-user)#sipbrauser add 0/2/0 0 telno 12345601

huawei(config)#save
----End
Result
After the configuration is completed, two ISDN BRA users of ports 0/2/0 and 0/3/0 can call
each other successfully.
Configuration File
braport
disable
disable
quit
esl user
sipbrauser add 0/2/0 0 telno 12345601
quit
save
Issue 01 (2016-04-29)

309

Access Module
3.3.7 Configuring the P2MP ISDN BRA Service

This topic describes how to configure the P2MP ISDN BRA service on the MA5600T/
MA5603T/MA5608T, which is applicable to the scenario where one NT1 is connected to
multiple terminals.
l
Two ISDN digital phones are connected to the MA5600T/MA5603T/MA5608T through

the same NT1.
Prerequisite
Networking
Figure 3-15 shows an example network of the P2MP ISDN BRA service.
Figure 3-15 Example network of the P2MP ISDN BRA service
Issue 01 (2016-04-29)

310

Access Module
Data Plan
Table 3-9 provides the data plan for configuring the P2MP ISDN BRA service.
Table 3-9 Data plan for the P2MP ISDN BRA service
Item
Data
MG interface ID
IUA link set

parameter
IUA link
parameter
ISDN BRA port
Issue 01 (2016-04-29)
IUA link set ID
Working mode of
a link set
override
Pending time
10s
Mode of
generating the
interface ID
Whether the link

in the link set
supports the
interlocking
enable
Service
environment
corresponding to
the IUA link set
client
IUA link ID
15
Local port ID
1401
Local IP address

address pool.)
Remote port ID
1400
IP address of the
primary MGC
MGC that is
bound to the IUA
link
primary-mgc
Priority of the
IUA link.
IP address of the
primary MGC
Subrack ID/Slot
ID/Port ID
0/3/1
IUA interface ID
10

311

Access Module
Item
Data
Working mode
P2MP
TID
106
Phone number
88880000
Procedure
In the BRA port mode, configure the working mode of the ISDN BRA port to P2MP,
configure the activation mode to stable activation, and enable automatic activation.
huawei(config-braport)#braport attribute set 0/3/1 workmode p2mp autodeactive
enable

then add IUA links.
override

telno 88880000

huawei(config)#save
----End
Result
After the configuration is completed, two ISDN BRA users of the NT1 connected to port
0/3/1 can make calls successfully.
Configuration File
braport
braport attribute set 0/3/1 workmode p2mp autodeactive enable
quit
sigtran
iua-link add 15 1 1401 10.13.4.116 1400 10.14.1.2
quit
esl user
Issue 01 (2016-04-29)

312

Access Module
mgbrauser add 0/3/1 0 1 interfaceid 10 terminalid 106

quit
save
telno 88880000
3.3.8 Configuring the P2MP ISDN BRA Service (SIP)

This topic describes how to configure the P2MP ISDN BRA service on the MA5600T/
MA5603T/MA5608T, which is applicable to the scenario where one NT1 is connected to
multiple terminals.
l
Two ISDN digital phones are connected to the MA5600T/MA5603T/MA5608T through

the same NT1.
Normal calls can be made on both phones.
IMS.
the DSRE board .
Prerequisite
Networking
Figure 3-16 shows an example network of the P2MP ISDN BRA service.
Issue 01 (2016-04-29)

313

Access Module
Figure 3-16 Example network of the P2MP ISDN BRA service
Data Plan
Table 3-10 provides the data plan for configuring the P2MP ISDN BRA service.
Table 3-10 Data plan for the P2MP ISDN BRA service
Item
Data
MG interface ID
ISDN BRA port
Subrack ID/Slot
ID/Port ID
0/3/1
Working mode
P2MP
Phone number
88880000
Procedure
In the BRA port mode, configure the working mode of the ISDN BRA port to P2MP,
configure the activation mode to stable activation, and enable automatic activation.
Issue 01 (2016-04-29)

314

Access Module
huawei(config-braport)#braport attribute set 0/3/1 workmode p2mp autodeactive

enable


huawei(config)#save
----End
Result
After the configuration is completed, two ISDN BRA users of the NT1 connected to port
0/3/1 can make calls successfully.
Configuration File
braport
braport attribute set 0/3/1 workmode p2mp autodeactive enable
quit
esl user
quit
save
3.3.9 Configuring the ISDN PRA Service

This topic is applicable to the scenario where the ISDN users are connected to the MA5600T/
MA5603T/MA5608T through the ISDN primary rate interface (PRI).
Prerequisite
l
The PSTN user (Phone B in the example network) must be configured and can
communicate with other users in the normal state. For the configuration method, see
3.3.1 Configuring the VoIP Service (H.248).
Users of the PBX must be configured and can communicate with each other in the
normal state.
The system must be configured with the EDTB board.
l
The PBX is connected to the MA5600T/MA5603T/MA5608T through the ISDN PRI.

PRI supports a data rate of 2048 kbit/s, including 30 B channels and one D channel. The
rate of both the B channel and the D channel is 64 kbit/s.
After the configuration is completed, users of the PBX can make calls successfully and
can communicate with users outside the PBX in the normal state.
Networking
Figure 3-17 shows an example of the ISDN PRA service.
Issue 01 (2016-04-29)

315

Access Module
Figure 3-17 Example of the ISDN PRA service
Data Plan
Table 3-11 provides the data plan for configuring the ISDN PRA service.
Table 3-11 Data plan for configuring the ISDN PRA service
Item
Data
MG interface ID
IUA link set

parameter
Issue 01 (2016-04-29)
IUA link set ID
Working mode of
a link set
override
Pending time
10s
Mode of
generating the
interface ID

316

Access Module
Item
Data
IUA link parameter
ISDN PRA port
Whether the link

in the link set
supports the
interlocking
enable
Service
environment
corresponding to
the IUA link set
client
IUA link ID
15
Local port ID
1401
Local IP address
10.13.4.116/16 (It must exist in the signaling

IP address pool.)
Remote port ID
1400
IP address of the
primary MGC
10.14.1.2/16 (IP address of the primary

MGC)
MGC that is
bound to the IUA
link
primary-mgc
Priority of the IUA

link.
IP address of the
primary MGC
10.14.1.2/16 (IP address of the primary

MGC)
Subrack ID/Slot
ID/Port ID
0/2/0
IUA interface ID
TID
512
Procedure
Step 1 Add the EDTB board.
According to the data plan, add an ISDN PRA service board to slot 0/2.
huawei(config)#board add 0/2 h802EDTB

then add IUA links.
override
Issue 01 (2016-04-29)

317

Access Module
NOTE
Step 3 Configure the ISDN PRA user data.

huawei(config-esl-user)#mgprauser add 0/2/0 0 1 interfaceid 1 terminalid 512
NOTICE
Each ISDN PRA user occupies 32 TIDs. You need to input only the first TID when adding an
ISDN PRA user.
l When the TID profile to which the ISDN PRA user of the MG interface is bound is not a
layering profile, the TID must be configured and cannot be within the configured TID
range.
l When the TID profile to which the ISDN PRA user of the MG interface is bound is a
layering profile, the configuration of the TID parameter is not available because the
system automatically allocates the TID.
huawei(config)#save
----End
Result
After the configuration is completed, all the users of the PBX can communicate with Phone B
in the normal state.
Configuration File
board add 0/2 h802EDTB
sigtran
iua-link add 15 1 1401 10.13.4.116 1400 10.14.1.2
quit
esl user
mgprauser add 0/2/0 0 1 interfaceid 1 terminalid 512
quit
save
3.3.10 Configuring the ISDN PRA Service (SIP)

This topic is applicable to the scenario where the ISDN users are connected to the MA5600T/
MA5603T/MA5608T through the ISDN primary rate interface (PRI).
Prerequisite
l
Issue 01 (2016-04-29)
IMS.
318

Access Module
The PSTN user (Phone B in the example network) must be configured and can
communicate with other users in the normal state. For the configuration method, see
3.3.3 Configuring the VoIP PSTN Service (SIP).
Users of the PBX must be configured and can communicate with each other in the
normal state.
The system must be configured with the EDTB board.
l
The PBX is connected to the MA5600T/MA5603T/MA5608T through the ISDN PRI.

PRI supports a data rate of 2048 kbit/s, including 30 B channels and one D channel. The
rate of both the B channel and the D channel is 64 kbit/s.
After the configuration is completed, users of the PBX can make calls successfully and
can communicate with users outside the PBX in the normal state.
Networking
Figure 3-18 shows an example of the ISDN PRA service.
Figure 3-18 Example of the ISDN PRA service
Issue 01 (2016-04-29)

319

Access Module
Data Plan
Table 3-12 provides the data plan for configuring the ISDN PRA service.
Table 3-12 Data plan for configuring the ISDN PRA service
Item
Data
MG interface ID
ISDN PRA port
Subrack ID/Slot
ID/Port ID
0/2/0
Phone number
12345600
Procedure
Step 1 Configure the ISDN PRA user data.
huawei(config-esl-user)#sipprauser add 0/2/0 0 telno 12345600

huawei(config)#save
----End
Result
After the configuration is completed, all the users of the PBX can communicate with Phone B
Configuration File
board add 0/2 H802EDTB
board confirm 0/2 H802EDTB
esl user
sipprauser add 0/2/0 0 telno 12345600
quit
save
3.3.11 Configuring TDM SHDSL for Carrying the PRA Service (H.
248)
The MA5600T/MA5603T/MA5608T is connected to the PBX in the TDM SHDSL mode and
then connected upstream to the IP network in the GE mode.
l
The PBX is connected to the IP network over a long distance to carry the PRA service.
The user interface data is transparently transmitted on the MA5600T/MA5603T/

MA5608T.
The following figure shows an example network of TDM SHDSL for carrying the PRA
service.
Issue 01 (2016-04-29)

320

Access Module
Figure 3-19 Example network of TDM SHDSL for carrying the PRA service
Data Plan
The following table lists the data plan for configuring TDM SHDSL for carrying the PRA
service.
Table 3-13 Data plan for configuring TDM SHDSL for carrying the PRA service
Item
Data
Clock source
E1 line clock on port 0/3/0
SHDSL port
Port ID: 0/3/16
IUA link set

parameter
IUA link parameter
Issue 01 (2016-04-29)
IUA link set ID
Working mode of a
link set
override
Pending time
10s
Mode of generating
the interface ID
Whether the link in

the link set supports
the interlocking
enable
Service
environment
corresponding to
the IUA link set
client
IUA link ID
15
Local port ID
1401
Local IP address
10.13.4.116/16 (It must exist in the signaling

IP address pool.)
Remote port ID
1400
IP address of the
primary MGC

321

Access Module
Item
Data
MGC that is bound
to the IUA link
primary-mgc
Priority of the IUA

link
IP address of the
primary MGC
PRA user interface data
MGID: 0
IUA link set ID: 0
Terminal ID: 0
Prerequisite
l
The H802EDTB board must be in position and must work in the normal state.
An MG interface must be created and must communicate with the MGC in the normal
state.
An SHDSL modem must be correctly connected and the SHDSL port(s) must be
activated.
Procedure
Step 1 (Optional) Configure the working mode of the board
Configure the working mode of the board to voice.
NOTE
The working sub-mode of the board can be configured only when the working mode of the board is
configured to voice. By default, the working mode of the board is voice.
huawei(config)#interface edt 0/3
huawei(config-edt-0/3)#board workmode voice
Step 2 (Optional) Configure the working sub-mode of the board.

According to the service requirement, configure the working sub-mode of the board to service
mode. By default, the working sub-mode of the board is service.
huawei(config-edt-0/3)#runmode service
Step 3 (Optional) Configure the clock source of the board.

Configure the E1 line clock on port 0/3/0 as the clock source.
NOTE
You can select the line clock or system clock as the clock source of the board according to your requirements.
By default, the system clock is used as the clock source.
huawei(config-edt-0/3)#set clockmode system
Step 4 Configure the attributes of the SHDSL port.

Configure the signaling mode of SHDSL port 0/3/16 to CCS. PRA D channel signaling is
transmitted in timeslot 16 and timeslot 0 is used for frame synchronization.
huawei(config-edt-0/3)#shdslport signal 16 CCS
huawei(config-edt-0/3)#quit
Issue 01 (2016-04-29)

322

Access Module

then add IUA links.
override
NOTE
Step 6 Configure a PRA user.

huawei(config-esl-user)#mgprauser add 0/3/16 0 0 terminalid 0

huawei(config)#save
----End
Result
The phone set connected to the PBX can communicate with a phone set in the PSTN network
Configuration File
interface edt 0/3
board workmode voice
runmode service
set clockmode system
shdslport signal 16 CCS
quit
override
esl user
mgprauser add 0/3/16 0 0 terminalid 0
quit
save
3.3.12 Configuring TDM SHDSL for Carrying the PRA Service

(SIP)
The MA5600T/MA5603T/MA5608T is connected to the PBX in the TDM SHDSL mode and
then connected upstream to the IP network in the GE mode.
l
The PBX is connected to the IP network over a long distance to carry the PRA service.
The configuration data is transparently transmitted on the MA5600T/MA5603T/

MA5608T.
Issue 01 (2016-04-29)

323

Access Module
The following figure shows an example network of TDM SHDSL for carrying the PRA
service.
Figure 3-20 Example network of TDM SHDSL for carrying the PRA service
Data Plan
The following table lists the data plan for configuring TDM SHDSL for carrying the PRA
service.
Table 3-14 Data plan for configuring TDM SHDSL for carrying the PRA service
Item
Data
Clock source
E1 line clock on port 0/3/0
SHDSL port
Port ID: 0/3/16
PRA user interface data
MGID: 0
IUA link set ID: 0
Terminal ID: 0
Phone number: 12345600
Prerequisite
l
IMS in the normao state.
activated.
Procedure
Step 1 (Optional) Configure the working mode of the board
NOTE
Issue 01 (2016-04-29)

324

Access Module

Step 2 (Optional) Configure the working sub-mode of the board.

According to the service requirement, configure the working sub-mode of the board to service
mode. By default, the working sub-mode of the board is service.
Step 3 (Optional) Configure the clock source of the board.

Configure the E1 line clock on port 0/3/0 as the clock source.
NOTE
You can select the line clock or system clock as the clock source of the board according to your requirements.
By default, the system clock is used as the clock source.
huawei(config-edt-0/3)#set clockmode system

Configure the signaling mode of SHDSL port 0/3/16 to CCS. PRA D channel signaling is
transmitted in timeslot 16 and timeslot 0 is used for frame synchronization.
huawei(config-edt-0/3)#shdslport signal 16 CCS
Step 5 Configure a PRA user.

huawei(config-esl-user)#sipprauser add 0/3/16 0 telno 12345600

huawei(config)#save
----End
Result
The phone set connected to the PBX can communicate with a phone set in the PSTN network
Configuration File
interface edt 0/3
runmode service
set clockmode system
shdslport signal 16 CCS
quit
esl user
sipprauser add 0/3/16 0 telno 12345600
quit
save
3.3.13 Configuring VAGs

The purpose of configuring virtual access gateways (VAGs) is to simulate multiple AGs by
using one AG, increasing the usage rate and flexibility of the device.
Configuring the VAG Service (H.248/MGCP)

This topic describes how to configure the VAG service by creating two MG interfaces on the
MA5600T/MA5603T/MA5608T and configuring PSTN users on the two MG interfaces. This
Issue 01 (2016-04-29)

325

Access Module
topic is applicable to the scenario where multiple logical AGs are simulated on one physical
AG.
Context
Configuring VAGs is literally to configure MG interfaces with different IDs on the same
device, and to configure user ports homing to different MG interfaces. Pay attention to the
following points:
l
When the system uses the MGCP or H.248 protocol, up to eight MG interfaces with
different IDs can be configured on the MA5600T/MA5603T/MA5608T, and each MG
interface can be considered as a VAG.
When configuring the parameters for interconnecting different MG interfaces with the
MGC, make sure that the values of the following parameters of the MG interfaces are not
the same. The values of at least one of the following parameters must be different on the
MG interfaces.
Local IP address
Local port ID
Remote IP address
Remote port ID
The service requirements are as follows:
l
As shown in Figure 3-21, configure VAG1, and configure the users in slot 0/2 to belong
to VAG1; configure VAG2, and configure the users in slot 0/3 to belong to VAG2.
The MG communicates with the MGC through the H.248 protocol.
Configure the data plan of VAG1 as listed in Table 3-15.
The data plan of VAG2 is the same as that of VAG1 except for the following differences:
The media IP address and signaling IP address of VAG2 are 10.10.10.11.
The MGC assigns phone numbers 85110000-85110031 to phones 0-31 of VAG2.
MG0 indicates VAG1 in the figure, and MG1 indicates VAG2 in the figure.
Networking
Figure 3-21 shows an example network of the VAG service.
Issue 01 (2016-04-29)

326

Access Module
Figure 3-21 Example network of the VAG service
Dataplan
Table 3-15 Data plan of VAG1
Item
MG interface
data
(The data
configuration
must be the
same as the
data
configuration
on the MGC.)
Issue 01 (2016-04-29)
Data
Media and
signaling
parameter
s
Media and
signaling
upstream VLAN

the upstream VLAN of the voice
adopted.
Media and
signaling
upstream port

port of the voice service.
Media IP address
and signaling IP
addresses

10.10.10.10.
Default gateway
IP address
The IP address of the next hop from

the MA5600T/MA5603T/MA5608T
to the MGC is 10.10.10.1.

327

Access Module
Item
Data
Attributes
of the MG
interface
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
MG
interface
fails to be
enabled if
these
parameter
s are not
configure
d.
MG interface ID
0 and 1
Signaling port ID
of the MG
interface
2944
IP address of the
primary MGC to
which the MG
interface belongs
The IP address of the primary MGC is

10.10.20.20, and the port ID is 2944,
MA5600T/MA5603T/MA5608T.
Port ID of the
primary MGC to
which the MG
interface belongs
Coding mode of
the MG interface
text (indicates the text coding mode)
Transmission
mode of the MG
interface
UDP
(Optional) Configuring the

TID Format of an MG
Interface

TID, the office requires that the
terminal prefix uses the community
name huawei and the TID is
automatically generated by the system
according to the subrack ID/slot ID/
port ID (F/S/P) of the user.
template (template 6) can meet the
requirements.
Voice user data
(The data
configuration
must be the
same as the
data
configuration
on the MGC.)

ASPB board in slot 0/2 and 0/3.
Configuri
ng the
PSTN
User Data
The emergency standalone is not

supported, and therefore the phone
numbers do not need to be configured
when the users are added.
Phone number

83110000-83110031 to phones 0-31.
TID
Issue 01 (2016-04-29)

and therefore the TIDs do not need to
be allocated manually.

328

Access Module
Procedure
l
Configure VAG1.
a.
Add the upstream VLAN interface.

According to the data plan, configure standard VLAN 20 as the media and signaling
upstream VLAN, add upstream port 0/19/0 to the VLAN, and configure the IP
address of the Layer 3 interface to 10.10.10.10, which facilitates the configuration
of the media and signaling IP address pools.
b.

Add the IP address of the VLAN Layer 3 interface configured in the previous step
to the media and signaling IP address pools respectively. Therefore, the media and
signaling IP addresses used for the services can be selected from the IP address
pools. According to the data plan, IP address 10.10.10.10 is added to the media and
signaling IP address pools, and the gateway IP address corresponding to the media
IP address is 10.10.10.1.
huawei(config)#voip
c.
Add an MG interface.
Add an MG interface for the MG to communicate with the MGC, which ensures
that the MGC can control the call connection through the MG interface. According
to the data plan, add MG interface 0, and configure the interface attributes.
d.
Configure the TID template of the PSTN users on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix
of PSTN users is huawei, and the TID template adopts layering template 6.
NOTICE
The MA5600T/MA5603T/MA5608T requires that the terminal prefixes of PSTN
users, ISDN BRA users, and ISDN PRA users on the same H.248 interface be either
the same or different. Note this when configuring the terminal prefix.
e.
Reset the MG interface.

Reset the MG interface to make the MG interface register with the MGC (and to
make the modified attributes of the MG interface take effect) so that the MG
interface can work in the normal state. The MG interface can be started in different
Issue 01 (2016-04-29)

329

Access Module
ways (see Parameters of the reset command). For a newly configured MG interface,
enable the MG interface through cold start.
f.

After the MG interface is interconnected with the MGC, the MG interface should be
in the normal state, indicating that the MG interface works in the normal state.
----------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
MGCPort MGCIP/
DomainName
----------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.10
2944
10.10.20.20
-----------------------------------------------------------------------------
g.

Confirm the ASPB service board that carries services so that the board can work in
the normal state.
h.

Add POTS users (phones 0-31) so that the users can go online.
i.
Save the data.

huawei(config)#save
Configure VAG2.
a.

According to the data plan, configure the secondary IP address of the Layer 3
interface to 10.10.10.11, which facilitates the configuration of the media and
signaling IP address pools.
In step a, the VLAN is added and the IP address of the VLAN Layer 3 interface is
configured. In this step, use the sub parameter to configure the secondary IP address
of the VLAN. The secondary IP address is the same as the primary IP address in
function. They are used for Layer 3 forwarding.
huawei(config-if-vlanif20)#ip address 10.10.10.11 24 sub
b.

Issue 01 (2016-04-29)

330

Access Module
huawei(config)#voip
c.
Add an MG interface for the MG to communicate with the MGC, which ensures
that the MGC can control the call connection through the MG interface. According
to the data plan, add MG interface 1, and configure the interface attributes.
d.
Configure the TID template of the PSTN users on MG interface 1.

Configure the TID generation mode. According to the data plan, the terminal prefix
of PSTN users is huawei, and the TID template adopts layering template 6.
NOTICE
The MA5600T/MA5603T/MA5608T requires that the terminal prefixes of PSTN
users, ISDN BRA users, and ISDN PRA users on the same H.248 interface be either
the same or different. Note this when configuring the terminal prefix.
e.

Reset the MG interface to make the MG interface register with the MGC (and to
make the modified attributes of the MG interface take effect) so that the MG
interface can work in the normal state. The MG interface can be started in different
ways (see Parameters of the reset command). For a newly configured MG interface,
enable the MG interface through cold start.
f.

After the MG interface is interconnected with the MGC, the MG interface should be
in the normal state, indicating that the MG interface works in the normal state.
----------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
MGCPort MGCIP/
DomainName
----------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.10
2944
10.10.20.2
1
UDP
Normal
2944
10.10.10.11
2944
10.10.20.20
Issue 01 (2016-04-29)

331

Access Module
-----------------------------------------------------------------------------
g.

the normal state.
h.

Add POTS users (phones 0-31) so that the users can go online.
i.
Save the data.

huawei(config)#save
----End
Result
1.
When MG0 communicates with the MGC in the normal state, phones 0-31 belonging to
MG0 can communicate with each other.
2.
When MG1 communicates with the MGC in the normal state, phones 0-31 belonging to
MG1 can communicate with each other.
3.
When MG0 and MG1 communicate with the MGC in the normal state, phones 0-31
belonging to MG0 and phones 0-31 belonging to MG1 can communicate with each other.
Configuring VAG Service (SIP)

This topic describes how to configure and verify the VAG service by creating two SIP
interfaces on the MA5600T/MA5603T/MA5608T and configuring PSTN users on the two
SIP interfaces. This topic is applicable to the scenario where multiple logical AGs are
simulated on one physical SIP AG.
Context
Configuring VAGs is literally to configure SIP interfaces with different IDs on the same
device, and to configure user ports homing to different SIP interfaces. Pay attention to the
following points:
l
When the system uses the SIP protocol, up to eight SIP interfaces with different IDs can
be configured on the MA5600T/MA5603T/MA5608T, and each SIP interface can be
considered as a VAG.
When configuring the parameters for interconnecting different SIP interfaces with the
IMS, make sure that the values of the following parameters of the SIP interfaces are not
completely the same. The values of at least one of the following parameters must be
different on the SIP interfaces.
Issue 01 (2016-04-29)
Local IP address
Local port ID
Remote IP address
Remote port ID
332

Access Module
Figure 3-22 shows an example network of the SIP-based VAG service.
Figure 3-22 Example network of the SIP-based VAG service
Data Plan
The service requirements are as follows:
l
As shown in Figure 3-22, configure VAG1, and configure the users in slot 0/2 to belong
to VAG1; configure VAG2, and configure the users in slot 0/3 to belong to VAG2.
The MA5600T/MA5603T/MA5608T communicates with the IMS through the SIP

protocol.
Configure the data plan of VAG1 as listed in Table 3-16.
The data plan of VAG2 is the same as that of VAG1 except for the following differences:
Issue 01 (2016-04-29)
The media IP address and signaling IP address of VAG2 are 10.20.10.11.
The IMS assigns phone numbers 85000000-85000031 to phones 0-31 of VAG2.
SIP interface 0 indicates VAG1 in the figure, and SIP interface 1 indicates VAG2 in the
figure.
333

Access Module
Table 3-16 Data plan of VAG1

Item
Remarks
SIP interface
data
(The data
configuration
must be the
same as the
data
configuration
on the IMS.)
Media and
signaling
parameter
s
Attributes
of the SIP
interface
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
SIP
interface
fails to be
enabled if
these
parameter
s are not
configure
d.
Voice user data

(The data
configuration
Issue 01 (2016-04-29)
Media and
signaling
upstream VLAN
Standard VLAN 30 is adopted.
Media and
signaling
upstream port

control board. Therefore, port 0/19/0
is used as the upstream port of the
voice service.
Media IP address
and signaling IP
addresses

10.20.10.10.
Default gateway
IP address
The IP address of the next hop from

the MA5600T/MA5603T/MA5608T
to the IMS core network device is
10.20.10.1.
SIP interface ID
0 and 1
Signaling port ID
of the SIP
interface
5060
IP address of the
primary IMS core
network device to
which the SIP
interface belongs
10.20.20.100
Port ID of the
primary IMS core
network device to
which the SIP
interface belongs
5060
Transmission
mode of the SIP
interface
UDP
Homing domain
name of the SIP
interface
huawei
Index of the
profile used by
the SIP interface
Default profile (profile 1)
The ASPB service board in slot 0/2

and 0/3.

334

Access Module
Item
Remarks
must be the
same as the
data
configuration
on the IMS.)
Phone number
80000000-80000031
Procedure
l
Configure VAG1.
a.

According to the data plan, configure standard VLAN 30 as the media and signaling
upstream VLAN, add upstream port 0/19/0 to the VLAN, and configure the IP
address of the Layer 3 interface to 10.20.10.10, which facilitates the configuration
of the media and signaling IP address pools.
b.

huawei(config)#voip
c.
Configure a static route to the IMS.

Make sure that the route between the local device and the IMS is reachable. The
static route is used as an example.
d.
Add a SIP interface.

According to the data plan, add SIP interface 0, and configure the interface
attributes.
signal-ip
10.20.10.10 signal-port 5060 transfer udp primary-proxy-ip1 10.20.20.100
primary-proxy-port 5060
home-domain huawei sipprofile-index 1
e.
Reset the SIP interface.

Reset the SIP interface to make the SIP interface register with the IMS (and to make
the modified attributes of the SIP interface take effect) so that the SIP interface can
work in the normal state.
Issue 01 (2016-04-29)

335

Access Module
f.

the normal state.
g.

Add POTS users (phones 0-31) to VAG1 so that the users can go online.
h.
Save the data.

huawei(config)#save
Configure VAG2.
a.

According to the data plan, configure the IP address of the Layer 3 interface to
10.20.10.11, which facilitates the configuration of the media and signaling IP
address pools.
When you need to connect the VLAN interface to multiple subnets and configure
the secondary IP address, use sub parameter. The secondary IP address is the same
as the primary IP address in function. They are used for Layer 3 forwarding.
In step a, the VLAN is added and the IP address of the VLAN Layer 3 interface is
configured. In this step, use the sub parameter to configure the secondary IP address
of the VLAN. The secondary IP address is the same as the primary IP address in
function. They are used for Layer 3 forwarding.
huawei(config-if-vlanif30)#ip address 10.20.10.11 24 sub
b.

huawei(config)#voip
c.
Configure a static route to the IMS.

Make sure that the route between the local device and the IMS is reachable. The
static route is used as an example. If the static route has been configured, skip this
step.
d.
Add a SIP interface.

According to the data plan, add SIP interface 1, and configure the interface
attributes.
Issue 01 (2016-04-29)

336

Access Module
signal-ip
primary-proxy-port 5060
home-domain huawei sipprofile-index 1
e.
Reset the SIP interface.

Reset the SIP interface to make the SIP interface register with the IMS (and to make
the modified attributes of the SIP interface take effect) so that the SIP interface can
f.

the normal state.
g.

Add POTS users (phones 0-31) to VAG2 so that the users can go online.
h.
Save the data.

huawei(config)#save
----End
Result
After the configuration:
l
Users of VAG1 can communicate with each other.
Users of VAG2 can communicate with each other.
Users of VAG1 and VAG2 can communicate with each other.
3.4 Example of the Triple Play

This topic describes how to configure the Triple Play on the MA5600T/MA5603T/MA5608T.
Triple play is a service provisioning mode in which integrated services can be provided to a
user. Currently, the prevailing integrated services include the high-speed Internet access
service, voice over IP (VoIP) service, and IPTV service.
The early broadband access provides only the high-speed Internet access service. As the
Internet is rapidly developing, it can offer much richer services, such as video (IPTV)
services. The development of multiple access modes such as ADSL2+ and VDSL2 access,
and the improvement of broadband access also lay a solid foundation for provisioning the
video service.
Issue 01 (2016-04-29)

337

Access Module
PVC Modes for Triple Play Implementation

MA5600T/MA5603T/MA5608T supports the triple play implemented in single-PVC multiple
services and multi-PVC multiple services modes.
PVC
Mode
Implementation
Application Scenario
SinglePVC for
single
service
Single-PVC for single service is a triple

play mode in which a PVC is adopted for
carrying one type of service.
This mode provides only the

Internet access service and is
used only in early days.
MultiPVC for
multiple
services
Multi-PVC for multiple services is a triple

play mode in which multiple PVCs are
adopted for carrying multiple services from
the MA5600T/MA5603T/MA5608T to each
DSL user terminal.
The home gateway

differentiates services based on
PVCs.
l On the user side, three PVCs are used

for carrying VoIP, IPTV, and Internet
services, and each xDSL port must be
configured with at least three PVCs.
This mode is adopted to utilize

the previously-configured
services and previouslydeployed user terminals.
l At the network end, three VLANs are

created for the upstream interface to
carry different types of services.
SinglePVC for
multiple
services
Single-PVC for multiple services is a triple

play mode in which a single PVC is adopted
for carrying multiple services from the
MA5600T/MA5603T/MA5608T to each
DSL user terminal. The MA5600T/
MA5603T/MA5608T can differentiate
services by the following means:
l User-side VLAN ID
The home gateway

differentiates services based on
Ethernet parameters such as
such as the VLAN ID or the
802.1p priority.
This mode is recommended if
the home gateway supports the
preceding function.
l 802.1p value + VLAN ID carried in the

Ethernet packet
l Ethernet type (IPoE/PPPoE) + VLAN
ID
Service Priorities and Bandwidth

The different services have different request on the bandwidth and priority.
l
Because the bandwidth and delay of the VoIP service are low, the priority of the VoIP
service is the highest among the triple play services.
Because the bandwidth occupied by the IPTV service is relatively high, and the bit error
ratio/packet loss ratio is relatively low, the priority of the IPTV service is lower than that
of the VoIP service, but is higher than that of the Internet access service.
Because common Internet access services, such as web browsing, require neither a
strong real-time performance nor a low packet loss ratio, the priority of the high-speed
Internet access service is the lowest among the triple play services.
Issue 01 (2016-04-29)

338

Access Module
Traffic Management for the Triple Play Services

Traffic management for the triple play includes two modes of rate limitations: stream-based
and user (xDSL port)-based. These two modes are implemented on different layers, and
therefore can be used together. When implementing the user (xDSL port)-based rate
limitation, ensure that the rate limit for the user (xDSL port) must be higher than the
aggregated rate limits for all services of the user.
l
The stream-based rate limitation

The stream-based rate limitation is planned based on services, for example, the
bandwidth is planned based on the IPTV HD program and the IPTV SD program.
The user (xDSL port)-based rate limitation

The user (xDSL port)-based rate limitation is planned based on physical information,
such as line quality and number of users per port. The bandwidth for each user is
managed in a unified way: Every users' VoIP, IPTV, and Internet services share one user
bandwidth, the bandwidth is preferentially allocated to the service with higher priority,
and one service burst can hold the total user bandwidth when the other two services carry
no traffic.
3.4.1 Configuring the Triple Play (Multi-PVC)

This topic describes how to configure the triple play in the multi-PVC for multiple services
mode. The user home gateway is connected to multiple terminals to implement the access of
multiple services such as Internet access service, VoIP service, and IPTV service. Carriers can
adopt this mode when they want to use the existing operation, maintenance, and management
system for the triple play services.
Prerequisites
l
Network devices and lines must be in the normal state.
The system is working properly.
The home gateway has been configured. Specifically, permanent virtual channels (PVCs)
have been configured on the home gateway for different services.
The asymmetric digital subscriber line 2 plus (ADSL2+) line template and alarm
template that need to be bound to ports have been configured.
ADSL2+ user 1 and ADSL2+ user 2 are connected to the MA5600T/MA5603T/MA5608T to
implement the triple play.
l
The PC user accesses the Internet properly.
The VoIP user makes calls properly.
The IPTV user watches programs properly.
After receiving different traffic streams, the MA5600T/MA5603T/MA5608T provides

different QoS guarantees to the traffic streams according to the traffic priorities of the
PVC.
Networking
Figure 3-23 shows an example network of the triple play service in the multi-PVC for
multiple services mode. The Internet service is provided in the PPPoE mode. The VoIP
Issue 01 (2016-04-29)

339

Access Module
service and the IPTV service are provided in the DHCP mode, obtaining IP addresses from
the DHCP server in the standard DHCP mode.
Figure 3-23 Example network of the triple play service in the multi-PVC for multiple
services mode
Data Plan
Table 3-17 shows the key data for configuring the triple play in multi-PVC for multiple
services mode on the MA5600T/MA5603T/MA5608T.
Table 3-17 Data plan for configuring the triple play in multi-PVC for multiple services mode
Issue 01 (2016-04-29)
Config
uration
Item
Data
Upstrea
m port
0/19 0
Internet access
Remarks
VoIP
IPTV

340

Access Module
Config
uration
Item
Data
ADSL2
+ port
l User 1: 0/2/1
VLAN
l VLAN ID: 2
l VLAN ID: 3
l VLAN ID: 4
l VLAN type:
smart
l VLAN type:
smart
l VLAN type:
smart
l Index: 7
l Index: 8
l Index: 9
l CIR: 2 Mbit/s
l CIR: 1 Mbit/s
l No rate limitation
l Default
packet 802.1p
priority: 1
l Default packet
802.1p
priority: 6
l Default packet
802.1p priority: 5
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
l VPI: 0
l VPI: 0
l VCI: 37
l VCI: 36
Traffic
profile
Service
port
Internet access
Remarks
VoIP
IPTV
-
l User 2: 0/3/1
l Priority
scheduling policy
of downstream
packets: LocalSetting
l Index: 100 and

101
l VPI: 0
l VCI: 35
Issue 01 (2016-04-29)

As VoIP,
IPTV, and
Internet
services
access from
the same port,
the 802.1p
priorities for
each service
must be
configured.
These three
services are
prioritized in
descending
order as
follows: VoIP,
IPTV, Internet
access.
The three
services have
different
VCIs.
341

Access Module
Config
uration
Item
Data
Remarks
Internet access
VoIP
IPTV
DHCP
relay
l Number of the
DHCP server
group: 1
l Number of the
DHCP server
group: 2
l IP address of
DHCP server
group 1:
20.1.1.2
l IP address of
DHCP server
group 1: 20.2.2.2
l IP address of
DHCP server
group 2:
20.1.1.3
l IP address of
the VLAN
Layer 3
interface:
10.1.1.1/24
Multicas
t
l IP address of
DHCP server
group 2: 20.2.2.3
l IP address of the
VLAN Layer 3
interface:
10.2.2.1/24
l Multicast mode:
IGMP Proxy
l Profile 0 of
multicast user 2:
the right to watch
only program
BTV-1
l Multicast
upstream port:
0/19/0
l Multicast IP
address of
program BTV-1:
224.1.1.1;
program source IP
address:
10.10.10.10
l Multicast IP
address of
program BTV-2:
224.1.1.2;
program source IP
address:
10.10.10.10
Procedure
l
Issue 01 (2016-04-29)
Configure the Internet service.

342

Access Module
a.
Create a VLAN and add an upstream port to the VLAN.

b.
Add a traffic profile.

huawei(config)#traffic table ip index 7 cir 2048 priority 1 prioritypolicy local-Setting
c.
Add a service port to the VLAN.

Add a service port to the VLAN 2 and use the traffic profile 7 added in the
preceding step.
huawei(config)#service-port vlan 2 adsl 0/2/1 vpi 0 vci 37 rx-cttr 7 txcttr 7
d.
Save the data.

huawei(config)#save
Configure the VoIP service.

a.

b.

c.

preceding step.
d.
Configure the DHCP relay.

Configure the IP addresses of DHCP server 1 and the IP address of the VLAN
Layer 3 interface, and bind the VLAN Layer 3 interface to DHCP server 1.
huawei(config)#dhcp mode layer-3 standard
huawei(config)#dhcp-server 1 ip 20.1.1.2 20.1.1 3
huawei(config-if-vlanif3)#dhcp-server 1
e.
Save the data.

huawei(config)#save
Configure the IPTV service.

a.

b.

huawei(config)#traffic table ip index 9 cir off priority 5 prioritypolicy local-Setting
c.
Issue 01 (2016-04-29)

343

Access Module
NOTICE
On the MA5600T/MA5603T/MA5608T, if the PVC is configured with a priority,
the priority of the multicast packets carried by the PVC does not take effect.
Add a service port to VLAN 4 and use traffic profile 9.
huawei(config)#service-port 100 vlan 4 adsl 0/2/1 vpi 0 vci 35 rx-cttr 9
tx-cttr 9
huawei(config)#service-port 101 vlan 4 adsl 0/3/1 vpi 0 vci 35 rx-cttr 9
tx-cttr 9
d.

Configure the IP address of DHCP server 2 and the IP address of the VLAN Layer
3 interface, and bind the VLAN Layer 3 interface to DHCP server 2.
huawei(config)#dhcp-server 2 ip 20.2.2.2 20.2.2.3
e.
Configure the multicast data.

Configure the multicast mode, authority profile, multicast upstream port, and
multicast program. Add multicast user 1 and multicast user 2 to multicast VLAN 4.
Are you sure to change IGMP mode?(y/n)[n]:y
huawei(config)#btv
huawei(config-btv)#igmp uplink-port-mode default
Are you sure to change the uplink port mode?(y/n)[n]:y
huawei(config-mvlan4)#igmp program add name BTV-1 ip 224.1.1.1 sourceip
10.10.10.10
10.10.10.10
huawei(config)#btv
huawei(config-btv)#igmp profile profile-name profile0 program-name BTV-1
watch
huawei(config-btv)#igmp policy service-port 100 normal
huawei(config-btv)#igmp user add service-port 100 no-auth
huawei(config-btv)#igmp user add service-port 101 auth
huawei(config-btv)#igmp user bind-profile service-port 101 profile-name
profile0
f.
Save the data.

huawei(config)#save
----End
Result
After the related upstream device and downstream device are configured, the triple play
service (Internet, VoIP, and IPTV services) is available.
Issue 01 (2016-04-29)

344

Access Module
Internet: user 1 and user 2 can access the Internet through PPPoE dialup.
VoIP: user 1 and user 2 can call each other.
IPTV: user 1 can watch all the programs after being connected to port 0/2/1, and user 2
can watch only program BTV-1 after being connected to port 0/3/1.
Configuration File
Internet:
vlan 2 smart
port vlan 0/19 0
traffic table ip index 7 cir 2048 priority 1 priority-policy local-Setting
service-port vlan 2 adsl 0/2/1 vpi 0 vci 37 rx-cttr 7 tx-cttr 7
dhcp mode layer-3 standard
dhcp-server 1 ip 20.1.1.2 20.1.1 3
save //Save the configuration.
VoIP:
vlan 3 smart
port vlan 3 0/19 0
dhcp-server 1 ip 20.1.1.2 20.1.1 3
interface vlanif 3
ip address 10.1.1.1 24
dhcp-server 1
quit
IPTV:
vlan 4 smart
port vlan 4 0/19 0
traffic table ip index 9 cir off priority 5 priority-policy local-Setting
service-port 100 vlan 4 adsl 0/2/1 vpi 0 vci 35 rx-cttr 9 tx-cttr 9
dhcp-server 2 ip 20.2.2.2 20.2.2.3
interface vlanif 4
dhcp-server 2
quit
multicast-vlan 4
igmp mode proxy
btv
igmp uplink-port-mode default
quit
multicast-vlan 4
igmp program add name BTV-1 ip 224.1.1.1 sourceip 10.10.10.10
btv
igmp profile profile-name profile0 program-name BTV-1 watch
igmp policy service-port 100 normal
igmp user add service-port 100 no-auth
igmp user add service-port 101 auth
igmp user bind-profile service-port 101 profile-name profile0
multicast-vlan 4
quit
Issue 01 (2016-04-29)

345

Access Module
3.4.2 Configuring the Triple Play (Single-PVC, Stream-based Rate

Limitation)
This topic describes how to configure the triple play in the single-PVC for multiple services
mode. The user home gateway is connected to multiple terminals to implement the access of
multiple services such as Internet access service, VoIP service, and IPTV service.
Prerequisites
l
The home gateway has been configured. Specifically, virtual local area networks
(VLANs) have been configured on the home gateway for different services.
template that need to be bound to ports have been configured. For details about how to
configure the ADSL2+ line template or alarm template, see Overview of Configuring
ADSL2+ Templates and Profiles.
l
After receiving different traffic streams through the same PVC, the MA5600T/
MA5603T/MA5608T provides different QoS guarantees to the traffic streams according
to the user-side VLANs.
Networking
Figure 3-24 shows an example network of the triple play service in the single-PVC for
multiple services mode. The Internet service is accessed in the PPPoE mode. The VoIP
service and the IPTV service are provided in the DHCP mode, obtaining IP addresses from
the DHCP server in the standard DHCP mode.
Issue 01 (2016-04-29)

346

Access Module
Figure 3-24 Example network of the triple play service in the single-PVC for multiple
services mode
Program1:224.1.1.1
Program2:224.1.1.2
Muticast source
OSS & RADIUS Server/RADIUS Proxy
BMS
GW
IPTV DHCP IP1:20.2.2.2

IP2:20.2.2.3
Server
Router
BRAS
VoIP DHCP IP1:20.1.1.2

Server
IP2:20.1.1.3
LSW
Access node
Home Gateway 2
Home Gateway 1
DHCP
PPPoE
DHCP
PPPoE
DHCP
DHCP
STB
STB
Ephone
PC
TV
Ephone
PC
TV
User 2
User 1
Data Plan
Table 3-18 shows the key data for configuring the triple play in single-PVC for multiple
Table 3-18 Data plan for configuring the triple play in single-PVC for multiple services mode
(stream-based rate limitation)
Issue 01 (2016-04-29)
Config
uration
Item
Data
Upstrea
m port
0/19 0
Internet access
Remarks
VoIP
IPTV

347

Access Module
Config
uration
Item
Data
ADSL2
+ port
l User 1: 0/2/1
VLAN
l SVLAN ID:
2
Internet access
VoIP
IPTV
-
l SVLAN ID: 3
l SVLAN ID: 4
l SVLAN type:
smart
l SVLAN type:
smart
l CVLAN ID:
30
l CVLAN ID: 40
l Index: 7
l Index: 8
l Index: 9
l CIR: 2 Mbit/s
l CIR: 1 Mbit/s
l No rate limitation
l Default
packet 802.1p
priority: 1
l Default packet
802.1p
priority: 6
l Default packet
802.1p priority: 5
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
l VPI: 0
l VPI: 0
l VCI: 35
l VCI: 35
l CVLAN ID:
20
Service
port
Remarks
l User 2: 0/3/1
l SVLAN type:
smart
Traffic
profile
l Priority
scheduling policy
of downstream
l Index: 100 and

101
l VPI: 0
l VCI: 35
Issue 01 (2016-04-29)

As VoIP,
IPTV, and
Internet
services
access from
the same port,
the 802.1p
priorities for
each service
must be
configured.
These three
services are
prioritized in
descending
order as
follows: VoIP,
IPTV, Internet
access.
The three
services have
different
VCIs.
348

Access Module
Config
uration
Item
Data
Remarks
Internet access
VoIP
IPTV
DHCP
relay
l Number of the
DHCP server
group: 1
l Number of the
DHCP server
group: 2
l IP address of
DHCP server
group 1:
20.1.1.2
l IP address of
DHCP server
group 1: 20.2.2.2
l IP address of
DHCP server
group 2:
20.1.1.3
l IP address of
the VLAN
Layer 3
interface:
10.1.1.1/24
Multicas
t
l IP address of
DHCP server
group 2: 20.2.2.3
l IP address of the
VLAN Layer 3
interface:
10.2.2.1/24
l Multicast mode:
IGMP Proxy
l Profile 0 of
multicast user 2:
the right to watch
only program
BTV-1
l Multicast
upstream port:
0/19/0
l Multicast IP
address of
program BTV-1:
224.1.1.1;
program source IP
address:
10.10.10.10
l Multicast IP
address of
program BTV-2:
224.1.1.2;
program source IP
address:
10.10.10.10
Procedure
l
Issue 01 (2016-04-29)
Configure the Internet service.

349

Access Module
a.

b.

c.

Add a service port to VLAN 2 and use the traffic profile added 7 in the preceding
step.
huawei(config)#service-port vlan 2 adsl 0/2/1 vpi 0 vci 35 multi-service
user-vlan 20 rx-cttr 7 tx-cttr 7
d.
Save the data.

huawei(config)#save

a.

b.

c.

preceding step.
NOTE
The video and voice services have stricter requirements on delay. You can run the bind channel
command to bind them to a low delay channel. Currently, this command is available for only the
VDSL port.
d.

e.
Save the data.

huawei(config)#save

a.

b.

Issue 01 (2016-04-29)

350

Access Module
c.
NOTICE
Add a service port to VLAN 4 and use traffic profile 9.
huawei(config)#service-port 100 vlan 4
service user-vlan 40 rx-cttr 9 tx-cttr
service user-vlan 40 rx-cttr 9 tx-cttr
d.
adsl 0/2/1 vpi 0 vci 35 multi9

adsl 0/3/1 vpi 0 vci 35 multi9

e.

huawei(config)#btv
10.10.10.10
10.10.10.10
huawei(config)#btv
watch
profile0
huawei(config-mvlan4)#igmp multicast-vlan member port 0/2/1
f.
Save the data.

huawei(config)#save
----End
Issue 01 (2016-04-29)

351

Access Module
Result
l
Configuration File
Internet:
vlan 2 smart
port vlan 0/19 0
service-port vlan 2 adsl 0/2/1 vpi 0 vci 35 multi-service user-vlan 20 rx-cttr 7
tx-cttr 7
tx-cttr 7
dhcp-server 1 ip 20.1.1.2 20.1.1 3
save
VoIP:
vlan 3 smart
port vlan 3 0/19 0
tx-cttr 8
tx-cttr 8
dhcp-server 1 ip 20.1.1.2 20.1.1 3
interface vlanif 3
dhcp-server 1
quit
save
IPTV:
vlan 4 smart
port vlan 4 0/19 0
service-port 100 vlan 4 adsl 0/2/1 vpi 0 vci 35 multi-service user-vlan 40 rxcttr 9 tx-cttr 9
service-port 101 vlan 4 adsl 0/3/1 vpi 0 vci 35 multi-service user-vlan 40 rxcttr 9 tx-cttr 9
dhcp-server 2 ip 20.2.2.2 20.2.2.3
interface vlanif 4
dhcp-server 2
quit
multicast-vlan 4
igmp mode proxy
btv
multicast-vlan 4
btv
Issue 01 (2016-04-29)

352

Access Module

multicast-vlan 4
quit
save
3.4.3 Configuring the Triple Play Service (Single-PVC, User-based

Rate Limitation)
This topic describes how to configure the triple play service in the single-PVC for multiple
services mode. The user home gateway is connected to multiple terminals to implement the
access of multiple services such as Internet access, VoIP, and IPTV services and perform userbased and stream-based rate limitation.
Prerequisites
l
The home gateway has been configured. Specifically, virtual local area networks
(VLANs) have been configured on the home gateway for different services.
template that need to be bound to ports have been configured.
l
The maximum bandwidth of each user is 10 Mbit/s, adopting user-based bandwidth

management: The Internet access, VoIP, and IPTV services of each user share the same
total bandwidth and the QoS scheduling is implemented. The service priorities are VoIP
(the value is 6), IPTV (the value is 5), and Internet access (the value is 1) in descending
order. If any two services carry no traffic, the third service can hold a burst of the total
user bandwidth.
After receiving different traffic streams through the same PVC, the MA5600T/
MA5603T/MA5608T provides different QoS guarantees to the traffic streams according
to the user-side VLANs.
Networking
Figure 3-25 shows an example network of the triple play in the single PVC for multiple
services mode. The Internet service is accessed in the PPPoE mode. The VoIP service and the
IPTV service are provided in the DHCP mode, obtaining IP addresses from the DHCP server
in the standard DHCP mode.
Issue 01 (2016-04-29)

353

Access Module
Figure 3-25 Example network of the triple play service in the single-PVC for multiple
services mode
Program1:224.1.1.1
Program2:224.1.1.2
Muticast source
OSS & RADIUS Server/RADIUS Proxy
BMS
GW
IPTV DHCP IP1:20.2.2.2

IP2:20.2.2.3
Server
Router
BRAS
VoIP DHCP IP1:20.1.1.2

Server
IP2:20.1.1.3
LSW
Access node
Home Gateway 2
Home Gateway 1
DHCP
PPPoE
DHCP
PPPoE
DHCP
DHCP
STB
STB
Ephone
PC
TV
Ephone
PC
TV
User 2
User 1
Data Plan
Table 3-19 shows the key data for configuring the triple play in single-PVC for multiple
Table 3-19 Data plan for configuring the triple play in single-PVC for multiple services mode
(user-based and stream-based rate limitation)
Issue 01 (2016-04-29)
Config
uration
Item
Data
Upstrea
m port
0/19 0
Internet access
Remarks
VoIP
IPTV

354

Access Module
Config
uration
Item
Data
ADSL2
+ port
l User 1: 0/2/0
Internet access
Remarks
VoIP
IPTV
-
l User 2: 0/2/1
l ADSL2+ channel profile
ID: 3
Minimum upstream/downstream rates: 32 kbit/s
Minimum reserved upstream/downstream rate: 32 kbit/s
Maximum upstream rate: 4096 kbit/s
Maximum downstream rate: 10240 kbit/s
l ADSL2+ line template:
ID: 3
Upstream/Downstream rate adaptation ratio of channel:
100
l ADSL2+ line alarm template ID: 1
VLAN
l SVLAN ID:
2
l SVLAN type:
smart
l CVLAN ID:
20
Issue 01 (2016-04-29)
l SVLAN ID: 3
l SVLAN ID: 4
l SVLAN type:
smart
l SVLAN type:
smart
l CVLAN ID:
30
l CVLAN ID: 40

355

Access Module
Config
uration
Item
Data
Internet access
VoIP
IPTV
Traffic
profile
l Index: 7
l Index: 8
l Index: 9
l CIR: 2 Mbit/s
l CIR: 1 Mbit/s
l CIR: 4 Mbit/s
l PIR: 10
Mbit/s
l PIR: 10 Mbit/s
l PIR: 10 Mbit/s
l Default packet
802.1p
priority: 6
l Default packet
802.1p priority: 5
l Default
packet 802.1p
priority: 1
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
Remarks
l Priority
scheduling
policy of
downstream
packets:
Local-Setting
l Priority
scheduling policy
of downstream
As VoIP,
IPTV, and
Internet
services
access from
the same port,
the 802.1p
priorities for
each service
must be
configured.
These three
services are
prioritized in
descending
order as
follows: VoIP,
IPTV, Internet
access.
The PIR and
maximum
user
bandwidth
must be the
same.
Service
port
l VPI: 0
l VPI: 0
l VCI: 35
l VCI: 35
l Index: 100 and

101
l VPI: 0
l VCI: 35
DHCP
relay
l Number of the
DHCP server
group: 1
l Number of the
DHCP server
group: 2
l IP address of
DHCP server
group 1:
20.1.1.2
l IP address of
DHCP server
group 1: 20.2.2.2
l IP address of
DHCP server
group 2:
20.1.1.3
l IP address of
the VLAN
Layer 3
interface:
10.1.1.1/24
Issue 01 (2016-04-29)
The three
services have
different
VCIs.
-
l IP address of
DHCP server
group 2: 20.2.2.3
l IP address of the
VLAN Layer 3
interface:
10.2.2.1/24

356

Access Module
Config
uration
Item
Data
Remarks
Internet access
VoIP
IPTV
Multicas
t
l Multicast mode:
IGMP Proxy
l Profile 0 of
multicast user 2:
the right to watch
only program
BTV-1
l Multicast
upstream port:
0/19/0
l Multicast IP
address of
program BTV-1:
224.1.1.1;
program source IP
address:
10.10.10.10
l Multicast IP
address of
program BTV-2:
224.1.1.2;
program source IP
address:
10.10.10.10
Procedure
l
Configure user bandwidth management.

a.
Configure ADSL channel profile 3 with a minimum upstream/downstream

transmission rate 32 kbit/s, a minimum upstream/downstream reserved rate 32
kbit/s, a maximum downstream transmission rate 10240 kbit/s and a maximum
upstream transmission rate 4096 kbit/s.
huawei(config)#adsl channel-profile quickadd 3 rate 32 32 10240 32 32
4096
b.
Configure ADSL line template 3 by binding channel profile 3.

huawei(config)#adsl line-template quickadd 3 channel1 3 100 100
Bind ADSL line template 3 created in the previous step to ADSL ports 0/2/0 and 0/2/1.
Activate the ports.
Issue 01 (2016-04-29)

357

Access Module
Configure the queue scheduling mode of the port.

Configure the queue scheduling mode of the port to priority queuing (PQ).
huawei(config)#queue-scheduler strict-priority
Configure the Internet access service.

a.

b.
Configure a traffic profile.

huawei(config)#traffic table ip index 7 cir 2048 pir 10240 priority 1
prioritypolicy local-Setting
c.

Create service virtual port, the S-VLAN ID to 2, the C-VLAN ID to 20, the
VPI/VCI to 0/35 and use the traffic profile 7 added in the preceding step.
huawei(config)#service-port vlan 2
multi-service user-vlan 20 rx-cttr
d.
adsl 0/2/0 vpi 0 vci 35

7 tx-cttr 7
7 tx-cttr 7
Save the data.

huawei(config)#save

a.

b.

priority-policy local-Setting
c.

Create service virtual port, the S-VLAN ID to 3, the C-VLAN ID to 30, the
VPI/VCI to 0/35 and use the traffic profile 8added in the preceding step.

8 tx-cttr 8
8 tx-cttr 8
NOTE
The video and voice services have stricter requirements on delay. You can run the bind channel
command to bind them to a low delay channel. Currently, this command is available for only the
VDSL2 port.
d.

e.
Save the data.

huawei(config)#save
l
Issue 01 (2016-04-29)

358

Access Module
a.

b.

c.
NOTICE
Create service virtual port, and use the traffic profile 9 added in the preceding step.
huawei(config)#service-port 100 vlan
multi-service user-vlan 40 rx-cttr 9
multi-service user-vlan 40 rx-cttr 9
d.
4 adsl 0/2/0 vpi 0 vci 35

tx-cttr 9
4 adsl 0/2/1 vpi 0 vci 35
tx-cttr 9

e.

10.10.10.10
10.10.10.10
watch
huawei(config-btv)#igmp user add port service-port 100 auth
huawei(config-btv)#igmp user add port service-port 101 auth
profile0
Issue 01 (2016-04-29)

359

Access Module
f.
Save the data.

huawei(config)#save
----End
Result
After the relevant upstream device and downstream device are configured, the triple play
service (Internet access, VoIP, and IPTV services) is available. If any two services carry no
traffic, the third service can hold a burst of the total user bandwidth.
l
Configuration File
adsl channel-profile quickadd 3 rate 32 32 10240 32 32 4096
adsl line-template quickadd 3 channel1 3 100 100
queue-scheduler strict-priority
interface adsl 0/2
deactivate 0
deactivate 1
alarm-config 0 1
alarm-config 1 1
quit
Internet:
vlan 2 smart
port vlan 0/19 0
service-port vlan 2 adsl 0/2/0
vpi 0 vci 35 multi-service user-vlan 20 rx-cttr 7 tx-cttr 7
dhcp-server 1 ip 20.1.1.2 20.1.1 3
save
VoIP:
vlan 3 smart
port vlan 3 0/19 0
dhcp-server 1 ip 20.1.1.2 20.1.1 3
interface vlanif 3
dhcp-server 1
quit
save
IPTV:
vlan 4 smart
port vlan 4 0/19 0
Issue 01 (2016-04-29)

360

Access Module
service-port 100 vlan 4 adsl 0/2/0

service-port 101 vlan 4 adsl 0/2/1
dhcp-server 2 ip 20.2.2.2 20.2.2.3
interface vlanif 4
dhcp-server 2
quit
multicast-vlan 4
igmp mode proxy
btv
quit
multicast-vlan 4
btv
multicast-vlan 4
quit
save
Issue 01 (2016-04-29)

361

Access Module
4 Configuration Example of the Private Line Service
Configuration Example of the Private Line

Service
About This Chapter

A private line service refers to a service carried over a true or virtual private line on the public
network for transparent transmission and for access of private network services. This topic
describes how to configure the private line service.
Context
The MA5600T/MA5603T/MA5608T supports the following private line services:
l
PWE3 private line service
TDM SHDSL access service
QinQ VLAN private line service
4.1 Example of the QinQ VLAN

The QinQ-VLAN-based private line service can achieve the interconnection and secure
communication among branches in different areas within the enterprise private network.
4.2 Example of the VLAN Stacking Multi-ISP Wholesale Access
In a Layer-2 switching metropolitan area network (MAN), there are multiple Internet service
providers (ISPs). To provision the services provided by the ISP to the specified user group
rapidly, the outer VLAN tags of VLAN stacking can be used to identify ISPs, while the inner
VLAN tags to identify users. In this way, different user groups can be connected to the
specified ISPs in batches through different outer VLAN tags to obtain services from the ISPs.
4.3 Example of the PWE3 Private Line Service
This topic describes how to configure the MPLS PWE3 private line service using examples.
4.4 Example of the TDM SHDSL Service for Narrowband Data
The TDM SHDSL extends the access distance. With the TDM SHDSL, the MA5600T/
MA5603T/MA5608T transparently transmits user-side configuration data to the digital data
network (DDN). In this way, the twisted pair can be fully used and the E1 line deployment
expense decreases.
4.5 Example of the Private Line Service Leasing E1 Timeslots
Leasing an entire E1 line is expensive and also a waste of the bandwidth resources. The
private line service leasing E1 timeslots can meet the requirement leasing a part of an E1 line.
Issue 01 (2016-04-29)

362

Access Module
With this service, users are assigned specific timeslots of an E1 line, and therefore can share
the bandwidth of the E1 line, hence saving the E1 line lease expense.
Issue 01 (2016-04-29)

363

Access Module
4.1 Example of the QinQ VLAN

The QinQ-VLAN-based private line service can achieve the interconnection and secure
communication among branches in different areas within the enterprise private network.
Prerequisites
l
The authentication data of the access user must be configured on the BRAS.
l
An enterprise requires to achieve the interconnection and secure communication between

its headquarters and the branches located in different areas through Layer 2 switching
network, and to isolate the data of different departments.
The access device uses xDSL or LAN access.
Networking
Figure 4-1 shows an example network for configuring the private line service.
The two branches of the enterprise are connected to the (metropolitan area network) MAN
through the MA5600T/MA5603T/MA5608T. The upper-layer network must work in the
Layer 2 mode, and must forward packets according to the VLAN and the MAC address.
On the MA5600T/MA5603T/MA5608T, the attribute of the upstream VLAN of user packets
is configured as QinQ private line service. A VLAN tunnel is created in Layer 2/Layer 3
MAN for transmitting data carrying the VLAN tag. Different VLAN IDs are used for
different departments to achieve user isolation and data security. In this way, the service
packets of the enterprise private network can be transparently transmitted through the public
network, and the two branches can communicate with each other securely.
Issue 01 (2016-04-29)

364

Access Module
Figure 4-1 Example network for configuring the private line service
L2/L3 LAN Switch
L2/L3 LAN Switch
MAN
(Layer 2 network)
VLAN 50 VLAN 10
VLAN 50 VLAN 20
Access node_A
Access node_B
Modem
Modem
VLAN 10
VLAN 10
VLAN 20
VLAN 20
L2 LAN Switch
L2 LAN Switch
Department Department
A
B
Department Department
B
A
Headquarters
Branch
QinQ VLAN private line for department A
QinQ VLAN private line for department B
The configuration on MA5600T/MA5603T/MA5608T_A is the same as the configuration on

MA5600T/MA5603T/MA5608T_B. The following uses the configuration on MA5600T/
MA5603T/MA5608T_A and VDSL2 access as examples to describe how to configure the
private line service implemented through a QinQ VLAN.
Data Plan
Table 4-1 lists the key data planning of the QinQ VLAN private line service on MA5600T/
MA5603T/MA5608T_A.
Issue 01 (2016-04-29)

365

Access Module
Table 4-1 Data plan for configuring the QinQ VLAN private line service
Item
Data
Remarks
VLAN
l VLAN ID: 50
The public network VLAN,

namely outer VLAN, is
configured here. The inner
VLAN belongs to the
enterprise private network,
which can be planned by
the enterprise self.
l VLAN type: smart VLAN

l VLAN attribute: QinQ
Transparent
transmission of
Layer 2 packets
Enable the transparent transmission of

BPDUs.
This function is mainly

used in the QinQ service to
provide a transparent and
secure data channel for the
enterprise branches located
in two places within the
enterprise private network.
After the transparent
transmission of BPDUs is
enabled, the Layer 2
protocol packets of a
private network can be
transparently transmitted
through the public network.
Upstream port
0/19/0
Traffic profile
l Traffic profile ID: 10
The CIR depends on the

user bandwidth
requirement.
l CIR: 4 Mbit/s
l Priority copy policy: user-cos
l Default 802.1p priority of the packet:
4
l Priority-based scheduling policy of the
downstream packets: local-setting
VDSL2 port
l VDSL2 port ID: 0/2/0
l Default VDSL2 line profile: 1

l Default VDSL2 alarm profile: 1
Service virtual
port
l VLAN ID: 50
l Service port: 0/2/0
l VDSL channel mode: ATM
l VPI: 0
l VCI: 35
l ID of the traffic profile in Rx
direction: 10
l The VPI/VCI is the

same as the management
VPI/VCI on the peer
modem.
l The traffic profile that
meets the service
requirement is used.
l ID of the traffic profile in Tx

direction: 10
Issue 01 (2016-04-29)

366

Access Module
Procedure
The VLAN ID is 50, and the VLAN is a smart VLAN.
Step 2 Set the VLAN attribute to QinQ.

huawei(config)#vlan attrib 50 q-in-q
Step 3 Enable the transparent transmission of BPDUs.

Enable the transparent transmission of BPDUs so that the Layer 2 protocol packets of a
private network can be transparently transmitted through the public network. By default, the
transparent transmission of BPDUs is disabled.
huawei(config)#bpdu tunnel vlan 50 enable

Add upstream port 0/19/0 to VLAN 50.

The profile ID is 10, the CIR is 4 Mbit/s, and packets are scheduled according to the priority
specified in the traffic profile.
huawei(config)#traffic table ip index 10 cir 4096 priority user-cos 4 prioritypolicy
local-Setting
Step 6 Activate the VDSL2 port and bind a profile to it.

Use the default VDSL2 line profile 1. Activate port 0/2/0 and bind alarm profile 1 to port
0/2/0.
NOTE
l By default, the VDSL port is in the activated state. Before binding a profile to the port, you must
Step 7 Add a service port to the VLAN.
Add a service port to the VLAN 50, and use traffic profile 10 that meets the service
requirements. The VPI and the VCI are 0 and 35 respectively, the same as those on the peer
modem. The user port is 0/2/0. The VDSL channel is in ATM mode.
huawei(config)#service-port vlan 50 vdsl mode atm 0/2/0 vpi 0 vci 35 rx-cttr 10
tx-cttr 10

huawei(config)#save
----End
Result
After the configuration, the two branches of the enterprise can communicate with each other.
Issue 01 (2016-04-29)

367

Access Module
Configuration File
vlan 50 smart
vlan attrib 50 q-in-q
port vlan 50 0/19 0
bpdu tunnel vlan 50 enable
traffic table ip index 10 cir 4096 priority user-cos 4 priority-policy localSetting
interface vdsl 0/2
deactivate 0
alarm-config 0 1
quit
service-port vlan 50 vdsl mode atm 0/2/0 vpi 0 vci 35 rx-cttr 10 tx-cttr 10
save
4.2 Example of the VLAN Stacking Multi-ISP Wholesale

Access
In a Layer-2 switching metropolitan area network (MAN), there are multiple Internet service
providers (ISPs). To provision the services provided by the ISP to the specified user group
rapidly, the outer VLAN tags of VLAN stacking can be used to identify ISPs, while the inner
VLAN tags to identify users. In this way, different user groups can be connected to the
specified ISPs in batches through different outer VLAN tags to obtain services from the ISPs.
Prerequisites
l
The authentication data of the access user must be configured on the BRAS.
l
The two ISPs in the Layer-2 switching MAN provide broadband services to enterprise
users. Different enterprise user groups are bulk connected to the specified ISP to obtain
services provided by the ISP.
The access device uses xDSL or LAN access.
Networking
Figure 4-2 shows an example network for configuring the VLAN stacking multi-ISP
wholesale access.
Enterprise 1 and 2 belong to ISP 1, and enterprise 3 and 4 belong to ISP 2. Based on the
VLAN stacking feature. The upper-layer network must work in the Layer 2 mode, and must
forward packets according to the VLAN and the MAC address. The MA5600T/MA5603T/
MA5608T adds the outer VLAN tag to differentiate ISPs and inner VLAN tag to differentiate
users and forwards the user packet to the Layer 2 network. Then the Layer 2/Layer 3 LAN
switch forwards the user packets to the specified ISP BRAS based on the outer VLAN tag.
The ISP BRAS removes the outer VLAN tag and identify the users based on the inner VLAN
tag. After passing the authentication, the enterprise users can obtain various services provided
by the ISP.
Issue 01 (2016-04-29)

368

Access Module
Figure 4-2 Example network for configuring the VLAN stacking multi-ISP wholesale access
ISP1
ISP2
MAN
(Lay 2 network)
BRAS
BRAS
L2/L3 LAN Switch

VLAN 61 VLAN 12
VLAN 60 VLAN 12
VLAN 61 VLAN 11
VLAN 60 VLAN 11
Access node
Modem
Enterprise 1
Enterprise 2
Enterprise 3
Enterprise 4
Enterprise 1 to ISP 1
Data Plan
Table 4-2 lists the key data planning of the VLAN stacking wholesale service on the
MA5600T/MA5603T/MA5608T. The ADSL2+ access is used as an example.
Issue 01 (2016-04-29)

369

Access Module
Table 4-2 Data plan for configuring the VLAN stacking wholesale service
Item
Data
Remarks
VLAN
VLAN ID:
The outer VLAN identifies

the ISP, and inner VLAN
identifies the user. The inner
VLAN tags must be unique
under the same ISP, but can
be the same under different
ISPs.
l ISP1: 60
Enterprise user 1: 11
l ISP2: 61
l VLAN type: smart VLAN
l VLAN attribute: stacking
Upstream
port
0/19/0
Traffic
profile
l Traffic profile ID: 10
The CIR depends on the user

bandwidth requirement.
l CIR: 2 Mbit/s
l Priority copy policy: user-cos
l Default 802.1p priority of the packet: 4
l Priority-based scheduling policy of the
downstream packets: local-setting
ADSL2+
port
l ADSL2+ port ID
Enterprise user 1: 0/2/0

l Default ADSL2+ line profile: 1
l Default ADSL2+ alarm profile: 1
Service
virtual
port
l Service port ID:

l VPI: 0
l The VPI/VCI is the same

as the management
VPI/VCI on the peer
modem.
l The traffic profile that
meets the service
requirement is used.
l VCI: 35
l ID of the traffic profile in Rx direction:
10
l ID of the traffic profile in Tx direction:
10
Issue 01 (2016-04-29)

370

Access Module
Procedure
Step 1 Create VLANs.
The outer VLAN IDs are 60 and 61, and the VLANs are smart VLANs.
huawei(config)#vlan 60-61 smart
It will take several minutes, and console may be timeout, please use command
idle-timeout to set time limit
Are you sure to add VLANs? (y/n)[n]:y
Step 2 Set the VLAN attribute to stacking.

huawei(config)#vlan attrib 60-61 stacking
Are you sure to continue? (y/n)[n]:y
Step 3 Add an upstream port to the VLANs.

Add upstream port 0/19/0 to VLANs 60 and 61.
huawei(config)#port vlan 60-61 0/19 0
Are you sure to add standard port(s)? (y/n)[n]:y
The total of the VLANs having been processed is 2
The total of the port VLAN(s) having been added is 2

The profile ID is 10, the CIR is 2 Mbit/s, and packets are scheduled according to the priority
specified in the traffic profile.
huawei(config)#traffic table ip index 10 cir 2048 priority user-cos 4 priority-policy localSetting
Step 5 Activate the ADSL2+ port and bind a profile to it.
Use the default ADSL2+ line profile 1. Activate the ADSL2+ port and bind alarm profile 1 to
the port. The following uses port 0/2/0 as an example. The configuration of the other three
ADSL2+ ports are similar to that of port 0/2/0.
NOTE
l By default, the port is in the activated state. Before binding a profile to the port, you must deactivate the
port.
Step 6 Add service ports to the VLANs.

Add service ports to the VLANs, and use traffic profile 10 that meets the service
requirements. The VPI and the VCI are 0 and 35 respectively, the same as those on the peer
modem.
10
10
10
10
0 vlan 60 adsl 0/2/0 vpi 0 vci 35 rx-cttr 10 tx-cttr

Step 7 Set the inner VLAN tags.

Issue 01 (2016-04-29)

371

Access Module
The inner VLAN tag identifies the user. Note that the inner VLAN tag must be unique in one
ISP domain, and the inner VLAN tags can be the same in different ISP domains.
huawei(config)#stacking
label
label
label
label
service-port
service-port
service-port
service-port
0
1
2
3
11
12
11
12

huawei(config)#save
----End
Result
l
After passing the authentication by the ISP1 BRAS, enterprise 1 and enterprise 2 can
obtain the service provided by ISP1.
After passing the authentication by the ISP2 BRAS, enterprise 3 and enterprise 4 can
obtain the service provided by ISP2.
Configuration File
vlan 60-61 smart
Are you sure to add VLANs? (y/n)[n]:y
The total of the added VLANs is 2
vlan attrib 60-61 stacking
Are you sure to continue? (y/n)[n]:y
The total of the VLAN(s) which have been operated successfully is 2
port vlan 60-61 0/19 0
The total of the port VLAN(s) having been added is 2
traffic table ip index 100 cir 2048 priority user-cos 4 priority-policy localSetting
save
4.3 Example of the PWE3 Private Line Service

This topic describes how to configure the MPLS PWE3 private line service using examples.
Context
For the PWE3 service model and network application, see Configuring the PWE3 Private
Line Service.
Issue 01 (2016-04-29)

372

Access Module
PWE3 encapsulation may be performed in the following typical scenarios based on user-side
service types and upstream network types.
User-Side
Service
Upstream
Network
Application
ATM
IP
Mainly used for the ATM network reconstruction. When

the IP protocol is deployed for the transmission network
and the ATM network evolves to the IP network, PWE3
encapsulation is recommended.
ATM
MPLS
Mainly used for the ATM network reconstruction. When

the MPLS protocol is deployed for the transmission
network and the ATM network evolves to the IP
network, PWE3 encapsulation is recommended.
ETH
MPLS
Mainly used for private network data interaction

between different enterprise branches.
TDM
IP
Mainly used to integrate the TDM circuit into the packet

switched network (PSN) to provide more value-added
services. When the IP protocol is deployed for the
transmission network and the IP network provides
simulated TDM services, PWE3 encapsulation is
recommended.
TDM
MPLS
Mainly used to integrate the TDM circuit into the PSN

to provide more value-added services. When the MPLS
protocol is deployed for the transmission network and
the IP network provides simulated TDM services,
PWE3 encapsulation is recommended.
4.3.1 Configuring ATM PWE3 to Implement Migration (IP)

ATM PWE3 applies to ATM network reconstruction. If the IP protocol is used in the transport
network, ATM PWE3 is recommended to migrate the ATM network to an IP network.
l
The original ATM DSLAM is replaced by the MA5600T/MA5603T/MA5608T and the

upper-layer ATM BRAS remains.
ATM service data is transparently transmitted across the network.
The quality of service (QoS) such as traffic and priority, can be guaranteed for real-time
ATM services.
Networking
Figure 4-3 shows an example network of the ATM PWE3.
l
Users access to MA5600T/MA5603T/MA5608T using xDSL service boards.
The PW encapsulation mode is used to enable the transparent transmission of data over
the IP network.
Issue 01 (2016-04-29)

373

Access Module
PWs in the Ntol mode are used. Specifically, one PW is bound to multiple PVCs so that
the same service from multiple users is carried by the same PW.
In the upstream direction, the trTCM by CoS remarking based on PWs is used; in the
downstream direction, the early drop based on CoS threshold is used. In this way, QoS
can be guaranteed for various services.
Figure 4-3 Example network of the ATM PWE3

Before migration
ISP
ATM DSLAM
Modem
xDSL
BRAS
ATM
Network
After migration
ISP
IP DSLAM
Modem
xDSL
PE
GE
BRAS
PSN
ATM PWE3
Prerequisite
l
The xDSL board and the SPUB board must be in position and must work in the normal
state.
The static routing protocol or the OSPF protocol must be successfully configured on
each device in the network (the host route of each port must be successfully advertised).
Context
For the principle and configuration of trTCM by CoS remarking, see Configuring PW-based
trTCM by CoS Remarking.
The following ATM service types are available:
l
Unspecified bit rate (UBR): UBR services support non-real-time applications, such as
file transferring and Email. These applications have low requirements on delay or delay
changes.
Variable bit rate (VBR): VBR services can be further classified into real-time variable bit
rate (rt-VBR) services and non-real-time variable bit rate (nrt-VBR) services. Both rtVBR and nrt-VBR services support changeable (burst) cell transmitting rate at the source
end. The rt-VBR service type mainly applies to voice and video services.
Constant bit rate (CBR): The CBR service type usually applies to real-time services that
have high requirements on delay changes. Such services include voice, video, and circuit
emulation services.
Issue 01 (2016-04-29)

374

Access Module
Data Plan
Table 4-3 lists the data plan for configuring the ATM PWE3.
Table 4-3 Key data plan for configuring the ATM PWE3
Item
Data
Remarks
MPLS
LSR ID: 5.5.5.5
The LSR ID must be the same as

the IP address of the loopback
interface on the device. To
differentiate between the LSR ID
and other IP addresses, set the LSR
ID to a special unique value so that
it identifies the device intuitively.
The MPLS feature must be enabled
for:
1. Global
2. L2VPN
3. VLAN and VLAN interfaces
VLAN
Smart VLAN: 300

IP address of the VLAN interface:
192.168.1.20
VLAN and VLAN interfaces must

be configured to enable MPLS
forwarding.
Upstream port: 0/19/1

PW
parameters
Peer IP address: 7.7.7.7

PW type: ATM Nto1 VCC
Control word: enabled
(Optional) Maximum number of
concatenated ATM cells: 4
(Optional) Maximum
encapsulation delay of ATM cells:
10 ms
PW type: static
Tunnel
Tunnel ID: 20; tunnel interface ID:

20
Encapsulation protocol of the
tunnel interface at the data link
layer: MPLS IP
The control word adds control

information into service packets to
rearrange the packets and to
prevent packet disorder. ATM
services must use the control word
since they have high requirements
on time sequence.
Cell concatenation enables a PW
packet to carry multiple ATM cells.
In this way, the transmission
efficiency of ATM cells over a PSN
network and bandwidth utilization
are improved.
IP tunnels are used.
Ingress and egress addresses of a
tunnel are the LSR IDs of the local
device and the peer PE device,
respectively.
Source IP address of the tunnel:

5.5.5.5
Destination IP address of the
tunnel: 7.7.7.7
Issue 01 (2016-04-29)

375

Access Module
Item
Data
Remarks
OSPF
OSPF process ID: 200; OSPF area

ID: 1
Routes use the OSPF protocol.
PWE3
gateway
LSR ID: 7.7.7.7
It is the LSR ID of the peer PE

device.
Table 4-4 Plan for configuring attributes of each type of service

service Type
Item
Board
Slot
UBR
VBR
CBR
0/2
0/3
0/4
Remarks
Multiple services of the same

type but from different users are
deployed at different ports on the
same board (in the same slot). By
doing so, the same PW is used to
carry multiple PVCs. This
improves the transmission
efficiency, reduces the number of
PWs required, and facilitates the
application of QoS policies.
Services of different types are
deployed on boards in different
slots, isolating the services
physically.
Issue 01 (2016-04-29)
VPI/V
CI of
Cells
0/35
0/35
0/35
Since the services belong to the

same ISP, the VPI/VCI
parameters of cells on PVCs at
different ports are the same.
Bindin
g PW
ID
20
21
22
Services of different types are

carried over different PWs,
eliminating service interaction.
Initial
Value
for
Ingress
PVC in
the PW
0/32
0/33
0/34
Initial
Value
for
Egress
PVC in
the PW
1/32
1/33
1/34
Since the VPI/VCI parameters of

cells on PVCs at different ports
are the same, the VPI/VCI
parameters must be changed once
before the cells on client-side
PVCs are encapsulated into PWs.
This ensures that the VPI/VCI
parameters are unique for cells on
each PVC in the PW.

376

Access Module
Item
service Type
Remarks
UBR
VBR
CBR
Egress
Label
of the
PW
8450
8451
8452
Ingress
Label
of the
PW
8460
8461
8462
PW
CAR
12288
Kbit/s
30720
Kbit/s
6144 Kbit/s
UserCoS
Priority
CoS
Priority
After
Remar
king
QoS policies:
In the upstream direction,
priorities of service packets are
remarked by setting CAR and
PIR for the PW and only yellow
packets are identified (CAR <
Rate < PIR).
WRED
Profile
ID: 5
ID: 5
ID: 5
QoS policies:
Traffic
Profile
l CAR:
OFF
l CAR:
OFF
l Color
policy:
cosremark
l Color
policy:
cosremark
l Downst
ream
priority
policy:
tag-inpackag
e
l Downst
ream
priority
policy:
tag-inpackag
e
In the downstream direction, the

xDSL board sets CoS drop
threshold globally to early drop
yellow packets.
l CAR: OFF
l Color policy:
cos-remark
The traffic profile does no limit

the rate. Instead the rate is limited
using PWs.
l Downstream
priority
policy: tagin-package
Procedure
Step 1 Configure a VLAN and add an upstream port to the VLAN.
Create upstream VLAN 300 and add upstream port 0/19/1 to VLAN 300.
Issue 01 (2016-04-29)

377

Access Module

Step 2 Enable MPLS.

1.
Configure the IP address of the loopback interface.

Configure the IP address of loopback interface 0 to 5.5.5.5/32.
huawei(config)#interface loopback 0
huawei(config-if-loopback0)#ip address 5.5.5.5 32
huawei(config-if-loopback0)#quit
2.
Configure the LSR ID of the MPLS and enable global MPLS function and Layer 2 VPN.
huawei(config)#mpls lsr-id 5.5.5.5
huawei(config)#mpls
huawei(config-mpls)#quit
huawei(config)#mpls l2vpn
3.
Enable the MPLS function for VLAN 300, configure the IP address of the VLAN
interface 300, and enable the MPLS function for it.
huawei(config)#mpls vlan 300
huawei(config-if-vlanif300)#mpls
Step 3 Configure a route.

PWE3 has no special requirement for the routing policy. Either a static route or an OSPF
dynamic route can be configured. Because OSPF supports MPLS RSVP-TE extension, an
OSPF dynamic route is recommended.
huawei(config)#ospf 1
huawei(config-ospf-1)#area 200
huawei(config-ospf-1-area-0.0.0.200)#network 192.168.1.0 0.0.0.255
huawei(config-ospf-1-area-0.0.0.200)#return
Step 4 Configure a PWE3 outer tunnel.

Configure the tunnel ID to 20 and the encapsulation protocol of the tunnel interface at the data
link layer to MPLS IP.
huawei#config
huawei(config)#interface tunnel 20
huawei(config-if-tunnel20)#tunnel-protocol mpls ip
Configure the source IP address of the tunnel to 5.5.5.5.

huawei(config-if-tunnel20)#source 5.5.5.5
Configure the destination IP address of the tunnel to 7.7.7.7.

huawei(config-if-tunnel20)#destination 7.7.7.7
huawei(config-if-tunnel20)#quit
Step 5 Configure the tunnel policy.

Configure the policy name to atmpw-plcy.
huawei(config)#tunnel-policy atmpw-plcy
Info: New tunnel-policy is configured.
huawei(config-tunnel-policy-atmpw-plcy)#tunnel select-seq ip load-balance-number
1
huawei(config-tunnel-policy-atmpw-plcy)#quit
Step 6 Configure the PW parameters.

Issue 01 (2016-04-29)

378

Access Module
NOTE
Take the configuration of PW 20 for example. To configure the PW 21 and PW 22 based on the data plan
using the same steps.
1.
Configure the PW ID to 20.

huawei(config)#pw-para 20
2.
Configure the LSR ID of the peer PWE3 gateway in the PW. Configure the LSR ID of
the PWE3 gateway to 7.7.7.7.
huawei(config-pw-para-20)#peer-address 7.7.7.7
3.
Configure the PW type to ATM NTo1 VCC.

huawei(config-pw-para-20)#pw-type atm nto1 vcc
4.
Configure the PW to support the control word.

huawei(config-pw-para-20)#control-word
5.
(Optional) Set the maximum number of concatenated ATM cells to 4.

huawei(config-pw-para-1)#max-atm-cells 4
6.
(Optional) Set the maximum encapsulation delay of ATM cells to 10 ms.

huawei(config-pw-para-1)#max-encapcell-delay 10
7.
Configure the tunnel policy used by the PW.

Configure the tunnel policy name to atmpw-plcy.
huawei(config-pw-para-20)#tnl-policy atmpw-plcy huawei(config-pw-para-20)#quit
Step 7 Configure a traffic profile.

1.
For UBR services, set the upstream/downstream traffic profile to 20, CIR to off (limiting
rate only on BRAS), color policy to CoS, user-side packet mapping mode to outer-layer
802.1p, default 802.1p to 1, and priority policy to tag-in-package.
huawei(config)#traffic table ip index 20 cir off color-policy cos priority
user-cos 1 priority-policy tag-in-package
NOTE
2.
The color policy in the upstream and downstream traffic profiles must be the same.
If the color policy is cos-remark, the priority policy must be tag-in-package for the downstream
direction.
For VBR services, set the upstream traffic profile to 21, CIR to off, color policy to CoS,
user-side packet mapping mode to outer-layer 802.1p, default 802.1p to 4, and priority
policy to tag-in-package.
3.
For CBR services, set the upstream traffic profile to 22, CIR to off, color policy to CoS,
user-side packet mapping mode to outer-layer 802.1p, default 802.1p to 5, and priority
policy to tag-in-package.
Step 8 Create an ATM access service stream.

ATM cells must be encapsulated into ATM over Ethernet (AOE) packets before being carried
by PWs. That is, create an ATM service stream.
l
Create AOE service streams in batches for UBR services.

The service board is in slot 0/2, VPI/VCI is 0/35, and the traffic profile for the upstream
and downstream directions is 20.
huawei(config)#multi-service-port vlan aoe board 2 vpi 0 vci 35 inbound
traffic-table index 20 outbound traffic-table index 20
l
Issue 01 (2016-04-29)
Create AOE service streams in batches for VBR services.

379

Access Module
Create AOE service streams in batches for CBR services.

Step 9 Bind the PVCs to PW 20 in batches to create an ATM PWE3 service.

Since the VPI/VCI parameters of cells on PVCs at different ports are the same, the VPI/VCI
parameters must be changed once before the cells on client-side PVCs are encapsulated into
PWs. This ensures that the VPI/VCI parameters are unique for cells on each PVC in the PW.
l
Bind PVCs and PWs in batches for UBR services.

huawei(config)#multi-pw-ac-binding pvc board 2 vpi 0 vci 35 from-outvpi 0
outvci 32
from-invpi 1 invci 32 pw 20 static transmit-label 8450 receive-label 8460
Bind PVCs and PWs in batches for VBR services.

outvci 33
Bind PVCs and PWs in batches for CBR services.

outvci 34
Step 10 Configure the WRED profile.

The index is 5. Configure the WRED profile so that green packets are not dropped, lower
threshold for dropping yellow packets is 50, upper threshold for dropping yellow packets is
80, and the packet dropping percentage is 100.
huawei(config)#wred-profile index 5 green low-limit 100 high-limit 100
discard-probability 0 yellow low-limit 50 high-limit 80 discard-probability 100
Step 11 Configure queues and bind the WRED profile.

huawei(config)#queue-wred queue0 5 queue1 5 queue2 5 queue3 5 queue4 5 queue5 5
queue6 5 queue7 5
Step 12 Configure the priority remarking policy.

Remark the priority of yellow packets. Specifically, remark priority 1 (UBR service packets)
to 0; priority 4 (VBR service packets) to 2, and priority 5 (CBR service packets) to 5.
huawei(config)#cos-remark cos1 0 cos4 2 cos5 5
Step 13 Configure the mapping between queues and 802.1p priorities.

Packets with 802.1p priorities 0 and 1 join queue 1; packets with 802.1p priorities 2 and 4 join
queue 4; packets with 802.1p priority 5 join queue 5.
NOTE
Ensure that the packets with the CoS values before and after remarking join the same queue.
huawei(config)#cos-queue-map cos0 1 cos1 1 cos2 4 cos4 4 cos5 5
Step 14 Set committed rate in the PW upstream direction.

l
Set CAR in the upstream direction of PW 20 to 12288 kbit/s.

huawei(config)#mpls car-pw 20 cir 12288

Issue 01 (2016-04-29)

380

Access Module

----End
Result
l
UBR, VBR, and CBR services can be migrated to an IP network smoothly. No change is
required on the user side and users will not feel any change.
Various services are scheduled based on their priorities. When a congestion occurs on the
network, the quality of CBR services is guaranteed with precedence.
When a congestion occurs at a port, the system first drops traffic of the burst bandwidth
(bandwidth > peak value), ensuring the guaranteed bandwidth for each type of service.
Configuration File
vlan 300 smart
interface loopback 0
quit
mpls lsr-id 5.5.5.5
mpls
quit
mpls l2vpn
mpls vlan 300
ip address 192.168.1.20 24
mpls
quit
ospf 1
area 200
network 192.168.1.0 0.0.0.255
network 5.5.5.5 0.0.0.0
return
config
interface tunnel 20
tunnel-protocol mpls ip
destination 7.7.7.7
quit
tunnel-policy atmpw-plcy
tunnel select-seq ip load-balance-number 1
quit
pw-para 20
peer-address 7.7.7.7
pw-type atm nto1 vcc
control-word
max-atm-cells 4
max-encapcell-delay 10
tnl-policy atmpw-plcy
quit
traffic table ip index 20 cir off color-policy cos priority user
-cos 1 priority-policy tag-in-package
multi-service-port vlan aoe board 2 vpi 0 vci 35 inbound traffi
c-table index 20 outbound traffic-table index 20
multi-pw-ac-binding pvc board 2 vpi 0 vci 35 from-outvpi 0 outvci 32
Issue 01 (2016-04-29)

381

Access Module

wred-profile index 5 green low-limit 100 high-limit 100 discard-probability
0 yellow low-limit 50 high-limit 80 discard-probability 100
queue-wred queue0 5 queue1 5 queue2 5 queue3 5 queue4 5 queue5 5
queue6 5 queue7 5
cos-remark cos1 0 cos4 2 cos5 5
cos-queue-map cos0 1 cos1 1 cos2 4 cos4 4 cos5 5
mpls car-pw 20 cir 12288
4.3.2 Configuring the ATM PWE3 to Achieve emulated

Services(MPLS)
ATM PWE3 is mainly used in ATM network reconstruction. When the MPLS protocol is
deployed for the transmission network and the ATM network evolves to the MPLS network,
PWE3 encapsulation is recommended.
l
The xDSL service board (or AIUG board) of the MA5600T/MA5603T/MA5608T is

used to provide the ATM service.
The PW encapsulation mode is adopted so that data can be transparently transmitted in

the MPLS network.
The xDSL board (or AIUG board) and the SPUB board must be in position and must
Prerequisite
Context
The implementation process of the ATM PWE3 (MPLS-based) is as follows:
1.
The xDSL modem or ATM DSLAM transmits the ATM service to the xDSL or AIUG
board of the MA5600T/MA5603T/MA5608T.
2.
The control board sends ATM packets to the SPUB board.
3.
After performing the PW and MPLS encapsulation for the packets, the SPUB board
performs the MPLS packet header encapsulation and then sends them to the control
board.
4.
The control board performs the Layer 2 forwarding and sends the packets to the
upstream port.
5.
The packets are sent over the MPLS network to the peer PWE3 gateway (such as the
PTN).
6.
The PWE3 gateway restores the ATM cells and sends them to the peer ATM device.
Networking
Figure 4-4 shows an example network of the ATM PWE3 (MPLS-based).
Issue 01 (2016-04-29)

382

Access Module
Figure 4-4 Example network of the ATM PWE3 (MPLS-based)
Modem
Modem
xDSL
PWE3
Gateway
Access
node
xDSL
MPLS
Network
ATM DSLAM
ATM
ATM DSLAM
ATM
ATM PWE3
Data Plan
Table 4-5 lists the data plan for configuring the ATM PWE3 (MPLS-based).
Table 4-5 Data plan for configuring the ATM PWE3 (MPLS-based)
Item
Data
MPLS
LSR ID: 5.5.5.5

Global MPLS TE: enabled
MPLS Layer 2 VPN: enabled
VLAN MPLS RSVP-TE: enabled
VLAN
Standard VLAN for MPLS forwarding: 300

MPLS address of the VLAN interface: 192.168.2.20
PW parameters
PW ID: 20
PW type: ATM Nto1 VCC
PW in VPI/VCI: 0/35
PW out VPI/VCI: 8/35
PW type: static
PW out port: 8450
PW in port: 8460
Tunnel
Tunnel ID: 20; tunnel interface ID: 20

Encapsulation protocol of the tunnel interface at the data link
layer: MPLS TE
Tunnel signaling protocol: RSVP-TE
Issue 01 (2016-04-29)

383

Access Module
Item
Data
ATM service port
Port: 0/2/0
Emulation SVLAN: 3001

VPI/VCI: 0/35
OSPF
OSPF process ID: 200; OSPF area ID: 1

Enable MPLS TE for the OSPF area
PWE3 gateway
LSR ID: 7.7.7.7
Procedure
Step 2 Enable MPLS.

1.

2.
Configure the LSR ID of the MPLS and enable global MPLS TE and Layer 2 VPN.
huawei(config)#mpls
huawei(config-mpls)#mpls te
huawei(config-mpls)#mpls rsvp-te
3.
Enable the VLAN interface MPLS TE function and configure the IP address of the
VLAN interface.
huawei(config-if-vlanif300)#mpls te
huawei(config-if-vlanif300)#mpls rsvp-te

huawei(config-ospf-1)#opaque-capability enable..//Enable the opaque capability
huawei(config-ospf-1-area-0.0.0.200)#mpls-te enable standard-complying //Enable
MPLS TE for the OSPF area
Issue 01 (2016-04-29)

384

Access Module

link layer to MPLS TE.
huawei#config
huawei(config-if-tunnel20)#tunnel-protocol mpls te

Configure the ID of the MPLS TE tunnel interface to 20. The tunnel ID and LSR ID uniquely
identify an MPLS TE tunnel.
huawei(config-if-tunnel20)#mpls te tunnel-id 20
Configure the signaling protocol of the MPLS TE tunnel to RSVP-TE.

huawei(config-if-tunnel20)#mpls te signal-protocol rsvp-te
Configure the MPLS TE tunnel for being bound by a VPN instance.

huawei(config-if-tunnel20)#mpls te reserved-for-binding
Commit the configuration and quit the tunnel configuration.

huawei(config-if-tunnel20)#mpls te commit

Configure the policy name to atmpw-plcy.
huawei(config)#tunnel-policy atmpw-plcy
huawei(config-tunnel-policy-atmpw-plcy)#tunnel binding destination 7.7.7.7 te
tunnel 20
huawei(config-tunnel-policy-atmpw-plcy)#quit

NOTE
Take the configuration of PW 20 for example. To configure the PW 21 and PW 22 based on the data plan
using the same steps.
1.

2.
3.
Configure the PW type to ATM NTo1 VCC.

huawei(config-pw-para-20)#pw-type atm nto1 vcc
4.

5.
(Optional) Set the maximum number of concatenated ATM cells to 4.

huawei(config-pw-para-1)#max-atm-cells 4
6.
(Optional) Set the maximum encapsulation delay of ATM cells to 10 ms.

huawei(config-pw-para-1)#max-encapcell-delay 10
7.

Configure the tunnel policy name to atmpw-plcy.
huawei(config-pw-para-20)#tnl-policy atmpw-plcy huawei(config-pw-para-20)#quit
Issue 01 (2016-04-29)

385

Access Module
Step 7 Create an ATM access service stream.

ATM cells must be encapsulated into ATM over Ethernet (AOE) packets before being carried
by PWs. That is, create an ATM service stream.
l
Create AOE service streams in batches for UBR services.

Create AOE service streams in batches for VBR services.

Create AOE service streams in batches for CBR services.

Step 8 Bind the PVCs to PW 20 in batches to create an ATM PWE3 service.

Since the VPI/VCI parameters of cells on PVCs at different ports are the same, the VPI/VCI
parameters must be changed once before the cells on client-side PVCs are encapsulated into
PWs. This ensures that the VPI/VCI parameters are unique for cells on each PVC in the PW.
l
Bind PVCs and PWs in batches for UBR services.

outvci 32
Bind PVCs and PWs in batches for VBR services.

outvci 33
Bind PVCs and PWs in batches for CBR services.

outvci 34
Step 9 Query the PW status.

huawei(config)#display pw-ac-binding pvc 0/2/0 vpi 0 vci 35
Total : 1 (Up/Down :
1/0
Static/LDP :
1/0)
---------------------------------------------------------------------------F/S/P
PW
PW
PROTO RECEIVE TRNS
PW
VPIVCI
ID
STATE TYPE
LABEL
LABEL
INDEX
---------------------------------------------------------------------------0/2/0 0 35
20
up
static 8460
8450
20
---------------------------------------------------------------------------Note : F--Frame, S--Slot, P--Port
*: Secondary
----End
Result
The ATM packets can be transparently transmitted in the MPLS network and the ATM-based
services can be provided normally.
Issue 01 (2016-04-29)

386

Access Module
Configuration File
vlan 300 standard
quit
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
quit
mpls l2vpn
mpls vlan 300
ip address 192.168.2.20 24
mpls
mpls te
mpls rsvp-te
quit
ospf 1
opaque-capability enable
area 200
mpls-te enable standard-complying
network 192.168.2.0 0.0.0.255
network 5.5.5.5 0.0.0.0
return
config
interface tunnel 20
tunnel-protocol mpls te
destination 7.7.7.7
mpls te tunnel-id 20
mpls te signal-protocol rsvp-te
mpls te reserved-for-binding
mpls te commit
quit
tunnel-policy atmpw-plcy
tunnel binding destination 7.7.7.7 te tunnel 20
quit
pw-para 20
pw-type atm nto1 vcc
control-word
vccv cc cw alert ttl cv lsp-ping
tnl-policy atmpw-plcy
quit
service-port vlan aoe adsl 0/2/0 vpi 0 vci 35 rx-cttr 6 tx-cttr 6
service-port vlan aoe atm 0/2/0 vpi 0 vci 35 rx-cttr 6 tx-cttr 6
pw-ac-bnding pvc 0/2/0 vpi 0 vci 35 outvpi 8 outvci 35 pw 20
static transmit-label 8450 receive-label 8460
//xDSL access
//ATM access
4.3.3 Configuring the ETH PWE3 to Emulate Ethernet Services

(MPLS)
The MA5600T/MA5603T/MA5608T supports the PW encapsulation for ethernet packets and
implements the ETH PWE3 emulation service after the MPLS encapsulation of the packets,
providing the solution of emulation Ethernet private line service over the MPLS network.
l
The data interaction between enterprise branches in different regions is achieved through
the metropolitan area network (MAN) that is running the MPLS protocol.
The Ethernet service data of the enterprise private network is transparently transmitted so
that the data security can be ensured.
Issue 01 (2016-04-29)

387

Access Module
Prerequisite
l
The SPUB board must be in position and must work in the normal state.
Context
The Ethernet packet-based data interaction between enterprise branches in different regions is
achieved using the routers of the public network to forward the packets. If the public network
uses the MPLS protocol, the Ethernet packets cannot be forwarded directly. In this case, the
Ethernet packet forwarding can be achieved by using the ETH PWE3 technology. In addition,
the ETH PWE3 technology can be deployed to achieve high security with low costs.
Networking
Figure 4-5 shows an example network of the ETH PWE3.
1.
The Ethernet switch or router of the enterprise aggregates the private network data of the
enterprise and sends the data to the ETH board of the MA5600T/MA5603T/MA5608T.
2.
The control board sends ETH packets to the SPUB board.
3.
After performing the PW and MPLS encapsulation for the packets, the SPUB board
performs the ETH packet header encapsulation and then sends them to the control board.
4.
The control board performs the Layer 2 forwarding and sends the packets to the
upstream port.
5.
The packets are sent over the MPLS network to the peer PWE3 gateway (such as the
PTN).
6.
The PWE3 gateway restores ETH signals and sends them to the peer Ethernet switch or
router.
Figure 4-5 Example network of the ETH PWE3

LAN Switch
FE/GE
Access
Node
PWE3
Gateway
MPLS
Network
Router
FE/GE
LAN Switch
FE/GE
Router
FE/GE
ETH PWE3
Data Plan
Table 4-6 lists the data plan for configuring the ETH PWE3.
Issue 01 (2016-04-29)

388

Access Module
Table 4-6 Data plan for configuring the ETH PWE3

Item
Data
MPLS
LSR ID: 5.5.5.5

Global MPLS TE: enabled
VLAN MPLS RSVP-TE: enabled
VLAN
Standard VLAN for MPLS forwarding: 200

IP address of the VLAN interface: 192.168.1.10
PW parameters
PW ID: 10
PW type: ETH tagged
Out label: 8500
In label: 8600
Tunnel
Tunnel ID: 10; tunnel interface ID: 10

layer: MPLS TE
Tunnel signaling protocol: RSVP-TE
ETH service port
Port: 0/4/0
Emulation SVLAN: 3001
CVLAN: 20
OSPF
OSPF process ID: 100; OSPF area ID: 1

Enable MPLS TE for the OSPF area
PWE3 gateway
LSR ID: 6.6.6.6
Procedure
Step 2 Enable MPLS.

1.

Issue 01 (2016-04-29)

389

Access Module
2.
Configure the LSR ID of the MPLS and enable global MPLS TE and Layer 2 VPN.
huawei(config)#mpls
huawei(config-mpls)#mpls te
huawei(config-mpls)#mpls rsvp-te
3.
Enable the VLAN interface MPLS TE function and configure the IP address of the
VLAN interface.
huawei(config-if-vlanif200)#mpls te
huawei(config-if-vlanif200)#mpls rsvp-te

huawei(config-ospf-1)#opaque-capability enable..//Enable the opaque capability
huawei(config-ospf-1-area-0.0.0.100)#mpls-te enable standard-complying //Enable
MPLS TE for the OSPF area

link layer to MPLS TE.
huawei#config
huawei(config-if-tunnel10)#tunnel-protocol mpls te

Configure the ID of the MPLS TE tunnel interface to 10. The tunnel ID and LSR ID uniquely
identify an MPLS TE tunnel.
huawei(config-if-tunnel10)#mpls te tunnel-id 10
Configure the signaling protocol of the MPLS TE tunnel to RSVP-TE.

huawei(config-if-tunnel10)#mpls te signal-protocol rsvp-te
Configure the MPLS TE tunnel for being bound by a VPN instance.

huawei(config-if-tunnel10)#mpls te reserved-for-binding
Commit the configuration and quit the tunnel configuration.

huawei(config-if-tunnel10)#mpls te commit

Configure the policy name to ethpw-plcy.
Issue 01 (2016-04-29)

390

Access Module
huawei(config)#tunnel-policy ethpw-plcy
huawei(config-tunnel-policy-ethpw-plcy)#tunnel binding destination 6.6.6.6 te
tunnel 10
huawei(config-tunnel-policy-ethpw-plcy)#quit

1.

2.
3.
Configure the PW type to ethernet tagged.

huawei(config-pw-para-10)#pw-type ethernet tagged
4.

5.
Enable the virtual circuit connectivity verification (VCCV) function.

huawei(config-pw-para-10)#vccv cc cw alert ttl cv lsp-ping
6.

Configure the tunnel policy name to ethpw-plcy.
huawei(config-pw-para-10)#tnl-policy etnpw-plcy
huawei(config-pw-para-10)#quit
Step 7 Create an Ethernet access service port.

Create a VLAN for the ETH emulation service (after ETH emulation, this VLAN will be
restored by the peer ETH PWE3 gateway), and then create a service port for translating the
CVLAN ID into the VLAN ID of the emulation service.
huawei(config)#vlan 3001
huawei(config)#service-port vlan 3001 eth 0/4/0 multi-service user-vlan 20 rxcttr 6 tx-cttr 6
Step 8 Bind the VLAN to the PW to create the ETH PWE3 service.
Bind emulation SVLAN 3001 to PW 10, and set PW type to static PW, out label of the PW to
8500, and in label of the PW to 8600.
huawei(config)#pw-ac-binding vlan 3001 pw 10 static transmit-label 8500 receivelabel 8600
Step 9 Query the PW status.

huawei(config)#display pw-ac-binding vlan 3001
1/0
Static/LDP :
1/0)
---------------------------------------------------------------------------VLAN
PW
PW
PROTO RECEIVE TRNS
PW
ID
ID
STATE TYPE
LABEL
LABEL
INDEX
---------------------------------------------------------------------------3001
10
up
static 8600
8500
10
----------------------------------------------------------------------------
----End
Result
The private network data of the enterprise can be transparently transmitted over the MPLS
network, and all services in the private network can be provided normally.
Issue 01 (2016-04-29)

391

Access Module
Configuration File
vlan 200 smart
quit
mpls lsr-id 5.5.5.5
mpls
mpls te
mpls rsvp-te
quit
mpls l2vpn
mpls vlan 200
ip address 192.168.1.10 24
mpls
mpls te
mpls rsvp-te
quit
ospf 1
opaque-capability enable
area 100
mpls-te enable standard-complying
network 192.168.1.0 0.0.0.255
network 5.5.5.5 0.0.0.0
return
config
interface tunnel 10
tunnel-protocol mpls te
destination 6.6.6.6
mpls te tunnel-id 10
mpls te signal-protocol rsvp-te
mpls te reserved-for-binding
mpls te commit
quit
tunnel-policy ethpw-plcy
tunnel binding destination 6.6.6.6 te tunnel 10
quit
pw-para 10
pw-type ethernet tagged
control-word
tnl-policy ethpw-plcy
quit
vlan 3001
service-port vlan 3001 eth 0/4/0 multi-service user-vlan 20 rx-cttr 6 tx-cttr 6
pw-ac-binding vlan 3001 pw 10 static transmit-label 8500 receive-label 8600
4.3.4 Configuring the TDM PWE3 to Emulate Services (IP)

The MA5600T/MA5603T/MA5608T supports SAToP encapsulation for non-frame E1 signals
and implements the TDM PWE3 emulation service after IP-encapsulating the signals. In this
way, the MA5600T/MA5603T/MA5608T provides emulated TDM private line service over
the IP network.
l
To make full use of legacy TDM line and equipment, and replace legacy DDN network
and ISDN PRI PBX convergence network.
To perform MPLS over IP encapsulation on the E1 data aggregated by the Nx64k private
line and ISDN PRI PBX, and transmit the data upstream as IP packets to the DDN
network or SDH network.
Issue 01 (2016-04-29)

392

Access Module
Prerequisite
l
The H802EDTB board and SPUB board are installed and work in the normal state.
The working mode of the H802EDTB board is set to SAToP by running the board
workmode command.
A static route or dynamic route is successfully configured on each device over the
network so that the IP routes between LSRs are reachable.
Context
The implementation process of TDM PWE3 is as follows:
1.
The data of the Nx64k private line service or ISDN PRI PBX service is converged and
then transmitted to the H802EDTB board of the MA5600T/MA5603T/MA5608T.
2.
After performing SAToP processing (adding CW control word and RTP header) on the
E1 data, the H802EDTB board sends the data to the SPUB board through the control
board.
3.
After performing the PW and MPLS encapsulation on the packets, the SPUB board adds
the ETH header to the packets, and then sends them to the control board.
4.
The control board performs Layer 2 forwarding and sends the packets to the upstream
port.
5.
The packets are sent over the PSN network to the peer PWE3 gateway (such as the
PTN).
6.
The PWE3 gateway restores the E1 signals from the packets and then sends them to the
DDN network or SDH network.
Networking
Figure 4-6 shows an example network of TDM PWE3 (IP-based).
Figure 4-6 Example network of TDM PWE3 (IP-based)
SHDSL Modem
SHDSL
Access
Node
PWE3
Gateway
E1
SDH
IP Network
PRI PBX
E1
E1
TDM PWE3
Data Plan
Table 4-7 lists the data plan for configuring TDM PWE3 (IP-based).
Issue 01 (2016-04-29)

393

Access Module
Table 4-7 Data plan for configuring TDM PWE3 (IP-based)

Parameter
Data
H802EDTB board
Board slot: 0/3

E1 port: 0/3/1
SPUB board
Board slot: 0/5
MPLS
VLAN for MPLS forwarding: VLAN 4001

IP address of VLAN interface 4001: 10.50.50.50/24
MPLS LSR ID: 3.3.3.3
Global MPLS LDP: enabled
PW parameters
PW ID: 2
Template type: TDM SAToP E1
PW load time: 125 s
Jitter buffer size: 2500 s
RTP: enabled
VCCV: enabled
Tunnel
Tunnel interface ID: 10

Tunnel ID: 10
layer: IP
Policy name: ip_policy
Tx clock of the E1 port
Network clock, recovered from PW2
Procedure
Step 1 Configure a loopback interface.
Set the ID of the loopback interface to 0 and its IP address to 3.3.3.3/32.
Step 2 Enable basic MPLS functions.

Set the IP address of loopback interface 0 as the LSR ID.
Enable global MPLS.

huawei(config)#mpls
huawei(config-mpls)#lsp-trigger host
Issue 01 (2016-04-29)
//set up an LSP by triggering the LDP

394

Access Module
through the host address

Enable Layer 2 VPN.

Enable global LDP.

huawei(config)#mpls ldp
huawei(config-mpls-ldp)#quit
NOTE
l Only one session can exist between two LSRs and a local LDP session takes priority over a remote LDP
session. To simplify the configuration, assume that the MA5600T/MA5603T/MA5608T is directly
connected to the PTN. Hence, you need to enable only the LDP function (the local LDP session is
automatically set up after the LDP function is enabled).
l If the MA5600T/MA5603T/MA5608T is not directly connected to the PTN, after the LDP function is
enabled, run the mpls ldp remote-peer command to create an LDP remote peer and then enter the remote
peer mode. Then, run the remote-ipip-addr command to specify the ID of the remote LSR.
l For detailed configurations, see Configuring the LDP LSP.
Step 3 Configure a VLAN and enable MPLS for the VLAN and the VLAN interface.
Add VLAN 4001 for forwarding MPLS packets and add an upstream port to it.
huawei(config)#port vlan 4001 0/19/0
Enable MPLS for VLAN 4001.

Set the IP address of VLAN interface 4001 to 10.50.50.50/24 and enable MPLS LDP for the
VLAN interface.
huawei(config-if-vlanif4001)#mpls ldp

PWE3 has no special requirements for the routing policy. A static route, or dynamic RIP, or
OSPF route can be configured. An OSPF dynamic route is recommended because OSPF
supports MPLS RSVP-TE extension.
Set the OSPF process ID to 100 and OSPF area ID to 1. In addition, configure the interfaces
(VLAN interface and loopback interface) that run OSPF and configure the areas of the
interfaces.

Set the tunnel ID to 10 and the encapsulation protocol of the tunnel interface at the data link
layer to MPLS IP.
huawei(config-if-tunnel10)#tunnel-protocol mpls ip
Issue 01 (2016-04-29)

395

Access Module
Set the destination IP address of the tunnel to the LSR ID of the PTN 9.9.9.9.

Set the policy name to ip_policy.
huawei(config)#tunnel-policy ip_policy
huawei(config-tunnel-policy-ip_policy)#tunnel select-seq ip load-balance-number 1
huawei(config-tunnel-policy-ip_policy)#quit
Step 7 Configure PW parameters.

1.
Create PW 2 and enter the PW parameter mode.

2.
Configure the loopback interface IP address of the remote PTN device.

Set the loopback interface IP address to 9.9.9.9.
3.
Set the PW type to TDM SAToP E1.

huawei(config-pw-para-2)#pw-type tdm satop e1
4.
Configure the PW load time.

Set the load time to 125 s.
huawei(config-pw-para-2)#tdm-load-time satop e1 loadtime 125
5.
Enable RTP. After RTP is enabled, PW packets of the TDM type contain the RTP control
header. By default, RTP is disabled.
NOTE
The RTP configuration must be the same as that on the PTN.

huawei(config-pw-para-2)#rtp-header
6.
(Optional) Configure the jitter buffer size. The jitter buffer can effectively prevent jitter
and latency. Only PW of the TDM type support the jitter buffer configuration. By
default, the jitter buffer size is 2000 s.
NOTE
The value range of the jitter buffer size is 500-32000 and the value must be an integer multiple of 125.
Configure this value according to actual conditions. In this example, the jitter buffer size is set to 2500
s.
huawei(config-pw-para-2)#jitter-buffer buffer-size 2500
7.

8.
Enable virtual circuit connectivity verification (VCCV).

9.
Configure the tunnel policy used by the PW parameters.

Set the tunnel policy name to ip-policy.
huawei(config-pw-para-2)#tnl-policy ip_policy
Step 8 Create a TDM connection.

Set the TDM connection ID to 1, type to PWE3, and ID of the E1 port on the H802EDTB
board to 0/3/1.
huawei(config)#tdm-connect connectid 1 tdm pwe3-uplink 0/3 e1 0/3/1
Issue 01 (2016-04-29)

396

Access Module
Step 9 Bind the TDM connection to the PW to create the PW service of the TDM type.
Bind TDM connection 1 to PW2.
huawei(config)#pw-ac-binding tdm 1 pw 2
Step 10 Confirm that the PW is in the normal state.

On the OLT, run the display pw or display pw-ac-binding command to query the PW status.
Confirm that the PW state is normal (up).
huawei(config)#display pw-ac-binding tdm 1
1/0
Static/LDP :
0/1)
---------------------------------------------------------------------------TDM
PW
PW
PROTO RECEIVE TRNS
PW
ID
ID
STATE TYPE
LABEL
LABEL
INDEX
---------------------------------------------------------------------------1
2
up
LDP
----2
*: Secondary
Step 11 Configure clock synchronization on the E1 port.

Configure the recovery clock source of the H802EDTB board. In the recovery clock mode,
the receive end recovers the clock of the transmit end according to the average arrival rate of
the received SAToP packets. In this example, clock signals are extracted from PW2 to serve as
the recovery clock of a board.
huawei(config-edt-0/3)#adapt-clock-source clock-source 0 2
Configure the Tx clock of E1 port 0/3/1 on the H802EDTB board as the network-side clock.
That is, configure the clock recovered from a TDM PW as the Tx clock of a port,
implementing voice service synchronization.
huawei(config-edt-0/3)#clock-work 1 net
----End
Result
After a network is restructured, the long-term bit error ratio and latency meet the requirements
for actual applications, the Nx64k private line service or ISDN PRI PBX service runs
normally, and the operation method for end users is not changed.
Configuration File
quit
mpls lsr-id 3.3.3.3
mpls
lsp-trigger host
quit
mpls l2vpn
mpls ldp
quit
vlan 4001 smart
port vlan 4001 0/19/0
mpls vlan 4001
ip address 10.50.50.50 24
mpls
mpls ldp
quit
ospf 1
area 100
Issue 01 (2016-04-29)

397

Access Module
network 10.50.50.0 0.0.0.255

network 3.3.3.3 0.0.0.0
return
interface tunnel 10
tunnel-protocol mpls ip
destination 9.9.9.9
quit
tunnel-policy ip_policy
tunnel select-seq ip load-balance-number 1
quit
pw-para 2
pw-type tdm satop e1
tdm-load-time satop e1 loadtime 125
rtp-header
jitter-buffer buffer-size 2500
control-word
tnl-policy ip_policy
quit
tdm-connect connectid 1 tdm pwe3-uplink 0/3 e1 0/3/1
pw-ac-binding tdm 1 pw 2
interface edt 0/3
adapt-clock-source clock-source 0 2
clock-work 1 net
4.3.5 Configuring the TDM PWE3 to Emulate Services (MPLS)

The MA5600T/MA5603T/MA5608T supports the SAToP encapsulation for non-frame E1
signals and implements the TDM PWE3 emulation service after MPLS-encapsulating the
signals. In this way, the MA5600T/MA5603T/MA5608T provides emulated TDM private line
service over the MPLS network.
l
To make full use of legacy TDM line and equipment, and replace legacy DDN network
and ISDN PRI PBX convergence network.
To perform MPLS over IP encapsulation on the E1 data aggregated by the Nx64k private
line and ISDN PRI PBX, and transmit the data upstream as MPLS packets to the DDN
network or SDH network.
The H802EDTB board and SPUB board are installed and work in the normal state.
The working mode of the H802EDTB board is set to SAToP by running the board
workmode command.
A static route or dynamic route is successfully configured on each device over the
network so that the IP routes between LSRs are reachable.
Prerequisite
Context
The implementation process of TDM PWE3 is as follows:
1.
The data of the Nx64k private line service or ISDN PRI PBX service is converged and
then transmitted to the H802EDTB board of the MA5600T/MA5603T/MA5608T.
2.
After performing SAToP processing (adding CW control word and RTP header) on the
E1 data, the H802EDTB board sends the data to the SPUB board through the control
board.
Issue 01 (2016-04-29)

398

Access Module
3.
After performing the PW and MPLS encapsulation on the packets, the SPUB board adds
the ETH header to the packets, and then sends them to the control board.
4.
The control board performs Layer 2 forwarding and sends the packets to the upstream
port.
5.
The packets are sent over the PSN network to the peer PWE3 gateway (such as the
PTN).
6.
The PWE3 gateway restores the E1 signals from the packets and then sends them to the
DDN network or SDH network.
Networking
Figure 4-7 shows an example network of TDM PWE3 (MPLS-based).
Figure 4-7 Example network of TDM PWE3 (MPLS-based)
SHDSL Modem
Access
SHDSL Node
PWE3
Gateway
MPLS
Network
PRI PBX
E1
E1
SDH
E1
TDM PWE3
Data Plan
Table 4-8 lists the data plan for configuring TDM PWE3 (MPLS-based).
Table 4-8 Data plan for configuring TDM PWE3 (MPLS-based)
Parameter
Data
H802EDTB board
Board slot: 0/4

E1 port: 0/4/5
SPUB board
Board slot: 0/5
MPLS
VLAN for MPLS forwarding: 4001

IP address of VLAN interface 4001: 10.50.50.50/24
MPLS LSR ID: 3.3.3.3
Global MPLS LDP: enabled
MPLS LDP for VLANIF 4001: enabled
Issue 01 (2016-04-29)

399

Access Module
Parameter
Data
PW parameters
PW ID: 3

PW type: TDM SAToP E1
PW load time: 125 s
Jitter buffer size: 2500 s
RTP: enabled
VCCV: enabled
Tx clock of the E1 port
Network clock, recovered from PW 3
Procedure
Step 1 Configure a loopback interface.
Step 2 Enable basic MPLS functions.

Set the IP address of loopback interface 0 as the LSR ID.
Enable global MPLS.

huawei(config)#mpls
through the host address
//set up an LSP by triggering the LDP
Enable Layer 2 VPN.

Enable global LDP.

NOTE
l Only one session can exist between two LSRs and a local LDP session takes priority over a remote LDP
session. To simplify the configuration, assume that the MA5600T/MA5603T/MA5608T is directly
connected to the PTN. Hence, you need to enable only the LDP function (the local LDP session is
automatically set up after the LDP function is enabled).
l If the MA5600T/MA5603T/MA5608T is not directly connected to the PTN, after the LDP function is
enabled, run the mpls ldp remote-peer command to create an LDP remote peer and then enter the remote
peer mode. Then, run the remote-ipip-addr command to specify the ID of the remote LSR.
l For detailed configurations, see Configuring the LDP LSP.
Step 3 Configure a VLAN and enable MPLS for the VLAN and the VLAN interface.
Add VLAN 4001 for forwarding MPLS packets and add an upstream port to it.
Issue 01 (2016-04-29)

400

Access Module


Set the IP address of VLAN interface 4001 to 10.50.50.50/24 and enable MPLS LDP for the
VLAN interface.

PWE3 has no special requirements for the routing policy. A static route, or dynamic RIP, or
OSPF route can be configured. An OSPF dynamic route is recommended because OSPF
supports MPLS RSVP-TE extension.
interfaces.
Step 5 Configure PW parameters.

1.
Create PW 3 and enter the PW parameter mode.

2.
Configure the loopback interface IP address of the remote PTN device in the PW.
Set the loopback interface IP address to 10.10.10.10.
3.
Set the PW type to TDM SAToP E1.

4.
Configure the PW load time.

Set the load time to 125 s.
5.
(Optional) Enable RTP. After RTP is enabled, PW packets of the TDM type contain the
RTP control header. By default, RTP is disabled.
NOTE
The RTP configuration must be the same as that on the PTN.

huawei(config-pw-para-3)#rtp-header
6.
(Optional) Configure the jitter buffer size. The jitter buffer can effectively prevent jitter
and delay. Only PW parameters of the TDM type support the jitter buffer configuration.
By default, the jitter buffer size is 2000 s.
NOTE
The value range of the jitter buffer is 500-32000 and the value must be an integer multiple of 125. You
can configure this value according to actual conditions. In this example, the jitter buffer size is set to
2500 s.
Issue 01 (2016-04-29)

401

Access Module
7.
Configure the PW parameter to support the control word.

8.
Enable virtual circuit connectivity verification (VCCV).

Step 6 Create a TDM connection.

Set TDM connection ID to 2, type to PWE3, and ID of the E1 port of the H802EDTB board
to 0/4/5.
Step 7 Bind the TDM connection to the PW to create the PW service of the TDM type.
Bind TDM connection 2 to PW 3.
Step 8 Confirm that the PW is in the normal state.

On the OLT, run the display pw or display pw-ac-binding command to query the PW status.
Confirm that the PW state is normal (up).
huawei(config)#display pw-ac-binding tdm 2
1/0
Static/LDP :
0/1)
---------------------------------------------------------------------------TDM
PW
PW
PROTO RECEIVE TRNS
PW
ID
ID
STATE TYPE
LABEL
LABEL
INDEX
---------------------------------------------------------------------------2
3
up
LDP
----3
*: Secondary
Step 9 Configure clock synchronization on the E1 port.

Configure the recovery clock source of the H802EDTB board. In the recovery clock mode,
the receive end recovers the clock of the transmit end according to the average arrival rate of
the received SAToP packets. In this example, clock signals are extracted from PW 3 to serve
as the recovery clock of a board.
huawei(config-edt-0/4)#adapt-clock-source clock-source 0 3
Configure the Tx clock of E1 port 0/4/5 on the H802EDTB board as the network-side clock.
That is, configure the clock recovered from a TDM PW as the Tx clock of a port,
implementing voice service synchronization.
huawei(config-edt-0/4)#clock-work 5 net
----End
Result
After a network is restructured, the long-term bit error ratio and latency meet the requirements
for actual applications, the Nx64k private line service or ISDN PRI PBX service runs
normally, and the operation method for end users is not changed.
Configuration File
quit
mpls lsr-id 3.3.3.3
mpls
Issue 01 (2016-04-29)

402

Access Module
lsp-trigger host
quit
mpls l2vpn
mpls ldp
quit
vlan 4001 smart
port vlan 4001 0/19/0
mpls vlan 4001
ip address 10.50.50.50 24
mpls
mpls ldp
quit
ospf 1
area 100
network 10.50.50.0 0.0.0.255
network 3.3.3.3 0.0.0.0
return
pw-para 3
pw-type tdm satop e1
tdm-load-time satop e1 loadtime 125
rtp-header
jitter-buffer buffer-size 2500
control-word
tnl-policy ip_policy
quit
tdm-connect connectid 1 tdm pwe3-uplink 0/4 e1 0/4/5
pw-ac-binding tdm 2 pw 3
interface edt 0/4
adapt-clock-source clock-source 0 3
clock-work 5 net
4.4 Example of the TDM SHDSL Service for Narrowband

Data
The TDM SHDSL extends the access distance. With the TDM SHDSL, the MA5600T/
MA5603T/MA5608T transparently transmits user-side configuration data to the digital data
network (DDN). In this way, the twisted pair can be fully used and the E1 line deployment
expense decreases.
l
Use the existing rich twisted pair resources for long-distance transmission, extending the
DDN node.
The user-side configuration data is transparently transmitted on the MA5600T/

MA5603T/MA5608T.
The following figure shows an example network of TDM SHDSL for transparently
transmitting the narrowband data private line service.
Issue 01 (2016-04-29)

403

Access Module
Figure 4-8 Example network of TDM SHDSL for transparently transmitting the narrowband
data private line service
Router
V.35
E1
SHDSL Modem
V.35
Access
Node
Router
Data Plan
The following table lists the data plan for configuring TDM SHDSL for transparently
transmitting the narrowband data private line service.
Table 4-9 Data plan for configuring TDM SHDSL for transparently transmitting the
narrowband data private line service
Item
Data
EDTB board
If the entire board is used for transparently transmitting the

narrowband data private line service:
l Slot ID: 0/3
l Board working mode: voice
l Board working sub-mode: transparent mode
If a port is used for transparently transmitting the narrowband
data private line service:
l Port ID: 0/3/0
l Board working mode: voice
l Board working sub-mode: service
l Port working mode: transparent mode
Prerequisite
l
activated. For details, see Configuring an SHDSL Port.
Issue 01 (2016-04-29)

404

Access Module
Procedure
Step 1 (Optional) Configure the working mode of the board.
NOTE
Step 2 Configure the working sub-mode of the board according to service requirements.
l
If the entire board is used for transparently transmitting the narrowband data private line
service, configure the working sub-mode of the board to transparent.
huawei(config-edt-0/3)#runmode transparent
If a specified port is used for transparently transmitting the narrowband data private line
service, configure the working sub-mode of the board to service and the running mode
of the port to transparent.
huawei(config-edt-0/3)#e1port runmode 0 transparent
NOTE
l Before changing the service mode to transparent mode, make sure that no service is configured for the
board.
l In the transparent mode, the E1 ports and SHDSL ports are in one-to-one mapping, that is, ports 0-15 map
ports 16-31 one by one.

huawei(config)#save
----End
Result
The user can normally access the DDN network by using the MA5600T/MA5603T/
MA5608T.
Configuration File
If the entire board is used for transparently transmitting the narrowband data private line
service:
interface edt 0/3
runmode transparent
quit
save
If E1 port 0 is used for transparently transmitting the narrowband data private line service:
interface edt 0/3
runmode service
e1port runmode 0 transparent
quit
save
Issue 01 (2016-04-29)

405

Access Module
4.5 Example of the Private Line Service Leasing E1

Timeslots
Leasing an entire E1 line is expensive and also a waste of the bandwidth resources. The
private line service leasing E1 timeslots can meet the requirement leasing a part of an E1 line.
With this service, users are assigned specific timeslots of an E1 line, and therefore can share
the bandwidth of the E1 line, hence saving the E1 line lease expense.
Prerequisites
l
An SHDSL modem must be correctly connected and the SHDSL port must be activated.
Context
The E1 private line service is mainly used in point-to-point (P2P) data exchange industries
that do not require immediate data exchange, such as finance, government, and enterprise.
These data exchange services do not need high bandwidth but have rigorous requirements on
quality, such as error code, delay, and packet loss. Leasing an entire E1 line is expensive and
also a waste of the bandwidth resources. The private line service leasing E1 timeslots can
reduce costs and improve bandwidth usage, which provides rates ranging from 64 kbit/s to 2
Mbit/s.
In this case, pay attention to the signaling mode of the E1 port. The signaling mode is set to
be common channel signaling (CCS) in general, which must be the same as that set on the
peer device in the digital data network (DDN).
l
CCS: frame format, in this mode, timeslot 0 is used to send frame synchronization
information and the other 31 timeslots are used to send valid data.
l
Use the existing rich twisted pair resources for long-distance transmission, extending the
DDN node.
The carrier does not need to deploy the new E1 line, which saves the deployment cost.
The user leases only one or more timeslots of the E1 line to save the lease expense.
Networking
Figure 4-9 shows an example network of the private line service leasing E1 timeslots.
The user end is connected to an SHDSL modem through a data terminal equipment (DTE)
that supports V.35 port, and then connected to the EDTB board of the MA5600T/MA5603T/
MA5608T through the TDM SHDSL port provided by the modem. By establishing internal
SPCs between different timeslots of the E1 and SHDSL ports, the EDTB board multiplexes
timeslot channels of different lines to the same E1 upstream port, implementing convergence
of multiple Nx64 kbit/s channels to the E1 port and saving E1 resources.
Issue 01 (2016-04-29)

406

Access Module
Figure 4-9 Example network of the private line service leasing E1 timeslots
CCS
V35 DTE
Access
Node
SHDSL
8*64k TDM
V35 DTE
4*64k TDM
SHDSL Modem
E1
SHDSL
Data Plan
Table 4-10 uses two-channel TDM aggregation (8*64 kbit/s and 4*64 kbit/s) as an example to
describe the data plan in CCS mode.
Table 4-10 Data plan for configuring the private line service leasing E1 timeslots
Item
Data
EDTB board
Working mode: voice

Working sub-mode: service mode
Clock source: E1 line clock
E1 port
Upstream port ID: 0/3/0

Line coding mode: HDB3 (default)
Port impedance: 75 ohms (default)
Port signaling mode: CCS
Issue 01 (2016-04-29)

407

Access Module
Item
Data
SHDSL port
Port IDs: 0/3/16 and 0/3/17

Port signaling mode: unframe
Line profile ID of the port: 2
l Rate: 512 kbit/s
l Channel mode: TDM
l Data frame type: V35
l Clock mode: system clock
l Other parameters: default values
l Bound to port 0/3/16
Line profile ID of the port: 3.
l Rate: 256 kbit/s
l Channel mode: TDM
l Data frame type: V35
l Clock mode: system clock
l Other parameters: default values
l Bound to port 0/3/17
Internal SPC
Establish internal SPCs between B channels 0-7 of SHDSL

port 0/3/16 and timeslots 1-8 of E1 port 0/3/0.
Establish internal SPCs between B channels 0-3 of SHDSL
port 0/3/17 and timeslots 9-12 of E1 port 0/3/0.
NOTE
In CCS mode, timeslot 0 of the E1 port is used to send the frame
locating information but is not used to send data. Therefore, it cannot
be used for internal semi-permanent connection (SPC).
Procedure
Step 1 Configure the working mode and clock source of the EDTB board.
Configure the working mode of the board to voice, working sub-mode to service, and clock
source to E1 line clock.
NOTE
To configure the private line service leasing timeslots, the working mode of the board must be configured to
voice and the sub-mode must be configured to service.
huawei(config-edt-0/3)#set clockmode line 0

1.
Set the signaling mode of the SHDSL port to unframe.

huawei(config-edt-0/3)#shdslport signal 16 unframe
huawei(config-edt-0/3)#shdslport signal 17 unframe
Issue 01 (2016-04-29)

408

Access Module
2.
Configure the line profiles of the SHDSL port.

Set line profile IDs to 2 and 3 with rates 512 kbit/s and 256 kbit/s respectively. Set the
channel mode to TDM, data frame type to V35, and clock mode to system clock. Other
parameters use default values.
NOTE
It is recommended that you set the rates on line profiles to be the same as those set on the SHDSL
modem to ensure that modems are normally activated.
The following uses adding line profile 2 as an example:

huawei(config)#shdsl line-profile add 2
Start adding
profile
During inputting,press 'Q' to quit,then settings at this time will be
ignored
Do you want to name the profile (y/n)
[n]:n
> G.SHDSL data path mode(1--3 1--ATM;2--PTM;3--TDM)[1]:
3
> G.SHDSL interface mode of line (1--two wire;2--four wire;3--six wire;4-eight
wire)
[1]:
> Do you use the default data to create a line profile?(y/n)
[y]:n
> G.SHDSL minimum line
rate
(Value must be multiple of 64,except 2312kbps and
3848kbps,
192~5696,2312,3848 kbps)[2048]:
512
> G.SHDSL maximum line
rate
(Value must be multiple of 64,except 2312kbps and
3848kbps,
512~5696,2312,3848 kbps)[2048]:
512
> Power spectral density mode (1--symmetric;2--asymmetric)
[1]:
> Transmission mode (1--G.991.2 Annex A/F;2--G.991.2 Annex B/
G;
3--All)
[3]:
> Remote enable (1--enabled;2--disabled)
[1]:
> Probe enable (1--disabled;2--enabled)
[1]:
> Modulation mode(1--TCPAM16;2--TCPAM32;3--auto)
[3]:
> Performance statistic mode(1--auto;2--absolute;3--delta)
[1]:
> G.SHDSL data frame type(1--E1;2--V35)[1]:
2
> G.SHDSL data clock align(1--synchronization 2--asynchronism)
[1]:
> Clock mode(1--freeRun 2--system)[1]:
2
> Do you config the target SNR margin?(y/n)
[n]:n
Add profile 2 successfully
3.
Bind the line profile and activate the SHDSL port.

huawei(config-shl-0/3)#deactivate all
huawei(config-shl-0/3)#activate 16 2
huawei(config-shl-0/3)#activate 17 3
uawei(config-shl-0/3)#quit
Issue 01 (2016-04-29)

409

Access Module
Step 3 Configure the attributes of the upstream E1 port.

Set the signaling mode of the E1 port to CCS.
huawei(config-edt-0/3)#e1port signal 0 ccs
Step 4 Configure internal SPCs.

Create one-to-one mapping from eight B channelsof SHDSL port 0/3/16 to eight timeslots of
E1 port 0/3/0; create one-to-one mapping from four B channels of SHDSL port 0/3/17 to four
timeslots of E1 port 0/3/0. This implements the convergence of (8+4) x 64 kbit/s channels.
NOTE
In CCS mode, timeslot 0 of the E1 port is used to send the frame locating information but is not used to send
data. Therefore, it cannot be used for internal SPC.
huawei(config)#spc
huawei(config-spc)#anspc add start 0/3/16/0 end 0/3/0/1 apptype normal channelnum
8
huawei(config-spc)#anspc add start 0/3/17/0 end 0/3/0/9 apptype normal channelnum
4
Step 5 Query the status of the internal SPCs.

huawei(config-spc)#display anspc from-connectid 0
{ <cr>|to-connectid<K> }:
Command:
display anspc from-connectid 0
-----------------------------------------------------------------------------ConnectId
:0
Start F/S/P/Chn
:0 /3/16/0
End F/S/P/Chn
:0 /3/0 /1
BChannelNum
:8
State
:normal
Apptype
:normal
Description
:timeslot0-7_to_e1timeslot1-8
-----------------------------------------------------------------------------ConnectId
:1
Start F/S/P/Chn
:0 /3/17/0
End F/S/P/Chn
:0 /3/0 /9
BChannelNum
:4
State
:normal
Apptype
:normal
Description
:timeslot0-3_to_e1timeslot9-12
------------------------------------------------------------------------------
----End
Result
l
The above-mentioned users can normally access the DDN by using the leased E1
timeslots.
The P2P data services of users are normal and no error codes are generated in a longtime service test.
Configuration File
interface edt 0/3
runmode service
set clockmode line 0
shdslport signal 16 unframe
shdslport signal 17 unframe
quit
Issue 01 (2016-04-29)

410

Access Module
shdsl line-profile add 2

shdsl line-profile add 3
interface shl 0/3
deactive all
activate 16 2
activate 17 3
quit
interface edt 0/3
e1port signal 0 ccs
quit
spc
anspc add start 0/3/16/0 end 0/3/0/1 apptype normal channelnum 8
anspc add start 0/3/17/0 end 0/3/0/9 apptype normal channelnum 4
Issue 01 (2016-04-29)

411

Access Module
5 Configuration Example of the MSTP Subtending

Network
Configuration Example of the MSTP

Subtending Network
About This Chapter

This topic describes how to configure the integrated services on the MA5600T/MA5603T/
MA5608Ts in the MSTP ring network.
5.1 MSTP Networking
This topic describes the typical networking in the MSTP mode.
5.2 MSTP Dataplan
This topic provides the data plan for the example RSTPMSTP network.
5.3 Configuring MA5600T/MA5603T/MA5608T-1
This topic describes how to configure MA5600T/MA5603T/MA5608T-1.
5.8 Verification
All services configured on all DSLAMs run in the normal state.
Issue 01 (2016-04-29)

412

Access Module

Network
5.1 MSTP Networking

This topic describes the typical networking in the MSTP mode.
Three MA5600T/MA5603T/MA5608Ts (MA5600T/MA5603T/MA5608T-1, MA5600T/
MA5603T/MA5608T-2, and MA5600T/MA5603T/MA5608T-3) form an MSTP ring
network.
l
MA5600T/MA5603T/MA5608T-1 is connected to the IP network.
MA5600T/MA5603T/MA5608T-2 is connected to the home gateway at the user end

through the xDSL service board, providing the Internet, voice, and IPTV services
concurrently.
MA5600T/MA5603T/MA5608T-3, through whose GE port, is subtended with

MA5600T/MA5603T/MA5608T-4.
MA5600T/MA5603T/MA5608T-1 works with MA5600T/MA5603T/MA5608T-5 to

provide the QinQ service through the IP network.
Figure 5-1 shows an example MSTP network of the MA5600T/MA5603T/MA5608T.
Issue 01 (2016-04-29)

413

Access Module

Network
Figure 5-1 Example MSTP network of the MA5600T/MA5603T/MA5608T
5.2 MSTP Dataplan

This topic provides the data plan for the example RSTPMSTP network.
Table 5-1 provides the service and the data plan for the example network of the MA5600T/
MA5603T/MA5608T.
Issue 01 (2016-04-29)

414

Access Module

Network
Table 5-1 Data plan for the example RSTPMSTP network

Item
MA5600T/
MA5603T/
MA5608T-1
MA5600T/
MA5603T/
MA5608T-2
MA5600T/
MA5603T/
MA5608T3
MA5600T/
MA5603T/
MA5608T-4
MA5600T/
MA5603T/
MA5608T-5
Service
l ADSL2+
service
l ADSL2+
service
l ADSL2+
service
l ADSL2+
service
l VDSL2
service
l SHDSL
service
l SHDSL
service
l SHDSL
service
l SHDSL
service
l GPON
service
l POTS
service
l GPON
service
l POTS
service
l POTS
service
l Stacking
wholesale
service
l QinQ
private
line
service
(interoper
ate with
MA5600
T/
MA5603
T/
MA5608
T-1)
l QinQ
private
line
service
(interopera
te with
MA5600T
/
MA5603T
/
MA5608T
-5)
l GPON
service
l Multicast
service
l Triple play
service
(multiple
PVCs for
multiple
services)
l Multicast
service
l Multicast
service
Inband
NMS
address
GE port
of the
GIU
board
Issue 01 (2016-04-29)
10.10.1.2
10.10.1.3
10.10.1.4
10.10.1.5
10.10.1.6
255.255.255.0
255.255.255.0
Gateway:
Gateway:
255.255.255
.0
255.255.255.
0
255.255.255.
0
10.10.1.1/24
10.10.1.1/24
Gateway:
Gateway:
Gateway:
10.10.1.1/24
10.10.1.1/24
10.10.1.1/24
Upstream:
0/19/0-0/19/
1
Upstream:
0/19/0
Upstream:
0/19/0
Upstream:
0/20/0
RSTP:
0/19/0-0/19/1
Upstream:
0/19/0-0/19/1
RSTP:
0/20/0

415

Access Module

Network
Item
MA5600T/
MA5603T/
MA5608T-1
MA5600T/
MA5603T/
MA5608T-2
MA5600T/
MA5603T/
MA5608T3
MA5600T/
MA5603T/
MA5608T-4
MA5600T/
MA5603T/
MA5608T-5
VLAN
NMS: 10
NMS: 10
NMS: 10
NMS: 10
NMS: 10
QinQ: 50
Multicast: 100
Stacking: 60-62
(inner stacking:
111-113)
Multicast:
100
QinQ: 50
Multicast:
100
ADSL2+:
2030 (uses
the PPPoE
authenticati
on)
ADSL2+:
1000-1031
(uses the
VLAN
authentication
)
SHDSL:
1300-1315
(uses the
VLAN
authentication
)
GPON: 1510
(the ONT
uses the SN +
password
authentication
)
Triple play:
100-102
ADSL2+: 2020
(uses the PPPoE
authentication)
SHDSL: 3020
(uses the PPPoE
authentication)
POTS: 1600
(uses the H.248
protocol)
SHDSL:
3030 (uses
the PPPoE
authenticati
on)
GPON:
1530 (the
ONT uses
the SN +
password
authenticati
on)
VDSL2:
1800 (uses
the PPPoE
authenticatio
n)
SHDSL:
3040 (uses
the PPPoE
authenticatio
n)
GPON: 1540
(the ONT
uses the SN
+ password
authenticatio
n)
POTS: 1600
(uses the H.
248
protocol)
POTS: 1600
(uses the H.
248 protocol)
Slot
ADSL2+:
2040 (uses
the PPPoE
authenticatio
n)
ADSL2+: 0/2
ADSL2+: 0/2
ADSL2+:
0/2
SHDSL: 0/5
SHDSL: 0/5
ADSL2+:
0/2
SHDSL: 0/5
POTS: 0/3
SHDSL: 0/5
SHDSL: 0/5
QinQ: 0/5/15
POTS: 0/3
Stacking:
GPON: 0/18
GPON: 0/18
QinQ: 0/5/31
0/2/0-10 (maps
VLAN 60,
ISP1)
GPON: 0/18
Multicast:
0/2/2, 0/2/3
VDSL: 0/2
POTS: 0/3
Multicast:
0/2/2, 0/2/3
0/2/11-20 (maps
VLAN 61,
ISP2)
0/2/21-30 (maps
VLAN 62,
ISP3)
Triple Play:
0/2/31
Issue 01 (2016-04-29)

416

Access Module

Network
Item
MA5600T/
MA5603T/
MA5608T-1
MA5600T/
MA5603T/
MA5608T-2
MA5600T/
MA5603T/
MA5608T3
MA5600T/
MA5603T/
MA5608T-4
MA5600T/
MA5603T/
MA5608T-5
User
PVC
PVC
VPI/VCI of
all users: 0/35
VPI/VCI of the
triple play:
PVC
VPI/VCI of
all users:
0/35
PVC
VPI/VCI of
all users:
0/35
PVC
VPI/VCI of
all users:
0/35
l Video
service: 0/35
l Internet
service: 0/36
l Voice
service: 0/37
POTS
service
MGC IP address: 10.30.80.65/24

Media/Signaling IP address of the MG interface: 10.176.6.33/24
Default media gateway of the MG interface: 10.176.6.62/24
IP address of the VLAN: 10.176.6.33/24
MG interface attributes: index is 0, supported protocol is H.248, coding type is
text, signaling port number is 2944, port number of the active MGC is 2944, and
transmission mode is UDP.
NMS
host
2.2.2.2 and 2.2.2.3
Log
host
3.3.3.3 and 3.3.4.3
Time
server
4.4.4.4 and 4.4.4.5
Multica
st server
10.10.10.10
EMU
AC PS4845 power monitoring, fan monitoring
DHCP
server
DHCP server1: 10.1.1.2 (active) 10.1.1.3 (standby)

Gateway: 10.1.1.1/24
DHCP server2: 10.4.4.2 (active) 10.4.4.3 (standby)
Gateway: 10.4.4.1/24
Upperlayer
device
The upper-layer device supports the DHCP option82 function.

The BRAS supports the PITP, stacking VLAN and QinQ VLAN function.
The BRAS supports inner and outer VLAN tags.
The VLAN ID of the traffic flow sent from the IP network to the DSLAM is
100.
The upper layer device classifies the downstream traffic. Different service
carries different 802.1p labels.
The VLAN mapping to the DSLAM is configured in the upper-layer IP network.
Issue 01 (2016-04-29)

417

Access Module

Network
NOTE
l In this networking, MA5600T/MA5603T/MA5608T-1 can be replaced with a GE switch or a BRAS.

l The upstream port of MA5600T/MA5603T/MA5608T supports the port aggregation function. In the
actual network planning, you can aggregate multiple ports for use.
l In this networking, the five MA5600T/MA5603T/MA5608Ts support the ADSL2+, SHDSL,
VDSL2, GPON, and POTS services. You can plan the services according to your actual network
conditions.

Procedure
Step 1 Confirm the board.
huawei>enable
huawei#config
huawei(config)#board confirm 0
Step 2 Configure the NMS.

1.
Configure the IP address of the inband NMS interface.
Create the NMS VLAN.

Add the upstream port.

huawei(config)#port vlan 10 0/19 0-2
Enter the NMS VLAN interface mode.

Configure the IP address of the NMS VLAN interface.

2.
Add the route.
Configure the route destined to the NMS (trap destination host).

preference 1
Configure the route destined to the time server.

preference 1
Configure the route destined to the log host.

preference 1
preference 1
3.
Add the ACL rule.

huawei(config-acl-adv-3050)#rule
0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
Issue 01 (2016-04-29)
permit ip source any destination any

deny ip source any destination 10.10.1.2
permit ip source 2.2.2.2 0.0.0.0

418

Access Module

Network
huawei(config-acl-adv-3050)#rule permit ip source 3.3.3.3 0.0.0.0

destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
huawei(config)#packet-filter inbound ip-group 3050 port 0/19/1
4.
Configure the SNMP parameters.

huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
Configure the contact information.

Configure the device location information.

huawei(config)#snmp-agent sys-info location Shenzhen China
Configure the SNMP version.

The SNMP version must be the same as the SNMP version of the NMS. In this
example, the NMS version is set as SNMP v2c.
5.
Enable the trap sending.

6.
Set the trap destination address.

trap-paramsname abc
huawei(config)#snmp-agent target-host trap-hostname huawei123 address 2.2.2.3
trap-paramsname 123
7.
Set the trap source address.

Step 3 Configure the time server.

huawei(config)#ntp-service unicast-server 4.4.4.4 source-interface vlanif 10
Step 4 Configure the log host.

huawei(config)#loghost
add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3
Step 5 Configure the EMU.

This topic uses the fan and PS4875L power supply as an example to describe how to
configure the environment monitoring unit (EMU).
By default, the default slave node number of the fan EMU is 0. In this example, suppose the
slave node number is 1. In this case, you need to set the DIP switch of the slave node number
on the fan monitoring unit as 1.
huawei(config)#emu add 0 power4875l 0 0
huawei(config)#emu add 1 fan 0 1
huawei(config-if-power4875l-0)#power module-num 2 1 2
Step 6 Configure GIU subtending

MA5600T/MA5603T/MA5608T-1 is subtended with MA5600T/MA5603T/MA5608T-2,
MA5600T/MA5603T/MA5608T-3 and MA5600T/MA5603T/MA5608T-4. Therefore,
subtending should be configured.
Issue 01 (2016-04-29)

419

Access Module
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#port

Network
60 to 62 standard
vlan 60 to 62 0/19 0-2
101 to 102 standard
vlan 101 to 102 0/19 0-2
Step 7 Configure MSTP.

1.
Enable the MSTP function.

huawei(config)#stp enable
Change global stp state may active region configuration,it may take
several
minutes,are you sure to change global stp state? [Y/N]
[N]Y
2.
Set the MST region name.

huawei(config)#stp region-configuration
huawei(stp-region-configuration)#region-name hwrg
3.
Configure MSTP instance 1.

huawei(stp-region-configuration)#instance 1 vlan 1 to 4094
4.
Activate the configuration of the MST region.

huawei(stp-region-configuration)#active region-configuration
STP actives region configuration, it may take several minutes,are you sure
to
active region configuration? [Y/N][N]y
5.
Set the priority of MA5600T/MA5603T/MA5608T_1 in the instance.

huawei(stp-region-configuration)#quit
huawei(config)#stp instance 0 priority 0
huawei(config)#stp instance 1 priority 0
Step 8 Configure ADSL2+ service.

The MA5600T/MA5603T/MA5608T supports the ADSL2+ service of multiple encapsulation
modes, such as IPoA, PPPoA, IPoE, and PPPoE. This topic uses the PPPoE mode as an
example to describe how to configure the ADSL2+ service. For other encapsulation modes,
see "3.1 Example of the xDSL Internet Access Service."
1.
Configure the ADSL2+ line profile.

You can configure the ADSL2+ line profile based on your requirements.
huawei(config)#adsl line-profile add 10
Start adding
profile
Press 'Q' to quit the current configuration and new configuration will
be
neglected
> Do you want to name the profile (y/n)
[n]:
>
Transmission
mode:
>
0:
Custom
>
1: All (G.
992.1~5,T1.413,ETSI)
>
2: Full rate(G.
992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G.
992.1/3/5)
>
4: G.HS (G.
992.1~5)
>
5: ADSL (G.
992.1~2,ETSI,T1.413)
>
6: ADSL2 & ADSL2+ (G.
992.3~5)
>
Please select (0~6)
Issue 01 (2016-04-29)

420

Access Module

Network
[1]:
> Trellis mode 1-disable 2-enable (1~2)
[2]:
> Bit swap downstream 1-disable 2-enable (1~2)
[2]:
> Bit swap upstream 1-disable 2-enable (1~2)
[2]:
> Please select the form of transmit rate adaptation
downstream:
> 1-fixed, 2-adaptAtStartup, 3-adaptAtRuntime (1~3)
[2]:
upstream:
[2]:
> Will you set SNR margin parameters? (y/n)
[n]:
> Will you set DPBO parameters? (y/n)
[n]:
> Will you set power management parameters? (y/n)
[n]:
> Will you set tone blackout configuration parameter? (y/n)
[n]:
> Will you set INM downstream parameter? (y/n)
[n]:
> Will you set RFI notch configuration parameter? (y/n)
[n]:
> Will you set mode-specific parameters? (y/n)
[n]:
> Will you set network timing reference? (y/n) [n]:
2.
Configure the ADSL2+ channel profile.

You can configure the ADSL2+ channel profile based on your requirements.
huawei(config)#adsl channel-profile add 10
Start adding
profile
be
neglected
[n]:n
> Data path mode 1-ATM, 2-PTM, 3-Both (1~3) [3]:
1
> Will you set the minimum impulse noise protection? (y/n)
[n]:y
>
Minimum impulse noise protection
downstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
tenSymbols
>
13-elevenSymbols 14-twelveSymbols 15-thirteenSymbols
fourteenSymbols
>
17-fifteenSymbols 18sixteenSymbols
>
Please select (1~18) [2]:
4
>
upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
tenSymbols
Issue 01 (2016-04-29)

481216-
4812-
421

Access Module

Network
>
13-elevenSymbols 14-twelveSymbols 15-thirteenSymbols 16fourteenSymbols
>
>
4
> Will you set interleaving delay parameters? (y/n)
[n]:y
>
Maximum interleaving delay downstream (0~63 ms) [16]:
24
>
Maximum interleaving delay upstream (0~63 ms) [6]:
12
> Will you set parameters for rate? (y/n)
[n]:y
>
Minimum transmit rate downstream (32~32000 Kbps)
[32]:
>
Minimum reserved transmit rate downstream (32~32000 Kbps)
[32]:
>
Maximum transmit rate downstream (32~32000 Kbps) [24544]:
8000
>
Minimum transmit rate upstream (32~6000 Kbps)
[32]:
>
Minimum reserved transmit rate upstream (32~6000 Kbps)
[32]:
>
Maximum transmit rate upstream (32~6000 Kbps)
[1024]:
> Will you set rate thresholds? (y/n)
[n]:
> Will you set retransmission function (y/n)
[n]:
> Will you set erasure decoding? (y/n) [n]:
3.
Configure the ADSL2+ line template.

Bind the preceding configured line profile and the channel profile together in the line
template with the index of 10.
huawei(config)#adsl line-template add
10
Start adding
template
be
neglected
> Do you want to name the template (y/n)
[n]:
> Please set the line-profile index (1~128) [1]:
10
> Will you set channel configuration parameters? (y/n)
[n]:y
>
Please set the channel number (1~2) [1]:
1
>
Channel1 configuration
parameters:
>
Please set the channel-profile index (1~128) [1]:
10
Add template 10
successfully
4.
Configure the ADSL2+ alarm profile.

You can configure the ADSL2+ alarm profile based on your requirements. For detailed
configuration, see "Configuring an ADSL2+ Alarm Template." This example adopts the
default alarm profile 1 in the system.
5.
Configure the ADSL2+ traffic profile.

You can configure the ADSL2+ traffic profile by running the traffic table ip command
based on your requirements.
Issue 01 (2016-04-29)

422

Access Module

Network
In this example, the default profile (profile 6) is used.

6.
Activate the ADSL2+ port.

huawei(config-if-adsl-0/2)#deactivate all
huawei(config-if-adsl-0/2)#alarm-config all 1
huawei(config-if-adsl-0/2)#activate all template-index 1
7.
Configure the upstream port.
Configure the GIU board.

The configuration of the upstream port of the GIU board should be the same as
that of the peer device.
Run the auto-neg command to set the port to work in the auto-negotiation mode.
If the port does not work in the auto-negotiation mode, change to the GIU config
mode and run the speed command to change the port rate, and run the duplex
command to change the port duplex mode.
Configure the VLAN.

The ADSL2+ users of MA5600T/MA5603T/MA5608T-1 use the VLAN
authentication. In this case, the MUX VLAN is used to identify the users.
huawei(config)#vlan 1000 to 1031 mux
huawei(config)#port vlan 1000 to 1031 0/19 0-2
8.
Add the service port.

All ports in slot 0/3 provide the ADSL2+ service. To add service ports in batches, run the
multi-service-port command.
huawei(config)#multi-service-port from-vlan 1000 port 0/2 0-31 vpi 0 vci 35
rx-cttr 6 tx-cttr 6
Step 9 Configure the SHDSL service.

The MA5600T/MA5603T/MA5608T supports the SHDSL service of multiple encapsulation
modes, such as IPoA, PPPoA, IPoE, and PPPoE. This topic takes the PPPoE mode as an
example to describe how to configure the SHDSL service. For other encapsulation modes, see
"3.1 Example of the xDSL Internet Access Service."
1.
Configure the SHDSL line profile.

To configure the SHDSL line profile, run the shdsl line-profile add or shdsl line-profile
quickadd command.
huawei(config)#shdsl line-profile quickadd 10 line two-wire rate 2048 2048
psd
symmetric transmission Annex-A remote disable probe disable snr-margin dscurr 10 ds-worst
10 us-curr 10 us-worst 10 bitmap 0x03
2.
Configure the SHDSL alarm profile.

To configure the SHDSL alarm profile, run the shdsl alarm-profile add command.
3.
Activate the SHDSL port.

huawei(config-if-shl-0/5)#deactivate all
huawei(config-if-shl-0/5)#alarm-config all 1
huawei(config-if-shl-0/5)#activate all 10
Issue 01 (2016-04-29)

423

Access Module
4.

Network

The SHDSL users of MA5600T/MA5603T/MA5608T-1 adopt the VLAN
authentication. In this case, the MUX VLAN is used to identify the users.
5.

Ports 0-14 in slot 0/5 provide the SHDSL service. To activate the ports in batches, run
the multi-service-port command.
rx-cttr 6 tx-cttr 6
Step 10 Configure the GPON service.

1.
Configure the service VLAN and the upstream port.

2.
Configure the DBA profile.

3.
4.
Configure the alarm threshold profile.
When you need to configure the alarm threshold value to monitor the performance
statistics of the activated ONT line, run the gpon alarm-profile add command to
configure the GPON alarm threshold profile.
In the default GPON alarm threshold profile 1, all alarm thresholds are set to 0,
which indicates that no alarm is reported.
In this example, the default alarm threshold profile is used. You do not need to
configure it.
Configure the GPON traffic profile.

tag-In-Package
5.
Add an ONT.
NOTE
You can add an ONT in two ways: run the ont add command to add an ONT offline or run the ont
confirm command to confirm an ONT that is in the auto-find state.
You need to run the port ont-auto-find command in the GPON mode to enable the auto-find
function of the ONT.

huawei(config-if-gpon-0/18)#ont add 1 sn-auth hwhw-10101010 profile-id 2
NOTE
In this example, the ONT uses the default capability set profile 2. You can run the ont-profile add
command to configure the capability set profile of the ONT based on your requirements.
6.
Bind the alarm threshold profile.

huawei(config-if-gpon-0/18)#ont alarm-profile 1 0 profile-id 1
7.
Bind the DBA profile.

huawei(config-if-gpon-0/18)#tcont bind-profile 1 0 1 profile-id 10
8.
Divide the ONT port VLAN.

huawei(config-if-gpon-0/18)#ont port vlan 1 0 eth 10 0
huawei(config-if-gpon-0/18)#ont port native-vlan 1 0 eth 1 vlan 1510
9.
Configure the GEM port.

huawei(config-if-gpon-0/18)#gemport add 1 gemportid 150 eth
Issue 01 (2016-04-29)

424

Access Module

Network
10. Bind the GEM port to an ONT T-CONT.

NOTE
In the actual application, if the ONT terminal does not support the priority queue scheduling, you can
use the CAR to limit the rate when binding the GEM port to the ONT T-CONT.
huawei(config-if-gpon-0/18)#ont gemport bind 1 0 150 1 priority-queue 3
11. Create the mapping between the GEM port and the service stream.
huawei(config-if-gpon-0/18)#ont gemport mapping 1 0 150 vlan 1510
12. Add the service port.

huawei(config)#service-port vlan 1510 gpon 0/18/0 gemport 150 multi-service
Step 11 Configure the POTS service.

1.
Configure the upstream ports of the media stream and the signaling flow.
2.
Configure the static route destined to the MGC.

NOTE
When the MGC and the MG are in the same network segment, you do not need to configure the
static route.
3.
Configure the media IP address pool and the signaling IP address pool.
huawei(config)#voip
4.
Configure the MG interface.

Are you sure to add MG interface? (y/n)[n]:y
Configure the MG interface attributes.

huawei(config-if-h248-0)#if-h248 attribute mgip 10.176.6.33 mgport 2944 code
text
transfer udp primary-mgc-ip1 10.30.80.65 primary-mgc-port 2944 mg-media-ip1
10.176.6.33
Configure the software parameters of the MG interface (in this example, only parameter
20 is configured, and other parameters use the default values).
huawei(config-if-h248-0)#mg-software parameter 20 2
5.

NOTE
After configuring the MG interface, you need to reset the interface to validate the configuration.
6.
Configure the data of PSTN user.

huawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/31 0 terminalid 0 telno
88660000
Issue 01 (2016-04-29)

425

Access Module

Network
Step 12 Configure the QinQ private line service.

MA5600T/MA5603T/MA5608T-1 and MA5600T/MA5603T/MA5608T-5 serve two
branches of a company to provide the QinQ private line service.
1.
Create VLAN 50.

huawei(config)#vlan 50 mux
2.
Set VLAN 50 as QinQ VLAN.

3.

4.

To add the service port, run the service-port command. Note that the VPI and VCI
values set during the execution of the service-port command must be the same as those
on the modem.
The QinQ VLAN supports the PVC-priority scheduling policy only. In this case, select
the profile that supports PVC-priority policy.
huawei(config)#traffic table ip index 7 cir off priority 0 priority-policy
local-Setting
huawei(config)#service-port vlan 50 shdsl mode atm 0/5/15 vpi 0 vci 36 rxcttr 7 tx-cttr 7
Step 13 Configure the multicast service.

After the configuration, the following results should be achieved:
l
Users of port 0/2/2 must be authenticated, and have rights to watch two programs and to
preview one program.
Users of port 0/2/3 do not need authenticating.
1.
Configure the xDSL.

In this example, it is unnecessary to configure the xDSL. The default line profile (profile
1002) is used.
2.
Configure the VLAN.
Create a VLAN.
Add the upstream port to the VLAN.

Configure the native VLAN.

huawei(config-if-giu-0/19)#native-vlan 0 vlan 100
huawei(config-if-giu-0/19)#native-vlan 2 vlan 100huawei(config-ifgiu-0/19)#quit
Create the traffic profile.

Add ADSL2+ port 2 and 3 to VLAN 100.

huawei(config)#service-port 100 vlan 100 adsl 0/2/2 vpi 0 vci 35 rx-cttr
8
tx-cttr 8
huawei(config)#service-port 101 vlan 100 adsl 0/2/3 vpi 0 vci 35 rx-cttr
8
tx-cttr 8
3.
Issue 01 (2016-04-29)
Configure the multicast service.

426

Access Module

Network
Enable the multicast proxy.


huawei(config-mvlan100)#igmp default uplink-port 0/20/0
huawei(config)#btv
huawei(config-btv)#igmp uplink-port-mode mstp
Configure the preview parameters.

In this example, set the preview authority profile 1 with the preview duration for
the program to 150s, the number of preview attempts to 6 each day, and the
preview interval to 60s.
huawei(config-btv)#igmp preview-profile add index 1 duration 150 times 6
interval 60
huawei(config-btv)#igmp preview auto-reset-time 00:00:00
Configure the program library.

huawei(config-mvlan100)#igmp program
sourceip 10.10.10.10
sourceip 10.10.10.10 preview-profile
add name program1 ip 224.1.1.1

1
Configure the authority profile.

huawei(config)#btv
huawei(config-btv)#igmp profile profile-name profile0 program-name
program1 watch
program2 watch
program3 preview
Configure the multicast user.

huawei(config-btv)#igmp user add port 0/2/3 adsl 0 35 no-auth
huawei(config-btv)#igmp user add port 0/2/2 adsl 0 35 auth
huawei(config-btv)#igmp user bind-profile port 0/2/2 profile-name
profile0
Step 14 Configure the subtending multicast service.

In the MSTP ring network, MA5600T/MA5603T/MA5608T-1 is subtended with MA5600T/
MA5603T/MA5608T-3, and MA5600T/MA5603T/MA5608T-3 is subtended with
MA5600T/MA5603T/MA5608T-4. According to the data plan, MA5600T/MA5603T/
MA5608T-4 provides the multicast service. In this way, it is necessary to configure the
multicast subtending on MA5600T/MA5603T/MA5608T-1 first.
1.

The upstream port is already added in Step 13.3. It is unnecessary to configure it again.
2.
Issue 01 (2016-04-29)
Configure the IGMP proxy.

427

Access Module

Network
The IGMP proxy is already configured in Step 13.3. It is unnecessary to configure it

again.
3.

The program library is already configured in Step 13.3. It is unnecessary to configure it
again.
4.
Configure the multicast for the subtending port.
Specify a subtending port.

huawei(config)#btv
huawei(config-btv)#igmp cascade-port 0/19/0
Modify the subtending port.

huawei(config-btv)#igmp cascade-port modify 0/19/0 static enable

huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.


Enter NMS VLAN interface mode.


2.
Add the route.
Configure the route destined to the NMS (Trap destination host).

preference 1

preference 1

preference 1
Issue 01 (2016-04-29)

428

Access Module

Network

preference 1
3.
Add the ACL rule.

huawei(config-acl-adv-3050)#rule permit ip source any destination any
huawei(config-acl-adv-3050)#rule deny ip source any destination 10.10.1.2
0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.
Configure the community name and access authority.


Configure the device local information.


NOTE
The SNMP version must be the same as that of NMS. In this example, the NMS version is set as
SNMP V2C.
5.
Enable trap sending.

6.

trap-paramsname abc
trap-paramsname 123
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

This topic uses the fan and the PS4875L power supply as an example to describe how to
configure the EMU.
Issue 01 (2016-04-29)

429

Access Module

Network
By default, the default slave node number of the fan EMU is 0. In this example, assume that
the slave node number is 1. In this case, you need to set the DIP switch of the node address on
the fan monitoring unit to 1.
Step 6 Configure GIU subtending.

MA5600T/MA5603T/MA5608T-3 and MA5600T/MA5603T/MA5608T-4. Therefore, the
Step 7 Configure MSTP.
1.

several
[N]Y
2.

3.

4.

to
Step 8 Enable PITP.

Step 9 Configure ADSL2+ service.

1.

Start adding
profile
be
neglected
[n]:
>
Transmission
mode:
>
0:
Custom
>
1: All (G.
992.1~5,T1.413,ETSI)
Issue 01 (2016-04-29)

430

Access Module

Network
>
2: Full rate(G.
992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G.
992.1/3/5)
>
4: G.HS (G.
992.1~5)
>
5: ADSL (G.
992.1~2,ETSI,T1.413)
>
992.3~5)
>
Please select (0~6)
[1]:
[2]:
[2]:
[2]:
downstream:
[2]:
upstream:
[2]:
[n]:
[n]:
[n]:
[n]:
[n]:
[n]:
[n]:
2.

Start adding
profile
be
neglected
[n]:n
1
[n]:y
>
downstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
tenSymbols
>
13-elevenSymbols 14-twelveSymbols 15-thirteenSymbols
fourteenSymbols
>
17-fifteenSymbols 18-
Issue 01 (2016-04-29)

481216-
431

Access Module

Network
sixteenSymbols
>
4
>
upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
4
[n]:y
>
24
>
12
[n]:y
>
[32]:
>
[32]:
>
8000
>
[32]:
>
[32]:
>
[1024]:
[n]:
[n]:
3.

huawei(config)#adsl line-template add 10
Start adding template
Press 'Q' to quit the current configuration and new configuration will be
neglected
> Do you want to name the template (y/n) [n]:
> Please set the line-profile index (1~128) [1]:10
> Will you set channel configuration parameters? (y/n) [n]:y
>
Please set the channel number (1~2) [1]:1
>
Channel1 configuration parameters:
>
Please set the channel-profile index (1~128) [1]:10
Add template 10 successfully
4.

You can configure the ADSL2+ alarm profile based on your requirements. For detailed
configuration, see "Configuring an ADSL2+ Alarm Template." This example uses the
default alarm profile 1 in the system.
5.

Issue 01 (2016-04-29)

432

Access Module

Network

6.

7.

the configuration of the peer device.
Configure the VLAN.

The ADSL2+ users of MA5600T/MA5603T/MA5608T-2 use the PPPoE
authentication. In this case, the smart VLAN is used to identify the users.
8.

All ports in slot 0/3 provide the ADSL2+ services. To add service ports in batches, run
huawei(config)#multi-service-port vlan 2020 port 0/2 0-31 vpi 0 vci 35
rx-cttr 6 tx-cttr 6

1.

quickadd command.
psd
2.

3.
Configure the SHDSL traffic profile.

To configure the SHDSL traffic profile, run the traffic table ip command.
4.

Issue 01 (2016-04-29)

433

Access Module

Network
5.

The SHDSL users of MA5600T/MA5603T/MA5608T-2 use the PPPoE authentication.
In this case, the smart VLAN is used to identify the users.
6.
Ports 0-15 of the SHDSL board in 0/5 provide the SHDSL services.
To add service ports in batches, run the multi-service-port command.

rx-cttr 6 tx-cttr 6

1.
2.

NOTE
static route.
3.
huawei(config)#voip
4.


text
10.176.6.33
5.

NOTE
6.

Issue 01 (2016-04-29)

434

Access Module

Network
88660032
Step 12 Configure the stacking multi-ISPs wholesale service.

ISP1 provides users of ports 0/2/0 to 0/2/10 on board with the multi-ISP wholesale service.
ISP2 provides users of ports 11-20 to with the multi-ISP wholesale service. ISP3 provides
users of port 21-30 with the multi-ISP wholesale service.
1.
Create a VLAN and set the attribute as stacking.

huawei(config)#vlan 60 to 62 smart
huawei(config)#vlan attrib 60 to 62 stacking
2.

3.

huawei(config)#multi-service-port vlan 60 port 0/2 0-10 vpi 0 vci 35 rx-cttr
6 tx-cttr 6
6 tx-cttr 6
6 tx-cttr 6
4.
Configure the inner label.

huawei(config)#stacking label vlan 60 baselabel 111
Step 13 Configure the triple play service.

After the configuration, the following results should be achieved: Users of ports 0/2/16 can
watch the programs stored on servers 224.1.1.1 and 224.1.1.2, and can preview the programs
stored on server 224.1.1.3.
1.
Configure the upstream port and the VLAN.

huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#port
2.
100 smart
vlan 100 0/19 0-1
101 mux
vlan 101 0/19 0-1
102 smart
vlan 102 0/19 0-1
Configure the traffic table.

The voice service has the highest priority, and the Internet access service has the lowest
priority.
Assume that the Internet access service uses traffic table 6, with the priority of 0. The
following shows how to create the traffic tables for the voice service and the video
service respectively.
huawei(config)#traffic table ip index 7 cir 1024 priority 7
local-Setting
3.
Configure the service port.

4.
Configure the DHCP relay mode for the video service.
Issue 01 (2016-04-29)
Enable the DHCP mode.

435

Access Module

Network
huawei(config)#dhcp mode layer-3 option60
Configure the DHCP server.

huawei(config)#dhcp domain video
huawei(config-dhcp-domain-video)#dhcp-server 1
huawei(config-dhcp-domain-video)#quit
Configure the gateway mapped to the DHCP domain.

huawei(config-if-vlanif100)#dhcp domain video gateway 10.1.1.1
Enable the DHCP option82 function.

huawei(config)#raio-mode xdsl-port-rate
5.
Configure the DHCP relay mode for the voice service.

huawei(config)#dhcp domain voice
huawei(config-dhcp-domain-voice)#dhcp-server 2
huawei(config-dhcp-domain-voice)#quit

huawei(config-if-vlanif102)#dhcp domain voice gateway 10.4.4.1
6.


In this example, configure preview authority profile 1 with the preview duration
for the program to 150s, the number of preview attempts to 6 each day, and the
preview interval to 60s.
huawei(config)#btv
huawei(config-btv)#igmp preview-profile index 1 duration 150 times 6
interval 60

huawei(config-mvlan100)#igmp program add name program1 ip 224.1.1.1
preview-profile 1

huawei(config)#btv
program1 watch
program2 watch
program3 preview
Issue 01 (2016-04-29)

436

Access Module

Network

profile0

In the MSTP ring network, MA5600T/MA5603T/MA5608T-1 is subtended with MA5600T/
MA5603T/MA5608T-3, and MA5600T/MA5603T/MA5608T-3 is subtended with
MA5600T/MA5603T/MA5608T-4. According to the data plan, MA5600T/MA5603T/
MA5608T-4 provides the multicast service. In this way, it is necessary to configure the
multicast subtending on MA5600T/MA5603T/MA5608T-2 first.
1.

The upstream port is already added in Step 13.6. It is unnecessary to configure it again.
2.

The IGMP proxy is already configured in Step 13.6. It is unnecessary to configure it
again.
3.

The program library is already configured in Step 13.6. It is unnecessary to configure it
again.
4.
Specify the subtending port.

Modify the subtending port.


huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.

Issue 01 (2016-04-29)

437

Access Module

Network



2.
Add the route.

preference 1

preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.




example, the NMS version is set as SNMP V2C.
5.

6.

trap-paramsname abc
Issue 01 (2016-04-29)

438

Access Module

Network

trap-paramsname 123
7.


huawei(config)#ntp-service unicast-server 4.4.4.4 source-interface
vlanif 10
huawei(config)#ntp-service unicast-server 4.4.4.5 source-interface
vlanif 10

add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

This topic uses the fan and the PS4875L power supply as examples to describe how to
the fan monitoring unit as 1.

MA5600T/MA5603T/MA5608T-3 and MA5600T/MA5603T/MA5608T-4. Therefore, the
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#port
60 to 62 standard
vlan 60 to 62 0/19 0-1
101 to 102 standard
vlan 101 to 102 0/19 0-1
100 standard
vlan 100 0/19 0-1
Step 7 Enable MSTP.

1.

several
[N]Y
2.

3.

4.

to
Issue 01 (2016-04-29)

439

Access Module

Network
Step 8 Configure the ADSL2+ service.

1.

Start adding
profile
be
neglected
[n]:
>
Transmission
mode:
>
0:
Custom
>
1: All (G.
992.1~5,T1.413,ETSI)
>
2: Full rate(G.
992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G.
992.1/3/5)
>
4: G.HS (G.
992.1~5)
>
5: ADSL (G.
992.1~2,ETSI,T1.413)
>
992.3~5)
>
Please select (0~6)
[1]:
[2]:
[2]:
[2]:
downstream:
[2]:
upstream:
[2]:
[n]:
[n]:
[n]:
[n]:
[n]:
[n]:
[n]:
Issue 01 (2016-04-29)

440

Access Module
2.

Network

Start adding
profile
be
neglected
[n]:n
1
[n]:y
>
downstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
4
>
upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
4
[n]:y
>
24
>
12
[n]:y
>
[32]:
>
[32]:
>
8000
>
[32]:
>
[32]:
>
[1024]:
[n]:
[n]:
Issue 01 (2016-04-29)

441

Access Module
>
3.

Network
Will you set erasure decoding? (y/n) [n]:


The configured ADSL2+ line profile and the ADSL2+ channel profile are bound
together in the ADSL2+ line template and the index of the ADSL2+ line template is 10.
neglected
>
>
>
4.

You can configure the ADSL2+ alarm profile based on your requirements. For details on
the configuration, see "Configuring an ADSL2+ Alarm Template." In this example, the
default alarm profile (template 1) is used.
5.

6.

7.

that of the peer device.
Configure the VLAN.

The ADSL2+ users of MA5600T/MA5603T/MA5608T-3 use the VLAN
8.

rx-cttr 6 tx-cttr 6

Issue 01 (2016-04-29)

442

Access Module

Network
1.

quickadd command.
psd
2.

3.

4.

5.

The SHDSL users of MA5600T/MA5603T/MA5608T-3 use the VLAN authentication.
In this case, the smart VLAN is used to identify the users.
6.

Ports 0-15 in slots 0/5 provide the SHDSL service. To add service ports in batches, run
huawei(config)#multi-service-port vlan 3030 port 0/5 0-15 vpi 0 vci 35 userencap
pppoe rx-cttr 6 tx-cttr 6

1.

2.

3.
4.
Issue 01 (2016-04-29)
configure it.

443

Access Module

Network

tag-In-Package
5.
Add an ONT.
NOTE

NOTE
6.

7.

8.

9.


NOTE


1.

huawei(config-if-giu-0/19)#quit


Issue 01 (2016-04-29)

444

Access Module
2.

Network
Configure the subtending multicast.
Specify the subtending ports.

huawei(config)#btv
Modify the subtending ports.


huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.


Enter NMS VLAN interface mode.


2.
Add the route.

preference 1

preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
Issue 01 (2016-04-29)

445

Access Module

Network

destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure the SNMP.




The SNMP version must be the same as that of NMS. In this example, the NMS
version is set as SNMP V2C.
5.

6.

trap-paramsname abc
trap-paramsname 123
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

This topic uses the fan and the PS4875L power supply as examples to describe how to
Issue 01 (2016-04-29)

446

Access Module

Network
Step 6 Enable PITP.


1.

Start adding
profile
be
neglected
[n]:
>
Transmission
mode:
>
0:
Custom
>
1: All (G.
992.1~5,T1.413,ETSI)
>
2: Full rate(G.
992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G.
992.1/3/5)
>
4: G.HS (G.
992.1~5)
>
5: ADSL (G.
992.1~2,ETSI,T1.413)
>
992.3~5)
>
Please select (0~6)
[1]:
[2]:
[2]:
[2]:
downstream:
[2]:
upstream:
[2]:
[n]:
[n]:
[n]:
[n]:
[n]:
Issue 01 (2016-04-29)

447

Access Module

Network
[n]:
[n]:
2.

Start adding
profile
be
neglected
[n]:n
1
[n]:y
>
downstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
4
>
upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
4
[n]:y
>
24
>
12
[n]:y
>
[32]:
>
[32]:
>
8000
>
[32]:
>
[32]:
>
[1024]:
Issue 01 (2016-04-29)

448

Access Module

Network

[n]:
[n]:
3.

The configured ADSL2+ line profile and the ADSL2+ channel profile are bound
together in the ADSL2+ line template and the index of the ADSL2+ line template is 10.
neglected
>
>
>
4.

You can configure the ADSL2+ alarm profile based on your requirements. For details on
the configuration, see "Configuring an ADSL2+ Alarm Template." In this example, the
default alarm profile (template 1) is used.
5.

6.

7.

the configuration of the peer device.
Configure the VLAN.

The ADSL2+ users of MA5600T/MA5603T/MA5608T-4 adopt the PPPoE
8.

rx-cttr 6 tx-cttr 6
Issue 01 (2016-04-29)

449

Access Module

Network

1.

quickadd command.
psd
2.

3.

4.

5.

The SHDSL users of MA5600T/MA5603T/MA5608T-4 adopt the PPPoE
6.

Ports 0-15 in slot 0/5 provide the SHDSL service. To add service ports in batches, run
rx-cttr 6 tx-cttr 6

1.

2.

3.
Issue 01 (2016-04-29)
configure it.
450

Access Module
4.

Network

tag-In-Package
5.
Add an ONT.
NOTE

NOTE
6.

7.

8.

9.


NOTE


1.
2.

NOTE
static route.
3.
huawei(config)#voip
Issue 01 (2016-04-29)

451

Access Module

Network

4.


text
10.176.6.33
5.

NOTE
6.

88660000

l
Users of port 0/2/2 must be authenticated, and have rights to watch two programs and to
preview one program.
Users of port 0/2/3 do not need authenticating.
1.
Configure the xDSL.

1002) is used.
2.
Configure the VLAN.
Create a smart VLAN.

Set the VLAN upstream port.


Create a traffic profile.

Add ADSL2+ ports 2 and port 3 to VLAN 100.

huawei(config)#service-port vlan 100 adsl 0/2/2 vpi 0 vci 35 rx-cttr 8
tx-cttr 8
tx-cttr 8
Issue 01 (2016-04-29)

452

Access Module
3.

Network
Enable the multicast proxy function.


huawei(config)#btv

In this example, configure the preview authority profile with the preview
duration for the program to 150s, the number of preview attempts to 6 each day,
and the preview interval to 60s.
interval 60


1

huawei(config)#btv
program1 watch
program2 watch
program3 preview
Configure the user data.

profile0

huawei(config)#save
----End

Issue 01 (2016-04-29)

453

Access Module

Network
Procedure
huawei>enable
huawei#config

1.




2.
Add the route.
Configure the route destined to the NMS (trap destination host).

preference 1

preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.



Issue 01 (2016-04-29)

454

Access Module

Network

example, the NMS version is set as SNMP V2C.
5.

6.

trap-paramsname abc
trap-paramsname 123
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

This topic uses the fan and the PS4875L power supply as an example to describe how to
configure the EMU.
Step 6 Configure the VDSL2 service.

The MA5600T/MA5603T/MA5608T supports the VDSL2 Internet service of multiple
encapsulation modes, such as IPoA, PPPoA, IPoE, and PPPoE. This topic uses the PPPoE
mode as an example to describe how to configure the VDSL2 service. For other encapsulation
modes, see "3.1 Example of the xDSL Internet Access Service."
1.
Configure the VDSL2 line profile.

You can configure the VDSL2 line profile based on your requirements.
huawei(config)#vdsl line-profile add 10
Start adding
profile
be
neglected
[n]:
>
Transmission
mode:
>
0:
Custom
Issue 01 (2016-04-29)

455

Access Module

Network
>
1: All (G.992.1~5,T1.413,G.
993.2)
>
2: Full rate(G.992.1/3/5,T1.413,G.
993.2)
>
3: G.DMT (G.992.1/3/5,G.
993.2)
>
4: G.HS (G.992.1~5,G.
993.2)
>
5: ADSL (G.
992.1~5,T1.413)
>
6: VDSL (G.
993.2)
>
Please select (0~6)
[1]:
[2]:
> Bit swap upstream
1-disable 2-enable (1~2)
[2]:
downstream:
[2]:
upstream:
[2]:
[n]:
[n]:
> Will you set UPBO parameters? (y/n)
[n]:
[n]:
[n]:
> Will you set ADSL tone blackout configuration parameter? (y/n)
[n]:
> Will you set VDSL tone blackout configuration parameter? (y/n)
[n]:
[n]:
> Will you set network timing reference? (y/n)
[n]:
> Will you set INM parameter? (y/n)
[n]:
> Will you set SOS downstream parameter? (y/n)
[n]:
> Will you set SOS upstream parameter? (y/n)
[n]:
2.
Configure the VDSL2 channel profile.

You can configure the VDSL2 channel profile based on your requirements.
huawei(config)#vdsl channel-profile add 10
Start adding
profile
be
neglected
[n]:
1
[n]:y
>
downstream:
Issue 01 (2016-04-29)

456

Access Module

Network
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
3
>
upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12tenSymbols
>
>
>
3
[n]:y
>
Maximum interleaving delay downstream (0~200 ms)
[20]:
>
Maximum interleaving delay upstream (0~200 ms)
[20]:
[n]:y
>
[64]:
>
[64]:
>
Maximum transmit rate downstream (64~100000 Kbps)
[100000]:
>
[64]:
>
[64]:
>
[100000]:
[n]:
[n]:
> Will you set erasure decoding? (y/n)
[n]:
> Will you set SOS bit rate (y/n) [n]:
3.
Configure the VDSL2 line template.

huawei(config)#vdsl line-template add 10
neglected
>
>
>
Issue 01 (2016-04-29)

457

Access Module
4.

Network
Configure the VDSL2 alarm profile.

You can configure the VDSL2 alarm profile based on your requirements. For the
configuration, see "Configuring a VDSL2 Alarm Template." In this example, the default
alarm profile 1 is used.
5.
Configure the VDSL2 traffic profile.

You can configure the VDSL2 traffic profile by running the traffic table ip command
6.
Activate the VDSL2 port.

huawei(config-if-vdsl-0/2)#alarm-config all
huawei(config-if-vdsl-0/2)#activate all template-index 10
7.

In general, the GE optical port uses the default gigabit full-duplex mode.
To change the mode, switch to the GIU config mode. Then run the speed
command to change the port rate, and run the duplex command to change the
port duplex mode.
The settings of the upstream port must be the same as the settings on the peer
device.
Configure the VLAN.

The VDSL2 users of MA5600T/MA5603T/MA5608T-1 use the PPPoE
8.

All ports in slot 0/2 provide the VDSL2 Internet access service. To add service ports in
batches, run the multi-service-port command.
user-encap pppoe rx-cttr 6 tx-cttr 6

MA5600T/MA5603T/MA5608T-1 and MA5600T/MA5603T/MA5608T-5 serve two
branches of a company to provide the QinQ private line service.
1.
Create VLAN 50.

2.
Set VLAN50 as QinQ VLAN.

3.

4.

values set during the execution of the service-port command must be the same as those
on the modem.
Issue 01 (2016-04-29)

458

Access Module

Network

local-Setting
huawei(config)#service-port vlan 50 shdsl mode atm 0/5/15 vpi 0 vci 35 rxcttr 7 tx-cttr 7

huawei(config)#save
----End
5.8 Verification
Issue 01 (2016-04-29)

459

Access Module
6 Configuration Example of the VPLS
Configuration Example of the VPLS
About This Chapter

Virtual private LAN service (VPLS) enables geographically isolated users (individuals or
branch offices of an enterprise) to establish point-to-multipoint connections between each
other using Ethernet links, achieving fast and flexible service deployment.
Prerequisites
Only the SPUB board supports the VPLS.
Context
As a combination of Ethernet and Multiprotocol Label Switching (MPLS) technologies,
VPLS emulates all functions of the traditional local area network (LAN), with a purpose to
connect multiple geographically isolated LANs that consist of Ethernet using the IP or MPLS
network provided by carriers and make the LANs work as a LAN.
Currently, the MA5600T/MA5603T/MA5608T only supports Label Distribution Protocol
(LDP)-based VPLS.
Table 6-1 provides basic concepts of VPLS.
Table 6-1 Basic concepts of VPLS
Issue 01 (2016-04-29)
Concept
Description
VSI
Virtual switch instance. This concept corresponds to virtual local area

network (VLAN) of Ethernet switch. Each VSI provides independent VPLS
service. VSI supports the Ethernet bridge function and can terminate PW.

460

Access Module
Concept
Description
PW
Pseudo wire. PW is a virtual connection between two PEs and transmits

frames between the PEs. PEs use signaling to establish PWs and maintain
PW status.
On a VPLS network, PE routers transmit signaling to each other to establish
PWs of full interconnection. Signaling exchange modes are as follows:
l Martini mode: In this mode, signaling is exchanged using the LDP
protocol. This mode does not support the PE automatic discovery
function. PEs need to be configured manually. With this mode, the
networking is simple, and low requirements are imposed on PEs which do
not need to cross domains.
l Kompella mode: Signaling is exchanged using the Border Gateway
Protocol (BGP). The MA5600T/MA5603T/MA5608T does not support
this mode.
AC
Attachment circuit. AC attaches a CE to a PE. An AC can be a physical or

logical link. It transmits frames between the CE and PE.
Split
horizon
Split horizon is a technology that prevents route loops and speeds up route
convergence. In a VPLS network, full mesh and split horizon are used to
prevent loops. Split horizon in VPLS means that the data packets received
from the PW at the PSN side are not forwarded to other PWs. Instead, they
are forwarded to the private network.
6.1 Example of the VPLS Service

This topic describes how to configure the Internet access service for individual users when the
VPLS networking is used at the access and aggregation layers.
6.2 Example of the VPLS Multicast Service
In the networking for multicast services, VPLS deployed on the MA5600T/MA5603T/
MA5608T enables the MA5600T/MA5603T/MA5608T to be dual homed to AGS devices
(aggregation switches), which ensures network reliability.
6.3 Example of the VPLS Enterprise Private Line Service
This topic describes how to configure the enterprise private line service when the VPLS
networking is used at the access and aggregation layers.
Issue 01 (2016-04-29)

461

Access Module
6.1 Example of the VPLS Service

This topic describes how to configure the Internet access service for individual users when the
VPLS networking is used at the access and aggregation layers.
Application Context
As shown in Figure 6-1, the MA5600T/MA5603T/MA5608T is dual homed to two AGS
devices (aggregation switches) PE3 and PE4 through VPLS, and the Internet access service is
received in PPPoE dialup mode. In the upstream direction, the traffic stream is mapped into
the VPLS domain through VLAN. The PPPOE active discovery initiation (PADI) packets
initiated by the user are broadcast in the VPLS domain it belongs to, and then the broadcast
packets are received by the two AGS devices. The AGS devices terminate packets of some
users respectively in delay response mode to achieve load sharing. When a BRAS device is
faulty, the user dials up again. Then the VPLS MAC learning and forwarding mechanism
automatically selects a new BRAS to provide services.
Figure 6-1 Networking for the VPLS Internet access service for individual users
Internet
BRAS1
BRAS2 Service carry &

Control Layer
IP Core
PE3
PE4
PW1
PW2
VPLS
PE1
Access &
Aggregation Layer
PE2
OLT/MSAN
ONU
HG
Customer
Premises
HSI
VPLS PW
Issue 01 (2016-04-29)

462

Access Module
Prerequisite
Traffic streams have been configured on the MA5600T/MA5603T/MA5608T for the Internet
access service.
NOTE
To configure the Internet access service, you must configure SVLAN 100-based traffic streams on the
MA5600T/MA5603T/MA5608T and perform corresponding configurations on the HG. The configurations
are the same as those for common Internet access service, which are not described here.
Data Plan
Table 6-2 provides the key data plan for the MA5600T/MA5603T/MA5608T.
Table 6-2 Key data plan
Confi
gurati
on
Item
Data
Remarks
Requirement on PE3 and

PE4
MPLS
l LSR ID:
10.10.10.10
MPLS must be enabled at

three layers.
l VLAN: 4001
l MPLS must be enabled

globally.
The LSR ID must be unique

on the entire network and
MPLS must be enabled.

for VLAN.
at VLAN interfaces.
LDP
l MPLS LDP is
enabled.
MPLS LDP must be enabled

at three layers.
l Split horizon is
enabled.
l MPLS LDP must be

enabled globally.
l MPLS LDP must be
enabled at VLAN
interfaces.
Routin
g
protoc
ol
Issue 01 (2016-04-29)
The Open Shortest

Path First (OSPF)
protocol is used.
Ensure that the Layer 3

interfaces on the MA5600T/
MA5603T/MA5608T and
those on PE3 and PE4 can
ping each other.

MPLS LDP is enabled. The

remote LDP session to the
MA5600T/MA5603T/
MA5608T is configured on
PE3 and PE4.
Layer 3 interfaces and routes

are configured on PE3 and
PE4. Ensure that the Layer 3
interfaces and LSR IDs on
PE3 and PE4 and those on
the MA5600T/MA5603T/
MA5608T can ping each
other.
463

Access Module
Confi
gurati
on
Item
Data
Remarks
Requirement on PE3 and

PE4
VPLS
PW
l PW ID: 1 and 2
On the MA5600T/
MA5603T/MA5608T, PW1
and PW2 are created for
PE3 and PE4 respectively.
In this way, packets can be
transmitted to BRAS
devices over two trails.
The LDP VPLS is

supported. VPLS PWs to the
MA5600T/MA5603T/
MA5608T are configured on
PE3 and PE4, and attributes
of PWs are consistent with
those on the MA5600T/
MA5603T/MA5608T.
VSI binds VLAN and PW to

map VLAN to the VPLS
domain, so that PADI
packets for the Internet
access service can be
broadcast in the VPLS
domain at first, until one of
the BRAS response.
VSI is configured on PE3

and PE4 and the VSI ID
must bind the corresponding
PW.
l Service type:
vpls
l Encapsulation
type: ethernet
tagged
l The control
word is
enabled.
VSI
l PW1 and PW2

are bound to
VSI.
l VLAN 100 of
the Internet
access service
is bound to
VSI.
Procedure
Step 1 Configure the basic MPLS.
1.
Configure a loopback interface.

2.
Configure the MPLS LSR-ID. Use the IP address of loopback interface 0 as the LSR ID.
3.
Enable MPLS globally.

Trigger LDP by the IP address of the host to set up an LSP.
huawei(config)#mpls
4.
Enable the L2VPN function.

5.
Enable the LDP function globally and enable the split horizon policy.
huawei(config-mpls-ldp)#outbound peer all split-horizon
Step 2 Configure VLAN and enable MPLS for VLAN and VLAN interfaces.
1.
Issue 01 (2016-04-29)
Add VLAN 4001 for forwarding MPLS packets and add upstream port 0/19/0 and 0/19/1
to it.
464

Access Module

2.

3.
Set the IP address of VLAN interface 4001 to 10.50.50.50/24 and enable MPLS LDP for
the VLAN interface.
Step 3 Configure routes.

VPLS has no special requirements on routing policy. You can use static route, RIP, or OSPF
policy. In the following example, OSPF is used.
interfaces.
Step 4 Configure the remote LDP session.

Configure the remote LDP session from the MA5600T/MA5603T/MA5608T to PE3 (LSR
ID: 3.3.3.3) and PE4 (LSR ID: 4.4.4.4) respectively. Name the sessions to_pe3 and to_pe4
respectively.
huawei(config)#mpls ldp remote-peer to_pe3
huawei(config-mpls-ldp-remote-to_pe3)#remote-ip
huawei(config-mpls-ldp-remote-to_pe3)#quit
3.3.3.3
auto-dod-request
4.4.4.4
auto-dod-request
Step 5 Configure a VSI.

1.
Add a VSI.
Create a VSI named hsi. Set the signaling protocol to LDP. and VSI ID to 1.
huawei(config)#vsi hsi
huawei(config-vsi-hsi)#pwsignal ldp
huawei(config-vsi-hsi)#vsi-id 1
2.
(Optional) Configure the attributes of VSI.

Configure basic attributes of VSI as required, including the encapsulation type, control
word, MTU value, and traffic suppression policy. In the following example, the control
word is enabled and default values are used for other parameters.
huawei(config-vsi-hsi)#control-word
Step 6 Configure PWs.

Create two PWs with IDs 1 and 2. Set the service type to vpls, remote IP addresses to 3.3.3.3
and 4.4.4.4 respectively, and encapsulation type to ethernet tagged. Enable the control word,
and set the receive labels of dynamic PW to 10240 and 10250 respectively.
huawei(config)#pw-para pwindex 1
huawei(config-pw-para-index-1)#service-type vpls
huawei(config-pw-para-index-1)#pwid 1
huawei(config-pw-para-index-1)#peer-address 3.3.3.3
Issue 01 (2016-04-29)

465

Access Module
huawei(config-pw-para-index-1)#pw-type ethernet tagged

huawei(config-pw-para-index-1)#control-word enable
huawei(config-pw-para-index-1)#dyn-receive-label 10240
huawei(config-pw-para-index-1)#quit
Step 7 Bind PW and VSI.

Dynamically bind PW1 and PW2 to the VSI named hsi to establish the VPLS PW service.
huawei(config)#vsi hsi
huawei(config-vsi-hsi)#vsi-pw-binding pwindex 1
huawei(config-vsi-hsi)#vsi-pw-binding pwindex 2
Step 8 Bind AC and VSI.

Bind VLAN 100 to the VSI named hsi, so that the Internet access service packets of VLAN
100 can be forwarded in the VSI.
huawei(config-vsi-hsi)#vsi-ac-binding vlan 100
----End
Result
1.
A user performs PPPoE dialup. A PADI packet is transmitted upstream.
2.
The OLT maps the PADI packet to VSI based on SVLAN carried in the packet and
broadcasts the packet on two PWs. At the same time, the OLT learns user's MAC
address.
3.
After receiving the PADI packet, two BRAS devices respond with PPPOE active
discovery offer (PADO) packets in random delay mode.
4.
After receiving the PADO packets from PWs, the OLT learns the MAC address carried
in the packets from PWs and forwards the packets to the user.
5.
The user receives two PADO packets at different time and only responds to the first
received PADO packet to establish a PPPoE session.
6.
The OLT forwards subsequent PPPOE active discovery request (PADR) and PPPOE
active discovery session-confirmation (PADS) packets based on learnt MAC addresses.
6.2 Example of the VPLS Multicast Service

In the networking for multicast services, VPLS deployed on the MA5600T/MA5603T/
MA5608T enables the MA5600T/MA5603T/MA5608T to be dual homed to AGS devices
(aggregation switches), which ensures network reliability.
Application Context
In the VPLS network, multicast services are still deployed based on multicast VLAN other
than based on VSI (VPLS instance). The multicast VLAN is bound to VSI for carrying
multicast services over the VPLS network, including upstream IGMP packets and
downstream multicast traffic streams.
Issue 01 (2016-04-29)

466

Access Module
Figure 6-2 Networking for the VPLS multicast service

SPE1
PE1
Multicast
Router
PE2
Multicast
Router
PW1
VPLS
UPE
PW2
SPE2
HVPLS
VPLS
VPLS Multicast
VPLS PW
As shown in Figure 6-2:

l
The MA5600T/MA5603T/MA5608T, functioning as a UPE (underlayer PE), is located

on the edge network of HVPLS. In the downstream direction, the MA5600T/MA5603T/
MA5608T accesses multicast users through multicast VLAN whose IGMP mode is
proxy or snooping. In the upstream direction, the MA5600T/MA5603T/MA5608T is
dual homed to two AGS devices that serve as SPEs (superstratum PEs) through two
PWs. The same VSI is set up on the MA5600T/MA5603T/MA5608T and AGS and the
two upstream PWs belong to the VSI.
Multiple AGS devices form a VPLS core bearer network. The AGS devices learn the
VPLS multicast forwarding table and duplicate multicast traffic based on VPLS PW
connections. Two edge AGS devices functioning as SPEs in the downstream direction
access the UPE on the edge network, and two edge AGS devices functioning as PEs in
the upstream direction terminate VPLS and are connected to multicast routers.
Two multicast routers back up each other and import multicast traffic streams from the
multicast source to the VPLS bearer network.
NOTE
Currently, a maximum of two PWs are supported for VPLS multicast services and both two PWs are used for
transmitting multicast packets upstream.
Prerequisite
The MA5600T/MA5603T/MA5608T has been configured with multicast VLAN 100-based
multicast traffic streams, and corresponding configurations have been performed on the HG.
The configurations are similar to those for common multicast services. The difference is that
multicast upstream ports do not need to be configured for VPLS multicast services and the
default mode is used for the multicast upstream ports.
Data Plan
Table 6-3 provides the key data plan for the MA5600T/MA5603T/MA5608T.
Issue 01 (2016-04-29)

467

Access Module

Confi
gurati
on
Item
Data
Remarks
Requirement on SPE1
and SPE2
MPLS
l LSR ID:
10.10.10.10

three layers.
l VLAN: 4001

globally.


for VLAN.
at VLAN interfaces.
LDP
l MPLS LDP is
enabled.

at two layers.
l Split horizon is
enabled.
l MPLS LDP must be

enabled globally.
l MPLS LDP must be
enabled at VLAN
interfaces.
Routin
g
protoc
ol
The Open Shortest

Path First (OSPF)
protocol is used.

MA5603T/MA5608T and
those on SPE1 and SPE2
can ping each other.

are configured on SPE1 and
SPE2. Ensure that the Layer
3 interfaces and loopback
interfaces on SPE1 and
SPE2 and those on the
MA5600T/MA5603T/
other.
VPLS
PW
l PW ID: 1 and 2
L2VPN must be enabled.
l Service type:
vpls
On the MA5600T/
MA5603T/MA5608T, PW1
SPE1 and SPE2
respectively.
The LDP VPLS is

supported. VPLS PWs to the
MA5600T/MA5603T/
SPE1 and SPE2, and
attributes of PWs are
consistent with those on the
MA5600T/MA5603T/
MA5608T.
l Encapsulation
type: ethernet
tagged
l The control
word is
enabled.
VSI
l PW1 and PW2

are bound to
VSI.
l Multicast
service VLAN
100 is bound to
VSI.
Issue 01 (2016-04-29)

MA5600T/MA5603T/
SPE1 and SPE2.
Multicast VLAN is bound

through VSI to map VLAN
to the VPLS domain, so that
multicast service packets
can be broadcast in the
VPLS domain.

VSI is configured on SPE1

and SPE2 and the VSI ID
must bind the corresponding
PW.
468

Access Module
Procedure
1.

2.
3.

huawei(config)#mpls
4.

5.
Enable the LDP function globally and enable the split horizon policy.
huawei(config-mpls-ldp)#outbound peer all split-horizon
Step 2 Configure VLAN, and enable MPLS for VLAN and VLAN interfaces.
1.
Add VLAN 4001 for forwarding MPLS packets and add two upstream ports to it.
2.

3.
the VLAN interface.

interfaces.

Issue 01 (2016-04-29)

469

Access Module
Configure the remote LDP sessions from the MA5600T/MA5603T/MA5608T to SPE1 (LSR
ID: 1.1.1.1) and SPE2 (LSR ID: 2.2.2.2) respectively. Name the sessions to_spe1 and to_spe2
respectively.
huawei(config)#mpls ldp remote-peer to_spe1
huawei(config-mpls-ldp-remote-to_spe1)#remote-ip
huawei(config-mpls-ldp-remote-to_spe1)#quit
huawei(config)#mpls ldp remote-peer to_spe2
huawei(config-mpls-ldp-remote-to_spe2)#quit
1.1.1.1
auto-dod-request
2.2.2.2
auto-dod-request
Step 5 Configure a VSI.

1.
Add a VSI.
Create a VSI named multicast. Set the signaling protocol to LDP and VSI ID to 1.
huawei(config)#vsi multicast
huawei(config-vsi-multicast)#pwsignal ldp
huawei(config-vsi-multicast)#vsi-id 1
2.
(Optional) Disable the suppression of the unknown multicast of the VSI.

If the VSI unknown multicast suppression is enabled, you need to configure this step.
Otherwise, packet loss will occur in the multicast services.
huawei(config-vsi-multicast)#undo traffic-suppress multicast
3.
(Optional) Configure attributes of VSI.

word, and MTU value. In the following example, the control word is enabled and default
values are used for other parameters.
huawei(config-vsi-multicast)#control-word

Create two PWs with IDs 1 and 2. Set the service type to vpls, the remote IP addresses to
1.1.1.1 and 2.2.2.2 respectively, and encapsulation type to ethernet tagged. Enable the
control word, and set the receive labels of dynamic PW to 10240 and 10250 respectively.

Dynamically bind PW1 and PW2 to the VSI named multicast to establish the VPLS PW
service.
huawei(config)#vsi multicast
huawei(config-vsi-multicast)#vsi-pw-binding pwindex 1
huawei(config-vsi-multicast)#vsi-pw-binding pwindex 2

Bind multicast VLAN 100 to the VSI named multicast, so that the multicast service packets of
VLAN 100 can be forwarded in VSI.
Issue 01 (2016-04-29)

470

Access Module
The same multicast VLAN cannot be bound to the VPLS instance and PW at the same
time.
The same restrictions are set for binding multicast VLANs and VSI as those for binding
unicast VLANs and VSI. That is, when the VPLS encapsulation type is raw, one VIS can
only be bound to a multicast VLAN; when the VPLS encapsulation type is tag, one VSI
can be bound to multiple multicast VLANs.
huawei(config-vsi-multicast)#vsi-ac-binding vlan 100
----End
Result
1.
A user orders a multicast program. An IGMP packet is transmitted upstream.
2.
The MA5600T/MA5603T/MA5608T broadcasts the IGMP packet over two upstream

PWs which serve as the multicast upstream ports of the multicast VLAN.
3.
On the AGS devices, VPLS exchange is performed on the IGMP packet. The AGS
devices learn the VPLS multicast forwarding table and duplicate multicast traffic based
on VPLS PW connections.
4.
Finally, multicast traffic streams are transmitted over one PW. The MA5600T/
MA5603T/MA5608T forwards the multicast traffic streams to the corresponding user
port based on the local multicast forwarding table. Then the user can watch the multicast
program normally.
6.3 Example of the VPLS Enterprise Private Line Service

This topic describes how to configure the enterprise private line service when the VPLS
networking is used at the access and aggregation layers.
Application Context
As shown in Figure 6-3, branch offices of an enterprise access the VPLS network through a
CE or PE. By deploying VPLS PWs between PEs, the service provider can provide Ethernetbased multipoint services to enterprise users over the MPLS backbone network and achieve
emulation of the local area network (LAN). For important branch offices (for example, branch
C in the following figure), PW redundancy is configured to provide protection.
In the following figure, as a key node, the OLT/MSAN (MA5600T/MA5603T/MA5608T)
exchanges data with PEs (PE1-PE4) through VPLS PWs. For important branch offices, a PW
protection group is configured to provide protection. PEs are connected to the OLT/MSAN
using Spoke PW.
Issue 01 (2016-04-29)

471

Access Module
Figure 6-3 Networking for the VPLS enterprise private line service
Branch C
PE2 (CX600)
CE
PW2
(Master)
PE3 (CX600)
VPLS
PW3
(Slave)
PW1
OLT/MSAN
PW4
PE1
PE4
Branch A
Branch B
VPLS PW
Prerequisite
QinQ traffic streams have been configured on PE1-PE4 for the private line service of different
branch offices.
NOTE
To configure the Ethernet-based enterprise private line service, you must configure QinQ VLAN-based
Ethernet traffic streams on PE1-PE4, and perform corresponding configurations on routers for branch offices
of the enterprise. The configurations are the same as those for common QinQ VLAN private line service,
which are not described here.
Data Plan
Table 6-4 provides the key data plan for the OLT/MSAN (MA5600T/MA5603T/MA5608T).
Confi
gurati
on
Item
Data
Remarks
Requirement on PE1-PE4
MPLS
l LSR ID:
10.10.10.10

three layers.
l VLAN: 4001

globally.


for VLAN.
at VLAN interfaces.
Issue 01 (2016-04-29)

472

Access Module
Confi
gurati
on
Item
Data
Remarks
LDP
MPLS LDP is
enabled.

at three layers.

MA5600T/MA5603T/
PE1-PE4.
l MPLS LDP must be

enabled globally.
l MPLS LDP must be
enabled at VLAN
interfaces.
Routin
g
protoc
ol
The Open Shortest

Path First (OSPF)
protocol is used.

MA5603T/MA5608T and
those on PE1-PE4 can ping
each other.

are configured on PE1-PE4.
interfaces and LSR IDs on
PE1-PE4 and those on the
MA5600T/MA5603T/
other.
VPLS
PW
l PW ID: 1, 2, 3,
4
On the OLT/MSAN, PW1

PE1 and PE4 respectively,
The LDP VPLS is

supported, and VPLS PWs
to the MA5600T/MA5603T/
PE1-PE4, and attributes of
PWs are consistent with
those on the MA5600T/
MA5603T/MA5608T.
l Service type:
vpls
l Encapsulation
type: ethernet
tagged
and PW2 and PW3 are

created for PE2 and PE3
respectively. PW2 and PW3
back up each other.
l The control
word is
enabled.
PW protection
group:
l PW ID: 2, 3
l Working mode:
master-slave
l The dual
receiving
function is
enabled for
PWs.
Issue 01 (2016-04-29)

473

Access Module
Confi
gurati
on
Item
Data
Remarks
VSI
l PW1-PW4 are
bound to VSI.
VSI binds VLAN and PW to

map VLAN to the VPLS
domain, so that packets for
the enterprise private line
service can be broadcast in
the VPLS domain.
VSI is configured on PE1PE4 and the VSI ID must

bind the corresponding PW.
l Binding mode
of PW 1 and
PW 4: spoke
l VLAN 100 of
the private line
service is
bound to VSI.
Procedure
1.

2.
3.

huawei(config)#mpls
4.

5.
Enable LDP globally.

Step 2 Configure VLAN, and enable MPLS for VLAN and VLAN interfaces.
1.
Add VLAN 4001 for forwarding MPLS packets and add four upstream ports to it.
huawei(config)#vlan
huawei(config)#port
huawei(config)#port
huawei(config)#port
huawei(config)#port
2.
4001
vlan
vlan
vlan
vlan
smart
4001 0/19
4001 0/19
4001 0/20
4001 0/20
0
1
0
1

3.
the VLAN interface.
Issue 01 (2016-04-29)

474

Access Module

interfaces.

Configure the remote LDP session from the MA5600T/MA5603T/MA5608T to PE1 (LSR
ID: 5.5.5.5), PE2 (LSR ID: 2.2.2.2), PE3 (LSR ID: 3.3.3.3), and PE4 (LSR ID: 4.4.4.4)
respectively. Name the sessions to_pe1, to_pe2, to_pe3, and to_pe4 respectively.
5.5.5.5
auto-dod-request
2.2.2.2
auto-dod-request
3.3.3.3
auto-dod-request
4.4.4.4
auto-dod-request
Step 5 Configure VSI.

1.
Add a VSI.
Create a VSI named enterprise_vpn. Set the signaling protocol to LDP and VSI ID to 1.
huawei(config)#vsi enterprise_vpn
huawei(config-vsi-enterprise_vpn)#pwsignal ldp
huawei(config-vsi-enterprise_vpn)#vsi-id 1
2.
(Optional) Configure the attributes of VSI.

word, MTU value, and traffic suppression policy. In the following example, the control
word is enabled and default values are used for other parameters.
huawei(config-vsi-enterprise_vpn)#control-word

Create four PWs with IDs 1-4. Set the service type to vpls, the remote IP addresses to the IP
addresses of PE1-PE4, and encapsulation type to ethernet tagged. Enable the control word,
and set the receive labels of dynamic PW to 10240, 10250, 10260, and 10270 respectively.
Issue 01 (2016-04-29)

475

Access Module

Dynamically bind PW 1 and PW 4 in spoke mode, and dynamically bind PW 2 and PW 3 to
the VSI named enterprise_vpn to establish the VPLS PW service. The spoke mode is used to
identify the peer is a user-side PE, and split horizon is not performed between PWs.
huawei(config-vsi-enterprise_vpn)#vsi-pw-binding
pwindex
pwindex
pwindex
pwindex
1 spoke
2
3
4 spoke
Step 8 Configure VPLS PW protection.

Configure PW2 and PW3 as a PW protection group named pg_pw. Set the working mode to
master-slave and enable the dual receiving function for PWs. In the protection group enabled
with dual receiving, two PWs are always allowed to receive traffic. In this way, when the
remote device performs traffic switching, the traffic will not be dropped.
huawei(config-vsi-enterprise_vpn)#protect-group pg_pw
huawei(config-vsi-enterprise_vpn-group-pg_pw)#pw-protect primary-pw pwindex 2
secondary-pw pwindex 3
huawei(config-vsi-enterprise_vpn-group-pg_pw)#protect-mode master
huawei(config-vsi-enterprise_vpn-group-pg_pw)#stream-dual-receiving

Bind QinQ VLAN 100 to the VSI named enterprise_vpn, so that the enterprise private line
service packets can be forwarded in the VSI.
huawei(config-vsi-enterprise_vpn)#vsi-ac-binding vlan 100
----End
Result
As shown in Figure 6-3, the private networks distributed in different branches can establish
point-to-multipoint communication with each other and various services can be provisioned
between these private networks. When a PE which branch C is connected to is faulty, services
can be automatically switched to another PE and therefore services are not affected.
Issue 01 (2016-04-29)

476

Access Module
7 Configuration Example of the Subtending Networking
Configuration Example of the Subtending

Networking
About This Chapter

This topic describes how to configure the integrated services on the MA5600Ts in the multitier subtending network.
7.1 Subtended Network
This topic describes an example of subtended network.
7.2 Data Plan for Subtended Network
This topic describes the data plan for the example subtended network.
7.3 Configuring MA5600T-1
This topic describes how to configure MA5600T-1.
7.7 Verification
Issue 01 (2016-04-29)

477

Access Module
7.1 Subtended Network

This topic describes an example of subtended network.
As shown in Figure 7-1:
l
MA5600T-1 is subtended with MA5600T-2 through the GE port on the GIU board.
MA5600T-2 is subtended with MA5600T-3 through the GE port on the GIU board.
Figure 7-1 shows an example subtended network of the MA5600T.
Issue 01 (2016-04-29)

478

Access Module
Figure 7-1 Example subtended network of the MA5600T

iManager N2000
DHCP Server
ISP2
ISP1
Multicast
Server
SoftSwitch
ISP3
LAN
Switch
BRAS
A
D
L
F
A
S
R
B
S
H
D
A
MA5600T-1
18
G
P
B
C
V
D
S
A
S
H
D
A
CON
ETH
ESC
SCU
SCU
2 3
A
D
L
F
S
H
D
A
A
S
R
B
STB
A
D
L
F
A
S
R
B
S
H
D
A
MA5600T-4
9
CON
ETH
ESC
SCU
Home Gateway
CON
ETH
ESC
MA5600T-2
18
9
CON
ETH
ESC
G
P
B
C
MA5600T-3
SCU
Ephone
TV
PC
Splitter
ADSL2+
Modem
ONT
...
phone1
phone32
PC
PC
7.2 Data Plan for Subtended Network

This topic describes the data plan for the example subtended network.
Issue 01 (2016-04-29)

479

Access Module
Table 7-1 provides the service and the data plan for the example subtended network of the
MA5600T in Figure 7-1.
Table 7-1 Data plan for the example subtended network
Item
MA5600T-1
MA5600T-2
MA5600T-3
MA5600T-4
Service
l ADSL2+
service
l ADSL2+
service
l ADSL2+
service
l VDSL2
service
l SHDSL
service
l SHDSL
service
l SHDSL
service
l GPON
service
l POTS service
l GPON service
l Stacking
wholesale
service
l POTS service
l QinQ private
line service
(for the
private line
interconnectio
n
withMA5600
T-1)
l POTS service
l QinQ private
line service
(for the
private line
interconnecti
on
withMA5600
T-4)
l Multicast
service
l Triple play
service
l Multicast
service
Inband
NMS
address
GE port
of the
GIU
board
Issue 01 (2016-04-29)
10.10.1.2
10.10.1.3
10.10.1.4
10.10.1.5
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
Gateway:
Gateway:
Gateway:
Gateway:
10.10.1.1/24
10.10.1.1/24
10.10.1.1/24
10.10.1.1/24
Upstream:
0/19/0
Upstream: 0/19/0
Upstream: 0/19/0
Upstream: 0/19/0
Subtending:
0/19/1
Subtending:
0/19/1

480

Access Module
Item
MA5600T-1
MA5600T-2
MA5600T-3
MA5600T-4
VLAN
NMS: 10
NMS: 10
NMS: 10
NMS: 10
QinQ: 50
Stacking: 60-62
(inner label:
111-113)
Multicast: 100
QinQ: 50
ADSL2+: 1000
(uses the PPPoE
authentication)
VDSL2: 1800
(uses the PPPoE
authentication)
Multicast: 100
ADSL2+:
1000-1031 (uses
the VLAN
authentication)
SHDSL:
1300-1315 (uses
the VLAN
authentication)
Triple play:
100-102
ADSL2+: 1000
(uses the PPPoE
authentication)
SHDSL: 1300
(uses the PPPoE
authentication)
SHDSL: 1300
(uses the PPPoE
authentication)
GPON: 1530 (the

ONT uses the SN
+ password
authentication)
POTS: 1600 (uses

the H.248
protocol)
POTS: 1600
(uses the H.248
protocol)
ADSL2+: 0/2
ADSL2+: 0/2
ADSL2+: 0/2
SHDSL: 0/5
SHDSL: 0/5
SHDSL: 0/5
SHDSL: 0/5
VDSL: 0/2
GPON: 0/18
POTS: 0/3
GPON: 0/18
QinQ: 0/5/15
POTS: 0/3
Stacking:
POTS: 0/3
QinQ: 0/5/15
0/2/0-10 (map
VLAN 60, ISP1)
GPON: 1510
(the ONT uses
the SN +
password
authentication)
POTS: 1600
(uses the H.248
protocol)
Slot and
port
Multicast: 0/2/2,
0/2/3
0/2/11-20 (map
VLAN 61, ISP2)
0/2/21-30 (map
VLAN 62, ISP3)
Triple play:
0/2/31
POTS
service
MGC IP address: 10.30.80.65/24

Media/Signaling IP address of the MG interface: 10.176.6.33/24
Default media gateway of the MG interface: 10.176.6.62/24
IP address of the VLAN: 10.176.6.33/24
MG interface attributes: index is 0, supported protocol is H.248, coding type is
text, signaling port number is 2944, port number of the active MGC is 2944,
and transmission mode is UDP.
Issue 01 (2016-04-29)
NMS
host
2.2.2.2 and 2.2.2.3
Log host
3.3.3.3 and 3.3.4.3

481

Access Module
Item
MA5600T-1
MA5600T-2
MA5600T-3
Time
server
4.4.4.4 and 4.4.4.5
Multicast
server
10.10.10.10
EMU
Fan monitoring
DHCP
server
DHCP server1: 10.1.1.2 (active), 10.1.1.3 (standby)
MA5600T-4
Gateway: 10.1.1.1/24
DHCP server2: 10.4.4.2 (active), 10.4.4.3 (standby)
Gateway: 10.4.4.1/24
Upperlayer
device
The upper-layer device supports the DHCP option82 function.

The BRAS supports the PITP, Stacking, and QinQ function.
The BRAS supports inner and outer VLAN tags.
The VLAN ID of the traffic flow sent from the IP network to the DSLAM is
100.
The upper-layer device classifies the downstream traffic. Different services
carry different 802.1p labels.
The VLAN mapping to the DSLAM is configured at the upper-layer device.
NOTE
l In this networking, MA5600T-1 can be replaced with a GE switch or a BRAS.

l The upstream port of the MA5600T supports the port aggregation function. In the actual network
planning, you can aggregate multiple upstream ports for use.
l In this networking, the four MA5600Ts support the ADSL2+, SHDSL, VDSL2, GPON, and POTS
services. You can plan the services according to your actual network conditions.

Procedure
huawei>enable
huawei#config

1.


It will take several minutes, and console may be timeout, please use
Issue 01 (2016-04-29)

482

Access Module
command
idle-timeout to set time
limit

Configure the IP address of the NMS interface.

2.
Add the route.
Configure the route destined to the NMS (Trap destination address).

preference 1
preference 1

preference 1
preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.
Set the community name and access authority.

Set the SysContact.

Set the SysLocation.


The SNMP version must be the same as that of the NMS. In this example, the
SNMP version is set as SNMP V2C.
5.

Issue 01 (2016-04-29)

483

Access Module
6.
Set trap destination address.

trap-paramsname abc
trap-paramsname 123
7.
Set trap source address.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

This topic uses the fan monitoring as an example to show how to configure the EMU.
In this example, assume that the slave node number is 1. In this case, you need to set the DIP
switch of the node address on the fan monitoring unit as 1.
huawei(config)#emu add 0 h801ESC 0 0

MA5600T-1 is subtended with MA5600T-2 andMA5600T-3. Therefore, the subtending
should be configured.
huawei(config)#vlan 60 to 62 standard
huawei(config)#vlan 101 to 102 standard

The MA5600T supports the ADSL2+ service of multiple encapsulation modes, such as IPoA,
PPPoA, IPoE, and PPPoE. This topic uses the PPPoE mode as an example to describe how to
configure the ADSL2+ service. For other encapsulation modes, see "3.1 Example of the
xDSL Internet Access Service."
1.

You can configure it based on your requirements.
Start adding profile
neglected
> Do you want to name the profile (y/n) [n]:
>
Transmission mode:
>
0: Custom
>
1: All (G992.1~5,T1.413,ETSI)
>
2: Full rate(G992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G992.1/3/5)
>
4: G.HS (G992.1~5)
>
5: ADSL (G992.1~2,ETSI,T1.413)
>
6: ADSL2 & ADSL2+ (G992.3~5)
Issue 01 (2016-04-29)

484

Access Module
>
>
>
>
>
>
>
>
>
>
>
>
>
2.

Trellis mode 1-disable 2-enable (1~2) [2]:
Bit swap downstream 1-disable 2-enable (1~2) [2]:
Bit swap upstream 1-disable 2-enable (1~2) [2]:
Please select the form of transmit rate adaptation downstream:
1-fixed, 2-adaptAtStartup, 3-adaptAtRuntime (1~3) [2]:
Please select the form of transmit rate adaptation upstream:
Will you set SNR margin parameters? (y/n) [n]:
Will you set DPBO parameters? (y/n)[n]:
Will you set power management parameters? (y/n) [n]:
Will you set tone blackout configuration parameter? (y/n) [n]:
Will you set mode-specific parameters? (y/n) [n]:

The ADSL2+ channel profile should be configured based on the actual channel
condition.
neglected
> Will you set the minimum impulse noise protection? (y/n) [n]:y
>
Minimum impulse noise protection downstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
13-elevenSymbols 14-twelveSymbols 15-thirteenSymbols 16-fourteenSymbols
>
17-fifteenSymbols 18-sixteenSymbols
>
Please select (1~18) [2]:4
>
Minimum impulse noise protection upstream:
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
> Will you set interleaving delay parameters? (y/n) [n]:y
>
Maximum interleaving delay downstream (0~63 ms) [16]:24
>
Maximum interleaving delay upstream (0~63 ms) [6]:12
> Will you set parameters for rate? (y/n) [n]:y
>
Minimum transmit rate downstream (32~32000 Kbps) [32]:
>
Minimum reserved transmit rate downstream (32~32000 Kbps) [32]:
>
Maximum transmit rate downstream (32~32000 Kbps) [24544]:8000
>
Minimum transmit rate upstream (32~6000 Kbps) [32]:
>
Minimum reserved transmit rate upstream (32~6000 Kbps) [32]:
>
Maximum transmit rate upstream (32~6000 Kbps) [1024]:
> Will you set rate thresholds? (y/n) [n]:
3.

Bind the configured line profile to the configured channel profile. The index of the line
template is 10.
huawei(config)#adsl line-template add
10
Start adding
template
be
neglected
> Do you want to name the template (y/n)
[n]:
> Please set the line-profile index (1~128) [1]:
10
> Will you set channel configuration parameters? (y/n)
[n]:y
Issue 01 (2016-04-29)

485

Access Module
>
1
>
Channel1 configuration
parameters:
>
Please set the channel-profile index (1~128) [1]:
10
Add template 10
successfully
4.

The ADSL2+ alarm profile should be configured based on the actual line condition. see
"Configuring an ADSL2+ Alarm Template" for the configuration. The following uses the
alarm profile 1 as an example.
5.

To configure the ADSL2+ traffic profile, run the traffic table ip command.
6.

7.

By default, the GE optical port of the GIU board works in the full duplex mode
with the rate of 1000 Mbit/s.
To change the port working mode and the port rate, run the speed and duplex
command in the GIU mode.
The settings must be the same as the settings of the peer device.
Configure the VLAN.

The ADSL2+ users of MA5600T-1 use the VLAN authentication. In this case,
the MUX VLAN is used to identify the users.
command
limit
huawei(config)#port vlan 1001 to 1031 0/19 0
8.

rx-cttr 6 tx-cttr 6

The MA5600T supports the SHDSL service of multiple encapsulation modes, such as IPoA,
configure the SHDSL service. For other encapsulation modes, see "3.1 Example of the xDSL
Internet Access Service."
1.
Issue 01 (2016-04-29)

486

Access Module
quickadd command.
psd
2.

3.

4.

huawei(config-if-shdsl-0/5)#deactivate all
huawei(config-if-shdsl-0/5)#alarm-config all 1
huawei(config-if-shdsl-0/5)#activate all 10
huawei(config-if-shdsl-0/5)#quit
5.

The SHDSL users of MA5600T-1 use the VLAN authentication. In this case, the MUX
VLAN is used to identify the users.
command
limit
6.
Ports 0-15 in slot 0/5 provide the SHDSL service.

rx-cttr 6 tx-cttr 6

1.

2.

huawei(config)#tcont-profile add profile-id 10 type1 fix 102400
3.
4.
Issue 01 (2016-04-29)
configure it.

487

Access Module

tag-In-Package
5.
Add an ONT.
NOTE

huawei(config-if-gpon-0/18)#ont add 1 0 hwhw-10101010 password-auth huawei
profile-id 2
6.

7.

8.

9.


NOTE


1.
2.

NOTE
static route.
3.
huawei(config)#voip
4.

Issue 01 (2016-04-29)

488

Access Module

text
10.176.6.33
5.

NOTE
6.
Add PSTN users in batches.

88660032
Step 11 Configuring the QinQ private line service.

MA5600T-1 and MA5600T-4 serve two branches of a company to provide the QinQ private
line service.
1.
Create VLAN 50.

2.

3.

4.

values of the virtual port must be the same as those on the modem.
local-Setting
huawei(config)#service-port vlan 50 shdsl 0/5/15 vpi 0 vci 35 rx-cttr 7
tx-cttr 7

l
Users of port 0/2/2 need to be authenticated, and have rights to watch two programs and
to preview one program.
Users of port 0/2/3 do not need to be authenticated.
1.
Configure the xDSL.

In this example, there is no need to configure the xDSL. The default line profile (profile
1002) is used.
2.
Configure the VLAN.
Create a VLAN.
Issue 01 (2016-04-29)

489

Access Module
Configure the VLAN upstream port.

command
limit

NOTE
When the VLAN ID of the tag packet is the same as the VLAN ID of the native VLAN of the
egress, the egress removes the tag of the packet. That is, the tagged packet becomes to the
untagged packet (without VLAN ID) after the tagged packet passes through the egress.

Add ADSL2+ ports 0/0/2 and 0/0/3 to VLAN 100.

tx-cttr 8
tx-cttr 8
3.

Set the upstream port.

huawei(config)#btv
Set the preview parameters.

In this example, configure the preview authority profile with the preview
duration for the program to 150s, the number of preview attempts to 6 each day
and the preview interval to 60s.
interval 60
Configured the program library.


1

huawei(config)#btv
huawei(config-btv)#igmp profile add profile-name profile0
program1 watch
program2 watch
Issue 01 (2016-04-29)

490

Access Module

program3 preview

profile0

1.
Set the upstream port.

The upstream port is already configured in Step 12.3.
2.

The IGMP proxy is already configured in Step 12.3.
3.

The program library is already configured in Step 12.3.
4.

Modify a subtending port.

Add programs for the static subtending port.

huawei(config-btv)#igmp static-join cascade-port 0/19/1 ip 224.1.1.1
vlan 100
vlan 100
vlan 100

huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.

Issue 01 (2016-04-29)

491

Access Module

command
limit


2.
Add the route.

preference 1
preference 1

preference 1
preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.

Set the SysContact.



example, the SNMP version is set as SNMP V2C.
Issue 01 (2016-04-29)

492

Access Module
5.

6.

trap-paramsname abc
trap-paramsname 123
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

the slave node number 1. In this case, you need to set the DIP switch of the node address on
huawei(config)#emu add 0 h801esc 0 0
Step 6 Configure GIU subtending

MA5600T-2 is subtended with MA5600T-3. Therefore subtending should be configured
transparently transmit the VLAN data of MA5600T-3. There are four VLANs configured on
MA5600T-3, with the VLAN ID of 10, 100, 1000 and 1300.
These VLAN are already configured with subtending, and it is unnecessary to configure them
again.
1.

neglected
>
Transmission mode:
>
0: Custom
>
1: All (G992.1~5,T1.413,ETSI)
>
2: Full rate(G992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G992.1/3/5)
>
4: G.HS (G992.1~5)
>
5: ADSL (G992.1~2,ETSI,T1.413)
>
6: ADSL2 & ADSL2+ (G992.3~5)
>
> Trellis mode 1-disable 2-enable (1~2) [2]:
Issue 01 (2016-04-29)

493

Access Module
>
>
>
>
>
>
>
>
>
>
>
2.
Bit swap downstream 1-disable 2-enable (1~2) [2]:

Bit swap upstream 1-disable 2-enable (1~2) [2]:
Please select the form of transmit rate adaptation downstream:
Please select the form of transmit rate adaptation upstream:
Will you set SNR margin parameters? (y/n) [n]:
Will you set DPBO parameters? (y/n)[n]:
Will you set power management parameters? (y/n) [n]:
Will you set tone blackout configuration parameter? (y/n) [n]:
Will you set mode-specific parameters? (y/n) [n]:

The configuration data in the ADSL2+ channel profile is set according to the actual
channel conditions.
neglected
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
>
>
>
>
>
>
3.

Bind the configured line profile and channel profile together to form line template 10.
neglected
>
>
>
4.

You can configure the ADSL2+ alarm profile based on your own needs. For details, see
"Configuring an ADSL2+ Alarm Template." In this example, the default alarm profile
(template 1) is used.
Issue 01 (2016-04-29)

494

Access Module
5.

6.

huawei(config-if-adsl-0/2)#activate all 10
7.

commands in GIU mode.
Configure the VLAN.

the smart VLAN is used to identify the users.
command
limit
8.

huawei(config)#multi-service-port vlan 2020 port 0/2 0-31 vpi 0 vci 35 userencap pppo
rx-cttr 6 tx-cttr 6

1.

quickadd command.
psd
2.

Issue 01 (2016-04-29)

495

Access Module
3.

4.

5.

The SHDSL users of MA5600T-2 use the PPPoE authentication. In this case, the smart
command
limit
6.
Ports 0-15 of in slot 0/5 provide the SHDSL service.


1.
2.

NOTE
static route.
3.
huawei(config)#voip
4.


text
transfer udp mgcip_1 10.30.80.65 mgcport_1 2944 mg-media-ip 10.176.6.33
Issue 01 (2016-04-29)

496

Access Module
5.

NOTE
6.

88660032
Step 10 Configure the stacking multi-ISP wholesale service.

l
ISP1 provides users of ports 0/2/0 to 0/2/10 with the multi-ISP wholesale service.
1.
Create a stacking VLAN.

huawei(config)#vlan attrib 60 to 62 stacking
huawei(config)#stacking outer-ethertype 0x8000
2.

3.

huawei(config)#multi-service-port vlan 60 adsl 0/2 0-10 vpi 0 vci 35
rx-cttr 6 tx-cttr 6
rx-cttr 6 tx-cttr 6
rx-cttr 6 tx-cttr 6
4.
Configure the inner label.

Step 11 Configure the triple play service.

After the configuration, the following results should be achieved: Uses of port 0/2/31 can
watch the programs stored on servers 224.1.1.1 and 224.1.1.2, and can preview the programs
stored on server 224.1.1.3.
1.
Configure the upstream port and the VLAN.

command
limit
2.
Configure the traffic table.

The voice service has the highest priority, and the network access service has the lowest
priority.
Assume that the network access service uses traffic table 6, with the priority of 0. The
following shows how to create the new traffic tables for the voice service and video
service respectively.
Issue 01 (2016-04-29)

497

Access Module

Tag-In-Package
Create traffic descriptor record
successfully
-----------------------------------------------TD Index
:
7
TD Name
: ip-traffictable_7
Priority
:
7
Copy Priority
:
Mapping Index
:
CTAG Mapping Priority:
CTAG Mapping Index
:
CTAG Default Priority:
0
Priority Policy
: tagpri
CIR
: 1024
kbps
CBS
: 34768
bytes
PIR
: 2048
kbps
PBS
: 67536
bytes
Referenced Status
: not
used
-----------------------------------------------huawei(config)#traffic table ip index 8 cir off priority 5 priority-policy
tag-In-Package
Create traffic descriptor record
successfully
-----------------------------------------------TD Index
:
8
TD Name
: ip-traffictable_8
Priority
:
5
Copy Priority
:
Mapping Index
:
CTAG Mapping Priority:
CTAG Mapping Index
:
CTAG Default Priority:
0
Priority Policy
: tagpri
CIR
:
off
CBS
:
off
PIR
:
off
PBS
:
off
Referenced Status
: not
Issue 01 (2016-04-29)

498

Access Module
used
------------------------------------------------
3.
Configure the service port.

huawei(config)#service-port vlan 100 adsl 0/2/31 vpi 0 vci 35
rx-cttr 8 tx-cttr 8
rx-cttr 6 tx-cttr 6
rx-cttr 7 tx-cttr 7
4.
Configure DHCP relay mode for video service.
Enable DHCP mode.

huawei(config)#dhcp mode layer-3 option-60


Enable DHCP Option82.

5.
Configure DHCP relay mode for voice service.


Enable the DHCP option82.

6.

huawei(config)#btv
10.10.10.10
10.10.10.10
10.10.10.10
huawei(config)#btv
huawei(config-btv)#igmp profile profile-name profile0 program-name program1
watch
watch
Issue 01 (2016-04-29)

499

Access Module

preview
huawei(config-btv)#igmp user add port 0/2/31 auth
huawei(config-btv)#igmp user bind-profile port 0/2/31 profile-name profile0

1.

The upstream port is already configured in Step 11.6.
2.

The IGMP proxy is already configured in Step 11.6.
3.

The program library is already configured in Step 11.6
4.

Modify a subtending port.

Add programs for the static subtending port.

vlan 100
vlan 100
vlan 100

huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.



Issue 01 (2016-04-29)

500

Access Module

2.
Add the route.

preference 1
preference 1

preference 1
preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.

Set the SysContact.



5.

6.

trap-paramsname abc
trap-paramsname 123
Issue 01 (2016-04-29)

501

Access Module
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3


1.

neglected
>
Transmission mode:
>
0: Custom
>
1: All (G992.1~5,T1.413,ETSI)
>
2: Full rate(G992.1/3/5,T1.413,ETSI)
>
3: G.DMT (G992.1/3/5)
>
4: G.HS (G992.1~5)
>
5: ADSL (G992.1~2,ETSI,T1.413)
>
6: ADSL2 & ADSL2+ (G992.3~5)
>
> Trellis mode 1-disable 2-enable (1~2) [2]:
> Bit swap downstream 1-disable 2-enable (1~2) [2]:
> Bit swap upstream 1-disable 2-enable (1~2) [2]:
> Please select the form of transmit rate adaptation downstream:
> 1-fixed, 2-adaptAtStartup, 3-adaptAtRuntime (1~3) [2]:
> Please select the form of transmit rate adaptation upstream:
> 1-fixed, 2-adaptAtStartup, 3-adaptAtRuntime (1~3) [2]:
> Will you set SNR margin parameters? (y/n) [n]:
> Will you set DPBO parameters? (y/n)[n]:
> Will you set power management parameters? (y/n) [n]:
> Will you set tone blackout configuration parameter? (y/n) [n]:
> Will you set mode-specific parameters? (y/n) [n]:
2.

The configuration data in the ADSL2+ channel profile is set according to the actual
channel conditions.
Issue 01 (2016-04-29)

502

Access Module
neglected
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
>
>
>
>
>
>
3.

Bind the configured line profile and channel profile together to form line template 10.
neglected
>
>
>
4.

You can configure the ADSL2+ alarm profile based on your own needs. For details, see
"Configuring an ADSL2+ Alarm Template." In this example, the default alarm profile
(template 1) is used.
5.

6.

huawei(config-if-adsl-0/2)#activate all 1
7.

Issue 01 (2016-04-29)

503

Access Module
commands in GIU mode.
Configure the VLAN.

the MUX VLAN is used to identify the users.
8.

All ports of in slot 0/2 provide the ADSL2+ service. To add service ports in batches, run

1.

quickadd command.
huawei(config)#shdsl line-profile quickadd 10 line two-wire rate 2048 2048 psd
2.

3.

4.

5.

The SHDSL users of MA5600T-3 use the PPPoE authentication. In this case, the smart
command
limit
6.
Issue 01 (2016-04-29)

504

Access Module
Ports 0-15 of SHDSL board 0/5 provide the SHDSL service.


1.

2.

huawei(config)#tcont-profile add profile-id 10 type1 fix 102400
3.
4.
configure it.

tag-In-Package
5.
Add an ONT.
NOTE

huawei(config-if-gpon-0/18)#ont add 1 0 hwhw-10101010 password-auth huawei
profile-id 2
6.

7.

8.

9.


NOTE
Issue 01 (2016-04-29)

505

Access Module


1.
2.

NOTE
static route.
3.
huawei(config)#voip
4.


text
transfer udp mgcip_1 10.30.80.65 mgcport_1 2944 mg-media-ip 10.176.6.33
5.

NOTE
6.

88660000

l
Users of port 0/2/2 need to be authenticated, and have rights to watch two programs and
to preview one program.
Users of port 0/2 do not need to be authenticated.
1.
Configure the xDSL.

1002) is used.
2.
Issue 01 (2016-04-29)
Configure the VLAN.

506

Access Module
Create a smart VLAN.
Set the VLAN upstream port.



huawei(config)#traffic table ip index 8 cir off priority 5 prioritypolicy tag-I
n-Packag
Add ADSL2+ port 2 and 3 to VLAN 100.

tx-cttr 8
tx-cttr 8
3.
Configure the multicast service


huawei(config-mvlan100)#igmp uplink-port 0/19/0 100
huawei(config)#btv

In this example, set the preview duration for program 1 to 150s, the number of
preview attempts to 6 each day, and the preview interval to 60s.
interval 60


1

huawei(config)#btv
huawei(config-btv)#igmp
program1 watch
program2 watch
program3 preview
profile add profile-name profile0

profile profile-name profile0 program-name

huawei(config-btv)#igmp user add port 0/2/3 no-auth
huawei(config-btv)#igmp user add port 0/2/2 auth
profile0
Issue 01 (2016-04-29)

507

Access Module


huawei(config)#save
----End

Procedure
huawei>enable
huawei#config

1.




2.
Add the route.

preference 1
preference 1

preference 1
preference 1

preference 1
preference 1
3.
Add the ACL rule.

0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
Issue 01 (2016-04-29)
permit ip source any destination any

deny ip source any destination 10.10.1.2

508

Access Module
destination 10.10.1.2 0.0.0.0

destination 10.10.1.2 0.0.0.0
destination 10.10.1.2 0.0.0.0
4.
Configure SNMP.

Set the SysContact.



5.

6.

trap-paramsname abc
trap-paramsname 123
7.



add 3.3.3.3
activate ip
add 3.3.4.3
activate ip
syslog-1
3.3.3.3
syslog-2
3.3.4.3

Step 6 Configure the VDSL2 service.

The MA5600T supports the VDSL2 Internet service of multiple encapsulation modes, such as
IPoA, PPPoA, IPoE, and PPPoE. This topic uses the PPPoE mode as an example to describe
how to configure the VDSL2 service. For other encapsulation modes, see "3.1 Example of
the xDSL Internet Access Service."
Issue 01 (2016-04-29)

509

Access Module
1.
Configure the VDSL2 line profile.

You can configure the VDSL2 line profile based on your requirements.
huawei(config)#vdsl line-profile add 10
be
neglected
>
Transmission mode:
>
0: Custom
>
1: All (G992.1~5,T1.413,G993.2)
>
2: Full rate(G992.1/3/5,T1.413,G993.2)
>
3: G.DMT (G992.1/3/5,G993.2)
>
4: G.HS (G992.1~5,G993.2)
>
5: ADSL (G.992.1~5,T1.413)
>
6: VDSL (G993.2)
>
> 1-fixed 2-adaptAtStartup (1~2) [2]:
> 1-fixed 2-adaptAtStartup (1~2) [2]:
> Will you set SNR margin parameters? (y/n) [n]:
> Will you set DPBO parameters? (y/n)[n]:
> Will you set UPBO parameters? (y/n)[n]:
> Will you set RFI notch configuration parameter? (y/n) [n]:
> Will you set ADSL tone blackout configuration parameter? (y/n) [n]:
> Will you set VDSL tone blackout configuration parameter? (y/n) [n]:
> Will you set mode-specific parameters? (y/n) [n]:
2.
Configure the VDSL2 channel profile.

You can configure the VDSL2 channel profile based on your requirements.
huawei(config)#vdsl channel-profile add 10
neglected
> Data path mode 1-ATM, 2-PTM, 3-Both (1~3) [3]:1
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
>
Minimum transmit rate downstream (128~100000 Kbps) [128]:512
>
>
>
3.
Issue 01 (2016-04-29)
Configure the VDSL2 line template.

510

Access Module
huawei(config)#vdsl line-template add 10
neglected
>
>
>
4.
Configure the VDSL2 alarm profile.

You can configure the VDSL2 alarm profile based on your requirements. For the
configuration, see "Configuring a VDSL2 Alarm Template". In this example, the default
alarm profile 1 is used.
5.
Configure the VDSL2 traffic profile.

You can configure the VDSL2 traffic profile by running the traffic table ip command
6.
Activate the VDSL2 port.

huawei(config-if-vdsl-0/2)#alarm-config all
huawei(config-if-vdsl-0/2)#activate all template-index 10
7.

In general, the GE optical port uses the default gigabit full-duplex mode.
To change the mode, switch to the GIU config mode. Then run the speed
command to change the port rate, and run the duplex command to change the
port duplex mode.
The settings of the upstream port must be the same as the settings on the peer
device.
Configure the VLAN.

The VDSL2 users of MA5600T-1 use the PPPoE authentication. In this case, the
smart VLAN is used to identify the users.
8.

All ports in slot 0/2 provide the VDSL2 Internet access service. To add service ports in
batches, run the multi-service-port command.

MA5600T-4 and MA5600T-1 serve two branches of a company to provide the QinQ private
line service.
1.
Issue 01 (2016-04-29)
Create VLAN 50.

511

Access Module
2.

3.

4.

values of the service port must be the same as those on the modem.
huawei(config)#service-port vlan 50 shdsl 0/5/15 vpi 0 vci 35
rx-cttr 7 tx-cttr 7

huawei(config)#save
----End
7.7 Verification
Issue 01 (2016-04-29)

512

Access Module
8 FTTx Configuration Summary
FTTx Configuration Summary
The Configuration Guide of the FTTx Solution is a set of configurations of FTTx networks,
including fiber to the home (FTTH), fiber to the building (FTTB), fiber to the curb (FTTC),
fiber to the office (FTTO), and fiber to the mobile base station (FTTM). This manual is
described according to the following:
Structure of Overview, Data Plan, and Configuration

The description structure of each sub-solution is overview, data plan, and configuration. In
this case, you can know about the overview first and then the details, and configure services
in actual scenarios.
1.
Concepts: Describes the basic concepts of solutions, providing necessary contexts for
users.
2.
Data plan: Describes the principle of data plan, providing reference to data configuration.
3.
Configuration: Describes the procedure of configuring a service in a network topology

and provides the method of verifying the service.
Recommended Principle of Data Plan

Data plan is the key factor and difficulty for network planning engineers and commissioning
engineers. This manual provides the recommended principle of data plan for security, device
management, QoS, and specific service in various sub-solutions. In this case, you can plan
and deploy services efficiently.
Takes the FTTB/C sub-solution as an example, the principle of data plan is shown in Figure
8-1.
Figure 8-1 Recommended Principle of Data Plan
Issue 01 (2016-04-29)

513

Access Module
8 FTTx Configuration Summary
Typical Network Topology and Application Scenario

Various sub-solutions have different features. This manual is described based on the typical
network topologies and application scenarios. In this case, you can find out the required
contents according to the actual network topology and application scenario.
Takes the FTTO (large-sized enterprise access) sub-solution as an example, the application
scenarios are shown in Figure 8-2.
Figure 8-2 Typical Application Scenario
typical network
topologies and
application
scenarios
One-button Script Tool

Through a simple-to-use interface, you can instantly transform any configuration page into
command scripts, which greatly reduces the probability of errors compared to manual
operation.
Click to experience: Script Conversion Tool.
Issue 01 (2016-04-29)

514

Access Module
9 FTTH Configuration
FTTH Configuration
About This Chapter

This section describes the configurations of Internet access, voice, broadband TV (BTV), and
VoD services in fiber to the home (FTTH) networking scenarios.
9.1 Basic Concepts
This section describes basic concepts related to the fiber to the home (FTTH) solution from
the user side to the network side on FTTH networking using PON and P2P upstream
transmission, respectively.
9.2 Principle of FTTH Data Plan
9.3 Bridging + Voice ONT Network Scenario (GPON Access)
This topic describes how to configure Internet access service, voice service, BTV service and
VoD service when bridging + voice ONTs are used to build an FTTH network.
9.4 Bridging ONT + HGW Network Scenario (GPON Access)
VoD service when bridging ONTs + HGWs are used to build an FTTH network.
9.5 Gateway ONT Network Scenario (GPON Access)
VoD service when gateway ONT are used to build an FTTH network.
9.6 Configuring Triple Play Service (GPON Access in Simplified Mode)
The GPON service configuration in simplified mode is implemented by creating an end-toend (E2E) service port between an OLT and an ONT. This topic describes how to achieve the
GPON service configuration in simplified mode by configuring the Internet access service,
voice service, and multicast service in the FTTH scenario.
9.7 Configuring FTTH Service (P2P Access)
Users connected to the OLT through an ONT, and are therefore provided with the Internet,
VoIP, and IPTV service through a same port.
Issue 01 (2016-04-29)

515

Access Module
9.1 Basic Concepts

This section describes basic concepts related to the fiber to the home (FTTH) solution from
the user side to the network side on FTTH networking using PON and P2P upstream
transmission, respectively.
FTTH Networking Using PON Upstream Transmission
FTTH Networking Using P2P Upstream Transmission
Issue 01 (2016-04-29)

516

Access Module
User Side
Concept
Description
Home gateway
(HGW or HG)
A gateway device positioned for small office and home office

(SOHO) users. It provides multiple service ports, such as POTS and
LAN, wireless local area network (WLAN), or xDSL ports. The
HGW supports routing and remote management and diagnosis.
VoD
A technology that enables users to order any program in a VoD

program library. During program playing, users can perform
operations, such as pause, fast forward, fast rewind, and program
locating.
Multicast
Is also called broadband TV (BTV), which is similar to traditional

cable TV (CATV) or satellite TV. The user experience in watching a
multicast program is the same as that in watching a traditional TV
program. Unlike the traditional TV, the IPTV system encodes audio
signals and sends them to user terminals through an IP network.
Concept
Description
PON
A network that uses the point-to-multipoint (P2MP) network

architecture. A PON network consists of an optical line terminal
(OLT), an optical distribution network (ODN), and optical network
units (ONUs). It uses optical fibers to transmit data, supports more
users with less optical fibers, and provides high access rates.
ODN
A network that consists of optical fibers and passive optical

components, such as one or more optical dividers. The ODN network
provides highly reliable optical paths to connect ONUs to an OLT.
OLT
An aggregation device located at a central office (CO), which

terminates PON protocols. In this document. OLTs are MA5600T/
MA5603T/MA5608Ts.
Optical network
terminal (ONT)
A user terminal that provides various ports for users. In PON

networking, the PON board of an OLT communicates with an ONT
through the intermediate ODN network. In point-to-point (P2P)
networking, an OLT communicates with an ONT through a P2P
Ethernet optical access board.
Split ratio
A ratio used for dividing a downstream optical signal into sub-signals

in the PON system. A greater split ratio will result in a high optical
power for signal transmission over the same physical distance.
Fiber to the home

(FTTH)
A type of network that provides high bandwidths for home users. In

PON networking, an OLT connects to ONTs through an ODN network
and the ONTs connect to home users. In P2P networking, an OLT
connects to ONTs and the ONTs connect to home users. The OLT
provides voice, Internet access, and IPTV services for home users.
Access Side
Issue 01 (2016-04-29)

517

Access Module
Network Side
Concept
Description
User-facing
provider edge (UPE)
A supplier routing device that connects to the router of a customer

edge (CE), which is an OLT in this document. The U-PE supports
routing and Multiprotocol Label Switching (MPLS) encapsulation. If
a U-PE connects to multiple CEs, the U-PE supports basic bridging
functions. In this case, the U-PE forwards data frames, which reduces
the load of switching provider edges (S-PEs).
Aggregation
provider edge
(PE-AGG)
An aggregation router, which provides aggregation and route

forwarding functions for access devices. Compared with U-PEs, PEAGGs provides fewer ports and higher performance and switching
rates.
NGN or IP
multimedia
subsystem (IMS)
A type of network that centers around softswitches and uses an open

and standardized architecture. It provides voice, video, and data
services.
A type of system that uses Session Initiation Protocol (SIP) signaling
as its call control signaling. It provides voice, data, and multimedia
services.
NOTE
In this document, the NGN or IMS is the softswitch that supports H.248 or SIP.
IPTV head end
A contents preparation platform in the IPTV system. It receives

signals, converts media formats, and manages media materials.
9.2 Principle of FTTH Data Plan

9.2.1 Data Plan Principles for IP Addresses
This section describes how to obtain an IP address in various scenarios.
Data Plan Principles for IP Addresses
Issue 01 (2016-04-29)
Terminal
Type
Service
Recommended Solution
Bridging
+Voice ONT
Internet
access
A PC obtains an IP address through PPPoE dialup. The

ONT transparently transmits the packets.
VoIP
The ONT functions as a DHCP client and obtains an IP

address from the DHCP server, or the NMS issues a static
IP address to the ONT using the configuration file. Voice
signaling and media streams at multiple POTS ports share
one IP address. Media streams are distinguished by port.

518

Access Module
Terminal
Type
Bridging
ONT+HGW
Gateway
ONT
Service
Recommended Solution
IPTV
The set top box (STB) obtains an IP address from the

DHCP server for ordering programs. The ONT
transparently transmits the packets.
Internet
access
The HGW functions as a PPPoE client and obtains an IP

address through PPPoE dialup. At the same time, the HGW
functions as a DHCP server and allocates IP addresses to
PCs through the network cable and wireless fidelity (WiFi) access. The ONT transparently transmits the packets.
VoIP
The HGW functions as a DHCP client and obtains an IP

address from the DHCP server, or the application control
server (ACS) issues a static IP address to the HGW using
TR069. Voice signaling and media streams at multiple
POTS ports share one IP address. Media streams are
distinguished by port. The ONT transparently transmits the
packets.
IPTV
The HGW is configured with a bridging WAN port. The

STB obtains an IP address from the DHCP server. The
HGW transparently transmits packets. The ONT also
Internet
access
The HGW functions as a PPPoE client and obtains an IP

address through PPPoE dialup. The ONT functions as a
DHCP server and allocates IP addresses to PCs through the
network cable.
Wi-Fi
access
l Layer 3 bridge Wi-Fi access service: A mobile

equipment (ME) searches the SSID. After the ME is
authenticated, the DHCP server assigns this ME the IP
address by IPoE.
l Layer 3 route Wi-Fi access service: An ME searches the
SSID. After the ME is authenticated, the DHCP address
pool of an ONT assigns this ME the IP address and then
PPPoE dialup is automatically performed on the ONT.
Issue 01 (2016-04-29)
VoIP

address from the DHCP server, or the NMS issues a static
IP address to the ONT using the configuration file. Voice
signaling and media streams at multiple POTS ports share
one IP address. Media streams are distinguished by port.
IPTV

address from the DHCP server. At the same time, the ONT
functions as a DHCP server and allocates IP addresses to
STBs.

519

Access Module
9.2.2 Principle of QoS Planning

The QoS planning is an E2E planning, and it can be divided into following policies: traffic
classification, marking, and scheduling policy; and traffic monitoring and DBA policy.
Traffic Classification, Marking, and Scheduling Policy

Service
Type
802.1p
Priority
Queue
Scheduling
Method
OLT
Queue ID
(8 Queues)
ONT Queue.ID
When
Eight
Queues
Are
Supported
When Four
Queues
Are
Supported
Management
service
PQ
VoIP service
PQ
IPTV
service
PQ
Wi-Fi access
service
PQ
Internet
access
service
PQ
Note: The service priorities in this table are the recommended values. The service priorities
are arranged according to the operators's actual plan.
Traffic Monitoring and DBA Policy
Issue 01 (2016-04-29)
Items
Manageme
nt service
Internet
access
service
Wi-Fi
access
service
VoIP
service
IPTV
service
GEM port
11 [Remark
1]
14
15
12
13
TCONT
Select a DBA type based on service types. For example, select Type1 for
the management service, Type4 for the Internet access service, and Type2
for the VoIP and IPTV services.
DBA type
Type 3 (DBA profile: assured bandwidth + maximum bandwidth. Users are

allowed to preempt the bandwidth on condition that the users' assured
bandwidth is guaranteed. However, the total bandwidth cannot exceed the
maximum bandwidth.)

520

Access Module
Internet
access
service
Items
Manageme
nt service
Wi-Fi
access
service
VoIP
service
IPTV
service
DBA
bandwidth
planning
Configure the DBA bandwidth according to the user's bandwidth package.

The assured bandwidth is the maximum bandwidth required by
management packets, VoIP, and IPTV upstream packets. The maximum
bandwidth is larger than or equal to the maximum bandwidth that users
apply.
Rate limit on
OLT
downstream
No rate limit
Configure
rate limit by
a traffic
profile as
required.
[Remark 2]
Rate limit on
ONU
upstream
port
No rate restriction
Rate limit on
ONU
downstream
port
No rate restriction
Configure
rate limit by
a traffic
profile as
required.
[Remark 2]
No rate limit
No rate limit
Remark 1: GEM port value depends on the planning of the service provider, but in principle,
use different GEM ports for different services.
Remark 2: Table 9-1 shows the reference service bandwidth of each service for each user.
Table 9-1 Reference service bandwidth of each service for each user
Issue 01 (2016-04-29)
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
Bandwidth Description
Internet
access
service/
WiFi
access
service
Determi
ned
based on
the
service
tariff
package.
Determined based
on the service tariff
package.
Available bandwidth of Internet access

service or WiFi access service =
Committed bandwidth of the service tariff
package - VoIP bandwidth - IPTV
bandwidth
VoIP
service
200
kbit/s
200 kbit/s
The upstream bandwidth and the

downstream bandwidth of VoIP service are
symmetrical. The actual bandwidth is
related to the coding format. This
bandwidth is calculated for two POTS ports.

521

Access Module
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
IPTV
service
(standar
d
definitio
n
program
)
2.5 Mbit/s per

channel
IPTV
service
(high
definitio
n
program
)
9.7 Mbit/s per

channel
IPTV service mainly occupies the

downstream bandwidth. The actual
bandwidth depends on the coding format,
the picture in picture information, 10%
bandwidth burst traffic, and the number of
programs that can be concurrently watched
by one user (in the case of multiple STBs).
The upstream bandwidth is mainly used for
transmitting IGMP packets, which requires
little bandwidth. Therefore, the bandwidth
occupied by IGMP packets can be
neglected.
Note:
l
The rate restriction on the BRAS or SR is recommended. OLTs and ONTs do not restrict
the rate for service streams.
If BRAS does not support rate restriction, OLTs can restrict the rate for service streams
through the traffic profile.
Different service packets on the ONT are distinguished by different VLAN IDs. The
service packets are mapped to GEM ports based on VLAN IDs so that different service
packets are transmitted to different GEM ports. Each GEM port (each service)
corresponds to a T-CONT or all GEM ports share a T-CONT.
The sum of the assured bandwidth of all ONTs connected to a PON port and the fixed
bandwidth of OMCI management channel is less than the GPON upstream bandwidth.
Some bandwidth must be reserved for the future service expansion.
9.2.3 Principles of Internet and Wi-Fi Access Services Data

Planning
This topic describes the principles of data planning for Internet and Wi-Fi access services and
will focus on the VLAN planning and VLAN translation policy planning in different network
scenarios.
Issue 01 (2016-04-29)

522

Access Module
VLAN and VLAN Translation Policy

Table 9-2 Planning of VLANs and VLAN translation policies for Internet access service
Application
Scenario
VLAN Plan
VLAN Translation Policy
Bridging+Voice
ONT
Double-tagged VLAN
ONT: ONTs configure the VLAN and

add the same C-VLAN tag to packets.
All ONTs are in the same C-VLAN.
OLT: The OLT performs VLAN
translation: C<->S+C'. The C'-VLAN
of every ONT differs from each other.
Bridging ONT +
HGW
Double-tagged VLAN
ONT: The upstream packets sent from

the HGW carry user-VLANs and the
ONT transparently transmits them.
OLT: The OLT translates the U-VLAN
to S-VLAN+C-VLAN.
Gateway ONT
Double-tagged VLAN

Table 9-3 Planning of VLANs and VLAN translation policies for Wi-Fi access service
Application
Scenario
VLAN Plan
Gateway ONT
Single-tagged VLAN

translation: C<->S.
Note:
l
User VLAN: VLAN carried by packets going upstream from user-side devices (such as a
home gateway), U-VLAN for short.
C-VLAN: VLAN added based on the ONT/ONU port. For details, see the description of
the Double-tagged VLAN S+C.
Double-tagged VLAN S+C: C indicates the inner VLAN (C-VLAN) and S indicates the
outer VLAN (S-VLAN).
Double-tagged VLAN S+C': C' indicates the translated inner VLAN (C'-VLAN) and S
indicates the outer VLAN (S-VLAN).
Issue 01 (2016-04-29)

523

Access Module
Single-tagged S-VLAN: Single-tagged VLAN marked or translated by the OLT. It is

generally used in a single-tagged VLAN translation scenario.
C<->S+C': Bidirectional VLAN translation: translates the C-VLAN and then adds an SVLAN.
C<->S+C: Bidirectional VLAN translation: maintains the C-VLAN and adds an SVLAN.
NOTE
l To ensure traceability of users and finer-grained QoS control and management of users and services, plan
per user per service per VLAN (PUPSPV) for the Internet access service. Considering OLT capacity and
VLAN scalability, use dual VLANs (S-VLAN+C-VLAN) on the OLT to differentiate users for the
Internet access service.
l The outer VLAN (S-VLAN), which identifies services and physical location, can be allocated based on
the OLT, PON board, or PON port. The inner VLAN (C-VLAN) identifies users. C-VLANs must be
unique in one S-VLAN.
l It is recommended that you use stacking VLANs as S-VLANs so that security features, such as PPPoE+/
option82, and anti-MAC attacks and anti-MAC spoofing, can be easily deployed.
l The 802.1q in 802.1q (QinQ) VLAN is used in the enterprise private line scenario, such as transparent
LAN service (TLS), in which the device transparently transmits packets. It is not recommended that you
use QinQ VLANs as S-VLANs for the triple play services of residential users.
9.2.4 Principle of Voice Service Data Plan

The voice service plan mainly includes the plan of the VLAN and VLAN translation policy in
different network scenarios, and the plan of voice protocol.

Application
Scenario
VLAN Plan
Bridging+voice
ONT
Single-tagged VLAN
(recommended)
ONT: VLANs are configured for the

ONTs on the same network in a unified
manner, and the ONTs have the same CVLAN. The ONT adds a C-VLAN tag
to packets.
OLT: transparently transmits the
VLAN.
Double-tagged VLAN

to packets.
OLT: adds an S-VLAN tag to the
packets (C-VLAN <-> S-VLAN+CVLAN).
Issue 01 (2016-04-29)

524

Access Module
Application
Scenario
VLAN Plan
Double-tagged VLAN

manner, and the ONTs have different CVLANs. The ONT adds a C-VLAN tag
to packets.
Bridging ONT
+HGW
Single-tagged VLAN
(recommended)
ONT: Packets that are sent upstream by

the HGW are tagged with a user VLAN.
The ONT transparently transmits the
user VLAN.
OLT: translates the VLAN tag (user
VLAN <-> S-VLAN).
Single-tagged VLAN

The ONT translates the user VLAN
(user VLAN <-> S-VLAN). All the
ONTs connected to the same OLT have
the same voice service S-VLAN; ONTs
connected to different OLTs may have
different voice service S-VLANs.
VLAN.
Double-tagged VLAN

The ONT transparently transmits the
user VLAN.
OLT: translates the VLAN tag (user
VLAN <-> S-VLAN+C-VLAN).
Double-tagged VLAN

The ONT translates the user VLAN
(user VLAN <-> C-VLAN). The CVLAN is an inner VLAN tag that
differentiates users.
Issue 01 (2016-04-29)

525

Access Module
Application
Scenario
VLAN Plan
Gateway ONT
Single-tagged VLAN
(recommended)

to packets.
OLT: translates the VLAN tag (CVLAN <-> S-VLAN).
Single-tagged VLAN

to packets.
VLAN.
Double-tagged VLAN

to packets.
OLT: translates the VLAN tag (CVLAN <-> S-VLAN+C-VLAN').
Note:
l

Issue 01 (2016-04-29)

526

Access Module
NOTE
l The voice service is a closed service operated by carriers. The single-tagged S-VLAN is the mainstream
application and is recommended.
l When the planned VLAN is single-tagged VLAN, the S-VLANs can be allocated based on the OLT
device, PON board or PON port. The S-VLANs identify services and physical locations. It is
recommended that you set different voice VLANs for the OLTs connected to one voice SR to avoid an
excessively large broadcast domain of the SR and convergence switch.
l When the planned VLAN is S-VLAN+C-VLAN (that is, double-tagged VLAN), the outer S-VLANs can
be allocated based on the OLT device, PON board or PON port. The S-+VLANs identify services and
physical locations. It is recommended to allocate S-VLANs based on PON board or PON port. The inner
C-VLAN is used to identify services (a fixed value) or users.
Voice Data Plan Based on H.248 or SIP

Description
Item
MG
interface/SI
P interface
data
NOTE
must be
consistent
with the
data on the
MGC/IMS
core
network
devices.
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLANs
Upstream VLANs of the voice service
Media and
signaling
upstream port
Upstream ports of the voice service
Media IP
addresses and
signaling IP
addresses
Supports separating media from signaling.
Default gateway
IP address.
The next hop IP address from an

ONU/HGW to an MGC/IMS.
MG interface/SIP interface ID
Signaling port ID
Choose the transmission mode according to

the requirement of the MGC/IMS side.
IP address of active MGC (H.

248)/IP address of active IMS
device (SIP)
If the dual homing is not configured, only

one MGC parameter needs to be
configured. If the dual homing is
configured, the IP address and port ID of
the standby MGC need to be configured.
Port ID of active MGC

(H248)/port ID of active IMS
device (SIP)
Issue 01 (2016-04-29)
Coding
Choose the coding method according to the

requirement on the MGC/IMS side.
Generally, the text coding method is
adopted.
Transmission mode
Choose the transmission mode according to

the requirement on the MGC/IMS side.
Generally, the UDP transmission mode is
adopted.
Home domain (SIP)

527

Access Module
Item
Voice user
configuratio
n data
Description
Profile index
The version of H248 protocol

that MG starts to negotiate
V1, V2 or V3 (by default). The interface

may fail to be registered because some
softswitches do not support V3.
Phone number
For H248 protocol: The phone numbers

allocated by the MGC need to be
determined, and the paging numbers for
users' emergency standalone need to be
planned if the emergency standalone
function is provided.
For SIP protocol: The phone number that
the IMS core network device allocates to
the user must be configured.
Terminal ID (H248)
If the TID template with which the POTS

user is bound does not support terminal
layering, this parameter needs to be
configured.
User priority
According to the service requirements, user

priorities must be specified. The user
priorities include the following:
l cat1: government1 (category 1
government users)
government users)
l cat3: common (common users)
User type

type needs to be specified. The user type
includes the following:
l DEL: direct exchange lines (default)
l ECPBX: earth calling PBX
l LCPBX: loop calling PBX
l PayPhone: pay phone
Common
parameter
Issue 01 (2016-04-29)
system parameter
The system parameters including the

overseas version flag and message waiting
indication (MWI) mode need to be
configured according to the local standard
to ensure that the response of the user
terminal complies with the local standard.

528

Access Module
Item
Description
Overseas parameters
The attributes such as the upper and lower

thresholds of the flash-hooking duration
need to be configured according to the local
standards to ensure that the response of the
user terminal complies with the local
standards.
POTS port attributes
If the POTS port needs to support the

polarity reversal accounting, the POTS port
needs to be configured to support the
polarity reversal pulse. Other attributes
need not be modified if there is no special
requirement.
When the attributes of ring current are

changed, ring volume is changed
accordingly. Generally, no adjustment is
required for the ringing tone volume. You
need to modify the parameters of the
ringing current attributes according to the
local standard only when the default
ringing current attributes do not comply
with the local standard.
9.2.5 Principle of IPTV Service Data Plan

The IPTV service data plan mainly include the plan of VLAN and VLAN translation policy in
different network scenario, and the plan of IPTV service.
IPTV services include multicast service and video on demand (VoD) service. These two
services are relevant but independent in VLAN planning.
VLAN and VLAN Translation Policy.

Applicatio
n Scenario
Service
Type
VLAN Plan
Bridging
+Voice
ONT
Multicast
service
Singletagged
VLAN
ONTs replicate multicast packets based on

user ports and multicast VLANs (M-VLANs)
are removed downstream.
The OLT replicates multicast packets based
on PON ports with M-VLAN unchanged.
VoD
Issue 01 (2016-04-29)
Singletagged
VLAN
ONTs add S-VLAN tags to iTV service

packets.
The OLT transparently transmits packets with
S-VLANs.

529

Access Module
Applicatio
n Scenario
Bridging
ONT +
HGW
Service
Type
Multicast
service
VLAN Plan
Doubletagged
VLAN
All ONTs add the same C-VLAN tag to

packets.
Singletagged
VLAN
ONTs transparently transmit upstream packets

with M-VLANs sent from HGW. Multicast
packets are replicated downstream with MVLAN unchanged.
The OLT implements VLAN translation: C>S+C'.

VoD
Gateway
ONT
Multicast
service
Singletagged
VLAN
ONTs translate the upstream VLANs sent

from HGW to M-VLANs.
Singletagged
VLAN
ONTs transparently transmit the upstream UVLANs sent from HGW.
Doubletagged
VLAN
ONTs transparently transmit the upstream UVLANs sent from HGW.
Singletagged
VLAN
ONTs replicate packets based on user ports

and M-VLANs are removed in downstream
direction.

The OLT implements VLAN translation: U>S.
The OLT implements VLAN translation: U>S+C.

VoD
Singletagged
VLAN
ONTs add C-VLAN tags to packets. Untagged

VLANs are translated to C-VLANs.
The OLT implements VLAN translation: C ->
S.
Note:
l
Issue 01 (2016-04-29)

530

Access Module

NOTE
l IPTV service is a closed service self-operated by carriers, and single-tagged S-VLAN is recommended.
l The same S-VLAN or different S-VLANs can be used as the M-VLAN and VoD VLAN. It is
recommended that you use different S-VLANs as M-VLAN and VoD VLAN so that the upper-level
device easily differentiates between the BTV service and VoD service.
l S-VLANs of VoD service can identify services and physical locations based on an entire network or an
OLT. It is recommended that you set different VoIP VLANs for the OLTs connected to one VoIP SR to
avoid an excessively large broadcast domain of the VoIP SR and convergence switch.
9.2.6 Principle of Security Data Plan

The security plan involves system security plan, user security plan, and service security plan.
Security policy ensures service security from different aspects.
NOTE
The device provides complete security measures, but not all security measures need to be deployed. Only the
security measures that meet the following requirements need to be deployed:
l The security measures can be used on the live network.
l The security measures are easy to deploy.
l The security measures are effective.
System Security
Security
Vulnerability
Solution
Description and Usage

Suggestion
DoS attack
Enable the anti-DoS-attack

function for OLT.
After the anti-DoS-attack function is

enabled, control packets are
monitored and those exceeding the
number threshold are discarded.
Use this solution for new site
deployment.
IP attack
Enable the anti-IP-attack

function for OLT.
After the anti-IP-attack function is

enabled, a device discards the IP
packets received from the user side
whose destination IP address is the
IP address of the device, and
therefore the system is protected.
deployment.
Issue 01 (2016-04-29)

531

Access Module
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing
Enable the anti-MACduplicate function for OLT.
After anti-MAC-duplicate is
enabled, the system records the first
MAC address learnt from the port
and binds the MAC address to the
port and VLAN. If receiving packets
sent from the host that has the same
MAC address with the port, the
system discards the packets directly.
In this case, it can prevent users from
forging MAC addresses to perform
malicious attacks.
deployment.
MAC attack
Enable the anti-MAC

spoofing function for OLT.
After anti-MAC spoofing is enabled,

the system can prevent users from
malicious attacks.
deployment.
IP spoofing
Enable the anti-IP spoofing

function for OLT.
After anti-IP spoofing is enabled, the

system can prevent users from
forging IP addresses to perform
malicious attacks.
deployment.
Issue 01 (2016-04-29)

532

Access Module
Service Security
Security
Vulnerability
Solution

Suggestion
Unauthorized
broadband access of
small enterprises
(IPoE)
DHCP option 82 is enabled

on OLT, and the BRAS
implements user
authentication based on the
RAIO information.
In the DHCP option 82 mode, user's

physical location is added to the
option 82 field carried in the DHCP
request packet initiated by a user.
The physical location, used for user
authentication on the upper-layer
authentication server, can help
implement the following functions:
l The DHCP relay forwards DHCP
response packets to devices with
specified CID and RID.
l Prevents DHCP address
exhaustion.
l Achieves static allocation of
DHCP addresses.
l Implements anti-IP spoofing.
l Implements anti-user ID
spoofing.
l Implements anti-MAC spoofing.
Use this solution for the DHCP
Broadband access of
residential users
(PPPoE), user
account theft/
borrowing
PPPoE+ (PITP) is enabled

on OLT, and the BRAS
implements user
authentication based on
binding of the RAIO
information to the user
account.
The BRAS responds to request

packets of users with specified CID
and RID. In this way, the following
functions are implemented:
l Prevents IP address exhaustion.
spoofing.
Use this solution for the PPPoE
9.3 Bridging + Voice ONT Network Scenario (GPON

Access)
VoD service when bridging + voice ONTs are used to build an FTTH network.
Issue 01 (2016-04-29)

533

Access Module
9.3.1 Service Requirements and Application Scenario

Optical fibers are connected to user homes and triple play services are required. The following
provides detailed service requirements:
l
Internet access of multiple PCs in a home is supported.
Access of multiple telephones in a home is supported.
IPTV programs can be previewed and watched using STBs.
Service extension is supported and different services do not affect each other.
Proper service security is ensured.
Internet access services are protected against unauthorized access, user account
theft or borrowing, MAC/IP spoofing, and malicious attacks.
Voice and IPTV services are protected against MAC/IP spoofing, malicious attack,
and traffic flooding attacks.
Service faults are easy to locate and services are easy to maintain.
As shown in Figure 9-1, the ONT integrating an integrated access device (IAD) provides
Internet, VoIP, and IPTV services to users.
The bridging+voice ONT provides Layer 2 data (Internet and IPTV services) and VoIP
services. This scenario provides transparent transmission channels and requires simple service
configuration, so this scenario applies to Layer 2 networking.
l
For Internet services, a PC directly performs dial-up. Then, the upper-layer broadband
remote access server (BRAS) device authenticates and accesses the PC. The PC can also
access the Internet using the Dynamic Host Configuration Protocol (DHCP) or static IP
address.
For VoIP services, the ONT with a bulit-in voice module encapsulates voice service
packets, and the OLT transmits them to the upstream next generation network (NGN) or
IP multimedia subsystem (IMS).
For IPTV services, the set top box (STB) obtains an IP address from the DHCP server
for ordering programs. The ONT transparently transmits the packets.
Issue 01 (2016-04-29)

534

Access Module
Figure 9-1 Bridging+Voice ONT
9.3.2 Configuration Process

Figure 9-2 shows the configuration roadmap in fiber to the home (FTTH) networking using a
bridging+voice optical network terminal (ONT).
Figure 9-2 Configuration roadmap in FTTH networking using a bridging+voice ONT
Issue 01 (2016-04-29)

535

Access Module
The following table describes the configuration steps.

Item
Step
Description
Optical
line
termina
l (OLT)
9.3.3 Adding an ONT to an OLT
Services can be configured for an ONT

only after the ONT is successfully added
to an OLT.
OLT
9.3.4 Configuring the Internet

Access Service
None
OLT
Configure the
VoIP service.
NOTE
ONT
U2000
9.3.5
Configuring
the H.248based Voice
Service (on a
Web Page or
the U2000)
9.3.6
Configuring
Service
(Through the
CLI)
9.3.7
Configuring
the SIP-based
Voice Service
(on a Web
Page or the
U2000)
l The H.248 and Session Initiation Protocol

(SIP) protocols are mutually exclusive for
the VoIP service. Either of them is
configured at a time.
l The voice service can be configured
through command line interface (CLI) on
an OLT, web page, or U2000. Select a
configuration mode based on site
requirements.
l OLT CLI: This mode can be used for
site deployment or the U2000 has not
been deployed.
l Web page: This mode can be used to
configure voice parameters after the
service channel has been configured
through the OLT CLI. It can be used for
site deployment.
l U2000: This mode can be used to
service provisioning in batches.
9.3.8
Configuring
the SIP-based
Voice Service
(Through the
CLI)
OLT
Configure the
IPTV service.
9.3.9
Configuring
the BTV
Service
IPTV services include the BTV and VoD

services that are different in configuration
procedures and need to be configured
separately.
9.3.10
Configuring
the VoD
Service
Issue 01 (2016-04-29)

536

Access Module
Item
Step
Description
OLT
9.3.11 Configuring Link

Aggregation, Congestion
Control, and Security Policies
The global configuration of link

aggregation and queue scheduling based
on priorities ensures service reliability. The
global configuration of security policies
ensures service security.
OLT
9.3.12 Verifying Services
The OLT provides remote verification

methods including ONT PPPoE/DHCP
dialup emulation and call emulation for
configuration and commissioning
engineers to verify services remotely after
service configuration, avoiding a second
on-site operation.

Services can be configured for an ONT only after the ONT is successfully added to an OLT.
Data Plan
Item
Data
DBA profile
Profile name: ftth_dba_mngt

l Profile type: Type1
l Fixed bandwidth: 1 Mbit/s
Profile name: ftth_dba_hsi
l Maximum bandwidth: 32 Mbit/s
Profile name: ftth_dba_voip
l Assured bandwidth: 1 Mbit/s
Profile name: ftth_dba_iptv
Issue 01 (2016-04-29)

537

Access Module
Item
Data
ONT line profile
Profile name: ftth

T-CONT ID for management services: 4
T-CONT ID for voice services: 5
T-CONT ID for video services: 6
T-CONT ID for Internet access services: 7
GEM port ID for management services: 11
GEM port ID for voice services: 12
GEM port ID for video services: 13
GEM port ID for Internet access services: 14
ONT service
profile
Profile name: ftth
Network
topology data
PON port: 0/1/0
ONT port capability set: adaptive
ONT IDs: 1 and 2
Procedure
Step 1 Configure GPON ONT profiles.
GPON ONT profiles include the DBA profile, line profile, service profile, and alarm profile.
l
DBA profile: A DBA profile describes GPON traffic parameters. A T-CONT is bound to
a DBA profile for dynamic bandwidth allocation, improving upstream bandwidth
utilization.
Line profile: A line profile describes the binding between the T-CONT and the DBA
profile, the QoS mode of the traffic stream, and the mapping between the GEM port and
the ONT-side service.
Service profile: A service profile provides the service configuration channel for the ONT
that is managed by using optical network terminal management and control interface
(OMCI).
Alarm profile: An alarm profile contains a series of alarm thresholds to measure and
monitor the performance of activated ONT lines. When a statistical value reaches the
threshold, the host is notified and an alarm is reported to the log host and the NMS.
1.
Configure a DBA profile.

Run the display dba-profile command to query existing DBA profiles in the system. If
the existing DBA profiles in the system do not meet the requirements, run the dbaprofile add command to add a DBA profile.
huawei(config)#dba-profile
add
add
add
add
profile-name
profile-name
profile-name
profile-name
ftth_dba_mngt type1 fix 1024

ftth_dba_voip type2 assure 1024
ftth_dba_iptv type2 assure 1024
ftth_dba_hsi type4 max 32768
NOTE
The DBA implementation is based on an ONT. Therefore, select a DBA profile of the proper bandwidth
type and configure proper bandwidth according to the service types and total user count of the ONT.
Note that the sum of the fixed bandwidth and the assured bandwidth must not be greater than the total
bandwidth of the PON port.
Issue 01 (2016-04-29)

538

Access Module
2.
Configure an ONT line profile.

Create a GPON ONT line profile, named ftth, and bind it to the DBA profile ftth_dba.
huawei(config)#ont-lineprofile gpon profile-name ftth
huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name
ftth_dba_mngt
ftth_dba_voip
ftth_dba_iptv
ftth_dba_hsi
Create different GEM ports according to different service types, in which
GEM port 11 is used to carry management services.
GEM port 12 is used to carry voice services.
GEM port 13 is used to carry video services.
GEM port 14 is used to carry Internet access services.
huawei(config-gpon-lineprofile-1)#gem
add
add
add
add
11
12
13
14
eth
eth
eth
eth
tcont
tcont
tcont
tcont
4
5
6
7
NOTE
1. To change the default QoS mode, run the qos-mode command to set the QoS mode to gem-car or
flow-car, and run the gem add command to set the index of the traffic profile bound to the GEM
port.
2. When the QoS mode is priority-queue (PQ), the default queue priority is 0; when the QoS mode is
flow-car or gem-car, traffic profile 6 is bound to the GEM port by default (no rate limitation).
After the configurations are complete, run the commit command to apply the parameters
settings.
3.
Configure an ONT service profile.

Create a GPON ONT service profile, named ftth. Configure the capability set of the
ETH port and POTS port to adaptive. Then the system automatically adapts to the ONT
according to the actual capability of the online ONT.
huawei(config)#ont-srvprofile gpon profile-name ftth
huawei(config-gpon-srvprofile-1)#ont-port eth adaptive pots adaptive
setting.
4.
(Optional) Add an alarm profile.
The default GPON alarm profile 1 is used. The alarm thresholds of the default
alarm profile are 0, which indicates that no alarm is generated.
In this example, the default alarm profile is used, and therefore the configuration of
the alarm profile is not required.
Run the gpon alarm-profile add command to configure a GPON alarm profile,
which is used for monitoring the performance of an activated ONT line.
Step 2 Add an ONT.

Connect two ONTs to GPON port 0/1/0. Set the ONT IDs to 1 and 2, SNs to
3230313126595540 and 6877687714852901, passwords to 0100000001 and 0100000002,
discovery mode for password authentication to once-on, and management mode to OMCI.
Bind the two ONTs to ONT line profile ftth and ONT service profile ftth.
Issue 01 (2016-04-29)

539

Access Module
There are two methods of adding an ONT: add an ONT offline and confirm an automatically
discovered ONT.
l
Add ONTs offline.

If the password of an ONT is known, run the ont add command to add an ONT offline.
huawei(config-if-gpon-0/1)#ont add 0 1 password-auth 0100000001 once-on noaging omci ont-lineprofile-name
ftth ont-srvprofile-name ftth
Confirm automatically discovered ONTs.

If the password or SN of an ONT is unknown, run the port portid ont-auto-find
command in GPON mode to enable the ONT auto-discovery function of the GPON port.
Then, run the ont confirm command to confirm the ONT.
huawei(config-if-gpon-0/1)#port 0 ont-auto-find enable
huawei(config-if-gpon-0/1)#display ont autofind 0
//After this command is executed, the information about all ONTs connected
to the GPON port through optical splitters is displayed.
huawei(config-if-gpon-0/1)#ont confirm 0 ontid 1 sn-auth 3230313126595540
omci ont-lineprofile-name
NOTE
If multiple ONTs of the same type bound to the same line profile or service profile are connected to the
same port, you can bulk add ONTs by bulk confirming automatically discovered ONTs to make
configuration easier and more efficient. To do so, the preceding command can be modified as follows:
huawei(config-if-gpon-0/1)#ont confirm 0 all sn-auth omci ont-lineprofilename ftth
ont-srvprofile-name ftth
(Optional) Bind the alarm profile to the ONT.

The default profile 1 is used in this example.
Step 3 Check ONT status.

After an ONT is added, run the display ont info command to query the current status of the
ONT. Ensure that Config flag of the ONT is active, Run State is online, Config state is
normal, and Match state is match.
huawei(config-if-gpon-0/1)#display ont info 0 1
--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
//Indicates that the ONT is
activated.
Run state
: online
//Indicates that the ONT goes online
successfully.
Config state
: normal
//Indicates that the configuration state of
the ONT is normal.
Match state
: match
//Indicates that the capability profile bound
to the ONT is consistent with the actual capability of the ONT.
...//The rest of the response information is omitted.
When Config state is failed, Run state is offline, or Match state is mismatch:
Issue 01 (2016-04-29)

540

Access Module
If Control flag is deactive, run the ont active command in GPON mode to activate the
ONU.
If Run state is offline, a physical line may be broken or the optical module may be
damaged. Check the line and the optical module.
If Config state is failed, the configured ONU capability exceeds the actual ONU
capability. In this case, run the display ont failed-configuration command in the
diagnose mode to check the failed configuration item and the failure cause. Then, rectify
the fault accordingly.
If the ONU does not match, that is, Match state is mismatch, the port types and number
of ports undermatch the actual port types and number of ports supported by the ONU. In
this case, run the display ont capability command to query the actual capability of the
ONU, and then select one of the following modes to modify the ONU configuration:
Create a proper ONU profile according to the actual capability of the ONU, and
then run the ont modify command to modify the configuration data of the ONU.
Modify the ONU profile according to the actual capability of the ONU and save the
modification. Then, the ONU automatically recovers the configuration successfully.
----End
9.3.4 Configuring the Internet Access Service

The OLT is connected to the remote ONT through a GPON port to provide users with highspeed Internet access services.
Prerequisites
l
The OLT is connected to the BRAS.
Related configurations are performed on the BRAS according to the authentication and
accounting requirements for dialup users. For details about the configuration, see the
configuration guide.
The ONT has been added to the OLT. For details, see 9.3.3 Adding an ONT to an OLT.
The VLAN of the LAN switch port connected to the OLT is consistent with the upstream
VLAN of the OLT.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID for Internet access service: 14
Network topology data

PON port: 0/1/0
ONT IDs: 1 and 2
ID of the port on the ONT that is connected to the PC: 1
Issue 01 (2016-04-29)

541

Access Module
Item
Data
VLAN Plan
Double-tagged VLAN:
l S-VLAN ID: 100

l S-VLAN type: smart
l S-VLAN attribute: stacking
l CVLAN ID: 1001
l C'-VLAN ID: 1010-1011
VLAN Translation Policy:
l ONT: ONTs configure the VLAN and add the same CVLAN tag to packets. All ONTs are in the same CVLAN.
l OLT: The OLT performs VLAN translation: C<->S
+C'. The C'-VLAN of every ONT differs from each
other.
Procedure
l
Configure the OLT.

a.

Run the display traffic table ip command to query existing traffic profiles in the
system. If the traffic profiles existing in the system do not meet the requirements,
you need to run the traffic table ip command to add a traffic profile.
Set the profile ID to ftth_hsi, the CIR to 4 Mbit/s, and the priority to 0. In addition,
configure the scheduling mode so that packets are scheduled according to their
priorities.
huawei(config)#traffic table ip name ftth_hsi cir 4096 priority 0
priority-policy local-setting
b.
Configure the mapping between a GEM port and a VLAN.

The service flow of C-VLAN 1001 is mapped to GEM port 14 in the ONT line
profile.
c.
Configure the VLAN of the Ethernet port on the ONT.

If the ONT is connected to the PC through Ethernet port 1, add Ethernet port 1 to
VLAN 1001 in the ONT service profile.
huawei(config-gpon-srvprofile-1)#port vlan eth 1 1001
d.
Configure the native VLAN of the ONT port.

Set the native VLAN ID of Ethernet port 1 to 1001.
Issue 01 (2016-04-29)

542

Access Module

e.
Create an Internet access service VLAN and add an upstream port to it.
f.
Create service flows.

Set the service VLAN to 100, GEM port ID to 14, and user VLAN to 1001. Use
traffic profile ftth_hsi.
huawei(config)#service-port vlan 100 gpon 0/1/0 ont 1 gemport 14 multiservice
user-vlan 1001 tag-transform translate-and-add inner-vlan 1010 inbound
traffic-table name
ftth_hsi outbound traffic-table name ftth_hsi
traffic-table name
g.
Save the data.

huawei(config)#save
The ONT does not need to be configured.
----End
9.3.5 Configuring the H.248-based Voice Service (on a Web Page

or the U2000)
The OLT is connected to the remote ONT through a GPON port to provide users with the IPbased high-quality and low-cost VoIP service.
Prerequisites
l
The interface data and POTS user configuration data corresponding to the MG interface
have been configured on the MGC.
The OLT has been connected to the MGC. The OLT can ping the IP address of the MGC
server successfully.
Different voice services require different ONT software versions. Before the
configuration, ensure that the current ONT software version supports H.248. For details,
see relevant ONT manuals.
The Web page and NMS window for configuring ONT varies with ONT versions, but
the parameter configuration is the same. For details, see relevant ONT manuals.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
Issue 01 (2016-04-29)

543

Access Module
Item
Data
VLAN plan
Single VLAN tag:
l VLAN ID: 300

l VLAN type: smart
l VLAN attribute: common
l CVLAN=SVLAN
VLAN translation policy:
l ONT: VLANs are configured for the ONTs on the
same network in a unified manner, and the ONTs have
the same C-VLAN. The ONT adds a C-VLAN tag to
packets.
l OLT: transparently transmits the VLAN.
Voice parameter
IP address of the MGC server: 200.200.200.200/24

Port ID of the MGC server: 2944
MG Domain: 0100000001 or 0100000002
Procedure
l
Configure the OLT.

a.

Run the display traffic table ip command to query the existing traffic profiles in
the system. If the existing traffic profiles in the system do not meet the
requirements, run the traffic table ip command to add a traffic profile.
Set the profile name to ftth_voip and do not limit the upstream and downstream
rates. Set the priority to 5 and packets are scheduled according to the priority
carried.
huawei(config)#traffic table ip name ftth_voip cir off priority 5
priority-policy
local-setting
b.
Configure the mapping relationship between a GEM port and a VLAN.

The service flow of user VLAN 300 is mapped to GEM port 12 in the ONT line
profile.
c.
Create a service VLAN and add an upstream port to it.

d.

Set the service VLAN to 300, GEM port ID to 12, and user VLAN to 300, and use
traffic profile ftth_voip.
Issue 01 (2016-04-29)

544

Access Module

service
user-vlan 300 inbound traffic-table
table name ftth_voip
service
e.
gpon 0/1/0 ont 1 gemport 12 multiname ftth_voip outbound trafficgpon 0/1/0 ont 2 gemport 12 multiname ftth_voip outbound traffic-
Enable the ARP proxy function.

Voice media streams for different users of the same SVLAN fail to interchange
because the service ports of the smart VLAN are isolated from each other.
Therefore, the ARP proxy function needs to be enabled on the OLT.
huawei(config)#arp proxy enable
huawei(config-if-vlanif300)#arp proxy enable
f.
Save the data.

huawei(config)#save
Configure the ONT on the Web page.

a.
b.
Log in to the Web configuration page.

i.
Configure the IP address of the PC network adapter to be in the same network

segment with the IP address of the local maintenance Ethernet port on the
ONT.
ii.
Open the Web browser, and enter the IP address (https with high priority is
recommended) of the local maintenance Ethernet port on the ONT. In the login
window that is displayed, enter the user name and password of the
administrator. After the password is authenticated, the web configuration
window is displayed.
Configure the voice protocol.

1
Choose Voice > SIP/H.248 Protocol Conversion.
H.248
NOTE
The default voice protocol is SIP. Therefore, change the voice protocol first.
c.
Issue 01 (2016-04-29)
Configure parameters for the voice WAN interface.

545

Access Module
1
Choose WAN > WAN Configuration.
For configuring the VoIP service, VoIP or a

combination containing VoIP needs to be selected.
The VLAN ID of the ONT must be the same as
the user-side VLAN ID configured on the OLT.
d.
Configure parameters for the H.248-based voice interface.

1
Choose Voice > VoIP Basic Configuration.
The terminal IDs A0 and A1 must be consistent

with the corresponding configuration on the MGC.
If Associated POTS Port is 2, port
TEL2 on the ONT is bound.
Issue 01 (2016-04-29)

546

Access Module
NOTE
l The parameters of the H.248-based voice interface must be consistent with the corresponding
configuration on the media gateway controller (MGC).
l If dual-homing is configured, Address of the Standby MGC must be configured.
l MID Format can be set to Domain Name, IP, or Device Name. If MID Format is set to
Domain Name or Device Name, the setting must be consistent with the corresponding
configuration on the MGC.
l MG Domain is ONT's domain name registered with the MGC. It is globally unique. MG
Domain in this example is ONT's password.
l If Media Port is empty, the parameter value is the same as Signaling Port. The media
streams are not isolated from signaling streams. If the upper-layer network requires isolation
of media streams from signaling streams, create different traffic streams for the media streams
and signaling streams on the OLT, create different WAN ports on the ONT, and bind the
created WAN ports to Media Port and Signaling Port. When the packet is forwarded from
two WAN ports, the configured VLAN is carried by default.
l When the ONT is interconnected with a third-party softswitch, check RTP TID Prefix, Start
Number of RTP TID, and Width of RTP TID Number.
e.
Check the registration status of the voice user.

1
Choose Status > VoIP Information
User Status is Up
Configure the ONT on the U2000.

a.
Issue 01 (2016-04-29)
Configure and bind a general value-added service (VAS) profile for the ONT.

547

Access Module
3
1
The VLAN ID of the ONT

must be the same as the
user-side VLAN ID
configured on the OLT.
The created voice WAN

port is bound.
If dual-homing is
configured, Secondary
MGC must be set.
If Interface ID is 1, port
TEL1 on the ONT is
bound.
To add a user, select User,

right-click and choose Add
from the shortcut menu.
9
10
11
Issue 01 (2016-04-29)

548

Access Module
NOTE
If the upper-layer network requires isolation of media streams from signaling streams, create
different traffic streams for the media streams and signaling streams on the OLT. When the packet
is forwarded from two WAN ports, the configured VLAN is carried by default. Create a WAN
port named WAN-RTP on the ONT, and set this WAN port to a media WAN port. Specifically,
choose Interface 1 > RTP and set Associate WAN Interface to WAN2.
b.
Bind a general VAS profile.

2
1 ONT
HG8040H
V3R015C00
GE
c.
Configure the ONT VAS service.

1
1 ONT
HG8240H
Set TID to A1 for

physical port 2 in
the same way.
A0
Issue 01 (2016-04-29)

549

Access Module
NOTE
Domain Name is ONT's domain name registered with the MGC. It is globally unique. MG
Domain Name in this example is ONT's password.
Pay attention to the RTP TID configuration when the ONT is interconnected with a softswitch of
other vendors. The terminal IDs A0 and A1 must be consistent with the corresponding
Do not configure Directory Number.
----End
9.3.6 Configuring the H.248-based Voice Service (Through the

CLI)
The OLT manages ONTs and applies VoIP configurations to the ONT using the OMCI
protocol. This topic describes how to configure the H.248-based voice service.
Prerequisites
l
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN plan
Single VLAN tag:

l VLAN ID: 300
l VLAN type: smart
l CVLAN=SVLAN
packets.
Issue 01 (2016-04-29)

550

Access Module
Item
Data
Voice parameter

MG Domain: 0100000001 or 0100000002
Procedure
Run the display traffic table ip command to query the existing traffic profiles in the system.
If the existing traffic profiles in the system do not meet the requirements, run the traffic table
ip command to add a traffic profile.
Step 2 Configure the mapping relationship between a GEM port and a VLAN.
The service flow of user VLAN 300 is mapped to GEM port 12 in the ONT line profile.
Step 3 Create a service VLAN and add an upstream port to it.

Step 4 Create service flows.

Set the service VLAN to 300, GEM port ID to 12, and user VLAN to 300, and use traffic
profile ftth_voip.
ftth_voip
ftth_voip
gpon 0/1/0 ont 1 gemport 12 multi-service

name ftth_voip outbound traffic-table name
Step 5 Enable the ARP proxy function.

Voice media streams for different users of the same SVLAN fail to interchange because the
service ports of the smart VLAN are isolated from each other. Therefore, the ARP proxy
function needs to be enabled on the OLT.
Step 6 Configure ONT voice profiles.

ONT voice service configurations include the VoIP service provisioning mode, ONT voice
profiles, voice users, and voice-related parameters.
ONT voice profiles include the common MG interface attribute profile, POTS port profile,
MGC profile, and voice signal profile.
Issue 01 (2016-04-29)

551

Access Module
Common MG interface attribute profile: saves common attributes of an ONT voice

interface, including the fax mode, fax/modem negotiation mode, and priority of the
coding and decoding mode.
POTS port profile: saves physical attributes of a POTS port on an ONT, including the
impedance, Tx gain, Rx gain, and signaling type of a POTS port.
MGC profile: saves the IP address or domain name of an MGC, protocol port ID of the
MGC transport layer to which the MG interface belongs, and DSCP priority of media
packets.
Voice signal profile: saves the ONT signal tone and ringing tone.
Currently, the common MG interface attribute profile, POTS port profile, and MGC profile
can be applied to an H.248 interface, and the voice signal profile can be bound to an H.248
interface.
For profiles that can be applied to an H.248 interface, if parameters in those profiles are
changed, those profiles must be reapplied to the H.248 interface so that the changed
parameters can take effect. For profiles that can be bound to an H.248 interface, if parameters
in those profiles are changed, those profiles do not need to be rebound to the H.248 interface
and the changed parameters can take effect.
1.
Configure the VoIP service provisioning mode.

Run the ont voip config-method command to configure the VoIP service provisioning
mode. Run the display ont info command to query the mode of issuing VoIP services.
In this example, the mode is default, that is, the VoIP service provisioning mode is
depended on the actual service provisioning mode on the ONT. Run this command to
select a proper mode if the system supports multiple voice service provisioning modes.
The service provisioning modes can be OMCI, FTP, and TR069.
2.
Configure and apply an MG interface public attribute profile.

In this example, the default profile 1 is used.
a.
Configure an MG interface public attribute profile.

Run the display ont-mg-attribute-profile command to query the existing profile in
the system. If the existing profile in the system does not meet the requirements, run
the ont-mg-attribute-profile add command to add a profile.
b.
Apply a common MG interface attribute profile.

Run the ont-if-h248 bat-apply command to apply profiles in batches to H.248
interfaces and run the if-h248 attribute command to apply a profile to an H.248
interface or configure customized parameters on an H.248 interface. If you run
these two commands to apply profiles in batches or configure customized
parameters repeatedly, the last configurations take effect.
3.
Configure and apply a POTS port profile.

a.
Configure a POTS port profile.

Run the display ont-pots-profile command to query the existing profile in the
system. If the existing profile in the system does not meet the requirements, run the
ont-pots-profile add command to add a profile.
b.
Apply a POTS port profile.

Run the ont-pstnport electric bat-apply command to apply POTS port profiles in
batches and run the pstnport electric command to apply a POTS port profile to an
H.248 interface or configure customized parameters on an H.248 interface. If you
Issue 01 (2016-04-29)

552

Access Module
run these two commands to apply profiles in batches or configure customized

4.
Configure the voice WAN port of the ONT.

For ONT 1 and ONT 2, configure the IP address obtaining mode to DHCP, set the
management VLAN to VLAN 300, and use default values for other parameters.
huawei(config-if-gpon-0/1)#ont ipconfig 0 1 dhcp vlan 300
5.
Configure and apply an MGC profile.

a.

Run the display ont-mgc-profile command to query the existing profile in the
ont-mgc-profile add command to add a profile.
Create MGC profile 2, set the IP address of the MGC to 200.200.200.200, and use
default values for other parameters.
huawei(config)#ont-mgc-profile add profile-id 2 primary-mgc
200.200.200.200
b.
Add an H.248 interface and apply an MGC profile to the interface.

For ONT 1 and ONT 2, set the MG ID to 1, apply MGC profile 2 to ONT 1 and
ONT 2, and use default values for other parameters.
huawei(config-if-gpon-0/1)#if-h248 add 0 1 1 mgc-profile profile-id 2
1.
Add POTS users.

For ONT 1 and ONT 2, create a POTS user, set the MG ID to 1 (identical to the MG ID
of the H.248 interface), and set the physical terminal port ID to A0 and A1.
huawei(config-if-gpon-0/1)#mgpstnuser add 0 1 1 mgid 1 terminalid A0
Run the display mgpstnuser attribute command to check whether the configuration of
the POTS user is properly set.
huawei(config-if-gpon-0/1)#display mgpstnuser attribute 0 1 1
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
: 1
Terminal ID
: A0
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
: 1
Terminal ID
: A1
1.
Configure and bind the voice signal profile.

a.
Configure the voice signal profile.

Run the display ont-voipsignal-profile command to query the existing profiles in
the system. If the existing profile in the system does not meet the requirement, run
the ont-voipsignal-profile command to add a profile.
Issue 01 (2016-04-29)

553

Access Module
b.
Configure the ONT signal tone.

Run the display ont-tone command to query the existing configuration in the
system. If the existing configuration in the system does not meet the requirement,
run the ont-tone add command to add signal tone parameters. The ONT signal tone
will not be configured independently in this example.
c.
Configure ONT ringing parameters.

Run the display ont-ring command to query the existing configuration in the
run the ont-ring add command to add ringing parameters. The ONT ringing
parameter will not be configured independently in this example.
d.
Run the commit command to save parameters of the voice signal profile to the
database.
e.
Bind the voice signal profile.

Run the ont-voipsignal bat-bind command to bind voice signal profiles in batches
or run the voipsignal command to bind a voice signal profile to an ONT. If you run
these two commands to bind profiles in batches or bind a voice signal profile to an
ONT repeatedly, the last configurations take effect.
2.
(Optional) Configure the H.248 user codec.

Run the mgpstnuser codec command to configure the H.248 user codec. The H.248 user
codec will not be configured independently in this example.
3.
(Optional) Configure the global VoIP media attributes of the ONT.

Run the ont-voip-media attribute command to configure the global VoIP media
attributes of the ONT. Before configuration, ensure that the configured media attributes
are supported by the corresponding ONT. Otherwise, the ONT configuration will fail.
The global VoIP media attributes of the ONT will not be configured independently in
this example.

huawei(config)#save
----End
9.3.7 Configuring the SIP-based Voice Service (on a Web Page or

the U2000)
The OLT is connected to the remote ONT through a GPON port to provide users with the SIPbased high-quality and low-cost VoIP service.
Prerequisites
l
The SIP interface data and POTS user configuration data corresponding to the MG
interface have been configured on the SIP server.
The connection between the OLT and the SIP server is set up. The OLT can ping the IP
address of the SIP server successfully.
configuration, ensure that the current ONT software version supports SIP. For details, see
relevant ONT manuals.
Issue 01 (2016-04-29)

554

Access Module
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN plan
Single VLAN tag:

l VLAN ID: 300
l VLAN type: smart
l CVLAN=SVLAN
same network in a unified manner, and the ONTs
have the same C-VLAN. The ONT adds a C-VLAN
tag to packets.
Voice parameter
IP address of the SIP server: 200.200.200.200/24

Port ID of the SIP server: 5060
Home domain name: huawei.com
User phone number 1: 77730010
Procedure
l
Configure the OLT.

a.

carried.
priority-policy
local-setting
b.

profile.
c.
Issue 01 (2016-04-29)

555

Access Module

d.

service
service
e.
gpon 0/1/0 ont 1 gemport 12 multiname ftth_voip outbound trafficgpon 0/1/0 ont 2 gemport 12 multiname ftth_voip outbound traffic-

f.
Save the data.

huawei(config)#save

a.
b.

i.

ONT.
ii.
Optional: Configure the voice protocol.

1
NOTE
The default voice protocol is SIP. If the protocol is not changed, skip this step.
c.
Issue 01 (2016-04-29)

556

Access Module
1

d.
Issue 01 (2016-04-29)
Configure parameters for the SIP-based voice interface.

557

Access Module
1

NOTE
l The parameters of the SIP-based voice interface must be consistent with the corresponding
configuration on the softswitch.
l If dual-homing is configured, Address of the Standby Proxy Server must be configured.
l If Signaling Port is empty, the parameter value is the same as Media Port. If the upper-layer
network requires isolation of media streams from signaling streams, create different traffic
streams for the media streams and signaling streams on the OLT, create different WAN ports
on the ONT, and bind the created WAN ports to Media Port and Signaling Port. When the
packet is forwarded from two WAN ports, the configured VLAN is carried by default.
l If Associated POTS Port is 1, port TEL1 on the ONT is bound. If Associated POTS Port is
2, port TEL2 on the ONT is bound.
e.
Issue 01 (2016-04-29)

558

Access Module
1
User Status is Up

a.
Issue 01 (2016-04-29)
Configure a general VAS profile for the ONT.

559

Access Module
3
1

user-side VLAN ID
The created voice

WAN port is bound.
If dual-homing is
Proxy Server must be set.
TEL1 on the ONT is
bound.
To add a user, click User,

9
10
11
b.
Issue 01 (2016-04-29)

560

Access Module
2
1 ONT
HG8040H
V3R015C00
GE
c.
Issue 01 (2016-04-29)

561

Access Module
2
1
1 ONT
HG8240H
Set parameters of User 2 using the same method.

R Directory Number: 77730020
R Auth User Name: +8675577730020@huawei.com
R Auth Password: iadtest2
+8675577730010@huawei.com
77730010
NOTE
The parameters of the SIP-based voice user must be consistent with the corresponding
----End
9.3.8 Configuring the SIP-based Voice Service (Through the CLI)

protocol. This topic describes how to configure the SIP-based voice service.
Prerequisites
l
Issue 01 (2016-04-29)

562

Access Module
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN plan
Single VLAN tag:

l VLAN ID: 300
l VLAN type: smart
l CVLAN=SVLAN
tag to packets.
Voice parameter

Procedure


profile ftth_voip.
Issue 01 (2016-04-29)

563

Access Module
ftth_voip
ftth_voip


SIP service profile, SIP agent profile, digitmap profile, and voice signal profile.
l

SIP service data profile: saves the data information about the ONT voice service,
including the rights of call waiting (CW), three-way calling (3WC), call transfer (CT),
and call hold (CH).
SIP agent profile: saves the SIP agent information about an ONT, including the IP
address and domain name of the SIP agent server and attributes of media packets and
signaling packets.
Digitmap profile: saves the digitmap information about an ONT, including the timeout
time of the digitmap timer and the digitmap format.
Currently, the common MG interface attribute profile, POTS port profile, SIP service profile,
and SIP agent profile can be applied to an SIP interface, and the digitmap profile and voice
signal profile can be bound to an SIP interface.
For profiles that can be applied to an SIP interface, if parameters in those profiles are
changed, those profiles must be reapplied to the SIP interface so that the changed parameters
can take effect. For profiles that can be bound to an SIP interface, if parameters in those
profiles are changed, those profiles do not need to be rebound to the SIP interface and the
changed parameters can take effect.
1.

Issue 01 (2016-04-29)

564

Access Module
2.

a.

b.

Run the ont-if-sip bat-apply command to apply profiles in batches to SIP
interfaces and run the if-sip attribute command to apply a profile to an SIP
interface or configure customized parameters on an SIP interface. If you run these
two commands to apply profiles in batches or configure customized parameters
repeatedly, the last configurations take effect.
3.

a.

b.

SIP interface or configure customized parameters on an SIP interface. If you run
4.

5.
Configure and apply an SIP agent profile.

a.
Configure an SIP agent profile.

Run the display ont-sipagent-profile command to query the existing profile in the
system. If the existing profile in the system does not meet the requirement, run the
ont-sipagent-profile add command to add a profile.
Create SIP agent profile 2, set the IP address of the SIP server to 200.200.200.200,
and use default values for other parameters.
huawei(config)#ont-sipagent-profile add profile-id 2 proxy-server
200.200.200.200
b.
Add an SIP interface and apply an SIP agent profile to the interface.
For ONT 1 and ONT 2, set the MG ID to 1, apply SIP agent profile 2 to ONT 1 and
huawei(config-if-gpon-0/1)#if-sip add 0 1 1 sipagent-profile profile-id 2
6.
Add POTS users.

For ONT 1 and ONT 2, set the MG ID to 1 (identical to the MG ID of the added SIP
interface), create two POTS users named huawei1 and huawei2, set passwords to user1
Issue 01 (2016-04-29)

565

Access Module
and user2, set their phone numbers to 77730010 and 77730020 and use default values for
other parameters.
huawei(config-if-gpon-0/1)#sippstnuser add 0 1 1 mgid 1 username huawei1
telno 77730010
telno 77730020
Run the display sippstnuser attribute command to check whether the configuration of
huawei(config-if-gpon-0/1)#display sippstnuser attribute 0 1 1
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
Telephone NO.
User name
Password
...//The rest of the response
: 1
: 77730010
: huawei1
: user1
information is omitted.

-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
Telephone NO.
User name
Password
1.
: 1
: 77730020
: huawei2
: user2
Configure and apply an SIP service profile.

a.
Configure an SIP service profile.

Run the display ont-siprightflag-profile command to query the existing profile in
the ont-siprightflag-profile add command to add a profile.
b.
Apply an SIP service profile.

Run the ont-sippstnuser bat-apply from command to apply profiles in batches to
SIP interfaces and run the sippstnuser rightflag command to apply a profile to a
SIP interface or configure customized parameters on a SIP interface. If you run
2.
Configure and bind a digitmap profile.

a.
Configure a digitmap profile.

Run the display ont-digitmap-profile command to query the existing profile in the
ont-digitmap-profile add command to add a profile.
b.
Bind a digitmap profile.

Run the ont-sippstnuser bat-bind from command to apply profiles in batches to
SIP interfaces, or run the sippstnuser digitmap command to bind a profile to an
SIP interface. If you use these two commands to bind the profile to SIP ports
Issue 01 (2016-04-29)

566

Access Module
3.

a.

b.

c.

d.
database.
e.

4.
(Optional) Configure the SIP user codec.

Run the sippstnuser codec command to configure the SIP user codec. The SIP user
5.

this example.

huawei(config)#save
----End
9.3.9 Configuring the BTV Service

The OLT is connected to the remote bridging ONT through a GPON port to provide users
with the multicast service.
Prerequisites
l
The OLT is connected to the BRAS and the multicast source.
The VLAN of the LAN switch port connected to the OLT is the same as the upstream
VLAN of the OLT.
Issue 01 (2016-04-29)

567

Access Module
Data Plan
Table 9-4 Data plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 13
Traffic profile
ID: 8
802.1p priority: 4
CIR: off (unlimited)
Priority-based scheduling policy: local-setting
VLAN Plan
Single VLAN tag:

l SVLAN ID: 1000
l MVLAN ID: 1000
l VLAN type: smart
l ONT: duplicates packets based on user ports and
multicast VLANs (MVLANs) are stripped off
downstream.
l OLT: duplicates multicast packets based on PON ports
with MVLAN unchanged.
Multicast service data
Multicast protocol: IGMP proxy

Multicast version: IGMPv2
Multicast program: dynamic obtaining mode
Procedure
l
Configure the OLT.

a.

Set the profile name to ftth_iptv. Set the CIR to off (unlimited), priority to 4, and
priority-based scheduling policy to local-setting (that is, queues are scheduled based
on the priority specified in the profile).
NOTE
Run the display traffic table ip command to query the existing traffic profiles in the system. If
the existing traffic profiles in the system do not meet the requirements, run the traffic table ip
command to add a traffic profile.
huawei(config)#traffic table name ftth_iptv cir off priority 4 prioritypolicy local-setting
b.

profile.
Issue 01 (2016-04-29)

568

Access Module

c.
Configure the VLAN of the Ethernet port on the ONT and the multicast forwarding
mode.
If the ONT is connected to the STB through Ethernet port 2, add Ethernet port 2 to
VLAN 1000. Configure the multicast forwarding mode is untagged.
huawei(config-gpon-srvprofile-1)#multicast-forward untag
d.

If the ONT is connected to the STB through Ethernet port 2, the native VLAN ID is
1000.
e.

f.

Set the service VLAN to 1000, GEM port ID to 13, and user VLAN to 1000, and
use traffic profile ftth_iptv.
user-vlan 1000 inbound traffic-table name ftth_iptv outbound traffictable name ftth_iptv
g.
Create an MVLAN and configure the IGMP version.

Set the IGMP version for the MVLAN to IGMPv2.
huawei(config-mvlan1000)#igmp version v2
This operation will delete all IPv4 programs with source IP addresses
in the
current multicast VLAN
Are you sure to change current IGMP version? (y/n)[n]:y
Command is being executed. Please wait...
Command has been executed successfully
h.
Configure a program library.

Set the mode for obtaining multicast programs to dynamic.
NOTE
You can set the mode for obtaining multicast programs to dynamic only when the IGMP mode is
off.
huawei(config-mvlan1000)#igmp mode off
Are you sure to close IGMP? (y/n)[n]:y
Issue 01 (2016-04-29)

569

Access Module

(Optional) Set the address range for the dynamic programs. If you need to limit the
address range of dynamic programs, perform this operation. For example, set the
address range of dynamic programs to 224.1.1.1-224.1.1.100.
i.
Set the IGMP mode.

Select the IGMP proxy mode.
Are you sure to change IGMP mode? (y/n)[n]:y
j.
(Optional) Configure the IGMP upstream port.

In this example, the IGMP upstream port uses default value default.
Run the display igmp config global command to query the IGMP upstream port
mode. If this mode does not meet the requirement, run the igmp uplink-port-mode
command to configure it.
k.
Configure multicast users.

Add service ports 1 and 2 as multicast users.
huawei(config-btv)#igmp user add service-port 1
l.
Save the data.

huawei(config)#save
The ONT does not need to be configured.
----End
9.3.10 Configuring the VoD Service

with the VoD service.
Prerequisites
l
The OLT is connected to the BRAS and the program source.
VLAN of the OLT.
Issue 01 (2016-04-29)

570

Access Module
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 13
Traffic profile
ID: 8
802.1p priority: 4
VLAN Plan
Single VLAN tag:

l SVLAN ID: 1000
l VLAN type: smart
l CVLAN=SVLAN
l ONT: adds CVLAN tags to iTV service packets.
l OLT: transparently transmits packets with SVLANs.
Procedure
Step 1 Configure the OLT.
1.

priority-based scheduling policy to local-setting (that is, queues are scheduled based on
the priority specified in the profile).
NOTE
Run the display traffic table ip command to query the existing traffic profiles in the system. If the
existing traffic profiles in the system do not meet the requirements, run the traffic table ip command to
add a traffic profile.
2.

3.

VLAN 1000.
Issue 01 (2016-04-29)

571

Access Module
4.

If the ONT is connected to the STB through Ethernet port 2, the native VLAN ID is
1000.
5.

6.

Set the service VLAN to 1000, GEM port ID to 13, and VLAN translation mode to
transparent transmission, and use traffic profile ftth_iptv.
traffic-table name ftth_iptv
outbound traffic-table name ftth_iptv
7.
gpon 0/1/0 ont 1 gemport 13 inbound

tag-transform transparent
Save the data.

huawei(config)#save
Step 2 The ONT does not need to be configured.

----End
9.3.11 Configuring Link Aggregation, Congestion Control, and

Security Policies
The global configuration of link aggregation and queue scheduling based on priorities ensures
service reliability. The global configuration of security policies ensures service security.
Context
Link aggregation provides a higher bandwidth and uplink reliability for optical line terminals
(OLTs) by aggregating multiple uplink Ethernet ports to one link aggregation group (LAG).
Link aggregation is recommended.
Congestion control places the packets to be sent from a port into multiple queues that are
marked with different priorities. Then, the packets are sent based on queue priorities.
Congestion control is recommended.
Security policies ensure system, user, and service security.
NOTE
Enable a service security function based on the service type. For details, see 9.2.6 Principle of Security Data
Plan.
Issue 01 (2016-04-29)

572

Access Module
Procedure
l
Configure link aggregation.

The following configurations are used as an example to configure link aggregation:
Uplink ports 0/19/0 and 0/19/1 are added to a LAG.
The two ports send packets upstream based on the packets' source MAC addresses.
The LAG works in Link Aggregation Control Protocol (LACP) static aggregation
mode.
huawei(config)#link-aggregation 0/19 0-1 ingress workmode lacp-static
Configure queue scheduling.

According to quality of service (QoS) planning principles, all packets are scheduled in
strict priority (SP) mode and mapped to queues according to the packets' priorities. For
details about QoS planning principles, see 9.2.2 Principle of QoS Planning.
huawei(config)#cos-queue-map cos0 0 cos4 4 cos5 5 cos6 6
Configure system security.
Enable deny of service (DoS) anti-attack on the OLT.

i.
Run the security anti-dos enable command to globally enable DoS antiattack.
ii.
Run the security anti-dos control-packet policy command to configure a

protocol packet processing policy that will be used when a DoS attack occurs.
iii. Run the security anti-dos control-packet rate command to configure the
threshold for the rate of sending protocol packets to the CPU.
Enable IP address anti-attack on the OLT.

Run the security anti-ipattack enable command to enable IP address anti-attack.
Configure user security.
Enable MAC address anti-flapping on the OLT.

Run the security anti-macduplicate enable command to enable MAC address antiflapping.
Issue 01 (2016-04-29)
Enable MAC address anti-spoofing on the OLT.

i.
In global config mode, run the security anti-macspoofing enable command to

globally enable MAC address anti-spoofing.
ii.
Enable MAC address anti-spoofing at VLAN level in global config mode or

service profile mode:
1)
In global config mode, run the security anti-macspoofing vlan

command to enable MAC address anti-spoofing.
2)
In global config mode, run the vlan service-profile command to create a

VLAN service profile.
3)
Perform the following operations to enable MAC address anti-spoofing in

VLAN service profile mode:
1)
Run the security anti-macspoofing enable command to enable

MAC address anti-spoofing at VLAN level.
2)
Run the commit command to make the profile configuration take

effect.
3)
Run the quit command to quit the VLAN service profile mode.

573

Access Module
4)
Run the vlan bind service-profile command to bind the created

VLAN service profile to a VLAN.
iii. (Optional) Run the security anti-macspoofing max-mac-count command to

set the maximum number of MAC addresses that can be bound to a service
flow.
iv.
(Optional) Run the security anti-macspoofing exclude command to configure

the types of packets for which MAC address anti-spoofing does not take effect,
such as Internet Group Management Protocol (IGMP) packets.
Enable IP address anti-spoofing on the OLT.

IP address anti-spoofing can be enabled or disabled at three levels: global, VLAN,
and service port levels. This function takes effect only after it is enabled at the three
levels. Among the three levels, IP address anti-spoofing is disabled only at the
global level by default.
i.
In global config mode, run the security anti-ipspoofing enable command to

enable IP address anti-spoofing at the global level.
ii.
In VLAN service profile mode, run the security anti-ipspoofing enable

command to enable IP address anti-spoofing at the VLAN level.
iii. Run the security anti-ipspoofing service-port serviceport-id enable

command to enable IP address anti-spoofing at the service port level.
l
Configure service security.
Enable Dynamic Host Configuration Protocol (DHCP) Option 82 on the OLT. This
configuration is recommended for the DHCP-based Internet access service.
i.
Enable DHCP Option 82 on the OLT.

DHCP Option 82 can be enabled or disabled at four levels: global, port,
VLAN, and service port levels. This function takes effect only after it is
enabled at the four levels. Among the four levels, DHCP Option 82 is disabled
only at the global level by default.
The global level: In global config mode, run the dhcp option82
command to enable DHCP Option 82 at the global level.
When you run this command, select the enable, forward, or rebuild
parameter based on site requirements. The three parameters can all enable
DHCP Option 82 but provide different packet processing policies on the
OLT. For details, see the dhcp option82 command.
Issue 01 (2016-04-29)
The port level: In global config mode, run the dhcp option82 port or
dhcp option82 board command to enable DHCP Option 82 at the port
level.
The VLAN level:

1)
In global config mode, run the vlan service-profile command to

create a VLAN service profile.
2)
Run the dhcp option82 enable command to enable DHCP Option

82 at the VLAN level.
3)

effect.
4)
5)


574

Access Module
ii.
The service port level: In global config mode, run the dhcp option82
service-port command to enable DHCP Option 82 at the service port
level.
On the OLT, run the dhcp-option82 permit-forwarding service-port

command with the enable parameter selected, to allow ONT DHCP packets to
carry Option 82 information.
Enable Policy Information Transfer Protocol (PITP) on the OLT. This configuration
is recommended for the PPPoE-based Internet access service.
i.
Enable PITP on the OLT.

PITP can be enabled or disabled at four levels: global, port, VLAN, and
service port levels. This function takes effect only after it is enabled at the four
levels. Among the four levels, PITP is disabled only at the global level by
default.
The global level: In global config mode, run the pitp enable pmode, pitp
forward pmode, or pitp rebuild pmode command to enable PITP at the
global level.
In the preceding commands, the enable, forward, and rebuild
parameters can all enable PITP but provide different packet processing
policies on the OLT. Select one of them based on site requirements. For
details, see the pitp command.
The port level: In global config mode, run the pitp port or pitp board
command to enable PITP at the port level.
The VLAN level:
ii.
1)

2)
Run the pitp enable command to enable PITP at the VLAN level.
3)

effect.
4)
5)

The service port level: In global config mode, run the pitp service-port
command to enable PITP at the service port level.
On the OLT, run the pitp permit-forwarding service-port command with the
enable parameter selected, to allow ONT PPPoE packets to carry a vendor tag.
----End

In the FTTH scenario, ONTs are installed in users' houses which are far away from the central
equipment room. ONTs provide remote service verification methods including PPPoE dialup
emulation, call emulation, and multicast emulation to facilitate configuration and
commissioning engineers to verify services remotely after service configuration.
Prerequisites
ONTs and upper-layer devices have been connected properly. The BRAS and MGC/IMS have
been configured.
Issue 01 (2016-04-29)

575

Access Module
Background
Remote
Service
Verificati
on
Method
Function
Description
PPPoE
dialup
emulation
An ONT simulates a PPPoE user

terminal software to perform
dialup and interact with the
BRAS to verify the connectivity
between the ONT and BRAS.
l PPPoE dialup emulation requires a

service flow which does not belong to
a QinQ VLAN.
l A user name, password, and
authentication mode must be
configured on the BRAS for the
PPPoE dialup emulation.
l An ONT supports a maximum of a
An ONT simulates a voice user

to make a call to check whether
the voice service data is
correctly configured. You can
also use the call emulation
function to locate a fault when
the voice service is faulty.
l An ONT can simulate a caller or

callee to communicate with a phone
in a call. In this case, only a
functional phone is required in the
central office where the acceptance
personnel is.
Multicast
emulation
This function enables you to

simulate a multicast user going
online and lead the program
stream to an ONT. You can
check whether the multicast
service is normal by checking
the real-time traffic of the
multicast program.
Multicast services configured in the

dynamic controllable multicast mode do
not support this function.
Item
Data
Remarks
PPPoE
dialup
emulation
parameters
PPPoE user name: test@huawei
The user name, password, and

authentication mode for the emulation
test must be configured on the BRAS.
The entered user name, password, and
authentication mode must be consistent
with those configured on the BRAS.
Call
emulation
parameters
ONT POTS ID: 1
Call
Emulation

call emulation.
Data plan
Issue 01 (2016-04-29)
Password: test
The default values are used. You can run

the display pots emulational
configuration command to check the
parameter values.

576

Access Module
Item
Data
Remarks
Multicast
emulation
parameters
Multicast service flow ID: 1
MVLAN: 1000
IP address of the multicast
program: 224.1.1.10
Procedure
l
Verify the Internet access service using PPPoE dialup emulation.

a.
In the xPON board mode, run the pppoe simulate start command to start a PPPoE
dialup emulation test. The following test uses GPON as an example:
huawei(config-if-gpon-0/1)#pppoe simulate start
{ portid<0,7> }:0
{ ontid<0,127> }:1
{ eth<K>|untagged<K>|vlanid<0,4095> }:eth
{ ont-portid<1,8> }:4
{ untagged<K>|vlanid<0,4095> }:100
{ priority<0,7>|user-name<K> }:user-name
{ username<S><Length 1-64> }:test@huawei
{ user-password<K> }:user-password
{ password<S><Length 1-64> }:test
{ authentication-mode<K> }:authentication-mode
{ protocol<E><chap,pap> }:chap
Command:
pppoe simulate start 0 1 eth 4 100 user-name test@huawei userpassword
test authentication-mode chap
huawei(config-if-gpon-0/1)#
---------------------------------ONT PPPoE Test Result
---------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
ONT ETH Port ID
: 4
ONT Vlan ID
: 100
Vlan Priority
: Emluator result
: Success
Session ID
: 18814
User IP
: 192.168.100.101
Gateway IP
: 192.168.100.1
----------------------------------
Troubleshooting methods for the Internet access service

a.
b.
Issue 01 (2016-04-29)
Check whether configurations are complete on the OLT.

n
Run the display ont info command to query the ONT status to check whether
the ONT is registered successfully.
Run the display service-port command to check whether the Internet access
service flow is configured and whether the inner VLAN ID of the service flow
is consistent with that in the data plan.
If a native VLAN is configured for the Ethernet port on the ONT, run the
display ont port attribute command in the xPON board mode to check
whether the native VLAN is correct.
Check the upstream and downstream ports by checking the MAC address learning
status.
577

Access Module
i.
ii.
Run the display mac-address vlan command to check the MAC address
learning status of the Internet service VLAN.
If the upstream port does not learn a MAC address, check the network
connections between the upstream port and upper-layer devices and check
the configurations of upper-layer devices.
If the downstream port does not learn a MAC address, check whether the
ONT is activated, whether the PC is connected to the right port on the
ONT, and whether the PC is working properly.
Run the display ont-learned-mac command to check whether the ONT

connecting to the PON port learned any MAC addresses.
If not, check whether the ONT properly connects to the PC or home gateway
(HGW).
Verify the voice service using call emulation.

a.
Run the ont emulational call command to configure a call emulation test.
huawei(config)#test
huawei(config-test)#ont emulational call caller-port 0/1/0 1 1 telno
77730020
{ <cr>|caller-stop-time<K> }:
Command:
ont emulational call caller-port 0/1/0 1 1 telno 77730020
b.
The ONT outputs the call emulation result after the test is complete.
huawei(config-test)#
---------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 0
ONT-POTSID
: 1
Test type
: caller emulational call test
Detected number
: 77730020
Reported number
: 77730020
Current status
: test end
Test Result
: success
----------------------------------------------------------------
Troubleshooting methods for the voice service.

a.
b.

n
Run the display service-port command to check whether the voice service
flow is configured and whether the inner VLAN ID of the service flow is
consistent with that in the data plan.
status.
Run the display mac-address vlan command to check the MAC address learning
status of the voice service VLAN.
Issue 01 (2016-04-29)
connections between the upstream port and upper-layer devices and check the
configurations of upper-layer devices.
If the downstream port does not learn a MAC address, check whether the ONT
is activated and whether physical links are normal.
If both the upstream and downstream ports can learn the MAC address, record
the MAC address of the ONT and log in to the service router (SR) to check
whether an IP address is allocated to the MAC address.
578

Access Module
c.
Check the registration status of the voice service.

n
You can run the display ont port state command on the OLT to query the call
connection status on the POTS port. If Call State is RegisterFail or
Connecting for a long time, check whether the voice configuration on the
MGC/SIP server is consistent with that on the ONT.
If the ONT uses the H.248 protocol, you can run the display ont mg status
command on the OLT to query the registration status of the MG interface that
connects to the ONT. If MG Status is UnRegistered or Registering for a long
time, check whether the voice configuration on the MGC/SIP server is
consistent with that on the ONT.
You can query the registration status of the voice service on the ONT web
page. If the query result shows that the registration fails or the voice service is
in the registering state for a long time, check whether the voice configuration
on the MGC/SIP server is consistent with that on the ONT.
Verify the multicast service using multicast emulation.

a.
Run the igmp static-join command to simulate a multicast user to order a multicast
program.
huawei(config)#btv
huawei(config-btv)#igmp static-join service-port 1 ip 224.1.1.10 vlan
1000
NOTE
If the multicast program is obtained dynamically, igmp static-join can be executed successfully
only when the range for obtaining the dynamic program is set.
b.
Run the display igmp user command to query the status of the multicast user.
huawei(config-btv)#display igmp user service-port 1
User
: 0/1/0/1
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 1
Video flow ID
: 1
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Current version
: IGMP v3
Current IGMP IPv6 version : IGMP IPv6 v2
Available programs
: 8
Global leave
: disable
User max bandwidth
: no-limit
Used bandwidth(kbps)
: 0
Used bandwidth
to max bandwidth(%)
: Total video bandwidth
: Mcast video bandwidth
: Active program list
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start time
-------------------------------------------------------------------------PROGRAM-5
1000 224.1.1.10
watching
2011-10-29
16:33:41+08:00
-------------------------------------------------------------------------Total: 1
Issue 01 (2016-04-29)

579

Access Module
c.
Run the display multicast flow-statistic command to query the real-time traffic of
the multicast program.
huawei(config-btv)#display multicast flow-statistic vlan 1000 ip
224.1.1.10
{ <cr>|sourceip<K> }:
Command:
display multicast flow-statistic vlan 1000 ip 224.1.1.10
Multicast flow statistic result: 8736(kbps)
----End
9.4 Bridging ONT + HGW Network Scenario (GPON

Access)
VoD service when bridging ONTs + HGWs are used to build an FTTH network.

Optical fibers are connected to user homes and triple play services are required. The following
provides detailed service requirements:
l
Service extension is supported and different services do not affect each other.
Proper service security is ensured.
Internet access services are protected against unauthorized access, user account
theft or borrowing, MAC/IP spoofing, and malicious attacks.
and traffic flooding attacks.
As shown in Figure 9-3, the HGW integrating an IAD provides Internet, voice over Internet
Protocol (VoIP), and Internet Protocol television (IPTV) services to users.
Services are mainly implemented on the HGW, and the bridging ONT works with the OLT to
provide Layer 2 channels.
Issue 01 (2016-04-29)

580

Access Module
Figure 9-3 Bridging ONT + HGW

bridging optical network terminal (ONT)+home gateway (HGW).
Figure 9-4 Configuration roadmap in FTTH networking using a bridging ONT+HGW

Issue 01 (2016-04-29)

581

Access Module
Item
Step
Description
Optical
line
termina
l (OLT)

to an OLT.
OLT

Access Service
l An ONT provides only Layer 2 service

channels, which do not require
configuration. An HGW is equipped
with an integrated access device (IAD)
provides the Internet access, VoIP, and
IPTV services for users.
l IPTV services include the BTV and
VoD services that are different in
configuration procedures and need to
be configured separately.
HGW
9.4.5 Configuring the Voice

Service
Configure the
IPTV service.
9.4.6
Configuring
the BTV
Service
9.4.7
Configuring
the VoD
Service
OLT


OLT

on-site operation.

Issue 01 (2016-04-29)

582

Access Module
Data Plan
Item
Data
DBA profile

ONT line profile
Profile name: ftth

ONT service
profile
Profile name: ftth
Network
topology data
PON port: 0/1/0
ONT IDs: 1 and 2
Procedure
l
utilization.
Issue 01 (2016-04-29)

583

Access Module
(OMCI).
1.

add
add
add
add
profile-name
profile-name
profile-name
profile-name

NOTE
2.

ftth_dba_mngt
ftth_dba_voip
ftth_dba_iptv
ftth_dba_hsi
add
add
add
add
11
12
13
14
eth
eth
eth
eth
tcont
tcont
tcont
tcont
4
5
6
7
NOTE
port.
settings.
3.

Issue 01 (2016-04-29)

584

Access Module
setting.
4.
Step 2 Add an ONT.

discovered ONT.
l
Add ONTs offline.


NOTE

Issue 01 (2016-04-29)

585

Access Module


--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
successfully.
Config state
: normal
the ONT is normal.
Match state
: match
l
ONU.
----End

Prerequisites
l
VLAN of the OLT.
Issue 01 (2016-04-29)

586

Access Module
Residential users generally access the Internet in Point-to-Point Protocol over Ethernet
(PPPoE) dial-up mode. PPPoE dial-up can be performed on personal computers (PCs) or
HGWs.
The configuration processes on HGWs of different models or in different appearances

are similar. This topic describes how to configure the Internet access service on an
HG239 that is connected to an ONT upstream through a LAN.
Data Plan
Item
Data
ONT line profile
Profile name: ftth


PON port: 0/1/0
ONT IDs: 1 and 2
ID of the port on the HGW that is connected to the PC: 1
VLAN Plan
Double-tagged VLAN:
l S-VLAN ID: 100
l C-VLAN ID: 1001-1002
l U-VLAN ID: 45
l ONT: The upstream packets sent from the HGW carry
user-VLANs and the ONT transparently transmits
them.
l OLT: The OLT translates the U-VLAN to S-VLAN+CVLAN.
Procedure
l
Configure the OLT.

a.

priorities.
b.
Issue 01 (2016-04-29)
Configure the mapping between a GEM port and a VLAN.

587

Access Module
The service flow of user-side VLAN 45 is mapped to GEM port 14 in the ONT line
profile.
NOTE
Here, the user-side VLAN is the VLAN carried by packets sent from HGW to ONT, namely, UVLAN.
c.

Add Ethernet port 1 to VLAN 45 in the ONT service profile.
d.
Create an Internet access service VLAN and add an upstream port to it.
e.
Create Internet access service flows.

Set S-VLAN ID to 100 and GEM port ID to 14. Use traffic profile ftth_hsi.
huawei(config)#service-port vlan 100 gpon 0/1/0 ont 1 gemport 14 multiservice user-vlan 45 tag-transform translate-and-add
inner-vlan 1001 inbound traffic-table name ftth_hsi outbound traffictable name ftth_hsi
huawei(config)#service-port vlan 100 gpon 0/1/0 ont 2 gemport 14 multiservice user-vlan 45 tag-transform translate-and-add
f.
Save the data.

huawei(config)#save
Configure the HGW.

a.
b.
Issue 01 (2016-04-29)
Log in to the web configuration window.

i.
Enter the default IP address in the address bar of the browser, and then press
Enter.
ii.
In the login window, enter the user name and password (the default value is
provided by ISP) of the administrator and click OK.
Set parameters for the Internet access service.

i.
Choose Internet access service configuration from the navigation tree.
ii.

Parameter
Value
Bearing
service
Internet

588

Access Module
Parameter
Value
VLAN
enabling
Enabled: VLAN tags are added to upstream packets.
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VLANID[1-4
094]
NOTE
When Internet access service flows are created on the OLT, if the
value of uservlan is untagged, set this parameter to Disabled;
otherwise, set it to Enabled.
The internet VLAN ID on the HGW. In this example, set

this parameter to 45.
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VPI/VCI
(Set this
parameter
when the
HGW uses
ADSL2+ for
upstream
transmission)
Mode
Set the VPI/VCI to be the same as that configured on the

devices at the central office. In this example, set this
parameter to 0/35.
PPPoE
iii. Submit the configuration.

----End
9.4.5 Configuring the Voice Service

Prerequisites
l
Issue 01 (2016-04-29)

589

Access Module
HGWs have different models and appearance and therefore, their configuration
processes are not the same. This topic describes how to configure the voice service on an
HGW. The actual configuration varies depending on different HGWs.
The built-in integrated access device (IAD) of the HGW uses SIP as the voice protocol.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN plan
Single VLAN tag:

l VLAN ID: 300
l VLAN type: smart
l UVLAN ID: 47
l ONT: Packets that are sent upstream by the HGW
are tagged with a user VLAN. The ONT
transparently transmits the user VLAN.
l OLT: translates the VLAN tag (user VLAN <-> SVLAN).
Voice parameter

User phone number: 77730010
Procedure
l
Configure the OLT.

a.

carried.
priority-policy
local-setting
b.

profile.
NOTE
The user VLAN is the VLAN in the packets sent from the HGW to the ONT, that is, the UVLAN.
Issue 01 (2016-04-29)

590

Access Module

c.

If the ONT is connected to the HGW through Ethernet port 1, add Ethernet port 1 to
VLAN 47 in the ONT service profile.
d.

e.

user-vlan 47 inbound traffic-table name ftth_voip outbound traffic-table
name ftth_voip
user-vlan 47 inbound traffic-table name ftth_voip outbound traffic-table
name ftth_voip
f.

g.
Save the data.

huawei(config)#save
Configure the HGW.

a.
b.
Issue 01 (2016-04-29)

i.
Enter.
ii.
Set parameters of the voice service.

i.
Choose the voice service configuration from the navigation tree.
ii.

Parameter
Value
Bearing
service
VoIP

591

Access Module
Parameter
Value
Enabling
status
Enabled
VLAN
enabling
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VLANID[1-4
094]
NOTE
When voice service flows are created on the OLT, if the value of
uservlan is untagged, set this parameter to Disabled; otherwise,
set it to Enabled.
The voice VLAN ID on the HGW. In this example, set this

parameter to 47.
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VPI/VCI
(Set this
parameter
when the
HGW uses
ADSL2+ for
upstream
transmission)

parameter to 0/35.
802.1p
Enabled
Mode
Route: Route mode
DHCP
Enabled
iii. Choose the voice telephone number configuration from the navigation tree. Set
the parameters as follows:
Issue 01 (2016-04-29)
Parameter
Value
Address
Preferred IP address of the proxy server: 200.200.200.200
Port ID
Preferred signaling port ID of the proxy server: 5060
Enabled
Enabled

592

Access Module
iv.
Parameter
Value
User number
To use the VoIP account, you can set the account to the
user telephone number. In this example, set the user
telephone number to 77730010.
User
password
Submit the configuration.
----End

Prerequisites
l
The OLT is connected to the BRAS and the multicast source.
VLAN of the OLT.
processes are not the same. This topic describes how to configure the Internet access
service on an HGW generally. The actual configuration varies depending on different
HGWs.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 13
Traffic profile
ID: 8
802.1p priority: 4
Issue 01 (2016-04-29)

593

Access Module
Item
Data
VLAN Plan
Single VLAN tag:
l SVLAN ID: 1000

l HGW VLAN: 43
l MVLAN ID: 1000
l VLAN type: smart
l ONT: translates the upstream VLAN of the HGW to an
MVLAN.

Procedure
l
Configure the OLT.

a.

priority-based scheduling policy to local-setting (that is, queues are scheduled based
on the priority specified in the profile).
NOTE
Run the display traffic table ip command to query the existing traffic profiles in the system. If
b.

If the ONT is connected to the HGW through Ethernet port 2, map the service flow
of Ethernet port 2 to GEM port 13 in the ONT line profile.
c.
Configure a VLAN translation policy for the Ethernet port on the ONT.
If the ONT is connected to the HGW through Ethernet port 2, VLAN 43 of the
HGW is translated to VLAN 1000 and the MVLAN of the ONT is translated to
VLAN 1000.
huawei(config-gpon-srvprofile-1)#port vlan eth 2 translation 1000 uservlan 43
huawei(config-gpon-srvprofile-1)#multicast-forward tag translation 43
Issue 01 (2016-04-29)

594

Access Module
d.

e.

Set the service VLAN to 1000, GEM port ID to 13, and user VLAN to 1000, and
use traffic profile ftth_iptv.
f.

in the
g.

NOTE
off.
h.
Set the IGMP mode.

i.

Issue 01 (2016-04-29)

595

Access Module
j.

k.
Save the data.

huawei(config)#save
Configure the HGW.

a.
b.

i.
Enter.
ii.
Set parameters for the BTV service.

i.
Choose BTV service configuration from the navigation tree.
ii.
Set parameters for the BTV service.

Parameter
Value
Bearing
service
OTHER: It is used for the BTV service.
VLAN
enabling
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VLANID[1-4
094]
NOTE
When BTV service flows are configured on the OLT, if the value
of uservlan is untagged, set this parameter to Disabled;
otherwise, set it to Enabled.
The BTV VLAN ID on the HGW. In this example, set this

parameter to 43.
(Set this
parameter
when the
HGW uses
the LAN or
VDSL2 for
upstream
transmission)
Issue 01 (2016-04-29)

596

Access Module
Parameter
Value
VPI/VCI

parameter to 0/35.
(Set this
parameter
when the
HGW uses
ADSL2+ for
upstream
transmission)
Binding item
LAN3 (Example: LAN3 interface serves as the BTV

interface)
Mode
Bridge
DHCP
transparent
transmission
Enabled
iii. Submit the configuration.

----End

Prerequisites
l
VLAN of the OLT.
processes are not the same. This topic describes how to configure the Internet access
service on an HGW generally. The actual configuration varies depending on different
HGWs.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

T-CONT ID: 4
GEM port ID: 13
Issue 01 (2016-04-29)

597

Access Module
Item
Data
Traffic profile
ID: 8
802.1p priority: 4
VLAN Plan
Single VLAN tag:

l SVLAN ID: 1000
l VLAN type: smart
l UVLAN (upstream VLAN of the HGW): 41
l CVLAN=UVLAN
l ONT: transparently transmits the UVLAN of the
HGW.
l OLT: implements VLAN translation: U<->S.
Procedure
1.

NOTE
2.

3.

If the ONT is connected to the HGW through Ethernet port 2, add Ethernet port 2 to
VLAN 41.
4.
Issue 01 (2016-04-29)

598

Access Module

5.

profile ftth_iptv.
huawei(config)#service-port vlan 1000 gpon
service user-vlan 41 inbound traffic-table
huawei(config)#service-port vlan 1000 gpon
service user-vlan 41 inbound traffic-table
6.
0/1/0 ont 1 gemport 13 multiname ftth_iptv

0/1/0 ont 2 gemport 13 multiname ftth_iptv
Save the data.

huawei(config)#save
Step 2 Configure the HGW.

1.
2.

a.
Enter the default IP address in the address bar of the browser, and then press Enter.
b.
Set parameters for the VoD service.

a.
Choose VoD service configuration from the navigation tree.
b.
Set parameters for the VoD service.

Parameter
Value
Bearing
service
OTHER: It is used for the VoD service.
VLAN
enabling
(Set this
parameter
when the
HGW uses the
LAN or
VDSL2 for
upstream
transmission)
VLANID[1-40
94]
NOTE
When VoD service flows are configured on the OLT, if the value of
uservlan is untagged, set this parameter to Disabled; otherwise, set it
to Enabled.
The VoD VLAN ID on the HGW. In this example, set this

parameter to 41.
(Set this
parameter
when the
HGW uses the
LAN or
VDSL2 for
upstream
transmission)
Issue 01 (2016-04-29)

599

Access Module
Parameter
Value
VPI/VCI

devices at the central office. In this example, set this parameter
to 0/35.
(Set this
parameter
when the
HGW uses
ADSL2+ for
upstream
transmission)
c.
Binding item
LAN4 (Example: LAN4 interface serves as the VoD interface)
Mode
Bridge
DHCP
transparent
transmission
Enabled
----End

Security Policy
Context
NOTE
Plan.
Procedure
l
Issue 01 (2016-04-29)

mode.
600

Access Module


i.
ii.




i.

ii.

1)

2)

3)

1)

2)

effect.
3)
4)


flow.
iv.
Issue 01 (2016-04-29)

601

Access Module

i.

ii.


l
i.

level.
The VLAN level:
ii.
Issue 01 (2016-04-29)
1)

2)

3)

effect.
4)
5)

level.

602

Access Module
i.

default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

Prerequisites
been configured.
Issue 01 (2016-04-29)

603

Access Module
Background
Remote
Service
Verificati
on
Method
Function
Description
PPPoE
dialup
emulation


a QinQ VLAN.


personnel is.
Multicast
emulation

multicast program.

Item
Data
Remarks
PPPoE
dialup
emulation
parameters

Call
emulation
parameters
ONT POTS ID: 1
Call
Emulation

call emulation.
Data plan
Issue 01 (2016-04-29)
Password: test

parameter values.

604

Access Module
Item
Data
Remarks
Multicast
emulation
parameters
MVLAN: 1000
program: 224.1.1.10
Procedure
l

a.
{ portid<0,7> }:0
{ ontid<0,127> }:1
Command:
---------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
ONT ETH Port ID
: 4
ONT Vlan ID
: 100
Vlan Priority
: Emluator result
: Success
Session ID
: 18814
User IP
: 192.168.100.101
Gateway IP
: 192.168.100.1
----------------------------------

a.
b.
Issue 01 (2016-04-29)

n
status.
605

Access Module
i.
ii.

(HGW).

a.
huawei(config)#test
77730020
Command:
b.
---------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 0
ONT-POTSID
: 1
Test type
Detected number
: 77730020
Reported number
: 77730020
Current status
: test end
Test Result
: success
----------------------------------------------------------------

a.
b.

n
status.
Issue 01 (2016-04-29)
606

Access Module
c.

n

a.
program.
huawei(config)#btv
1000
NOTE
b.
User
: 0/1/0/1
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 1
Video flow ID
: 1
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Current version
: IGMP v3
Available programs
: 8
Global leave
: disable
User max bandwidth
: no-limit
: 0
Used bandwidth
to max bandwidth(%)
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start time
-------------------------------------------------------------------------PROGRAM-5
1000 224.1.1.10
watching
2011-10-29
16:33:41+08:00
-------------------------------------------------------------------------Total: 1
Issue 01 (2016-04-29)

607

Access Module
c.
224.1.1.10
Command:
----End
9.5 Gateway ONT Network Scenario (GPON Access)

VoD service when gateway ONT are used to build an FTTH network.

Optical fibers are connected to users' home and triple play services are required. The
following provides detailed service requirements:
l
Service expansibility is supported and different services do not affect each other.
Service security is ensured.
Internet and Wi-Fi access services are protected against unauthorized access, user
account theft or borrowing, MAC/IP spoofing, and malicious attack.
and traffic flooding attack.
As shown in Figure 9-5, the ONT integrating an IAD provides Internet, Wi-Fi, VoIP, and
IPTV services to users.
The HGW ONT facilitates interconnection of home devices by providing Layer 3 services,
such as Point-to-Point Protocol over Ethernet (PPPoE)/DHCP dialup, network address
translation (NAT), and Internet Group Management Protocol (IGMP) snooping. This scenario
provides fine-grained management channels and service control, and mainly applies to Layer
3 networking.
Issue 01 (2016-04-29)

608

Access Module
Figure 9-5 HGW ONT

gateway optical network terminal (ONT).
Issue 01 (2016-04-29)

609

Access Module
Figure 9-6 Configuration roadmap in FTTH networking using a gateway ONT

Item
Step
Description
Optical
line
termina
l (OLT)

to an OLT.
OLT

Access Service (on a Web Page
or the U2000)
None
9.5.5 Configuring the Wi-Fi

Access Service (on a Web Page)
None
ONT
U2000
Issue 01 (2016-04-29)

610

Access Module
Item
Step
Configure the
VoIP service.
Description
9.5.6
Configuring
Service (on a
Web Page or
the U2000)
9.5.7
Configuring
Service
(Through the
CLI)
9.5.8
Configuring
the SIP-based
Voice Service
(on a Web
Page or the
U2000)
NOTE
l The H.248 and Session Initiation Protocol
(SIP) protocols are mutually exclusive for
the VoIP service. Either of them is
configured at a time.
l The voice service can be configured
through command line interface (CLI) on
an OLT, web page, or U2000. Select a
configuration mode based on site
requirements.
l OLT CLI: This mode can be used for
site deployment or the U2000 has not
been deployed.
l Web page: This mode can be used to
site deployment.
l U2000: This mode can be used to
service provisioning in batches.
9.5.9
Configuring
the SIP-based
Voice Service
(Through the
CLI)
Configure the
IPTV service.
9.5.10
Configuring
the BTV
Service
IPTV services include the BTV and VoD

separately.
9.5.11
Configuring
the VoD
Service
OLT
Issue 01 (2016-04-29)



611

Access Module
Item
Step
Description
OLT

on-site operation.

Data Plan
Item
Data
DBA profile

ONT line profile
Profile name: ftth

ONT service
profile
Issue 01 (2016-04-29)
Profile name: ftth


612

Access Module
Item
Data
Network
topology data
PON port: 0/1/0

ONT IDs: 1 and 2
Procedure
l
utilization.
(OMCI).
1.

add
add
add
add
profile-name
profile-name
profile-name
profile-name

NOTE
2.

ftth_dba_mngt
ftth_dba_voip
ftth_dba_iptv
ftth_dba_hsi

Issue 01 (2016-04-29)

613

Access Module

NOTE
port.
settings.
3.

setting.
4.
Step 2 Add an ONT.

discovered ONT.
l
Add ONTs offline.


Issue 01 (2016-04-29)

614

Access Module

NOTE


--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
successfully.
Config state
: normal
the ONT is normal.
Match state
: match
l
ONU.
Issue 01 (2016-04-29)
615

Access Module
----End
9.5.4 Configuring the Internet Access Service (on a Web Page or

the U2000)
Prerequisites
l
accounting requirements for dialup users. For details about the configurations, see the
VLAN of the OLT.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 14
VLAN Plan
Double-tagged VLAN:
l S-VLAN ID: 100
l CVLAN ID: 1001
l C'-VLAN ID: 1010-1011
other.
Procedure
l
Issue 01 (2016-04-29)
Configure the OLT.

616

Access Module
a.

priorities.
b.

profile.
c.

d.

huawei(config)#service-port vlan 100 gpon 0/1/0 ont
service
user-vlan 1001 tag-transform translate-and-add
inner-vlan 1010 inbound traffic-table name ftth_hsi
table name ftth_hsi
huawei(config)#service-port vlan 100 gpon 0/1/0 ont
service
inner-vlan 1011 inbound traffic-table name ftth_hsi
table name ftth_hsi
e.
1 gemport 14 multioutbound traffic2 gemport 14 multioutbound traffic-
Save the data.

huawei(config)#save

a.
b.

i.

ONT.
ii.
Configure the working mode of a LAN port.

The LAN port bound to the WAN port must work in the Layer 3 mode. Therefore,
set the working mode to Layer 3 for the LAN port connected to the PC.
Issue 01 (2016-04-29)

617

Access Module
1
Choose LAN > LAN Port Work Mode.
Select the check box of LAN 1 and set LAN1 to work

in the Layer 3 mode.
c.
Configure parameters of a WAN port.

1
For configuring the Internet access service, INTERNET or a

combination containing INTERNET needs to be selected.
The VLAN ID of the ONT must be the same as the user-side VLAN
ID configured on the OLT.
The user name and password must be the same as the user name
and password configured on the BRAS.
The WAN port is bound to LAN1.
NAT must be enabled to configure the

d.
Check the ONT connection status.

Choose Status > WAN Information.
Connection Status is Connected.

a.
Issue 01 (2016-04-29)
Add a general VAS configuration profile for the ONT.

618

Access Module
4
2
They should be the

same as that
configured on the OLT
at the user side.
8
Enable the NAT function when
configuring an online service.
To configure an Internet access

service, INTERNET or a
combination containing
INTERNET needs to be selected.
The LAN port bound to

the WAN port must be
a Layer 3 interface.
10
11
WAN1 and LAN1 are

bound.
12
NOTE
To bind a WAN port to multiple LAN ports, set Physical Port Name to LAN1,...,LANx. For
example, to bind WAN 1 to LAN 1 and LAN 2, set Physical Port Name to LAN1, LAN2.
b.

2
1 ONT
HG8040H
V3R015C00
GE
c.
Issue 01 (2016-04-29)
Configure the ONT value-added service.

619

Access Module
2
1
1 ONT
HG8240H
NOTE
The User Name and Password must be the same as those configured on the BRAS.
----End
9.5.5 Configuring the Wi-Fi Access Service (on a Web Page)

The OLT is connected to the remote ONT through a GPON port to provide users with highspeed Internet Wi-Fi services.
Prerequisites
l
accounting requirements for dialup users. For details about the configurations, see the
VLAN of the OLT.
The Web page for configuring ONT varies with ONT versions, but the parameter
configuration is the same. For details, see relevant ONT manuals.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 14
Issue 01 (2016-04-29)

620

Access Module
Item
Data
VLAN Plan
Double-tagged VLAN:
l S-VLAN ID: 100

l CVLAN ID: 1001
l C'-VLAN ID: 1010-1011
other.
Procedure
l
Configure the OLT.

a.

priorities.
b.

profile.
c.

d.

Issue 01 (2016-04-29)

621

Access Module

e.
Save the data.

huawei(config)#save

Layer 3 bridge Wi-Fi service
a.
b.

i.

ONT.
ii.
Configure the Wi-Fi parameters.

1
Choose Wi-Fi > Wi-Fi Basic Configuration.
c.
Issue 01 (2016-04-29)
Configure the parameters of the Layer 3 bridge WAN port.

622

Access Module
1

combination containing INTERNET needs to be selected
The VLAN ID of the ONT must be the same as the user-side VLAN ID
NOTE
When you use Wi-Fi access service in the IPoE mode, you need to enable the DHCP relay
function. For procedure details, see DHCP Server Configuration.
d.

In the navigation tree, choose Status > WAN Information. In the right pane,
1
Layer 3 route Wi-Fi service

a.
b.
Issue 01 (2016-04-29)

i.

ONT.
ii.
Configure the Wi-Fi parameters.

623

Access Module
1
Choose Wi-Fi > Wi-Fi Basic Configuration.
c.
Configure the parameters of the Layer 3 route WAN port.

1

combination containing INTERNET needs to be selected
The VLAN ID of the ONT must be the same as the user-side VLAN ID
d.
Issue 01 (2016-04-29)

Connection Status is Connected and the obtained IP address is displayed at IP
Address.
624

Access Module
1
----End
Result
l
Layer 3 bridge Wi-Fi service: SSID radio signals can be searched on the Wi-Fi terminal.
After the user enter the authentication key and pass the authentication, the user can
access the Internet.
Layer 3 route Wi-Fi service: SSID radio signals can be searched on the Wi-Fi terminal.
After the user enter the authentication key and pass the authentication, the Wi-Fi
terminal can obtain the IP address allocated by the DHCP IP address pool on the ONT.
After the PPPoE dialup is successfully performed on the ONT, the user can access the
Internet.
NOTE
The security mode and encryption configured on a Wi-Fi terminal must be the same as those of an ONT. If
you cannot find the following encryption modes: TKIP&AES, and AES. The reason may lie in an old Wi-Fi
driver version. If so, replace the old version with a new one.
9.5.6 Configuring the H.248-based Voice Service (on a Web Page

or the U2000)
Prerequisites
l
Issue 01 (2016-04-29)

625

Access Module
Context
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN Plan
Single VLAN tag:

l SVLAN ID: 200
l SVLAN type: smart
l SVLAN attribute: common
l CVLAN ID: 300
packets.
l OLT: translates the VLAN tag (C-VLAN <-> SVLAN).
Voice parameter

MG Domain: 0100000001 or 0100000002
Procedure
l
Configure the OLT.

a.

carried.
priority-policy
local-setting
b.

profile.
c.

Issue 01 (2016-04-29)

626

Access Module

d.

user-vlan 300 inbound traffic-table name ftth_voip outbound traffictable name ftth_voip
e.

f.
Save the data.

huawei(config)#save

a.
b.

i.

ONT.
ii.
Configure the voice protocol.

1
H.248
NOTE
The default voice protocol is SIP. Therefore, change the voice protocol first.
c.
Issue 01 (2016-04-29)

627

Access Module
1

d.
Configure parameters for the H.248-based voice interface.

1
The terminal IDs A0 and A1 must be consistent

with the corresponding configuration on the MGC.
Issue 01 (2016-04-29)

628

Access Module
NOTE
l The parameters of the H.248-based voice interface must be consistent with the corresponding
configuration on the media gateway controller (MGC).
l If dual-homing is configured, Address of the Standby MGC must be configured.
l MID Format can be set to Domain Name, IP, or Device Name. If MID Format is set to
Domain Name or Device Name, the setting must be consistent with the corresponding
l MG Domain is ONT's domain name registered with the MGC. It is globally unique. MG
Domain in this example is ONT's password.
streams are not isolated from signaling streams. If the upper-layer network requires isolation
of media streams from signaling streams, create different traffic streams for the media streams
and signaling streams on the OLT, create different WAN ports on the ONT, and bind the
created WAN ports to Media Port and Signaling Port. When the packet is forwarded from
two WAN ports, the configured VLAN is carried by default.
l When the ONT is interconnected with a third-party softswitch, check RTP TID Prefix, Start
Number of RTP TID, and Width of RTP TID Number.
e.

1
User Status is Up

a.
Issue 01 (2016-04-29)
Configure and bind a general value-added service (VAS) profile for the ONT.

629

Access Module
3
1

user-side VLAN ID
The created voice WAN

port is bound.
If dual-homing is
MGC must be set.
TEL1 on the ONT is
bound.
To add a user, select User,

9
10
11
Issue 01 (2016-04-29)

630

Access Module
NOTE
If the upper-layer network requires isolation of media streams from signaling streams, create
different traffic streams for the media streams and signaling streams on the OLT. When the packet
is forwarded from two WAN ports, the configured VLAN is carried by default. Create a WAN
port named WAN-RTP on the ONT, and set this WAN port to a media WAN port. Specifically,
choose Interface 1 > RTP and set Associate WAN Interface to WAN2.
b.

2
1 ONT
HG8040H
V3R015C00
GE
c.

1
1 ONT
HG8240H
Set TID to A1 for

physical port 2 in
the same way.
A0
Issue 01 (2016-04-29)

631

Access Module
NOTE
Domain Name is ONT's domain name registered with the MGC. It is globally unique. MG
Domain Name in this example is ONT's password.
Pay attention to the RTP TID configuration when the ONT is interconnected with a softswitch of
other vendors. The terminal IDs A0 and A1 must be consistent with the corresponding
Do not configure Directory Number.
----End

CLI)
Prerequisites
l
Context
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN Plan
Single VLAN tag:

l SVLAN ID: 200
l SVLAN type: smart
l CVLAN ID: 300
packets.
Issue 01 (2016-04-29)

632

Access Module
Item
Data
Voice parameter

MG Domain: 0100000001 or 0100000002
Procedure


Set the service VLAN to 200, GEM port ID to 12, and user VLAN to 300. Use traffic profile
ftth_voip.
huawei(config)#service-port vlan 200 gpon 0/1/0 ont 1 gemport 12 multi-service
user-vlan 300 inbound traffic-table name ftth_voip outbound traffic-table name
ftth_voip
ftth_voip


MGC profile, and voice signal profile.
Issue 01 (2016-04-29)

633

Access Module

MGC profile: saves the IP address or domain name of an MGC, protocol port ID of the
MGC transport layer to which the MG interface belongs, and DSCP priority of media
packets.
Currently, the common MG interface attribute profile, POTS port profile, and MGC profile
can be applied to an H.248 interface, and the voice signal profile can be bound to an H.248
interface.
For profiles that can be applied to an H.248 interface, if parameters in those profiles are
changed, those profiles must be reapplied to the H.248 interface so that the changed
parameters can take effect. For profiles that can be bound to an H.248 interface, if parameters
in those profiles are changed, those profiles do not need to be rebound to the H.248 interface
and the changed parameters can take effect.
1.

2.

a.

b.

Run the ont-if-h248 bat-apply command to apply profiles in batches to H.248
interfaces and run the if-h248 attribute command to apply a profile to an H.248
interface or configure customized parameters on an H.248 interface. If you run
3.

a.

b.

H.248 interface or configure customized parameters on an H.248 interface. If you
Issue 01 (2016-04-29)

634

Access Module
run these two commands to apply profiles in batches or configure customized

4.

5.

a.

Run the display ont-mgc-profile command to query the existing profile in the
ont-mgc-profile add command to add a profile.
Create MGC profile 2, set the IP address of the MGC to 200.200.200.200, and use
default values for other parameters.
huawei(config)#ont-mgc-profile add profile-id 2 primary-mgc
200.200.200.200
b.
Add an H.248 interface and apply an MGC profile to the interface.

For ONT 1 and ONT 2, set the MG ID to 1, apply MGC profile 2 to ONT 1 and
1.
Add POTS users.

For ONT 1 and ONT 2, create a POTS user, set the MG ID to 1 (identical to the MG ID
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
: 1
Terminal ID
: A0
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
: 1
Terminal ID
: A1
1.

a.

Issue 01 (2016-04-29)

635

Access Module
b.

c.

d.
database.
e.

2.
(Optional) Configure the H.248 user codec.

3.

this example.

huawei(config)#save
----End
9.5.8 Configuring the SIP-based Voice Service (on a Web Page or

the U2000)
Prerequisites
l
Issue 01 (2016-04-29)

636

Access Module
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN Plan
Single VLAN tag:

l SVLAN ID: 200
l SVLAN type: smart
l CVLAN ID: 300
tag to packets.
Voice parameter

Procedure
l
Configure the OLT.

a.

carried.
priority-policy
local-setting
b.

profile.
Issue 01 (2016-04-29)

637

Access Module
c.

d.

e.

f.
Save the data.

huawei(config)#save

a.
b.

i.

ONT.
ii.
Optional: Configure the voice protocol.

1
NOTE
The default voice protocol is SIP. If the protocol is not changed, skip this step.
c.
Issue 01 (2016-04-29)

638

Access Module
1

d.
Issue 01 (2016-04-29)
Configure parameters for the SIP-based voice interface.

639

Access Module
1

NOTE
l The parameters of the SIP-based voice interface must be consistent with the corresponding
l If dual-homing is configured, Address of the Standby Proxy Server must be configured.
l If Signaling Port is empty, the parameter value is the same as Media Port. If the upper-layer
network requires isolation of media streams from signaling streams, create different traffic
streams for the media streams and signaling streams on the OLT, create different WAN ports
on the ONT, and bind the created WAN ports to Media Port and Signaling Port. When the
packet is forwarded from two WAN ports, the configured VLAN is carried by default.
e.
Issue 01 (2016-04-29)

640

Access Module
1
User Status is Up

a.
Issue 01 (2016-04-29)
Configure a general VAS profile for the ONT.

641

Access Module
3
1

user-side VLAN ID
The created voice

WAN port is bound.
If dual-homing is
Proxy Server must be set.
TEL1 on the ONT is
bound.
To add a user, click User,

9
10
11
b.
Issue 01 (2016-04-29)

642

Access Module
2
1 ONT
HG8040H
V3R015C00
GE
c.
Issue 01 (2016-04-29)

643

Access Module
2
1
1 ONT
HG8240H
Set parameters of User 2 using the same method.

R Directory Number: 77730020
R Auth User Name: +8675577730020@huawei.com
R Auth Password: iadtest2
+8675577730010@huawei.com
77730010
NOTE
The parameters of the SIP-based voice user must be consistent with the corresponding
----End
9.5.9 Configuring the SIP-based Voice Service (Through the CLI)

Prerequisites
l
Issue 01 (2016-04-29)

644

Access Module
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 12
VLAN Plan
Single VLAN tag:

l SVLAN ID: 200
l SVLAN type: smart
l CVLAN ID: 300
tag to packets.
Voice parameter

Procedure


Set the service VLAN to 200, GEM port ID to 12, and user VLAN to 300. Use traffic profile
ftth_voip.
Issue 01 (2016-04-29)

645

Access Module

ftth_voip
ftth_voip


SIP service profile, SIP agent profile, digitmap profile, and voice signal profile.
l

SIP service data profile: saves the data information about the ONT voice service,
including the rights of call waiting (CW), three-way calling (3WC), call transfer (CT),
and call hold (CH).
SIP agent profile: saves the SIP agent information about an ONT, including the IP
signaling packets.
Digitmap profile: saves the digitmap information about an ONT, including the timeout
Currently, the common MG interface attribute profile, POTS port profile, SIP service profile,
and SIP agent profile can be applied to an SIP interface, and the digitmap profile and voice
signal profile can be bound to an SIP interface.
1.

Issue 01 (2016-04-29)

646

Access Module
2.

a.

b.

Run the ont-if-sip bat-apply command to apply profiles in batches to SIP
interfaces and run the if-sip attribute command to apply a profile to an SIP
interface or configure customized parameters on an SIP interface. If you run these
two commands to apply profiles in batches or configure customized parameters
3.

a.

b.

SIP interface or configure customized parameters on an SIP interface. If you run
4.

5.
Configure and apply an SIP agent profile.

a.

Run the display ont-sipagent-profile command to query the existing profile in the
ont-sipagent-profile add command to add a profile.
Create SIP agent profile 2, set the IP address of the SIP server to 200.200.200.200,
200.200.200.200
b.
For ONT 1 and ONT 2, set the MG ID to 1, apply SIP agent profile 2 to ONT 1 and
6.
Add POTS users.

For ONT 1 and ONT 2, set the MG ID to 1 (identical to the MG ID of the added SIP
Issue 01 (2016-04-29)

647

Access Module
other parameters.
telno 77730010
telno 77730020
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
Telephone NO.
User name
Password
: 1
: 77730010
: huawei1
: user1

-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
Telephone NO.
User name
Password
1.
: 1
: 77730020
: huawei2
: user2
Configure and apply an SIP service profile.

a.
Configure an SIP service profile.

Run the display ont-siprightflag-profile command to query the existing profile in
the ont-siprightflag-profile add command to add a profile.
b.
Apply an SIP service profile.

Run the ont-sippstnuser bat-apply from command to apply profiles in batches to
SIP interfaces and run the sippstnuser rightflag command to apply a profile to a
SIP interface or configure customized parameters on a SIP interface. If you run
2.
Configure and bind a digitmap profile.

a.

Run the display ont-digitmap-profile command to query the existing profile in the
ont-digitmap-profile add command to add a profile.
b.

Run the ont-sippstnuser bat-bind from command to apply profiles in batches to
SIP interfaces, or run the sippstnuser digitmap command to bind a profile to an
SIP interface. If you use these two commands to bind the profile to SIP ports
Issue 01 (2016-04-29)

648

Access Module
3.

a.

b.

c.

d.
database.
e.

4.
(Optional) Configure the SIP user codec.

Run the sippstnuser codec command to configure the SIP user codec. The SIP user
5.

this example.

huawei(config)#save
----End

The OLT is connected to the remote gateway ONT through a GPON port to provide users
with the bridge WAN multicast service.
Prerequisites
l
The OLT has been connected to the BRAS and the multicast source.
VLAN of the OLT.
Issue 01 (2016-04-29)

649

Access Module
Data Plan
Table 9-5 Data plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 13
Traffic profile
ID: 8
802.1p priority: 4
VLAN Plan
Single VLAN tag:

l SVLAN ID: 1000
l MVLAN ID: 1000
l VLAN type: smart
l ONT: duplicates multicast packets based on user ports
and MVLANs are stripped off downstream.

Procedure
1.

NOTE
2.
Issue 01 (2016-04-29)

650

Access Module
3.
mode.
4.

5.

traffic profile ftth_iptv.
user-vlan 1000 inbound traffic-table name ftth_iptv outbound traffic-table
name ftth_iptv
name ftth_iptv
6.

This operation will delete all IPv4 programs with source IP addresses in the
7.

NOTE
You can set the mode for obtaining multicast programs to dynamic only when the IGMP mode is off.
address range of dynamic programs, perform this operation. For example, set the address
range of dynamic programs to 224.1.1.1-224.1.1.100.
Issue 01 (2016-04-29)

651

Access Module
8.
Set the IGMP mode.

9.

Run the display igmp config global command to query the IGMP upstream port mode.
If this mode does not meet the requirement, run the igmp uplink-port-mode command
to configure it.
10. Configure multicast users.

11. Save the data.

huawei(config)#save
Step 2 Configure the ONT on the Web page.

1.

The LAN port bound to the WAN port must work in the Layer 3 mode. Therefore, set the
working mode to Layer 3 for the LAN port connected to the PC.
1
Select the check box of LAN 2 and set LAN2 to

work in the Layer 3 mode.
2.
Issue 01 (2016-04-29)

652

Access Module
1
Select INTERNET or a combination containing INTERNET to

configure the BTV service. Alternatively, select IPTV or a
combination containing IPTV.
NAT is invalid when the BTV service is

enabled.
NOTE
If Service Type is set to IPTV or a type containing IPTV, this WAN port does not need to be bound to a
LAN port.
3.

1
----End

The OLT is connected to the remote gateway ONT through a GPON port to provide users
Issue 01 (2016-04-29)

653

Access Module
Prerequisites
l
The iTMS has configured the IPTV WAN ports on the ONT.
The OLT has been connected to the BRAS and the program source.
VLAN of the OLT.
Data Plan
Item
Data
ONT line profile
Profile name: ftth

GEM port ID: 13
Traffic profile
ID: 8
802.1p priority: 4
VLAN Plan
Single VLAN tag:

l SVLAN ID: 1000
l VLAN type: smart
l CVLAN: 2001
l The ONT adds CVLAN tags (configured on the iTMS)
to packets: untag<->C.
l The OLT implements VLAN translation: C<->S.
Procedure
1.

NOTE
2.
Issue 01 (2016-04-29)

654

Access Module
3.

VLAN 1000.
4.

5.

Create service flows. Set the S-VLAN to 1000, GEM port ID to 13, and C-VLAN to
2001, and use traffic profile ftth_iptv. Set the VLAN translation policy to Translate. The
C-VLAN 2001 of the ONT is translated to S-VLAN 1000.
huawei(config)#service-port vlan 1000 gpon 0/1/0 ont 1 gemport 13 multiservice user-vlan 2001
tag-transform translate inbound traffic-table name ftth_iptv outbound traffictable name ftth_iptv
huawei(config)#service-port vlan 1000 gpon 0/1/0 ont 2 gemport 13 multiservice user-vlan 2001
tag-transform translate inbound traffic-table name ftth_iptv outbound traffictable name ftth_iptv
6.
Save the data.

huawei(config)#save
Step 2 Configure the ONT on the Web page.

1.

The LAN port bound to the WAN port must work in the Layer 3 mode. Therefore, set the
working mode to Layer 3 for the LAN port connected to the PC.
1
Select the check box of LAN 2 and set LAN2 to

work in the Layer 3 mode.
2.
Issue 01 (2016-04-29)

655

Access Module
1
Select INTERNET or a combination containing INTERNET to

configure the VoD service. Alternatively, select IPTV or a
combination containing IPTV.

VoD service.
NOTE
If Service Type is set to IPTV or a type containing IPTV, this WAN port does not need to be bound to a
LAN port.
3.

1
----End
9.5.12 Configuring Any Port Any Service (on the Web Page)
The OLT can connect a remote ONT through the GPON interface. This topic describes how to
configure the function of any port any service.
Issue 01 (2016-04-29)

656

Access Module
Prerequisites
l
VLAN of the OLT.
Data Plan
Item
Service Type
Data
ONT line profile
Internet access
Profile name: ftth

T-CONT ID: 4
GEM port ID for Internet access service:
14
Multicast service
Profile name: ftth

T-CONT ID: 4
GEM port ID for Internet access service:
13
Traffic profile
Internet access
l Profile name: ftth_hsi

l 802.1p priority: 0
l Upstream and downstream bandwidth:
4 Mbit/s
l Priority-based scheduling policy: localsetting
Multicast service
l ID: 8
l 802.1p priority: 4
l CIR: off (unlimited)
l Priority-based scheduling policy: localsetting
Issue 01 (2016-04-29)

657

Access Module
Item
Service Type
Data
VLAN Plan
Internet access
Double-tagged VLAN:
l S-VLAN ID: 100
l CVLAN ID: 1001
l C'-VLAN ID: 1010-1011
VLAN Translation Policy:
l ONT: ONTs configure the VLAN and
l OLT: The OLT performs VLAN
Multicast service
Single VLAN tag:

l SVLAN ID: 1000
l MVLAN ID: 1000
l CVLAN ID:1000
l VLAN type: smart
l ONT: duplicates multicast packets
based on user ports and MVLANs are
stripped off downstream.
l OLT: duplicates multicast packets
based on PON ports with MVLAN
unchanged.
Procedure
l
Configure the OLT.

a.

Set the name to ftth_hsi for the traffic profile of the Internet access service, the CIR
to 4 Mbit/s, and the priority to 0. In addition, configure the scheduling mode so that
packets are scheduled according to their priorities.
Configure traffic profile 8 for the multicast service. Set the CIR to off (unlimited),
priority to 4, and priority-based scheduling policy to local-setting (that is, queues
are scheduled based on the priority specified in the profile).
Issue 01 (2016-04-29)

658

Access Module
huawei(config)#traffic table ip index 8 cir off priority 4 prioritypolicy local-setting
b.

profile. Map the service flows of user VLAN 1100 to the GEM port with index 13.
NOTE
Do not configure the port VLAN or native VLAN of an ONT port.
c.

Add upstream port 0/19/0 to VLAN 100 and 1000.
huawei(config)#vlan 100,1000 smart
huawei(config)#port vlan 100,1000 0/19 0
d.

For the Internet access service, set the service VLAN to 100, GEM port ID to 14,
and user VLAN to 1001. Use traffic profile ftth_hsi.
huawei(config)#service-port 1 vlan 100 gpon 0/1/0 ont 1 gemport 14 multiservice
traffic-table name
For the multicast service, set the service VLAN to 1000, GEM port ID to 13, and
user VLAN to 1000, and use traffic profile 8.
huawei(config)#service-port 2 vlan 1000 gpon 0/1/0 ont 1 gemport 13
multi-service
e.

in the
f.

NOTE
off.
Issue 01 (2016-04-29)

659

Access Module
g.
Set the IGMP mode.

h.

i.

Add service port 2 as multicast users.
j.
Save the data.

huawei(config)#save
Configure the ONT on the web page.

a.
b.

i.

ONT.
ii.

The function of any port any service requires that all LAN ports work in Layer 3
mode. Set LAN ports to Layer 3 mode.
1
c.

NOTE
Do not bind WAN ports and LAN ports during the configuration of any port any service.
WAN configuration for the Internet access service

Issue 01 (2016-04-29)

660

Access Module
1

combination containing INTERNET needs to be selected.

WAN configuration for the multicast service
Issue 01 (2016-04-29)

661

Access Module
1
For configuring the IPTV access service, IPTV or a combination

containing IPTV needs to be selected.
d.
1000
Configure a static route for the multicast service.

1
Choose Route > Static Route Configuration.
e.
Issue 01 (2016-04-29)

662

Access Module
1
----End
Result
The ONT can connect to the Internet access service or Multicast service through any LAN
port.

Security Policy
Context
NOTE
Plan.
Procedure
l
Issue 01 (2016-04-29)

mode.
663

Access Module


i.
ii.




i.

ii.

1)

2)

3)

1)

2)

effect.
3)
4)


flow.
iv.
Issue 01 (2016-04-29)

664

Access Module

i.

ii.


l
i.

level.
The VLAN level:
ii.
Issue 01 (2016-04-29)
1)

2)

3)

effect.
4)
5)

level.

665

Access Module
i.

default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

Prerequisites
been configured.
Issue 01 (2016-04-29)

666

Access Module
Background
Remote
Service
Verificati
on
Method
Function
Description
PPPoE
dialup
emulation


a QinQ VLAN.


personnel is.
Multicast
emulation

multicast program.

Item
Data
Remarks
PPPoE
dialup
emulation
parameters

Call
emulation
parameters
ONT POTS ID: 1
Call
Emulation

call emulation.
Data plan
Issue 01 (2016-04-29)
Password: test

parameter values.

667

Access Module
Item
Data
Remarks
Multicast
emulation
parameters
MVLAN: 1000
program: 224.1.1.10
Procedure
l

a.
{ portid<0,7> }:0
{ ontid<0,127> }:1
Command:
---------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
ONT ETH Port ID
: 4
ONT Vlan ID
: 100
Vlan Priority
: Emluator result
: Success
Session ID
: 18814
User IP
: 192.168.100.101
Gateway IP
: 192.168.100.1
----------------------------------

a.
b.
Issue 01 (2016-04-29)

n
status.
668

Access Module
i.
ii.

(HGW).

a.
huawei(config)#test
77730020
Command:
b.
---------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 0
ONT-POTSID
: 1
Test type
Detected number
: 77730020
Reported number
: 77730020
Current status
: test end
Test Result
: success
----------------------------------------------------------------

a.
b.

n
status.
Issue 01 (2016-04-29)
669

Access Module
c.

n

a.
program.
huawei(config)#btv
1000
NOTE
b.
User
: 0/1/0/1
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 1
Video flow ID
: 1
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Current version
: IGMP v3
Available programs
: 8
Global leave
: disable
User max bandwidth
: no-limit
: 0
Used bandwidth
to max bandwidth(%)
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start time
-------------------------------------------------------------------------PROGRAM-5
1000 224.1.1.10
watching
2011-10-29
16:33:41+08:00
-------------------------------------------------------------------------Total: 1
Issue 01 (2016-04-29)

670

Access Module
c.
224.1.1.10
Command:
----End
9.6 Configuring Triple Play Service (GPON Access in

Simplified Mode)
The GPON service configuration in simplified mode is implemented by creating an end-toend (E2E) service port between an OLT and an ONT. This topic describes how to achieve the
GPON service configuration in simplified mode by configuring the Internet access service,
voice service, and multicast service in the FTTH scenario.
NOTE
On the same ONT, service ports in the simplified mode conflict with services ports in the profile mode.
Therefore, they cannot be configured concurrently.
Subscribers use the bridging ONTs (supporting VoIP). The PC, STB, and phone are
connected to different ports on the ONT to achieve the triple play service.
Different services are distinguished by different S-VLANs on an OLT.
The internet access service has a rate restriction of 4 Mbit/s both in upstream and
downstream directions.
IPTV service has no rate restriction in upstream or downstream direction.
The VoIP adopts the H.248 protocol and the phones connected to different ONTs can
communicate with each other.
Figure 9-7 shows an example network of the FTTH triple play service.
Issue 01 (2016-04-29)

671

Access Module
Figure 9-7 Example network of the FTTH triple play service
Prerequisite
l
The OLT is connected to the BRAS, MGC, and the multicast source.
The interface data and the POTS user configuration data corresponding to the MG
interface is configured on the MGC.
VLAN of the OLT.
Configure the OLT.
Procedure
a.
Configure GPON ONT profiles.

GPON ONT profiles include the DBA profile, line profile, service profile, and
alarm profile. In the simplified mode, the default DBA profile, line profile, and
service profile are used. That is, these profiles do not need to be configured.
i.
Add an ONT line profile

The default line profile 0 is used. In this profile, the default T-CONT 0 and TCONT 1 are created. T-CONT 0 is bound to the default DBA profile 2 (the
fixed bandwidth: 1 Mbit/s), and is used for the OMCI management channel. TCONT 1 is bound to the default DBA profile 0 (the assured bandwidth: 8
Mbit/s, the maximum bandwidth: 20 Mbit/s), and is used for the service
channel. The DBA profile bound to a T-CONT can be modified.
ii.
Add an ONT service profile

The default service profile 0 is used. In this profile, the capability set of the
ETH port and POTS port is set to adaptive by default and therefore the OLT
automatically matches the number of ports according to the type of the online
ONT.
Issue 01 (2016-04-29)

672

Access Module
iii. (Optional) Add an alarm profile.
b.
The default GPON alarm profile 1 is used. The alarm thresholds of the
default alarm profile are 0, which indicates that no alarm is generated.
In this example, the default alarm profile is used, and therefore the
configuration of the alarm profile is not required.
Run the gpon alarm-profile add command to configure a GPON alarm

profile, which is used for monitoring the performance of an activated
ONT line.
Add ONTs on the OLT.

The ONT is connected to a GPON port of the OLT by optical fibers. The service
can be configured only after ONTs are successfully added on the OLT.
Two ONTs are connected to GPON port 0/1/1. The ONT IDs are 1 and 2, SNs are
3230313126595540 and 6877687714852901, passwords are 0100000001 and
0100000002, the discovery mode of passwords is once-on, and the management
mode is OMCI.
i.
Add ONTs offline.

If the password of an ONT is known, run the ont add command to add an
ONT offline.
huawei(config-if-gpon-0/1)#ont add 1 1 password-auth 0100000001 onceon no-aging omci
huawei(config-if-gpon-0/1)#ont add 1 2 password-auth 0100000002 onceon no-aging omci
ii.
Discover ONTs automatically.

If the password or SN of an ONT is unknown, run the port portid ont-autofind command in GPON mode to enable the ONT auto-discovery function of
the GPON port. Then, run the ont confirm command to confirm the ONT.
//After this command is executed, the information of all ONTs
connected to the GPON port through optical splitters is displayed.
----------------------------------------------------------------------Number
: 1
F/S/P
: 0/1/1
Ont SN
: 3230313126595540
Password
:
VenderID
: HWTC
Ont Version
: 120A0000
Ont SoftwareVersion : V1R001C01
Ont EquipmentID
: EchoLife:HG8245
Ont autofind time
: 2009-10-24 14:59:10
----------------------------------------------------------------------Number
: 2
F/S/P
: 0/1/1
Ont SN
: 6877687714852901
Password
:
VenderID
: HWTC
Ont Version
: 120A0000
Ont EquipmentID
: EchoLife:HG8245
Ont autofind time
: 2009-10-24 14:59:12
Issue 01 (2016-04-29)

673

Access Module
----------------------------------------------------------------------huawei(config-if-gpon-0/1)#ont confirm 1 ontid 1 sn-auth

3230313126595540 omci
huawei(config-if-gpon-0/1)#ont confirm 1 ontid 2 sn-auth
6877687714852901 omci
iii. (Optional) Bind the alarm profile to the ONT.

c.
Confirm that the ONTs go online successfully.

After an ONT is added, run the display ont info command to query the current
status of the ONT. Ensure that Config flag of the ONT is active, Run State is
online, Config state is normal, and Match state is match.
--------------------------------------------------------------------F/S/P
:
0/1/1
ONT-ID
:
1
Control flag
: active
activated.
Run state
: online
successfully.
Config state
: normal
//Indicates that the configuration
state of the ONT is normal.
Match state
: match
//Indicates that the capability
profile bound to the ONT is consistent with the actual capability of the
ONT.
n
If Control flag is deactive, run the ont active command in GPON mode to
activate the ONU.
If Run state is offline, a physical line may be disconnected or the optical

module may be damaged. Check the line and the optical module.
If Config state is failed, the configured ONU capability exceeds the actual
ONU capability. In this case, run the display ont failed-configuration
command in the diagnose mode to check the failed configuration item and the
failure cause. Then, rectify the fault accordingly.
NOTE
If the ONT only supports 4 queues, the priority-queue parameter of the gem add command
is invalid when the priority-queue value is set to 4-7. Consequently Config state is failed.
n
Issue 01 (2016-04-29)
If the ONU does not match, that is, Match state is mismatch, the port types
and number of ports undermatch the actual port types and number of ports
supported by the ONU. In this case, run the display ont capability command
to query the actual capability of the ONU, and then select one of the following
modes to modify the ONU configuration:
Create a proper ONU profile according to the actual capability of the

ONU, and then run the ont modify command to modify the configuration
data of the ONU.
Modify the ONU profile according to the actual capability of the ONU
and save the modification. Then, the ONU automatically recovers the
configuration successfully.

674

Access Module
d.
Configure the Internet access service.

i.
Create an S-VLAN and add an upstream port to it.

The VlAN ID is 100, and the VLAN type is smart. Add upstream port 0/19/0
to smart VLAN 100.
ii.

Run the display traffic table ip command to query existing traffic profiles in
the system. If the traffic profiles existing in the system do not meet the
requirements, you need to run the traffic table ip command to add a traffic
profile.
Set the profile ID to 8, the CIR to 4 Mbit/s, and the priority to 1. In addition,
priorities.
huawei(config)#traffic table ip index 8 cir 4096 priority 1 prioritypolicy local-setting
iii. Create a service port.

Set the service port indexes to 1 and 2, S-VLAN ID to 100, and C-VLAN ID
to 10. The user PC is connected to EHT port 1 on the ONT. The traffic profile
8 is used.
NOTICE
The user PC is connected to the ONT port. Therefore, the user-side VLAN is
set to untagged.
huawei(config)#service-port 1 vlan 100 port 0/1/1 ont 1 eth 1 multiservice
user-vlan untagged inbound traffic-table index 8 outbound traffictable index 8
huawei(config)#service-port 2 vlan 100 port 0/1/1 ont 2 eth 1 multiservice
user-vlan untagged inbound traffic-table index 8 outbound traffictable index 8
e.
Configure the voice service.

i.

to smart VLAN 200.
ii.
Enable ARP proxy.

For different users of the same S-VLAN, because the service ports of the smart
VLAN are isolated from each other, the voice media streams cannot
interchange normally. The ARP proxy function of the OLT must be enabled so
that different users of the same VLAN can communicate with each other.
Issue 01 (2016-04-29)

675

Access Module
iii. Configure a traffic profile.

profile.
Set the profile ID to 9, the priority to 6 and no rate limitation on both the
upstream and downstream directions. In addition, configure the scheduling
mode so that packets are scheduled according to their priorities.
iv.
Create a service port.

Set the service port indexes to 3 and 4, S-VLAN ID to 200, and C-VLAN ID
to 20. The user phone is connected to the POTS port on the ONT. The traffic
profile 9 is used.
service
index 9
service
index 9
f.
200 port 0/1/1 ont 1 iphost multiindex 9 outbound traffic-table

200 port 0/1/1 ont 2 iphost multiindex 9 outbound traffic-table

i.

to smart VLAN 1000.
ii.

profile.
Set the profile ID to 10, the priority to 4 and no rate limitation on both the
upstream and downstream directions. In addition, configure the scheduling
mode so that packets are scheduled according to their priorities.
iii. Create a service port.

Set the service port indexes to 5 and 6, S-VLAN ID to 1000, C-VLAN ID to
30, and the ID of the ONT ETH port connected to the user STB to 2. The
traffic profile 10 is used.
NOTE
If the STB interconnected to the ONT does not support VLAN tag, the user-side VLAN is
set to untagged when creating service port.
service
index 10
service
index 10
Issue 01 (2016-04-29)
1000 port 0/1/1 ont 1 eth 2 multiindex 10 outbound traffic-table

1000 port 0/1/1 ont 2 eth 2 multiindex 10 outbound traffic-table

676

Access Module
iv.
Configure the IGMP version.

Set the IGMP version of the multicast VLAN to IGMPv3.
v.
Create a multicast VLAN and select the IGMP mode.

Set the multicast VLAN ID to 1000 and select the IGMP proxy mode.
vi. Configure a program library.

Configure the IP address of the multicast program to 224.1.1.10, program
name to program1, program source IP address to 10.10.10.10, and priority to 4.
huawei(config-mvlan1000)#igmp program add name program1 ip
224.1.1.10 sourceip 10.10.10.10 priority 4
vii. Configure a right profile.

Configure a profile named profile0, with the right of watching program 1.
program1 watch
viii. Configure multicast users.

Configure users of service ports 5 and 6 as multicast users and bind right
profile profile0 to the service ports.
huawei(config-btv)#igmp user bind-profile service-port 5 profilename profile0
huawei(config-btv)#igmp user bind-profile service-port 6 profilename profile0
g.
Save the data.

huawei(config)#save
Configure the ONT.

Configurations on the ONT are consistent with those in the profile mode.
----End
Result
l
Use the PPPoE dialup software to dial on the PC. After the dialup is successful, the user
can access the Internet.
Connect two phones to two TEL ports of different ONTs, and subscribers can use these
two phones to call each other.
The subscriber can watch program 1 on the TV.
9.7 Configuring FTTH Service (P2P Access)

Users connected to the OLT through an ONT, and are therefore provided with the Internet,
VoIP, and IPTV service through a same port.
Issue 01 (2016-04-29)

677

Access Module
l
ONT_1 and ONT_2 are provided with the triple play service through FTTH.
The Internet access service is provided in the PPPoE access mode.
The IPTV user connected to ONT_1 can watch all the programs, and the IPTV user
connected to ONT_2 can watch only program BTV-1.
The VoIP service and the IPTV service are provided in the DHCP mode and obtain IP
addresses from the DHCP server in the DHCP option-60 mode.
After receiving different traffic streams, the OLT provides different QoS guarantees to
the traffic streams according to the priorities of the traffic streams.
Traffic streams are differentiated on the OLT by the user-side VLAN (C-VLAN).
Figure 9-8 Example network of the optical fiber access service in the single-port for multiple
services mode
Table 9-6 Data plan for configuring the VLANs

Configuration Item
Data Item
Data
SVLAN
HSI service
SVLAN: 100
CVLAN: 2
IPTV service
SVLAN: 1000
CVLAN: 4
VoIP service
SVLAN: 200
CVLAN: 3
IPTV service data
Issue 01 (2016-04-29)
Multicast protocol
IGMP proxy
Multicast version
IGMP V3
Configuration mode of the

multicast program
Static configuration mode

678

Access Module
Configuration Item
Data Item
Data

server
10.10.10.10
Multicast DHCP server group
20.2.2.2
20.2.2.3
Multicast program
BTV-1: 224.1.1.10
BTV-2: 224.1.1.20
QoS (priority)
VoIP service data
HSI service
Priority: 1; queue scheduling:

WRR
IPTV service

WRR
VoIP service

PQ
VoIP DHCP server group
20.1.1.2
20.1.1.3
Prerequisite
l
The OLT is connected to the upper-layer devices such as the BRAS, multicast server,
SoftX3000, and DHCP server.
VLAN of the OLT.
Configure the Internet access service on the OLT.
Procedure
a.

The VLAN ID is 100, and the VLAN is a smart VLAN. The upstream port is
0/19/0.
b.

Because the VoIP, IPTV, and Internet access services are provided through the same
port, you must set the 802.1p priority of each service. Generally, the priorities are in
a descending order for the VoIP service, IPTV service, and Internet access service.
In this example, set the traffic profile index to 7 and the priority of the Internet
access service to 1.
c.
Configure a service port.

Add a service port to the VLAN and use traffic profile 7. The user-side VLAN ID is
2.
huawei(config)#service-port vlan 100 eth 0/5/2 multi-service user-vlan 2
rx-cttr 7 tx-cttr 7
Issue 01 (2016-04-29)

679

Access Module

rx-cttr 7 tx-cttr 7
d.

Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with the
weights of 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode.
NOTE
Queue scheduling is a global configuration. You need to configure queue scheduling only once on
the OLT, and then the configuration takes effect globally. In the subsequent phases, you need not
configure queue scheduling repeatedly when configuring other services.
huawei(config)#queue-scheduler wrr 10 10 20 20 40 0 0 0
Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map
queues 0-7 respectively.
huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5
cos6 6 cos7 7
NOTE
For the service board that supports only four queues, the mapping between 802.1p priorities and
queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue 2; priorities
4 and 5 map queue 3; priorities 6 and 7 map queue 4.
e.
Save the data.

huawei(config)#save
Configure the VoIP service on the OLT.

a.

The VLAN ID is 200, and the VLAN is a smart VLAN. The upstream port is0/19/0.
b.

The traffic profile index is 8, and the 802.1p priority of the VoIP service is 5.
c.

3.
rx-cttr 8 tx-cttr 8
rx-cttr 8 tx-cttr 8
d.

The VoIP service and the IPTV service are provided in the DHCP mode. The DHCP
option 60 domain is used to differentiate service types.
n
The DHCP domain of the VoIP service is voice.
The IP addresses of VoIP DHCP server group 1 are 20.1.1.2 and 20.1.1.3.
The IP address of the Layer 3 interface of VLAN 200 is 10.1.1.1/24.
The gateway IP address of the DHCP domain is 10.1.1.1/24.
huawei(config)#dhcp mode layer-3 option-60

Issue 01 (2016-04-29)

680

Access Module

NOTE
The DHCP option 60 domain of the Ethernet phone (Ephone) varies with the terminal type. In the
actual configuration, see the operation instructions of the Ephone.
e.
Save the data.

huawei(config)#save
Configure the IPTV service on the OLT.

a.

The VLAN ID is 1000, and the VLAN is a smart VLAN. The upstream port
is0/19/0.
b.

The traffic profile index is 9, and the 802.1p priority of the IPTV service is 4.
c.

4.
huawei(config)#service-port 200 vlan 1000 eth 0/5/2 multi-service uservlan 4 rx-cttr 9 tx-cttr 9
d.

The VoIP service and the IPTV service are provided in the DHCP mode. The DHCP
option 60 domain is used to differentiate service types.
n
The DHCP domain of the IPTV service is video.
The IP addresses of IPTV DHCP server group 2 are 20.2.2.2 and 20.2.2.3.
The IP address of the Layer 3 interface of VLAN 1000 is 10.2.2.1/24.
The gateway IP address of the DHCP domain is 10.2.2.1/24.
huawei(config)#dhcp mode layer-3 option60

NOTE
The DHCP option 60 domain of the set-top box (STB) varies with the terminal type. In the actual
configuration, see the operation instructions of the STB.
e.
Create a multicast VLAN and select the IGMP mode.

f.
Set the IGMP version.

Set the IGMP version of the multicast VLAN to IGMP v3.
Issue 01 (2016-04-29)

681

Access Module
g.

Configure the program names to BTV-1 and BTV-2, multicast IP addresses of the
programs to 224.1.1.10 and 224.1.1.20, source IP address of the programs to
10.10.10.10, and priority to 4.
huawei(config-mvlan1000)#igmp program add name BTV-1 ip 224.1.1.10
sourceip 10.10.10.10 priority 4
sourceip 10.10.10.10 priority 4
h.
Configure the right profile.

Configure the profile name to profile0, with the right of watching program BTV-1.
watch
i.
Configure the multicast users.

profile0
j.
Save the data.

huawei(config)#save
----End
Result
l
The Internet user can access the Internet in the PPPoE mode.
The VoIP user can make and receive phone calls.
The IPTV user connected to port 0/5/2 can watch all the programs, and the IPTV user
connected to port 0/5/3 can watch only program BTV-1.
Issue 01 (2016-04-29)

682

Access Module
10
10 FTTB and FTTC Configuration
FTTB and FTTC Configuration
About This Chapter

The FTTB and FTTC solution configuration guide describes how to configure typical
FTTB/C services (such as high-speed Internet access, multicast, and VoIP) on the OLT and
the ONU step by step through examples.
10.1 FTTB and FTTC Configuration Summary
FTTB and FTTC Configuration Guide is written based on solution scenarios, covering the
entire E2E service configuration process for the OLT, ONU, and HGW. This guide provides
guidance for service configuration in FTTB and FTTC involving the OLT and ONUs of
different models. The OLT is used in all service scenarios for FTTB and FTTC. Therefore,
OLT users can select the concerned scenarios. Different ONUs may be used in service
scenarios for FTTB and FTTC. Therefore, ONU users can see the following to select the
concerned scenarios.
10.2 Basic Concept
FTTB and FTTC solutions involve many concepts. This topic describes concepts involved in
FTTB and FTTC solutions from user side to network side based on the following integrated
FTTB and FTTC network diagram.
10.3 Principle of FTTB and FTTC Data Plan
This topic describes principles of data plan for various FTTB and FTTC networking diagrams
in terms of device management, QoS, services, and security. The examples in this topic are
based on these principles to plan data.
10.4 FTTB Networking (GPON Networking, LAN Access, Without HGW)
In this kind of networking, the ONU provides 100M FE access and POTS access for Internet
access service and VoIP service respectively for users. This topic describes how to configure
the Internet access service and VoIP service on the OLT and ONU in this networking.
10.5 FTTB/C Networking (GPON Networking, xDSL Access, Without HGW)
In this kind of networking, an optical network unit (ONU) supports x digital subscriber line
(xDSL) and plain old telephone service (POTS) access and provides Internet access and voice
over IP (VoIP) services. This topic describes the OLT and ONU configurations required for
commissioning Internet access and voice services.
10.6 FTTB/FTTC+HGW Networking (GPON Networking, Voice Service Provided by ONU)
The home gateway (HGW) provides Internet access and Internet Protocol television (IPTV)
services. The services are sent upstream to the optical network unit (ONU) over a local area
Issue 01 (2016-04-29)

683

Access Module
network (LAN) or x digital subscriber line (xDSL). The Integrated Access Device (IAD) in
the ONU provides voice services.
10.7 FTTB/FTTC+HGW Networking (GPON Networking, HGW Providing the VoIP
Service)
In this kind of networking, the HGW provides the Internet access and IPTV services. In
addition, the built-in IAD of the HGW provides the VoIP service by connecting to the
upstream ONU using LAN or xDSL.
10.8 FTTB and FTTC Ethernet Cascade Networking (ONU Works as an Independent NE)
Cascade a multi-dwelling unit (MDU) to an optical line terminal (OLT) using an Ethernet
access board, the MDU works as an independent NE. The following topics describe the
configuration method of this scenario.
10.9 FTTB and FTTC Ethernet Cascade Networking (ONU works as a GE remote extended
subrack)
Working with high bandwidth technologies, such as VDSL2 and Vectoring, GE remote
extended subracks provide high bandwidth access for users over existing copper line
networks. GE remote extended subracks can be connected to traditional VDSL2 modems to
provide Internet access and voice services for users; or be connected to home gateways
(HGWs) to provide Internet, voice, and IPTV services for home users.
Issue 01 (2016-04-29)

684

Access Module
10.1 FTTB and FTTC Configuration Summary

FTTB and FTTC Configuration Guide is written based on solution scenarios, covering the
entire E2E service configuration process for the OLT, ONU, and HGW. This guide provides
guidance for service configuration in FTTB and FTTC involving the OLT and ONUs of
different models. The OLT is used in all service scenarios for FTTB and FTTC. Therefore,
OLT users can select the concerned scenarios. Different ONUs may be used in service
scenarios for FTTB and FTTC. Therefore, ONU users can see the following to select the
concerned scenarios.
The following table lists GPON/10G GPON scenarios and the related information.
Service Scenario
ONU Supported
Remarks
FTTB Networking (LAN

Access Without HGW)
MA5616
l The MA5616 supports only LAN,

VDSL2, POTS, and ADSL2+
ports. Therefore, pay attention to
contents related to LAN, VDSL2,
POTS, and ADSL2+ only.
l The MA5612 and MA5878 support
only LAN and POTS ports.
Therefore, pay attention to LANand POTS-related contents only.
l The MA5811S series and MA5818
support only G.fast ports.
Therefore, pay attention to G.fastrelated contents only.
MA5612
MA5878
FTTB/C Networking
(xDSL Access, Without
HGW)
MA5616
FTTB/FTTC+HGW
Networking (Voice
Service Provided by
ONU)
MA5616
MA5603T
MA5612
MA5878
MA5603T
FTTB/FTTC+HGW
Networking (HGW
Providing the VoIP
Service)
MA5616
MA5612
MA5878
MA5811S series
MA5818
MA5603T
The following table lists Ethernet cascade scenarios and the related information.
Service Scenario
ONU Supported
Remarks
FTTB and FTTC

Ethernet Cascade
Networking (ONU
Works as an
Independent NE)
MA5616
l The MA5616 supports only LAN,

VDSL2, POTS, and ADSL2+
ports. Therefore, pay attention to
contents related to LAN, VDSL2,
POTS, and ADSL2+ only.
MA5811S series
MA5818
l The MA5811S series and MA5818

support only G.fast ports.
Therefore, pay attention to G.fastrelated contents only.
Issue 01 (2016-04-29)

685

Access Module
Service Scenario
ONU Supported
Remarks
FTTB and FTTC

Ethernet Cascade
Networking (ONU works
as a GE remote extended
subrack)
MA5623AR
NA
10.2 Basic Concept

FTTB and FTTC solutions involve many concepts. This topic describes concepts involved in
FTTB and FTTC solutions from user side to network side based on the following integrated
FTTB and FTTC network diagram.
Integrated FTTB and FTTC Network Diagram

Figure 10-1 Integrated FTTB and FTTC network diagram (PON)
PC
ONU
TV
PE-AGG
OLT
STB
NGN/IMS
UPE
Metro Network
Laptop
Splitter
Phone
STB
Internet
UPE
HGW
PC
IPTV
Headend
PE-AGG
ONU
TV
Phone
User Side
Access Side
Network Side
Figure 10-2 Integrated FTTB and FTTC network diagram (Ethernet cascading)
PC
ONU
STB
TV
FE/GE
FE/GE
Laptop
PE-AGG
OLT
NGN/IMS
UPE
Metro Network
IPTV
Headend
Phone
HGW
PC
STB
FE/GE
Internet
UPE
PE-AGG
ONU
TV
Phone
Issue 01 (2016-04-29)
User Side
Access Side

Network Side
686

Access Module
User Side
Concept
Introduction
HGW (or HG)
Home gateways (HGWs or HGs) are gateway devices designed for

households and small-office network users. They provide routing
functions, support various service interfaces (POTS, LAN, WLAN, or
xDSL interfaces), and support remote management and diagnosis.
VoD
Video on demand (VoD) is known as interactive video on demand.

Users can choose their desired programs from the VoD program
database. When watching programs, users can perform operations
such as pause, fast forward, fast rewind, and locate.
Multicast
Multicast, or broadband TV (BTV) is similar to traditional wired

broadcasting or television satellite broadcasting. Users have the same
experience in watching BTV programs and traditional television
programs. Unlike the traditional television, the IPTV system encodes
audio signals into media streams and multicasts the media streams
over an IP network to user terminals.
Concept
Introduction
PON
A passive optical network (PON) uses a point-to-multipoint (P2MP)

network architecture. A PON network consists of three parts: optical
line terminal (OLT), optical distribution network (ODN), and optical
network units (ONUs). A PON network uses optical fibers for data
transmission, supports more users with less optical fiber resources,
and provides a higher access rate.
Access Side
Mainstream PON technologies include broadband passive optical

network (BPON), Ethernet passive optical network (EPON), and
gigabit passive optical network (GPON).
ODN
The ODN is composed of passive optical components, such as optical

fibers and one or more passive optical splitters. The ODN provides
highly reliable optical channels between the OLT and ONUs.
OLT
The OLT is an aggregation device located at the central office (CO),

which terminates PON protocols. OLTs in this document are
MA5600T/MA5603T/MA5608T.
ONU
ONUs are located on the user side, providing various types of ports
for connecting to user terminals. The ONUs communicate with the
OLT through a passive ODN.
NOTE
ONUs in FTTB and FTTC networks refer to multi-dwelling units (MDUs).
Split Ratio
Issue 01 (2016-04-29)
Split ratio is the ratio of dividing a downstream optical signal into

subsignals in the PON system. Greater optical ratio requires more
power to support physical distances.

687

Access Module
Concept
Introduction
PTP Ethernet
cascading
On a point to point (P2P) Ethernet cascading network, the OLT uses

P2P Ethernet access board and optical terminal to provide FTTx
access to subscribers. The OLT can provide the combined service of
video, voice, and data to meet application requirements of nextgeneration access devices.
FTTB
Fiber to the building (FTTB) applies to medium- and high-density

apartments or office buildings. The OLT is connected to the ONU
(deployed in the corridor) through optical fibers, and the ONU is then
connected to users through twisted pairs to provide users with the
voice, data, and video services.
FTTC
Fiber to the curb (FTTC) applies to scattered apartments and

industrial parks. The OLT is connected to the ONU (deployed in the
hole at the curb or FAT on a telegraph pole) through optical fibers, and
the ONU is then connected to users through twisted pairs to provide
users with the voice, data, and video services.
NOTE
The difference between FTTB and FTTC is the ONU position. To simply
description, this document uses FTTB and FTTC, indicating that both FTTB
and FTTC networks are supported.
Network Side
Concept
Introduction
U-PE
User-end provider edges (U-PEs) are routing devices directly

connected to customer edges (UEs). U-PEs support routing and MPLS
encapsulation. If a U-PE is connected to multiple CEs and possesses
the basic bridging function, data frame forwarding only needs to be
performed on the U-PE. This reduces the load of the S-PE.
PE-AGG
Aggregation provider edge (PE-AGG) routers provide aggregation

and route forwarding functions for access equipment. Compared with
U-PEs, PE-AGGs features higher performance, fewer interfaces, and
higher switching rates.
NGN/IMS
A next generation network (NGN) is a network that uses softswitches

as its core and uses open and standardized architectures to provide
abundant services such as VoIP, video, and data.
The IP multimedia subsystem (IMS) uses SIP signaling as its call
control signaling to provide services such as VoIP, data, and
multimedia services.
NOTE
NGN/IMS in this document refers to softswitches that support H.248 and SIP.
IPTV Headend
Issue 01 (2016-04-29)
The IPTV headend system functions as the contents preparation

platform in the IPTV system. It provides functions such as signal
receipt, media format conversion, and media material management.

688

Access Module
10.3 Principle of FTTB and FTTC Data Plan

This topic describes principles of data plan for various FTTB and FTTC networking diagrams
in terms of device management, QoS, services, and security. The examples in this topic are
based on these principles to plan data.
10.3.1 Principle of Device Management Data Plan

The device management plan includes channel management plan and the IP address plan.
Plan
Device/Service
Introduction
Management
channel
OLT
Use a single S-VLAN as the equipment

management VLAN of the OLT and that of all
other equipment in the network.
ONU/MDU/GE
remote extended
subrack
Use a single S-VLAN as the equipment

management VLAN of the ONU and that of all
other equipment in the network.
HGW
Use a single S-VLAN as the management

VLAN of the HGW that are managed by the
items.
Set a management VLAN for an entire network,
an OLT, a PON board, or a PON port for
identifying services and physical locations. It is
recommended that you set different HGW
management VLANs for the OLTs connected to
one SR to avoid an excessively large broadcast
domain of the SR and convergence switch.
IP address
plan
Device management
It is recommended that you use private network

IP addresses as the management IP address of
the OLT and MDU for securing network
devices.
Internet access service
A PC obtains a public network IP address using

PPPoE dialup for Internet access.
The HGW obtains a public network IP address
using PPPoE dialup.
A PC obtains a private network IP address using
DHCP.
VoIP service
Issue 01 (2016-04-29)
If an MDU has a built-in voice module, the

MDU functions as a DHCP client and obtains IP
addresses using DHCP. Multiple POTS ports on
the MDU share one public network IP address.
If an HGW has a built-in voice module, the
HGW obtains IP address using DHCP.

689

Access Module
Plan
Device/Service
Introduction
IPTV service
An STB obtains a public network IP address

using DHCP and the subscriber can order
programs. The MDU is only used for transparent
transmission.
TR069 service
For scenarios in which TR069 is used for

management, maintenance, and service
provisioning, the HGW functions as a DHCP
client, obtains a public network IP address using
DHCP, and connects to the TR069 server (ACS).
10.3.2 QoS Planning Principles

QoS plan for FTTB is in E2E mode, and it can be divided into following policies: traffic
classification, marking, scheduling, traffic monitoring, and DBA policies.
Traffic Classification, Marking, and Scheduling Policies

Service
Type
802.1p
Priority
Queue
Scheduling
Method
OLT
Queue ID
(8 Queues)
ONT Queue ID
Supporting
Eight
Queues
Supporting
Four
Queues
Management
service
PQ
VoIP service
PQ
IPTV
service
PQ
Internet
access
service
PQ
Note
l
Different service packets are distinguished by different VLAN IDs. GEM ports are
mapped based on 802.1p priorities for the GPON system.
Service priorities in this table are recommended values. The service priorities are
arranged according to the operators' actual planning.
Issue 01 (2016-04-29)

690

Access Module
Traffic Monitoring and DBA Policies

Item
Management
Service
Internet
Access
Service
VoIP Service
IPTV Service
T-CONT (used
only in GPON
networks)
Use different T-CONTs for different services.
DBA type
Select a DBA type based on service types. For example, select Type1 for
the management and voice services, and Type3 or Type4 for the Internet
access and IPTV services.
DBA
bandwidth
planning
Configure the DBA bandwidth according to the user's bandwidth

package.
Rate limit on
OLT
downstream
No rate limit
Rate limit on
ONU uplink
port
Set ONU port rate limit or xDSL line rate limit as required. [Remark 1]
Rate limit on
ONU downlink
port
Set ONU port rate limit or xDSL line rate limit as required. [Remark 1]

bandwidth is greater than or equal to the maximum bandwidth that users
apply.
Configure rate
limit by a traffic
profile as
required.
[Remark 1]
No rate limit
No rate limit
Remark 1: For details about the reference service bandwidth of each service for each user, see
Table 10-1.
Issue 01 (2016-04-29)
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
Internet
access
service
Determi
ned
based on
the tariff
package.
Determined based
on the tariff package.
Available bandwidth of Internet access

service = Committed bandwidth of the tariff
package - VoIP bandwidth - IPTV
bandwidth

691

Access Module
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
VoIP
service
200
kbit/s
200 kbit/s

symmetrical. The actual bandwidth varies
with the coding format. This bandwidth is
calculated for two POTS ports.
IPTV
service
(commo
n
program
)
N/A
2.5 Mbit/s per

channel
IPTV
service
(high
definitio
n
program
)
N/A
9.7 Mbit/s per

channel

by one user (in the case of multi STBs
access). The upstream bandwidth is mainly
used for transmitting IGMP packets, which
requires little bandwidth and can be
neglected.
Note
l
Rate limit on the BRAS or SR is recommended. OLTs and ONUs do not limit rates on
service flows. If the BRAS does not support rate limit, OLTs can limit rates on service
flows using traffic profiles.
The sum of assured bandwidth of all ONTs under a PON port and the fixed bandwidth of
OMCI management channel must be smaller than the GPON upstream bandwidth. Some
bandwidth must be reserved for future service expansion.
10.3.3 Principle of Internet Access Service Data Plan

The Internet access service plan mainly includes the plan of the VLAN and VLAN translation
policy in different network scenarios.
Issue 01 (2016-04-29)

692

Access Module
VLAN Planning and VLAN Translation Policy on PON Networks

Application
Scenario
VLAN Plan
FTTB networking
(without HGWs)
Two-tagged
VLAN (S-VLAN
+C-VLAN)
FTTB/FTTC+HGW
networking (ONU
providing the VoIP
service)
FTTB/FTTC+HGW
networking (HGW
providing the VoIP
service)
VLAN Translation
ONU
OLT
The inner C-VLAN is

mapped based on user
ports to ensure that
ONUs under the same
PON board do not
have the same CVLAN.
The OLT translates

VLANs and adds an
S-VLAN. C'-VLAN
<-> S-VLAN + CVLAN
HGWs (LAN
upstream
transmission)
l Untagged
upstream packets
of HGWs: ONUs
map C-VLANs
based on user
ports.
l Tagged upstream
packets of HGWs:
ONUs translate
user VLANs to C'VLANs.
[Remark 1]
HGWs (xDSL
upstream
transmission): ONUs
translate PVCs to C'VLANs.
Note
l
To ensure traceability of users and finer-grained QoS control and management of users
and services, plan per user per service per VLAN (PUPSPV) for the Internet access
service. Considering OLT capacity and VLAN scalability, use dual VLANs (S-VLAN
+C-VLAN) on the OLT to differentiate users for the Internet access service.
The outer S-VLAN, which identifies services and physical location, can be allocated
based on the OLT, PON board (recommended), or PON port (recommended). The inner
C-VLAN identifies users. User C-VLANs are unique in one S-VLAN.
NOTE
It is recommended that you associate C-VLAN IDs with PON ports, optical splitters, and ONU
ports to ensure C-VLAN uniqueness and to facilitate location. Example: C-VLAN ID = 256 x
PON port ID + 32 x Split ratio x (Optical port ID - 1) + ONU port ID + 1
Issue 01 (2016-04-29)
It is recommended that you use stacking VLANs as S-VLANs so that security features,
such as PPPoE+/option 82, and anti-MAC attack, and anti-MAC spoofing can be easily
deployed.
693

Access Module
VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

Application
Scenario
VLAN
Plan
VLAN Translation
MDU/GE Remote Extended Subrack
OLT/
Master
Subrac
k
FTTB and FTTC

Ethernet cascading
(MDUs serving as
independent nodes)
Two-tag
VLAN
solution
Without HGWs: The outer S-VLAN is

planned based on MDUs and the inner CVLAN identifies a user. Ensure that the CVLANs of users using the same S-VLAN do
not repeat each other.
The
OLT
transmit
s
packets
transpar
ently.
LAN access using HGWs:

l Untagged upstream packets of HGWs:
MDUs map C-VLANs based on user
ports and add S-VLANs to packets.
l Tagged upstream packets of HGWs:
MDUs translate user VLANs to CVLANs (user VLAN <-> C-VLAN) and
add S-VLANs to packets.
xDSL access using HGWs:
l Asynchronous transfer mode (ATM)
upstream transmission: MDUs translate
PVCs to C-VLANs (PVC <-> C-VLAN)
and add S-VLANs to packets. Ensure
that the C-VLANs of users using the
same S-VLAN do not repeat each other.
l Packet transfer mode (PTM) upstream
transmission: Untagged upstream packets
of HGWs: MDUs map C-VLANs based
on user ports and add S-VLANs to
packets. Tagged upstream packets of
HGWs: MDUs translate user VLANs to
C-VLANs (user VLAN <-> C-VLAN)
and add S-VLANs to packets. Ensure
same S-VLAN do not repeat each other.
Issue 01 (2016-04-29)

694

Access Module
Application
Scenario
VLAN
Plan
FTTB and FTTC

Ethernet cascading
(centralized
management for GE
remote extended
subracks)
VLAN Translation
MDU/GE Remote Extended Subrack
OLT/
Master
Subrac
k
l Without HGWs: The extended subrack

maps inner C-VLANs based on user
ports and adds S-VLANs to packets.
Ensure that the C-VLANs of users using
the same S-VLAN do not repeat each
other.
The
master
subrack
transmit
s
packets
transpar
ently.
l xDSL access using HGWs:

ATM upstream transmission: The
extended subrack translates PVCs to
C-VLANs (PVC <-> C-VLAN) and
adds S-VLANs to packets. Ensure
same S-VLAN do not repeat each
other.
PTM upstream transmission:
Untagged upstream packets of
HGWs: The extended subrack maps
C-VLANs based on user ports and
adds S-VLANs to packets. UserVLAN-tagged upstream packets of
HGWs: The extended subrack
translates user VLANs to C-VLANs
(user VLAN <-> C-VLAN) and adds
S-VLANs to packets. Ensure that the
C-VLANs of users using the same SVLAN do not repeat each other.
10.3.4 (Optional) Principle of Vectoring Data Plan

Vectoring data plan includes grouping, the policy for activating a legacy customer premises
equipment (CPE), and line profile planning of a port.
Issue 01 (2016-04-29)

695

Access Module
Item
Description
Grouping
In vectoring network planning, grouping is a key phase.

Accurate grouping cancels inter-line crosstalk to the largest
extent and develops vectoring advantages.
l It is recommended that you learn the actual physical routing
beforehand. Crosstalk between lines in a bundle reaches the
maximum value. Therefore, it is better to plan members in a
vectoring group the same as actual routing.
l If you do not know actual routing in the system, you cannot
group. In this case, you can use the default global grouping.
Then, you can add all lines supporting vectoring to default
vectoring group 1.
Policy for activating a

legacy customer
premises equipment
(CPE)
A legacy CPE is a VDSL2 CPE that supports G.993.2 but does

not support G.9930.5 or vectoring. If such a CPE is activated by
G.993.2 in the vectoring system, it affects lines and the
performance of the vectoring system deteriorates. Therefore,
configure the policy for activating a vectoring legacy CPE based
on site requirements to reduce the effect to minimum. The
system supports three activation polices. The default policy is
limit.
l No-limit: The legacy CPE can be activated in the common
VDSL2 mode. That is, the legacy CPE is activated in the
non-Vectoring mode and the performance of the Vectoring
system is affected. This activation policy is generally used in
the initial stage of Vectoring applications. In this stage, a lot
of CPEs need to be upgraded or replaced and the Vectoring
performance is not mostly concerned.
l Limit: The legacy CPE can be activated in the common
VDSL2 mode; however, the line is automatically shaped by
power spectrum density (PSD) and is activated by low-speed
VDSL2 to prevent other lines from being affected. This
activation policy is generally used in the medium stage of
Vectoring applications. In this stage, some CPEs are not
upgraded or replaced. This is the system default policy.
l Force-friendly-ds-limit-us: force friendly is used in the
downstream direction and PSD automatic shaping is used in
the upstream direction.
l Force-friendly-ds-no-limit-us: force friendly is used in the
downstream direction and no restriction is used in the
upstream direction.
l Block: The legacy CPE cannot be activated in the common
VDSL2 mode (G.993.2). If a legacy CPE needs to be
activated in G.993.2 mode, you need to delete it from the
Vectoring group first. This activation policy is generally used
in the mature stage of Vectoring applications. In this stage,
the Vectoring performance is concerned and unnecessary
crosstalk is better to be masked.
Issue 01 (2016-04-29)

696

Access Module
Item
Description
Line profile of a port
The maximum rate in the line profile bound to a port is the target
value for vectoring rate improvement. Carriers need to plan the
line profile based on services.
10.3.5 Principle of VoIP Service Data Plan

The VoIP service plan mainly includes the plan of VLANs and VLAN translation policy in
different network scenarios, and the plan of voice protocols.
VLAN Planning and VLAN Translation Policy on PON Networks

Application
Scenario
VLAN
Plan
VLAN Translation
ONU
OLT
FTTB
networking
(without
HGWs)
Singletagged
VLAN
ONUs provide
the VoIP service
and use the same
S-VLAN.
Transparently
transmits packets.
FTTB+HGW
networking
(ONU
providing the
VoIP service)
Singletagged
VLAN
ONUs provide
the VoIP service
and use the same
S-VLAN.
Transparently
transmits packets.
This solution is
recommended.
Doubletagged
VLAN (SVLAN+CVLAN)
ONUs provide
the VoIP service
and use the same
C-VLAN.
The OLT adds

one S-VLAN tag:
C-VLAN <-> SVLAN+CVLAN.
This solution is
used only when
double-tagged
VLANs are
planned.
FTTB+HGW
networking
(HGW
providing the
VoIP service)
Singletagged
VLAN
When packets
sent from the
HGW using LAN
upstream
transmission
carries user
VLANs, the
ONU translates
user VLANs to
C-VLANs.
Transparently
transmits packets.
This solution is
recommended.
The OLT adds

one S-VLAN tag:
C-VLAN <-> SVLAN+CVLAN.
This solution is
used only when
double-tagged
VLANs are
planned.
Doubletagged
VLAN (SVLAN+CVLAN)
Remarks
HGWs (xDSL
upstream
transmission):
ONUs translate
PVCs to C'VLANs.
Issue 01 (2016-04-29)

697

Access Module
Note
l
The VoIP service is a closed service self-operated by carriers. The single-tagged SVLAN is the mainstream application and is recommended.
Set an S-VLAN for an entire network, an OLT, a PON board, or a PON port for
identifying services and physical locations. It is recommended that you set different VoIP
VLANs for the OLTs connected to one VoIP SR to avoid an excessively large broadcast
domain of the VoIP SR and convergence switch.
The outer S-VLAN, which identifies services and physical locations, can be allocated
based on the OLT, PON board, or PON port. The inner C-VLAN identifies services or
users.
VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

Application
Scenario
VLAN
Plan
VLAN Translation
MDU/GE Remote
Extended Subrack
OLT/Master Subrack
FTTB or FTTC
Ethernet cascading
(MDUs serving as
independent nodes)
One-tag
VLAN
solution
Without HGWs and with

voice services provided
by the MDU: Each MDU
uses the same S-VLAN
for its voice users.
The OLT transmits

packets transparently.
LAN access with voice

services provided by
HGWs: MDUs translate
user VLANs to CVLANs.
xDSL access with voice
HGWs:
l ATM upstream
transmission: MDUs
translate PVCs to CVLANs (PVC <-> CVLAN).
l PTM upstream
transmission:
Untagged upstream
packets of HGWs:
MDUs map C-VLANs
based on user ports.
User-VLAN-tagged
upstream packets of
HGWs: MDUs
translate user VLANs
to C-VLANs (user
VLAN <-> C-VLAN).
Issue 01 (2016-04-29)

698

Access Module
Application
Scenario
VLAN
Plan
FTTB or FTTC
Ethernet cascading
(centralized
management for GE
remote extended
subracks)
VLAN Translation
MDU/GE Remote
Extended Subrack
OLT/Master Subrack
xDSL access with voice

HGWs:
The master subrack

transmits packets
transparently.
l ATM upstream
transmission: The
extended subrack
translates PVCs to CVLANs (PVC <-> CVLAN).
l PTM upstream
transmission:
Untagged upstream
packets of HGWs: The
extended subrack
maps C-VLANs based
on user ports. UserVLAN-tagged
upstream packets of
HGWs: The extended
subrack translates user
VLANs to C-VLANs
(user VLAN <-> CVLAN).
VoIP data plan based on H.248 or SIP

Item
MG
interface/SI
P interface
data
NOTE
(Must be
the same as
that on the
MGC or
IMS core
network
device.)
Issue 01 (2016-04-29)
Remarks
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLAN
Upstream VLANs of the VoIP service
Media and
signaling
upstream port
Upstream ports of the VoIP service
Media IP address
and signaling IP
address
Separating media streams from signaling

streams
Default IP address
of the MG
Next hop IP address from an ONU/HGW to

an MGC/IMS
Signaling port ID
Choose the transmission method according

to the requirement on the MGC/IMS side.

699

Access Module
Item
Remarks
IP address of primary MGC
(H.248)/IP address of primary
IMS device (SIP)
Port ID of primary MGC
(H248)/port ID of primary
IMS device (SIP)
VoIP user
configuratio
n data
When dual homing is not configured, the

parameters of the primary MGC need to be
configured. When dual homing is
configured, the IP address and the port ID
of the secondary MGC must also be
configured.
Codec mode
The codec mode is selected according to

the requirements on the MGC/IMS side.
Generally, the text mode is used.
Transmission mode
The transmission mode is selected

according to the requirements on the
MGC/IMS side. Generally, UDP is used.
Home domain name (SIP)
Profile index (SIP)
H.248 version used for

starting negotiation
V1, V2 or V3 (default value). The interface

may fail to register because some
Phone number
H.248: The phone numbers allocated by the

MGC need to be determined, and the
paging numbers for users' emergency
standalone need to be planned if the
emergency standalone function is provided.
SIP: The phone number that the IMS core
network device allocates to the user must
be configured.
TID (H.248)
If the TID template with which the PSTN

configured.
User priority

government users)
government users)
l cat3: normal (common users). This is
the default value.
Issue 01 (2016-04-29)

700

Access Module
Item
Remarks
User type

Common
Parameter
System parameter
The system parameters, including the

international version flag and message
waiting indication (MWI) mode, need to be
configured according to local standards to
ensure that the response of the user terminal
complies with the local standards.
International parameters

standards.
If the PSTN port needs to support the

polarity reversal accounting, the PSTN port
polarity reversal pulse. Other attributes do
not need to be modified if there is no
special requirement.

changed, ring volume is changed. This
parameter needs to be modified according
to the local standard only when the default
ring current attribute does not comply with
the local standard.

The IPTV service plan mainly includes the plan of VLANs and VLAN translation policies in
different network scenarios, and the plan of IPTV services.
IPTV services include multicast service and VoD service. These two services have
relationships and independence in VLAN planning.
Issue 01 (2016-04-29)

701

Access Module
VLAN and VLAN translation policy

Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
OLT
Scenario 1:
FTTB
+HGW
networking
(ONU
providing
the VoIP
service)
Multic
ast
service
Onetagged
VLA
N
1. The multicast
VLAN
(MVLAN) of the
HGW is
different from
the network-side
MVLAN.
l Upstream
IGMP: The
OLT
performs
IGMP proxy
to terminate
IGMP
packets
transmitted
from the user
side and
encapsulate
IGMP
packets
transmitted
by networkside
MVLANs.
and
Scenario 2:
FTTB
+HGW
networking
(HGW
providing
the VoIP
service)
l Upstream
IGMP: The
ONU
performs
IGMP proxy
to terminate
IGMP
packets
transmitted
from the user
side and
encapsulate
IGMP
packets
transmitted
by networkside
MVLANs.
l Downstream
multicast
service flows:
The ONU
replicates
multicast
packets based
on user ports
and
multicasts
downstream
multicast
packets
across
VLANs: user
VLAN <->
MVLAN
Issue 01 (2016-04-29)
Remarks
This solution is
recommended
because carriers
will define a
unified MVLAN
on the HGW.
l The OLT
replicates
multicast
packets
based on
PON ports
with
MVLANs
unchanged.

702

Access Module
Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
OLT
Multic
ast
VoD
service
Onetagged
VLA
N
VLAN
translation
policy:
Transparently
transmits
packets.
l When
packets sent
from the
HGW using
LAN
upstream
transmission
carries user
VLANs, the
ONU
translates
user VLANs
to C-VLANs.
Remarks
This solution is
recommended.
The PSPV mode
is recommended
for the VoD
service because
the service
requires fewer
VLANs.
l When
packets are
sent from the
HGW using
xDSL
upstream
transmission,
the ONU
translates
PVCs to CVLANs.
Issue 01 (2016-04-29)

703

Access Module
Issue 01 (2016-04-29)
Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
OLT
FTTB or
FTTC
Ethernet
cascading
(MDUs
serving as
independent
nodes)
Multic
ast
service
Onetag
VLA
N
soluti
on
l Upstream
IGMP
packets: The
MDU
performs
IGMP proxy
to terminate
IGMP
packets
transmitted
from the user
side,
encapsulate
the packets
with an
MVLAN tag
on the
network side,
and send the
packets
upstream.
l Upstream
IGMP
packets: The
OLT
performs
IGMP proxy
to terminate
IGMP
packets
transmitted
from the user
side,
encapsulate
the packets
with an
MVLAN tag
on the
network side,
and send the
packets
upstream.
l Downstream
multicast
service flows:
The MDU
replicates
multicast
packets based
on user ports
and
multicasts
downstream
packets
among
MVLANs.
l Downstream
multicast
service
flows: The
OLT
replicates
multicast
packets
based on GE
ports with
MVLANs
unchanged.

Remarks
This solution is
recommended.
704

Access Module
Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
OLT
Multic
ast
VoD
service
Onetag
VLA
N
soluti
on
HGWs (LAN
upstream
transmission):
MDUs translate
user VLANs to
C-VLANs (user
VLAN <-> CVLAN).
The OLT
transmits
packets
transparently.
Remarks
This solution is
recommended.
HGWs (xDSL
upstream
transmission):
l ATM
upstream
transmission:
MDUs
translate
PVCs to CVLANs
(PVC <-> CVLAN).
l PTM
upstream
transmission:
Untagged
upstream
packets of
HGWs:
MDUs map
C-VLANs
based on user
ports. UserVLANtagged
upstream
packets of
HGWs:
MDUs
translate user
VLANs to CVLANs (user
VLAN <->
C-VLAN).
Issue 01 (2016-04-29)

705

Access Module
Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
OLT
FTTB or
FTTC
Ethernet
cascading
(centralized
management
for GE
remote
extended
subracks)
Multic
ast
service
Onetag
VLA
N
soluti
on
HGWs (xDSL
upstream
transmission)
when MVLANs
on HGW side
and network side
are different:
l Upstream
IGMP
packets: The
master
subrack
performs
IGMP proxy
to terminate
IGMP
packets
transparently
transmitted
from the
extending
board and
reported by
the extended
subrack,
encapsulate
the packets
with an
MVLAN tag
on the
network side,
and send the
packets to the
upper-layer
network.
l Upstream
IGMP
packets: The
extended
subrack
performs
IGMP proxy
to terminate
IGMP
packets
transmitted
from the user
side,
encapsulate
the packets
with an
MVLAN tag
on the
network side,
and send the
packets to the
extending
board.
l Downstream
multicast
service flows:
The extended
subrack
replicates
multicast
packets based
on user ports,
and
multicasts the
packets
among
MVLANs
(user VLAN
<- MVLAN).
Issue 01 (2016-04-29)
Remarks
This solution is
recommended.
l Downstream
multicast
service
flows: The
control board
in the master
subrack
replicates
multicast
packets
based on
Ethernet
extending
boards, and
the Ethernet
extending
boards
replicate
multicast
packets

706

Access Module
Applicatio
n Scenario
Servic
e
Type
VLA
N
Plan
VLAN Translation
ONU
Remarks
OLT
based on GE
ports with
MVLANs
unchanged.
Multic
ast
VoD
service
Onetag
VLA
N
soluti
on
HGWs (xDSL
upstream
transmission):
l ATM
upstream
transmission:
The extended
subrack
translates
PVCs to CVLANs
(PVC <-> CVLAN).
The master
subrack
transmits
packets
transparently.
This solution is
recommended.
l PTM
upstream
transmission:
Untagged
upstream
packets of
HGWs: The
extended
subrack maps
C-VLANs
based on user
ports. UserVLANtagged
upstream
packets of
HGWs: The
extended
subrack
translates
user VLANs
to C-VLANs
(user VLAN
<-> CVLAN).
Note
l
Issue 01 (2016-04-29)
IPTV service is a closed service self-operated by carriers, and one-tagged S-VLAN is

recommended.
707

Access Module
The same S-VLAN or different S-VLANs can be used as the MVLAN and VoD VLAN.
It is recommended that you use different S-VLANs as MVLAN and VoD VLAN so that
the upper-layer device can easily differentiate the BTV service and VoD service.
S-VLANs of VoD service can identify services and physical locations based on an entire
network or an OLT. It is recommended that you set different VoD VLANs for the OLTs
connected to one IPTV SR to avoid an excessively large broadcast domain of the SR and
convergence switch.
Data plan for multicast service

Data Item
Remarks
Multicast protocol
The OLT and ONU generally use IGMP proxy. The ONT or
HGW generally uses IGMP snooping.
IGMP version
The compatibility policies of the IGMP version on access

equipment distinguish between the network side and the user
side.
1. In normal application scenarios, the device is usually the
active initiating party. The IGMP version on the multicast
router can be seamlessly degraded without packet loss.
2. The terminals are always the active initiating party and can
be seamlessly degraded without packet loss.
The recommended versions are as follows:
l If the network-side version is V2, the recommended version
for the access equipment is V2.
l If the network-side version is V3, the recommended version
for the access equipment is V2 or V3.
l If the user-side version is V2, the recommended version for
the access equipment is V2 or V3.
l If the user-side version is V3, the recommended version for
the access equipment is V3.
Issue 01 (2016-04-29)
Multicast program
Static configuration is recommended. The OLT can also

generate a multicast program library. In other words, the OLT
dynamically generates a program list according to the programs
requested by users. In this mode, the program list does not need
to be configured or maintained; however, the functions such as
program management, user multicast bandwidth management,
program preview, and program prejoin are not supported.
Multicast preview
profile
Default
Multicast fast leave
Enabling this function is recommended. It reduced the exchange

of IGMP packets, saving the bandwidth resources.

708

Access Module

NOTE
l The device provides complete security measures, but not all security measures need to be deployed. Only
the security measures that meet the following requirements need to be deployed:
l
The security measures can be used on the live network.
The security measures are easy to deploy.
The security measures are effective.
l Different ONUs support different security features. Select the security feature recommended in this topic
according to actual ONU capabilities.
System Security
Security
Vulnerability
Solution

Suggestion
DoS attack

function for OLT and
MDU.

deployment.
IP attack

MDU.

deployment.
Issue 01 (2016-04-29)

709

Access Module
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing
Enable the anti-MACduplicate function for OLT

and MDU.
malicious attacks.
deployment.
MAC attack
Enable the anti-MAC

spoofing function for OLT
and MDU.

malicious attacks.
deployment.
IP spoofing

function for MDU.

malicious attacks.
deployment.
Issue 01 (2016-04-29)

710

Access Module
Service Security
Security
Vulnerability
Solution

Suggestion
Unauthorized
broadband access of
small enterprises
(IPoE)

on OLT and MDU, and the
BRAS implements user
RAIO information.

exhaustion.
DHCP addresses.
spoofing.
Broadband access of
residential users
(PPPoE), user
account theft/
borrowing

binding of the RAIO
account.

spoofing.
10.4 FTTB Networking (GPON Networking, LAN Access,

Without HGW)
In this kind of networking, the ONU provides 100M FE access and POTS access for Internet
access service and VoIP service respectively for users. This topic describes how to configure
the Internet access service and VoIP service on the OLT and ONU in this networking.
Issue 01 (2016-04-29)

711

Access Module
Context
There are two xPON configuration modes: distributed mode (also called discrete mode) and
profile mode. The difference between the two modes lies in command lines.
l
Distributed mode: In this mode, ONUs need to be configured one by one but not in
batches.
Profile mode: In this mode, an ONU line profile and service profile are configured first.
Then, ONUs can be added in batches by binding profiles. This mode greatly improves
service provisioning efficiency.
Generally, the xPON configuration mode is determined in a new deployment on the OLT and
will not be changed.
NOTE
For commands for the distributed configuration mode, see PON distributed-mode commands in the OLT
Command Reference.
The description of this topic is based on the mode below.

Mode
Query Method
GPON profile mode (system

default)
On the OLT:
huawei(config)#diagnose
huawei(diagnose)%%display xpon mode
------------------------------------------Current config mode: Profile-mode
-------------------------------------------
10.4.1 Service Requirements and Application Scenarios

FTTB networking is usually used in trade estate and housing estate having high-density
buildings and users. In FTTB networking, optical fibers are connected from the central office
(CO) to buildings. The network section from the service convergence nodes to users is
deployed by xDSL or LAN access. LAN access is easily and commonly deployed and
therefore becomes the first choice for bandwidth construction.
Only Internet access service and VoIP service are needed and there is no multicast
requirement.
Considering simple and flexible service provisioning and easy OM, category-5 cables and
FTTB (LAN access) are used for deployment.
Application Scenarios
As shown in Figure 10-3, the ONU is deployed in the building and is connected to the user's
home through the category-5 cable.
l
For the Internet access service: Users are connected to the ONU through category-5
cables and are authenticated by dialup using PCs. Each user has an independent account
and is authenticated and managed on the BRAS.
For the VoIP service: Users are provisioned with the VoIP service through the ONU with
the build-in voice module.
Issue 01 (2016-04-29)

712

Access Module
ONU for FTTB networking: MA5616, MA5612, MA5878.

Figure 10-3 Example network of the FTTB service (LAN access)
PE-AGG
OLT
LAN
NGN/IMS
UPE
PC
S
OT
ONU
Metro Network
Optical
splitter
Phone
PC
TS
PO
Internet
UPE
LAN
PE-AGG
ONU
Phone
10.4.2 Configuration Procedure

Figure 10-4 shows the configuration roadmap diagram in the FTTB and FTTC networking
scenarios using LAN access without HGWs.
Figure 10-4 Configuration Roadmap Diagram in the FTTB and FTTC Networking Scenarios
Using LAN Access Without HGWs
Issue 01 (2016-04-29)

713

Access Module
The following table lists the detailed description steps..

Item
Procedure
Remarks
OLT
Add an ONU to the OLT.
Services can be configured for an ONU only

after the ONU is successfully added to an
OLT.
Configure the
management channel
between the OLT and
the ONU.
After the inband management channel

between the OLT and the ONU is configured
and available, you can log in to the ONU
from the OLT to configure the ONU.
Configure the service

channel between the
OLT and the ONU.
Service channels, such as Internet access

service channel, are set up on the OLT so that
services on the ONU can be normally
forwarded.
Configure the Internet

access service.
This topic describes how to configure the

Internet access service through the Ethernet
port by the ONU. Specifically, configure
service flows on the ONU and configure the
upstream VLAN to provide the service
channel from the ONU to the user and set up
the upstream channel from the ONU to the
OLT.
Configure the VoIP

service
NOTE
The H.248 and SIP protocols are mutually
exclusive for the VoIP service. Only one of them
is configured at a time.
ONU
Configure the link

aggregation, congestion
control, and security
policy.
The global configuration of upstream link

aggregation and queue scheduling based on
priorities ensures service reliability. The
ONU
Verify the service.
The ONU provides remote verification

methods including PPPoE dialup emulation
and call emulation for configuration and
commissioning engineers to verify services
remotely after service configuration,
avoiding a second on-site operation.
ONU
OLT
10.4.3 Adding an ONU to an OLT

Services can be configured for an ONU only after the ONU is successfully added to an OLT.
Context
l
Issue 01 (2016-04-29)
When an ONU is added, desired profiles, including the dynamic bandwidth allocation
(DBA) profile, line profile, and alarm profile, must be bound to the ONU. For details
about functions and configuration methods for these profiles, see Table 10-2.
714

Access Module
Table 10-2 Introduction to ONU profiles

Profile
Type
Function
Command
DBA
profile
A DBA profile describes

GPON traffic parameters. A TCONT is bound to a DBA
profile for dynamic bandwidth
allocation, improving upstream
bandwidth utilization.
Query a DBA profile. display dbaprofile
A line profile describes

binding between the T-CONT
and the DBA profile, the QoS
mode of the service flow, and
mapping between the GEM
port and the ONU-side service.
Query a line profile. display ontlineprofile
An alarm profile contains a

series of alarm threshold
parameters that are used for
performance measurement and
monitoring of the activated
ONT lines.
Query an alarm profile. display gpon

alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)
Add a DBA profile. dba-profile add
Add a line profile. ont-lineprofile add
Add an alarm profile. gpon alarmprofile add
An ONU can be added in two modes. Select either mode as required.

Mode
Usage Scenario
Command
Add an
ONU
offline.
The ONU password or serial

number (SN) is obtained.
Run the ont add command to add an

ONU.
Online
confirm
an ONU.
Both the ONU password and

SN are not obtained.
In the GPON mode, run the port ontauto-find command to enable the
ONU auto-discovery function of a
GPON port and then run the ont
confirm command to add an ONU.

715

Access Module
Data Plan
Table 10-3 Data plan
Item
Data
DBA profile
NOTE
All configuration items are provided here. Select desired ones
based on service types.
l Profile name: fttb_dba_mngt

Profile type: Type1
Fixed bandwidth: 1 Mbit/s
l Profile name: fttb_dba_voip
Profile type: Type1
l Profile name: fttb_dba_hsi
Profile type: Type4
Maximum bandwidth: 512 Mbit/s
l Profile name: fttb_dba_vod
Profile type: Type3
Assured bandwidth: 8 Mbit/s
l Profile name: fttb_dba_iptv
Profile type: Type3
NOTE
Line profile
Profile name: fttb(c)

Profile ID: 10
T-CONT ID used by the management service: 4
T-CONT ID used by the voice service: 5
T-CONT ID used by the Internet access service: 6
T-CONT ID used by the VoD service: 7
T-CONT ID used by the IPTV service: 8
PON port: 0/2/1

ONT ID: 1
Procedure
Step 1 Configure GPON ONU profiles.
Issue 01 (2016-04-29)

716

Access Module
NOTE
All configuration items are provided here. Select desired ones based on service types.
1.

max 16384
max 16384
2.
add
add
add
add
profile-name
profile-name
profile-name
profile-name
fttb_dba_mngt type1 fix 1024

fttb_dba_voip type1 fix 4096
fttb_dba_hsi type4 max 524288
fttb_dba_vod type3 assure 8192
add profile-name fttb_dba_iptv type3 assure 8192
Configure an ONU line profile.

a.
Add GPON ONU line profile 10 fttb(c).

huawei(config)#ont-lineprofile gpon profile-id 10 profile-name fttb(c)
NOTE
The ID of the line profile to be created must not exist in the system, and the line profile must be
created according to the data plan. In this example, line profile 10 is used.
b.
In the line profile mode, bind the T-CONT to the DBA profile.
huawei(config-gpon-lineprofile-10)#tcont
c.
4
5
6
7
8
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
fttb_dba_mngt
fttb_dba_voip
fttb_dba_hsi
fttb_dba_vod
fttb_dba_iptv
In the line profile mode, create a GEM port for each T-CONT.
QoS policies must be configured for various service flows. For details about QoS
data plan, see 10.3.2 QoS Planning Principles.
//Create
GEM port 11 for T-CONT 4. Use the same method to create other GEM ports.
//Create
two GEM ports for the Internet access service. The reason is as follows:
Each GEM port maps up to 8 ONU-side service flows, and a total of 16
Internet access service flows are configured on the ONU in the following
section.
d.
Configure mapping between the GEM port and the ONU-side service.
Set the mode for mapping a GEM port to an ONU-side service to VLAN (default
mode). Map management service flows with C-VLAN 8 to GEM port 11, voice
service flows with C-VLAN 200 to GEM port 12, Internet access service flows with
C-VLANs 1001-1016 to GEM ports 13 and 14, VoD service flows with C-VLAN
300 to GEM port 15, and IPTV service flows with C-VLAN 1000 to GEM port 16.
......
......
e.
mapping 11 0 vlan 8
mapping 12 1 vlan 200
After the configuration is completed, run the commit command to make the
configured parameters take effect.
Issue 01 (2016-04-29)

717

Access Module
3.
The ID of the default GPON alarm profile is 1. The thresholds for all the alarm
parameters in the default alarm profile are 0, which indicates that no alarm is
generated.
In this example, the default alarm profile is used and therefore the configuration of
Step 2 Add an ONU to an OLT.

Assume that the ID of GPON port 0/2/1 is 1, SN is 32303131B39FD641, management mode
is SNMP, and the bound line profile is fttb(c). Connect the ONU to such a GPON port through
the optical splitter.
There are two modes to add an ONT: add an ONT offline and confirm an automatically
discovered ONU.
l
Add an ONU offline.

huawei(config-if-gpon-0/2)#ont add 1 ontid 1 sn-auth 32303131B39FD641
snmp ont-lineprofile-name fttb(c)
Confirm an automatically discovered ONU.

huawei(config-if-gpon-0/2)#ont confirm 1 ontid 1 sn-auth 32303131B39FD641
1.
(Optional) Bind the alarm profile to the ONU.

By default, alarm profile 1 automatically bound to an ONU. A non-default alarm profile
is bound manually only when the default one does not meet the requirement.
In this example, default alarm profile 1 is used and therefore the configuration of the
alarm profile is not required.
Step 3 Check the ONU status.

After an ONU is added, run the display ont info command to query the current status of the
ONU. Ensure that Config flag of the ONU is active, Run State is online, and Config state is
normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
//The ONU is activated.
Run state
: online
//The ONU is online.
Config state
: normal
//The ONU configurations are recovered
normally.
...//The rest of the response information is not provided here.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

718

Access Module
If the ONU does not match (Match state is mismatch), the port types and number of
ports do not match the actual port types and number of ports supported by the ONU. In
10.4.4 Configuring the Management Channel Between the OLT

and the ONU
After the inband management channel between the OLT and the ONU is configured and
available, you can log in to the ONU from the OLT to configure the ONU.
Data plan
Item
Data
Remarks
Management VLAN
and management IP
address on the OLT
side
Management VLAN ID: 8
Management VLAN
and management IP
address on the ONU
side
To configure the MDU from the OLT

by remote logging in to the MDU, the
management VLAN of the OLT and
that of the MDU must be the same,
and the management IP address of the
OLT and that of the MDU must be in
the same network segment.
Management VLAN type:

smart VLAN
Inband management IP
address: 192.168.50.1/24

smart VLAN
address: 192.168.50.2/24
Procedure
Step 1 Configure the inband management VLAN and IP address of the OLT.
Configure the inband management VLAN to 8, VLAN priority to 6, and the IP address to
192.168.50.1/24.
huawei(config)#vlan priority 8 6
Step 2 Configure the inband management VLAN and IP address of the ONU.
Issue 01 (2016-04-29)

719

Access Module
Configure the static IP address of the ONU to 192.168.50.2/24, gateway to 192.168.50.254,

and the management VLAN ID to 8 (the same as the management VLAN of the OLT).
255.255.255.0 gateway
192.168.50.254 vlan 8
Step 3 Configure an inband management service port.

Configure the management service port ID to 1, management VLAN ID to 8, GEM port ID to
11, and user-side VLAN ID to 8. The OLT does not limit inband management service flows.
Therefore, it is recommended that you use default traffic profile 6.
huawei(config)#service-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 11 multi-service
Step 4 Confirm that the management channel between the OLT and the ONU is available.
l
On the OLT, run the ping 192.168.50.2 command to check the connectivity between the
OLT and the ONU. The ICMP ECHO-REPLY packet from the ONU should be received.
On the OLT, you can remote log in to the ONU to perform the configuration.
----End
10.4.5 Configuring the Service Channel Between the OLT and the
ONU
Various service flows can be configured on the OLT for different services so that service
packets on the ONU can be forwarded at Layer 2 according to the planned VLAN and
forwarding policies.
Context
Service flows can be added in two modes, as described in Table 10-4. Select either mode as
required.
Table 10-4 Adding service flows
Issue 01 (2016-04-29)
Mode
Command
Remarks
Add service flows

one by one.
service-port
Add service flows

in batches.
multi-service-port
You need to specify the ontid +

gemindex to identify a service
flow and ensure that the number of
GEM ports is the same as the
number of VLANs on the user
side.

720

Access Module
Data plan
Item
Data
Remarks
Internet access
service
OLT VLAN ID:
Assume that the split ratio of the

optical splitter is 1:32, the ONU is
connected to port 1 on the optical
splitter using the optical cable, and
the user PC is connected to port 1
on the ONU. In this case, the inner
VLAN is 258 according to the
formula for calculating the inner
VLAN.
l CVLAN ID: 256 x GPON

port ID + 32 x Split ratio x
(Splitter port ID - 1) +
ONU port ID + 1
l SVLAN: VLAN ID 100
and attribute stacking
Upstream VLANs of the
ONU: 1001-1016
VoIP service
Service flow ID: 101
For details about the data plan, see

10.3.3 Principle of Internet
Access Service Data Plan.
OLT VLAN ID (VLAN

transparently transmitting the
ONU service): 200

10.3.5 Principle of VoIP Service
Data Plan.
ONU VLAN ID: 200

Procedure
l
Configure the channel for the Internet access service.

a.
Configure the service VLAN and add the upstream port to this VLAN.
Configure the SVLAN ID to 100, VLAN type to smart VLAN, and VLAN attribute
to stacking. Add upstream port 0/19/0 to VLAN 100.
b.
Configure the corresponding traffic profile.

The 802.1p priority for the Internet access service is 0 and the traffic profile is
unlimited. You can run the display traffic table ip command to query the traffic
profile in the system. Use traffic profile 6.
c.
Configure service flows to receive and transparently transmits the Internet access
service from the ONU.
According to the data plan,
n
For the OLT: The SVLAN ID is 100, inner VLAN ID is 258. The user-side
VLAN ID of the OLT is the upstream VLAN ID of the ONU, that is, 1001.
The Internet access service uses GEM port 13.
For the ONU: The upstream VLAN ID is 1001.

multi-service
user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6
tx-cttr 6
Issue 01 (2016-04-29)

721

Access Module
Configure the channel for the VoIP service.

a.
Configure the SVLAN ID to 200 and VLAN type to smart VLAN. Add upstream
port 0/19/0 to VLAN 200.
b.

The 802.1p priority of the VoIP service is 5 and the traffic profile is unlimited. You
can run the display traffic table ip command to query the traffic profile in the
system. If the existing traffic profile does not meet data plan requirements, a new
traffic profile is required.
New traffic profile 9 is added. In the command execution, priority-policy is localsetting, which indicates that service packets are scheduled by the priority specified
in the traffic profile.
c.
Configure service flows to receive and transparently transmits the VoIP service
from the ONU.
n
For the OLT: The SVLAN ID is 200. The user-side VLAN ID of the OLT is
the upstream VLAN ID of the ONU, that is, 200. The VoIP service uses GEM
port 12.

multi-service
----End
10.4.6 Configuring LAN Internet Access Service (On the ONU)

This topic describes how to configure the Internet access service through the Ethernet port by
the ONU. Specifically, configure service flows on the ONU and configure the upstream
VLAN to provide the service channel from the ONU to the user and set up the upstream
channel from the ONU to the OLT.
Data plan
Item
Data
Remarks
Port
Service port: 0/3/1
Issue 01 (2016-04-29)

722

Access Module
Item
Data
Remarks
Service VLAN
VLAN ID: 1001-1016
The ONU supporting 16 FE ports is

used as an example. In actual
configuration, plan the data according
to actual capabilities of devices.
VLAN type: smart VLAN

VLAN attribute: common

10.3.3 Principle of Internet Access
Service Data Plan.
Traffic profile
Profile ID: 8
Committed rate: 4 Mbit/s

10.3.2 QoS Planning Principles.
Priority: 0
Procedure
Step 1 Log in to and configure the ONU.
You can remote log in to the ONU from the OLT to perform the configuration. The user name
is root and the password is admin123.
Step 2 Create SVLANs.
Create smart SVLANs 1001-1016 in batches with attribute common.
Step 3 Add the upstream port to SVLANs.

Add upstream port 0/0/1 to SVLANs.

If the existing traffic profile in the system does not meet the requirement, run the traffic table
Assume that the committed information rate (CIR) is 4 Mbit/s, priority of upstream packets is
0, and downstream packets are scheduled based on the priorities specified in the traffic
profile. Configure traffic profile 8.
huawei(config)#traffic table ip index 8 cir 4096 priority 0 priority-policy localSetting
Step 5 Add a service port.

Create service port 101, bind it to port 0/3/1, set the user-side VLAN to untagged and bind the
VLAN to traffic profile 8.
NOTE
This example creates one service port as an example. Each service port maps a user. When configuring
another service port, map the corresponding SVLAN.
huawei(config)#service-port 101 vlan 1001 eth 0/3/1 multi-service user-vlan
untagged rx-cttr 8 tx-cttr 8
Issue 01 (2016-04-29)

723

Access Module

huawei(config)#save
----End
10.4.7 Configuring H.248 Voice Service (on the ONU)

This topic describes how to configure the voice service on the ONU based on the H.248
protocol to provide the high quality and low cost VoIP service for users.
Prerequisites
l
The media gateway controller (MGC) interface data and the PSTN user data
corresponding to the media gateway (MG) interface is configured on the MGC.
Ensure that the Status of the voice board on the ONU is Normal by running the display
board 0 command.
1.
An ONU supports both the H.248 and SIP protocols; however, these two protocols are
mutually exclusive. You can run the display protocol support command to query the
currently supported voice protocol.
2.
If the voice protocol needs to be switched, you need to delete the global digitmap and the
MG interface (under H.248 protocol) or SIP interface (under SIP protocol) first and run
the protocol support command to switch the protocol. After the configuration is
complete, save the configuration and restart the system to make the configured protocol
take effect.
Precautions
CAUTION
This operation interrupts the ongoing services carried on the currently used MG/SIP interface.
Hence, exercise caution when performing this operation.
Data plan
For details about the data plan, see 10.3.5 Principle of VoIP Service Data Plan.
Item
MG
interface
data
NOTE
The data
configurati
on must be
the same as
the data
configurati
on on the
MGC.
Issue 01 (2016-04-29)
Data
Media
and
signalin
g
paramet
ers
Media and signaling

upstream VLANs
200
Media and signaling

upstream port
0/0/1
Media IP address and

signaling IP address
10.10.10.10/24
Default gateway IP
address
10.10.10.1/24
MG interface ID

724

Access Module
Item
Voice user
configuratio
n data
Data
Signaling port ID
2944
IP address of the primary MGC
200.200.200.200/24
Port ID of the primary MGC
2944
Coding
Text
Transmission mode
UDP
H248 version that MG starts to

negotiate
1 (the negotiation starts from V1)
Phone number
83110001-83110016
Terminal identification
Terminal layering is not supported

and the terminal identification
ranges from 0 to 15.
User priority
Cat2 for phone 1

Cat3 for phone 2 to phone 16
(default)
Common
parameter
User type
Common user (DEL user by

default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal
Ringing current attribute
Default value
Procedure
Step 2 Configure the upstream VLAN interface.
Specify the upstream VLAN interface for the media stream and the signaling flows and
configure the IP addresses of the Layer 3 interface. These IP addresses are the sources of the
IP address pools for the media stream and the signaling flows.
1.
Create an upstream VLAN.

The VLAN ID is 200 and the VLAN is a smart VLAN.
2.
Add the upstream port to the created upstream VLAN.

Issue 01 (2016-04-29)

725

Access Module
3.
Configure the IP address of the Layer 3 interface.

Enter the VLAN interface mode and configure the lP address of the Layer 3 interface to
10.10.10.10

Configure both the media IP address and signaling IP address to 10.10.10.10 and the MG IP
address to 10.10.10.1.
huawei(config)#voip
NOTE
You can configure the attributes of the MG interface only when the media IP address and the
signaling IP address exist in the media and signaling IP address pools.
The media IP address can be different from the signaling IP address. Plan the data according to
actual networking.
Step 4 Configure static routes.

Because the IP address of the VLAN interface and the IP address (200.200.200.200/24) of the
MGC are in different network segments, you need to configure a route for the network
segment from gateway 10.10.10.1 to 200.200.200.0.

control the call connection through the MG interface. Add MG interface 0 according to the
data plan.

Pay attention to the following when configuring the attributes of the MG interface according
to the data plan:
l
The MG interface is registered by the IP address (default mode) or domain name, which
must be the same as that on the MGC.
The negotiated H.248 protocol version is V1, V2 or V3 (default value). The interface
may fail to be registered because some softswitches do not support V3.
huawei(config-if-h248-0)#if-h248 attribute mgip 10.10.10.10 mgport

2944 code text transfer udp primary-mgc-ip1 200.200.200.200 primary-mgc-port
2944 mg-media-ip1 10.10.10.10 start-negotiate-version 1

NOTE
l You must cold reset the MG interface after configuring. Otherwise, the MG interface does not take effect.
l The MG interface can be cold reset only after parameters mgip, mgport, primary-mgc-ip1 (or mgcdomain-name1), mgcport_1, code, transfer, and mg-media-ip are correctly configured.
Issue 01 (2016-04-29)

726

Access Module

Configure phone numbers of users 0/3/0-0/3/15 to 83110001-83110016 in batches and
terminal identification to 0-15.
l
Phone numbers are used for only internal emergency standalone, that is, internal
extensions call each other. Actual phone numbers are assigned by the MGC.
If the user of the MG interface is configured to support terminal layering, you need not
configure the terminal identification because the system automatically allocates it. If the
user of the MG interface does not support terminal layering, the terminal identification is
mandatory. The terminal identification must be unique on one MG interface.
83110001
Step 9 Configure the call priority of a PSTN user.

huawei(config-esl-user)#mgpstnuser modify 0/3/0 priority cat2
Step 10 Configure all the PSTN ports to support polarity reversal.

Configure the physical attributes of the PSTN port to which the users belong to support
polarity reversal so that the user supports polarity reversal accounting.
enable

huawei(config)#save
----End
10.4.8 Configuring SIP Voice Service (on the ONU)

This topic describes how to configure voice services based on the Session Initiation Protocol
(SIP) on an optical network unit (ONU). The voice over IP (VoIP) services have high quality,
but require low cost.
Prerequisites
l
The IP Multimedia Subsystem (IMS) interface data and public switched telephone
network (PSTN) user data corresponding to the SIP interface is configured on the IMS.
Status of the voice board on the ONU is normal. (To verify board status, run the display
board 0 command.)
1.
2.
take effect.
Precautions
Issue 01 (2016-04-29)

727

Access Module
CAUTION
Data Plan
For configuration rules and description of configuration items, see 10.3.5 Principle of VoIP
Service Data Plan.
Data
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Voice user
configuratio
n data
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLAN
200
Media and
signaling
upstream port
0/0/1
Media IP address
and signaling IP
address
10.10.10.10/24
Default gateway
IP address
10.10.10.1/24
SIP interface ID
Signaling port ID
5060
IP address of the main IMS

equipment
200.200.200.200/24
Port ID of the main IMS

equipment
5060
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110016
User priority
Phone 1 indicates Cat2.

Phone 2 to phone 16 indicate Cat3 (default
value).
Common
Parameter
Issue 01 (2016-04-29)
User type
Common user (the DEL user by default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-Reversing Pulse

728

Access Module
Item
Data
Default value
Procedure
1.

2.

3.

10.10.10.10

Set the media IP address and signaling IP address to 10.10.10.10, and the media gateway to
10.10.10.1.
huawei(config)#voip
NOTE
Attributes of the SIP interface can be configured only when the media IP address and the signaling
IP address exist in the media and signaling IP address pools.
The Media IP address and signaling IP address can be different. Data planning should be based on
networking requirements.

Because the IP address of the VLAN interface and that of the IMS (200.200.200.200/24) are
in different network segments, the configured routes must be from gateway 10.10.10.1 to the
network segment 200.200.200.0.

The SIP interface is used for IMS communication.
Issue 01 (2016-04-29)

729

Access Module

Step 7 (Optional) Configure the optional attributes of the SIP interface.

Run the if-sip attribute optional command to configure the optional attributes, including the
domain name, description, register server uniform resource identifier (URI), phone context,
and conference factory URI of the SIP interface.
Step 9 Configure the SIP PSTN user data.

Configure in batches the phone numbers of users 0/3/0-0/3/15 to 83110001-83110016.
NOTE
l To configure the data of a single SIP PSTN user, run the sippstnuser add command.
l To configure the data of multiple SIP PSTN users in batches, run the sippstnuser batadd command.
Step 10 Configure call priorities for SIP PSTN users.


enable

huawei(config)#save
----End

Security Policy
The global configuration of upstream link aggregation and queue scheduling based on
priorities ensures service reliability. The global configuration of security policies ensures
service security.
Context
On the OLT, link aggregation provides a higher bandwidth and uplink reliability for optical
line terminals (OLTs) by aggregating multiple uplink Ethernet ports to one link aggregation
group (LAG). Link aggregation is recommended.
Issue 01 (2016-04-29)

730

Access Module
NOTE
Enable a service security function based on the service type. For details, see 10.3.7 Principle of Security
Data Plan.
Procedure
l

On the OLT, the following configurations are used as an example to configure link
aggregation:
mode.

On both the OLT and optical network units (ONUs), according to quality of service
(QoS) planning principles, all packets are scheduled in strict priority (SP) mode and
mapped to queues according to the packets' priorities. For details about QoS planning
principles, see 10.3.2 QoS Planning Principles.
Enable deny of service (DoS) anti-attack on both the OLT and ONUs.
i.
ii.

Enable IP address anti-attack on both the OLT and ONUs.

Enable MAC address anti-flapping on both the OLT and ONUs.

Enable MAC address anti-spoofing on both the OLT and ONUs.

i.

ii.

1)
Issue 01 (2016-04-29)


731

Access Module
2)

1)

2)

3)

effect.
4)
5)


flow.
iv.

Enable IP address anti-spoofing on ONUs.

i.

ii.


l
Enable Dynamic Host Configuration Protocol (DHCP) Option 82 on both the OLT
and ONUs. This configuration is recommended for the DHCP-based Internet access
service.
i.
Enable DHCP Option 82 on both the OLT and ONUs.

Issue 01 (2016-04-29)
level.

732

Access Module
ii.
The VLAN level:

1)

2)

3)

effect.
4)
5)

level.

command with the enable parameter selected, to allow ONU DHCP packets to
Enable Policy Information Transfer Protocol (PITP) on both the OLT and ONUs.
This configuration is recommended for the PPPoE-based Internet access service.
i.
Enable PITP on both the OLT and ONUs.

default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

enable parameter selected, to allow ONU PPPoE packets to carry a vendor tag.
----End
Issue 01 (2016-04-29)

733

Access Module

In the Fiber-to-the-building (FTTB) scenario, optical network units (ONUs) are installed in
buildings that are far from the central equipment room. ONUs support methods of remote
service verification such as Point-to-Point Protocol over Ethernet (PPPoE) dialup emulation
and call emulation. Remote site verification eliminates the need to go to site for a second
time.
Prerequisites
ONUs are properly connected to upper-layer devices. The broadband remote access server
(BRAS) and media gateway controller (MGC)/IP Multimedia Subsystem (IMS) have been
configured.
Background Information
Remote
Service
Verificati
on
Method
Function
Remarks
PPPoE
emulation
dialup
By emulating PPPoE terminal

software, an ONU dials up and
interacts with the BRAS, to verify
the connectivity between the ONT
and BRAS.
PPPoE dialup emulation requires a

service flow that does not belong to a
QinQ VLAN.
configured on the BRAS before the
PPPoE dialup emulation starts.
An ONU supports a maximum of
one PPPoE dialup emulation.
Call
emulation
An ONU emulates a call to check

whether the voice service
configurations are correct. The call
emulation function can also be used
to locate faults when a voice service
is faulty.
l An ONU can emulate a caller or

callee in an emulation test. A
functional phone is required in
the central office where the
acceptance personnel is.
l An ONU can emulate the caller
and callee simultaneously in an
emulation test. No phone is
required in the test.
l An ONU supports a maximum of
one call emulation.
Procedure
l

The user name, password, and authentication mode required by the emulation test must
be consistent with those configured on the BRAS.
Issue 01 (2016-04-29)

734

Access Module
a.
In global config mode, start an emulation test by running the pppoe simulate start
command.
b.
Query the emulation test information by running the display pppoe simulate info
command.
c.
Terminate the emulation test by running the pppoe simulate stop command.

When an ONU simultaneously emulates the caller and the callee in an emulation test,
retain the parameter settings as default. To query default values, run the display pots
emulational configuration command.
Assume that:
Caller port: 0/3/0
Called port: 0/3/15
Called number: 83110016
a.
Start an emulation test.

huawei(config)#test
huawei(config-test)#pots emulational-call caller-port 0/3/0 callee-port
0/3/15 callee-telno 83110016
b.
The ONU outputs the call emulation result after the test is complete.
The ONU outputs the call emulation result and failure of the cause if the emulation
test fails.
----End
10.5 FTTB/C Networking (GPON Networking, xDSL

Access, Without HGW)
In this kind of networking, an optical network unit (ONU) supports x digital subscriber line
(xDSL) and plain old telephone service (POTS) access and provides Internet access and voice
over IP (VoIP) services. This topic describes the OLT and ONU configurations required for
commissioning Internet access and voice services.
Context
l
batches.
NOTE
Command Reference.

Issue 01 (2016-04-29)

735

Access Module
Mode
Query Method

default)
On the OLT:
-------------------------------------------

Generally, Fiber-to-the-building (FTTB) applies to high-density residential areas or
commercial centers. Users can access service aggregation nodes using the local area network
(LAN) and x digital subscriber line (xDSL). Fiber-to-the-curb (FTTC) applies to low-density
residential areas such as villas. xDSL is mainly used in the FTTC scenario because the
subscribers are as far as 300 m to 3000 m from the fiber distribution terminal.
Only Internet access service and VoIP service are needed and there is no multicast
requirement.
To reuse the existing phone lines and overcome the challenges caused by long distance
between ONUs and subscribers, FTTB/C with xDSL access is recommended.
As shown in Figure 10-5, an ONU is deployed in the building corridor, the curb (fiber
distribution terminal), or at home through twisted wires.
l
Internet access service: A modem at the subscriber's house allows for high-speed Internet
access. The subscriber needs to dial up on a computer for authentication because the
modem is a Layer 2 device. Each subscriber has a unique account. The broadband
remote access server (BRAS) manages and authenticates subscribers.
Voices service: The voice module built in an ONU can provide voice over IP (VoIP)
services.
The ONUs used in this application scenario include MA5616, MA5603T.
Issue 01 (2016-04-29)

736

Access Module
Figure 10-5 FTTB/C networking diagram (xDSL)

Phone
PC
xD
SL
+P
OT
S
PE-AGG
Modem Splitter
OLT
S
POT
Phone
ONU
Optical
splitter
Phone
PC
Modem Splitter
S
OT
Metro Network
Internet
UPE
ONU
PE-AGG
PO
TS
xD
+P
SL
NGN/IMS
UPE
Phone

Figure 10-6 shows the configuration roadmap diagram in the FTTB and FTTC networking
scenarios using xDSL access without HGWs.
Figure 10-6 Configuration Roadmap Diagram in the FTTB and FTTC Networking Scenarios
Using xDSL Access Without HGWs
Issue 01 (2016-04-29)

737

Access Module
The following table lists the configuration procedure.

Item
Procedure
Remarks
OLT
Add an ONU on the

OLT.
Services can be configured for an ONU

only after the ONU is successfully added
to an OLT.
Configure the
management channel
between the OLT and
the ONU.

between the OLT and the ONU is
configured and available, you can log in to
the ONU from the OLT to configure the
ONU.

channel between the
OLT and the ONU.

service channel, are set up on the OLT so
that services on the ONU can be normally
forwarded.

access service.
NOTE
Different ONUs have different ports, including
ADSL2+, VDSL2, G.fast and VDSL2/G.fast
vectoring ports, for the Internet access. Select
an appropriate configuration method according
to the port type.
Configure the VoIP

service.
NOTE
exclusive for the VoIP service. Only one of
them is configured at a time.
ONU
Configure the link

policy.

on priorities ensures service reliability.
The global configuration of security
policies ensures service security.
ONU
Verify the service.

methods including PPPoE dialup
emulation and call emulation for
on-site operation.
ONU
OLT

Context
l
Issue 01 (2016-04-29)
738

Access Module

Profile
Type
Function
Command
DBA
profile



ONT lines.

alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)

Mode
Usage Scenario
Command
Add an
ONU
offline.


ONU.
Online
confirm
an ONU.


739

Access Module
Data Plan
Item
Data
DBA profile
NOTE

Profile type: Type1
Profile type: Type1
Profile type: Type4
Profile type: Type3
Profile type: Type3
NOTE
Line profile

Profile ID: 10
PON port: 0/2/1

ONT ID: 1
Procedure
Issue 01 (2016-04-29)

740

Access Module
NOTE
1.

max 16384
max 16384
2.
add
add
add
add
profile-name
profile-name
profile-name
profile-name


a.

NOTE
b.
c.
4
5
6
7
8
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
fttb_dba_mngt
fttb_dba_voip
fttb_dba_hsi
fttb_dba_vod
fttb_dba_iptv
//Create
//Create
section.
d.
......
......
e.
mapping 11 0 vlan 8
Issue 01 (2016-04-29)

741

Access Module
3.
generated.

discovered ONU.
l
Add an ONU offline.


1.


normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
Run state
: online
Config state
: normal
normally.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

742

Access Module

and the ONU
Data plan
Item
Data
Remarks
Management VLAN
and management IP
address on the OLT
side
Management VLAN
and management IP
address on the ONU
side


smart VLAN
address: 192.168.50.1/24

smart VLAN
address: 192.168.50.2/24
Procedure
192.168.50.1/24.
Issue 01 (2016-04-29)

743

Access Module

255.255.255.0 gateway
192.168.50.254 vlan 8

l
----End
ONU
Various service flows can be configured on the OLT for different services so that service
packets on the ONU can be forwarded at Layer 2 according to the planned VLAN and
Context
Service flows can be added in two modes, as described in Table 10-7. Select either mode as
required.
Table 10-7 Adding service flows
Issue 01 (2016-04-29)
Mode
Command
Remarks
Add service flows

one by one.
service-port
Add service flows

in batches.
multi-service-port
You need to specify the ontid +

gemindex to identify a service
flow and ensure that the number of
GEM ports is the same as the
number of VLANs on the user
side.

744

Access Module
Data plan
Item
Data
Remarks
Internet access
service
OLT VLAN ID:

splitter using the optical cable, and
the user PC is connected to port 1
on the ONU. In this case, the inner
VLAN is 258 according to the
formula for calculating the inner
VLAN.
l CVLAN ID: 256 x GPON

port ID + 32 x Split ratio x
(Splitter port ID - 1) +
ONU port ID + 1
l SVLAN: VLAN ID 100
and attribute stacking
ONU: 1001-1016
VoIP service

10.3.3 Principle of Internet
OLT VLAN ID (VLAN

ONU service): 200

10.3.5 Principle of VoIP Service
Data Plan.
ONU VLAN ID: 200

Procedure
l
Configure the channel for the Internet access service.

a.
Configure the SVLAN ID to 100, VLAN type to smart VLAN, and VLAN attribute
b.

The 802.1p priority for the Internet access service is 0 and the traffic profile is
unlimited. You can run the display traffic table ip command to query the traffic
profile in the system. Use traffic profile 6.
c.
Configure service flows to receive and transparently transmits the Internet access
service from the ONU.
n
For the OLT: The SVLAN ID is 100, inner VLAN ID is 258. The user-side
VLAN ID of the OLT is the upstream VLAN ID of the ONU, that is, 1001.
The Internet access service uses GEM port 13.

multi-service
user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6
tx-cttr 6
Issue 01 (2016-04-29)

745

Access Module
Configure the channel for the VoIP service.

a.
Configure the SVLAN ID to 200 and VLAN type to smart VLAN. Add upstream
b.

The 802.1p priority of the VoIP service is 5 and the traffic profile is unlimited. You
can run the display traffic table ip command to query the traffic profile in the
system. If the existing traffic profile does not meet data plan requirements, a new
traffic profile is required.
New traffic profile 9 is added. In the command execution, priority-policy is localsetting, which indicates that service packets are scheduled by the priority specified
c.
Configure service flows to receive and transparently transmits the VoIP service
from the ONU.
n
For the OLT: The SVLAN ID is 200. The user-side VLAN ID of the OLT is
the upstream VLAN ID of the ONU, that is, 200. The VoIP service uses GEM
port 12.

multi-service
----End
10.5.6 Configuring the Internet Access Service (ADSL2+ Access,

on the ONU)
This topic describes how to configure the Internet access service for ADSL2+ users on an
optical network unit (ONU).
Context
Issue 01 (2016-04-29)
Mode
Query Method
ADSL2+ common mode

(RFC2662 mode)
On the ONU:
huawei(diagnose)%%display xdsl mode
------------------------------------------ADSL Current mode : rfc2662
VDSL Current mode : tr129
--------------------------------------------

746

Access Module
ADSL2+ ports working in normal mode (that is, RFC 2662 mode) need to bind an ADSL2+
line profile and an ADSL2+ alarm profile. For the functions and configurations of each
profile, see Table 10-8.
Table 10-8 ADSL2+ profile
Profile
Type
Function
Configuration
ADSL2+
line
profile
An ADSL2+ line profile provides the

following parameters:
The system has four default profiles

(profile 1, profile 1022, profile 1023,
and profile 1024) for activation of
ADSL2+ ports in different conditions.
l ADSL/ADSL2+ working mode

l Channel mode
l Upstream/Downstream line rate
l Profile 1 is used for activation of

common ADSL ports.
l Upstream/Downstream interleave
depth
l Profile 1022 is used for fast

activation of ADSL ports.
l Noise margin
l Profile 1023 is used for long-reach

activation of existing ADSL ports.
When an ADSL2+ port is activated,

the central office (CO) and the
customer premises equipment (CPE)
negotiate based on the parameters
configured in the ADSL2+ line
profile, to determine whether the
ADSL2+ port can work in the normal
state in these conditions.
ADSL2+
alarm
profile
Values to be configured in an
ADSL2+ line alarm profile are
thresholds within any 15 minutes.
When the statistics of an item reach
the threshold, the system informs the
device of the event and sends alarms
to the NMS.
l Profile 1024 is used for activation

of ports on ADSL2+ boards.
Commands:
l To query: display adsl line-profile
l To add: adsl line-profile add or
adsl line-profile quickadd
Commands:
l To query: display adsl alarmprofile
l To add: adsl alarm-profile add or
adsl alarm-profile quickadd
Data Plan
The following table provides key information about the Internet access service (ADSL2+
access).
Item
Data
Remarks
Traffic
profile
ID: 8
A traffic profile implements rate-limiting.
CIR: 4 Mbit/s
VLAN priority: 0
Downstream priority policy:
local-setting
Issue 01 (2016-04-29)

747

Access Module
Item
Data
Remarks
VPI/VCI of
ADSL2+
users
VPI: 0
Internet service providers (ISPs) provide

VPI/VCI information.
ADSL2+
line profile
ID: 1024 (default); key

parameters:
VCI: 35
l Working mode: full

compatibility
A traffic profile or an ADSL2+ line profile

can implement rate-limiting on ADSL2+
ports. This example uses a default traffic
profile.
l Channel working mode:

interleaved
l Maximum upstream/
downstream rate (kbit/s):
24544/1024
ADSL2+
alarm
profile
ID: 1 (default)
The system does not check whether

parameter thresholds are crossed and so does
not report alarms.
Procedure
Step 1 Log in to the ONU to perform the configuration.
You can remote log in to the ONU from the OLT to perform the configuration. User name:
root (default). Password: admin123 (default).
You can run the display traffic table ip command to query the traffic profiles existing in the
system. If the traffic profiles existing in the system do not meet the requirements, you need to
run the traffic table ip command to add a traffic profile.
Add traffic profile 8 and set the committed information rate (CIR) to 4 Mbit/s. The priority for
upstream packets is 0, and downstream packets are scheduled based on the priority specified
huawei(config)#traffic table ip index 8 cir 4096 priority 0 priority-policy localsetting
Step 3 Create service VLANs.

Create service VLANs 1001-1016 in batches whose type is smart and attribute is common
(the service VLAN IDs must be consistent with the user VLAN IDs of the OLT). Add the
service VLANs to upstream port 0/0/1.

Assume that the VPI/VCI of users is 0/35 and the VLAN ID is 1001. Add a service port as
follows:
//Create service port 101, bind port 0/2/0 to it, set VPI/VCI to 0/35, and
bind traffic profile 8 to the user VLAN./
huawei(config)#service-port 101 vlan 1001 adsl 0/2/0 vpi 0 vci 35 multi-service
user-vlan untagged rx-cttr 8 tx-cttr 8
Issue 01 (2016-04-29)

748

Access Module
Step 5 (Optional) Configure an ADSL2+ line profile.

l
Configure an ADSL2+ line profile only when the default one does not meet
requirements.
This example uses the default ADSL2+ line profile (ID: 1024).
Step 6 (Optional) Configure an ADSL2+ alarm profile.

This example uses the default ADSL2+ alarm profile (ID: 1).
Step 7 Bind an ADSL2+ line profile and an ADSL2+ alarm profile, and activate the ADSL2+ port.
For example, bind ADSL2+ line profile 1024 and ADSL2+ alarm profile 1, and activate
ADSL2+ port 0/2/0.
----End
10.5.7 Configuring the Internet Access Service (VDSL2 Access, on

the ONU)
This topic describes how to configure the Internet access service for VDSL2 users on an
Context
Mode
Query Method
VDSL2 common mode (TR129

mode)
On the ONU:
--------------------------------------------
VDSL2 ports working in normal mode (that is, TR129 mode) need to bind the VDSL2 line
template and VDSL2 alarm template. For the functions and configurations of each profile, see
Table 10-9.
Issue 01 (2016-04-29)

749

Access Module
Table 10-9 VDSL2 template

Templ
ate
Type
Function
Configuration
VDSL2
line
template
A VDSL2 line template consists of a

VDSL2 line profile and a VDSL2
channel profile. When a VDSL2 port
is activated, the central office (CO)
and the customer premises equipment
(CPE) negotiate based on the
parameters configured in the VDSL2
line template, to determine whether
the VDSL2 port can work in the
normal state in these conditions.
The system has one default VDSL2

line template (template 1), which is
used for activation of common VDSL2
ports.
A VDSL2 line profile provides the

following parameters: line
transmission mode, adaptation mode
of upstream/downstream transmit
rates, signal-to-noise ratio (SNR)
margin, upstream power back-off
(UPBO), and downstream power
back-off (DPBO).
l To query: display vdsl line-profile
A VDSL2 channel profile provides the

following parameters: data channel
mode, minimum impulse noise
protection, interleaved delay
parameters, rate parameters,
retransmission at the physical layer,
erasure decoding, and G.998.4
retransmission.
l To query: display vdsl channeltemplate
A VDSL2 alarm template consists of a

VDSL2 line alarm profile and a
VDSL2 channel alarm profile. Values
to be configured in a VDSL2 alarm
template are thresholds within any 15
minutes. When the statistics of an item
reach the threshold, the system
informs the device of the event, and
sends alarms to the NMS.

alarm template (template 1).
VDSL2
alarm
template
Issue 01 (2016-04-29)
l To query: display vdsl linetemplate

l To add: vdsl line-template add or
vdsl line-template quickadd
l To add: vdsl line-profile add or

vdsl line-profile quickadd
l To add: vdsl channel-template

add or vdsl channel-profile
quickadd
l To query: display vdsl alarmtemplate

l To add: vdsl alarm-template add
or vdsl alarm-template quickadd

750

Access Module
Templ
ate
Type
Function
Configuration
A VDSL2 line alarm profile provides

the following parameters for COs and
CPEs:
l To query: display vdsl alarmprofile
l Forward error check seconds

(FECS)
l To add: vdsl alarm-profile add or

vdsl alarm-profile quickadd
l Errored seconds (ES)

l Severely errored seconds (SES)
l Loss of signal seconds (LOSS)
l Unavailable seconds (UAS)
l Low error-free throughput rate
(LEFTR) defect seconds
A VDSL2 channel alarm profile
provides the following parameters for
COs and CPEs:
l Coding violations counts (CVC)
l Corrected blocks counts (CBC)
l To query: display vdsl channelalarm-profile

l To add: vdsl channel-alarmprofile add or vdsl channelalarm-profile quickadd
Data Plan
Table 10-10 provides key information about the Internet access service (VDSL2 access).
Table 10-10 Key information about the Internet access service (VDSL2 access)
Item
Data
Remarks
Traffic profile
ID: 8
A traffic profile implements ratelimiting.
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
VDSL2 line
mode
PTM
There are two VDSL line modes: ATM

mode and PTM mode.
l ATM mode: ATM cells are
transmitted in channels. This mode
is compatible with the ADSL2+
mode.
l PTM mode: IP cells are transmitted
in channels. This mode is
incompatible with the ADSL2+
mode.
This example assumes the PTM mode.
Issue 01 (2016-04-29)

751

Access Module
Item
Data
Remarks
VDSL2 line
template
Line profile ID: 6
A traffic profile or a VDSL2 line

template can implement rate-limiting
on VDSL2 ports. When they are
specified in both ways, the actual
activation rate is determined by the
smaller one.
Channel profile ID: 6

Line template ID: 6
VDSL2 alarm
template
Line alarm profile ID: 1

(default)
Channel alarm profile ID: 1
(default)

parameter thresholds are crossed and
so does not report alarms.
Alarm template ID: 1 (default)
Procedure


Assume that the VDSL2 path mode is PTM mode, VLAN ID is 1001, port is 0/1/0, packets
from the user VLAN are untagged, and service flow ID is 101. Add a service port as follows:
huawei(config)#service-port 101 vlan 1001 vdsl mode ptm 0/1/0 multi-service uservlan untagged rx-cttr 8 tx-cttr 8
Step 5 Configure a VDSL2 line template.

Configure a VDSL2 line template according to actual requirements because values of DSL
line parameters are related to actual data planning and line quality. The following command
output is only an example. During actual configuration, the actual command output prevails.
huawei(config)#vdsl line-profile add
{ <cr>|profile-index<2,770> }:6
Issue 01 (2016-04-29)

752

Access Module
Command:
vdsl line-profile add 6
neglected
> Do you want to name the profile? (y/n) [n]:
>
Transmission mode:
>
0: Custom
>
1: All (G.992.1~5,T1.413,G.993.2)
>
2: Full rate (G.992.1/3/5,T1.413,G.993.2)
>
3: G.DMT (G.992.1/3/5,G.993.2)
>
4: G.HS (G.992.1~5,G.993.2)
>
5: ADSL (G.992.1~5,T1.413)
>
6: VDSL (G.993.2)
>
> Bit swap upstream
1-disable 2-enable (1~2) [2]:
> 1-fixed, 2-adaptAtStartup, 3-adaptAtRuntime, 4-adaptAtRuntimewithsos (1~4) [
2]:
2]:
> Will you set SNR margin parameters? (y/n) [n]:y
>
Target SNR margin downstream (0~310 0.1dB) [60]:80
//Note that the
parameter value is expressed in 0.1 dB.
>
Minimum SNR margin downstream (0~80 0.1dB) [0]:
>
Maximum SNR margin downstream (80~310 0.1dB) [300]:
>
Target SNR margin upstream (0~310 0.1dB) [60]:80
//Note that the
>
Minimum SNR margin upstream (0~80 0.1dB) [0]:
>
Maximum SNR margin upstream (80~310 0.1dB) [300]:
> Will you set DPBO parameters? (y/n) [n]:
> Will you set UPBO parameters? (y/n) [n]:
> Will you set mode-specific parameters? (y/n) [n]:y
>
Current configured modes:
>
1-defmode
>
Please select 1-Add 2-Modify 3-Save and quit
[3]:2
>
1-defmode
>
Please select [1]:
>
G.993.2 profile:
>
1-Profile8a
2-Profile8b
3-Profile8c
4-Profile8d
>
5-Profile12a
6-Profile12b
7-Profile17a
8-Profile30a
>
>
VDSL2 PSD class mask:
>
1-AnnexA998-D-32
2-AnnexA998-D-64
>
3-AnnexBHPE17-M1-NUS0(B7-7)
4-AnnexB997E17-M2x-A(B7-9)
>
5-AnnexB998E17-M2x-NUS0(B8-8)
6-AnnexB998E17-M2x-NUS0-M(B8-9)
>
7-AnnexB998ADE17-M2x-NUS0-M(B8-10) 8-AnnexB998ADE17-M2x-B(B8-12)
>
9-AnnexB998ADE17-M2x-A(B8-11)
10-AnnexA998-D-48
>
11-AnnexA998-D-128
12-AnnexB998ADE17-M2x-M(B8-17)
>
>
VDSL2 link use of U0 1-unused, 2-used (1~2) [1]:2
//Enable US0.
>
Maximum nominal aggregate transmit power downstream
>
(-255~145 0.1dBm) [145]:
>
Maximum nominal aggregate transmit power upstream
>
(-255~145 0.1dBm) [145]:
>
Will you set PSD mask value downstream parameter? (y/n) [n]:
>
Will you set PSD mask value upstream parameter? (y/n) [n]:
>
Will you set Upstream PSD mask selection parameter? (y/n) [n]:
>
Will you set transmitter referred virtual noise parameters? (y/n) [n]:
>
>
1-defmode
>
[3]:
Issue 01 (2016-04-29)

753

Access Module
>
>
>
>
>
>
Will you set

Will you set
Will you set
Will you set
Will you set
Will you set
Add profile 6
network timing reference? (y/n) [n]:

INM parameter? (y/n) [n]:
SOS downstream parameter? (y/n) [n]:
SOS upstream parameter? (y/n) [n]:
the G.998.4 retransmission function? (y/n) [n]:
force framer setting for inp? (y/n) [n]:
successfully
huawei(config)#vdsl channel-profile add

Command:
vdsl channel-profile add 6
neglected
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
> Will you set interleaving delay parameters? (y/n) [n]:
>
>
>
>
>
>
Maximum transmit rate upstream (32~200000 Kbps) [200000]:15000
> Will you set PHY-R function? (y/n) [n]:
> Will you set SOS bit rate? (y/n) [n]:
> Will you set the G.998.4 retransmission function? (y/n) [n]:
> Will you set channel initialization policy selection? (y/n) [n]:
huawei(config)#vdsl line-template add
{ <cr>|template-index<2,770> }:6
Command:
vdsl line-template add 6
neglected
> Do you want to name the template? (y/n) [n]:y
>
Please input template name:VDSL2-PORT1
>
//Configurations are
required only for channel 1.
>
>
Step 6 Configure a VDSL2 alarm template.

This example uses the default VDSL2 alarm template (ID: 1).
Issue 01 (2016-04-29)

754

Access Module
Step 7 Bind a VDSL2 line template and a VDSL2 alarm template, and activate the VDSL2 port.
For example, bind VDSL2 line template 1 and VDSL2 alarm template 1, and activate VDSL2
port 0/1/0.
----End
10.5.8 Configuring the Internet Access Service (G.fast Access, on

the ONU)
This topic describes how to configure the Internet access service for home gateway (HGW)
users on an optical network unit (ONU) when HGWs are connected upstream to the ONU in
G.fast mode.
Data Plan
Mode
Query Method
G.fast TR165 mode
On the ONU:
huawei(config)#display xdsl
mode
----------------------------------------------------------------------G.fast Current mode :
tr165
-----------------------------------------------------------------------
Table 10-11 provides key information about the Internet access service (G.fast access).
Table 10-11 Key information about the Internet access service (G.fast access)
Item
Data
Remarks
Traffic profile
ID: 8
A traffic profile limits rates.
CIR: 120 Mbit/s

VLAN priority: 0
local-setting
Issue 01 (2016-04-29)

755

Access Module
Item
Data
Remarks
G.fast line
profile
G.fast reach: approximately 200

m, with the sum of typical
upstream and downstream rates
of being approximately 160
Mbit/s
G.fast port rates can be limited based

on the traffic profile or G.fast line
profile. When both the profiles take
effect, the lower activation rate takes
effect.
Ratio of upstream rate to

downstream rate: 1:3
G.fast alarm
template
Start G.fast frequency: 2.2 MHz
This example uses the lowest start

G.fast frequency. If both G.fast lines
and VDSL2 lines are required on one
network, ensure that they use different
frequencies. For example, if VDSL2
lines use the 17a profile, the start
G.fast frequency must be at least 17
MHz. Some idle frequencies are
required between the VDSL2 and
G.fast frequencies to prevent inter-line
crosstalk.

(default)


(default)
Procedure
Step 1 Use the default user name root and password admin123 to remotely log in to the ONU from
the OLT.
Step 2 Configure the traffic profile.
Run the display traffic table ip command to query existing traffic profiles. If no existing
traffic profile meets usage requirements, run the traffic table ip command to add a new one.
The configuration of the added traffic profile is as follows: The profile ID is 16, the CIR is
120 Mbit/s, the priority of upstream packets is 0, and downstream packets are scheduled using
the priority specified in the traffic profile.
local-setting
Step 3 Create S-VLANs.

Create S-VLANs 1001 through 1016, which correspond to the S-VLANs created on the OLT.
These S-VLANs are of smart type with the common attribute. Then, add uplink port 0/0/1 to
these S-VLANs.

Issue 01 (2016-04-29)

756

Access Module
This example uses G.fast port 0/1/0, VLAN ID 1001, untagged packets from the user VLAN,
and service flow ID 101. Add a service port as follows:
huawei(config)#service-port 101 vlan 1001 g.fast 0/1/0 multi-service user-vlan
Step 5 Configure a G.fast line profile.

This example uses the parameter settings in the preceding data plan.
huawei(config)#g.fast tdd-profile quickadd
{ <cr>|name<K>|profile-index<2,4294967294>|symbol-parameter<K> }:3
{ <cr>|name<K>|symbol-parameter<K> }:symbol-parameter
{ symbol-num-per-tdd-frame<E><23,36> }:36
//The default G.9701 setting is used
as an example.
{ symbol-num-per-tdd-frame-ds<6,32> }:27 //The ratio of the upstream rate to
the downstream rate is 1:3.
{ <cr>|name<K>|operation-interval<K> }:operation-interval
{ ttr-ds<1,32> }:5
//This parameter can be configured but does not take
effect. Use the default value.
{ ttr-us<1,25> }:2
{ tbudget-ds<1,32> }:8 //This parameter can be configured but does not take
{ tbudget-us<1,25> }:2 //This parameter can be configured but does not take
{ <cr>|name<K> }:
Command:
g.fast tdd-profile quickadd 3 symbol-parameter 36 27 operation-interval
5 2 8 2
//This profile applies to rate limitation in the downstream direction.
huawei(config)#xdsl data-rate-profile quickadd g.fast-rate 32 120000 60000
120000 desc G.FAST-PORT0-DS
//This profile applies to rate limitation in the upstream direction.
huawei(config)#xdsl data-rate-profile quickadd g.fast-rate 32 40000 8000 40000
desc G.FAST-PORT0-US
//The lowest start G.fast frequency is 2.2 MHz, and the subcarrier index is 43.
huawei(config)#xdsl line-spectrum-profile quickadd g.fast-line-spectrum 2 43
//Configure retransmission parameters. Set parameter values based on electrical
and noise parameters of the site.
huawei(config)#xdsl inp-delay-profile quickadd g.fast-inp-delay g.fast-iat-rein 1
1 g
.fast-inp-min-rein 4 2 g.fast-inp-min-shine 2 2 g.fast-shine-ratio 20
20
Step 6 Configure a G.fast alarm template.

This example uses the default G.fast alarm template (ID: 1).
Step 7 Bind the line profile and alarm template and activate the G.fast port.
//Bind the G.fast TDD profile to the ONU.
huawei(config)#g.fast tdd-profile-config 0 profile-index 3
//Bind the line profile and alarm template to the G.fast port and activate this
port.
huawei(config)#interface g.fast 0/1
huawei(config-if-g.fast-0/1)#deactivate 0
huawei(config-if-g.fast-0/1)#activate 0 prof-idx ds-rate 9 us-rate 10 spectrum 2
Issue 01 (2016-04-29)

757

Access Module
inp-delay 5
huawei(config-if-g.fast-0/1)#alarm-config 0 1
----End
10.5.9 (Optional) Configuring Vectoring

Vectoring configurations on VDSL2 lines cancel the far-end crosstalk (FEXT) of VDSL2
lines to improve the line rate.
Context
For MA5623A/MA5616/MA5611S/MA5811S, when configuring vectoring, learn
configuration item functions and configuration methods beforehand by referring to Table
10-12.
Table 10-12 Vectoring configuration items
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Global band
plan
In the vectoring
algorithm, the system
requires that the
upstream band and
downstream band are
separate from each
other. Therefore, the
band plan must be
globally configured.
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
l After vectoring is
globally enabled, if
the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from each
other, the port
cannot be
activated.

758

Access Module
Item
Function
Description
Commands
Global
vectoring
configurations
Vectoring
configurations take
effect only when
vectoring is globally
enabled.
l Before enabling
vectoring, globally
configure the band
plan.
xdsl vectoring
Configure the function

of canceling the
upstream and
downstream crosstalk
in the vectoring
profile. After binding
the configured
vectoring profile to
the ports, the system
implements the
vectoring algorithm
on the ports in the
vectoring group based
on profile
configurations.
By default, all ports

are bound to vectoring
profile 1.
The Vectoring
algorithm is executed
every time a port in a
Vectoring group goes
online or offline. To
prevent adverse
impact on system
functions due to longterm running
Vectoring tasks caused
by frequent online and
offline on a port, set
the policy for
controlling frequent
online and offline on
ports based on site
requirements.
By default, the policy

for controlling
frequent online and
offline is set to limit.
Vectoring
profile
Policy for
controlling
frequent online
and offline on
ports
Issue 01 (2016-04-29)
NOTE
Services in a
vectoring group
port are interrupted
when the vectoring
function is enabled
or disabled.
Query a vectoring
profile: display xdsl
vectoring-profile
Default value:
l Upstream crosstalk
cancelation: enable
l Downstream
crosstalk
cancelation: enable

xdsl frequentlyretrain-control
759

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring
crosstalk
matrix
The vectoring
crosstalk matrix refers
to crosstalk on a port
in a vectoring group
from other ports in the
same vectoring group.
Before querying
information about the
vectoring crosstalk
matrix, ensure that the
global vectoring
function is enabled
and the specified port
is in a vectoring group
and activated.
display xdsl vectoring

crosstalk-couplingmatrix

760

Access Module
Item
Function
Description
Commands
Policy for
activating a
legacy
customer
premises
equipment
(CPE)
A legacy CPE is a
VDSL2 CPE
(supporting G.993.2,
not G.993.5) that does
not support Vectoring.
If such a CPE is
activated in G.993.2
mode in the Vectoring
system, the crosstalk
impact on other lines
cannot be canceled,
causing the Vectoring
system performance to
deteriorate. To
minimize the impact,
set the activation
policy of a legacy
CPE based on site
requirements.

for activating a legacy
CPE is set to limit.
xdsl vectoring legacycpe activate-policy
l no-limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode (G.993.2
mode), or nonVectoring mode, in
which the
Vectoring system
performance is
affected. This
mode is used in the
Vectoring initial
phase when a large
number of CPEs
need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode but the line
PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode is
used in Vectoring
medium phase
when some CPEs
have not been
upgrade or
replaced.
l force-friendly-dslimit-us: force
friendly is used in
the downstream
direction and PSD
Issue 01 (2016-04-29)

761

Access Module
Item
Function
Description
Commands
automatic shaping
is used in the
upstream direction.
l force-friendly-dsno-limit-us: force
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
For MA5603T/MA5600T, when configuring vectoring, learn configuration item functions and
configuration methods beforehand by referring to Table 10-13.
Issue 01 (2016-04-29)

762

Access Module

Item
Function
Description
Commands
Global band plan
In the vectoring
algorithm, the
system requires
that the upstream
band and
downstream band
are separate from
each other.
Therefore, the
band plan must
be globally
configured.
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
Vectoring
configurations
take effect only
when vectoring is
globally enabled.
l Vectoring can be
globally enabled
only when devices
are configured
with VP boards.
Global vectoring
configurations
globally enabled,
if the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from
each other, the
port cannot be
activated.
xdsl vectoring
l Before enabling
vectoring,
globally configure
the band plan.
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Issue 01 (2016-04-29)

763

Access Module
Item
Function
Description
Commands
Vectoring profile
Configure the
function of
canceling the
upstream and
downstream
crosstalk in the
vectoring profile.
After binding the
configured
vectoring profile
to the ports, the
system
implements the
vectoring
algorithm on the
ports in the
vectoring group
based on profile
configurations.

are bound to
vectoring profile 1.
Commands:
The Vectoring
algorithm is
executed every
time a port in a
Vectoring group
goes online or
offline. To
prevent adverse
impact on system
functions due to
long-term
running Vectoring
tasks caused by
frequent online
and offline on a
port, set the
policy for
controlling
frequent online
and offline on
ports based on
site requirements.

for controlling
frequent online and
Policy for controlling

frequent online and
offline on ports
Issue 01 (2016-04-29)
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable
l Add a vectoring
profile: xdsl
vectoring-profile
add
l Modify a
vectoring profile:
xdsl vectoringprofile modify
l Delete a vectoring
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
xdsl vectoringprofile
l Bind a vectoring
profile to the port:
vectoring-config
(VDSL mode)

764

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring crosstalk
matrix
The vectoring
crosstalk matrix
refers to crosstalk
on a port in a
vectoring group
from other ports
in the same
vectoring group.
Before querying
vectoring crosstalk
matrix, ensure that
the global vectoring
function is enabled
is in a vectoring
group and activated.


765

Access Module
Item
Function
Description
Commands
Policy for activating

a legacy customer
premises equipment
(CPE)
A legacy CPE is
a VDSL2 CPE
(supporting G.
993.2, not G.
993.5) that does
not support
Vectoring. If such
a CPE is
activated in G.
993.2 mode in the
Vectoring system,
the crosstalk
impact on other
lines cannot be
canceled, causing
the Vectoring
system
performance to
deteriorate. To
minimize the
impact, set the
activation policy
of a legacy CPE
based on site
requirements.

for activating a
legacy CPE is set to
limit.
l no-limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode (G.
993.2 mode), or
non-Vectoring
mode, in which
the Vectoring
system
performance is
affected. This
mode is used in
the Vectoring
initial phase when
a large number of
CPEs need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode but
the line PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode
is used in
Vectoring medium
phase when some
CPEs have not
been upgrade or
replaced.
friendly is used in
Issue 01 (2016-04-29)

766

Access Module
Item
Function
Description
Commands
the downstream
direction and PSD
automatic shaping
is used in the
upstream
direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Data Plan
The Table 10-14 lists key parameters of vectoring configurations.
Table 10-14 Key parameters of vectoring configurations
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l Band plan type: 998ade
l US0 type: type-a

legacy customer
premises equipment
(CPE)
Issue 01 (2016-04-29)
no-limit

The policy for activating a

vectoring legacy CPE is
configured as no-limit at the
initial stage of vectoring
application.
767

Access Module
Item
Data
Description

frequent online and
offline on ports
no-limit
Vectoring group
Group ID: 1
All ports are added to the

default vectoring group 1.
Vectoring profile
For the MA5623A/MA5616/

MA5611S/MA5811S:
Profile ID: 1 The upstream/

cancelation function in default
Profile 1 are as follows:
cancelation: enable
l Downstream crosstalk
cancelation: enable
For MA5603T/MA5600T:
l Profile name: huawei
cancelation: enable
cancelation: enable
l The port to which a
vectoring profile is bound:
all ports on the 0/4 board.
NOTE
The Vectoring is configured on the ONU, and the configuration between the MA5623A/MA5616/
MA5611S/MA5811S and MA5603T/MA5600T is a little different, Here gives the configuring steps of
MA5623A/MA5616/MA5611S/MA5811S and MA5603T/MA5600T respectively.
Procedure
l
Configuration procedure for the MA5623A/MA5616/MA5611S/MA5811S:

a.
Log in to the ONU remotely and start the configuration.

By default, the user name is root and the password is admin123.
b.
Globally configure the band plan type.

huawei(config)#xdsl vectoring bandplan-type 998ade us0-type type-a
c.
Configure the policy for activating a vectoring legacy CPE.

huawei(config)#xdsl vectoring legacy-cpe activate-policy no-limit
d.
Configure the policy for controlling frequent online and offline on ports.
huawei(config)#xdsl frequent-retrain-control 0/1/0 control-policy nolimit
e.
Enable global vectoring.

huawei(config)#xdsl vectoring enable
Issue 01 (2016-04-29)

768

Access Module
f.
Save the data.

huawei(config)#save
Configuration procedure for the MA5603T/MA5600T:

a.

b.

c.
Configure the vectoring profile as huawei and bind it to the VDSL2 port in the
vectoring group.
huawei(config)#xdsl vectoring-profile add control enable enable name
huawei
huawei(config-if-vdsl-0/4)#vectoring-config all profile-name huawei
d.

e.
f.
Enable the global vectoring.

g.
Save the data.

huawei(config)#save
----End

Prerequisites
l
board 0 command.
1.
2.
take effect.
Precautions
Issue 01 (2016-04-29)

769

Access Module
CAUTION
Data plan
Data
Item
MG
interface
data
NOTE
The data
configurati
on must be
the same as
the data
configurati
on on the
MGC.
Voice user
configuratio
n data
Media
and
signalin
g
paramet
ers
Media and signaling

upstream VLANs
200
Media and signaling

upstream port
0/0/1

10.10.10.10/24
Default gateway IP
address
10.10.10.1/24
MG interface ID
Signaling port ID
2944
200.200.200.200/24
2944
Coding
Text
Transmission mode
UDP

negotiate
Phone number
83110001-83110016

User priority
Cat2 for phone 1

(default)
Common
parameter
Issue 01 (2016-04-29)
User type

default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal

770

Access Module
Item
Data
Default value
Procedure
1.

2.

3.

10.10.10.10

huawei(config)#voip
NOTE
actual networking.


Issue 01 (2016-04-29)

771

Access Module
data plan.

to the data plan:
l


NOTE

l
83110001


enable

Issue 01 (2016-04-29)

772

Access Module
huawei(config)#save
----End

Prerequisites
l
board 0 command.)
1.
2.
take effect.
Precautions
CAUTION
Data Plan
Service Data Plan.
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Issue 01 (2016-04-29)
Data
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLAN
200
Media and
signaling
upstream port
0/0/1
Media IP address
and signaling IP
address
10.10.10.10/24

773

Access Module
Item
Data
Default gateway
IP address
Voice user
configuratio
n data
10.10.10.1/24
SIP interface ID
Signaling port ID
5060

equipment
200.200.200.200/24

equipment
5060
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110016
User priority

value).
Common
Parameter
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Default value
Procedure
1.

2.

Issue 01 (2016-04-29)

774

Access Module
3.

10.10.10.10

10.10.10.1.
huawei(config)#voip
NOTE





NOTE
Issue 01 (2016-04-29)

775

Access Module


enable

huawei(config)#save
----End

Security Policy
service security.
Context
NOTE
Data Plan.
Procedure
l

aggregation:
mode.

Issue 01 (2016-04-29)

776

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)

777

Access Module
i.

ii.


l
service.
i.

level.
The VLAN level:
ii.
1)

2)

3)

effect.
4)
5)

level.

i.

Issue 01 (2016-04-29)

778

Access Module
default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

In the Fiber-to-the-building (FTTB) scenario, optical network units (ONUs) are installed in
buildings that are far from the central equipment room. ONUs support methods of remote
service verification such as Point-to-Point Protocol over Ethernet (PPPoE) dialup emulation
and call emulation. Remote site verification eliminates the need to go to site for a second
time.
Prerequisites
ONUs are properly connected to upper-layer devices. The broadband remote access server
(BRAS) and media gateway controller (MGC)/IP Multimedia Subsystem (IMS) have been
configured.
Issue 01 (2016-04-29)

779

Access Module
Remote
Service
Verificati
on
Method
Function
Remarks
PPPoE
emulation
dialup
By emulating PPPoE terminal

software, an ONU dials up and
interacts with the BRAS, to verify
and BRAS.

service flow that does not belong to a
QinQ VLAN.
configured on the BRAS before the
PPPoE dialup emulation starts.
Call
emulation
An ONU emulates a call to check

whether the voice service
configurations are correct. The call
emulation function can also be used
to locate faults when a voice service
is faulty.
l An ONU can emulate a caller or

callee in an emulation test. A
functional phone is required in
the central office where the
acceptance personnel is.
one call emulation.
Procedure
l

a.
command.
b.
command.
c.

Assume that:
Issue 01 (2016-04-29)
Caller port: 0/3/0

780

Access Module
Called port: 0/3/15
a.
huawei(config)#test
0/3/15 callee-telno 83110016
b.
test fails.
----End
10.6 FTTB/FTTC+HGW Networking (GPON Networking,

Voice Service Provided by ONU)
The home gateway (HGW) provides Internet access and Internet Protocol television (IPTV)
services. The services are sent upstream to the optical network unit (ONU) over a local area
network (LAN) or x digital subscriber line (xDSL). The Integrated Access Device (IAD) in
the ONU provides voice services.
Context
l
batches.
NOTE
Command Reference.

Mode
Query Method

default)
On the OLT:
-------------------------------------------

Issue 01 (2016-04-29)

781

Access Module
A gigabit-capable passive optical network (GPON) should be capable of delivering triple play
service over Category 5 cables or twisted pairs. Service requirements are described as
follows:
l
Sharing of Internet access among multiple computers in the household
Access of multiple phones in the household
Internet Protocol (IPTV) services (program preview or watch) enabled by set-top boxes
(STB)
Independent provisioning of Internet access, voice, and IPTV services
Ensured service security:
Internet access services protected against unauthorized access, hijacking or

unauthorized borrowing of user accounts, MAC/IP spoofing, and malicious attack
Voice and IPTV services protected against MAC/IP spoofing, malicious attack, and
traffic flooding attack
Easy fault location and service maintenance
As shown in Figure 10-7, a GPON optical line terminal (OLT) is deployed at the central
office (CO), where services are converged into the metropolitan area network. An optical
network unit (ONU) is deployed in the building corridor or the curb (fiber distribution
terminal). Service access ports are provided by the local area network (LAN) or the home
gateway (HGW) of an x digital subscriber line (xDSL) upstream.
l
An HGW sends services upstream to an ONU through ETH or xDSL ports, and provides
Internet services for downstream subscribers through fast Ethernet (FE) ports or WiFi,
and IPTV services through FE ports.
The HGW has Layer 3 functions (such as PPPoE dialup and NAT), which enable
multiple PCs of a family to access the Internet at the same time (NAT is short for
network address translation).
Set-top boxes (STB) are connected to HGWs to provide IPTV services (program preview
and watch).
The integrated access device (IAD) in an ONU provides at least one plain old telephone
service (POTS) interface, which allows for access of multiple phones in the household.
The ONUs used in this application scenario include MA5616, MA5603T, MA5612, MA5878.
Issue 01 (2016-04-29)

782

Access Module
Figure 10-7 GPON FTTB+HGW networking Diagram (voice, Internet access and IPTV
services)
Laptop
PC
HGW
PE-AGG
LAN
STB
OLT
TV
ONU
Metro Network
Phone
Laptop
HGW
Internet
Phone
STB
PE-AGG
xDSL+
POTS
Splitter
ONU
PO
TS
PC
IPTV
Headend
Splitter
UPE
TV
NGN/IMS
UPE
Phone

Figure 10-8 shows the configuration roadmap diagram in the FTTB+HGW networking
scenarios (ONU providing the VoIP service).
Issue 01 (2016-04-29)

783

Access Module
Figure 10-8 Configuration Roadmap Diagram in the FTTB+HGW Networking Scenarios

(ONU Providing the VoIP Service)
The following table lists the configuration procedure..
Issue 01 (2016-04-29)
Item
Procedure
Remarks
OLT
Add an ONU on the OLT.

only after the ONU is successfully
added to an OLT.
Configure the
management channel
between the OLT and the
ONU.

configured and available, you can log in
to the ONU from the OLT to configure
the ONU.

channel between the OLT
and the ONU.

service channel, are set up on the OLT
so that services on the ONU can be
normally forwarded.

784

Access Module
Item
Procedure
Remarks
ONU

access service.
NOTE
Different ONUs have different ports,
including LAN, ADSL2+, VDSL2, and
VDSL2 vectoring ports, for the Internet
access. Select an appropriate configuration
method according to the port type.
NOTE
Configure the IPTV

service.
IPTV services include the VoD and

multicast services that are different in
configuration procedures and need to be
configured separately.
Configure the link

policy.
The global configuration of upstream

link aggregation and queue scheduling
based on priorities ensures service
reliability. The global configuration of
security policies ensures service
security.

access service on the
HGW.
HGWs have different models and

appearances but their configuration
procedures are similar. This topic uses
the HG239 that uses LAN for upstream
transmission and the HG527 uses
ADSL2+ for upstream transmission as
examples.
OLT
ONU
HGW
NOTE
Vectoring is supported by the HG612 and
HG622 only.
ONU
Configure the IPTV

service on the HGW.
Verify the services.

emulation, call emulation and multicast
emulation for the commissioning and
configuration engineers to verify
services remotely after service
configuration, avoiding a second on-site
operation.

Issue 01 (2016-04-29)

785

Access Module
Context
l
Profile
Type
Function
Command
DBA
profile



ONT lines.

alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)

Mode
Usage Scenario
Command
Add an
ONU
offline.


ONU.
Online
confirm
an ONU.


786

Access Module
Data Plan
Item
Data
DBA profile
NOTE

Profile type: Type1
Profile type: Type1
Profile type: Type4
Profile type: Type3
Profile type: Type3
NOTE
Line profile

Profile ID: 10
PON port: 0/2/1

ONT ID: 1
Procedure
Issue 01 (2016-04-29)

787

Access Module
NOTE
1.

max 16384
max 16384
2.
add
add
add
add
profile-name
profile-name
profile-name
profile-name


a.

NOTE
b.
c.
4
5
6
7
8
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
fttb_dba_mngt
fttb_dba_voip
fttb_dba_hsi
fttb_dba_vod
fttb_dba_iptv
//Create
//Create
section.
d.
......
......
e.
mapping 11 0 vlan 8
Issue 01 (2016-04-29)

788

Access Module
3.
generated.

discovered ONU.
l
Add an ONU offline.


1.


normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
Run state
: online
Config state
: normal
normally.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

789

Access Module

and the ONU
Data plan
Item
Data
Remarks
Management VLAN
and management IP
address on the OLT
side
Management VLAN
and management IP
address on the ONU
side


smart VLAN
address: 192.168.50.1/24

smart VLAN
address: 192.168.50.2/24
Procedure
192.168.50.1/24.
Issue 01 (2016-04-29)

790

Access Module

255.255.255.0 gateway
192.168.50.254 vlan 8

l
----End
ONU
This topic describes how to configure service channels between an optical line terminal (OLT)
and an optical network unit (ONU) on a gigabit-capable passive optical network (GPON).
After channels for involved service types are configured on an OLT to which an ONU is
connected, packets of the service types from the ONU can be forwarded based on planned
VLANs and policies at Layer 2.
Prerequisites
1.
10.7.3 Adding an ONU to an OLT is performed.
2.
10.7.4 Configuring the Management Channel Between the OLT and the ONU is
performed.
Data Plan
The following table provides key information about the service channels between an OLT and
an ONU.
Issue 01 (2016-04-29)
Service
Type
VLAN Plan
Remarks
Internet
access
service
S-VLAN ID: 100; SVLAN attribute:

stacking
Plan the Internet access service in per user per

service per VLAN (PUPSPV) mode and apply SVLAN+C-VLAN to differentiate users.
C-VLAN ID: 1001-1016
For details, see 10.3.3 Principle of Internet


791

Access Module
Service
Type
VLAN Plan
Remarks
VoIP
service
S-VLAN ID: 200
The voice over IP (VoIP) service is a carrieroperating, closed service and primarily adopts
only S-VLAN tags, which are transparently
transmitted by OLTs.
C-VLAN ID: 200
For details, see 10.3.5 Principle of VoIP Service

Data Plan.
VoD
service
S-VLAN ID: 300
Plan the video on demand (VoD) service in per

user per VLAN (PUPV) mode if possible, as the
VoD service requires only a few VLAN
resources.
The VoD service is a carrier-operating, closed
service and primarily adopts only S-VLAN tags,
which are transparently transmitted by OLTs.
For details, see 10.3.6 Principle of IPTV
Service Data Plan.
Multicast
service
Multicast VLAN ID:

1000
Multicast cascading
port: 0/2/1
IGMP version: IGMPv3
The multicast service is a carrier-operating,

closed service and primarily adopts only SVLAN tags.
Service Data Plan.
IGMP mode: IGMP

proxy
Multicast IP address
range:
224.1.1.10-224.1.1.100
IP address of the
multicast server:
10.10.10.10/24
NOTE
C-VLANs in the preceding table are defined for OLTs. That is, they are upstream VLANs or S-VLANs of
ONUs.
Procedure
l
Configure a channel for the Internet access service.

a.

Create S-VLAN 100 with the stacking attribute and add upstream port 0/19/0 to the
S-VLAN.
b.
Issue 01 (2016-04-29)

792

Access Module
The 802.1p priority of the Internet access service is 0, and rate limitation is not
required. To check whether any existing traffic profile meets the requirements, run
the display traffic table ip command. In this example, the query result shows that
traffic profile 6 meets the requirements, so no traffic profile needs to be configured.
c.
Configure a service flow for receiving and transparently transmitting the Internet
access service from the ONU side.
Configure a service flow with the GEM port ID being 13 and user-side VLAN ID
being 1001 (example value). The ONU is connected to GPON port 0/2/1, upstream
and downstream traffic are rate-limited on the ONU but not on the OLT, and traffic
profile 6 is referenced.
huawei(config)#service-port vlan 100 gpon 0/2/1 ont 1 gemport 13 multiservice user-vlan 1001 tag-transform translate-and-add rx-cttr 6 tx-cttr
6
Configure a channel for the VoIP service.

a.

Create S-VLAN 200 with the common attribute and add upstream port 0/19/0 to the
S-VLAN.
b.

The 802.1p priority of the VoIP service is 5, and rate limitation is not required. To
check whether any existing traffic profile meets the requirements, run the display
traffic table ip command. In this example, the query result shows that no traffic
profile meets the requirements, so a traffic profile needs to be configured.
Add traffic profile 9 and set priority-policy to local-setting. Then, traffic is
scheduled based on the priority specified in the traffic profile.
c.
Configure a service flow for receiving and transparently transmitting the VoIP
service from the ONU side.
being 200. The ONU is connected to GPON port 0/2/1, upstream and downstream
traffic are rate-limited on the ONU but not on the OLT, and traffic profile 9 is
referenced.
huawei(config)#service-port vlan 200 gpon 0/2/1 ont 1 gemport 12 multiservice user-vlan 200 rx-cttr 9 tx-cttr 9
Configure a channel for the VoD service.

a.

S-VLAN.
b.

The 802.1p priority of the VoD service is 4, and rate limitation is not required. To
Issue 01 (2016-04-29)

793

Access Module
c.
Configure a service flow for the VoD service.

referenced.
Configure a channel for the multicast service.

a.

Create S-VLAN 1000 with the common attribute and add upstream port 0/19/0 to
the S-VLAN.
b.
Configure a service flow for the multicast service.

being 1000. ONT 1 is connected to GPON port 0/2/1, upstream and downstream
referenced.
c.
Configure a multicast cascading port.

Set GPON port 0/2/1 as a multicast cascading port, ONU ID to 1, and GEM port 16
to carry the multicast service.
huawei(config)#btv
huawei(config-btv)#igmp cascade-port 0/2/1 ontid 1 gemport-index 16
d.

Set the IGMP version to IGMPv3.
e.
Set the IGMP mode.

f.
Configure an IGMP upstream port.

Set the IGMP upstream port to port 0/19/0.
g.
Issue 01 (2016-04-29)

794

Access Module
Set the multicast IP address range to 224.1.1.10-224.1.1.100 and the IP address of

the multicast server to 10.10.10.10.
huawei(config-mvlan1000)#igmp program add batch ip 224.1.1.10 to-ip
224.1.1.100 sourceip 10.10.10.10
----End
10.6.6 Configuring the Internet Access Service (LAN Access, on

the ONU)
users on an optical network unit (ONU) when HGWs are connected upstream to the ONU
through local area networks (LANs).
Data Plan
The following table provides key information about the Internet access service (LAN access).
Item
Data
Remarks
Traffic
profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
User
VLAN
Untagged
User VLAN ID: 1, 2, 3...
HGWs can send untagged packets or packets

with user VLAN tags.
Procedure

Issue 01 (2016-04-29)

795

Access Module


Configurations for untagged packets and packets with user VLAN tags are different.
l
For untagged packets, the configuration is as follows (assuming that the VLAN ID is
1001):
//Create service port 101, bind port 0/3/1 to it, set the user VLAN to
untagged, and bind traffic profile 8 to the user VLAN./
For packets with user VLAN tags, the configuration is as follows (assuming that the user
VLAN ID is 10 and the VLAN ID is 1001):
//Create service port 101, bind port 0/3/1 to it, set the user VLAN ID to
10, and bind traffic profile 8 to the user VLAN./
10 rx-cttr 8 tx-cttr 8
----End

on the ONU)
Context
Mode
Query Method
ADSL2+ common mode

(RFC2662 mode)
On the ONU:
--------------------------------------------
Issue 01 (2016-04-29)

796

Access Module

Profile
Type
Function
Configuration
ADSL2+
line
profile



l Channel mode

common ADSL ports.
depth

l Noise margin


ADSL2+
alarm
profile
to the NMS.

Commands:
Commands:
Data Plan
access).
Item
Data
Remarks
Traffic
profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
VPI/VCI of
ADSL2+
users
Issue 01 (2016-04-29)
VPI: 0
VCI: 35


797

Access Module
Item
Data
Remarks
ADSL2+
line profile

parameters:

profile.

compatibility
interleaved
l Maximum upstream/
24544/1024
ADSL2+
alarm
profile
ID: 1 (default)

not report alarms.
Procedure


follows:

l
Issue 01 (2016-04-29)
requirements.
798

Access Module

ADSL2+ port 0/2/0.
----End

the ONU)
Context
Mode
Query Method

mode)
On the ONU:
--------------------------------------------
Table 10-18.
Issue 01 (2016-04-29)

799

Access Module

Templ
ate
Type
Function
Configuration
VDSL2
line
template


ports.

back-off (DPBO).

retransmission.


VDSL2
alarm
template
Issue 01 (2016-04-29)



quickadd


800

Access Module
Templ
ate
Type
Function
Configuration

CPEs:

(FECS)


COs and CPEs:

Data Plan
Item
Data
Remarks
Traffic profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
VDSL2 line
mode
PTM

mode and PTM mode.
mode.
mode.
Issue 01 (2016-04-29)

801

Access Module
Item
Data
Remarks
VDSL2 line
template
Line profile ID: 6

smaller one.

Line template ID: 6
VDSL2 alarm
template

(default)
(default)

Procedure



Issue 01 (2016-04-29)

802

Access Module
Command:
neglected
>
Transmission mode:
>
0: Custom
>
1: All (G.992.1~5,T1.413,G.993.2)
>
2: Full rate (G.992.1/3/5,T1.413,G.993.2)
>
3: G.DMT (G.992.1/3/5,G.993.2)
>
4: G.HS (G.992.1~5,G.993.2)
>
5: ADSL (G.992.1~5,T1.413)
>
6: VDSL (G.993.2)
>
> Bit swap upstream
2]:
2]:
>
//Note that the
>
>
>
//Note that the
>
>
>
>
1-defmode
>
[3]:2
>
1-defmode
>
Please select [1]:
>
G.993.2 profile:
>
1-Profile8a
2-Profile8b
3-Profile8c
4-Profile8d
>
5-Profile12a
6-Profile12b
7-Profile17a
8-Profile30a
>
>
>
1-AnnexA998-D-32
2-AnnexA998-D-64
>
>
>
>
10-AnnexA998-D-48
>
11-AnnexA998-D-128
>
>
//Enable US0.
>
>
(-255~145 0.1dBm) [145]:
>
>
(-255~145 0.1dBm) [145]:
>
>
>
>
>
>
1-defmode
>
[3]:
Issue 01 (2016-04-29)

803

Access Module
>
>
>
>
>
>
Will you set

Will you set
Will you set
Will you set
Will you set
Will you set
Add profile 6
network timing reference? (y/n) [n]:

INM parameter? (y/n) [n]:
SOS downstream parameter? (y/n) [n]:
SOS upstream parameter? (y/n) [n]:
the G.998.4 retransmission function? (y/n) [n]:
force framer setting for inp? (y/n) [n]:
successfully

Command:
neglected
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
>
>
>
>
Command:
neglected
>
>
>
>

Issue 01 (2016-04-29)

804

Access Module
port 0/1/0.
----End

Context
10-20.
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Global band
plan
In the vectoring
requires that the
upstream band and
downstream band are
separate from each
band plan must be
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from each
other, the port
cannot be
activated.

805

Access Module
Item
Function
Description
Commands
Global
vectoring
configurations
Vectoring
configurations take
effect only when
enabled.
l Before enabling
vectoring, globally
configure the band
plan.
xdsl vectoring

of canceling the
upstream and
in the vectoring
the configured
implements the
vectoring algorithm
on the ports in the
on profile
configurations.

profile 1.
The Vectoring
prevent adverse
impact on system
the policy for
ports based on site
requirements.

for controlling
frequent online and
Vectoring
profile
Policy for
controlling
frequent online
and offline on
ports
Issue 01 (2016-04-29)
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Query a vectoring
vectoring-profile
Default value:
cancelation: enable
l Downstream
crosstalk
cancelation: enable

806

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring
crosstalk
matrix
The vectoring
Before querying
vectoring crosstalk
global vectoring
function is enabled
and activated.


807

Access Module
Item
Function
Description
Commands
Policy for
activating a
legacy
customer
premises
equipment
(CPE)
A legacy CPE is a
VDSL2 CPE
If such a CPE is
cannot be canceled,
deteriorate. To
set the activation
policy of a legacy
CPE based on site
requirements.

l no-limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode (G.993.2
which the
Vectoring system
performance is
affected. This
mode is used in the
Vectoring initial
phase when a large
number of CPEs
need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode but the line
PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode is
used in Vectoring
medium phase
when some CPEs
have not been
upgrade or
replaced.
friendly is used in
the downstream
direction and PSD
Issue 01 (2016-04-29)

808

Access Module
Item
Function
Description
Commands
automatic shaping
is used in the
upstream direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Issue 01 (2016-04-29)

809

Access Module

Item
Function
Description
Commands
Global band plan
In the vectoring
algorithm, the
system requires
that the upstream
band and
downstream band
are separate from
each other.
Therefore, the
band plan must
be globally
configured.
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
Vectoring
configurations
take effect only
when vectoring is
globally enabled.
l Vectoring can be
globally enabled
only when devices
are configured
with VP boards.
Global vectoring
configurations
globally enabled,
if the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from
each other, the
port cannot be
activated.
xdsl vectoring
l Before enabling
vectoring,
globally configure
the band plan.
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Issue 01 (2016-04-29)

810

Access Module
Item
Function
Description
Commands
Vectoring profile
Configure the
function of
canceling the
upstream and
downstream
crosstalk in the
vectoring profile.
After binding the
configured
vectoring profile
to the ports, the
system
implements the
vectoring
algorithm on the
ports in the
vectoring group
based on profile
configurations.

are bound to
Commands:
The Vectoring
algorithm is
executed every
time a port in a
Vectoring group
goes online or
offline. To
prevent adverse
impact on system
functions due to
long-term
running Vectoring
tasks caused by
frequent online
and offline on a
port, set the
policy for
controlling
frequent online
and offline on
ports based on
site requirements.

for controlling
frequent online and

frequent online and
offline on ports
Issue 01 (2016-04-29)
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable
l Add a vectoring
profile: xdsl
vectoring-profile
add
l Modify a
vectoring profile:
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
l Bind a vectoring
vectoring-config
(VDSL mode)

811

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring crosstalk
matrix
The vectoring
crosstalk matrix
refers to crosstalk
on a port in a
vectoring group
from other ports
in the same
vectoring group.
Before querying
vectoring crosstalk
matrix, ensure that
function is enabled
is in a vectoring


812

Access Module
Item
Function
Description
Commands

a legacy customer
premises equipment
(CPE)
A legacy CPE is
a VDSL2 CPE
(supporting G.
993.2, not G.
993.5) that does
not support
Vectoring. If such
a CPE is
activated in G.
993.2 mode in the
Vectoring system,
the crosstalk
impact on other
lines cannot be
canceled, causing
the Vectoring
system
performance to
deteriorate. To
minimize the
impact, set the
activation policy
of a legacy CPE
based on site
requirements.

for activating a
limit.
l no-limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode (G.
993.2 mode), or
non-Vectoring
mode, in which
the Vectoring
system
performance is
affected. This
mode is used in
the Vectoring
initial phase when
a large number of
CPEs need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode but
the line PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode
is used in
Vectoring medium
phase when some
CPEs have not
been upgrade or
replaced.
friendly is used in
Issue 01 (2016-04-29)

813

Access Module
Item
Function
Description
Commands
the downstream
direction and PSD
automatic shaping
is used in the
upstream
direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Data Plan
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l US0 type: type-a

legacy customer
premises equipment
(CPE)
Issue 01 (2016-04-29)
no-limit


application.
814

Access Module
Item
Data
Description

frequent online and
offline on ports
no-limit
Vectoring group
Group ID: 1

Vectoring profile

MA5611S/MA5811S:

cancelation: enable
cancelation: enable
cancelation: enable
cancelation: enable
NOTE
Procedure
l

a.

b.

c.

d.
e.

Issue 01 (2016-04-29)

815

Access Module
f.
Save the data.

huawei(config)#save

a.

b.

c.
vectoring group.
huawei
d.

e.
f.

g.
Save the data.

huawei(config)#save
----End

Prerequisites
l
board 0 command.
1.
2.
take effect.
Precautions
Issue 01 (2016-04-29)

816

Access Module
CAUTION
Data plan
Data
Item
MG
interface
data
NOTE
The data
configurati
on must be
the same as
the data
configurati
on on the
MGC.
Voice user
configuratio
n data
Media
and
signalin
g
paramet
ers
Media and signaling

upstream VLANs
200
Media and signaling

upstream port
0/0/1

10.10.10.10/24
Default gateway IP
address
10.10.10.1/24
MG interface ID
Signaling port ID
2944
200.200.200.200/24
2944
Coding
Text
Transmission mode
UDP

negotiate
Phone number
83110001-83110016

User priority
Cat2 for phone 1

(default)
Common
parameter
Issue 01 (2016-04-29)
User type

default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal

817

Access Module
Item
Data
Default value
Procedure
1.

2.

3.

10.10.10.10

huawei(config)#voip
NOTE
actual networking.


Issue 01 (2016-04-29)

818

Access Module
data plan.

to the data plan:
l


NOTE

l
83110001


enable

Issue 01 (2016-04-29)

819

Access Module
huawei(config)#save
----End

Prerequisites
l
board 0 command.)
1.
2.
take effect.
Precautions
CAUTION
Data Plan
Service Data Plan.
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Issue 01 (2016-04-29)
Data
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLAN
200
Media and
signaling
upstream port
0/0/1
Media IP address
and signaling IP
address
10.10.10.10/24

820

Access Module
Item
Data
Default gateway
IP address
Voice user
configuratio
n data
10.10.10.1/24
SIP interface ID
Signaling port ID
5060

equipment
200.200.200.200/24

equipment
5060
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110016
User priority

value).
Common
Parameter
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Default value
Procedure
1.

2.

Issue 01 (2016-04-29)

821

Access Module
3.

10.10.10.10

10.10.10.1.
huawei(config)#voip
NOTE





NOTE
Issue 01 (2016-04-29)

822

Access Module


enable

huawei(config)#save
----End
10.6.12 Configuring the IPTV Service (on the ONU)

This topic describes how to configure the video on demand (VoD) service and multicast
service for home gateway (HGW) users on an optical network unit (ONU) when HGWs are
connected upstream to the ONU through local area networks (LANs) or in xDSL mode.
Data Plan
The following table provides key information about the IPTV service.
Item
Data
Remarks
Traffic
profile
ID: 10
CIR: off
VLAN priority: 4
local-setting
User
VLAN in
the
scenario in
which
HGWs are
upstream
connected
to an ONU
through
LANs
Issue 01 (2016-04-29)


823

Access Module
Item
Data
Remarks
VPI/VCI of
ADSL2+
users in the
scenario in
which
HGWs are
connected
upstream to
an ONU in
ADSL2+
mode
VPI: 0

VDSL2
path mode
in the
scenario in
which
HGWs are
connected
upstream to
an ONU in
VDSL2
mode
PTM
Both the central office and HGWs must

support the PTM mode.
VLAN ID
of the VoD
service
300

service and primarily adopts only SVLAN
tags, which are transparently transmitted by
OLTs.
Multicast
VLAN ID
of the ONU
1000
Multicast
VLAN ID
of HGWs
43
A carrier generally specifies a globally

unique multicast VLAN ID for HGWs.
VCI: 35
Procedure
l
Configure the VoD service.

Create VLAN 300 with the common attribute and add upstream port 0/0/1 to the VLAN.
Configure a traffic profile for the IPTV service.

The IEEE 802.1p priority of the IPTV service is 4, and rate limitation is not required. To
check whether any existing traffic profile meets the requirements, run the display traffic
table ip command. In this example, the query result shows that no traffic profile meets
the requirements, so a traffic profile needs to be configured.
Issue 01 (2016-04-29)

824

Access Module
Add traffic profile 10 and set priority-policy to local-setting. Then, traffic is scheduled
based on the priority specified in the traffic profile.
local-setting

Configurations vary according to upstream interface types of HGWs.
If HGWs are connected to an ONU upstream through LANs and upstream packets
contain user VLAN tags, the ONU needs to perform a switch between user VLAN
IDs and SVLAN IDs.
Assume that the user VLAN ID is 1 and the Ethernet port is 0/3/1. Add a service
flow as follows:
If HGWs are connected to an ONU upstream in ADSL2+ mode, upstream packets

contain users' PVC information so the ONU needs to perform a switch between
PVC information and SVLAN IDs.
Assume that the VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0. Add a service flow
as follows:
huawei(config)#service-port 301 vlan 300 adsl vpi 0 vci 35 0/2/0 multiservice user-vlan untagged rx-cttr 10 tx-cttr 10
If HGWs are connected to an ONU upstream in VDSL2 mode, formats of upstream

packets depend on the encapsulation mode.
Assume that the VDSL2 path mode is PTM mode, port is 0/1/0, and packets from
the user VLAN are untagged. Add a service flow as follows:
huawei(config)#service-port 301 vlan 300 vdsl mode ptm 0/1/0 multiservice user-vlan untagged rx-cttr 10 tx-cttr 10

Create multicast VLAN 1000 with the common attribute and add upstream port 0/0/1 to
the multicast VLAN.
Set the IGMP version to IGMP v3.

Set the IGMP mode to IGMP proxy.


Configure a program library. Set the multicast IP address range to

224.1.1.10-224.1.1.100 and the IP address of the multicast server to 10.10.10.10.
224.1.1.100 sourceip 10.10.10.10

Issue 01 (2016-04-29)

825

Access Module
If HGWs are connected to an ONU upstream through LANs, assume that the user
VLAN ID is 43 and the Ethernet port is 0/3/1, and add a service flow as follows:
If HGWs are connected to an ONU upstream in ADSL2+ mode, assume that the
VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0, and add a service flow as follows:
If HGWs are connected to an ONU upstream in VDSL2 mode, assume that the
VDSL2 path mode is PTM mode, the user VLAN ID is 43, and the VDSL2 port is
0/1/0, and add a service flow as follows:
huawei(config)#service-port 401 vlan 1000 vdsl mode ptm 0/1/0 multiservice user-vlan 43 rx-cttr 10 tx-cttr 10
Configure a multicast user and add the user to the multicast VLAN.
Configure service flow 401 as a multicast user, add the user to multicast VLAN 1000,
and adopt the no-auth mode for the multicast user.
----End

Security Policy
service security.
Context
NOTE
Data Plan.
Procedure
l

aggregation:
Issue 01 (2016-04-29)

826

Access Module
mode.

i.
ii.



Issue 01 (2016-04-29)

i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


827

Access Module

flow.
iv.


i.

ii.


l
service.
i.

Issue 01 (2016-04-29)
level.
The VLAN level:

1)

2)

3)

effect.
4)
5)


828

Access Module
ii.
level.

i.

default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End
10.6.14 Configuring the Internet Access Service (on the HGW)

This topic describes how to configure the Internet access service on home gateways (HGWs)
that use the LAN or xDSL for upstream transmission. This configuration enables home users
to access Internet at high speeds through PCs.
Context
Home users generally access the Internet in Point-to-Point Protocol over Ethernet (PPPoE)
dial-up mode. PPPoE dial-up can be performed on PCs or HGWs.
Issue 01 (2016-04-29)

829

Access Module
HGWs have different models and appearance and therefore, their configuration processes are
not the same. This topic describes how to configure the Internet access service on an HGW
generally. The actual configuration varies depending on different HGWs.
Procedure
Step 1 Log in to the web configuration window.
1.
2.
In the login window, enter the user name and password (the default value is provided by
ISP) of the administrator and click OK.
Step 2 Set parameters for the Internet access service.

1.
2.

Parameter
Value
Bearing service
Internet
VLAN enabling
(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)
Disabled: VLAN tags are not added to upstream packets.
VLANID[1-409
4]
If VLAN enabling is set to Enabled, the values of UserVLAN,

such as 1, 2, and 3 and so on, map the values of uservlan when
Internet access service flows are created on the ONU.
(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VPI/VCI
(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
Mode
3.
NOTE
When Internet access service flows are created on the ONU, if the value of
uservlan is untagged, set this parameter to Disabled; otherwise, set it to
Enabled.
Set the VPI/VCI to be the same as that configured on the devices at

the central office. In this example, set this parameter to 0/35.
PPPoE
----End
Issue 01 (2016-04-29)

830

Access Module
10.6.15 Configuring the IPTV Service (on the HGW)

This topic describes how to configure the IPTV service on high gateways (HGWs) that use
LAN or xDSL for upstream transmission. This configuration enables home users to watch
IPTV programs using STBs and TVs.
Context
Procedure
1.
2.
Step 2 Set parameters for the multicast service.

1.
Choose multicast service configuration from the navigation tree.
2.
Set parameters for the multicast service.

Parameter
Value
Bearing service
OTHER: It is used for the IPTV service.
VLAN enabling

NOTE
When multicast service flows are configured on the ONU, if the value of
Enabled.
VLANID[1-409
4]
Multicast VLAN IDs on the HGW map the values of uservlan

when multicast service flows are created on the ONU.
VPI/VCI

(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
Issue 01 (2016-04-29)
Binding item
LAN4 (Example: LAN4 interface serves as the IPTV interface)
Mode
Bridge
DHCP
transparent
transmission
Enabled

831

Access Module
3.
----End

This topic describes how to verify service configurations in the FTTB+HGW networking
(ONU providing the VoIP service). In this scenario, the ONUs are placed in the building far
away from the central office. The ONUs provide remote service verification methods
including PPPoE dialup emulation, call emulation, and multicast emulation for configuration
and commissioning engineers to verify services remotely after services are configured.
Prerequisites
ONUs and upper-layer devices have been connected properly. The BRAS and MGC/IMS
have been configured.
The following table lists the remote verification methods for different services.
NOTE
Currently, the VoD service does not support remote verification.
Remote
Service
Verificati
on
Method
Function
Remarks
PPPoE
dialup
emulation
An ONT emulates PPPoE user

terminal software to perform dialup
and interact with the BRAS to verify
and BRAS.

service flow which does not belong
to a QinQ VLAN.
A user name, password, and
Call
emulation
An ONT emulates a VoIP user to

make a call to check whether the
VoIP service data is correctly
configured. You can also use the call
emulation function to locate a fault
when the VoIP service is faulty.

or callee in a call to a phone.
Therefore, a functioning phone is
required in the central office
where the acceptance personnel
is.
one call emulation.
Issue 01 (2016-04-29)

832

Access Module
Remote
Service
Verificati
on
Method
Function
Remarks
Multicast
emulation
This function enables you to emulate

a multicast user going online and
lead the program stream to an ONU.
By querying the real-time traffic of
the multicast program, you can check
whether the multicast function is
performing well.
The multicast service that is

configured in the dynamic
controllable multicast mode does not
support remote verification.
Procedure
l

a.
command.
b.
command.
c.

Assume that:
Caller port: 0/3/0
Called port: 0/3/15
a.

huawei(config)#test
0/3/15 callee-telno 83110016
b.
test fails.

Assume that:
Issue 01 (2016-04-29)
Multicast VLAN: 1000

833

Access Module
IP address of the multicast program: 224.1.1.10
a.
Order a multicast program by emulating a multicast user.

huawei(config)#btv
1000
b.
Query the status of the multicast user.

c.
Query the real-time traffic of the multicast program.

huawei(config-btv)#display multicast flow-statistic ip 224.1.1.10 vlan
1000
Verify the VoD service.

a.
Run the display mac-address service-port command on the ONU to query learned
MAC addresses of VoD users. The learned MAC addresses of VoD users indicate
that services are functioning properly between the ONU and VoD users.
b.
On the OLT, run the display mac-address vlan command to query the learned
ONU MAC addresses. The learned ONU MAC addresses indicate that services are
functioning properly between the OLT and ONUs.
----End
10.7 FTTB/FTTC+HGW Networking (GPON Networking,

HGW Providing the VoIP Service)
In this kind of networking, the HGW provides the Internet access and IPTV services. In
addition, the built-in IAD of the HGW provides the VoIP service by connecting to the
upstream ONU using LAN or xDSL.
Context
l
batches.
NOTE
Command Reference.
Issue 01 (2016-04-29)

834

Access Module
Mode
Query Method

default)
On the OLT:
-------------------------------------------

A gigabit-capable passive optical network (GPON) should be capable of delivering triple play
service over Category 5 cables or twisted pairs. Service requirements are described as
follows:
l
Sharing of Internet access among multiple computers in the household
Access of multiple phones in the household
Internet Protocol (IPTV) services (program preview or watch) enabled by set-top boxes
(STB)
Independent provisioning of Internet access, voice, and IPTV services
Ensured service security:
Internet access services protected against unauthorized access, hijacking or

unauthorized borrowing of user accounts, MAC/IP spoofing, and malicious attack
Voice and IPTV services protected against MAC/IP spoofing, malicious attack, and
traffic flooding attack
Easy fault location and service maintenance
Figure 10-9 shows a GPON FTTB+HGW network. The GPON OLT is deployed at the
central office and connects to the MAN using aggregation, and the ONU is deployed in the
buildings or street fiber distribution terminals. Access interfaces are deployed on the HGW
that connects to the ONU using LAN or xDSL.
l
The HGW connects to the upstream ONU through the Ethernet or xDSL port and
provides the Internet access service through the FE or Wi-Fi port and the IPTV service
through the FE port in the downstream direction.
The HGW has Layer 3 functions (such as PPPoE dialup and NAT), which enable
multiple PCs of a family to access the Internet at the same time.
The STB connected to the HGW provides IPTV program preview and access functions.
The IAD embedded in the HGW provides one or several POTS ports, which enable
multiple phones of a family to access the Internet at the same time.
ONUs applicable to this scenario: MA5616, MA5811S-DE16, MA5811S-AE08, MA5811SDE48, MA5811S-AE48, MA5818, MA5603T, MA5612, MA5878.
Issue 01 (2016-04-29)

835

Access Module
Figure 10-9 GPON FTTB+HGW Networking for the Internet, VoIP, and IPTV Services
(HGW Providing the VoIP Service)
Laptop
PC
STB
HGW
LAN
ONU
PE-AGG
OLT
NGN/IMS
UPE
TV
Metro Network
Phone
Laptop
IPTV
Headend
Splitter
STB
Internet
UPE
HGW
xDSL
PC
PE-AGG
ONU
TV
Phone

Figure 10-10 shows the configuration roadmap diagram in the FTTB+HGW networking
scenarios (HGW providing the VoIP service).
Issue 01 (2016-04-29)

836

Access Module
Figure 10-10 Configuration Roadmap Diagram in the FTTB+HGW Networking Scenarios

(HGW providing the VoIP service)
The following table describes the configuration procedure.
Issue 01 (2016-04-29)
Configured
Device
Procedure
Configuration
OLT

only after the ONU is successfully added
to an OLT.
Configure the
management channel
ONU.

configured and available, you can log in to
the ONU from the OLT to configure the
ONU.

837

Access Module
Configured
Device
ONU
OLT
ONU
HGW
Procedure
Configuration

and the ONU.

service channel, are set up on the OLT so
that services on the ONU can be normally
forwarded.

access service.
NOTE
Different ONUs have different ports, including
LAN, ADSL2+, VDSL2, G.fast and VDSL2/
G.fast vectoring ports, for the Internet access.
Select an appropriate configuration method
according to the port type.
Configure the VoIP service

channel on the ONU.
In the FTTB+HGW networking (HGW

provides the VoIP service), the built-in
IAD of the HGW provides the VoIP
service. Therefore, VoIP service
parameters do not need to be configured
on the ONU and only transparent
transmission service flows need to be
created.
Configure the IPTV

service on the ONU.
IPTV services include VoD and multicast

separately.
Configure the link

policy.

on priorities ensures service reliability.
The global configuration of security

access service on the
HGW.
HGWs have different models and

appearances but their configuration
procedures are similar. This topic uses the
HG239 that uses LAN for upstream
transmission and the HG527 uses
ADSL2+ for upstream transmission as
examples.
NOTE
Vectoring is supported by the HG612 and
HG622 only.
Issue 01 (2016-04-29)
Configure the IPTV

services on the HGW.
Configure the VoIP service

on the HGW.
This topic describes how to configure the

voice service on home gateways (HGWs)
that use the LAN or xDSL for upstream
transmission. This configuration enables
home users to enjoy the POTS service by
using an analog telephone.

838

Access Module
Configured
Device
Procedure
Configuration
ONU
Verify the services.
ONUs provide remote service verification

emulation, call emulation, and multicast
emulation to allow configuration and
commissioning engineers to verify
services remotely after service
configuration. This remote service
verification eliminates a second on-site
operation.
HGW
Voice services on the HGW do no support

remote service verification.

Context
l
Profile
Type
Function
Command
DBA
profile



ONT lines.

alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)

839

Access Module

Mode
Usage Scenario
Command
Add an
ONU
offline.


ONU.
Online
confirm
an ONU.

Data Plan
Item
Data
DBA profile
NOTE

Profile type: Type1
Profile type: Type1
Profile type: Type4
Profile type: Type3
Profile type: Type3
Issue 01 (2016-04-29)

840

Access Module
Item
Data
Line profile
NOTE

Profile ID: 10
PON port: 0/2/1

ONT ID: 1
Procedure
NOTE
1.

max 16384
max 16384
2.
add
add
add
add
profile-name
profile-name
profile-name
profile-name


a.

NOTE
b.
c.
4
5
6
7
8
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
dba-profile-name
fttb_dba_mngt
fttb_dba_voip
fttb_dba_hsi
fttb_dba_vod
fttb_dba_iptv
GEM port 11 for T-CONT 4. Use the same
Issue 01 (2016-04-29)
add 11
method
add 12
add 13
add 14

eth tcont
to create
eth tcont
eth tcont
eth tcont
4
//Create
other GEM ports.
5
6
6
//Create
841

Access Module
section.
d.
......
......
e.
mapping 11 0 vlan 8
3.
generated.

discovered ONU.
l
Add an ONU offline.


1.

Issue 01 (2016-04-29)

842

Access Module

normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
Run state
: online
Config state
: normal
normally.
----End
Follow-up Procedure
l
ONU.

and the ONU
Issue 01 (2016-04-29)

843

Access Module
Data plan
Item
Data
Remarks
Management VLAN
and management IP
address on the OLT
side
Management VLAN
and management IP
address on the ONU
side


smart VLAN
address: 192.168.50.1/24

smart VLAN
address: 192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.254 vlan 8

l
----End
Issue 01 (2016-04-29)

844

Access Module
10.7.5 Configuring Service Channels Between an OLT and an

ONU
This topic describes how to configure service channels between an optical line terminal (OLT)
and an optical network unit (ONU) on a gigabit-capable passive optical network (GPON).
After channels for involved service types are configured on an OLT to which an ONU is
connected, packets of the service types from the ONU can be forwarded based on planned
VLANs and policies at Layer 2.
Prerequisites
1.
10.7.3 Adding an ONU to an OLT is performed.
2.
10.7.4 Configuring the Management Channel Between the OLT and the ONU is
performed.
Data Plan
The following table provides key information about the service channels between an OLT and
an ONU.
Service
Type
VLAN Plan
Remarks
Internet
access
service
S-VLAN ID: 100; SVLAN attribute:

stacking
Plan the Internet access service in per user per

service per VLAN (PUPSPV) mode and apply SVLAN+C-VLAN to differentiate users.
C-VLAN ID: 1001-1016
For details, see 10.3.3 Principle of Internet

S-VLAN ID: 200
The voice over IP (VoIP) service is a carrieroperating, closed service and primarily adopts
only S-VLAN tags, which are transparently
transmitted by OLTs.
VoIP
service
C-VLAN ID: 200
For details, see 10.3.5 Principle of VoIP Service

Data Plan.
VoD
service
S-VLAN ID: 300
Plan the video on demand (VoD) service in per

user per VLAN (PUPV) mode if possible, as the
VoD service requires only a few VLAN
resources.
service and primarily adopts only S-VLAN tags,
which are transparently transmitted by OLTs.
Service Data Plan.
Issue 01 (2016-04-29)

845

Access Module
Service
Type
VLAN Plan
Remarks
Multicast
service
Multicast VLAN ID:

1000
The multicast service is a carrier-operating,

closed service and primarily adopts only SVLAN tags.
Multicast cascading
port: 0/2/1

Service Data Plan.
IGMP mode: IGMP

proxy
Multicast IP address
range:
224.1.1.10-224.1.1.100
IP address of the
multicast server:
10.10.10.10/24
NOTE
C-VLANs in the preceding table are defined for OLTs. That is, they are upstream VLANs or S-VLANs of
ONUs.
Procedure
l

a.

S-VLAN.
b.

required. To check whether any existing traffic profile meets the requirements, run
the display traffic table ip command. In this example, the query result shows that
traffic profile 6 meets the requirements, so no traffic profile needs to be configured.
c.
Configure a service flow for receiving and transparently transmitting the Internet
access service from the ONU side.
being 1001 (example value). The ONU is connected to GPON port 0/2/1, upstream
and downstream traffic are rate-limited on the ONU but not on the OLT, and traffic
profile 6 is referenced.
huawei(config)#service-port vlan 100 gpon 0/2/1 ont 1 gemport 13 multiservice user-vlan 1001 tag-transform translate-and-add rx-cttr 6 tx-cttr
6
l
Issue 01 (2016-04-29)
Configure a channel for the VoIP service.

846

Access Module
a.

S-VLAN.
b.

The 802.1p priority of the VoIP service is 5, and rate limitation is not required. To
c.
Configure a service flow for receiving and transparently transmitting the VoIP
service from the ONU side.
referenced.

a.

S-VLAN.
b.

c.

referenced.
l
Issue 01 (2016-04-29)

847

Access Module
a.

the S-VLAN.
b.

being 1000. ONT 1 is connected to GPON port 0/2/1, upstream and downstream
referenced.
c.

Set GPON port 0/2/1 as a multicast cascading port, ONU ID to 1, and GEM port 16
to carry the multicast service.
huawei(config)#btv
d.

Set the IGMP version to IGMPv3.
e.
Set the IGMP mode.

f.

Set the IGMP upstream port to port 0/19/0.
g.

Set the multicast IP address range to 224.1.1.10-224.1.1.100 and the IP address of
the multicast server to 10.10.10.10.
224.1.1.100 sourceip 10.10.10.10
----End
10.7.6 Configuring the Internet Access Service (LAN Access, on

the ONU)
users on an optical network unit (ONU) when HGWs are connected upstream to the ONU
through local area networks (LANs).
Data Plan
The following table provides key information about the Internet access service (LAN access).
Issue 01 (2016-04-29)

848

Access Module
Item
Data
Remarks
Traffic
profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
User
VLAN
Untagged

Procedure


l
1001):
10, and bind traffic profile 8 to the user VLAN./
----End
Issue 01 (2016-04-29)

849

Access Module

on the ONU)
Context
Mode
Query Method
ADSL2+ common mode

(RFC2662 mode)
On the ONU:
--------------------------------------------
Profile
Type
Function
Configuration
ADSL2+
line
profile



l Channel mode

common ADSL ports.
depth

l Noise margin


Issue 01 (2016-04-29)

Commands:

850

Access Module
Profile
Type
Function
Configuration
ADSL2+
alarm
profile
to the NMS.
Commands:
Data Plan
access).
Item
Data
Remarks
Traffic
profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
VPI/VCI of
ADSL2+
users
VPI: 0
ADSL2+
line profile

parameters:
VCI: 35

compatibility

profile.

interleaved
l Maximum upstream/
24544/1024
ADSL2+
alarm
profile
ID: 1 (default)

not report alarms.
Procedure
Issue 01 (2016-04-29)

851

Access Module



follows:

l
requirements.

ADSL2+ port 0/2/0.
----End

the ONU)
Context
Issue 01 (2016-04-29)

852

Access Module
Mode
Query Method

mode)
On the ONU:
--------------------------------------------
Table 10-26.
Issue 01 (2016-04-29)
Templ
ate
Type
Function
Configuration
VDSL2
line
template


ports.

back-off (DPBO).

retransmission.



quickadd

853

Access Module
Templ
ate
Type
Function
Configuration
VDSL2
alarm
template



CPEs:

(FECS)



COs and CPEs:

Data Plan
Item
Data
Remarks
Traffic profile
ID: 8
CIR: 4 Mbit/s
VLAN priority: 0
local-setting
Issue 01 (2016-04-29)

854

Access Module
Item
Data
Remarks
VDSL2 line
mode
PTM

mode and PTM mode.
mode.
mode.
VDSL2 line
template
Line profile ID: 6

Line template ID: 6
VDSL2 alarm
template

(default)
(default)

smaller one.
Procedure

Issue 01 (2016-04-29)

855

Access Module


Command:
neglected
>
Transmission mode:
>
0: Custom
>
1: All (G.992.1~5,T1.413,G.993.2)
>
2: Full rate (G.992.1/3/5,T1.413,G.993.2)
>
3: G.DMT (G.992.1/3/5,G.993.2)
>
4: G.HS (G.992.1~5,G.993.2)
>
5: ADSL (G.992.1~5,T1.413)
>
6: VDSL (G.993.2)
>
> Bit swap upstream
2]:
2]:
>
//Note that the
>
>
>
//Note that the
>
>
>
>
1-defmode
>
[3]:2
>
1-defmode
>
Please select [1]:
>
G.993.2 profile:
>
1-Profile8a
2-Profile8b
3-Profile8c
4-Profile8d
>
5-Profile12a
6-Profile12b
7-Profile17a
8-Profile30a
>
>
>
1-AnnexA998-D-32
2-AnnexA998-D-64
>
>
Issue 01 (2016-04-29)

856

Access Module
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
10-AnnexA998-D-48
11-AnnexA998-D-128
//Enable US0.
(-255~145 0.1dBm) [145]:
(-255~145 0.1dBm) [145]:
1-defmode
[3]:
Will you set network timing reference? (y/n) [n]:
Will you set INM parameter? (y/n) [n]:
Will you set SOS downstream parameter? (y/n) [n]:
Will you set SOS upstream parameter? (y/n) [n]:
Will you set the G.998.4 retransmission function? (y/n) [n]:
Will you set force framer setting for inp? (y/n) [n]:

Command:
neglected
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
1-noProtection
2-halfSymbol
3-singleSymbol
4-twoSymbols
>
5-threeSymbols
6-fourSymbols
7-fiveSymbols
8-sixSymbols
>
9-sevenSymbols
10-eightSymbols
11-nineSymbols
12-tenSymbols
>
>
>
>
>
>
>
>
>
Command:
Issue 01 (2016-04-29)

857

Access Module

neglected
>
>
>
>

port 0/1/0.
----End
10.7.9 Configuring the Internet Access Service (G.fast Access, on

the ONU)
users on an optical network unit (ONU) when HGWs are connected upstream to the ONU in
G.fast mode.
Data Plan
Mode
Query Method
G.fast TR165 mode
On the ONU:
huawei(config)#display xdsl
mode
----------------------------------------------------------------------G.fast Current mode :
tr165
-----------------------------------------------------------------------
Table 10-28 provides key information about the Internet access service (G.fast access).
Issue 01 (2016-04-29)

858

Access Module
Table 10-28 Key information about the Internet access service (G.fast access)
Item
Data
Remarks
Traffic profile
ID: 8
A traffic profile limits rates.
CIR: 120 Mbit/s

VLAN priority: 0
local-setting
G.fast line
profile
G.fast reach: approximately 200

m, with the sum of typical
upstream and downstream rates
of being approximately 160
Mbit/s
G.fast port rates can be limited based

on the traffic profile or G.fast line
profile. When both the profiles take
effect, the lower activation rate takes
effect.
Ratio of upstream rate to

downstream rate: 1:3
G.fast alarm
template
Start G.fast frequency: 2.2 MHz
This example uses the lowest start

G.fast frequency. If both G.fast lines
and VDSL2 lines are required on one
network, ensure that they use different
frequencies. For example, if VDSL2
lines use the 17a profile, the start
G.fast frequency must be at least 17
MHz. Some idle frequencies are
required between the VDSL2 and
G.fast frequencies to prevent inter-line
crosstalk.

(default)


(default)
Procedure
Step 1 Use the default user name root and password admin123 to remotely log in to the ONU from
the OLT.
Step 2 Configure the traffic profile.
Run the display traffic table ip command to query existing traffic profiles. If no existing
traffic profile meets usage requirements, run the traffic table ip command to add a new one.
The configuration of the added traffic profile is as follows: The profile ID is 16, the CIR is
120 Mbit/s, the priority of upstream packets is 0, and downstream packets are scheduled using
the priority specified in the traffic profile.
local-setting
Issue 01 (2016-04-29)

859

Access Module
Step 3 Create S-VLANs.

Create S-VLANs 1001 through 1016, which correspond to the S-VLANs created on the OLT.
These S-VLANs are of smart type with the common attribute. Then, add uplink port 0/0/1 to
these S-VLANs.

This example uses G.fast port 0/1/0, VLAN ID 1001, untagged packets from the user VLAN,
and service flow ID 101. Add a service port as follows:
huawei(config)#service-port 101 vlan 1001 g.fast 0/1/0 multi-service user-vlan
Step 5 Configure a G.fast line profile.

This example uses the parameter settings in the preceding data plan.
huawei(config)#g.fast tdd-profile quickadd
{ <cr>|name<K>|profile-index<2,4294967294>|symbol-parameter<K> }:3
{ <cr>|name<K>|symbol-parameter<K> }:symbol-parameter
{ symbol-num-per-tdd-frame<E><23,36> }:36
//The default G.9701 setting is used
as an example.
{ symbol-num-per-tdd-frame-ds<6,32> }:27 //The ratio of the upstream rate to
the downstream rate is 1:3.
{ <cr>|name<K>|operation-interval<K> }:operation-interval
{ ttr-ds<1,32> }:5
{ ttr-us<1,25> }:2
{ tbudget-ds<1,32> }:8 //This parameter can be configured but does not take
{ tbudget-us<1,25> }:2 //This parameter can be configured but does not take
{ <cr>|name<K> }:
Command:
g.fast tdd-profile quickadd 3 symbol-parameter 36 27 operation-interval
5 2 8 2
//This profile applies to rate limitation in the downstream direction.
huawei(config)#xdsl data-rate-profile quickadd g.fast-rate 32 120000 60000
120000 desc G.FAST-PORT0-DS
//This profile applies to rate limitation in the upstream direction.
huawei(config)#xdsl data-rate-profile quickadd g.fast-rate 32 40000 8000 40000
desc G.FAST-PORT0-US
//The lowest start G.fast frequency is 2.2 MHz, and the subcarrier index is 43.
huawei(config)#xdsl line-spectrum-profile quickadd g.fast-line-spectrum 2 43
//Configure retransmission parameters. Set parameter values based on electrical
and noise parameters of the site.
huawei(config)#xdsl inp-delay-profile quickadd g.fast-inp-delay g.fast-iat-rein 1
1 g
.fast-inp-min-rein 4 2 g.fast-inp-min-shine 2 2 g.fast-shine-ratio 20
20
Step 6 Configure a G.fast alarm template.

This example uses the default G.fast alarm template (ID: 1).
Issue 01 (2016-04-29)

860

Access Module
Step 7 Bind the line profile and alarm template and activate the G.fast port.
//Bind the G.fast TDD profile to the ONU.
huawei(config)#g.fast tdd-profile-config 0 profile-index 3
//Bind the line profile and alarm template to the G.fast port and activate this
port.
huawei(config)#interface g.fast 0/1
huawei(config-if-g.fast-0/1)#deactivate 0
huawei(config-if-g.fast-0/1)#activate 0 prof-idx ds-rate 9 us-rate 10 spectrum 2
inp-delay 5
huawei(config-if-g.fast-0/1)#alarm-config 0 1
----End

Context
10-29.
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Global band
plan
In the vectoring
requires that the
upstream band and
downstream band are
separate from each
band plan must be
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from each
other, the port
cannot be
activated.

861

Access Module
Item
Function
Description
Commands
Global
vectoring
configurations
Vectoring
configurations take
effect only when
enabled.
l Before enabling
vectoring, globally
configure the band
plan.
xdsl vectoring

of canceling the
upstream and
in the vectoring
the configured
implements the
vectoring algorithm
on the ports in the
on profile
configurations.

profile 1.
The Vectoring
prevent adverse
impact on system
the policy for
ports based on site
requirements.

for controlling
frequent online and
Vectoring
profile
Policy for
controlling
frequent online
and offline on
ports
Issue 01 (2016-04-29)
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Query a vectoring
vectoring-profile
Default value:
cancelation: enable
l Downstream
crosstalk
cancelation: enable

862

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring
crosstalk
matrix
The vectoring
Before querying
vectoring crosstalk
global vectoring
function is enabled
and activated.


863

Access Module
Item
Function
Description
Commands
Policy for
activating a
legacy
customer
premises
equipment
(CPE)
A legacy CPE is a
VDSL2 CPE
If such a CPE is
cannot be canceled,
deteriorate. To
set the activation
policy of a legacy
CPE based on site
requirements.

l no-limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode (G.993.2
which the
Vectoring system
performance is
affected. This
mode is used in the
Vectoring initial
phase when a large
number of CPEs
need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated in
common VDSL2
mode but the line
PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode is
used in Vectoring
medium phase
when some CPEs
have not been
upgrade or
replaced.
friendly is used in
the downstream
direction and PSD
Issue 01 (2016-04-29)

864

Access Module
Item
Function
Description
Commands
automatic shaping
is used in the
upstream direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Issue 01 (2016-04-29)

865

Access Module

Item
Function
Description
Commands
Global band plan
In the vectoring
algorithm, the
system requires
that the upstream
band and
downstream band
are separate from
each other.
Therefore, the
band plan must
be globally
configured.
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
Vectoring
configurations
take effect only
when vectoring is
globally enabled.
l Vectoring can be
globally enabled
only when devices
are configured
with VP boards.
Global vectoring
configurations
globally enabled,
if the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from
each other, the
port cannot be
activated.
xdsl vectoring
l Before enabling
vectoring,
globally configure
the band plan.
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Issue 01 (2016-04-29)

866

Access Module
Item
Function
Description
Commands
Vectoring profile
Configure the
function of
canceling the
upstream and
downstream
crosstalk in the
vectoring profile.
After binding the
configured
vectoring profile
to the ports, the
system
implements the
vectoring
algorithm on the
ports in the
vectoring group
based on profile
configurations.

are bound to
Commands:
The Vectoring
algorithm is
executed every
time a port in a
Vectoring group
goes online or
offline. To
prevent adverse
impact on system
functions due to
long-term
running Vectoring
tasks caused by
frequent online
and offline on a
port, set the
policy for
controlling
frequent online
and offline on
ports based on
site requirements.

for controlling
frequent online and

frequent online and
offline on ports
Issue 01 (2016-04-29)
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable
l Add a vectoring
profile: xdsl
vectoring-profile
add
l Modify a
vectoring profile:
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
l Bind a vectoring
vectoring-config
(VDSL mode)

867

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Vectoring crosstalk
matrix
The vectoring
crosstalk matrix
refers to crosstalk
on a port in a
vectoring group
from other ports
in the same
vectoring group.
Before querying
vectoring crosstalk
matrix, ensure that
function is enabled
is in a vectoring


868

Access Module
Item
Function
Description
Commands

a legacy customer
premises equipment
(CPE)
A legacy CPE is
a VDSL2 CPE
(supporting G.
993.2, not G.
993.5) that does
not support
Vectoring. If such
a CPE is
activated in G.
993.2 mode in the
Vectoring system,
the crosstalk
impact on other
lines cannot be
canceled, causing
the Vectoring
system
performance to
deteriorate. To
minimize the
impact, set the
activation policy
of a legacy CPE
based on site
requirements.

for activating a
limit.
l no-limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode (G.
993.2 mode), or
non-Vectoring
mode, in which
the Vectoring
system
performance is
affected. This
mode is used in
the Vectoring
initial phase when
a large number of
CPEs need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode but
the line PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode
is used in
Vectoring medium
phase when some
CPEs have not
been upgrade or
replaced.
friendly is used in
Issue 01 (2016-04-29)

869

Access Module
Item
Function
Description
Commands
the downstream
direction and PSD
automatic shaping
is used in the
upstream
direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Data Plan
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l US0 type: type-a

legacy customer
premises equipment
(CPE)
Issue 01 (2016-04-29)
no-limit


application.
870

Access Module
Item
Data
Description

frequent online and
offline on ports
no-limit
Vectoring group
Group ID: 1

Vectoring profile

MA5611S/MA5811S:

cancelation: enable
cancelation: enable
cancelation: enable
cancelation: enable
NOTE
Procedure
l

a.

b.

c.

d.
e.

Issue 01 (2016-04-29)

871

Access Module
f.
Save the data.

huawei(config)#save

a.
b.

c.
vectoring group.
huawei
d.

e.
f.

g.
Save the data.

huawei(config)#save
----End
10.7.11 Configuring the Voice Service Channel (on the ONU)

This topic describes how to configure the VoIP service on an ONU. In this scenario, The
HGW provides the VoIP service and the ONU is configured to establish VoIP service
channels.
Data Plan
Data plan for configuring the VoIP service on the ONU
Item
Data
Remarks
Upstream
VLAN
200
The upstream VLAN on the ONU is

also called the SVLAN on the
ONU. It corresponds to the CVLAN
on the OLT.
The VoIP service is a closed service
operated by carriers. SVLAN with a
single tag is the mainstream
application. The OLT transparently
transmits the SVLAN of the ONU.
Issue 01 (2016-04-29)

872

Access Module
Item
Data
Remarks
Traffic
profile
ID: 9
For the VoIP service, it is

recommended to rate limit traffic on
the BRAS or SR without using
traffic profiles.
Committed rate: off

VLAN priority
Priority policy: Local-Setting
User port
The HGW uses LAN for upstream

transmission: 0/3/1
Different types of HGWs establish

service flows in different ways.
The HGW uses ADSL2+ for

upstream transmission: 0/2/0
The HGW uses VDSL2 for
upstream transmission: 0/1/0
User VLAN
on the HGW
200
It is recommended that the user

VLAN on the HGW be the same as
the upstream VLAN on the ONU
when the HGW provides the VoIP
service.
Procedure
Step 1 Create the upstream VLAN and add upstream ports 0/0/1 to it.
Step 2 Configure a VoIP service traffic profile.

The 802.1p priority of the VoIP service is 5 and the traffic profile specifies no rate limit. Run
the display traffic table ip command to query existing traffic profiles in the system. If there
is no traffic profile to meet the requirements listed in the data plan, create one.
Add traffic profile 9 and set Local-Setting to priority-policy so that packets are scheduled
according to their priorities.
huawei(config)#traffic table ip index 9 cir off priority 5 priority-policy LocalSetting
Step 3 Create the VoIP service flow.

l
For the HGW that uses LAN for upstream transmission, the VoIP service is configured
as follows:
For the HGW that uses ADSL2+ for upstream transmission, the VoIP service is
configured as follows:
huawei(config)#service-port 201 vlan 200 adsl 0/2/0 vpi 0 vci 35 multiservice user-vlan
Issue 01 (2016-04-29)
For the HGW that uses VDSL2 for upstream transmission, the VoIP service is configured
as follows:

873

Access Module
huawei(config)#service-port 201 vlan 200 vdsl mode ptm 0/1/0 multi-service

user-vlan
----End
10.7.12 Configuring the IPTV Service (on the ONU)

This topic describes how to configure the video on demand (VoD) service and multicast
service for home gateway (HGW) users on an optical network unit (ONU) when HGWs are
connected upstream to the ONU through local area networks (LANs) or in xDSL mode.
Data Plan
The following table provides key information about the IPTV service.
Item
Data
Remarks
Traffic
profile
ID: 10
CIR: off
VLAN priority: 4
local-setting
Issue 01 (2016-04-29)
User
VLAN in
the
scenario in
which
HGWs are
upstream
connected
to an ONU
through
LANs

VPI/VCI of
ADSL2+
users in the
scenario in
which
HGWs are
connected
upstream to
an ONU in
ADSL2+
mode
VPI: 0

VCI: 35

874

Access Module
Item
Data
Remarks
VDSL2
path mode
in the
scenario in
which
HGWs are
connected
upstream to
an ONU in
VDSL2
mode
PTM
Both the central office and HGWs must

support the PTM mode.
VLAN ID
of the VoD
service
300

service and primarily adopts only SVLAN
tags, which are transparently transmitted by
OLTs.
Multicast
VLAN ID
of the ONU
1000
Multicast
VLAN ID
of HGWs
43
A carrier generally specifies a globally

unique multicast VLAN ID for HGWs.
Procedure
l


table ip command. In this example, the query result shows that no traffic profile meets
the requirements, so a traffic profile needs to be configured.
Add traffic profile 10 and set priority-policy to local-setting. Then, traffic is scheduled
based on the priority specified in the traffic profile.
local-setting

Issue 01 (2016-04-29)
contain user VLAN tags, the ONU needs to perform a switch between user VLAN
IDs and SVLAN IDs.
875

Access Module
Assume that the user VLAN ID is 1 and the Ethernet port is 0/3/1. Add a service
flow as follows:

contain users' PVC information so the ONU needs to perform a switch between
PVC information and SVLAN IDs.
Assume that the VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0. Add a service flow
as follows:

Assume that the VDSL2 path mode is PTM mode, port is 0/1/0, and packets from
the user VLAN are untagged. Add a service flow as follows:
huawei(config)#service-port 301 vlan 300 vdsl mode ptm 0/1/0 multiservice user-vlan untagged rx-cttr 10 tx-cttr 10

Create multicast VLAN 1000 with the common attribute and add upstream port 0/0/1 to
the multicast VLAN.



Configure a program library. Set the multicast IP address range to

224.1.1.10-224.1.1.100 and the IP address of the multicast server to 10.10.10.10.
224.1.1.100 sourceip 10.10.10.10

If HGWs are connected to an ONU upstream through LANs, assume that the user
VLAN ID is 43 and the Ethernet port is 0/3/1, and add a service flow as follows:
Issue 01 (2016-04-29)

876

Access Module
If HGWs are connected to an ONU upstream in VDSL2 mode, assume that the
VDSL2 path mode is PTM mode, the user VLAN ID is 43, and the VDSL2 port is
0/1/0, and add a service flow as follows:
huawei(config)#service-port 401 vlan 1000 vdsl mode ptm 0/1/0 multiservice user-vlan 43 rx-cttr 10 tx-cttr 10
Configure a multicast user and add the user to the multicast VLAN.
Configure service flow 401 as a multicast user, add the user to multicast VLAN 1000,
and adopt the no-auth mode for the multicast user.
----End

Security Policies
service security.
Context
NOTE
Data Plan.
Procedure
l

aggregation:
mode.

Issue 01 (2016-04-29)

877

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)

878

Access Module
i.

ii.


l
service.
i.

level.
The VLAN level:
ii.
1)

2)

3)

effect.
4)
5)

level.

i.

Issue 01 (2016-04-29)

879

Access Module
default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

Context
Procedure
1.
2.
Issue 01 (2016-04-29)

880

Access Module

1.
2.

Parameter
Value
Bearing service
Internet
VLAN enabling
(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VLANID[1-409
4]

(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VPI/VCI
(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
Mode
3.
NOTE
Enabled.

PPPoE
----End

Context
Issue 01 (2016-04-29)

881

Access Module
Procedure
1.
2.

1.
2.

Parameter
Value
Bearing service
VLAN enabling

NOTE
Enabled.
VLANID[1-409
4]

VPI/VCI

(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
3.
Binding item
Mode
Bridge
DHCP
transparent
transmission
Enabled
----End
10.7.16 Configuring the VoIP Service (on the HGW)

This topic describes how to configure the voice service on home gateways (HGWs) that use
the LAN or xDSL for upstream transmission. This configuration enables home users to enjoy
the POTS service by using an analog telephone.
Context
not the same. This topic describes how to configure the voice service on an HGW. The actual
configuration varies depending on different HGWs.
Issue 01 (2016-04-29)

882

Access Module
Procedure
1.
2.
Step 2 Set parameters of the voice service.

1.
2.

Parameter
Value
Bearing service
VoIP
Enabling status
Enabled
VPI/VCI

(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
3.
Issue 01 (2016-04-29)
Vlan ID
The voice VLAN IDs on the HGW map the values of uservlan
when voice service flows are created on the ONU.
802.1p
Enabled
Mode
Route: Route mode
DHCP
Enabled
NAT
Enabled
Choose the voice telephone number configuration from the navigation tree. Set the
parameters as follows:
Parameter
Value
Address
Port ID
Enabled
Enabled
User number
To use the VoIP account, you can set the account to the user
telephone number. In this example, set the user telephone number
to 83110001.
User password

883

Access Module
4.
----End

This topic describes the remote verification methods in the FTTB+HGW scenario (HGW
providing the VoIP service). ONUs provide remote service verification methods including
PPPoE dialup emulation and multicast emulation for configuration and commissioning
engineers to verify services remotely after service configuration, avoiding a second on-site
operation.
Prerequisites
ONUs and upper-layer devices are connected properly. The BRAS and MGC/IMS have been
configured.
Context
This topic describes the remote verification method for different service.
NOTE
The VoD service and HGW VoIP service currently do not support remote verification.
Remote
Service
Verificati
on
Method
Function
Remarks
PPPoE
dialup
emulation
An ONU emulates a PPPoE user

terminal software to perform dialup
and interact with the BRAS to verify
and BRAS.
l PPPoE dialup emulation requires

a service flow which does not
belong to a QinQ VLAN.
Multicast
emulation
This function enables you to emulate

a multicast user goes online and lead
the program stream to an ONU. By
querying the real-time traffic of the
multicast program, you can check
whether the multicast function is
performing well.
The multicast service configured in

dynamic controllable multicast mode
does not support the remote
acceptance function.
Procedure
l
Issue 01 (2016-04-29)

884

Access Module
a.
command.
b.
command.
c.

Assume that:
a.

huawei(config)#btv
1000
b.

c.

1000

a.
Run the display mac-address service-port command on the ONU to query learned
MAC addresses of VoD users. The learned MAC addresses of VoD users indicate
that services are functioning properly between the ONU and VoD users.
b.
On the OLT, run the display mac-address vlan command to query the learned
ONU MAC addresses. The learned ONU MAC addresses indicate that services are
functioning properly between the OLT and ONUs.
Verify the VoIP service.

a.
Log in to the HGW management web page.

For details, see the 10.7.16 Configuring the VoIP Service (on the HGW).
b.
Choose Status > Broadband VoIP Information (here depending on the actual
HGW web page) to query the service registration status and telephone number.
Expected service registration status: Register successfully.
----End
10.8 FTTB and FTTC Ethernet Cascade Networking (ONU

Works as an Independent NE)
Cascade a multi-dwelling unit (MDU) to an optical line terminal (OLT) using an Ethernet
access board, the MDU works as an independent NE. The following topics describe the
configuration method of this scenario.
Issue 01 (2016-04-29)

885

Access Module
10.8.1 Service Requirements and Usage Scenario

If an optical network unit (ONU) works as an independent NE on a fiber to the building
(FTTB) or fiber to the curb (FTTC) Ethernet cascading network, the service requirements and
usage scenario of this network are the same as those of a PON network. The differences lie in
the ONU upstream transmission mode and the user access mode. Specifically, on an FTTB or
FTTC Ethernet cascading network, an ONU connects to the optical line terminal (OLT)
through an Ethernet port and users connect to the ONU through xDSL lines; on a PON
network, an ONU connects to the OLT through a PON port and users connect to the ONU
through optical lines.
Networking Scenario
Service Requirements and Usage Scenario
FTTB/FTTC Networking
(xDSL Access Without
HGW)
See 10.5.1 Service Requirements and Application

Scenario. For the networking diagram, the Ethernet
cascading network does not need the optical splitter.
FTTB/FTTC+HGW
Networking (ONU Providing
the VoIP Service)

Scenario. Focus only on the xDSL access. For the
networking diagram, the Ethernet cascading network does
not need the optical splitter.
FTTB/FTTC+HGW
Networking (HGW Providing
the VoIP Service)

Scenario. Focus only on the xDSL access. For the
networking diagram, the Ethernet cascading network does
not need the optical splitter.
The following figure shows the networking in the preceding scenarios.
Issue 01 (2016-04-29)

886

Access Module
Phone
xD
SL
+P
OT
S
Modem Splitter
PC
S
POT
Phone
ONU
GE
Laptop
PE-AGG
OLT
HGW
PC
STB
Splitter
Metro Network
ONU
IPTV Headend
UPE
PE-AGG
Internet
GE
Phone
UPE
GE
PO
TS
TV
xDSL+
POTS
NGN/IMS
Phone
Laptop
HGW
PC
xDSL
STB
ONU
TV
Phone

Figure 10-11 shows the configuration procedure for a fiber to the building (FTTB) or fiber to
the curb (FTTC) Ethernet cascading network where an optical network unit (ONU) works as
an independent NE.
Issue 01 (2016-04-29)

887

Access Module
Figure 10-11 Configuration process for an FTTB or FTTC Ethernet cascading network where
an ONU works as an independent NE
Issue 01 (2016-04-29)
Configur
ation
Object
Step
Description
Optical
line
terminal
(OLT)
Configure the
working mode of
an Ethernet
cascading board.
An Ethernet cascading board supports various working

modes. Configure the working mode to cascade in this
scenario.

888

Access Module
Configur
ation
Object
ONU
Home
gateway
(HGW)
OLT
ONU
ONU
HGW
Step
Description
Configure the
management
channel between
the OLT and the
ONU.
After the inband management channel between the

OLT and the ONU is configured and available, you
can log in to the ONU from the OLT to configure the
ONU.
Configure the
service channel
between the OLT
and the ONU.
Configure a channel on the OLT for the Internet access

service, voice service, or IPTV service.
Configure the
service flow on the
ONU or HGW.
Configure the service flow based on site requirements.
Configure link
aggregation,
congestion control,
and security
policies.
The global configuration of upstream link aggregation

and queue scheduling based on priorities ensures
service reliability. The global configuration of security
Verify services.
ONUs support remote service verification methods,

such as PPPoE dialup, call, and multicast service
emulation tests. This allows commissioning and
configuration engineers to remotely verify services.
If the remote software commissioning using GE

upstream transmission is required, configure the
management channel on the OLT. If the remote
software commissioning using GE upstream
transmission is not required, configure the
management channel on both the OLT and the ONU.
The configuration object listed in this table is only the
main object.
The voice service on the HGW does not support

remote verification.
10.8.3 Configuring the Working Mode of an Ethernet Cascading

Board
This section describes how to configure the working mode of an Ethernet cascading board to
cascade. After the configuration, an optical network unit (ONU) can cascade with an optical
line terminal (OLT) equipped with the Ethernet cascading board.
Issue 01 (2016-04-29)

889

Access Module
Data Plan
Item
Data
ETHB cascading board
Cascading port: 0/3/0
OPGD cascading board
Cascading port: 0/2/0
Procedure
l
Configure the working mode of an ETHB cascading board to cascade.

huawei(config)#interface eth 0/3
huawei(config-if-eth-0/3)#network-role cascade
huawei(config-if-eth-0/3)#quit
NOTICE
If the working mode of the ETHB cascading board was originally extend, the board
restarts after this operation is performed.
l
Configure the working mode of an OPGD cascading board to cascade.

huawei(config)#interface opg 0/2
huawei(config-if-opg-0/2)#network-role cascade
huawei(config-if-opg-0/2)#quit
----End
10.8.4 Configuring the Management Channel Between an OLT

and an ONU
This section describes how to configure a management channel between an optical line
terminal (OLT) and an optical network unit (ONU). After the configuration, you can log in to
the ONU from the OLT and configure the ONU.
Context
FTTx V100R012 or later supports remote software commissioning using GE upstream
transmission. Similar to the remote software commissioning function supported by a PON
network, the remote software commissioning using GE upstream transmission implements
one site visit for newly deployed GE-upstream devices. Before using remote software
commissioning using GE upstream transmission, learn the prerequisites and notes from the
corresponding version's Feature Guide.
Issue 01 (2016-04-29)

890

Access Module
Data Plan When Remote Software Commissioning Using GE Upstream

Transmission Is Enabled
Configuration
Item
Data
Remarks
Ethernet cascading
port on the OLT
ETHB cascading board: 0/3/0
None
Management VLAN
and IP address of
the OLT
ID of the management VLAN: 8
OPGD cascading board: 0/2/0
Type of the management VLAN:

smart
Management IP address:
192.168.50.1/24
Management VLAN
and IP address of
the ONU

smart
Here we take the scenario of "to

remotely log in to the ONU from
the OLT for configuration" for
example, so we need to ensure
that the management VLAN of
the OLT is the same as that of
the ONU and that the
management IP address of the
OLT is in the same network
segment as that of the ONU.
192.168.50.2/24
Management profile
of the ONU
ID: 64
None
Name: snmp-profile_64
SNMP version: SNMPv2c
Data Plan When Remote Software Commissioning Using GE Upstream

Transmission Is Disabled
Configuration
Item
Data
Remarks
Ethernet cascading
port on the OLT
ETHB cascading board: 0/3/0
None
Management VLAN
and IP address of
the OLT
OPGD cascading board: 0/2/0

smart
192.168.50.1/24
Management VLAN
and IP address of
the ONU

smart
Here we take the scenario of "to

remotely log in to the ONU
from the OLT for configuration"
for example, so we need to
ensure that the management
VLAN of the OLT is the same as
that of the ONU and that the
management IP address of the
OLT is in the same network
segment as that of the ONU.
192.168.50.2/24
Issue 01 (2016-04-29)

891

Access Module
Procedure
l
Configure a management channel if the remote software commissioning using GE

upstream transmission is enabled and the cascading board is ETHB.
a.
Configure the inband management VLAN and IP address of the OLT.

The ID of the inband management VLAN is 8, the VLAN priority is 6, and the
management IP address is 192.168.50.1/24.
b.
Add the cascading port to the management VLAN.

c.
Enable NAC on the OLT.

huawei(config)#nac enable master 0/3 0
d.
(Optional) Create an SNMP management profile.

Perform this operation if the ONU is managed through the U2000. Plan an SNMP
management profile on the U2000 and ONU before creating the profile.
huawei(config)#snmp-profile add profile-id 64 profile-name snmpprofile_64 v2c public
private 192.168.50.55 30000 trapstatus
e.
Configure ONU management parameters on the OLT.

NOTE
ONU management parameters can be configured using NAC or RN commands. Do not configure
the parameters using both NAC and RN commands. Otherwise, the OLT will generate an error
message.
Configure and query ONU management parameters using NAC commands.

huawei(config)#nac config master 0/3/0 slave vlan 8 priority 3 ipaddress
192.168.50.2 mask 255.255.255.0 gateway 192.168.50.254 snmp-profile-id 64
Check whether the ONU management parameters have been configured on the
OLT.
huawei(config)#display nac configuration master
Configure and query ONU management parameters using RN commands.

huawei(config)#rn ipconfig 0/3/0 ip-address 192.168.50.2 mask
255.255.255.0 gateway 192.168.50.254 vlan 8 priority 3
huawei(config)#rn snmp-config all snmp-index 0 profile-id 64
OLT.
huawei(config)#display rn info 0/3/0
f.
Upon power-on, the ONU exchanges data with the OLT to obtain the management
parameters. Two minutes later, run the telnet command to remotely log in to the
ONU.
g.
Query the device connected to the OLT cascading port.

Query the device using NAC commands.
huawei(config)#display nac slave info detail
Query the device using RN commands.

Issue 01 (2016-04-29)

892

Access Module
h.
(Optional) Disable NAC on the OLT.

Perform this operation after the ONU obtains the management parameters. This
prevents the OLT from issuing the originally planned data to a substituted ONU.
huawei(config)#nac disable master 0/3 0

upstream transmission is enabled and the cascading board is OPGD.
a.

b.
Configure the inband management service flow.

The index of the service flow is 1. The ID of the management VLAN is 8. The
Ethernet cascading port is 0/2/0. The ID of the user-side VLAN is 8. The OLT does
not limit the rate of the inband management service flow. Therefore, use the default
traffic profile with ID 6, which does not limit the rate of a service flow.
huawei(config)#service-port 1 vlan 8 eth 0/2/0 multi-service user-vlan 8
rx-cttr 6 tx-cttr 6
c.
Enable NAC on the OLT.

d.

Perform this operation if the ONU is managed through the U2000. Plan an SNMP
management profile on the U2000 and ONU before creating the profile.
huawei(config)#snmp-profile add profile-id 64 profile-name snmpprofile_64 v2c public
e.
Configure ONU management parameters on the OLT.

NOTE
ONU management parameters can be configured using NAC or RN commands. Do not configure
the parameters using both NAC and RN commands. Otherwise, the OLT will generate an error
message.
Configure and query ONU management parameters using NAC commands.

huawei(config)#nac config master 0/2/0 slave vlan 8 priority 3 ipaddress
OLT.
Configure and query ONU management parameters using RN commands.

huawei(config)#rn ipconfig 0/2/0 ip-address 192.168.50.2 mask
255.255.255.0 gateway 192.168.50.254 vlan 8 priority 3
huawei(config)#rn snmp-config all snmp-index 0 profile-id 64
OLT.
Issue 01 (2016-04-29)

893

Access Module
f.
Upon power-on, the ONU exchanges data with the OLT to obtain the management
parameters. Two minutes later, run the telnet command to remotely log in to the
ONU.
g.
Query the device connected to the cascading port on the OLT.

Query the device using NAC commands.
huawei(config)#display nac slave info detail
Query the device using RN commands.

h.
(Optional) Disable NAC on the OLT.

Perform this operation after the ONU obtains the management parameters. This
prevents the OLT from issuing the originally planned data to a substituted ONU.
huawei(config)#nac disable master 0/2 0

upstream transmission is disabled and the cascading board is ETHB.
a.
Configure the inband management VLAN and IP address of the ONU.

Log in to the ONU through a local serial port and configure the ONU as follows:
The ID of the inband management VLAN is 8 and the management IP address is
192.168.50.2/24.
b.

c.
Add the cascading port to the management VLAN.

d.
Check whether the management channel between the OLT and the ONU is
available.
n
Run the ping 192.168.50.2 command on the OLT to check the connectivity
between the OLT and the ONU. If the OLT can receive Internet Control
Message Protocol (ICMP) ECHO-REPLY packets sent from the ONU, the
ONU is connected to the OLT.
If you can remotely log in to the ONU from the OLT for configuration, the

upstream transmission is disabled and the cascading board is OPGD.
a.

Log in to the ONU through a local serial port and configure the ONU as follows:
The ID of the inband management VLAN is 8 and the management IP address is
192.168.50.2/24.
Issue 01 (2016-04-29)

894

Access Module
b.

c.
Configure the inband management service flow.

The index of the service flow is 1. The ID of the management VLAN is 8. The
Ethernet cascading port is 0/2/0. The ID of the user-side VLAN is 8. The OLT does
not limit the rate of the inband management service flow. Therefore, use the default
traffic profile with ID 6, which does not limit the rate of a service flow.
rx-cttr 6 tx-cttr 6
d.
Check whether the management channel between the OLT and the ONU is
available.
n
Run the ping 192.168.50.2 command on the OLT to check the connectivity
between the OLT and the ONU. If the OLT can receive ICMP ECHO-REPLY
packets sent from the ONU, the ONU is connected to the OLT.
If you can remotely log in to the ONU from the OLT for configuration, the
----End
10.8.5 Configuring the Service Channel Between an OLT and an

ONU
This section describes how to configure a service channel between an optical line terminal
(OLT) and an optical network unit (ONU). After the configuration, the service channel
forwards service packets on the ONU at Layer 2 based on the planned VLAN and forwarding
policy.
Data Plan and Configuration Description

Planning the service channel between an OLT and an ONU is planning VLAN data. The
following table lists the data plan in various Ethernet cascading scenarios.
Issue 01 (2016-04-29)

895

Access Module
Networking Scenario
Data Plan and Configuration Procedure
HGW)
Internet access service channel (Create a common SVLAN on the OLT to transparently transmit the Internet
access service packets from a stacking VLAN on the
ONU. For details about VLAN planning principles, see
10.3.3 Principle of Internet Access Service Data Plan):
l S-VLAN: 1001
l C-VLAN (Internet access service S-VLAN on the
ONU): 1001
Voice service channel (The OLT transparently transmits
VLAN tags carried in voice service packets. For details
about VLAN planning principles, see 10.3.5 Principle of
VoIP Service Data Plan):
l S-VLAN: 200
l C-VLAN (Voice service S-VLAN on the ONU): 200
Issue 01 (2016-04-29)

896

Access Module
Networking Scenario
FTTB/FTTC+HGW
the VoIP Service)
Internet access channel (Create a common S-VLAN on the

OLT to transparently transmit the Internet access service
packets from a stacking VLAN on the ONU. For details
about VLAN planning principles, see 10.3.3 Principle of
Internet Access Service Data Plan):
l S-VLAN: 1001
l C-VLAN (Internet access service S-VLAN on the
ONU): 1001
Voice service channel (The OLT transparently transmits
VLAN tags carried in voice service packets from the
ONU. For details about VLAN planning principles, see
10.3.5 Principle of VoIP Service Data Plan):
l S-VLAN: 200
l C-VLAN (Voice service S-VLAN on the ONU): 200
VoD service channel (The OLT transparently transmits
VLAN tags carried in VoD service packets from the ONU.
For details about VLAN planning principles, see 10.3.6
Principle of IPTV Service Data Plan):
l S-VLAN: 300
l C-VLAN (VoD service S-VLAN on the ONU): 300
Multicast service channel (The OLT functions as an IGMP
proxy. For details about VLAN planning principles, see
10.3.6 Principle of IPTV Service Data Plan):
l Multicast VLAN: 1000
l Multicast cascading port: 0/3/0 (ETHB) or 0/2/0
(OPGD)
l IGMP version: IGMPv3
l IGMP mode: IGMP proxy
l Multicast program library: 224.1.1.10-224.1.1.100
l IP address of the multicast server: 10.10.10.10/24
FTTB/FTTC+HGW
the VoIP Service)
See the description for "FTTB/FTTC+HGW networking

(ONU providing the VoIP service)".
Based on the preceding data plan, the service channel configuration in "FTTB/FTTC+HGW
networking (ONU providing the VoIP service)" involves the other two sub-scenarios. The
following section uses this networking as an example to describe how to configure the
channels.
Procedure
l
Issue 01 (2016-04-29)
Configure a service channel if the Ethernet cascading board is ETHB.

897

Access Module
If the Ethernet cascading board is ETHB, no service flow needs to be configured on the
OLT. You only need to add the Ethernet cascading port (for example, 0/3/0) to each SVLAN.
a.

Create S-VLAN 1001 for the Internet access service and add uplink port 0/19/0 and
Ethernet cascading port to the VLAN.
b.
Configure a channel for the voice service.

Create S-VLAN 200 for the voice service and add uplink port 0/19/0 and Ethernet
cascading port to the VLAN.
c.

Create S-VLAN 300 for the VoD service and add uplink port 0/19/0 and Ethernet
cascading port to the VLAN.
d.

Create S-VLAN 1000 for the multicast service and add uplink port 0/19/0 and
Ethernet cascading port to the VLAN.

huawei(config)#btv

Configure the IGMP mode.

Configure a multicast uplink port.

Configure multicast programs.

224.1.1.100
Configure a service channel if the Ethernet cascading board is OPGD.

If the Ethernet cascading board is OPGD, service flows must be configured on the OLT.
The following configurations uses the Ethernet cascading port 0/2/0 on the OPGD board
as an example.
a.

Create VLAN 1001 for the Internet access service and add uplink port 0/19/0 to the
VLAN.
Issue 01 (2016-04-29)

898

Access Module

Configure a traffic profile for the service flow. (The 802.1p priority of the Internet
access service is 0 and the traffic profile does not limit rates. You can run the
display traffic table ip command to query the traffic profiles existing in the
system. Traffic profile 6 meets the requirements and you do not need to configure
it.)
Configure a service flow to receive and transparently transmit the Internet access
service packets from the ONU.
huawei(config)#service-port vlan 1001 eth 0/2/0 multi-service user-vlan
1001
tag-transform transparent rx-cttr 6 tx-cttr 6
b.
Configure a channel for the voice service.

Create VLAN 200 for the voice service and add uplink port 0/19/0 to the VLAN.
Configure a traffic profile for the service flow. (The 802.1p priority of the voice
service is 5 and the traffic profile does not limit rates. You can run the display
traffic table ip command to query the traffic profiles existing in the system. No
traffic profile meets the requirements and create traffic profile 9, where prioritypolicy is set to local-setting, indicating that queues are scheduled based on the
priority specified in the traffic profile.)
Configure a service flow to receive and transparently transmit the voice service
packets from the ONU.
200
c.

Create VLAN 300 for the VoD service and add uplink port 0/19/0 to the VLAN.
Configure a traffic profile for the service flow. (The 802.1p priority of the VoD
service is 4 and the traffic profile does not limit rates. You can run the display
traffic table ip command to query the traffic profiles existing in the system. No
traffic profile meets the requirements and create traffic profile 10, where prioritypolicy is set to local-setting, indicating that queues are scheduled based on the
priority specified in the traffic profile.)
Configure a service flow.

300
d.

Create VLAN 1000 for the multicast service and add uplink port 0/19/0 to the
VLAN.
Create a multicast service flow.

Issue 01 (2016-04-29)

899

Access Module

1000

huawei(config)#btv

Configure the IGMP mode.

Configure a multicast uplink port.


224.1.1.100
----End
10.8.6 Configuring the Service Flow on an ONU or HGW

This section describes how to configure the service flow on an optical network unit (ONU) or
a home gateway (HGW) to provide a user service.
Data Plan and Configuration Description

The data plan and configuration method for the Internet access service on an ONU or HGW in
Ethernet cascading scenarios are different from those in PON scenarios. The reason is as
follows: In Ethernet cascading scenarios, data is encapsulated in S-VLAN+C-VLAN mode on
the ONU and the OLT transparently transmits the S-VLAN tag (C-VLAN tag for the OLT)
carried in ONU packets. Each ONU uses an S-VLAN and it differentiates users by C-VLAN.
In addition, the user access modes are different. Specifically, in Ethernet cascading scenarios,
users are connected to the ONU through xDSL lines; in PON scenarios, users are connected to
the ONU through optical lines.
Issue 01 (2016-04-29)

900

Access Module
Networking Scenario
FTTB/FTTC networking
(xDSL access without an
HGW)
For details, see:

l 10.5.7 Configuring the Internet Access Service
(VDSL2 Access, on the ONU)
The configurations in steps 3 and 4 are modified as
follows (the configurations in other steps remain
unchanged):
3. Create an S-VLAN.
Configure stacking S-VLAN 1001 for the ONU and
add uplink port 0/0/1 to the VLAN.
4. Add service ports.

VDSL2 mode PTM and untagged user packets are
used as an example. Add a service port for the users
connected to ports 0/1/0 and 0/1/1, respectively.
vdsl mode ptm 0/1/0 multi-service user-vlan
untagged
tag-transform add-double inner-vlan 2 rxcttr 8 tx-cttr 8
//Users are
differentiated by C-VLAN (inner-vlan).
Therefore, the C-VLAN (inner-vlan) of each
user must be unique.
untagged
l 10.7.10 (Optional) Configuring Vectoring

l 10.5.10 Configuring H.248 Voice Service (on the
ONU)
l 10.5.11 Configuring SIP Voice Service (on the ONU)
Issue 01 (2016-04-29)

901

Access Module
Networking Scenario
FTTB/FTTC+HGW
networking (ONU providing
the VoIP service)
For details, see:

unchanged):

untagged
//Users are
differentiated by C-VLAN (inner-vlan).
untagged

l 10.4.7 Configuring H.248 Voice Service (on the
ONU)
l 10.4.8 Configuring SIP Voice Service (on the ONU)
l 10.7.12 Configuring the IPTV Service (on the ONU)
l 10.7.14 Configuring the Internet Access Service (on
the HGW)
l 10.7.15 Configuring the IPTV Service (on the
HGW)
Issue 01 (2016-04-29)

902

Access Module
Networking Scenario
FTTB/FTTC+HGW
networking (HGW providing
the VoIP service)
For details, see:

unchanged):

vdsl mode ptm 0/1/0 multi-service user
-vlan untagged tag-transform add-double
inner-vlan 2 rx-cttr 8 tx-cttr 8
//Users
are differentiated by C-VLAN (inner-vlan).
vdsl mode ptm 0/1/1 multi-service user
-vlan untagged tag-transform add-double
inner-vlan 3 rx-cttr 8 tx-cttr 8

l 10.7.11 Configuring the Voice Service Channel (on
the ONU)
l 10.6.12 Configuring the IPTV Service (on the ONU)
l 10.6.14 Configuring the Internet Access Service (on
the HGW)
l 10.6.15 Configuring the IPTV Service (on the
HGW)
l 10.7.16 Configuring the VoIP Service (on the HGW)

Security Policy
service security.
Context
Issue 01 (2016-04-29)

903

Access Module
NOTE
Data Plan.
Procedure
l

aggregation:
mode.

i.
ii.




i.

ii.

1)
Issue 01 (2016-04-29)


904

Access Module
2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


i.

ii.


l
service.
i.

Issue 01 (2016-04-29)
level.

905

Access Module
ii.
The VLAN level:

1)

2)

3)

effect.
4)
5)

level.

i.

default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End
Issue 01 (2016-04-29)

906

Access Module

In fiber to the building (FTTB) or fiber to the curb (FTTC) scenarios, optical network units
(ONUs) are deployed far from the central office (CO). To facilitate service verification, ONUs
support remote service verification methods, such as PPPoE dialup, call, and multicast service
emulation tests. This allows commissioning and configuration engineers to remotely verify
services.
Verification Methods
The method of verifying a service on an Ethernet cascading network is the same as that of
verifying a service on a PON network.
Networking Scenario
HGW)
For details, see 10.5.13 Verifying Services.
FTTB/FTTC+HGW
the VoIP Service)
FTTB/FTTC+HGW
the VoIP Service)
10.9 FTTB and FTTC Ethernet Cascade Networking (ONU

works as a GE remote extended subrack)
Working with high bandwidth technologies, such as VDSL2 and Vectoring, GE remote
extended subracks provide high bandwidth access for users over existing copper line
networks. GE remote extended subracks can be connected to traditional VDSL2 modems to
provide Internet access and voice services for users; or be connected to home gateways
(HGWs) to provide Internet, voice, and IPTV services for home users.
10.9.1 Service Requirements and Application Scenarios for GE

Remote Extended Subrack
Centric management for GE remote extended subracks is used on networks that require high
bandwidth access without adding more standalone NEs.
l
If only high speed Internet (HSI) and voice services are required, use traditional VDSL2
modems for user access.
If HSI, voice, and IPTV services are required, use HGWs for user access.
Issue 01 (2016-04-29)

907

Access Module
As shown in Figure 10-12, a GE remote extended subrack is deployed in a corridor or
roadside fiber distribution terminal, like a remotely deployed service board of a master
subrack and is directly managed by the master subrack. In the upstream direction, it is
connected to the master subrack through GE fibers; in the downstream direction, it is
connected to user terminals through twisted pairs.
l
When using traditional VDSL2 modems for user access:
For HSI service, users are provided with the HSI service through modems at their
home. Dialup authentication is required because modems are Layer 2 devices. Each
user has an independent account and is authenticated and managed on the BRAS.
For voice service, users are provided with the traditional telephone service by
connecting telephones to the VDSL2 splitter.
When using HGWs for user access:
The HGW is connected to the upstream extended subrack through VDSL2 ports,
and provides the Internet access service through FE or Wi-Fi ports and the IPTV
service through FE ports in the downstream direction.
The HGW has Layer 3 functions (such as PPPoE dialup and NAT), which enables
multiple PCs of a family to access the Internet at the same time.
The STB connected to the HGW provides IPTV program preview and access
functions.
The IAD embedded in the HGW provides one or several POTS ports, which
provides access for multiple phones of a family at the same time.
Applicable master subrack: MA5600T, MA5603T (uses the SCUN board as the control board,
and is cascaded to the GE remote extended subrack through the ETHB board.)
Applicable GE remote extended subrack: MA5623AR
Figure 10-12 Service networking diagram for GE remote extended subracks
Centralized management for GE remote
extended subracks
Laptop
HGW
PC
VDSL2
STB
GE remote
extended
subrack
TV
PE-AGG
UPE
GE
Phone
Metro Network
GE
FE/GE
PC
Issue 01 (2016-04-29)
Modem
Master
subrack
VDSL2
NGN/IMS
Internet
UPE
PE-AGG
GE remote
extended
subrack

908

Access Module
10.9.2 Principle of Data Planning for GE Remote Extended

Subrack
Data planning for GE remote extended subracks covers security data, QoS data, and data
about the cascading between the master subrack and the extended subrack (including the
reliability of uplink links on the extended subrack).
Data Plan for Cascading Between the Master Subrack and the GE Remote
Extended Subrack (Including the Reliability of Uplink Links on the Extended
Subrack)
Item
Solution
Extending port of
the master subrack
Adding a GE remote extended subrack to a master subrack is like

adding a service board to the master subrack. You can add a GE
remote extended subrack in offline pre-deployment or automatic
discovery mode. In offline pre-deployment mode, an extending port
on the master subrack needs to be planned for adding the extended
subrack. In automatic discovery mode, an extending port does not
need to be planned, and the port where the extended subrack is
automatically discovered is used as the extending port.
Extended subrack ID
The master subrack ID is always 0. After the GE remote extended

subrack is introduced, the extended subrack ID starts from 1.
Currently, a maximum of 32 extended subracks are supported.
Therefore, the extended ID ranges from 1 to 32.
In offline pre-deployment mode, an available subrack ID needs to
be specified for the extended subrack to be added. In automatic
discovery mode, the master subrack automatically allocates an
available subrack ID to the extended subrack that is confirmed.
Reliability of uplink
links on the
extended subrack
The reliability of uplink links on the extended subrack can be

enhanced using only Ethernet link aggregation, which is similar to
Ethernet link aggregation of the master subrack in upstream
transmission. When a GE remote extended subrack is used, pay
attention to the following points:
l Link aggregation can be performed only on an ETHB extending
board, instead of between boards and only manually, instead of
using LACP.
l If aggregation is performed for uplink links on the extended
subrack, the ETHB extending port in the aggregation group of
the master subrack must be set as the master port in the
aggregation group. The ETHB extending port refers to the
extending port specified during the offline configuration of the
extended subrack or the extended subrack port that is discovered
automatically. The master port in the aggregation group of the
extended subrack can be configured as required.
Plan security and QoS data based on the following items:

Issue 01 (2016-04-29)

909

Access Module
QoS data planning
Internet service data planning
(Optional) Vectoring data planning
Voice service data planning (VoIP services are provided by home gateways and
therefore, only planning voice VLANs for home gateways is required for voice services.
PSTN voice services are transmitted to PSTN networks through the splitter and
therefore, FTTx network data planning is not required for PSTN voice services.)
IPTV service data planning
Security data planning
10.9.3 Configuration Procedure for GE Remote Extended Subrack

Compared with a traditional network using VDSL2 modems to connect to users, the network
using a GE remote extended subrack requires the addition of a GE remote extended
subrack. The other service configuration process and methods are the same for the two
networks and therefore are not described in this section. For details, see the MA5600T
Configuration Guide or the MA5603T Configuration Guide. This section describes the service
configuration process for the FTTB/FTTC+HGW networking (FTTB is the abbreviation for
fiber to the building, FTTC for fiber to the curb, and HGW for home gateway).
Figure 10-13 shows the configuration roadmap for the FTTB/FTTC+HGW networking.
Issue 01 (2016-04-29)

910

Access Module
Figure 10-13 Configuration roadmap for the FTTB/FTTC+HGW networking (voice service
provided through the HGW)

Configur
ation
Object
Step
Description
DSLAM
(master
subrack)
Add a GE remote
extended subrack.
The operation of adding a GE remote extended

subrack to the master subrack is the same as that of
adding a service board to the master subrack. The GE
remote extended subrack can be automatically
discovered or deployed in offline mode.
After the extended subrack is added, the master
subrack manages it as a service board.
GE
remote
extended
subrack
(configure
Issue 01 (2016-04-29)
Configure a
VDSL2 port.
Configure a VDSL2+ profile and bind it to the VDSL2

port. Then, activate the VDSL2 port for service
transmission.

911

Access Module
Configur
ation
Object
Step
Description
d through
the master
subrack)
Configure a
VDSL2 service
flow.
In HGW networking, a VDSL2 service flow is of the

multi-service over multi-PVC type, which facilitates
the management and maintenance of various services.
(Optional)
Configure
vectoring.
The vectoring function enabled on a VDSL2 line can

greatly cancel the far-end crosstalk (FEXT) on the line
and increase the VDSL2 line rate.
Configure link
aggregation,
congestion control,
and security
policies.
The global configuration of link aggregation and

upstream queue scheduling based on priorities ensures
service reliability. The global configuration of security
Configure the
Internet access
service.
Refer to service configurations on the HGW on the

network where services are transmitted upstream
through DSL lines.
HGW
Configure the
IPTV service.
Configure the voice
service.
GE
remote
extended
subrack
(configure
d through
the master
subrack)
Verify the
configured services.
PPPoE dialup, call, and multicast service emulation

tests can be performed on the master subrack for the
services on the GE remote extended subrack. This
allows commissioning and configuration engineers to
remotely verify services.
VoD and HGW voice service do not support remote
verification.
HGW
10.9.4 Adding GE Remote Extended Subracks

This topic describes how to add a GE remote extended subrack to the master subrack so that
the master subrack can manage the extended subrack.
Data Plan
The following table lists the data plan for interconnection between the master subrack and
extended subrack.
Issue 01 (2016-04-29)

912

Access Module
Item
Data
Remarks
Extending port
of the master
subrack
ETHB extending port:

0/3/0
Adding a GE remote extended subrack to a

master subrack is like adding a service board
to the master subrack. You can add a GE
remote extended subrack in offline predeployment or automatic discovery mode. In
offline pre-deployment mode (as in this
example), an extending port on the master
subrack needs to be planned for adding the
extended subrack. In automatic discovery
mode, an extending port does not need to be
planned, and the port where the extended
subrack is automatically discovered is used
as the extending port.
Extended
subrack ID
In offline predeployment mode, the

extended subrack ID is
1.
The master subrack ID is always 0. After the

GE remote extended subrack is introduced,
the extended subrack ID starts from 1.
Currently, a maximum of 32 extended
subracks are supported. Therefore, the
extended ID ranges from 1 to 32.
In offline pre-deployment mode (as in this
example), an available subrack ID needs to
be specified for the extended subrack to be
added. In automatic discovery mode, the
master subrack automatically allocates an
available subrack ID to the extended subrack
that is confirmed.
Procedure
Step 1 Set the auto-negotiation function of the extending port to enable.
huawei(config-if-eth-0/3)#auto-neg all enable
Step 2 Set the working mode of the ETHB extending board to extend.
huawei(config-if-eth-0/3)#network-role extend
NOTICE
An ETHB board resets if its working mode switches from extend to other modes or from
other modes to extend.
Step 3 Add a remote extended subrack in offline mode.
huawei(config)#frame add 1 MA5623AR extend-port 0/3/0
----End
Issue 01 (2016-04-29)

913

Access Module
Follow-up Procedure
After being powered on, the extended subrack automatically communicates with the master
subrack to complete registration, and enters the normal state. Then, the master subrack can
manage the extended subrack.
NOTE
In automatic discovery mode, perform the following operations to add a remote extended subrack:
l
Run the display network-role command to check whether the working mode of the ETHB board is
extend
If the working mode is not extend, run the network-role command to set the working mode to extend.
Note that mode switching will reset the ETHB board.
Run the frame confirm command to confirm the extended subrack. Then, the extended subrack enters
the normal state.
10.9.5 Configuring VDSL2 User Ports

This topic describes how to activate VDSL2 ports and bind a VDSL2 profile to the ports for
service transmission.
Data Plan
Data plan for VDSL2 user ports focuses on line parameters, such as spectrum profile, OSNR
tolerance, and maximum interleave delay. The parameter plan for VDSL2 ports on a GE
remote extended subrack is the same as that for VDSL2 ports on the master subrack. For
details, see "Configuring VDSL2 Profiles" in MA5600T/MA5603T Configuration Guide.
Procedure
Step 1 Select a default VDSL2 profile ID, or configure a VDSL2 profile according to service
requirements.
Step 2 Activate the VDSL2 user ports.
1.
Run the activate command to activate the VDSL2 ports, and then bind a line profile
(non-line-alarm profile) to the VDSL2 ports. Note that the format of the activate
command varies with the VDSL2 modes (TR129, TI, or TR165).
2.
Run the alarm-config command to bind a line alarm profile to the VDSL2 ports.
----End
10.9.6 Configuring VDSL2 Service Flows

This topic describes how to configure different service flows on GE remote extended subracks
for different services so that service packets on HGWs can be forwarded at Layer 2 according
to the planned VLAN and forwarding policies.
Data Plan
The following table lists the data plan for configuring service flows.
Issue 01 (2016-04-29)

914

Access Module
Service
Type
VLAN Plan
Remarks
Internet
access
service
S-VLAN: 100; VLAN

attribute: stacking
The Internet access service use dual VLAN tags

(S-VLAN+C-VLAN) to differentiate users.
C-VLAN: 10011002
For details, refer to 10.3.3 Principle of Internet

Voice
service
S-VLAN: 200
The voice over IP (VoIP) service is a carrieroperating closed service. It primarily uses only SVLAN tags which are transparently transmitted
from a GE remote extended subrack to an HGW.
C-VLAN: 200
For details, refer to 10.3.5 Principle of VoIP

Service Data Plan.
NOTE
VLAN planning is required only when HGWs provide
all VoIP services. Service boards in the extended
subrack do not process traditional public switched
telephone network (PSTN) voice services that are
transmitted through splitters. PSTN voice signals are
transparently transmitted through the splitter upstream
to PSTN networks.
VoD
service
S-VLAN: 300
C-VLAN: 300
The PSPV mode is recommended for the video

on demand (VoD) service because the service
requires fewer VLANs.
The voice over IP (VoIP) service is a carrieroperating closed service. It primarily uses only SVLAN tags which are transparently transmitted
from a GE remote extended subrack to an HGW.
For details, refer to 10.3.6 Principle of IPTV
Service Data Plan.
Multicast
service
MVLAN: 1000
The multicast service is a carrier-operating closed

service and primarily uses only S-VLAN tags.
IGMP mode: IGMP

proxy
For details, refer to 10.3.6 Principle of IPTV

Service Data Plan.
Multicast program
library: 224.1.1.10
224.1.1.100
IP address of the
multicast server:
10.10.10.10/24
NOTE
C-VLANs in the preceding table are defined for remote extended subracks. That is, they are upstream
VLANs or S-VLANs of HGWs.
Issue 01 (2016-04-29)

915

Access Module
Procedure
l
Configure an Internet access service flow.

a.

S-VLAN.
b.

required. To query existing traffic profiles, run the display traffic table ip
command. In this example, the query result shows that traffic profile 6 meets the
requirements, so no traffic profile needs to be configured.
c.
Configure a service port to receive and transparently transmit the Internet access
service from the HGW.
Configure an Internet access service port with the user VLAN being 1001 or 1002.
The HGW is connected to port 1/1/0 of the GE remote extended subrack. Upstream
and downstream traffic is rate-limited using a line profile. A traffic profile (traffic
profile 6 in this example) that does not limit rates is referenced.
huawei(config)#service-port vlan
user-vlan 1001 rx-cttr 6 tx-cttr
huawei(config)#service-port vlan
user-vlan 1002 rx-cttr 6 tx-cttr
100 vdsl mode ptm 1/1/0 multi-service

6
100 vdsl mode ptm 1/1/0 multi-service
6
Configure a voice service flow.

a.

S-VLAN.
b.

The 802.1p priority of the voice service is 5, and rate limitation is not required. To
query existing traffic profiles, run the display traffic table ip command. In this
example, the query result shows that no existing traffic profile meets the
requirements, so a new traffic profile needs to be configured.
c.
Configure a service port to receive and transparently transmit the voice service from
the HGW.
Configure a service port with the user VLAN being 200. The HGW is connected to
port 1/1/0 of the GE remote extended subrack. Upstream and downstream traffic is
rate-limited using a line profile. A traffic profile (traffic profile 9 in this example)
that does not limit rates is referenced.
Issue 01 (2016-04-29)

916

Access Module
huawei(config)#service-port vlan 200 vdsl mode ptm 1/1/0 multi-service

Configure a VoD service port.

a.

S-VLAN.
b.
Configure a VoD traffic profile.

query existing traffic profiles, run the display traffic table ip command. In this
example, the query result shows that no existing traffic profile meets the
requirements, so a new traffic profile needs to be configured.
c.
Configure a VoD service port.

Configure a service port with the user VLAN being 300. The HGW is connected to
port 1/1/0 of the GE remote extended subrack. Upstream and downstream traffic is
rate-limited using a line profile. A traffic profile (traffic profile 10 in this example)
that does not limit rates is referenced.
Configure a multicast service flow.

a.

the S-VLAN.
b.
Create a multicast service port.

Configure a service port with the user VLAN being 1000. The HGW is connected
to port 1/1/0 of the GE remote extended subrack. Upstream and downstream traffic
is rate-limited using a line profile. A traffic profile (traffic profile 10 in this
example) that does not limit rates is referenced.
c.

d.
Set the IGMP mode.

Issue 01 (2016-04-29)

917

Access Module
e.
Configure the multicast upstream port.

Configure the IGMP upstream port as 0/19/0.
f.

Set the IP address of multicast programs to 224.1.1.10224.1.1.100, and IP
address of the multicast server to 10.10.10.10.
224.1.1.100
----End

Context
For MA5623AR, when configuring vectoring, learn configuration item functions and
Issue 01 (2016-04-29)
Item
Function
Description
Commands
Global band plan
In the vectoring
algorithm, the
system requires
that the upstream
band and
downstream band
are separate from
each other.
Therefore, the
band plan must
be globally
configured.
l The band plan can

be globally
configured only
when vectoring is
globally enabled.
xdsl vectoring
bandplan-type
globally enabled,
if the band plan
configured for the
line profile is
incompatible with
the band plan
globally
configured for
vectoring and the
upstream band
plan and
downstream band
plan are not
separate from
each other, the
port cannot be
activated.

918

Access Module
Item
Function
Description
Commands
Global vectoring
configurations
Vectoring
configurations
take effect only
when vectoring is
globally enabled.
l Before enabling
vectoring,
globally configure
the band plan.
xdsl vectoring
Configure the
function of
canceling the
upstream and
downstream
crosstalk in the
vectoring profile.
After binding the
configured
vectoring profile
to the ports, the
system
implements the
vectoring
algorithm on the
ports in the
vectoring group
based on profile
configurations.

are bound to
Vectoring profile
Issue 01 (2016-04-29)
NOTE
Services in a
vectoring group
when the vectoring
function is enabled
or disabled.
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable

Commands:
l Add a vectoring
profile: xdsl
vectoring-profile
add
l Modify a
vectoring profile:
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
l Bind a vectoring
vectoring-config
(VDSL mode)
919

Access Module
Issue 01 (2016-04-29)
Item
Function
Description
Commands

frequent online and
offline on ports
The Vectoring
algorithm is
executed every
time a port in a
Vectoring group
goes online or
offline. To
prevent adverse
impact on system
functions due to
long-term
running Vectoring
tasks caused by
frequent online
and offline on a
port, set the
policy for
controlling
frequent online
and offline on
ports based on
site requirements.

for controlling
frequent online and
Vectoring crosstalk
matrix
The vectoring
crosstalk matrix
refers to crosstalk
on a port in a
vectoring group
from other ports
in the same
vectoring group.
Before querying
vectoring crosstalk
matrix, ensure that
function is enabled
is in a vectoring


920

Access Module
Item
Function
Description
Commands

a legacy customer
premises equipment
(CPE)
A legacy CPE is
a VDSL2 CPE
(supporting G.
993.2, not G.
993.5) that does
not support
Vectoring. If such
a CPE is
activated in G.
993.2 mode in the
Vectoring system,
the crosstalk
impact on other
lines cannot be
canceled, causing
the Vectoring
system
performance to
deteriorate. To
minimize the
impact, set the
activation policy
of a legacy CPE
based on site
requirements.

for activating a
limit.
l no-limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode (G.
993.2 mode), or
non-Vectoring
mode, in which
the Vectoring
system
performance is
affected. This
mode is used in
the Vectoring
initial phase when
a large number of
CPEs need to be
upgraded or
replaced and the
Vectoring
performance are
not concerned.
l limit: The
Vectoring legacy
CPE is activated
in common
VDSL2 mode but
the line PSD is
automatically
shaped so that the
CPE can be
activated at a low
VDSL2 rate,
preventing
crosstalk on other
lines. This mode
is used in
Vectoring medium
phase when some
CPEs have not
been upgrade or
replaced.
friendly is used in
Issue 01 (2016-04-29)

921

Access Module
Item
Function
Description
Commands
the downstream
direction and PSD
automatic shaping
is used in the
upstream
direction.
friendly is used in
the downstream
direction and no
restriction is used
in the upstream
direction.
l block: The
Vectoring legacy
CPE cannot be
activated in
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
Data Plan
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l US0 type: type-a

legacy customer
premises equipment
(CPE)
Issue 01 (2016-04-29)
no-limit


application.
922

Access Module
Item
Data
Description

frequent online and
offline on ports
no-limit
Vectoring group
Group ID: 1

Vectoring profile

cancelation: enable
cancelation: enable
Procedure
Step 1 Globally configure the band plan type.
Step 2 Configure the vectoring profile as huawei and bind it to the VDSL2 port in the vectoring
group.
huawei(config)#xdsl vectoring-profile add control enable enable name huawei
Step 3 Configure the policy for activating a vectoring legacy CPE.

Step 4 Configure the policy for controlling frequent online and offline on ports.
huawei(config)#xdsl frequent-retrain-control 1/1/0 control-policy no-limit
Step 5 Enable the global vectoring.


huawei(config)#save
----End

Security Policies
This topic describes how to configure uplink aggregation and priority scheduling policies for
upstream queues in global config mode to enhance service reliability, and configure security
policies in global config mode to secure services.
Issue 01 (2016-04-29)

923

Access Module
Context
Link aggregation aggregates multiple upstream Ethernet ports into a group to increase the
uplink bandwidth and improve service reliability. It is advisable to configure congestion
control.
Congestion control queues packets from one port into multiple queues and schedules the
packets based on queue priorities. It is advisable to configure congestion control.
Security policies involve system security, user security, and service security, securing services
from different aspects.
NOTE
It is advisable to enable a required service security feature according to the service type. For details, see
10.3.7 Principle of Security Data Plan.
Procedure
l

Configure upstream ports 0/19/0 and 0/19/1 of the master subrack as a link aggregation
group (LAG). Each member port in the LAG is allocated packets based on the source
MAC address, and works in LACP static aggregation mode.
Configure upstream ports 1/0/0 and 1/0/1 of the GE remote extended subrack as an LAG.
Each member port in the LAG is allocated packets based on the source MAC address,
and works in manual aggregation mode. Ports 1/0/0 and 1/0/1 are connected to ports
0/3/0 (extending port) and 0/3/1 respectively on the ETHB extending board of the master
subrack.
NOTICE
Pay attention to the following when configuring link aggregation for GE remote
extended subracks:
l Only intra-ETHB extending board aggregation in manual aggregation mode is
supported.
l For the uplink aggregation configuration on the master subrack, the ETHB extending
port (which is specified during the offline pre-deployment of an extended subrack or
where an extended subrack is automatically discovered) must be configured as the
master port of an LAG. However, the extended subrack has no requirements on the
master port of an LAG.
l Before adding/deleting a port to/from an LAG, if the port is connected to a peer
device, run the shutdown command to deactivate the slave port of the LAG or
remove the fiber from the slave port to prevent a loopback. (Note that ports on the
ETHB board support the shutdown command, but upstream ports of the extended
subrack do not.) After the LAG is configured, re-activate the port or reconnect the
fiber to the slave port.
huawei(config)#link-aggregation 1/0 0-1 egress-ingress
huawei(config)#link-aggregation 0/3 0 0/3 1 egress-ingress
Issue 01 (2016-04-29)

According to "10.3.2 QoS Planning Principles", all packets are scheduled in strict
priority queue mode and mapped into different queues based on priorities.
924

Access Module
Enable deny of service (DoS) anti-attack on the master subrack.

i.
ii.

Enable IP address anti-attack on the master subrack.

Enable MAC address anti-flapping on the master subrack.

Enable MAC address anti-spoofing on the master subrack.

i.

ii.

1)

2)

1)
Run the vlan service-profile command to create a VLAN service

profile.
2)

3)

effect.
4)
5)


flow.
iv.

Enable IP address anti-spoofing on the master subrack.

Issue 01 (2016-04-29)

925

Access Module
i.

ii.


l
Enable Dynamic Host Configuration Protocol (DHCP) Option 82 on the master

subrack. This configuration is recommended for the DHCP-based Internet access
service.
DHCP Option 82 can be enabled or disabled at four levels: global, port, VLAN, and
levels. Among the four levels, DHCP Option 82 is disabled only at the global level
by default.
n
The global level: In global config mode, run the dhcp option82 command to
enable DHCP Option 82 at the global level.
DHCP Option 82 but provide different packet processing policies on the OLT.
For details, see the dhcp option82 command.
The port level: In global config mode, run the dhcp option82 port or dhcp
option82 board command to enable DHCP Option 82 at the port level.
The VLAN level:
1)

2)
Run the dhcp option82 enable command to enable DHCP Option 82 at

the VLAN level.
3)
Run the commit command to make the profile configuration take effect.
4)
5)
Run the vlan bind service-profile command to bind the created VLAN
service profile to a VLAN.
The service port level: In global config mode, run the dhcp option82 serviceport command to enable DHCP Option 82 at the service port level.
Enable Policy Information Transfer Protocol (PITP) on the master subrack. This
configuration is recommended for the PPPoE-based Internet access service.
PITP can be enabled or disabled at four levels: global, port, VLAN, and service port
levels. This function takes effect only after it is enabled at the four levels. Among
the four levels, PITP is disabled only at the global level by default.
n
global level.
In the preceding commands, the enable, forward, and rebuild parameters can
all enable PITP but provide different packet processing policies on the OLT.
Select one of them based on site requirements. For details, see the pitp
command.
Issue 01 (2016-04-29)
926

Access Module
n
The VLAN level:

1)

2)
3)
4)
5)
----End

Context
Procedure
1.
2.

1.
2.
Issue 01 (2016-04-29)
Parameter
Value
Bearing service
Internet
VLAN enabling
(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)

NOTE
Enabled.

927

Access Module
Parameter
Value
VLANID[1-409
4]

(Set this
parameter when
the HGW uses
the LAN or
VDSL2 for
upstream
transmission)
VPI/VCI
(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
Mode
3.

PPPoE
----End

Context
Procedure
1.
2.

1.
2.
Issue 01 (2016-04-29)

928

Access Module
Parameter
Value
Bearing service
VLAN enabling

NOTE
Enabled.
VLANID[1-409
4]

VPI/VCI

(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
3.
Binding item
Mode
Bridge
DHCP
transparent
transmission
Enabled
----End
10.9.11 Configuring the VoIP Service (on the HGW)

This topic describes how to configure the voice service on home gateways (HGWs) that use
the LAN or xDSL for upstream transmission. This configuration enables home users to enjoy
the POTS service by using an analog telephone.
Context
not the same. This topic describes how to configure the voice service on an HGW. The actual
configuration varies depending on different HGWs.
Procedure
1.
2.
Issue 01 (2016-04-29)

929

Access Module
Step 2 Set parameters of the voice service.

1.
2.

Parameter
Value
Bearing service
VoIP
Enabling status
Enabled
VPI/VCI

(Set this
parameter when
the HGW uses
ADSL2+ for
upstream
transmission)
3.
4.
Vlan ID
The voice VLAN IDs on the HGW map the values of uservlan
when voice service flows are created on the ONU.
802.1p
Enabled
Mode
Route: Route mode
DHCP
Enabled
NAT
Enabled
Choose the voice telephone number configuration from the navigation tree. Set the
parameters as follows:
Parameter
Value
Address
Port ID
Enabled
Enabled
User number
To use the VoIP account, you can set the account to the user
telephone number. In this example, set the user telephone number
to 83110001.
User password
----End

This topic describes how to verify services such as Internet access and IPTV services.
Issue 01 (2016-04-29)

930

Access Module
Prerequisites
The master subrack and upper-layer devices have been connected correctly, and the BRAS has
been configured.
Context
The following table lists the remote verification methods for different services.
NOTE
The VoD service and voice service on HGWs do no support remote service verification.
Remote
Verificati
on
Method
Function
Remarks
PPPoE
dialup
emulation
Emulates PPPoE user terminal to

perform dialup and interact with the
between the access device and
BRAS.
l PPPoE dialup emulation requires

a service flow which does not
belong to a QinQ VLAN.
l A GE remote extended subrack
supports a maximum of one
PPPoE dialup emulation at the
same time.
Multicast
emulation
Emulates a multicast user going

online and leads the program stream
to an access device. You can check
whether the multicast service is
normal by checking the real-time
traffic of the multicast program.

dynamic controllable multicast mode
do not support this function.
Item
Data
Remarks
PPPoE
dialup
emulation
parameters
Referenced service flow ID: 101

authentication mode for the
emulation test must be configured on
the BRAS and must be the same as
those planned for the BRAS.
Multicast
emulation
parameters
Data Plan
Issue 01 (2016-04-29)
Emulation timeout time: 10s
MVLAN: 1000
IP address of the multicast program:
224.1.1.10

931

Access Module
Procedure
l

a.
command.
b.
command.
c.

Assume that:
a.

huawei(config)#btv
1000
b.

c.

1000

a.
Run the display mac-address service-port command to check whether the MAC
addresses of VoD subscribers are learned. If yes, the VoD service is reachable.
Verify the voice service.

a.
Log in to the HGW management web page.
b.
Choose Status > Broadband VoIP Information to query the service registration
status and phone number.
Expected service registration status: Register successfully.
----End
Issue 01 (2016-04-29)

932

Access Module
11
11 FTTO Configuration (SOHO and SME)
FTTO Configuration (SOHO and SME)
About This Chapter

This chapter describes the configurations of the following services for small office and home
office (SOHO) users and small- and medium-sized enterprises (SMEs) in fiber to the office
(FTTO) scenarios: services of Internet access through cables, services of Internet access
through wireless fidelity (Wi-Fi), VoIP services, fax services, point of sale (POS) sdadianhua
ervices, multicast services, and private line services.
Context
FTTO is positioned for SOHO users, SMEs, and enterprises. This chapter provides service
configurations only for SOHO users and SMEs. For details about service configurations for
enterprises, see 12 FTTO Configuration (Large-sized Enterprise Access).
11.1 Basic Concept
FTTO SOHO and SME solutions involve many concepts. This topic describes concepts
involved in FTTO SOHO and SME solutions from user side to network side based on the
following FTTO SOHO and SME network diagram.
11.2 Principles of Planning Data for FTTO Services (SOHO and SME)
This section describes the principles of planning data for small office and home office
(SOHO) users and small- and medium-sized enterprises (SMEs) in fiber to the office (FTTO)
scenarios, from the aspect of security, device management, quality of service (QoS), and
services. The data of all the examples involved in this section is planned following the
principles.
11.3 Bridging Networking(GPON)
This section describes the configurations for the Internet access, voice, and video services on
optical network units (ONUs) in bridging networking.
11.4 Gateway Networking(GPON)
optical network units (ONUs) in gateway networking.
11.5 Layer 2 Interoperation Service Between Enterprise Branches
Different branches of an enterprise can achieve Layer 2 interoperation through ONUs. Then,
different branches can transmit service traffic to each other just like in the same LAN, which
can improve coordination work efficiency.
Issue 01 (2016-04-29)

933

Access Module
11.6 Configuring FTTO SOHO and SME Services (GE Optical Port)
FTTO ONU users connect to the P2P board of the OLT or to the switch using a GE optical
uplink port to use the Internet access, Wi-Fi, voice, and video services.
11.7 Configuring FTTO SOHO and SME Services (GE Electrical Port)
An FTTO ONU functions as a routing gateway. Its users use a GE electrical uplink port to
connect to the LAN port of an ONU on an FTTB or FTTC network to use the Internet access,
Wi-Fi, voice, and video services.
Issue 01 (2016-04-29)

934

Access Module
11.1 Basic Concept

FTTO SOHO and SME solutions involve many concepts. This topic describes concepts
involved in FTTO SOHO and SME solutions from user side to network side based on the
following FTTO SOHO and SME network diagram.
FTTO SOHO and SME Network Diagram
Scenario
Concept
Description
Small office home

office (SOHO)
SOHO is positioned for miniature enterprises, such as home offices,

shops, and markets.
Small- and
medium-sized
enterprise (SME)
An SME contains 10-300 personnel. SME is positioned for small- and

medium-sized enterprises, campuses, and net bars.
Concept
Introduction
VoD
VoD is known as interactive video on demand. Users can choose their

desired programs from the VoD program database. When watching
programs, users can perform operations such as pause, fast forward,
fast rewind, and locate.
User Side
Issue 01 (2016-04-29)

935

Access Module
Concept
Introduction
Multicast
Multicast, or broadband TV (BTV) is similar to traditional wired

broadcasting or television satellite broadcasting. Users have the same
experience in watching BTV programs and traditional television
programs. Unlike the traditional television, the IPTV system encodes
audio signals into media streams and multicasts the media streams
over an IP network to user terminals.
Fax
A communication tool widely used in enterprises and institutions to

transmit digital text and images through phone lines.
Point of sale
(POS)
A terminal supporting multiple functions. After being installed in a

promissory shop or designated network of a credit card and accessing
the network, the POS machine implements speedy, convenient, and
reliable automatic electronic funds transfer. The POS machine
supports consumption, advance payment, balance inquiry, and
transfer.
Wireless fidelity
(Wi-Fi)
A short-distance wireless transmission technology, which supports

wireless signals for Internet access within hundreds of feet.
Concept
Introduction
PON

ODN

OLT

MA5600T/MA5603T/MA5608T.
ONU
Split Ratio
Split ratio is the ratio of dividing a downstream optical signal into

sub-signals in the PON system. Greater optical ratio requires more
power to support physical distances.
Access Side
Issue 01 (2016-04-29)

936

Access Module
Network Side
Concept
Introduction
U-PE
User-end provider edges (U-PEs) are routing devices directly

connected to customer edges (UEs). U-PEs support routing and MPLS
encapsulation. If a U-PE is connected to multiple CEs and possesses
the basic bridging function, data frame forwarding only needs to be
performed on the U-PE. This reduces the load of the S-PE.
PE-AGG
Aggregation provider edge (PE-AGG) routers provide aggregation

and route forwarding functions for access equipment. Compared with
U-PEs, PE-AGGs features higher performance, fewer interfaces, and
higher switching rates.
NGN/IMS

NOTE
IPTV head end
The IPTV head end system functions as the contents preparation

platform in the IPTV system. It provides functions such as signal
receipt, media format conversion, and media material management.
11.2 Principles of Planning Data for FTTO Services

(SOHO and SME)
This section describes the principles of planning data for small office and home office
(SOHO) users and small- and medium-sized enterprises (SMEs) in fiber to the office (FTTO)
scenarios, from the aspect of security, device management, quality of service (QoS), and
services. The data of all the examples involved in this section is planned following the
principles.
11.2.1 Principles of Planing Device Management Data

The device management plan includes the channel management plan and the IP address plan.
Device Management Data Plan
Issue 01 (2016-04-29)
Plan
Device/Service
Description
Management
channel
OLT
Use a single-tagged VLAN as the device

management VLAN of the OLT. All other devices
in the network use single-tagged VLANs as the
device management VLAN.

937

Access Module
Plan
Device/Service
Description
ONU
Use a single-tagged S-VLAN as the management

VLAN of the ONU that is managed.
Set an S-VLAN for an entire network, an OLT, a
PON board or a PON port for identifying services
and physical locations.
IP address plan
(bridging
networking)
IP address plan
(gateway
networking)
Internet access
service
A PC obtains an IP address through PPPoE dialup.

The ONU transparently transmits the packets.
IPTV service
The set top box (STB) obtains an IP address from

the DHCP server for ordering programs. The ONU
VoIP service
The ONU functions as a DHCP client and obtains

an IP address from the DHCP server, or the NMS
issues a static IP address to the ONU using the
configuration file. Voice signaling and media
streams at multiple POTS ports share one IP
address. Media streams are distinguished by port.
Internet access
service
As a DHCP client, the ONU obtains a public IP

address through PPPoE dialup. As a DHCP server,
the ONU allocates private network IP addresses to
PCs that access the Internet through the network
cables or Wi-Fi. After NAT, all the PCs connected
to the router use the public IP address to access the
Internet.
IPTV service
As a DHCP client, the ONU obtains a public

network IP address through DHCP. As a DHCP
server, the ONU allocates private IP addresses to
STBs. After NAT, all the STBs connected to the
ONU use a public IP address to order programs.
VoIP service
As a DHCP client, the ONU obtains a public IP

address through DHCP, or the NMS allocates an
IP address to the ONU through a configuration
file, or the ACS allocates a static IP address to the
ONU through TR069. The voice signaling streams
and the media streams of multiple POTS ports
share the IP address. Media streams can be
distinguished by different ports.
11.2.2 Principle of QoS Planning

The QoS planning is an E2E planning, and it can be divided into following policies: traffic
classification, marking, and scheduling policy; and traffic monitoring and DBA policy.
Issue 01 (2016-04-29)

938

Access Module
Traffic Classification, Marking, and Scheduling Policy

Service
Type
802.1p
Priority
Queue
Scheduling
Method
OLT
Queue ID
(8 Queues)
ONU Queue.ID
When
Eight
Queues
Are
Supported
When Four
Queues
Are
Supported
Management
service
PQ
VoIP service
PQ
IPTV
service
PQ
Internet
access
service
PQ
Note: The service priorities in this table are the recommended values. The service priorities
are arranged according to the operators's actual plan.
Traffic Monitoring and DBA Policy
Issue 01 (2016-04-29)
Items
Management
service
Internet
access service
VoIP service
IPTV service
GEM port
11 [Remark 1]
12
13
14
TCONT
All services share a T-CONT.
DBA type
Type 3 (DBA profile: assured bandwidth + maximum bandwidth. Users

are allowed to preempt the bandwidth on condition that the users'
assured bandwidth is guaranteed. However, the total bandwidth cannot
exceed the maximum bandwidth.)
DBA
bandwidth
planning
Configure the DBA bandwidth according to the user's bandwidth

package.
Rate limit on
OLT
downstream
No rate limit

bandwidth is larger than or equal to the maximum bandwidth that users
apply.
Configure rate
limit by a traffic
profile as
required.
[Remark 2]
No rate limit

No rate limit
939

Access Module
Items
Management
service
Rate limit on
ONU upstream
port
No rate restriction
Rate limit on
ONU
downstream
port
No rate restriction
Internet
access service
VoIP service
IPTV service
Remark 1: GEM port value depends on the planning of the service provider, but in principle,
use different GEM ports for different services.
Remark 2: Table 11-1 shows the reference service bandwidth of each service for each user.
Issue 01 (2016-04-29)
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
Internet
access
service
Determi
ned
based on
the
service
tariff
package.
Determined based
on the service tariff
package.
Available bandwidth or Internet access

service = Committed bandwidth of the
service tariff package - VoIP bandwidth IPTV bandwidth
VoIP
service
200
kbit/s
200 kbit/s

symmetrical. The actual bandwidth is
related to the coding format. This
bandwidth is calculated for two POTS ports.
IPTV
service
(standar
d
definitio
n
program
)
2.5 Mbit/s per

channel

by one user (in the case of multiple STBs).
The upstream bandwidth is mainly used for
transmitting IGMP packets, which requires
little bandwidth. Therefore, the bandwidth
occupied by IGMP packets can be
neglected.

940

Access Module
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
IPTV
service
(high
definitio
n
program
)
9.7 Mbit/s per

channel
Note:
l
The rate restriction on the BRAS or SR is recommended. OLTs and ONUs do not restrict
the rate for service streams.
If BRAS does not support rate restriction, OLTs can restrict the rate for service streams
through the traffic profile.
Different service packets on the ONU are distinguished by different VLAN IDs. The
service packets are mapped to GEM ports based on VLAN IDs so that different service
packets are transmitted to different GEM ports. Each GEM port (each service)
corresponds to a T-CONT or all GEM ports share a T-CONT.
The sum of the assured bandwidth of all ONUs connected to a PON port and the fixed
bandwidth of OMCI management channel is less than the GPON upstream bandwidth.
Some bandwidth must be reserved for the future service expansion.
11.2.3 Principle of Internet Access Service Data Plan

The Internet access service plan mainly includes the plan of the VLAN and VLAN translation
policy in different network scenarios.
VLAN and VLAN Translation policy for Internet Access Service

Application
Scenario
VLAN Plan
Bridging ONU
Double-tagged VLAN
ONU: ONUs configure the VLAN and

All ONUs are in the same C-VLAN.
of every ONU differs from each other.
Gateway ONU
Double-tagged VLAN
ONU: ONUs configure the VLAN and

of every ONU differs from each other.
Issue 01 (2016-04-29)

941

Access Module
VLAN and VLAN Translation policy for Wi-Fi Service

Application
Scenario
VLAN Plan
Gateway ONU
Single-tagged VLAN
ONU: The upstream packets sent from

the Router carry user-VLANs and the
ONU transparently transmits them.
translation: C<->S.
Note:
l
UserVLAN: VLAN carried by upstream packets of user-side devices, U for short.
C-VLAN: VLAN added based on the ONU port. For details, see the description of the
Double-tagged VLAN S+C.
Double-layer VLAN S+C': C' indicates the translated inner VLAN (C'-VLAN) and S
indicates the outer VLAN (SVLAN).

C<->S+C': Bidirectional VLAN translation: translates the inner C-VLAN and then adds
one outer S-VLAN.
C<->S+C: Bidirectional VLAN translation: maintains the inner C-VLAN and adds one
outer S-VLAN.
NOTE
l To ensure traceability of users and finer-grained QoS control and management of users and services, plan
per user per service per VLAN (PUPSPV) for the Internet access service. Considering OLT capacity and
VLAN scalability, use dual VLANs (S-VLAN+C-VLAN) on the OLT to differentiate users for the
l The outer S-VLAN, which identifies services and physical location, can be allocated based on the OLT,
PON board, or PON port. The inner C-VLAN identifies users. User C-VLANs must be unique in one SVLAN.
l It is recommended that you use stacking VLANs as S-VLANs so that security features, such as PPPoE+/
opton82, and anti MAC attacks and anti spoofing spoofing can be easily deployed.
l The 802.1q in 802.1q (QinQ) VLAN is used in the enterprise private line scenario, such as (TLS). The
device transparently transmits packets. It is not recommended that you use QinQ VLANs as S-VLANs for
the triple play services of residential users.
11.2.4 Principles of Planning Voice Service Data

The voice service plan mainly includes the plan of the VLAN and VLAN translation policy in
different network scenario, and the plan of voice protocol.
Issue 01 (2016-04-29)

942

Access Module

Usage Scenario
VLAN Plan
Bridging ONU
Single-tagged VLAN
ONU: Provide the VoIP service through

the ONU. Configure the service VLAN
(S-VLAN) tag in a unified manner.
OLT: The OLT transparently transmits
S-VLAN tags.
Double-tagged VLAN
ONU: Provide the VoIP service through

the ONU. Configure the customer
VLAN (C-VLAN) tag in a unified
manner. The C-VLAN tag identifies the
VoIP service.
OLT: The OLT adds an S-VLAN tag to
a C-VLAN tag and supports the
switching between the C-VLAN tag and
the S-VLAN+C-VLAN tag.
Gateway ONU
Single-tagged VLAN
ONU: Configure a VLAN for all ONUs

and add the same C-VLAN tag to
packets. All ONUs are in the same CVLAN.
OLT: The OLT transparently transmits
VLAN tags (the C-VLAN is the same
as the planned S-VLAN).
Single-tagged VLAN
ONU: Configure a VLAN for all ONUs

packets. All ONUs are in the same CVLAN.
OLT: The OLT switches between the CVLAN tag and the S-VLAN tag (the CVLAN is different from the planned SVLAN).
Note:
l

one outer S-VLAN.
Issue 01 (2016-04-29)

943

Access Module
outer S-VLAN.
NOTE
l The VoIP service is a closed service self-operated by carriers. The single-tagged S-VLAN is the
mainstream application and is recommended.
l When the planned VLAN is single-tagged VLAN, the S-VLAN can identify services and physical
locations based on an OLT device, a PON board or a PON port. It is recommended that you set different
voice VLANs for the OLTs connected to one VoIP SR to avoid an excessively large broadcast domain of
the SR and convergence switch.
l When the planned VLAN is S-VLAN+C-VLAN, the outer S-VLAN can identify services and physical
locations based on an OLT device, a PON board or a PON port. The inner C-VLAN is used to identify
services (the fixed value) and users.
VoIP Data Plan Based on H. 248 or SIP

Description
Item
MG
interface/SI
P interface
data
NOTE
must be
consistent
with the
data on the
MGC/IMS
core
network
devices.
Media
and
signalin
g
paramet
ers
Media and
signaling
upstream VLANs
Upstream VLANs of the VoIP service
Media and
signaling
upstream port
Upstream ports of the VoIP service
Media IP
addresses and
signaling IP
addresses
Supports separating media from signaling.
Default gateway
IP address.
The next hop IP address from an

ONU/HGW to an MGC/IMS.
None
Signaling port ID
Select a transmission mode according to the

IP address of active MGC (H.

248)/IP address of active IMS
device (SIP)
If the dual homing is not configured, only

one MGC parameter needs to be
configured. If the dual homing is
configured, the IP address and port ID of
the standby MGC need to be configured.
Port ID of active MGC

(H248)/port ID of active IMS
device (SIP)
Issue 01 (2016-04-29)
Coding
Select the coding method according to the

Generally, the text coding method is
adopted.
Transmission mode
Select a transmission mode according to the

Generally, the UDP transmission mode is
adopted.

944

Access Module
Item
Voice port
data
Description
Home domain (SIP)
None
Profile index
None
The version of H248 protocol

that MG starts to negotiate
V1, V2 or V3 (by default). The interface

may fail to be registered because some
Phone number
For H248 protocol: The phone numbers

allocated by the MGC need to be
determined, and the paging numbers for
users' emergency standalone need to be
planned if the emergency standalone
function is provided.
For SIP protocol: The phone number that
the IMS core network device allocates to
the user must be configured.
Terminal ID (H248)
If the TID template with which the POTS

configured.
User priority

government users)
government users)
l cat3: common (common users)
User type

Common
parameter
Issue 01 (2016-04-29)
system parameter
The system parameters including the

overseas version flag and message waiting
indication (MWI) mode need to be
configured according to the local standard
to ensure that the response of the user
terminal complies with the local standard.

945

Access Module
Item
Description
Overseas parameters

standards.
POTS port attributes
If the POTS port needs to support the

polarity reversal accounting, the POTS port
polarity reversal pulse. Other attributes do
not need to be modified if there is no
special requirement.

changed, ring volume is changed
accordingly. Generally, no adjustment is
required for the ringing tone volume. You
need to modify the parameters of the
ringing current attributes according to the
local standard only when the default
ringing current attributes do not comply
with the local standard.

The IPTV service data plan mainly include the plan of VLAN and VLAN translation policy in
different network scenario, and the plan of IPTV service.
IPTV services include multicast service and video on demand (VoD) service. These two
services are relevant but independent in VLAN planning.

Applicatio
n Scenario
Service
Type
VLAN Plan
Bridging
ONU
Multicast
service
Singletagged
VLAN
ONUs transparently transmit upstream

packets with M-VLANs sent from STB.
Multicast packets are replicated downstream
with M-VLAN unchanged.
The OLT replicates multicast packets based on
PON ports with M-VLAN unchanged.
Singletagged
VLAN
Issue 01 (2016-04-29)
ONUs translate the upstream VLANs sent

from STB to M-VLANs.

946

Access Module
Applicatio
n Scenario
Gateway
ONU
Service
Type
VLAN Plan
VoD
Singletagged
VLAN
The ONU adds the default S-VLAN tag to

packets from iTV service ports.
Doubletagged
VLAN
The ONU adds C-VLAN tags to packets. All

ONUs are in the same C-VLAN.
Singletagged
VLAN
ONUs replicate packets based on user ports

and M-VLANs are removed in downstream
direction.
Multicast
service
The OLT transparently transmits S-VLAN

tags.
The OLT implements VLAN translation: U>S+C.

VoD
Singletagged
VLAN
ONUs add C-VLAN tags to packets.

Untagged VLANs are translated to C-VLANs.
The OLT implements VLAN translation: C ->
S.
Note:
l

one outer S-VLAN.
outer S-VLAN.
NOTE
l IPTV service is a closed service self-operated by carriers, and single-tagged S-VLAN is recommended.
l The same S-VLAN or different S-VLANs can be used as the M-VLAN and VoD VLAN. It is
recommended that you use different S-VLANs as M-VLAN and VoD VLAN so that the upper-level
device easily differentiates between the BTV service and VoD service.
l S-VLANs of VoD service can identify services and physical locations based on an entire network or an
OLT. It is recommended that you set different VoIP VLANs for the OLTs connected to one VoIP SR to
avoid an excessively large broadcast domain of the VoIP SR and convergence switch.
Issue 01 (2016-04-29)

947

Access Module

NOTE
l
System Security
Security
Vulnerability
Solution

Suggestion
DoS attack

MDU.

deployment.
IP attack

MDU.

deployment.
Issue 01 (2016-04-29)

948

Access Module
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing

and MDU.
malicious attacks.
deployment.
MAC attack
Enable the anti-MAC

and MDU.

malicious attacks.
deployment.
IP spoofing

function for MDU.

malicious attacks.
deployment.
Issue 01 (2016-04-29)

949

Access Module
Service Security
Security
Vulnerability
Solution

Suggestion
Unauthorized
broadband access of
small enterprises
(IPoE)

RAIO information.

exhaustion.
DHCP addresses.
spoofing.
Broadband access of
residential users
(PPPoE), user
account theft/
borrowing

binding of the RAIO
account.

spoofing.
11.3 Bridging Networking(GPON)

optical network units (ONUs) in bridging networking.
Issue 01 (2016-04-29)

950

Access Module

Optical network units (ONUs) work in bridging mode. This scenario provides transparent
transmission channels and requires simple service configuration, so this scenario applies to
Layer 2 networking.
l
PCs connect to an ONU.
TVs connect to an ONU through set top boxes (STBs) to receive VoD and multicast
services.
The Internet access, and IPTV services are secure.
The Internet access service is protected against unauthorized access, user account
forgery or unauthorized borrowing, MAC or IP address spoofing, and attacks from
malicious users.
The IPTV services are protected against MAC or IP address spoofing, attacks from
malicious users, and heavy traffic.
A service fault is easy to locate, and services are easy to maintain.
Usage Scenario
Figure 11-1 Bridging networking

Figure 11-2 shows the configuration procedure in the bridging networking.
Issue 01 (2016-04-29)

951

Access Module
Figure 11-2 Configuration procedure in the bridging networking
The following table lists the detailed description steps.
Issue 01 (2016-04-29)
Item
Procedure
Remarks
OLT
Adding an ONU to an OLT

only after the ONU is successfully added to
an OLT.
OLT
Configuring the Internet Access

Service
OLT
Configuring the BTV Service
OLT
Configuring the VoD Service

OLT
Configuring Link Aggregation,

Congestion Control, and
Security Policy
Service reliability is improved by

configuring uplink aggregation and priority
scheduling policy for queues in global
configuration mode, and service security is
improved by configuring security policy in
global configuration mode.

952

Access Module
Item
Procedure
Remarks
OLT
Verifying Services

methods including ONU PPPoE and DHCP
dialup emulation and multicast emulation
for configuration and commissioning
on-site operation.

Data Plan
Item
Data
DBA profile
Profile name: ftto_dba

Profile type: type3
ONU line profile
Profile name: ftto_line

T-CONT ID: 4
ONU service
profile
Profile name: ftto_ser
Network
topology data
PON port: 0/1/0
ONU port capability set: adaptive
ONU IDs: 1 and 2
Procedure
GPON ONU profiles include the DBA profile, line profile, service profile, and alarm profile.
l
Issue 01 (2016-04-29)
utilization.
953

Access Module
the ONU-side service.
Service profile: A service profile provides the service configuration channel for the ONU
(OMCI).
monitor the performance of activated ONU lines. When a statistical value reaches the
1.

Create the same DBA profile for different types of services. Set the profile name to
ftto_dba, profile type to type3, assured bandwidth to 8 Mbit/s, and maximum bandwidth
to 50 Mbit/s.
huawei(config)#dba-profile add profile-name ftto_dba type3 assure 8192 max
51200
NOTE
The DBA implementation is based on an ONU. Therefore, select a DBA profile of the proper
bandwidth type and configure proper bandwidth according to the service types and total user count of
the ONU. Note that the sum of the fixed bandwidth and the assured bandwidth must not be greater than
the total bandwidth of the PON port.
2.

Create a GPON ONU line profile, named ftto_line, and bind it to the DBA profile
ftto_dba.
huawei(config)#ont-lineprofile gpon profile-name ftto_line
huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name ftto_dba

NOTE
port.
settings.
3.
Issue 01 (2016-04-29)
Configure an ONU service profile.

Create a GPON ONU service profile, named ftto_ser. Configure the capability set of the
ETH port and POTS port to adaptive. Then the system automatically adapts to the ONU
according to the actual capability of the online ONU.
954

Access Module
huawei(config)#ont-srvprofile gpon profile-name ftto_ser

setting.
4.
which is used for monitoring the performance of an activated ONU line.
Step 2 Add an ONU.

Connect two ONUs to GPON port 0/1/0. Set the ONU IDs to 1 and 2, SNs to
Bind the two ONUs to ONU line profile ftto_line and ONU service profile ftto_ser.
There are two methods of adding an ONU: add an ONU offline and confirm an automatically
discovered ONU.
l
Add ONUs offline.

If the password of an ONU is known, run the ont add command to add an ONU offline.
ftto_line ont-srvprofile-name ftto_ser
Confirm automatically discovered ONUs

If the password or SN of an ONU is unknown, run the port portid ont-auto-find
command in GPON mode to enable the ONU auto-discovery function of the GPON port.
Then, run the ont confirm command to confirm the ONU.
//After this command is executed, the information about all ONUs connected
huawei(config-if-gpon-0/1)#ont
ftto_line ont-srvprofile-name
confirm 0 ontid 1 sn-auth 3230313126595540

ftto_ser
ftto_ser
NOTE
If multiple ONUs of the same type bound to the same line profile or service profile are connected to the
same port, you can bulk add ONUs by bulk confirming automatically discovered ONUs to make
huawei(config-if-gpon-0/1)#ont confirm 0 all sn-auth omci ont-lineprofilename ftto_line
ont-srvprofile-name ftto_ser
l
Issue 01 (2016-04-29)

955

Access Module

Step 3 Check ONU status.

ONU. Ensure that Config flag of the ONU is active, Run State is online, Config state is
--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
//Indicates that the ONU is
activated.
Run state
: online
//Indicates that the ONU goes online
successfully.
Config state
: normal
the ONU is normal.
Match state
: match
to the ONU is consistent with the actual capability of the ONU.
l
ONU.
----End

The OLT is connected to the remote ONU through a GPON port to provide users with highspeed Internet access services.
Prerequisite
l
The ONU has been added to the OLT. For details, see 11.3.3 Adding an ONU to an
OLT.
Issue 01 (2016-04-29)

956

Access Module
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
ONU service profile


PON port: 0/1/0
ONU IDs: 1 and 2
ID of the port on the ONU that is connected to the PC: 1
Procedure
l
Configure the OLT.

a.

Set the profile ID to ftto_hsi, the CIR to 4 Mbit/s, and the priority to 0. In addition,
priorities.
huawei(config)#traffic table ip name ftto_hsi cir 4096 priority 0
b.
Issue 01 (2016-04-29)
Configure the mapping between a GEM port and a VLAN. Create a VLAN and a
service flow.

957

Access Module
Table 11-4 Scenario plan

Scenario
VLAN Plan
bridging ONU +
Router
Double-tagged
VLAN
ONU: ONUs configure the VLAN

packets. All ONUs are in the same
C-VLAN.
l S-VLAN ID: 100

l S-VLAN type:
smart
l S-VLAN
attribute:
stacking
OLT: The OLT switches between

the C-VLAN tag and the S-VLAN
+C'-VLAN tag.
l C'-VLAN ID:
1001-1002
l C-VLAN ID: 45
Configure the mapping between a GEM port and a VLAN. The service flow of
user-side VLAN 45 is mapped to GEM port 14 in the ONU line profile.
Configure the VLAN of the Ethernet port on the ONU. add Ethernet port 1 to
VLAN 45 in the ONU service profile.
Create an Internet access service VLAN and add an upstream port to it. Add
upstream port 0/19/0 to VLAN 100.
Create Internet access service flows. Set S-VLAN ID to 100 and GEM port ID to
14. Use traffic profile ftto_hsi.
traffic-table
name ftto_hsi outbound traffic-table name ftto_hsi
traffic-table
name ftto_hsi outbound traffic-table name ftto_hsi
c.
Save the data.

huawei(config)#save
The ONU does not need to be configured.
----End
Issue 01 (2016-04-29)

958

Access Module

The OLT is connected to the remote bridging ONU through a GPON port to provide users
Prerequisites
l
The IPTV WAN ports on the ONU use factory defaults.
OLT.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 13
ONU service profile

Traffic profile
ID: 8
802.1p priority: 4

Procedure
l
Configure the OLT.

a.

Configure traffic profile 8. Set the CIR to off (unlimited), priority to 4, and prioritybased scheduling policy to local-setting (that is, queues are scheduled based on the
priority specified in the profile).
NOTE
Run the display traffic table ip command to query existing traffic profiles in the system. If the
existing traffic profiles in the system do not meet the requirements, run the traffic table ip
huawei(config)#traffic table ip index 8 cir off priority 4 prioritypolicy
local-setting
Issue 01 (2016-04-29)

959

Access Module
b.
Configure the mapping between a GEM port and an Ethernet port on an ONU.
Create a service VLAN and a service flow.
VLAN Plan
l S-VLAN ID: 1000
ONU: transparently transmits the

MVLAN of the user port. Multicast
packets are duplicated downstream
l C-VLAN ID: 1000

l MVLAN ID: 1000
l VLAN type: smart
OLT: duplicates multicast packets

based on PON ports with MVLAN
unchanged.
Configure the mapping between a GEM port and an Ethernet port on an ONU. If
the ONU is connected to the STB through Ethernet port 2, map the service flow of
Ethernet port 2 to GEM port 13 in the ONU line profile.
huawei(config-gpon-lineprofile-1)#mapping mode port
huawei(config-gpon-lineprofile-1)#gem mapping 13 1 eth 2
Configure a VLAN translation policy for the Ethernet port on the ONU. If the ONU
is connected to the HGW through Ethernet port 2, VLAN 43 of the HGW is
translated to VLAN 1000 and the MVLAN of the ONU is translated to VLAN
1000.
Configure the native VLAN of the ONU port. If the ONU is connected to the STB
through Ethernet port 2, the native VLAN ID is 1000.
Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to
VLAN 1000.
Create service flows. Set the service VLAN to 1000, GEM port ID to 13, and user
VLAN to 1000, and use traffic profile 8.
multi-service
multi-service
Issue 01 (2016-04-29)

960

Access Module
c.

in the
d.

NOTE
off.
e.
Set the IGMP mode.

f.
Configure the IGMP upstream port.

Set the IGMP upstream port ID to 0/19/0 and working mode to default. Protocol
packets are transmitted to all the IGMP upstream ports in the multicast VLAN.
g.
(Optional) Set multicast global parameters.

In this example, the default settings are used for all the multicast global parameters.
h.

i.
Save the data.

huawei(config)#save
The ONU does not need to be configured.
----End
Issue 01 (2016-04-29)

961

Access Module

The OLT is connected to the remote bridging ONU through a GPON port to provide users
Prerequisites
l
OLT.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 13
ONU service profile

Traffic profile
ID: 8
802.1p priority: 4
Procedure
1.

NOTE
Run the display traffic table ip command to query existing traffic profiles in the system. If the existing
traffic profiles in the system do not meet the requirements, run the traffic table ip command to add a
traffic profile.
local-setting
2.
Issue 01 (2016-04-29)
Perform this step in the bridging ONU (single VLAN tag) scenario.

962

Access Module

VLAN Plan
S-VLAN ID: 1100
The ONU adds the default S-VLAN tag

to packets from iTV service ports.
VLAN type: smart

C-VLAN = U-VLAN
The OLT transparently transmits SVLAN tags.
Configure the mapping between a GEM port and a VLAN. The service flow of user
VLAN 1100 is mapped to GEM port 13 in the ONU line profile.
Configure the VLAN of the Ethernet port on the ONU. If the ONU is connected to the
STB through Ethernet port 2, add Ethernet port 2 to VLAN 1100.
VLAN 1100.
rx-cttr 8 tx-cttr 8 tag-transform transparent
rx-cttr 8 tx-cttr 8 tag-transform transparent
3.
Perform this step in the bridging ONU (double VLAN tags) scenario.
VLAN Plan
S-VLAN ID: 1100
The ONU adds C-VLAN tags to packets.

VLAN type: smart

VLAN attribute: stacking
C'-VLAN: 2010
The OLT switches between the C-VLAN

tag and the S-VLAN+C'-VLAN tag.
C-VLAN: 2001
Issue 01 (2016-04-29)

963

Access Module
Configure the VLAN of the Ethernet port on the ONU. If the ONU is connected to the
STB through Ethernet port 2, add Ethernet port 2 to VLAN 2001.
Create a service VLAN and add an upstream port to it. Set the attribute of VLAN 1100
VLAN to 2001, and use traffic profile 8. Set the VLAN translation policy to Translate
and Add to translate the C-VLAN 2001 to C'-VLAN 2010.
multi-service user-vlan 2001 tag-transform translate-and-add inner-vlan 2010
rx-cttr 8 tx-cttr 8
multi-service user-vlan 2001 tag-transform translate-and-add inner-vlan 2010
rx-cttr 8 tx-cttr 8
4.
Save the data.

huawei(config)#save
Step 2 The ONU does not need to be configured.

----End

Security Policy
Service reliability is improved by configuring uplink aggregation and priority scheduling
policy for queues in global configuration mode, and service security is improved by
configuring security policy in global configuration mode.
Context
In link aggregation, multiple uplink Ethernet ports are aggregated into a group to increase
bandwidth and reliability of uplinks of the OLT. You are advised to configure link
aggregation.
packets based on queue priorities. You are advised to configure congestion control.
Security policy involves system security, user security, and service security, ensuring service
security from different aspects.
NOTE
l You are advised to enable the service security feature according to service types. For details, see 11.2.6
Principle of Security Data Plan.
l The configuration of the system security, user security, and service security introduced in this topic is on
the OLT side. The configuration on the ONU side is through the web and is simple, here we do not
introduced it.
Issue 01 (2016-04-29)

964

Access Module
Procedure
l

On the OLT side, configure upstream ports 0/19/0 and 0/19/1 as an aggregation group.
Each member port in the aggregation group is allocated packets based on the source
MAC address. The working mode is LACP static aggregation.
Configure queue scheduling(On the OLT side).

According to "11.2.2 Principle of QoS Planning", all packets are scheduled in strict

i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
Issue 01 (2016-04-29)

965

Access Module
iv.

i.

level.
The VLAN level:
ii.
1)

2)

3)

effect.
4)
5)

level.

i.
default.
global level.
Issue 01 (2016-04-29)

966

Access Module
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

In the FTTO scenario, ONUs are installed at users' houses or in business buildings which are
far away from the central equipment room. ONUs provide remote service verification
methods including PPPoE dialup emulation, and multicast emulation to facilitate
configuration and commissioning engineers to verify services remotely after service
configuration.
Prerequisites
ONUs and upper-layer devices have been connected properly. The BRAS has been
configured.
Issue 01 (2016-04-29)

967

Access Module
Background
Remote
Service
Verificati
on
Method
Function
Description
PPPoE
dialup
emulation
An ONU simulates a PPPoE user

between the ONU and BRAS.

a QinQ VLAN.
l An ONU supports a maximum of a
Multicast
emulation

stream to an ONU. You can
multicast program.

Item
Data
Remarks
PPPoE
dialup
emulation
parameters

Multicast
emulation
parameters
Data plan
Password: test
MVLAN: 1000
program: 224.1.1.10
Procedure
l

a.
Issue 01 (2016-04-29)
dialup emulation test.

968

Access Module
The service is functional if the test result is success. The following test uses GPON
as an example:
{ portid<0,7> }:0
{ ontid<0,127> }:1
Command:
---------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
ONT ETH Port ID
: 4
ONT Vlan ID
: 100
Vlan Priority
: Emluator result
: Success
Session ID
: 18814
User IP
: 172.16.100.109
Gateway IP
: 172.16.100.1
----------------------------------

a.
b.

n
Run the display ont info command to query the ONU status to check whether
the ONU is registered successfully.
If a native VLAN is configured for the Ethernet port on the ONU, run the
status.
i.
ii.
Issue 01 (2016-04-29)
ONU is activated, whether the PC is connected to the right port on the
ONU, and whether the PC is working properly.
Run the display ont-learned-mac command to check whether the ONU

969

Access Module
If not, check whether the ONU properly connects to the PC or home gateway
(HGW).
l

a.
program.
huawei(config)#btv
1000
NOTE
b.
The multicast user is normal if the queried result is online.
User
: 0/1/0/1
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 1
Video flow ID
: 1
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Current version
: IGMP v3
Available programs
: 8
Global leave
: disable
User max bandwidth
: no-limit
: 0
Used bandwidth
to max bandwidth(%)
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start time
-------------------------------------------------------------------------PROGRAM-5
1000 224.1.1.10
watching
2011-10-29
16:33:41+08:00
-------------------------------------------------------------------------Total: 1
c.
The multicast program can be ordered if the queried result is a non-empty value.
224.1.1.10
Command:
----End
Issue 01 (2016-04-29)

970

Access Module
11.4 Gateway Networking(GPON)

optical network units (ONUs) in gateway networking.
Context
NOTE
Web pages displayed in this section are examples of the MA5675 unless otherwise stated. Other ONUs
have the similar operation process. Web pages of different products may be different. However,
differences do not affect functions.

Small office and home office (SOHO) is positioned for miniature enterprises, such as shops
and markets, and home officers.
Optical network units (ONUs) work in gateway mode. Users require Internet, voice, and
multicast services. The HGW ONU facilitates interconnection of home devices by providing
Layer 3 services, such as Point-to-Point Protocol over Ethernet (PPPoE)/DHCP dialup,
network address translation (NAT), and Internet Group Management Protocol (IGMP)
snooping. This scenario provides fine-grained management channels and service control, and
mainly applies to Layer 3 networking.
l
The Internet can be accessed through not only cables but also wireless fidelity (Wi-Fi). A
SOHO user connects to an ONU through the LAN port on the user's computer. The
Dynamic Host Configuration Protocol (DHCP) address pool of the ONU assigns an IP
address to the user. After PPPoE dialup is automatically performed on the ONU, the
ONU connects to the OLT in GPON access mode and then connects to the upper-layer
network, to provide the high-speed Internet access service for the SOHO user.
Many voice service ports are required to connect to phone sets, fax machines, and point
of sale (POS) machines.
TVs connect to an ONU through set top boxes (STBs) to receive VoD and multicast
services.
The Internet access, voice, and IPTV services are secure.
The Internet access service is protected against unauthorized access, user account
forgery or unauthorized borrowing, MAC or IP address spoofing, and attacks from
malicious users.
The voice and IPTV services are protected against MAC or IP address spoofing,
attacks from malicious users, and heavy traffic.
A service fault is easy to locate, and services are easy to maintain.
Usage Scenario
Issue 01 (2016-04-29)

971

Access Module
Figure 11-3 SOHO networking

PC
ONU
TV
AAA Server
STB
Portal Server
Phone
PE-AGG
Fax
OLT
POS
UPE
Metro Network
PC
ONU
Optical
splitter
NGN/IMS
IPTV
Headend
Internet
UPE
PE-AGG
TV
STB
Phone
AAA Server
Fax
HLR
POS

Figure 11-4 shows the configuration procedure in the gateway networking.
Figure 11-4 Configuration procedure in the gateway networking
Issue 01 (2016-04-29)

972

Access Module

Item
Procedure
Remarks
OLT

only after the ONU is successfully added to
an OLT.
OLT
Configuring the Internet Access

Service
Configuring the
Voice Service
NOTE
ONU
OLT
ONU
Configuring
Service (on a
Web Page)
Configuring
Service
(Through the
CLI)
Configuring
the SIP-based
Voice Service
(on a Web
Page)
Configuring
the SIP-based
Voice Service
(Through the
CLI)
OLT
OLT
Configuring the VoD Service
OLT
Configuring the
Wi-Fi Service
ONU
Issue 01 (2016-04-29)

Configuring
the Wi-Fi
Service
Configuring
Soft GRE
Tunnel-based
Wi-Fi Sharing
Configuring
VLAN Tunnelbased Wi-Fi
Sharing

973

Access Module
Item
Procedure
Remarks
OLT
Configuring Link Aggregation,

Congestion Control, and
Security Policy
Service reliability is improved by

configuring uplink aggregation and priority
scheduling policy for queues in global
configuration mode, and service security is
improved by configuring security policy in
global configuration mode.
OLT
Verifying Services

methods including ONU PPPoE and DHCP
dialup emulation, call emulation, and
multicast emulation for configuration and
commissioning engineers to verify services
remotely after service configuration,
avoiding a second on-site operation.

Data Plan
Item
Data
DBA profile
Profile name: ftto_dba

Profile type: type3
ONU line profile

T-CONT ID: 4
Issue 01 (2016-04-29)
ONU service
profile
Network
topology data
PON port: 0/1/0
ONU IDs: 1 and 2

974

Access Module
Procedure
GPON ONU profiles include the DBA profile, line profile, service profile, and alarm profile.
l
utilization.
the ONU-side service.
Service profile: A service profile provides the service configuration channel for the ONU
(OMCI).
monitor the performance of activated ONU lines. When a statistical value reaches the
1.

ftto_dba, profile type to type3, assured bandwidth to 8 Mbit/s, and maximum bandwidth
to 50 Mbit/s.
huawei(config)#dba-profile add profile-name ftto_dba type3 assure 8192 max
51200
NOTE
The DBA implementation is based on an ONU. Therefore, select a DBA profile of the proper
bandwidth type and configure proper bandwidth according to the service types and total user count of
the ONU. Note that the sum of the fixed bandwidth and the assured bandwidth must not be greater than
the total bandwidth of the PON port.
2.

Create a GPON ONU line profile, named ftto_line, and bind it to the DBA profile
ftto_dba.
huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name ftto_dba
Issue 01 (2016-04-29)
add
add
add
add
11
12
13
14
eth
eth
eth
eth

tcont
tcont
tcont
tcont
4
4
4
4
975

Access Module
NOTE
port.
settings.
3.

Create a GPON ONU service profile, named ftto_ser. Configure the capability set of the
ETH port and POTS port to adaptive. Then the system automatically adapts to the ONU
according to the actual capability of the online ONU.
setting.
4.
which is used for monitoring the performance of an activated ONU line.
Step 2 Add an ONU.

Connect two ONUs to GPON port 0/1/0. Set the ONU IDs to 1 and 2, SNs to
Bind the two ONUs to ONU line profile ftto_line and ONU service profile ftto_ser.
There are two methods of adding an ONU: add an ONU offline and confirm an automatically
discovered ONU.
l
Add ONUs offline.

If the password of an ONU is known, run the ont add command to add an ONU offline.
Confirm automatically discovered ONUs

If the password or SN of an ONU is unknown, run the port portid ont-auto-find
command in GPON mode to enable the ONU auto-discovery function of the GPON port.
Then, run the ont confirm command to confirm the ONU.
Issue 01 (2016-04-29)

976

Access Module

//After this command is executed, the information about all ONUs connected

ftto_ser
ftto_ser
NOTE
If multiple ONUs of the same type bound to the same line profile or service profile are connected to the
same port, you can bulk add ONUs by bulk confirming automatically discovered ONUs to make
huawei(config-if-gpon-0/1)#ont confirm 0 all sn-auth omci ont-lineprofilename ftto_line
ont-srvprofile-name ftto_ser

Step 3 Check ONU status.

ONU. Ensure that Config flag of the ONU is active, Run State is online, Config state is
--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
successfully.
Config state
: normal
the ONU is normal.
Match state
: match
to the ONU is consistent with the actual capability of the ONU.
l
ONU.
Issue 01 (2016-04-29)

977

Access Module
----End

The OLT is connected to the remote ONU through a GPON port to provide users with highspeed Internet access services.
Prerequisite
l
OLT.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
ONU service profile

Procedure
l
Configure the OLT.

a.

Set the profile ID to ftto_hsi, the CIR to 4 Mbit/s, and the priority to 0. In addition,
priorities.
huawei(config)#traffic table ip name ftto_hsi cir 4096 priority 0
b.
Issue 01 (2016-04-29)
Configure the mapping between a GEM port and a VLAN. Create a service VLAN
and a service flow.
978

Access Module

Scenario
VLAN Plan
gateway ONU
Double-tagged
VLAN
ONU: Configure a VLAN for all

ONUs and add the same C-VLAN
tag to packets. All ONUs are in
the same C-VLAN.
l S-VLAN ID: 100

l S-VLAN type:
smart
l S-VLAN
attribute:
stacking
OLT: The OLT switches between

the C-VLAN tag and the S-VLAN
+C'-VLAN tag. All ONUs are in
different C-VLANs.
l C-VLAN ID:
1001
l C'-VLAN ID:
1010-1011
VLAN 100.
VLAN to 1001, and use traffic profile ftto_hsi.
traffic-table name
ftto_hsi outbound traffic-table name ftto_hsi
traffic-table name
ftto_hsi outbound traffic-table name ftto_hsi
c.
Save the data.

huawei(config)#save
Configure an optical network terminal (ONU) on the Web page.

Layer 3 route mode is used for connecting an ONU to the upper-layer device. IP
addresses of users' PCs are allocated by the DHCP IP address pool on the ONU. PPPoE
auto dialup is performed on the ONU. Parameters of the WAN port must be configured
on the ONU.
a.
Issue 01 (2016-04-29)
Log in to the Web configuration window.

979

Access Module
i.

segment as the IP address of the local maintenance Ethernet port on the ONU
(default: 192.168.100.1).
ii.
Open the Web browser, and enter the IP address of the local maintenance
Ethernet port of the ONU.
iii. On the login window, enter the user name (default: telecomadmin) and
password (default: admintelecom) of the administrator. After the password
authentication is passed, the Web configuration interface is displayed.
b.
c.
Issue 01 (2016-04-29)

i.
In the navigation tree, choose LAN > LAN Port Work Mode. Select the
check box of LAN 1 and set LAN1 to work in the Layer 3 mode.
ii.
Click Apply to apply the configuration.

i.
In the navigation tree, choose WAN > WAN Configuration.
ii.
In the right pane, click New. In the dialog box that is displayed, configure
parameters of a WAN port as follows:
WAN Connection: Enable
Encapsulation Mode: PPPoE
WAN mode: Route WAN
Service type: INTERNET (For configuring the Internet access service,

INTERNET or a combination containing INTERNET needs to be
selected.)
VLAN ID: 1001 (The VLAN ID of the ONU must be the same as the
user-side VLAN ID configured on the OLT.)
802.1p: 1
User Name: iadtest@pppoe, Password: iadtest (The user name and

password must be the same as the user name and password configured on
the BRAS.)
Binding options: LAN1
IP acquisition Mode: PPPoE
NAT: Enable (NAT must be enabled to configure the Internet access

service.)

980

Access Module
iii. Click Apply to apply the configuration.

d.
Save the configuration.

In the navigation tree, choose System Tools > Configuration File. In the right
pane, click Save Configuration to save the configuration.
e.
Check the ONU connection status.

Status is Connected and the obtained IP address is displayed at IP Address.
----End
Issue 01 (2016-04-29)

981

Access Module
11.4.5 Configuring the Wi-Fi Service (Web Pages)

An OLT connects to remote ONUs using GPON ports to provide the high-speed Wi-Fi access
service for users.
Prerequisites
l
The OLT communicates with the BRAS.
Dialup users have been configured on the BRAS based on user authentication and
charging requirements. For details about the configurations, see the Configuration
Guide.
An ONU has been added to the OLT. For details about how to add an ONU to an OLT,
see 11.4.3 Adding an ONU to an OLT.
The Internet access service has been configured. For details, see Configuring the
Internet Access Service.
The VLAN housing the LAN switch port connected to the OLT is the same as the
upstream VLAN configured on the OLT.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID of the Internet access service: 14
VLAN planning
Dual VLAN tags:

l S-VLAN ID: 100
l C-VLAN ID: 1001
l C'-VLAN ID: 1010-1011
l ONU: VLANs are centrally configured. A C-VLAN
tag is added to packets on ONUs, and all ONUs use the
same C-VLAN.
l OLT: VLAN translation, C <-> S+C', is performed on
the OLT. Each ONU has a unique C'-VLAN.
Procedure
Step 1 Before configuring the Wi-Fi service using web pages, perform the following operations to
log in to the configuration web page:
1.
Issue 01 (2016-04-29)
Set the IP address of the network interface card (NIC) on the PC. Ensure that this IP
address is in the same network segment as the local maintenance IP address
(192.168.100.1 by default) of the ONU.
982

Access Module
2.
Start the IE browser, enter https://192.168.100.1:80 or http://192.168.100.1 in the

address bar. (https://192.168.100.1:80 is preferred because of higher security.) In the
login web page, enter the user name and password, the default values of which are
telecomadmin and admintelecom, respectively. After the password is authenticated, the
configuration web page is displayed.
Configure the Layer 3 bridging Wi-Fi service.

1.
Configure Wi-Fi parameters.

Choose WLAN from the main menu. Then, in the navigation tree on the left side of the
page, choose WLAN Basic Configuration and configure parameters shown in the
following figure.
2.
Configure Layer 3 bridging WAN port parameters.

Choose WAN from the main menu. Then, in the navigation tree on the left side of the
page, choose WAN Configuration and configure parameters shown in the following
figure.
Issue 01 (2016-04-29)

983

Access Module

1
Must be the same as the

user-side VLAN ID configured
on the OLT
2
NOTE
In this example, the Internet access service using Wi-Fi is implemented in PPPoE dialup mode. If the
DHCP mode is required, set Encapsulation Mode to IPoE and enable DHCP relay. For details, see
Web Page Reference.
3.
Check ONU connection status.

Choose Status from the main menu. Then, in the navigation tree on the left side of the
page, choose WAN Information to check the ONU connection status.
Configure the Layer 3 routing Wi-Fi service.

1.

Choose WLAN from the main menu. Then, in the navigation tree on the left side of the
page, choose WLAN Basic Configuration and configure parameters shown in the
following figure.
Issue 01 (2016-04-29)

984

Access Module
2.
Issue 01 (2016-04-29)
Configure Layer 3 routing WAN port parameters.

985

Access Module
For configuring the Internet access

service, INTERNET or a combination
containing INTERNET needs to be
selected
Must be the same as the user-side VLAN
ID configured on the OLT
(The user name and password must be

the same as the user name and
password configured on the BRAS
3.

Choose Status from the main menu. Then, in the navigation tree on the left side of the
page, choose WAN Information to check the ONU connection status.
----End
Result
l
For the Layer 3 bridging Wi-Fi service, SSID-specific wireless signals can be detected
by the PC. After a user enters a correct authentication key and is PPPoE authenticated,
the user can access the Internet.
For the Layer 3 routing Wi-Fi service, SSID-specific wireless signals can be detected by
the PC. After a user enters a correct authentication key, the PC automatically obtains an
Issue 01 (2016-04-29)

986

Access Module
IP address allocated by the ONU using DHCP. After the ONU automatically performs
PPPoE dialup and the dialup is successful, the user can access the Internet.
NOTE
The security and encryption modes configured on Wi-Fi terminals must be the same as those configured on
the ONU. If a Wi-Fi terminal does not support TKIP&AES or AES, the Wi-Fi driver may be of an early
version. In such a case, update the driver.
11.4.6 Configuring Soft GRE Tunnel-based Wi-Fi Sharing (U2000)

This section describes how to configure soft GRE tunnel-based Wi-Fi sharing on a GPON
ONU.
Prerequisites
In the soft GRE tunnel solution, the BRAS supports Ethernet over GRE tunnels and
encapsulates and decapsulates GRE packets. The ONU connects to a Huawei ME60, which
uses a specified version and service board to support soft GRE tunnels. If the ONU connects
to a third-party router, the router supports EoGRE tunnels.
Data Plan
For data upstream transmission using soft GRE tunnels, data can be authenticated in web
portal or 802.1x mode.
This section uses the 802.1x authentication as an example. The differences between the two
authentication modes are provided in the following steps.
Item
Data
Value-added ONU service

profile
Profile name: FTTO_value
WAN port parameters
WAN port name: WAN1

WAN port status: enabled
Connection type: routing
NAT (NATEnabled) status: enabled
Service type: Internet access
RADIUS parameters
Authentication mode: 802.1x-EAP

IP address of the RADIUS server: 195.101.106.254
Key of the RADIUS server: SoftGRE1
RADIUS authentication port: 1812
RADIUS accounting: enabled
RADIUS accounting port: 1813
GRE tunnel parameters
Tunnel name: GRE

Outbound port: WAN1
IP address of the peer end: 136.136.136.136
Inbound port: SSID2
Issue 01 (2016-04-29)

987

Access Module
Item
Data
Static routing parameters
Destination IP address: 195.101.106.254

Mask of the destination address: 255.255.255.255
WAN port name: WAN1
Procedure
Step 1 Configure a WAN port.
1.
Log in to a U2000 client and choose Configuration > Access Profile Management
from the main menu.
2.
In the navigation tree on the left side of the window, choose PON Profile > ONT VAS
Profile. Then, click the General ONT VAS Profile tab page on the right side of the
window. Right-click the list in the lower part and choose Add(Service Configuration
Type) from the shortcut menu.
3.
In the dialog box that is displayed, configure the profile name. In the navigation tree on
the left side of the window, right-click WAN Device > WAN Device 1 > WAN
Connection and choose Add IP Connection from the shortcut menu. Add a routing
WAN port and configure basic WAN parameters.
Step 2 Add two SSIDs. Configure SSID2 as the operator SSID. Set WLAN authentication
parameters for the operator.
1.
Issue 01 (2016-04-29)
In the navigation tree on the left side of the window, right-click LAN Device > LAN
Interface 1 > WLAN Configuration and choose Add from the shortcut menu. Then,
add two SSIDs.

988

Access Module
2.
Interface 1 > WLAN Configuration for ISP and choose Add from the shortcut menu.
Right-click the added WLAN Configuration for ISP 1 and choose SSID Index 2 from
the shortcut menu.
3.
Click Next. In the window that is displayed, click Add. Then, configure the
authentication mode and parameters for WLAN Configuration for ISP 1.
Issue 01 (2016-04-29)

989

Access Module
NOTE
In 802.1x authentication mode, RADIUS parameters listed in the red box must be configured. In web
portal authentication mode, RADIUS parameters do not need to be configured.
Step 3 Configure WAN port parameters.

In the navigation tree on the left side of the window, choose WAN Device > WAN Device 1 >
WAN Connection > WAN Connection 1 > WAN IP Interface > WAN IP Interface 1.
Then, in the pane on the right side of the window, configure WAN port parameters.
Step 4 Configure a GRE tunnel.

1.
Issue 01 (2016-04-29)
In the navigation tree on the left side of the window, right-click SoftGRE Tunnel
Management and choose Add from the shortcut menu. Click the added SoftGRE
990

Access Module
Tunnel InfoInstance 1 and configure the soft GRE tunnel in the pane on the right side
of the window.
Egress Interface is the configured WAN port, and Remote Address is the IP address of
the ME60.
2.
In the navigation tree on the left side of the window, right-click SoftGRE Tunnel
Management > SoftGRE Tunnel InfoInstance 1 > SoftGRE Tunnel Ingress
Interface and choose Add from the shortcut menu. Click the added SoftGRE Tunnel 1
and configure the inbound port of the soft GRE tunnel in the pane on the right side of the
window.
Step 5 Configure a static route.

1. In the navigation tree on the left side of the window, right-click Layer 3 Forwarding >
Static route and choose Add from the shortcut menu. Click the added Policy Route 1
Issue 01 (2016-04-29)

991

Access Module
and configure the destination IP address, mask, and uplink bridging WAN 1 port in the
pane on the right side of the window. The destination IP address is the IP address of the
RADIUS server.
NOTE
In 802.1x authentication mode, a static route must be configured. The reason is as follows: After the
WAN port functioning as a GRE tunnel obtains an IP address, no default route is generated. In such a
case, the RADIUS client cannot communicate with the RADIUS server. In web portal authentication
mode, this step is not required.
2.
Click OK and then Finish.
Step 6 Issue a universal value-added service profile to the ONU.

1.
Choose View > Main Topology from the main menu to enter the main topology.
2.
In Main Topology, double-click the OLT connected to the ONU to enter the service
configuration window. In the navigation tree on the left side of the window, choose
GPON > GPON Management. Then, click the GPON ONU tab page on the right side
of the window.
3.
Right-click the ONU to which the profile is to be bound and choose Value-Added
ServiceBind VAS Profile from the shortcut menu.
4.
In the dialog box that is displayed, select the configured universal value-added service
profile and click OK.
Issue 01 (2016-04-29)

992

Access Module
----End
11.4.7 Configuring VLAN Tunnel-based Wi-Fi Sharing (U2000)

This section describes how to configure VLAN tunnel-based Wi-Fi sharing on a GPON ONU.
Data Plan
For data upstream transmission using VLAN tunnels, data can be authenticated in web portal
or 802.1x mode.
This section uses the 802.1x authentication as an example.
Issue 01 (2016-04-29)
Item
Data
Value-added ONU service

profile
Profile name: FTTO_value

993

Access Module
Item
Data
WAN port parameters
WAN 1:
l WAN port status: enabled

l Connection type: routing
l NAT (NATEnabled) status: enabled
l Service type: Internet access
WAN 2:
l WAN port status: enabled
l Connection type: bridging
l NAT (NATEnabled) status: disabled
l Service type: Internet access
RADIUS parameters
Authentication mode: 802.1x-EAP

IP address of the RADIUS server: 195.101.106.254
Key of the RADIUS server: SoftGRE1
RADIUS authentication port: 1812
RADIUS accounting: enabled
RADIUS accounting port: 1813
Policy routing parameters
Policy routing type: SourcePhyPort

Physical port name: SSID2
WAN port name: WAN2
Procedure
Step 1 Configure WAN ports.
1.
Log in to a U2000 client and choose Configuration > Access Profile Management
from the main menu.
2.
In the navigation tree on the left side of the window, choose PON Profile > ONT VAS
Profile. Then, click the General ONT VAS Profile tab page on the right side of the
window. Right-click the list in the lower part and choose Add(Service Configuration
Type) from the shortcut menu.
3.
In the dialog box that is displayed, configure the profile name. In the navigation tree on
the left side of the window, right-click WAN Device > WAN Device 1 > WAN
Connection and choose Add IP Connection from the shortcut menu. Add two WAN
ports and configure basic WAN parameters.
WAN port 1 is configured as a routing WAN port, which is used for transmitting data
upstream for private users in addition to being used by RADIUS clients. WAN port 2 is
configured as a bridging WAN port, which is used for transmitting data upstream for WiFi shared users.
Issue 01 (2016-04-29)

994

Access Module
NOTE
In web portal authentication mode, only one bridging WAN is required.
Step 2 Add two SSIDs. Configure SSID2 as the operator SSID. Set WLAN authentication
parameters for the operator.
1.
Issue 01 (2016-04-29)
Interface 1 > WLAN Configuration and choose Add from the shortcut menu. Then,
add two SSIDs.

995

Access Module
2.
Interface 1 > WLAN Configuration for ISP and choose Add from the shortcut menu.
Right-click the added WLAN Configuration for ISP 1 and choose SSID Index 2 from
the shortcut menu.
3.
Click Next. In the window that is displayed, click Add. Then, configure the
authentication mode and parameters for WLAN Configuration for ISP 1.
Issue 01 (2016-04-29)

996

Access Module
NOTE
In 802.1x authentication mode, RADIUS parameters listed in the red box must be configured. In web
portal authentication mode, RADIUS parameters do not need to be configured.

1.
In the navigation tree on the left side of the window, choose WAN Device > WAN
Device 1 > WAN Connection > WAN Connection 1 > WAN IP Interface > WAN IP
Interface 1. Then, in the pane on the right side of the window, configure WAN port
parameters.
2.
Use the same method to configure WAN port parameters for WAN IP Interface 2. The
only difference is as follows: WAN IP Interface 2 is a bridging WAN port, which does
not require the configuration of the NATEnabled parameter.
Issue 01 (2016-04-29)

997

Access Module
NOTE
In web portal authentication mode, bridging WAN port parameters are also required.
Step 4 Configure a policy route.

1.
In the navigation tree on the left side of the window, right-click Layer 3 Forwarding >
Policy route and choose Add from the shortcut menu. Click the added Policy Route 1
and bind SSID 2 to uplink bridging WAN port 2 in this route in the pane on the right side
of the window.
2.
Click OK and then Finish.
Step 5 Issue a universal value-added service profile to the ONU.

1.
Choose View > Main Topology from the main menu to enter the main topology.
2.
In Main Topology, double-click the OLT connected to the ONU to enter the service
configuration window. In the navigation tree on the left side of the window, choose
GPON > GPON Management. Then, click the GPON ONU tab page on the right side
of the window.
3.
Right-click the ONU to which the profile is to be bound and choose Value-Added
ServiceBind VAS Profile from the shortcut menu.
4.
In the dialog box that is displayed, select the configured universal value-added service
profile and click OK.
Issue 01 (2016-04-29)

998

Access Module
----End
11.4.8 Configuring the H.248-based Voice Service (on a Web Page)

The OLT is connected to the remote ONU through a GPON port to provide users with the IPbased high-quality and low-cost VoIP service.
Prerequisite
l
The interface data and POTS port data corresponding to the MG interface have been
configured on the MGC.
OLT.
Different voice services require different ONU software versions. Before the
configuration, ensure that the ONU software version supports H.248. For details, see
relevant ONU manuals.
Issue 01 (2016-04-29)

999

Access Module
Context
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 12
ONU service profile

Networking data

Procedure
l
Configure the OLT.

a.

Set the profile name to ftto_voip and do not limit the upstream and downstream
carried.
system. If the existing traffic profiles in the system do not meet the requirements,
huawei(config)#traffic table ip name ftto_voip cir off priority 5
priority-policy
local-setting
b.
and a service flow.
Scenario
VLAN Plan
VLAN Translation
Policy
Scenario 1
Single VLAN tag
ONU: Configure a VLAN

for all ONUs and add the
same C-VLAN tag to
packets. All ONUs are in
the same C-VLAN.
l S-VLAN ID: 300

l S-VLAN attribute:
common
l C-VLAN ID: 300
Issue 01 (2016-04-29)

OLT: The OLT

transparently transmits
VLAN tags (the C-VLAN is
the same as the planned SVLAN).
1000

Access Module
Scenario
VLAN Plan
VLAN Translation
Policy
Scenario 2
Single VLAN tag

same C-VLAN tag to
the same C-VLAN.
l S-VLAN ID: 300

l S-VLAN attribute:
common
l C-VLAN ID: 3001
OLT: The OLT switches

between C-VLAN tags and
S-VLAN tags (C-VLAN is
different from the planned
S-VLAN).
Scenario 1:
VLAN 300.
VLAN to 300, and use traffic profile ftto_voip.
service
table name
ftto_voip
service
table name
ftto_voip
gpon 0/1/0 ont 1 gemport 12 multiname ftto_voip outbound trafficgpon 0/1/0 ont 2 gemport 12 multiname ftto_voip outbound traffic-
Scenario 2:
VLAN 300.
Issue 01 (2016-04-29)

1001

Access Module
VLAN to 3001. Use traffic profile ftto_voip.
user-vlan 3001 tag-transform translate inbound traffic-table name
ftto_voip outboun
d traffic-table name ftto_voip
ftto_voip outboun
c.

Voice media streams for different users of the same S-VLAN fail to interchange
d.
Save the data.

huawei(config)#save
Configure the ONU on the Web page.

a.

i.

(default: 192.168.100.1).
ii.
b.
Issue 01 (2016-04-29)
Configure parameters of a voice WAN port.

i.
ii.
Service List: VoIP (For configuring the VoIP service, VoIP or a

combination containing VoIP needs to be selected.)
Mode: Route
VLAN ID: 300 (The VLAN ID of the ONU must be the same as the userside VLAN ID configured on the OLT.)
802.1p: 5
IP Acquisition Mode: DHCP

1002

Access Module

c.
Configure the parameters of the H.248-based voice interface.

i.
In the navigation tree, choose Voice > VoIP Basic Configuration.
ii.
In the right pane, configure the parameters of the H.248-based voice interface
as follows (other parameters use the default settings):
Set MGC Address below Primary Server to 200.200.200.200.
MID Format: DomainName
MG Domain: 6877687714852901
Signaling Port: 1_VOIP_R_VID_300
Region: China
NOTE
l The parameters of the H.248-based voice interface must be consistent with the
corresponding configuration on the media gateway controller (MGC).
l If dual-homing is configured, MGC Address below Secondary Server must be
configured.
l MID Format can be set to Domain Name, IP, or Device. If MID Format is set to
Domain Name or Device, the setting must be consistent with the corresponding
l Domain Name is ONU's domain name registered with the MGC. It is globally unique.
Domain Name in this example is ONU's SN.
streams are not isolated from signaling streams. If the upper-layer network requires
isolation of media streams from signaling streams, create different traffic streams for the
media streams and signaling streams on the OLT, create different WAN ports on the
ONU, and bind the created WAN ports to Media Port and Signaling Port.
l Profile Index can be set to Default, BT, FT, KPN, PCCW, ZTE, or BELL. Choose
the value based on the MGC type. Profile Index is set to Default (indicating
interconnection with Huawei MGC) in this example. If the settings do not meet
requirements, configure UserDefine. For details about how to configure this parameter,
contact Huawei technical support engineers.
l When the ONU is interconnected with a third-party softswitch, check RTP TID Prefix,
Start Number of RTP TID, and Width of RTP TID Number.
Issue 01 (2016-04-29)

1003

Access Module

d.
Configure parameters of the H.248-based voice users.

i.
ii.
In the right pane, configure the parameters of voice user 1 as follows:
Line Name: A0
Associated POTS: 1 (binding port TEL1 on the ONU)
Select Enable Line Name to enable the voice user configuration.

iv.
v.
In the right pane, click New to add voice user 2, and configure the parameters
of voice user 2 as follows:
Line Name: A1

NOTE
l The terminal IDs A0 and A1 must be consistent with the corresponding configuration on the
MGC.
l If Associated POTS is 1, port TEL1 on the ONU is bound. If Associated POTS is 2, port
TEL2 on the ONU is bound.
Issue 01 (2016-04-29)

1004

Access Module
e.
(Optional) Configure a route.

Perform this operation if the IP address of the ONU and the IP address of the voice
server are in different network segments.
i.
Choose Route > Default Route Configuration from the main menu.
ii.
Select Enable the default route and set WAN name to

1_VOIP_R_VID_300.
Figure 11-5 shows the settings.
Figure 11-5 Configuring a route

f.

g.
Restart the voice process.

In the navigation tree, choose Status > VoIP Information. In the right pane, click
Restart VoIP.
Issue 01 (2016-04-29)

1005

Access Module
h.

i.
Check the registration status of a voice user.

In the navigation tree, choose Status > VoIP Information. In the right pane, User
Status is Up.
----End

CLI)
The OLT manages ONUs and applies VoIP configurations to the ONU using the OMCI
Prerequisite
l
The interface data and POTS port data corresponding to the MG interface have been
configured on the MGC.
Issue 01 (2016-04-29)

1006

Access Module
OLT.
configuration, ensure that the ONU software version supports H.248. For details, see
relevant ONU manuals.
Context
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 12
ONU service profile

Networking data

Procedure
Set the profile name to ftto_voip and do not limit the upstream and downstream rates. Set the
priority to 5 and packets are scheduled according to the priority carried.
Run the display traffic table ip command to query existing traffic profiles in the system. If
Step 2 Configure the mapping between a GEM port and a VLAN. Create a service VLAN and a
service flow.
Scenario
VLAN Plan
Scenario 1
Single VLAN tag
ONU: Configure a VLAN for

all ONUs and add the same CVLAN tag to packets. All
ONUs are in the same CVLAN.
l S-VLAN ID: 300

l S-VLAN attribute: common
l C-VLAN ID: 300
Issue 01 (2016-04-29)

OLT: The OLT transparently

transmits VLAN tags (the CVLAN is the same as the
planned S-VLAN).
1007

Access Module
Scenario
VLAN Plan
Scenario 2
Single VLAN tag

l S-VLAN ID: 300

l C-VLAN ID: 3001

between C-VLAN tags and SVLAN tags (C-VLAN is
different from the planned SVLAN).
Scenario 1:
Configure the mapping between a GEM port and a VLAN. The service flow of user VLAN
300 is mapped to GEM port 12 in the ONU line profile.
Create a service VLAN and add an upstream port to it. Add upstream port 0/19/0 to VLAN
300.
Create service flows. Set the service VLAN to 300, GEM port ID to 12, and user VLAN to
300, and use traffic profile ftto_voip.
ftto_voip
ftto_voip

name ftto_voip outbound traffic-table name
Scenario 2:
300.
3001. Use traffic profile ftto_voip.
user-vlan 3001 tag-transform translate inbound traffic-table name ftto_voip
Issue 01 (2016-04-29)

1008

Access Module
outboun
outboun
Step 3 Configure ONU voice service profiles.

ONU voice service profiles include the interface common profile, MGC interface profile, and
POTS port profile.
l
Interface common profile: saves common attributes of an ONU voice interface, including
the fax mode, fax/modem negotiation mode, and priority of the coding and decoding
mode.
MGC interface profile: saves the IP address or domain name of the MGC, protocol port
ID of the MGC transport layer to which the MG interface belongs, and DSCP priority of
media packets.
POTS port profile: saves physical attributes of a POTS port on an ONU, including the
impedance, transmitting gain, receiving gain, and signaling type of the POTS port.
1.
Configure an interface common profile.

Run the display ont-mg-attribute-profile command to query the existing interface
common profile in the system. If the existing interface common profile in the system
does not meet the requirements, run the ont-mg-attribute-profile add command to add
an interface common profile.
In this example, the default interface common profile, namely interface common profile
1 is used.
2.
Configure an MGC interface profile.

Run the display ont-mgc-profile command to query the existing MGC interface profile
in the system. If the existing MGC interface profile in the system does not meet the
requirements, run the ont-mgc-profile add command to add an MGC interface profile.
Create MGC interface profile 2, set the IP address of the MGC to 200.200.200.200, and
use default values for other parameters.
huawei(config)#ont-mgc-profile add profile-id 2 primary-mgc 200.200.200.200
3.

Run the display ont-pots-profile command to query the existing POTS port profile in
the system. If the existing POTS port profile in the system does not meet the
requirements, run the ont-pots-profile add command to add a POTS port profile.
In this example, the default POTS port profile, namely POTS port profile 1 is used.
Step 4 Configure the IP addresses of ONU SIP users.

For ONU 1 and ONU 2, configure the IP address obtaining mode to the static mode, set the IP
addresses to 10.10.10.10/24 and 10.10.10.20/24, set the management VLAN to VLAN 20,
Step 5 Configure H.248 POTS users.

1.
Add an H.248 interface and apply an MGC interface profile to the interface.
For ONU 1 and ONU 2, set the MG ID to 1, apply MGC interface profile 2 to ONU 1
and ONU 2, and use default values for other parameters.
Issue 01 (2016-04-29)

1009

Access Module
If parameters of an MGC interface profile are changed, the MGC interface profile must
be reapplied to the ONU so that the changed parameters can take effect.
2.
Add POTS users.

For ONU 1 and ONU 2, create a POTS user, set the MG ID to 1 (identical to the MG ID
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
: 1
Terminal ID
: A0
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
: 1
Terminal ID
: A1
Step 6 Apply ONU voice service profiles

After ONU voice service profiles are applied, if parameters in those profiles are changed,
those profiles must be reapplied so that the changed parameters can take effect.
1.
Apply an interface common profile.

Run the if-h248 attribute command to apply an interface common profile to an H.248
interface or configure the interface customized parameters, or run the ont-if-h248 batapply command to bulk apply the interface common profiles to H.248 interfaces. If you
use these two commands to apply the interface common profiles or configure the
interface customized parameters repeatedly, the last configurations take effect.
1 is used.
2.

Run the pstnport electric command to apply a POTS port profile to an H.248 interface
or configure the interface customized parameters, or run the ont-pstnport electric batapply command to bulk apply the POTS port profiles to H.248 interfaces. If you use
these two commands to apply the POTS port profiles or configure the interface
customized parameters repeatedly, the last configurations take effect.
Step 7 (Optional) Configure the H.248 user codec.

Issue 01 (2016-04-29)

1010

Access Module

huawei(config)#save
----End
11.4.10 Configuring the SIP-based Voice Service (on a Web Page)

The OLT is connected to the remote ONU through a GPON port to provide users with the IPbased high-quality and low-cost VoIP service.
Prerequisite
l
The SIP interface data and POTS port data corresponding to the MG interface have been
configured on the SIP server.
The ONU has been added to the OLT. For details, see 9.3.3 Adding an ONT to an OLT.
configuration, ensure that the current ONU software version supports SIP. For details,
see relevant ONU manuals.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 12
ONU service profile

Voice parameter

Procedure
l
Configure the OLT.

a.

Set the profile name to ftto_voip and do not limit the upstream and downstream
carried.
Issue 01 (2016-04-29)

1011

Access Module
system. If the existing traffic profiles in the system do not meet the requirements,
huawei(config)#traffic table ip name ftto_voip cir off priority 5
priority-policy
local-setting
b.
and a service flow.
Scenario
VLAN Plan
VLAN Translation
Policy
Scenario 1
Single VLAN tag

same C-VLAN tag to
the same C-VLAN.
l S-VLAN ID: 300

l S-VLAN attribute:
common
l C-VLAN ID: 300
Scenario 2
Single VLAN tag

l S-VLAN ID: 300
l S-VLAN attribute:
common
l C-VLAN ID: 3001
OLT: The OLT

VLAN tags (the C-VLAN is
the same as the planned SVLAN).
same C-VLAN tag to
the same C-VLAN.
between C-VLAN tags and
S-VLAN tags (C-VLAN is
S-VLAN).
Scenario 1:
VLAN 300.
VLAN to 300, and use traffic profile ftto_voip.
Issue 01 (2016-04-29)

1012

Access Module
service
table name
ftto_voip
service
table name
ftto_voip

gpon 0/1/0 ont 1 gemport 12 multiname ftto_voip outbound trafficgpon 0/1/0 ont 2 gemport 12 multiname ftto_voip outbound traffic-
Scenario 2:
VLAN 300.
VLAN to 3001. Use traffic profile ftto_voip.
ftto_voip outboun
ftto_voip outboun
c.

Voice media streams for different users of the same S-VLAN fail to interchange
d.
Save the data.

huawei(config)#save
Configure the ONU on the Web page.

a.

i.

(default: 192.168.100.1).
ii.
Issue 01 (2016-04-29)

1013

Access Module
b.

i.
ii.

Mode: Route
802.1p: 5

c.
Configure parameters of the SIP-based voice interface.

i.
ii.
In the right pane, configure parameters of the SIP-based voice interface as

follows (other parameters use the default settings):
Set Proxy Server Address below Primary Server to 200.200.200.200.
Home Domain: softx3000.huawei.com
Region: China
NOTE
l The parameters of the SIP-based voice interface must be consistent with the
corresponding configuration on the softswitch.
l If dual-homing is configured, Proxy Server Address below Secondary Server must be
configured.
l If Signaling Port is empty, the parameter value is the same as Media Port. If the upperlayer network requires isolation of media streams from signaling streams, create
different traffic streams for the media streams and signaling streams on the OLT, create
different WAN ports on the ONU, and bind the created WAN ports to Media Port and
Signaling Port. When the packet is forwarded from two WAN ports, the configured
VLAN is carried by default.
Issue 01 (2016-04-29)

1014

Access Module

d.
Configure parameters of the SIP-based voice users.

i.
ii.
In the right pane, configure parameters of voice user 1 as follows:
Register User Name: 80001234
Auth User Name: 80001234@softx3000.huawei.com
Password: iadtest1
Select Enable to enable the voice user configuration.

iv.
v.
vi. Password: iadtest2

vii. Associated POTS: 2 (binding port TEL2 on the ONU)
viii. Select Enable User to enable the voice user configuration.
ix. Click Apply to apply the configuration.
NOTE
l The parameters of the SIP-based voice user must be consistent with the corresponding
Issue 01 (2016-04-29)

1015

Access Module
e.

i.
ii.

1_VOIP_R_VID_300.

f.

g.

Restart VoIP.
Issue 01 (2016-04-29)

1016

Access Module
h.

i.

Status is Up.
----End
11.4.11 Configuring the SIP-based Voice Service (Through the

CLI)
The OLT manages ONUs and applies VoIP configurations to the ONU using the OMCI
Prerequisite
l
The SIP interface data and POTS port data corresponding to the MG interface have been
configured on the SIP server.
The ONU has been added to the OLT. For details, see 9.3.3 Adding an ONT to an OLT.
Issue 01 (2016-04-29)

1017

Access Module
configuration, ensure that the current ONU software version supports SIP. For details,
see relevant ONU manuals.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 12
ONU service profile

Voice parameter

Procedure
Set the profile name to ftto_voip and do not limit the upstream and downstream rates. Set the
priority to 5 and packets are scheduled according to the priority carried.
Run the display traffic table ip command to query existing traffic profiles in the system. If
Step 2 Configure the mapping between a GEM port and a VLAN. Create a service VLAN and a
service flow.
Scenario
VLAN Plan
Scenario 1
Single VLAN tag

l S-VLAN ID: 300

l C-VLAN ID: 300
Issue 01 (2016-04-29)

OLT: The OLT transparently

transmits VLAN tags (the CVLAN is the same as the
planned S-VLAN).
1018

Access Module
Scenario
VLAN Plan
Scenario 2
Single VLAN tag

l S-VLAN ID: 300

l C-VLAN ID: 3001

between C-VLAN tags and SVLAN tags (C-VLAN is
different from the planned SVLAN).
Scenario 1:
300.
300, and use traffic profile ftto_voip.
ftto_voip
ftto_voip

Scenario 2:
300.
3001. Use traffic profile ftto_voip.
Issue 01 (2016-04-29)

1019

Access Module
outboun
outboun
Step 3 Configure ONU voice service profiles.

ONU voice service profiles include the interface common profile, SIP agent profile, SIP
service data profile, POTS port profile, and digitmap profile.
l
Interface common profile: saves common attributes of an ONU voice interface, including
mode.
SIP agent profile: saves the SIP agent information about an ONU, including the IP
signaling packets.
SIP service data profile: saves the data information about ONU voice services, including
the rights of the call waiting service, three-party service, call forwarding service, and call
holding service.
POTS port profile: saves physical attributes of a POTS port on an ONU, including the
Digitmap profile: saves the digitmap information about an ONU, including the timeout
1.

1 is used.
2.

Run the display ont-sipagent-profile command to query the existing SIP agent profile
in the system. If the existing SIP agent profile in the system does not meet the
requirements, run the ont-sipagent-profile add command to add an SIP agent profile.
Create SIP agent profile 2, set the IP address of the SIP server to 200.200.200.200, and
200.200.200.200
3.
Configure an SIP service data profile.

Run the display ont-siprightflag-profile command to query the existing SIP agent
profile in the system. If the existing SIP service data profile in the system does not meet
the requirements, run the ont-siprightflag-profile add command to add an SIP service
data profile.
In this example, the default SIP service data profile, namely SIP service data profile 1 is
used.
4.

Issue 01 (2016-04-29)

1020

Access Module
5.

Run the display ont-digitmap-profile command to query the existing digitmap profile
in the system. If the existing digitmap profile in the system does not meet the
requirements, run the ont-digitmap-profile add command to add a digitmap profile.
In this example, the default digitmap profile, namely digitmap profile 1 is used.
Step 4 Configure an IP address for an ONU SIP user.

For ONU 1 and ONU 2, configure the IP address obtaining mode to the DHCP mode, set the
Step 5 Configure SIP POTS users.

1.
For ONU 1 and ONU 2, set the MG ID to 1, apply SIP agent profile 2 to ONU 1 and
ONU 2, and use default values for other parameters.
If parameters in an SIP agent profile are changed, the SIP agent profile must be reapplied
to the ONU so that the changed parameters can take effect.
2.
Add POTS users.

For ONU 1 and ONU 2, set the MG ID to 1 (identical to the MG ID of the added SIP
other parameters.
telno 77730010
telno 77730020
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
Telephone NO.
User name
Password
: 1
: 77730010
: huawei1
: user1

-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
Telephone NO.
User name
Password
Issue 01 (2016-04-29)
: 1
: 77730020
: huawei2
: user2

1021

Access Module
Step 6 Apply and bind an ONU voice service profile to an SIP interface
Currently, the interface common profile, SIP agent profile, SIP service data profile, and POTS
port profile can be applied to an SIP interface, and the digitmap profile can be bound to an
SIP interface.
The method for applying an SIP agent profile is introduced in Step 5.1. The following will
introduce the methods for applying an interface common profile, an SIP service data profile,
and a POTS port profile, and the method for binding a digitmap to an SIP interface.
1.

Run the if-sip attribute command to apply an interface common profile to an SIP
interface or configure the interface customized parameters, or run the ont-if-sip batapply from command to bulk apply the interface common profiles to SIP interfaces. If
you use these two commands to apply the interface common profiles or configure the
1 is used.
2.
Apply an SIP service data profile.

Run the sippstnuser rightflag command to apply an SIP service data profile to an SIP
interface or configure the interface customized parameters, or run the ont-sippstnuser
bat-apply from command to bulk apply the SIP service data profiles to SIP interfaces. If
you use these two commands to apply the SIP service data profiles or configure the
In this example, the default SIP service data profile, namely SIP service data profile 1 is
used.
3.

Run the pstnport electric command to apply a POTS port profile to an SIP interface or
configure the interface customized parameters, or run the ont-pstnport electric batapply command to bulk apply the POTS port profiles to SIP interfaces. If you use these
two commands to apply the POTS port profiles or configure the interface customized
4.

Run the sippstnuser digitmap command to bind a digitmap profile to an SIP interface,
or run the ont-sippstnuser bat-bind from command to bulk apply the digitmap profiles
to SIP interfaces. If you use these two commands to bind the SIP service data profiles to
SIP ports repeatedly, the last configurations take effect.
In this example, the default digitmap profile, namely digitmap profile 1 is used.
Step 7 (Optional) Configure the SIP user codec.

Run the sippstnuser codec command to configure the SIP user codec. The SIP user codec
Issue 01 (2016-04-29)

1022

Access Module
huawei(config)#save
----End

The OLT is connected to the remote gateway ONU through a GPON port to provide users
with the bridge WAN multicast service.
Prerequisites
l
OLT.
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 13
ONU service profile

Traffic profile
ID: 8
802.1p priority: 4

Procedure
1.

NOTE
traffic profile.
Issue 01 (2016-04-29)

1023

Access Module

local-setting
2.
Configure the VLAN and service flows.

VLAN Plan
Single VLAN tag
ONU: duplicates multicast packets based

on user ports and MVLANs are stripped
off downstream.
S-VLAN ID: 1000

MVLAN ID: 1000
VLAN type: smart
OLT: duplicates multicast packets based

on PON ports with MVLAN unchanged.
Configure the mapping between a GEM port and an Ethernet port on an ONU. If the
ONU is connected to the STB through Ethernet port 2, map the service flow of Ethernet
port 2 to GEM port 13 in the ONU line profile.
Configure the multicast forwarding mode is untagged.

VLAN 1000.
3.

4.

Issue 01 (2016-04-29)

1024

Access Module
NOTE
address range of dynamic programs, perform this operation. For example, set the address
range of dynamic programs to 224.1.1.1-224.1.1.100.
5.
Set the IGMP mode.

6.
Configure the IGMP upstream port.

Set the IGMP upstream port ID to 0/19/0 and working mode to default. Protocol packets
are transmitted to all the IGMP upstream ports in the multicast VLAN.
7.
(Optional) Set multicast global parameters.

In this example, the default settings are used for all the multicast global parameters.
8.

9.
Save the data.

huawei(config)#save

----End

The OLT is connected to the remote gateway ONU through a GPON port to provide users
Prerequisites
l
The OLT has been connected to the BRAS and the program source.
OLT.
Issue 01 (2016-04-29)

1025

Access Module
Data Plan
Item
Data
ONU line profile

T-CONT ID: 4
GEM port ID: 13
ONU service profile

Traffic profile
ID: 8
802.1p priority: 4
Procedure
1.

NOTE
traffic profile.
local-setting
2.
Configure the VLAN and service flows.

VLAN Plan
Single VLAN tag
The ONU adds CVALN tags to packets:

untagged <-> C-VLAN tag.
S-VLAN ID: 1100

VLAN type: smart
The OLT implements VLAN translation:

C-VLAN tag <-> S-VLAN tag.
C-VLAN: 2001
Issue 01 (2016-04-29)

1026

Access Module

VLAN 1100.
Create service flows. Set the S-VLAN to 1100, GEM port ID to 13, and C-VLAN to
2001, and use traffic profile 8. Set the VLAN translation policy to Translate. The CVLAN 2001 of the ONU is translated to S-VLAN 1100.
multi-service user-vlan 2001 tag-transform translate rx-cttr 8 tx-cttr 8
multi-service user-vlan 2001 tag-transform translate rx-cttr 8 tx-cttr 8
3.
Save the data.

huawei(config)#save

----End
11.4.14 Configuring L2TP Services

An enterprise employee in a business trip or an enterprise branch visits HQ intranet resources
using Layer 2 Tunneling Protocol (L2TP) tunnels.
Prerequisites
l
The ONU is added to the OLT.
The OLT assigns the ONU WAN the VLAN.
Context
This function is supported by only the MA5675, MA5675M, and MA5676. An ONU
functions as a L2TP client but does not a L2TP server.
Procedure
Step 1 Log in to the web page.
1.
Configure the IP address of the PC network interface card (NIC) to be in the same
network segment as the local maintenance IP address of the ONU (default:
192.168.100.1).
2.
Open the browser, and enter the local maintenance IP address of the ONT.
3.
In the login window, enter the user name (default: telecomadmin) and password (default:
admintelecom) of the administrator. After the password authentication, the web
configuration window is displayed.

1.
Select WAN > WAN Configuration from the main menu.
2.
In the right pane, click New. In the dialog box that is displayed, set WAN port
parameters in sequence as follows:
Issue 01 (2016-04-29)

1027

Access Module
Enable WAN: enable
Encapsulation Mode: IPoE
WAN mode: Route WAN
Service type: INTERNET
VLAN ID: 199 (The VLAN ID of the ONU must be the same as the user-side
VLAN ID configured on the OLT.)
802.1p: 6
IP acquisition Mode: Static
NAT: Enable (NAT must be enabled to configure the Internet access service.)
IP Address: 30.10.20.26
NOTE
You are advised to separately create a WAN port for L2TP services (do not share the same WAN
port with other services). Configuring the priority of a WAN port to improve the priority of L2TP
services so as to ensure point-to-point (P2P) QoS scheduling.
Binding Options cannot select LAN-related options.
Step 3 Enable L2TP LAC.

1.
Choose Network Application > L2TP LAC Configurationfrom the main menu.
2.
In the right pane, click New. In the dialog box that is displayed, set L2TP LAC
Issue 01 (2016-04-29)
Enable LAC: enable
LNS Address: 198.51.100.254
LNS Port: 1701
Interface: 1_INTERNET_R_VID_199 (use the WAN port for L2TP services)

1028

Access Module
Step 4 Configure an L2TP tunnel route.

1.
ChooseNetwork Application > L2TP Tunnel Route Configuration from the main
menu.
2.
In the right pane, click New. In the dialog box that is displayed, set L2TP tunnel route
Destination IP Address: 192.168.98.12
Destination Subnet Mask: 255.255.255.255
Step 5 Confirm the L2TP tunnel status.

Choose Status > L2TP LAC Tunnel Status from the main menu. After an L2TP tunnel is set
up, you can query its status, for example, whether packets are received and transmitted
normally.
----End
Issue 01 (2016-04-29)

1029

Access Module

Security Policy
Service reliability is improved by configuring uplink aggregation and priority scheduling
policy for queues in global configuration mode, and service security is improved by
configuring security policy in global configuration mode.
Context
In link aggregation, multiple uplink Ethernet ports are aggregated into a group to increase
bandwidth and reliability of uplinks of the OLT. You are advised to configure link
aggregation.
packets based on queue priorities. You are advised to configure congestion control.
Security policy involves system security, user security, and service security, ensuring service
security from different aspects.
NOTE
introduced it.
Procedure
l

On the OLT side, configure upstream ports 0/19/0 and 0/19/1 as an aggregation group.
Each member port in the aggregation group is allocated packets based on the source
MAC address. The working mode is LACP static aggregation.
Configure queue scheduling(On the OLT side).

According to "11.2.2 Principle of QoS Planning", all packets are scheduled in strict

i.
ii.


Issue 01 (2016-04-29)

1030

Access Module

i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.

i.

level.
The VLAN level:

1)
Issue 01 (2016-04-29)


1031

Access Module
ii.
2)

3)

effect.
4)
5)

level.

i.
default.
global level.
The VLAN level:
ii.
1)

2)
3)

effect.
4)
5)

----End

In the FTTO scenario, ONUs are installed at users' houses or in business buildings which are
far away from the central equipment room. ONUs provide remote service verification
Issue 01 (2016-04-29)

1032

Access Module
methods including PPPoE dialup emulation, call emulation, and multicast emulation to
facilitate configuration and commissioning engineers to verify services remotely after service
configuration.
Prerequisites
ONUs and upper-layer devices have been connected properly. The BRAS and MGC/IMS
have been configured.
Background
Remote
Service
Verificati
on
Method
Function
Description
PPPoE
dialup
emulation
An ONU simulates a PPPoE user

between the ONU and BRAS.

a QinQ VLAN.
l An ONU supports a maximum of a
Call
Emulation
Multicast
emulation
Issue 01 (2016-04-29)
An ONU simulates a voice user

l An ONU can simulate a caller or

personnel locate.

stream to an ONU. You can
multicast program.

l An ONU supports only once call

emulation.

1033

Access Module
Data plan
Item
Data
Remarks
PPPoE
dialup
emulation
parameters

Call
emulation
parameters
ONU POTS ID: 1

parameter values.
Multicast
emulation
parameters
Password: test
MVLAN: 1000
program: 224.1.1.10
Procedure
l

a.
The service is functional if the test result is success. The following test uses GPON
as an example:
{ portid<0,7> }:0
{ ontid<0,127> }:1
Command:
---------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
ONT ETH Port ID
: 4
ONT Vlan ID
: 100
Vlan Priority
: Emluator result
: Success
Session ID
: 18814
User IP
: 172.16.100.109
Issue 01 (2016-04-29)

1034

Access Module
Gateway IP
: 172.16.100.1
----------------------------------

a.
b.

n
If a native VLAN is configured for the Ethernet port on the ONU, run the
status.
i.
ii.
ONU is activated, whether the PC is connected to the right port on the
ONU, and whether the PC is working properly.
Run the display ont-learned-mac command to check whether the ONU

If not, check whether the ONU properly connects to the PC or home gateway
(HGW).

a.
huawei(config)#test
28777192
Command:
b.
The service is functional if the test result is success.
---------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 0
ONT-POTSID
: 1
Test type
Detected number
: 28777192
Reported number
: 28777192
Current status
: test end
Test Result
: success
----------------------------------------------------------------

a.

n
Issue 01 (2016-04-29)
1035

Access Module
n
b.
status.
c.
If the downstream port does not learn a MAC address, check whether the ONU
the MAC address of the ONU and log in to the service router (SR) to check

n
You can run the display ont port state command in the GPON mode on the
OLT to query the call connection status on the POTS port. If Call State is
RegisterFail or Connecting for a long time, check whether the voice
configuration on the MGC/SIP server is consistent with that on the ONU.
If the ONU uses the H.248 protocol, you can run the display ont mg status
command in the GPON mode on the OLT to query the registration status of the
MG interface that connects to the ONU. If MG Status is UnRegistered or
Registering for a long time, check whether the voice configuration on the
MGC/SIP server is consistent with that on the ONU.
You can query the registration status of the voice service on the ONU web
on the MGC/SIP server is consistent with that on the ONU.

a.
program.
huawei(config)#btv
1000
NOTE
b.
The multicast user is normal if the queried result is online.
User
: 0/1/0/1
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 1
Video flow ID
: 1
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Current version
: IGMP v3
Issue 01 (2016-04-29)

1036

Access Module
Available programs
Global leave
User max bandwidth
Used bandwidth
to max bandwidth(%)
Total video bandwidth
Mcast video bandwidth
Active program list

:
:
:
:
8
disable
no-limit
0
: : : -
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start time
-------------------------------------------------------------------------PROGRAM-5
1000 224.1.1.10
watching
2011-10-29
16:33:41+08:00
-------------------------------------------------------------------------Total: 1
c.
The multicast program can be ordered if the queried result is a non-empty value.
224.1.1.10
Command:
----End
11.5 Layer 2 Interoperation Service Between Enterprise

Branches
11.5.1 Service Requirement and Application Scenario

Service Requirement
An enterprise that has multiple branches requires intercommunication between different
branches or between its headquarter and branches. Virtual private network (VPN) can achieve
secure interconnection but requires additional devices and complex management. It requires
high costs even if a leased VPN is used. In addition, the bandwidth provided by a VPN is
limited due to restricted VPN access modes and the bandwidth control is inflexible.
To address the preceding problems, the Layer 2 interoperation technology using fiber access
is put forward and becomes the main trend.
Issue 01 (2016-04-29)

1037

Access Module
As shown in Figure 11-7, ONUs are deployed in branches of an enterprise. The ONUs access
and converge Ethernet services of the enterprise through GE/FE ports and transmit the
services to the OLT. The OLT implements Layer 2 interoperation between different branches
of the enterprise.
ONUs supporting this scenario: MA5612, MA5628, MA5616, MA5694, MA5698
Figure 11-7 Network diagram for Layer 2 interoperation between enterprise branches
IP/MPLS
ONU 1
GE/FE
Headquarter
ONU 2
GE/FE
GE/FE
Branch A
Branch B
Service flows between

enterprise branches
Note: Because the bandwidth of upstream and downstream PON ports is fixed, the number of
enterprises connected to an OLT is limited when the enterprises require symmetric bandwidth.
When an enterprise requires 100 Mbit/s symmetric bandwidth and uses an 8-channel PON
board:
1.
The number of enterprises or branches connected to a PON port should not exceed eight.
2.
The number of enterprises or branches connected to a PON board should not exceed 64.
3.
The number of enterprises connected to an OLT cannot exceed 200 (20G/100M) if the
upstream bandwidth is 2 x 10GE. (The number of enterprises connected to an OLT is
mainly restricted by the upstream bandwidth.)
Issue 01 (2016-04-29)

1038

Access Module

Figure 11-8 shows the configuration procedure for Layer 2 interoperation between branches
of an enterprise.
Figure 11-8 Configuration procedure for Layer 2 interoperation between branches of an
enterprise
Issue 01 (2016-04-29)
Item
Procedure
Remarks
OLT
This topic describes how to add ONUs to

the OLT. ONUs can be configured only
after they are added to the OLT
successfully.
OLT
Configuring Layer 2
Interoperation Service Ports on
OLT
None
OLT
Configuring Congestion Control

and Security Policies
This topic describes how to configure

global priority-based scheduling policies
for upstream queues to ensure service
reliability and configure global security
policies to ensure service security.

1039

Access Module
Item
Procedure
Remarks
OLT
Configuring E2E Reliability
The upstream and downstream networking

protection ensures the E2E reliability. Link
aggregation and protection groups can be
configured for upstream networking
protection. Type x protection for PON
ports can be configured for downstream
networking protection.
OLT
Verifying Services
None
11.5.3 Adding ONUs to OLT

This topic describes how to add ONUs to the OLT. ONUs can be configured only after they
are added to the OLT successfully.
Context
l
When adding ONUs, you need to bind related profiles to the ONUs, including the DBA
profile, line profile, service profile, and alarm profile. For the functions of each profile
and how to configure profiles, see Table 11-25.
Table 11-25 ONU profile
Issue 01 (2016-04-29)
Profile
Type
Function
Command
DBA
profile
Describes GPON traffic

parameters. A T-CONT is
bound to a DBA profile for
dynamic bandwidth allocation,
improving upstream bandwidth
utilization.
Query: display dba-profile
Line
profile
Describes the binding

relationship between T-CONTs
and DBA profiles, QoS mode
of service flows, and mapping
between GEM ports and
services on ONUs.
Query: display ont-lineprofile
Service
profile
Describes the parameters of the

ONT managed by the OLT in
OMCI mode.
Query: display ont-srvprofile
Alarm
profile
Provides a series of alarm

threshold parameters that are
used for performance
measurement and monitoring
of activated ONU lines.
Query: display gpon alarm-profile
Add: dba-profile add
Add: ont-lineprofile add
Add: ont-srvprofile add
Add: gpon alarm-profile add

1040

Access Module

Mode
Usage Scenario
Command
Offline
addition
The password or serial number

of an ONU has been obtained.
Run the ont add command to add the

ONU.
Online
confirmat
ion
The password and serial

number of an ONU are
unknown.
Run the port ont-auto-find command

in the GPON mode to enable the
automatic discovery function for the
GPON port and run the ont confirm
command to add the ONU.
Data Planning
Configuration
Item
Data
DBA profile
Profile ID: 20
Profile type: Type 3
Line profile
Profile ID: 10
T-CONT ID: 4
GEM port ID for Layer 2 interoperation service: 12
Service profile
Profile ID: 11
Ethernet and POTS port capability set: adaptive
ID of the ONU Ethernet VLAN: 300
NOTE
Ensure that the capability set of the service profile is greater than or equal to that
of the device. Otherwise, some ports fail to be configured.
Networking data
For example, add two ONUs (ONU 1 and ONU 2) for carrying services
of different branches.
l ONU 1 is connected to PON port 0/3/1.
Procedure
1.

huawei(config)#dba-profile add profile-id 20 type3 assure 102400 max 122880
2.
Issue 01 (2016-04-29)

1041

Access Module
a.
Create GPON ONU line profile 10.

NOTE
Create a line profile according to the data plan. The ID of the line profile to be created cannot
conflict with existing profile IDs in the system. In this example, the ID of the line profile is 10.
b.
In the line profile configuration mode, bind T-CONT 4 to DBA profile 20.
c.
In the line profile configuration mode, bind GEM ports to T-CONTs.

Add GEM port 12 for carrying the Layer 2 interoperation service flow.
GEM port 11 is bound to T-CONT 4. During configuration, set QoS policies for
each service flow. For details on QoS data planning, see 12.3.3 Principle of QoS
Data Plan.
huawei(config-gpon-lineprofile-10)#gem add 12 eth tcont 4 cascade on
d.
Configure mapping between GEM ports and ONU-side services.

Set the mapping mode to VLAN mode (the default mode). Map Layer 2
interoperation service flow (C-VLAN 300) to GEM port 12.
e.
After the configuration is complete, run the commit command to make the
3.

a.
Create a GPON ONU service profile with ID 11.

huawei(config)#ont-srvprofile gpon profile-id 11
NOTE
Ensure that the ID of the service profile to be created does not exist in the system. Create a
service profile according to the planned data. Service profile 11 is used as an example.
b.
Configure the Ethernet and POTS port capability set to adaptive. Then, the system
adapts the capability to the actual capability of the online ONU.
c.
Add Ethernet port 1 to VLAN 300.

d.
Run the commit command to make the configurations take effect.

4.
Set the ID of the native VLAN containing Ethernet port 1 to 300.

5.
(Optional) Configure an alarm profile.
The default GPON alarm profile ID is 1. The value of each alarm threshold is 0
which indicates that alarms are not reported.
In this example, the default alarm profile is used and no configuration is required.
Step 2 Add ONUs to the OLT.

Issue 01 (2016-04-29)

1042

Access Module
1.
Add ONU 1 and ONU2 in offline mode.

Connect ONU 1 and ONU 2 to GPON ports 0/3/1 and 0/4/1 respectively through an
optical splitter. The serial numbers of the two ONUs are 3230313163902641 and
32303131B39FD642 respectively, and the management mode is OMCI. Both the ONUs
are bound to line profile 10 and service profile 11.
huawei(config-if-gpon-0/3)#ont add 1 ontid 1
omci ont-lineprofile-id 10 ont-srvprofile-id
huawei(config-if-gpon-0/4)#ont add 1 ontid 2
omci ont-lineprofile-id 10 ont-srvprofile-id
2.
sn-auth 3230313163902641
11
sn-auth 32303131B39FD642
11
(Optional) Bind an alarm profile.

By default, an ONU will be automatically bound to alarm profile 1 (default profile). You
need to manually bind an alarm profile to an ONU only when the default alarm profile
does not meet requirements.
In this example, the default alarm profile is used. Therefore, you do not need to manually
bind an alarm profile.
Step 3 Confirm the ONU status.

After adding an ONU, run the display ont info command to query the current status of the
ONU. Ensure that Control flag is active, Run State is online, and Config state is normal.
The following uses ONU 1 as an example to describe how to confirm ONU status.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
//Indicates that the ONU is in normal
state.
...//Other command output is omitted.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

1043

Access Module
11.5.4 Configuring Layer 2 Interoperation Service Ports on OLT

This topic describes how to configure service ports on the OLT for Layer 2 interoperation so
that data packets sent from different ONUs can be forwarded based on the same VLAN at
Layer 2.
Prerequisites
1.
The main control board on the device is an SCUN board.
2.
The ARP proxy function is disabled using the arp proxy disable command. (The Layer
2 interoperation function and ARP proxy function are mutually exclusive.)
Data Plan
Configuratio
n Item
Data
Layer 2
interoperation
SVLAN
OLT VLAN ID (the OLT transparently transmits VLANs of ONU): 300

VLAN forwarding mode: vlan-mac (default)
ONU VLAN ID: 300
Traffic profile
Profile ID: 10
Priority source: user-cos
Default priority: 4
NOTE
For detailed data planning, see 12.3.2 Principle of VLAN Data Plan.
Procedure
Step 1 Configure an SVLAN and add an upstream port to it.
Set the SVLAN ID of the Layer 2 interoperation service to 300, VLAN type to smart VLAN,
and add upstream port 0/19/0 to the VLAN.

Add a new traffic profile 10 and set the assured rate to 100 Mbit/s. Packets transmitted
upstream use the priority (4 by default) copied from the user side. Packets transmitted
downstream use the priority carried by themselves.
Issue 01 (2016-04-29)

1044

Access Module
huawei(config)#traffic table ip index 10 cir 102400 priority user-cos 4 prioritypolicy tag-in-package
Step 3 Configure a service port to receive and transparently transmit the Layer 2 interoperation
service that is sent from ONU 1 and ONU 2.
Set the service attributes based on the data plan:
l
For the OLT, set the SVLAN ID to 300, CVLAN ID to 300 which is the same as the
upstream VLAN ID of the ONU, and GEM port ID to 12 for the Layer 2 interoperation
service.
For ONUs, set the upstream VLAN ID to 300.

Step 4 Configure attributes for protocol transparent transmission.

Create a VLAN service profile, enable the VLAN Layer 2 interoperation function, and
configure attributes for protocol transparent transmission. Then, bind the profile to VLAN
300. For details on data planning for protocol transparent transmission, see 12.3.4 Principle
of Protocol Transparent Transmission Data Plan.
huawei(config)#vlan service-profile profile-id 1
huawei(config-vlan-srvprof-1)#user-bridging enable
//Mandatory
huawei(config-vlan-srvprof-1)#bpdu tunnel enable
huawei(config-vlan-srvprof-1)#ospf tunnel enable
huawei(config-vlan-srvprof-1)#rip tunnel enable
huawei(config-vlan-srvprof-1)#vtp-cdp tunnel enable
huawei(config-vlan-srvprof-1)#commit
huawei(config-vlan-srvprof-1)#quit
huawei(config)#multicast-unknown policy service-port 301 transparent
huawei(config)#vlan bind service-profile 300 profile-id 1
----End
11.5.5 Configuring Congestion Control and Security Policies

This topic describes how to configure global priority-based scheduling policies for upstream
queues to ensure service reliability and configure global security policies to ensure service
security.
Context
Congestion control uses queue scheduling technology to map packets sent from the same port
into multiple queues and process packets in each queue based on priority. Congestion control
is recommended.
Security policies cover system security, user security, and service security, which ensure
normal running of services.
NOTE
introduced it.
Issue 01 (2016-04-29)

1045

Access Module
Procedure
l

Based on 12.3.3 Principle of QoS Data Plan, all packets use strict priorities for queue
scheduling and are mapped to queues based on priorities.
huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6
cos7 7 //System default
Configure system security policies.

i.
ii.


Configure user security policies.


i.

globally enable IP address anti-spoofing.
ii.
Enable IP address anti-spoofing at VLAN level, perform the following

operations to enable IP address anti-spoofing in service profile mode:
1)
Run the vlan service-profile command to create a VLAN service profile.
2)
Run the security anti-ipspoofing enable command to enable IP address

anti-spoofing at VLAN level.
3)
4)
5)
The service port level: In global config mode, run the security anti-ipspoofing
service-port serviceport-id enable command to enable IP address anti-spoofing at
the service port level.
----End

This topic describes how to verify the Layer 2 interoperation service by checking the service
configurations, service port status, and connectivity between PCs in different branches of an
enterprise.
Issue 01 (2016-04-29)

1046

Access Module
Prerequisites
PCs (with different MAC addresses) connected to different ONUs have been configured.
Ensure that the IP addresses of the PCs are in the same network segment or subnet segment.
Procedure
Step 1 Check whether the VLAN configurations are correct.
huawei(config)#display vlan 300
{ <cr>|inner-vlan<K>|to<K> }:
Command:
display vlan 300
VLAN ID: 300
VLAN type: smart
VLAN description:
VLAN forwarding mode in control board: VLAN-MAC
VLAN forwarding mode: VLAN-MAC
VLAN broadcast packet forwarding policy: forward
VLAN unknown multicast packet forwarding policy: forward
VLAN unknown unicast packet forwarding policy: forward
VLAN bind service profile ID: 1
VLAN bind RAIO profile index: VLAN priority: Standard port number: 0
--------------------------------------------------------INDEX TYPE STATE F/ S/ P VPI VCI
FLOWTYPE FLOWPARA
--------------------------------------------------------10 gpon up
0/3 / 1 1
12
vlan
300
11 gpon up
0/3 / 1 2
12
vlan
300
--------------------------------------------------------Service virtual port number: 2
Note: F--Frame, S--Slot, P--Port,
VPI indicates ONT ID for PON, VCI indicates GEM index for GPON,
v/e--vlan/encap, pri-tag--priority-tagged
huawei(config)#display vlan service-profile profile-id 1
Profile
ID: 1
Profile Name: srvprof-1
--------------------------------------------------------------------Parameter
Committed
Not Committed
--------------------------------------------------------------------Forwarding mode
NotConfig
Anti-macspoofing
NotConfig
Anti-ipspoofing
enable
PPPoE MAC mode
NotConfig
BPDU tunnel
enable
RIP tunnel
enable
VTP-CDP tunnel
enable
DHCP mode
n/a
DHCP proxy
enable
DHCP option82
enable
PITP
enable
Broadcast packet policy
NotConfig
Multicast packet policy
NotConfig
Unknown unicast packet policy
NotConfig
User-bridging
enable
IPoE VMAC
NotConfig
PPPoE VMAC
NotConfig
PPPoA VMAC
NotConfig
Mismatch IGMP packet policy
discard
VMAC aging mode
MAC-learning
OSPF tunnel
enable
Layer-3 protocol tunnel
enable
MAC-address learning fabric
enable
DHCPv6 mode
n/a
DHCPv6 option
enable
-
Issue 01 (2016-04-29)

1047

Access Module
PPPoA MAC mode

NotConfig
Anti-IPv6spoofing
enable
IPv6 DAD proxy
disable
Bind route and ND
disable
NS-reply function
disable
ARP-reply function
disable
DHCP relay-interface relay-agent NotConfig
Multicast packet policy fabric
forward
--------------------------------------------------------------------Binding VLAN list
: 300
---------------------------------------------------------------------
Step 2 Check whether the service port is normal.

huawei(config)#display service-port vlan 300
{ <cr>|autosense<K>|sort-by<K> }:
Command:
display service-port vlan 300
---------------------------------------------------------------------------INDEX VLAN VLAN
FLOW FLOW
RX
TX
STATE
ID
ATTR
TYPE
TYPE PARA
---------------------------------------------------------------------------10 300 common
gpon 0/3 /1 1
12
vlan 300
up
11 300 common
gpon 0/3 /1 2
12
vlan 300
up
---------------------------------------------------------------------------Total : 2 (Up/Down :
2/0)
huawei(config)#display statistics service-port 10
Number of upstream bytes
: 1044794
Number of upstream packets
: 4522
Number of upstream discard packets
: 200
Number of downstream bytes
: 1351261
Number of downstream packets
: 4677
Number of downstream discard packets : 0
Step 3 Check the connectivity between the PCs.

1.
Use the PCs to ping each other. If the PCs can ping each other successfully, the PCs are
reachable to each other.
For example, the IP addresses of PC1 and PC2 are 192.168.1.10 and 192.168.1.30
respectively. Ping PC2 on PC1. The expected result is as follows:
2.
You can see one PC in My Network Places on the other PC and the two PCs can share
data.
----End
Issue 01 (2016-04-29)

1048

Access Module
11.6 Configuring FTTO SOHO and SME Services (GE

Optical Port)
FTTO ONU users connect to the P2P board of the OLT or to the switch using a GE optical
uplink port to use the Internet access, Wi-Fi, voice, and video services.
Usage Scenario
This section uses the ONU users connecting to the P2P board of the OLT through a GE
optical uplink port as an example to describe how to configure the FTTO SOHO and SME
services.
In this scenario, an FTTO ONU connects to a P2P board, of the OLT using a GE optical
uplink port and then to the upper-layer network.
Figure 11-9 Networking using a GE optical port for upstream transmission
PC
ONU
TV
AAA Server
STB
Portal Server
G
U EO
ps p
tre tic
am al
Phone
Fax
PE-AGG
OLT
POS
UPE
Metro Network
PC
ONU
TV
STB
l
ca
p ti m
O
a
GE stre
Up
NGN/IMS
IPTV
Headend
Internet
UPE
PE-AGG
Phone
AAA Server
Fax
HLR
POS
Data Plan
Table 11-27 Data Plan
Item
Sub-item
Data
S-VLAN
HSI service
S-VLAN: 100
C-VLAN: 1001
Issue 01 (2016-04-29)

1049

Access Module
Item
Sub-item
Data
IPTV service
S-VLAN: 1000
M-VLAN: 1000
C-VLAN: 400
VoIP service
S-VLAN: 300
C-VLAN: 300
IPTV service data
IGMP mode
IGMP proxy
IGMP version
IGMPv3
Configuration mode for

multicast videos
Static

server
10.10.10.10
IP addresses of the DHCP

server group
20.2.2.2
Multicast videos:
BTV-1: 224.1.1.10
20.2.2.3
BTV-2: 224.1.1.20
QoS (priority)
HSI service
Priority: 1; queue scheduling

mode: WRR
IPTV service

mode: WRR
VoIP service

mode: PQ
Procedure
l
Configure the Internet access service on the OLT.

a.
Create a VLAN and add the uplink port to it.

The ID and type of the VLAN are 100 and smart, respectively. The uplink port is
0/19/0.
b.

The VoIP, IPTV, and Internet access services are provisioned using the same port.
Therefore, the 802.1p priority for each service must be configured. The 802.1p
priorities for the VoIP, IPTV, and Internet access services are in descending order
generally. In this example, the index of the traffic profile is 7, and the 802.1p
priority of the Internet access service is 1.
huawei(config)#traffic table ip index 7 cir 10240 priority 1 prioritypolicy
local-Setting
c.
Issue 01 (2016-04-29)
Configure service ports.

1050

Access Module
Add service ports to the VLAN. The VLAN ID is 1001, and traffic profile 7 is
bound to this VLAN.
1001
rx-cttr 7 tx-cttr 7
1001
rx-cttr 7 tx-cttr 7
d.

Queues are scheduled in 3PQ+5WRR mode. Specifically, queues 5-7 are scheduled
in PQ mode, and queues 0-4 are scheduled in WRR mode with weights 10, 10, 20,
20, and 40, respectively.
NOTE
Queue scheduling is configured globally. Specifically, after queue scheduling is configured on the
OLT, this configuration takes effect globally and also for follow-up configured services.
Configure mappings between 802.1p priorities and queues. 802.1p priorities 0-7
map to queues 0-7, respectively.
huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5
cos6 6
cos7 7
NOTE
If a board supports only four queues, the mappings between 802.1p priorities and queues are as
follows: 802.1p priorities 0 and 1 map queue 1, 2 and 3 map queue 2, 4 and 5 map queue 3, and 6
and 7 map queue 4.
e.
Save the data.

huawei(config)#save
Configure the Internet access service on the ONU.

on the ONU.
a.

i.

(default: 192.168.100.1).
ii.
b.

i.
Issue 01 (2016-04-29)

1051

Access Module
ii.
c.

i.
ii.
WAN mode: Route WAN

selected.)
VLAN ID: 1001 (The VLAN ID of the ONU must be the same as the
user-side VLAN ID configured on the OLT.)
802.1p: 1

the BRAS.)

service.)

d.
Issue 01 (2016-04-29)


1052

Access Module
e.

Configure the VoIP service on the OLT.

a.

0/19/0.
b.

The index of the traffic profile is 8. The 802.1p priority of the VoIP service is 6.
huawei(config)#traffic table ip index 8 cir 2048 priority 6 prioritypolicy
local-Setting
c.

Add service ports to the VLAN. The VLAN ID is 300, and traffic profile 8 is bound
to this VLAN.
300
rx-cttr 8 tx-cttr 8
300
rx-cttr 8 tx-cttr 8
d.
Save the data.

huawei(config)#save
Configure the H.248-compliant VoIP service on the ONU.

a.

i.
Issue 01 (2016-04-29)

(default: 192.168.100.1).
1053

Access Module
ii.
b.

i.
ii.

Mode: Route
802.1p: 5

c.
Issue 01 (2016-04-29)

i.
ii.
MG Domain: 6877687714852901
Region: China

1054

Access Module
NOTE
configured.

d.
Issue 01 (2016-04-29)

i.
ii.
Line Name: A0

1055

Access Module

iv.
v.
Line Name: A1

NOTE
MGC.
e.

i.
ii.

1_VOIP_R_VID_300.

f.

Issue 01 (2016-04-29)

1056

Access Module
g.

Restart VoIP.
h.

i.

Status is Up.
l
Issue 01 (2016-04-29)
Configure the SIP-compliant VoIP service on the ONU.

1057

Access Module
a.

i.

(default: 192.168.100.1).
ii.
b.

i.
ii.

Mode: Route
802.1p: 5

c.
Issue 01 (2016-04-29)

i.
ii.

Region: China

1058

Access Module
NOTE
configured.

d.

i.
ii.
Password: iadtest1

iv.
v.

Issue 01 (2016-04-29)

1059

Access Module

NOTE
e.

i.
ii.

1_VOIP_R_VID_300.

f.
Issue 01 (2016-04-29)


1060

Access Module
g.

Restart VoIP.
h.

i.

Status is Up.
l
Issue 01 (2016-04-29)
Configure the IPTV service on the OLT.

1061

Access Module
NOTE
The IPTV service does not need to be configured on the ONU.
a.

0/19/0.
b.

The index of the traffic profile is 9. The 802.1p priority of the IPTV service is 5.
huawei(config)#traffic table ip index 9 cir off priority 5 prioritypolicy
local-Setting
c.

Add service ports to the VLAN. The VLAN ID is 4, and traffic profile 9 is bound to
this VLAN.
huawei(config)#service-port 200 vlan 1000 eth 0/5/2 multi-service uservlan 400
rx-cttr 9 tx-cttr 9
huawei(config)#service-port 300 vlan 1000 eth 0/5/3 multi-service uservlan 400
rx-cttr 9 tx-cttr 9
d.
Create an M-VLAN and set the IGMP mode to IGMP proxy.

e.
Configure the IGMP version to IGMPv3.

f.
Configure the IGMP uplink port.

The IGMP uplink port is 0/19/0 and works in default mode. In addition, protocol
packets are sent to all IGMP uplink ports contained in the M-VLAN housing the
ordered video.
g.
(Optional) Configure global multicast parameters.

Perform this step if the default multicast parameters must be modified. In this
example, all global multicast parameters use default settings.
h.
Configure multicast videos.

The multicast videos are BTV-1 and BTV-2. The IP addresses of these videos are
224.1.1.10 and 224.1.1.20, respectively. Both videos use the same source IP address
10.10.10.10.
sourceip
10.10.10.10
sourceip
10.10.10.10
i.
Configure a rights profile.

The profile name is profile0, which allows users to watch video BTV-1.
Issue 01 (2016-04-29)

1062

Access Module

watch
j.

Configure multicast users with service flows 200 and 300.
profile0
k.
Save the data.

huawei(config)#save
Configure the Wi-Fi service on the ONU.

a.

Choose WLAN from the main menu. Then, in the navigation tree on the left side of
the page, choose WLAN Basic Configuration and configure parameters shown in
Issue 01 (2016-04-29)

1063

Access Module
b.

selected
ID configured on the OLT

c.

Choose Status from the main menu. Then, in the navigation tree on the left side of
the page, choose WAN Information to check the ONU connection status.
Issue 01 (2016-04-29)

1064

Access Module
----End
Result
The configured services can be used only after both the OLT and ONU are configured.
l
For the Internet access service, users can access the Internet using PPPoE dialup.
For the VoIP service, users can make and receive calls.
For the IPTV service, the user connected to port 0/5/2 can watch both videos, and the
user connected to port 0/5/3 can watch only video BTV-1.
For the Wi-Fi service, SSID-specific wireless signals can be detected by the PC. After a
user enters a correct authentication key, the PC automatically obtains an IP address
allocated by the ONU using DHCP. After the ONU automatically performs PPPoE
dialup and the dialup is successful, the user can access the Internet.
11.7 Configuring FTTO SOHO and SME Services (GE

Electrical Port)
An FTTO ONU functions as a routing gateway. Its users use a GE electrical uplink port to
connect to the LAN port of an ONU on an FTTB or FTTC network to use the Internet access,
Wi-Fi, voice, and video services.
Usage Scenario
In this scenario, the FTTO ONU functions as a routing gateway. It uses a GE electrical uplink
port to connect to the LAN port on an upper-layer ONU and then to the upper-layer network
through a PON network.
NOTE
l MA5676C do not support voice service.

l In this scenario, the GE electrical uplink port can alternatively be a GE service port.
Issue 01 (2016-04-29)

1065

Access Module
Figure 11-12 Networking using a GE electrical port for upstream transmission

AAA Server
Portal Server
PE-AGG
PC
FTTO ONU
TV
ONU
OLT
PON
GE
Electrical
Upstream
STB
NGN/IMS
UPE
Metro Network
Internet
UPE
Phone
IPTV
Headend
PE-AGG
Fax
POS
AAA Server
HLR
Data Plan
Table 11-28 Data Plan
Item
Sub-item
HSI service
Encapsulation type: PPPoE

VLAN ID: 1001 (same as the user VLAN configured on the
upper-layer ONU)
NAT (NATEnabled) status: enabled
VoIP service
VLAN ID: 300

IP address obtaining mode: DHCP
Wi-Fi service
SSID name: WirelessNet1

Authentication mode: WPA Pre-Shared-key
Encryption mode: TKIP
WPS status: enabled
IPTV service
Omitted (This service is configured on the upper-layer ONU

and OLT.)
Procedure
l
Configure the FTTB or FTTC network.

For details about how to configure the FTTB or FTTC network, see the Configuration
Guide.
Configure the Internet access service on the FTTO ONU.

on the ONU.
Issue 01 (2016-04-29)

1066

Access Module
a.

i.

(default: 192.168.100.1).
ii.
b.
c.
Issue 01 (2016-04-29)

i.
ii.

i.
ii.
WAN mode: Route WAN

selected.)
VLAN ID: 1001 (The VLAN ID of the FTTO ONU must be the same as
the user-side VLAN ID configured on the upper ONU.)
802.1p: 1

the BRAS.)

service.)

1067

Access Module
d.

e.

Configure the H.248-compliant VoIP service on the FTTO ONU.

a.
Issue 01 (2016-04-29)

1068

Access Module
i.

(default: 192.168.100.1).
ii.
b.

i.
ii.

Mode: Route
VLAN ID: 300 (The VLAN ID of the ONU must be the same as the userside VLAN ID configured on the upper ONU.)
802.1p: 5

c.
Issue 01 (2016-04-29)

i.
ii.
MG Domain: 6877687714852901
Region: China

1069

Access Module
NOTE
configured.

d.
Issue 01 (2016-04-29)

i.
ii.
Line Name: A0

1070

Access Module

iv.
v.
Line Name: A1

NOTE
MGC.
e.

i.
ii.

1_VOIP_R_VID_300.

f.

Issue 01 (2016-04-29)

1071

Access Module
g.

Restart VoIP.
h.

i.

Status is Up.
l
Issue 01 (2016-04-29)
Configure the SIP-compliant VoIP service on the FTTO ONU.

1072

Access Module
a.

i.

(default: 192.168.100.1).
ii.
b.

i.
ii.

Mode: Route
VLAN ID: 300 (The VLAN ID of the ONU must be the same as the userside VLAN ID configured on the upper ONU.)
802.1p: 5

c.
Issue 01 (2016-04-29)

i.
ii.

Region: China

1073

Access Module
NOTE
configured.

d.

i.
ii.
Password: iadtest1

iv.
v.

Issue 01 (2016-04-29)

1074

Access Module

NOTE
e.

i.
ii.

1_VOIP_R_VID_300.

f.
Issue 01 (2016-04-29)


1075

Access Module
Issue 01 (2016-04-29)
g.

Restart VoIP.
h.

i.

Status is Up.
Configure the IPTV service. (The IPTV service does not need to be configured on the
FTTO ONU.)
1076

Access Module
Configure the Wi-Fi service on the FTTO ONU.

a.

Choose WLAN from the main menu. Then, in the navigation tree on the left side of
the page, choose WLAN Basic Configuration and configure parameters shown in
b.
Issue 01 (2016-04-29)

1077

Access Module

selected
ID configured on the upper ONU

c.

Choose Status from the main menu. Then, in the navigation tree on the left side of
the page, choose WAN Information to check the ONU connection status.
----End
Result
The configured services can be used only after both the FTTB/FTTC ONU and FTTO ONU
are configured.
l
For the Internet access service, users can access the Internet using PPPoE dialup.
For the VoIP service, users can make and receive calls.
Issue 01 (2016-04-29)

1078

Access Module
For the IPTV service, users can watch videos with configured permissions.
For the Wi-Fi service, SSID-specific wireless signals can be detected by the PC. After a
user enters a correct authentication key, the PC automatically obtains an IP address
allocated by the ONU using DHCP. After the ONU automatically performs PPPoE
dialup and the dialup is successful, the user can access the Internet.
Issue 01 (2016-04-29)

1079

Access Module
12
12 FTTO Configuration (Large-sized Enterprise Access)
FTTO Configuration (Large-sized

Enterprise Access)
About This Chapter

Large-sized enterprises generally adopt private line access service. Compared with individual
services, this service features various access methods, large number of access users, high
security requirement, and cross-region deployment.
NOTE
In this document, the FTTO large-sized enterprise private line access service is written as enterprise access
service for short.
12.1 FTTO (Large-sized Enterprise Access) Configuration Summary

FTTO (Large-sized Enterprise Access) Configuration Guide is written based on solution
scenarios, covering the entire E2E service configuration process for the OLT and ONU. This
guide provides guidance for service configuration in FTTO (Large-sized Enterprise Access)
involving the OLT and ONUs of different models. The OLT and MA5612 are used in all
service scenarios for FTTO (Large-sized Enterprise Access). Therefore, OLT or ONU users
can select the concerned scenarios.
12.2 Overview of Enterprise Access Service
This topic describes the basic knowledge about the enterprise access service. Before
configuring the enterprise access service, you are advised to learn about the basic knowledge.
12.3 Principle of Planning Data for Enterprise Access Service
This topic plans data for the enterprise access service from multiple dimensions. The data plan
guides configuration and optimization of the enterprise service in different scenarios.
12.4 Configuring Layer 2 Interoperation Service Between Enterprise Branches (GPON)
12.5 Configuring Enterprise DDN Private Line Access Service (GPON)
Enterprise DDN private line service is converted to E1 signals. ONUs access the E1 signals
and transmit them in Native TDM mode.
12.6 Configuring Enterprise IP PBX Private Line Access Service (GPON)
ONUs provide GE/FE ports to access IP private branch exchange (PBX) services of an
enterprise and transmit them to an OLT. Then, the OLT forwards the service data upstream to
Issue 01 (2016-04-29)

1080

Access Module
the packet switched network (PSN). This achieves unified carrying of voice, data, and video
services.
12.7 Configuring Enterprise PRA PBX Private Line Access Service (GPON)
ONUs provide PRA E1 ports to access PRA private branch exchange (PBX) services of an
the packet switched network (PSN). This achieves voice-to-IP conversion, simplifying the
network architecture.
12.8 Configuring Enterprise E1 Unified Access Service (GPON)
ONUs transmit E1 signals of enterprises to OLTs in SAToP mode and OLTs are
interconnected with transmission equipment through E1 ports. In this manner, traditional
circuit switching services can be carried over GPON networks.
12.9 Configuring Enterprise E1 Unified Access Service (OLT Cascading, GPON)
ONUs access enterprise TDM service in E1 access mode, and transmits the data to the SDH
network in OLT cascading mode over the GPON network which supports long-distance
transmission and high bandwidth. In this way, uniform deployment of E1 service is achieved.
Issue 01 (2016-04-29)

1081

Access Module
12.1 FTTO (Large-sized Enterprise Access) Configuration

Summary
FTTO (Large-sized Enterprise Access) Configuration Guide is written based on solution
scenarios, covering the entire E2E service configuration process for the OLT and ONU. This
guide provides guidance for service configuration in FTTO (Large-sized Enterprise Access)
involving the OLT and ONUs of different models. The OLT and MA5612 are used in all
service scenarios for FTTO (Large-sized Enterprise Access). Therefore, OLT or ONU users
can select the concerned scenarios.
12.2 Overview of Enterprise Access Service

This topic describes the basic knowledge about the enterprise access service. Before
configuring the enterprise access service, you are advised to learn about the basic knowledge.
Network Diagram of Enterprise Access Service

PRA PBX
ONU
Switch
E1/STM-1
IP PBX
Digital Terminal
DDN
SDH
OLT
Switch
Splitter
DDN Node Protocol

Machine Converter
GE
/10
GE
IP network
NGN/IMS
E1
V.24/V.35
Enterprise Side
ONU
Access Side
Network Side
User Side
Issue 01 (2016-04-29)
Concept
Description
IP PBX
IP private branch exchange (PBX) is an IP-based enterprise telephone

exchange system. IP PBX uses ICT technology to seamlessly
integrate voice communication into the data communication network
of an enterprise, simply network architecture, and provide better voice
communication between branches of the enterprise.
PRA PBX
PRA PBX, that is, TDM PBX, also called a switch, is a telephone
exchange used within an enterprise. With the PRA PBX, staff in the
enterprise can use internal telephones to make free calls by dialing
short numbers. Outgoing calls are made through a unified trunk. PRA
PBX can lower costs and improve work efficiency for the enterprise.
1082

Access Module
Concept
Description
DDN
Digital data network (DDN) is a network that uses digital channels to

transmit data signals. It provides permanent and semi-permanent
connections for users. Compared with traditional analog channels,
DDN channels have a higher transmission quality, transmission rate,
and bandwidth use rate. DDN is widely used in financial departments,
governments, and enterprise groups that require high real-time data
switching
DDN node
machine
A DDN network consists of backbone node machines and access node

machines.
A backbone node machine (2M node) implements network service
conversion. It provides interfaces and cross-connections for 2 Mbit/s
(E1) digital channels, multiplexes and cross-connects Nx64 kbit/s
circuit signals, and supports cables reconnection for frame relay
services.
An access node machine accesses various services for DDN. It
provides interfaces for Nx64 kbit/s and 2048 kbit/s digital channels,
multiplexes Nx64 kbit/s (N=131) signals, and accesses voice and
fax users.
Protocol converter
Protocol converter is a device used to convert standard or proprietary

protocol of one device to the protocol suitable for the other device or
tools to achieve the interoperability. In this document, it implements
protocol conversion between V.24/V.35 and E1.
Concept
Description
PON

Access Side

Issue 01 (2016-04-29)
ODN

OLT

MA5600T/MA5603T/MA5608T.

1083

Access Module
Concept
Description
ONU
Concept
Description
SDH
Synchronous digital hierarchy (SDH) is a transmission scheme that

follows ITU-T G.707, G.708, and G.709. It defines the transmission
features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part
of ISDN and B-ISDN. It interleaves the bytes of low-speed signals to
multiplex the signals to high-speed counterparts, and the line coding
of scrambling is used only for signals. SDH is suitable for the fiber
communications system with high speed and a large capacity since it
uses synchronous multiplexing and flexible mapping structure.
NGN/IMS

Network Side

NOTE
12.3 Principle of Planning Data for Enterprise Access

Service
This topic plans data for the enterprise access service from multiple dimensions. The data plan
guides configuration and optimization of the enterprise service in different scenarios.
12.3.1 Principle of Equipment Management Data Plan

Data planning for equipment management covers planning of management VLANs and IP
addresses.
Management VLAN Planning

l
The OLT and ONUs use the same management VLAN.
The OLT and ONUs use a single SVLAN as the equipment management VLAN.
Issue 01 (2016-04-29)

1084

Access Module
IP Address Planning
Scenario
IP Address Planning
Equipment
management
A management IP address is allocated to each OLT/ONU.

Management IP addresses of ONUs connected to the same OLT are
usually in the same network segment. Private IP addresses planned
by the carrier are used for the purpose of security.
Layer 2
interoperation
between different
enterprise branches
Enterprise service flows are forwarded at Layer 2 within the FTTx

network. Therefore, no IP addresses need to be planned on the OLT
and ONUs for enterprise users.
Enterprises DDN
private line access
No IP addresses need to be planned because ONUs access the

private line service through E1.
Enterprise IP PBX
access
No IP addresses need to be planned because the OLT and ONUs

provide Layer 2 transparent channels.
Enterprise PRA
PBX access
ONUs convert PRA voice signals to H.248 or SIP voice signals.

Therefore, the following IP addresses need to be planned:
l Media IP address
l Signaling IP address
l Default gateway IP address
Enterprise E1/T1
unified access
Enterprise E1/T1
unified access (OLT
Cascading)
IP addresses are planned as follows:

l On OLTs, source IP addresses of SAToP connections must be
planned for E1 boards.
l On ONUs, source IP addresses of SAToP connections must be
These IP addresses are valid only between OLTs and ONUs and
therefore can be planned as private IP addresses.
12.3.2 Principle of VLAN Data Plan

VLAN planning for the enterprise access service covers planning of VLANs and VLAN
translation policies in different networking scenarios.
Issue 01 (2016-04-29)

1085

Access Module

Scenario
VLAN Planning
Layer 2
interoperation
between
different
enterprise
branches
l ONUs and the OLT

must use single VLAN
tags.
l Service flows of the
same enterprise has the
same VLAN on the
OLT.
l Service flows of the
same enterprise can
have different VLANs
on ONUs but the
VLANs must be
translated to the same
VLAN on the OLT.
Enterprises
DDN private
line access
Use a reserved CVLAN

(starts from 4000).
Enterprise IP
PBX access
Single VLAN tag: ONUs

and the OLT use single
VLAN tags. Service
packets are forwarded
based on single VLAN tags
after being transmitted from
the OLT upstream to the
metro network. In this way,
a large number of VLANs
for the metro network will
be occupied if there are
many OLTs.
VLAN Translation
ONU
OLT
l The same
CVLAN is
planned for
different
branches of an
enterprise.
The OLT allocates

a global SVLAN
to each enterprise:
CVLAN<>SLVAN.
l Different
CVLANs are
planned for
different
enterprises.
NOTICE
Packets must be
forwarded based on
VLAN+MAC at
Layer 2 instead of
SVLAN+CVLAN.
N/A
N/A
1. Different user
VLANs are
planned for
different
services
(service
packets with
different
destination
addresses or
paths) of the IP
PBX.
The OLT
transparently
transmits packets
with CVLANs
from ONUs.
NOTICE
A reserved CVLAN cannot be
used for Ethernet services on
ONUs.
2. User VLANs
of packets sent
from the IP
PBX are
translated to a
specified
CVLAN based
on service
types.
Issue 01 (2016-04-29)

1086

Access Module
Scenario
VLAN Planning
(Recommended) Double
VLAN tags: Each OLT uses
double VLAN tags, an
outer VLAN tag (SVLAN)
and inner VLAN tag
(CVLAN). SLVANs are the
same but CLVANs are
different. In this way, the
number of VLANs required
for the metro network is
significantly reduced.
VLAN Translation
ONU
OLT
1. Different user
VLANs are
planned for
different
services
(service
packets with
different
destination
addresses or
paths) of the IP
PBX.
The OLT adds an

SVLAN tag:
CVLAN<>SVLAN
+CVLAN.
2. User VLANs
of packets sent
from the IP
PBX are
translated to a
specified
CVLAN based
on service
types.
Enterprise PRA
PBX access
Enterprise
E1/T1 unified
access
Enterprise
E1/T1 unified
access (OLT
Cascading)
Issue 01 (2016-04-29)
(Recommended) Single
VLAN tag
ONUs access the

PRA PBX through
E1, provide the
VoIP PRA service,
and use the same
CVLAN.
The OLT
transparently
transmits packets.
Double VLAN tags
ONUs access the

PRA PBX through
E1, provide the
VoIP PRA service,
and use the same
CVLAN.
The OLT adds an

SVLAN tag:
CVLAN<>SVLAN
+CVLAN.
Plan a global VLAN on the

OLT and ONUs, which
cannot conflict with other
service VLANs.
N/A
N/A

1087

Access Module
12.3.3 Principle of QoS Data Plan

QoS planning for the enterprise access service is end-to-end. QoS policies include traffic
classification, marking and scheduling, traffic monitoring, and DBA policies. QoS policies for
different scenarios are different. This topic provides QoS policies in the following scenarios.
Layer 2 interoperation Between Different Enterprise Branches

Value
Parameter
Traffic
classification,
marking, and
scheduling policies
Traffic
monitorin
g and
DBA
policies
OLT
ONU
802.1p priority
Queue scheduling
mode
PQ
OLT queue ID
(eight queues)
T-CONT (only for

GPON)
An independent T-CONT is used.
DBA Type
Type 3 ("Assured bandwidth+maximum

bandwidth" DBA profile. This type of DBA
not only ensures a fixed bandwidth for users
but also enables users to preempt a certain
amount of bandwidth, but the total bandwidth
cannot exceed the maximum bandwidth.)
DBA bandwidth
Plan the bandwidth according to users'

requirements.
Downstream traffic
profile
Configure the profile according to users'

bandwidth requirements.
Upstream port rate

limit
Rates of upstream ports are not limited.
Downstream port
rate limit
Rates of downstream ports are not limited.
Enterprise DDN Private Line Access

In this scenario, ONUs access services from the DDN through E1 lines. Therefore, the QoS
policies are mainly planned for traffic on PON lines.
Issue 01 (2016-04-29)
Parameter
Value
Remarks
T-CONT
It is recommended that the

number of T-CONTs do not
exceed 3. The T-CONT ID ranges
from 1 to 3.
It is recommended that all E1

lines of the same ONU use the
same T-CONT.

1088

Access Module
Parameter
Value
Remarks
DBA type
Fixed bandwidth and minimum

delay
The DBA must be configured

properly to achieve low delay,
low jitter, and zero packet loss so
that the quality of the DDN
private line service can be
ensured.
DBA bandwidth
Nx7232 kbit/s is recommended.

(N is the number of E1 lines.)
It is recommended that the TCONT ID be 1, 2, or 3 and all E1

same T-CONT. This setting can
leverage bandwidth resources.
Each E1 line requires only 5440
kbit/s.
Enterprise PRA PBX Access

Value
Parameter
Traffic
classification,
marking, and
scheduling policies
Traffic
monitorin
g and
DBA
policies
OLT
802.1p priority
Queue scheduling
mode
PQ
OLT queue ID
(eight queues)
T-CONT (only for

GPON)
All services share one T-CONT.
DBA type

DBA bandwidth
DBA bandwidth is configured based on the

bandwidth package selected by the user.
The assured bandwidth is the maximum
bandwidth required for transmitting
management packets and VoIP service packets.
The maximum bandwidth is equal to or higher
than the maximum bandwidth applied by the
user.
ONU
Issue 01 (2016-04-29)
Downstream traffic
profile
Downstream traffic rate is not limited.
Upstream port rate

limit
Set this parameter based on requirements.

1089

Access Module
Parameter
Value
Downstream port
rate limit
Set this parameter based on requirements.
Enterprise IP PBX Access

The QoS policies for this scenario are the same as those for the Layer 2 interoperation
Between Different Enterprise Branches scenario.
Enterprise E1/T1 unified access

In this scenario, ONUs access services through E1/T1 lines. Therefore, the QoS policies are
mainly planned for traffic on PON lines.
Parameter
Value
Remarks
T-CONT

from 1 to 3.

same T-CONT.
DBA type

delay

that the quality of the T1 base
station access service can be
ensured.
DBA bandwidth
l E1 access: Nx8 Mbit/s is

recommended. (N is the
number of E1 lines.)
l T1 access: Nx6 Mbit/s is

Enterprise E1/T1 unified access (OLT Cascading)

The QoS policies for this scenario are the same as those for the Enterprise E1/T1 unified
access scenario.
12.3.4 Principle of Protocol Transparent Transmission Data Plan

The enterprise access service involves transparent transmission of protocol packets. Different
equipment configurations are required for transparently transmitting different protocol
packets.
Issue 01 (2016-04-29)

1090

Access Module
Configurations for Protocol Transparent Transmission

Protocol
Type
Protocol Description
Configuration (remarks 1)
BPDU
STP, MSTP, RSTP, ISIS
The function of transparently transmitting

BPDU packets must be enabled.
Configuration example:
huawei(config)#vlan service-profile
profile-id 1
huawei(config-vlan-srvprof-1)#bpdu
tunnel enable
ETH OAM
IEEE 802.1ag
No configuration is required because packets

are transparently transmitted by hardware.
Broadcast
ARP

Layer 2/Layer
3 protocol
NTP, BGP, LDP, RSVP,

IGMP, PIM

OSPF

OSPF packets must be enabled.
profile-id 1
huawei(config-vlan-srvprof-1)#ospf
tunnel enable
RIP
The function of transparently transmitting RIP

packets must be enabled.
profile-id 1
huawei(config-vlan-srvprof-1)#rip
tunnel enable
VTP/CDP
Unknown
multicast
VTP/CDP protocol is a
proprietary protocol of
other vendors. It is used
to discover neighbors
and establish neighbor
relationship.

VTP/CDP packets must be enabled.
Planned by carriers for

special purposes

unknown multicast packets must be enabled.
profile-id 1
huawei(config-vlan-srvprof-1)#vtp-cdp
tunnel enable
huawei(config)#multicast-unknown policy
service-port 1 transparent
Remarks 1: The configurations take effect only after the configured VLAN service profile is
bound to a VLAN. Command: vlan bind service-profile vlan-id profile-id
Issue 01 (2016-04-29)

1091

Access Module

Security planning covers planning of system security, user security, and service security data.
An appropriate security plan ensures normal running of services.
NOTE
l
System Security
Security
Vulnerability
Solution

Suggestion
DoS attack

MDU.

deployment.
IP attack

MDU.

deployment.
Issue 01 (2016-04-29)

1092

Access Module
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing

and MDU.
malicious attacks.
deployment.
MAC attack
Enable the anti-MAC

and MDU.

malicious attacks.
deployment.
IP spoofing

function for MDU.

malicious attacks.
deployment.
12.3.6 Principle of Reliability Data Plan

Reliability planning covers planning of equipment reliability and upstream/downstream
networking protection. Reliability planning helps to achieve high reliability of private line
services.
Issue 01 (2016-04-29)

1093

Access Module
Equipment Reliability
Protection Scheme
Description
Suggestion
Main control board

1+1 protection
The system uses two main control

boards of the same model and
version. The two main control
boards work in the active/standby
mode by default. When the active
main control board fails, the system
switches to the standby main control
board to prevent service
interruption.
Mandatory
Power board 1+1

protection
A subrack is configured with two

power boards of the same model
and version, which back up each
other. When one of the power board
fails, the other power board can still
provide power supply to the device
and so the system can still work
properly.
Mandatory
Upstream board 1+1

protection
The system uses two upstream

interface boards of the same model
and version. Each GIU board
provides one upstream port and two
upstream ports are bound together
using Link Aggregation Control
Protocol (LACP). When the active
upstream port fails, traffic will be
standby upstream port.
This protection scheme is

recommended when the
GIU board is used to
transmit traffic upstream.
Upstream Networking Protection
Issue 01 (2016-04-29)
Protection Scheme
Description
Suggestion
Link aggregation
group
Multiple Ethernet ports are bound

together as an aggregation group to
increase the bandwidth and balance
the inbound and outbound load of
each member port. In addition, the
ports in an aggregation group back
up each other, which enhances the
reliability of links.

mandatory when the GIU
board is used to transmit
traffic upstream.

1094

Access Module
Protection Scheme
Description
Suggestion
Protection group
(Ethernet/STM-1)
A protection group of upstream

ports contains a working port and a
protection port. In normal state, the
working port carries services and
the protection port does not. When
the link at the working port is faulty,
the system automatically switches
services from the working port to
the protection port to ensure normal
service transmission and protect the
uplink.
When the main control

traffic upstream, this
protection scheme is
mandatory.
recommended when traffic
is transmitted upstream
through STM-1 ports.
NOTE
Link aggregation group and Ethernet protection group usually are not configured at the same time. You are
advised to configure only one of the two protection schemes.
Downstream Networking Protection
Issue 01 (2016-04-29)
Protection Scheme
Description
Suggestion
xPON Type B single

homing
Two PON ports on the same OLT

back up each other. When one of the
PON ports fails, the system
automatically switches to the other
PON port. This protection scheme
provides port-level protection with
low costs. It protects services
against fiber failure at the working
port.
It rovides port-level
protection and has a low
cost. The inter-board
protection mode is
recommended.
GPON Type C single

homing
Two PON ports on the same OLT,

two PON ports on an ONU, two
backbone optical fibers, two optical
splitters, and two tributary optical
fibers are configured to provide
link-level protection.
It rovides link-level
protection.

1095

Access Module
Protection Scheme
Description
Suggestion
GPON Type C dual

homing
Two PON ports on different OLTs,

fibers are configured to implement
this protection. The difference
between this protection scheme and
the GPON Type C single homing
protection scheme is that the ONU
needs to be dual homed to two OLTs
in this protection scheme. This fullbackup protection scheme provides
the highest-level protection for links
and has the highest costs.
It provides full backup

protection, which is the
highest level of protection,
at the same time, it has the
highest cost.
This protection scheme
can be configured for only
the Ethernet QinQ private
line service. It does not
support TDM services,
including Native TDM and
SAToP.
NOTE
The Type B single homing protection scheme, Type C single homing scheme, and Type C dual homing
protection scheme are mutually exclusive. Therefore, only one of these protection schemes can be configured
for an ONU.
12.4 Configuring Layer 2 Interoperation Service Between

Enterprise Branches (GPON)

Service Requirement
An enterprise that has multiple branches requires intercommunication between different
branches or between its headquarter and branches. Virtual private network (VPN) can achieve
secure interconnection but requires additional devices and complex management. It requires
high costs even if a leased VPN is used. In addition, the bandwidth provided by a VPN is
limited due to restricted VPN access modes and the bandwidth control is inflexible.
To address the preceding problems, the Layer 2 interoperation technology using fiber access
is put forward and becomes the main trend.
As shown in Figure 12-1, ONUs are deployed in branches of an enterprise. The ONUs access
and converge Ethernet services of the enterprise through FE/GE ports and transmit the
services to the OLT. The OLT implements Layer 2 interoperation between different branches
of the enterprise.
Issue 01 (2016-04-29)

1096

Access Module
Figure 12-1 Network diagram for Layer 2 interoperation between enterprise branches
IP/MPLS
ONU 1
GE
Headquarter
ONU 2
FE
Branch A
FE
Branch B
Service flows between

enterprise branches
Note: Because the bandwidth of upstream and downstream PON ports is fixed, the number of
enterprises connected to an OLT is limited when the enterprises require symmetric bandwidth.
When an enterprise requires 100 Mbit/s symmetric bandwidth:
1.
The number of enterprises or branches connected to a PON port should not exceed eight.
2.
The number of enterprises or branches connected to a PON board should not exceed 64.
3.
The number of enterprises connected to an OLT cannot exceed 200 (20G/100M) if the
upstream bandwidth is 2x10GE. (The number of enterprises connected to an OLT is
mainly restricted by the upstream bandwidth.)

The following figure shows the configuration process for Layer 2 interoperation between
branches of an enterprise.
Issue 01 (2016-04-29)

1097

Access Module
Start
Adding ONUs to OLT
Configuring Management
Service Ports on OLT
and ONUs
OLT Side
Configuring Layer 2
Interoperation Service
Service Ports
Configuring Congestion
Control and Security
Policies
Configuring E2E
Reliability
Configuring Ethernet
Access Service Ports
ONU Side
Verifying Layer 2
Interoperation Service
End
NOTE
An OLT can connect to multiple ONUs (for enterprise branches). Configurations for different ONUs are
similar. Therefore, this document uses two ONUs (ONU1 and ONU2) as example to describe how to
configure Layer 2 interoperation.

Issue 01 (2016-04-29)

1098

Access Module
Context
l
profile, line profile, and alarm profile. For the functions of each profile and how to
configure profiles, see Table 12-1.
Table 12-1 ONU profile
Issue 01 (2016-04-29)
Profile
Type
Function
Command
DBA
profile

parameters. A T-CONT is
bound to a DBA profile for
dynamic bandwidth allocation,
improving upstream bandwidth
utilization.
Query: display dba-profile
Line
profile
Describes the binding

relationship between T-CONTs
and DBA profiles, QoS mode
of service flows, and mapping
between GEM ports and
services on ONUs.
Query: display ont-lineprofile
Alarm
profile
Provides a series of alarm

threshold parameters that are
used for performance
measurement and monitoring
of activated ONU lines.
Query: display gpon alarm-profile
Add: dba-profile add
Add: ont-lineprofile add
Add: gpon alarm-profile add

Mode
Command
Offline
addition
The password or serial number

of an ONU has been obtained.

ONU.
Online
confirmat
ion
The password and serial

number of an ONU are
unknown.
Run the port ont-auto-find command

in the GPON mode to enable the
automatic discovery function for the
GPON port and run the ont confirm
command to add the ONU.

1099

Access Module
Data Planning
Configuration
Item
Data
DBA profile
Profile ID: 20
Line profile
Profile ID: 10
T-CONT ID: 4
GEM port ID for management service: 11
GEM port ID for Layer 2 interoperation service: 12
Networking data
For example, add two ONUs (ONU 1 and ONU 2) for carrying services
of different branches.
Procedure
1.

2.

a.
Create GPON ONU line profile 10.

NOTE
Create a line profile according to the data plan. The ID of the line profile to be created cannot
conflict with existing profile IDs in the system. In this example, the ID of the line profile is 10.
b.
In the line profile configuration mode, bind T-CONT 4 to DBA profile 20.
c.
In the line profile configuration mode, bind GEM ports to T-CONTs.

n
Add GEM port 11 for carrying the management service flow.
Add GEM port 12 for carrying the Layer 2 interoperation service flow.
Both GEM port 11 and GEM port 12 are bound to T-CONT 4. During
configuration, set QoS policies for each service flow. For details on QoS data
planning, see 12.3.3 Principle of QoS Data Plan.
d.
Issue 01 (2016-04-29)
Configure mapping between GEM ports and ONU-side services.

1100

Access Module
Set the mapping mode to VLAN mode (the default mode). Map the management
service flow (CVLAN 8) to GEM port 11, and map Layer 2 interoperation service
flow (CVLAN 300) to GEM port 12.
e.
3.

1.
Add ONU 1 and ONU2 in offline mode.

Connect ONU 1 and ONU 2 to GPON ports 0/3/1 and 0/4/1 respectively through an
optical splitter. The serial numbers of the two ONUs are 3230313163902641 and
32303131B39FD642 respectively, and the management mode is SNMP. Both the ONUs
are bound to line profile 10.
huawei(config-if-gpon-0/3)#ont add 1 ontid 1 sn-auth 3230313163902641
snmp ont-lineprofile-id 10
2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Issue 01 (2016-04-29)

1101

Access Module
Follow-up Procedure
l
ONU.
12.4.4 Configuring Management Service Ports on OLT and ONUs

This topic describes how to configure management service ports (also called service flows) on
the OLT and ONUs. After the connections between the in-band management service ports on
the OLT and ONUs are reachable, you can log in to the ONUs on the OLT and configure the
ONUs.
Data Plan
Configuration
Item
Data
Management
VLAN and
management IP
address for OLT
Management
VLAN and
management IP
address for
ONU
Management VLAN type: smart

In-band management IP address: 192.168.50.1/24

In-band management IP address for ONU 1: 192.168.50.2/24
In-band management IP address for ONU 2: 192.168.50.3/24
NOTE
To log in to and configure an ONU remotely on the OLT, the management VLAN of the OLT must be the
same as that of the ONU, and the management IP address of the OLT and that of the ONU must be in the
same network segment.
Issue 01 (2016-04-29)

1102

Access Module
Procedure
Step 1 Configure the in-band management VLAN and IP address for the OLT.
Set the in-band management VLAN to 8, VLAN priority to 6, and IP address to
192.168.50.1/24.
Step 2 Configure the in-band management VLAN and IP addresses for the ONUs.
Set the static IP address to 192.168.50.2/24 for ONU1, 192.168.50.3/24 for ONU2, the
gateway IP address to 192.168.50.1, and management VLAN to 8 (which is the same as that
of the OLT).
255.255.255.0 gateway
192.168.50.1 vlan 8
255.255.255.0 gateway
192.168.50.1 vlan 8
Step 3 Configure the in-band management service port.

Set the management VLAN to 8, GEM port ID to 11, and user VLAN to 8. The OLT does not
rate limit the in-band management service port. Therefore, directly use the default traffic
profile 6.
Step 4 Confirm that the connections between the management service ports on the OLT and ONUs
are reachable.
l
Run the ping ONU ip command on the OLT to verify the connectivity between the OLT
and ONUs. If the OLT receives ICMP ECHO-REPLY packets from the ONUs, the
connection is reachable.
When the connection is reachable, you can remote log in to the ONU from the OLT and
configure the ONUs.
----End
12.4.5 Configuring Layer 2 Interoperation Service Ports on OLT

This topic describes how to configure service ports on the OLT for Layer 2 interoperation so
that data packets sent from different ONUs can be forwarded based on the same VLAN at
Layer 2.
Prerequisites
1.
Issue 01 (2016-04-29)
The main control board on the device is an SCUN board.

1103

Access Module
2.
The ARP proxy function is disabled using the arp proxy disable command. (The Layer
2 interoperation function and ARP proxy function are mutually exclusive.)
Data Plan
Configuratio
n Item
Data
Layer 2
interoperation
SVLAN
OLT VLAN ID (the OLT transparently transmits VLANs of ONU): 300

VLAN forwarding mode: vlan-mac (default)
ONU VLAN ID: 300
Traffic profile
Profile ID: 10
Default priority: 4
NOTE
For detailed data planning, see 12.3.2 Principle of VLAN Data Plan.
Procedure
Set the SVLAN ID of the Layer 2 interoperation service to 300, VLAN type to smart VLAN,
and add upstream port 0/19/0 to the VLAN.

Step 3 Configure a service port to receive and transparently transmit the Layer 2 interoperation
service that is sent from ONU 1 and ONU 2.
Set the service attributes based on the data plan:
l
For the OLT, set the SVLAN ID to 300, CVLAN ID to 300 which is the same as the
upstream VLAN ID of the ONU, and GEM port ID to 12 for the Layer 2 interoperation
service.
For ONUs, set the upstream VLAN ID to 300.

huawei(config)#service-port 302 vlan 300 gpon 0/4/1 ont 2 gemport 12 multi-
Issue 01 (2016-04-29)

1104

Access Module
service
Step 4 Configure attributes for protocol transparent transmission.

Create a VLAN service profile, enable the VLAN Layer 2 interoperation function, and
configure attributes for protocol transparent transmission. Then, bind the profile to VLAN
300. For details on data planning for protocol transparent transmission, see 12.3.4 Principle
of Protocol Transparent Transmission Data Plan.
//Mandatory
huawei(config-vlan-srvprof-1)#bpdu tunnel enable
huawei(config-vlan-srvprof-1)#ospf tunnel enable
huawei(config-vlan-srvprof-1)#rip tunnel enable
huawei(config-vlan-srvprof-1)#vtp-cdp tunnel enable
----End
12.4.6 Configuring Ethernet Access Service Ports on ONUs

This topic describes how to configure service ports on ONUs and configure upstream VLANs
to make the ONU-to-user connection reachable and create ONU-to-OLT upstream data
channels.
Data Planning
Configuration
Item
Data
Port

Service port: 0/3/1
SVLAN
VLAN ID: 300

VLAN type: smart
Traffic profile
Profile ID: 8
Assured rate: no rate limit
Default riority: 4
NOTE
Data plans for ONU1 and ONU 2 are the same. This topic uses one ONU as an example to describe how to
configure the ONU.
Procedure
Step 1 Remotely log in to an ONU to configure the ONU.
Issue 01 (2016-04-29)

1105

Access Module
root (default); password: admin123 (default)
Step 2 Create an SVLAN and add an upstream port to the VLAN.

Configure traffic profile 8. The upstream and downstream rates are not limited. Packets
transmitted upstream use the priority (4 by default) copied from the user side. Packets
transmitted downstream use the priority carried by themselves.
huawei(config)#traffic table ip index 8 cir off priority user-cos 4 prioritypolicy tag-in-package

Add service port 301 and bind it to port 0/3/1. Set the user VLAN to untagged and bind it to
traffic profile 8.
NOTE
Packets sent from the user side (enterprise branches) may be transmitted upstream with a VLAN tag. In this
case, change untagged to the VLAN tag when configuring a service port.
----End

This topic describes how to configure global priority-based scheduling policies for queues to
ensure service reliability and configure global security policies to ensure service security.
Context
is recommended.
NOTE
Enable security features based on service types. For details, see 12.3.5 Principle of Security Data Plan.
Procedure
l

i.
Issue 01 (2016-04-29)
1106

Access Module
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)
i.

ii.


1107

Access Module

----End
12.4.8 Configuring E2E Reliability

This topic describes how to configure end-to-end (E2E) protection schemes for the enterprise
private line service which has a high requirement on service reliability.
Context
Reliability covers equipment reliability, upstream networking protection, and downstream
networking protection. For details on reliability data planning, see 12.3.6 Principle of
Reliability Data Plan.
l
Upstream networking protection includes link aggregation group and protection group.
Usually, link aggregation group is configured when the GIU board is used to transmit
traffic upstream; protection group is configured when the main control board is used to
transmit traffic upstream. The two protection schemes are not configured at the same
time.
Downstream networking protection includes Type B, Type C single homing, and Type C
dual homing, which are used to protect service ports. Ports on the same ONU can be
configured only with the same protection scheme.
NOTE
This topic describes how to configure five mainstream protection schemes. Select required protection
schemes based on the carrier's requirement and actual networking scenario.
Procedure
l
Configure a link aggregation group.

Bind upstream ports 0/19/0 and 0/19/1 together as an aggregation link group. Each
member port in the group transmits packets based on source MAC addresses. The
working mode is LACP static aggregation.
Configure a protection group.

Configure upstream ports 0/19/0 and 0/19/1 on board GIU as a port protection group. Set
port 0/19/0 as the working port and port 0/19/1 as the protection port, set the working
mode to time delay detection, and enable the protection group.
huawei(config-protect)#protect-group first 0/19/0 second 0/19/1 eth workmode
timedelay enable
Configure the Type B protection.

Figure 12-2 shows the Type B protection networking diagram.
Issue 01 (2016-04-29)

1108

Access Module
Figure 12-2 Type B protection
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
Configure redundancy backup for ports 0/3/1 and 0/3/2 on the same GPON board on
OLT. When port 0/3/1 fails, the system can automatically switch to port 0/3/2.
huawei(config)#protect-group 0 protect-target gpon-uni-port workmode timedelay
huawei(protect-group-0)#protect-group member port 0/3/1 role work
huawei(protect-group-0)#protect-group member port 0/3/2 role protect
huawei(protect-group-0)#protect-group enable
NOTE
The configurations of services accessed by the ONUs remain the same after the Type B protection is
configured. That is, the service configurations are applied only to the working GPON port.
Configure the Type C single homing protection.

Figure 12-3 shows networking diagram for the Type C single homing protection.
Configure two 1:N optical splitters, one for connecting the working PON ports on the
OLT and ONUs, and one for connecting the protection PON ports on the OLT and
ONUs. This protection scheme protects both the backbone fibers and tributary fibers.
The configurations of services accessed by the ONUs remain the same after the Type C
single homing protection is configured. That is, the service configurations are applied
only to the working PON port on the OLT and working upstream PON ports on the
ONUs.
Figure 12-3 Type C single homing protection
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
Issue 01 (2016-04-29)

1109

Access Module
As shown in the preceding figure, Type C single homing protecting is configured for
optical fiber links between the OLT and ONU.
The ports on the GPON service board are 0/3/1 and 0/3/2.
The link at port 0/3/1 is the working link.
The link at port 0/3/2 is the protection link.
The ONU ID is 1.
The ONU is authenticated by serial number (SN). The SN of the ONU is

3230313163902641 and the management mode is SNMP.
The ID of the line profile bound to the ONU is 10.

huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ontlineprofile-id 10
huawei(config-if-gpon-0/3)#ont add 2 1 protect-side
huawei(config)#protect-group protect-target gpon-uni-ont workmode portstate
huawei(protect-group-1)#protect-group member port 0/3/1 ont 1 role work
huawei(protect-group-1)#protect-group member port 0/3/2 ont 1 role protect
huawei(protect-group-1)#quit
Configure the Type C dual homing protection.

Figure 12-4 shows the networking diagram for the Type C dual homing protection. Two
PON ports on different OLTs, two PON ports on an ONU, two backbone optical fibers,
two optical splitters, and two tributary optical fibers are configured to implement this
protection. The difference between this protection scheme and the Type C single homing
protection scheme is that the ONU needs to be dual homed to two OLTs in this
protection scheme.
The models and versions of main control boards on the active and standby OLTs must be
the same. The models and versions of GPON boards on the active and standby OLTs also
must be the same. Data on the active OLT cannot be automatically synchronized with
that on the standby OLT. Therefore, data synchronization between the active and standby
OLTs must be manually ensured.
This protection scheme can be configured for only the Ethernet QinQ private line
service. It does not support TDM services, including Native TDM and SAToP.
Issue 01 (2016-04-29)

1110

Access Module
Figure 12-4 Type C dual homing protection
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
As shown in the preceding figure, Type C dual homing protection is configured for two
OLTs (huawei_A and huawei_B).
huawei_A is the active OLT while huawei_B is the standby OLT.
The ports on the service boards on both OTLs are 0/3/1.
The dual homing protection group ID is 1.
The ONU ID is 1.

Configurations on the active OLT huawei_A:

huawei_A(config)#interface gpon 0/3
huawei_A(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ontlineprofile-id 10
huawei_A(config-if-gpon-0/3)#quit
huawei_A(config)#protect-group 1 protect-target gpon-uni-ont workmode dualparenting
huawei_A(protect-group-1)#protect-group member port 0/3/1 ont 1 role work
Configurations on the standby OLT huawei_B:
huawei_B(config)#interface gpon 0/3
huawei_B(config-if-gpon-0/3)#ont add 1 1 sn-auth 3230313163902641 snmp ontlineprofile-id 10
huawei_B(config-if-gpon-0/3)#quit
huawei_B(config)#protect-group 1 protect-target gpon-uni-ont workmode dualparenting
huawei_B(protect-group-1)#protect-group member port 0/3/1 ont 1 role protect
huawei_B(protect-group-1)#protect-group enable
----End
Issue 01 (2016-04-29)

1111

Access Module

This topic describes how to verify the Layer 2 interoperation service by checking the service
configurations, service port status, and connectivity between PCs in different branches of an
enterprise.
Prerequisites
PCs (with different MAC addresses) connected to different ONUs have been configured.
Ensure that the IP addresses of the PCs are in the same network segment or subnet segment.
Procedure
Step 1 Check whether the VLAN configurations are correct.
huawei(config)#display vlan 300
{ <cr>|inner-vlan<K>|to<K> }:
Command:
display vlan 300
VLAN ID: 300
VLAN type: smart
VLAN description:
VLAN forwarding mode in control board: VLAN-MAC
VLAN forwarding mode: VLAN-MAC
VLAN broadcast packet forwarding policy: forward
VLAN unknown multicast packet forwarding policy: forward
VLAN unknown unicast packet forwarding policy: forward
VLAN bind service profile ID: 1
VLAN bind RAIO profile index: VLAN priority: Standard port number: 0
--------------------------------------------------------INDEX TYPE STATE F/ S/ P VPI VCI
FLOWTYPE FLOWPARA
--------------------------------------------------------10 gpon up
0/3 / 1 1
12
vlan
300
11 gpon up
0/3 / 1 2
12
vlan
300
--------------------------------------------------------Service virtual port number: 2
Note: F--Frame, S--Slot, P--Port,
VPI indicates ONT ID for PON, VCI indicates GEM index for GPON,
v/e--vlan/encap, pri-tag--priority-tagged
huawei(config)#display vlan service-profile profile-id 1
Profile
ID: 1
Profile Name: srvprof-1
--------------------------------------------------------------------Parameter
Committed
Not Committed
--------------------------------------------------------------------Forwarding mode
NotConfig
Anti-macspoofing
NotConfig
Anti-ipspoofing
enable
PPPoE MAC mode
NotConfig
BPDU tunnel
enable
RIP tunnel
enable
VTP-CDP tunnel
enable
DHCP mode
n/a
DHCP proxy
enable
DHCP option82
enable
PITP
enable
Broadcast packet policy
NotConfig
Multicast packet policy
NotConfig
Unknown unicast packet policy
NotConfig
User-bridging
enable
IPoE VMAC
NotConfig
-
Issue 01 (2016-04-29)

1112

Access Module
PPPoE VMAC
NotConfig
PPPoA VMAC
NotConfig
Mismatch IGMP packet policy
discard
VMAC aging mode
MAC-learning
OSPF tunnel
enable
Layer-3 protocol tunnel
enable
MAC-address learning fabric
enable
DHCPv6 mode
n/a
DHCPv6 option
enable
PPPoA MAC mode
NotConfig
Anti-IPv6spoofing
enable
IPv6 DAD proxy
disable
Bind route and ND
disable
NS-reply function
disable
ARP-reply function
disable
DHCP relay-interface relay-agent NotConfig
Multicast packet policy fabric
forward
--------------------------------------------------------------------Binding VLAN list
: 300
---------------------------------------------------------------------
Step 2 Check whether the service port is normal.

huawei(config)#display service-port vlan 300
{ <cr>|autosense<K>|sort-by<K> }:
Command:
display service-port vlan 300
---------------------------------------------------------------------------INDEX VLAN VLAN
FLOW FLOW
RX
TX
STATE
ID
ATTR
TYPE
TYPE PARA
---------------------------------------------------------------------------10 300 common
gpon 0/3 /1 1
12
vlan 300
up
11 300 common
gpon 0/3 /1 2
12
vlan 300
up
---------------------------------------------------------------------------Total : 2 (Up/Down :
2/0)
huawei(config)#display statistics service-port 10
Number of upstream bytes
: 1044794
Number of upstream packets
: 4522
Number of upstream discard packets
: 200
Number of downstream bytes
: 1351261
Number of downstream packets
: 4677
Number of downstream discard packets : 0
Step 3 Check the connectivity between the PCs.

1.
Issue 01 (2016-04-29)
Use the PCs to ping each other. If the PCs can ping each other successfully, the PCs are
reachable to each other.
For example, the IP addresses of PC1 and PC2 are 192.168.1.10 and 192.168.1.30
respectively. Ping PC2 on PC1. The expected result is as follows:

1113

Access Module
2.
You can see one PC in My Network Places on the other PC and the two PCs can share
data.
----End
12.5 Configuring Enterprise DDN Private Line Access

Service (GPON)
Enterprise DDN private line service is converted to E1 signals. ONUs access the E1 signals
and transmit them in Native TDM mode.

Service Requirement
The DDN private line service is widely used in financial departments, governments, and
enterprises that require highly real-time data switching. It provides a rate from 64 kbit/s to 2
Mbit/s. GPON access in OLT+ONU mode can access the DDN private line service along with
other data services and voice service. This access mode does not require independent
maintenance of the DDN network, simplifying network architecture.
As shown in Figure 12-5, a protocol converter is deployed between an ONU and DDN node
machine to convert DDN private line services to E1 services. The ONU accesses the E1
services and encapsulates the service packets in TDM over GEM mode and then transmits the
packets to the OLT. The OLT decapsulates the service packets to E1 data and transmits the
data to the SDH network through upstream E1/STM-1 ports, achieving transparent
transmission of DDN services.
Applicable ONUs: MA5612, MA5628, MA5616, MA5694, MA5698
Figure 12-5 Networking diagram of the DDN private line access service
DDN Node
Machine
Digital Terminal
DDN
V.24/
V.35
ONU
OLT
E1
SDH
E1/STM-1
DDN Node
Machine Protocol
Converter
Digital Terminal
DDN
Issue 01 (2016-04-29)
Protocol
Converter
V.24/
V.35
Splitter
E1
ONU

1114

Access Module

The following figure shows the configuration process for the DDN private line access service.
Start
Adding ONUs to OLT
Service Ports on OLT and
ONUs
OLT Side
Configuring TDM E1
Connections
Policies
Configuring Clock
Synchronization
Verifying DDN Access

Services
End

Issue 01 (2016-04-29)

1115

Access Module
Context
l
profile, line profile, and alarm profile.
An ONU can be added in two modes: offline addition and online confirmation. Select
either mode as required.
Data Plan
Configurati
on Item
Data
DBA profile
DBA profile for management service: dba-profile_1 (system default)

DBA profile for private line service:
l Profile ID: 21
l Profile type: Fixed bandwidth and minimum delay
l DBA bandwidth: 28928 kbit/s (Each ONU accesses four E1 private
lines and each line has a recommended DBA bandwidth of 7232
kbit/s.)
Line profile
Profile ID: 11
T-CONT ID: 1 (for private line service) and 2 (for management service)
GEM port ID for DDN private line service: 13
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.
Configure a DBA profile. Enable the bandwidth compensation function and set the DBA
bandwidth allocation mode for the GPON port to minimum bandwidth delay.
bandwidth_compensate yes
huawei(config-if-gpon-0/3)#port dba bandwidth-assignment-mode 1 min-loop-delay
2.

huawei(config-gpon-lineprofile-11)#tcont 1 dba-profile-id 21 //Bind T-CONT 1
to DBA profile 21
to DBA profile 1
huawei(config-gpon-lineprofile-11)#gem add 13 tdm tcont 1 //Add GEM port 13
to T-CONT 1.
Issue 01 (2016-04-29)

1116

Access Module

huawei(config-gpon-lineprofile-11)#gem mapping 13 1 e1 1 //Map GEM port 13 to
E1 port 1 on the ONU.
3.

1.
Add ONU 3 in offline mode.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

1117

Access Module

ONUs.
Data Plan
Configuration Item
Data
Management VLAN and management IP

address for OLT

In-band management IP address:
192.168.50.1/24

address for ONU

In-band management IP address for ONU 3:
192.168.50.2/24
Procedure
192.168.50.1/24.
Step 2 Configure the in-band management VLAN and IP address for the ONU.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
Issue 01 (2016-04-29)

1118

Access Module

Step 4 Confirm that the connection between the management service ports on the OLT and ONU is
reachable.
l
and ONU. If the OLT receives ICMP ECHO-REPLY packets from the ONU, the
configure the ONU.
----End
12.5.5 Configuring TDM Connections

This topic describes how to configure Native TDM connections between GPON ports and E1/
STM-1 upstream ports to transmit E1/STM-1 private line service data.
Prerequisites
Required hardware is available:
l
TOPA+NH1A for upstream transmission through E1
TOPA+O2CE for upstream transmission through STM-1
GPON board: GPBC, GPBD
Context
The OLT can transmit data to the SDH network through E1 or STM-1 lines. Each E1 line
provides 2 Mbit/s bandwidth. After being mapped, aligned, and encapsulated, 63xE1 signals
are multiplexed into one STM-1 signal through VC12. One STM-1 line provides 155 Mbit/s.
When the OLT transmits data to SDH equipment through STM-1 lines, pay attention to the
VC12 mode and VC12 number.
l
When the OLT is interconnected with Huawei SDH equipment, the VC12 mode is
huawei and the VC12 numbers on the OLT and the SDH equipment must be consistent.
When the OLT is interconnected with Lucent SDH equipment, the VC12 mode is lucent.
The VC12 numbers has the following mapping relationships (which can be queried using
the display vc12-mode-table command):
Huawei: Mapping between the multiplexing number and VC12 number: VC12 number =
(TUG31) + (TUG21) x 3 + (TU121) x 21
Lucent: Mapping between the multiplexing number and VC12 number: VC12 number =
(TU121) + (TUG21) x 3 + (TUG31) x 21
Issue 01 (2016-04-29)

1119

Access Module
Data Plan
Upstream
Transmissio
n Mode
Data
Upstream
transmission
through E1
Port on the TOPA board: 0/5/0
Upstream
transmission
through
STM-1
Daughter board type: NH1A (provides E1 ports)
Daughter board type: O2CE (provides STM-1 ports)

VC12 number: 0
NOTE
The VC12 parameter must match that on the interconnected SDH equipment.
Otherwise, services fail.
Procedure
l
Configure a TDM E1 connection for E1 upstream transmission.

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 gpon 0/3/1 ontid 3
gemportIndex 13
Configure a TDM E1 connection for STM-1 upstream transmission.

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 vc12 0 gpon 0/3/1 ontid 3
gemportIndex 13
----End
12.5.6 Configuring Clock Synchronization

In this scenario, the E1/STM-1 line clock can be used to achieve network-wide clock
synchronization.
Prerequisites
The clock daughter board CKMC/CKMD must be on the SCU main control board.
Context
Configuration roadmap for clock synchronization:
1.
The OLT traces the upstream E1/STM-1 line clock of the TOPA board as the system
clock.
2.
The system clock is delivered to an ONU through optical paths of the GPON board.
3.
The ONU uses the line clock of the GPON upstream port as the system clock.
4.
The ONU E1 transmit clock is synchronized with the system clock of the ONU.
Configure a clock on the OLT.
Procedure
a.
Issue 01 (2016-04-29)
Add a system clock source.

1120

Access Module
Run the clock source command to configure the line clock of E1/STM-1 port 0/5/0
on the TOPA board as the system clock source. Set the ID of the clock source to 0.
The clock module automatically judges the type of the specified clock source (E1/
STM-1) and selects a reference source for phase lock based on priorities.
huawei(config)#clock source 0 0/5/0
b.
Configure a priority for the system clock source.

Run the clock priority command to set the priority of clock source 0 to the highest
priority.
huawei(config)#clock priority system 0
c.
Query configurations and the status of the system clock source.

Run the display clock source system command to query configurations and the
status of the clock source. Ensure that configurations of the system clock source are
correct and the status is Normal.
huawei(config)#display clock source system
----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801TOPA 0/5/0
E1
Normal
0
--YES
-----------------------------------------------------------------------------
Run the display clock mode command to query the clock working mode. Ensure
that the clock daughter board works in tracing mode.
huawei(config)#display clock mode
Clock manage-mode:Third-mode
Clock subboard work-mode:Tracing
Configure a clock on the ONU.

a.
Configure the GPON line clock as the system clock.

The system clock of the OLT is delivered to the ONU through the GPON port on
the OLT, achieving clock synchronization between the OLT and the ONU.
i.
Run the clock source command to configure the clock recovered from the
GPON upstream port as the system clock of the ONU.
ii.
Run the clock priority command to configure the priority of the clock source.

Clock source set succeeded
b.
Configure the system clock as the transmit clock for an E1 port.

i.
Run the interface tdm command to enter the E1 port configuration mode.
ii.
Run the tx clock or port portid udt system command to configure the system
clock as the transmit clock of the port.
iii. Run the display port state command to query the transmit clock of the E1
port.
huawei(config)#interface tdm 0/1
huawei(config-if-tdm-0/1)#port 0 udt system
Issue 01 (2016-04-29)

1121

Access Module
huawei(config-if-tdm-0/1)#display port state 0

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
c.

Run the display clock source command to query configurations and the status of
the system clock source.
huawei(config-if-tdm-0/1)#quit
huawei(config)#display clock source
--------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
--------------------------------------------------------------0
YES
line
0/0/1
Normal
0
YES
1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ---------------------------------------------------------------------
----End

This topic describes how to use the PDH/SDH tester to verify the private line access service.
Prerequisites
The private line service has been configured.
Networking
Figure 12-6 Test setup for E1 upstream service
E1 port
loopback
ONU
OLT
E1 line tester
E1
ONU trace
the clock of
the OLT
Issue 01 (2016-04-29)
OLT trace
the clock of
the tester

Internal
free-run
clock
1122

Access Module
Figure 12-7 Test setup for STM-1 upstream service
E1 port
loopback
ONU
OLT
STM-1 line tester

STM-1
ONU trace
the clock of
the OLT
OLT trace
the clock of
the tester
Internal
free-run
clock
Procedure
Step 1 Set up network environment according to the preceding diagrams for service acceptance tests.
NOTE
Ensure clock synchronization for the test. It is recommended that the tester use the internal free-run clock, the
OLT trace the clock of the tester, and the ONU trace the clock of the OLT.
Step 2 Use the E1 or STM-1 line tester to send packets for the test.
The test duration must be 12 hours or longer. There should be no alarms on the tester and the
bit error rate must be less than 1E-9.
----End
Follow-up Procedure
When the test on service connectivity fails, you can check for the failure causes by
performing loopbacks. The following loopbacks are supported:
l
Remote loopback on the OLT TOPA board
Local loopback on the OLT TOPA board
Local loopback on the ONU
Remote loopback on the ONU
Issue 01 (2016-04-29)

1123

Access Module
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
TOPA
board
Loops back
signals to the
network side on
the TOPA board
on the OLT. This
loopback checks
whether the
service from the
TOPA board to
the network-side
channel is
normal.
Local
loopba
ck on
the
TOPA
board
Local
loopba
ck on
the
ONU
Issue 01 (2016-04-29)
Loops back
signals to the
user side on the
TOPA board on
the OLT. This
loopback checks
whether the link
between the
TOPA board and
the E1 port on
the ONU is
normal.
Loops back
signals to the
network side on
the ONU. This
loopback checks
whether the link
between the E1
port on the ONU
and the TOPA
board on the
OLT is normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
Enable/Disable the remote

loopback for the E1 port.
huawei(config)#interface
top 0/5
huawei(config-iftop-0/5)#loopback 0
remote
huawei(config-iftop-0/5)#undo loopback 0
Remote loopback

loopback for the STM-1 port.
top-stm1 0/5
huawei(config-if-topstm1-0/5)#loopback 0
remote
huawei(config-if-topstm1-0/5)#undo loopback 0
E1 line
tester
ONU
OLT
E1
Local loopback
Enable/Disable the local

top 0/5
huawei(config-iftop-0/5)#loopback 0 local

top-stm1 0/5
local
ONU
E1 line
tester
OLT
E1
Local loopback

tdm 0/1
huawei(config-iftdm-0/1)#loopback 0 local
huawei(config-iftdm-0/1)#undo loopback 0
1124

Access Module
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
ONU
Loops back
signals to the
user side on the
ONU. This
loopback checks
whether the link
between the
ONU and user
terminal is
normal.
Networking
E1 line
tester
ONU
Configuration
OLT
E1
Remote loopback
tdm 0/1
huawei(config-iftdm-0/1)#loopback 0
remote
12.6 Configuring Enterprise IP PBX Private Line Access

Service (GPON)
ONUs provide GE/FE ports to access IP private branch exchange (PBX) services of an
the packet switched network (PSN). This achieves unified carrying of voice, data, and video
services.

Service Requirement
l
The IP private branch exchange (PBX) data can be transparently transmitted on the PON
network.
The operation method for end users connected to the IP PBX is not changed.
As shown in Figure 12-8, ONUs access IP PBX services through FE/GE ports. The OLT
transparently transmits the data to the IP network in QinQ mode.
Applicable ONUs: MA5612, MA5628, MA5616, MA5694, MA5698
Issue 01 (2016-04-29)

1125

Access Module
Figure 12-8 Networking diagram of the IP PBX access service

IP PBX
FE/G
E
ONU
OLT
IP network
GE/10GE
E
FE/G
Splitter
NGN/IMS
ONU
IP PBX

The following figure shows the configuration process for the IP PBX access service.
Issue 01 (2016-04-29)

1126

Access Module
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring OLT QinQ

Service Ports
Policies
ONU Side
Verifying IP PBX Services
End

Issue 01 (2016-04-29)

1127

Access Module
Context
l
Data Planning
Configurati
on Item
Data
DBA profile
Profile ID: 20
Line profile
Profile ID: 10
T-CONT ID: 4
GEM port ID for other services: 12
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.

2.

to DBA profile 20
huawei(config-gpon-lineprofile-10)#gem add 12 eth tcont 4 //Add GEM port 12
to T-CONT 4
huawei(config-gpon-lineprofile-10)#gem mapping 12 1 vlan 300 //Map GEM port
12 to CVLAN 300
3.
Issue 01 (2016-04-29)
1128

Access Module

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)
1129

Access Module

ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
reachable.
l
Issue 01 (2016-04-29)
1130

Access Module
configure the ONU.
----End
12.6.5 Configuring OLT QinQ Service Ports

This topic describes how to configure QinQ service ports on the OLT to add an SVLAN tag to
IP PBX packets sent from ONUs and transmit the packets to the upper-layer IP network.
Data Plan
For details on VLAN planning, see 12.3.2 Principle of VLAN Data Plan. VLAN translation
policies for the Enterprise IP private branch exchange (PBX) access service are shown in
Figure 12-9. Different data packets of the IP PBX carry different user VLANs (for example,
20, 21, ... in the following figure). The user VLANs are translated to CVLAN 300 on the
ONU and then the OLT adds the outer VLAN 1300 to the packets before transmitting them
upstream.In this manner, only two VLANs are required on the MAN for the base station
access service, which significantly reduces the number of VLANs.
Figure 12-9 VLAN translation process
Configuration Item
Data
SVLAN
VLAN ID: 1300

VLAN attribute: q-in-q
CVLAN (upstream
VALN of the ONU)
300
Traffic profile
Profile ID: 10
Default priority: 4
NOTE
Because packets transmitted from the OLT carry two VLAN tags, the interconnected equipment on the metro
network must be able to identify and restore packets with two VLAN tags.
Issue 01 (2016-04-29)

1131

Access Module
Procedure
Set the SVLAN ID of the IP PBX service to 1300, VLAN type to smart, VLAN attribute to
QinQ, and add upstream port 0/19/0 to the VLAN.
Step 2 Configure a traffic profile for the service port.

Step 3 Configure a QinQ service port.

According to 12.3.2 Principle of VLAN Data Plan, VLANs of packets sent from the IP PBX
are all translated to CLVAN 300. Then, the OLT adds an SVLAN tag to the packets:
CVLAN<->SVLAN+CVLAN. Traffic profile 10 is used.
NOTE
If you need to transparently transmit the CVLAN to SVLAN, then user qinq SVLAN, set SVLAN=CVLAN,
and creat a service-port with "tag-transform transparent".
----End
12.6.6 Configuring Ethernet Access Service Ports on ONUs

This topic describes how to configure service ports on ONUs and upstream VLANs to make
the connections between ONUs and user terminals reachable and create upstream channels
between ONUs and the OLT, achieving access of IP PBX services through Ethernet ports.
Data Planning
Configuration
Item
Data
Port

Service port: 0/3/1
SVLAN
VLAN ID: 300

VLAN type: smart
Traffic profile
Profile ID: 8
Assured rate: no rate limit
Default priority: 4
Issue 01 (2016-04-29)

1132

Access Module
Procedure
Step 1 Remotely log in to an ONU to configure the ONU.
root (default); password: admin123 (default)
Step 2 Create an SVLAN 300.
Step 3 Add upstream port 0/0/1 to the SVLAN.


Configure traffic profile 8. The upstream and downstream rates are not limited. Packets
transmitted upstream use the priority (4 by default) copied from the user side. Packets

Add a service port and bind it to port 0/3/1. Set the user VLAN to untagged and bind it to
traffic profile 8.
NOTE
Packets sent from the user side (IP PBX) may be transmitted upstream with a VLAN tag. In this case, change
untagged to the VLAN tag when configuring a service port.
----End

Context
is recommended.
NOTE
Procedure
l
Issue 01 (2016-04-29)

1133

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)

1134

Access Module
i.

ii.


----End

Context
l
time.
NOTE
Procedure
l


timedelay enable

Issue 01 (2016-04-29)

1135

Access Module
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
Issue 01 (2016-04-29)

1136

Access Module
The ONU ID is 1.



Figure 12-12 shows the networking diagram for the Type C dual homing protection.
Two PON ports on different OLTs, two PON ports on an ONU, two backbone optical
fibers, two optical splitters, and two tributary optical fibers are configured to implement
this protection. The difference between this protection scheme and the Type C single
homing protection scheme is that the ONU needs to be dual homed to two OLTs in this
protection scheme.
Issue 01 (2016-04-29)

1137

Access Module
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
The ONU ID is 1.


----End

This topic describes how to verify the IP PBX access service by testing calls.
Issue 01 (2016-04-29)

1138

Access Module
Prerequisites
The IP PBX access service has been deployed.
Procedure
Step 1 Test calls between users connected to the IP PBX according to table 1.
Step 2 Test calls from a user connected to the IP PBX to an IMS user according to table 1.
Step 3 Test calls from an IMS user to a user connected to the IP PBX according to table 1.
Table 12-5 IP PBX access service verification
Categ
ory
Test Calls Between

Users Connected to
the IP PBX
Test Calls from a User

Connected to the IP
PBX to an IMS User
Test Calls from an IMS

User to a User
Connected to the IP
PBX
Prereq
uisites
1. User A and user B

access the network
through the IP
PBX and both
users have been
registered.
1. User A accesses the

network through the IP
PBX and has been
registered.
1. User A is a common
IMS user and has been
registered.

are idle.
Test
proced
ure
1. User A calls user

B.
2. User B answers
the call. Check the
call between user
A and user B.
2. User B is a common
IMS user and has been
registered.
2. User B accesses the

network through the IP
PBX and has been
registered.
3. User A and user B are

idle.

idle.
The same as that in the

"Test Calls Between Users
Connected to the IP PBX"
column

column

column

column
3. User A releases
the call.
Expect
ed
result
1. User B hears the

ringing tone.
2. The call is set up.
3. The call is
released.
----End
12.7 Configuring Enterprise PRA PBX Private Line Access

Service (GPON)
ONUs provide PRA E1 ports to access PRA private branch exchange (PBX) services of an
Issue 01 (2016-04-29)

1139

Access Module
the packet switched network (PSN). This achieves voice-to-IP conversion, simplifying the
network architecture.

Service Requirement
PRA PBX is a telephone exchange used in an enterprise. With the PRA PBX, staff in the
enterprise can use internal telephones to make free calls by dialing short numbers. Outgoing
calls are made through a unified trunk. After the PRA PBX service is accessed in PON mode
using "OLT+ONU", VoIP calls can be made. Compared with services provided by the PRA
PBX itself, the VoIP service has following advantages:
l
Outgoing call data is carried over IP, which greatly lowers communication costs for
enterprises and retains good call quality.
No extra investment is required because the voice service is deployed directly using the
PRA PBX.
Free calls can be made between branches in different regions.
More value-added services can be provided based on IP networks.
In addition, the operation method for end users connected to the PRA PBX is not changed.
As shown in Figure 12-13, ONUs access PRA PBX services through E1 lines. The OLT
transmits the data to the upper NGN/IMS, achieving the VoIP-based PRA voice service.
Applicable ONU: MA5612, MA5616.
Figure 12-13 Networking diagram of the PRA PBX access service
PRA PBX
E1
ONU
OLT
IP network
GE/10GE
Splitter
E1
NGN/IMS
ONU
PRA PBX

The following figure shows the configuration process for the PRA PBX access service.
Issue 01 (2016-04-29)

1140

Access Module
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring Transparentlytransmitted Voice Service
Ports
Policies
Configuring VoIP PRA

Services
ONU Side
Verifying PRA PBX
Services
End

Context
l
Issue 01 (2016-04-29)
1141

Access Module
Data Planning
Configurati
on Item
Data
DBA profile
Profile ID: 20
Line profile
Profile ID: 10
T-CONT ID: 4
GEM port ID for other services: 12
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.

2.

to DBA profile 20
to T-CONT 4
12 to CVLAN 300
3.

1.
Issue 01 (2016-04-29)

1142

Access Module

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.

Issue 01 (2016-04-29)

1143

Access Module
ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
reachable.
l
configure the ONU.
----End
Issue 01 (2016-04-29)

1144

Access Module
12.7.5 Configuring Service Ports for Voice Transparent

Transmission
This topic describes how to create service ports on the OLT to transparently transmit VoIP
service data from ONUs to the upper-layer voice server.
Data Plan
Configuration Item
Data
SVLAN
VLAN ID: 300

CVLAN (upstream VALN of

the ONU)
300
Traffic profile
Profile ID: 10
Default priority: 5
NOTE
The VoIP service is a self-operated service. The single SVLAN is a mainstream application and is
recommended.
Procedure
Set the SVLAN ID of the PRA PBX service to 300, VLAN type to smart, and add upstream
port 0/19/0 to the VLAN.
Step 2 Configure a traffic profile for the service port.


According to 12.3.2 Principle of VLAN Data Plan, VLANs of packets sent from the PRA
PBX are all translated to CLVAN 300. The OLT transparently transmits the packets. The
traffic profile 10 is used.
----End
Issue 01 (2016-04-29)

1145

Access Module
12.7.6 Configuring VoIP PRA Access

This topic describes how to configure VoIP PRA access. ONUs provide PRA E1 ports to
access the PRA PBX service and convert PRA signaling to ISDN Q.931-User Adaptation
Layer (IUA) signaling, achieving signaling exchange between ONUs and media gateway
controller (MGCs).
Prerequisites
The H.248 protocol is a master/slave protocol which is used by an MGC to control access
gateways (AGs) to implement call connections. The data, including media gateway (MG)
interface attributes and voice user attributes on AGs, must be consistent with those on the
MGC. Therefore, before configuring the VoIP voice service, plan data with the MGC.
Context
IUA is the ISDN Q.931-User Adaptation Layer protocol. IUA links carry signaling exchanged
between ONUs and MGCs.
Data Plan
Table 12-7 Data plan for VoIP PRA service
Configuration
Item
Data
VLAN
VLAN ID: 300

IP address of the Layer 3 interface: 10.10.10.10/24
MG interface
MG ID: 0
Media/signaling IP address: 10.10.10.10/24
MGC IP address: 200.200.200.200
Gateway IP address: 10.10.10.1
Protocol port: 2944
IUA linkset
IUA link set ID: 1

Working mode of the link set: override
Interface ID (IID) generation mode: 2
Service environment of the IUA link set: client
Interlocking function: enabled
IUA link
IUA link ID: 0

Local port ID: 1402
Local IP address: 10.10.10.10
Remote port ID: 1404
Remote IP address for the primary MGC: 200.200.200.200
Interlocking policy: the link switches over with the primary MAC
Issue 01 (2016-04-29)

1146

Access Module
Configuration
Item
Data
PRA port
Subrack ID/slot ID/port ID: 0/1/0

Terminal ID: 512
Procedure
Step 1 Configure an upstream VLAN and VLAN interface.
Specify an upstream VLAN interface for the media stream and signaling flow, and set the IP
addresses of the Layer 3 interface. These IP addresses are the sources of the media and
signaling IP address pools.
1.
Create an upstream VLAN 300 and add upstream port 0/0/1 to the VLAN.
2.
Configure the IP address of Layer 3 interface.

Enter the VLAN interface mode and set the IP address of the Layer 3 interface to
10.10.10.10.

The media and signaling IP addresses are 10.10.10.10, and the media gateway IP address is
10.10.10.1.
huawei(config)#voip
NOTE
The media IP address can be different from the signaling IP address. You can make data plan according
to the actual network situation.
Step 3 Configure a static route.

Because the IP address of the VLAN interface and the IP address of the MGC
(200.200.200.200/24) are in different network segments, a route from gateway 10.10.10.1 to
200.200.200.0 network segment must be configured.
Step 4 Add an MG interface and configure interface attributes.

1.
Add an MG interface for the MG to communicate with the MGC, which ensures that the
MGC can control call connections through the MG interface. Add MG interface 0
according to the data plan.
2.
Configure MG interface attributes.

Configure MG interface attributes according to the data plan. When configuring the
attributes, note that:
Issue 01 (2016-04-29)

1147

Access Module
The registration mode of the MG interface must be consistent with that on the
MGC. Registration mode: by IP address (default) or by domain name
H.248 version for negotiation: H.248v1, H.248v2, or H.248v3 (default). When H.

248v3 is used, interfaces fail to be registered if some softswitches do not support H.
248v3.

3.
Enable the MG interface.

NOTE
4.
After configuring the MG interface, you must perform a cold reset on the interface. Otherwise, the
interface cannot take effect.
You can perform a cold reset on the MG interface only after the following parameters are correctly
configured: mgip, mgport, primary-mgc-ip1 (or mgc-domain-name1), mgcport_1, code,
transfer, and mg-media-ip.

If the MG interface is interconnected with the MGC successfully, the MG interface is in
normal state which indicates that the interface is working properly.
------------------------------------------------------------------------MGID
Trans
State
MGPort MGIP
------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.10
2944
200.200.200.200
-------------------------------------------------------------------------
Step 5 Configure IUA links.

In the sigtran mode, configure the Signaling Transport protocol stack. Add an IUA link set
first and then add IUA links.
override iid-map 2 cs-mode client
jointly-work-with primary-mgc
Step 6 Add ISDN PRA user.

huawei(config-esl-user)#mgprauser add 0/1/0 0 1 interfaceid 0 terminalid 512
----End

Context
is recommended.
Issue 01 (2016-04-29)

1148

Access Module
NOTE
Procedure
l

i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
Issue 01 (2016-04-29)

1149

Access Module
iv.


i.

ii.


----End

Context
l
time.
NOTE
Procedure
l


timedelay enable
Issue 01 (2016-04-29)

1150

Access Module

ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
Issue 01 (2016-04-29)

1151

Access Module
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
The ONU ID is 1.



protection scheme.
Issue 01 (2016-04-29)

1152

Access Module
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
The ONU ID is 1.


----End

This topic describes how to verify the PRA PBX service by testing calls.
Issue 01 (2016-04-29)

1153

Access Module
Prerequisites
The PRA PBX access service has been deployed.
Procedure
Step 1 Test calls between users connected to the PRA PBX according to table 1.
Step 2 Test calls from a user connected to the PRA PBX to an MGC user according to table 1.
Step 3 Test calls from an MGC user to a user connected to the PRA PBX according to table 1.
Table 12-8 PRA PBX access service verification
Categ
ory
Test Calls Between

Users Connected to
the PRA PBX
Test Calls from a User

Connected to the PRA
PBX to an MGC User
Test Calls from an

MGC User to a User
PBX
Prereq
uisites

access the network
through the PRA
PBX and both
users have been
registered.
1. User A accesses the

network through the
PRA PBX and has been
registered.
1. User A is a common
MGC user and has
been registered.

are idle.
Test
proced
ure
1. User A calls user

B.
2. User B answers
the call. Check the
call between user
A and user B.
2. User B is a common
MGC user and has been
registered.
2. User B accesses the

network through the
PRA PBX and has
been registered.

idle.

idle.

PBX" column

PBX" column

PBX" column

PBX" column
3. User A releases
the call.
Expect
ed
result
1. User B hears the

ringing tone.
2. The call is set up.
3. The call is
released.
----End
Issue 01 (2016-04-29)

1154

Access Module
12.8 Configuring Enterprise E1 Unified Access Service

(GPON)
ONUs transmit E1 signals of enterprises to OLTs in SAToP mode and OLTs are

Service Requirement
l
Existing SDH resources are utilized efficiently. In this way, carriers' existing investments
are protected and enterprise users in different regions are won.
Services are received over optical fibers, reducing investment in copper cables between
enterprises and the SDH network.
The standardized user-side ports facilitate deployment and maintenance.
As shown in Figure 12-17, the ONU accesses enterprise E1 service through standardized
hardware ports, and transmits data to the OLT over the GPON line after performing structureagnostic time division multiplexing over packet (SAToP) encapsulation on the service. After
receiving the signals, the OLT restores E1 signals and transmits the signals to the SDH
network.
l
For carriers, with this networking, they can win enterprise users with GPON lines which
support long-distance transmission and high bandwidth. With the trend of fiber-in and
copper-out, deployment of GPON lines can reduce deployment costs of copper cables
and support service expansion.
For enterprise users, with GPON access, they can reduce fees spent in leasing lines.
Figure 12-17 E1 access in SAToP mode

OLT
Enterprise
ONU
E1/
STM-1
E1
TDM
E1
SDH
Splitter
SAToP
E1/STM-1

The following figure shows the configuration process for E1 enterprise private line.
Issue 01 (2016-04-29)

1155

Access Module
Start
Adding ONUs to OLT
and ONUs
OLT Side
Configuring SAToP
Connections and Service
Ports
Policies
Configuring Network
Protection
Configuring SAToP
Connections
ONU Side
Configuring Clock
Synchronization
Verifying Services
End
Issue 01 (2016-04-29)

1156

Access Module

ONUs can be configured only after they are added to the OLT successfully.
Context
l
Data Plan
Item
Data
DBA profile
Profile ID: 20
Profile type: Fixed bandwidth and minimum delay
DBA bandwidth:
E1 access: 32 Mbit/s is recommended. (Each ONU accesses four E1
private lines and each line has a recommended DBA bandwidth of 8
Mbit/s)
Line profile
Profile ID: 10
T-CONT ID: 1
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.
Configure a DBA profile. and set the DBA bandwidth allocation mode for the GPON
port to minimum bandwidth delay.
For example, configure the DBA profile for 4-channel E1 private line.
2.

to DBA profile 20
Issue 01 (2016-04-29)

1157

Access Module
to T-CONT 1
12 to CVLAN 300
3.

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

1158

Access Module

ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
Issue 01 (2016-04-29)

1159

Access Module

reachable.
l
configure the ONU.
----End
12.8.5 Configuring SAToP Connections and Service Ports

This topic describes how to configure a SAToP connection of the IP+UDP encapsulation type
and a service port to enable packets of enterprise to be encapsulated on ONUs and restored on
OLTs.
Prerequisites
l
Main control boards on the OLT: SCUN+CKMC/CKMD
Upstream board on the OLT: EDTB (for E1 upstream transmission)
Context
Figure 12-18 shows SAToP encapsulation for enterprise E1 unified access service. As shown
in the following figure, after TDM signals are encapsulated in the IP+UDP format, an outer
VLAN tag and an Ethernet header are added to the TDM signals. Then the TDM signals
become a standard Ethernet packet that is transmitted on the PON line between the ONU and
OLT.
Figure 12-18 SAToP encapsulation
Enterprise
OLT
E1/T1
ONU
SDH
T1
SAToP
T1
E1
SAToP
E1/STM-1
TDM
Issue 01 (2016-04-29)
TDM
TDM
UDP1
UDP1
IP1
IP1
VLAN
VLAN
ETH
ETH

TDM
1160

Access Module
Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
Board IP address: 10.10.50.10
Board MAC address: dynamically obtained (remark 1)
Local UDP port number: 50048 (remark 2)
E1 port
(ONU)

UDP port number: 50048 (remark 2)
VLAN
SVLAN: 300
Remark 1: MAC address configuration modes (statically configured or dynamically obtained)

at two ends must be consistent to establish a SAToP connection. It is recommended that MAC
addresses be dynamically obtained, which facilitates configuration and maintenance.
Remark 2: The UDP port cannot be a port that is widely used in the industry and for specific
services. For example, port 80 is used for HTTP service. The dynamic and private ports are
recommended.
Procedure
Step 1 Configure EDTB board attributes.
Set the board working mode to SAToP.
huawei(config-if-edt-0/5)#board workmode satop
Configure the access mode and frame format.

l
E1 access:
huawei(config-if-edt-0/5)#tdm access-mode E1
Configure the IP address of the E1 port on the EDTB board.

huawei(config-if-edt-0/5)#set ip-address 10.10.50.10
huawei(config-if-edt-0/5)#quit
Step 2 Create a SAToP connection.

Create TDM VCL 10.
l
For E1 access, set the TDM VCL type to SAToP.

huawei(config)#tdm-vcl tdm-vcl-id 10 satop 0/5/0
Create a SAToP connection at the E1 port 0/5/0. Set SVLAN to 300, local UDP port number
to 50048, remote IP address (the IP address of the E1 access board on the ONU) to
10.10.50.20, and remote UDP port number to 50048. The remote MAC address is obtained
dynamically.
Issue 01 (2016-04-29)

1161

Access Module
NOTE
To create a SAToP connection, the local UDP port number must be consistent with the remote UDP port
number, that is, [ local-udp = portid of EDTB + Cardinal number (50048) ].
huawei(config)#cesop-connect tdm 10 vlan 300 local-udp 50048 remote-ip
10.10.50.20 remote-udp 50048
You can also create a SAToP connection by configuring the MAC address statically. If the
remote MAC address (the MAC address of the E1 access board on the ONU, which can be
queried by running the display cesop-mac-address command on the ONU) is 00e0fc01-0450, create a SAToP connection in static mode as follows:
huawei(config)#cesop-connect tdm 10 vlan 300 local-udp 50048 remote-mac
00e0-fc01-0450 remote-ip 10.10.50.20 remote-udp 50048
Step 3 (Optional) Configure attributes of the SAToP connection.

NOTE
The attributes of the SAToP connection on the OLT must be consistent with those on the ONU. Generally, use
the system default values.
Run the cesop rtp command to configure whether the SAToP packet carries the RTP
header. The SAToP packet carries the RTP header by default.
Run the cesop encap command to configure SSRC, payload type, and SN of the SAToP
packet. The default value of these parameters is 0.
Run the cesop jitter-buffer command to configure the buffer depth of the SAToP packet.
The default buffer depth is 2000 s.
Run the cesop loadtime command to configure the load time of the SAToP packet. The
default load time is 125 s.
Run the cesop priority command to configure the priority of the SAToP packet. The
default priority is 7.

Set the service port ID to 1, SVLAN ID to 300, GEM port ID to 12, and user VLAN ID to
300. The ONU limits upstream and downstream traffic rates but the OLT does not. Therefore,
use default traffic profile 6.
The user VLAN must be the same as the upstream VLAN of the ONU.
----End
12.8.6 Configuring ONU SAToP Connections

and a service VLAN to enable packets of base stations to be encapsulated on ONUs as
Ethernet packets and then forwarded based on VLANs and MAC addresses.
Issue 01 (2016-04-29)

1162

Access Module
Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
E1 port
(ONU)

VLAN
SVLAN: 300

recommended.
Procedure
Create the upstream VLAN 300, and add upstream port 0/0/1 to VLAN 300.
Step 2 Configure E1 port attributes.

Configure the IP address of TDM service board 0/1 as 10.10.50.20.
huawei(config-if-tdm-0/1)#set ip-address 10.10.50.20
Configure the board and port working mode and transmit clock.
l
For E1 access, set the working mode to UDT and configure the transmit clock as the
system clock.
huawei(config-if-tdm-0/1)#tdm access-mode E1

Create TDM VCL 10.
l

Create a SAToP connection at TDM port 0/1/0. Set SVLAN to 300, local UDP port number to
50048, remote IP address (the IP address of the EDTB board on the OLT) to 10.10.50.10, and
remote UDP port number to 50048. The remote MAC address is obtained dynamically.
Issue 01 (2016-04-29)

1163

Access Module

10.10.50.10 remote-udp 50048
NOTE
You can also create a SAToP connection by configuring the MAC address statically. If the remote MAC
address (the MAC address of the EDTB board on the OLT) is 0800-3E32-5310, create a SAToP connection in
static mode as follows:
0800-3E32-5310 remote-ip 10.10.50.10 remote-udp 50048

NOTE
----End

In this scenario, the E1 line clock can be used to achieve network-wide clock synchronization.
Prerequisites
The CKMC/CKMD clock daughter board has been installed on the SCU main control board.
Context
1.
The OLT traces the upstream E1 line clock of the EDTB board as the system clock.
2.
3.
4.
Procedure
a.

Configure the E1 line clock input from port 0/5/0 on the EDTB board as the system
clock 0. Set the priority to 0 (highest priority).
b.
Issue 01 (2016-04-29)

1164

Access Module
----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H802EDTB 0/5/0
E1
Normal
0
--YES
-----------------------------------------------------------------------------

a.

i.
ii.

b.

i.
ii.
port.
--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
c.
Issue 01 (2016-04-29)

1165

Access Module
--------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
--------------------------------------------------------------0
YES
line
0/0/1
Normal
0
YES
1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ---------------------------------------------------------------------
----End

Context
is recommended.
NOTE
Procedure
l

i.
ii.


Issue 01 (2016-04-29)

1166

Access Module


i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


i.

ii.


----End
12.8.9 Configuring Network Protectio

The base station access service has high requirements on reliability. Therefore, network
protection solutions must be configured in the upstream and downstream directions.
Issue 01 (2016-04-29)

1167

Access Module
Context
The protection solutions supported in this scenario are Type B protection and Type C singlehoming protection.
Procedure
l

ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
Issue 01 (2016-04-29)

1168

Access Module
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
The ONU ID is 1.


----End

Prerequisites
Issue 01 (2016-04-29)

1169

Access Module
Networking
E1 port
loopback
ONU
OLT
E1 line tester
E1
ONU trace
the clock of
the OLT
OLT trace
the clock of
the tester
Internal
free-run
clock
Procedure
NOTE
Step 2 Use the E1 line tester to send packets for the test.
----End
Follow-up Procedure
l
Remote loopback on the OLT EDTB board
Local loopback on the OLT EDTB board
Issue 01 (2016-04-29)

1170

Access Module
Issue 01 (2016-04-29)
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
EDTB
board
Loops back
signals to the
network side on
the EDTB board
on the OLT. This
loopback checks
whether the
service from the
EDTB board to
the network-side
channel is
normal.
Local
loopba
ck on
the
EDTB
board
Loops back
signals to the
user side on the
EDTB board on
the OLT. This
loopback checks
whether the link
between the
EDTB board
and the E1 port
on the ONU is
normal.
Local
loopba
ck on
the
ONU
Loops back
signals to the
network side on
the ONU. This
loopback checks
whether the link
between the E1
port on the ONU
and the EDTB
board on the
OLT is normal.
Remote
loopba
ck on
the
ONU
Loops back
signals to the
user side on the
ONU. This
loopback checks
whether the link
between the
ONU and user
terminal is
normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
edt 0/5
huawei(config-ifedt-0/5)#loopback 0
remote
huawei(config-ifedt-0/5)#undo loopback 0
Remote loopback
E1 line
tester
ONU
OLT
E1
Local loopback
ONU
E1 line
tester
OLT
E1
Local loopback
E1 line
tester
ONU

OLT
E1
Remote loopback


edt 0/5
huawei(config-ifedt-0/5)#loopback 0 local
tdm 0/1
tdm 0/1
remote
1171

Access Module
12.9 Configuring Enterprise E1 Unified Access Service

(OLT Cascading, GPON)
ONUs access enterprise TDM service in E1 access mode, and transmits the data to the SDH
network in OLT cascading mode over the GPON network which supports long-distance
transmission and high bandwidth. In this way, uniform deployment of E1 service is achieved.

Service Requirement
l
Existing SDH resources are utilized efficiently. In this way, carriers' existing investments
are protected and enterprise users in different regions are won.
Services are received over optical fibers, reducing investment in copper cables between
enterprises and the SDH network.
The standardized user-side ports facilitate deployment and maintenance.
As shown in Figure 12-22, a carrier's SDH network is migrated gradually. In a city, there are
only some nodes (for example, OLT_A in the following figure) can transmit signals upstream
to the SDH network through STM-1 ports, and other nodes (for example, OLT_B in the
following figure) must access SDH resources through GE/10GE ports. In this scenario,
ONU_B accesses the E1 service in SAToP mode, and transmits the service to the OLT at the
local site (OLT_B) over the GPON line. OLT_B transparently transmits the service to another
OLT with SDH resources (OLT_A) through GE/10GE ports.
l
For carriers, with this networking, they can win enterprise users who have no SDH
resources with GPON lines which support long-distance transmission and high
bandwidth. With the trend of fiber-in and copper-out, deployment of GPON lines can
reduce deployment costs of copper cables and support service expansion.
For enterprise users, with GPON access, they can reduce fees spent in leasing lines.
Figure 12-22 E1 access in SAToP mode (OLT cascading)

OLT_A
E1/
STM-1
E1
TDM
ONU
E1
TDM
E1
Issue 01 (2016-04-29)
L2
G
10 E/
GE
OLT_B
Enterprise
SDH
Splitter
Splitter
SAToP

E1/
STM-1
1172

Access Module

The following figure shows the configuration process for the E1 unified access service (OLT
cascading).
OLT_A
OLT_B
ONU
Start
Start
Start
Configure cascading
with OLT_B
Adding ONUs to OLT
Configuring ONU
SAToP Connections
Configuring SAToP
Connections between
OLT_A and ONU
Configuring
Management and
Service Channel
Configuring Clock
Synchronization
End
Functions of different network element are listed in the table below.

Network
element
Functions
OLT_A
1. In the downstream direction, creates SAToP connections with ONU_B; in

the upstream direction, restores E1 signals and transmits the signals to the
SDH network.
2. Cascaded with OLT_B and transmits clock synchronization information
downstream.
OLT_B
1. Transmits SAToP-encapsulated packets in GEM frames over the GPON

line.
2. Transmits SAToP packets to OLT_A in Ethernet mode for decapsulation.
3. Transmits clock synchronization information to ONU_B.
ONU_B
1. Access the E1 private line service.

2. Create the SAToP connection between ONU_B and OLT_A.
3. Transmits SAToP packets to OLT_B by PON line.
4. Transmits clock synchronization information to enterprise.
Issue 01 (2016-04-29)

1173

Access Module
12.9.3 Configure OLT_A cascading with OLT_B

Prerequisites
Required hardware for OLT_A is ready.
l
Control board: SCUN+CKMC/CKMD
GPON service board: GPBD
Upstream board: EDTB
Cascaded service board:
GE port: GICK or OPGD
10GE port: X2CS
Data Plan
Table 12-10 provides the key data plan.
Table 12-10 Key data plan for OLT_A
Item
Data
Remarks
OPGD
Port: 0/2/1
Assume that OLT_A is cascaded with OLT_B using the

OPGD board. Then you need to set the network role of the
OPGD board to cascade.
VLA
N ID
and IP
addres
s
In-band management
VLAN ID: 8
To telnet to another OLT or ONU from the OLT and then

configure the OLT or ONU, you must configure the inband management VLANs and IP addresses of the OLT
on the OLT.
In-band management
IP address:
192.168.50.30/24
If the management IP address and the IP address of

OLT_B or ONU_B are not in the same network segment,
you also need to configure routes.
Procedure
Step 1 Configure the management VLAN and IP address.
Create management VLAN 8, and set the management IP address to 192.168.50.30 and
subnet mask to 255.255.255.0.
Step 2 Configure cascading with OLT_B.

Cascade OLT_A and OLT_B through GE port 0/2/1 on the OPGD board. Set the port attribute
to cascade, and add the cascading port to VLAN 300.
Issue 01 (2016-04-29)

1174

Access Module

----End
12.9.4 Configuring SAToP Connections between OLT_A and

ONU
Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
E1 port
(ONU)

VLAN
SVLAN: 300

recommended.
Procedure

l
E1 access:


Create TDM VCL 10.
Issue 01 (2016-04-29)

1175

Access Module

dynamically.
NOTE
10.10.50.20 remote-udp 50048

NOTE
----End
12.9.5 Adding ONUs to OLT_B

Issue 01 (2016-04-29)

1176

Access Module
Data Plan
Item
Data
DBA profile
Profile ID: 20
DBA bandwidth:
Mbit/s)
Line profile
Profile ID: 10
T-CONT ID: 1
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.
2.

to DBA profile 20
to T-CONT 1
12 to CVLAN 300
3.
Issue 01 (2016-04-29)
1177

Access Module

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)
1178

Access Module
12.9.6 Configuring Management and Service Channel on OLT_B

and ONU
After the management service ports is added, you can log in to the ONUs on the OLT and
configure the ONUs. After the GPON service port is added, E1 traffic stream are able to
transmitted upstream to OLT_B.
Prerequisites
Required hardware for OLT_B (cascading) is ready.
l
Control board: SCUN+CKMC/CKMD
GPON service board: GPBD
Upstream board:
GE port: GICK
10GE port: X2CS
Data Plan
Item
Data
Management VLAN and

management IP address for OLT

Service VLAN
300
Management VLAN and

management IP address for ONU

Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

Issue 01 (2016-04-29)

1179

Access Module
profile 6.
reachable.
l
configure the ONU.
Step 5 Configure the upstream port.

Add upstream port 0/19/0 (on the GICK board) to VLAN 100.
Step 6 Configure the GPON service port.

Set SVLAN ID to 300, GEM port ID to 12, and CVLAN ID to 300. Rate limit for upstream
and downstream packets is performed on the ONU instead of on the OLT. Therefore, use
traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip
command to add a traffic profile and bind it to the service port.
The CVLAN must be the same as the upstream VLAN of the ONU.
----End
12.9.7 Configuring ONU SAToP Connections

Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
E1 port
(ONU)

VLAN
Issue 01 (2016-04-29)
SVLAN: 300
1180

Access Module

recommended.
Procedure

l
system clock.

Create TDM VCL 10.
l

10.10.50.10 remote-udp 50048
NOTE

NOTE
Issue 01 (2016-04-29)
1181

Access Module
----End

Context
Configuration concept for clock synchronization:
1.
OLT_A traces the upstream E1 line clock of the EDTB board as the system clock.
2.
OLT_B Obtains the system clock by GICK/X2CS boards in synchronous Ethernet mode.
3.
4.
The Tx clock of ONU is synchronized to the system clock of the ONU.
Data Plan
System
clock
Clock source
Description
OLT_A
E1 line clock: 0/5/0
OLT_A Obtains E1 line clock from SDH as the

system clock. and then transmits it to the cascading
OLT_B over GE/10GE interface.
OLT_B
Synchronous ethernet
line clock: 0/19/0
OLT_B Obtains the system clock in synchronous

Ethernet mode. The clock is transmitted to the
ONU over the GPON line.
ONU
GPON line clock:

0/0/1
ONU uses the line clock of the GPON upstream

port as the system clock.
Procedure
Step 1 Cofnigure a clock on OLT_A.
1.

2.
Issue 01 (2016-04-29)

1182

Access Module
Run the display clock source system command to query configurations and the status of
the clock source. Ensure that configurations of the system clock source are correct and
the status is Normal.
-----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
-----------------------------------------------------------------------------0
H802EDTB 0/5/0
E1
Normal
0
--YES
------------------------------------------------------------------------------
Run the display clock mode command to query the clock working mode. Ensure that the
clock daughter board works in tracing mode.
Step 2 Cofnigure a clock on OLT_B.

Obtain the system clock through the GICK board in synchronous Ethernet mode. The clock is
transmitted to the ONU over the GPON line.
Step 3 Configure a clock on the ONU.

1.

The system clock of the OLT is delivered to the ONU through the GPON port on the
OLT, achieving clock synchronization between the OLT and the ONU.
a.
Run the clock source command to configure the clock recovered from the GPON
upstream port as the system clock of the ONU.
b.

2.

a.
b.
Run the tx clock or port portid udt system command to configure the system clock
as the transmit clock of the port.
c.
Run the display port state command to query the transmit clock of the E1 port.

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
Issue 01 (2016-04-29)

1183

Access Module
3.

Run the display clock source command to query configurations and the status of the
system clock source.
--------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
--------------------------------------------------------------0
YES
line
0/0/1
Normal
0
YES
1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ---------------------------------------------------------------------
----End

Prerequisites
Networking
E1 port
loopback
ONU
OLT
E1 line tester
E1
ONU trace
the clock of
the OLT
OLT trace
the clock of
the tester
Internal
free-run
clock
Procedure
NOTE
Issue 01 (2016-04-29)

1184

Access Module
----End
Follow-up Procedure
l
Issue 01 (2016-04-29)
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
EDTB
board
Loops back
signals to the
network side on
the EDTB board
on the OLT. This
loopback checks
whether the
service from the
EDTB board to
the network-side
channel is
normal.
Local
loopba
ck on
the
EDTB
board
Loops back
signals to the
user side on the
EDTB board on
the OLT. This
loopback checks
whether the link
between the
EDTB board
and the E1 port
on the ONU is
normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
edt 0/5
remote
Remote loopback
E1 line
tester
ONU

OLT
E1
Local loopback


edt 0/5
1185

Access Module
Issue 01 (2016-04-29)
Loopb
ack
Mode
Function
Local
loopba
ck on
the
ONU
Loops back
signals to the
network side on
the ONU. This
loopback checks
whether the link
between the E1
port on the ONU
and the EDTB
board on the
OLT is normal.
Remote
loopba
ck on
the
ONU
Loops back
signals to the
user side on the
ONU. This
loopback checks
whether the link
between the
ONU and user
terminal is
normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
Local loopback
E1 line
tester
ONU
OLT
E1
Remote loopback

tdm 0/1
tdm 0/1
remote
1186

Access Module
13
13 FTTM Configuration (Base Station Access)
FTTM Configuration (Base Station

Access)
About This Chapter

On a FTTM (base station access) network, 2G or 3G/4G base stations are connected to ONUs
that serve as cell backhaul units (CBUs) in multiple modes. Then the ONUs transmit 2G or
3G services to OLTs and then to the upper-layer network. After being transmitted over the
upper-layer network, the services access the basic station controller (BSC) or radio network
controller (RNC). In this manner, 2G or 3G services are carried on the base station access
network.
13.1 Basic Concepts
Many concepts are involved in the base station access solution. The following only provides
major concepts involved in the network diagram of base station access service.
13.2 Prinpicle of Planning Data for Base Station Access Service
This topic plans base station access service in a unified manner from different dimensions.
The data plans are used to guide configuration and optimization of base station access service
in different scenarios.
13.3 Configuring Base station access Clock Synchronization
This topic describes the concept and principle of clock synchronization in bse station access
network, clock synchronization solutions supported by devices, and configuration differences.
13.4 Configuring Base Station Access Service (GPON)
This topic describes how to configure the base station access service in GPON mode in
different networking scenarios.
Issue 01 (2016-04-29)

1187

Access Module
13.1 Basic Concepts

Many concepts are involved in the base station access solution. The following only provides
major concepts involved in the network diagram of base station access service.
Network Diagram of Base Station Access Service

BTS
ONU
OLT
E1
BSC
NodeB
E1
SDH
FE/GE
Splitter
E1
Base station Side
GE
E1/STM-1
STM-1
GE
/10
GE
IP/MPLS
RNC
GE
ONU
Access Side
Network Side
User Side
Concept
Description
BTS
Base transceiver station, a 2G base station. BTSs are controlled by

base station controllers (BSCs) and constitute a a base station
subsystem (BSS) with BSCs as radio devices. BTSs serve for a
district and communicate with mobile stations (MSs) through air
interfaces.
NodeB
A 3G base station, providing physical radio links between mobile

devices (mobile phones) and the universal mobile telecommunications
system (UMTS) network. NodeBs transmit and receive data through
radio interfaces.
Concept
Description
SDH
Synchronous digital hierarchy. SDH is a transmission scheme that

follows ITU-T G.707, G.708, and G.709. It defines the transmission
features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part
of ISDN and B-ISDN. It interleaves the bytes of low-speed signals to
multiplex the signals to high-speed counterparts, and the line coding
of scrambling is used only for signals. SDH is suitable for the fiber
communications system with high speed and a large capacity since it
uses synchronous multiplexing and flexible mapping structure.
Network Side
Issue 01 (2016-04-29)

1188

Access Module
Concept
Description
PTN
Packet transport network. PTN provides bidirectional point-to-point

connections for packet switching services and supports point-to-point
networking using various service granularities. It can use lower-layer
transmission channels such as SDH, Ethernet, and OTN to transmit
services.
BSC/RNC
BSC: Base station controller. A BSC controls a group of base stations

and manages the radio network. Specifically, BSCs manage radio
districts and channels, operate and maintain radio devices, manage
connections of MSs, and provide interfaces between base stations and
the mobile switching center (MSC). Radio control functions can be
integrated in BSCs whenever possible to simplify functions of base
stations.
RNC: radio network controller. RNCs are key NEs on 3G networks.
RNCs manage mobility, process calls, manage links, and switch users
on the access network.
13.2 Prinpicle of Planning Data for Base Station Access

Service
This topic plans base station access service in a unified manner from different dimensions.
The data plans are used to guide configuration and optimization of base station access service
in different scenarios.
13.2.1 Principle of Equipment Management Data Plan

Equipment management planning involves planning for management VLANs and IP
addresses.
Management VLAN Planning

l
The OLT and ONUs use the same management VLAN.
The OLT and ONUs use a single SVLAN as the equipment management VLAN.
IP Address Planning
Issue 01 (2016-04-29)
Scenario
IP Address Planning
Equipment
management
A management IP address is allocated to each OLT/ONU.

Management IP addresses of ONUs connected to the same OLT are
usually in the same network segment. Private IP addresses planned
by the carrier are used for the purpose of security.
E1 base station
access service (in
Native TDM mode)
No IP addresses need to be planned because ONUs access the

private line service through E1.

1189

Access Module
Scenario
IP Address Planning
E1/T1 base station

access service (in
SAToP mode)
IP addresses are planned as follows:

l On OLTs, source IP addresses of SAToP connections must be
l On ONUs, source IP addresses of SAToP connections must be
These IP addresses are valid only between OLTs and ONUs and
therefore can be planned as private IP addresses.
Ethernet base
station access
service (in QinQ
VLAN mode)
No IP addresses need to be planned because the OLT and ONUs

provide Layer 2 transparent channels.
13.2.2 Principle of VLAN Data Plan

VLAN planning for the base station access service covers planning of VLANs and VLAN
translation policies in different networking scenarios.

Scenario
Issue 01 (2016-04-29)
VLAN Planning
E1 base station
access service
(in Native TDM
mode)
Use a reserved CVLAN

(starts from 4000).
E1 base station
access service
(in SAToP
mode)
Plan a global VLAN on the

OLT and ONUs, which
cannot conflict with other
service VLANs.
VLAN Translation
ONU
OLT
N/A
N/A
N/A
N/A
NOTICE
A reserved CVLAN cannot be
used for Ethernet services on
ONUs.

1190

Access Module
Scenario
VLAN Planning
Ethernet base
station access
service (in
QinQ VLAN
mode)
VLAN Translation
ONU
OLT
Single VLAN tag: ONUs

and the OLT use single
VLAN tags. Service
packets are forwarded
based on single VLAN tags
after being transmitted from
the OLT upstream to the
metro network. In this way,
a large number of VLANs
for the metro network will
be occupied if there are
many OLTs.
1. Different user
VLANs are
planned for
different
services
(service
packets with
different
destination
addresses or
paths) of base
stations.
The OLT
transparently
transmits packets
with CVLANs
from ONUs.
Generally, four VLANs are

planned for Ethernet base
station access service,
which are used for:
2. User VLANs
of packets sent
from the base
stations are
translated to a
specified
CVLAN based
on service
types.
l Clock synchronization
l Voice and data services
of base stations
l Base station
management
l ONU management
(Recommended) Double
VLAN tags: Each OLT uses
double VLAN tags, an
outer VLAN tag (SVLAN)
and inner VLAN tag
(CVLAN). SLVANs are the
same but CLVANs are
different. In this way, the
number of VLANs required
for the metro network is
significantly reduced.
1. Different user
VLANs are
planned for
different
services
(service
packets with
different
destination
addresses or
paths) of base
stations.
The OLT adds an

SVLAN tag:
CVLAN<>SVLAN
+CVLAN.
2. User VLANs
of packets sent
from the base
stations are
translated to a
specified
CVLAN based
on service
types.
Issue 01 (2016-04-29)

1191

Access Module
13.2.3 Principle of QoS Data Plan

QoS planning for the base station access service is end-to-end. QoS policies include traffic
classification, marking and scheduling, traffic monitoring, and DBA policies. QoS policies for
different scenarios are different. This topic provides QoS policies in the following scenarios.
E1 Base Station Access Service (in Native TDM Mode)

In this scenario, ONUs access services through E1 lines. Therefore, the QoS policies are
Parameter
Value
Remarks
T-CONT

from 1 to 3.

same T-CONT.
DBA type

delay

that the quality of the E1 base
ensured.
DBA bandwidth
Nx7232 kbit/s is recommended.

(N is the number of E1 lines.)
It is recommended that the TCONT ID be 1, 2, or 3 and all E1

same T-CONT. This setting can
leverage bandwidth resources.
Each E1 line requires only 5440
kbit/s.
E1 Base Station Access Service (in GPON SAToP Mode)

In this scenario, ONUs access services through E1 lines. Therefore, the QoS policies are
Issue 01 (2016-04-29)
Parameter
Value
Remarks
T-CONT

from 1 to 3.

same T-CONT.
DBA type

delay

that the quality of the T1 base
ensured.

1192

Access Module
Parameter
Value
Remarks
DBA bandwidth
l E1 access: Nx8 Mbit/s is

l T1 access: Nx6 Mbit/s is

Ethernet Base Station Access Service (in QinQ VLAN Mode)

Value
Parameter
Traffic
classification,
marking, and
scheduling policies
Traffic
monitorin
g and
DBA
policies
OLT
ONU
802.1p priority
OAM service of base stations: 7

Synchronization service of base stations: 7
Voice and data services of base stations: 7
Queue scheduling
mode
PQ
OLT queue ID
(eight queues)
T-CONT (only for

GPON)
QinQ private line services use a separate TCONT to distinguish the QinQ private line
services from other services.
DBA type

DBA bandwidth
Configure DBA bandwidth based on

bandwidth requirements of base stations.
Downstream traffic
profile
Configure a traffic profile based on bandwidth

requirements of base stations.
Upstream port rate

limit
Rates of upstream ports are not limited.
Downstream port
rate limit
Rates of downstream ports are not limited.
13.2.4 Principle of Clock Synchronization Data Plan

Wireless base stations have high requirements on clock precision. Clock synchronization
solutions must be planned based on types and standards of base stations.
Issue 01 (2016-04-29)

1193

Access Module
Clock Synchronization Solution

Classific
ation
Clock
Synchronizat
ion Solution
Description
Frequenc
y
synchroni
zation
BITS clock
For GSM and WCDMA base stations that only require

frequency synchronization, BITS clocks are transmitted to
base stations to achieve network-wide clock
synchronization when OLTs have BITS input clocks.
E1/STM-1 line
clock

frequency synchronization, E1/STM-1 line clocks are used
to achieve clock synchronization when OLTs transmit
services upstream to SDH networks through E1/STM-1
ports.
Synchronous
Ethernet clock

frequency synchronization, clocks restored from code
streams on Ethernet links are used to achieve network-wide
clock synchronization when OLTs transmit services
upstream to PSN networks through GE/10GE ports.
1PPS+ToD
time
OLTs receive time information through 1PPS+TOD ports.

The time information is transmitted from external time
servers (such as Huawei SYNLOCK T6020) that obtain
standard time synchronization information using GPS. This
solution is recommended for 3G and LTE stations.
1588V2 time
The OLT obtains the 1588v2 time by using the upstream

network interface (the time is transmitted by the upstream
network hop by hop). Then, the OLT transmits the time to
the ONU through the GPON line. After recovering the time,
the ONU transmits the time to the base station by means of
the 1588v2 or time interface.
Time
synchroni
zation
NOTE
The priority of recommended frequency synchronization solutions is as follows: BITS clock > line clock >
synchronous Ethernet clock. Select a clock source based on the actual conditions of COs.
Recommended Clock Synchronization Solutions for Different Base Station

Access Scenarios
Issue 01 (2016-04-29)
Scenario
Recommended Clock Synchronization Solution
E1 base station access

service (in Native TDM
mode)
BITS clock
E1 base station access

service (in GPON SAToP
mode)
BITS clock
E1/STM-1 line clock
E1/STM-1 line clock

1194

Access Module
Scenario
Recommended Clock Synchronization Solution
Ethernet base station access

service (in QinQ VLAN
mode)
Synchronous Ethernet clock

1PPS+ToD time (remark 1)
1588v2 time
Remark 1: Ethernet base stations may require time synchronization.

Security planning involves planning for system security, user security, and service security.
Security policy ensures normal services.
NOTE
l
System Security
Security
Vulnerability
Solution

Suggestion
DoS attack

MDU.

deployment.
IP attack

MDU.

deployment.
Issue 01 (2016-04-29)

1195

Access Module
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing

and MDU.
malicious attacks.
deployment.
MAC attack
Enable the anti-MAC

and MDU.

malicious attacks.
deployment.
IP spoofing

function for MDU.

malicious attacks.
deployment.
13.2.6 Planning Reliability Data

Reliability planning covers planning of equipment reliability and upstream/downstream
networking protection. Reliability planning helps to achieve high reliability of private line
services.
Issue 01 (2016-04-29)

1196

Access Module
Equipment Reliability
Protection Scheme
Description
Suggestion
Main control board

1+1 protection
The system uses two main control

boards of the same model and
version. The two main control
boards work in the active/standby
mode by default. When the active
main control board fails, the system
switches to the standby main control
board to prevent service
interruption.
Mandatory
Power board 1+1

protection
A subrack is configured with two

power boards of the same model
and version, which back up each
other. When one of the power board
fails, the other power board can still
provide power supply to the device
and so the system can still work
properly.
Mandatory
Upstream board 1+1

protection
The system uses two upstream

interface boards of the same model
and version. Each GIU board
provides one upstream port and two
upstream ports are bound together
using Link Aggregation Control
Protocol (LACP). When the active
upstream port fails, traffic will be
standby upstream port.

recommended when the
GIU board is used to
transmit traffic upstream.
Upstream Networking Protection
Issue 01 (2016-04-29)
Protection Scheme
Description
Suggestion
Link aggregation
group
Multiple Ethernet ports are bound

together as an aggregation group to
increase the bandwidth and balance
the inbound and outbound load of
each member port. In addition, the
ports in an aggregation group back
up each other, which enhances the
reliability of links.

mandatory when the GIU
traffic upstream.

1197

Access Module
Protection Scheme
Description
Suggestion
Protection group
(Ethernet/STM-1)
A protection group of upstream

ports contains a working port and a
protection port. In normal state, the
working port carries services and
the protection port does not. When
the link at the working port is faulty,
the system automatically switches
services from the working port to
the protection port to ensure normal
service transmission and protect the
uplink.
When the main control

traffic upstream, this
protection scheme is
mandatory.
recommended when traffic
is transmitted upstream
through STM-1 ports.
NOTE
Link aggregation group and Ethernet protection group usually are not configured at the same time. You are
advised to configure only one of the two protection schemes.
Downstream Networking Protection
Issue 01 (2016-04-29)
Protection Scheme
Description
Suggestion
xPON Type B single

homing
Two PON ports on the same OLT

back up each other. When one of the
PON ports fails, the system
automatically switches to the other
PON port. This protection scheme
provides port-level protection with
low costs. It protects services
against fiber failure at the working
port.
It rovides port-level
protection and has a low
cost. The inter-board
protection mode is
recommended.
GPON Type C single

homing
Two PON ports on the same OLT,

fibers are configured to provide
link-level protection.
It rovides link-level
protection.

1198

Access Module
Protection Scheme
Description
Suggestion
GPON Type C dual

homing
Two PON ports on different OLTs,

fibers are configured to implement
this protection. The difference
between this protection scheme and
the GPON Type C single homing
protection scheme is that the ONU
needs to be dual homed to two OLTs
in this protection scheme. This fullbackup protection scheme provides
the highest-level protection for links
and has the highest costs.
It provides full backup

protection, which is the
highest level of protection,
at the same time, it has the
highest cost.
This protection scheme
can be configured for only
the Ethernet QinQ private
line service. It does not
support TDM services,
including Native TDM and
SAToP.
NOTE
The Type B single homing protection scheme, Type C single homing scheme, and Type C dual homing
protection scheme are mutually exclusive. Therefore, only one of these protection schemes can be configured
for an ONU.
13.3 Configuring Base station access Clock

Synchronization
This topic describes the concept and principle of clock synchronization in bse station access
network, clock synchronization solutions supported by devices, and configuration differences.
13.3.1 Overview of Base station access Clock/Time

Synchronization
This topic describes the clock/time synchronization concept, clock/time synchronization
solutions supported by the system, and solution comparison. Proper clock synchronization
solutions are selected for Base station access networks based on base station type and
equipment layout.
Synchronization Concept
Synchronization includes frequency synchronization and time synchronization.
Frequency synchronization is also called clock synchronization, which indicates that certain
strict relations are kept between signals in terms of frequency and phase. The valid transience
occurs at the same rate for a signal. In this way, the equipment in the entire network runs at
the same rate.
Time synchronization is also called frequency and phase synchronization, which has two
meanings: instant and interval. Instant refers to an instant of continuous time, and interval
refers to an interval between two instants.
The purpose of clock/time synchronization is to control the occurrence of controlled slip and
to decrease the slip, burst bit error, sudden phase change, jitter, or drift of various device
Issue 01 (2016-04-29)

1199

Access Module
signals in the telecommunications service network to the minimum, ensuring the high-quality
and high-efficiency running of the telecommunications service network.
Clock/Time Synchronization Solution

Figure 13-1 shows a clock/time synchronization solution in base station access network. The
clock/time synchronization principle is as follows: The clock obtained by the OLT serves as
the clock source and transmits signals to the base station through xPON lines.
Figure 13-1 Clock/Time synchronization solution in base station access network
CITD
Selector
E1
BITS
Base
station
ONU
Clock output
BITS_IN1
BITS_IN0
2MHz,2Mb/s
1PPS+TOD
EDTB card
Clock
output by
PON
board
CKMC
PLL
1PPS+TOD
Selector
Sync-ETH
BITSB port
TOPA card
GSCA/X2CS
/GICK
System PLL
SCU card
(active)
OLT
SPUA
Line clock
source
The figure shows that the OLT can obtain the following clock sources:
l
BITS clock source
E1/STM-1/T1 line clock source
Synchronous Ethernet line clock
"1PPS+ToD" time injection
End-to-end 1588v2 clock source
Internal clock sources are not recommended because they are in free oscillation state and
do not have advantages in precision.
Comparison of Clock/Time Synchronization Solution

Table 13-1 shows a clock synchronization solution in base station access network.
Issue 01 (2016-04-29)

1200

Access Module
Table 13-1 Comparison of clock/time synchronization solution

Synchronization
Solution
Usage Scenario
Advantage
Limitation or
Hardware
Requirements
BITS clock
Applies to the base

station that requires
only frequency
synchronization,
such as GSM/
WCDMA. In
addition, the OLT
must have BITS
clock input
resources.
1. Clock precision
meets the
following
requirements:
1. The OLT must

have BITS clock
resources.
l G.8262
features when
CKMC/
CKMD
stratum-3
clock units
are
configured
l EEC
specifications
defined in G.
8261 when no
stratum-3
clock units
are
configured
2. BITS clocks
cannot provide
independent
service clocks for
each E1 channel.
3. BITS clocks
support only
frequency
synchronization.
Board that support
this feature:
H801CITD
(configured with the
H801BITSB
daughter board)
2. No requirements
on delay, jitter, or
pack loss of a
PSN network
Issue 01 (2016-04-29)

1201

Access Module
Synchronization
Solution
Usage Scenario
Advantage
Limitation or
Hardware
Requirements
E1/STM-1/T1 line
clock
Applies to the BTS

that requires only
frequency
synchronization,
such as GSM/
WCDMA. In
addition, the OLT
can directly connect
to an SDH network.
1. Clock precision
meets the
following
requirements:
1. In E1/STM-1
upstream
transmission, the
OLT must be in
the same office
as SDH
equipment.
l G.8262
features when
CKMC/
CKMD
stratum-3
clock units
are
configured
l EEC
specifications
defined in G.
8261 when no
stratum-3
clock units
are
configured
2. E1/STM-1 line
clocks are all
obtained from
physical line
clocks and they
have the best
performance in
terms of stability
and reliability.
2. E1/STM-1 line
clocks support
only frequency
synchronization.
Boards that support
this feature:
l STM-1 line
clock:
H801TOPA
(configured with
the H801CSSA
daughter board)
or H801TOPA
(configured with
the H801O2CE
daughter board).
l E1 line clock:
H801TOPA
(configured with
the H801NH1A
daughter board),
H801TOPA
(configured with
the H801EH1A
daughter board)
or H802EDTB.
l T1 line clock:
H802EDTB
Issue 01 (2016-04-29)

1202

Access Module
Synchronization
Solution
Usage Scenario
Advantage
Limitation or
Hardware
Requirements
Ethernet clock
Applies to the BTS

that requires only
frequency
synchronization,
such as GSM/
WCDMA. In
addition, the OLT
upstream network
has the capability of
synchronizing
Ethernet clocks.
1. Clock precision
meets the
following
requirements:
1. Ethernet clocks
require that
MAN PSN
networks have
the capability of
synchronizing
Ethernet clocks.
l G.8262
features when
CKMC/
CKMD
stratum-3
clock units
are
configured
l EEC
specifications
defined in G.
8261 when no
stratum-3
clock units
are
configured
2. Ethernet clocks
support only
frequency
synchronization.
Boards that support
this feature:
H801X2CS,
H801GSCA,
H801GICK,
H801SPUA, and
H801SPUF
2. No requirements
on delay, jitter, or
pack loss of a
PSN network
"1PPS+ToD" time
injection
Issue 01 (2016-04-29)
Applies to the BTS

that requires time
synchronization,
such as
CDMA2000/TDSCDMA/LTE.
When the OLT
upstream network
does not support
1588V2, this
solution is
recommended.
1. This solution
supports time
synchronization
and frequency
synchronization
and provides
high-precision
time. The clock
quality meets G.
813 and G.8262
specifications.
A BITS server must

be at the same place
as the OLT.
2. This solution
does not have
requirements on
PSN networks.

1203

Access Module
Synchronization
Solution
Usage Scenario
Advantage
Limitation or
Hardware
Requirements
End-to-end 1588v2
clock
Applies to the BTS

that requires time
synchronization,
such as
CDMA2000/TDSCDMA/LTE.
When the OLT
upstream network
supports 1588V2
hop by hop, this
solution is
recommended.
1. This solution
supports time
synchronization
and frequency
synchronization
and provides
high-precision
time. The clock
quality meets G.
813 and G.8262
specifications.
The upstream
network of the OLT
should support
1588V2 hop by hop.
2. This solution
does not require
a 1588V2 server
on the OLT.
13.3.2 Configuring BITS Clock Synchronization

The OLT receives the clock through the BITS and transmits the clock to the ONU through the
PON line and then downstream to the base station, implementing clock synchronization of the
entire network.
Application Context
As shown in Figure 13-2, the OLT receives the clock from the BITS and the clock share the
same clock source with the BSC/RNC. Then the OLT transmits the clock to the ONU through
the PON line clock. After recovering the clock, the ONU transmits the clock to the base
station through the E1 or FE/GE port.
Figure 13-2 BITS clock synchronization
BITS
BTS
N*E1 ONU
BSC
OLT
FE/GE
GE/10GE
NodeB
N*E1
PSN
CX600
GE
RNC
ONU
BITS clock
PON line clock
Issue 01 (2016-04-29)

1204

Access Module
Prerequisite
l
The clock daughter board CKMC/CKMD of the SCU board must be in position.
The OLT must have the BITS clock input resource.
The CITD board (its BITS clock daughter board must be in position) must work in the
normal state.
Data Plan
Item
Data
CITD board
Ports: 0/0/0 and 0/0/1

Clock type: BITS 2 MHz, 120 ohms
Clock priority: p0 > p1
GIU upstream board
Port: 0/19/0
E1 port of the ONU
0/1/0
ETH port of the

ONU
0/3/1
Configuration Concept
1.
The OLT uses the BITS line clock as the system clock.
2.
The system clock is issued to the ONU through the optical path of the PON service
board.
3.
The ONU uses the line clock of the PON upstream port as the system clock.
4.
The E1 Tx clock of the ONU is synchronized to the system clock of the ONU.
Procedure
Step 1 Configure the OLT-side clock.
1.
Configure a system clock source.

Run the clock source command to configure BITS_IN ports 0/0/0 and 0/0/1 on the CITD
board as the system clock sources. Set their IDs to 0 and 1 respectively.
huawei(config)#clock source 0 0/0/0 2mhz 120ohm
2.
Set the priority of the system clock source.

Run the clock priority command to configure the priorities of clock sources 0 and 1 to
p0 > P1.
huawei(config)#clock priority system 0/1
3.
Query the configuration and status of the system clock source.

Run the display clock source command to query the configuration and status of the
clock source. Ensure that the configuration information about the system clock is
matching and the status is normal.
Issue 01 (2016-04-29)

1205

Access Module
Step 2 Configure the ONU-side clock.

1.
Configure the PON line clock source as the system clock.

The system clock of the OLT is issued to the ONU through the optical path of the PON
port, implementing the clock synchronization between the OLT and the ONU.
a.
Run the clock source command to configure the clock recovered from the PON
upstream port as the system clock source of the ONU.
b.

2.
(Optional) Configure the system clock as the Tx clock of the E1 port.

NOTE
This step is required only when the base station is connected to the ONU through the E1 port. When the
base station is connected to the ONU through the ETH port, this step is not required. By default, it is the
system clock and cannot be modified.
a.
b.
Run the tx clock or port portid udt system command to configure the Tx clock of
the port as the system clock.
c.
Run the display port state command to query the Tx clock of the E1 port.

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
3.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Issue 01 (2016-04-29)

1206

Access Module
Result
After the configuration of base station access service is complete, use the test meter to
perform tests on the E1/ETH access port of the ONU and the upstream GE/10GE port. The
long-term bit error ratio (BER) and delay should be able to meet the requirements for actual
applications.
13.3.3 Configuring E1/STM-1 Line Clock Synchronization

When optical line terminals (OLTs) access a base station that requires only frequency
synchronization, such as GSM/WCDMA, and when OLTs are connected upstream to the
synchronous digital hierarchy (SDH) network by using the E1/STM-1 port, the E1/STM-1
line clock can be used for clock synchronization.
Application Context
As shown in Figure 13-3, the OLT recovers the clock from the E1/STM-1 line. This clock is
transmitted by the BSC/RNC through the SDH network and then transmitted to the ONU
through the PON line clock. After recovering the clock, the ONU transmits the clock to the
base station through the E1 line.
Figure 13-3 E1/STM-1 line clock synchronization
BTS
ONU
BSC
OLT
N*E1
SDH
N*E1
E1/STM-1
NodeB
ONU
CX600
RNC
E1/STM-1 line clock

PON line clock
Prerequisite
Issue 01 (2016-04-29)

1207

Access Module
Data Plan
Item
Data
TOPA board
Port ID: 0/5/0

Daughter board type:
l When the OLT and the ONU adopt the Native TDM mode,
NH1A provides the E1 port and O2CE provides the STM-1 port.
E1 port of the ONU
0/1/0
1.
clock.
2.
board.
3.
4.
The E1 Tx clock of the ONU is synchronized to the system clock of the ONU.
Procedure
1.

Run the clock source command to configure the line clock of E1/STM-1 port 0/5/0 on
the TOPA board as the system clock source. Set the clock source ID to 0.
The clock module automatically judges the types of the specified clock sources (E1/
STM-1) and selects them according to their priority, serving as the clock sources for
phase lock.
2.

Run the clock priority command to configure clock source 0 to have the highest priority.
3.


1.

a.
Issue 01 (2016-04-29)
1208

Access Module
b.

2.
Configure the system clock as the Tx clock of the E1 port.

a.
b.
c.

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
3.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Result
perform tests on the E1 port of the ONU and the upstream E1/STM-1 port of the TOPA board.
The long-term bit error ratio (BER) and delay should be able to meet the application
requirements.
13.3.4 Configuring Ethernet Clock Synchronization

When OLTs access a base transceiver station (BTS) that requires only frequency
synchronization, such as GSM/WCDMA/FDD LTE and when the OLTs are connected
Issue 01 (2016-04-29)

1209

Access Module
upstream to the packet switched network (PSN) by using the GE/10GE port, the clock can be
recovered from the bit streams on the Ethernet link, implementing synchronization between
over the entire network.
Application Context
As shown in Figure 13-4, the OLT receives the clock from the upstream synchronous
Ethernet port. (This clock is transmitted through the PSN network and must be supported by
all intermediate nodes.) Then the clock is transmitted to the ONU through the PON line clock.
After recovering the clock, the ONU transmits the clock to the base station through the
synchronous Ethernet or independent clock port.
Figure 13-4 Ethernet clock synchronization
BTS
N*E1
ONU
BSC
OLT
FE/GE
GE/10GE
NodeB/
eNodeB
N*E1
PSN
GE
CX600
E1/STM-1 line clock RNC
Synchronization Ethernet line clock
GPON line clock
ONU
Prerequisite
l
The ethernet upstream board must be GICK/GSCA (GE port) or X2CS (10GE port)/
SPUF (need an independent service board slot).
The upstream MAN PSN of the OLT must feature the capability of Ethernet
synchronization.
Data Plan
Item
Data
GIU Upstream
Boards
Port: 0/19/0
E1 port of the ONU
0/1/0
ETH port of the

ONU
0/3/1
1.
Issue 01 (2016-04-29)
The OLT uses the synchronous Ethernet clock of the upstream slot as the system clock.
1210

Access Module
2.
board.
3.
4.
The Tx clock of the E1 or ETH port on the ONU is synchronized to the system clock of
the ONU.
Procedure
1.

Run the clock source command to configure the line clock of the GE/10GE port on the
GIU board as the system clock source. Set the clock source ID to 0.
The clock module automatically judges the types of the specified clock sources (ETH),
and selects them according to their priorities, serving as clock sources for phase lock.
2.

Run the clock priority command to configure clock source 0 to have the highest priority.
3.


1.

a.
b.

2.
(Optional) Configure the system clock as the Tx clock of the E1 port.

NOTE
This step is required only when the base station is connected to the ONU through the E1 port. When the
base station is connected to the ONU through the ETH port, this step is not required. By default, it is the
system clock and cannot be modified.
a.
b.
c.

---------------------------------------
Issue 01 (2016-04-29)

1211

Access Module
Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
3.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Result
perform tests on the E1/ETH access port of the ONU and the upstream GE/10GE port. The
long-term bit error ratio (BER) and delay should be able to meet the requirements for actual
applications.
13.3.5 Configuring "1PPS+ToD" Clock Synchronization

In the base stations that require time synchronization, such as CDMA2000/TD-SCDMA/LTE,
the OLT obtaions time by "1PPS+ToD" time injection way. The OLT transmits the clocks to
the ONU through GPON lines and then downstream to the base station, implementing clock
synchronization of the entire network.
Context
"1PPS+ToD" is a time synchronization technology. The quality of clock transmitted by "1PPS
+ToD" meets the stratum 3 clock requirement and the time quality reaches a submicrosecond
precision, which solves the time and clock synchronization problems of the user. In addition,
using "1PPS+ToD" can better reduce user's investment. Therefore, it is applicable to the base
station access services.
Application Context
As shown in Figure 13-5, the OLT is injected with time through the 1PPS+ToD interface (the
time source is obtained from the GPS). Then, the OLT transmits the time signals to the ONU
Issue 01 (2016-04-29)

1212

Access Module
by means of the GPON time synchronization technology. After recovering the time signals,
the ONU transmits them to the base station by means of the time interface.
This scheme has no additional requirement for the PSN network, but the OLT must be
deployed with a BITS server (such as SYNLOCK from Huawei). Therefore, this scheme is
recommended when the upstream network of the OLT does not support 1588V2.
This scheme requires that ONU supports external clock interface.
Figure 13-5 "1PPS+ToD" time injection
GPS
eNodeB
OLT
FE/GE
ONU
N*E1
PSN
FE/GE
GE/10GE
ONU
NodeB
RNC
SYNLOCK
CX600
GE
1pps+ToD
RNC
GPON line clock
Prerequisite
l
The clock daughter board CKMC/CKMD of the SCU control board must be in position.
The CITD board (with the BITSB daughter board) must be in position.
GPON service boards must support 1588v2. For details, see hardware supported by
1588v2.
Data Plan
Item
Data
Clock source
The time is injected from the BITS IN port of the CITD board to the
1PPS+ToD interface:
l BITS IN ports of the CITD board: 0/0/0 and 0/0/1
l Clock priority: p0 > p1
ETH port of the

ONU
Issue 01 (2016-04-29)
0/3/1

1213

Access Module
1.
On the OLT side, select the 1PPS+ToD clock signal as the system clock source.
2.
board.
3.
The ONU uses the 1588V2 clock of the PON upstream port as the system clock.
4.
The ONU transmits time signals to the base station by using the FE/GE port or the clock
output interface on panel.
Configure the OLT-side clock.
Procedure
a.
Add a "1PPS+ToD" clock source.

Add two line "1PPS+ToD" clock source, and specify their index and priority.
huawei(config)#ptp source 0 0/0/0
huawei(config)#ptp priority 0/1
b.
Configure the "1PPS+ToD" clock source as the system clock source.

c.
Query the configuration and status of the "1PPS+ToD" clock source and system
clock source.
huawei(config)#display ptp source
---------------------------------------------------------------Index Board
Source
State Priority Selected LockState
---------------------------------------------------------------0
H801CITD 0/0/ 0
Normal 0
YES
successful
1
H801CITD 0/0/ 1
Normal 1
successful
2
---/ -/ - --------3
---/ -/ - --------4
---/ -/ - --------5
---/ -/ - --------6
---/ -/ - --------7
---/ -/ - --------8
---/ -/ - --------9
---/ -/ - -----------------------------------------------------------------------huawei(config)#display clock source system
----------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------0
H801CITD 0/0/ 0
2MHz
Normal
0
--YES
1
H801CITD 0/0/ 1
2MHz
Normal
1
---------------------------------------------------------------------------
Configure the ONU-side clock (the clock is connected to the base station by using
GE port to implement time synchronization).
This configuration is applicable to time synchronization in the base station where
synchronous base station technologies (TDS-CDMA/CDMA2000/LTE is a
representative) are adopted. The base station must provide ETH ports and support
1588v2 packets.
a.
Add a system clock source (frequency synchronization).

The 1588v2 clock is issued to the ONU through the optical path of the PON port,
implementing the clock synchronization between the OLT and the ONU.
i.
Issue 01 (2016-04-29)
Run the clock source command to add the 1588v2 clock source as the system
clock source.
1214

Access Module
ii.
Run the clock priority command to configure the priority of the 1588v2 clock
source.
b.
Configure the 1588v2 time source (time synchronization).

i.
Run the ptp enable command to enable the 1588v2 function.

huawei(config)#ptp enable
ii.
Run the ptp source command to add the 1588v2 clock source as the system
clock source.
iii. Run the ptp priority command to configure the priority of the 1588v2 clock
source.
huawei(config)#ptp priority 0
c.
Run the ptp port enable command to enable the 1588v2 function on the Ethernet
port to transmit 1588v2 packets on the specified port.
huawei(config)#ptp port 0/3/1 enable
d.
Query the configuration and status of the 1588v2 clock source and system clock
source.
n
Run the display ptp source command to query the status of the 1588v2 clock
source.
Run the display clock source command to query the configuration and status
of the system clock source.

--------------------------------------------------------------------Index Type
Source
State
Priority Selected
Lock state
--------------------------------------------------------------------0
1588
0/0/1
Normal
0
--successful
1
--/ -/ --------2
--/ -/ --------3
--/ -/ --------4
--/ -/ --------5
--/ -/ --------6
--/ -/ --------7
--/ -/ --------8
--/ -/ --------9
--/ -/ ----------------------------------------------------------------------------huawei(config)#display clock source
-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
Issue 01 (2016-04-29)
Configure the ONU-side clock (the ONU provides the base station with a clock by
using the clock interface on the panel to implement time synchronization).
representative) are adopted. If a base station provides the ETH port but does not support
1588v2 packets, the ONU outputs 1PPS+ToD time for the base station synchronization.
1215

Access Module
a.

i.
clock source.
ii.
source.
b.

i.

ii.
clock source.
source.
c.
Configure the time output mode of the clock output interface.

The ONU provides an independent output clock through time output port 0 on the
panel. Configure the clock output signal to 2 MHz and time signal to 1pps+ubx.
NOTE
Configure the clock/time output mode according to actual conditions.

huawei(config)#clock bits-type 0 clock 2mhz
BITS clock parameter set successfully
huawei(config)#clock bits-type 0 time 1pps protocol ubx
----End
13.3.6 Configuring 1588v2 Clock Synchronization

In the base stations that require time synchronization, such as CDMA2000/TD-SCDMA/LTE,
the OLT brings 1588v2 clocks in end-to-end (E2E) 1588v2 mode. The OLT transmits the
clocks to the ONU through GPON lines and then downstream to the base station,
implementing clock synchronization of the entire network.
Context
1588v2 is a time synchronization technology. The quality of clock transmitted by 1588v2
meets the stratum 3 clock requirement and the time quality reaches a submicrosecond
precision, which solves the time and clock synchronization problems of the user. In addition,
using 1588v2 can better reduce user's investment. Therefore, 1588v2 is applicable to the base
station access services.
Application Context
As shown in Figure 13-6, the OLT obtains the 1588v2 time by using the upstream network
interface (the time is transmitted by the upstream network hop by hop). Then, the OLT
transmits the time to the ONU through the GPON line. After recovering the time, the ONU
transmits the time to the base station by means of the 1588v2 or time interface.
Issue 01 (2016-04-29)

1216

Access Module
This scheme does not require a 1588v2 server on the OLT. Therefore, this scheme is
recommended when the upstream network of the OLT supports 1588v2 hop by hop.
Figure 13-6 E2E 1588v2
eNodeB
GE
ONU
BSC
OLT
N*E1
PSN
GE
CX600
GE/10GE
ONU
NodeB
GE
1588V2
RNC
GPON line clock
Prerequisite
l
The clock daughter board CKMC/CKMD of the SCU control board must be in position.
The GE 1588v2 upstream board GICK or SPUF (10GE) must be in position.
GPON service boards must support 1588v2. For details, see hardware supported by
1588v2.
Data Plan
Item
Data
1588v2 clock
source
When the 1588v2 clock packets are injected by using the GICK/
SPUF board or the 1588v2 clock packets of the upstream network
are transparently transmitted:
l GE ports of the GICK board: 0/19/0 and 0/19/1
l 10 GE ports of the SPUF board: 0/2/0 and0/2/1
l Clock source selection mode: priority
l Clock priority: p0 > p1
GPON port
0/3/1
ETH port of the

ONU
0/3/1
1.
On the OLT side, select the clock signal recovered from 1588v2 packets as the system
clock source.
2.
board.
Issue 01 (2016-04-29)

1217

Access Module
3.
The ONU uses the 1588v2 clock of the PON upstream port as the system clock.
4.
The Tx clock of the GE port on the ONU is synchronized to the system clock of the
ONU.
5.
The ONU synchronizes the clock and time with the base station in the following three
modes:
The ONU transmits 1588v2 packets to the base station by using the GE port.
The ONU provides independent time signals to the base station by using the clock
output interface.
Procedure
l

a.
Configure the global 1588v2 function.

Run the ptp enable command to enable 1588v2 on a device.
(Optional) Run the ptp domain command to configure a 1588v2 time domain.
Each time domain supports only one clock source. All the devices in the 1588v2
time domain are synchronized with the clock source. Ensure that the time domain of
an MDU is the same as that of the optical line terminal (OLT).
huawei(config)#ptp domain 1
b.
Configure the system clock source and time synchronization (frequency

synchronization).
i.
Run the command to configure the index of the system clock source.
The clock source can be the synchronous clock recovered from a GE or 10 GE
line on the network side, 1588v2 clock, or BITS clock.
When the network supports synchronous Ethernet clock, the clock is
recommended.
ii.
Run the clock priority system command to set the priority of the clock source.
A device may trace multiple clock sources for synchronizing the clock. It
selects the clock source with the highest priority as the clock source.
iii. Optional: Configure the mode for dynamically selecting the system clock
source.
The system supports static and dynamic selection. When dynamic selection is
required based on Synchronization Status Message (SSM), run the clock qlmode enable command to enable the SSM selection mode.
n
If the GICK board is used to access the 1588v2 clock source:

If the SPUF board is used to access the 1588v2 clock source:

c.
Issue 01 (2016-04-29)
Configure a 1588v2 time source (time synchronization).

i.
Run the ptp source command to configure a 1588v2 time source.
ii.
Configure the mode of selecting the 1588v2 time source.

1218

Access Module
A time source can be statically or dynamically selected.
To statically select a time source based on the local priority, run the ptp
priority command to set the priority of the time source.
To dynamically select a time source based on the best master clock

(BMC), run the ptp bmc enable command to configure the status of the
automatic BMC source selection function.
iii. Run the ptp port enable command to enable 1588v2 on an Ethernet port to
transmit 1588v2 packets.
Enable 1588v2 on the ports that are required to transmit 1588v2 packets, for
example, the uplink port on an OLT and user-side port on an MDU. You are
not required to enable the function on the GPON port connecting the OLT and
MUD.
n
If the GICK board is used to access the 1588V2 clock source:

huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
If the SPUF board is used to access the 1588V2 clock source:

huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
huawei(config)#ptp
d.
source 0 0/19/0
source 1 0/19/1
priority 0/1
port 0/19/0 enable
port 0/19/1 enable
source 0 0/2/0
source 1 0/2/1
priority 0/1
port 0/2/0 enable
port 0/2/1 enable
(Optional) Configure the attributes of the 1588 V2 clock source.

Configure 1588v2 parameters, such as timestamp mode of the 1588v2 packets,
MAC encapsulation mode, and UDP encapsulation mode. By default, the MAC
mode is used as the packet encapsulation mode, and the L2 multicast mode is used
as the packet forwarding mode.
When the default attributes of the 1588v2 clock source do not meet the actual
requirement, run the command to modify the attributes.
NOTE
Before modification, ensure that the attributes of the 1588v2 clock source are the same as the
actual ones. In this example, assume that the default attributes of the system clock source meet the
application requirements.
e.
source.
n
Run the command to query the status of the 1588v2 clock source.
Run the command to query the configuration and status of the system clock
source.

----------------------------------------------------------------Index Board
Source
State Priority Selected
LockState
----------------------------------------------------------------0
H801GICK 0/19/ 0 Normal 0
YES
successful
1
H801GICK 0/19/ 1 Normal 1
successful
2
---/ -/ - --------3
---/ -/ - --------4
---/ -/ - --------5
---/ -/ - --------6
---/ -/ - --------7
---/ -/ - --------8
---/ -/ - --------9
---/ -/ - ---------
Issue 01 (2016-04-29)

1219

Access Module
----------------------------------------------------------------huawei(config)#display clock source system

----------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------0
H801GICK 0/19/ 0 --Normal
0
--YES
1
H801GICK 0/19/ 1 --Normal
1
---------------------------------------------------------------------------
Configure the ONU-side clock (the clock is connected to the base station by using
GE port to implement time synchronization).
representative) are adopted. The base station must provide ETH ports and support
1588v2 packets.
a.

i.
clock source.
ii.
source.
b.

i.

ii.
clock source.
source.
c.
Run the ptp port enable command to enable the 1588v2 function on the Ethernet
port to transmit 1588v2 packets on the specified port.
huawei(config)#ptp port 0/3/1 enable
d.
source.
n
Run the display ptp source command to query the status of the 1588v2 clock
source.
Run the display clock source command to query the configuration and status
of the system clock source.

--------------------------------------------------------------------Index Type
Source
State
Priority Selected
Lock state
--------------------------------------------------------------------0
1588
0/0/1
Normal
0
--successful
1
--/ -/ --------2
--/ -/ --------3
--/ -/ --------4
--/ -/ --------5
--/ -/ --------6
--/ -/ --------7
--/ -/ --------8
--/ -/ --------9
--/ -/ ---------
Issue 01 (2016-04-29)

1220

Access Module
--------------------------------------------------------------------huawei(config)#display clock source

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
Configure the ONU-side clock (the ONU provides the base station with a clock by
using the clock interface on the panel to implement time synchronization).
representative) are adopted. If a base station provides the ETH port but does not support
1588v2 packets, the ONU outputs 1PPS+ToD time for the base station synchronization.
a.

i.
clock source.
ii.
source.
b.

i.

ii.
clock source.
source.
c.
Configure the time output mode of the clock output interface.

The ONU provides an independent output clock through time output port 0 on the
panel. Configure the clock output signal to 2 MHz and time signal to 1pps+ubx.
NOTE
Configure the clock/time output mode according to actual conditions.

huawei(config)#clock bits-type 0 clock 2mhz
huawei(config)#clock bits-type 0 time 1pps protocol ubx
----End
Issue 01 (2016-04-29)

1221

Access Module
Result
After the FTTM service configuration is complete, use the test meter to perform tests on the
ETH access port of the ONU and the upstream GE/10GE port of the OLT. The long-term bit
error ratio (BER) and delay should be able to meet the requirements for actual applications.
13.4 Configuring Base Station Access Service (GPON)

This topic describes how to configure the base station access service in GPON mode in
Context
l
Distributed mode: In this mode, ONTs need to be configured one by one but not in
batches.
Profile mode: In this mode, an ONT line profile and service profile are configured first.
Then, ONTs can be added in batches by binding profiles. This mode greatly improves
Generally, the xPON configuration mode is determined in a new deployment and will not be
changed. This chapter describes how to configure the enterprise access service in PON profile
mode (which is the default mode). You can run the commands in the following table to query
the xPON configuration mode.
Mode
Query Method
PON profile
mode
--------------------------------------------------Current config mode: Profile-mode
---------------------------------------------------
NOTE
For commands for the distributed configuration mode, see PON distributed-mode commands in the
Command Reference.
13.4.1 Configuring E1 Base Station Access Service (in Native

TDM Mode, GPON)
ONUs transmit E1 signals of base stations to OLTs in Native TDM mode and OLTs are
Service Requirement and Application Scenario

Service Requirement
As a mainstream full-service access technology in the future, the passive optical network
(PON) supports fast deployment and service provisioning. It also helps simplify the access
Issue 01 (2016-04-29)

1222

Access Module
network and reduce the costs on construction and subsequent maintenance of the access
network. Currently, carriers in China and outside China are using the PON to carry 2G/3G
base station services over their existing FTTx networks that are established for accessing
individual/enterprise users. In this manner, carriers can implement the access of all the
services at the access layer in an unified mode.
l
ONUs are connected to 2G or 3G base stations through E1 ports.
GPON is used for carrying the mobile access network in a unified manner to meet
mobile carriers' requirements for a high bandwidth and high-density coverage of base
stations.
Existing SDH resources are utilized efficiently to implement high-quality transmission of

TDM services.
As shown in Figure 13-7, the ONU accesses TDM services of the 2G or 3G base station
through the E1 port, and then transmits the service data to the GPON service board on the
OLT in the Native TDM mode. The OLT restores TDM signals, and then transmits the signals
to the SDH network through the E1 port (provided by the NH1A daughter board) or STM-1
port (provided by the O2CE daughter board) on the TOPA board. In this manner, service
access of the 2G or 3G base station is implemented between the ONU and the OLT in the
Native TDM mode.
Figure 13-7 Networking diagram of E1 base station access service
BTS
N*E1 ONU
NodeB
N*E1
BSC
OLT
N*E1
SDH
ONU
CX600
N*E1
E1
Native TDM
E1/STM-1
RNC
The following figure shows the configuration process for E1 base station access service.
Issue 01 (2016-04-29)

1223

Access Module
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring TDM E1
Connections
Policies
Configuring Network
Protection
Configuring Clock
Synchronization
Verifying Services
End
Adding ONUs to OLT

Issue 01 (2016-04-29)

1224

Access Module
Context
l
Data Plan
Configurati
on Item
Data
DBA profile
DBA profile for management service: dba-profile_1 (system default)

DBA profile for private line service:
l Profile ID: 21
l Profile type: Fixed bandwidth and minimum delay
l DBA bandwidth: 28928 kbit/s (Each ONU accesses four E1 private
lines and each line has a recommended DBA bandwidth of 7232
kbit/s.)
Line profile
Profile ID: 11
T-CONT ID: 1 (for private line service) and 2 (for management service)
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.
Configure a DBA profile. Enable the bandwidth compensation function and set the DBA
bandwidth allocation mode for the GPON port to minimum bandwidth delay.
2.

to DBA profile 21
to DBA profile 1
to T-CONT 1.
Issue 01 (2016-04-29)

1225

Access Module

huawei(config-gpon-lineprofile-11)#gem mapping 13 1 e1 1 //Map GEM port 13 to
E1 port 1 on the ONU.
3.

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

1226

Access Module
Configuring Management Service Ports on OLT and ONUs

ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
Issue 01 (2016-04-29)

1227

Access Module

reachable.
l
configure the ONU.
----End
Configuring TDM E1 Connections

This topic describes how to configure Native TDM connections between GPON ports and E1/
STM-1 upstream ports to transmit E1/STM-1 private line service data.
Prerequisites
l
TOPA+NH1A for upstream transmission through E1
TOPA+O2CE for upstream transmission through STM-1
GPON board: GPBC, GPBD
Context
The OLT can transmit data to the SDH network through E1 or STM-1 lines. Each E1 line
provides 2 Mbit/s bandwidth. After being mapped, aligned, and encapsulated, 63xE1 signals
are multiplexed into one STM-1 signal through VC12. One STM-1 line provides 155 Mbit/s.
When the OLT transmits data to SDH equipment through STM-1 lines, pay attention to the
VC12 mode and VC12 number.
l
When the OLT is interconnected with Huawei SDH equipment, the VC12 mode is
huawei and the VC12 numbers on the OLT and the SDH equipment must be consistent.
When the OLT is interconnected with Lucent SDH equipment, the VC12 mode is lucent.
The VC12 numbers has the following mapping relationships (which can be queried using
the display vc12-mode-table command):
Huawei: Mapping between the multiplexing number and VC12 number: VC12 number =
(TUG31) + (TUG21) x 3 + (TU121) x 21
Lucent: Mapping between the multiplexing number and VC12 number: VC12 number =
(TU121) + (TUG21) x 3 + (TUG31) x 21
Issue 01 (2016-04-29)

1228

Access Module
Data Plan
Upstream
Transmissio
n Mode
Data
Upstream
transmission
through E1
Upstream
transmission
through
STM-1
Daughter board type: NH1A (provides E1 ports)
Daughter board type: O2CE (provides STM-1 ports)

VC12 number: 0
NOTE
The VC12 parameter must match that on the interconnected SDH equipment.
Otherwise, services fail.
Procedure
l
Configure a TDM E1 connection for E1 upstream transmission.

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 gpon 0/3/1 ontid 3
gemportIndex 13
Configure a TDM E1 connection for STM-1 upstream transmission.

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 vc12 0 gpon 0/3/1 ontid 3
gemportIndex 13
----End
Configuring Clock Synchronization

In this scenario, the E1/STM-1 line clock can be used to achieve network-wide clock
synchronization.
Prerequisites
The clock daughter board CKMC/CKMD must be on the SCU main control board.
Context
1.
clock.
2.
3.
4.
Procedure
a.
Issue 01 (2016-04-29)

1229

Access Module
Run the clock source command to configure the line clock of E1/STM-1 port 0/5/0
on the TOPA board as the system clock source. Set the ID of the clock source to 0.
The clock module automatically judges the type of the specified clock source (E1/
STM-1) and selects a reference source for phase lock based on priorities.
b.
Configure a priority for the system clock source.

Run the clock priority command to set the priority of clock source 0 to the highest
priority.
c.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801TOPA 0/5/0
E1
Normal
0
--YES
-----------------------------------------------------------------------------

a.

i.
ii.

b.

i.
ii.
port.
Issue 01 (2016-04-29)

1230

Access Module

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
c.

--------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
--------------------------------------------------------------0
YES
line
0/0/1
Normal
0
YES
1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ---------------------------------------------------------------------
----End
Configuring Congestion Control and Security Policies

Context
is recommended.
NOTE
Procedure
l

Issue 01 (2016-04-29)

1231

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


i.
Issue 01 (2016-04-29)

1232

Access Module
ii.


----End
Configuring Network Protection

Context
l
The upstream protection solution is STM-1 1+1 protection (OLTs must transmit services
upstream through STM-1 ports).
The downstream protection solutions are Type B protection and Type C single-homing
protection. For details on configurations, see 12.4.8 Configuring E2E Reliability. The
following uses Type C single-homing protection as an example.
Configure an STM-1 protection group.

Configure STM-1 ports 0/5/0 and 0/5/1 on the TOPA board as members in the same
protection group. When a hardware or line fault occurs at the protected port 0/5/0, the
system automatically switches services at the faulty port to the standby port 0/5/1.
Procedure
huawei(config)#protect-group 1 protect-target stm-nni-port workmode

unidirection
NOTICE
OLTs only support unidirectional STM-1 protection. When OLTs are interconnected with
SDH equipment, the STM-1 protection mode of the remote SDH equipment must be set
to unidirectional.
l

ONUs.
Issue 01 (2016-04-29)

1233

Access Module
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
The ONU ID is 1.


----End
Verifying Services
Prerequisites
Issue 01 (2016-04-29)

1234

Access Module
Networking
E1 port
loopback
ONU
OLT
E1 line tester
E1
ONU trace
the clock of
the OLT
OLT trace
the clock of
the tester
Internal
free-run
clock
Figure 13-10 Test setup for STM-1 upstream service
E1 port
loopback
ONU
OLT
STM-1 line tester

STM-1
ONU trace
the clock of
the OLT
OLT trace
the clock of
the tester
Internal
free-run
clock
Procedure
NOTE
Step 2 Use the E1 or STM-1 line tester to send packets for the test.
----End
Follow-up Procedure
l
Remote loopback on the OLT TOPA board
Local loopback on the OLT TOPA board
Issue 01 (2016-04-29)

1235

Access Module
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
TOPA
board
Loops back
signals to the
network side on
the TOPA board
on the OLT. This
loopback checks
whether the
service from the
TOPA board to
the network-side
channel is
normal.
Local
loopba
ck on
the
TOPA
board
Local
loopba
ck on
the
ONU
Issue 01 (2016-04-29)
Loops back
signals to the
user side on the
TOPA board on
the OLT. This
loopback checks
whether the link
between the
TOPA board and
the E1 port on
the ONU is
normal.
Loops back
signals to the
network side on
the ONU. This
loopback checks
whether the link
between the E1
port on the ONU
and the TOPA
board on the
OLT is normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1

top 0/5
huawei(config-iftop-0/5)#loopback 0
remote
Remote loopback

top-stm1 0/5
remote
E1 line
tester
ONU
OLT
E1
Local loopback

top 0/5
huawei(config-iftop-0/5)#loopback 0 local

top-stm1 0/5
local
ONU
E1 line
tester
OLT
E1
Local loopback

tdm 0/1
1236

Access Module
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
ONU
Loops back
signals to the
user side on the
ONU. This
loopback checks
whether the link
between the
ONU and user
terminal is
normal.
Networking
E1 line
tester
ONU
Configuration
OLT
E1
Remote loopback
tdm 0/1
remote
13.4.2 E1 Base Station Access Service (in SAToP Mode, GPON)

ONUs transmit E1 signals of base stations to OLTs in SAToP mode and OLTs are

Service Requirement
As a mainstream full-service access technology in the future, the passive optical network
(PON) supports fast deployment and service provisioning. It also helps simplify the access
network and reduce the costs on construction and subsequent maintenance of the access
network. Currently, carriers in China and outside China are using the PON to carry 2G/3G
base station services over their existing FTTx networks that are established for accessing
individual/enterprise users. In this manner, carriers can implement the access of all the
services at the access layer in an unified mode.
l
ONUs are connected to 2G or 3G base stations through E1/T1 ports.
GPON is used for carrying the mobile access network in a unified manner to meet
mobile carriers' requirements for a high bandwidth and high-density coverage of base
stations.
Existing SDH resources are utilized efficiently to implement high-quality transmission of

TDM services.
As shown in Figure 13-11, the ONU accesses E1/T1 services of the 2G or 3G base station
through the unified hardware port, and then transmits the service data to the OLT in the
SAToP mode. The OLT restores E1/T1 signals, and then transmits the signals to the SDH
network through the E1/T1 port. In this manner, service access of the 2G or 3G base station is
implemented between the ONU and the OLT in the SAToP mode.
Issue 01 (2016-04-29)

1237

Access Module
Figure 13-11 Networking diagram of E1/T1 base station access service

BTS
N*E1 ONU
NodeB
N*E1
BSC
OLT
N*E1
SDH
ONU
CX600
N*E1
E1
SAToP
E1
RNC
The following figure shows the configuration process for E1/T1 base station access service (in
SAToP mode).
Issue 01 (2016-04-29)

1238

Access Module
Start
Adding ONUs to OLT
and ONUs
OLT Side
Configuring SAToP
Connections and Service
Ports
Policies
Configuring Network
Protection
Configuring SAToP
Connections
ONU Side
Configuring Clock
Synchronization
Verifying Services
End
Issue 01 (2016-04-29)

1239

Access Module
Adding ONUs to OLT

Context
l
Data Plan
Item
Data
DBA profile
Profile ID: 20
DBA bandwidth:
Mbit/s)
Line profile
Profile ID: 10
T-CONT ID: 1
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Procedure
1.
2.

to DBA profile 20
Issue 01 (2016-04-29)

1240

Access Module
to T-CONT 1
12 to CVLAN 300
3.

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)

1241

Access Module

ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
Issue 01 (2016-04-29)

1242

Access Module

reachable.
l
configure the ONU.
----End
Configuring SAToP Connections and Service Ports

and a service port to enable packets of base stations to be encapsulated on ONUs and restored
on OLTs.
Prerequisites
l
Main control boards on the OLT: SCUN+CKMC/CKMD
Upstream board on the OLT: EDTB (for E1 upstream transmission)
Context
Figure 13-12 shows SAToP encapsulation for E1 base station access service. As shown in the
following figure, after TDM signals are encapsulated in the IP+UDP format, an outer VLAN
tag and an Ethernet header are added to the TDM signals. Then the TDM signals become a
standard Ethernet packet that is transmitted on the PON line between the ONU and OLT.
Figure 13-12 SAToP encapsulation
OLT
E1
ONU
SDH
NodeB
TDM
Issue 01 (2016-04-29)
E1/STM-1
SAToP
E1
TDM
TDM
UDP1
UDP1
IP1
IP1
VLAN
VLAN
ETH
ETH

TDM
1243

Access Module
Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
E1 port
(ONU)

VLAN
SVLAN: 300

recommended.
Procedure

l
E1 access:


Create TDM VCL 10.
l

dynamically.
Issue 01 (2016-04-29)

1244

Access Module
NOTE
10.10.50.20 remote-udp 50048

NOTE

Set the service port ID to 1, SVLAN ID to 300, GEM port ID to 12, and user VLAN ID to
300. The ONU limits upstream and downstream traffic rates but the OLT does not. Therefore,
use default traffic profile 6.
The user VLAN must be the same as the upstream VLAN of the ONU.
----End

In this scenario, the E1 line clock can be used to achieve network-wide clock synchronization.
Prerequisites
The CKMC/CKMD clock daughter board has been installed on the SCU main control board.
Context
1.
Issue 01 (2016-04-29)
The OLT traces the upstream E1 line clock of the EDTB board as the system clock.
1245

Access Module
2.
3.
4.
Procedure
a.

b.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H802EDTB 0/5/0
E1
Normal
0
--YES
-----------------------------------------------------------------------------

a.

i.
ii.

b.

i.
ii.
port.
Issue 01 (2016-04-29)

1246

Access Module

--------------------------------------Port
: 0
State
: normal
Mode
: UDT
Code
: HDB3
Looptype
: Timeslot
: Clock
: system
CRC4
: Signaling
: ESF
: Impedance
: 120 Ohm
---------------------------------------
c.

--------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
--------------------------------------------------------------0
YES
line
0/0/1
Normal
0
YES
1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ---------------------------------------------------------------------
----End

Context
is recommended.
NOTE
Procedure
l

Issue 01 (2016-04-29)

1247

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


i.
Issue 01 (2016-04-29)

1248

Access Module
ii.


----End

Context
The protection solutions supported in this scenario are Type B protection and Type C singlehoming protection.
Procedure
l

ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

Issue 01 (2016-04-29)

1249

Access Module
ONUs.
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
The ONU ID is 1.


----End
Configuring ONU SAToP Connections

Issue 01 (2016-04-29)

1250

Access Module
Data Plan
Configurati
on Item
Data
EDTB (OLT)
Port: 0/5/0
E1 port
(ONU)

VLAN
SVLAN: 300

recommended.
Procedure

l
system clock.

Create TDM VCL 10.
l

Issue 01 (2016-04-29)

1251

Access Module

10.10.50.10 remote-udp 50048
NOTE

NOTE
----End
Verifying Services
Prerequisites
Networking
E1 port
loopback
ONU
OLT
E1 line tester
E1
ONU trace
the clock of
the OLT
Issue 01 (2016-04-29)
OLT trace
the clock of
the tester

Internal
free-run
clock
1252

Access Module
Procedure
NOTE
----End
Follow-up Procedure
l
Issue 01 (2016-04-29)
Loopb
ack
Mode
Function
Remote
loopba
ck on
the
EDTB
board
Loops back
signals to the
network side on
the EDTB board
on the OLT. This
loopback checks
whether the
service from the
EDTB board to
the network-side
channel is
normal.
Local
loopba
ck on
the
EDTB
board
Loops back
signals to the
user side on the
EDTB board on
the OLT. This
loopback checks
whether the link
between the
EDTB board
and the E1 port
on the ONU is
normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
edt 0/5
remote
Remote loopback
E1 line
tester
ONU

OLT
E1
Local loopback


edt 0/5
1253

Access Module
Loopb
ack
Mode
Function
Local
loopba
ck on
the
ONU
Loops back
signals to the
network side on
the ONU. This
loopback checks
whether the link
between the E1
port on the ONU
and the EDTB
board on the
OLT is normal.
Remote
loopba
ck on
the
ONU
Loops back
signals to the
user side on the
ONU. This
loopback checks
whether the link
between the
ONU and user
terminal is
normal.
Networking
ONU
Configuration
E1 line
tester
OLT
E1
Local loopback
E1 line
tester
ONU
OLT
E1
Remote loopback
tdm 0/1
tdm 0/1
remote
13.4.3 Configuring Ethernet Base Station Access Service (in QinQ

VLAN Mode, GPON)
ONUs are connected to IP base stations through FE/GE Ethernet ports and OLTs are
interconnected with MAN equipment in QinQ VLAN mode to achieve access of base station
services. Alternatively, OLTs are interconnected with MAN equipment in command VLAN or
stacking VLAN mode to achieve access of base station services. You can plan the access
mode according to your requirements. The QinQ VLAN mode is described as an example.

Service Requirement
l
ONUs are connected to 3G/LTE base stations and GPON is used for carrying the mobile
access network in a unified manner to meet mobile carriers' requirements for a high
bandwidth and high-density coverage of base stations.
A simple, mature solution is used for service configuration to ensure high service quality
as well as high transmission efficiency.
As shown in Figure 13-16, ONUs receive the ETH service data from 3G base stations
through FE/GE ports, encapsulate the ETH packets into GEM frames, and then send them to
Issue 01 (2016-04-29)

1254

Access Module
the OLT through the GPON upstream ports. The OLT restores the ETH signals and configures
QinQ VLANs for the signals to enable the data of base stations to be transparently transmitted
to the remote PTN over the public network. Then the remote PTN device restores the ETH
signals.
Figure 13-16 Networking diagram of Ethernet base station access service
eNodeB
FE/GE
RNC
ONU
OLT
FE/GE
GE/10GE
NodeB
FE/GE
PSN
ONU
GE
CX600
RNC
FE/GE
ETH
GPON
QinQ
L2/L3 VPN
ETH
The following figure shows the configuration process for Ethernet base station access service
(in QinQ VLAN mode).
Issue 01 (2016-04-29)

1255

Access Module
Start
Adding ONUs to OLT
ONUs
OLT Side
Configuring OLT QinQ

VLANs and Service Ports
Policies
Configuring Network
Protection
ONU Side
Configuring Clock
Synchronization
Verifying Services
End
Adding ONUs to OLT

Issue 01 (2016-04-29)

1256

Access Module
Context
l
Data Planning
Configurati
on Item
Data
DBA profile
Profile ID: 20
Line profile
Profile ID: 10
T-CONT ID: 4
GEM port ID for management service of ONUs: 11
GEM Port ID for synchronization service of base stations: 12
GEM Port ID for OAM service of base stations: 13
GEM Port ID for voice and data services of base stations: 14
VLAN
(remark 1)
VLAN for management service of ONUs: 8

VLAN for base station access service:
l VLAN for synchronization service: 1000
l VLAN for OAM service: 1001
l VLAN for voice and data services: 1002
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Remark 1: Ethernet base stations have multiple services and different services require
different VLANs. The preceding table uses the synchronization service, OAM service, and
voice and data services as an example.
Procedure
1.

Issue 01 (2016-04-29)

1257

Access Module
2.

to DBA profile 20.
to T-CONT 4.
to T-CONT 4.
to T-CONT 4.
12 to CVLAN 1000.
13 to CVLAN 1001.
14 to CVLAN 1002.
3.

1.

2.


--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
online.
Config state
: normal
state.
----End
Follow-up Procedure
Issue 01 (2016-04-29)

1258

Access Module
ONU.

ONUs.
Data Plan
Configuration Item
Data

address for OLT

192.168.50.1/24

address for ONU

192.168.50.2/24
Procedure
192.168.50.1/24.
Issue 01 (2016-04-29)

1259

Access Module
255.255.255.0 gateway
192.168.50.1 vlan 8

profile 6.
reachable.
l
configure the ONU.
----End
Configuring OLT QinQ VLANs and Service Ports

This topic describes how to configure QinQ VLANs and service ports to enable various
packets received from base stations to be forwarded based on specified policies.
Prerequisites
The MAN equipment (for example, CX600) interconnected with the OLT must support the
QinQ VLAN encapsulation mode and be able to terminate QinQ VLANs.
Context
For details on VLAN planning, see 13.2.2 Principle of VLAN Data Plan. VLAN translation
policies for the Ethernet base station access service are shown in Figure 13-17.
l
Synchronization packets (remark 1) of the base station are untagged. A VLAN tag is
added to the packets on the ONU and the OLT transparently transmits the VLAN tag.
Different management packets of the base station carry different user VLANs (for
example, 20, 21, ... in the following figure). The user VLANs are translated to CVLAN
1001 on the ONU and then the OLT adds the outer VLAN 300 to the packets before
transmitting them upstream.
Different voice and data packets of the base station carry different user VLANs (for
example, 30, 31, ... in the following figure). The user VLANs are translated to CVLAN
1002 on the ONU and then the OLT adds the outer VLAN 300 to the packets before
transmitting them upstream.
In this manner, only two VLANs are required on the MAN for the base station access service,
which significantly reduces the number of VLANs.
Remark 1: In this example, the base station supports the clock over IP mode and is
synchronized with the IP clock server using the NTP protocol.
Issue 01 (2016-04-29)

1260

Access Module
Figure 13-17 VLAN translation for Ethernet base station access service
OLT
FE/GE
ONU
PSN
NodeB/
eNodeB
NodeB SYNC
NodeB OAM
QinQ
GPON
ETH
20,21,...
NodeB Traffic 30,31,...
NodeB SYNC
1000
NodeB SYNC
1000
NodeB OAM
1001
NodeB OAM
1001 300
NodeB Traffic
1002
NodeB Traffic
1002 300
Data Plan
Configuration Item
Data
SVLAN
VLAN for synchronization service of base stations: 1000

VLAN for voice and data services of base stations: 300
CVLAN (upstream
VALN of the ONU)

Traffic profile
OAM service and synchronization service of base stations:

l ID: 10
l CIR: OFF
l Ppriority source: user-cos, default priority: 7
l Priority policy: tag-in-package
Voice and data services of base stations:
l ID: 11
l CIR: 20 Mbit/s
l Priority source: user-inner-cos, default priority: 7
Issue 01 (2016-04-29)
ONT ID
PON port
PON port: 0/3/1

1261

Access Module
Procedure
Step 1 Configure QinQ VLANs.
Add two VLANs 1000 and 300 on the OLT, set attributes of the two VLANs to QinQ, and add
the upstream port to the two VLANs.
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
1000 smart
attrib 1000 q-in-q
vlan 1000 0/19 0
300 smart
attrib 300 q-in-q
vlan 300 0/19 0
Step 2 Configure traffic profiles.

l
Add a traffic profile 10 and do not limit rates. Packets transmitted upstream use the
priority (7 by default) copied from the user VLAN. Packets transmitted downstream use
the priority carried by themselves.
Add a traffic profile 11 and set the assured rate to 20 Mbit/s. Packets transmitted
upstream use the priority (7 by default) copied from the inner VLAN. Packets

huawei(config)#traffic table ip index 11 cir 20480 priority user-inner-cos 7
priority-policy tag-in-package
Step 3 Configure service ports.

Configure service ports for the synchronization service, OAM service, and voice and data
services of base stations.
user-vlan
1000 tag-transform transparent rx-cttr 10 tx-cttr 10 //Synchronization service
port
user-vlan
1001 tag-transform default rx-cttr 10 tx-cttr 10 //OAM service port
user-vlan
1002 tag-transform default rx-cttr 11 tx-cttr 11 //Voice and data service port
----End
Configuring Ethernet Access Service Ports on ONUs

Add a service port on an ONU and configure an upstream VLAN to make the ONU-to-user
service flows available and create an ONU-to-OLT upstream data channel.
Data Planning
Configuration
Item
Data
Port

Service port: 0/3/1
Issue 01 (2016-04-29)

1262

Access Module
Configuration
Item
Data
SVLAN
(upstream
VLAN of the
ONU)

User VLAN
(original VLAN
of packets from
base stations)
l Synchronization service of base stations: untagged
Traffic profile
l ID: 10
l VLAN for OAM service of base stations: 20

l VLAN for voice and data services of base stations: 30
l CIR: OFF
l Priority source: user-cos, default priority: 7
Procedure
Step 1 Create SVLANs and add an upstream port to the VLANs.
Create VLANs 1000, 1001, and 1002.
huawei(config)#vlan
huawei(config)#port
huawei(config)#port
huawei(config)#port
1000-1002
vlan 1000
vlan 1001
vlan 1002
smart
0/0 1
0/0 1
0/0 1

Add a traffic profile 10 and do not limit rates. Packets transmitted upstream use the priority (7
by default) copied from the user VLAN. Packets transmitted downstream use the priority
carried by themselves.
Step 3 Configure Ethernet access service ports.

services of base stations. According to 13.2.2 Principle of VLAN Data Plan, ONUs translate
user VLANs to a specified CVLAN.
untagged rx-cttr 10 tx-cttr 10 //Syncronization service port
20 rx-cttr 10 tx-cttr 10 //OAM service port
30 rx-cttr 10 tx-cttr 10 //Voice and data service port
NOTE
Packets from different base stations may carry different user VLANs. Ensure that user VLANs are consistent
with the actual ones during configuration.
----End
Issue 01 (2016-04-29)

1263

Access Module

In this scenario, the synchronous Ethernet clock can be used to achieve network-wide clock
synchronization.
Prerequisites
l
synchronization.
Context
According to actual requirements, Ethernet base stations support synchronous Ethernet
(frequency synchronization) and 1588v2 (time synchronization). This document uses
synchronous Ethernet as an example. For details about how to configure 1588v2 time
synchronization, see "13.3.6 Configuring 1588v2 Clock Synchronization".
Data Plan
Configuration
Item
Data
Upstream port
Port: 0/19/0
ETH port on the

ONU
0/3/1
Procedure
l

a.

Configure the Ethernet line clock input from GIU port 0/19/0 as the system clock 0.
Set the priority to 0 (highest priority).
b.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
Issue 01 (2016-04-29)

1264

Access Module
-----------------------------------------------------------------------------

The transmit clock of the port is the system clock by default when base stations are
connected to the ONU through ETH ports. The transmit clock cannot be modified.
Therefore, you only need to configure the system clock for the ONU.
a.
Configure the PON line clock as the system clock.

b.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End

Context
is recommended.
NOTE
Procedure
l
Issue 01 (2016-04-29)

1265

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)

1266

Access Module
i.

ii.


----End

This topic describes how to configure end-to-end (E2E) protection schemes for the base
station access service which has a high requirement on service reliability.
Context
l
time.
NOTE
Procedure
l


Configure upstream ports 0/19/0 and 0/19/1 on the GIU board as a port protection group.
Set port 0/19/0 as the working port and port 0/19/1 as the protection port, set the working
timedelay enable

Issue 01 (2016-04-29)

1267

Access Module
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
Issue 01 (2016-04-29)

1268

Access Module
The ONU ID is 1.



protection scheme.
Issue 01 (2016-04-29)

1269

Access Module
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
The ONU ID is 1.


----End
Issue 01 (2016-04-29)

1270

Access Module
Verifying Services
The Ethernet base station access service can be verified by checking the connectivity and
alarms of the service.
Prerequisites
The base station access service has been deployed.
Procedure
Step 1 Check connectivity.
1.
Check the connectivity between base stations and the IP clock server.
On base stations, configure management IP addresses and static routes to the IP clock
server, and then perform ping operations. In normal cases, the ICMP ECHO-REPLY
message can be received from the IP clock server.
2.
Check the connectivity between base stations and the OAM server.
On base stations, configure IP addresses of management channels and static routes to the
OAM server, and then perform ping operations. In normal cases, the ICMP ECHOREPLY message can be received from the OAM server.
3.
Check the connectivity between base stations and the RNC.

On base stations, configure service port IP addresses and static routes to the RNC, and
then perform ping operations. In normal cases, the ICMP ECHO-REPLY message can be
received from the RNC.
Step 2 Check alarms.

Check logs on base stations. Verify that no alarms are generated within 24 hours.
----End
13.4.4 Configuring Symmetrical TDM PWE3 Access for OLTs on

Both Sides (GPON)
Two OLTs are symmetrically connected to the packet switched network (PSN). Signals of
enterprise or base transceiver station (BTS) private line services are transmitted to an ONU
through an E1 port, and then the ONU sends the signals to the OLT through GPON lines. The
OLT, functioning as a superstratum provider edge (SPE), is connected to its peer OLT through
TDM PWE3. This enables the PSN network to carry traditional circuit switched (CS)
services.
Service Requirements and Application Scenario

Enhancing O&M capability: The MxU configurations can be performed on the OLT, which
simplifies the configuration process.
Minimizing network construction costs: Only 1 SPUB board is required for an OLT.
Allowing TDM services to traverse the packet switched network (PSN): TDM services are
deployed independently.
Issue 01 (2016-04-29)

1271

Access Module
As shown in Figure 13-21, OLT-A and OLT-B are symmetrically deployed on both sides of
the PSN network. Both OLT-A and OLT-B are connected to ONUs through GPON lines.
Enterprise or base transceiver station (BTS) private line services are transmitted to the ONUs
through E1 ports. Proprietary TOE channels between the ONUs and OLTs are used to
encapsulate the packets of TDM services. Symmetrical TDM PWs are created between the 2
OLTs to provide cross-PSN-network access and backhaul for enterprise or BTS private line
services.
Figure 13-21 Example network of symmetrical GPON TDM PWE3 access
OLT-A
ONU
BTS/
NodeB
OLT-B
ONU
IP/MPLS
E1
TDM
E1
ToE
PW1
PW2
ToE
RNC/
BSC
TDM
Configuration Procedure
The following figure shows the procedure of symmetrically configuring TDM PWE3 access
for OLTs on both sides of the packet switched network (PSN). Because the 2 OLTs are
symmetrically deployed, the configuration steps on the 2 OLT are the same.
Issue 01 (2016-04-29)

1272

Access Module
Start
Add ONUs to the OLT and
configure the management
service port
OLT-A/B
Configure the TDM

connection and TDM PW
OLT-A/B
Configure the congestion

control policy and security
policy
OLT-A/B
Configure network
protection
OLT-A/B
Configure clock
synchronization
OLT-A/B
/ONU
Verify services
End
Adding ONUs to the OLT and Configuring the Management Service Port
Related configurations can be performed for ONUs only after the ONUs are successfully
added to the OLT. After the inband management service port is created and available, you can
log in to the ONUs from the OLT to configure the ONUs.
Context
l
When an ONU is added, related profiles need to be bound to the ONU, including the
dynamic bandwidth allocation (DBA) profile, line profile, and alarm profile.
An ONU can be added in two modes: adding an ONU offline and confirming an ONU
online. Select either mode as required.
Issue 01 (2016-04-29)

1273

Access Module
Data Plan
Item
Data
DBA profile
DBA profile for management services: system default profile 1

DBA profile for private line services:
l Profile ID: 21
l Profile type: fixed bandwidth and minimum delay mode
l DBA bandwidth: 28928 kbit/s (assume that 4 E1 private lines are
connected to 1 ONU and each E1 private line is configured with a
bandwidth of 7232 kbit/s)
Line profile
Profile ID: 11
T-CONT 1 is used for private line services and T-CONT 2 for management
services.
GEM port ID for private line services: 13
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Management
VLAN and
management
IP address
On the OLT:
Management VLAN type: smart VLAN
Inband management IP address: 192.168.50.1/24
On the ONU:
Procedure
1.
Configure the DBA profile for private line services, enable bandwidth compensation,
and set the DBA bandwidth allocation mode of the GPON port to min-loop-delay.
2.
Configure the ONU line profile.

profile 21 to T-CONT 1.
Issue 01 (2016-04-29)

//Bind DBA
1274

Access Module
huawei(config-gpon-lineprofile-11)#tcont 2 dba-profile-id 1 //Bind DBA

to T-CONT 1.
huawei(config-gpon-lineprofile-11)#gem mapping 13 1 tdm-vcl //Map GEM port 13
to the TDM connection.
3.
(Optional) Configure the alarm profile.
generated.
Step 2 Add an ONU to the OLT.

1.
Add ONU 1 offline.

2.
(Optional) Bind the alarm profile to ONU 1.

By default, alarm profile 1 is automatically bound to the ONU. You need to manually
bind a non-default alarm profile to the ONU only when the default one does not meet the
requirement.
In this example, default alarm profile 1 is used, and therefore the configuration of the

After the ONU is added, run the display ont info command to query the status of the ONU.
Ensure that Config flag of the ONU is active, Run State is online, and Config state is
normal.
To query the status of ONU 1, do as follows:
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
normally.
Config state
: normal
//Indicates that the configuration recovery
state of the ONU is normal.
...//The following command output is omitted.
Create a VLAN whose ID is 8 as the inband management VLAN of the OLT, set the VLAN
priority to 6, and set the IP address of the VLAN interface to 192.168.50.1/24.
Issue 01 (2016-04-29)

1275

Access Module
255.255.255.0 gateway
192.168.50.1 vlan 8

The management VLAN is VLAN 8, the GEM port ID is 11, and user VLAN is VLAN 8. The
OLT does not limit the rate of inband management services. Therefore, you can directly bind
default traffic profile 6 to the inband management service port.
Step 7 Check whether the management service port between the OLT and the ONU is available.
l
Run the ping ONU ip command on the OLT to check the connectivity between the OLT
and the ONU. If the ICMP ECHO-REPLY packets from the ONU are received, the
connectivity between the OLT and the ONU is in good condition.
If you can remotely log in to the ONU from the OLT to perform configurations for the
ONU, the management service port between the OLT and the ONU is available.
----End
Follow-up Procedure
l
ONU.
Configuring the TDM Connection and TDM PW

A TDM connection between the OLT and ONU is created and bound to the PW, so that TDM
PWE3 services can be transmitted between two OLTs.
Prerequisites
The SPUB board is in position and functions normally.
Issue 01 (2016-04-29)

1276

Access Module
Data Plan
When OLTs are symmetrically connected to the packet switched network (PSN), the
configuration steps for OLT-A and OLT-B are the same, and only the configuration data varies
with the OLTs. The varied configuration data of OLT-A and OLT-B will be separately
described in this topic.
Item
Data
VLAN
1000
ONU E1 port
l Port ID: 0/1/0

l Port signaling mode: unstructured data transfer (UDT)
l Transmit clock of the port: system clock
IP address
OLT-A:
l IP address of the VLAN interface: 10.0.0.10/24
l IP address of the loopback interface: 1.1.1.1/32
OLT-B:
PW parameters
The following parameters must be the same on the 2 OLTs.

l PW ID: 1
l PW type: TDM SAToP E1
l Control word: enabled
l PW load time: 125 s
l Size of jitter buffer: 500 s
l RTP header: enabled
Procedure
Step 1 Configure the TDM connection.
1.
Configure the TDM virtual channel link (VCL) on the ONU.

On GPON port 0/3/1, create the TDM VCL for E1 port 0/1/0 of ONU 0.
NOTE
Each E81A board has 8 E1 ports. Port IDs 0 to 7 on board 0/1 correspond to ONT port IDs 1 to 8, port
IDs 0 to 7 on board 0/2 correspond to ONT port IDs 9 to 16, and so forth.
huawei(config-if-gpon-0/3)ont tdm-vcl 1 0 tdm-vcl-id 0 satop 1
huawei(config-if-gpon-0/3)quit
2.
Configure the TDM connection on the OLT.

huawei(config)tdm-connect connectid 0 tdm pwe3-uplink gpon 0/3/11 ontid 1
gemportIndex 13 tdm-vcl 0
Step 2 Configure the basic functions of multiprotocol label switching (MPLS).

Issue 01 (2016-04-29)

1277

Access Module
1.
Create VLAN 1000, add the upstream port into VLAN 1000, and configure the IP
address of VLAN interface 1000.
2.
Configure the IP address of the loopback interface and MPLS LSR ID.
3.
Enable MPLS, MPLS L2VPN, and MPLS LDP globally, and then enable MPLS and
MPLS LDP for the VLAN interface.
huawei(config)#mpls
Info: Mpls starting, please wait... OK!
4.
Configure a static route to the peer OLT.

Configure a static route from OLT-A to OLT-B.
Configure a static route from OLT-B to OLT-A.

After the static routes are configured successfully, ping the VLAN interface or LSR ID
of the peer OLT from one OLT. Normally, the ICMP ECHO-REPLY packets from the
peer OLT can be received.
Step 3 Configure the MPLS PW.
PW parameter peer-address (configured on the 2 OLTs) is set to the LSR ID of the peer OLT,
and other PW parameters must be set identically on the 2 OLTs.
ID of the peer OLT.
the attribute of the E1 port on the ONU.
//Set the peer address to the LSR

//The PW type must be the same as
//Configure the SAToP

encapsulation, and set the E1 port signaling mode to UDT.
huawei(config-pw-para-1)#rtp-header encap payload-type 0 sn 0 ssrc rcv 0 tx 0
Step 4 Dynamically bind PW 1 to the TDM connection.

Step 5 Configure the attributes of the E1 port on the ONU.

Log in to the ONU from the OLT, and then configure the port signaling mode of E1 port 0/1/0
to UDT and the transmit clock to system.
----End
Issue 01 (2016-04-29)

1278

Access Module
Follow-up Procedure
After all the configurations are performed successfully, the related information about the
CESoP connection can be queried by running the display cesop-connect command on the
ONU.
huawei(config)#display cesop-connect all
-----------------------------------------------------------------------------ID
PORT VCL ENCAP
REMOTEMAC
REMOTEIP LOCALUDP
REMOTEUDP VLAN
ID TYPE
/RXPWLABEL /TXPWLABEL
-----------------------------------------------------------------------------0
0/1 /0
0 MPLS e024-7f98-a21b
9343
8192 TOE
-----------------------------------------------------------------------------Total: 1

In this scenario, network-wide clock synchronization is implemented through synchronous
Ethernet clocks.
Prerequisites
l
The clock daughter board CKMC/CKMD of the SCU control board is in position.
The Ethernet upstream board is the GICK/GSCA (GE port) or X2CS/SPUF (10GE port)
board.
The upstream MAN PSN of the OLT supports Synchronous Ethernet.
Data Plan
Item
Data
Ethernet upstream
board
Port: 0/19/0
NOTE
The SPUF board exclusively occupies a service slot. This topic uses the GIU
upstream board as an example.
Procedure
l

a.

Use the Ethernet line clock input from GIU port 0/19/0 as the system clock. Set the
index of the system clock to 0 and priority to 0 (highest priority).
b.
Query the configurations and status of the system clock source.

Run the display clock source system command to query the configurations and
status of the clock source. Ensure that the configurations of the system clock source
are correct and the status of the system clock source is Normal.
----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
Issue 01 (2016-04-29)

1279

Access Module
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------
Run the display clock mode command to query the working mode of the clock.
Ensure that the working mode of the clock daughter board is Tracing.
Configure the ONU-side clock.

a.

b.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End

Context
is recommended.
NOTE
Procedure
l
Issue 01 (2016-04-29)

1280

Access Module
i.
ii.




i.

ii.

1)

2)

1)

2)

3)

effect.
4)
5)


flow.
iv.


Issue 01 (2016-04-29)

1281

Access Module
i.

ii.


----End

Context
l
time.
NOTE
Procedure
l


timedelay enable

Issue 01 (2016-04-29)

1282

Access Module
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
Issue 01 (2016-04-29)

1283

Access Module
The ONU ID is 1.



protection scheme.
Issue 01 (2016-04-29)

1284

Access Module
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
The ONU ID is 1.


----End
Verifying Services
Verifying private line services requires a dedicated E1 line test instrument.
Issue 01 (2016-04-29)

1285

Access Module
Prerequisites
The configuration of private line services has been completed.
Context
Because E1 access is applied to both sides of the packet switched network (PSN), an E1 line
test instrument can be used to verify services. The E1 line test instrument is connected to the
E1 port of the device on one side of the network after the port loopback or hardware loopback
is configured on the E1 port of the device on the other side of the network.
Procedure
Step 1 Configure a local loopback on the E1 port.
If the E1 port of the ONU is used to provide access for the private line services, the
configurations are as follows:
huawei(config-if-tdm-0/1)#loopback 0 local
This operation will interrupt the service, continue? (y/n)[n]:y
If the E1 port of the EDTB board on the OLT is used to provide access for the private line
services, the configurations are as follows:
huawei(config-if-edt-0/2)#loopback 0 local
Step 2 Use the E1 line test instrument to send packets.

NOTE
Ensure the synchronization between clocks. It is recommended that the E1 line test instrument should use the
self-generated clock, the OLT should trace the clock of the E1 line test instrument, and the ONU should trace
the clock of the OLT.
The test duration must be equal to or longer than 12 hours. No alarm information is displayed
on the test instrument, and the bit error rate (BER) must be lower than 1E-9.
----End
Follow-up Procedure
You can collect the packet statistics to check whether the CESoP and TDM connections are
normal.
l
Collect the statistics of packets sent and received by the CESoP connection on the ONU.
huawei(config)#display cesop-connect statistics 0
-----------------------------------------------------CONNECTID : 0
-----------------------------------------------------Lost Packet Count:
0
Received Packet Count:
58733
Transmitted Packet Count:
58732
Overflow Jitter Buffer Times:
0
Underflow Jitter Buffer Times:
0
Received Abnormal Packet Count:
0
Received Sn-error Packet Count:
0
Received Ssrc-error Packet Count: 0
------------------------------------------------------
In the command output, the number of received packets must be the same as that of sent
packets.
Issue 01 (2016-04-29)

1286

Access Module
Collect the statistics of packets sent and received by the TDM connection on the OLT.
huawei(config)#display tdm-connect statistics 0
--------------------------------------------------------------Statistics on ONU side:
Discarded Packets
: 0
Received Packets
: 132252
Transmitted Packets
: 132253
Received Error CESoP Packets
: 0
Received SN Error CESoP Packets
: 0
Received SSRC Error CESoP Packets
: 0
-------------------------------------------------------------
packets.
13.4.5 GPON Access for the OLT one Side and E1 or SHDSL
access for the OLT on the Peer Side
Signals of enterprise or base transceiver station (BTS) private line services are transmitted to
an ONU through an E1 port on one side of the packet switched network (PSN), and then
transmitted to the OLT through GPON lines. The OLT functions as a superstratum provider
edge (SPE) in this scenario. On the other side of the PSN network, signals of enterprise or
BTS private line services are transmitted to the OLT through E1 or SHDSL lines. TDM
PWE3 is created between the 2 OLTs on both sides of the PSN network to enable the PSN
network to carry traditional circuit switched (CS) services.

Minimizing network construction costs: Only 1 SPUB board is required for an OLT.
As shown in Figure 13-25, OLT-A and OLT-B are deployed on both sides of the PSN
network. OLT-A is connected to an ONU through GPON lines. Enterprise or base transceiver
station (BTS) private line services are transmitted to the ONU through an E1 port. A
proprietary TOE channel between the ONU and OLT is used to encapsulate the packets of
TDM services. Enterprise or BTS private line services are transmitted to OLT-B through E1 or
SHDSL lines. TDM PWs are created between the 2 OLTs to provide cross-PSN-network
access and backhaul for enterprise or BTS private line services.
Issue 01 (2016-04-29)

1287

Access Module
Figure 13-25 Example network of GPON access on one side and E1 or SHDSL access on the
peer side
OLT-A
ONU
BTS/
NodeB
OLT-B
MODEM
SHDSL
IP/MPLS
E1
TDM
E1
PW1
ToE
PW2
RNC/
BSC
TDM
The following figure shows the procedure of configuring GPON access for the OLT on one
side and E1 or SHDSL access for the OLT on the peer side of the packet switched network
(PSN). The configuration steps on the 2 OLT are the same, but the methods for configuring
TDM connections on the 2 OLTs are different.
Start
Add ONUs to OLT-A and
configure the
management service port
OLT-A
Configure the TDM

connection and TDM PW
OLT-A/B
Configure network
protection
Configure clock
synchronization
OLT-A
OLT-A/B
/ONU
Verify services
End
Adding ONUs to OLT-A and Configuring the Management Service Port

Related configurations can be performed for ONUs only after the ONUs are successfully
added to OLT-A. After the inband management service port is created and available, you can
log in to the ONUs from the OLT to configure the ONUs.
Issue 01 (2016-04-29)

1288

Access Module
Context
l
Data Plan
Item
Data
DBA profile
DBA profile for management services: system default profile 1

DBA profile for private line services:
l Profile ID: 21
l Profile type: fixed bandwidth and minimum delay mode
l DBA bandwidth: 28928 kbit/s (assume that 4 E1 private lines are
Line profile
Profile ID: 11
T-CONT 1 is used for private line services and T-CONT 2 for management
services.
Networking
data
PON port: 0/3/1

ONU parameters:
l ONU ID: 1
l SN: 3230313163902641
Management
VLAN and
management
IP address
On the OLT:
On the ONU:
Procedure
1.
Issue 01 (2016-04-29)
Configure the DBA profile for private line services, enable bandwidth compensation,
and set the DBA bandwidth allocation mode of the GPON port to min-loop-delay.
1289

Access Module

2.

to T-CONT 1.
huawei(config-gpon-lineprofile-11)#gem mapping 13 1 tdm-vcl //Map GEM port 13
to the TDM connection.
3.
generated.

1.
Add ONU 1 offline.

2.

requirement.

normal.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
normally.
Config state
: normal
Issue 01 (2016-04-29)

1290

Access Module
255.255.255.0 gateway
192.168.50.1 vlan 8

l
----End
Follow-up Procedure
l
ONU.
Issue 01 (2016-04-29)
1291

Access Module

A TDM connection is created between OLT-A and the ONU and bound to the PW. A TDM
connection for the E1 or SHDSL port is created on OLT-B. SPUB boards are used to transmit
TDM PWE3 services between the 2 OLTs.
Prerequisites
1.
The EDTB board on OLT-B is in position and functions normally.
2.
SPUB boards on OLT-A and OLT-B are in position and function normally.
Data Plan
Item
Data
VLAN
1000
ONU E1 port
l Port ID: 0/1/0

l Port signaling mode: unstructured data transfer (UDT)
l Transmit clock of the port: system clock
E1 or SHDSL
port parameters
on OLT-B
Slot for the EDTB board: 0/2

Port ID for E1 access: 0/2/0
Port ID for SHDSL access: 0/2/16
Transmit clock of the port: system clock
IP address
OLT-A:
OLT-B:
PW parameters
The following parameters must be the same on the 2 OLTs.

l PW ID: 1
Procedure
Issue 01 (2016-04-29)

1292

Access Module
OLT-A adopts GPON access. TDM connections need to be configured on the ONU and OLTA separately.
1.
Configure the TDM virtual channel link (VCL) on the ONU.

On GPON port 0/3/1, create the TDM VCL for E1 port 0/1/0 of ONU 0.
NOTE
Each E81A board has 8 E1 ports. Port IDs 0 to 7 on board 0/1 correspond to ONT port IDs 1 to 8, port
IDs 0 to 7 on board 0/2 correspond to ONT port IDs 9 to 16, and so forth.
huawei(config-if-gpon-0/3)ont tdm-vcl 1 0 tdm-vcl-id 0 satop 1
huawei(config-if-gpon-0/3)quit
2.
Configure the TDM connection on OLT-A.

huawei(config)tdm-connect connectid 0 tdm pwe3-uplink gpon 0/3/1 ontid 1
gemportIndex 13 tdm-vcl 0
OLT-B adopts E1 or SHDSL access. The following shows how to configure the TDM
connection.
l
For E1 access:
//The EDTB board must work
in the SAToP mode.
Success: Set the board workmode success
For SHDSL access:

huawei(config)#tdm-connect connectid 0 tdm pwe3-uplink 0/2 shdsl 0/2/16

1.
2.
3.
huawei(config)#mpls
4.


Issue 01 (2016-04-29)

1293

Access Module
ID of the peer OLT.



Step 5 Configure the attributes of the E1 port on the ONU.

Log in to the ONU from the OLT, and then configure the port signaling mode of E1 port 0/1/0
to UDT and the transmit clock to system.
Step 6 (Optional) Configure the attributes of the E1 or SHDSL port on OLT-B.

By default, the transmit clock of the E1 or SHDSL port is the system clock, and therefore the
configuration of the transmit clock is not required.
l
For E1 access:
huawei(config-if-edt-0/2)#clock-work 0 system
the system clock.
//The clock of the E1 port is
For SHDSL access:

huawei(config-if-edt-0/2)#tdm-clock clock-recovery-mode 0 retiming
----End
Follow-up Procedure
ONU.
-----------------------------------------------------------------------------ID
PORT VCL ENCAP
REMOTEMAC
REMOTEIP LOCALUDP
REMOTEUDP VLAN
ID TYPE
-----------------------------------------------------------------------------0
0/1 /0
0 MPLS e024-7f98-a21b
9343
8192 TOE
-----------------------------------------------------------------------------Total: 1
Issue 01 (2016-04-29)

1294

Access Module

Ethernet clocks.
Prerequisites
l
board.
Data Plan
Item
Data
Ethernet upstream
board
Port: 0/19/0
NOTE
Procedure
l

a.

b.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------
Issue 01 (2016-04-29)

1295

Access Module

a.

b.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End

Context
l
time.
NOTE
Procedure
l

l
Issue 01 (2016-04-29)

1296

Access Module
timedelay enable

ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
NOTE

ONUs.
Issue 01 (2016-04-29)

1297

Access Module
ONU
Tributary Fibers
Protection
Splitter A
OLT
Splitter B
Backbone Fibers
Protection
Active
Standby
The ONU ID is 1.



protection scheme.
Issue 01 (2016-04-29)

1298

Access Module
Active OLT
Splitter A
ONU
Splitter B
Standby OLT
Active
Standby
The ONU ID is 1.


----End
Verifying Services
Issue 01 (2016-04-29)

1299

Access Module
Prerequisites
Context
Procedure

NOTE
----End
Follow-up Procedure
normal.
l
-----------------------------------------------------CONNECTID : 0
0
58733
58732
0
0
0
0
------------------------------------------------------
packets.
Issue 01 (2016-04-29)

1300

Access Module
Discarded Packets
: 0
Received Packets
: 132252
Transmitted Packets
: 132253
: 0
: 0
: 0
-------------------------------------------------------------
packets.
13.4.6 Symmetrical E1 or SHDSL Access for OLTs on Both Sides

Signals of enterprise or base transceiver station (BTS) private line services are transmitted to
the OLTs on both sides of the packet switched network (PSN) through E1 or SHDSL lines.
TDM PWE3 is created between the 2 OLTs to enable the PSN network to carry circuit
switched (CS) services.
Minimizing network construction costs: Only 1 EDTB board is required for an OLT.
As shown in Figure 13-29, OLT-A and OLT-B are deployed on both sides of the PSN
network. Enterprise or base transceiver station (BTS) private line services are transmitted to
OLT-A and OLT-B through E1 or SHDSL lines. TDM PWs are created between the 2 OLTs to
provide cross-PSN-network access and backhaul for enterprise or BTS private line services.
Figure 13-29 Example network of symmetrical E1 or SHDSL access
OLT-A
MODEM
OLT-B
SHDSL
BTS/
NodeB
IP/MPLS
E1
E1
TDM
Issue 01 (2016-04-29)
MODEM
SHDSL
PW1
PW2

RNC/
BSC
TDM
1301

Access Module
The following figure shows the procedure of symmetrically configuring E1 or SHDSL access
for OLTs on both sides of the packet switched network (PSN). Because OLTs are
symmetrically deployed, the configuration steps on the 2 OLTs are the same, but the IP
addresses for specific interfaces are different.
Start
Configure the TDM
connection and TDM
PW
OLT-A/B
Configure clock
synchronization
OLT-A/B
Verify services
End

TDM connections for E1 or SHDSL ports are created on OLT-A and OLT-B. SPUB boards are
used to transmit TDM PWE3 services between the 2 OLTs.
Prerequisites
The EDTB and SPUB boards on OLT-A or OLT-B are in position and function normally.
Data Plan
When OLTs are symmetrically connected to the packet switched network (PSN), the
configuration steps for OLT-A and OLT-B are the same, and only the configuration data varies
with the OLTs. The varied configuration data of OLT-A and OLT-B will be separately
described in this topic.
Item
Data
VLAN
1000
E1 or SHDSL
port parameters
on the OLT
Slot for the EDTB board: 0/2

Port ID for E1 access: 0/2/0
Port ID for SHDSL access: 0/2/16
Issue 01 (2016-04-29)

1302

Access Module
Item
Data
IP address
OLT-A:

OLT-B:
PW parameters
l PW ID: 1
Procedure
Both OLT-A and OLT-B adopt E1 or SHDSL access. The following shows how to configure
the TDM connection.
l
For E1 access:
//The EDTB board must work
in the SAToP mode.
For SHDSL access:

huawei(config)#tdm-connect connectid 0 tdm pwe3-uplink 0/2 shdsl 0/2/16

1.
2.
3.
huawei(config)#mpls
Issue 01 (2016-04-29)

1303

Access Module
4.


ID of the peer OLT.



Step 5 (Optional) Configure the attributes of the E1 or SHDSL port.

By default, the transmit clock of the E1 or SHDSL port is the system clock, and therefore the
configuration of the transmit clock is not required.
l
For E1 access:
huawei(config-if-edt-0/2)#clock-work 0 system
the system clock.
//The clock of the E1 port is
For SHDSL access:

huawei(config-if-edt-0/2)#tdm-clock clock-recovery-mode 0 retiming
----End
Follow-up Procedure
ONU.
-----------------------------------------------------------------------------ID
PORT VCL ENCAP
REMOTEMAC
REMOTEIP LOCALUDP
REMOTEUDP VLAN
ID TYPE
------------------------------------------------------------------------------
Issue 01 (2016-04-29)

1304

Access Module
0
0/1 /0
0 MPLS e024-7f98-a21b
9343
8192 TOE
-----------------------------------------------------------------------------Total: 1

Ethernet clocks.
Prerequisites
l
board.
Data Plan
Item
Data
Ethernet upstream
board
Port: 0/19/0
NOTE
Procedure
l

a.

b.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------
Issue 01 (2016-04-29)

1305

Access Module


a.

b.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Verifying Services
Prerequisites
Context
Procedure
Issue 01 (2016-04-29)

1306

Access Module

NOTE
----End
Follow-up Procedure
normal.
l
-----------------------------------------------------CONNECTID : 0
0
58733
58732
0
0
0
0
------------------------------------------------------
packets.
l
Discarded Packets
: 0
Received Packets
: 132252
Transmitted Packets
: 132253
: 0
: 0
: 0
-------------------------------------------------------------
packets.
13.4.7 Configuring E1 Access for the ONU and Creating TDM

PWE3 Between the ONU and Peer PE (GPON)
An ONU is connected to the OLT through GPON lines. Signals of enterprise or base
transceiver station (BTS) private line services are transmitted to the OLT through the E1 port
on the ONU. TDM PWE3 is created between the ONU and the peer provider edge (PE)
CX600 to enable the packet switched network (PSN) to carry traditional circuit switched (CS)
services.
Issue 01 (2016-04-29)

1307

Access Module
Minimizing network construction costs: No CSPA or SPUB board is required on the OLT.
As shown in Figure 13-30, an ONU is connected to the OLT through GPON lines. Enterprise
or base transceiver station (BTS) private line services are transmitted to the ONU through an
E1 port. Static TDM PWs are created between the ONU and the peer provider edge (PE) to
provide cross-PSN-network access and backhaul for enterprise or BTS private line services.
Figure 13-30 Example network of E1 access for the ONU and TDM PWE3 between the ONU
and peer PE
ONU
BTS/
NodeB
OLT-A
CX600
IP/MPLS
E1/STM-1
E1
TDM
Static PW
RNC/
BSC
TDM
The following figure shows the procedure of configuring E1 access for the ONU and creating
TDM PWE3 between the ONU and peer PE.
Issue 01 (2016-04-29)

1308

Access Module
Start
Add ONUs to OLT-A and
configure the service port
for transparently
transmitting services
OLT-A
Configure the TDM VCL

and CESoP connection
on the ONU
ONU
Configure the static LSP

and PW on the CX600
CX600
Configure clock
synchronization
OLT-A/
ONU/CX600
Verify services
End
Adding ONUs to the OLT and Configuring the Management Service Port
Services can be configured for an ONU only after the ONU is successfully added to the OLT.
Context
l
Data Plan
Item
Data
DBA profile
Profile ID: 21
Profile type: fixed bandwidth and minimum delay mode
DBA bandwidth: 28928 kbit/s (assume that 4 E1 private lines are
Line profile
Profile ID: 11
T-CONT ID: 1
Issue 01 (2016-04-29)

1309

Access Module
Item
Data
Networking
data
PON port: 0/3/1
ONU parameters:
l ONU ID: 1
l SN: 32303131B39FD641
Management
VLAN and
management
IP address
On the OLT:
On the ONU:
Service
VLAN
300
Traffic
profile (for
transparent
transmission)
Index: 10
CIR: off
Policy: user-cos; default priority: 7
Priority policy: tag-in-package
Procedure
1.
Configure the DBA profile, and set the DBA bandwidth allocation mode of the GPON
port to min-loop-delay.
2.

to T-CONT 1.
13 to VLAN 300.
3.
Issue 01 (2016-04-29)
generated.
1310

Access Module

1.
Add ONU 1 offline.

2.

requirement.

normal.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
normally.
Config state
: normal
255.255.255.0 gateway
192.168.50.1 vlan 8

Issue 01 (2016-04-29)

1311

Access Module
l
Step 8 Configure the traffic profile and create the service port for transparently transmitting services.
Set the service VLAN (SVLAN) ID to 300, GEM port ID to 13, and customer VLAN
(CVLAN) ID to 300. The OLT does not limit the rate of services that are transparently
transmitted. Traffic profile 10 is bound to the service port for transparently transmitting
services.
huawei(config)#traffic table ip index 10 cir off priority user-cos 7 prioritypolicy tag-In-package
----End
Follow-up Procedure
l
ONU.
Configuring the TDM VCL and CESoP Connection on the ONU
Issue 01 (2016-04-29)

1312

Access Module
Data Plan
Item
Data
E1 port parameters
Port ID: 0/1/0

Port signaling mode: structured data transfer (SDT)
Port signaling: common channel signaling (CCS)
CRC-4 frame check: enabled
IP address: 10.0.0.10
Port timeslot: 1-15 (timeslot bitmap: 0xfffe)
Service VLAN
300
Static LSP parameters
Tx LSP label: 2000

Rx LSP label: 8200
Static PW parameters
Tx PW label: 8000
NOTE
The PW parameters on
the ONU must be the
same as those on the
CX600.
Rx PW label: 8500
RTP header: enabled
PW load time: 1000 s
Maximum jitter delay: 2 ms
Procedure
Step 1 Create the service VLAN and add an upstream port to the VLAN.
Step 2 Configure the attributes of the E1 Port.

huawei(config-if-tdm-0/1)#port 0 sdt system ccs crc enable
Step 3 Configure the TDM virtual channel link (VCL).

Set the TDM VCL ID to 0 and the type to CESoP, and use timeslot 1-16.
huawei(config)#tdm-vcl tdm-vcl-id 0 cesop 0/1/0 timeslot 0xfffe
Step 4 Configure the CESoP connection.

Use VLAN 300 to carry CESoP services. Set the Rx PW label to 8500, Tx PW label to 8000,
Rx LSP label to 8200, Tx LSP label to 2000, and gateway IP address (the next hop is the
CX600) to 10.0.0.20. Then configure the specific attributes of the CESoP connection.
huawei(config)#cesop-connect 1 tdm 0 vlan 300 rcv-pw-label 8500 trans-pw-label
8000
rcv-lsp-label 8200 trans-lsp-label 2000 gateway 10.0.0.20
huawei(config)#cesop rtp 1 enable
//Enable RTP header.
huawei(config)#cesop loadtime 1 1000
//The load time is 1000 s (namely 8
frames).
Issue 01 (2016-04-29)

1313

Access Module
huawei(config)#cesop jitter-buffer 1 2000

//The maximum jitter delay is 2 ms.
huawei(config)#cesop encap 0 ssrc rcv 0 tx 0
//Both the Tx and Rx SSRIDs are 0.
----End
Configuring the Static LSP and PW on the CX600

Data Plan
Item
Data
Parameters of the GE
sub interface
Sub interface ID: 1/0/0.1

VLAN to which the sub interface belongs: 300
IP address of the sub interface: 10.0.0.20/24
E1 port parameters
Port ID: 2/1/0

Working mode: channelized mode (CEL)
Timeslot: 1-15
Static LSP parameters
Parameters configured on the ingress node:

l Destination ID address: 10.0.0.10/32
l Next-hop IP address: 10.0.0.10
l Egress interface: GE sub interface 1/0/0.1
l Egress label: 8200 (the same as the Rx LSP label on the
ONU)
Parameters configured on the egress node:
l Ingress interface: GE sub interface 1/0/0.1
l Ingress label: 2000 (the same as the Tx LSP label on the
ONU)
Static PW parameters
Tx PW label: 8500 (the same as the Rx PW label on the ONU)
NOTE
The PW parameters on
the CX600 must be the
same as those on the
ONU.
Rx PW label: 8000 (the same as the Tx PW label on the ONU)

RTP header: enabled
Number of TDM frames encapsulated in each PW packet: 8
Maximum jitter delay: 2 ms
Procedure
Step 1 Configure the GE sub interface.
Set the ID of the sub interface to 1/0/0.1, add the sub interface to VLAN 300, and set the IP
address of the sub interface to 10.0.0.20/24.
[CX600]interface GigabitEthernet 1/0/0.1
[CX600-GigabitEthernet1/0/0.1]vlan-type dot1q 300
[CX600-GigabitEthernet1/0/0.1]ip address 10.0.0.20 24
[CX600-GigabitEthernet1/0/0.1]quit
Enable MPLS globally and then enable MPLS for the GE sub interface.
Issue 01 (2016-04-29)

1314

Access Module
[CX600]mpls
[CX600]interface GigabitEthernet 1/0/0.1
[CX600-GigabitEthernet1/0/0.1]mpls
Step 2 Configure the E1 port.

Configure E1 port 2/1/0. Set the working mode to CEL and timeslot 1-15 as a channel.
NOTE
The timeslot on the CX600 must be the same as that on the ONU.
[CX600]controller E1 2/1/0
[CX600-E1 2/1/0]using ce1
[CX600-E1 2/1/0]channel-set 0 timeslot-list 1-15
[CX600-E1 2/1/0]quit
Step 3 Configure the static route to the ONU.

Configure the static route whose destination IP address is the IP address of the E1 board on
the ONU and egress interface is GE sub interface 1/0/0.1.
[CX600]ip route-static 10.0.0.10 32 GigabitEthernet 1/0/0.1 10.0.0.10
Step 4 Configure the CX600 as the ingress node of the static LSP.
[CX600]static-lsp ingress lsp1 destination 10.0.0.10 32 nexthop 10.0.0.10
outgoing-interface GigabitEthernet 1/0/0.1 out-label 8200
Step 5 Configure the CX600 as the egress node of the static LSP.
[CX600]static-lsp egress lsp2 incoming-interface GigabitEthernet 1/0/0.1
in-label 2000
Step 6 Configure the static PW.

[CX600]interface Serial2/1/0:0
[CX600-Serial2/1/0:0]link-protocol tdm
[CX600-Serial2/1/0:0]mpls static-l2vc destination 10.0.0.10 transmit-vpn
-label 8500 receive-vpn-label 8000 rtp-header tdm-encapsulation 8 jitter-buffer 2
----End

Ethernet clocks.
Prerequisites
l
board.
Issue 01 (2016-04-29)

1315

Access Module
Data Plan
Item
Data
Ethernet upstream
board
Port: 0/19/0
NOTE
Procedure
l

a.

b.

----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------

a.

b.

-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/1
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
---
Issue 01 (2016-04-29)

1316

Access Module
3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Verifying Services
Prerequisites
Context
Procedure

NOTE
----End
Follow-up Procedure
normal.
Issue 01 (2016-04-29)

1317

Access Module
-----------------------------------------------------CONNECTID : 0
0
58733
58732
0
0
0
0
------------------------------------------------------
packets.
l
Discarded Packets
: 0
Received Packets
: 132252
Transmitted Packets
: 132253
: 0
: 0
: 0
-------------------------------------------------------------
packets.
13.4.8 Configuring Small-Cell Base Station Access Service

(through CLI Configuration, GPON)
Dock ONUs are connected to small-cell base stations through Ethernet ports, and OLTs
interconnect with the devices on the metro network through QinQ VLANs to provide the
access service for small-cell base stations. This topic describes how to implement the access
service of a small-cell base station through the CLI in the scenario without the U2000 NMS.
Service Requirements and Application Scenarios

As the last mile that connects users to the Internet, small-cell backhaul is an important part of
an FTTx network. For small-cell backhaul, customers expect to:
l
Make full use of the existing access resources to provide backhaul services for
distributed small-cell base stations.
Use a simple and mature service configuration scheme, featuring a high transmission
efficiency in addition to ensuring the QoS.
Simplify sites to lower the site installation and maintenance costs.
Issue 01 (2016-04-29)

1318

Access Module
Figure 13-31 Implementing access service of small-cell base stations
U2000
Small cell
ETH
GPON
Dock
RNC
GPON
OLT
ETH
GE/10GE
Small cell
GPON
ETH Dock
Metro
GPON
CX600
RNC
ETH
The following figure shows the configuration procedure for implementing the access service
of a small-cell base station (QinQ VLAN and CLI configuration).
OLT
ONU
Adding ONUs to OLT, and configuring

management service ports
Configuring OLT QinQ VLANs and
service ports
Configuring ethernet
access service ports
GPON Dock Configuring congestion control and

security policies
Configuring network protection
Cascading the DSLAM to the OLT

Configuring OLT QinQ VLANs and
VDSL2 Dock
service ports
Configuring congestion control
and security policies
Configuring network protection
Configuring the VDSL2

bonding group
Configuring the VDSL2
service ports
DSLAM
Cascading the DSLAM to the OLT

Prerequisites
In this scenario, only the MA5616 can be used as the DSLAM.
Issue 01 (2016-04-29)

1319

Access Module
Context
Here the traditional configuration method is used to cascade the DSLAM to the OLT.
Actually, you can also cascade the DSLAM to the DSLAM using the remote software
commissioning method (through the GE upstream channel). For details, see 10.8.4
Configuring the Management Channel Between an OLT and an ONU.
Data Plan
Configuration
Item
Data
Remarks
Ethernet cascading
port on the OLT
If the ETHB board is used

as the cascading board:
0/3/0
If the OPGD board is used

as the cascading board:
0/2/0
Management VLAN
and IP address of
the OLT
ID of the management
VLAN: 8
Type of the management
VLAN: smart
192.168.50.1/24
Management VLAN
and IP address of
the DSLAM
If you want to log in to the DSLAM

from the OLT for configuring the
DSLAM, ensure that the management
VLAN of the OLT is the same as that
of the DSLAM, and the management
IP address of the OLT and that of the
DSLAM are in the same network
segment.

VLAN: smart
192.168.50.2/24
Procedure
Step 1 Configure the working mode of the cascading board.
l
If the ETHB board is used as the cascading board, do as follows:

huawei(config-if-eth-0/3)#network-role cascade
NOTICE
If the working mode of the ETHB cascading board was originally extend, the board
resets after this operation is performed.
l
If the OPGD board is used as the cascading board, do as follows:

Issue 01 (2016-04-29)

1320

Access Module
Step 2 Configure the management channel between the OLT and the DSLAM.
1.
Configure the management VLAN and IP address of the OLT.

Set the ID of the management VLAN to 8, the VLAN priority to 6, and the management
IP address to 192.168.50.1/24.
2.
Configure the management VLAN and IP address of the DSLAM.

Log in to the DSLAM through a local serial port, and then set the ID of the management
VLAN to 8 and the management IP address to 192.168.50.2/24.
3.
(ETHB board working as the cascading board) Add the ports on the cascading board to
the management VLAN.
4.
(OPGD board working as the cascading board) Configure the management service flow.
The index of the service flow is 1, the ID of the management VLAN is 8, the Ethernet
cascading port is 0/2/0, and the ID of the user-side VLAN is 8. The OLT does not limit
the rate of the management service flow. Therefore, you can directly bind traffic profile 6
(default traffic profile) to the management service flow.
huawei(config)#service-port 1 vlan 8 eth 0/2/0 multi-service user-vlan 8 rxcttr 6 tx-cttr 6
5.
Check whether the management channel (namely, the management service flow)
between the OLT and the DSLAM is available.
You can run the ping 192.168.50.2 command on the OLT to check the connectivity
between the OLT and the DSLAM. If the OLT can receive ICMP ECHO-REPLY
packets sent from the DSLAM, the management channel between the OLT and the
DSLAM is available.
If you can remotely log in to the DSLAM from the OLT to perform configurations
for the DSLAM, the management channel between the OLT and the DSLAM is
available.
----End
Configuring the QinQ VLAN and Service Flow on the OLT

This topic describes how to configure the QinQ VLAN and service flow on the OLT so that
the various packets from small-cell base stations can be forwarded according to the specified
Prerequisites
The metro network device (for example, CX600) that interconnects with the OLT supports
and terminates the QinQ VLAN encapsulation.
Issue 01 (2016-04-29)

1321

Access Module
Context
Generally, a small-cell base station carries multiple types of packets, and the VLAN
translation policies for these packets are different, as listed in the following.
l
Synchronization service packets: The synchronization service packet (see Note 1) is an

untagged packet. The ONU adds a VLAN tag to the synchronization service packet, and
the DSLAM and OLT transparently transmit this packet with the VLAN tag.
Management packets: Management packets from different base stations carry different
user VLAN tags. The ONU translates the user VLAN tags of the management packets to
a uniform customer VLAN (C-VLAN) tag, and then the OLT adds an outer VLAN tag
(namely, S-VLAN tag) to these packets before sending them upstream..
Voice and data packets: Voice and data packets from different base stations carry
different user VLAN tags. The ONU translates the user VLAN tags of the voice and data
packets to a uniform C-VLAN tag (the C-VLAN tag of the voice and data packet cannot
be the same as that of the management packet), and then the OLT adds an outer VLAN
tag to these packets before sending them upstream.
In this way, only 2 VLANs are required for implementing the access service of a small-cell
base station on the metro network side. This greatly saves the VLAN resources.
Note 1: In this topic, the small-cell base station supports the clock over IP mode and
synchronizes with the IP clock server through the Network Time Protocol (NTP).
Data Plan
Configuration Item
Data
Service VLAN (SVLAN)
ID of the VLAN for the base station synchronization services:

1000
ID of the VLAN for base station voice and data services: 300
C-VLAN (upstream
VLAN on the ONU)

NOTE
The upstream C-VLAN on the DSLAM must be the same as the upstream
VLAN on the ONU.
Issue 01 (2016-04-29)

1322

Access Module
Configuration Item
Data
Traffic profile
For base station OAM services and synchronization services:

l ID: 10
l CIR: off
l Source of the priority: user-cos; default priority: 7.
l Priority policy for scheduling packets that enter a queue: TagIn-Package
For base station voice and data services:
l ID: 11
l CIR: 20 Mbps
l Source of the priority: user-inner-cos; default priority: 7.
l Priority policy for scheduling packets that enter a queue: TagIn-Package
Ethernet cascading
port on the OLT
If the ETHB board is used as the cascading board: 0/3/0

If the OPGD board is used as the cascading board: 0/2/0
Procedure
Step 1 Configure QinQ VLANs.
Add two VLANs 1000 and 300 on the OLT, set attributes of the two VLANs to QinQ, and add
the upstream port to the two VLANs.
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
1000 smart
attrib 1000 q-in-q
vlan 1000 0/19 0
300 smart
attrib 300 q-in-q
vlan 300 0/19 0
Step 2 Configure traffic profiles.

l
Add a traffic profile 10 and do not limit rates. Packets transmitted upstream use the
priority (7 by default) copied from the user VLAN. Packets transmitted downstream use
the priority carried by themselves.
Add a traffic profile 11 and set the assured rate to 20 Mbit/s. Packets transmitted
upstream use the priority (7 by default) copied from the inner VLAN. Packets

huawei(config)#traffic table ip index 11 cir 20480 priority user-inner-cos 7
priority-policy tag-in-package
Step 3 Configure a service channel.

l
If the ETHB board is used as the cascading board, no service flow needs to be
configured on the OLT. You only need to add the Ethernet cascading port (for example,
0/3/0) to each S-VLAN.
Issue 01 (2016-04-29)

1323

Access Module
If the OPGD board is used as the cascading board, you need to configure a service flow
for each of the base station services (synchronization service, OAM service, and voice
and data service) on the OLT.
1000 tag-transform default rx-cttr 10 tx-cttr 10 //Base station
synchronization service flow
huawei(config)#service-port vlan 300 eth 0/2.0 multi-service user-vlan
1001 tag-transform default rx-cttr 10 tx-cttr 10 //Base station OAM service
flow
1002 tag-transform default rx-cttr 11 tx-cttr 11 //Voice and data service
flow
----End
Configuring the VDSL2 Bonding Group and Service Flow on the DSLAM
Data Plan
Configuration
Item
Data
Upstream VLANs
10001002
VDSL2 bonding
group
l Index of the bonding group: 1

l Primary port: 0/3/0
l Member ports: 0/3/1 to 0/3/3
l Bonding scheme: EFM
l ID of the profile of the bonding group: 1 (system default profile)
l Multiple services distinguished by different user VLANs
Service flow
l The user VLAN and the service VLAN (S-VLAN) of the same
service flow must be the same.
Procedure
Step 1 Create an S-VLAN and add the upstream port to the S-VLAN.
Create VLANs 1000, 1001, and 1002. Add the upstream port to these 3 VLANs.
huawei(config)#vlan
huawei(config)#port
huawei(config)#port
huawei(config)#port
1000-1002
vlan 1000
vlan 1001
vlan 1002
smart
0/0 1
0/0 1
0/0 1
Step 2 Configure the VDSL2 bonding group.

The index of the bonding group is 1, the primary port of the bonding group is 0/3/0, the
member ports are 0/3/1, 0/3/2, and 0/3/3, the bonding scheme is EFM, and system default
profile 1 is used to activate this bonding group.
huawei(config)#bonding-group add 1 primary-port 0/3/0 scheme efm peer-scheme efm
huawei(config)#bonding-group link add 1 0/3/1
huawei(config)#active bonding-group 1 profile-index 1
Step 3 Configure VDSL2 service flows.

Issue 01 (2016-04-29)

1324

Access Module
In the VDSL2 bonding group, create a service flow for VLANs 1000, 1001, and 1002
respectively. When creating service flows, ensure that the user VLAN and the S-VLAN of the
same service flow are the same, and system default traffic profile 6 is bound to the service
flows both in upstream and downstream directions (this indicates that rate of the service flows
is not limited).
1000
inbound traffic-table index
1001
1002
vlan 1000 vdsl mode ptm 0/3/0 multi-service user-vlan

6 outbound traffic-table index 6
----End
Configuring Ethernet Access Service Ports on ONUs

Add a service port on an ONU and configure an upstream VLAN to make the ONU-to-user
service flows available and create an ONU-to-OLT upstream data channel.
Data Planning
Configuration
Item
Data
Port

Service port: 0/3/1
SVLAN
(upstream
VLAN of the
ONU)

User VLAN
(original VLAN
of packets from
base stations)
l Synchronization service of base stations: untagged
Traffic profile
l ID: 10
l VLAN for OAM service of base stations: 20

l VLAN for voice and data services of base stations: 30
l CIR: OFF
l Priority source: user-cos, default priority: 7
Procedure
Step 1 Create SVLANs and add an upstream port to the VLANs.
Create VLANs 1000, 1001, and 1002.
huawei(config)#vlan
huawei(config)#port
huawei(config)#port
huawei(config)#port
Issue 01 (2016-04-29)
1000-1002
vlan 1000
vlan 1001
vlan 1002
smart
0/0 1
0/0 1
0/0 1

1325

Access Module

Add a traffic profile 10 and do not limit rates. Packets transmitted upstream use the priority (7
by default) copied from the user VLAN. Packets transmitted downstream use the priority
carried by themselves.
Step 3 Configure Ethernet access service ports.

services of base stations. According to 13.2.2 Principle of VLAN Data Plan, ONUs translate
user VLANs to a specified CVLAN.
untagged rx-cttr 10 tx-cttr 10 //Syncronization service port
20 rx-cttr 10 tx-cttr 10 //OAM service port
30 rx-cttr 10 tx-cttr 10 //Voice and data service port
NOTE
Packets from different base stations may carry different user VLANs. Ensure that user VLANs are consistent
with the actual ones during configuration.
----End

Context
is recommended.
NOTE
Procedure
l

Issue 01 (2016-04-29)
Enable deny of service (DoS) anti-attack on both the OLT and optical network units
(ONUs).
i.
ii.

1326

Access Module


----End

Ethernet clocks.
Prerequisites
l
synchronization.
Context
The clock synchronization scheme of a small-cell base station can be synchronous Ethernet
(frequency synchronization) or IEEE 1588v2 (time synchronization). This topic uses the
synchronous Ethernet as an example to describe how to configure clock synchronization. For
IEEE 1588v2 time synchronization configurations, see 13.3.6 Configuring 1588v2 Clock
Synchronization.
Data Plan
Configuration
Item
Data
GIU upstream board
Port: 0/19/0
DSLAM (MA5616)
port
ONU Port
UNI interface: 0/3/0
Procedure
l
Issue 01 (2016-04-29)

1327

Access Module
a.

b.

status of the system clock source. Ensure that the configurations of the system clock
source are correct and the status of the system clock source is Normal.
----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------
(ONU functioning as the VDSL2 Dock device) Configure the DSLAM-side clock.
When the ONU functions as the VDSL2 Dock device, the MA5694S (ONU) is
connected upstream to the DSLAM (MA5616) through VDSL2 bonding. In this way,
you need to configure clock synchronization on the OLT, DSLAM, and ONU.
Use the line clock obtained from the upstream port as the system clock.
huawei(config)#clock source 0/0/1

When a small-cell base station is connected to an ONU through the Ethernet port, the
port transmit clock is defaulted to the system clock and cannot be modified. Therefore,
you need to configure only the system clock of the ONU.
When the ONU functions as the GPON Dock device, the MA5694S is connected
upstream to the OLT through the GPON port. In this way, you need to configure clock
synchronization on the OLT and ONU.
a.
b.

Run the display clock source command to query the configurations and status of
-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
Issue 01 (2016-04-29)

1328

Access Module
-------------------------------------------------------------------0
line
0/0/0
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Configuring End to End Protection

The access service of a small-cell base station has high requirements on reliability.
Configuring end-to-end (E2E) protection well addresses the requirements.
Context
Configuring upstream and downstream network protection can improve the network
reliability. For details, see 12.3.6 Principle of Reliability Data Plan. Among these reliability
configurations:
l
The upstream network protection schemes include link aggregation and protection
groups. Generally, the link aggregation is configured if the GIU board is used for
upstream transmission; the protection group is configured if the control board is used for
upstream transmission. Link aggregation and protection group are not configured at the
same time.
The downstream network protection (specifically, type B protection) is intended for

service ports.
NOTE
This topic lists several protection schemes supported by the MA5694S. You are advised to choose the proper
scheme based on the carriers' requirements and actual network conditions.
Procedure
l

Create a link aggregation group and add upstream ports 0/19/0 and 0/19/1 to the
aggregation group. Each member port in the aggregation group forwards packets based
on the source MAC address. The working mode of the aggregation group is LACP static
aggregation.
Configured a protection group.

Create a protection group and add upstream ports 0/19/0 and 0/19/1 on board GIU to the
protection group (among which, port 0/19/0 is the working port of the protection group,
while port 0/19/1 is the protection port). Set the working mode of the protection group to
the delay detection mode, and then enable the protection group.
timedelay enable
Configure type B protection.

Figure 13-32 shows the example network with type B protection.
Issue 01 (2016-04-29)

1329

Access Module
Figure 13-32 Type B network protection
ONU
OLT
Backbone Fibers
Protection
Splitter
Active
Standby
Create a type B protection group and add ports 0/3/1 and 0/3/2 on the same GPON board
of the OLT to the group. Specifically, port 0/3/1 is the working port and port 0/3/2 is the
protection port. When port 0/3/1 is faulty, the system can automatically switch services
to port 0/3/2 to ensure continued service access.
NOTE
Service configurations on the ONU remain unchanged before and after type B protection is configured.
That is, service configurations are applied only to the active GPON port.
----End
Verifying Services
Prerequisites
Procedure
1.
2.
3.
Issue 01 (2016-04-29)

1330

Access Module
----End
13.4.9 Configuring Small-Cell Base Station Access Service

(through GUI Pre-Deployment, GPON)
Dock ONUs are connected to small-cell base stations through Ethernet ports, and OLTs
interconnect with the devices on the metro network through QinQ VLANs to provide the
access service for small-cell base stations. This topic describes how to implement the access
service of a small-cell base station through GUI pre-deployment in the scenario with the
U2000 NMS available.
Service Requirements and Application Scenarios

As the last mile that connects users to the Internet, small-cell backhaul is an important part of
an FTTx network. For small-cell backhaul, customers expect to:
l
Make full use of the existing access resources to provide backhaul services for
distributed small-cell base stations.
Use a simple and mature service configuration scheme, featuring a high transmission
efficiency in addition to ensuring the QoS.
Simplify sites to lower the site installation and maintenance costs.
As shown in Figure 13-33, ONUs, functioning as Dock devices, receive Ethernet service data
from small-cell base stations through Ethernet ports and then send the service data to the OLT.
The OLT restores the Ethernet signals and adds 2 VLAN tags (QinQ VLAN encapsulation) to
the data, so that the data from the small cell bases can be transparently transmitted to the peer
PTN devices through the public network and then the PTN devices restore them to the
original data.
ONU applicable to this scenario: MA5694S
Issue 01 (2016-04-29)

1331

Access Module
Figure 13-33 Implementing access service of a small-cell base station

U2000
Small cell
GPON
Dock
ETH
RNC
GPON
OLT
ETH
GE/10GE
Small cell
GPON
ETH Dock
CX600
Metro
GPON
RNC
ETH
The following figure shows the configuration procedure for implementing the access service
of a small-cell base station (in QinQ VLAN mode through GUI pre-deployment).
U2000
OLT
ONU
Configuring the IP Address of the NMS

Server and the IP Address Pool of the
ONU
GPON Dock
Creating the Authentication-Free Policy

and Associating It with the OLT
End
Configuring the Remote Software

Commissioning Policy
Configuring the IP Address of the NMS

Server
VDSL2 Dock
Creating the Authentication-Free Policy

Configuring the Remote Software
Commissioning Policy
Adding the P2P Pre-Deployment Policy
Adding VDSL2 Bonding Group on

the DSLAM
Adding the P2P Pre-Deployment
Policy
DSLAM
Configuring the IP Address of the NMS Server and the IP Address Pool of the
ONU (GPON Dock Scenario)
Prerequisites
l
The OLT is added to the NMS.
Related xFTP configurations are completed.
Issue 01 (2016-04-29)

1332

Access Module
Data Plan
Configurati
on Item
Data
Remarks
IP address of
the NMS
server
10.10.10.10
The NMS server needs to use ports 23,

8080, 9801, and 9803. Therefore, ensure
that the firewall does not block these
ports so that the NMS server can
normally communicate with devices.
IP address of
the OLT
10.10.10.20
This IP address is designated for Layer 3

VLAN interface 8 and is used for inband
management.
IP address
pool of the
ONU
IP address pool: 10.10.11.2 to

10.10.11.125
The ONU gateway IP address is used as

the IP address of the Layer 3 interface on
the OLT.
Subnet mask: 255.255.254.0

ONU gateway: 10.10.10.20
VLAN priority: 7
Procedure
l
Configure the IP address of the NMS server used for receiving traps.
The OLT reports FTTM ONU information to the NMS through traps. Here the trap
destination host (namely, the destination host to which traps are sent) is the NMS server.
For any OLT, only 1 trap destination host is required. If multiple trap destination hosts
are configured for the OLT, delete the unnecessary ones.
Issue 01 (2016-04-29)
a.
Choose Administration > NE Communicate Parameter > Set NE SNMP

Expanded Parameters (traditional style) from the main menu or select FixNetwork NE Configuration in Application Center and choose Administration >
NE Communicate Parameter > Set NE SNMP Expanded Parameters
(application style) from the main menu.
b.
Click Filter. In the Select Device dialog box, select the desired OLT from the
Device Type drop-down list and click OK.
c.
In the device list, select a record and click the Target Host tab.
d.
On the Target Host tab, right-click in a blank area and choose Add from the
shortcut menu.
e.
In the dialog box that is displayed, set the parameters, as shown in Figure 13-34.

1333

Access Module
Figure 13-34 Configuring the trap destination host
f.
l
Click OK.
Configure the IP address pool of the ONU.

On an FTTM network, IP addresses are automatically allocated because no
authentication is required. In this way, an ONU IP address pool needs to be configured
so that ONUs, when going online, can automatically obtain an IP address.
a.
Choose Configuration > FTTx Service Pre-Deployment > ONU IP Pool

Management (traditional style) from the main menu or select Fix-Network NE
Configuration in Application Center and choose Access Service > FTTx Service
Pre-Deployment > ONU IP Pool Management (application style) from the main
menu.
b.
In the information list, right-click and choose Add from the shortcut menu.
c.
In the dialog box that is displayed, set the parameters, as shown in Figure 13-35.
Figure 13-35 Configuring the IP address pool of the ONU
MA5600T
d.
Click OK.
----End
Issue 01 (2016-04-29)

1334

Access Module
Creating the Authentication-Free Policy and Associating It with the OLT (GPON
Dock Scenario)
Prerequisites
You have completed the configurations of the following profiles:
l
SNMP profile
DBA profile
Line profile
MEF IP traffic profile
Context
If you configure an ONU authentication-free policy and associate it with the OLT through the
NMS, the FTTM ONU, when going online, will be automatically added to the NMS
according to the ONU type and the authentication-free policy.
Data Plan
Configuration Item
Data
SNMP profile
Name: snmpv1
DBA profile
Name: MA5694S_dba
Line profile
Name: MA5694S_lineprofile
Management service flow
Name: pvc_manage. The attributes of the management

service flow are as follows:
l Smart VLAN ID: 8
l multi-service user-vlan (multiple services distinguished
by different user VLANs)
l User VLAN ID: 8
l VLAN translation policy: translate
l Upstream and downstream traffic profile: ip-traffictable_6
Voice and data service flow
Name: pvc_traffic. The attributes of the voice and data

l Smart VLAN ID: 300
l User VLAN ID: 1002
l VLAN translation policy: translate-and-add
Issue 01 (2016-04-29)

1335

Access Module
Configuration Item
Data
Base station synchronization

service flow
Name: pvc_sync. The attributes of the base station

synchronization service flow are as follows:
l VLAN translation policy: transparent
Base station OAM service

flow
Name: pvc_oam. The attributes of the base station OAM

Procedure
Step 1 Configure the FTTM GPON ONU authentication-free policy.
1.
Choose Configuration > FTTx Service Pre-Deployment > ONU PnP Management
(compatibility style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Access Service > FTTx Service Pre-Deployment >
ONU PnP Management (application style) from the main menu.
2.
Click the ONU Authentication-Free Configuration tab.
3.
Right-click in a blank area and choose Add from the shortcut menu. Configure related
parameters in the displayed Add ONU Authentication-Free Configuration dialog box,
as shown in Figure 13-36.
Issue 01 (2016-04-29)

1336

Access Module
Figure 13-36 Configuring the ONU authentication-free policy
snmpv1
MA5694S_lineprofile
4.
Right-click Service Port in the navigation tree and choose Add Service Port from the
shortcut menu to add service ports according to services supported by the small cell.
Figure 13-37 shows how to add a management service flow; Figure 13-38 shows how to
add a voice and data service flow.
Figure 13-37 Adding a management service flow
ip-traffic-table_6
Issue 01 (2016-04-29)

ip-traffic-table_
1337

Access Module
Figure 13-38 Adding a voice and data service flow
ip-traffic-table_11
ip-traffic-table_1
Step 2 Associate the ONU authentication-free policy with the OLT.

1.
In the authentication-free policy list, select the MDU authentication-free policy and click
the NE Reference tab in the lower pane.
2.
On the NE Reference tab, right-click the OLT and choose Associate from the shortcut
menu.
----End
Configuring the Remote Software Commissioning Policy (GPON Dock Scenario)

Prerequisites
The configuration script is available.
Context
If you configure a remote software commissioning policy through the NMS, the NMS,
according to the ONU type and the configured policy, will automatically issue the
configuration script to the FTTM ONUs once the ONUs go online, and the service channels
will be automatically established.
Procedure
Step 1 Choose Configuration > FTTx Service Pre-Deployment > ONU PnP Management
Application Center and choose Access Service > FTTx Service Pre-Deployment > ONU
PnP Management (application style) from the main menu.
Step 2 Click the ONU Onsite Commissioning-Free Configuration tab.
Step 3 Right-click in a blank area and choose Add from the shortcut menu. In the dialog box that is
displayed, configure a GPON-upstream MDU commissioning-free policy.
Issue 01 (2016-04-29)

1338

Access Module
The following figure shows the configuration dialog box.
----End
Configuring the IP Address of the NMS Server (VDSL2 Dock Scenario)

Prerequisites
l
The OLT is added to the NMS.
Related xFTP configurations are completed.
Context
The OLT reports FTTM ONU information to the NMS through traps. Here the trap
destination host (namely, the destination host to which traps are sent) is the NMS server.
For any OLT, only 1 trap destination host is required. If multiple trap destination hosts are
configured for the OLT, delete the unnecessary ones.
Data Plan
Issue 01 (2016-04-29)
Configurati
on Item
Data
Remarks
IP address of
the NMS
server
10.10.10.10/24
The NMS server needs to use ports 23,

8080, 9801, and 9803. Therefore, ensure
that the firewall does not block these
ports so that the NMS server can
normally communicate with devices.

1339

Access Module
Configurati
on Item
Data
Remarks
IP address of
the OLT
10.10.10.20/24
This IP address is designated for Layer 3

VLAN interface 8 and is used for inband
management.
Procedure
Step 1 Choose Configuration > Router/Switch/Security Configuration > Switch EPON
Template (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Configuration > Router/Switch/Security Configuration >
Switch EPON Template (application style) from the main menu.
Step 2 Click Filter. In the Select Device dialog box, select the desired OLT NE from the Device
Type drop-down list and click OK.
Step 3 In the device list, select a record and click the Target Host tab.
Step 4 On the Target Host tab, right-click in a blank area and choose Add from the shortcut menu.
Step 5 In the dialog box that is displayed, set the parameters, as shown in Figure 13-39.
Figure 13-39 Configuring the trap destination host
Step 6 Click OK.

----End
Creating the Authentication-Free Policy (VDSL2 Dock Scenario)

Prerequisites
You have completed the configurations of the following profiles:
l
SNMP profile
DBA profile
Issue 01 (2016-04-29)

1340

Access Module
Line profile
MEF IP traffic profile
Context
If you configure an ONU authentication-free policy and associate it with the OLT through the
NMS, the FTTM ONU, when going online, will be automatically added to the NMS
according to the ONU type and the authentication-free policy.
Data Plan
Configuration Item
Data
SNMP profile
Name: snmpv1
DBA profile
Name: MA5694S_dba
Line profile
Name: MA5694S_lineprofile
Management service flow
Name: pvc_manage. The attributes of the management

l Smart VLAN ID: 8
l User VLAN ID: 8
l VLAN translation policy: translate
Voice and data service flow
Name: pvc_traffic. The attributes of the voice and data

Base station synchronization

service flow
Name: pvc_sync. The attributes of the base station

synchronization service flow are as follows:
l VLAN translation policy: transparent
Issue 01 (2016-04-29)

1341

Access Module
Configuration Item
Data
Base station OAM service

flow
Name: pvc_oam. The attributes of the base station OAM

Procedure
Step 1 Configure the FTTM ONU authentication-free policy in the VDSL2 upstream transmission
scenario.
1.
Choose Configuration > FTTx Service Pre-Deployment > ONU PnP Management
Application Center and choose Access Service > FTTx Service Pre-Deployment >
ONU PnP Management (application style) from the main menu.
2.
Click the ONU Authentication-Free Configuration tab.
3.
Right-click in a blank area and choose Add from the shortcut menu. Configure related
parameters in the displayed Add ONU Authentication-Free Configuration dialog box,
as shown in Figure 13-40.
Figure 13-40 Configuring the ONU authentication-free policy
4.
Issue 01 (2016-04-29)
Right-click Service Port in the navigation tree and choose Add Service Port from the
shortcut menu to add service ports according to services supported by the small cell.
1342

Access Module
Figure 13-41 shows how to add a management service flow; Figure 13-42 shows how to
add a voice and data service flow.
Figure 13-41 Adding a management service flow
ip-traffic-table_6
ip-traffic-table_
Figure 13-42 Adding a voice and data service flow
ip-traffic-table_11
ip-traffic-table_1
----End
Configuring the Remote Software Commissioning Policy (VDSL2 Dock

Scenario)
Issue 01 (2016-04-29)

1343

Access Module
Prerequisites
l
The configuration script is available.
Ensure that the database of MA5694S is empty. Otherwise, the remote software
commissioning cannot be used.
Context
If you configure a remote software commissioning policy through the NMS, the NMS,
according to the ONU type and the configured policy, will automatically issue the
configuration script to the FTTM ONUs once the ONUs go online, and the service channels
will be automatically established.
Procedure
Step 1 Choose Configuration > FTTx Service Pre-Deployment > ONU PnP Management
Application Center and choose Access Service > FTTx Service Pre-Deployment > ONU
PnP Management (application style) from the main menu.
Step 2 Click the ONU Onsite Commissioning-Free Configuration tab.
Step 3 Right-click in a blank area and choose Add from the shortcut menu. In the dialog box that is
displayed, configure a VDSL2-upstream MDU commissioning-free policy.
The following figure shows the configuration dialog box.
----End
Example
The following provides the contents of above-mentioned configuration file MA5694SCOMM.cfg.
vlan 1000-1002 smart
Issue 01 (2016-04-29)

1344

Access Module

traffic table ip index 10 cir off priority user-cos 7 priority-policy tag-inpackage
service-port vlan 1000 eth 0/1/0 multi-service user-vlan
Configuring the VDSL2 Bonding Group on the DSLAM (VDSL2 Dock Scenario)
Prerequisites
l
The DSLAM (MA5616) is successfully added to the NMS.
The service channel between the OLT and the DSLAM is established and available.
Data Plan
Configurati
on Item
Data
Remarks
VDSL2
bonding
group
Master port: 0/3/0
The MA5616 supports only 4-pair

bonding VDSL2 Dock devices.
Bonding
group profile
DEFVAL (system default

profile which does not limit the
rate in upstream and
downstream directions)
Slave ports: 0/3/1 to 0/3/3
Procedure
Step 1 In the Main Topology, double-click the required NE and choose NE Explorer from the
shortcut menu.
Step 2 Choose DSL > VDSL Port from the navigation tree.
Step 3 On the VDSL2 Bonding Group tab page, right-click in a blank area and choose Add from
the shortcut menu.
Step 4 In the Adding Bonding Group dialog box, select the desired ports, as shown in the following
figure.
Issue 01 (2016-04-29)

1345

Access Module
Figure 13-43 Adding the VDSL2 bonding group
Step 5 In the list of bonding groups, select the newly-added bonding group, right-click, and choose
Activate from the shortcut menu.
----End
Follow-up Procedure
Wait for a moment, and then check whether the ports in the bonding group are activated.
Adding the P2P Pre-Deployment Policy (VDSL2 Dock Scenario)

Data Plan
Configurati
on Item
Data
Remarks
ONU
information
l Upstream transmission
mode: VDSL2 bonding
l Master port in the bonding

group: 0/3/0
l IP address and subnet mask:
10.10.11.2/255.255.254.0
l Management VLAN ID: 8
l Default gateway:
10.10.10.20
SNMP
profile
Issue 01 (2016-04-29)
snmpv1

1346

Access Module
Configurati
on Item
Data
Remarks
Authenticati
on-free
configuratio
n
Enabled; name of the

authentication-free policy:
MA5694S_noauth_vdsl
Procedure
Step 1 In the Main Topology, double-click a desired DSLAM (MA5616) in the Physical Root
navigation tree, or right-click a desired DSLAM and choose NE Explorer from the shortcut
menu.
Step 2 Choose P2P Device Predeployment from the navigation tree.
Step 3 In the P2P Device Predeployment tab, right-click and choose Add... from the shortcut menu.
Step 4 In the dialog box that is displayed, set the parameters, as shown in Figure 13-44.
Figure 13-44 Adding the P2P device pre-deployment policy
MA5694S_noaut
Step 5 Click OK.

----End
Result
After the P2P pre-deployment is completed, connect a VDSL2 Dock device to the port of the
VDSL2 bonding group on the DSLAM, and then wait for several minutes until the VDSL2
Dock device is automatically found and obtains IP address. In this moment, the deployment
status in the P2P Device Predeployment tab becomes green (as shown in the following
figure), and the NMS topology shows that the VDSL2 Dock device functions normally after
the VDSL2 Dock device is synchronized to the NMS.
Issue 01 (2016-04-29)

1347

Access Module

Ethernet clocks.
Prerequisites
l
synchronization.
Context
The clock synchronization scheme of a small-cell base station can be synchronous Ethernet
(frequency synchronization) or IEEE 1588v2 (time synchronization). This topic uses the
synchronous Ethernet as an example to describe how to configure clock synchronization. For
IEEE 1588v2 time synchronization configurations, see 13.3.6 Configuring 1588v2 Clock
Synchronization.
Data Plan
Issue 01 (2016-04-29)
Configuration
Item
Data
GIU upstream board
Port: 0/19/0
DSLAM (MA5616)
port


1348

Access Module
Configuration
Item
Data
ONU Port
Procedure
l

a.

b.

status of the system clock source. Ensure that the configurations of the system clock
source are correct and the status of the system clock source is Normal.
----------------------------------------------------------------------------Index Board
Source
Clk-type State
Priority QL
Selected
----------------------------------------------------------------------------0
H801GICK 0/19/0
ETH
Normal
0
--YES
-----------------------------------------------------------------------------
(ONU functioning as the VDSL2 Dock device) Configure the DSLAM-side clock.
When the ONU functions as the VDSL2 Dock device, the MA5694S (ONU) is
connected upstream to the DSLAM (MA5616) through VDSL2 bonding. In this way,
you need to configure clock synchronization on the OLT, DSLAM, and ONU.
huawei(config)#clock source 0/0/1

When a small-cell base station is connected to an ONU through the Ethernet port, the
port transmit clock is defaulted to the system clock and cannot be modified. Therefore,
you need to configure only the system clock of the ONU.
When the ONU functions as the GPON Dock device, the MA5694S is connected
upstream to the OLT through the GPON port. In this way, you need to configure clock
synchronization on the OLT and ONU.
Issue 01 (2016-04-29)

1349

Access Module
a.
b.

Run the display clock source command to query the configurations and status of
-------------------------------------------------------------------Index Type
Source
State
Priority
QL
Selected
-------------------------------------------------------------------0
line
0/0/0
Normal
0
--YES
1
--/ -/ ----NO
--2
--/ -/ ----NO
--3
--/ -/ ----NO
--4
--/ -/ ----NO
--5
--/ -/ ----NO
--6
--/ -/ ----NO
--7
--/ -/ ----NO
--8
--/ -/ ----NO
--9
--/ -/ ----NO
----------------------------------------------------------------------
----End
Verifying Services
Prerequisites
Procedure
1.
2.
3.


----End
Issue 01 (2016-04-29)

1350

Access Module
14
14 D-CCAP Service Configuration (Centralized

Management)
D-CCAP Service Configuration

(Centralized Management)
About This Chapter

The OptiCable solution implements cable TV (CATV) and broadband signal transmission
over a coaxial network. It applies in CATV network reconstruction in upstream and
downstream directions or new residential areas requiring the CATV and broadband services
over a coaxial network. The radio frequency (RF) access mode applies in the PON
+distributed converged cable access platform (D-CCAP) scenario. This mode complies with
the data over cable service interface specification (DOCSIS) and supports multiple broadcast
and TV services, such as high-speed Internet (HSI) and IPTV services. The OptiCable
centralized management solution, in which an MA5633 works as a remote extended frame of
an optical line terminal (OLT), supports more coax medium converters (CMCs) without
increasing the number of management IP addresses, thereby simplifying CMC management
and reducing maintenance costs.
14.1 D-CCAP Service Overview
This section describes the services supported by a distributed converged cable access platform
(D-CCAP) for multiservice operators (MSOs) from the aspect of basic concepts, networking
scenarios, and hardware configurations. This information provides a basis for configuring the
services on the D-CCAP.
14.2 D-CCAP Data Plan Rules
This section describes the principles of planning frequency spectrum management, device
management, quality of service (QoS), and VLANs for distributed converged cable access
platform (D-CCAP) services.
14.3 Home Service Networking
14.4 L2VPN Enterprise Service Networking
In L2VPN enterprise service networking, a distributed converged cable access platform (DCCAP) connects to cable modems (CMs) through radio frequency (RF) ports, and the CMs
connect to switches or routers to provide the L2VPN service for users. This section describes
how to configure the optical line terminal (OLT) to provision the L2VPN service.
14.5 Multiple services in multiple VLANs Service Networking (GPON)
In home service (VLAN tag transparent transmission) networking, a distributed converged
cable access platform (D-CCAP) connects to cable modems (CMs) at user homes through
Issue 01 (2016-04-29)

1351

Access Module

Management)
radio frequency (RF) ports and provides home services for users, including the cable TV
(CATV) service, Internet access service, and VoD service. This section describes how to
configure the optical line terminal (OLT) to provision the home services.
Issue 01 (2016-04-29)

1352

Access Module

Management)

14.1.1 Basic Concepts

This section describes basic concepts related to a distributed converged cable access platform
(D-CCAP) from the user side to the network side on D-CCAP networks when the MA5633
works as a GPON remote extended frame.
Figure 14-1 D-CCAP networking when the MA5633 works as an extended frame
Issue 01 (2016-04-29)

1353

Access Module

Management)
User Home Side

Concept
Description
Cable modem
(CM)
A device that connects customer premises equipment (CPE) to a

hybrid fiber coaxial (HFC) network. It transmits data over a cable
network through data over cable service interface specification
(DOCSIS).
Media terminal
adapter (MTA)
A network client that provides user terminal (such as a phone set)oriented ports and call control unit-oriented network signaling
interfaces. It connects to cable network units through an HFC
network.
MTAs are classified into embedded MTAs (EMTAs) and single MTAs
(SMTAs) according to PacketCable.
l An EMTA integrates CM and MTA functions.
l An SMTA supports only MTA functionalities.
VoD

locating.
Distributor
A component that distributes signals in a cable TV (CATV)

transmission system. It equally outputs several channels of signals
from one channel of input signals. The common distribution ratios are
1:2, 1:3, 1:4, and 1:6.
Concept
Description
D-CCAP
A device that connects an aggregation network to an HFC network. It

forwards network data, processes protocols, and modulates or
demodulates radio frequency (RF) signals. The D-CCAP provides the
quality of service (QoS) required by CMs and allocates upstream
bandwidths and service resources to the CMs based on CMs' request
and network QoS policy.
Built-in optical
receiver
l An optical receiver, which performs optical-to-electrical (O/E)

conversion for CATV and upstream backhaul signals.
Optical Node
l The fiber node does not require an additional optical receiver. The
O/E conversion is performed by the optical receiver built in the
MA5633 and the MA5633 can receive CATV optical signals.
Issue 01 (2016-04-29)

1354

Access Module

Management)
Concept
Description
Built-in WDM
l A device that multiplexes the optical signals with different

standard wavelengths into one channel of multiplexed signals and
transmits the signals over one optical fiber.
l The WDM in the branch equipment room combines data signals
and CATV signals for signal transmission over one feeder fiber.
On the optical node, the WDM built in the MA5633 separates the
two types of signals from each other.
Built-in EQAM
l The edge quadrature amplitude modulation (EQAM) feature

enables the MA5633 to function as the gateway of a hybrid fiber
coaxial (HFC) network connected to an IP network. The MA5633
multiplexes and modulates IP signals into radio frequency (RF)
signals so that the data carried in the IP signals can be transmitted
over the HFC network.
l The EQAM built in the MA5633 is moved downwards from the
branch equipment room to the fiber node. Therefore, the fiber node
does not require an additional EQAM.
l Video streams are transmitted over a MAN network through the
OLT to the MA5633. The MA5633 uses the built-in EQAM to
module the video signals into RF signals and sends the RF signals
to the STB.
Splitter
A component that connects to the center of a branch or feeder fiber. It

consists of a main input end, a main output end, and multiple branch
output ends. Each branch output end receives only few input signals
on the main path. The majority signals are transmitted forward over
the main path.
Branch Equipment Room

Concept
Description
PON

Issue 01 (2016-04-29)
Optical
distribution
network (ODN)
A network that is composed of passive optical components, such as

optical fibers and one or more passive optical splitters. The ODN
provides highly reliable optical channels between the OLT and ONUs.
Optical line
terminal (OLT)
An aggregation device located at the central office (CO), which

terminates PON protocols.

1355

Access Module

Management)
Concept
Description
Optical splitter
A passive component, which allocates optical power to multiple

ONUs connected to one feeder fiber. In a GPON network that consists
of an OLT, ONUs, optical splitters, and optical fibers, the optical fiber
connected to the OLT uses an optical splitter to connect to multiple
ONUs. The number of ONUs that can be connected to the optical
fiber is determined based on the split ratio.
RX
An optical receiver, which performs optical-to-electrical (O/E)

TX
An optical transmitter, which performs O/E conversion for received

CATV signals.
Combiner
A component that combines multiple channels of analog signals into

one channel of signals on an RF port and then sends the signals to the
downstream optical TX.
GPON remote
extended frame
An OLT, deployed in a branch equipment room and working as a main

frame, connects to an MA5633 through a GPON cascading board. In
this manner, the MA5633 is no longer a standalone NE (no longer
allocated with an independent management IP address), but is
managed by the OLT. The MA5633 is regarded as a remote service
board of the OLT and has the same functions and features as those of
the OLT.
Concept
Description
Softswitch or IP
multimedia
subsystem (IMS)
Softswitch: core of the NGN network call and control, which supports
call and connection control for the services having high real-time
requirements. For the softswitch, services are separated from call
control and call control is separated from bearing. In addition, the
softswitch uses open service interface (API) and standard protocols,
which facilitates the development for new services and features.
MAN Network
IMS: uses Session Initiation Protocol (SIP) signaling as the call

control signaling. It provides voice, data, and multimedia services.
Broadband TV
(BTV) source
IPTV head end, a contents preparation platform in the IPTV system. It

receives signals, converts media formats, and manages media
materials.
14.1.2 Networking Scenarios and Hardware Configurations

(GPON)
This section describes networking scenarios of a distributed converged cable access platform
(D-CCAP) when the D-CCAP works as a GPON remote extended frame and D-CCAP's
hardware configurations.
Issue 01 (2016-04-29)

1356

Access Module

Management)
Typical Networking Scenarios for GPON Remote Extended Frames Working in

Centralized Management Mode and Supported Products
Issue 01 (2016-04-29)
Networki
ng
Scenario
Description
MA5600T
Series
MA5800
Series
MA5633
Home
service
networkin
g
In home service
networking, a
distributed converged
cable access platform
(D-CCAP) connects to
cable modems (CMs)
at user homes through
radio frequency (RF)
ports and provides
home services for
users, including the
cable TV (CATV)
service, Internet access
service, VoD service,
broadband TV (BTV)
service, and
PacketCable service.
Supported
Supported
Supported
Dot1QBase
L2VPN
BSoD
service
networkin
g
In L2VPN enterprise
service networking, a
cable modems (CMs)
through radio
frequency (RF) ports,
and the CMs connect
to switches or routers
to provide the L2VPN
service for users.
Supported
Supported
Supported

1357

Access Module

Management)
Networki
ng
Scenario
Description
MA5600T
Series
MA5800
Series
MA5633
Dot1adbased
L2VPN
service
networkin
g
Two VLAN tags are

added to packets to
differentiate services
from different users,
meeting service
requirements of
L2VPN enterprises.
Supported
Supported
Supported
NOTE
The Dot1ad-based
L2VPN service is
configured in the CM
configuration file.
Therefore, the
configuration of this
service model is not
described in this
document.
Issue 01 (2016-04-29)
MPLSbased
L2VPN
service
networkin
g
Configure the MPLSbased L2VPN service

to comply with BSoD
service requirements.
Not supported
Supported
Supported (by
working with
the MA5800)
Wireless
local area
network
(WLAN)
hotspot
radio
backhaul
service
networkin
g
In wireless local area

network (WLAN)
hotspot radio backhaul
cable modems (CMs)
through radio
frequency (RF) ports.
A CM connects to
wireless access points
(APs) to provide
wireless fidelity (WiFi) access for users.
Supported
Supported
Supported
L3VPN
BSoD
service
networkin
g
The L3VPN service

allows the users only
in the same VPN to
communicate with
each other.
Not supported
Supported
Supported (by
working with
the MA5800)

1358

Access Module

Management)
Table 14-1 Hardware Configurations

Typical Configurations
of the MA5600T Series
of the MA5800 Series
(Control Board+Service
Board+Upstream
Transmission Board)
Board+Upstream
Transmission Board)
l MA5603T or
MA5600T: SCUV
+GPMD+SPUF
MA5800-X17 or MA5800X7
NOTE
For large-capacity CMCs,
run the router mode
enhanced command to
configure the enhanced
Layer 3 forwarding mode
to comply with service
requirements.
MDU Model
MA5633
l MPLB+GPHF
l MPLB+GPHF+NXED
(not recommended)
l MA5608T: MCUE
+GPMD
14.1.3 Networking Scenarios and Hardware Configurations (GE)

(D-CCAP) when the D-CCAP works as a GE remote extended frame and D-CCAP's
hardware configurations.
Issue 01 (2016-04-29)

1359

Access Module

Management)
Typical Networking Scenarios for GE Remote Extended Frames Working in

Centralized Management Mode and Supported Products
Issue 01 (2016-04-29)
Networki
ng
Scenario
Description
MA5600T
Series
MA5800
Series
MA5633
Home
service
networkin
g
In home service
networking, a
cable modems (CMs)
at user homes through
radio frequency (RF)
ports and provides
home services for
users, including the
cable TV (CATV)
service, Internet access
service, VoD service,
broadband TV (BTV)
service, and
Supported
Supported
Supported
Dot1Qbased
L2VPN
BSoD
service
networkin
g
In L2VPN enterprise
cable modems (CMs)
through radio
frequency (RF) ports,
and the CMs connect
to switches or routers
service for users.
Supported
Supported
Supported

1360

Access Module

Management)
Networki
ng
Scenario
Description
MA5600T
Series
MA5800
Series
MA5633
Dot1adbased
L2VPN
service
networkin
g
Two VLAN tags are

added to packets to
differentiate services
from different users,
meeting service
requirements of
L2VPN enterprises.
Supported
Supported
Supported
NOTE
The Dot1ad-based
L2VPN service is
configured in the CM
configuration file.
Therefore, the
configuration of this
service model is not
described in this
document.
Issue 01 (2016-04-29)
MPLSbased
L2VPN
service
networkin
g
Configure the MPLSbased L2VPN service

to comply with BSoD
service requirements.
Not supported
Supported
Supported (by
working with
the MA5800)
WLAN
hotspot
radio
backhaul
service
networkin
g

network (WLAN)
hotspot radio backhaul
cable modems (CMs)
through radio
frequency (RF) ports.
A CM connects to
wireless access points
(APs) to provide
wireless fidelity (WiFi) access for users.
Supported
Supported
Supported
L3VPN
BSoD
service
networkin
g
The L3VPN service

allows the users only
in the same VPN to
communicate with
each other.
Not supported
Supported
Supported (by
working with
the MA5800)

1361

Access Module

Management)
Table 14-2 Hardware configurations

of the MA5600T Series
of the MA5800 Series
Board+Upstream
Transmission Board)
Board+Upstream
Transmission Board)
l MA5603T or
MA5600T: SCUV
+OPGE+SPUF
MA5800-X17 or MA5800X7
NOTE
For large-capacity CMCs,
run the router mode
enhanced command to
configure the enhanced
Layer 3 forwarding mode
to comply with service
requirements.
MDU Model
MA5633
l MPLB+OGHK
l MPLB+OGHK+NXED
(not recommended)
l MA5608T: MCUE
+OPGE
14.2 D-CCAP Data Plan Rules

This section describes the principles of planning frequency spectrum management, device
management, quality of service (QoS), and VLANs for distributed converged cable access
platform (D-CCAP) services.
14.2.1 Frequency Spectrum Management

Total Frequency Bandwidth
The total frequency bandwidth supported by a distributed converged cable access platform
(D-CCAP) ranges from 5 MHz to 1 GHz.
Upstream Frequency Bandwidth

The upstream frequency bandwidth supported by a D-CCAP can be of the European or North
American standard.
l
European standard: 5 MHz to 65 MHz
North American standard: 5 MHz to 42 MHz
Downstream Frequency Bandwidth

The downstream frequency bandwidth supported by a D-CCAP can be of the European or
North American standard.
l
European standard: 87 MHz to 1002 MHz
North American standard: 54 MHz to 1002 MHz
Issue 01 (2016-04-29)

1362

Access Module

Management)
Recommended Frequency Spectrum Configuration

Figure 14-2 lists the recommended frequency spectrum configuration, using the European
standard as an example.
Figure 14-2 Recommended frequency spectrum configuration
Table 14-3 Description of recommended frequency spectrum configuration

Item
Planning Suggestion
Planning Principle
Upstream
frequency
bandwidth
The upstream frequency

bandwidth ranging from 5 MHz
to 15 MHz is used to transmit
low-traffic data without strict
requirements on signal-to-noise
ratio (SNR), such as network
status monitoring, VoD, user
passwords, and program
indexes.
l Plan the upstream frequency

bandwidth for the cable TV (CATV)
service to support the services that
have been provisioned and those to
be provisioned.
l Plan continuous upstream frequency
bandwidths for the analog TV
service, digital TV service, and data
over cable service interface
specification (DOCSIS) data service
to prevent interference between the
services. In addition, the planning
should facilitate the system in
handling the issues of a service
without affecting other services.
The upstream frequency

bandwidth ranging from 16
MHz to 65 MHz is used to
transmit upstream data.
Downstream
frequency
bandwidth
Issue 01 (2016-04-29)
The downstream frequency

MHz to 108 MHz is used to
carry the frequency modulation
(FM) broadcast service. The
FM frequency is 400 kHz. The
downstream frequency
bandwidth supports 52
frequency points.

1363

Access Module
Item

Management)
Planning Suggestion
Planning Principle
The downstream frequency

MHz to 1 GHz is used to carry
the analog TV service, digital
service, and DOCSIS data
service. In the range from 111
MHz to 1 GHz:
l 111 MHz to 550 MHz:
analog TV service
l 550 MHz to 750 MHz:
digital TV service
l 750 MHz to 1 GHz:
DOCSIS data service
14.2.2 Device Management

Table 14-4 Data Plan for Device Management
Item
Device or Service
Planning Principle
Management
channel
Optical line terminal

(OLT)
The management VLANs of all OLTs on an

entire network carry only service VLAN tags.
IP address
Device management
The management IP address of an OLT uses a

private IP address to ensure the OLT security.
Cable modem (CM)
A CM obtains a private IP address through

Dynamic Host Configuration Protocol (DHCP).
The high-speed Internet (HSI) service uses

public IP addresses, which are planned by
carriers.
PacketCable service
A media terminal adapter (MTA) obtains a

private IP address through DHCP.
VoD and multicast

services
A set top box (STB) obtains a private IP address

through DHCP for program ordering.
14.2.3 QoS
Quality of service (QoS) planning varies according to service types. For details, see Table
14-5.
Issue 01 (2016-04-29)

1364

Access Module

Management)
Service Priority Planning and Queue Scheduling Policy

Table 14-5 Service priority planning and queue scheduling policy
Service Type
802.1p
Queue
Network protocol and signaling
CS6 (PQ)
VoIP
EF (PQ)
IPTV, OAM for EMS or NMS, and

golden enterprises
AF4 (WFQ)
Silver enterprise
AF3 (WFQ)
Bronze enterprise
AF2 (WFQ)
High-speed Internet (HSI) service
BE (WFQ)
NOTE
The priorities listed in the preceding table are recommended. Change the priorities based on site and carriers'
requirements.
QoS Model
Figure 14-3 shows the end to end (E2E) QoS processing for the data over cable service
interface specification (DOCSIS) service. This section uses a distributed converged cable
access platform (D-CCAP) that works as a GPON remote extended frame of an optical line
terminal (OLT) as an example.
The only difference between the QoS processing for a D-CCAP that works as a GE extended
frame and that for a D-CCAP that works as a GPON extended frame is as follows: The QoS
processing is not required for the GPON module of the D-CCAP that works as a GE extended
frame.
Figure 14-3 QoS module for a D-CCAP that works as a GPON extended frame
Issue 01 (2016-04-29)

1365

Access Module

Management)
Table 14-6 QoS planning principles

Service
Cable
modem
(CM)
control
service,
HSI
service, or
VoIP
service
Packet
Directi
on
Upstrea
m
QoS Planning
CM
MA5633
OLT
1. A CM
classifies
flows for
service
packets.
l Coaxial media
converter (CMC)
module
QoS parameters
are defined in a
CM configuration
file. Using the QoS
parameter settings,
an MA5633 limits
service rates or
schedules queues
by priorities. In
addition, an OLT
supports the
configuration of a
QoS profile, which
defines QoS
parameters for
various CM
services. If a QoS
parameter is
defined both in a
CM configuration
file and a QoS
profile, the
configuration in
the CM
configuration file
preferentially takes
effect.
An OLT maps the

priority of a DOCSIS
service flow to the
802.1p field in the
Ethernet header and
uses the 802.1p
priority to schedule
queues.
2. A CM
schedules
queues
according to
the priorities
of DOCSIS
service
flows.
1. An MA5633
limits CM
service rates
based on
service priority.
2. An MA5633
schedules
queues for
service flows.
l GPON module
1. All service
flows are
mapped from
GPON
encapsulation
Issue 01 (2016-04-29)

1366

Access Module
Service
Packet
Directi
on

Management)
QoS Planning
CM
MA5633
OLT
mode (GEM)
port 0 to
transmission
container (TCONT) 1.
2. T-CONT 1 is
bound to the
default dynamic
bandwidth
allocation
(DBA) profile.
T-CONT 1 is of
type 4 and
supports a
maximum
bandwidth of
1000 Mbit/s.
Downstr
eam
L2VPN
enterprise
or
wireless
local area
network
(WLAN)
hotspot
radio
backhaul
service
A CM does not
control traffic.
An MA5633 controls
traffic based on traffic
settings of DOCSIS
service flows and
performs committed
access rate (CAR)
based on the CM
traffic control
parameters defined in
a CM configuration
file.
An OLT uses the

802.1p priority to
schedule queues.
The QoS processing for L2VPN enterprise and WLAN hotspot radio backhaul
services is the same as that for home services.
14.2.4 VLAN
Issue 01 (2016-04-29)

1367

Access Module

Management)
Table 14-7 VLAN planning principles

Service
Internet
access
service
VLAN Tag Translation

CM
OLT (Main Frame)
Layer 3 MAN Device
The packets of the

Internet access
service do not
carry a VLAN
tag.
CM management packets
and high-speed Internet
(HSI) packets carry the
same VLAN tag.
l When an OLT
forwards services at
Layer 2, a Layer 3
MAN device forwards
the services at Layer 3
and adds a unique
VLAN tag to the
packets of a service
type.
A service flow is
created between a
cable modem
(CM) and an
MA5633.
l When an OLT
Layer 2, the OLT
VLAN tags to a MAN
device.
l When an OLT
Layer 3, the OLT adds
a unique VLAN tag to
the packets of a service
type.
VoD service
The packets of the

VoD service do
not carry a VLAN
tag.
and electronic program
guide (EPG) packets carry
the same VLAN tag.
A service flow is
created between a
CM and an
MA5633.
l When an OLT
Layer 2, the OLT
VLAN tags to a MAN
device.
l When an OLT
type.
Issue 01 (2016-04-29)

l When an OLT
Layer 3, a Layer 3
MAN device forwards
the services at Layer 3.
l When an OLT
Layer 2, a Layer 3
MAN device forwards
and adds a unique
VLAN tag to the
type.
l When an OLT
Layer 3, a Layer 3
MAN device forwards
1368

Access Module
Service
VoIP
service

CM
OLT (Main Frame)
Layer 3 MAN Device
The packets of the

VoIP service do
not carry a VLAN
tag.
and VoIP packets carry
the same VLAN tag.
l When an OLT
Layer 2, a Layer 3
MAN device forwards
and adds a unique
VLAN tag to the
type.
A service flow is
created between a
CM and an
MA5633.
L2VPN
enterprise
service

Management)
The packets of the

L2VPN enterprise
service do not
carry a VLAN
tag.
Two service flows
are created
between a CM
and an MA5633.
One is the default
service flow and
the other is the
VPN service flow.
l When an OLT
Layer 2, the OLT
VLAN tags to a MAN
device.
l When an OLT
type.
l When an OLT
Layer 3, a Layer 3
MAN device forwards
and enterprise packets
carry different VLAN
tags.
l When an OLT
Layer 2, a Layer 3
MAN device forwards
and adds a unique
VLAN tag to the
type.
The VLAN preconfigured for the packets

of the L2VPN enterprise
service must be the same
as that configured in the
CM configuration file.
l When an OLT
Layer 2, the OLT
VLAN tags to a MAN
device.
l When an OLT
Layer 3, a Layer 3
MAN device forwards
l When an OLT
type.
Issue 01 (2016-04-29)

1369

Access Module
Service
Wireless
local area
network
(WLAN)
hotspot
radio
backhaul
service

Management)

CM
OLT (Main Frame)
Layer 3 MAN Device
The packets of the

WLAN hotspot
radio backhaul
service do not
carry a VLAN
tag.
and Wi-Fi packets carry
different VLAN tags.
l When an OLT
Layer 2, a Layer 3
MAN device forwards
and adds a unique
VLAN tag to the
type.
Two service flows

are created
between a CM
and an MA5633.
One is the default
service flow and
the other is the
Wi-Fi service
flow.
The VLAN preconfigured for the Wi-Fi

packets must be the same
as that configured in the
CM configuration file.
l When an OLT
Layer 2, the OLT
VLAN tags to a MAN
device.
l When an OLT
Layer 3, a Layer 3
MAN device forwards
l When an OLT
type.
The VLAN planning principles are summarized as follows:

l
HSI, VoIP, and CM management services for home users carry the different S-VLAN
tags. Service types can be identified based on VLANs.
An OLT identifies the L2VPN enterprise and WLAN hotspot radio backhaul services by
S-VLAN tag.
NOTE
When planning a VLAN, ensure that the VLAN for the L2VPN service is different from S-VLANs.
14.2.5 Multiple Services in Multiple VLANs

Overview
With the development of hybrid fiber coaxial networks, CMTSs are evolving from traditional
CMTSs to coaxial media converters (CMCs) and the deployment location has been moved
downwards from distribution hubs to fiber nodes. In this case, the application of the CMTSs
on traditional telecom networks poses the following challenges:
l
The number of access network layers is changed from two to five. Specifically, the
original layers CMTSs and cable modems (CMs) are enlarged to routers, convergence
LAN switches, CMCs, CMs, and home gateways (HGWs). The enlarged Layer 2
network promotes higher requirements on the CMCs for processing VLANs.
Some carriers deploy HGWs on the lower-layer of CMs. The HGWs add different
VLAN tags to packets based on service types. This requires that the CMCs support
transparent transmission of VLAN tags.
Issue 01 (2016-04-29)

1370

Access Module

Management)
Values
VLAN classification based on service types brings the following business value points for
carriers:
l
Services are isolated, which narrows down the broadcast scope.
Service types can be identified based on VLANs.
Layer 2 networks can be managed based on VLANs.
Forwarding paths can be selected on Layer 2 networks based on VLANs.
Typical Network Planning

NOTE
The VLAN tags used in the following section are for reference only.
Figure 14-4 VLAN tag transparent transmission (home access)
In the preceding network, IP addresses are allocated and service flows and VLAN tags are
processed as follows:
1.
The PC, set top box (STB), HGW, and CM use dynamic IP addresses allocated by a
Dynamic Host Configuration Protocol (DHCP) server.
2.
All packets sent by the PC and STB are untagged. The HGW adds VLAN tag 200 to
STB packets, adds VLAN tag 300 to HGW management packets (HGW Mg), and
transparently transmits high-speed Internet (HSI) service packets.
3.
The CMC adds VLAN tag 100 to the HSI service packets and CM management packets
(CM Mg).
Issue 01 (2016-04-29)

1371

Access Module

Management)
Figure 14-5 Multiple services in multiple VLANs (home access)
1.
The PC, STB, and CM use dynamic IP addresses allocated by a DHCP server.
2.
All packets sent by the PC and STB are untagged.
3.
(CM Mg), adds VLAN tag 200 to the VoD service packets, and adds VLAN tag 300 to
the VoIP service packets.
Figure 14-6 VLAN QinQ (home access)
1.
The CM and STB use dynamic IP addresses allocated by a DHCP server. The PC uses
PPPoE dialup.
2.
All packets sent by the PC and STB are untagged. The corridor switch adds VLAN tag
10 to the HSI service packets and adds VLAN tag 20 to the VoD service packets.
Issue 01 (2016-04-29)

1372

Access Module
3.

Management)
(CM Mg) and adds VLAN tag 200 to the VoD service packets.
Figure 14-7 VLAN tag transparent transmission (VPN access)
1.
The CM uses the dynamic IP address allocated by a DHCP server.
2.
The enterprise switch statically configures the IP address of the PC and adds VLAN tag
200 to VPN data packets.
3.
The CMC adds VLAN tag 100 to the CM management packets (CM Mg) and
transparently transmits the VLAN tag of the VPN data packets.
NOTE
The preceding VLAN planning applies to the CMC, regardless of whether the CMC is deployed in standalone
NE or centralized management mode.
VLAN translation policies

Table 14-8 VLAN translation policies supported (home access and VPN access)
VLAN Tag
Before
Translation
VLAN Tag
After
Translation
VLAN
Translation Policy
Description
Untagged
Service VLAN
(S-VLAN)
add
An S-VLAN tag is attached.
Service VLAN
+customer VLAN
(S-VLAN+CVLAN)
add double
Two VLAN tags, the outer SVLAN tag and inner CVLAN tag, are attached.
C-VLAN
transparent
The VLAN tag is

transparently transmitted.
S-VLAN
translate
One VLAN tag is translated.
C-VLAN
Issue 01 (2016-04-29)

1373

Access Module
VLAN Tag
Before
Translation

Management)
VLAN Tag
After
Translation
VLAN
Translation Policy
Description
S-VLAN+CVLAN
add
An S-VLAN tag is attached.
S-VLAN+C'VLAN
translate and add
The C-VLAN tag is

translated and the S-VLAN
tag is attached.
NOTE
l S-Tag: S-VLAN Tag, indicates the service VLAN tag.

l C-Tag: C-VLAN Tag, indicates the user VLAN tag.
l C'-Tag: C'-VLAN Tag, indicates another user VLAN tag.
l untagged: No VLAN tag
Restrictions and Limitations

In home access services, although the CMC supports multiple service VLANs (S-VLANs), all
home access services are within the same broadcast domain. Therefore, the home access
services do not support VLAN-based broadcast domains.
14.3 Home Service Networking

14.3.1 Configuring Home Services (Centralized Management,
GPON)
In home service networking, a distributed converged cable access platform (D-CCAP)
connects to cable modems (CMs) at user homes through radio frequency (RF) ports and
provides home services for users, including the cable TV (CATV) service, Internet access
service, VoD service, broadband TV (BTV) service, and PacketCable service. This section
describes how to configure the optical line terminal (OLT) to provision the home services.
NOTE
Configuration procedures are the same for IPv6 and IPv4 networks except in "Configure Dynamic Host
Configuration Protocol (DHCP) relay" and "Configure a route". In addition, IPv6 does not support the
function of configuring PacketCable dynamic voice services.
Table 14-9 Example hardware configurations of the MA5600T series
Issue 01 (2016-04-29)
Control Board
SCUV
Cascading Board
GPMD: 0/3
SPU Board
SPUF: 0/4, 0/5

1374

Access Module

Management)

Users require the provisioning of the TV service, Internet access service, VoD service, and
VoIP service. The TV service can be provisioned immediately after the distributed converged
cable access platform (D-CCAP) hardware is connected. This section only describes how to
configure the Internet access service, VoD service,, and VoIP service.
Usage Scenario
As shown in Figure 14-8, a D-CCAP is deployed on an optical node and cable modems
(CMs) are deployed at user homes. The CMs connect to radio frequency (RF) ports on the
MA5633 through cables.
l
Port 1 on CM 1 connects to a PC for the Internet access service, port 2 connects to a

phone set for the VoIP service, and the distributor connects to the STB for the VoD
service. CM 1 supports embedded media terminal adapter (EMTA) functions and the
voice users of CM 1 use PacketCable 1.x.
CM 2 does not support EMTA functions and needs to connect to a media terminal
adapter (MTA). The voice users of CM 2 use PacketCable Multimedia.
Users access the Internet through Dynamic Host Configuration Protocol (DHCP) dialup.
The IP addresses of the CM, STB, PC, and MTA are assigned by the DHCP server and in
different network segments.
The D-CCAP is used as a GPON remote extended frame. This reduces D-CCAP
management and maintenance costs and simplifies configurations.
Figure 14-8 Home service networking
Figure 14-9 shows the configuration roadmap for the home service networking.
Issue 01 (2016-04-29)

1375

Access Module

Management)
Figure 14-9 Configuration roadmap for the home service networking
The following table describes configuration steps. All configurations are issued from the
optical line terminal (OLT).
No.
Step
Description
l IPv4: Configure Dynamic

Host Configuration Protocol
(DHCP) relay.
This section describes how to configure

Dynamic Host Configuration Protocol
(DHCP) relay so that cable modems (CMs)
can obtain IP addresses in different
network segments.

(DHCP) relay (IPv6).
2
l IPv4: Configure a route

(IPv4).
(IPv6).
Issue 01 (2016-04-29)
This section describes how to implement

network communication by configuring a
route in Layer 3 networking with an optical
line terminal (OLT). Through the route,
packets are forwarded at Layer 3 between
the OLT and its upper-layer devices or
servers.

1376

Access Module

Management)
No.
Step
Description
Add a remote extended frame

to the OLT.
An MA5633 that works as a remote

extended frame connects to a port on a
cascading board of an optical line terminal
(OLT). You can configure the remote
extended frame only after adding it to the
OLT.
Configure RF port parameters

(DOCSIS 3.0).
Radio frequency (RF) port parameters

define the frequency spectrum range for
signal transmission and modulation mode.
The configuration of RF port parameters
implements data service transmission over
cables.
RF port parameters can be configured
using either of the following methods:
l Use a cable initialization profile to
configure the parameters.
l Customize the parameters in cable
mode.
Configure the high-speed

Internet (HSI) service.
None
Configure the EQAM VoD

service.
If the MA5633 is equipped with a built-in

EQAM module, the MA5633 sets idle
downstream DOCSIS channels as EQAM
channels to transmit VoD data.
Configure the dynamic

None
Verify the configured services.
An OLT supports multiple remote service

verification methods. This allows
commissioning and configuration
engineers to remotely verify services.
1. A DHCP dialup emulation test checks
whether the OLT can communicate with
the DHCP server and verifies CM
DHCP configurations on the DHCP
relay, proxy, and server.
2. The status of a CM can be queried.
Based on the information, you can
determine whether the CM is online.
Configuring DHCP Relay

This section describes how to configure Dynamic Host Configuration Protocol (DHCP) relay
so that cable modems (CMs) can obtain IP addresses in different network segments.
Issue 01 (2016-04-29)

1377

Access Module

Management)
Prerequisites
The upper-layer router, DHCP server, and Trivial File Transfer Protocol (TFTP) server of an
optical line terminal (OLT) have been configured.
Data Plan
Table 14-10 DHCP data plan for the OLT
Item
Data
VLAN
ID of the CM management S-VLAN: 100; type of the VLAN:

smart
DHCP server group

parameters
l IP address of the DHCP domain gateway for CMs:

10.10.224.1; domain name: docsis
l IP address of the DHCP domain gateway for media terminal
adapters (MTAs): 10.100.224.1; domain name: pktc
l IP address of the DHCP domain gateway for paid PCs:
10.100.187.1; domain name: default
l IP address of the DHCP domain gateway for overdue PCs:
l IP address of the DHCP domain gateway for set top boxes
(STB): 10.200.160.1; domain name: stb
Table 14-11 Data plan for the upper-layer devices of the OLT
Item
IP Address
Layer 3 interfaces
connecting the router to
the OLT
l Forwarding DHCP and broadband packets: 11.11.11.11
IP addresses of DHCP
servers
l DHCP server assigning IP addresses to CMs and MTAs:

192.168.10.10-192.168.10.11
l Forwarding CM management, VoD, and multicast packets:

11.11.12.11
l DHCP server assigning IP addresses to PCs and STBs:

192.168.10.12-192.168.10.13
IP address of the TFTP
server
192.168.5.10-192.168.5.13
Procedure
Step 1 Set the IP addresses of Layer 3 VLAN interfaces.
huawei(config-if-vlanif100)#ip address 10.10.224.1 255.255.255.0 description
docsis
//Set the IP address of the DHCP domain gateway for CMs.
huawei(config-if-vlanif100)#ip address 10.100.224.1 255.255.255.0 sub description
Issue 01 (2016-04-29)

1378

Access Module

Management)
pktc
//Set the IP address of the DHCP domain gateway for MTAs.
stb
//Set the IP address of the DHCP domain gateway for STBs.
default
//Set the IP address of the DHCP domain gateway for paid PCs.
default
//Set the IP address of the DHCP domain gateway for overdue PCs.
Step 2 Configure the working mode of the DHCP relay to Layer 3 Option 60.
In DHCP Option 60 mode, a DHCP server group is selected according to the Option 60
domain name in DHCP packets. Users in this mode are identified by domain information of
packets, which differentiates various service types in a VLAN. Ensure that the Option 60
domain name and the DHCP server group bound to the Option 60 domain name are
configured beforehand.
huawei(config)#dhcp mode layer-3 Option60
Several minutes may be required and no action can be taken during this period
Are you sure to perform this operation? (y/n)[n]: y
Step 3 Enable the DHCP option82 feature.

The DHCP feature does not have any mechanism for authentication or security. Thus, the
DHCP feature encounters many security problems when it is used in the network. To solve
these problems, the DHCP option82 is introduced.
Step 4 Set the IP addresses of the servers in a DHCP server group.

server group 0 to assign IP addresses to CMs and MTAs.
server group 1 to assign IP addresses to PCs and STBs.
//Configure DHCP
//Configure DHCP
Step 5 Create a DHCP Option 60 domain.

huawei(config)#dhcp domain default
//Create Option 60 domain name default for
PCs.
huawei(config-dhcp-domain-default)#dhcp-gateway learning enable
//Paid and
overdue PCs are in different network segments. Therefore, self-learning needs to
be enabled on OLT gateways.
huawei(config-dhcp-domain-default)#dhcp-server 1 vlan 100
//Bind DHCP
server group 1 to the DHCP domain where the PCs locate. After the configuration,
the PCs in the DHCP domain are corresponded to DHCP server group 1.
huawei(config-dhcp-domain-default)#quit
huawei(config)#dhcp domain docsis
//Create Option 60 domain name docsis for CMs.
huawei(config-dhcp-domain-docsis)#dhcp-server 0 vlan 100
//Bind DHCP server
group 0 to the DHCP domain where the CMs locate. After the configuration, the CMs
in the DHCP domain are corresponded to DHCP server group 0.
huawei(config-dhcp-domain-docsis)#quit
huawei(config)#dhcp domain pktc
//Create Option 60 domain name pktc for MTAs.
huawei(config-dhcp-domain-pktc)#dhcp-server 0 vlan 100
//Bind DHCP server
group 0 to the DHCP domain where the MTAs locate. After the configuration, the
CMs in the DHCP domain are corresponded to DHCP server group 0.
huawei(config-dhcp-domain-pktc)#quit
huawei(config)#dhcp domain stb
//Create Option 60 domain name stb for STBs.
huawei(config-dhcp-domain-stb)#dhcp-server 1 vlan 100
//Bind DHCP server
group 1 to the DHCP domain where the STBs locate. After the configuration, the
STBs in the DHCP domain are corresponded to DHCP server group 1.
huawei(config-dhcp-domain-stb)#quit
Step 6 Set IP addresses of the gateways for the DHCP domain.

huawei(config-if-vlanif100)#dhcp domain default gateway 10.100.187.1
10.100.8.1
//Set the IP address of the gateway for the PC domain to
10.100.187.1 for paid PCs and to 10.100.8.1 for overdue PCs.
Issue 01 (2016-04-29)

1379

Access Module

Management)
huawei(config-if-vlanif100)#dhcp domain docsis gateway 10.10.224.1

IP address of the gateway for the CM domain to 10.10.224.1.
huawei(config-if-vlanif100)#dhcp domain pktc gateway 10.100.224.1
address of the gateway for the MTA domain to 10.100.224.1.
huawei(config-if-vlanif100)#dhcp domain stb gateway 10.200.160.1
address of the gateway for the STB domain to 10.200.160.1.
//Set the
//Set the IP
//Set the IP
----End
Configuring a Route
This section describes how to implement network communication by configuring a route in
Layer 3 networking with an optical line terminal (OLT). Through the route, packets are
forwarded at Layer 3 between the OLT and its upper-layer devices or servers.
Prerequisites
The upper-layer router has been configured.
Data Plan
Table 14-12 Data plan for the Layer 3 interfaces on the network side
Item
IP Address
Layer 3 interfaces on
the OLT network side
Forwarding Dynamic Host Configuration Protocol (DHCP) and

broadband packets:
l VLAN ID: 2004
l Port number: 0/4/0
l IP address: 11.11.11.10/24
Forwarding cable modem (CM) management, VoD, and
multicast packets:
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT
Upper-layer servers of
the OLT
l DHCP servers:

11.11.12.11
DHCP server assigning IP addresses to CMs and media

terminal adapters (MTAs): 192.168.10.10-192.168.10.11
DHCP server assigning IP addresses to PCs and set top
boxes (STBs): 192.168.10.12-192.168.10.13
l CM management system, VoD server, and multicast server:
192.168.20.10-192.168.20.12
l Softswitch or IP multimedia subsystem (IMS) server:
192.168.50.10
Issue 01 (2016-04-29)

1380

Access Module

Management)
Procedure
Step 1 Create Layer 3 VLAN interfaces on the network side.
1.
Create VLANs and configure their uplink ports.
VLAN 2004 is of the smart VLAN type and used for forwarding DHCP and
broadband packets. Add uplink port 0/4/0 to VLAN 2004.
VLAN 2005 is of the smart VLAN type and used for forwarding CM management,
VoD, and multicast packets. Add uplink port 0/5/0 to VLAN 2005.

2.
(Optional) Create native VLANs for Ethernet outbound ports.

Packets between the OLT and its upper-layer router are assumed to be forwarded at
Layer 3 and no VLAN information is required. The created native VLANs remove
VLAN tags from the packets transmitted out of Ethernet ports.
huawei(config-if-eth-0/4)#native-vlan 0 vlan 2004
the packets transmitted out of the 0/8/0 port.
3.
//Remove VLAN tags from
Create Layer 3 VLAN interfaces.

a.
Create a Layer 3 interface for VLAN 2004, through which DHCP and broadband
packets are forwarded.
b.
Create a Layer 3 interface for VLAN 2005, through which CM management and
VoD packets are forwarded.
Step 2 Configure static routes to implement the communication between the OLT and its upper-layer
devices.
//Broadband
packets are forwarded through the Layer 3 interface of VLAN 2004.
//CM
management, VoD, and multicast packets are forwarded through the Layer 3
interface of VLAN 2005.
//COPS
//DHCP
//TFTP
server
//
Softswitch or IMS server
NOTE
The interconnected router must set static routes and add the routes to dynamic routes.
----End
Issue 01 (2016-04-29)

1381

Access Module

Management)
Result
The OLT can communicate with its upper-layer devices. To check network connectivity
between two devices, run the ping and tracert commands.
The configured static routes can be queried in an IPv4 routing table by running the display ip
routing-table command.
Configuring DHCP Relay (IPv6)

This section describes how to configure DHCPv6 relay so that terminals can obtain IP
addresses in different network segments.
Prerequisites
The upper-layer router and DHCP server have been configured.
Data Plan
Table 14-13 DHCP data plan
Configuration Item
Data
Terminal-side of CM
l network segment of CM: 2001:0db8:0001::/64

l network segment of PCs with fees paid:
2001:0db8:0003::/64
l network segment of overdue PCs: 2001:0db8:0004::/64
User-side of OLT
l IP address of the gateway for the DHCP domain of CMs:

2001:0db8:0001::1/64; domain name: docsis
l IP address of the gateway for the DHCP domain of PCs with
fees paid: 2001:0db8:0003::3/64; domain name: default
l IP address of the gateway for the DHCP domain of overdue
PCs: 2001:0db8:0004::4/64; domain name: default
Network-side of OLT
Forwarding DHCP and broadband packets:

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
Forwarding CM management packets, multicast packets, and
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router
l IP address of the Layer 3 interface for forwarding DHCP

and broadband packets: 2001:0db8:0007::6/64
l IP address of the Layer 3 interface for forwarding CM
management packets: 2001:0db8:0008::7/64
Issue 01 (2016-04-29)

1382

Access Module

Management)
Configuration Item
Data
Server
l IP addresses of DHCP servers:

DHCP server allocating IP addresses for CMs:
2001:0db8:0006::8/64-2001:0db8:0006::9/64
DHCP server allocating IP addresses for PCs:
2001:0db8:0006::10/64-2001:0db8:0006::11/64
l IP addresses of the CM management system:
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
Step 1 Configure a CM service provisioning mode, which can be IPv6 (preferentially used), APM, or
DPM (used for dual-stack service provisioning). Select a mode based on site requirements.
huawei(config)#interface cable 1/1/0
huawei(config-if-cable-1/1/0)#cable ip-mode dpm
huawei(config-if-cable-1/1/0)#quit

huawei(config)#ipv6
//Enable IPv6 packet forwarding.
huawei(config-if-vlanif100)#ipv6 enable
//Enable IPv6 on ports.
huawei(config-if-vlanif100)#undo ipv6 nd ra halt
//enables a router to send
RA messages.
huawei(config-if-vlanif100)#ipv6 nd autoconfig managed-address-flag
//
Configure the state-based auto-configuration address flag bit. The host obtains
an IPv6 address using the state-based automatic configuration.
huawei(config-if-vlanif100)#ipv6 address 2001:0db8:0001::1/64
//Configure the
IP address of the gateway for the DHCP domain of CMs.
//Configure the
IP address of the gateway for the DHCP domain of PCs with fees paid.
//Configure the
IP address of the gateway for the DHCP domain of overdue PCs.
Step 3 Enable duplicate address detect (DAD) proxy, which prevents repeated link local addresses
(LLAs) on the user side.
After receiving a DAD packet sent from the user side with destination IP address LLA, the
OLT with DAD proxy enabled checks user online information based on the destination IP
address and VLAN. If a user with the same IP address in the VLAN has been online, the OLT
makes a response and prohibits the new user from going online. Otherwise, the OLT does not
make a response.
huawei(config)#ipv6 dad proxy enable
huawei(config-vlan-srvprof-10)#ipv6 dad proxy enable
//DAD proxy takes effect
after it is enabled at system level and VLAN service profile level.
Step 4 Configure the working mode of DHCP relay to Layer 3 Option 16.
Option 16 is an option with code 16 in DHCPv6 packets, which identifies terminal types. In
DHCPv6 Option 16 mode, packets select a DHCPv6 server based on the Option 16 domain.
Therefore, in DHCPv6 Option 16 mode, packets select a DHCPv6 server based on terminal
types.
Issue 01 (2016-04-29)

1383

Access Module

Management)
huawei(config)#dhcpv6 mode layer-3 option16

Step 5 Enable DHCPv6 Option.

No authentication and security mechanisms are available for DHCPv6. Therefore, the
application of DHCPv6 faces multiple security issues on networks. The enabled DHCPv6
Option function resolves these issues.
huawei(config)#dhcpv6 option enable
Step 6 Configure the IP addresses of the servers in a DHCP server group.

huawei(config)#dhcpv6-server 0 ipv6 2001:0db8:0006::8/64
2001:0db8:0006::9/64
//Configure DHCP server group 0 to allocate IP addresses
for CMs.
2001:0db8:0006::11/64
for PCs.
Step 7 Create DHCP Option 16 domains.

//Create Option 16 domain default for PCs.
huawei(config-dhcp-domain-default)#dhcpv6-gateway learning enable
//PCs require
different IP address segments based on fee payment state. Therefore, automatic
gateway learning must be enabled on the OLT.
huawei(config-dhcp-domain-default)#dhcpv6-server 1 vlan 100
/Bind DHCP
server group 1 to the DHCP domain of PCs. After the configuration, the PCs in
this DHCP domain are mapped to DHCP server group 1.
//Create Option 16 domain docsis for CMs.
huawei(config-dhcp-domain-docsis)#dhcpv6-server 0 vlan 100
//Bind DHCP
server group 0 to the DHCP domain of CMs. After the configuration, the CMs in
Step 8 Configure the IP addresses of the gateways for DHCP domains.

huawei(config-if-vlanif100)#dhcp domain default gateway ipv6 2001:0db8:0003::3/64
2001:0db8:0004::4/64
//Configure IP addresses of the gateways for the DHCP
domain of PCs, including the IP address of the gateway for the PCs with fees paid
and the IP address of the gateway for overdue PCs.
huawei(config-if-vlanif100)#dhcp domain docsis gateway ipv6
2001:0db8:0001::1/64
//Configure the IP address of the gateway for the DHCP
domain of CMs.
----End
Configuring a Route (IPv6)

Layer 3 networking with an OLT. Through the route, the OLT can forward packets at Layer 3
between the OLT and its upper-layer devices or servers.
Prerequisites
The upper-layer router of the OLT has been configured.
Issue 01 (2016-04-29)

1384

Access Module

Management)
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
Step 1 Create VLAN Layer 3 interfaces on the network side.
1.
Create VLANs and add an uplink port to them, respectively.
Issue 01 (2016-04-29)
VLAN 2004 used for forwarding DHCP and broadband packets is a smart VLAN.
Add uplink port 0/4/0 to VLAN 2004.
1385

Access Module

Management)
VLAN 2005 used for forwarding CM management packets, multicast packets, and
VoD packets is a smart VLAN. Add uplink port 0/5/0 to VLAN 2005.

2.

Packets between the OLT and its upper-layer router are forwarded at Layer 3 and no
VLAN tag is required. The created native VLANs remove VLAN tags from the packets
transmitted out of Ethernet ports.
transmitted out of port 0/4/0 are untagged.
3.
//The packets
//The packets
Create VLAN Layer 3 interfaces.

a.
Create the Layer 3 interface of VLAN 2004, through which DHCP and broadband
b.
Create the Layer 3 interface of VLAN 2005, through which CM management

packets, multicast packets, and VoD packets are forwarded.
Step 2 Configure static routes for the communication between the OLT and its upper-layer devices.
huawei(config)#ipv6 route-static ::/0 2001:0db8:0007::6/64
//Broadband
huawei(config)#ipv6 route-static 2001:0db8:0011::/64
2001:0db8:0008::7/64
//CM management packets are forwarded through the Layer
3 interface of VLAN 2005.
huawei(config)#ipv6 route-static 2001:0db8:0006::/64 2001:0db8:0007::6/64
//
DHCP packets are forwarded through the Layer 3 interface of VLAN 2004.
NOTE
Configure static routes on the router connected to the OLT. In addition, add the static routes to dynamic ones.
----End
Result
between two devices, run the ping ipv6 and tracert ipv6 commands.
The configured static routes can be queried in an IPv6 routing table by running the display
ipv6 routing-table command.
Adding a Remote Extended Frame to an OLT

An MA5633 that works as a remote extended frame connects to a port on a cascading board
of an optical line terminal (OLT). You can configure the remote extended frame only after
adding it to the OLT.
Issue 01 (2016-04-29)

1386

Access Module

Management)
Prerequisites
The MA5633 management policy is set to extend-frame. To do so, run the sysman
centralized-mgmt primary command.
Context
A GPON remote extended frame is added to an OLT in the following two steps: Add the
MA5633 to the OLT as a GPON optical network unit (ONU). Then add the MA5633 to the
OLT as a GPON remote extended frame.
You can use either of the methods listed in the following table to add a remote extended frame
to an OLT based on site requirements.
Table 14-15 Methods of adding a remote extended frame to an OLT
Method
Usage Scenario
Remarks
Add a remote
extended frame
in offline mode.
A carrier has planned all

remote extended frame IDs
together and the remote
extended frames must be
deployed one by one. This
method facilitates remote
extended frame management.
1. You have obtained the serial

number (SN) of the remote
extended frame.
A great number of remote

extended frames need to be
deployed. This method reduces
manual configurations.
1. You do not know the SN of the

remote extended frame.
Add an
automatically
discovered
remote extended
frame.
2. The remote extended frame ID

has been planned.

does not need to be planned.
Data Plan
Item
Data
GPON cascading
board
Port ID: 0/3/1

Remote extended frame ID: 1
Remote extended frame authentication mode: SN
Remote extended frame SN: 48575443E6D8B541
NOTE
Only one OLT model is used as an example. The configuration method is the
same for other OLT models. The only difference lies in slot IDs.
Dynamic
bandwidth
allocation (DBA)
Issue 01 (2016-04-29)
Profile: default
Type: type4

1387

Access Module
Item
Data
Line profile
Profile: default

Management)
GPON encapsulation mode (GEM) port ID: 0 (fixed port in

centralized management mode)
Transmission container (T-CONT) ID: 1 (fixed T-CONT in centralized
management mode)
MA5633
management
mode
extend-frame
Procedure
l
Add a remote extended frame in offline mode.

huawei(config)#frame add 1 MA5633 extending-port 0/3/1 sn 48575443E6D8B541
NOTE
When running the frame add command to add a remote extended frame in offline mode, the OLT
automatically allocates a temporary SN for the remote extended frame. Therefore, you do not need to
specify the SN of the remote extended frame. After obtaining the SN of the remote extended frame, run
the frame bind command to add the binding relationship between the SN and the remote extended
frame to the OLT. Then the remote extended frame is added.
Add an automatically discovered remote extended frame.

The OLT supports the adding of an automatically discovered GPON remote extended
frame. This function does not require manual confirmation, thereby simplifying the
remote extended frame registration and adding flow.
----End
Result
The remote extended frame is online.
After adding the remote extended frame, run the display frame info command to query the
status of the remote extended frame. Ensure that Online state is online and State is normal.
Follow-up Procedure
If the remote extended frame cannot be discovered, follow the troubleshooting suggestions
listed in the following table to rectify faults.
Issue 01 (2016-04-29)
Possible Cause
Troubleshooting Suggestion
The optical fiber is insecurely

connected to the MA5633.
Securely connect to the optical fiber to the MA5633.

1388

Access Module

Management)
Possible Cause
The RX optical power of the

MA5633 has exceeded the
permitted range.
Add an optical attenuator to the OLT to decrease the RX

optical power of the MA5633 to be within the range from
-27 dBm to -8 dBm.
The MA5633 automatic

discovery function is
disabled.
In GPON mode, run the port ont-auto-find command to

enable the MA5633 automatic discovery function on
GPON ports.
The MA5633 works as a

standalone NE and cannot
work as a remote extended
frame.
Replace the MA5633 with the one that works as a remote

extended frame.
The MA5633 management

policy is set to stand-alone
on the OLT.
Run the sysman centralized-mgmt primary command to

configure the MA5633 management policy to extendframe.
The number of remote

extended frames on the OLT
has reached the threshold.
Run the frame delete command to delete a remote

extended frame that is no longer used from the OLT.
Configuring RF Port Parameters (DOCSIS 3.0)

Radio frequency (RF) port parameters define the frequency spectrum range for signal
transmission and modulation mode. The configuration of RF port parameters implements data
service transmission over cables.
Context
You can use either of the methods listed in the following table to configure RF port
parameters based on site requirements.
Issue 01 (2016-04-29)

1389

Access Module

Management)
Table 14-17 Methods of configuring RF port parameters

Method
Usage Scenario
Remarks
Use a cable
initialization
profile to
configure RF
port parameters.
A carrier needs to deploy

remote extended frames in
batches. This method reduces
data configuration for remote
extended frames, thereby
improving service provisioning
efficiency.
l If the RF port parameters are the

same for all the remote extended
frames to be deployed in batches,
use the cable initialization profile
to configure the parameters.
Configure the RF parameter

profile for the remote extended
frames on the optical line
terminal (OLT). After the
remote extended frames are
powered on and added to the
OLT, the OLT automatically
issues the RF parameter profile
to the remote extended frames,
without requiring any software
configuration.
NOTE
After the cable initialization
profile is configured, a remote
extended frame uses the RF port
parameters configured in the
profile after going online,
regardless of whether the remote
extended frame in added in offline
mode or automatically discovered
by the OLT.
Customize RF
port parameters
in cable mode.
Requires differentiated plans

and configurations for RF port
parameters of remote extended
frames, and the remote
configured one by one.
l If the RF port parameters are

basically the same for all the
remote extended frames to be
deployed in batches, use the cable
initialization profile to configure
the parameters. Then, modify
parameter settings in customized
cable configuration mode.
l If the remote extended frames to
be deployed in batches provide
different hardware capabilities,
and RF port parameters are
significantly different, create
different initialization profiles,
and customize RF parameters in
each initialization profile.
If the RF port parameters are

significantly different for the remote
extended frames to be deployed in
batches, use this method to configure
the parameters.
Data Plan
Table 14-18 Data plan for RF port parameters
Issue 01 (2016-04-29)
Item
Data
RF port
1/1/0
Upstream
channels
l Type: European standard (default channel type)

l Channel central frequency (MHz): 29.8, 42.60, 49.00, and 55.4

1390

Access Module

Management)
Item
Data
Downstream
channels

l Channel central frequency (MHz): 602.00, 610.00, 618.00, ..., and
722.00
Procedure
l
Use a cable initialization profile to configure RF port parameters.

a.
Configure the frequency spectrum range and channel type.

In this example, the channel is of the European type. To change the type to North
American, run the cable command.
b.
Configure RF port parameters for upstream channels and activate the upstream
channels.
Parameter
Description
frequency and channel-width
A central frequency and a frequency

bandwidth determine a frequency range,
within which packets are transmitted. For
example, the central frequency of a
European channel is 55 MHz and the
frequency bandwidth is 6400 kHz. Then
the frequency range of the channel is
51.8-58.2 MHz.
modulation-profile
An upstream channel modulation profile

defines parameters for processing the
signals transmitted over the upstream
channel. Select the corresponding
modulation profile according to actual line
conditions. In this example, ATDMA
profile 23 is selected.
The following configurations are used as an example to configure RF parameters

for upstream channels:
n
Number of upstream channels: 4
Frequency bandwidth of the channels: 3.2 MHz (default value)
huawei(config)#interface cable init-template

huawei(config-cable-init-template)#cable upstream
modulation-profile 23 enable
c.
Issue 01 (2016-04-29)
1 frequency 29.8
2 frequency 42.60
3 frequency 49.00
4 frequency 55.40
Configure RF port parameters for downstream channels and activate the

downstream channels.
1391

Access Module

Management)
Parameter
Description
modulation
A greater modulation mode value for

downstream channels results in a higher
channel bandwidth but weaker antiinterference capability. Therefore,
configure the modulation mode based on
site requirements. The default modulation
mode is QAM256. This example uses the
default setting.
The following configuration is used as an example to configure RF parameters for

downstream channels: A total of 16 downstream channels have been purchased.
huawei(config-cable-init-template)#cable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
Issue 01 (2016-04-29)
downstream 1 frequency 602.00


1392

Access Module

Management)
NOTE
Alternatively, run the cable init-template-rf add command to create a cable initialization profile
for configuring downstream and upstream channel parameters. If the remote extended frames
provide different hardware capabilities, create multiple initialization profiles and customize RF
parameters in each initialization profile. This method is recommended.
1. Create cable initialization profile 3 and configure the number of downstream and upstream
channels. (This remote extended frame is not equipped with a built-in EQAM.)
huawei(config)#cable init-template-rf add profile-id 3 condition
upstream channel-num
4 downstream channel-num 16 eqam no
2. Configure RF parameters for downstream and upstream channels and activate these channels.
huawei(config)#interface cable init-template-rf profile-id 3
huawei(config-cable-init-template-rf-3)#cable upstream 1 frequency
29.8 modulation-profile 23 enable
huawei(config-cable-init-template-rf-3)#cable downstream 1 frequency
602.00 enable
610.00 enable
618.00 enable
626.00 enable
634.00 enable
642.00 enable
650.00 enable
658.00 enable
666.00 enable
674.00 enable
682.00 enable
690.00 enable
698.00 enable
706.00 enable
714.00 enable
722.00 enable
Customize RF port parameters in cable mode.

NOTE
The configuration is complete if you have configured the RF port parameters using a cable initialization
profile. For details, see Use a cable initialization profile to configure RF port parameters. Perform
this operation if you need to customize the RF port parameters of a remote extended frame.
a.
channels.
huawei(config-if-cable-1/1/0)#cable upstream 1 frequency 29.8 modulationprofile 23 enable
huawei(config-if-cable-1/1/0)#cable upstream 2 frequency 42.60
Issue 01 (2016-04-29)

1393

Access Module

Management)
b.

huawei(config-if-cable-1/1/0)#cable
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
1 frequency 602.00 enable

----End
Result
1.
The transmit power of the downstream channels meets site requirements.

Run the display cable downstream frameid/slotid/portid { all | channel-id } status
command to check whether the RF port parameters meet site requirements.
2.
The signal-to-noise (SNR) ratio of the upstream channels meets site requirements.
Run the display cable signal quality [ frameid/slotid/portid [ upstream channel-id ] ]
command to check whether the RF port parameters meet site requirements. A greater
SNR ratio results in better signal quality. The recommended SNR ratio is greater than 30
dB.
Configuring the HSI Service

A cable modem (CM) connects to a distributed converged cable access platform (D-CCAP)
through a cable and provides the high-speed Internet (HSI) service for users.
Data Plan
Table 14-19 Data plan for the HSI service
Item
Data
VLAN
ID of the HSI service VLAN (S-VLAN): 100; type of the

VLAN: smart
Uplink ports
Forwarding Dynamic Host Configuration Protocol (DHCP),

broadband, and VoIP packets: 0/4/0
Forwarding cable modem (CM) management and VoD packets:
0/5/0
Issue 01 (2016-04-29)

1394

Access Module

Management)
Procedure
Step 1 Create an S-VLAN.
The S-VLAN is a user-side service VLAN between the optical line terminal (OLT) and the DCCAP. The OLT works in Layer 3 forwarding mode.
Step 2 Create a CM S-VLAN.

The CM S-VLAN identifies a CM service flow. After the CM S-VLAN is configured, the
OLT automatically creates a CM service flow when the CM goes online.
NOTE
l The cable service-vlan vlanid command is used to configure a global S-VLAN for CM services. After
the configuration, all CM services of the D-CCAPs connected to the same OLT use the same VLAN.
When the number of IP address segments planned for an OLT is less than eight, this command is
recommended.
l The cable service-vlan vlanid frameid/slotid command is used to configure an S-VLAN for CM services
on a specified D-CCAP. After the configuration, the D-CCAP does not use the global S-VLAN. When the
number of IP address segments planned for an OLT is greater than eight, this command is recommended.
huawei(config)#cable service-vlan 100
Info: The new service VLAN will take effect after the CM is restarted, are you
sure to modify? (y/n)[n]:y
----End
Configuring the DOCSIS VoD Service

through a cable and provides the DOCSIS VoD service for users.
Context
All home services use a service VLAN (S-VLAN) and the S-VLAN is globally configured. If
the S-VLAN has been configured for other home services, use the S-VLAN for the VoD
service.
Data Plan
Table 14-20 Data plan for the VoD service
Item
Data
VLAN
ID of the VoD S-VLAN: 100; type of the VLAN: smart
Uplink ports

multicast packets: 0/5/0
Issue 01 (2016-04-29)

1395

Access Module

Management)
Procedure

NOTE
recommended.
----End
Configuring the EQAM VoD Service

If the MA5633 is equipped with a built-in EQAM module, the MA5633 sets idle downstream
DOCSIS channels as EQAM channels to transmit VoD data.
Prerequisites
The MA5633 supports built-in EQAM.
Context
In multiservice operator (MSO)-oriented solutions, both HFC networks and STBs use the
broadcast television QAM technology and support only RF signals.
Video data is encapsulated into IP and UDP packet headers that are transmitted on IP
networks, which cannot be transmitted on HFC networks. To transmit the video data on HFC
networks, the video data must be modulated into RF signals using the EQAM module.
Video data transmission on HFC networks uses existing CATV coaxial cables on the HFC
networks, thereby reducing network deployment costs.
Data Plan
Issue 01 (2016-04-29)
Item
Data
EQAM IP address
10.10.10.10

1396

Access Module

Management)
Item
Data
VLAN
Uplink port
Forwarding CM management, VoD, and multicast packets:

0/5/0
EQAM channel ID
13-16
Modulation mode
QAM 64
Symbol rate
6.875
UDP port number
501-514
Procedure
Step 1 Use a cable initialization profile to configure RF port parameters.
huawei(config-cable-init-template)#cable downstream 13 frequency
qam64 enable channel-mode eqam symbol-rate 6.875
modulation qam64 enable channel-mode eqam symbol-rate 6.875
huawei(config-cable-init-template)#quit
115.0 modulation
123.00
131.00
139.00
Step 2 Configure a video profile.

A video profile contains all video mappings on an EQAM module and supports batch video
mapping configurations. This facilitates video mapping configuration and management.
huawei(config)#cable eqam video profile name vod1
huawei(config-eqam-video-profile-vod1)#mapping index
output-program 1 pmtpid 32 channel 13
Issue 01 (2016-04-29)

1 type spts udp-port 501

1397

Access Module

Management)

huawei(config-eqam-video-profile-vod1)#quit
NOTE
To configure video mappings in batches, do as follows:

output-program 1 pmtpid 32 chan
nel 13 number 4 increment output-program 1 pmtpid 16

udp-port 1
udp-port 1
udp-port 1
udp-port 1
Step 3 Configure the VoD S-VLAN.

VLAN 50 is the S-VLAN that functions between the OLT and the MA5633. The OLT works
in Layer 3 forwarding mode.
Step 4 Configure a video domain.

A video domain defines the relationships between an EQAM module and an EQAM IP
address, and between the S-VLAN used for video data forwarding on an EQAM module, the
EQAM module, and a video profile. This facilitates data management.
huawei(config)#cable eqam video domain huawei
huawei(config-eqam-domain-huawei)#local ip 10.10.10.10 vlan 50
huawei(config-eqam-domain-huawei)#bind video profile name vod1 1/1/0
huawei(config-eqam-domain-huawei)#quit
----End
Result
The MA5633 supports packet statistics query. Based on the statistical results, you can
determine whether users can order programs and whether packet loss occurs in program
transmitting.
l
Run the display cable eqam video stream command to check the TS status. If the status
is online, the TS is functional.
Run the display cable eqam video statistics input command to query packet statistics
and network jitter of a TS on the video service input end.
Check whether the program ordered by a user has been sent to the MA5633. If the
program has been sent to the MA5633, check whether the program traffic is normal.
Run the display cable eqam video statistics output command to query packet statistics
of a TS on the video service output end.
Check whether the TS contains the ordered program, whether the program has been sent
to the STB, and whether the TS traffic is normal.

through a cable and provides the multicast service for users.
Issue 01 (2016-04-29)

1398

Access Module

Management)
Context
the S-VLAN has been configured for other home services, use the S-VLAN for the multicast
service.
Data Plan
Table 14-22 Data plan for the multicast service
Item
Data
VLAN
ID of the multicast S-VLAN: 100; type of the VLAN: smart
Uplink ports

Procedure

NOTE
recommended.
Step 3 Configure multicast VLAN 100.

NOTE
This configuration takes effect only after the CMs go online again.
Step 4 Configure the Internet Group Management Protocol (IGMP) version to IGMPv3.
Step 5 Configure a multicast program generation mode.

Issue 01 (2016-04-29)

1399

Access Module

Management)
Multicast programs can be dynamically or statically generated. For the D-CCAP, the
multicast programs are dynamically generated.
Step 6 Configure the multicast uplink port to 0/5/0.

Step 7 Configure the IGMP mode to IGMP proxy.

Step 8 Bind CM multicast users to the multicast VLAN.

NOTE
huawei(config)#cable multicast-vlan 100
Step 9 (Optional) Disable multicast DSID-based forwarding (MDF).

Multicast DSID-based forwarding is defined in data over cable service interface specification
(DOCSIS) 3.0, perform this step if the CMs comply with DOCSIS 2.0.
Disable MDF if the CMTS is connected to a CM equipped with a TI chip. Otherse, the CM
may go online and offline repeatedly.
huawei(config)#cable multicast mdf disable
Step 10 (Optional) Configure multicast user authentication.

NOTE
Perform this step if the configuration file on the CM server contains only the multicast rights profile name
and the multicast rights must be configured on the D-CCAP.
The following configurations are used as an example to configure multicast user

authentication:
l
Multicast authentication function: enabled globally
Maximum number of programs can be ordered if the CM does not match any rights rule:
32
IP addresses of the multicast programs that can be ordered by multicast users: 225.1.1.1
and 225.1.1.2
IP address of the multicast server: 192.168.20.11
Multicast program priorities: 254 and 255
huawei(config)#cable multicast authorization enable max-sessions 32 default-acti

on permit
huawei(config)#cable multicast auth-profile profile-name btv1
huawei(config-multicast-profile-btv1)#rule 1 priority 255 group-ip 225.1.1.1 gro
up-ip-mask 24 src-ip 192.168.20.11 src-ip-mask 24 permit
Step 11 (Optional) Configure cable multicast version.

huawei(config)#cable multicast igmp-version v3
----End
Issue 01 (2016-04-29)

1400

Access Module

Management)
Configuring the Dynamic PacketCable Service

through a cable and provides the dynamic PacketCable service for users.
Context
Table 14-23 Data plan for the PacketCable service on the OLT
Item
Data
Uplink port
Forwarding VoIP packets: 0/4/0
VLAN
ID of service VLAN: 100

ID of the common open policy service (COPS) connection VLAN:
1000
IP address for
creating a COPS
connection to an
IP multimedia
subsystem (IMS)
or a softswitch
192.168.60.3/24 (in the same network segment as the IMS or

softswitch or can communicate with the IMS or softswitch)
Procedure
Step 1 Create a service VLAN (S-VLAN).
NOTE
All home services use an S-VLAN and the S-VLAN is globally configured. If the S-VLAN has been
configured for other home services, use the S-VLAN in steps Step 1 and Step 2.
The ID of S-VLAN is 100 and the type of the VLAN is smart. The S-VLAN is a user-side
service VLAN between the OLT and the D-CCAP. The OLT works in Layer 3 forwarding
mode.

NOTE
recommended.
Issue 01 (2016-04-29)

1401

Access Module

Management)
Step 3 Configure the Layer 3 interface for COPS connections.

Step 4 Configure a COPS connection.

The following configurations are used as an example to configure a COPS connection:
COPS policy enforcement point (PEP) ID: IP address of the Layer 3 interface for the COPS
connection
huawei(config)#cops pepid 192.168.60.3
Step 5 Configure PacketCable parameters.

PacketCable 1.x parameter settings are as follows:
l
Embedded media terminal adapter (EMTA) creating a dynamic media stream: permitted
Other parameters: default settings
huawei(config)#packetcable 1dotx enable

huawei(config)#packetcable authorize common-docsis-mta enable
huawei(config)#packetcable multimedia enable
----End
Verifying Services
A CMC working as a remote extended frame locates on an optical node. To facilitate service
verification, the optical line terminal (OLT) supports multiple remote service verification
methods, such as Dynamic Host Configuration Protocol (DHCP) dialup emulation tests. This
allows commissioning and configuration engineers to remotely verify services. In addition,
this section describes how to verify the home services on site.
Prerequisites
l
The OLT is properly connected to the upper-layer network.
The DHCP server, Trivial File Transfer Protocol (TFTP) server, and softswitch or IP
multimedia subsystem (IMS) have been configured.
Perform a DHCP dialup emulation test.
Procedure
In this test, a cable modem (CM) is emulated on the OLT to apply to the DHCP server
for an IP address. This checks whether the OLT can communicate with the DHCP server
and verifies CM DHCP configurations on the DHCP relay, proxy, and server.
a.
Run the simulate dhcp start cm mac-address [ option60 option60 ] command to

start a DHCP dialup emulation test.
NOTE
You can run the simulate dhcp stop command to stop the DHCP emulation.
b.
Issue 01 (2016-04-29)
Run the display simulation dhcp command to query the results of the DHCP
1402

Access Module
c.
l

Management)
Check whether the User IP has obtained an IP address.
Check the CM status.

Run the display cable modem command to query the CM status in Status.
huawei(config)#display cable modem
all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
ol: 0, ol-ptd: 0, ol-pt: 1, ol-d: 0, wol: 0, wol-ptd: 0, wol-pt: 0, wol-d:
0,
pol: 0, pol-ptd: 0, pol-pt: 0, pol-d: 0, offline: 0, rej-m: 0, rej-pt: 0, rejo:
0, init: 0, init-rc: 0, DHCP: 0, DHCP-O: 0, DHCP-R: 0, DHCP-C: 0, REG:
0
Note: 1. Idx is the index of a
CM.
2. The downstream received power is in the unit of
dBmV.
3. In status, "ol" means online, "rej" means reject.
The following table lists the CM status and handling suggestions.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init
Indicates that the CM initialization

ranging message is received.the
CM initialization.
If a CM is always in the ranging state,

the ranging fails. Then check radio
frequency (RF) line indicators and
detect line faults.
init-rc

ranging is complete.
No action is required. The ranging of

the CM is complete.
DHCP
Indicates that the DHCP discovery

from the CM is received.
If a CM initiates a DHCP request but

does not obtain an IP address, check
the DHCP server, routing between the
OLT and the DHCP server, and
DHCP server parameter settings.

1403

Access Module
Issue 01 (2016-04-29)

Management)
CM
Status
Description
Handling Suggestion
l DH
CPO
l DHCP-O: indicates that the

offer from the DHCP server is
received.
l DH
CPR
l DHCP-R: indicates that the

DHCP request from the CM is
received.
l DH
CPC
l DHCP-C: indicates that the

acknowledge from the DHCP
server is received.
The DHCP server has assigned an IP

address to the CM and sent
configuration file name and IP
address of the TFTP or ToD server to
the CM using the Option 67 and
Option 66 fields (the Option 67 field
carries the configuration file name
and the Option 66 field carries the IP
address of the TFTP or ToD server).
REG
Indicates that a registration is

started.
If the CM is always in the DHCP-C

state, the CM fails to obtain the
configuration file. Then check the
TFTP server, routing between the
OLT and the TFTP server, and TFTP
server parameter settings.
If the CM is always in the register
state, the CM obtains an incorrect
configuration file. Then change the
configuration file.

1404

Access Module

Management)
CM
Status
Description
Handling Suggestion
l ol
l ol: indicates that the CM is

online. (valid only for CMs
complying with DOCSIS 2.0)
No action is required. The status

indicates that the CM has registered
with the OLT and can correctly
transmit and receive services.
l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold
l ol-pt: indicates that the CM is

online and passes the BPI
authentication. (valid only for
CMs complying with DOCSIS
2.0)
l ol-ptd: indicates that the CM is
authentication, and
NetAccessEnable is disabled.
(valid only for CMs complying
with DOCSIS 2.0)
l ol-d: indicates that the CM is
online and NetAccessEnable is
disabled. (valid only for CMs
l wol: indicates that the CM is
online and all channels bound
to the CM are available. (valid
only for CMs complying with
DOCSIS 3.0)
l wol-pt: indicates that the CM
is online and passes the BPI
authentication, and all channels
bound to the CM are available.
with DOCSIS 3.0)
l wol-ptd: indicates that the CM
authentication,
NetAccessEnable is disabled,
and all channels bound to the
CM are available. (valid only
for CMs complying with
DOCSIS 3.0)
l wol-d: indicates that the CM is
online, NetAccessEnable is
disabled, and all channels
with DOCSIS 3.0)
l pol: indicates that the CM is
online and some channels
Issue 01 (2016-04-29)

1405

Access Module
CM
Status

Management)
Description
Handling Suggestion

with DOCSIS 3.0)
l pol-pt: indicates that the CM is
authentication, and some
channels bound to the CM are
available. (valid only for CMs
l pol-ptd: indicates that the CM
authentication,
and some channels bound to
the CM are available. (valid
DOCSIS 3.0)
l pol-d: indicates that the CM is
disabled, and some channels
with DOCSIS 3.0)
offline
Indicates the offline status.
If the CM is in the offline state, check

the power status, noise, and channel
frequency of the CM.
l rejm
l rej-m: indicates that the MIC

verification fails.
l rejpt
l rej-pt: indicates that the BPI

authentication fails.
l rej-o
l rej-o: indicates that the

authentication reject due to
other reasons.
If the CM is in the reject state, no

service flow can be created. Then
check the CM authentication and CM
message integrity check (MIC), and
check whether class of service (COS)
parameters specified in the CM
configuration file are supported by the
OLT.
Verify that home services can be provisioned.

a.
After the CM is installed at a user home and commissioned, the user can watch TV
programs.
b.
After the high-speed Internet (HSI) service is provisioned, the user can access the
Internet from a PC.
c.
After the VoD service is provisioned, the user can order programs.
d.
After the VoIP service is provisioned, the user can make and receive phone calls.
----End
Issue 01 (2016-04-29)

1406

Access Module

Management)
14.3.2 Configuring Home Services (Centralized Management, GE)

In home service networking, a distributed converged cable access platform (D-CCAP)
connects to cable modems (CMs) at user homes through radio frequency (RF) ports and
provides home services for users, including the cable TV (CATV) service, Internet access
service, VoD service, broadband TV (BTV) service, and PacketCable service. This section
describes how to configure the optical line terminal (OLT) to provision the home services.
NOTE

Control Board
SCUV
Cascading Board
GPMD: 0/3
SPU Board
SPUF: 0/4, 0/5

Usage Scenario
As shown in Figure 14-10, a distributed converged cable access platform (D-CCAP) is
deployed on an optical node and cable modems (CMs) are deployed at user homes. The CMs
connect to radio frequency (RF) ports on the MA5633 through cables.
l

The MA5633 works as a GE remote extended frame to reduce MA5633 management

and maintenance costs and simplify configurations.
Issue 01 (2016-04-29)

1407

Access Module

Management)
Issue 01 (2016-04-29)

1408

Access Module

Management)
The following table describes the configuration steps. All configurations are issued from the
No.
Step
Description

(DHCP) relay.

network segments.

2
l IPv4: Configure a route.

(IPv6).
Issue 01 (2016-04-29)

servers.

1409

Access Module

Management)
No.
Step
Description

to the OLT.
A distributed converged cable access

platform (D-CCAP) that works as a GE
remote extended frame connects to a port
on a GE cascading board of an optical line
terminal (OLT). You can configure the
remote extended frame only after adding it
to the OLT.
Configure RF port parameters

(DOCSIS 3.0).

cables.
mode.

None
None
Configure the broadband TV

(BTV) service.
None

None


Issue 01 (2016-04-29)

1410

Access Module

Management)
Prerequisites
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

Item
IP Address
Layer 3 interfaces
the OLT
servers

192.168.10.10-192.168.10.11

11.11.12.11

192.168.10.12-192.168.10.13
server
192.168.5.10-192.168.5.13
Procedure
docsis
Issue 01 (2016-04-29)

1411

Access Module

Management)
pktc
stb
default
default


//Configure DHCP
//Configure DHCP

PCs.
//Paid and
//Bind DHCP
//Bind DHCP server
//Bind DHCP server
//Bind DHCP server

10.100.8.1
Issue 01 (2016-04-29)

1412

Access Module

Management)

//Set the
//Set the IP
//Set the IP
----End
Configuring a Route
Prerequisites
Data Plan
Item
IP Address

broadband packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
multicast packets:
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT
the OLT
l DHCP servers:

11.11.12.11

boxes (STBs): 192.168.10.12-192.168.10.13
192.168.20.10-192.168.20.12
192.168.50.10
Issue 01 (2016-04-29)

1413

Access Module

Management)
Procedure
1.

2.

3.

a.
b.
devices.
//Broadband
//CM
//COPS
//DHCP
//TFTP
server
//
Softswitch or IMS server
NOTE
----End
Issue 01 (2016-04-29)

1414

Access Module

Management)
Result

Prerequisites
The upper-layer router and DHCP server have been configured.
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Issue 01 (2016-04-29)

1415

Access Module

Management)
Configuration Item
Data
Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure

huawei(config)#ipv6
RA messages.
//
//Configure the
//Configure the
//Configure the
make a response.
types.
Issue 01 (2016-04-29)

1416

Access Module

Management)

Step 5 Enable DHCPv6 Option.

No authentication and security mechanisms are available for DHCPv6. Therefore, the
application of DHCPv6 faces multiple security issues on networks. The enabled DHCPv6
Option function resolves these issues.

2001:0db8:0006::9/64
for CMs.
2001:0db8:0006::11/64
for PCs.

//PCs require
/Bind DHCP
//Bind DHCP

2001:0db8:0004::4/64
2001:0db8:0001::1/64
domain of CMs.
----End

Prerequisites
Issue 01 (2016-04-29)

1417

Access Module

Management)
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.
Issue 01 (2016-04-29)
1418

Access Module

Management)

2.

3.
//The packets
//The packets

a.
b.

//Broadband
2001:0db8:0008::7/64
//
NOTE
----End
Result

A distributed converged cable access platform (D-CCAP) that works as a GE remote extended
frame connects to a port on a GE cascading board of an optical line terminal (OLT). You can
configure the remote extended frame only after adding it to the OLT.
Issue 01 (2016-04-29)

1419

Access Module

Management)
Prerequisites
The D-CCAP management policy is set to extend-frame. To do so, run the sysman
Context
Method
Usage Scenario
Remarks
Add a remote
extended frame
in offline mode.
The remote extended frames

must be deployed one by one.
This method facilitates remote
The remote extended frame ID has

been planned.
Add an
automatically
discovered
remote extended
frame.

The remote extended frame ID does

not need to be planned.
Data Plan
Item
Data
GE cascading
board
Port ID: 0/3/1

NOTE
Procedure
l

huawei(config-if-opg-0/3)#network-role extend
This operation will reset the board. Are you sure to continue ? (y/n)[n]:y
huawei(config)#frame add 1 MA5633 extending-port 0/3/1

The OLT supports the adding of an automatically discovered GE remote extended frame.
This function does not require manual confirmation, thereby simplifying the remote
extended frame registration and adding flow.
Issue 01 (2016-04-29)

1420

Access Module

Management)
----End
Result
remote extended frame status. Ensure that Online state is online and State is normal.
Follow-up Procedure
Possible Cause


permitted range.

-19.5 dBm to -3 dBm.
The D-CCAP works as a

frame.
Replace the D-CCAP with the one that works as a remote

extended frame.
The D-CCAP management

on the OLT.

configure the D-CCAP management policy to extendframe.


The working mode of the

ports on the remote extended
frame is not extend.
In Ethernet mode, run the network-role extend command

to set the working mode of the ports to extend.
Configuring RF Port Parameters

Context
Issue 01 (2016-04-29)

1421

Access Module

Management)

Method
Usage Scenario
Remarks
Use a cable
initialization
profile to
configure RF
port parameters.

efficiency.


configuration.
NOTE
by the OLT.
Customize RF
port parameters
in cable mode.



the parameters.
Data Plan
Issue 01 (2016-04-29)
Item
Data
RF port
1/1/0
Upstream
channels


1422

Access Module

Management)
Item
Data
Downstream
channels

722.00
Procedure
l

a.

b.
channels.
Parameter
Description

51.8-58.2 MHz.
modulation-profile


n

c.
Issue 01 (2016-04-29)
1 frequency 29.8
2 frequency 42.60
3 frequency 49.00
4 frequency 55.40

1423

Access Module

Management)
Parameter
Description
modulation

default setting.

enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
Issue 01 (2016-04-29)


1424

Access Module

Management)
NOTE
602.00 enable
610.00 enable
618.00 enable
626.00 enable
634.00 enable
642.00 enable
650.00 enable
658.00 enable
666.00 enable
674.00 enable
682.00 enable
690.00 enable
698.00 enable
706.00 enable
714.00 enable
722.00 enable

NOTE
a.
channels.
Issue 01 (2016-04-29)

1425

Access Module

Management)
b.

downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Configuring the HSI Service

Data Plan
Item
Data
VLAN

VLAN: smart
Uplink ports

Forwarding cable modem (CM) management and VoD packets:
0/5/0
Issue 01 (2016-04-29)

1426

Access Module

Management)
Procedure

NOTE
recommended.
----End
Configuring the DOCSIS VoD Service

Context
service.
Data Plan
Item
Data
VLAN
Uplink ports

Issue 01 (2016-04-29)

1427

Access Module

Management)
Procedure

NOTE
recommended.
----End
Configuring the EQAM VoD Service

Prerequisites
Context
Data Plan
Issue 01 (2016-04-29)
Item
Data
EQAM IP address
10.10.10.10

1428

Access Module

Management)
Item
Data
VLAN
Uplink port

0/5/0
EQAM channel ID
13-16
Modulation mode
QAM 64
Symbol rate
6.875
UDP port number
501-514
Procedure
Step 1 Use a cable initialization profile to configure RF port parameters.
qam64 enable channel-mode eqam symbol-rate 6.875
huawei(config-cable-init-template)#quit
115.0 modulation
123.00
131.00
139.00

Issue 01 (2016-04-29)


1429

Access Module

Management)

NOTE


udp-port 1
udp-port 1
udp-port 1
udp-port 1


----End
Result
transmitting.
l

Issue 01 (2016-04-29)

1430

Access Module

Management)
Context
service.
Data Plan
Item
Data
VLAN
Uplink ports

Procedure

NOTE
recommended.

NOTE
Step 5 Configure a multicast program generation mode.

Issue 01 (2016-04-29)

1431

Access Module

Management)
Multicast programs can be dynamically or statically generated. For the D-CCAP, the
multicast programs are dynamically generated.



NOTE


NOTE

authentication:
l
32
and 225.1.1.2

on permit

----End
Issue 01 (2016-04-29)

1432

Access Module

Management)
Configuring the Dynamic PacketCable Service

Context
Table 14-38 Data plan for the PacketCable service on the OLT
Item
Data
Uplink port
Forwarding VoIP packets: 0/4/0
VLAN
ID of service VLAN: 100

1000
IP address for
creating a COPS
connection to an
IP multimedia
subsystem (IMS)
or a softswitch

Procedure
NOTE
The ID of S-VLAN is 100 and the type of the VLAN is smart. The S-VLAN is a user-side
service VLAN between the OLT and the D-CCAP. The OLT works in Layer 3 forwarding
mode.

NOTE
recommended.
Issue 01 (2016-04-29)

1433

Access Module

Management)


connection

l

----End
Verifying Services
A CMC working as a remote extended frame locates on an optical node. To facilitate service
verification, the optical line terminal (OLT) supports multiple remote service verification
this section describes how to verify the home services on site.
Prerequisites
l
Procedure
a.

NOTE
b.
Issue 01 (2016-04-29)
1434

Access Module
c.
l

Management)

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.
DHCP



1435

Access Module
Issue 01 (2016-04-29)

Management)
CM
Status
Description
Handling Suggestion
l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1436

Access Module

Management)
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1437

Access Module
CM
Status

Management)
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

a.
programs.
b.
Internet from a PC.
c.
d.
----End
Issue 01 (2016-04-29)

1438

Access Module

Management)
14.4 L2VPN Enterprise Service Networking

In L2VPN enterprise service networking, a distributed converged cable access platform (DCCAP) connects to cable modems (CMs) through radio frequency (RF) ports, and the CMs
connect to switches or routers to provide the L2VPN service for users. This section describes
how to configure the optical line terminal (OLT) to provision the L2VPN service.
NOTE
Configuration Protocol (DHCP) relay" and "Configure a route".
14.4.1 Overview of the L2VPN BSoD Service

Business Services over DOCSIS (BSoD), launched by CableLabs.
Dot1Q-based L2VPN Service Model

In this service model, an OLT functions as a CE, and a router functions as a PE. The data is
forwarded between the OLT and the router at Layer 2 based on 802.1Q and between the router
and its upper-layer device in IP/MPLS PWE3 mode.
The following section uses two examples to describe how packets are forwarded in the
network. The following table lists packet encapsulation only in the upstream direction. The
packet encapsulation in the downstream direction is in reversal order of that in the upstream
direction and therefore will not be described in the remainder of this document.
Issue 01 (2016-04-29)
Ex
a
m
pl
e
N
o.
Packets
Sent from
a CPE
Packets Sent
from a CM
Packets Sent from the

CMC and OLT
Packets Sent from

a Router
Data
packets
These packets are

only DOCSIS
encapsulated,
without adding
any VLAN tag.
These packets are

DOCSIS decapsulated
and then added with an
S-VLAN tag.
The S-VLAN tag is

removed from these
packets. Then, these
packets are
encapsulated in
PWE3 mode.
Data
packets
These packets are

added with a CVLAN tag and
then DOCSIS
encapsulated.
These packets are

DOCSIS decapsulated.
The C-VLAN tag is
removed from these
packets are added with an
S-VLAN tag.
The S-VLAN tag is

removed from these
packets are
encapsulated in
PWE3 mode.

1439

Access Module

Management)
Figure 14-12 Dot1Q-based L2VPN service model
In addition to the L2VPN BSoD service in the preceding two examples, the L2VPN BSoD
service in the D-CCAP solution supports VLAN translation listed in the following table.
Table 14-39 VLAN Translation
Type
Status
untag >
S
untag > S
+C
C > S and C
S
C > S and
C=S
C>S
+C
C>S
+C'
Supporte
d
Supported
Supported
Supported
Support
ed
Support
ed
Note:
In "untag > S", the content before > shows the format of the packets sent from a CM, and
the content after > shows the format of the packets sent from the CMC and OLT.
Dot1ad-based L2VPN Service Model

In this service model, an OLT functions as a CE, and a router functions as a PE. The data is
forwarded between the OLT and the router at Layer 2 based on 802.1ad and between the
router and its upper-layer device in IP/MPLS PWE3 mode.
The following section uses one example to describe how packets are forwarded in the
network. The following table lists packet encapsulation only in the upstream direction. The
packet encapsulation in the downstream direction is in reversal order of that in the upstream
direction and therefore will not be described in the remainder of this document.
Issue 01 (2016-04-29)

1440

Access Module

Management)
Packets
Sent from
a CPE
Packets Sent
from a CM
Packets Sent from the

CMC and OLT
Packets Sent from a

Router
Data
packets
These packets are

only DOCSIS
encapsulated,
without adding any
VLAN tag.
These packets are DOCSIS

decapsulated and then
added with C-VLAN and
S-VLAN tags.
The S-VLAN tag is

removed from these
packets are
encapsulated in PWE3
mode.
Figure 14-13 Dot1ad-based L2VPN service model
14.4.2 Configuring the Dot1Q-based L2VPN BSoD Service

(GPON)
Control Board
SCUV
Cascading Board
GPMD: 0/3
SPU Board
SPUF: 0/4, 0/5

An enterprise requires the provisioning of the L2VPN service.
Issue 01 (2016-04-29)

1441

Access Module

Management)
Usage Scenario
As shown in Figure 14-14, an MA5633 is deployed on an optical node and cable modems
(CMs) are deployed at enterprises. The CMs connect to radio frequency (RF) ports on the
l
A CM provides the enterprise service through a switch, which connects to enterprise

users.
Enterprise users access the Internet through Dynamic Host Configuration Protocol
(DHCP) dialup.
The MA5633 works as a GPON remote extended frame. This reduces MA5633
Figure 14-14 L2VPN enterprise service networking
Figure 14-15 shows the configuration roadmap for the L2VPN service networking.
Issue 01 (2016-04-29)

1442

Access Module

Management)
Figure 14-15 Configuration roadmap for the L2VPN service networking
No.
Step
Description

(DHCP) relay.

network segments.

2

(IPv6).
Issue 01 (2016-04-29)

to the OLT.

servers.
OLT.

1443

Access Module

Management)
No.
Step
Description
Configure radio frequency (RF)

port parameters.

cables.
mode.
Configure the L2VPN service.
In the upstream direction, a cable modem

(CM) connects to a distributed converged
cable access platform (D-CCAP) through a
cable. In the downstream direction, the CM
connects to a switch to provide the L2VPN
enterprise service to the users connected to
the switch.
Verify the configured service.


Prerequisites
Issue 01 (2016-04-29)

1444

Access Module

Management)
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters
IP address of the DHCP domain gateway for CMs: 10.10.224.1;

domain name: docsis
Item
IP Address
Layer 3 interfaces
the OLT
IP address of the DHCP

server
DHCP server assigning IP addresses to CMs and media terminal

adapters (MTAs): 192.168.10.10-192.168.10.11
l Forwarding CM management packets: 11.11.12.11
Procedure
Step 1 Set the IP address of the VLAN Layer 3 interface.
address of the DHCP domain gateway for CMs.
//Set the IP

server group 0 to assign IP addresses to CMs.
//Configure DHCP

//Bind DHCP server
Issue 01 (2016-04-29)

1445

Access Module

Management)
Step 5 Set the IP address of the gateway for the DHCP domain.
//Set the
----End
Configuring a Route
Prerequisites
The upper-layer router of an OLT has been configured.
Data Plan
Item
IP Address
Forwarding Dynamic Host Configuration Protocol (DHCP)

packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
Forwarding cable modem (CM) management packets:
l VLAN ID: 2005
l IP address: 11.11.12.10/24
l Forwarding DHCP packets: 11.11.11.11
Layer 3 interfaces
the OLT
the OLT
l DHCP server assigning IP addresses to CMs and media

l CM management system: 192.168.20.1
Procedure
1.
Issue 01 (2016-04-29)
VLAN 2004 is of the smart VLAN type and used for forwarding DHCP packets.
VLAN 2005 is of the smart VLAN type and used for forwarding CM management
packets. Add uplink port 0/5/0 to VLAN 2005.
1446

Access Module

Management)

2.

VLAN information is required. The created native VLANs remove VLAN tags from the
packets transmitted out of Ethernet ports.
3.

a.
Create a Layer 3 interface for VLAN 2004, through which DHCP packets are
forwarded.
b.
Create a Layer 3 interface for VLAN 2005, through which CM management

devices.
//CM
management and VoD packets are forwarded through the Layer 3 interface of VLAN
2005.
//DHCP
NOTE
----End
Result

This section describes how to configure DHCPv6 relay so that CMs can obtain IP addresses
in different network segments.
Issue 01 (2016-04-29)

1447

Access Module

Management)
Prerequisites
OLT have been configured.
Data Plan
Table 14-44 data plan
Configuration Item
Data
Terminal-side of CM
network segment of CM: 2001:0db8:0001::/64
User-side of OLT
IP address of the gateway for the DHCP domain of CMs:

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure

huawei(config)#ipv6
Issue 01 (2016-04-29)

1448

Access Module

Management)

RA messages.
//
//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.

//Bind DHCP

huawei(config-if-vlanif100)#dhcpv6 domain docsis gateway
2001:0db8:0001::1/64
domain of CMs.
----End

Issue 01 (2016-04-29)

1449

Access Module

Management)
Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.
VLAN 2004 used for forwarding DHCP packets is a smart VLAN. Add uplink port
0/4/0 to VLAN 2004.
VLAN 2005 used for forwarding CM management packets is a smart VLAN. Add
uplink port 0/5/0 to VLAN 2005.

Issue 01 (2016-04-29)

1450

Access Module
2.

Management)

3.
//The packets
//The packets

a.
Create the Layer 3 interface of VLAN 2004, through which DHCP packets are
forwarded.
b.

2001:0db8:0008::7/64
//
NOTE
----End
Result

Prerequisites
Issue 01 (2016-04-29)

1451

Access Module

Management)
Context
Method
Usage Scenario
Remarks
Add a remote
extended frame
in offline mode.


extended frame.


Add an
automatically
discovered
remote extended
frame.

has been planned.

Data Plan
Item
Data
GPON cascading
board
Port ID: 0/3/1

NOTE
Dynamic
bandwidth
allocation (DBA)
Profile: default
Line profile
Profile: default
Type: type4

management mode)
Issue 01 (2016-04-29)

1452

Access Module
Item
Data
MA5633
management
mode
extend-frame

Management)
Procedure
l

NOTE

----End
Result
Follow-up Procedure
Issue 01 (2016-04-29)
Possible Cause


permitted range.

-27 dBm to -8 dBm.

disabled.

GPON ports.

1453

Access Module

Management)
Possible Cause

frame.

extended frame.

on the OLT.




Context
Issue 01 (2016-04-29)

1454

Access Module

Management)

Method
Usage Scenario
Remarks
Use a cable
initialization
profile to
configure RF
port parameters.

efficiency.


configuration.
NOTE
by the OLT.
Customize RF
port parameters
in cable mode.



the parameters.
Data Plan
Issue 01 (2016-04-29)
Item
Data
RF port
1/1/0
Upstream
channels


1455

Access Module

Management)
Item
Data
Downstream
channels

722.00
Procedure
l

a.

b.
channels.
Parameter
Description

51.8-58.2 MHz.
modulation-profile


n

c.
Issue 01 (2016-04-29)
1 frequency 29.8
2 frequency 42.60
3 frequency 49.00
4 frequency 55.40

1456

Access Module

Management)
Parameter
Description
modulation

default setting.

enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
Issue 01 (2016-04-29)


1457

Access Module

Management)
NOTE
602.00 enable
610.00 enable
618.00 enable
626.00 enable
634.00 enable
642.00 enable
650.00 enable
658.00 enable
666.00 enable
674.00 enable
682.00 enable
690.00 enable
698.00 enable
706.00 enable
714.00 enable
722.00 enable

NOTE
a.
channels.
Issue 01 (2016-04-29)

1458

Access Module

Management)
b.

downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Configuring the L2VPN Enterprise Service

In the upstream direction, a cable modem (CM) connects to a distributed converged cable
access platform (D-CCAP) through a cable. In the downstream direction, the CM connects to
a switch to provide the L2VPN enterprise service to the users connected to the switch.
Context
An L2VPN S-VLAN can be configured through a CM configuration file or commands. Only
one mode is used each time generally. If both modes are used, the S-VLAN configuration
through commands preferentially takes effect on the system when the CM goes online.
l
S-VLAN configuration through a CM configuration file: Run the vlan command to add a
CM S-VLAN and run the port vlan command to add the uplink port for the CM to the
S-VLAN. The L2VPN S-VLAN is specified in the CM configuration file. When the CM
goes online, the system obtains the L2VPN S-VLAN from the CM configuration file and
automatically creates L2VPN service flows.
S-VLAN configuration through commands: Manually configure the L2VPN S-VLAN on

the system. For details, see the following procedure.
Issue 01 (2016-04-29)

1459

Access Module

Management)
Data Plan
Table 14-50 Data plan for the L2VPN service
Item
Data
VLAN
ID of the L2VPN S-VLAN: 200; type of the VLAN: smart
Uplink ports
Port forwarding Dynamic Host Configuration Protocol (DHCP)

and broadband packets: 0/4/0
Port forwarding CM management packets: 0/5/0
Procedure
Step 1 Create an L2VPN S-VLAN and add the uplink port to it.
The ID of the L2VPN S-VLAN is 200 and the type of the VLAN is smart. Uplink port 0/4/0
is added to S-VLAN 200.
When the L2VPN S-VLAN is configured through commands, the ID of the L2VPN VLAN is
200 for the CM with MAC address 0000-0000-1111 connected to port 1/1/0.
l
To configure the L2VPN S-VLAN through a CM configuration file, run the following
commands:
To configure the L2VPN S-VLAN through commands, run the following commands:
huawei(config)#cable l2vpn dot1q 1/1/0 cm 0000-0000-1111 200
Step 2 Configure a VLAN service profile and set the DHCP forwarding mode for VLAN 200 to
Layer 2 forwarding.
huawei(config)#vlan service-profile profile-name l2vpn
huawei(config-vlan-srvprof-1)#dhcp mode layer-2
huawei(config)#vlan bind service-profile 200 profile-name l2vpn
----End
Verifying Services
A distributed converged cable access platform (D-CCAP) working as a remote extended
frame locates on an optical node. To facilitate service verification, the optical line terminal
(OLT) supports multiple remote service verification methods, such as Dynamic Host
Configuration Protocol (DHCP) dialup emulation tests. This allows commissioning and
configuration engineers to remotely verify services. In addition, this section describes how to
verify the L2VPN service on site.
Prerequisites
l
Issue 01 (2016-04-29)

1460

Access Module

Management)
Procedure
l

a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.

1461

Access Module
Issue 01 (2016-04-29)

Management)
CM
Status
Description
Handling Suggestion
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1462

Access Module

Management)
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1463

Access Module
CM
Status

Management)
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.
Verify that the L2VPN service can be provisioned.

After the CM is installed in the enterprise and the switch connected to the CM is
commissioned, L2VPN service can be provisioned.
----End
14.4.3 WLAN Hotspot Radio Backhaul Service Networking

(GPON)
In wireless local area network (WLAN) hotspot radio backhaul service networking, a
distributed converged cable access platform (D-CCAP) connects to cable modems (CMs)
through radio frequency (RF) ports. A CM connects to wireless access points (APs) to
Issue 01 (2016-04-29)

1464

Access Module

Management)
provide wireless fidelity (Wi-Fi) access for users. This section describes how to configure the
optical line terminal (OLT) to provision the WLAN hotspot radio backhaul service.
A network supplier needs to provide the Internet access service through Wi-Fi for a business
area covered by APs.
Usage Scenario
As shown in Figure 14-16, a D-CCAP is deployed on an optical node and CMs are deployed
at shops. The CMs connect to RF ports on the D-CCAP through cables.
l
A CM connects to wireless APs to provide the WLAN hotspot radio backhaul service.
The wireless APs provide Wi-Fi access for users.
Wi-Fi users access the Internet through Dynamic Host Configuration Protocol (DHCP)
dialup.
The D-CCAP works as a GPON remote extended frame. This reduces D-CCAP
Figure 14-16 WLAN hotspot radio backhaul service networking
Configuration
The method of configuring the WLAN hotspot radio backhaul service is the same as that of
configuring the L2VPN enterprise service and therefore is not described in this section. For
details, see Configuration Process.
14.4.4 Configuring the Dot1Q-based L2VPN BSoD Service (GE)

Issue 01 (2016-04-29)
Control Board
SCUV
Cascading Board
OPGE: 0/3

1465

Access Module
SPU Board

Management)
SPUF: 0/4, 0/5

Usage Scenario
l

users.
(DHCP) dialup.
The MA5633 works as a GE remote extended frame to reduce MA5633 management

and maintenance costs and simplify configurations.
Issue 01 (2016-04-29)

1466

Access Module

Management)
No.
Step
Description

(DHCP) relay.

network segments.

2

(IPv6).
Issue 01 (2016-04-29)

to the OLT.

servers.
OLT.

1467

Access Module

Management)
No.
Step
Description

port parameters.

cables.
mode.
In the upstream direction, a cable modem

(CM) connects to a distributed converged
cable access platform (D-CCAP) through a
cable. In the downstream direction, the CM
connects to a switch to provide the L2VPN
enterprise service to the users connected to
the switch.


Prerequisites
Issue 01 (2016-04-29)

1468

Access Module

Management)
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

domain name: docsis
Item
IP Address
Layer 3 interfaces
the OLT

server

adapters (MTAs): 192.168.10.10-192.168.10.11
Procedure
//Set the IP

//Configure DHCP

//Bind DHCP server
Issue 01 (2016-04-29)

1469

Access Module

Management)
//Set the
----End
Configuring a Route
Prerequisites
Data Plan
Item
IP Address

packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT
the OLT

Procedure
1.
Issue 01 (2016-04-29)
1470

Access Module

Management)

2.

3.

a.
forwarded.
b.

devices.
//CM
2005.
//DHCP
NOTE
----End
Result

Issue 01 (2016-04-29)

1471

Access Module

Management)
Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure

huawei(config)#ipv6
Issue 01 (2016-04-29)

1472

Access Module

Management)

RA messages.
//
//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.

//Bind DHCP

2001:0db8:0001::1/64
domain of CMs.
----End

Issue 01 (2016-04-29)

1473

Access Module

Management)
Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.
0/4/0 to VLAN 2004.

Issue 01 (2016-04-29)

1474

Access Module
2.

Management)

3.
//The packets
//The packets

a.
forwarded.
b.

2001:0db8:0008::7/64
//
NOTE
----End
Result

A distributed converged cable access platform (D-CCAP) that works as a GE remote extended
frame connects to a port on a GE cascading board of an optical line terminal (OLT). You can
configure the remote extended frame only after adding it to the OLT.
Prerequisites
The D-CCAP management policy is set to extend-frame. To do so, run the sysman
Issue 01 (2016-04-29)

1475

Access Module

Management)
Context
Method
Usage Scenario
Remarks
Add a remote
extended frame
in offline mode.
The remote extended frames

must be deployed one by one.
This method facilitates remote
The remote extended frame ID has

been planned.
Add an
automatically
discovered
remote extended
frame.

The remote extended frame ID does

not need to be planned.
Data Plan
Item
Data
GE cascading
board
Port ID: 0/3/1

NOTE
Procedure
l

huawei(config)#frame add 1 MA5633 extending-port 0/3/1

The OLT supports the adding of an automatically discovered GE remote extended frame.
This function does not require manual confirmation, thereby simplifying the remote
extended frame registration and adding flow.
----End
Issue 01 (2016-04-29)

1476

Access Module

Management)
Result
remote extended frame status. Ensure that Online state is online and State is normal.
Follow-up Procedure
Possible Cause


permitted range.

-19.5 dBm to -3 dBm.
The D-CCAP works as a

frame.
Replace the D-CCAP with the one that works as a remote

extended frame.
The D-CCAP management

on the OLT.

configure the D-CCAP management policy to extendframe.


The working mode of the

ports on the remote extended
frame is not extend.
In Ethernet mode, run the network-role extend command

to set the working mode of the ports to extend.

Context
Issue 01 (2016-04-29)

1477

Access Module

Management)

Method
Usage Scenario
Remarks
Use a cable
initialization
profile to
configure RF
port parameters.

efficiency.


configuration.
NOTE
by the OLT.
Customize RF
port parameters
in cable mode.



the parameters.
Data Plan
Issue 01 (2016-04-29)
Item
Data
RF port
1/1/0
Upstream
channels


1478

Access Module

Management)
Item
Data
Downstream
channels

722.00
Procedure
l

a.

b.
channels.
Parameter
Description

51.8-58.2 MHz.
modulation-profile


n

c.
Issue 01 (2016-04-29)
1 frequency 29.8
2 frequency 42.60
3 frequency 49.00
4 frequency 55.40

1479

Access Module

Management)
Parameter
Description
modulation

default setting.

enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
Issue 01 (2016-04-29)


1480

Access Module

Management)
NOTE
602.00 enable
610.00 enable
618.00 enable
626.00 enable
634.00 enable
642.00 enable
650.00 enable
658.00 enable
666.00 enable
674.00 enable
682.00 enable
690.00 enable
698.00 enable
706.00 enable
714.00 enable
722.00 enable

NOTE
a.
channels.
Issue 01 (2016-04-29)

1481

Access Module

Management)
b.

downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Configuring the L2VPN Enterprise Service

Context
l
S-VLAN. The L2VPN S-VLAN is specified in the CM configuration file. When the CM
goes online, the system obtains the L2VPN S-VLAN from the CM configuration file and

Issue 01 (2016-04-29)

1482

Access Module

Management)
Data Plan
Item
Data
VLAN
Uplink ports
Port forwarding Dynamic Host Configuration Protocol (DHCP)

and broadband packets: 0/4/0
Port forwarding CM management packets: 0/5/0
Procedure
l
commands:
Step 2 Configure a VLAN service profile and set the DHCP forwarding mode for VLAN 200 to
Layer 2 forwarding.
huawei(config)#vlan service-profile profile-name l2vpn
huawei(config-vlan-srvprof-1)#dhcp mode layer-2
huawei(config)#vlan bind service-profile 200 profile-name l2vpn
----End
Verifying Services
verify the L2VPN service on site.
Prerequisites
l
Issue 01 (2016-04-29)

1483

Access Module

Management)
Procedure
l

a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.

1484

Access Module
Issue 01 (2016-04-29)

Management)
CM
Status
Description
Handling Suggestion
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1485

Access Module

Management)
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1486

Access Module
CM
Status

Management)
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

----End
14.4.5 WLAN Hotspot Radio Backhaul Service Networking (GE)

In wireless local area network (WLAN) hotspot radio backhaul service networking, a
distributed converged cable access platform (D-CCAP) connects to cable modems (CMs)
through radio frequency (RF) ports. A CM connects to wireless access points (APs) to
provide wireless fidelity (Wi-Fi) access for users. This section describes how to configure the
optical line terminal (OLT) to provision the WLAN hotspot radio backhaul service.
Issue 01 (2016-04-29)

1487

Access Module

Management)
Usage Scenario
As shown in Figure 14-19, a D-CCAP is deployed on an optical node and CMs are deployed
at shops. The CMs connect to RF ports on the D-CCAP through cables.
l
dialup.
The D-CCAP works as a GE remote extended frame. This reduces D-CCAP

Configuration
14.5 Multiple services in multiple VLANs Service

Networking (GPON)
In home service (VLAN tag transparent transmission) networking, a distributed converged
cable access platform (D-CCAP) connects to cable modems (CMs) at user homes through
radio frequency (RF) ports and provides home services for users, including the cable TV
(CATV) service, Internet access service, and VoD service. This section describes how to
configure the optical line terminal (OLT) to provision the home services.

Issue 01 (2016-04-29)

1488

Access Module

Management)
Users require the provisioning of the broadcast and TV services, Internet access service, and
VoD service. Broadcast and TV services can be provisioned immediately after the distributed
converged cable access platform (D-CCAP) hardware is connected. This section only
describes how to configure the Internet access service, and VoD service.
Usage Scenario
Some carriers deploy HGWs on the lower-layer of CMs. The HGWs add different VLAN tags
to packets based on service types. This requires that the CMCs support transparent
transmission of VLAN tags. As shown in Figure 14-20, a D-CCAP is deployed on an optical
node and cable modems (CMs) are deployed at user homes. The CMs connect to radio
frequency (RF) ports on the MA5633 through cables.
l
Port 1 on CM connects to a PC to provide the Internet access service. A set top box
(STB) connects to the distributor to provide a backhaul channel for the VoD service.
The IP addresses of the CM, STB, and PC are assigned by the DHCP server and in
The D-CCAP is used as a GPON remote extended frame. This reduces D-CCAP
Figure 14-20 Home service networking (VLAN tag transparent transmission)

Issue 01 (2016-04-29)

1489

Access Module

Management)
The following table describes configuration steps. All configurations are issued from the
No.
Step
Description

to the OLT.

OLT.

port parameters.

cables.
mode.
Issue 01 (2016-04-29)

None

1490

Access Module

Management)
No.
Step
Description
Configure the DOCSIS VoD

service.
l If the MA5633 is not equipped with a

built-in EQAM module, the MA5633
uses DOCSIS channels to transmit VoD
data.
l If the MA5633 is equipped with a builtin EQAM module, the MA5633 sets
idle downstream DOCSIS channels as
EQAM channels to transmit VoD data.
The DOCSIS VoD service and the EQAM
VoD service are generally not concurrently
used. The DOCSIS VoD service is used as
an example.

14.5.3 Adding a Remote Extended Frame to an OLT

Prerequisites
Context
Issue 01 (2016-04-29)

1491

Access Module

Management)

Method
Usage Scenario
Remarks
Add a remote
extended frame
in offline mode.


extended frame.


Add an
automatically
discovered
remote extended
frame.

has been planned.

Data Plan
Item
Data
GPON cascading
board
Board: H801GPMD
Port ID: 0/3/1
NOTE
Dynamic
bandwidth
allocation (DBA)
Profile: default
Line profile
Profile: default
Type: type4

management mode)
MA5633
management
mode
Issue 01 (2016-04-29)
extend-frame

1492

Access Module

Management)
Procedure
l
Configure the working mode of the DHCP layer 2 forwarding mode.

huawei(config)#dhcp mode layer-2
Enable the DHCP option82 feature.

DHCP feature encounters many security problems when it is used in the network. To
solve these problems, the DHCP option82 is introduced.

NOTE

----End
Result
Follow-up Procedure
Issue 01 (2016-04-29)
Possible Cause


permitted range.

-27 dBm to -8 dBm.

disabled.

GPON ports.

1493

Access Module

Management)
Possible Cause

frame.

extended frame.

on the OLT.



14.5.4 Configuring RF Port Parameters

Context
Issue 01 (2016-04-29)

1494

Access Module

Management)

Method
Usage Scenario
Remarks
Use a cable
initialization
profile to
configure RF
port parameters.

efficiency.


configuration.
NOTE
by the OLT.
Customize RF
port parameters
in cable mode.



the parameters.
Data Plan
Issue 01 (2016-04-29)
Item
Data
RF port
1/1/0
Upstream
channels


1495

Access Module

Management)
Item
Data
Downstream
channels

722.00
Procedure
l

a.

b.
channels.
Parameter
Description

51.8-58.2 MHz.
modulation-profile


n

c.
Issue 01 (2016-04-29)
1 frequency 29.8
2 frequency 42.60
3 frequency 49.00
4 frequency 55.40

1496

Access Module

Management)
Parameter
Description
modulation

default setting.

enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
enable
Issue 01 (2016-04-29)


1497

Access Module

Management)
NOTE
602.00 enable
610.00 enable
618.00 enable
626.00 enable
634.00 enable
642.00 enable
650.00 enable
658.00 enable
666.00 enable
674.00 enable
682.00 enable
690.00 enable
698.00 enable
706.00 enable
714.00 enable
722.00 enable

NOTE
a.
channels.
Issue 01 (2016-04-29)

1498

Access Module

Management)
b.

downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
14.5.5 Configuring the HSI Service

A CM connects to an MA5633 through a cable and provides the HSI service for users.
Data Plan
Item
Data
VLAN
Tag type of the packets sent by the PC: untagged; VLAN ID of

the HGW management packets (HGW Mg) added on the HGW:
300; transmission mode of the HGW management packets on
the HGW: transparent transmission
VLAN ID of the HSI service packets and CM management
packets (CM Mg) added on the MA5633: 100; type of the
VLAN: smart; attribute of the VLAN: common
Name of a cable service domain: huawei
Issue 01 (2016-04-29)

1499

Access Module

Management)
Item
Data
Uplink port
Forwarding DHCP and broadband packets: 0/4/0

Forwarding CM and HGW management packets: 0/5/0
Procedure
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
huawei(config)#port
huawei(config)#port
100 smart
300 smart
vlan 100 0/4 0
vlan 100 0/5 0
vlan 300 0/5 0

Step 3 Add cable service domain huawei, add the HSI service to this service domain, and configure
mapping rules.
huawei(config)#cable service-domain huawei
huawei(config-cable-srv-domain-huawei)#mapping vlan 100 tag-transform add ifmatch user-vlan untagged
huawei(config-cable-srv-domain-huawei)#mapping vlan 300 tag-transform translate
if-match user-vlan 300
//Transparently transmitting HGW management packets
huawei(config-cable-srv-domain-huawei)#member cm ip-prefix 10.10.10.0
255.255.255.0
----End
14.5.6 Configuring the DOCSIS VoD Service

A CM connects to an MA5633 through a cable and provides the DOCSIS VoD service for
users.
Data Plan
Table 14-67 Data plan for the DOCSIS VoD service
Item
Data
VLAN
Tag type of the packets sent by the STB: untagged; VLAN ID

of the VoD packets added on the HGW: 200; type of the VLAN:
smart; attribute of the VLAN: common
Transmission mode of the VoD packets on the MA5633:
transparent transmission
Name of a cable service domain: huawei
Uplink port
Issue 01 (2016-04-29)
Forwarding VoD packets: 0/5/0

1500

Access Module

Management)
Procedure
Step 2 Add cable service domain huawei, add the VoD service to this service domain, and configure
mapping rules.
huawei(config)#cable service-domain huawei
huawei(config-cable-srv-domain-huawei)#mapping vlan 200 tag-transform translate
if-match user-vlan 200
//Transparently transmitting VoD packets
huawei(config-cable-srv-domain-huawei)#member cm ip-prefix 10.10.10.0
255.255.255.0
----End

verify the home services on site.
Prerequisites
l
Procedure
a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
Issue 01 (2016-04-29)

1501

Access Module

Management)
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.


1502

Access Module
Issue 01 (2016-04-29)

Management)
CM
Status
Description
Handling Suggestion
REG

started.

configuration file.

1503

Access Module

Management)
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1504

Access Module
CM
Status

Management)
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

a.
programs.
b.
Internet from a PC.
c.
----End
Issue 01 (2016-04-29)

1505

Access Module
15
15 D-CCAP Service Configuration (Standalone NE)
D-CCAP Service Configuration

(Standalone NE)
About This Chapter

The optiCable solution implements cable TV (CATV) and broadband signal transmission over
a coaxial network. It applies in CATV network reconstruction in upstream and downstream
directions or new residential areas requiring the CATV and broadband services over a coaxial
network. The radio frequency (RF) access mode applies in the PON+distributed converged
cable access platform (D-CCAP) scenario or GE+D-CCAP scenario. This mode complies
with the data over cable service interface specification (DOCSIS) and supports multiple
broadcast and TV services, such as high-speed Internet (HSI) and IPTV services.
15.2 Configuring Services on an MA5633 (GE)
This section describes how to configure services, including home services, L2VPN enterprise
service, and wireless local area network (WLAN) hotspot radio backhaul service, on an
MA5633 that works in GE access mode on a Layer 3 network. The MA5603T equipped with
the SCUV, OPGE, and SPUF boards is used as an example.
15.3 Configuring Services on a D-CCAP ()
service, and wireless local area network (WLAN) hotspot radio backhaul service, on a
distributed converged cable access platform (D-CCAP) that works in access mode on a Layer
3 network. The MA5603T equipped with the SCUV, GPBH, and SPUF boards is used as an
example.
Issue 01 (2016-04-29)

1506

Access Module

15.1.1 Basic Concepts

This section describes basic concepts related to a distributed converged cable access platform
(D-CCAP) from the user side to the network side on D-CCAP networks using PON and GE
Issue 01 (2016-04-29)

1507

Access Module
Figure 15-1 D-CCAP networking
User Home Side
Issue 01 (2016-04-29)
Concept
Description
Cable modem
(CM)
A device that connects customer premises equipment (CPE) to a

hybrid fiber coaxial (HFC) network. It transmits data over a cable
network through data over cable service interface specification
(DOCSIS).

1508

Access Module
Concept
Description
Media terminal
adapter (MTA)
A network client that provides user terminal (such as a phone set)oriented ports and call control unit-oriented network signaling
interfaces. It connects to cable network units through an HFC
network.
MTAs are classified into embedded MTAs (EMTAs) and single MTAs
(SMTAs) according to PacketCable.
l An EMTA integrates CM and MTA functions.
l An SMTA supports only MTA functionalities.
VoD

locating.
Distributor
A component that distributes signals in a cable TV (CATV)

transmission system. It equally outputs several channels of signals
from one channel of input signals. The common distribution ratios are
1:2, 1:3, 1:4, and 1:6.
Concept
Description
D-CCAP
A device that connects an aggregation network to an HFC network. It

forwards network data, processes protocols, and modulates or
demodulates radio frequency (RF) signals. The D-CCAP provides the
quality of service (QoS) required by CMs and allocates upstream
bandwidths and service resources to the CMs based on CMs' request
and network QoS policy.
Built-in optical
receiver
l An optical receiver, which performs optical-to-electrical (O/E)

Optical Node
l The fiber node does not require an additional optical receiver. The
O/E conversion is performed by the optical receiver built in the
MA5633 and the MA5633 can receive CATV optical signals.
Built-in WDM
l A device that multiplexes the optical signals with different

standard wavelengths into one channel of multiplexed signals and
transmits the signals over one optical fiber.
l The WDM in the branch equipment room combines data signals
and CATV signals for signal transmission over one feeder fiber.
On the optical node, the WDM built in the MA5633 separates the
two types of signals from each other.
Issue 01 (2016-04-29)

1509

Access Module
Concept
Description
Built-in EQAM
l The edge quadrature amplitude modulation (EQAM) feature

enables the MA5633 to function as the gateway of a hybrid fiber
coaxial (HFC) network connected to an IP network. The MA5633
multiplexes and modulates IP signals into radio frequency (RF)
signals so that the data carried in the IP signals can be transmitted
over the HFC network.
l The EQAM built in the MA5633 is moved downwards from the
branch equipment room to the fiber node. Therefore, the fiber node
does not require an additional EQAM.
l Video streams are transmitted over a MAN network through the
OLT to the MA5633. The MA5633 uses the built-in EQAM to
module the video signals into RF signals and sends the RF signals
to the STB.
Splitter
A component that connects to the center of a branch or feeder fiber. It

consists of a main input end, a main output end, and multiple branch
output ends. Each branch output end receives only few input signals
on the main path. The majority signals are transmitted forward over
the main path.
Branch Equipment Room

Concept
Description
PON

Issue 01 (2016-04-29)
Optical
distribution
network (ODN)

Optical line
terminal (OLT)

which terminates PON protocols.
Optical splitter
A passive component, which allocates optical power to multiple

ONUs connected to one feeder fiber. In a GPON network that consists
of an OLT, ONUs, optical splitters, and optical fibers, the optical fiber
connected to the OLT uses an optical splitter to connect to multiple
ONUs. The number of ONUs that can be connected to the optical
fiber is determined based on the split ratio.

1510

Access Module
Concept
Description
RX
An optical receiver, which performs optical-to-electrical (O/E)

TX
An optical transmitter, which performs O/E conversion for received

CATV signals.
Combiner
A component that combines multiple channels of analog signals into

one channel of signals on an RF port and then sends the signals to the
downstream optical TX.
Concept
Description
Softswitch or IP
multimedia
subsystem (IMS)
Softswitch: core of the NGN network call and control, which supports
call and connection control for the services having high real-time
requirements. For the softswitch, services are separated from call
control and call control is separated from bearing. In addition, the
softswitch uses open service interface (API) and standard protocols,
which facilitates the development for new services and features.
MAN Network
IMS: uses Session Initiation Protocol (SIP) signaling as the call

control signaling. It provides voice, data, and multimedia services.
Broadband TV
(BTV) source
IPTV head end, a contents preparation platform in the IPTV system. It

receives signals, converts media formats, and manages media
materials.
15.1.2 Networking Scenarios and Hardware Configurations

(D-CCAP) and D-CCAP's hardware configurations.
Issue 01 (2016-04-29)

1511

Access Module
Networking Scenarios and Hardware Configurations

Networking
Scenario
Description
MA5600T Series
ONU Device
Home service
networking
In home service networking,

an MA5633 connects to
cable modems (CMs) at user
homes through radio
frequency (RF) ports and
provides home services for
users, including the cable
TV (CATV) service, Internet
access service, VoD service,
broadband TV (BTV)
service, and PacketCable
service.
MA5603T/
MA5600T:
l Equipped with a
built-in optical
receiver:
MA5633,
providing 4-out
radio frequency
(RF) ports
L2VPN
enterprise
service
networking
In L2VPN enterprise service

networking, an MA5633
connects to cable modems
(CMs) through radio
frequency (RF) ports, and
the CMs connect to switches
service for users.
l GE: MCUE
+OPGE+SPUF
Wireless local
area network
(WLAN)
hotspot radio
backhaul
service
networking

network (WLAN) hotspot
radio backhaul service
networking, an MA5633
connects to cable modems
(CMs) through radio
frequency (RF) ports. A CM
connects to wireless access
points (APs) to provide
wireless fidelity (Wi-Fi)
access for users.
l GPON: SCUV
+GPMD
+SPUF
l GE: SCUV
+OPGE+SPUF
MA5608T:
l GPON: MCUE
+GPMD
+SPUF
l Equipped without
a built-in optical
receiver:
MA5633,
providing 2-in-2out or 4-in-4-out
RF ports
l Equipped with a
built-in WDM:
MA5633,
providing 4-out
radio frequency
(RF) ports
15.2 Configuring Services on an MA5633 (GE)

service, and wireless local area network (WLAN) hotspot radio backhaul service, on an
MA5633 that works in GE access mode on a Layer 3 network. The MA5603T equipped with
the SCUV, OPGE, and SPUF boards is used as an example.
Issue 01 (2016-04-29)
Control Board
SCUV
Interface Board
OPGE: 0/3
SPU Board
SPUF: 0/4, 0/5

1512

Access Module
NOTE
When an OPGE board is used, run the network-role command on the OLT to configure the ports on the
OPGE board as cascading ports.
15.2.1 Home Service Networking

In home service networking, an MA5633 connects to cable modems (CMs) at user homes
through radio frequency (RF) ports and provides home services for users, including the cable
TV (CATV) service, Internet access service, VoD service, broadband TV (BTV) service, and
PacketCable service. This section describes how to configure the optical line terminal (OLT)
and the MA5633 to provision the home services.
NOTE

Usage Scenario
(CMs) are deployed at user homes. The CMs connect to radio frequency (RF) ports on the
l

Issue 01 (2016-04-29)

1513

Access Module
Issue 01 (2016-04-29)

1514

Access Module
NOTE
Before logging in to the MA5633 to configure services on it, ensure that the MA5633 has been properly
connected.

Config
uration
Object
Step
Description
OLT

(DHCP) relay.

network segments.

(IPv6).
MA563
3
Issue 01 (2016-04-29)

servers.
Configure a management
channel between the OLT and
the D-CCAP.
This section describes how to configure a

management channel between an optical
line terminal (OLT) and an MA5633. After
the configuration, you can log in to the
MA5633 from the OLT and configure the
MA5633.
Configure a service channel

between the OLT and the DCCAP.

service channel between an optical line
terminal (OLT) and an MA5633. After the
configuration, the service channel forwards
service packets on the MA5633 based on
the planned VLAN and forwarding policy.

port parameters.

cables.

None
None
Configure the broadband TV

(BTV) service.
None

1515

Access Module
Config
uration
Object
Step
Description

None


Prerequisites
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

Issue 01 (2016-04-29)

1516

Access Module
Item
IP Address
Layer 3 interfaces
the OLT
servers

192.168.10.10-192.168.10.11

11.11.12.11

192.168.10.12-192.168.10.13
server
192.168.5.10-192.168.5.13
Procedure
docsis
pktc
stb
default
default


Issue 01 (2016-04-29)

//Configure DHCP
1517

Access Module

//Configure DHCP

PCs.
//Paid and
//Bind DHCP
//Bind DHCP server
//Bind DHCP server
//Bind DHCP server

10.100.8.1
//Set the
//Set the IP
//Set the IP
----End
Configuring a Route
Prerequisites
Issue 01 (2016-04-29)

1518

Access Module
Data Plan
Item
IP Address

broadband packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
Forwarding cable modem (CM) management, VoD, COPS, and
multicast packets:
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT

l Forwarding CM management, VoD, COPS, and multicast
packets: 11.11.12.11
l COPS gateway IP address: 192.168.60.1
the OLT
l DHCP servers:
boxes (STBs): 192.168.10.12-192.168.10.13
192.168.20.10-192.168.20.12
192.168.50.10
Procedure
1.

2.

Issue 01 (2016-04-29)

1519

Access Module

3.

a.
b.
devices.
//Broadband
//CM
//DHCP
NOTE
l The interconnected router must set static routes and add the routes to dynamic routes.
----End
Result

Prerequisites
The upper-layer router, DHCP server server of an OLT have been configured.
Issue 01 (2016-04-29)

1520

Access Module
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
huawei(config)#ipv6
Issue 01 (2016-04-29)

1521

Access Module
RA messages.
//
//Configure the
//Configure the
//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.
2001:0db8:0006::11/64
for PCs.

//PCs require
/Bind DHCP
//Bind DHCP

2001:0db8:0004::4/64
Issue 01 (2016-04-29)

1522

Access Module

2001:0db8:0001::1/64
domain of CMs.
----End

Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Issue 01 (2016-04-29)

1523

Access Module
Configuration Item
Data
Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.

2.

3.
//The packets
//The packets

a.
b.

//Broadband
2001:0db8:0008::7/64
Issue 01 (2016-04-29)

1524

Access Module

//
NOTE
----End
Result
Configuring a Management Channel Between an OLT and an MA5633

terminal (OLT) and an MA5633. After the configuration, you can log in to the MA5633 from
the OLT and configure the MA5633.
Prerequisites
The MA5633 management policy is set to stand-alone. To do so, run the sysman
Data Plan
Item
Data
Remarks
OLT
GE port: 0/3/0
Management VLAN
and IP address of
the D-CCAP
VLAN: 8
l Do not enable both the remote

software commissioning using
PON upstream transmission and
the remote software
commissioning using GE upstream
transmission.
l Ensure that the database of a
newly deployed D-CCAP is empty.
Otherwise, the remote software
transmission cannot be used.
l When the D-CCAP automatically
obtains management parameters, it
automatically generates a default
route that can be restored.
However, the default route may
not be proper in service
configuration. Therefore, you are
advised to add a new route and
delete the default one after the DCCAP management channel is
available.

VLAN: smart
192.168.50.2/24
Issue 01 (2016-04-29)

1525

Access Module
Item
Data
Remarks
Management profile
of the D-CCAP
ID: 64
l After the D-CCAP automatically

obtains management parameters,
the remote software
commissioning function is
automatically disabled if
configurations are issued to the DCCAP through the U2000. To
modify the D-CCAP management
parameters, remotely log in to the
D-CCAP through the command
line interface (CLI).
Procedure
Step 1 Configure a management channel between the OLT and the MA5633.
1.

2.
Enable Network Admission Control (NAC) on the OLT.

3.

Perform this operation if the MA5633 is managed through the U2000. Plan an SNMP
management profile on the U2000 and MA5633 before creating the profile.
huawei(config)#snmp-profile add profile-id 64 profile-name snmp-profile_64
v2c public
4.
Configure MA5633 management parameters on the OLT.

huawei(config)#nac config master 0/3/0 slave vlan 8 priority 6 ip-address
Check whether the MA5633 management parameters have been configured on the OLT.
{ <cr>|frameid/slotid/portid<S><Length 1-255>|frameid/slotid<S><Length
1-15> }:
Command:
display nac configuration master
----------------------------------------------------------------------------Frame ID/Slot ID/Port ID : 0/3/0
VLAN
: 8
VLAN priority
: 3
IP address
: 192.168.50.2
Mask
: 255.255.255.0
Gateway
: 192.168.50.254
Snmp-profile-id
: 64
Snmp-profile-name
: snmp-profile_64
----------------------------------------------------------------------------Total: 1
Issue 01 (2016-04-29)

1526

Access Module
Step 2 Check whether the management channel between the OLT and the MA5633 is available.
Upon power-on, the MA5633 exchanges data with the OLT to obtain the management
parameters.
l
Run the ping 192.168.50.2 command on the OLT to check whether the MA5633 can
communicate with the OLT. If the OLT can receive Internet Control Message Protocol
(ICMP) ECHO-REPLY packets sent from the MA5633, the MA5633 is connected to the
OLT.
Run the telnet command on the OLT to remotely log in to the ONU from the OLT to
perform the configuration. The user name is root and the password is admin123.
----End
Configuring a Service Channel Between an OLT and anMA5633

This section describes how to configure a service channel between an optical line terminal
(OLT) and an MA5633. After the configuration, the service channel forwards service packets
on the MA5633 based on the planned VLAN and forwarding policy.
Data Plan
Item
Data
High-speed Internet (HSI), VoD,

broadband TV (BTV), or dynamic
PacketCable service
ID of the OLT VLAN (transparently transmitting

MA5633 packet tags): 100
ID of the MA5633 VLAN: 100
ID of the common open policy service (COPS)
connection VLAN: 1000
Uplink ports
Forwarding Dynamic Host Configuration Protocol

(DHCP) and broadband packets: 0/4/0
Forwarding cable modem (CM) management, VoD,
and multicast packets: 0/5/0
Procedure
l
Configure a channel for a home service.

a.
Configure service flows to receive and transparently transmit MA5633 packets.

The following configurations are used as an example to configure service flows:
n
Issue 01 (2016-04-29)
Configuration of a service flow:
Service flow ID: 1
S-VLAN ID: 100
Customer VLAN (C-VLAN) ID: 100
Configuration of a COPS connection service flow:
Service flow ID: 2
VLAN (shared with the S-VLAN) ID: 100
C-VLAN ID: 1000

1527

Access Module
n
Device where upstream and downstream packet rates are limited: MA5633
In this case, use the default traffic profile with ID 6, which does not limit the
rate of a service flow. To limit packet rates, run the traffic table ip command
to create a traffic profile and bind it to the service flow.
C-VLAN and S-VLAN of the MA5633: same
huawei(config)#service-port 1 vlan 100 eth 0/3/0 multi-service

NOTE
l On IPv6 networks, run the dhcpv6-option permit-forwarding port 0/3/0 enable

command to enable DHCPv6 Option forwarding on a specified port.
l If CPEs support IPv6 prefixes, run the security bind-route-nd enable command to
enable associated routes and neighbor entries. Then, the OLT automatically generates the
routing and neighbor entries of a DHCPv6 user based on the user information recorded
when the user goes online. This prevents the need of manually configuring static routes
and sending neighbor discovery (ND) packets to the user side, thereby improving system
security.
b.
Configure the maximum number of dialup users allowed on a service port.

For functions (such as, MAC address spoofing, anti-IP spoofing, anti-IPv6
spoofing, DHCP Proxy, IP Aware, IPoE single-MAC, VMAC DHCP aging, NS
proxy response, ARP proxy response, DAD proxy, and DHCPv6 associated routes)
depending on dialup operations performed by DHCP, DHCPv6, PPPoE, and
SLAAC users, run this command to restrict the number of users allowed on each
service port.
huawei(config)#security user max-user-count service-port 1 2048
c.
Configure multicast cascading port 0/3/0.

huawei(config)#btv
d.
Configure the Internet Group Management Protocol (IGMP) version to IGMPv3.

e.
Configure the multicast uplink port to 0/5/0.

f.
Configure a multicast program generation mode.

For the MA5633, the multicast programs are dynamically generated.
g.
Configure the IGMP mode to IGMP proxy.

----End
Configuring RF Port Parameters on an MA5633 (DOCSIS 3.0)

Issue 01 (2016-04-29)

1528

Access Module
Data Plan
Item
Data
RF port
0/1/0
Upstream
channels
Downstream
channels

722.00
Procedure
l
Log in to and configure the ONU.

You can remote log in to the ONU from the OLT to perform the configuration. The user
name is root and the password is admin123.

a.

b.
channels.
Parameter
Description

51.8-58.2 MHz.
modulation-profile

The following configurations are used as an example to configure RF port

parameters:
Issue 01 (2016-04-29)

1529

Access Module

huawei(config-if-cable-0/1/0)#cable upstream
profile 23 enable
c.
1 frequency 29.8 modulation2 frequency 42.60

3 frequency 49.00
4 frequency 55.40

Parameter
Description
modulation

default setting.

downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Issue 01 (2016-04-29)

1530

Access Module
Configuring the HSI Service on a D-CCAP

Data Plan
Table 15-7 Data plan for the high-speed Internet (HSI) service
Item
Data
VLAN

VLAN: smart
Uplink port
0/0/1
Procedure
The S-VLAN is a user-side service VLAN between the optical line terminal (OLT) and the
distributed converged cable access platform (D-CCAP). The OLT works in Layer 3
forwarding mode.
Step 3 Create a cable modem (CM) S-VLAN.

----End
Configuring the DOCSIS VoD Service on an MA5633

Context
service.
Issue 01 (2016-04-29)

1531

Access Module
Data Plan
Item
Data
VLAN
Uplink port
0/0/1
Procedure
forwarding mode.

----End
Configuring the EQAM VoD Service on an MA5633

Prerequisites
Context
Issue 01 (2016-04-29)

1532

Access Module
Data Plan
Item
Data
EQAM IP address
10.10.10.10
VLAN
Uplink port

0/0/1
EQAM channel ID
13-16
Modulation mode
QAM 64
Symbol rate
6.875
UDP port number
501-514
Access port on the OLT
0/3/0
Uplink port on the OLT
0/5/0
Procedure
Step 2 Configure RF port parameters.
huawei(config-if-cable-0/1/0)#cable eqam-channel
modulation qam64 enable symbol-rate 6.875
13 frequency 698000000

Issue 01 (2016-04-29)


1533

Access Module
huawei(config-eqam-video-profile-vod1)#mapping
index 6 type spts udp-port 506

NOTE


udp-port 1
udp-port 1
udp-port 1
udp-port 1


----End
Result
transmitting.
l
Issue 01 (2016-04-29)
1534

Access Module
Follow-up Procedure
After configuring the MA5633, perform the following steps to configure a service channel on
the OLT.
1.
Configure an S-VLAN.
VLAN 50 is the S-VLAN that functions between the OLT and the MA5633. The OLT
works in Layer 3 forwarding mode.
OLT(config)#vlan 50 smart
OLT(config)#port vlan 50 0/5 0
2.

n
Service flow ID: 3
S-VLAN ID: 50
Device where upstream and downstream packet rates are limited: MA5633 (In this
case, use the default traffic profile with ID 6, which does not limit the rate of a
service flow. To limit packet rates, run the traffic table ip command to create a
traffic profile and bind it to the service flow.)
Configuration if the service is accessed using a GPON board:

OLT(config)#service-port 3 vlan 50 gpon 0/3/0 ont 1 gemport 1 multi-service
Configuration if the service is accessed using a GE board:

OLT(config)#service-port 3 vlan 50 eth 0/3/0 multi-service

Context
service.
Issue 01 (2016-04-29)

1535

Access Module
Data Plan
Item
Data
VLAN
Uplink ports
0/0/1
Procedure
forwarding mode.


NOTE



NOTE
Issue 01 (2016-04-29)

1536

Access Module


NOTE

authentication:
l
32
and 225.1.1.2

on permit

----End
Configuring the Dynamic PacketCable Service on a D-CCAP

Context
Table 15-11 Data plan for the PacketCable service
Item
Data
Uplink port
0/0/1
VLAN
ID of the PacketCable service VLAN (S-VLAN): 100; type of the

VLAN: smart
1000
Issue 01 (2016-04-29)

1537

Access Module
Item
Data
IP address for
creating a COPS
connection to an
IP multimedia
subsystem (IMS)
or a softswitch

Procedure
NOTE



connection

l
Issue 01 (2016-04-29)

1538

Access Module

----End
Verifying Services
To facilitate service verification, an MA5633 supports multiple remote service verification
this section describes how to verify services on site.
Prerequisites
l
The MA5633 is properly connected to the upper-layer network.
Procedure
l

In this test, a cable modem (CM) is emulated on the MA5633 to apply to the DHCP
server for an IP address. This checks whether the MA5633 can communicate with the
DHCP server and verifies CM DHCP configurations on the DHCP relay, proxy, and
server.
a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
0/1/0/U4
ol-pt
1
0
D2.0
-
Issue 01 (2016-04-29)

1539

Access Module
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1540

Access Module
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1541

Access Module
CM
Status
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

a.
programs.
b.
Internet from a PC.
c.
d.
----End
Issue 01 (2016-04-29)

1542

Access Module
15.2.2 L2VPN Enterprise Service Networking

In L2VPN enterprise service networking, an MA5633 connects to cable modems (CMs)
through radio frequency (RF) ports, and the CMs connect to switches to provide the L2VPN
service for users. This section describes how to configure the optical line terminal (OLT) and
the MA5633 to provision the L2VPN service.
NOTE
Configuration procedures are the same for IPv6 and IPv4 networks except in "onfigure Dynamic Host
Configuration Protocol (DHCP) rela" and "onfigure a route".

Usage Scenario
As shown in Figure 15-4, MA5633 is deployed on an optical node and cable modems (CMs)
are deployed at enterprises. The CMs connect to radio frequency (RF) ports on the MA5633
through cables.
l

users.
(DHCP) dialup.
Issue 01 (2016-04-29)

1543

Access Module
NOTE
connected.

Configuration
Object
Step
Optical line
terminal (OLT)
l IPv4: Configure Dynamic Host Configuration Protocol

(DHCP) relay.
l IPv6: Configure Dynamic Host Configuration Protocol
l IPv6: Configure a route (IPv6).
Configure a management channel between the OLT and the DCCAP.
Configure a service channel between the OLT and the D-CCAP.
MA5633
Configure radio frequency (RF) port parameters.

Issue 01 (2016-04-29)

1544

Access Module

Prerequisites
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

domain name: docsis
Item
IP Address
Layer 3 interfaces
the OLT

server

adapters (MTAs): 192.168.10.10-192.168.10.11
Procedure
//Set the IP
Issue 01 (2016-04-29)

1545

Access Module

//Configure DHCP

//Bind DHCP server
//Set the
----End
Configuring a Route
Prerequisites
Data Plan
Item
IP Address

packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT
the OLT

Issue 01 (2016-04-29)

1546

Access Module
Procedure
1.

2.

3.

a.
forwarded.
b.

devices.
//CM
2005.
//DHCP
NOTE
----End
Result
Issue 01 (2016-04-29)

1547

Access Module

Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
huawei(config)#ipv6
Issue 01 (2016-04-29)

1548

Access Module

RA messages.
//
//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.

//Bind DHCP

2001:0db8:0001::1/64
domain of CMs.
----End

Issue 01 (2016-04-29)

1549

Access Module
Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.
0/4/0 to VLAN 2004.

Issue 01 (2016-04-29)

1550

Access Module
2.

3.
//The packets
//The packets

a.
forwarded.
b.

2001:0db8:0008::7/64
//
NOTE
----End
Result

terminal (OLT) and an MA5633. After the configuration, you can log in to the MA5633 from
the OLT and configure the MA5633.
Prerequisites
Issue 01 (2016-04-29)

1551

Access Module
Data Plan
Item
Data
Remarks
OLT
GE port: 0/3/0
Management VLAN
and IP address of
the D-CCAP
VLAN: 8
l Do not enable both the remote

software commissioning using
PON upstream transmission and
the remote software
transmission.

VLAN: smart
192.168.50.2/24
Management profile
of the D-CCAP
ID: 64
l Ensure that the database of a

newly deployed D-CCAP is empty.
Otherwise, the remote software
transmission cannot be used.
l When the D-CCAP automatically
obtains management parameters, it
automatically generates a default
route that can be restored.
However, the default route may
not be proper in service
configuration. Therefore, you are
advised to add a new route and
delete the default one after the DCCAP management channel is
available.
l After the D-CCAP automatically
obtains management parameters,
the remote software
commissioning function is
automatically disabled if
configurations are issued to the DCCAP through the U2000. To
modify the D-CCAP management
parameters, remotely log in to the
D-CCAP through the command
line interface (CLI).
Procedure
Step 1 Configure a management channel between the OLT and the MA5633.
1.

2.
Enable Network Admission Control (NAC) on the OLT.

3.
Issue 01 (2016-04-29)

1552

Access Module
Perform this operation if the MA5633 is managed through the U2000. Plan an SNMP
management profile on the U2000 and MA5633 before creating the profile.
huawei(config)#snmp-profile add profile-id 64 profile-name snmp-profile_64
v2c public
4.
Configure MA5633 management parameters on the OLT.

huawei(config)#nac config master 0/3/0 slave vlan 8 priority 6 ip-address
Check whether the MA5633 management parameters have been configured on the OLT.
{ <cr>|frameid/slotid/portid<S><Length 1-255>|frameid/slotid<S><Length
1-15> }:
Command:
display nac configuration master
----------------------------------------------------------------------------Frame ID/Slot ID/Port ID : 0/3/0
VLAN
: 8
VLAN priority
: 3
IP address
: 192.168.50.2
Mask
: 255.255.255.0
Gateway
: 192.168.50.254
Snmp-profile-id
: 64
Snmp-profile-name
: snmp-profile_64
----------------------------------------------------------------------------Total: 1
Step 2 Check whether the management channel between the OLT and the MA5633 is available.
Upon power-on, the MA5633 exchanges data with the OLT to obtain the management
parameters.
l
Run the ping 192.168.50.2 command on the OLT to check whether the MA5633 can
(ICMP) ECHO-REPLY packets sent from the MA5633, the MA5633 is connected to the
OLT.
----End
Configuring a Service Channel Between an OLT and a D-CCAP

Data Plan
Item
Data
L2VPN enterprise service
ID of the OLT VLAN (transparently transmitting DCCAP packet tags): 200

ID of the D-CCAP VLAN: 200
Uplink ports
Port forwarding Dynamic Host Configuration

Protocol (DHCP) and broadband packets: 0/4/0
Port forwarding cable modem (CM) management
and VoD packets: 0/5/0
Issue 01 (2016-04-29)

1553

Access Module
Procedure
l
Configure a channel for the L2VPN enterprise service.

a.
Configure an L2VPN service VLAN (S-VLAN).

The following configurations are used as an example to configure an S-VLAN:
n
S-VLAN ID: 200
S-VLAN type: smart
ID of the VLAN containing uplink port 0/4/0: 200 (S-VLAN ID)

b.
Configure a service flow to receive and transparently transmit D-CCAP packets.

n
Service flow ID: 1
S-VLAN ID: 200
Device where upstream and downstream packet rates are limited: D-CCAP
C-VLAN and S-VLAN of the D-CCAP: same

c.

service port.
Configure a CM management channel.

a.

n
Service flow ID: 2
S-VLAN ID: 100
C-VLAN ID: 100
Issue 01 (2016-04-29)

1554

Access Module

b.

NOTE

security.
----End
Configuring RF Port Parameters on an MA5633

Data Plan
Item
Data
RF port
0/1/0
Upstream
channels
Downstream
channels

722.00
Procedure
l


a.

b.
Issue 01 (2016-04-29)
channels.
1555

Access Module
Parameter
Description

51.8-58.2 MHz.
modulation-profile


parameters:
n

profile 23 enable
c.

3 frequency 49.00
4 frequency 55.40

Parameter
Description
modulation

default setting.

huawei(config-if-cable-0/1/0)#cable downstream 1 frequency 602.00 enable
Issue 01 (2016-04-29)

1556

Access Module
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Configuring the L2VPN Enterprise Service(on the CMC)

Context
l
S-VLAN. Then, run the cable service-vlan command to make the CM go online. The
L2VPN S-VLAN is specified in the CM configuration file. When the CM goes online,
the system obtains the L2VPN S-VLAN from the CM configuration file and

Issue 01 (2016-04-29)

1557

Access Module
Data Plan
Item
Data
VLAN
Uplink port
0/0/1
Procedure
Step 2 Configure a CM management S-VLAN.
The ID of the CM management S-VLAN is 100 and the type of the VLAN is smart.
//The CM S-VLAN identifies a CM service
flow. After the CM S-VLAN is configured, the D-CCAP automatically creates a
service flow when the CM goes online.
l
commands:
----End
Verifying Services
A distributed converged cable access platform (D-CCAP) locates on an optical node when the
D-CCAP functions as a standalone NE. To facilitate service verification, the D-CCAP
supports multiple remote service verification methods, such as Dynamic Host Configuration
Protocol (DHCP) dialup emulation tests. This allows commissioning and configuration
engineers to remotely verify services. In addition, this section describes how to verify the
L2VPN service on site.
Issue 01 (2016-04-29)

1558

Access Module
Prerequisites
l
The D-CCAP is properly connected to the upper-layer network.
Procedure
l

server.
a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.

Issue 01 (2016-04-29)

1559

Access Module
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1560

Access Module
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1561

Access Module
CM
Status
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

----End

In wireless local area network (WLAN) hotspot radio backhaul service networking, an
MA5633 connects to cable modems (CMs) through radio frequency (RF) ports. A CM
connects to wireless access points (APs) to provide wireless fidelity (Wi-Fi) access for users.
Issue 01 (2016-04-29)

1562

Access Module
Usage Scenario
(CMs) are deployed at shops. The CMs connect to radio frequency (RF) ports on the MA5633
through cables.
l
dialup.
Configuration
The method of configuring the wireless local area network (WLAN) hotspot radio backhaul
service is the same as that of configuring the L2VPN enterprise service and therefore is not
described in this section. For details, see Configuration Process.
15.3 Configuring Services on a D-CCAP ()

service, and wireless local area network (WLAN) hotspot radio backhaul service, on a
distributed converged cable access platform (D-CCAP) that works in access mode on a Layer
3 network. The MA5603T equipped with the SCUV, GPBH, and SPUF boards is used as an
example.
Issue 01 (2016-04-29)
Control Board
SCUV
Service Board
GPMD: 0/3

1563

Access Module
SPU Board
SPUF: 0/4, 0/5
15.3.1 Home Service Networking

In home service networking, an MA5633 connects to cable modems (CMs) at user homes
through radio frequency (RF) ports and provides home services for users, including the cable
TV (CATV) service, Internet access service, VoD service, broadband TV (BTV) service, and
PacketCable service. This section describes how to configure the optical line terminal (OLT)
and the MA5633 to provision the home services.
NOTE

Usage Scenario
As shown in Figure 15-7, MA5633 is deployed on an optical node and cable modems (CMs)
are deployed at user homes. The CMs connect to radio frequency (RF) ports on the MA5633
through cables.
l

Issue 01 (2016-04-29)

1564

Access Module
Issue 01 (2016-04-29)

1565

Access Module
NOTE
connected.

Configur
ation
Object
Step
Description
Optical
line
terminal
(OLT)
l IPv4: Configure Dynamic Host

Configuration Protocol (DHCP)
relay.
This section describes how to

configure Dynamic Host
relay so that cable modems (CMs)
network segments.
l IPv6: Configure Dynamic Host

relay (IPv6).
l IPv6: Configure a route (IPv6).
Issue 01 (2016-04-29)

implement network communication
by configuring a route in Layer 3
networking with an optical line
terminal (OLT). Through the route,
packets are forwarded at Layer 3
between the OLT and its upperlayer devices or servers.
Add a D-CCAP to the OLT.
You can configure a distributed

converged cable access platform
(D-CCAP) only after adding it to an
Configure a management channel

between the OLT and the D-CCAP.

configure a management channel
between an optical line terminal
(OLT) and a distributed converged
cable access platform (D-CCAP).
After the configuration, you can log
in to the D-CCAP from the OLT
and configure the D-CCAP.

between the OLT and the D-CCAP.

configure a service channel between
an optical line terminal (OLT) and
an MA5633. After the
configuration, the service channel
forwards service packets on the
MA5633 based on the planned
VLAN and forwarding policy.

1566

Access Module
Configur
ation
Object
Step
Description
MA5633

port parameters.
Radio frequency (RF) port

parameters define the frequency
spectrum range for signal
transmission and modulation mode.
The configuration of RF port
parameters implements data service
transmission over cables.
Configure the high-speed Internet

(HSI) service.
None
None
Configure the broadband TV (BTV)

service.
None
Configure the dynamic PacketCable

service.
None
A D-CCAP supports multiple

remote service verification
methods. This allows
engineers to remotely verify
services.
1. A DHCP dialup emulation test
checks whether the D-CCAP can
communicate with the DHCP
server and verifies CM DHCP
configurations on the DHCP
2. The status of a CM can be
queried. Based on the
information, you can determine
whether the CM is online.

Prerequisites
Issue 01 (2016-04-29)

1567

Access Module
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

Item
IP Address
Layer 3 interfaces
the OLT
servers

192.168.10.10-192.168.10.11

11.11.12.11

192.168.10.12-192.168.10.13
server
192.168.5.10-192.168.5.13
Procedure
docsis
pktc
stb
default
Issue 01 (2016-04-29)

1568

Access Module
default


//Configure DHCP
//Configure DHCP

PCs.
//Paid and
//Bind DHCP
//Bind DHCP server
//Bind DHCP server
//Bind DHCP server

10.100.8.1
//Set the
//Set the IP
//Set the IP
Issue 01 (2016-04-29)

1569

Access Module

----End
Configuring a Route
Prerequisites
Data Plan
Item
IP Address

broadband packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
Forwarding cable modem (CM) management, VoD, COPS, and
multicast packets:
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT

l Forwarding CM management, VoD, COPS, and multicast
packets: 11.11.12.11
l COPS gateway IP address: 192.168.60.1
the OLT
l DHCP servers:
boxes (STBs): 192.168.10.12-192.168.10.13
192.168.20.10-192.168.20.12
192.168.50.10
Issue 01 (2016-04-29)

1570

Access Module
Procedure
1.

2.

3.

a.
b.
devices.
//Broadband
//CM
//DHCP
NOTE
l The interconnected router must set static routes and add the routes to dynamic routes.
----End
Result
Issue 01 (2016-04-29)

1571

Access Module

Prerequisites
The upper-layer router, DHCP server server of an OLT have been configured.
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Issue 01 (2016-04-29)

1572

Access Module
Configuration Item
Data
Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
huawei(config)#ipv6
RA messages.
//
//Configure the
//Configure the
//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.
Issue 01 (2016-04-29)

1573

Access Module

2001:0db8:0006::11/64
for PCs.

//PCs require
/Bind DHCP
//Bind DHCP

2001:0db8:0004::4/64
2001:0db8:0001::1/64
domain of CMs.
----End

Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM

2001:0db8:0003::/64
Issue 01 (2016-04-29)

1574

Access Module
Configuration Item
Data
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.

2.

Issue 01 (2016-04-29)

1575

Access Module

3.
//The packets
//The packets

a.
b.

//Broadband
2001:0db8:0008::7/64
//
NOTE
----End
Result
Adding a D-CCAP to an OLT

You can configure a distributed converged cable access platform (D-CCAP) only after adding
it to an optical line terminal (OLT).
Prerequisites
Context
l
Issue 01 (2016-04-29)
When adding a D-CCAP to an OLT, bind the following profiles to the D-CCAP:
dynamic bandwidth allocation (DBA) profile, line profile, and alarm profile. For details
about the functions and configuration method of each profile, see Table 15-24.
1576

Access Module
Table 15-24 D-CCAP profiles

Profile
Function
Command
DBA
profile

parameters. A transmission
container (T-CONT) is bound
to a DBA profile for dynamic
bandwidth allocation. This
improves the upstream
bandwidth usage.
Command for querying a DBA profile:

display dba-profile
Describes the binding between

a T-CONT and a DBA profile,
quality of service (QoS) mode
of a service flow, and mapping
from a GEM port to D-CCAP
services.
Command for querying a line profile:

display ont-lineprofile
Contains a series of alarm

thresholds for measuring and
monitoring the performance of
activated D-CCAP lines.
Command for querying an alarm

profile: display gpon alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)
Command for adding a DBA profile:

dba-profile add
Command for adding a line profile:

ont-lineprofile
Command for adding an alarm profile:

gpon alarm-profile add
Add a D-CCAP using either of the methods listed in the following table based on site
requirements.
Method
Usage Scenario
Command
Add a DCCAP in
offline
mode.
You have obtained the

password or serial number (SN)
of the D-CCAP.

D-CCAP to an OLT.
Add an
online DCCAP
and
confirm
the
automatic
ally
discovere
d DCCAP.
You do not know the password

or SN of the D-CCAP.
In GPON mode, run the port ont-autofind command to enable the D-CCAP
automatic discovery function on GPON
ports. Then run the ont confirm
command to add the D-CCAP.

1577

Access Module
Data Plan
Item
Data
DBA profile
Profile name: PrivateLine

Type: type4
Line profile
Profile ID: 10, bound to DBA profile PrivateLine

GPON encapsulation mode (GEM) port IDs: 0 and 1
T-CONT ID: 5
Networking data
Port: 0/3/1
D-CCAP ID: 1
D-CCAP authentication mode: SN
D-CCAP SN: 48575443E6D8B541
Management VLAN: 8
Service VLAN: 100
Common open policy service (COPS) connection
VLAN: 1000
Procedure
Step 1 Configure D-CCAP profiles.
D-CCAP profiles include a DBA profile, a line profile, and an alarm profile.
1.

Run the display dba-profile command to query DBA profiles existing in the system. If
the existingDBA profiles do not meet service requirements, run the dba-profile add
command to add a DBA profile.
huawei(config)#dba-profile add profile-name PrivateLine type4 max 1000000
2.
Configure a line profile.

Add line profile 10 and bind T-CONT 5 to DBA profile PrivateLine. In this way, the TCONT provides flexible DBA solutions based on the configurations in the DBA profile.
huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name PrivateLine
The following configurations are used as an example to add a line profile:
Issue 01 (2016-04-29)
Index of the GEM port for carrying management service flows: 0
Index of the GEM port for carrying high-speed Internet (HSI) and VoD service
flows: 1
ID of the T-CONT that GEM ports 0 and 1 are bound: 5
QoS mode: priority-queue (default)
Queue priority of GEM ports 0 and 1: 3, 1

1578

Access Module
NOTE
When the QoS mode is PQ, the default queue priority is 0.
huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 5 priority-queue 3

l
Mode of the mapping from the GEM port to D-CCAP services: VLAN (default)
Index of the GEM port to which the management service flows in VLAN 8 are mapped:
0
Index of the GEM port to which the service flows in VLAN 100 are mapped: 1
Index of the GEM port to which the service flows in COPS connection VLAN 1000 are
mapped: 2
huawei(config-gpon-lineprofile-10)#mapping-mode vlan
Run the commit command to make the configured parameters take effect.

l
The ID of the default GPON alarm profile is 1. In this profile, the thresholds for all alarm
parameters in the default alarm profile are 0, which indicates that no alarm is generated.
This section uses the default alarm profile and therefore the alarm profile does not need
to be configured.
To add an alarm profile for monitoring the performance of activated D-CCAP lines, run
the gpon alarm-profile add command.
Step 2 Add a D-CCAP to an OLT.

The D-CCAP connects to a GPON port on the OLT through an optical fiber. You can
configure the D-CCAP only after adding it to the OLT.
1.
Add a D-CCAP.
The following configurations are used as an example to add a D-CCAP: The
management mode is SNMP; the ID of the line profile bound to the D-CCAP is 10.
To add a D-CTMS in offline mode, do as follows:
huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ontlineprofile-id
10 desc MA5633_0/3/1/1_lineprofile10
To automatically find a D-CCAP, do as follows:

//This command displays the information about all automatically discovered
D-CCAPs that are connected to the GPON port through an optical splitter.
-----------------------------------------------------------Number
: 1
F/S/P
: 0/3/1
Ont SN
: 48575443E6D8B541
Password
: 0x30303030303030303030(0000000000)
Loid
: 000000000000000000000000
Checkcode
: 000000000000
VendorID
: HWTC
Issue 01 (2016-04-29)

1579

Access Module
Ont Version
: MA5633 VER.A
Ont SoftwareVersion : V8R313 C10
Ont EquipmentID
: 5633
Ont autofind time
: 2013-09-25 20:42:45+08:00
-----------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541
snmp ont-lineprofile-id
NOTE
If multiple D-CCAPs of the same type are connected to a port and the same line or service profile is
bound to the D-CCAPs, add these D-CCAPs in batches by confirming the automatically discovered DCCAPs in batches. This simplifies operations and improves configuration efficiency. To do so, change
the preceding command huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth
48575443E6D8B541 snmp ont-lineprofile-id 10 desc MA5633_0/3/1/1_lineprofile10 to
huawei(config-if-gpon-0/3)#ont confirm 1 all sn-auth snmp ont-lineprofile-id 10 desc
MA5633_0/3/1_lineprofile10.
----End
Result
The D-CCAP is online.
After adding the D-CCAP, run the display ont info command to query the D-CCAP status.
Ensure that Control flag is active, Run State is online, and Config state is normal.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
//The D-CCAP has been activated.
Run state
: online
//The D-CCAP has been online.
Config state
: normal
//The D-CCAP has been configured.
...//The following terminal display is omitted.
Follow-up Procedure
If the D-CCAP malfunctions, follow the troubleshooting suggestions listed in the following
table to rectify faults.
Issue 01 (2016-04-29)
D-CCAP Status
The Control flag of the DCCAP is deactivated.
In GPON port mode, run the ont activate command to

activate the D-CCAP.
The D-CCAP is offline (Run

state displayed as offline).
The physical line may be disconnected, or the optical

module may be damaged. Rectify the fault by checking
line connection and the hardware.
The D-CCAP fails to be

configured (Config state
displayed as failed)
The possible cause is that the D-CCAP cannot support the

configured D-CCAP capability set. In this case, run the
display ont failed-configuration command to query the
failed configuration items and failure causes. Then rectify

1580

Access Module
Configuring a Management Channel Between an OLT and a D-CCAP

terminal (OLT) and a distributed converged cable access platform (D-CCAP). After the
configuration, you can log in to the D-CCAP from the OLT and configure the D-CCAP.
Data Plan
Item
Data
Remarks
Management VLAN
and IP address of
the OLT
VLAN: 8
To remotely log in to the D-CCAP

from the OLT for configuration,
ensure that the management VLAN of
the OLT is the same as that of the DCCAP and that the management IP
address of the OLT is in the same
network segment as that of the DCCAP.

VLAN: smart
192.168.50.1/24
Management VLAN
and IP address of
the D-CCAP
VLAN: 8
VLAN: smart
192.168.50.2/24
Procedure
Step 1 Configure a management channel between the OLT and the D-CCAP.
NOTE
Perform this operation only when the OLT remotely manages the D-CCAP through SNMP.
1.
Set the inband management VLAN and IP address of the OLT.

To remotely log in to the D-CCAP for configuration, set the inband management VLANs
and IP addresses of the OLT and the D-CCAP on the OLT.
2.
Set the inband management VLAN and IP address of the D-CCAP.

Set the static IP address of the D-CCAP to 192.168.50.2/24, the IP address of the
gateway to 192.168.50.1, and the ID of the management VLAN to 8 (the same as the
management VLAN of the OLT).
huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2
mask 255.255.255.0 gateway
192.168.50.1 vlan 8
3.
Configure an inband management service flow.

The following configurations are used as an example to configure an inband
management service flow:
Issue 01 (2016-04-29)

1581

Access Module
Configuration of the service flow:

n
ID of the management service flow: 0
ID of the GPON encapsulation mode (GEM) port: 0
ID of the customer VLAN (C-VLAN): 8
In this case, use the default traffic profile with ID 6, which does not limit the rate of
a service flow. To limit packet rates, run the traffic table ip command to create a
traffic profile and bind it to the service flow.

NOTE
l On IPv6 networks, run the dhcpv6-option permit-forwarding port 0/3/0 enable command to
enable DHCPv6 Option forwarding on a specified port.
l If CPEs support IPv6 prefixes, run the security bind-route-nd enable command to enable
associated routes and neighbor entries. Then, the OLT automatically generates the routing and
neighbor entries of a DHCPv6 user based on the user information recorded when the user goes
online. This prevents the need of manually configuring static routes and sending neighbor discovery
(ND) packets to the user side, thereby improving system security.
Step 2 Check whether the management channel between the OLT and the D-CCAP is available.
l
Run the ping 192.168.50.1 command on the OLT to check whether the D-CCAP can
(ICMP) ECHO-REPLY packets sent from the D-CCAP, the D-CCAP is connected to the
OLT.
----End

Data Plan
Item
Data
High-speed Internet (HSI), VoD,

broadband TV (BTV), or dynamic
PacketCable service

ID of the common open policy service (COPS)
connection VLAN: 1000
Procedure
l
Configure a channel for a home service.

a.
Configure service flows to receive and transparently transmit D-CCAP packets.

Issue 01 (2016-04-29)

1582

Access Module
n
Service flow ID: 1
S-VLAN ID: 100
Configuration of a COPS connection service flow:
Service flow ID: 2
VLAN (shared with the S-VLAN) ID: 100
C-VLAN ID: 1000

NOTE

security.
b.

service port.
c.
Configure multicast cascading port 0/3/1.

huawei(config)#btv
d.
Configure the Internet Group Management Protocol (IGMP) version to IGMPv3.

e.
Configure the multicast uplink port to 0/5/0.

f.
Configure a multicast program generation mode.

For the MA5633, the multicast programs are dynamically generated.
Issue 01 (2016-04-29)

1583

Access Module

g.
Configure the IGMP mode to IGMP proxy.

----End

Data Plan
Item
Data
RF port
0/1/0
Upstream
channels
Downstream
channels

722.00
Procedure
l


a.

b.
Issue 01 (2016-04-29)
channels.

1584

Access Module
Parameter
Description

51.8-58.2 MHz.
modulation-profile


parameters:
n

profile 23 enable
c.

3 frequency 49.00
4 frequency 55.40

Parameter
Description
modulation

default setting.

Issue 01 (2016-04-29)

1585

Access Module
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream

----End
Result
1.

2.
dB.
Configuring the HSI Service on an MA5633

Data Plan
Table 15-27 Data plan for the high-speed Internet (HSI) service
Item
Data
VLAN

VLAN: smart
Uplink port
0/0/1
Procedure
forwarding mode.
Issue 01 (2016-04-29)

1586

Access Module


----End
Configuring the DOCSIS VoD Service on an MA5633

Context
service.
Data Plan
Item
Data
VLAN
Uplink port
0/0/1
Procedure
forwarding mode.

Issue 01 (2016-04-29)

1587

Access Module

----End
Configuring the EQAM VoD Service on an MA5633

Prerequisites
Context
Data Plan
Item
Data
EQAM IP address
10.10.10.10
VLAN
Uplink port

0/0/1
EQAM channel ID
13-16
Modulation mode
QAM 64
Symbol rate
6.875
UDP port number
501-514
Access port on the OLT
0/3/0
Uplink port on the OLT
0/5/0
Procedure
Issue 01 (2016-04-29)

1588

Access Module
Step 2 Configure RF port parameters.


NOTE

Issue 01 (2016-04-29)


udp-port 1
udp-port 1
udp-port 1
udp-port 1
1589

Access Module


----End
Result
transmitting.
l
Follow-up Procedure
After configuring the MA5633, perform the following steps to configure a service channel on
the OLT.
1.
Configure an S-VLAN.
VLAN 50 is the S-VLAN that functions between the OLT and the MA5633. The OLT
works in Layer 3 forwarding mode.
OLT(config)#vlan 50 smart
OLT(config)#port vlan 50 0/5 0
2.
Issue 01 (2016-04-29)

n
Service flow ID: 3
S-VLAN ID: 50
Device where upstream and downstream packet rates are limited: MA5633 (In this
case, use the default traffic profile with ID 6, which does not limit the rate of a
1590

Access Module
service flow. To limit packet rates, run the traffic table ip command to create a
traffic profile and bind it to the service flow.)
Configuration if the service is accessed using a GPON board:
OLT(config)#service-port 3 vlan 50 gpon 0/3/0 ont 1 gemport 1 multi-service
Configuration if the service is accessed using a GE board:

OLT(config)#service-port 3 vlan 50 eth 0/3/0 multi-service
Configuring the BTV Service on an MA5633

Context
service.
Data Plan
Item
Data
VLAN
Uplink ports
0/0/1
Procedure
forwarding mode.

Issue 01 (2016-04-29)

1591

Access Module

NOTE



NOTE


NOTE

authentication:
l
32
and 225.1.1.2

on permit

Issue 01 (2016-04-29)

1592

Access Module
----End
Configuring the Dynamic PacketCable Service on an MA5633

Context
Table 15-31 Data plan for the PacketCable service
Item
Data
Uplink port
0/0/1
VLAN
ID of the PacketCable service VLAN (S-VLAN): 100; type of the

VLAN: smart
1000
IP address for
creating a COPS
connection to an
IP multimedia
subsystem (IMS)
or a softswitch

Procedure
NOTE

Issue 01 (2016-04-29)

1593

Access Module


connection

l

----End
Verifying Services
To facilitate service verification, an MA5633 supports multiple remote service verification
this section describes how to verify services on site.
Prerequisites
l
The MA5633 is properly connected to the upper-layer network.
Procedure
l

server.
a.

NOTE
Issue 01 (2016-04-29)

1594

Access Module
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
0/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.
DHCP



1595

Access Module
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1596

Access Module
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1597

Access Module
CM
Status
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

a.
programs.
b.
Internet from a PC.
c.
d.
----End
Issue 01 (2016-04-29)

1598

Access Module
15.3.2 L2VPN Enterprise Service Networking

In L2VPN enterprise service networking, an MA5633 connects to cable modems (CMs)
through radio frequency (RF) ports, and the CMs connect to switches to provide the L2VPN
service for users. This section describes how to configure the optical line terminal (OLT) and
the MA5633 to provision the L2VPN service.
NOTE
Configuration procedures are the same for IPv6 and IPv4 networks except in "onfigure Dynamic Host
Configuration Protocol (DHCP) rela" and "onfigure a route".

Usage Scenario
l

users.
(DHCP) dialup.
Issue 01 (2016-04-29)

1599

Access Module
NOTE
connected.

Config
uration
Object
Step
Description
OLT

(DHCP) relay.

network segments.

(IPv6).
Add a D-CCAP to the OLT.
Issue 01 (2016-04-29)

servers.
You can configure a distributed converged
cable access platform (D-CCAP) only after
adding it to an optical line terminal (OLT).

1600

Access Module
Config
uration
Object
MA563
3
Step
Description
the D-CCAP.

management channel between an optical
line terminal (OLT) and a distributed
converged cable access platform (DCCAP). After the configuration, you can
log in to the D-CCAP from the OLT and
configure the D-CCAP.

between the OLT and the DCCAP.

service channel between an optical line
terminal (OLT) and an MA5633. After the
configuration, the service channel forwards
service packets on the MA5633 based on
the planned VLAN and forwarding policy.

port parameters.

cables.
None
A D-CCAP supports multiple remote

service verification methods. This allows
whether the D-CCAP can communicate
with the DHCP server and verifies CM

Prerequisites
Issue 01 (2016-04-29)

1601

Access Module
Data Plan
Item
Data
VLAN

smart
DHCP server group

parameters

domain name: docsis
Item
IP Address
Layer 3 interfaces
the OLT

server

adapters (MTAs): 192.168.10.10-192.168.10.11
Procedure
//Set the IP

//Configure DHCP

//Bind DHCP server
Issue 01 (2016-04-29)

1602

Access Module
//Set the
----End
Configuring a Route
Prerequisites
Data Plan
Item
IP Address

packets:
l VLAN ID: 2004
l IP address: 11.11.11.10/24
l VLAN ID: 2005
l IP address: 11.11.12.10/24
Layer 3 interfaces
the OLT
the OLT

Procedure
1.
Issue 01 (2016-04-29)
1603

Access Module

2.

3.

a.
forwarded.
b.

devices.
//CM
2005.
//DHCP
NOTE
----End
Result

Issue 01 (2016-04-29)

1604

Access Module
Prerequisites
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
huawei(config)#ipv6
RA messages.
//
Issue 01 (2016-04-29)

1605

Access Module

//Configure the
make a response.
types.

2001:0db8:0006::9/64
for CMs.

//Bind DHCP

2001:0db8:0001::1/64
domain of CMs.
----End

Prerequisites
Issue 01 (2016-04-29)

1606

Access Module
Data Plan
Configuration Item
Data
Terminal-side of CM
User-side of OLT

Network-side of OLT

l VLAN ID: 2004
l IP address: 2001:0db8:0007::12/64
VoD packets:
l VLAN ID: 2005
l IP address: 2001:0db8:0008::13/64
Router

Server

2001:0db8:0006::8/64-2001:0db8:0006::9/64
2001:0db8:0006::10/64-2001:0db8:0006::11/64
2001:0db8:0011::14/64-2001:0db8:0011::16/64
Procedure
1.
0/4/0 to VLAN 2004.

2.
Issue 01 (2016-04-29)

1607

Access Module
3.
//The packets
//The packets

a.
forwarded.
b.

2001:0db8:0008::7/64
//
NOTE
----End
Result
Adding a D-CCAP to an OLT

You can configure a distributed converged cable access platform (D-CCAP) only after adding
it to an optical line terminal (OLT).
Prerequisites
Issue 01 (2016-04-29)

1608

Access Module
Context
l
When adding a D-CCAP to an OLT, bind the following profiles to the D-CCAP:
dynamic bandwidth allocation (DBA) profile, line profile, and alarm profile. For details
about the functions and configuration method of each profile, see Table 15-37.
Table 15-37 D-CCAP profiles
Profile
Function
Command
DBA
profile

parameters. A transmission
container (T-CONT) is bound
to a DBA profile for dynamic
bandwidth allocation. This
improves the upstream
bandwidth usage.
Command for querying a DBA profile:

display dba-profile
Describes the binding between

a T-CONT and a DBA profile,
quality of service (QoS) mode
of a service flow, and mapping
from a GEM port to D-CCAP
services.
Command for querying a line profile:

display ont-lineprofile
Contains a series of alarm

thresholds for measuring and
monitoring the performance of
activated D-CCAP lines.
Command for querying an alarm

profile: display gpon alarm-profile
Line
profile
Alarm
profile
Issue 01 (2016-04-29)
Command for adding a DBA profile:

dba-profile add
Command for adding a line profile:

ont-lineprofile
Command for adding an alarm profile:

gpon alarm-profile add
Add a D-CCAP using either of the methods listed in the following table based on site
requirements.
Method
Usage Scenario
Command
Add a DCCAP in
offline
mode.
You have obtained the

password or serial number (SN)
of the D-CCAP.

D-CCAP to an OLT.
Add an
online DCCAP
and
confirm
the
automatic
ally
discovere
d DCCAP.
You do not know the password

or SN of the D-CCAP.
In GPON mode, run the port ont-autofind command to enable the D-CCAP
automatic discovery function on GPON
ports. Then run the ont confirm
command to add the D-CCAP.

1609

Access Module
Data Plan
Item
Data
DBA profile

Type: type4
Line profile
Profile ID: 10, bound to DBA profile PrivateLine

GPON encapsulation mode (GEM) port IDs: 0 and 1
T-CONT ID: 5
Networking data
Port: 0/3/1
D-CCAP ID: 1
D-CCAP authentication mode: SN
D-CCAP SN: 48575443E6D8B541
Management VLAN: 8
Service VLAN: 200
Procedure
Step 1 Configure D-CCAP profiles.
D-CCAP profiles include a DBA profile, a line profile, and an alarm profile.
1.

Run the display dba-profile command to query DBA profiles existing in the system. If
the existingDBA profiles do not meet service requirements, run the dba-profile add
huawei(config)#dba-profile add profile-name PrivateLine type4 max 1000000
2.
Configure a line profile.

Add line profile 10 and bind T-CONT 5 to DBA profile PrivateLine. In this way, the TCONT provides flexible DBA solutions based on the configurations in the DBA profile.
The following configurations are used as an example to add a line profile:
Index of the GEM port for carrying management service flows: 0
Index of the GEM port for carrying L2VPN service flows: 1
ID of the T-CONT that GEM ports 0 and 1 are bound: 5
QoS mode: priority-queue (default)
Queue priority of GEM ports 0 and 1: 3, 1

NOTE
When the QoS mode is PQ, the default queue priority is 0.

Issue 01 (2016-04-29)

1610

Access Module

l
Mode of the mapping from the GEM port to D-CCAP services: VLAN (default)
Index of the GEM port to which the management service flows in VLAN 8 are mapped:
0
Index of the GEM port to which the service flows in VLAN 200 are mapped: 1
Run the commit command to make the configured parameters take effect.

l
The ID of the default GPON alarm profile is 1. In this profile, the thresholds for all alarm
parameters in the default alarm profile are 0, which indicates that no alarm is generated.
This section uses the default alarm profile and therefore the alarm profile does not need
to be configured.
To add an alarm profile for monitoring the performance of activated D-CCAP lines, run
the gpon alarm-profile add command.
Step 2 Add a D-CCAP to an OLT.

The D-CCAP connects to a GPON port on the OLT through an optical fiber. You can
configure the D-CCAP only after adding it to the OLT.
1.
Add a D-CCAP.
The following configurations are used as an example to add a D-CCAP: The
management mode is SNMP; the ID of the line profile bound to the D-CCAP is 10.
To add a D-CTMS in offline mode, do as follows:
To automatically find a D-CCAP, do as follows:

//This command displays the information about all automatically discovered
D-CCAPs that are connected to the GPON port through an optical splitter.
-----------------------------------------------------------Number
: 1
F/S/P
: 0/3/1
Ont SN
: 48575443E6D8B541
Password
: 0x30303030303030303030(0000000000)
Loid
: 000000000000000000000000
Checkcode
: 000000000000
VendorID
: HWTC
Ont Version
: MA5633 VER.A
Ont SoftwareVersion : V8R313 C10
Ont EquipmentID
: 5633
Ont autofind time
: 2013-09-25 20:42:45+08:00
-----------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541
snmp ont-lineprofile-id
Issue 01 (2016-04-29)

1611

Access Module
NOTE
If multiple D-CCAPs of the same type are connected to a port and the same line or service profile is
bound to the D-CCAPs, add these D-CCAPs in batches by confirming the automatically discovered DCCAPs in batches. This simplifies operations and improves configuration efficiency. To do so, change
the preceding command huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth
48575443E6D8B541 snmp ont-lineprofile-id 10 desc MA5633_0/3/1/1_lineprofile10 to
----End
Result
The D-CCAP is online.
After adding the D-CCAP, run the display ont info command to query the D-CCAP status.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
//The D-CCAP has been activated.
Run state
: online
//The D-CCAP has been online.
Config state
: normal
//The D-CCAP has been configured.
...//The following terminal display is omitted.
Follow-up Procedure
If the D-CCAP malfunctions, follow the troubleshooting suggestions listed in the following
table to rectify faults.
D-CCAP Status
The Control flag of the DCCAP is deactivated.
In GPON port mode, run the ont activate command to

activate the D-CCAP.
The D-CCAP is offline (Run

state displayed as offline).
The physical line may be disconnected, or the optical

module may be damaged. Rectify the fault by checking
line connection and the hardware.
The D-CCAP fails to be

configured (Config state
displayed as failed)
The possible cause is that the D-CCAP cannot support the

configured D-CCAP capability set. In this case, run the
display ont failed-configuration command to query the
failed configuration items and failure causes. Then rectify

terminal (OLT) and a distributed converged cable access platform (D-CCAP). After the
configuration, you can log in to the D-CCAP from the OLT and configure the D-CCAP.
Issue 01 (2016-04-29)

1612

Access Module
Data Plan
Item
Data
Remarks
Management VLAN
and IP address of
the OLT
VLAN: 8
To remotely log in to the D-CCAP

from the OLT for configuration,
ensure that the management VLAN of
the OLT is the same as that of the DCCAP and that the management IP
address of the OLT is in the same
network segment as that of the DCCAP.

VLAN: smart
192.168.50.1/24
Management VLAN
and IP address of
the D-CCAP
VLAN: 8
VLAN: smart
192.168.50.2/24
Procedure
Step 1 Configure a management channel between the OLT and the D-CCAP.
NOTE
Perform this operation only when the OLT remotely manages the D-CCAP through SNMP.
1.
Set the inband management VLAN and IP address of the OLT.

To remotely log in to the D-CCAP for configuration, set the inband management VLANs
and IP addresses of the OLT and the D-CCAP on the OLT.
2.
Set the inband management VLAN and IP address of the D-CCAP.

Set the static IP address of the D-CCAP to 192.168.50.2/24, the IP address of the
gateway to 192.168.50.1, and the ID of the management VLAN to 8 (the same as the
management VLAN of the OLT).
huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2
mask 255.255.255.0 gateway
192.168.50.1 vlan 8
3.
Configure an inband management service flow.

The following configurations are used as an example to configure an inband
management service flow:
Issue 01 (2016-04-29)

n
ID of the management service flow: 0
ID of the GPON encapsulation mode (GEM) port: 0
ID of the customer VLAN (C-VLAN): 8

1613

Access Module
In this case, use the default traffic profile with ID 6, which does not limit the rate of
a service flow. To limit packet rates, run the traffic table ip command to create a
traffic profile and bind it to the service flow.

NOTE
l On IPv6 networks, run the dhcpv6-option permit-forwarding port 0/3/0 enable command to
enable DHCPv6 Option forwarding on a specified port.
l If CPEs support IPv6 prefixes, run the security bind-route-nd enable command to enable
associated routes and neighbor entries. Then, the OLT automatically generates the routing and
neighbor entries of a DHCPv6 user based on the user information recorded when the user goes
online. This prevents the need of manually configuring static routes and sending neighbor discovery
(ND) packets to the user side, thereby improving system security.
Step 2 Check whether the management channel between the OLT and the D-CCAP is available.
l
Run the ping 192.168.50.1 command on the OLT to check whether the D-CCAP can
(ICMP) ECHO-REPLY packets sent from the D-CCAP, the D-CCAP is connected to the
OLT.
----End

Data Plan
Item
Data
L2VPN enterprise service

Uplink ports
Port forwarding Dynamic Host Configuration

Protocol (DHCP) and broadband packets: 0/4/0
Port forwarding cable modem (CM) management
and VoD packets: 0/5/0
Procedure
l
Configure a channel for the L2VPN enterprise service.

a.
Configure an L2VPN service VLAN (S-VLAN).

The following configurations are used as an example to configure an S-VLAN:
Issue 01 (2016-04-29)
S-VLAN ID: 200
S-VLAN type: smart
ID of the VLAN containing uplink port 0/4/0: 200 (S-VLAN ID)

1614

Access Module

b.

The following configurations are used as an example to configure a service flow:
n
Service flow ID: 1
S-VLAN ID: 200

c.

service port.
Configure a CM management channel.

a.

n
S-VLAN ID: 100
C-VLAN ID: 100

NOTE

security.
Issue 01 (2016-04-29)

1615

Access Module
b.

----End

Data Plan
Item
Data
RF port
0/1/0
Upstream
channels
Downstream
channels

722.00
Procedure
l


a.

b.
Issue 01 (2016-04-29)
channels.
Parameter
Description

51.8-58.2 MHz.

1616

Access Module
Parameter
Description
modulation-profile


parameters:
n

profile 23 enable
c.

3 frequency 49.00
4 frequency 55.40

Parameter
Description
modulation

default setting.

Issue 01 (2016-04-29)
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream
downstream


1617

Access Module

----End
Result
1.

2.
dB.
Configuring the L2VPN Enterprise Service on an MA5633

Context
l
S-VLAN. Then, run the cable service-vlan command to make the CM go online. The
L2VPN S-VLAN is specified in the CM configuration file. When the CM goes online,
the system obtains the L2VPN S-VLAN from the CM configuration file and

Data Plan
Item
Data
VLAN
Uplink port
0/0/1
Procedure
Issue 01 (2016-04-29)

1618

Access Module
Step 2 Configure a CM management S-VLAN.
The ID of the CM management S-VLAN is 100 and the type of the VLAN is smart.
//The CM S-VLAN identifies a CM service
flow. After the CM S-VLAN is configured, the D-CCAP automatically creates a
service flow when the CM goes online.
l
commands:
----End
Verifying Services
A distributed converged cable access platform (D-CCAP) locates on an optical node when the
D-CCAP functions as a standalone NE. To facilitate service verification, the D-CCAP
supports multiple remote service verification methods, such as Dynamic Host Configuration
Protocol (DHCP) dialup emulation tests. This allows commissioning and configuration
engineers to remotely verify services. In addition, this section describes how to verify the
L2VPN service on site.
Prerequisites
l
The D-CCAP is properly connected to the upper-layer network.
Procedure
l

Issue 01 (2016-04-29)

1619

Access Module
server.
a.

NOTE
b.
c.

all
-----------------------------------------------------------------------------Idx
MAC
IP
I/F
Status
Prim Num Ver DS
RX
SID
CPE
Power
-----------------------------------------------------------------------------1
0023-ED6F-21A3 192.168.1.118
1/1/0/U4
ol-pt
1
0
D2.0
-----------------------------------------------------------------------------Total:
1
0,
0
CM.
dBmV.
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
init

CM initialization.

detect line faults.
init-rc


the CM is complete.

1620

Access Module
Issue 01 (2016-04-29)
CM
Status
Description
Handling Suggestion
DHCP


l DH
CPO

received.
l DH
CPR

received.
l DH
CPC

server is received.

REG

started.

configuration file.

1621

Access Module
CM
Status
Description
Handling Suggestion
l ol


l ol-pt
l olptd
l ol-d
l wol
l wolpt
l wolptd
l wold
l pol
l polpt
l polptd
l pold

2.0)
authentication, and
with DOCSIS 2.0)
DOCSIS 3.0)
with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
Issue 01 (2016-04-29)

1622

Access Module
CM
Status
Description
Handling Suggestion

with DOCSIS 3.0)
authentication,
DOCSIS 3.0)
with DOCSIS 3.0)
offline

l rejm

verification fails.
l rejpt

l rej-o

other reasons.

OLT.

----End

In wireless local area network (WLAN) hotspot radio backhaul service networking, an
MA5633 connects to cable modems (CMs) through radio frequency (RF) ports. A CM
connects to wireless access points (APs) to provide wireless fidelity (Wi-Fi) access for users.
This section describes how to configure the MA5633 to provision the WLAN hotspot radio
backhaul service.
Issue 01 (2016-04-29)

1623

Access Module
Usage Scenario
As shown in Figure 15-11, an MA5633 is deployed on an optical node and CMs are deployed
at shops. The CMs connect to RF ports on the MA5633 through cables.
l
dialup.
Configuration
Issue 01 (2016-04-29)

1624

Access Module
16
16 Electrical Service Configuration
Electrical Service Configuration
About This Chapter

The MA5621/MA5621A can be used for remote and intelligent information collection and
transmission (regarding power stations and user electricity consumption) in an electricity
system, and can also be used for video monitoring.
16.1 Configuration Example of the FTTx Service (GPON Access)
This topic describes how to configure the data service in the GPON access mode in various
FTTx scenarios. Only MA5621(4GE/FE) supports GPON access.
Issue 01 (2016-04-29)

1625

Access Module
16.1 Configuration Example of the FTTx Service (GPON

Access)
This topic describes how to configure the data service in the GPON access mode in various
FTTx scenarios. Only MA5621(4GE/FE) supports GPON access.
16.1.1 Configuration Example of Transmitting Video Monitoring

Data over Ethernet Access
An optical network unit (ONU) can receive video monitoring data through gigabit Ethernet
(GE)/fast Ethernet (FE) autonegotiation electrical ports and transmit the data to the optical
line terminal (OLT) through gigabit-capable passive optical network (GPON) ports. Then the
OLT transmits the data to an upper-layer device.
l
To enhance area security, a video monitoring point is deployed and monitored in real
time at the monitoring center.
The video encoder at this monitoring point provides Ethernet access so an ONU can
receive video monitoring data over Ethernet.
The data is transmitted over a GPON network.
Networking
Figure 16-1 shows an example network for configuring video monitoring data transmission
over Ethernet.
l
Located at a monitored point, the ONU is connected to video encoders through GE/FE
autonegotiation electrical ports. The ONU receives encoded video monitoring
information and forwards the information upstream to an OLT at the monitoring center.
The OLT forwards the information to other monitoring devices at the monitoring center.
Figure 16-1 Example network for configuring video monitoring data transmission over
Ethernet
Monitoring TV
wall
Video decoder
Network
camera
Management
terminal
ONU
Splitter
Network
camera
Issue 01 (2016-04-29)
OLT
Storage
server

1626

Access Module
Configuration Flowchart
Figure 16-2 provides the procedure for configuring video monitoring data transmission over
Ethernet.
Figure 16-2 Procedure for configuring video monitoring data transmission over Ethernet
ONU
OLT
Start
Start
Add an ONU to the

OLT
Create a VLAN and

add the uplink port to
the VLAN
and the ONU
ONU
Create a service port
Save
End
End
Device
Step
Remarks
OLT
1. Add an ONU on the OLT.
You can configure data for an ONU

only after it has been added on an OLT.
2. Configure a management
the ONU.
After configuring an inband

management channel between the OLT
and the ONU, you can log in to the
ONU and configure data for the ONU
on the OLT.
3. Configure a service
the ONU.
The video monitoring data is received

by the ONU and then transmitted to the
OLT. The OLT transparently transmits
the data to the monitoring center over
the upper-layer network.
1. Configure the virtual local

area network (VLAN) uplink
port.
To transmit packets with a VLAN tag

through an uplink port, add the uplink
port to the VLAN.
ONU
Issue 01 (2016-04-29)

1627

Access Module
Device
Step
Remarks
2. Configure a service port.
Create a service port on the ONU to

receive the video monitoring data. The
data is transmitted upstream to the OLT
through an uplink port.
Data Plan
Table 16-1 provides the OLT data plan, and Table 16-2 provides the ONU data plan.
Table 16-1 Data plan for configuring video monitoring data transmission over Ethernet-OLT
side
Item
Data
VLAN
l Uplink port: 0/19/0

l Inband management VLAN: smart VLAN 8
l Service VLAN: smart VLAN 100
address
192.168.50.20/24
GPON service board
l Port: 0/3/1
l ONU ID: 1
l ONU authentication mode: SN
l ONU SN: 48575443E6D8B541
l Profile name: VideoMonitoring
DBA profile
l Type: type3
ONU line profile
l Profile ID: 10, bound to DBA profile VideoMonitoring

l GEM port ID: 0 (used for transmitting inband management
service stream)
l GEM port ID: 1 (used for transparently transmitting video
monitoring service stream)
l T-CONT ID: 5
ONU management
mode
Issue 01 (2016-04-29)
SNMP

1628

Access Module
Table 16-2 Data plan for configuring video monitoring data transmission over Ethernet-ONU
side
Configuration
Item
Data
Remarks
Inband
management IP
address
192.168.50.2/24
Traffic profile
Index 6 (default)
Service port
0/1/1
Uplink port
0/0/0
Uplink VLAN
smart VLAN 100
The uplink VLAN

must be the same as
the user VLAN on the
OLT.
User VLAN
smart VLAN 2
Procedure
1.
Create an SVLAN and add an upstream port to it.

Create smart VLAN 100, and then add upstream port 0/19/0 to the VLAN.
2.
(Optional) Configure upstream link aggregation.

In this example, a single uplink port is used. In the case of multiple uplink ports,
upstream link aggregation can be configured.
3.
Configure GPON ONU profiles.

GPON ONU profiles include the DBA profile, line profile, service profile, and alarm
profile.
Issue 01 (2016-04-29)
DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT is
bound to a DBA profile for dynamic bandwidth allocation, improving the upstream
bandwidth usage rate.
Line profile: A line profile describes the binding between the T-CONT and the
DBA profile, the QoS mode of the traffic stream, and the mapping between the
GEM port and the ONU-side service.
Service profile: A service profile provides the service configuration channel for the
ONU that is managed through OMCI.
monitor the performance of activated ONU lines. When a statistical value reaches
the threshold, the host is notified and an alarm is reported to the log host and the
NMS.
1629

Access Module
a.
Add a DBA profile.

You can at first run the display dba-profile command to query the DBA profiles
existing in the system. If the DBA profiles existing in the system do not meet the
requirements, you need to run the dba-profile add command to add a DBA profile.
Configure the profile name to VideoMonitoring, profile type to Type3, assured
bandwidth to 20 Mbit/s, and maximum bandwidth to 50 Mbit/s.
huawei(config)#dba-profile add profile-name VideoMonitoring type3 assure
20480 max 51200
b.
Add an ONU line profile.

Add GPON ONU line profile 10 and bind T-CONT 5 to the DBA profile named
VideoMonitoring. In this way, the T-CONT can provide flexible DBA solutions
based on different configurations in the DBA profile.
VideoMonitoring
Add GEM port 0 for transmitting management traffic streams, GEM port 1 for
transmitting video monitoring information traffic streams. Bind GEM port 0 and
GEM port 1 to T-CONT 5. Configure the QoS mode to priority-queue (default) and
the queue priority to 3.
Configure the mapping mode from the GEM port to ONU-side service to VLAN
(default), map the service port of management VLAN 8 to GEM port 0, map the
service port of video monitoring information SVLAN 100 to GEM port 1.
c.
4.

n
The ID of the default GPON alarm profile is 1. The thresholds of all the alarm
generated.
Run the gpon alarm-profile add command to add an alarm profile, which is
used for monitoring the performance of an activated ONU line.

The ONU is connected to the GPON port of the OLT through an optical fiber. You can
perform the service configuration only after adding an ONU successfully on the OLT.
a.
Add an ONU.
Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is
48575443E6D8B541, the management mode is SNMP, and the bound line profile
ID is 10.
There are two ways to add an ONU. Select either of the two ways according to
actual conditions.
Issue 01 (2016-04-29)

1630

Access Module
Add an ONU offline: If the password or SN of an ONU is obtained, you can

run the ont add command to add the ONU offline.
Automatically find an ONU: If the password or SN of an ONU is unknown,

run the port ont-auto-find command in the GPON mode to enable the ONU
auto-find function of the GPON port. Then, run the ont confirm command to
confirm the ONU.
To add an ONU offline, do as follows:

To automatically find an ONU, do as follows:

//After this command is executed, the information about all ONUs
connected to the GPON port through the optical splitter is displayed.
48575443E6D8B541 snmp ont-lineprofile-id
NOTE
If multiple ONUs of the same type are connected to a port and the same line profile or service
profile is bound to the ONUs, you can add ONUs in batches by confirming the auto-found ONUs
in batches to simplify the operation and increase the configuration efficiency. For example, the
preceding command can be modified as follows:
5.
Confirm that the ONU goes online normally.

After an ONU is added, run the display ont info command to query the current status of
the ONU. Ensure that Control flag of the ONU is active, Run State is online, Config
state is normal, and Match state is match.
--------------------------------------------------------------------F/S/P
:
0/3/1
ONT-ID
:
1
Control flag
: active
activated.
Run state
: online
//Indicates that the ONU already goes
online normally.
Config state
: normal
//Indicates that the configuration status
of the ONU is normal.
Match state
: match
//Indicates that the capability profile
bound to the ONU is
//consistent with the actual capability
of the ONU.
If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match,
check the ONU state by referring to the above-mentioned descriptions.
Issue 01 (2016-04-29)
If Control flag is deactive, run the ont activate command in the GPON port mode
to activate the ONU.
1631

Access Module
If the ONU fails to be in the up state, that is, Run state is offline, the physical line
may be broken or the optical transceiver may be damaged. You need to check both
the material and the line.
If the ONU state fails, that is, Config state is failed, the ONU capability set
outmatches the actual ONU capabilities. In this case, run the display ont failedconfiguration command in the diagnosis mode to check the failed configuration
item and the failure cause. Then, rectify the fault according to actual conditions.
NOTE
If an ONT supports only four queues, the values of 4-7 of the priority-queue parameter in the gem
add command are invalid. After configuration recovers, Config state will be failed.
6.
Configure the management channel from the OLT to the ONU.

NOTE
Only when the OLT remotely manages the ONU through SNMP, the management channel needs to be
configured. When the OLT remotely manages the ONU through OMCI, the management channel need
not be configured.
a.

To log in to the ONU through Telnet and configure the ONU from the OLT, you
must configure the inband management VLANs and IP addresses of the OLT and
the ONU on the OLT.
Create management VLAN 8 and add upstream port 0/0/0 to it. Configure the
inband management IP address to 192.168.50.20/24.
b.

Configure the static IP address of the ONU to 192.168.50.2/24 and the management
VLAN ID to 8 (the same as the management VLAN of the OLT).
huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address
192.168.50.2 mask
255.255.255.0 vlan 8
c.
Configure an inband management service port.

Configure the management service port ID to 0, management VLAN ID to 8, GEM
port ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT is
not limited. Therefore, use traffic profile 6 (default). To limit the rate of the service
port, run the traffic table ip command to add a traffic profile and bind it to the
service port.
7.
8.
Confirm that the management channel between the OLT and the ONU is available.
On the OLT, run the ping 192.168.50.2 command to check the connectivity to the
ONU. The ICMP ECHO-REPLY packet from the ONU should be received.
You can run the telnet 192.168.50.2 command to telnet to the ONU and then
configure the ONU.

Configure the Video Monitoring Data service port ID to 1, SVLAN ID to 100, GEM port
ID to 1, CVLAN ID to 100. Rate limitation for upstream and downstream packets is
Issue 01 (2016-04-29)

1632

Access Module
performed on the ONU instead of on the OLT. Therefore, use traffic profile 6 (default).
To limit the rate of the service port, run the traffic table ip command to add a traffic
profile and bind it to the service port.
9.

Queue scheduling is a global configuration. You need to configure queue scheduling
only once on the OLT, and then the configuration takes effect globally. In the subsequent
phases, you need not configure queue scheduling repeatedly when configuring other
services.
Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map queues
0-7 respectively.
For the service board that supports only four queues, the mapping between 802.1p
priorities and queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and 3
map queue 2; priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.
cos7 7
10. Save the data.

huawei(config)#save
Step 2 Configure the ONU.

NOTE
Because the management VLAN and the management IP address have been configured, you can run the
telnet 192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You can also
log in to the ONU through a serial port to perform the configuration.
1.
Log in to the ONU to perform the configuration.

On the OLT, use the management IP address of the ONU to log in to the ONU through
Telnet. User name: root (default). Password: admin123 (default).
huawei(config)#telnet 192.168.50.2
{ <cr>|service-port<0,4294967295> }:
Command:
telnet 192.168.50.2
Press CTRL_] to quit telnet mode
Trying 192.168.50.2 ...
Connected to 192.168.50.2 ...
>>User name:root
>>User password:
//It is not displayed on the console.
2.
Create a VLAN.
3.
Add an uplink port to the VLAN.

Add uplink port 0/0/0 to the VLAN.
Issue 01 (2016-04-29)

1633

Access Module
4.

Create service port 2. Its user VLAN ID is 2 and service VLAN ID is 100. Use the
default traffic profile (traffic profile 6). To limit the traffic rate, run the traffic table ip
command to configure the traffic profile.
huawei(config)#service-port 2 vlan 100 eth 0/1/1 multi-service user-vlan 2 rxcttr 6
tx-cttr 6
5.
Save the data.

huawei(config)#save
----End
Result
After the preceding configurations are complete, devices at the monitoring center (such as the
storage server, management terminal, and video decoder) will receive video monitoring
information.
Configuration File
Configure the OLT.
vlan 100 smart
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.20 24
quit
dba-profile add profile-name VideoMonitoring type3 assure 20480 max 51200
tcont 5 dba-profile-name VideoMonitoring
gem add 0 eth tcont 5 priority-queue 3
mapping-mode vlan
commit
quit
interface gpon 0/3
port 1 ont-auto-find enable
display ont autofind 1
ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id
quit
service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service
queue-scheduler wrr 10 10 20 20 40 0 0 0
cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7
save
Configure the ONU.

vlan 100 smart
port vlan 100 0/0 0
service-port 2 vlan 100 eth 0/1/1 multi-service user-vlan 2 rx-cttr 6 tx-cttr 6
save
Issue 01 (2016-04-29)

1634

Access Module
16.1.2 Configuration Example of Intelligently Collecting Power

Consumption Information over Ethernet Access
An optical network unit (ONU) can intelligently collect power consumption information in
the electrical power system through gigabit Ethernet (GE)/fast Ethernet (FE) autonegotiation
electrical ports, and transmit the data upstream to the optical line terminal (OLT) through
gigabit-capable passive optical network (GPON) ports.
l
A large number of power consumption information in the electrical power system needs
to be collected in real time and transmitted to an automatic meter reading system (AMR)
server.
The smart meter on the user side has a serial port and an ONU is connected to the smart
meter through the serial port.
The power consumption information is transmitted through a GPON network.
Networking
Figure 16-3 shows an example network for configuring intelligent collection of power
consumption information in the electrical power system over Ethernet.
l
The ONU is connected to a concentrator through a GE/FE autonegotiation electrical port.

The concentrator is connected to a collector using power cables and sends the power
consumption information collected by the collector to the ONU.
The ONU forwards the power consumption information to an OLT and the OLT
forwards the information to the upper-layer device. Then the upper-layer device forwards
the information to an AMR server.
Issue 01 (2016-04-29)

1635

Access Module
Figure 16-3 Example network for configuring intelligent collection of power consumption
information in the electrical power system over Ethernet
Master station system
OLT
Splitter
ONU
GE/FE
Concentrator
collector
Smart meter
Electric cable
Serial port cable
Network cable
Figure 16-4 provides the procedure for configuring intelligent collection of power
consumption information in the electrical power system over Ethernet
Issue 01 (2016-04-29)

1636

Access Module
Figure 16-4 Procedure for configuring intelligent collection of power consumption

information in the electrical power system over Ethernet
ONU
OLT
Start
Start
Add an ONU to the

OLT
Create a VLAN and

add the uplink port to
the VLAN
and the ONU
ONU
Create a service port
Save
End
End
Device
Step
Remarks
OLT
1. Add an ONU on an OLT.
You can configure data for an ONU

only after it has been added on an OLT.
the ONU.
After configuring an inband

management channel between the OLT
and the ONU, you can log in to the
ONU on the OLT and configure data
for the ONU.
the ONU.
The power consumption information

collected by the ONU is transparently
transmitted by the OLT through the
upper-layer network to the AMR
server.
1. Create a virtual local area

network (VLAN) and add the
uplink port to the VLAN.
To transmit packets with a VLAN tag

through an uplink port, add the uplink
port to the VLAN.
2. Create a service port.
Create a service port on the ONU to

receive the power consumption
information. The data is transmitted
upstream to the OLT through an uplink
port.
ONU
Issue 01 (2016-04-29)

1637

Access Module
Data Plan
Table 16-3 Data plan for configuring intelligent collection of power consumption information
in the electrical power system over Ethernet-OLT side
Item
Data
VLAN

l Inband management VLAN: smart VLAN 8
l Service VLAN: smart VLAN 100
address
IP address: 192.168.50.20/24
GPON service board
l Port: 0/3/1
l ONU ID: 1
l ONU SN: 48575443E6D8B541
l Profile name: Data
DBA profile
l Type: type3
l Profile ID: 10, bound to DBA profile Data
ONU line profile
l GEM port ID: 0 (used for transmitting inband management

service stream)
l GEM port ID: 1 (used for transparently transmitting meter
data)
l T-CONT ID: 5
ONU management
mode
SNMP
Table 16-4 Data plan for configuring intelligent collection of power consumption information
in the electrical power system over Ethernet-ONU side
Issue 01 (2016-04-29)
Configuration
Item
Data
Remarks
Inband
management IP
address
IP address: 192.168.50.2/24
Traffic profile
Index 6 (default)
Service port
0/1/1

1638

Access Module
Configuration
Item
Data
Remarks
Uplink port
0/0/0
Uplink VLAN
smart VLAN 100
The uplink VLAN

must be the same as
the user VLAN on the
OLT.
User VLAN
untagged
Procedure
1.

Create smart VLAN 100, and then add upstream port 0/19/0 to the VLAN.
2.

3.

profile.
ONU that is managed through OMCI.
NMS.
a.
Add a DBA profile.

Configure the profile name to Data, profile type to Type3, assured bandwidth to 20
Mbit/s, and maximum bandwidth to 50 Mbit/s.
huawei(config)#dba-profile add profile-name Data type3 assure 20480 max
51200
Issue 01 (2016-04-29)

1639

Access Module
b.

Data. In this way, the T-CONT can provide flexible DBA solutions based on
different configurations in the DBA profile.
huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name Data
transmitting data traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 5.
Configure the QoS mode to priority-queue (default) and the queue priority to 3.
service port of SVLAN 100 to GEM port 1.
c.
4.

n
generated.

a.
Add an ONU.
ID is 10.
actual conditions.
n


confirm the ONU.

huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541
snmp ont-lineprofile-id 10 desc MA5621_0/3/1/1_lineprofile10

Issue 01 (2016-04-29)

1640

Access Module

huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541
snmp ont-lineprofile-id 10 desc MA5621_0/3/1/1_lineprofile10
NOTE
in batches to simplify the operation and increase the configuration efficiency. For example, the
preceding command can be modified as follows:
MA5621_0/3/1_lineprofile10
5.

the ONU. Ensure that Control flag of the ONU is active, Run State is online, and
Config state is normal.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
//Indicates that the ONU is activated.
Run state
: online
online normally.
Config state
: normal
NOTE
6.

NOTE
not be configured.
a.

To remote log in to the ONU and configure the ONU from the OLT, you must
configure the inband management VLANs and IP addresses of the OLT and the
ONU on the OLT.
Issue 01 (2016-04-29)

1641

Access Module
Create management VLAN 8, and configure the inband management IP address to

192.168.50.20/24.
b.

192.168.50.2 mask 255.255.255.0 vlan 8
c.

port ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT is
not limited. Therefore, use traffic profile 6 (default). To limit the rate of the service
service port.
huawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multiservice user-vlan 8 rx-cttr 6 tx-cttr 6
7.
8.
You can remote log in to the ONU from the OLT to perform the configuration.

Configure the Data service port ID to 1, SVLAN ID to 100, GEM port ID to 1, CVLAN
ID to 100. Rate limitation for upstream and downstream packets is performed on the
ONU instead of on the OLT. Therefore, use traffic profile 6 (default). To limit the rate of
the service port, run the traffic table ip command to add a traffic profile and bind it to
the service port.
huawei(config)#service-port 1 vlan 100 gpon 0/3/1 ont 1 gemport 1 multiserviceuser-vlan 100 rx-cttr 6 tx-cttr 6
9.

services.
0-7 respectively.
Issue 01 (2016-04-29)

1642

Access Module

cos7 7
10. Save the data.

huawei(config)#save

NOTE
Because the management VLAN and the management IP address have been configured, you can remote log
in to the ONU from the OLT to perform the configuration.
1.

On the OLT, you can remote log in to the ONU to perform the configuration. User name:
2.
Create a VLAN.
3.
Add an uplink port to the VLAN.

Add uplink port 0/0/0 to the VLAN.
4.

Create service port 2. Its user VLAN ID is untagged and service VLAN ID is 100. Use
the default traffic profile (traffic profile 6). To limit the traffic rate, run the traffic table
ip command to configure the traffic profile.
5.
Save the data.

huawei(config)#save
----End
Result
After the preceding configurations are complete, the power consumption information
collected by the smart meter is transmitted to the AMR server.
Configuration File
Configure the OLT.
vlan 100 smart
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.20 24
quit
dba-profile add profile-name Data type3 assure 20480 max 51200
tcont 5 dba-profile-name Data
mapping-mode vlan
commit
quit
Issue 01 (2016-04-29)

1643

Access Module
interface gpon 0/3

quit
save
Configure the ONU.

vlan 100 smart
port vlan 100 0/0 0
service-port 2 vlan 100 eth 0/1/1 multi-service user-vlan untagged rx-cttr 6 txcttr 6
save
16.1.3 Configuration Example of Automatically Transmitting Site

Information over Ethernet (Single Homing)
An optical network unit (ONU) can receive site information in the electrical power system
through gigabit Ethernet (GE) or fast Ethernet (FE) autonegotiation electrical ports, and
automatically transmit the information to an optical line terminal (OLT). The ONU cooperates
with an OLT to provide GPON type C single-homing protection, ensuring service reliability.
GPON is the acronym for gigabit-capable passive optical network.
Context
Generic object oriented substation event (GOOSE) is a mechanism defined in IEC 61850 for
rapidly transmitting events in a substation automation system. GOOSE packets are multicast
packets for communication between terminal units.
In the GPON type C single-homing protection mechanism, the two PON lines between an
ONU and an OLT work in active/standby mode and cannot forward packets at the same time.
l
If the OLT detects that the upstream link to the active PON port is faulty, the OLT
automatically switches services to the upstream link to the standby PON port. In
addition, the OLT sends a PON section trace (PST) message to the ONU to notify the
ONU of the switching and switching cause over the uplink to the standby PON port, and
instructs the ONU to perform the switching.
If the ONU detects that the downstream link to the active PON port is faulty, the ONU
automatically switches services to the downstream link to the standby PON port. In
addition, the ONU sends a PST message to the OLT to notify the OLT of the switching
and switching cause over the downlink to the standby PON port, and instructs the OLT to
perform the switching.
l
In a smart grid, terminal units collect the running status information, as well as
monitoring and control information about the power distribution system and send the
information to the master station system.
The information collected by terminal units is transparently transmitted to the master

station system, and therefore the transmission network must be secure enough to ensure
reliable running of the smart grid.
Issue 01 (2016-04-29)

1644

Access Module
Terminal units must communicate with each other. This is because, when a breaker is
disconnected or the switch position of an isolator switch changes, a terminal unit must
directly send the change information to the measuring and monitoring device and the
substation monitoring system in real time. GOOSE can rapidly transmit events in a
substation automation system, and requires that ONUs connecting to the same or
different PON ports support Layer 2 interconnection.
A terminal unit provides Ethernet access so an ONU can receive the collected
information over Ethernet.
The information is transmitted over a GPON network.
Networking
Figure 16-5 shows an example network for configuring automatic transmission of site
information in the electrical power system over Ethernet, and the active and standby line
connections between the terminal units and the master station system. This example describes
how to configure the transmission for terminal unit A connected to ONU_A. The
configuration procedure for ONU_B is similar to that for ONU_A.
l
ONU_A and ONU_B are connected to terminal units through a GE or FE

autonegotiation electrical port. After receiving messages from a terminal unit, ONU_A
and ONU_B report the messages to the OLT. The OLT forwards the messages to the
master station system.
In a single homing scenario, an ONU is connected to one OLT. The OLT provides two
passive optical network (PON) ports. An ONU provides two PON ports for upstream
transmission, and the backbone fiber, optical splitter, and distribution fiber are
configured for redundancy backup. In this scenario, PON type C single-homing
protection can be configured to ensure service reliability.
Issue 01 (2016-04-29)

1645

Access Module
Figure 16-5 Example network for configuring automatic transmission of site information in
the electrical power system over Ethernet
Master station system
Transmission
OSN/PTN
OLT
Splitter
ONU_A
Terminal unit A
ONU_B
Terminal unit B
Active Link
Standby Link
Data Plan
Table 16-5 Data plan for configuring automatic transmission of site information in the
electrical power system over Ethernet-OLT side
Issue 01 (2016-04-29)
Devi
ce
Item
Data
OLT
Uplink port
Ethernet port: 0/19/0

1646

Access Module
Devi
ce
Item
Data
VLAN
l Inband management virtual local area

network (VLAN): smart VLAN 8
l Customer VLAN (CVLAN): smart
VLAN 200; service VLAN (SVLAN):
smart VLAN 200 (used for
transmitting the site information about
the electrical power system)
l CVLAN: smart VLAN 100; SVLAN:
smart VLAN 100 (used for
transmitting GOOSE packets)
Inband management IP address
IP address: 192.168.50.20/24
GPON service board
l Port:
The GPON service board can be the

H801GPBC, H802GPBD, or
H805GPBD board.
0/3/1: GPON port connecting to

the active line
0/4/1: GPON port connecting to
the standby line
l ONU ID: 1
l ONU SN: 48575443E6D8B541
DBA profile
l Profile name: Data

l Type: type3
ONU line profile
l Profile ID: 10, bound to the DBA

profile named Data
l GEM port ID: 0 (used for transmitting
inband management service stream)
l GEM port ID: 1 (used for
information about the electrical power
system)
l GEM port ID: 2 (used for
transparently transmitting GOOSE
packets)
l T-CONT ID: 5
Issue 01 (2016-04-29)
ONU management mode
SNMP
Priority
The 802.1p priority is used: The priority

of the site information about the electrical
power system is 1 and the priority of
GOOSE packets is 5.

1647

Access Module
Table 16-6 Data plan for configuring automatic transmission of site information in the
electrical power system over Ethernet-ONU side
Device
Configurati
on Item
Data
Remarks
ONU_A
Inband
management
IP address
192.168.50.2/24
Traffic
profile
l Index 10 (used for transmitting the

power distribution site
information)
l Index 11 (used for transmitting

GOOSE packets)
Service port
Ethernet port: 0/1/1
Port 0/1/1 is used

for services on
terminal unit A.
Uplink port
GPON port
l 0/0/0: active uplink port

l 0/0/1: standby uplink port
Uplink
VLAN
l Smart VLAN 8 (used for inband

management VLAN)
l Smart VLAN 200 (used for
transmitting power distribution
site information)
The uplink
VLAN must be
the same as the
CVLAN on the
OLT.

Priority
The 802.1p priority is used: The

priority of power distribution site
information is 1 and the priority of
GOOSE packets is 5.
User-side
VLAN
l Untagged (used for transmitting

information)

ONU_B
The data plan is the same as that of ONU_A except for the IP address.
NOTE
When deploying GPON type C protection, ensure that static MAC address, static Address Resolution
Protocol (APR), and Ethernet operation, administration, and maintenance (OAM) functions are not
configured on an uplink port. Otherwise, service protection switchover may be affected.
When deploying GPON type C protection, ensure that the configurations of port virtual local area network
(VLAN), traffic suppression, line rate, and access control list (ACL) on the two uplink ports on an ONU are
the same.
Issue 01 (2016-04-29)

1648

Access Module
Procedure
1.
Create an SVLAN and add an uplink port to it.

Create service VLANs 100 and 200, and then add uplink port 0/19/0 to VLAN 200.
2.

3.

profile.
ONU that is managed through OMCI. You do not need to configure a service
profile in this configuration example.
NMS.
a.
Add a DBA profile.

51200
b.

transmitting the electric system site information traffic streams and GEM port 2 for
transmitting goose packets traffic streams. Bind GEM port 0, GEM port 1 and GEM
port 2 to T-CONT 5. Configure the QoS mode to priority-queue (default) and the
queue priority to 3.
NOTE
The MA5621 does not support QoS mode gem-car or flow-car.
Issue 01 (2016-04-29)

1649

Access Module

service port of the site information SVLAN 200 to GEM port 1 and map the service
port of the goose packets SVLAN 100 to GEM port 2.
c.
4.

n
generated.

a.
Add an ONU.
ID is 10.
actual conditions.
n


confirm the ONU.

huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ontlineprofile-id 10 desc MA5621_0/3/1/1_lineprofile10

48575443E6D8B541 snmp ont-lineprofile-id 10 desc
MA5621_0/3/1/1_lineprofile10
Issue 01 (2016-04-29)

1650

Access Module
NOTE
in batches to simplify the operation and increase the configuration efficiency.
For example, the preceding command can be modified as follows: huawei(config-ifgpon-0/3)#ont confirm 1 all sn-auth snmp ont-lineprofile-id 10 desc
5.

--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
Run state
: online
online normally.
Config state
: normal
NOTE
6.

NOTE
not be configured.
a.

the ONU on the OLT.
192.168.50.20/24.
Issue 01 (2016-04-29)

1651

Access Module

b.

192.168.50.2 mask 255.255.255.0 vlan 8
c.

port ID to 0, and customer VLAN (CVLAN) ID to 8. The rate of the inband service
port on the OLT is not limited. Therefore, use traffic profile 6 (default). To limit the
rate of the service port, run the traffic table ip command to add a traffic profile and
bind it to the service port.
7.
8.
configure the ONU.
Configure a GPON type C protection group.

Configure cross-board backup on ports 0/3/1 and 0/4/1 on different GPON service
boards on the OLT. After the configuration, when port 0/3/1 is faulty, the OLT
automatically switches services to port 0/4/1, ensuring services running.
huawei(config-if-gpon-0/4)#ont add 1 protect-side
//Set the link to
port 0/4/1 as the standby link.
huawei(config)#protect-group 0 protect-target gpon-uni-ont workmode portstate
9.

Configure the site information service port ID to 1, SVLAN ID to 200, CVLAN ID to
200, and GEM port ID to 1, and configure the GOOSE packets service port ID to 2,
SVLAN ID to 100, CVLAN ID to 100, and GEM port ID to 2. Rate limitation for
upstream and downstream packets is performed on the ONU instead of on the OLT.
The same port is used for transmitting the site information about the electrical power
system and GOOSE packets. Therefore, the 802.1p priority of each service needs to be
set. The priority of the site information about the electrical power system is lower than
that of GOOSE packets. Set the traffic profile index of the site information about the
electrical power system to 20 and the priority to 1; set the traffic profile index of GOOSE
packets to 21 and the priority to 5.
local-Setting
Create traffic descriptor record successfully
-----------------------------------------------TD Index
: 20
Issue 01 (2016-04-29)

1652

Access Module
TD Name
: ip-traffic-table_20
Priority
: 1
Copy Priority
: Mapping Index
: CTAG Mapping Priority: CTAG Mapping Index
: CTAG Default Priority: 0
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Fix
: off
CAR Threshold Profile: Color Mode
: color-blind
Color Policy
: dei
Referenced Status
: not used
local-Setting
-----------------------------------------------TD Index
: 21
TD Name
Priority
: 5
Copy Priority
: Mapping Index
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Fix
: off
: color-blind
Color Policy
: dei
Referenced Status
: not used
-----------------------------------------------huawei(config)#service-port 1 vlan 200 gpon 0/3/1 ont 1 gem port 1 multiservice user-vlan 200 inbound traffic-table index 20 outbound traffic-table
index 20
huawei(config)#service-port 2 vlan 100 gpon 0/3/1 ont 1 gem port 2 multiservice user-vlan 100 inbound traffic-table index 21 outbound traffic-table
index 21
10. Configure the bridging function for GOOSE packets.

a.
Disable the unknown multicast suppression function.

Goose packets are unknown multicast packets. Disable the unknown multicast
suppression function on the OLT to ensure that GOOSE packets are not lost.
huawei(config-vlan-srvprof-20)#packet-policy multicast forward
Info: Please use the commit command to make modifications take effect
b.
Enable the bridging function.

To support the electrical GOOSE function, ONU_A must communicate with
ONU_B at Layer 2.
Issue 01 (2016-04-29)

1653

Access Module
c.
Bind the VLAN service profile to the uplink VLAN.

11. Configure queue scheduling.

The GOOSE service traffic is forwarded in PQ mode.
services.
0-7 respectively.
cos7 7
12. Save the data.

huawei(config)#save
Step 2 The following describes the procedure for configuring the automatic transmission of site
information about the electrical power system over Ethernet on ONU_A.
NOTE
1.

{ <cr>|service-port<0,4294967295> }:
Command:
telnet 192.168.50.2
Trying 192.168.50.2 ...
Connected to 192.168.50.2 ...
>>User name:root
>>User password:
2.
Configure the dual PON ports upstream mode.

For GPON type C single-homing protection, set the dual PON ports upstream mode to
Active-standby uplink mode.
huawei(config)#pon uplink-mode active-standby
3.

The same port is used for transmitting power distribution site information and GOOSE
packets. Therefore, the 802.1p priority of each service needs to be set. The priority of
power distribution site information is lower than that of GOOSE packets. Set the traffic
profile index of power distribution site information to 10 and the priority to 1; set the
traffic profile index of GOOSE packets to 11 and the priority to 5.
local-Setting
Issue 01 (2016-04-29)

1654

Access Module

-----------------------------------------------TD Index
: 10
TD Name
Priority
: 1
Copy Priority
: CTAG Mapping Priority: CTAG Default Priority: 0
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Color Mode
: color-blind
Referenced Status
: not used
local-Setting
-----------------------------------------------TD Index
: 11
TD Name
Priority
: 5
Copy Priority
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Color Mode
: color-blind
Referenced Status
: not used
------------------------------------------------
4.
Create VLANs.
transmission from ONU_A to the OLT
5.
//Create SVLANs for service
Add an uplink port to the VLANs.

Add uplink port 0/0/0 and 0/0/1 to the VLANs.
huawei(config)#port vlan 100,200 0/0 0-1
6.
Create service ports.

For power distribution site information, create service port 2 with SVLAN 200 and
traffic profile 10.
For GOOSE packets, create service port 3 with SVLAN 100, CVLAN 2 and traffic
profile 11.
7.
Configure the bridging function for GOOSE packets.

a.

Info: Please use the commit command to make modifications take
effect
Issue 01 (2016-04-29)

1655

Access Module
b.

huawei(config-vlan-srvprof-10)#user-bridging
enable
Info: Please use the commit command to make modifications take
effect
c.

d.
In ETH mode, disable the unknown multicast suppression function on the user
interface and uplink port.
huawei(config-if-eth-0/1)#undo traffic-suppress 1 multicast
huawei(config-if-eth-0/0)#undo traffic-suppress all multicast
8.
Set the queue scheduling mode to strict priority queue (PQ).

9.
Save the data.

huawei(config)#save
----End
Result
After the master station server queries the power distribution site information, the power
distribution site information is transmitted to the master station server.
Configuration File
Configure OLT_A.
vlan 100,200 smart
mapping-mode vlan
commit
quit
interface gpon 0/3
quit
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.20 24
Issue 01 (2016-04-29)

1656

Access Module
quit
interface gpon 0/3
quit
interface gpon 0/4
ont add 1 protect-side
quit
protect-group 0 protect-target gpon-uni-ont workmode portstate
protect-group member port 0/3/1 ont 1 role work
protect-group member port 0/4/1 ont 1 role protect
protect-group enable
quit
user-vlan 200 inbound traffic-table index 20 outbound traffic-table index 20
user-vlan 100 gemport 2 inbound traffic-table index 21 outbound traffic-table
index 21
multicast-unknown policy service-port 2 transparent
vlan service-profile profile-id 20
packet-policy multicast forward
user-bridging enable
commit
quit
vlan bind service-profile 100 profile-id 20
save
Configure ONU_A.
pon uplink-mode active-standby
vlan 100,200 smart
port vlan 100,200 0/0 0-1
service-port 2 vlan 200 eth 0/1/1 multi-service user-vlan untagged
rx-cttr 10 tx-cttr 10
commit
quit
interface eth 0/1
undo traffic-suppress 1 multicast
quit
interface eth 0/0
undo traffic-suppress all multicast
quit
save
16.1.4 Configuration Example of Automatically Transmitting Site

Information over Ethernet (Dual Homing)
An optical network unit (ONU) can automatically transmit power distribution site information
in the electrical power system through gigabit Ethernet (GE) or fast Ethernet (FE)
autonegotiation electrical ports. The ONU cooperates with an optical line terminal (OLT) to
provide GPON type C dual-homing protection, ensuring service reliability. GPON is the
acronym for gigabit-capable passive optical network.
Issue 01 (2016-04-29)

1657

Access Module
Context
Generic object oriented substation event (GOOSE) is a mechanism defined in IEC 61850 for
rapidly transmitting events in a substation automation system. GOOSE packets are multicast
packets for communication between terminal units.
On a type C dual-homing GPON network, the two PON links between an OLT and an ONU
work in active/standby mode and they cannot forward packets at the same time. When the
active link is faulty due to a component fault, the ONU can rapidly switch services to the
standby OLT. If a protection group is bound to the status of an upstream Ethernet port or
Bidirectional Forwarding Detection (BFD) sessions on an optical line terminal (OLT),
namely, a protection group is associated with the status of an upstream Ethernet port of BFD
sessions, the OLT notifies the ONU of performing an active/standby switchover to restore
services when the OLT upstream network fails to be connected or an OLT Layer 2 physical
link fails.
l
In a smart grid, terminal units collect the running status information, as well as
monitoring and control information about the power distribution system and send the
information to the master station system.
The information collected by terminal units is transparently transmitted to the master

station system, and therefore the transmission network must be secure enough to ensure
reliable running of the smart grid.
Terminal units must communicate with each other. This is because, when a breaker is
disconnected or the switch position of an isolator switch changes, a terminal unit must
directly send the change information to the measuring and monitoring device and the
substation monitoring system in real time. GOOSE can rapidly transmit events in a
substation automation system, and requires that ONUs connecting to the same or
different PON ports support Layer 2 interconnection.
A terminal unit provides Ethernet access so an ONU can receive the collected
information over Ethernet.
The information is transmitted over a GPON network.
Networking
Figure 16-6 shows an example network for configuring the automatic transmission of power
distribution site information in the electrical power system over Ethernet.
l
ONU_A and ONU_B are connected to terminal units through a GE or FE

autonegotiation electrical port. After receiving messages from a terminal unit, ONU_A
and ONU_B report the messages to the OLT. The OLT forwards the messages to the
master station system.
In a dual homing scenario, an ONU is connected to two OLTs. Each OLT provides a
passive optical network (PON) port. An ONU provides two PON ports for upstream
transmission, and the backbone fiber, optical splitter, and distribution fiber are
configured for redundancy backup. In this scenario, GPON type C dual-homing
protection can be configured to ensure service reliability.
Issue 01 (2016-04-29)

1658

Access Module
Figure 16-6 Example network for configuring automatic transmission of power distribution
site information in the electrical power system over Ethernet
Master station
system
LAN Switch
Transmission
OSN
/PTN
OSN
/PTN
OLT_A
OLT_B
Splitter
ONU_B
ONU_A
FE
FE
Terminal unit
Terminal unit
Standby Link
Active Link
Data Plan
Table 16-7 Data plan for configuring automatic transmission of power distribution site
information in the electrical power system over Ethernet-OLT side
Issue 01 (2016-04-29)
Device
Item
Data
OLT_A
Uplink port
0/19/0

1659

Access Module
Device
Item
Data
VLAN
l Inband management virtual local area

network (VLAN): smart VLAN 8
l Customer VLAN (CVLAN): smart VLAN
100; service VLAN (SVLAN): smart VLAN
200 (used for transmitting the site
information about the electrical power
system)
l CVLAN: smart VLAN 101; SVLAN: smart
VLAN 100 (used for transmitting GOOSE
packets)
address
192.168.50.20/24
GPON service board
Port: 0/3/1
The GPON service board

can be an H801GPBC,
H802GPBD, or H805GPBD
board.
ONU ID: 1
DBA profile
Profile name: Data
ONU authentication mode: SN

ONU SN: 48575443E6D8B541
Type: type3
ONU line profile
l Profile ID: 10, bound to the DBA profile

named Data
l GEM port ID: 0 (used for transmitting
inband management service stream)
l GEM port ID: 1 (used for transparently
transmitting the information about the
electrical power system)
l GEM port ID: 2 (used for transparently
l T-CONT ID: 5
Issue 01 (2016-04-29)
ONU management mode
SNMP
Priority
The 802.1p priority is used: The priority of the

site information about the electrical power
system is 1 and the priority of GOOSE packets
is 5.

1660

Access Module
Device
Item
Data
Associated protection
switching
A protection group is associated with the status

of upstream Ethernet ports.
NOTE
l To detect the link status at the IP layer (the
connection status of the OLT upstream network),
you need to associate the protection group with
BFD sessions.
l To detect a Layer 2 physical link fault, you need
to associate the protection group with the status of
the upstream Ethernet port.
In this example, the protection group is associated
with the status of the upstream Ethernet port.
OLT_B
The data plan is the same as that of OLT_A. OLT_A and OLT_B must have the
same configurations. Otherwise, service switching will be affected.
Table 16-8 Data plan for configuring automatic transmission of power distribution site
information in the electrical power system over Ethernet-ONU side
Device
Configurati
on Item
Data
Remarks
ONU_A
Inband
management
IP address
IP address: 192.168.50.2/24
Traffic
profile
l Index 10 (used for transmitting the

information)
l Index 11 (used for transmitting

GOOSE packets)
Service port
Eth port: 0/1/1
Uplink port
GPON port: 0/0/0, 0/0/1
Uplink
VLAN

transmitting power distribution
site information)
The uplink
VLAN must be
the same as the
CVLAN on the
OLT.

Priority
Issue 01 (2016-04-29)
The 802.1p priority is used: The

priority of power distribution site
information is 1 and the priority of
GOOSE packets is 5.

1661

Access Module
Device
Configurati
on Item
Data
Remarks
User-side
VLAN
Untagged (used for transmitting

power distribution site information)
Smart VLAN 2 (used for transmitting

GOOSE packets)
ONU_B
The data plan is the same as that of ONU_A except for the IP address.
NOTE
When deploying GPON type C dual-homing protection, ensure that static MAC address, static Address
Resolution Protocol (APR), and Ethernet operation, administration, and maintenance (OAM) functions are
not configured on an uplink port. Otherwise, service protection switchover may be affected.
When deploying GPON type C dual-homing protection, ensure that the configurations of port virtual local
area network (VLAN), traffic suppression, line rate, and access control list (ACL) on the two uplink ports on
an ONU are the same.
Procedure
1.
Create an SVLAN and add an uplink port to it.

Create smart VLAN 101 and VLAN 200, and then add uplink port 0/19/0 to these
VLANs.
2.

3.

profile.
Issue 01 (2016-04-29)
ONU that is managed through OMCI. You do not need to configure a service
profile in this configuration example.
NMS.
1662

Access Module
a.
Add a DBA profile.

51200
b.

transmitting the electrical power system site information traffic streams and GEM
port 2 for transmitting GOOSE packets traffic streams. Bind GEM port 0, GEM
port 1 and GEM port 2 to T-CONT 5. Configure the QoS mode to priority-queue
(default) and the queue priority to 3.
NOTE
The MA5621 does not support QoS mode gem-car or flow-car.

service port of the site information SVLAN 100 to GEM port 1 and map the service
port of the GOOSE packets SVLAN 101 to GEM port 2.
c.
4.

n
generated.

a.
Issue 01 (2016-04-29)
Add an ONU.
1663

Access Module

ID is 10.
actual conditions.
n


confirm the ONU.


NOTE
in batches to simplify the operation and increase the configuration efficiency.
For example, the preceding command can be modified as follows: huawei(config-ifgpon-0/3)#ont confirm 1 all sn-auth snmp ont-lineprofile-id 10 desc
5.

--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
Run state
: online
online normally.
Config state
: normal
Issue 01 (2016-04-29)
1664

Access Module
NOTE
6.

NOTE
not be configured.
a.

the ONU on the OLT.
192.168.50.20/24.
b.

192.168.50.2 mask 255.255.255.0 vlan 8
c.

port ID to 0, and customer VLAN (CVLAN) ID to 8. The rate of the inband service
port on the OLT is not limited. Therefore, use traffic profile 6 (default). To limit the
rate of the service port, run the traffic table ip command to add a traffic profile and
7.
8.
configure the ONU.
Configure a GPON type C protection group.

Set OLT_A as the active OLT and OLT_B as the standby OLT. Configure a protection
group on both OLT_A and OLT_B. Set the group member status on OLT_A to work and
the group member status on OLT_B to protect. After the setting, when the active OLT is
faulty, the system automatically switches to the standby OLT, ensuring service running.
Issue 01 (2016-04-29)

1665

Access Module
NOTE
For a working port, the protect group is enabled by default and you do not need to enable it any
more. For a protect port, the protect group is disabled by default. Run the protect-group enable
command to enable the protect group.
Run the protect-group member port 0/3/1 ont 1 role protect command on OLT_B to specify the
member type in a protect group to protect. Other configurations are the same as that on OLT_A.
huawei(config)#protect-group 0 protect-target gpon-uni-ont workmode dualparenting

huawei(protect-group-0)#protect-group enable//Determine whether to run this
command based on the type of the member type in a protect group on the port
9.

Configure the site information service port ID to 1, SVLAN ID to 200, GEM port ID to
1, and CVLAN ID to 100, and configure the GOOSE packets service port ID to 2,
SVLAN ID to 101, GEM port ID to 2, and CVLAN ID to 101. Rate limitation for
upstream and downstream packets is performed on the ONU instead of on the OLT.
The same port is used for transmitting the site information about the electrical power
system and GOOSE packets. Therefore, the 802.1p priority of each service needs to be
set. The priority of the site information about the electrical power system is lower than
that of GOOSE packets. Set the traffic profile index of the site information about the
electrical power system to 20 and the priority to 1; set the traffic profile index of GOOSE
packets to 21 and the priority to 5.
local-Setting
-----------------------------------------------TD Index
: 20
TD Name
Priority
: 1
Copy Priority
: Mapping Index
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Fix
: off
: color-blind
Color Policy
: dei
Referenced Status
: not used
local-Setting
-----------------------------------------------TD Index
: 21
TD Name
Priority
: 5
Copy Priority
: Mapping Index
Priority Policy
: local-pri
Issue 01 (2016-04-29)

1666

Access Module
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Fix
: off
: color-blind
Color Policy
: dei
Referenced Status
: not used
-----------------------------------------------huawei(config)#service-port 1 vlan 200 gpon 0/3/1 ont 1 gemport 1 multiservice user-vlan 100 rx-cttr 20 tx-cttr 20
10. Configure the bridging function for GOOSE packets.

a.

b.

To support the electrical GOOSE function, ONU_A must communicate with
ONU_B at Layer 2.
huawei(config-vlan-srvprof-20)#user-bridging
enable
c.

11. Configure queue scheduling.

services.
0-7 respectively.
cos7 7
12. Associated a protection group with an upstream Ethernet port.

huawei(config)#protect-group 0
huawei(protect-group-0)#uplink-monitor port 0/19/0
Issue 01 (2016-04-29)

1667

Access Module
NOTE
If an Ethernet link aggregation group is configured, the Ethernet port that is associated with the
dual-homing protection group must be the primary port in the aggregation group. Use the uplinkmonitor bfd command to associate the protection group with BFD sessions. For the configuration
of BFD, please refer to Configuring the BFD in OLT Configuration Guide.
13. Save the data.

huawei(config)#save
information about the electrical power system over Ethernet on ONU_A.
NOTE
1.

{ <cr>|service-port<0,4294967295> }:
Command:
telnet 192.168.50.2
Trying 192.168.50.2 ...
Connected to 192.168.50.2 ...
>>User name:root
>>User password:
2.
Configure the dual PON ports upstream mode.

When GPON type C dual-homing protect is configured, set the two PON uplink ports to
be in the active/standby mode. Run the display pon config command to query the
working mode of the two ports. The two ports work in active/standby mode by default.
Run the pon uplink-mode active-standby command to set the mode.
huawei(config)#pon uplink-mode active-standby//Determine whether to run this
command based on the dual PON ports upstream mode
3.

The same port is used for transmitting power distribution site information and GOOSE
packets. Therefore, the 802.1p priority of each service needs to be set. The priority of
power distribution site information is lower than that of GOOSE packets. Set the traffic
profile index of power distribution site information to 10 and the priority to 1; set the
traffic profile index of GOOSE packets to 11 and the priority to 6.
local-Setting
-----------------------------------------------TD Index
: 10
TD Name
Priority
: 1
Copy Priority
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Color Mode
: color-blind
Issue 01 (2016-04-29)

1668

Access Module
Referenced Status
: not used
local-Setting
-----------------------------------------------TD Index
: 11
TD Name
Priority
: 5
Copy Priority
Priority Policy
: local-pri
CIR
: off
CBS
: off
PIR
: off
PBS
: off
Color Mode
: color-blind
Referenced Status
: not used
------------------------------------------------
4.
Create VLANs.
5.
Add an uplink port to the VLANs.

Add uplink port 0/0/0 and 0/0/1 to the VLANs.
6.

For power distribution site information, create service port 2 with SVLAN 100 and
traffic profile 10. For GOOSE packets, create service port 3 with SVLAN 101 and traffic
profile 11.
7.
Configure the bridging function for GOOSE packets.

a.

b.

c.

d.
In ETH mode, disable the unknown multicast suppression function on the user side
interface and uplink port.
huawei(config-if-eth-0/1)#undo traffic-suppress 1 multicast
Issue 01 (2016-04-29)

1669

Access Module

huawei(config-if-eth-0/0)#undo traffic-suppress all multicast
8.
Set the queue scheduling mode to strict priority queue (PQ).

9.
Save the data.

huawei(config)#save
information about the electrical power system over Ethernet on ONU_B.
The procedure is the same as that on ONU_A except for the ID of the uplink VLAN used for
transmitting power distribution site information and IP address.
----End
Result
After the master station server queries the power distribution site information, the power
distribution site information is transmitted to the master station server.
Configuration File
Configure OLT_A.
vlan 101,200 smart
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.20 24
quit
mapping-mode vlan
commit
quit
interface gpon 0/3
quit
protect-group 0 protect-target gpon-uni-ont workmode dual-parenting
protect-group member port 0/3/1 ont 1 role work
protect-group enable
quit
Issue 01 (2016-04-29)

1670

Access Module

multicast-unknown policy service-port 2 transparent
commit
quit
protect-group 0
uplink-monitor port 0/19/0
quit
save
Configure ONU_A.
pon uplink-mode active-standby
vlan 100 smart
vlan 101 smart
port vlan 100 0/0 0-1
port vlan 101 0/0 0-1
service-port 2 vlan 100 eth 0/1/1 multi-service user-vlan untagged rx-cttr 10 txcttr 10
commit
quit
interface eth 0/1
undo traffic-suppress 1 multicast
quit
interface eth 0/0
undo traffic-suppress all multicast
quit
save
16.1.5 Configuration Example of Intelligently Collecting Power

Consumption Information over a Serial Port
An optical network unit (ONU) supports the serial port access service, and transmits the
service upstream to an optical line terminal (OLT) through a gigabit-capable passive optical
network (GPON) port. Then the OLT forwards the service data to upper-layer devices. This
process intelligently collects power consumption information in an electrical power system.
l
In an electrical power system, a large amount of meter data needs to be collected in

centralized mode in real time and sent to an automatic meter reading system (AMR)
server for monitoring and processing.
A user-side smart meter has a serial port, through which the ONU connects to the smart
meter.
Data is transmitted over a GPON network.
Issue 01 (2016-04-29)

1671

Access Module
Networking
Figure 16-7 shows the network diagram for transmitting information collected in centralized
mode in the smart grid over a serial port.
l
A terminal unit collects meter information and transparently transmits it to an AMR

server through an ONU serial port.
An ONU obtains serial port data through its serial port, encapsulates the serial port data
into User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) packets,
and transmits the packets upstream to an OLT through a GPON port. The OLT forwards
the packets to an upper-layer device and finally to the AMR server. After receiving the
UDP or TCP packets sent downstream from the AMR server, the ONU restores the UDP
or TCP packets to serial port data flows and transmits the data flows to terminal units.
Figure 16-7 Network diagram for transmitting information collected in centralized mode in
the smart grid over a serial port
Serial port
frame
Socket
communication
0/0/0/:VLAN 30
10.1.1.3/24
10.1.1.2/24
0/2/0
Electric
terminal
ONU
OLT
Master electric
station server
Figure 16-8 shows the flowchart for transmitting information collected in centralized mode in
the smart grid over a serial port.
Issue 01 (2016-04-29)

1672

Access Module
Figure 16-8 Flowchart for transmitting information collected in centralized mode in the smart
grid over a serial port
ONU
OLT
Start
Start
Add an ONU to the

OLT
Configure a Layer 3
interface
and the ONU
Configure serial port

attributes

ONU
Configure a serial port

connection
Save
End
End
Device
Configuration Description
OLT
1. Add an ONU to the OLT.
You can configure the ONU only after

the ONU.
You can log in to the ONU from the

OLT and configure the ONU only after
the inband management channel
available.
the ONU.
The meter data collected by the ONU

needs to be transparently transmitted to
the AMR server on the upper-layer
network through the OLT.
1. Configure a Layer 3
interface.
The data collected by an ONU needs to

carry IP addresses so that it can be
transmitted over an IP network.
2. Configure serial port

attributes.
An ONU can communicate with a

terminal unit properly only when they
have the same serial port attributes.
3. Configure a serial port

connection.
The data collected by an ONU is

converted between serial port lines and
the Ethernet network through this serial
port connection.
ONU
Issue 01 (2016-04-29)

1673

Access Module
Data Plan
Table 16-9 provides the data plan for the optical line terminal (OLT) and Table 16-10
provides the data plan for the ONU.
Table 16-9 Data plan for the OLT
Configuration Item
Data
Virtual local area network

(VLAN)

l Inband management VLAN 8 with VLAN type
smart
l Service VLAN 30 with VLAN type smart
IP address
GPON service board
l Port ID: 0/3/1

l ONT ID: 1
l ONU serial number (SN): 48575443E6D8B541
Dynamic bandwidth allocation

(DBA) profile
l Profile name: SerialAccess

l Type: type3
l ONU line profile 10 bound to DBA profile
SerialAccess
ONU line profile
l GPON encapsulation mode (GEM) port ID: 0

(inband management service port ID)
l GEM port ID: 1 (transparent transmission service
port ID)
l Transmission container (T-CONT) ID: 5
ONU management mode
Simple Network Management Protocol (SNMP)
Table 16-10 Data plan for the ONU

Configuration Item
Data
Remarks
Attributes of the inband

management interface
l VLAN ID: 8
l Inband management IP address:
192.168.50.2/24
l Index of a traffic profile: 6 (default
value)
Issue 01 (2016-04-29)

1674

Access Module
Configuration Item
Data
Remarks
Attributes of the VLAN

Layer 3 interface
The IP address of
the master station
server is 10.1.1.2.
l VLAN ID: 30
l IP address of the VLAN Layer 3
interface: 10.1.1.3
Attributes of the serial

port
l Serial port ID: 0/2/0

l Working mode: rs485
l Baud rate: 2400 bit/s
The default baud

rate specified in the
DL645-2007 MultiFunction WattHour Meter
Communication
Protocol is 2400
bit/s.
Ensure that the
serial port attributes
are the same as
those on the
interconnected
terminal unit.
Connections of the
serial port
l Connection ID: 1
l Transmission mode: tcp-server
l Local port ID: 3000
l Serial port frame type: none
If a remote port ID
is not specified on
an ONU, the
system obtains the
port ID based on
the connection
packets received on
the serial port from
the remote port.
NOTE
When specifying a
remote port ID on
an ONU, ensure that
it is the same as the
ID of the source port
sending connection
packets.
Procedure
1.
Create a service VLAN and add an uplink port to it.

The ID of the service VLAN is 30 and the uplink port added to service VLAN 30 is
0/19/0.
2.
Issue 01 (2016-04-29)
(Optional) Configure uplink aggregation.

1675

Access Module
This topic uses a single uplink port as an example. If there are multiple uplink ports,
configure uplink aggregation.
3.

profile.
DBA profile: describes GPON traffic parameters. A T-CONT is bound to a DBA

profile to allocate dynamic bandwidths, improving upstream bandwidth usage.
Line profile: describes the binding between T-CONTs and DBA profiles, quality of
service (QoS) mode of a service port, and mapping between GEM ports and ONU
services.
Service profile: provides service configuration channels for an ONU that is

managed through an optical network terminal management and control interface
(OMCI).
Alarm profile: contains a series of alarm thresholds to measure and monitor the
performance of activated ONT lines. When a statistical value reaches the threshold,
a PON board on the OLT notifies the OLT of this event and sends an alarm to a log
host and the network management system (NMS).
a.

Run the display dba-profile command to query existing DBA profiles in the
system. If the existing DBA profiles in the system cannot meet site requirements,
run the dba-profile add command to add a DBA profile.
Set the DBA profile parameters as follows: profile name SerialAccess, type Type3,
assured bandwidth 20 Mbit/s, and maximum bandwidth 50 Mbit/s.
huawei(config)#dba-profile add profile-name SerialAccess type3 assure
20480 max 51200
b.

Add GPON ONU line profile 10 and bind T-CONT 5 to DBA profile SerialAccess.
Then the T-CONT can provide flexible DBA solutions based on different DBA
profile configurations.
huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name SerialAccess
Add GEM port 0 to carry management service streams and GEM port 1 to carry
service flows for collecting information in the smart grid. Bind GEM ports 0 and 1
to T-CONT 5. Set the QoS mode to priority-queue (default mode) and the queue
priority to 3.
Configure the mapping mode between GEM ports and ONU services to VLAN (default
mode), map service flows of management VLAN 8 to GEM port 0, and map service
flows of service VLAN 30 to GEM port 1.
After the configuration is complete, run the commit command to make the configuration
take effect.

Issue 01 (2016-04-29)

1676

Access Module
4.
The default alarm profile is GPON alarm profile 1, in which each alarm threshold is
0, indicating that no alarm is reported.
This topic uses the default alarm profile. Therefore, you do not need to configure
the profile.
If necessary, run the gpon alarm-profile add command to add a GPON alarm
profile to measure and monitor the performance of activated ONT lines.
Add an ONU to the OLT.

The ONU connects to a GPON port on the OLT using an optical fiber. You can configure
services only after adding the ONU to the OLT.
a.
Add the ONU.

Connect the ONU to GPON port 0/3/1 using an optical splitter. The ONU ID is 1,
the SN is 48575443E6D8B541, the management mode is SNMP, and the ID of the
bound line profile is 10.
You can use either of the following methods to add an ONU:
n
Add an ONU in offline mode. If you have obtained the password or SN of an

ONU, run the ont add command to add it in offline mode.
Use the ONU automatic discovery function. If the password or SN of an ONU

is unknown, run the port ont-auto-find command in GPON mode to enable
the ONU automatic discovery function. Then run the ont confirm command to
confirm the automatically discovered ONU.
To add an ONU in offline mode, run the following commands:

To add an ONU using the ONU automatic discovery function, run the following
commands:
//This command displays the information about all ONUs connected to
the GPON port using an optical splitter.
NOTE
If a port on the OLT connects to multiple ONUs of the same type and the port on the OLT is
bound to the same line profile or service profile, you can add ONUs in batches by
confirming the automatically discovered ONUs in batches. This function simplifies
operations and improves configuration efficiency.
For example, in the preceding information, huawei(config-if-gpon-0/3)#ont confirm 1 ontid
1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 desc
MA5621_0/3/1/1_lineprofile10 can be changed to huawei(config-if-gpon-0/3)#ont confirm
1 all sn-auth snmp ont-lineprofile-id 10 desc MA5621_0/3/1_lineprofile10.
5.
Confirm that the ONU goes online properly.

After adding the ONU, run the display ont info command to query the ONU status.
--------------------------------------------------------------------F/S/P
: 0/3/1
ONT-ID
: 1
Control flag
: active
//The ONU has been activated.
Issue 01 (2016-04-29)

1677

Access Module
Run state
: online
Config state
: normal
//The ONU configuration status has been
restored.
...//The follow-up terminal display is omitted.
If the ONU status is abnormal, the ONU cannot be in the up state, or the ONU does not
meet requirements, check the ONU status based on the preceding information.
If Control flag is deactive, run the ont activate command in GPON port mode to
activate the ONU.
If the ONU cannot be in the up state (Run state is offline), check materials and
lines because the physical line may be cut or the optical module may be damaged.
If the ONU status is abnormal (Config state is failed), ONU capabilities cannot
support the configured ONU capability set. Then run the display ont failedconfiguration command in diagnosis mode to check failed configuration items and
failure causes. Then, rectify the fault based on site requirements.
NOTE
If an ONT supports only four queues, the values 4 through 7 of the priority-queue parameter in
the gem add command are invalid, which causes Config state to be failed.
6.
Configure a management channel from the OLT to the ONU.

NOTE
A management channel needs to be configured only when the OLT remotely manages the ONU
using SNMP.
a.
Configure the inband management VLAN for the OLT and set the inband
management IP address.
To log in to the ONU from the OLT and configure the ONU remotely, configure the
inband management VLAN for the OLT and the ONU and set the inband
Configure inband management VLAN 8 and set the inband management IP address
to 192.168.50.10/24.
b.
Configure the inband management VLAN for the ONU and set the inband
Set the static IP address of the ONU to 192.168.50.2/24 and management VLAN 8
(the same as the management VLAN for the OLT).
192.168.50.2 mask 255.255.255.0 vlan 8
c.

port ID to 0, and customer VLAN ID to 8. The rate of the inband service port on the
OLT is not limited. Therefore, use traffic profile 6 (default profile). To limit the rate
of the service port, run the traffic table ip command to add a traffic profile and
Issue 01 (2016-04-29)

1678

Access Module
7.
8.
Verify that the management channel between the OLT and the ONU is available.
Run the ping 192.168.50.2 command on the OLT to check the connectivity to the
ONU. If the OLT can receive ICMP ECHO-REPLY packets sent from the ONU, the
OLT is connected to the ONU.
Run the telnet 192.168.50.2 command to log in to the ONU and configure it.

Configure the ID of the service port for the power distribution site information to 1,
service VLAN ID to 30, and customer VLAN ID to 30. In addition, the traffic of
upstream and downstream packets is not limited. Therefore, use traffic profile 6 (default
profile).
Ensure that the customer VLAN is the same as the Layer 3 interface VLAN of the ONU.
9.

Use the 3PQ+5WRR queue scheduling. PQ is the acronym for priority queuing and
WRR is the acronym for weighted round robin. Queues 0-4 use the WRR mode, with the
weights of 10, 10, 20, 20, and 40 respectively. Queues 5-7 use the PQ mode.
Queue scheduling is a global configuration. Specifically, you need to configure queue
scheduling only once on the OLT. Then the configuration takes effect globally. In followup operations, you do not need to configure queue scheduling repeatedly when
configuring other services.
0-7.
If a board supports only four queues, the mapping between 802.1p priorities and queue
IDs is as follows: Priorities 0 and 1 map queue 1. Priorities 2 and 3 map queue 2.
Priorities 4 and 5 map queue 3. Priorities 6 and 7 map queue 4.
cos7 7
10. Save the data.

huawei(config)#save

NOTE
The management VLAN and the management IP address have been configured. Therefore, you can run
the telnet 192.168.50.2 command on the OLT to log in to the ONU and configure the ONU. You can
also log in to the ONU through a serial port and configure it.
1.
Log in to the ONU and configure it.

On the OLT, use the management IP address of the ONU to log in to the ONU in telnet
mode. The user name is root (default) and its default password is admin123.
{ <cr>|service-port<0,4294967295> }:
Command:
telnet 192.168.50.2
Trying 192.168.50.2 ...
Connected to 192.168.50.2 ...
>>User name:root
>>User password:
Issue 01 (2016-04-29)

1679

Access Module
2.
Configure a VLAN Layer 3 interface.

Configure the service VLAN ID to 30 and VLAN type to smart, add uplink port 0/0/0 to
VLAN 30, and set the IP address of the Layer 3 interface to 10.1.1.3.
3.
Configure the serial port working mode.

Configure the serial port working mode to RS485, which is the same as the working
mode of the serial port on the terminal unit.
huawei(config)#interface serial 0/2
huawei(config-if-serial-0/2)#port mode 0 rs485
4.
(Optional) Configure serial port attributes.

The default value of the serial port baud rate is 2400 bit/s. Configure the serial port baud
rate to be the same as the baud rate of the serial port on the terminal unit.
huawei(config-if-serial-0/2)#port config 0 baudrate 2400
5.
Configure a serial port connection.

Configure the data transmission mode to TCP Server, local end IP address for the
TCP/IP connection to 10.1.1.3, local port ID to 3000, peer end IP address for the TCP/IP
connection to 10.1.1.2, and serial port frame type to none.
huawei(config-if-serial-0/2)#quit
huawei(config)#serialop-connection 1 port 0/2/0 working-mode tcp-server localaddress 10.1.1.3 local-port 3000 peer-address 10.1.1.2 frame-type none
6.
Save the data.

huawei(config)#save
----End
Result
1.
Run the ping command to verify that the route between the ONU and the master station
server is available.
2.
Run the display serialop-connection command to query whether the status of the serial
port TCP/IP connection is established to determine whether the ONU and the master
station server communicate with each other properly.
NOTE
If working-mode of the serial port connection is TCP-Client, run the display serialopconnection command to query whether the status of the serial port TCP/IP connection is
connected to determine whether the ONU and the master station server communicate with each
other properly.
If working-mode of the serial port connection is UDP, run the display serialop-connection
statistics command to query the number of frames received on or sent from the serial port to
determine whether the ONU and the master station server communicate with each other properly.
Configuration File
Configure the OLT.
vlan 30 smart
port vlan 30 0/19 0
Issue 01 (2016-04-29)

1680

Access Module
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.10 24
quit
dba-profile add profile-name SerialAccess type3 assure 20480 max 51200
tcont 5 dba-profile-name SerialAccess
mapping-mode vlan
commit
quit
interface gpon 0/3
quit
save
Configure the ONU.

vlan 30 smart
port vlan 30 0/0 0
interface vlanif 30
quit
interface serial 0/2
port mode 0 rs485
port config 0 baudrate 2400
quit
serialop-connection 1 port 0/2/0 working-mode tcp-server local-address
10.1.1.3 local-port 3000 peer-address 10.1.1.2 frame-type none
save
Issue 01 (2016-04-29)

1681

Access Module
17
17 OptiCable EoC Bandwidth Configuration
OptiCable EoC Bandwidth

Configuration
About This Chapter

The OptiCable solutions mainly apply to two scenarios: bidirectional restructuring for
existing cable TV users, and cable TV and broadband service access over coaxial cables for
new users. The radio frequency (RF) access can be deployed in a network to support both
passive optical network (PON) and ethernet over coaxial cable (EoC) services. Such a
network scenario supports high-speed Internet (HSI) and Internet protocol television (IPTV)
services, meeting broadcast and television services requirements.
17.1 Configuring Example of EoC Services (OLTs Use GPON Access)
Ethernet over coaxial cable (EoC) is a key technology for the next-generation broadcast and
TV networks. This technology can be used to reconstruct the existing cable networks to
bidirectional broadband network to provide bandwidth services such as high-speed Internet
(HSI) and Internet protocol television (IPTV). This topic uses the MA5631 as an optical
network unit (ONU) to describe how to configure EoC broadband services.
Issue 01 (2016-04-29)

1682

Access Module
17.1 Configuring Example of EoC Services (OLTs Use

GPON Access)
Ethernet over coaxial cable (EoC) is a key technology for the next-generation broadcast and
TV networks. This technology can be used to reconstruct the existing cable networks to
bidirectional broadband network to provide bandwidth services such as high-speed Internet
(HSI) and Internet protocol television (IPTV). This topic uses the MA5631 as an optical
network unit (ONU) to describe how to configure EoC broadband services.
Users can subscribe to broadcast and TV services, Internet access services, and interaction
services. Broadcast and TV services can be provided after the ONU hardware is connected
and the service channel is set up. No configuration is required. This topic only describes how
to configure the Internet access and interaction services.
The CNU uses the HG7022, providing two LAN ports. Port 1 is connected to a PC for
providing the Internet access service and port 2 is connected to a set top box (STB) for
providing a return channel for the interactive TV service. The CNU differentiates services by
port. Virtual local area networks (VLANs) are not switched on the optical line terminal (OLT)
and services are transparently transmitted on the OLT.
l
Users access the Internet in Point-to-Point Protocol over Ethernet (PPPoE) dialup mode.
Policy Information Transfer Protocol (PITP) is enabled to protect user accounts against
theft and roaming.
NOTE
In Dynamic Host Configuration Protocol (DHCP) dialup mode, you can configure anti-theft and
roaming for user accounts. For details, see Configuring Anti-Theft and Roaming for User Accounts
Using DHCP.
Networking
Figure 17-1 shows a network diagram of the EoC broadband service.
Figure 17-1 Network diagram of the EoC broadband service
Issue 01 (2016-04-29)

1683

Access Module
Data Plan
Table 17-1 provides the data plan for the OLT, and Table 17-2 provides the data plan for the
ONU.
Table 17-1 Data plan for configuring the EoC broadband service-OLT side
Item
Data
VLAN
Inband management VLAN: smart VLAN 8

SVLAN: smart VLAN 100 with the attribute Common
SVLAN: smart VLAN 101 with the attribute Common
IP address
GPON service board
Port ID: 0/3/1

ONU ID: 1
ONU authentication mode: SN
ONU SN: 48575443E6D8B541
DBA profile

Type: type3
ONU line profile
Profile ID: 10, bound to the DBA profile named PrivateLine

GEM port IDs: 0, 1, and 2
T-CONT ID: 5
ONU management
mode
SNMP
Table 17-2 Data plan for configuring the EoC broadband service-ONU side
Item
Data
CNU
l CNU ID: 0
l CNU MAC address: 00B0-5240-0003
l CNU SN: hwhw-12341234
l CNU line profile: 1
VLAN
Inband management VLAN: smart VLAN 8, adding GPON upstream

port 0/0/0 to this VLAN
HSI SVLAN: smart VLAN 100 with the attribute Stacking, adding
GPON upstream port 0/0/0 to the VLAN
Interactive TV SVLAN: smart VLAN 101 with the attribute Common,
adding GPON upstream port 0/0/0 to the VLAN
IP address
Issue 01 (2016-04-29)

1684

Access Module
Procedure
1.

Create smart VLANs 100 and 101, their attributes are common, and add upstream port
0/19/0 to the VLANs.
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
2.
100-101 smart
attrib 100 common
attrib 101 common
vlan 100-101 0/19 0

In this example, a single upstream port is used. In the case of multiple upstream ports,
configure upstream link aggregation. For details, see "Configuring the Link Aggregation
of Upstream Ethernet Port".
3.

profile.
bandwidth usage.
ONU that is managed using optical network terminal management and control
interface (OMCI).
NMS.
a.
Add a DBA profile.

Run the display dba-profile command to query the DBA profiles in the system. If
the DBA profiles in the system do not meet requirements, run the dba-profile add
Configure the profile name to PrivateLine, profile type to Type3, assured bandwidth
to 20 Mbit/s, and maximum bandwidth to 50 Mbit/s.
huawei(config)#dba-profile add profile-name PrivateLine type3 assure
20480 max 51200
b.

PrivateLine. In this way, the T-CONT can provide flexible DBA solutions based on
transmitting HSI traffic streams and GEM port 2 for transmitting interactive TV
Issue 01 (2016-04-29)

1685

Access Module
traffic streams. Bind GEM port 0, GEM port 1 and GEM port 2 to T-CONT 5.
Configure the QoS mode to priority-queue (default) and the queue priority to 3.
NOTE
1. To change the QoS mode, run the qos-mode command to configure the QoS mode to gem-car
or flow-car, and run the gem add command to configure the ID of the traffic profile bound to
the GEM port.
2. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car, traffic
profile 6 is bound to the port by default (no rate limitation); when the QoS mode is gem-car,
traffic profile 6 is bound to the port by default (no rate limitation).

(default), map the service port of management VLAN 8 to GEM port 0, map the service
port of HSI SVLAN 100 to GEM port 1 and map the service port of the interactive TV
SVLAN 101 to GEM port 2.
After the configuration is complete, run the commit command to make the configured
parameters take effect.
4.
generated.
Run the gpon alarm-profile add command to add an alarm profile, which is used
for monitoring the performance of an activated ONU line.

The ONU is connected to the GPON port of the OLT using an optical fiber. You can
a.
Add an ONU.
Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the serial number (SN) is
ID is 10.
Add an ONU in either of the following two methods based on site requirements:
n

Find an ONU automatically: If the password or SN of an ONU is unknown,

run the port ont-auto-find command in GPON mode to enable the ONU autofind function of the GPON port. Then run the ont confirm command to
confirm the ONU.

Issue 01 (2016-04-29)

1686

Access Module


//After this command is executed, the information about all the ONUs
connected to
//the GPON port using the optical splitter is displayed.
-----------------------------------------------------------Number
: 1
F/S/P
: 0/3/1
Ont SN
: 48575443E6D8B541
Password
:
VenderID
: HWTC
Ont Version
: MA5631
Ont EquipmentID
: SmartAX MA5631
Ont autofind time
: 2011-09-10 11:20:16
-----------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth
48575443E6D8B541 snmp ont-lineprofile-id
NOTE
If multiple ONUs of the same type are connected to a port and the same line profiles or service
profiles are bound to the ONUs, add these ONUs in batches by confirming the auto-found ONUs
in batches. The adding simplifies the operation and increases the configuration efficiency.
Therefore, the preceding command can be modified to: huawei(config-if-gpon-0/3)#ont confirm
1 all sn-auth snmp ont-lineprofile-id 10 desc MA5631_0/3/1_lineprofile10.
5.
Confirm that the ONU goes online properly.

After an ONU is added, run the display ont info command to query the ONU status.
Ensure that Control flag of the ONU is active, Run State is online, and Config state is
normal.
--------------------------------------------------------------------F/S/P
:
0/3/1
ONT-ID
:
1
Control flag
: active
activated.
Run state
: online
online properly.
Config state
: normal
If the ONU configuration fails or the ONU fails to be up, check the ONU state by
referring to the above-mentioned descriptions.
Issue 01 (2016-04-29)
If Control flag is deactive, run the ont activate command in GPON port mode to
activate the ONU.
If Run state is offline, the ONU fails to be up. The physical line may be broken or
the optical module may be damaged. Check both the materials and line.
If Config state is failed, the ONU configuration fails. The ONU capability set
outmatches the actual ONU capabilities. Run the display ont failed-configuration
1687

Access Module
command in diagnosis mode to check the failed configuration item and the failure
cause. Then rectify the fault according to actual conditions.
NOTE
If an ONT supports only four queues, the values of 47 of the priority-queue parameter in the
gem add command are invalid. After configuration recovers, Config state will be failed.
6.

NOTE
The management channel needs to be configured only when the OLT remotely manages the ONU using
the SNMP protocol. When the OLT remotely manages the ONU using the OMCI, the management
channel need not be configured.
a.

To remote log in to the ONU and configure the ONU from the OLT, configure the
inband management VLANs and IP addresses of the OLT and the ONU on the OLT.
Create management VLAN 8 and set the inband management IP address to
192.168.50.1/24.
b.

Set the static IP address of the ONU to 192.168.50.2/24 and the management
192.168.50.2 mask 255.255.255.0 vlan 8
c.

Set the management service port ID to 0, management VLAN ID to 8, GEM port ID
to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT is not
limited. Therefore, use traffic profile 6 (default). To limit the rate of the service
service port.
7.
8.
ONU. ICMP ECHO-REPLY packets from the ONU should be received.
You can remote log in to the ONU from the OLT to perform the configuration.

Configure the port ID of the HSI service to 1, SVLAN ID to 100, GEM port ID to 1,
CVLAN ID to 100, and configure the port ID of the interactive TV service to 2, SVLAN
ID to 101, GEM port ID to 2, CVLAN ID to 101. Rate limitation for upstream and
downstream packets is performed on the MDU instead of on the OLT. Therefore, use
traffic profile 6 (default). To limit the rate of the service port, run the traffic table ip
command to add a traffic profile and bind it to the service port.
Issue 01 (2016-04-29)

1688

Access Module

9.

Use the 3PQ+5WRR queue scheduling. Queues 0-4 use the WRR mode, with the
weights of 10, 10, 20, 20, and 40 respectively; queues 5-7 use the PQ mode. The service
priority is 4, using the WRR scheduling.
Queue scheduling is a global configuration. Configure queue scheduling on the OLT
only once, and then the configuration takes effect globally. In subsequent service
configurations, you do not need to configure queue scheduling.
0-7 respectively.
For the service board that supports only four queues, the mappings between 802.1p
priorities and queue IDs are as follows: priorities 0 and 1 map queue 1; priorities 2 and 3
cos7 7
10. Save the data.

huawei(config)#save
Step 2 Configure the ONU to provide services automatically.

The CNU can automatically provide services after going online. No additional service
configuration operation is required and therefore the service provisioning efficiency is
improved.
NOTE
1.

On the OLT, you can remote log in to the ONU to perform the configuration. The user
name is root (default) and the password is mduadmin (default).
2.
Confirm an automatically discovered CNU.

Services are automatically provided after the CNU is automatically discovered.
huawei(config)#interface eoc 0/1
huawei(config-if-eoc-0/1)#cnu auto confirm all
3.
Create an SVLAN.
Set the VLAN ID of the HSI service to 100, the VLAN type to smart, and the attribute to
stacking, and add uplink port 0/0/0 to this VLAN. Set the VLAN ID of the interactive
TV service to 101, the VLAN type to smart, and the attribute to common, and add uplink
port 0/0/0 to this VLAN.
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
4.
Issue 01 (2016-04-29)
100-101 smart
attrib 100 stacking
attrib 101 common
vlan 100-101 0/0 0
Create a profile for automatic service provisioning by the CNU.

1689

Access Module
Configure the HSI service profile ID to 1, service VLAN ID to 100, CNU port ID to 1,
and traffic profile to 3.
huawei(config)#cnu auto-service-profile add 1 vlan 100 eth 1 inbound traffictable index 3 outbound traffic-table index 3
Configure the interactive TV service profile ID to 1, service VLAN ID to 100, CNU port
ID to 1, and traffic profile to 3.
huawei(config)#cnu auto-service-profile add 1 vlan 101 eth 2 inbound traffictable index 4 outbound traffic-table index 4
Step 3 Configure the ONU to provide services through manual operations.

Users must manually configure services after the CNU goes online.
NOTE
1.

On the OLT, you can remote log in to the ONU to perform the configuration. The user
name is root (default) and the password is mduadmin (default).
2.
Optional: Configure a line profile for the EoC head end module.
A line profile is generally not required for the EoC head end module because the default
line profile 1 is automatically bound to the head end module port. For details about how
to customize a line profile, see Configuration Guide of the ONU.
The default profile is used in this example.
3.
Optional: Configure a CNU line profile.

A CNU line profile is generally not required because the default line profile 1 is
automatically bound to the CNU. For details about how to customize a line profile, see
Configuration Guide of the ONU.
The default profile is used in this example.
4.
Add a CNU to an ONU.

Assume that a CNU ID is 0, the CNU SN is hwhw-12341234, the bound line profile is 1,
the description added to the CNU is huaweicnu, and the CNU alarm reporting function is
disabled by default. To connect this CNU to EoC head end module port 0/1/0, you can
use two methods: add a CNU offline and confirm an automatically discovered CNU.
Add an CNU offline.

If the CNU SN is known, run the cnu add command to add the CNU offline.
huawei(config-if-eoc-0/1)#cnu add 0 0 sn-auth hwhw-12341234 lineprofileid 1
desc huaweicnu
huawei(config-if-eoc-0/1)#quit
Confirm an automatically discovered CNU.

If the CNU SN is unknown, run the cnu auto confirm command in EoC mode to
enable the CNU automatic discover function on the EoC port.
huawei(config-if-eoc-0/1)#cnu auto confirm all
5.
Issue 01 (2016-04-29)
Create an SVLAN.
1690

Access Module
Set the VLAN ID of the HSI service to 100, the VLAN type to smart, and the attribute to
stacking, and add uplink port 0/0/0 to this VLAN. Set the VLAN ID of the interactive
TV service to 101, the VLAN type to smart, and the attribute to common, and add uplink
port 0/0/0 to this VLAN.
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#vlan
huawei(config)#port
6.
100-101 smart
attrib 100 stacking
attrib 101 common
vlan 100-101 0/0 0
Configure the traffic profile.

Run the display traffic table ip command to query the traffic profiles in the system. If
the traffic profiles in the system do not meet requirements, run the traffic table ip
command to add a traffic profile. This example uses the default traffic profile.
huawei(config)#display traffic table ip from-index
0
{ <cr>|toindex<K> }:
Command:
display traffic table ip from-index
0
---------------------------------------------------------------------------TID CIR(kbps) CBS(bytes) PIR(kbps) PBS(bytes) Pri Copy-policy
PriPolicy
---------------------------------------------------------------------------0
512
18384
1024
36768
6 tagpri
1
1024
34768
2048
69536
0 tagpri
2
2048
67536
4096
135072
0 tagpri
3
4096
133072
8192
266144
4 tagpri
4
8192
264144
16384
528288
4 tagpri
5
16384
526288
32768
1024000
4 tagpri
6
off
off
off
off
0 tagpri
---------------------------------------------------------------------------Total Num : 7
7.
Create a service port and bind it to a traffic profile.

VLAN tags are switched for the HSI service. The outer VLAN tag, or SVLAN tag,
identifies OLT+PON port+services, and the inner VLAN tag, or CVLAN tag, identifies
CNU+ONU ID.
huawei(config)#service-port 1 vlan 100 eoc 0/1/0 cnu 0 eth 1 multi-service
uservlan untagged inbound traffic-table index 3 outbound traffic-table index 3
CVLAN to SVLAN tag switching is performed for the interactive TV service. The SVLAN identifies services.
huawei(config)#service-port 2 vlan 101 eoc 0/1/0 cnu 0 eth 2 multi-service
uservlan untagged inbound traffic-table index 4 outbound traffic-table index 4
8.
Configure the user account security.

The PITP P mode can be enabled to protect the user account against theft and roaming.
Issue 01 (2016-04-29)

1691

Access Module
NOTE
For details about the PITP configuration for the user account security, see Configuring Anti-Theft and
Roaming of User Account Using PITP.
9.
Save the data.

huawei(config)#save
----End
Result
l
The users connected to port 1 on the CNU can use the HSI service.
The users connected to port 2 on the CNU can use the interactive TV service.
NOTE
The users connected to LAN ports can use the Internet access service or interactive TV service based on
requirements, regardless of whether the CNU provides two or four ports. The procedure for configuring the
EoC broadband services on the CNU with four ports is the same as the preceding procedure for configuring
the EoC broadband services on the CNU with two ports.
Configuration File
Configure the OLT.
vlan 100-101 smart
vlan attrib 100 common
vlan attrib 101 common
port vlan 100-101 0/19 0
vlan 8 smart
port vlan 8 0/19 0
interface vlanif 8
ip address 192.168.50.1 24
quit
dba-profile add profile-name PrivateLine type3 assure 20480 max 51200
tcont 5 dba-profile-name PrivateLine
mapping-mode vlan
commit
quit
interface gpon 0/3
display ont autofind 1
ont alarm-profile 1 1 profile-id 1
save
Configure the ONU to provide services automatically.

interface eoc 0/1
cnu auto confirm all
Issue 01 (2016-04-29)

1692

Access Module
vlan 100-101 smart
port vlan 100-101 0/0 0
cnu auto-service-profile add
outbound traffic-table index
cnu auto-service-profile add
outbound traffic-table index
1 vlan 100 eth 1 inbound traffic-table index 3

3
1 vlan 101 eth 2 inbound traffic-table index 4
4
Configure the ONU to provide services through manual operations.

interface eoc 0/1
cnu add 0 0 sn-auth hwhw-12341234 lineprofile-id 1
desc huaweicnu
quit
vlan 100-101 smart
port vlan 100-101 0/0 0
commit
quit
service-port 1 vlan 100 eoc 0/1/0 cnu 0 eth 1 multi-service uservlan untagged inbound traffic-table index 3 outbound traffic-table index 3
service-port 2 vlan 101 eoc 0/1/0 cnu 0 eth 2 multi-service uservlan untagged inbound traffic-table index 4 outbound traffic-table index 4
pitp enable pmode
save
Issue 01 (2016-04-29)

1693

Access Module
18
18 IPv6 Configuration
IPv6 Configuration
About This Chapter

18.1 IPv6 Networking
The FTTH IPv6 solution is part of the Huawei fixed broadband solution for IPv6, supporting
the access of the IPv6 high speed Internet (HSI) service and IPTV service.
18.2 Configuration Difference Between IPv6 and IPv4
The main configuration difference between the IPv6 and IPv4 services lies in the
configurations on the OLT, MDU, and ONT.
18.3 Configuring IPv6 Services in the FTTB/C (No HGWs) Scenario
This section describes the methods for configuring IPv6 services in the FTTB/C (No HGWs)
scenario.
18.4 Configuring IPv6 Services in the FTTB+HGW Scenario
This section describes the methods for configuring IPv6 services in the FTTB+HGW
scenario.
18.5 Configuring IPv6 Services in the FTTH (Bridging ONT) Scenario
This section describes the methods for configuring IPv6 services in the FTTH (bridging ONT)
scenario.
18.6 Configuring IPv6 Services in the FTTH (Gateway ONT) Scenario
This section describes the methods for configuring IPv6 services in the FTTH (gateway ONT)
scenario.
Issue 01 (2016-04-29)

1694

Access Module
18.1 IPv6 Networking

The FTTH IPv6 solution is part of the Huawei fixed broadband solution for IPv6, supporting
the access of the IPv6 high speed Internet (HSI) service and IPTV service.
The Huawei FBB solution for IPv6 includes the following scenarios based on service access
modes. Since "HSI scenario: IPv4/IPv6 DS+PPPoE+L2TP" and "HSI scenario: IPv4/IPv6 DS
+NAT+PPPoE" in this solution are the same as those in the FTTx solution, they are not
elaborated in this document.
l
HSI scenario: IPv4/IPv6 DS+NAT+PPPoE
HSI scenario: IPv4/IPv6 DS+NAT+IPoE
HSI scenario: IPv4/IPv6 DS+PPPoE+L2TP
HSI scenario: DS-Lite+PPPoE
IPTV scenario: IPv4/IPv6 DS+IPoE
IPTV scenario: IPv4/IPv6 DS+PPPoE
The access network devices still use IPv4, instead of IPv6, to implement voice services.
Table 18-1 lists how the access network devices process different services in different IPv6
networking scenarios. For details, see the data planning and configuration for each scenario.
Table 18-1 IPv6 networking scenarios
Netwo
rk
Topol
ogy
Servic
e
Scheme
OLT
ONU
FTTB/
C (no
HGW)
HSI
IPv4/IPv6
DS+NAT
+PPPoE
Layer 2 forwarding
Layer 2 forwarding
DS-Lite
+PPPoE
Not supported
Not supported
IPv4/IPv6
DS+IPoE
No such networking
scenario
No such networking
scenario
Layer 2 forwarding
Layer 2 forwarding
IPv4/IPv6
DS+NAT
+IPoE
IPTV
IPv4/IPv6
DS
+PPPoE
FTTB
+HGW
Issue 01 (2016-04-29)
HSI
IPv4/IPv6
DS+NAT
+PPPoE

1695

Access Module
Netwo
rk
Topol
ogy
Servic
e
Scheme
OLT
ONU
IPv4/IPv6
DS+IPoE
It is recommended to
establish a multicast service
channel from the OLT to
the ONU to transparently
transmit multicast service
packets at Layer 2.
It is recommended to use
the ONU to duplicate IPv6
multicast flows.
IPv4/IPv6
DS
+PPPoE
Not recommended
Not recommended
IPv4/IPv6
DS+NAT
+PPPoE
Layer 2 forwarding
Layer 2 forwarding
DS-Lite
+PPPoE
Not supported
Not supported
IPv4/IPv6
DS+IPoE
The OLT is used to

duplicate IPv6 multicast
flows.
Bridge forwarding
IPv4/IPv6
DS
+PPPoE
Not recommended
Not recommended
IPv4/IPv6
DS+NAT
+PPPoE
Layer 2 forwarding
To enable IPv4/IPv6 DS on
the ONT, enable IPv4 and
IPv6 concurrently on the
WAN port.
IPv4/IPv6
DS+NAT
+IPoE
DS-Lite
+PPPoE
IPTV
FTTH
(bridgi
ng
ONT)
HSI
IPv4/IPv6
DS+NAT
+IPoE
IPTV
FTTH
(gatew
ay
ONT)
HSI
IPv4/IPv6
DS+NAT
+IPoE
DS-Lite
+PPPoE
Issue 01 (2016-04-29)

If DS-Lite is enabled on the

ONT, enable IPv6 and DSLite on the WAN port.
1696

Access Module
Netwo
rk
Topol
ogy
Servic
e
Scheme
OLT
ONU
IPTV
IPv4/IPv6
DS+IPoE
The OLT is used to

duplicate IPv6 multicast
flows.
Bridge forwarding
IPv4/IPv6
DS
+PPPoE
Not recommended
Not recommended
NOTE
In the "IPv4/IPv6 DS+PPPoE" scheme of each networking scenario, the broadband remote access server
(BRAS), instead of the access network devices, duplicates multicast flows, so that this scheme does not
support large scale application and is therefore not recommended.
18.2 Configuration Difference Between IPv6 and IPv4

The main configuration difference between the IPv6 and IPv4 services lies in the
configurations on the OLT, MDU, and ONT.
18.2.1 Configuration Differences Between IPv6 and IPv4 on the

OLT
Configurations between IPv6 and IPv4 on the OLT vary in the ACL, security feature, and
IPTV multicast service.
Configuration Difference in Each Scenario

Table 18-2 lists the configuration difference between IPv6 and IPv4 on the OLT in each
scenario. For details about the commands, see the later section.
Table 18-2 Configuration difference between IPv6 and IPv4 on the OLT
Issue 01 (2016-04-29)
Service
Scheme
Configuration Difference Between IPv6 and

IPv4
HSI
IPv4/IPv6 DS
+NAT+PPPoE
The ACL and anti-IP spoofing configurations are

different for the two services.
IPv4/IPv6 DS
+NAT+IPoE
The ACL, anti-IP spoofing, and DHCP option

configurations are different for the two services.
DS-Lite+PPPoE


1697

Access Module
Service
Scheme

IPv4
IPTV
IPv4/IPv6 DS
+IPoE
The ACL, anti-IP spoofing, DHCP option, and

multicast IGMP protocol configurations are
ACL
ACL configurations on the OLT are different for IPv6 and IPv4 on the network which runs
both IPv4 and IPv6 services, irrespective of the networking scenarios and service
implementation schemes. When configuring basic and advanced IPv6 ACLs, ensure that the
keyword "ipv6" is included in the configuration command. For details, see Table 18-3.
Table 18-3 Commands for configuring IPv4 and IPv6 ACL on the OLT
IPv4
IPv6
IPv6 ACL Supported or

Not
acl
acl ipv6
Supported
packet-filter { inbound |
outbound }
outbound } ipv6
Supported
rule
rule
Supported
NOTE
After IPv6 is introduced, the
protocol parameter in the rule
command is extended to
support the IPv6 protocols.
Security Feature
Anti-IP spoofing configurations for IPv6 and IPv4 are different on the network which runs
implementation schemes. If the IPoE and DHCP protocols are used, DHCP option
configurations for IPv6 and IPv4 are also different. For details, see Table 18-4.
l
The IP addresses in anti-IP spoofing configurations are different for the two services.
In the IPv4 configuration, DHCP option is DHCPv4 option 82. In the IPv6
configuration, DHCP option is DHCPv6 option 18/37.
The DHCP option function is used together with the RAIO function, which enables the
OLT to include physical information (including RID and CID) of the user, such as the
subrack/slot/port. In this way, the BRAS or DHCP server is able to perform user
authentication and tracing. When DHCPv4 is in use, the OLT includes RID and CID to
the option 82 field. When DHCPv6 is in use, the OLT includes the RID to the option 37
field in the DHCPv6 packet and the CID to the option 18 field. The sub option 7 and sub
option 9 functions of DHCPv4 option 82 are not supported by DHCPv6.
Issue 01 (2016-04-29)

1698

Access Module
Table 18-4 Commands for configuring IPv4 and IPv6 security features on the OLT
IPv4
IPv6
IPv6 Security Supported

or Not
raio-mode mode dhcpoption82
raio-mode mode dhcpv6option
Supported
dhcp option82
dhcpv6 option
Supported
dhcp-option82 permitforwarding service-port
dhcpv6-option permitforwarding
Supported
raio sub-option
Not supported
dhcp sub-option7
Not supported
raio dhcpv6-option37
enterprise-num
Supported
display dhcp option82
display dhcpv6 option
Supported
display dhcp config
display dhcpv6 config
Supported
security anti-ipspoofing
security anti-ipv6spoofing
Supported
display security bind ip
display security bind ipv6
Supported
DHCP Option
Anti-IP spoofing
IPTV Multicast Service

The IGMP protocol configurations (used to implement the IPTV multicast service) for IPv6
and IPv4 on the OLT are different. IPv4 uses the IGMP protocol while IPv6 uses the MLD
protocol (the IGMP protocol for IPv6). The IPv4 multicast service can share VLANs with the
IPv6 multicast service; therefore, you can deploy the IPv6 multicast service in existing IPv4
MVLANs only by adding IPv6 multicast programs in the IPv4 MVLANs and in right profiles.
The configured parameters such as the bound right profiles and MVLANs can remain
unchanged. For details about the difference of the IGMP commands between the two services,
see Table 18-5.
Table 18-5 Commands for configuring the IPv4 and IPv6 multicast services on the OLT
IPv4
IPv6
IPv6 Multicast
Supported or Not
igmp mode
igmp ipv6 mode
Supported
igmp match mode
igmp ipv6 match mode
Supported
igmp version
igmp ipv6 version
Supported
MVLAN
Issue 01 (2016-04-29)

1699

Access Module
IPv4
IPv6
IPv6 Multicast
Supported or Not
igmp match group
igmp ipv6 match group
Supported
display igmp config vlan
display igmp ipv6 config

vlan
Supported
igmp inner-vlan
Not supported
igmp send global-leave
Not supported
debugging igmp ipv6
Supported
igmp preview
Not supported
igmp preview reset count
Not supported
igmp preview reset record
Not supported
igmp preview-profile add
Not supported
igmp preview-profile delete
Not supported
igmp preview-profile
modify
Not supported
display igmp preview user
Not supported
display igmp previewprofile
Not supported
igmp proxy router genquery-interval
igmp ipv6 proxy router genquery-interval
Supported
igmp proxy router genresponse-time
igmp ipv6 proxy router genresponse-time
Supported
igmp proxy router

robustness
igmp ipv6 proxy router

robustness
Supported
igmp proxy router sp-queryinterval
igmp ipv6 proxy router spquery-interval
Supported
igmp proxy router sp-querynumber
igmp ipv6 proxy router spquery-number
Supported
igmp proxy router spresponse-time
igmp ipv6 proxy router spresponse-time
Supported
igmp initial-unsolicitedreport interval
igmp ipv6 initialunsolicited-report interval
Supported
Multicast user and right

debugging igmp
Preview
Protocol parameter
Issue 01 (2016-04-29)

1700

Access Module
IPv4
IPv6
IPv6 Multicast
Supported or Not
igmp unsolicited-report
interval
igmp ipv6 unsolicited-report

interval
Supported

vlan
Supported
igmp proxy router timeout
Not supported
igmp leave-proxy
igmp ipv6 leave-proxy
Supported
igmp priority
igmp ipv6 priority
Supported
imgp report-proxy
igmp ipv6 report-proxy
Supported
igmp accelerator
Not supported
igmp echo
Not supported
igmp encapsulation
Not supported
igmp multicast-tag
Not supported
igmp policy
Not supported
igmp query-offline-user
Not supported
igmp user-action-report
Not supported
igmp mismatch
Not supported
display igmp policy
Not supported
igmp sip-gip-forward
Not supported
igmp statistic reset
igmp ipv6 statistic reset
Supported
display igmp statistic
display igmp ipv6 statistic
Supported
display multicast flowstatistic
Not supported
Not supported
Multicast additional function
Statistics
Log
display igmp log statistic
NOTE
The multicast commands that are not listed in this table are the commands shared by the IPv4 multicast
and IPv6 multicast.
Issue 01 (2016-04-29)

1701

Access Module
18.2.2 Configuration Differences Between IPv6 and IPv4 on the

ONU
Configurations between IPv6 and IPv4 on the ONU vary in the ACL, security feature, and
IPTV multicast service.
Configuration Difference in Each Scenario

Table 18-6 lists the configuration difference between IPv6 and IPv4 on the ONU in each
scenario. For details about the commands, see the later section.
Table 18-6 Configuration difference between IPv6 and IPv4 on the ONU
Service
Scheme

IPv4
HSI
IPv4/IPv6 DS
+NAT+PPPoE

IPv4/IPv6 DS
+NAT+IPoE
The ACL, anti-IP spoofing, and DHCP option

configurations are different for the two services.
DS-Lite+PPPoE

IPv4/IPv6 DS
+IPoE
The ACL, anti-IP spoofing, DHCP option, and

multicast IGMP protocol configurations are
IPTV
ACL
ACL configurations on the ONU are different for IPv6 and IPv4 on the network which runs
implementation schemes. When configuring basic and advanced IPv6 ACLs, ensure that the
keyword "ipv6" is included in the configuration command. For details, see Table 18-7.
Table 18-7 Commands for configuring IPv4 and IPv6 ACL on the ONU
IPv4
IPv6
IPv6 ACL Supported or

Not
acl
acl ipv6
Supported
outbound }
outbound } ipv6
Supported
rule
rule
Supported
NOTE
After IPv6 is introduced, the
protocol parameter in the rule
command is extended to
support the IPv6 protocols.
Issue 01 (2016-04-29)

1702

Access Module
Security
Anti-IP spoofing configurations for IPv6 and IPv4 are different on the network which runs
implementation schemes. If the IPoE and DHCP protocols are used, DHCP option
configurations for IPv6 and IPv4 are also different. For details, see Table 18-8.
l
The IP addresses in anti-IP spoofing configurations are different for the two services.
In the IPv4 configuration, DHCP option is DHCPv4 option 82. In the IPv6
configuration, DHCP option is DHCPv6 option 18/37.
In the IPv6 configuration, the DHCP option function is used together with the RAIO
function, which enables the ONU to include physical information (including RID and
CID) of the user, such as the subrack/slot/port. In this way, the BRAS or DHCP server is
able to perform user authentication and tracing. When DHCPv4 is in use, the ONU
includes RID and CID to the option 82 field. When DHCPv6 is in use, the ONU includes
the RID to the option 37 field in the DHCPv6 packet and the CID to the option 18 field.
The sub option 7 and sub option 9 functions of DHCPv4 option 82 are not supported by
DHCPv6.
Table 18-8 Commands for configuring IPv4 and IPv6 security features on the ONU
IPv6
IPv6 Security Supported

or Not
raio-mode mode dhcpoption82
raio-mode mode dhcpv6option
Supported
dhcp option82
dhcpv6 option
Supported
dhcp-option82 permitforwarding service-port
dhcpv6-option permitforwarding
Supported
raio sub-option
Not supported
dhcp sub-option7
Not supported
raio dhcpv6-option37
enterprise-num
Supported
display dhcp option82
display dhcpv6 option
Supported
display dhcp config
display dhcpv6 config
Supported
security anti-ipspoofing
security anti-ipv6spoofing
Supported
display security bind ip
display security bind ipv6
Supported
IPv4
Supports DHCP option82.
Anti-IP spoofing
IPTV Multicast Service

The IGMP protocol configurations (used to implement the IPTV multicast service) for IPv6
and IPv4 on the ONU are different. IPv4 uses the IGMP protocol while IPv6 uses the MLD
Issue 01 (2016-04-29)

1703

Access Module
protocol (the IGMP protocol for IPv6). The IPv4 multicast service can share VLANs with the
IPv6 multicast service; therefore, you can deploy the IPv6 multicast service in existing IPv4
MVLANs only by adding IPv6 multicast programs in the IPv4 MVLANs and in right profiles.
The configured parameters such as the bound right profiles and MVLANs can remain
unchanged. For details about the difference in the IGMP commands for the two services, see
Table 18-9.
Table 18-9 Commands for configuring the IPv4 and IPv6 multicast services on the ONU
IPv6
IPv6 Multicast
Supported or Not
igmp mode
igmp ipv6 mode
Supported
igmp match mode
igmp ipv6 match mode
Supported
igmp version
igmp ipv6 version
Supported
igmp match group
igmp ipv6 match group
Supported

vlan
Supported
igmp send global-leave
Not supported
debugging igmp ipv6
Supported
igmp preview
Not supported
igmp preview reset count
Not supported
igmp preview reset record
Not supported
igmp preview-profile add
Not supported
igmp preview-profile delete
Not supported
igmp preview-profile
modify
Not supported
display igmp preview user
Not supported
display igmp previewprofile
Not supported
igmp proxy router genquery-interval
igmp ipv6 router gen-queryinterval
Supported
igmp proxy router genresponse-time
igmp ipv6 router genresponse-time
Supported
IPv4
MVLAN
Multicast user and right

debugging igmp
Preview
Protocol parameter
Issue 01 (2016-04-29)

1704

Access Module
IPv4
IPv6
IPv6 Multicast
Supported or Not
igmp proxy router

robustness
igmp ipv6 router robustness
Supported
igmp proxy router sp-queryinterval
igmp ipv6 router sp-queryinterval
Supported
igmp proxy router sp-querynumber
igmp ipv6 router sp-querynumber
Supported
igmp proxy router spresponse-time
igmp ipv6 router spresponse-time
Supported
igmp initial-unsolicitedreport interval
igmp ipv6 initialunsolicited-report interval
Supported
igmp unsolicited-report
interval
igmp ipv6 unsolicited-report

interval
Supported

vlan
Supported
igmp proxy router timeout
Not supported
igmp statistic reset
igmp ipv6 statistic reset
Supported
Supported
display multicast flowstatistic
Not supported
display igmp log
Not supported
Supported
igmp leave-proxy
igmp ipv6 leave-proxy
Supported
igmp priority
igmp ipv6 priority
Supported
imgp report-proxy
igmp ipv6 report-proxy
Supported
igmp echo
Not supported
igmp encapsulation
Not supported
igmp policy
Not supported
igmp query-offline-user
Not supported
igmp user-action-report
Not supported
igmp mismatch
Not supported
Statistics
Log
Multicast additional function
Issue 01 (2016-04-29)

1705

Access Module
IPv4
IPv6
IPv6 Multicast
Supported or Not
display igmp policy
Not supported
NOTE
The multicast commands that are not listed in this table are the commands shared by IPv4 and IPv6
multicast services.
18.2.3 Configuration Difference Between IPv6 and IPv4 on the

ONT
For the bridging ONT, configurations for IPv6 and IPv4 are the same. For the gateway ONT,
the HSI service configurations for IPv6 and IPv4 are different.
Configuring the IPv6 WAN Port on the Gateway ONT

For IPv6 IPTV multicast service, no extra configuration is required. For the IPv6 HSI service,
the Internet WAN port on the gateway ONT must be configured (only Internet WAN port
supports IPv6). If the gateway ONT uses the IPv6/IPv4 DS scheme, select IPv4/IPv6 for
Protocol Type. If the gateway ONT uses the DS-Lite scheme, select IPv6 for Protocol Type.
For details, see Figure 18-1.
Figure 18-1 Configuring the IPv6 WAN port
Issue 01 (2016-04-29)

1706

Access Module
Configuring the IPv6 Address of the LAN Side on the Gateway ONT
The gateway ONT can be configured to allocate IPv6 addresses to the terminals after IPv6 is
introduced. For details, see Figure 18-2.
Figure 18-2 Configuring the IPv6 address on the LAN side
Configuring the Static IPv6 Route on the Gateway ONT

The gateway ONT can be configured with the static IPv6 route after IPv6 is introduced. For
details, see Figure 18-3.
Figure 18-3 Configuring the IPv6 static route
18.3 Configuring IPv6 Services in the FTTB/C (No HGWs)

Scenario
This section describes the methods for configuring IPv6 services in the FTTB/C (No HGWs)
scenario.
Issue 01 (2016-04-29)

1707

Access Module
18.3.1 Application Scenarios

The FTTB/C (no HGW) networking supports the access of IPv6 HSI services. Generally, no
IPTV services will be deployed when there is no HGW.
As shown in Figure 18-4, the ONU, which is installed in a corridor or street optical
distribution box, transmits services to users through category-5 cables (LAN access) or
twisted pairs (xDSL access). The OLT and ONU work with upper-layer devices to support
Huawei DS+NAT+PPPoE/DS+NAT+IPoE HSI IPv6 solutions.
l
For voice services: The ONU with a built-in voice module can directly provide VoIP
services for users. The ONU processes VoIP services using the IPv4 protocol instead of
the IPv6 protocol.
For Internet access services: Users connect to the ONU through category-5 cables (LAN
access) or the modem and twisted pairs (xDSL access). The PC and BRAS support the
IPv4/IPv6 DS and can be connected in the PPPoE or IPoE mode. The OLT and ONU
implement Layer 2 forwarding, irrespective of whether the access service is IPv4 or
IPv6. Service configurations for IPv4 and IPv6 are the same. Only the ACL, anti-IP
spoofing, and DHCP option configurations for IPv4 and IPv6 are different.
Figure 18-4 FTTB/C (no HGW) networking

OLT
LAN
PC
T
PO
FE/GE
PC
BRAS
ONU
Optical
splitter
Phone
NGN/IMS
CGN
Metro Network
Internet
xDSL
T
PO
PE-AGG
UPE
UPE
PE-AGG
ONU
Phone
18.3.2 Data Planning

This section describes the security, device management data, QoS, Internet service data, and
voice service data planning.
Security Planning
Security planning includes system security, user security, and service security, ensuring that
user services are provided properly from different dimensions.
In the FTTB/C (no HGW) networking scenario, the data for IPv6 and IPv4 security planning
differs only in anti-IP spoofing and DHCP option.
Anti-IP spoofing: This function needs to be configured separately for IPv6 services.
The anti-IP spoofing function can be enabled or disabled at three levels. This function takes
effect only when it is enabled at all the three levels.
Issue 01 (2016-04-29)

1708

Access Module
1.
Global level: Run the security anti-ipv6spoofing enable command in global config
mode.
2.
VLAN level: Run the security anti-ipv6spoofing enable command in VLAN service
profile mode.
3.
Service port level: Run the security anti-ipv6spoofing service-port serviceport-id

enable command.
DHCP option: The DHCP option for IPv4 is DHCPv4 option 82 and for IPv6 is DHCPv6
option 18/37.
The DHCPv6 option18 and option37 functions can be enabled or disabled at two levels. This
function takes effect only when it is enabled at both levels.
1.
Global level: Run the dhcpv6 option enable command in global config mode.
2.
VLAN level: Run the dhcpv6 option enable command in VLAN service profile mode.
Device Management Data Planning

Device management data planning includes the management channel and IP address planning.
The management channel for IPv6 and IPv4 services are the same.
Planning
Device or
Service
Solution Introduction
Management
channel
OLT
The device management uses single-tagged

VLANs on the entire network.
ONU

Device
management
IPv4 private network IP addresses are still used as

management IP addresses of the OLT and MDU
devices.
Internet
l IPv4 address: A PC obtains the IPv4 address

from the BRAS using PPPoE or DHCP. If IPoE
dial-up is used, the static address can be
configured for the PC.
IP address
planning
The BRAS can allocate a public network IP

address to a PC for Internet access.
The BRAS can allocate a private network
address to a PC. The private network
address is translated to the public network
address by CGN (NAT44).
l IPv6 address: A PC obtains the IPv6 address
from the BRAS using PPPoE, SLAAC, or
DHCPv6. If IPoE dial-up is used, the static
address can be configured for the PC.
IPTV service
Issue 01 (2016-04-29)
The IPTV service is not provisioned in this

scenario.

1709

Access Module
Planning
Device or
Service
VoIP service
The IPv4 protocol is still used. An ONU functions

as the DHCP client to obtain the IP address using
DHCP.
QoS Planning
The E2E QoS planning includes the flow classification, marking/scheduling policy, traffic
monitoring, and DBA policy.
When the IPv6 protocol is used, the QoS planning is the same for both IPv6 and IPv4.
l
Management service: IPv4
Voice service: IPv4
IPTV service: N/A.
Internet service: It is recommended that access devices use one flow to carry IPv6 and
IPv4 Internet services. The QoS planning is the same for the flow that carries both IPv6
and IPv4 Internet services and the flow that carries only the IPv4 Internet service.
Internet Service Planning

The Internet service planning includes the VLAN and VLAN switching policy planning in
IPv6 and IPv4 Internet services: It is recommended that devices use one flow to carry IPv6
and IPv4 Internet services. This facilitates the control of the aggregate rate for IPv6 and IPv4
Internet services. The QoS planning is the same for the flow that carries both IPv6 and IPv4
Internet services and the flow that carries only the IPv4 Internet service. For details, see
10.3.3 Principle of Internet Access Service Data Plan.
Voice Service Data Planning

Voice service data planning includes the VLAN/VLAN switching policy planning in different
networking scenarios, and voice protocol planning.
Even after IPv6 is used, the device still uses IPv4 to implement voice services.

This section describes the IPv6 service configuration procedure by scenario, and compares it
with the IPv4 service configuration procedure.
FTTB (No HGW, LAN Access) Configuration Procedure

The following figure shows the IPv6 service configuration procedure in the FTTB (no HGW,
LAN access) scenario. In this scenario, the planning and configuration procedure/method for
IPv6 and IPv4 services are almost the same except the commands for configuring anti-IP
spoofing and DHCP option. For details, see 18.2 Configuration Difference Between IPv6
and IPv4.
Issue 01 (2016-04-29)

1710

Access Module
Start
Add an ONU on the OLT
Configure the management channel

between the OLT and the ONU
OLT
Configure the service channel

Configure the link aggregation,

congestion control, and security policy
Configure the LAN

Configure the VoIP

service (H.248/SIP)
ONU
Verify the Internet access service and

VoIP service
End
NOTE
Texts in blue show the configuration difference between IPv6 and IPv4.
FTTB/C (No HGW, xDSL Access) Configuration Procedure

The following figure shows the IPv6 service configuration procedure in the FTTB/C (no
HGW, xDSL access) scenario. In this scenario, the planning and configuration procedure/
method for IPv6 and IPv4 services are almost the same except the commands for configuring
anti-IP spoofing and DHCP option. For details, see 18.2 Configuration Difference Between
IPv6 and IPv4.
Issue 01 (2016-04-29)

1711

Access Module
Start

OLT


Configure the xDSL

Configure the VoIP

service (H.248/SIP)
(Optional) Configure
Vectoring
ONU
Verify the Internet access service and

VoIP service
End
NOTE
18.3.4 Configuration Example

Introduce the end-to-end service configuration based on the FTTB/C without HGW
networking and the corresponding data plan.
Key Messages for Configuration

l
Even after IPv6 is used, the OLT and ONU implement Layer 2 forwarding in this
networking, irrespective of whether the access service is IPv4 or IPv6. Service
configurations for IPv4 and IPv6 are the same.
For the HSI service from one end user, one service flow is used to carry IPv6 and IPv4
Internet services, and the same service VLAN is used.
Even after IPv6 is used, the voice service is still realized by IPv4.
Data plan on the OLT side

Item
Data
Memo
ONU data plan

Issue 01 (2016-04-29)

1712

Access Module
Item
Data
Memo
DBA profile
Profile name: fttb_dba
The ONU is connected to OLT

through the GPON interface.
Profile type: type3

Assured bandwidth: 8
Mbit/s
Maximum bandwidth: 20
Mbit/s
Line profile

Profile ID: 10
T-CONT ID: 4
GEM port ID for
management service: 11
GEM port ID for Internet
access service: 12
GEM port ID for VoIP
service: 13
Network topology
data
PON port: 0/2/1

ONT ID: 1
LAG data plan

LAG
Ports: 0/19/0 and 0/19/1

Working mode: LACP
static aggregation
Configure upstream ports 0/19/0 and

0/19/1 into an aggregation group.
Each member port in the aggregation
group allocates packets based on the
source MAC address.
Queue scheduling data plan

Queue scheduling
Queue scheduling: strict

priority (SQ) mode
System default is adopted in this

example.
Priority mapping: mapped

into different queues based
on priorities
Management channel data plan
Issue 01 (2016-04-29)
Management VLAN
and management IP
address on the OLT
side
Management VLAN
and management IP
address on the ONU
side

smart VLAN
address: 192.168.50.1/24

by logging in to the MDU, the

smart VLAN
address: 192.168.50.2/24

1713

Access Module
Item
Data
Memo
Service channel data plan

Internet access
service
OLT VLAN ID:

l CVLAN ID: 256 x
GPON port ID + 32 x
Split ratio x (Splitter
port ID - 1) + ONU
port ID + 1
l SVLAN: VLAN ID
100 and attribute
stacking
ONU: 1001-1016

splitter using the optical cable, and the
user PC is connected to port 1 on the
ONU. In this case, the inner VLAN is
258 according to the formula for
calculating the inner VLAN.
18.3.2 Data Planning.

VoIP service
OLT VLAN ID (VLAN

transparently transmitting
the ONU service): 200

ONU VLAN ID: 200

Security data plan
System security
Anti-DOS attack: disabled

Anti-ICMP attack:
disabled

example.
Anti-IP attack: disabled

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
Service security
Forward the packet with

PITP tag: enabled
DHCPv4 Option82:
enabled
In this example, the location

information is added to packets by the
ONU equipment and these packets are
forwarded by the OLT equipment.

DHCPv6 Option18/37:
enabled
Data plan of the ONU side

Item
Data
Memo
HSI service data plan
Issue 01 (2016-04-29)

1714

Access Module
Item
Data
Memo
Port
Service port: 0/3/1

Service VLAN
VLAN ID: 1001-1016

VLAN type: smart VLAN
The ONU supporting 16 FE ports is

used as an example. In actual
configuration, plan the data according
to actual capabilities of devices.
Traffic profile
Profile ID: 8
Committed rate: 4 Mbit/s

Priority: 0
Queue scheduling

priority (SQ) mode

example.

on priorities
Service security data plan
System security

Anti-ICMP attack:
disabled

example.

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
PPPoE Service
security
RAIO Type: PITP P
IPv4oE Service
security
RAIO Type: DHCP Option

82
PITP is recommended for PPPoE.
RAIO Mode: common

DHCPv4 option and DHCPv6 option
are recommended for IPoE.
RAIO Mode: common

IPv6oE Service
security
RAIO Type: DHCPv6

Option
RAIO Mode: common
Voice service data plan

Media and signaling
upstream VLANs
Issue 01 (2016-04-29)
200
H.248 protocol is adopted in this

example.

1715

Access Module
Item
Data
Media and signaling

upstream port
0/0/1
Media IP address
and signaling IP
address
11.11.11.11/24
Default gateway IP
address
11.11.11.11/24
MG interface ID
Signaling port ID
2944
IP address of the
primary MGC
200.200.200.200/24
Port ID of the
primary MGC
2944
Coding
Text
Transmission mode
UDP
H248 version that

MG starts to
negotiate
1 (the negotiation starts

from V1)
Phone number
83110001-83110024
Terminal
identification
Terminal layering is not

supported and the terminal
identification ranges from
0 to 23.
User priority
Cat2 for phone 1
Memo
Cat3 for phone 2 to phone

24 (default)
Issue 01 (2016-04-29)
User type
Common user (DEL user

by default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal
Ringing current
attribute
Default value

1716

Access Module
Procedure
1.

huawei(config)#dba-profile add profile-name fttb_dba type3 assure 8192 max
20480
2.

huawei(config-gpon-lineprofile-10)#tcont 4 dba-profile-name fttb_dba
3.

In this example, the default alarm profile is used and therefore the configuration of the

Assume that the ID of GPON port 0/2/1 is 1, SN is 3230313163902641, management mode is
SNMP, and the bound line profile is fttb(c). Connect the ONU to such a GPON port through
discovered ONU.
l
Add an ONU offline.


1.


normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
Run state
: online
Config state
: normal
normally.
Issue 01 (2016-04-29)

1717

Access Module
255.255.255.0 gateway
192.168.50.1 vlan 8

l
Step 8 Configure the channel for the Internet access service.

user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6 tx-cttr 6
Step 9 Configure the channel for the VoIP service.

huawei(config)#traffic table ip index 9 cir off priority 5 priority-policy localsetting
Step 10 Configure LAG for upstream ports.

Configure upstream ports 0/19/0 and 0/19/1 into an aggregation group. Each member port in
the aggregation group allocates packets based on the source MAC address. The working mode
is LACP static aggregation.
Step 11 (Optional) When PPPoE is adopted, enable forwarding the packets with PITP tag on the OLT
equipment.
huawei(config)#pitp permit-forwarding service-port 101 enable
Step 12 (Optional) When IPoE is adopted, enable forwarding the packets with DHCP option on the
OLT equipment.
huawei(config)#dhcp-option82 permit-forwarding service-port 101 enable
//For
IPv4 packets
huawei(config)#dhcpv6-option permit-forwarding port 0/2/1 ontid 1 enable
//For
IPv6 packets
Step 13 Save the configuration data on the OLT.

huawei(config)#save

Issue 01 (2016-04-29)

1718

Access Module
You can remote log in to the ONU from the OLT to perform the configuration. By default, the
user name is root and the password is mduadmin.
NOTE
The following steps are configured on the ONU side.
Step 15 Configuration the HSI service on the ONU side.

NOTE
huawei(config)#traffic table ip index 8 cir 4096 priority 0 priority-policy localSetting
Step 16 (Optional) Configure the PITP function for PPPoE.

huawei(config)#raio-mode common pitp-pmode
Step 17 (Optional) Configure the DHCP option function for IPoE.

huawei(config)#raio-mode common dhcp-option82
huawei(config)#raio-mode common dhcpv6-option
//For DHCPv4 packets

Step 18 Configure the voice service.

huawei(config)#voip
83110001
enable
Step 19 Save the configuration on the ONU side.

huawei(config)#save
----End
Issue 01 (2016-04-29)

1719

Access Module
18.4 Configuring IPv6 Services in the FTTB+HGW

Scenario
This section describes the methods for configuring IPv6 services in the FTTB+HGW
scenario.
18.4.1 Application Scenario

The FTTB+HGW networking includes two scenarios: The ONU provides the voice service in
one scenario and the HGW provides the voice service in another scenario. After IPv6 is
introduced to the network, the voice service still uses IPv4 so that these two voice scenarios
do not change after IPv6 introduction.
FTTB+HGW Application Scenario

Figure 18-5 shows an FTTB+HGW network. The OLT is deployed at the CO and connects to
the MAN by aggregation, and the ONU is deployed in the buildings or street fiber distribution
terminals. Access interfaces are deployed on the HGW that connects to the ONU using LAN
or xDSL upstream transmission (deployed in user houses). Together with upper layer devices,
the FTTB+HGW network supports the HSI and IPTV services implemented by the schemes
of the Huawei fixed broadband solution for IPv6: IPv4/IPv6 DS+NAT+PPPoE, IPv4/IPv6 DS
+NAT+IPoE, and DS-Lite+PPPoE (for the HSI services) and IPv4/IPv6 DS+IPoE and IPv4/
IPv6 DS+PPPoE (for the IPTV service).
l
Upstream networking: The HGW connects to the ONU through upstream ETH or xDSL
port.
HSI service: The HGW has Layer 3 functions (such as PPPoE dial-up and NAT), which
enable multiple PCs of a family to access the Internet at the same time.
If the HGW uses the IPv4/IPv6 DS scheme, the PPPoE or IPoE channel that
supports both IPv4 and IPv6 is established between the HGW and the BRAS. The
OLT and ONU perform Layer 2 forwarding, irrespective of whether the access
service is IPv4 or IPv6. Service configurations for IPv4 and IPv6 are the same.
Only the ACL, anti-IP spoofing, and DHCP option configurations for IPv4 and
IPv6 are different.
If the HGW uses the DS-Lite scheme, the PPPoE channel that supports only IPv6 is
established between the HGW and the BRAS. As for IPv4, the HGW encapsulates
IPv4 packets and transmits them to the BRAS or CGN using the 4in6 tunnel. The
OLT and ONU perform Layer 2 forwarding, irrespective of whether the access
service is IPv4 or IPv6. Service configurations for IPv4 and IPv6 are the same.
Only the ACL, anti-IP spoofing, and DHCP option configurations for IPv4 and
IPv6 are different.
IPTV service: Users can preview or view IPTV programs by connecting an STB to the
HGW. STB supports IPv4/IPv6 DS and uses IPv4 or IPv6 (cannot be used together) to
carry IPTV services.
Issue 01 (2016-04-29)
If the STB uses IPoE, choose the ONU preferentially to duplicate multicast flows.
On the ONU, IPv6 and IPv4 multicast services are configured in the same way but
with different commands. On the OLT, service channels to the ONU need to be
established, multicast flows do not need to be duplicated, and IGMP IPv6 data
needs to be configured.
1720

Access Module
If the STB uses PPPoE, it establishes a PPPoE connection to the BRAS. The OLT,
ONU, and HGW only forward PPPoE service flows and do not process multicast
services. Therefore, this scheme is not recommended.
Voice service: The voice service can be provided by the ONU with the build-in voice
module or the build-in IAD of the HGW. The VoIP service on ONU or HGW is still
implemented by IPv4.
Figure 18-5 FTTB+HGW service networking

Laptop
PC
HGW
ONU
PE-AGG
OLT
STB
NGN/IMS
UPE
TV
IPTV
Headend
Metro Network
Phone
Laptop
Splitter
STB
Internet
UPE
HGW
PC
PE-AGG
ONU
TV
Phone

This section describes the security, device management data, QoS, Internet service data, voice
service data, and IPTV service data planning.
Security Planning
Security planning includes system security, user security, and service security, ensuring user
services are provided properly from different dimensions.
In the FTTB+HGW networking scenario, only anti-IP spoofing and DHCP option of IPv6 and
IPv4 services are different.
1.
mode.
2.
profile mode.
3.

enable command.
option 18/37.
Issue 01 (2016-04-29)

1721

Access Module
1.
2.

Planning
Device or
Service
Management
channel
OLT

ONU

HGW
Single-tagged S-VLANs are used as management

VLANs for all HGWs that need to be managed by
the iTMS.
The management VLANs for HGWs can be
allocated to an entire network, an OLT, a PON
board, or a PON port to identify services and
physical locations. It is recommended that you set
different HGW management VLANs for the OLTs
connected to one SR to avoid an excessively large
broadcast domain of the SR and convergence
switch.
IP address
planning
Issue 01 (2016-04-29)
Device
management
IPv4 private network IP addresses are still used as

management IP addresses of the OLT and MDU
devices.

1722

Access Module
Planning
Device or
Service
Internet
l IPv4 address: An HGW obtains the IPv4

address from the BRAS using PPPoE or
DHCP. If IPoE dial-up is used, the static
address can be configured. Meanwhile, as the
DHCP server, the HGW allocates private
network IP addresses to PCs. The NAT
function enables these PCs to go online by
sharing the IPv4 address allocated by the
BRAS.
address to an HGW.
address to an HGW. The private network
l IPv6 address: An HGW obtains the IPv6
address can be configured. Meanwhile, the
HGW as the DHCP server obtains the prefix of
an IPv6 address, and allocates IPv6 addresses
to connected PCs.
IPTV service
l If the IPv4 protocol is used, an STB obtains the

IP address from the BRAS using DHCP.
l If the IPv6 protocol is used, the STB obtains
the IP address in either of the following ways:
Obtains the IP address from the BRAS
using DHCPv6.
using SLAAC.
VoIP service
The IPv4 protocol is still used. An ONU or HGW

functions as the DHCP client to obtain the IP
address using DHCP.
TR069 service
The IPv4 protocol is still used. In scenarios in

which TR069 is required for management
maintenance and service provisioning, the HGW
functions as the DHCP client to obtain a public
network IP address from the DHCP server to
connect the TR069 server ACS.
QoS Planning
Issue 01 (2016-04-29)

1723

Access Module
l
Voice service: IPv4
IPTV service: One user uses either IPv6 or IPv4 at one time. The QoS planning for IPv6
and IPv4 IPTV services is the same.

Internet services and the flow that carries only the IPv4 Internet service.

IPTV Service Data Planning

IPTV service data planning includes the VLAN/VLAN switching policy planning in different
networking scenarios, and IPTV service planning.
When the IPv6 protocol is used, one IPTV user uses either IPv6 or IPv4 at one time. The
VLAN data planning for IPv6 is consistent with that for IPv4. For details, see 10.3.6
Principle of IPTV Service Data Plan. The IPv6 version of the IGMP protocol is aslo known
as multicast listener discovery (MLD). The following table lists the detailed data planning.
Issue 01 (2016-04-29)
Data Item
Remarks
IGMP
The OLT and ONU use the IGMP IPv6 proxy.

1724

Access Module
Data Item
Remarks
IGMP version
The compatibility policies of the IGMP version on access

devices are different on the network side (multicast router) and
the user side (terminal).
In normal application scenarios:
1. The device is usually the initiating party. The IGMP version
on the multicast router can be seamlessly degraded without
packet loss.
2. The terminal is usually the initiating party. The IGMP
version on the device can be seamlessly degraded without
packet loss.
Recommended IGMP IPv6 protocol versions are as follows:
l When the network side is V1, the access device uses V1.
l When the network side is V2, the access device uses V1 or
V2.
l When the network side is V1, the access device uses V1 or
V2.
l When the network side is V2, the access device uses V2.
Multicast program
Static configuration is recommended. The OLT can also

generate a multicast program library, that is, dynamically
generate a program list according to the programs requested by
users.
Multicasat preview
profile
Not supported.
Multicast quick leave
The quick leave function is enabled (recommended) to help

reduce the exchange of IGMP packets and save bandwidth
resources.

This section describes IPv6 service configuration procedure by scenario, and compares it with
the IPv4 service configuration procedure.
FTTB+HGW (ONU Provides the Voice Service) Configuration Procedure

The following figure shows the IPv6 service configuration procedure in the FTTB+HGW
(ONU provides the voice service) scenario. In this scenario, the planning and configuration
procedure/method for IPv6 and IPv4 services are almost the same except the following
differences. On the OLT side, multicast service channels between the OLT and ONU and part
configuration commands of the security policy are different. On the ONU side, configuration
commands of IPTV multicast services are different. 18.2 Configuration Difference Between
IPv6 and IPv4 shows the differences.
Issue 01 (2016-04-29)

1725

Access Module
Start

OLT



access service
Configure the VoIP

service (H.248/SIP)
Configure the IPTV

service
Vectoring
ONU
Configure the IPTV

service

access service
HGW
Verify the Internet access service,
VoIP service and IPTV services
End
NOTE
Texts in blue show the configuration (on OLT and ONU ) difference between IPv6 and IPv4.
For differences between the HGW's IPv6 and IPv4 service processing, see documentation of the HGW
products.
FTTB+HGW (HGW provides the voice service) Configuration Procedure

The following figure shows the IPv6 service configuration procedure in the FTTB+HGW
(ONU provides the voice service) scenario. In this scenario, the planning and configuration
procedure/method for IPv6 and IPv4 services are almost the same except the following
differences. On the OLT side: Multicast service channels between the OLT and ONU and part
configuration commands of the safety policy are different. On the ONU side: Configuration
commands of IPTV multicast services are different. 18.2 Configuration Difference Between
IPv6 and IPv4 shows the differences.
Issue 01 (2016-04-29)

1726

Access Module
Start

OLT


ONU
access service
Configure the VoIP

service
Configure the IPTV

service
Configure the VoIP

service (SIP)
Configure the IPTV

service
Vectoring

access service
Verify the VoIP

service
HGW
Verify the Internet access service

and IPTV services
End
NOTE
Texts in blue show the configuration (on OLT and ONU ) difference between IPv6 and IPv4.
For differences between the HGW's IPv6 and IPv4 service processing, see documentation of the HGW
products.

Introduce the end-to-end service configuration based on the FTTB+HGW networking and the
corresponding data plan.

l
Even after IPv6 is used, the OLT and ONU implement Layer 2 forwarding for HSI
service in this networking, irrespective of whether the access service is IPv4 or IPv6.
Service configurations for IPv4 and IPv6 are the same. For the HSI service from one end
user, one service flow is used to carry IPv6 and IPv4 Internet services, and the same
service VLAN is used.
Issue 01 (2016-04-29)

1727

Access Module
For multicast service, the ONU is the node to make multicast duplication. The
configuration procedure is the same for IPv4 multicast and IPv6 multicase. The IPv4
multicast service and IPv6 multicast service can be configured in the same multicast
VLAN on the ONU equipment.

Item
Data
Memo
Profile name: fttb_dba
The ONU is connected to OLT

through the GPON interface.
ONU data plan

DBA profile
Profile type: type3

Mbit/s
Mbit/s
Line profile

Profile ID: 10
T-CONT ID: 4
GEM port ID for
management service: 11
access service: 12
GEM port ID for VoIP
service: 13
Network topology
data
PON port: 0/2/1

ONT ID: 1
LAG data plan

LAG
Ports: 0/19/0 and 0/19/1

Working mode: LACP
static aggregation

source MAC address.

Queue scheduling

priority (SQ) mode

example.

on priorities
Management channel data plan
Issue 01 (2016-04-29)

1728

Access Module
Item
Data
Memo
Management VLAN
and management IP
address on the OLT
side
Management VLAN
and management IP
address on the ONU
side

by logging in to the MDU, the

smart VLAN
address: 192.168.50.1/24

smart VLAN
address: 192.168.50.2/24
Service channel data plan

Internet access
service
S-VLAN ID: 100; SVLAN attribute: stacking

C-VLAN ID: 1000-1016
Traffic profile: 6
Plan the Internet access service in per

user per service per VLAN (PUPSPV)
mode and apply S-VLAN+C-VLAN
to differentiate users.
The 802.1p priority of the Internet
access service is 0, and rate limitation
is not required. System traffic profile
6 can be used.
For details, see 18.4.2 Data Planning.
VoIP service
S-VLAN ID: 200

C-VLAN ID: 200
Traffic profile: 9
The voice over IP (VoIP) service is a

carrier-operating, closed service and
primarily adopts only S-VLAN tags,
which are transparently transmitted by
OLTs.
The 802.1p priority of the VoIP
service is 5, and rate limitation is not
required. System traffic profiles do
not meet the requirements and new
traffic profile shall be configured.
Issue 01 (2016-04-29)

1729

Access Module
Item
Data
Memo
VoD service
S-VLAN ID: 300
Plan the video on demand (VoD)

service in per user per VLAN (PUPV)
mode if possible, as the VoD service
requires only a few VLAN resources.
Traffic profile: 10
The VoD service is a carrieroperating, closed service and

primarily adopts only S-VLAN tags,
OLTs.
The 802.1p priority of the VoD
service is 4, and rate limitation is not
required. System traffic profiles do
not meet the requirements and new
traffic profile shall be configured.
Multicast service
Multicast VLAN ID: 1000

Multicast cascading port:
0/2/1
IGMP mode: IGMP proxy
Multicast IP address range:
224.1.1.10-224.1.1.100
The multicast service is a carrieroperating, closed service and

primarily adopts only S-VLAN tags.
Take the same traffic profile with the
VoD service.

server: 10.10.10.10/24
Traffic profile: 10
Security data plan
System security

Anti-ICMP attack:
disabled

example.

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
Service security

PITP tag: enabled
DHCPv4 Option82:
enabled
In this example, the location

information is added to packets by the
ONU equipment and these packets are
forwarded by the OLT equipment.

DHCPv6 Option18/37:
enabled
Issue 01 (2016-04-29)

1730

Access Module
Data plan of the ONU side

Item
Data
Memo
ID: 8

Traffic profile
CIR: 4 Mbit/s
VLAN priority: 0
Downstream priority
policy: local-setting
User VLAN
Untagged
HGWs can send untagged packets or

packets with user VLAN tags.

Queue scheduling

priority (SQ) mode

example.

on priorities
Service security data plan
System security

Anti-ICMP attack:
disabled

example.

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
PPPoE Service
security
RAIO Type: PITP P
IPv4oE Service
security

82
RAIO Mode: common

RAIO Mode: common

IPv6oE Service
security
RAIO Type: DHCPv6

Option
RAIO Mode: common

Media and signaling
upstream VLANs
Issue 01 (2016-04-29)
200
H.248 protocol is adopted in this

example.

1731

Access Module
Item
Data
Media and signaling

upstream port
0/0/1
Media IP address
and signaling IP
address
11.11.11.11/24
Default gateway IP
address
11.11.11.11/24
MG interface ID
Signaling port ID
2944
IP address of the
primary MGC
200.200.200.200/24
Port ID of the
primary MGC
2944
Coding
Text
Transmission mode
UDP
H248 version that

MG starts to
negotiate
1 (the negotiation starts

from V1)
Phone number
83110001-83110024
Terminal
identification
Terminal layering is not

supported and the terminal
identification ranges from
0 to 23.
User priority
Cat2 for phone 1
Memo
Cat3 for phone 2 to phone

24 (default)
User type
Common user (DEL user

by default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal
Ringing current
attribute
Default value
IPTV service data plan
Issue 01 (2016-04-29)

1732

Access Module
Item
Data
Memo
Traffic profile
ID: 10
CIR: off
VLAN priority: 4
Downstream priority
User VLAN in the
scenario in which
HGWs are upstream
connected to an
ONU through LANs
HGWs can send untagged packets or

packets with user VLAN tags.
VPI/VCI of
ADSL2+ users in
the scenario in
which HGWs are
connected upstream
to an ONU in
ADSL2+ mode
VPI: 0
Internet service providers (ISPs)

provide VPI/VCI information.
VDSL2 path mode

in the scenario in
which HGWs are
connected upstream
to an ONU in
VDSL2 mode
PTM
Both the central office and HGWs

must support the PTM mode.
VLAN ID of the
VoD service
300
The VoD service is a carrieroperating, closed service and

primarily adopts only SVLAN tags,
OLTs.
Multicast VLAN ID
of the ONU
1000
Multicast VLAN ID
of HGWs
43
A carrier generally specifies a

globally unique multicast VLAN ID
for HGWs.
VCI: 35
Procedure
1.

huawei(config)#dba-profile add profile-name fttb_dba type3 assure 8192 max
20480
2.

huawei(config-gpon-lineprofile-10)#tcont 4 dba-profile-name fttb_dba
Issue 01 (2016-04-29)

1733

Access Module
huawei(config-gpon-lineprofile-10)#gem add 11 eth
huawei(config-gpon-lineprofile-10)#gem mapping 11
3.
tcont 4 cascade on
tcont 4 cascade on
tcont 4 cascade on
0 vlan 8
1 vlan 1001
2 vlan 200

In this example, the default alarm profile is used and therefore the configuration of the

Assume that the ID of GPON port 0/2/1 is 1, SN is 3230313163902641, management mode is
SNMP, and the bound line profile is fttb(c). Connect the ONU to such a GPON port through
discovered ONU.
l
Add an ONU offline.


1.


normal.
--------------------------------------------------------------------F/S/P
: 0/2/1
ONT-ID
: 1
Control flag
: active
Run state
: online
Config state
: normal
normally.
Issue 01 (2016-04-29)

1734

Access Module

255.255.255.0 gateway
192.168.50.1 vlan 8

l
Step 8 Configure a channel for the Internet access service.

user-vlan 1001 tag-transform translate-and-add rx-cttr 6 tx-cttr 6
Step 9 Configure a channel for the Voice service.

Step 10 Configure a channel for the VoD service.

huawei(config)#traffic table ip index 10 cir off priority 4 priority-policy localSetting
Step 11 Configure a channel for the multicast service.

huawei(config)#btv
huawei(config-mvlan1000)#igmp ipv6 version v2
huawei(config-mvlan1000)#igmp ipv6 mode proxy
Are you sure to change IGMP IPv6 mode?(y/n)[n]:y
huawei(config-mvlan1000)#igmp program add batch ipv6 ff15:: to-ipv6 ff15::ffff
source-ipv6 2000::1

Step 13 (Optional) When PPPoE is adopted, enable forwarding the packets with PITP tag on the OLT
equipment.
huawei(config)#pitp permit-forwarding service-port 101 enable
Issue 01 (2016-04-29)

1735

Access Module
Step 14 (Optional) When IPoE is adopted, enable forwarding the packets with DHCP option on the
OLT equipment.
huawei(config)#dhcp-option82 permit-forwarding service-port 101 enable
//For
IPv4 packets
huawei(config)#dhcpv6-option permit-forwarding port 0/2/1 ontid 1 enable
//For
IPv6 packets
Step 15 Save the configuration data on the OLT.

huawei(config)#save

You can remote log in to the ONU from the OLT to perform the configuration. By default, the
user name is root and the password is mduadmin.
NOTE
The following steps are configured on the ONU side.
Step 17 Configuration the HSI service on the ONU side.

NOTE
l
1001):
10, and bind traffic profile 8 to the user VLAN./ huawei(config)#service-port
101 vlan 1001 eth 0/3/1 multi-service user-vlan 10 rx-cttr 8 tx-cttr 8



Step 20 Configure the voice service.

huawei(config)#voip
Issue 01 (2016-04-29)

1736

Access Module
83110001
enable
Step 21 Configure the VoD service.

huawei(config)#vlan 300 smart huawei(config)#port vlan 300 0/0 1

table ip command. In this example, the query result shows that no traffic profile meets the
requirements, so a traffic profile needs to be configured.
Add traffic profile 10 and set priority-policy to local-setting. Then, traffic is scheduled based
on the priority specified in the traffic profile.

l
contain user VLAN tags, the ONU needs to perform a switch between user VLAN IDs
and SVLAN IDs.
Assume that the user VLAN ID is 1 and the Ethernet port is 0/3/1. Add a service flow as
follows:
rx-cttr 10 tx-cttr 10

contain users' PVC information so the ONU needs to perform a switch between PVC
information and SVLAN IDs.
Assume that the VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0. Add a service flow as
follows:

Assume that the VDSL2 path mode is PTM mode, port is 0/1/0, and packets from the
user VLAN are untagged. Add a service flow as follows:
Issue 01 (2016-04-29)

1737

Access Module

Are you sure to change IGMP IPv6 mode?(y/n)[n]:y
huawei(config-mvlan1000)#igmp program add batch ipv6 ff15:: to-ipv6 ff15::ffff
source-ipv6 2000::1

l
If HGWs are connected to an ONU upstream through LANs, assume that the user VLAN
ID is 43 and the Ethernet port is 0/3/1, and add a service flow as follows:
If HGWs are connected to an ONU upstream in VDSL2 mode, assume that the VDSL2
path mode is PTM mode, the user VLAN ID is 43, and the VDSL2 port is 0/1/0, and add
a service flow as follows:
Step 23 Save the configuration on the ONU side.

huawei(config)#save
----End
18.5 Configuring IPv6 Services in the FTTH (Bridging

ONT) Scenario
This section describes the methods for configuring IPv6 services in the FTTH (bridging ONT)
scenario.

The FTTH (bridging ONT) supports multiple IPv6 HSI and IPTV service schemes.
FTTH (Bridging ONT) Application Scenario

As shown in Figure 18-6, the FTTH (bridging ONT) works with upper-layer devices to
support DS+NAT+PPPoE/DS+NAT+IPoE HSI and DS+IPoE or DS+PPPoE IPTV services in
the Huawei fixed network IPv6 solution.
Issue 01 (2016-04-29)

1738

Access Module
For the voice service: An ONT with a bulit-in voice module can directly provide VoIP
services for users. The ONT still processes VoIP services using IPv4.
Internet service: The PC and BRAS support the IPv4/IPv6 dual-stack, and can be
connected through the PPPoE or IPoE dial-up. The OLT and ONT perform Layer 2
forwarding for both IPv4 and IPv6 user services, which can be configured almost in the
same way. The only difference is that commands for configuring the ACL and security
(DHCP option and anti-IP spoofing) features are different.
IPTV service: STBs support IPv4/IPv6 dual-stack and carry IPTV services using either
IPv4 or IPv6.
When STBs use IPoE and the OLT functions as the multicast duplication point, the
process for configuring IPv6 and IPv4 multicast services is the same, but commands
are different. The ONTs perform Layer 2 forwarding for only IPTV services, and
the configurations for IPv6 and IPv4 multicast services are the same on the ONT
side.
When STBs use the PPPoE dial-up, they directly connect to the BRAS by PPPoE.
The OLT and ONTs only forward PPPoE services instead of processing multicast
services. This solution is not recommended.
Figure 18-6 FTTH (bridging ONT) service networking

PC
ONT
STB
TV
PE-AGG
OLT
BRAS
Phone
PC
TV
NGN/IMS
UPE
Optical
splitter
STB
CGN
IPTV
Headend
Internet
UPE
ONT
PE-AGG
Phone

Security Planning
In the FTTH (briding ONT) networking scenario, only anti-IP spoofing and DHCP option of
IPv6 and IPv4 services are different.
Issue 01 (2016-04-29)

1739

Access Module
1.
mode.
2.
profile mode.
3.

enable command.
option 18/37.
1.
2.

The management channel for IPv6 and IPv4 services is the same.
Planning
Device or
Service
Management
channel
OLT

IP address
planning
(bridging ONT)
Internet
l IPv4 address: The PC obtains the IPv4 address

from the BRAS using PPPoE or IPoE.
address to the PC.
address to the PC. The private address is
translated to the public network address by
CGN (NAT44).
When the IPoE dial-up is used, the static
IPv4 address can be allocated to the PC.
l IPv6 address: The PC obtains the IPv4 address
from the BRAS using PPPoE or IPoE.
The PC can also obtain the IP address from
the BRAS using DHCPv6.
The PC can aslo obtain the IP address from
the BRAS using SLAAC.
When the IPoE dial-up is used, the static
IPv4 address can be allocated to the PC.
In all above-mentioned situations, the ONT is only
used for transparent transmission, but does not
participate in the address allocation.
Issue 01 (2016-04-29)

1740

Access Module
Planning
Device or
Service
IPTV service

using DHCPv6.
using SLAAC.
In all above-mentioned situations, the ONT is only
used for transparent transmission, but does not
participate in the address allocation.
VoIP service
The IPv4 protocol is still used. The ONT functions

as the DHCP client to obtain an IP address from
the DHCP server, or the NMS issues a static IP
address to the ONT using the configuration file.
Voice media/signaling flows at multiple POTS
ports share one IP address. Media flows are
differentiated by port.
QoS Planning
l
Voice service: IPv4
Internet service: It is recommended that devices use one flow to carry IPv6 and IPv4
Internet services. The QoS planning is the same for the flow that carries both IPv6 and
IPv4 Internet services and the flow that carries only the IPv4 Internet service.

Issue 01 (2016-04-29)

1741

Access Module

networking scenarios, and the voice protocol planning.
When the IPv6 protocol is used, the voice service still uses IPv4 to implement voice services.

VLAN data planning for IPv6 is consistent with that for IPv4. For details, see 9.2.5 Principle
of IPTV Service Data Plan.

This section describes IPv6 configuration procedure, and compares it with the IPv4
configuration procedure.
FTTH (Bridging ONT) Configuration Procedure

After IPv6 is introduced to the FTTH (bridging ONT) scenario, the service configuration
procedure is shown in the following figure. When IPv6 is introduced, the configurations for
security features and BTV multicast services on the OLT side are different from those of IPv4.
Other configurations do not change. For differences, see 18.2 Configuration Difference
Between IPv6 and IPv4.
Start
Add an ONT to an OLT
Configure Link Aggregation, Congestion

Control, and Security Policy
Configure the L2 HIS

service
Configure the voice

service
Configure the BTV

multicast service
Configure the VoD

service
Verifying services
End
NOTE
Issue 01 (2016-04-29)

1742

Access Module

Introduce the end-to-end service configuration based on the FTTH (Bridging ONT)

In this example, two ONTs are connected to the same PON port of the OLT. Triple play
services are required
l
Even after IPv6 is used, the OLT and ONT implement Layer 2 forwarding for HSI
service in this networking, irrespective of whether the access service is IPv4 or IPv6.
Service configurations for IPv4 and IPv6 are the same. For the HSI service from one end
user, one service flow is used to carry IPv6 and IPv4 Internet services, and the same
service VLAN is used.
For multicast service, the OLT is the node to make multicast duplication. The
VLAN on the OLT equipment.

The data of the bridging ONT can be configured through the web, the NMS, or the CLI at the
OLT side. In this example, the data of the ONT is configured through the CLI at the OLT side.
Item
Data
Memo
Profile name: ftth_dba
The ONTs are connected to the OLT

through the GPON port.
ONT data plan

DBA profile
Profile type: type3

Mbit/s
Mbit/s
ONT line profile
Profile name: ftth

T-CONT ID: 4
GEM port ID for
management services: 11
GEM port ID for voice
services: 12
GEM port ID for video
services: 13
access services: 14
Issue 01 (2016-04-29)

1743

Access Module
Item
Data
ONT service profile
Profile name: ftth
Memo
ONT port capability set:

adaptive
Network topology
data
PON port: 0/1/0

ONT IDs: 1 and 2
LAG data plan

LAG
Ports: 0/19/0 and 0/19/1

Working mode: LACP
static aggregation

source MAC address.

Queue scheduling

priority (SQ) mode

example.

on priorities
Security data plan
System security

Anti-ICMP attack:
disabled

example.

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
PPPoE Service
security
RAIO Type: PITP P
IPv4oE Service
security

82
RAIO Mode: common

RAIO Mode: common

IPv6oE Service
security
RAIO Type: DHCPv6

Option
RAIO Mode: common
Issue 01 (2016-04-29)

1744

Access Module
Item
Data
Memo
ONT line profile
Profile name: ftth
T-CONT ID: 4
access service: 14
ONT service profile
Profile name: ftth

adaptive
Traffic profile
Profile name: ftth_hsi

CIR: 4Mbit/s
Priority: 0
Network topology
data

PON port: 0/1/0
ONT IDs: 1 and 2
ID of the port on the ONT
that is connected to the
PC: 1

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 12
ONT service profile
Profile name: ftth

adaptive
Traffic profile
Profile name: ftth_voip

CIR: not limited
Priority: 5
Networking data
IP address of the MGC

server:
200.200.200.200/24
Port ID of the MGC
server: 2944
BTV multicast service data plan

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 13
Issue 01 (2016-04-29)

1745

Access Module
Item
Data
ONT service profile
Profile name: ftth
Memo

adaptive
Traffic profile
ID: 8
802.1p priority: 4
Priority-based scheduling
VLAN Plan
SVLAN ID: 1000

VLAN type: smart
VLAN Translation
Policy
ONT: duplicates packets

based on user ports and
multicast VLANs
(MVLANs) are stripped
off downstream.
OLT: duplicates multicast
packets based on PON
ports with MVLAN
unchanged.
Multicast service
data
Multicast protocol: IGMP

proxy
Multicast version:
IGMPv2
Multicast program:
dynamic obtaining mode
Program address area:
ff15::-ff15::ffff
VOD service data plan

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 13
ONT service profile
Profile name: ftth

adaptive
Traffic profile
ID: 8
802.1p priority: 4
Issue 01 (2016-04-29)

1746

Access Module
Item
Data
VLAN Plan
l SVLAN ID: 1100
Memo
l VLAN type: smart

l VLAN attribute:
common
l CVLAN=SVLAN
VLAN Translation
Policy
ONT: adds CVLAN tags

to iTV service packets.
OLT: transparently
transmits packets with
SVLANs.
Procedure

1.

ftth_dba, profile type to type3, assured bandwidth to 8 Mbit/s, and maximum bandwidth
to 20 Mbit/s.
huawei(config)#dba-profile add profile-name ftth_dba type3 assure 8192 max
20480
2.

huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name ftth_dba
3.

4.
Issue 01 (2016-04-29)
(Optional) Add an alarm profile. In this example, the default alarm profile is used, and
therefore the configuration of the alarm profile is not required.
1747

Access Module
Step 3 Add ONTs.

discovered ONT.
l
Add ONTs offline.

Confirm automatically discovered ONTs

NOTE


--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
Issue 01 (2016-04-29)

1748

Access Module
successfully.
Config state
: normal
the ONT is normal.
Match state
: match
l
ONU.
Step 5 Configure the traffic profile for the HSI service.

huawei(config)#traffic table ip name ftth_hsi cir 4096 priority 0 priority-policy
local-setting
Step 6 Configure the service port for the HSI service.

Scenario
VLAN Plan
Scenario 1
Double-tagged VLAN

l S-VLAN ID: 100

l S-VLAN type:
smart
l S-VLAN attribute:
stacking

l CVLAN ID: 1001

l C'-VLAN ID:
1010-1011
Issue 01 (2016-04-29)

1749

Access Module
Scenario
VLAN Plan
Scenario 2
Double-tagged VLAN
ONT: ONTs transparently transmit

untagged packets on the user side.
l S-VLAN: 100
l S-VLAN type:
smart
l S-VLAN attribute:
stacking
OLT: The OLT adds two VLAN tags

(S+C) to packets. The C-VLAN of
every ONT differs from each other.
l C-VLAN ID:
1001-1002
Scenario 1:
Configure the mapping between a GEM port and a VLAN. The service flow of C-VLAN
1001 is mapped to GEM port 14 in the ONT line profile.
Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the PC
through Ethernet port 1, add Ethernet port 1 to VLAN 1001 in the ONT service profile.
Configure the native VLAN of the ONT port. Set the native VLAN ID of Ethernet port 1
to 1001.
Create an Internet access service VLAN and add an upstream port to it. Add upstream
Create service flows. Set the service VLAN to 100, GEM port ID to 14, and user VLAN
to 1001. Use traffic profile ftth_hsi.
traffic-table name
traffic-table name
Scenario 2:
Configure the mapping between a GEM port and an Ethernet port on the ONT. Map the
service flow of Ethernet port 1 to GEM port 14 in the ONT line profile.
Issue 01 (2016-04-29)

1750

Access Module
Configure the ONT packet processing mode. If the ONT is connected to the PC through
Ethernet port 1, In the ONT service profile, set the packet transmission mode to TAG
transparent transmission for Ethernet port 1.
huawei(config-gpon-srvprofile-1)#port vlan eth 1 transparent
Create an Internet access service VLAN and add an upstream port to it. Add upstream
Create service flows. Set S-VLAN ID to 100 and GEM port ID to 14. Use traffic profile
ftth_hsi.
user-vlan untagged tag-transform add-double inner-vlan 1001 inbound traffictable
name ftth_hsi outbound traffic-table name ftth_hsi
user-vlan untagged tag-transform add-double inner-vlan 1002 inbound traffictable
name ftth_hsi outbound traffic-table name ftth_hsi
Step 7 Configure the traffic profile for the voice service.

huawei(config)#traffic table ip name ftth_voip cir off priority 5 priority-policy
local-setting
Step 8 Configure the VLAN translation policy and service flows for the voice service.
1.
Perform this step in the bridging ONT (single VLAN tag) scenario.
Scenario
VLAN Plan
Bridging ONT
Single VLAN tag
ONT: provides the VoIP

service and uses the same
SVLAN.
VLAN ID: 300

VLAN type: smart
Configure the mapping relationship between a GEM port and a VLAN. The service flow
of user VLAN 300 is mapped to GEM port 12 in the ONT line profile.
VLAN 300.
Issue 01 (2016-04-29)

1751

Access Module
to 300, and use traffic profile ftth_voip.
name
ftth_voip
name
ftth_voip
2.

name ftth_voip outbound traffic-table
name ftth_voip outbound traffic-table
Perform this step in the bridging ONT (double VLAN tags) scenario.
Scenario
VLAN Plan
Bridging ONT
Double VLAN tags
ONT: provides the VoIP

service and uses the same
CVLAN. A CVLAN
identifies a VoIP service.
SVLAN ID: 300

SVLAN type: smart
SVLAN attribute: stacking
CVLAN ID: 3001
OLT: implements VLAN

translation: C<->S+C.
VLAN 300.
to 3001, and use traffic profile ftth_voip.
service
user-vlan 3001 tag-transform default
outboun
d traffic-table name ftth_voip
service
user-vlan 3001 tag-transform default
outboun
gpon 0/1/0 ont 1 gemport 12 multiinbound traffic-table name ftth_voip

gpon 0/1/0 ont 2 gemport 12 multiinbound traffic-table name ftth_voip
Step 9 Configure ONT voice service profiles.

ONT voice service profiles include the interface common profile, MGC interface profile, and
POTS port profile.
l
Issue 01 (2016-04-29)
Interface common profile: saves common attributes of an ONT voice interface, including
mode.
1752

Access Module
media packets.
1.

1 is used.
2.

3.

Step 10 Configure the IP addresses of ONT H.248 users.

For ONT 1 and ONT 2, configure the IP address obtaining mode to the dhcp mode, set the
Step 11 Configure H.248 PSTN users.

1.
For ONT 1 and ONT 2, set the MG ID to 1, apply MGC interface profile 2 to ONT 1 and
be reapplied to the ONT so that the changed parameters can take effect.
2.
Add PSTN users.

For ONT 1 and ONT 2, create a PSTN user, set the MG ID to 1 (identical to the MG ID
the PSTN user is properly set.
------------------------------------------------------------------------------
Issue 01 (2016-04-29)

1753

Access Module
F/S/P
ONT ID
Port ID
: 0/1/0
: 1
: 1
MG ID
: 1
Terminal ID
: A0
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
: 1
Terminal ID
: A1
Step 12 Apply ONT voice service profiles

After ONT voice service profiles are applied, if parameters in those profiles are changed,
1.

1 is used.
2.


Step 14 Configure the traffic profile for the IPTV service.
local-setting
Step 15 Configure the VLAN translation policy and service port for the multicast service.
Configure the mapping relationship between a GEM port and an Ethernet port on the ONT. If
the ONT is connected to the STB through Ethernet port 2, map the service flow of Ethernet
port 2 to GEM port 13 in the ONT line profile.
Issue 01 (2016-04-29)

1754

Access Module
Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the STB
through Ethernet port 2, add Ethernet port 2 to VLAN 1000.
Configure the native VLAN of the ONT port. If the ONT is connected to the STB through
Ethernet port 2, the native VLAN ID is 1000.
1000.
untagged, and use traffic profile 8.
user-vlan untagged rx-cttr
user-vlan untagged rx-cttr
1
8
2
8
vlan 1000 gpon 0/1/0 ont 1 gemport 13 multi-service

tx-cttr 8
vlan 1000 gpon 0/1/0 ont 2 gemport 13 multi-service
tx-cttr 8
Step 16 Create an MVLAN and configure the IGMP version.

Set the IGMP version for the MVLAN to IGMP IPv6 v2.
Are you sure to change current IGMP IPv6 version? (y/n)[n]:y
Step 17 Configure a program library.

NOTE
huawei(config-mvlan1000)#igmp ipv6 mode off
Are you sure to close IGMP IPv6? (y/n)[n]:y
huawei(config-mvlan1000)#igmp ipv6 match mode disable
(Optional) Set the address range for the dynamic programs. If you need to limit the address
range of dynamic programs, perform this operation. For example, set the address range of
dynamic programs to ff15::-ff15::ffff.
huawei(config-mvlan1000)#igmp ipv6 match group ipv6 ff15:: to-ipv6 ff15::ffff
Step 18 Set the IGMP IPv6 mode.

Select the IGMP IPv6 proxy mode.
Are you sure to change IGMP IPv6 mode? (y/n)[n]:y
Issue 01 (2016-04-29)

1755

Access Module

Step 19 Configure the IGMP upstream port.

Set the IGMP upstream port ID to 0/19/0 and working mode to default. Protocol packets are
transmitted to all the IGMP upstream ports in the multicast VLAN.

Step 21 Configure the traffic profile for the VoD service.

local-setting
Step 22 Configure the VLAN translation policy and service port for the VoD service.
Configure the mapping relationship between a GEM port and a VLAN. The service flow of
user VLAN 1100 is mapped to GEM port 13 in the ONT line profile.
Configure the VLAN of the Ethernet port on the ONT. If the ONT is connected to the STB
through Ethernet port 2, add Ethernet port 2 to VLAN 1100.
Configure the native VLAN of the ONT port. If the ONT is connected to the STB through
Ethernet port 2, the native VLAN ID is 1100.
1100.
Create service flows. Set the service VLAN to 1100, GEM port ID to 13, and VLAN
translation mode to transparent transmission, and use traffic profile 8.
huawei(config)#service-port 3 vlan 1100 gpon 0/1/0 ont 1 gemport 13 rx-cttr 8 txcttr 8 tag-transform transparent
huawei(config)#service-port 4 vlan 1100 gpon 0/1/0 ont 2 gemport 13 rx-cttr 8 txcttr 8 tag-transform transparent
Issue 01 (2016-04-29)

1756

Access Module



Step 25 Save the configuration on the OLT side.

huawei(config)#save
----End
18.6 Configuring IPv6 Services in the FTTH (Gateway

ONT) Scenario
This section describes the methods for configuring IPv6 services in the FTTH (gateway ONT)
scenario.

The FTTH (gateway ONT) supports multiple IPv6 HSI and IPTV service solutions.
FTTH (Gateway ONT) Application Scenarios

As shown in Figure 18-7, the FTTH (gateway ONT) works with upper-layer devices to
support DS+NAT+PPPoE, DS+NAT+IPoE/DS-Lite+NAT+PPPoE HSI and DS+IPoE/DS
+PPPoE IPTV services in the Huawei fixed network IPv6 solution.
l
Voice service: The ONT with a bulit-in voice module can provide VoIP services for
users. The ONT can process VoIP services using IPv4.
Internet service: The PC and BRAS support the IPv4/IPv6 dual-stack and are connected
using the PPPoE or IPoE dial-up. The OLT and ONT have the same forwarding and
configuration methods for both IPv4 and IPv6 user services. The only difference is that
commands for configuring the ACL and security (DHCP option and anti-IP spoofing)
features are different.
Issue 01 (2016-04-29)
For DS+NAT+PPPoE and DS+NAT+IPoE solutions, both the ONT and BRAS
support IPv4/IPv6 dual-stack and are connected using PPPoE or IPoE. The ONT
must enable the IPv4 and IPv6 simultaneously at the WAN port. The OLT performs
Layer 2 forwarding for both IPv4 and IPv6 user services, which are configured
almost in the same way. The only difference is that commands for configuring the
ACL and security features (DHCP option and anti-IP spoofing) are different.
For DS-Lite+PPPoE, the BRAS must support IPv4/IPv6 dual-stack while the ONT
supports the DS-Lite. The ONT and BRAS are connected using PPPoE. The HGW
encapsulates IPv4 service packets into the 4in6 tunnel, and transmits them to the
CGN for decapsulation. The ONT must enable DS-Lite at the WAN port. The OLT
performs Layer 2 forwarding for both IPv4 and IPv6 user services, which are
configured almost in the same way. The only difference is that commands for
configuring DHCP option and anti-IP spoofing are different.
IPTV service: The STB supports IPv4/IPv6 dual-stack and carries IPTV services using
either IPv4 or IPv6.
1757

Access Module
When the STB uses IPoE and the OLT functions as the multicast duplicate point,
the process for configuring IPv6 and IPv4 multicast services is the same, but
commands are different. The OLT and ONU perform bridge forwarding for both
IPv4 and IPv6 user services, which can be configured almost in the same way.
When the STB uses PPPoE, it directly connects to the BRAS by PPPoE. The OLT
and ONT only forward PPPoE services instead of processing multicast services.
This solution is not recommended.
Figure 18-7 FTTH (gateway ONT) service networking

PC
ONT
STB
TV
PE-AGG
OLT
NGN/IMS
UPE
BRAS
Phone
PC
TV
Optical
splitter
STB
CGN
IPTV
Headend
Internet
UPE
ONT
PE-AGG
Phone
18.6.2 Data Plan

Security Planning
In the FTTH (gateway ONT) networking scenario, only anti-IP spoofing and DHCP option of
IPv6 and IPv4 services are different.
1.
mode.
2.
profile mode.
3.

enable command.
option 18/37.
Issue 01 (2016-04-29)

1758

Access Module
1.
2.

Planning
Device or
Service
Management
channel
OLT

IP address
planning
(gateway ONT)
Internet
l IPv4 address: An ONT obtains the IPv4

address can be configured. Meanwhile, as the
DHCP server, the ONT allocates private
network IP addresses to PCs. The NAT
function enables these PCs to go online by
sharing the IPv4 address allocated by the
BRAS.
address to an ONT.
address to an ONT. The private network
l IPv6 address: An ONT obtains the IPv6
address from the BRAS using PPPoE, SLAAC,
or DHCPv6. If IPoE dial-up is used, the static
address can be configured. Meanwhile, the
ONT as the DHCP server obtains the prefix of
an IPv6 address, and allocates IPv6 addresses
to connected PCs using the network cable or
WiFi.
IPTV service

using DHCPv6.
using SLAAC.
Issue 01 (2016-04-29)

1759

Access Module
Planning
Device or
Service
VoIP service
The IPv4 protocol is still used. The ONT functions

as the DHCP client to obtain an IP address from
the DHCP server, or the NMS issues a static IP
address to the ONT using the configuration file.
Voice media/signaling flows at multiple POTS
ports share one IP address. Media flows are
classified by port.
TR069
management
The IPv4 protocol is still used. For scenarios in

which TR069 is required for management
maintenance and service provisioning, the ONT
functions as the DHCP client to obtain a public
network IP address from the DHCP server to
connect the TR069 server ACS.
QoS Planning
l
Voice service: IPv4


Issue 01 (2016-04-29)

1760

Access Module

VLAN data planning for IPv6 is consistent with that for IPv4. IGMP protocol differences are
demonstrated in the configuration procedure.

This section describes IPv6 configuration procedure, and compares it with the IPv4
configuration procedure.
FTTH (Gateway ONT) Configuration Procedure

After IPv6 is introduced to the FTTH (gateway ONT) scenario, the service configuration
procedure is shown in the following figure. When IPv6 is introduced, the configurations for
security features, Layer 3 Internet services, bridging WAN multicast services are different
from those of IPv4. For differences, see 18.2 Configuration Difference Between IPv6 and
IPv4.
Start
Add an ONT to an OLT
Configure Link Aggregation, Congestion

Control, and Security Policy
Configure L3 HSI
service
Configure the voice

service
Configure the bridge

WAN multicast service
Configure the VoD

service
Verifying Services
End
NOTE

Introduce the end-to-end service configuration based on the FTTH (Gateway ONT)
Issue 01 (2016-04-29)

1761

Access Module

In this example, two ONTs are connected to the same PON port of the OLT. Triple play
services are required
l
Even after IPv6 is used, the OLT implement Layer 2 forwarding for HSI service in this
networking, irrespective of whether the access service is IPv4 or IPv6. Service
configurations for IPv4 and IPv6 are the same. For the HSI service from one end user,
one service flow is used to carry IPv6 and IPv4 Internet services, and the same service
VLAN is used. The gateway ONT requires specific configuration to enable the IPv4/
IPv6 dual stack or the DS-Lite for the HSI service.
For multicast service, the OLT is the node to make multicast duplication. The
VLAN on the OLT equipment.

Web or the NMS is recommended to configure the gateway ONT layer 3 HSI service. CLI
through the OLT is recommended to configure the gateway ONT voice service. The WAN
interface for multicast service on the ONT is configured by iTMS.
Item
Data
Memo
Profile name: ftth_dba
The ONTs are connected to the OLT

through the GPON port.
ONT data plan

DBA profile
Profile type: type3

Mbit/s
Mbit/s
ONT line profile
Profile name: ftth

T-CONT ID: 4
GEM port ID for
management services: 11
GEM port ID for voice
services: 12
GEM port ID for video
services: 13
access services: 14
ONT service profile
Profile name: ftth

adaptive
Network topology
data
Issue 01 (2016-04-29)
PON port: 0/1/0

ONT IDs: 1 and 2

1762

Access Module
Item
Data
Memo
Ports: 0/19/0 and 0/19/1

source MAC address.
LAG data plan

LAG
Working mode: LACP

static aggregation

Queue scheduling

priority (SQ) mode

example.

on priorities
Security data plan
System security

Anti-ICMP attack:
disabled

example.

User security
Anti-MAC duplicate:
disabled

example.
Anti-IP sproofing:
disabled
PPPoE Service
security
RAIO Type: PITP P
IPv4oE Service
security

82
RAIO Mode: common

RAIO Mode: common

IPv6oE Service
security
RAIO Type: DHCPv6

Option
RAIO Mode: common

ONT line profile
Profile name: ftth
For details, see 18.6.2 Data Plan.
T-CONT ID: 4
GEM port ID: 14
ONT service profile
Profile name: ftth

adaptive
Issue 01 (2016-04-29)

1763

Access Module
Item
Data
Traffic profile
Profile name: ftth_hsi
Memo
CIR: 4Mbit/s
Priority: 0
Network topology
data

PON port: 0/1/0
ONT IDs: 1 and 2
ID of the port on the ONT
that is connected to the
PC: 1

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 12
ONT service profile
Profile name: ftth

adaptive
Traffic profile
Profile name: ftth_voip

CIR: not limited
Priority: 5
Networking data
IP address of the MGC

server:
200.200.200.200/24
Port ID of the MGC
server: 2944
Bridge WAN multicast service data plan

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 13
ONT service profile
Profile name: ftth

adaptive
Traffic profile
ID: 8
802.1p priority: 4
Issue 01 (2016-04-29)

1764

Access Module
Item
Data
VLAN Plan
SVLAN ID: 1000
Memo
VLAN type: smart

VLAN Translation
Policy
ONT: duplicates packets

based on user ports and
multicast VLANs
(MVLANs) are stripped
off downstream.
OLT: duplicates multicast
packets based on PON
ports with MVLAN
unchanged.
Multicast service
data
Multicast protocol: IGMP

proxy
Multicast version:
IGMPv2
Multicast program:
dynamic obtaining mode
Program address area:
ff15::-ff15::ffff
VOD service data plan

ONT line profile
Profile name: ftth
T-CONT ID: 4
GEM port ID: 13
ONT service profile
Profile name: ftth

adaptive
Traffic profile
ID: 8
802.1p priority: 4
VLAN Plan
Single VLAN tag

l SVLAN ID: 1100
l VLAN type: smart
l VLAN attribute:
common
l CVLAN: 2001
Issue 01 (2016-04-29)

1765

Access Module
Item
Data
VLAN Translation
Policy
The ONT adds CVALN

tags (configured on the
iTMS) to packets: untag<>C.
Memo
The OLT implements

VLAN translation: C<->S.
Procedure

1.

ftth_dba, profile type to type3, assured bandwidth to 8 Mbit/s, and maximum bandwidth
to 20 Mbit/s.
huawei(config)#dba-profile add profile-name ftth_dba type3 assure 8192 max
20480
2.

huawei(config-gpon-lineprofile-1)#tcont 4 dba-profile-name ftth_dba
3.

4.
(Optional) Add an alarm profile. In this example, the default alarm profile is used, and
therefore the configuration of the alarm profile is not required.
Step 3 Add ONTs.

Issue 01 (2016-04-29)

1766

Access Module
discovered ONT.
l
Add ONTs offline.

Confirm automatically discovered ONTs

NOTE


--------------------------------------------------------------------F/S/P
: 0/1/0
ONT-ID
: 1
Control flag
: active
activated.
Run state
: online
successfully.
Config state
: normal
the ONT is normal.
Match state
: match
Issue 01 (2016-04-29)

1767

Access Module
ONU.
Step 5 Configure the traffic profile for the HSI service.

huawei(config)#traffic table ip name ftth_hsi cir 4096 priority 0 priority-policy
local-setting
Step 6 Configure the VLAN translation policy and the service port for the HSI service.
Scenario
VLAN Plan
Scenario 1
Double VLAN tags
ONT: The iTMS factory default setting

(untag) is used.
l SVLAN ID: 100

l SVLAN type: smart
l SVLAN attribute:
stacking
OLT: performs VLAN translation:

Untag<->S+C. The OLT adds different
CVLANs to packets from different
ONTs.
l CVLAN ID:
1001-1002
Scenario 2
Double VLAN tags

l SVLAN ID: 100
l SVLAN type: smart
l SVLAN attribute:
stacking
ONT: The iTMS configures CVLANs

in a unified manner.
OLT: performs VLAN translation: C<>S+C'. The OLT translates CVLANs
from different ONTs to different
C'VLANs.
l C'VLAN ID:
1010-1011
l CVLAN ID: 1001
Scenario 1:
Configure the ONT packet processing mode. In the ONT service profile, set the packet
transmission mode to TAG transparent transmission for Ethernet port 1.
huawei(config-gpon-srvprofile-1)#port vlan eth 1 transparent
Issue 01 (2016-04-29)

1768

Access Module
VLAN 100.
Create service flows. Set SVLAN ID to 100 and GEM port ID to 14. Use traffic profile
ftth_hsi.
user-vlan untagged tag-transform add-double inner-vlan 1001 inbound traffictable name
user-vlan untagged tag-transform add-double inner-vlan 1002 inbound traffictable name
Scenario 2:
VLAN 100.
to 1001, and use traffic profile ftth_hsi.
traffic-table name
traffic-table name
Step 7 Configure the traffic profile for the voice service.

huawei(config)#traffic table ip name ftth_voip cir off priority 5 priority-policy
local-setting
Step 8 Configure the VLAN translation policy and service port for the voice service.
Issue 01 (2016-04-29)

1769

Access Module

Scenario
VLAN Plan
Scenario 1
Single VLAN tag
ONT: The iTMS issues the

VLAN of the WAN port or
factory default setting is used.
l SVLAN ID: 300

l SVLAN type: smart
l CVLAN ID: 300
Scenario 2
Single VLAN tag

l SVLAN ID: 300
l SVLAN type: smart
l CVLAN ID: 3001
OLT: transparently transmits

VLAN (CVLAN is the same as
the planned SVLAN).
ONT: The iTMS issues the
VLAN of the WAN port or
factory default setting is used.
OLT: performs VLAN
translation: C<->S (CVLAN is
SVLAN).
Scenario 1:
300.
300, and use traffic profile ftth_voip.
ftth_voip
ftth_voip

Scenario 2:
300.
Issue 01 (2016-04-29)

1770

Access Module

3001. Use traffic profile ftth_voip.
user-vlan 3001 tag-transform translate inbound traffic-table name ftth_voip
outboun
user-vlan 3001 tag-transform translate inbound traffic-table name ftth_voip
outboun
Step 9 Configure ONT voice service profiles.

ONT voice service profiles include the interface common profile, MGC interface profile, and
POTS port profile.
l
Interface common profile: saves common attributes of an ONT voice interface, including
mode.
media packets.
1.

1 is used.
2.

3.

Step 10 Configure the IP addresses of ONT H.248 users.

For ONT 1 and ONT 2, configure the IP address obtaining mode to the dhcp mode, set the
Issue 01 (2016-04-29)

1771

Access Module
Step 11 Configure H.248 PSTN users.

1.
For ONT 1 and ONT 2, set the MG ID to 1, apply MGC interface profile 2 to ONT 1 and
be reapplied to the ONT so that the changed parameters can take effect.
2.
Add PSTN users.

For ONT 1 and ONT 2, create a PSTN user, set the MG ID to 1 (identical to the MG ID
the PSTN user is properly set.
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 1
Port ID
: 1
MG ID
: 1
Terminal ID
: A0
-----------------------------------------------------------------------------F/S/P
: 0/1/0
ONT ID
: 2
Port ID
: 1
MG ID
: 1
Terminal ID
: A1
Step 12 Apply ONT voice service profiles

After ONT voice service profiles are applied, if parameters in those profiles are changed,
1.

1 is used.
2.

Issue 01 (2016-04-29)

1772

Access Module
Step 14 Configure the traffic profile for the IPTV service.
local-setting
Step 15 Configure the VLAN translation policy and service port for the multicast service.
1.

2.
mode.
3.

4.

traffic profile ftth_iptv.
name ftth_iptv
name ftth_iptv
Step 16 Create an MVLAN and configure the IGMP version.

Set the IGMP version for the MVLAN to IGMP IPv6 v2.
Are you sure to change current IGMP IPv6 version? (y/n)[n]:y
Step 17 Configure a program library.

Issue 01 (2016-04-29)

1773

Access Module
NOTE
huawei(config-mvlan1000)#igmp ipv6 mode off
Are you sure to close IGMP IPv6? (y/n)[n]:y
huawei(config-mvlan1000)#igmp ipv6 match mode disable
(Optional) Set the address range for the dynamic programs. If you need to limit the address
range of dynamic programs, perform this operation. For example, set the address range of
dynamic programs to ff15::-ff15::ffff.
huawei(config-mvlan1000)#igmp ipv6 match group ipv6 ff15:: to-ipv6 ff15::ffff
Step 18 Set the IGMP IPv6 mode.

Select the IGMP IPv6 proxy mode.
Are you sure to change IGMP IPv6 mode? (y/n)[n]:y
Step 19 Configure the IGMP upstream port.

Set the IGMP upstream port ID to 0/19/0 and working mode to default. Protocol packets are
transmitted to all the IGMP upstream ports in the multicast VLAN.

Step 21 Configure the VLAN translation policy and service port for the VoD service.
1.

2.

VLAN 1000.
3.
Issue 01 (2016-04-29)

1774

Access Module

4.

Set the service VLAN to 1000, GEM port ID to 13, and VLAN translation mode to
transparent transmission, and use traffic profile ftth_iptv.




Step 24 Save the configuration on the OLT side.

huawei(config)#save
Step 25 Log in to the Web configuration window.

1.
Configure the IP address of the PC network adapter to be in the same network segment
with the IP address of the local maintenance Ethernet port on the ONT (default:
192.168.100.1).
2.
Open the Web browser, and enter the IP address of the local maintenance Ethernet port
on the ONT. In the login window, enter the user name (default: telecomadmin) and
password (default: admintelecom) of the administrator. After the password is
authenticated, the Web configuration window is displayed.
NOTE
The following steps are configured on the ONT through the web page.
Step 26 Configure the working mode for the LAN port.

1.
Choose LAN > LAN Port Work Mode from the navigation tree. Select the check box
next to LAN1 to set port LAN1 to work in Layer 3 mode. Figure 18-8 shows the
parameter settings.
Figure 18-8 Parameter settings on the Web page for the LAN port
Issue 01 (2016-04-29)

1775

Access Module
2.
Click Apply to make the configuration take effect.
Step 27 Configure parameters for a WAN interface.

1.
Choose WAN > WAN Configuration from the navigation tree.
2.
In the right pane, click New. In the dialog box that is displayed, set the parameters as
follows:
Select Enable WAN Connection to enable the new WAN connection.
Set Encapsulation Mode to PPPOE or IPOE according to the IPv6 HSI solution.
Set Protocol Type to IPv4/IPv6 (dual stack) or IPv6 (DS-Lite).
Set Mode to Route WAN.
Set Service List to INTERNET.
Select Enable VLAN.
Set VLAN ID to 1001.
Set 802.1p to 0.
Set User Name to iadtest@pppoe and Password to iadtest.
Select the check box next to LAN1 in the Binding options area, indicating that the
WAN port is bound to LAN1.
IPv4 Information
Set IP Acquisition Mode to PPPoE when PPPoE is adopted for HSI. Set IP
Acquisition Mode to Static or DHCP according to the data plan.
Select Enable NAT to enable the NAT function.
IPv6 Information
DHCP-PD is recommended for Prefix Acquisition Mode.
DHCP is recommended for IP Acquisition Mode.
In case of DS-Lite solution and the Protocol Type in the Basic Information field is
set to IPv6, set the DSLite Work Mode to Auto.
Figure 18-9 shows the parameter settings.
Issue 01 (2016-04-29)

1776

Access Module
Figure 18-9 Parameter settings on the Web page for the WAN port
3.
Click Apply to make the configuration take effect.
----End
Issue 01 (2016-04-29)

1777

MA5600T&MA5603T&MA5608T V800R017C00 Commissioning and Configuration Guide 01 PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MA5600T&MA5603T&MA5608T V800R017C00 Commissioning and Configuration Guide 01 PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

SmartAX MA5600T/MA5603T/MA5608T Multiservice Access Module

Commissioning and Configuration

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

About This Document

About This Document

Installation and commissioning engineers

System maintenance engineers

Data configuration engineers

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

About This Document

The keywords of a command line are in boldface.

Command arguments are in italics.

Items (keywords or arguments) in square brackets [ ] are

Alternative items are grouped in braces and separated by

Optional alternative items are grouped in square brackets

Alternative items are grouped in braces and separated by

Buttons, menus, parameters, tabs, window, and dialog

Multi-level menus are in boldface and separated by the

Updates in Issue 01 (2016-04-29)

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

1.4.5 Commissioning the Interconnection with the SIP Interface.................................................................................... 169

3 Configuration Example of DSLAM Services....................................................................... 228

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

4 Configuration Example of the Private Line Service........................................................... 362

5 Configuration Example of the MSTP Subtending Network............................................ 412

6 Configuration Example of the VPLS..................................................................................... 460

7 Configuration Example of the Subtending Networking .................................................. 477

8 FTTx Configuration Summary................................................................................................513

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

9.1 Basic Concepts........................................................................................................................................................... 516

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

9.5.11 Configuring the VoD Service.................................................................................................................................653

10 FTTB and FTTC Configuration.............................................................................................683

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

10.6 FTTB/FTTC+HGW Networking (GPON Networking, Voice Service Provided by ONU).....................................781

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

11 FTTO Configuration (SOHO and SME)............................................................................. 933

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

11.4.9 Configuring the H.248-based Voice Service (Through the CLI).........................................................................1006

12 FTTO Configuration (Large-sized Enterprise Access)................................................... 1080

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

12.5.5 Configuring TDM Connections........................................................................................................................... 1119

Huawei Proprietary and Confidential

SmartAX MA5600T/MA5603T/MA5608T Multi-service

12.9.8 Configuring Clock Synchronization.................................................................................................................... 1182

13 FTTM Configuration (Base Station Access)..................................................................... 1187