MA5616 V800R311C01 Configuration Guide 02

SmartAX MA5616 Multi-service Access Module
V800R311C01
Configuration Guide
Issue
02
Date
2013-10-08
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. 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 02 (2013-10-08)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Configuration Guide
About This Document
About This Document

Intended Audience
This document describes the configuration of important services supported by the MA5616. The
description covers the following topics:
l
Purpose
Networking
Data plan
Prerequisite(s)
Note
Configuration flowchart
Operation procedure
Result
This document helps users to know the configuration of important services on the MA5616.
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
Indicates a hazard with a high level of risk which, if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk which,
if not avoided, could result in minor or moderate injury.
Issue 02 (2013-10-08)

ii

Configuration Guide
Symbol
About This Document
Description
Indicates a potentially hazardous situation that, if not
avoided, could cause equipment damage, data loss, and
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
your time.
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.
Issue 02 (2013-10-08)
Compared with issue 01 (2012-08-01)of V800R311C01, issue 02 (2013-10-08) has the
following changes:
Issue 02 (2013-10-08)

iii

Configuration Guide
About This Document
Modified: 3.1.4 Configuring Inband Management (GE Upstream)
Issue 01 (2012-08-01)
Compared with issue 01 (2012-07-25) of V800R311C00, issue 01 (2012-08-01) has the
following changes:
Added:
l
4.4 (Optional) Configuring Line Bonding
4.8 (Optional) Configuring the VDSL2 Vectoring Function
Deleted:
l
Configuring the Ethernet Access Service
Configuration Example of the Ethernet Access Service in the Single-Port for Multi-Service
Mode
Issue 02 (2013-10-08)

iv

Configuration Guide
Contents
Contents
About This Document.....................................................................................................................ii
1 Deploying Network Devices.......................................................................................................1
1.1 Introduction to the Network Device Deployment..........................................................................................................2
1.2 Example of Deploying Network Devices (GPON Upstream)........................................................................................3
1.3 Configuration Example of Network Device Deployment Using GE Upstream Transmission......................................7
2 Checking Before the Configuration.........................................................................................11

2.1 Checking the Software Version....................................................................................................................................12
2.2 Checking the Board Status...........................................................................................................................................12
3 Basic Configuration.....................................................................................................................14
3.1 Configuring the Maintenance Terminal.......................................................................................................................16
3.1.1 Configuring Management Through a Local Serial Port............................................................................................16
3.1.2 Configuring Outband Management...........................................................................................................................22
3.1.3 Configuring Inband Management (GPON Upstream)...............................................................................................35
3.1.4 Configuring Inband Management (GE Upstream)....................................................................................................37
3.2 Configuring the U2000.................................................................................................................................................50
3.2.1 Configuring the U2000 (Based on SNMPv1)............................................................................................................50
3.2.2 Configuring the U2000 (Based on SNMPv2c)..........................................................................................................56
3.2.3 Configuring the U2000 (Based on SNMPv3)............................................................................................................60
3.3 Configuring the Attributes of the Upstream Port.........................................................................................................66
3.3.1 (Optional) Configuring an Uplink Ethernet Port.......................................................................................................66
3.3.2 Configuring the Attributes of an Uplink GPON Port................................................................................................69
3.4 Configuring the ANCP.................................................................................................................................................70
3.5 Configuring a VLAN....................................................................................................................................................73
3.5.1 Configuring a VLAN.................................................................................................................................................75
3.5.2 Configuring the VLAN Forwarding Policy...............................................................................................................77
3.5.3 Configuring a VLAN Service Profile........................................................................................................................78
3.6 Configuring Basic IPv6 Information............................................................................................................................82
3.6.1 Configuring an IPv6 Address for an Interface...........................................................................................................83
3.6.2 Configuring an IPv6 Address Selection Policy Table...............................................................................................85
3.6.3 Configuring IPv6 Neighbor Discovery......................................................................................................................87
3.6.4 Configuring PMTU....................................................................................................................................................90
Issue 02 (2013-10-08)


Configuration Guide
Contents
3.7 Configuring a Route.....................................................................................................................................................91

3.7.1 Configuring an IPv4 Static Route..............................................................................................................................91
3.7.2 Configuring an IPv6 Static Route..............................................................................................................................92
3.8 Configuring the System Clock.....................................................................................................................................94
3.8.1 Configuring the Reference Source of the System Clock...........................................................................................94
3.8.2 Configuring the Priority of the System Clock...........................................................................................................96
3.9 Configuring the NTP Time...........................................................................................................................................97
3.9.1 (Optional) Configuring NTP Authentication.............................................................................................................98
3.9.2 Configuring the NTP Broadcast Mode......................................................................................................................99
3.9.3 Configuring the NTP Multicast Mode.....................................................................................................................101
3.9.4 Configuring the NTP Unicast Server Mode............................................................................................................103
3.9.5 Configuring the NTP Peer Mode.............................................................................................................................105
3.10 Configuring the User Security..................................................................................................................................107
3.10.1 Configuring Anti-Theft and Roaming of User Account Through PITP................................................................108
3.10.2 Configuring Anti-Theft and Roaming of User Accounts Through DHCPv4........................................................113
3.10.3 Configuring Anti-Theft and Roaming of User Accounts Through DHCPv6........................................................117
3.10.4 Configuring the Anti-IP Address Attack...............................................................................................................120
3.10.5 Configuring the Anti-MAC Address Attack ........................................................................................................122
3.11 Configuring System Security....................................................................................................................................125
3.11.1 Configuring Firewall.............................................................................................................................................126
3.11.2 Configuring Anti-Attack........................................................................................................................................128
3.11.3 Preventing the Access of Illegal Users..................................................................................................................130
3.11.4 Enabling the Ring Network Detection on the User Side.......................................................................................132
3.12 Configuring AAA.....................................................................................................................................................133
3.12.1 Configuring the Local AAA..................................................................................................................................134
3.12.2 Configuring the Remote AAA (Based on the RADIUS Protocol)........................................................................135
3.12.3 Configuring the Remote AAA (Based on the HWTACACS Protocol)................................................................139
3.12.4 Configuration Example of the AAA Based on the RADIUS Protocol (802.1X Access Users)............................143
3.12.5 Configuration Example of the AAA Based on the HWTACACS Protocol (802.1X Access Users)....................146
3.12.6 Configuration Example of the Authentication Based on the RADIUS Protocol (Device Management Users)
..........................................................................................................................................................................................150
3.12.7 Configuration Example of the Authentication Based on the HWTACACS Protocol (Device Management Users)
..........................................................................................................................................................................................153
3.13 Configuring the ACL for Packet Filtering................................................................................................................156
3.13.1 Configuration Differences Between IPv4 ACLs and IPv6 ACLs.........................................................................158
3.13.2 Configuring the Basic ACL for Packet Filtering...................................................................................................158
3.13.3 Configuring the Advanced ACL for Packet Filtering...........................................................................................159
3.13.4 Configuring the Link Layer ACL for Packet Filtering..........................................................................................161
3.14 Configuring QoS.......................................................................................................................................................162
3.14.1 Configuring Traffic Management..........................................................................................................................163
3.14.2 Configuring Queue Scheduling.............................................................................................................................171
3.14.3 Configuring Early Drop.........................................................................................................................................175
Issue 02 (2013-10-08)

vi

Configuration Guide
Contents
3.14.4 Configuring Traffic Management Based on ACL Rules.......................................................................................178

3.15 Configuring Environment Monitoring......................................................................................................................181
3.15.1 Configuring Monitoring Through the ESC...........................................................................................................181
3.15.2 Configuring Monitoring Through the Power System............................................................................................189
3.15.3 Configuring the Heat Exchanger Environment Monitoring Parameters...............................................................207
3.15.4 Configuring the Monitoring Through the Fan Tray..............................................................................................209
4 Configuring the xDSL Internet Access Service...................................................................211

4.1 Configuring the xDSL Profile....................................................................................................................................215
4.1.1 Configuring an ADSL2+ Profile.............................................................................................................................215
4.1.2 Configuring the SHDSL Profile..............................................................................................................................221
4.1.3 Configuring the VDSL2 Profile..............................................................................................................................222
4.1.4 Configuring xDSL Profiles (TR165 Mode).............................................................................................................231
4.2 Configuring a VLAN..................................................................................................................................................235
4.3 Configuring an Upstream Port....................................................................................................................................236
4.4 (Optional) Configuring Line Bonding........................................................................................................................237
4.5 Configuring an xDSL Port..........................................................................................................................................239
4.6 Creating an xDSL Service Port..................................................................................................................................242
4.7 (Optional) Configuring the xPoA-xPoE Protocol Conversion...................................................................................247
4.8 (Optional) Configuring the VDSL2 Vectoring Function...........................................................................................249
5 Configuring the Multicast Service (MVLAN Mode)..........................................................252

5.1 Default Settings of the Multicast Service...................................................................................................................254
5.2 Configuration Differences Between IPv4 Multicase and IPv6 Multicast..................................................................254
5.3 Configuring the Multicast Service on a Single-NE Network.....................................................................................257
5.3.1 Configuring Multicast Global Parameters...............................................................................................................258
5.3.2 Configuring the Multicast Program.........................................................................................................................262
5.3.3 Configuring the Multicast User...............................................................................................................................270
5.3.4 (Optional) Configuring the Multicast Bandwidth...................................................................................................275
5.3.5 (Optional) Configuring the Multicast Preview........................................................................................................278
5.3.6 (Optional) Configuring the Program Prejoin...........................................................................................................283
5.3.7 (Optional) Configuring the Multicast Log...............................................................................................................285
5.4 Configuring the Multicast Service on a Subtending Network....................................................................................290
6 Configuring the Voice Service................................................................................................296

6.1 Configuring the VoIP PSTN Service (Based on the H.248 Protocol)........................................................................298
6.1.1 Configuring an MG Interface..................................................................................................................................303
6.1.2 Configuring the VoIP PSTN User...........................................................................................................................320
6.2 Configuring the VoIP PSTN Service (Based on the SIP Protocol)............................................................................330
6.2.1 Configuring the SIP Interface..................................................................................................................................334
6.2.2 Configuring the VoIP PSTN User...........................................................................................................................343
6.3 Configuring the VoIP ISDN BRA Service (Based on the H.248 Protocol)...............................................................354
6.3.1 Configuring an MG Interface..................................................................................................................................361
Issue 02 (2013-10-08)

vii

Configuration Guide
Contents
6.3.2 Configuring the IUA Link.......................................................................................................................................378

6.3.3 Configuring the VoIP ISDN BRA User..................................................................................................................380
6.4 Configuring the VoIP ISDN BRA Service (Based on the SIP Protocol)...................................................................386
6.4.1 Configuring the SIP Interface..................................................................................................................................389
6.4.2 Configuring the VoIP ISDN BRA User..................................................................................................................398
6.5 Configuring the FoIP Service (Based on the H.248 Protocol)...................................................................................405
6.6 Configuring the FoIP Service (Based on the SIP Protocol).......................................................................................408
6.7 Configuring the MoIP Service (Based on the H.248 Protocol)..................................................................................410
6.8 Configuring the MoIP Service (Based on the SIP Protocol)......................................................................................413
6.9 Configuring the Security and Reliability of the Voice Service..................................................................................415
6.9.1 Configuring the Device Authentication...................................................................................................................415
6.9.2 Configuring the Dual Homing.................................................................................................................................418
6.9.3 Configuring the Emergency Standalone..................................................................................................................421
7 Configuring the Ethernet OAM..............................................................................................423

7.1 Configuring the Ethernet CFM OAM........................................................................................................................424
7.2 Configuring the Ethernet EFM OAM.........................................................................................................................427
8 Configuring Network Protection............................................................................................431

8.1 Configuring the MSTP...............................................................................................................................................432
8.2 Configuring the Link Aggregation of Uplink Ethernet Port ......................................................................................435
9 Configuration Example of Services on the MA5616 Through GE Upstream Transmission

..........................................................................................................................................................437
9.1 Configuration Example of the xDSL Internet Access Service...................................................................................439
9.1.1 Configuration Example of the PPPoE xDSL Internet Access Service....................................................................439
9.1.2 Configuration Example of the IPoE xDSL Internet Access Service.......................................................................447
9.1.3 Configuration Example of the PPPoA xDSL Internet Access Service....................................................................454
9.1.4 Configuration Example of the IPoA xDSL Internet Access Service.......................................................................462
9.1.5 Configuration Example of VDSL2 Bonding Services............................................................................................469
9.2 Configuration Example of the Multicast Service (Multicast VLAN Mode)..............................................................474
9.2.1 Configuration Example of the Multicast Video Service (Static Configuration Mode)...........................................474
9.2.2 Configuration Example of the Multicast Video Service (Dynamic Configuration Mode).....................................478
9.3 Configuration Example of the VoIP Service..............................................................................................................482
9.3.1 Configuration Example of the VoIP PSTN Service (Based on the H.248 Protocol)..............................................482
9.3.2 Configuration Example of the VoIP PSTN Service (Based on the SIP Protocol)..................................................491
9.3.3 Configuration Example of the VoIP ISDN BRA Service (Based on the H.248 Protocol)......................................495
9.3.4 Configuration Example of the VoIP ISDN BRA Service (Based on the SIP Protocol)..........................................501
9.4 Configuration Example of the VAG Service..............................................................................................................506
9.4.1 Configuration Example of the VAG Service (Based on the H.248 Protocol).........................................................506
9.4.2 Configuration Example of the VAG Service (Based on the SIP Protocol).............................................................514
9.5 Configuration Example of the VLAN Stacking Wholesale Service..........................................................................520
9.5.1 Configuring the VLAN Stacking Wholesale Service..............................................................................................520
Issue 02 (2013-10-08)

viii

Configuration Guide
Contents
9.5.2 Configuring the VLAN ID Extension Service........................................................................................................524

9.6 Configuration Example of the QinQ VLAN Private Line Service.............................................................................527
9.7 Configuring the Triple Play Service...........................................................................................................................531
9.7.1 Configuration Example of the Triple Play Service - Single PVC for Multiple Services Based on the User-Side VLAN
..........................................................................................................................................................................................531
9.7.2 Configuration Example of the Triple Play Service - Single PVC for Multiple Services Based on the User-Side 802.1p
..........................................................................................................................................................................................538
9.7.3 Configuration Example of the Triple Play Service - Multiple PVCs for Multiple Services...................................545
10 FTTB and FTTC Service Overview......................................................................................552

10.1 Basic Concept...........................................................................................................................................................553
10.2 Scenario and Hardware Configuration.....................................................................................................................555
10.3 Scenario and Hardware Configuration (10G GPON)...............................................................................................557
10.4 GPON ONU Capability Sets....................................................................................................................................559
10.5 10G GPON ONU Capability Sets............................................................................................................................564
11 Principle of FTTB and FTTC Data Plan..............................................................................565

11.1 Principle of Security Data Plan................................................................................................................................566
11.2 Principle of Device Management Data Plan.............................................................................................................568
11.3 Principle of QoS Data Plan.......................................................................................................................................569
11.4 (Optional) Principle of Vectoring Data Plan............................................................................................................572
11.5 Principle of Internet Access Service Data Plan........................................................................................................573
11.6 Principle of VoIP Service Data Plan........................................................................................................................575
11.7 Principle of IPTV Service Data Plan........................................................................................................................578
12 Configuring Services in Various FTTB and FTTC Scenarios (GPON and 10G GPON
Access).............................................................................................................................................582
12.1 FTTB Networking (LAN Access Without HGW)...................................................................................................584
12.1.1 Service Requirements and Application Scenarios.................................................................................................584
12.1.2 Configuration Procedure........................................................................................................................................585
12.1.3 Adding an ONU to an OLT...................................................................................................................................586
12.1.4 Configuring the Management Channel Between the OLT and the ONU..............................................................590
12.1.5 Configuring the Service Channel Between the OLT and the ONU.......................................................................591
12.1.6 Configuring Link Aggregation, Congestion Control, and Security Policies.........................................................594
12.1.7 Configuring LAN Internet Access Service (On the ONU)....................................................................................597
12.1.8 Configuring H.248 Voice Service (on the ONU)..................................................................................................598
12.1.9 Configuring SIP Voice Service (on the ONU)......................................................................................................602
12.1.10 Verifying Services...............................................................................................................................................605
12.2 FTTB/C Networking (xDSL Access, Without HGW).............................................................................................607
12.2.1 Service Requirements and Application Scenario..................................................................................................607
12.2.3 Configuring the Service Channel Between the OLT and the ONU.......................................................................610
12.2.5 Configuring the Internet Access Service (ADSL2+ Access, on the ONU)...........................................................616
Issue 02 (2013-10-08)

ix

Configuration Guide
Contents
12.2.6 Configuring the Internet Access Service (VDSL2 Access, on the ONU).............................................................619
12.2.7 (Optional) Configuring Vectoring.........................................................................................................................622
12.2.9 Configuring SIP Voice Service (on the ONU)......................................................................................................634
12.3 FTTB/FTTC+HGW Networking (Voice Service Provided by ONU).....................................................................639
12.3.3 Configuring Service Channels Between an OLT and an ONU.............................................................................644
12.3.5 Configuring the Internet Access Service (LAN Access, on the ONU).................................................................651
12.3.10 Configuring SIP Voice Service (on the ONU)....................................................................................................670
12.3.11 Configuring the IPTV Service (on the ONU)......................................................................................................673
12.3.12 Configuring the Internet Access Service (on the HGW).....................................................................................676
12.3.13 Configuring the IPTV Service (on the HGW).....................................................................................................678
12.4 FTTB/FTTC+HGW Networking (HGW Providing the VoIP Service)...................................................................684
12.4.3 Configuring Service Channels Between an OLT and an ONU.............................................................................688
12.4.5 Configuring the Internet Access Service (LAN Access, on the ONU).................................................................696
12.4.9 Configuring the Voice Service Channel (on the ONU).........................................................................................711
12.4.10 Configuring the IPTV Service (on the ONU)......................................................................................................713
12.4.11 Configuring the Internet Access Service (on the HGW).....................................................................................716
12.4.12 Configuring the IPTV Service (on the HGW).....................................................................................................718
12.4.13 Configuring the VoIP Service (on the HGW).....................................................................................................720
A Acronyms and Abbreviations................................................................................................727
Issue 02 (2013-10-08)


Configuration Guide
1 Deploying Network Devices
Deploying Network Devices
About This Chapter

Deploy the ONUs at sites according to network planning so that the NMS, OLT, and ONU can
communicate with each other.
1.1 Introduction to the Network Device Deployment
This topic describes how to deploy network devices, including optical network unit (ONU) data
plan, ONU offline deployment (through the NMS or the CLI of the OLT), ONU installation,
and ONU binding. After the deployment, you can remotely configure services for the ONU.
1.2 Example of Deploying Network Devices (GPON Upstream)
This topic describes how to deploy network devices in the scenario with or without the NMS.
1.3 Configuration Example of Network Device Deployment Using GE Upstream Transmission
This topic describes how to configure the optical network unit (ONU) to use a gigabit Ethernet
(GE) port for upstream transmission. After the configuration, the network management system
(NMS) management parameters must be manually configured so that the NMS can manage the
ONU. To reduce device deployment costs, the ONU supports the software commissioning-free
function for GE upstream transmission. Specifically, the device is automatically managed and
configured, and services are automatically provisioned after the ONU is powered on and the
software commissioning-free function takes effect.
Issue 02 (2013-10-08)


Configuration Guide
1.1 Introduction to the Network Device Deployment

This topic describes how to deploy network devices, including optical network unit (ONU) data
plan, ONU offline deployment (through the NMS or the CLI of the OLT), ONU installation,
and ONU binding. After the deployment, you can remotely configure services for the ONU.
Table 1-1 describes the activities involved in network device deployment in the scenario with
the NMS.
Table 1-1 Activities involved in network device deployment in the scenario with the NMS
Activities
Description
ONU data plan
Perform the data plan according to the network planning sheet

provided by the NMS. The resource deployment sheet will be
generated finally.
NOTE
The ONU refers to
MA5616.
ONU offline deployment
Import the resource deployment sheet through the NMS to

implement the predeployment for the ONU.
ONU installation
The hardware installation engineer draws the ONU from the

storehouse and installs it at the destination site. After installing it
and confirming that the hardware is fault-free, the hardware
installation engineer returns the ONU type, service port
information, and ONU SN to the commissioning engineer.
ONU binding
The IP address and the SN of the ONU are bound through the
NMS.
Table 1-2 describes the activities involved in network device deployment in the scenario without
the NMS.
NOTE
In the scenario without the NMS, you can add the ONT through the OLT by using one of the following
methods:
l
Method 1:
1. Install the ONU and power on the device normally.
2. Run the port portid ont-auto-find command in the GPON mode to enable the ONU autodiscovery function.
3. The OLT discovers the ONU automatically.
4. Run the ont confirm command to in the GPON mode confirm the automatically discovered ONU.
Method 2:
1. Run the ont add command in the GPON mode to add the ONU on the OLT offline.
2. Install the ONU and power on the device normally.
In this topic, method 1 is used for the deployment.
Issue 02 (2013-10-08)


Configuration Guide
Table 1-2 Activities involved in network device deployment in the scenario without the NMS
Activities
Description
ONU data plan
Perform the data plan for the OLT and ONU according to the
actual FTTx service plan and the corresponding OLT version.
NOTE
The ONU refers to
MA5616.
ONU installation
The hardware installation engineer draws the ONU from the

storehouse and installs it at the destination site. After installing it
and confirming that the hardware is fault-free, the hardware
installation engineer returns the ONU type, service port
information, and ONU SN to the commissioning engineer.
ONU deployment
Enable the auto-discovery function on the PON port through the

CLI command of the OLT, confirm the automatically discovered
ONU, and add the ONU by using the preconfigured profile.
Configuration of the
services of the ONU
You can remote log in to the ONU according to the management

IP address of the ONU to configure the services for the ONU.
1.2 Example of Deploying Network Devices (GPON

Upstream)
This topic describes how to deploy network devices in the scenario with or without the NMS.
Prerequisites
l
Network devices and lines must be in the normal state.
The control board and the GPON service board of the OLT must be in the normal state.
Context
When the ONU adopts the GPON upstream transmission, the SN is used for authentication.
Scenario with the NMS

Figure 1-1 shows an example network of device deployment in the scenario with the NMS.
Issue 02 (2013-10-08)


Configuration Guide
Figure 1-1 Example network of device deployment in the scenario with the NMS
NMS client_A
NMS
NMS client_B
MGC
Router
OLT
Splitter
Splitter
ONU_A
ONU_B
ONU_C
ONU_D
The procedure for deploying network devices in the scenario with the NMS is as follows:
1.
According to the user's FTTx data plan, the commissioning engineer prepares the network
planning sheet and obtains the resource deployment sheet.
2.
The commissioning engineer imports the resource deployment sheet through the NMS to
implement the predeployment for the ONU.
3.
The hardware installation engineer draws the ONUs and sends them to the destination sites,
and then performs hardware installation, wiring, and power-on operations at the destination
sites.
NOTE
Inserting or removing boards is prohibited during startup.
4.
The hardware installation engineer checks the running status of the ONU that is installed
and powered on.
There are two LEDs, namely Link and Auth, on the ONU.
Issue 02 (2013-10-08)


Configuration Guide
l If the Link LED is on, it indicates that the upstream optical path is through.
l If the Auth LED is blinking, it indicates that the ONU is registering.
l If the Auth LED is always on, it indicates that the ONU registers successfully.
5.
After confirming that the ONU works in the normal state (the Link LED is on and the Auth
LED blinks), the hardware installation engineer records the ONU SN and reports the SN
to the commissioning engineer.
6.
The commissioning engineer maps the ONU SN, the management IP address of the ONU,
and the physical position of the ONU, and binds the IP address and the SN of the ONU
through the NMS.
7.
After being powered on, the ONU registers with the OLT automatically. Then, the OLT
sends the management channel parameters of the ONU (management VLAN, IP address,
and SNMP parameters) to the ONU and also sends the trap message to the NMS for
informing the NMS that an ONU goes online.
8.
The commissioning engineer receives the trap indicating that the ONU goes online reported
by the OLT on the NMS.
After the trap indicating that the ONU goes online is received on the NMS, the ONU
management channel is enabled successfully. Then, you can remotely configure services
for the ONU through the NMS.
Scenario Without the NMS

Figure 1-2 shows an example network of device deployment in the scenario without the NMS.
Issue 02 (2013-10-08)


Configuration Guide
Figure 1-2 Example network of device deployment in the scenario without the NMS
PC_A
MGC
PC_B
Router
OLT
Splitter
Splitter
ONU_A
ONU_B
ONU_C
ONU_D
The procedure for deploying network devices in the scenario without the NMS is as follows:
1.
According to the user's FTTx service plan and the corresponding OLT version, the
commissioning engineer performs the data plan for the OLT and ONU.
2.
The hardware installation engineer draws the ONUs and sends them to the destination sites,
and then performs hardware installation, wiring, and power-on operations at the destination
sites.
NOTE
Inserting or removing boards is prohibited during startup.
3.
The hardware installation engineer checks the running status of the ONU that is installed
and powered on.
There are two LEDs, namely Link and Auth, on the ONU.
l If the Link LED is on, it indicates that the upstream optical path is through.
l If the Auth LED is blinking, it indicates that the ONU is registering.
l If the Auth LED is always on, it indicates that the ONU registers successfully.
Issue 02 (2013-10-08)


Configuration Guide
4.
After confirming that the ONU works in the normal state (the Link LED is on and the Auth
LED blinks), the hardware installation engineer records the ONU SN and reports the SN
to the commissioning engineer.
5.
According to the data plan of the OLT and ONU, the commissioning engineer configures
data on the OLT.
6.
The commissioning engineer enables the auto-discovery function of the OLT for the ONU.
7.
The commissioning engineer adds the ONU to the OLT according to the data plan of the
OLT and ONU and the SN reported by the hardware installation engineer.
8.
The commissioning engineer configures the management IP address of the ONU through
the OLT.
9.
On the OLT, the commissioning engineer can remote log in to the ONU according to the
management IP address of the ONU to configure the services for the ONU.
1.3 Configuration Example of Network Device Deployment

Using GE Upstream Transmission
This topic describes how to configure the optical network unit (ONU) to use a gigabit Ethernet
(GE) port for upstream transmission. After the configuration, the network management system
(NMS) management parameters must be manually configured so that the NMS can manage the
ONU. To reduce device deployment costs, the ONU supports the software commissioning-free
function for GE upstream transmission. Specifically, the device is automatically managed and
configured, and services are automatically provisioned after the ONU is powered on and the
software commissioning-free function takes effect.
Prerequisites
l
A Dynamic Host Configuration Protocol (DHCP) server and a File Transfer Protocol (FTP)
or Trivial File Transfer Protocol (TFTP) server have been configured.
The DHCP relay function has been configured on the router.

If the ONU is connected to a Layer 2 upstream device, which can transparently transmit
DHCP packets, the DHCP relay function is not required.
When the ONU transmits untagged DHCP packets to the upper-layer device, the port
default VLAN ID (PVID) must be configured on the upper-layer device so that the device
can transparently transmit the DHCP packets.
The device database is empty. Otherwise, the software commissioning-free function cannot
take effect for GE upstream transmission.
Context
CAUTION
The software commissioning-free function for GE upstream transmission takes effect on a single
device or multiple devices cascaded on a link-type network. You are advised to install and power
on cascaded devices from the upper layer to the lower layer, preventing service interruptions on
a lower-layer device caused by an upper-layer device.
Issue 02 (2013-10-08)


Configuration Guide
Figure 1-3 shows the example network in which the ONU uses GE upstream transmission. The
network supports the FTP or TFTP server for transferring files. You can configure either the
FTP or TFTP server as required.
Figure 1-3 Example network in which the ONU uses GE upstream transmission
NMS
DHCP Server
FTP/TFTP Server
Router
MA5616
Process for Configuring GE Upstream Transmission

1.
A software commissioning engineer creates a configuration file based on the data plan and
uploads the file to the FTP or TFTP server.
NOTE
The name of a configuration file must be either IP_cfgfile.txt or MAC_cfgfile.txt. IP in

IP_cfgfile.txt is the planned IP address of a device, and MAC in MAC_cfgfile.txt is the actual Media
Access Control (MAC) address of the device. For example, if the planned IP address of a device is
192.168.10.10, the name of the configuration file for the device is 192.168.10.10_cfgfile.txt; if the
MAC address of a device is 00e0fc11abee, the name of the configuration file for the device is 00e0-fc-11-ab-ee_cfgFile.txt.
When the configuration file is named IP_cfgfile.txt, the ONU IP address cannot conflict with the IP
addresses of other devices. To ensure that the ONU IP address is unique, bind the ONU IP address
to its MAC address.
The configuration file must be created based on service deployment and script issuing requirements.
2.
Issue 02 (2013-10-08)
The software commissioning engineer creates a policy file based on the device type and
version information and uploads the file to the FTP or TFTP server.


Configuration Guide
NOTE
The name of a policy file must be xxx.ini. A policy file contains the name (either IP_cfgfile.txt or
MAC_cfgfile.txt) of and path for a configuration file.
One policy file is used for all the devices at one site. For example, if the name of the configuration
file at a site is IP address-based, the contents of the policy file at the site is as follows:
[MA5616]
//Indicates the device
type.
TargetVersion=MA5616 V800R311C01
//Indicates the device
version.
[H831CCUE]
//Indicates the control
board type.
PacketFile="Dir\H831CCUB_packetfile.bin"
//Indicates the package
file to be loaded to the control board.
CfgFile="Dir\[IP]_cfgFile"
//Indicates the
configuration file to be loaded to the control board. The file is named
IP_cfgfile.txt.
3.
A hardware installation engineer obtains optical network units (ONUs), transports the
ONUs from the warehouse to each site, installs hardware, seats wires, and powers on the
ONUs.
NOTE
No board can be inserted or removed during device startup.
4.
The hardware installation engineer records site information and the MAC addresses of the
ONUs and reports them to the software commissioning engineer.
5.
The software commissioning engineer establishes the mapping among the MAC addresses,
management IP addresses, and physical locations of the ONUs, uses the NMS to bind the
IP and MAC addresses of the ONUs, and configures data on the DHCP server.
6.
The hardware installation engineer powers on the ONUs after the ONU installation and
observes the running status of the ONUs.
If the Link indicator turns on, the upstream optical path is available.
7.
After power-on, the ONU automatically sends DHCP requests to the DHCP server.
8.
The DHCP server configures the IP address assigned by the NMS on the ONU, writes the
FTP or TFTP information in an option packet, and sends the option packet to the ONU.
The information includes the IP address, user name, and password of the FTP or TFTP
server, and the name of the policy file. Table 1-3 lists the information included in DHCP
Option fields.
Table 1-3 Information included in DHCP Option fields
Issue 02 (2013-10-08)
DHCP Option Field
Information
DHCP Option 3
Gateway list
DHCP Option 6
DNS list
DHCP Option 15
Domain name
DHCP Option 66
TFTP server name
DHCP Option 67
Policy description file name
DHCP Option 141
FTP user name


Configuration Guide
9.
DHCP Option Field
Information
DHCP Option 142
FTP user password
DHCP Option 143
FTP server address
DHCP Option 150
TFTP server address
After receiving the option packet from the DHCP server, the ONU configures the IP address
and gateway, and sends requests to the FTP or TFTP server.
10. The FTP or TFTP server issues the configuration file to the ONU.
11. The ONU downloads the configuration file from the FTP or TFTP server and automatically
configures related data. After the configuration, the ONU restarts for the configuration to
take effect.
12. The ONU reports traps to the NMS, indicating that ONUs connected to the NMS go online.
13. The software commissioning engineer uses the NMS to receive the traps from the ONU.
If the traps from the ONU are received, the management channel is available for the NMS
to remotely manage the ONU.
Issue 02 (2013-10-08)

10

Configuration Guide
2 Checking Before the Configuration
Checking Before the Configuration
About This Chapter

Before the service configuration, you need to check the software version and board status of the
MA5616 to ensure that the service runs normally after the configuration.
2.1 Checking the Software Version
This topic describes how to check whether the current software version meets the deployment
requirement.
2.2 Checking the Board Status
This topic describes how to check whether the inserted board is the same as the board specified
in the data plan, and whether the boards are in the normal state.
Issue 02 (2013-10-08)

11

Configuration Guide
2.1 Checking the Software Version

This topic describes how to check whether the current software version meets the deployment
requirement.
Prerequisites
You must be logged in to the MA5616. For details about how to log in to the device, see 3.1
Configuring the Maintenance Terminal.
Procedure
l
The procedure of checking the software version through the MA5616 is as follows:
1.
In the user mode, run the display language command to check whether the multilanguage information supported by the system and the system version meet the
deployment requirement.
2.
In the user mode, run the display version command to check whether the versions of
the host software and patch that is running in the system meet the deployment
requirement.
The procedure of checking the software version through the iManager U2000 is as follows:
1.
In the Workbench window, double-click

displayed. Click
. The Main Topology window is
2.
In the Search dialog box, select NE from the Search Type drop-down list and enter
the description of the MA5616 to be queried. Then, click Search.
3.
In the search result, select the desired MA5616. Click Locate and select Locate to
NE Panel from the list. In the Device Detailed Info tab page, verify that the device
type and activated patch meet the deployment requirement.
----End
Result
l
The versions of the host software and patch meet the deployment requirement.
If the versions do not meet the deployment requirement, contact Huawei technical support
center to upgrade the host software if necessary. For details about the upgrade, see the
MA5616 Upgrade guide.
2.2 Checking the Board Status

This topic describes how to check whether the inserted board is the same as the board specified
in the data plan, and whether the boards are in the normal state.
Procedure
l
Issue 02 (2013-10-08)
The procedure of checking the board status through the MA5616 is as follows:
12

Configuration Guide
1.
Run the display board command to check whether the board information (including
the board types and the slots housing the boards) meets the data plan and whether the
boards are in the normal state.
If all the required boards are inserted correctly and all the boards are in the normal
state, the operation ends.
If a required board is not inserted in the device, insert the board and run the board
confirm command to confirm the board in the auto-find state. Then, run the display
board command to query the status of all the boards.
The procedure of checking the board status through the iManager U2000 is as follows:
1.
In the Workbench window, double-click

displayed. Click
. The Main Topology window is
2.
In the Search dialog box, select Board from the Search Type drop-down list and
enter the description of the board to be queried. Then, click Search.
3.
In the search result, select the desired board of the MA5616. Click Locate to
Board. Then, verity that the board type and slot meet the requirements of the data
planning and verify the board status.
----End
Result
l
The status of all the boards is "Normal" in the result of the query on the MA5616.
All the boards on the MA5616 are in the normal state, represented by
the query through the iManager U2000.
Issue 02 (2013-10-08)

, in the result of
13

Configuration Guide
3 Basic Configuration
Basic Configuration
About This Chapter

This topic describes how to perform the basic configuration, including common configuration,
public configuration, and service preconfiguration. These types of configurations do not have
definite logic relations between each other. Therefore, you can perform the configuration based
on actual requirements.
3.1 Configuring the Maintenance Terminal
This topic describes three modes of managing the MA5616 from the maintenance terminal.
3.2 Configuring the U2000
The MA5616 can be interconnected with Huawei iManager U2000 (hereinafter referred to as
U2000). Hence, the administrator can maintain and manage the device through the U2000. The
MA5616 can be interconnected with the U2000 in inband or outband networking mode. The
following part describes how to configure the inband networking and outband networking based
on SNMP V1, SNMP V2c, and SNMP V3 respectively.
3.3 Configuring the Attributes of the Upstream Port
The MA5616 can be interconnected with the upstream device through upstream GPON/GE port.
This topic describes how to configure the attributes of upstream GPON/GE port so that the device
communicates successfully with the upstream device.
3.4 Configuring the ANCP
Access Node Control Protocol (ANCP) is used to implement the functions such as topology
discovery, line configuration, and Layer 2 Control (L2C) OAM on the user ports. The
MA5616 establishes an ANCP session according to the communication IP address of the General
Switch Management Protocol (GSMP) that is used by the network access server (NAS).
3.5 Configuring a VLAN
A virtual local area network (VLAN) is used to separate broadcast domains. VLANs have
enhanced security and support expansion and flexible networking. Configuring VLAN is a
prerequisite for configuring a service. Hence, before configuring a service, make sure that the
VLAN configuration based on planning is complete.
3.6 Configuring Basic IPv6 Information
Issue 02 (2013-10-08)

14

Configuration Guide
This topic describes the IPv6 features supported by the MA5616. The basic IPv6 configuration
includes configuration of the IPv6 address, IPv6 neighbor, and path maximum transmission unit
(PMTU).
3.7 Configuring a Route
This topic describes how to configure Internet Protocol version 4 (IPv4) or Internet Protocol
version 6 (IPv6) routes on the MA5616.
3.8 Configuring the System Clock
This topic describes how to configure the system clock to restrict the clock frequency and phase
of each node on a network within the preset tolerance scope. This prevents the deterioration of
the TDM service quality caused by inaccurate signal timing at both the transmit and receive ends
in the digital transmission system.
3.9 Configuring the NTP Time
Configuring the NTP protocol to keep the time of all devices in the network synchronized, so
that the Context implement various service applications based on universal time, such as the
network management system and the network accounting system.
3.10 Configuring the User Security
Configuring the security mechanism can protect operation users and access users against user
account theft and roaming or from the attacks from malicious users.
3.11 Configuring System Security
This topic describes how to configure the network security and protection measures of the system
to protect the system from malicious attacks.
3.12 Configuring AAA
This topic describes how to configure the AAA on the MA5616, including configuring the
MA5616 as the local and remote AAA servers.
3.13 Configuring the ACL for Packet Filtering
This topic describes the type, rule, and configuration of the ACL on the MA5616.
3.14 Configuring QoS
This topic describes how to configure quality of service (QoS) on the MA5616 to provide endto-end quality assurance for user services.
3.15 Configuring Environment Monitoring
This topic provides concepts associated with environment monitoring and describes how to
configure environment monitoring on the MA5616.
Issue 02 (2013-10-08)

15

Configuration Guide
3.1 Configuring the Maintenance Terminal

This topic describes three modes of managing the MA5616 from the maintenance terminal.
3.1.1 Configuring Management Through a Local Serial Port

This topic describes how to connect the maintenance terminal to the MA5616 through a local
serial port, log in to the MA5616, and then manage the MA5616 from the maintenance terminal.
Networking
Figure 3-1 shows an example network for configuring management through a local serial port.
Figure 3-1 Example network for configuring management through a local serial port
RS-232 serial
port cable
PC
ONU
Configuration Flowchart
Figure 3-2 shows the flowchart for configuring management through a local serial port.
Issue 02 (2013-10-08)

16

Configuration Guide
Figure 3-2 Flowchart for configuring management through a local serial port
Start
Connect the serial port cable
Start the HyperTerminal

Set parameters of the
HyperTerminal
Set the terminal emulation
type
Set the line delay and the
character delay
Log in to the system
End
NOTE
This topic uses Windows XP operating system as an example.
Procedure
Step 1 Connect the serial port cable.
Use a standard RS-232 serial port cable to connect the serial port of the PC to the CONSOLE
port (maintenance serial port) on the control board of the MA5616, as shown in Figure 3-1.
Step 2 Start the HyperTerminal.
1.
Set up a connection.
Choose Start > Programs > Accessories > Communications > HyperTerminal on the
PC. The Connection Description dialog box is displayed. Enter the connection name, as
shown in Figure 3-3, and click OK.
Issue 02 (2013-10-08)

17

Configuration Guide
Figure 3-3 Setting up a connection
2.
Set the serial port.

On the PC that is connected to the MA5616, select the number of the PC terminal serial
port In this example, "COM2" is selected, as shown in Figure 3-4. Click OK.
Figure 3-4 Selecting the serial port ID
Step 3 Set the communication parameters of the HyperTerminal.

Set the parameters in the COM2 Properties dialog box, as shown in Figure 3-5. The parameters
are as follows:
Issue 02 (2013-10-08)

18

Configuration Guide
l Baud rate: 9600 bit/s

l Data bit: 8
l Parity: None
l Stop bit: 1
l Flow control: None
NOTE
l The baud rate of the HyperTerminal must be the same as that of the serial port on the MA5616. By
default, the baud rate of the serial port on the MA5616 is 9600 bit/s.
l There may be illegible characters in the displayed input information after you log in to the system. This
is because the baud rates between the HyperTerminal and the MA5616 are not the same. In this case,
set a different baud rate 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.
Figure 3-5 Setting the parameters of the HyperTerminal
Click OK, and the HyperTerminal interface is displayed, as shown in Figure 3-6.
Issue 02 (2013-10-08)

19

Configuration Guide
Figure 3-6 HyperTerminal interface
Step 4 Set the terminal emulation type.

Choose File > Properties on the HyperTerminal interface. In the dialog box that is displayed,
click the Settings tab, and set the terminal emulation type to VT100 or Auto detect. Use default
values for other parameters. Then, click OK, as shown in Figure 3-7.
Issue 02 (2013-10-08)

20

Configuration Guide
Figure 3-7 Setting the terminal emulation type
Step 5 Set the line delay and the character delay.

Click ASCII Setup. In the dialog box that is displayed, set Line delay to 200 ms and Character
delay to 200 ms, and use default values for other parameters. Click OK, as shown in Figure
3-8.
NOTE
l By default, Line delay is 0, and Character delay is 0.

l 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.
Issue 02 (2013-10-08)

21

Configuration Guide
Figure 3-8 Setting the line delay and the character delay
----End
Result
On the HyperTerminal interface, press Enter, and the system prompts you to enter the user
name. Enter the user name and the password for user registration (by default, the super user
name is root and the password is mduadmin), and wait until the CLI prompt character is
displayed. For instructions on CLI, see CLI Operation Characteristics.
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.
and then click

on the operation interface. If your login still fails,
If your login fails, click
return to step 1 to check the parameter settings and the physical connections, and then try again.
3.1.2 Configuring Outband Management

This topic describes how to connect the MA5616 to the maintenance terminal through an outband
management port in the telnet mode or secure shell (SSH) mode, log in to the MA5616, and then
manage the MA5616. The SSH provides authentication, encryption, and authorization to ensure
the network communication security. When a user logs in to the MA5616 remotely over an
insecure network, SSH provides security guarantee and powerful authentication to protect the
MA5616 against attacks such as IP address spoofing and interception of plain text password.
Prerequisites
l
Issue 02 (2013-10-08)
You must log in to the system through a local serial port. For the configuration process,
see 3.1.1 Configuring Management Through a Local Serial Port.
22

Configuration Guide
The IP address of the maintenance terminal must be properly configured.

NOTE
In the following operations, the configurations of the MA5616 must be performed through a local serial
port.
Networking - LAN
Figure 3-9 shows an example network for configuring outband management over a LAN.
Figure 3-9 Example network for configuring outband management over a LAN
ONU
LAN
PC
PC
PC
In this example network, the IP address of the maintenance Ethernet port of the MA5616 and
the IP address of the maintenance terminal are in the same network segment. You can also
manage the MA5616 through an outband channel by directly connecting the maintenance
Ethernet port of the maintenance terminal to the maintenance Ethernet port on the control board
of the MA5616.
Data Plan - LAN

Table 3-1 and Table 3-2 provide the data plan for configuring outband management over a
LAN .
Table 3-1 Data plan for configuring outband management over a LAN in remote login mode
Issue 02 (2013-10-08)
Item
Data
Maintenance Ethernet port of the

MA5616
IP address: 10.10.20.2/24
Ethernet port of the maintenance

terminal
IP address: 10.10.20.3/24

23

Configuration Guide
Table 3-2 Data plan for configuring outband management over a LAN in the SSH mode
Item
Data

MA5616
l IP address: 10.10.20.2/24
l User authentication mode: RSA public key
authentication
l RSA key name: key
l User name/Password: huawei/test01
New user
l Authority: Operator
l Permitted reenter number: 4
terminal
IP address: 10.10.20.3/24
Networking - WAN
Figure 3-10 shows an example network for configuring outband management over a WAN.
Figure 3-10 Example network for configuring outband management over a WAN
PC
PC
Router
LAN
PC
ONU
In this example network, the MA5616 is connected to the WAN through the maintenance
Ethernet port. You can manage the MA5616 remotely from the maintenance terminal.
Data Plan - WAN

Table 3-3 and Table 3-4 provide the data plan for configuring outband management over a
WAN in remote login mode.
Issue 02 (2013-10-08)

24

Configuration Guide
Table 3-3 Data plan for configuring outband management over a WAN in remote login mode
Item
Data

MA5616
IP address: 10.10.20.2/24

terminal
IP address: 10.10.21.3/24
Port of the router connected to the

MA5616
IP address: 10.10.20.254/24
Table 3-4 Data plan for configuring outband management over a WAN in the SSH mode
Item
Data

MA5616
l IP address: 10.10.20.2/24
l User authentication mode: RSA public key
authentication
l RSA key name: key
New user
terminal
IP address: 10.10.21.3/24
Router port connecting to theMA5616
IP address: 10.10.20.254/24
Figure 3-11 and Figure 3-12 show the flowchart for outband management in remote login mode.
Issue 02 (2013-10-08)

25

Configuration Guide
Figure 3-11 Flowchart for outband management in remote login mode

Start
Set up the configuration

environment
Configure the IP address

and subnet mask of the
maintenance port
Is it a WAN environment?
No
Yes
Add a route
Start Telnet on the

maintenance terminal
End
Issue 02 (2013-10-08)

26

Configuration Guide
Figure 3-12 Flowchart for outband management in the SSH mode
Start
Set up the configuration environment

Configure the IP address of the
maintenance Ethernet port
WAN environment or
not?
No
Yes
Add a outband route for the NMS
Create an SSH user
Create the key pair for the SSH server

Password
Set SSH user
authentication mode
rsa, all, passwordpublickey
Generate the RSA public key
Generate the public key for SSH user

Authorize the public key to the SSH
user

End
Issue 02 (2013-10-08)

27

Configuration Guide
NOTE
The blue-shaded configuration procedures are the difference in the SSH mode and the telent mode.
Procedure
Step 1 Set up the configuration environment.
Figure 3-9 or Figure 3-10 shows how to set up the configuration environment according to the
actual requirements and conditions.
Step 2 In the meth mode, run the ip address command to configure the IP address and subnet mask of
the maintenance Ethernet port of the MA5616.
NOTE
The default IP address of the maintenance Ethernet port is 10.11.104.2, and the subnet mask is
255.255.255.0. You can configure the IP address of the maintenance Ethernet port based on the actual
network planning.
huawei(config)#interface meth 0
huawei(config-if-meth0)#ip address 10.10.20.2 24
Step 3 Add a route.

l If the configuration environment is set up as shown in Figure 3-9, you need not add a route.
l If the remote WAN management environment is set up as shown in Figure 3-10, run the ip
route-static command to add a route to the next hop.
huawei(config-if-meth0)#quit
huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254
Step 4 Perform the following operations based on the login mode.

l If you login in the telnet mode, perform the following operations:
1.
Run the telnet application.

Choose Start > Run on the maintenance terminal. In the Open address bar, enter telnet
10.10.20.2 (10.10.20.2 is the IP address of the maintenance Ethernet port of the
MA5616), as shown in Figure 3-13 (considering the Windows OS as an example). Click
OK, and the telnet interface is displayed.
Figure 3-13 Starting Telnet
2.
Issue 02 (2013-10-08)
Log in to the MA5616.

28

Configuration Guide
On the telnet interface, enter the user name and the password. By default, the super user
name is root and the password is mduadmin. When the login is successful, the system
displays the following information:
>>User
name:root
>>User
password:
Huawei Integrated Access Software

(MA5616).
Copyright(C) Huawei Technologies Co., Ltd. 2002-2012. All rights reserved.
l If you login in the SSH mode, perform the following operations:

1.
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
maintenance terminal.
Confirm Password(length<6,15>):test01 //The password is not displayed on
the maintenance terminal.
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
2.
Create the local RSA key pair.

Run the rsa local-key-pair create command to create the local RSA key pair.
CAUTION
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...
..++++++++++++
....................++++++++++++
...............................++++++++
...........++++++++
3.
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.
Issue 02 (2013-10-08)

29

Configuration Guide
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.
4.
Generate the RSA public key.

a.
Run the key generator.

Run the client software key generator Puttygen.exe. Figure 3-14 shows the
interface of the key generator.
Figure 3-14 Interface of the key generator
b.
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 3-15.
Issue 02 (2013-10-08)

30

Configuration Guide
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 3-16.
Figure 3-16 Save the public key and the private key
Issue 02 (2013-10-08)

31

Configuration Guide
c.

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 3-17.
Figure 3-17 Interface of converting the client public key to the RSA public key
5.
Generate the public key for the SSH user.

Create RSA public key. Copy the RSA public key to the server in the config-rsa-keycode 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
198BAC15
huawei(config-rsa-key-code)#D32834F7 365CFD17 E7FE4041 3266E416 710D13ED
22BD4D59
huawei(config-rsa-key-code)#DF0C3E46 A995CC61 DC4CB179 F6888B8C 3F8A3085
51EDB5C7
Issue 02 (2013-10-08)

32

Configuration Guide
huawei(config-rsa-key-code)#5DEBDBE1 3AB4A256 0D0B9AA8 9A419D85 35C0E562

AE0BBFAB
huawei(config-rsa-key-code)#515299F9 D2803E84 3AE36C20 949367EA 0697EB20
2594A774
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
6.
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
7.
Log in to the system.

a.
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 3-18. Click
Browse to display the window for selecting the file. In the window, select the file
for the private key, and click OK.
Figure 3-18 Interface of the SSH client software
b.

Choose Session from the navigation tree, and then input the IP address of the
MA5616 in the Host Name (or IP address) field, as shown in Figure 3-19. Then,
click Open to log in to the system.
Issue 02 (2013-10-08)

33

Configuration Guide
NOTE
The port in the Figure 3-19 generally uses the default number 22, you can also use the
display sysman service state command to query and then to configure.
Figure 3-19 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 3-20. Input the user name to log
in to the system (here, the user name is huawei).
Issue 02 (2013-10-08)

34

Configuration Guide
----End
Result
After logging in to the MA5616, you can manage the MA5616. For instructions on CLI, see CLI
Operation Characteristics.
3.1.3 Configuring Inband Management (GPON Upstream)

This topic describes how to log in to the MA5616 through an OLT from the maintenance terminal
to manage the MA5616.
Prerequisites
l
The physical connection between the MA5616 and the OLT must be normal.
Issue 02 (2013-10-08)

35

Configuration Guide
Networking - LAN
Figure 3-21 Example network for configuring inband management over a LAN in the GPON
upstream mode
LAN
OLT
PC
PC
ONU
Networking - WAN
Figure 3-22 Example network for configuring inband management over a WAN in the GPON
upstream mode
Router
LAN
OLT
PC
PC
ONU
Figure 3-23 shows the flowchart for managing the MA5616 through an inband channel in the
GPON upstream mode.
NOTE
In the GPON upstream mode, the MA5616 and the OLT are interconnected to implement inband
management. All required configurations are performed on the OLT. This document provides only the
flowchart for configuring the OLT. For the detailed configuration process, see the configuration guide
corresponding to the OLT.
Issue 02 (2013-10-08)

36

Configuration Guide
Figure 3-23 Flowchart for configuring inband management in the GPON upstream mode
Start
Configure the L3 interface of the OLT
Configure corresponding profiles
Adding an ONU
Configure the IP address of the ONU

and the corresponding information
Is it a WAN environment?
No
Yes
Add a route
Use Telnet to log in to the ONU through

the OLT or maintenance terminal
End
Result
After logging in to the MA5616 through the OLT or maintenance terminal, you can configure
the MA5616. For instructions on CLI, see CLI Operation Characteristics.
3.1.4 Configuring Inband Management (GE Upstream)

This topic describes how to use the remote login or secure shell (SSH) mode log in to the
MA5616 through an upstream port (inband management port) of the MA5616 for inband
management. The SSH provides authentication, encryption, and authorization to ensure the
network communication security. When a user logs in to the MA5616 remotely over an insecure
network, SSH provides security guarantee and powerful authentication to protect the MA5616
against attacks such as IP address spoofing and interception of plain text password.
Issue 02 (2013-10-08)

37

Configuration Guide
Prerequisites
l
You must be logged in to the system through a local serial port. For the configuration
process, see 3.1.1 Configuring Management Through a Local Serial Port.

NOTE
In the following operations, the configurations of the MA5616 must be performed through a local serial
port.
Networking - LAN
Figure 3-24 shows an example network for configuring inband management over a LAN.
Figure 3-24 Example network for configuring inband management over a LAN
LAN
PC
PC
LAN Switch
PC
DSLAM
Data Plan - LAN

Table 3-5 and Table 3-6 provide the data plan for configuring inband management over a LAN.
Table 3-5 Data plan for configuring inband management over a LAN in the remote login mode
Item
Data
Upstream port of the

MA5616
l VLAN ID: 30
l Port ID: 0/0/1
l IP address: 10.10.20.2/24
Ethernet port of the

Issue 02 (2013-10-08)
IP address: 10.10.20.3/24

38

Configuration Guide
Table 3-6 Data plan for configuring inband management over a LAN in the SSH mode
Item
Data

MA5616
l VLAN ID: 30
l Port ID: 0/0/1
l IP address: 10.10.20.2/24
l User authentication mode: RSA public key authentication
l RSA key name: key
New user
IP address: 10.10.20.3/24
Networking - WAN
Figure 3-25 shows an example network for configuring inband management over a WAN.
Figure 3-25 Example network for configuring inband management over a WAN
PC
LAN
Router
PC
PC
LAN Switch
DSLAM
Data Plan - WAN

Table 3-7 and Table 3-8 provide the data plan for configuring inband management over a WAN.
Issue 02 (2013-10-08)

39

Configuration Guide
Table 3-7 Data plan for configuring inband management over a WAN in the remote login mode
Item
Data

MA5616
l VLAN ID: 30
l Port ID: 0/0/1
l IP address: 10.10.20.2/24

IP address: 10.10.21.3/24
Port of the LAN

switch connected to
the router
IP address: 10.10.20.3/24
Table 3-8 Data plan for configuring inband management over a WAN in the SSH mode
Item
Data

MA5616
l VLAN ID: 30
l Port ID: 0/0/1
l IP address: 10.10.20.2/24
l User authentication mode: RSA public key authentication
l RSA key name: key
New user
IP address: 10.10.21.3/24
Router port
connecting to the LAN
Switch
IP address: 10.10.20.3/24
Figure 3-26 and Figure 3-27 show the flowchart for configuring inband management.
Issue 02 (2013-10-08)

40

Configuration Guide
Figure 3-26 Flowchart for configuring inband management in the remote login mode
Start
Set up the configuration

environment
Configure the IP address
of the VLAN L3 interface
Is it a WAN
environment?
No
Yes
Add a route
Start Telnet on the

End
Issue 02 (2013-10-08)

41

Configuration Guide
Figure 3-27 Flowchart for configuring inband management in the SSH mode
Start

Configure the IP address of the VLAN
L3 interface
WAN environment or
not?
No
Yes
Add a outband route for the NMS
Create an SSH user
Create the key pair for the SSH server

Password
Set SSH user
authentication mode
rsa, all, passwordpublickey
Generate the RSA public key
Generate the public key for SSH user

Authorize the public key to the SSH
user

End
Issue 02 (2013-10-08)

42

Configuration Guide
NOTE
The blue-shaded configuration procedures are the difference in the SSH mode and the telent mode.
Procedure
Step 1 Set up the configuration environment.
Figure 3-24 or Figure 3-25 shows how to set up the configuration environment according to
the actual requirements and conditions.
Step 2 Configure the IP address of the VLAN L3 interface.
1.
Run the vlan command to create a VLAN.

huawei(config)#vlan 30 smart
2.
Run the port vlan command to add an upstream port to the VLAN.
huawei(config)#port vlan 30 0/0 1
3.
In the VLANIF mode, run the ip address command to configure the IP address and subnet
mask of the VLAN L3 interface.
huawei(config)#interface vlanif 30
huawei(config-if-vlanif30)#ip address 10.10.20.2 255.255.255.0
Step 3 Add a route.

l If the configuration environment is set up as shown in Figure 3-24, you need not add a route.
l If the remote WAN management environment is set up as shown in Figure 3-25, run the ip
route-static command to add a route to the next hop.
huawei(config-if-vlanif30)#quit
Step 4 Save the data.

Run the save command to save the data.
huawei(config)#save
Step 5 Perform the following operations based on the login mode.

l If you login in the telnet mode, perform the following operations:
1.
Start Telnet.
Choose Start > Run on the maintenance terminal. In the Open address bar, enter telnet
10.10.20.2 (10.10.20.2 is the IP address of the VLAN L3 interface of the MA5616), as
shown in Figure 3-28 (considering the Windows OS as an example). Click OK, and
the telnet interface is displayed.
Figure 3-28 Starting Telnet
Issue 02 (2013-10-08)

43

Configuration Guide
2.
Log in to the MA5616.

On the telnet interface, enter the user name and the password. By default, the super user
name is root and the password is mduadmin. When the login is successful, the system
displays the following information:
>>User
name:root
>>User
password:
Huawei Integrated Access Software

(MA5616).
Copyright(C) Huawei Technologies Co., Ltd. 2002-2012. All rights reserved.
l If you login in the SSH mode, perform the following operations:

1.
Create a user.
Run the terminal user name command to create a user.
User Name(length<6,15>):huawei
User Password(length<6,15>):test01 //The password is not displayed on the
maintenance terminal.
Confirm Password(length<6,15>):test01 //The password is not displayed on
the maintenance terminal.
User's Level:
1. Common User 2. Operator:2
2.
Create the local RSA key pair.

Run the rsa local-key-pair create command to create the local RSA key pair.
CAUTION
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...
..++++++++++++
....................++++++++++++
...............................++++++++
...........++++++++
3.
Set the SSH user authentication mode.

Run the ssh user huawei authentication-type rsa command to choose the
authentication mode of the SSH user.
Issue 02 (2013-10-08)

44

Configuration Guide
There are four authentication modes for SSH users, as shown in the following. In this
topic, authentication mode rsa is considered as an example.
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.
4.

a.
Run the key generator.

Run the client software key generator Puttygen.exe. Figure 3-29 shows the
interface of the key generator.
b.
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 3-30.
Issue 02 (2013-10-08)

45

Configuration Guide
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 3-31.
Figure 3-31 Save the public key and the private key
Issue 02 (2013-10-08)

46

Configuration Guide
c.

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 3-32.
Figure 3-32 Interface of converting the client public key to the RSA public key
5.
Generate the public key for the SSH user.

Create RSA public key. Copy the RSA public key to the server in the config-rsa-keycode 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
198BAC15
huawei(config-rsa-key-code)#D32834F7 365CFD17 E7FE4041 3266E416 710D13ED
22BD4D59
huawei(config-rsa-key-code)#DF0C3E46 A995CC61 DC4CB179 F6888B8C 3F8A3085
51EDB5C7
Issue 02 (2013-10-08)

47

Configuration Guide
huawei(config-rsa-key-code)#5DEBDBE1 3AB4A256 0D0B9AA8 9A419D85 35C0E562

AE0BBFAB
huawei(config-rsa-key-code)#515299F9 D2803E84 3AE36C20 949367EA 0697EB20
2594A774
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
6.
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
7.

a.
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 3-33. Click
Browse to display the window for selecting the file. In the window, select the file
for the private key, and click OK.
Figure 3-33 Interface of the SSH client software
b.

Choose Session from the navigation tree, and then input the IP address of the
MA5616 in the Host Name (or IP address) field, as shown in Figure 3-34. Then,
click Open to log in to the system.
Issue 02 (2013-10-08)

48

Configuration Guide
NOTE
The port in the Figure 3-34 generally uses the default number 22, you can also use the
display sysman service state command to query and then to configure.
The user authentication mode is set to the RSA authentication mode, and the system
therefore displays the prompt, as shown in Figure 3-35. Input the user name to log
in to the system (here, the user name is huawei).
Issue 02 (2013-10-08)

49

Configuration Guide
----End
Result
After logging in to the MA5616, you can manage the MA5616. For instructions on CLI, see CLI
Operation Characteristics.
3.2 Configuring the U2000

The MA5616 can be interconnected with Huawei iManager U2000 (hereinafter referred to as
U2000). Hence, the administrator can maintain and manage the device through the U2000. The
MA5616 can be interconnected with the U2000 in inband or outband networking mode. The
following part describes how to configure the inband networking and outband networking based
on SNMP V1, SNMP V2c, and SNMP V3 respectively.
3.2.1 Configuring the U2000 (Based on SNMPv1)

When SNMPv1 is used, the MA5616 can be interconnected with the U2000 in inband or outband
networking mode.
Prerequisites
l
Issue 02 (2013-10-08)
If the device is interconnected with the NMS in outband networking mode, the
communication port (maintenance network port) must be configured. For detailed
procedure, see 3.1.2 Configuring Outband Management. The

50

Configuration Guide
If the device is interconnected with the NMS through the GPON upstream port in inband
networking mode, the communication port (GPON upstream port) must be configured. For
detailed procedure, see 3.1.3 Configuring Inband Management (GPON Upstream).
If the device is interconnected with the NMS through the GE upstream port in inband
networking mode, the communication port (GE upstream port) must be configured. For
detailed procedure, see 3.1.4 Configuring Inband Management (GE Upstream).
Networking - Inband Networking Mode

As shown in Figure 3-36, the SNMP protocol is transmitted through the service channel. Service
packets and management packets are transmitted through the same channel. The inband NMS
management is implemented through the upstream port.
l
The MA5616 supports the GPON/GE upstream port.
A static route is used between the MA5616 and the U2000.
Figure 3-36 Inband networking

NMS Client A
Integrated NMS
Center
ONU
NMS Client B
U2000
BRAS
OLT
Service channel and

Management channel
Networking - Outband Networking Mode

As shown in Figure 3-37, the SNMP protocol is transmitted through the management channel.
Service packets and management packets are transmitted through different channels. The
outband NMS management is implemented through the maintenance network port.
l
The MA5616 supports the local maintenance network port ETH.
Issue 02 (2013-10-08)

51

Configuration Guide
Figure 3-37 Outband networking

NMS client A
NMS client B
Integrated NMS
Center
BRAS
U2000
LAN Switch
Service channel
Management channel
ONU
Figure 3-38 shows the flowchart for configuring the NMS.
Figure 3-38 Flowchart for configuring the NMS
Flowchart for
configuring the MXU
Start
Set the SNMP parameters
Enable trap sending

Set the IP address of the
target host for traps
Set the source address for
traps sending
Save the data
End
Issue 02 (2013-10-08)

52

Configuration Guide
Procedure
l
Configuration procedure on the device

1.
Configure the SNMP parameters.

a.
Configure the community names and the access rights.

Run the snmp-agent community command to configure the community names
and the access rights.
NOTE
The read community name is public. The write community name is private.
The read community name and the write community name on the device must be the
same as those configured on the U2000.
huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
b.
(Optional) Set the information about the administrator.

Run the snmp-agent sys-info command to set the contact of the SNMP Agent
administrator and the physical position of the device.
Contact of the administrator: HW-075528780808. Physical position of the
device: Shenzhen_China.
huawei(config)#snmp-agent sys-info contact HW-075528780808
huawei(config)#snmp-agent sys-info location Shenzhen_China
c.
Set the SNMP version.

Run the snmp-agent sys-info command to set the required SNMP version.
huawei(config)#snmp-agent sys-info version v1
NOTE
The SNMP version on the device must be the same as that configured on the U2000.
2.
Enable the function of sending traps.

Run the snmp-agent trap enable command on the device to enable the function of
sending traps to the NMS. After the function is enabled, the device reports abnormal
events to the NMS server.
huawei(config)#snmp-agent trap enable standard
3.
Configure the IP address of the target host of the traps.

Run the snmp-agent target-host trap-hostnamehostnameaddressip-addr [ udpportudp-portid ] trap-paramsnameparamsname command to configure the IP
address of the target host of the traps.
The host name is huawei, the IP address of the host is 10.10.1.10/24 (that is, the IP
address of the U2000), the name of the target host is ABC, the SNMP version is V1,
and the security name is private (that 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
NOTE
udp-port: is the destination host port ID of traps. The default value (162) takes effect if you
do not specify a value. The default values on the NMS is 162 and is recommended.
4.
Issue 02 (2013-10-08)
Configure the source IP address of the traps.

53

Configuration Guide
Run the snmp-agent trap source command to configure the source IP address of the
traps.
In inband networking mode, the IP address of the upstream port is used as the
source IP address of the traps.
In outband networking mode, the IP address of the maintenance network port is
used as the source IP address of the traps.
NOTE
This document considers the outband networking mode as an example.

huawei(config)#snmp-agent trap source meth 0
5.
Save the data.

huawei(config)#save
Configuration procedure on the NMS

NOTE
In inband networking mode, you only need to perform the configuration on the MA5616. This step
can be omitted because the MA5616 can be automatically discovered through the OLT.
In outband networking mode, you need to follow this step to perform the configuration on the NMS.
1.
Add a route from the NMS to the device.

Configure the IP address of the gateway from the NMS server to network segment
10.50.1.0/24 to 10.10.1.1.
In the Solaris operating system (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 NMS port and the IP address of the U2000 are in the same
network segment, you need not configure the route.
2.
Log in to the U2000.
3.

NOTE
A default SNMP profile exists in the system and is used in this example. If you need to configure
a new profile, do as follows:
Issue 02 (2013-10-08)
a.
Choose Administration > NE Communicate Parameter > Default Access

Protocol Parameters from the main menu.
b.
In Default Access Protocol Parameters, click the SNMPv1 Parameters tab,

and then click Add.
54

Configuration Guide
c.
Set the profile name, and then set other parameters according to the plan.
NOTE
NE Port: is the management port ID. The default value on the NMS is 161 and is
recommended.
d.
4.
Click OK. Then, the SNMP parameters are configured.
Add a device.
a.
Right-click in the main topology, and then choose New > NE from the shortcut
menu.
b.
In the dialog box that is displayed, set relevant parameters.
NOTE
l The IP address is the management IP address of the MA5616.

l Select the SNMP parameters based on the selected SNMP protocol. This section
considers the SNMP V1 default profile as an example. You can select the profile
according to the plan.
c.
Click OK. Several seconds to some 10 minutes are required for uploading the
device data. After reading the related data, the system automatically updates the
device icon.
----End
Result
You can maintain and manage the MA5616 through the U2000.
Issue 02 (2013-10-08)

55

Configuration Guide
Configuration File
The following part provides the script for configuring the outband NMS (on the device).
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
save
community read public

community write private
sys-info contact HW-075528780808
sys-info location Shenzhen_China
sys-info version v1
trap enable standard
target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABC
target-host trap-paramsname ABC v1 securityname private
trap source meth 0
The following part provides the script for configuring the inband NMS (on the device). The
management VLAN ID of the upstream port is 30.
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
save

sys-info version v1
target-host trap-paramsname ABC v1 securityname private
trap source vlanif 30
3.2.2 Configuring the U2000 (Based on SNMPv2c)

When SNMPv2c is used, the MA5616 can be interconnected with the U2000 in inband or
outband networking mode.
Prerequisites
l

As shown in the inband networking in 3.2.1 Configuring the U2000 (Based on SNMPv1), the
SNMP protocol is transmitted through the service channel. Service packets and management
packets are transmitted through the same channel. The inband NMS management is implemented
through the upstream port.
l
Issue 02 (2013-10-08)

56

Configuration Guide

SNMP protocol is transmitted through the management channel. Service packets and
management packets are transmitted through different channels. The outband NMS management
is implemented through the maintenance network port.
l
To configure the NMS, see the flowchart for configuring the NMS in 3.2.1 Configuring the
U2000 (Based on SNMPv1).
Procedure
l

1.

a.
Configure the community names and the access rights.

Run the snmp-agent community command to configure the community names
and the access rights.
NOTE
The read community name is public. The write community name is private.
The read community name and the write community name on the device must be the
same as those configured on the U2000.
huawei(config)#snmp-agent community read public
huawei(config)#snmp-agent community write private
b.
(Optional) Set the information about the administrator.

huawei(config)#snmp-agent sys-info location XA_China
c.

huawei(config)#snmp-agent sys-info version v2c
NOTE
2.

3.
Issue 02 (2013-10-08)

57

Configuration Guide
address of the U2000), the name of the target host is ABC, the SNMP version is V2c,
and the security name is private (that is, the SNMP community name).
huawei(config)#snmp-agent target-host trap-paramsname ABC v2c
securityname private
NOTE
4.

traps.
NOTE

5.
Save the data.

huawei(config)#save

NOTE
In inband networking mode, you only need to perform the configuration on the MA5616. This step
can be omitted because the MA5616 can be automatically discovered through the OLT.
In outband networking mode, you need to follow this step to perform the configuration on the NMS.
1.

10.50.1.0/24 to 10.10.1.1.
table.
route.
Issue 02 (2013-10-08)

58

Configuration Guide
table.
NOTE
2.
3.

NOTE
A default SNMP profile exists in the system and is considered in this example. If you need to
configure a new profile, do as follows:
a.

b.

and then click Add.
c.
NOTE
recommended.
d.
4.
Issue 02 (2013-10-08)
Add a device.
a.
menu.
b.

59

Configuration Guide
NOTE

l Select the SNMP parameters based on the selected SNMP version. This section
considers the SNMP V2 default profile as an example. You can select the profile
corresponds to the actual planning.
c.
device data. After reading the related data, the system automatically updates the
device icon.
----End
Result
Configuration File
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
save

sys-info version v2c
target-host trap-paramsname ABC v2c securityname private
trap source meth 0
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
snmp-agent
save

sys-info version v2c
target-host trap-paramsname ABC v2c securityname private
trap source vlanif 30
3.2.3 Configuring the U2000 (Based on SNMPv3)

When SNMPv3 is used, the MA5616 can be interconnected with the U2000 in inband or outband
networking mode.
Prerequisites
l
Issue 02 (2013-10-08)
60

Configuration Guide

SNMP protocol is transmitted through the service channel. Service packets and management
packets are transmitted through the same channel. The inband NMS management is implemented
through the upstream port.
l

As shown in the outband networking in 3.2.1 Configuring the U2000 (Based on SNMPv1),
the SNMP protocol is transmitted through the management channel. Service packets and
management packets are transmitted through different channels. The outband NMS management
is implemented through the maintenance network port.
l
To configure the NMS, see the flowchart for configuring the NMS in 3.2.1 Configuring the
U2000 (Based on SNMPv1).
Procedure
l

1.

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

The user name is user1, the group name is group1, the user authentication mode
is MD5, the authentication password is authkey123, the user encryption mode is
des56, the encryption password is prikey123, the read and write view names are
hardy, and the view includes the Internet subtree.
huawei(config)#snmp-agent usm-user v3 user1 group1 authenticationmode md5 authk
ey123 privacy-mode des56 prikey123
huawei(config)#snmp-agent group v3 group1 privacy read-view hardy
write-view hardy
huawei(config)#snmp-agent mib-view hardy include internet
b.
(Optional) Set the information about the administrator and the device.
Issue 02 (2013-10-08)

61

Configuration Guide

huawei(config)#snmp-agent sys-info location Shenzhen_China
c.
(Optional) Configure the engine ID of the SNMP entity.

Run the snmp-agent local-engineid command to configure the engine ID of the
SNMP environment to 0123456789.
NOTE
The engine ID of the SNMP environment must be the same as that configured on the
U2000.
huawei(config)#snmp-agent local-engineid 0123456789
Info: Modify the local-engineid will disable the configured SNMPv3
user, all
users must be reconfigured, proceed? (y/n)[n]:y
d.

huawei(config)#snmp-agent sys-info version v3
NOTE
2.

3.

address of the U2000), the name of the target host is ABC, the SNMP version is V3,
the security name is user1 (when SNMP V3 is used, the security name is the USM
user name), and the traps are authenticated and encrypted.
huawei(config)#snmp-agent target-host trap-paramsname ABC v3 securityname
user1 privacy
NOTE
4.

traps.
Issue 02 (2013-10-08)

62

Configuration Guide

NOTE

5.
Save the data.

huawei(config)#save

1.

10.50.1.0/24 to 10.10.1.1.
table.
route.
table.
NOTE
Issue 02 (2013-10-08)
2.
3.

a.

b.

and then click Add.
c.

63

Configuration Guide
NOTE
recommended.
d.
Select corresponding protocol type in Priv Protocol and Auth Protocol, and
behind the parameter. In the Password dialog box, set the
then click
passwords for Priv Protocol and Auth Protocol. Then, click OK.
NOTE
NE User, Context Engine ID, Priv Protocol and the password, and Auth Protocol and
the password must be the same as those configured on the MA5616. The display snmpagent usm-user command is used to query the device user, data encryption protocol, and
authentication protocol configured on the MA5616. The display snmp-agent localengineid command is used to query the environment engine ID configured on the
MA5616.
e.
4.
Issue 02 (2013-10-08)
Add a device.
a.
menu.
b.

64

Configuration Guide
NOTE

l Select the SNMP parameters based on the selected SNMP version. This section
considers the SNMP V3: huawei profile as an example. You can select the profile
according to the plan.
c.
device data. After reading the related, the system automatically updates the
device icon.
----End
Result
Configuration File
snmp-agent usm-user v3 user1 group1 authentication-mode md5 authkey123 privacy-mode
des56 prikey123
snmp-agent group v3 group1 privacy read-view hardy write-view hardy
snmp-agent mib-view hardy include internet
snmp-agent sys-info contact HW-075528780808
snmp-agent sys-info location Shenzhen_China
snmp-agent local-engineid 0123456789
snmp-agent sys-info version v3
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 v3 securityname user1 privacy
snmp-agent trap source meth 0
save
snmp-agent usm-user v3 user1 group1 authentication-mode md5 authkey123 privacy-mode
Issue 02 (2013-10-08)

65

Configuration Guide
des56 prikey123
snmp-agent group v3 group1 privacy read-view hardy write-view hardy
snmp-agent mib-view hardy include internet
snmp-agent sys-info contact HW-075528780808
snmp-agent sys-info location Shenzhen_China
snmp-agent local-engineid 0123456789
snmp-agent sys-info version v3
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 v3 securityname user1 privacy
snmp-agent trap source vlanif 30
save
3.3 Configuring the Attributes of the Upstream Port

The MA5616 can be interconnected with the upstream device through upstream GPON/GE port.
This topic describes how to configure the attributes of upstream GPON/GE port so that the device
communicates successfully with the upstream device.
3.3.1 (Optional) Configuring an Uplink Ethernet Port

This topic describes how to configure a specified uplink Ethernet port so that the system can use
it to communicate with an upper-layer device.
Prerequisites
If you configure the MA5616 in offline mode, the port mode is configured using the port
mode command.
NOTE
The CCUC or CCUE control board supports this command and the CCUB control board does not support.
Context
The MA5616 must be interconnected with an upper-layer device through Ethernet port.
Therefore, ensure that the attributes of the Ethernet port connecting the two devices are the same.
The MA5616 supports Ethernet cascading network. On the network, multiple devices can be
cascaded using GE ports to extend the network coverage and meet the requirements for large
access capacity. When two MA5616s are cascaded, set GE port 0 on the upper-layer device as
the cascaded port and set GE port 0 on the lower-layer device as the uplink port. For details
about the configuration principles, see Table 3-9.
Table 3-9 Configuration principles of uplink and cascaded ports on an MA5616
Control Board
Daughter Board
on the Control
Board
Configuration Principles
CCUB
GP1A
l GE port 0: is set as a cascaded or uplink port.

l GPON port: is always set as an uplink port.
Issue 02 (2013-10-08)

66

Configuration Guide
Control Board
Daughter Board
on the Control
Board
Configuration Principles
EP1A

l EPON port: is always set as an uplink port.
GE1A

l GE port 1: is always set as an uplink port.
CCUC
UP2A/UP2C

CCUE
UP2A

XP1A
10G GPON port: is always set as an uplink port.
Default Settings
Table 3-10 lists the default settings of Ethernet port attributes.
Table 3-10 Default settings of Ethernet port attributes
Parameter
Default Setting (Optical Port)
Default Setting (Electrical

Port)
Auto negotiation
mode
Enabled
Enabled
Rate
Auto negotiation
N/A
NOTE
After the auto negotiation mode
of a port is disabled, configure the
port rate.
Duplex mode
Auto negotiation
N/A
NOTE
After the auto negotiation mode
of a port is disabled, configure the
duplex mode.
Issue 02 (2013-10-08)
Network cable
adaptation mode
Not supported
Flow control
Disabled
l FE electrical port: auto

l GE electrical port: normal

Disabled
67

Configuration Guide
Procedure
l
Configure the physical attributes of an Ethernet port.

1.
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.
After the auto negotiation mode is enabled, the port automatically negotiates with
the peer port for the rate and working mode.
After the auto negotiation mode is disabled, the rate and working mode of the port
are in the forced mode (the two attributes use default values or are set using
command line interface (CLI)).
2.
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 preset rate. When setting the rate, ensure that:
The rate of the Ethernet port is the same as that of the interconnected port on the
upper-layer device. This prevents communication failures.
The auto negotiation mode of the Ethernet port is disabled.
3.
Configure the duplex mode of the Ethernet port.

Run the duplex command to configure the duplex mode of the Ethernet port. The
duplex mode of an Ethernet port can be full-duplex, half-duplex, or auto negotiation.
When setting the duplex mode, ensure that:
The ports of two interconnected devices work in the same duplex mode. This
prevents communication failures.
The auto negotiation mode is disabled.
4.
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 classified
into:
normal: The straight-through cable is used as the network cable. In this mode, the
network cable connecting to the Ethernet port must be a straight-through cable.
across: The crossover cable is used as the network cable. In this mode, the network
cable connecting to the Ethernet port must be a crossover cable.
auto: The network cable is selected in auto negotiation mode. In this mode, the
network cable can be a straight-through or crossover cable.
When configuring the network cable adaptation mode, pay attention to the following
points:
The Ethernet optical port does not support the network cable adaptation mode.
If an Ethernet electrical port works in forced mode (the auto negotiation mode is
disabled), the network cable adaptation mode of the port cannot be configured to
auto.
Configure an Ethernet cascaded port.

1.
Run the network-role command to set the port as an uplink or cascaded port.
For details about the configuration principles of uplink or cascaded ports, see Table
3-9.
Issue 02 (2013-10-08)

68

Configuration Guide
2.
Run the combo-mode command to switch the optical/electrical adaptation mode of

the Ethernet port.
On a cascading network, the optical/electrical adaptation mode of a cascaded port
must be the same as that of an uplink port. The recommended mode is
autoadaptation because the setting ensures that the system can select a mode
automatically.
A GE port supports optical and electrical modes:
For a CCUB control board, uplink GE port 0 on the daughter board or GE electrical
port 0 on the front panel can be selected. Only one port is used at a time.
For a CCUC or CCUE control board:
The uplink port on the daughter board supports GE optical or electrical module
and provides GE optical or electrical port. Only one port is used at a time.
Uplink port 0 on the daughter board or GE electrical port 0 on the front panel
can be selected. Only one port is used at a time.
Run the flow-control command to enable the flow control on the Ethernet port.
Run the mirror port command to mirror the Ethernet port.
----End
Example
Assume that an Ethernet optical port on the 0/0/1 has the following attributes:
l
Duplex mode: full-duplex
Flow control: enabled
Auto negotiation mode: not enabled
To configure the Ethernet port, do as follows:

huawei(config)#interface eth 0/0
huawei(config-if-eth-0/0)#auto-neg 1 disable
huawei(config-if-eth-0/0)#duplex 1 full
huawei(config-if-eth-0/0)#flow-control 1
3.3.2 Configuring the Attributes of an Uplink GPON Port

This topic describes how to query the statistics for a port, set the working mode of an optical
module, and set the alarm thresholds for the receive optical power of the optical module through
an uplink GPON port.
Prerequisites
If you configure the MA5616 in offline mode, the port attribute can be configured only after the
port mode is configured using the port mode command.
Procedure
l
Set the password for registering with an OLT.

Run the password (in GPONNNI mode) command to set the registration password of the
current device that functions as a GPON ONU.
Issue 02 (2013-10-08)

69

Configuration Guide
NOTE
When dual GPON ports are used for upstream transmission, only 0/0/1 port can be set. After the
setting, the parameters of port 0/0/1 are the same as those of port 0/0/0.
(Optional) Set the alarm thresholds for the optical module.

Run the optical-module threshold (in GPONNNI mode) command to set the alarm
thresholds of the optical module.
Set the working mode of the optical module of the uplink GPON port.
Run the laser (in GPONNNI mode) command to set the working mode of the optical module
to auto, on, or off.
auto: indicates the automatic optical signal transmission mode. When this mode is used,
the optical port is working properly and services are running properly.
on: indicates the continuous optical signal transmission mode. This mode is used to
detect the transmit power of an optical port. When the detection is complete, the optical
signal transmission mode is automatically switched to auto.
off: disables the optical port. This mode is used in a test or to locate a fault.
CAUTION
If the working mode of an optical module is set to off, services are interrupted and the
ONU goes offline. Therefore, before setting the work mode to off, ensure that no
services are carried on the uplink port.
l
Query the statistics for the port.

Run the display gpon-port statistic command to query the traffic information and line
status of the GPON port.
----End
Example
To set the password for registering with an OLT through a GPON port, set the lower limit for
the receive optical power of an optical module to 5 dBm and the upper limit for the receive
optical power to 50 dBm, set the working mode of the optical module of the uplink PON port
to auto, run the following command:
huawei(config-if-gponnni-0/0/1)#password huawei
huawei(config-if-gponnni-0/0/1)#optical-module threshold rx-power lower-limit 5
upper-limit 50
huawei(config-if-gponnni-0/0/1)#laser auto
huawei(config-if-gponnni-0/0/0)#password huawei
huawei(config-if-gponnni-0/0/0)#optical-module threshold rx-power lower-limit 5
upper-limit 50
huawei(config-if-gponnni-0/0/0)#laser auto
3.4 Configuring the ANCP

Access Node Control Protocol (ANCP) is used to implement the functions such as topology
discovery, line configuration, and Layer 2 Control (L2C) OAM on the user ports. The
Issue 02 (2013-10-08)

70

Configuration Guide
MA5616 establishes an ANCP session according to the communication IP address of the General
Switch Management Protocol (GSMP) that is used by the network access server (NAS).
Context
l
The MA5616 and the NAS use the TCP connection to carry an ANCP session. Therefore,
before creating the ANCP session, you must create a TCP connection between the
MA5616 and the NAS. The NAS functions as the server of the TCP connection, and the
MA5616 functions as the client of the TCP connection.
After the TCP connection is created successfully between the MA5616 and the NAS, an
ANCP session is created between the MA5616 and the NAS. After the ANCP session is
created successfully, the MA5616 and the NAS need to use the ANCP ACK packets for
heartbeat detection to maintain the ANCP session.
The default values of the ANCP parameters are as follows:

GSMP communication IP address for an ANCP session: 0.0.0.0
ANCP session capability set: topology-discovery, line-config, and oam
ANCP packet sending priority: 6
GSMP TCP communication port ID on the NAS side in an ANCP session: 6068
Interval for sending packets during the initial stage of an ANCP session: 10 (unit: 0.1s)
Interval for sending packets during the ANCP session stage: 100 (unit: 0.1s)
NOTE
Before an ANCP session is enabled, related parameters can be configured or modified. After an ANCP
session is enabled, related parameters cannot be configured or modified.
Procedure
Step 1 Run the ancp session command to enter the ANCP session mode.
NOTE
Currently, the system supports 60 ANCP sessions.
Step 2 Run the ancp ip command to configure the GSMP communication IP address for the ANCP
session.
l The IP address configured here must be the same as the GSMP communication IP address
configured on the NAS, but it should to not be the same as the default IP address, multicast
IP address, or broadcast IP address.
l When an ANCP session is enabled, the GSMP communication IP address cannot be
configured.
Step 3 (Optional) Run the ancp capability command to configure the capability set of the ANCP
session. The default value is all, that is, the three capabilities (topology discovery, line
configuration, and L2C OAM) are supported.
l Supports topology discovery. When you select topology-discovery parameter, the DSLAM
automatically reports the line parameters to the NAS.
l Supports line configuration. When you select line-config parameter, the DSLAM responds
to the line configuration that is sent by the NAS.
l Supports the OAM. When you select oam parameter, the DSLAM responds to the line testing
information that is sent by the NAS.
Issue 02 (2013-10-08)

71

Configuration Guide
l Supports the preceding three types of capabilities, when you select all.
Step 4 (Optional) Run the ancp ancp-8021p command to set the priority for sending ANCP packets.
You can set the priority according to the actual requirements and network conditions, the higher
the priority, the higher the reliability.
Step 5 (Optional) Run the ancp nas-tcp-port command to set the GSMP TCP communication port ID
for the ANCP session on the NAS. By default, the GSMP TCP communication port ID is 6068.
The GSMP TCP communication port ID on the MA5616 must be the same as that on the NAS.
Step 6 (Optional) Run the ancp init-interval command to set the interval for sending packets during
the establishment of the ANCP session. By default, the general query interval is 1s.
Step 7 (Optional) Run the ancp keep-alive command to set the interval for sending packets during the
ACNP session so that the handshake messages can be sent to the peer end at the preset interval.
By default, the interval is 25s.
Step 8 Run the ancp enable command to enable the ANCP function. By default, the ANCP function
is disabled.
Step 9 Run the quit command to quit the ANCP mode.
Step 10 Run the display ancp session command to query the information about the ANCP session.
----End
Example
Assume that:
l
The GSMP communication IP address for an ANCP session is 10.10.10.10.
The interval for sending packets during the initial stage of an ANCP session is 2s.
The ANCP session capability set is topology-discovery.
The ANCP packet sending priority is 7.
The GSMP TCP communication port ID on the NAS side in an ANCP session is 6000.
The interval for sending packets during the ANCP session stage is 7s.
The ANCP function is enabled.
To perform the preceding configurations, do as follows:

huawei(config)#ancp session 1
huawei(config-session-1)#ancp ip 10.10.10.10
huawei(config-session-1)#ancp capability topology-discovery
huawei(config-session-1)#ancp ancp-8021p 7
huawei(config-session-1)#ancp nas-tcp-port 6000
huawei(config-session-1)#ancp init-interval 20
huawei(config-session-1)#ancp keep-alive 70
huawei(config-session-1)#ancp enable
huawei(config-session-1)#quit
huawei(config)#display ancp session 1
Session config status
: Enable
Session running status
: Before syn phase
Session diagnostic status
: GSMP version
: 3
GSMP sub version
: 1
Configured AN name
: AN name
: NAS name
: -
Issue 02 (2013-10-08)

72

Configuration Guide
NAS IP
Local IP
AN instance
NAS instance
Configured capabilities
Negotiate capabilities
NAS TCP port
Startup time(0.01s)
Discontinuity time(0.01s)
Init interval(0.1s)
Keepalive interval(0.1s)
PartitionID
Partition used status
Bandwidth CAC status
Line config roll default
OAM threshold(0.01)
Topology report shaper interval(0.1s)
S-VLAN
S-VLAN priority
C-VLAN
C-VLAN priority
Session down send trap status
Session up send trap status
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
10.10.10.10
TopologyDiscovery
6000
20
70
0
Disable
Disable
100
10
7
Disable
Disable

Prerequisites
The ID of the planned VLAN is not occupied.
Application Scenario
VLAN application is specific to user types. For details on the VLAN application, see Table
3-11.
Table 3-11 VLAN application and plan
Issue 02 (2013-10-08)
Usage
Scenarios
VLAN Plan
Remarks
The device
communicates
with a network
management
system (NMS) or
the devices are
cascaded.
VLAN type: standard VLAN
This plan is only applicable to

Ethernet ports.
VLAN attribute: common

VLAN forwarding mode: VLAN
+MAC

A standard VLAN only contains

multiple uplink ports. The Ethernet
ports in one VLAN can
communicate with each other and
the Ethernet ports in different
VLANs are separated.
73

Configuration Guide
Usage
Scenarios
VLAN Plan
Remarks
N:1 access
VLAN type: smart VLAN
This plan is used for converging

and transmitting the services of
multiple users to one VLAN. This
reduces the number of VLANs to
be used.

+MAC
A smart VLAN can contain

multiple uplink ports and multiple
service ports. The service ports in
one smart VLAN are separated.
The service ports in different
VLANs are also separated.
1:1 access
l Multi-ISP
wholesale
service (ISP is
the
abbreviation
of Internet
service
provider.)
VLAN attribute: stacking

+MAC or S+C
A stacking VLAN packet contains

two VLAN tags (inner and outer
VLAN) assigned by the MA5616.
The outer VLAN identifies a
service (service VLAN) and the
inner VLAN identifies a user
(customer VLAN).
The service used by a user is
identified by a unique VLAN ID (S
+C VLAN).
l VLAN ID
expansion
service
The upper layer broadband remote

access server (BRAS)
authenticates a service by the two
VLAN tags contained in the
service packets. In this manner, the
BRAS can receive packets from
more users.
On a Layer-2 upper layer network
of the MA5616, packets can also be
forwarded by the outer VLAN
+MAC ID. This function enables
ISPs to provide the wholesale
services.
Enterprise private
line service
access
Issue 02 (2013-10-08)

VLAN attribute: QinQ
+MAC or S+C

A QinQ VLAN contains an inner

VLAN tag from the user private
network, and an outer VLAN tag
assigned by the MA5616.
The outer VLAN forms a Layer 2
virtual private network (VPN) on
the user private network for
transparently transmitting user
services on the private network.
74

Configuration Guide
3.5.1 Configuring a VLAN

Configuring VLAN is a prerequisite for configuring a service. Hence, before configuring a
service, make sure that the VLAN configuration based on planning is complete.
Prerequisites
l
Service VLAN cannot be reserve VLAN.
Default Configuration
Table 3-12 lists the default parameter settings of VLAN.
Table 3-12 Default parameter settings of VLAN
Parameter
Default Setting
Remarks
Default VLAN of
the system
VLAN ID: 1
None
Reserved VLAN
of the system
VLAN ID range:
4079-4093
You can run the vlan reserve command to

modify the VLAN reserved by the system.
Default attribute
of a new VLAN
Common
None
Type: smart VLAN
Procedure
Step 1 Create a VLAN.
Run the vlan command to create a VLAN. VLANs of different types are applicable to different
scenarios.
VLAN Type
Configuration Command
Standard VLAN
To add a standard VLAN, run the vlan vlanid standard

command.
Smart VLAN
To add a smart VLAN, run the vlan vlanid smart command.
MUX VLAN
To add a MUX VLAN, run the vlan vlanid mux command.
NOTE
l To add VLANs that have consecutive IDs in batches, run the vlan vlanid to end-vlanid command.
l To add VLANs that do not have consecutive IDs in batches, run the vlan vlan-list command.
Step 2 (Optional) Configure the VLAN attribute.

Issue 02 (2013-10-08)

75

Configuration Guide
The default attribute for a new VLAN is "common". You can run the vlan attrib command to
configure the attribute of the VLAN.
Configure the attribute according to VLAN planning.
VLAN
Attribute
Configuration Command
VLAN Type
Common
The default attribute for a new VLAN

is "common".
The VLAN with this attribute can be

a standard VLAN, smart VLAN, or
MUX VLAN.
QinQ VLAN
To configure QinQ as the attribute of

a VLAN, run the vlan attrib vlanid
q-in-q command.
The VLAN with this attribute can be

a standard VLAN, smart VLAN, or
MUX VLAN.
VLAN
Stacking
To configure stacking as the attribute

of a VLAN, run the vlan attrib
vlanid stacking command.
The VLAN with this attribute can

only be a smart VLAN or a MUX
VLAN.
l If a stacking VLAN is used, users

can run the stacking label
command to configure the label of
a service port.
l Users can run the stacking outerethertype command to configure
the outer Ethernet protocol type
supported by VLAN stacking on
the MA5616.
l Users can run the stacking innerethertype command to configure
the inner Ethernet protocol type
supported by system VLAN
stacking. To ensure connection,
the inner and outer Ethernet
protocol types configured on the
MA5616 and on the connected
device from other vendors must
be the same.
NOTE
l To configure attributes for the VLANs with consecutive IDs in batches, run the vlan attrib vlanid to endvlanid command.
l To configure attributes for the VLANs with inconsecutive IDs in batches, run the vlan attrib vlan-list
command.
Step 3 (Optional) Configure VLAN description.
Issue 02 (2013-10-08)

76

Configuration Guide
To configure VLAN description, run the vlan desc command. You can configure VLAN
description to facilitate maintenance. The general VLAN description includes the usage and
service information of the VLAN.
----End
Example
To configure VLAN 10 (attribute: common) for N:1 access scenario, do as follows:
huawei(config)#vlan attrib 10 common
Assume that a stacking VLAN with ID of 50 is to be configured for VLAN ID extension. A

service port is added to VLAN 50. The outer VLAN tag 50 of the stacking VLAN identifies the
access device and the inner VLAN tag 10 identifies the user with access to the device. For the
VLAN, description needs to be configured for easy maintenance. To configure such a VLAN,
do as follows:
huawei(config)#vlan attrib 50 stacking
huawei(config)#service-port vlan 50 eth 0/3/1 multi-service user-encap pppoe
rx-cttr 6 tx-cttr 6
huawei(config)#stacking label vlan 50 baselabel 10
huawei(config)#vlan desc 50 description stackingvlan/label10
3.5.2 Configuring the VLAN Forwarding Policy

The configuration of VLAN forwarding policies is the foundation of the VLAN configuration,
and is also an important step to ensure that services are forwarded correctly. Before the service
configuration, make sure that VLAN forwarding policies have been configured properly
according to the actual planning.
Prerequisites
l
VLAN IDs are created correctly.
VLAN attributes are configured properly.
Context
VLAN forwarding policy refers to the Layer 2 forwarding mechanism of packets. It can be vlanconnect or vlan-mac.
l
In the vlan-connect mode, the system forwards packets based on S+C. This mode ensures
higher security by solving the problems of insufficient MAC address space, MAC address
aging, MAC address spoofing, and MAC address attacks. The S+C forwarding policy is
used when an MA5616 is connected to a large number of terminals.
In the vlan-mac mode, the system forwards the packets based on the VLAN and MAC
address of packets. On Layer 2, packets are generally forwarded based on the VLAN tags
contained in the packets and the MAC addresses of the packets. The VLAN+MAC
forwarding policy is used when an MA5616 is connected to a small number of terminals.
Table 3-13 lists the default forwarding policy settings of VLAN.
Issue 02 (2013-10-08)

77

Configuration Guide
Table 3-13 Default parameter settings of VLAN

Parameter
Default Setting
VLAN forwarding mode
VLAN+MAC
Procedure
Step 1 Run the vlan service-profile command to create a VLAN service profile and enter the VLAN
service profile mode.
Step 2 Run the forwarding command to configure the VLAN forwarding policy. The default VLAN
forwarding policy is VLAN+MAC in the system.
Step 3 Run the commit command to validate the profile configuration. The configuration of the VLAN
service profile takes effect only after execution of this command.
Step 4 Run the quit command to quit the VLAN service profile mode.
Step 5 Run the vlan bind service-profile command to bind the VLAN to the VLAN service profile
created in Step 1.
----End
Example
Assume that a QinQ VLAN with ID of 100 is to be configured for enterprise private line service,
and that the S+C VLAN forwarding policy is used to ensure higher security. The VLAN
description also needs to be configured for easy maintenance. To configure such a VLAN, do
as follows:
huawei(config)#vlan attrib 100 q-in-q
huawei(config)#vlan desc 100 description qinqvlan/forhuawei
huawei(config)#vlan service-profile profile-id 1
huawei(config-vlan-srvprof-1)#forwarding vlan-connect
Info: Please use the commit command to make modifications take effect
huawei(config-vlan-srvprof-1)#commit
huawei(config-vlan-srvprof-1)#quit
huawei(config)#vlan bind service-profile 100 profile-id 1
3.5.3 Configuring a VLAN Service Profile

This topic describes how to configure a virtual local area network (VLAN) service profile, which
contains service-related VLAN parameters. After being bound to a service profile, a VLAN has
the attributes defined in the service profile. The VLAN service profile is used to efficiently
configure VLANs.
Prerequisite
l
The VLAN to which the VLAN service profile is bound is created.
The Policy Information Transfer Protocol (PITP), Dynamic Host Configuration Protocol
(DHCP), VMAC, anti-IP address spoofing, anti-MAC address spoofing functions can be
Issue 02 (2013-10-08)

78

Configuration Guide
enabled or disabled at two levels, global level and VLAN level. These functions take effect
only when they are enabled at all the levels.
Context
The configuration of a VLAN, which is necessary for access network (AN) devices, involves a
large number of discrete service parameters related to the forwarding mode, forwarding policy,
security feature, protocol packet transparent transmission, and enabling or disabling a protocol.
The live network usually requires massive VLANs, resulting in complex VLAN configuration.
A VLAN service profile collects service parameters related to a specified type of VLAN and
encapsulates the service parameters. After a VLAN service profile is bound to or unbound from
multiple VLANs of the same type, the VLANs are efficiently configured.
l
If the VLAN profile is bound to a QinQ VLAN, the IP spoofing and MAC spoofing
functions do not take effect.
The VLAN profile does not support the use of the SVLAN+CVLAN forwarding and MAC
spoofing functions at the same time.
If the VLAN profile is bound to a smart VLAN with the common attribute, the packet
forwarding mode cannot be set to vlan-connect (SVLAN+CVLAN).
Procedure
Step 1 Create a VLAN service profile.
Run the vlan service-profile command to create a VLAN service profile or enter the
configuration mode of the VLAN service profile.
l When the profile does not exist, running this command creates a VLAN service profile and
enters the configuration mode of the service profile.
l When the profile exists, running this command directly enters the configuration mode of the
service profile.
Step 2 Configure parameters of the VLAN service profile.
The VLAN service profile contains VLAN-related configurations. You can configure them
based on site requirements.
l VLAN forwarding mode
Run the forwarding command to configure the VLAN forwarding mode.
The VLAN forwarding mode in which packets are forwarded at Layer 2 can be either
VLAN+MAC (default value: vlan-mac) or SVLAN+CVLAN (or S+C; default value:
vlan-connect). In VLAN+MAC forwarding mode, the system dynamically learns the
mapping between VLANs, source Media Access Control (MAC) addresses, and ports to
forward packets. In S+C forwarding mode, the system determines the forwarding entries
only based on the 2-tuple formed by a virtual local area network (SVLAN) and a customer
virtual local area network (CVLAN). The S+C forwarding mode does not require the
system to learn MAC addresses, and therefore has the following advantages:
Preventing failures caused by insufficient MAC addresses
Resolving security issues when unknown unicast packets caused by aged MAC
addresses are broadcast in a VLAN
Preventing MAC address spoofing or attacks
Issue 02 (2013-10-08)

79

Configuration Guide
Run the user-bridging command to configure the Layer 2 bridging function of the VLAN
service profile. After the Layer 2 bridging function is enabled, two users in the same
VLAN can directly communicate with each other at Layer 2.
l Forwarding policy
The forwarding policy determines whether to and how to discard downstream broadcast
packets, unknown unicast packets, or unknown multicast packets.
Run the packet-policy command to configure the forwarding policy for the unknown
multicast packets in a VLAN. Two policies (forward and discard) are supported.
Run the igmp mismatch command to configure the processing policy for the unmatched
IGMP packets. Two policies (discard and transparent) are supported.
l Security feature
A security feature prevents malicious users from attacking the network using IP or MAC
address spoofing. Among security features, the virtual MAC address (VMAC) function or
the anti-IP address spoofing function cannot be used when the S+C mode is enabled.
Run the security anti-ipspoofing command to configure the anti-IP address spoofing
function. After the anti-IP address spoofing function is enabled, the system automatically
and dynamically binds the IP address to the user. The device transmits the packet upstream
only when the source IP address of the packet is the same as the bound IP address.
Otherwise, the device discards the packet.
Run the security anti-ipv6spoofing command to configure the anti-IPv6 spoofing
function. After the anti-IPv6 spoofing function is enabled, the system automatically and
dynamically binds the IPv6 address to the user. The device transmits the packet upstream
only when the source IPv6 address of the packet is the same as the bound IPv6 address.
Otherwise, the device discards the packet.
NOTE
The CCUC and CCUE control boards support the anti-IPv6 spoofing function and the CCUB
control board does not support this function.
Run the security anti-macspoofing command to configure the anti-MAC address

spoofing function. After the anti-MAC address spoofing function is enabled, the system
automatically and dynamically binds the MAC address to the traffic stream. The device
transmits the traffic stream upstream only when the source MAC address of the traffic
stream is the same as the bound MAC address. Otherwise, the device discards the traffic
stream.
Run the vmac command to enable or disable VMAC of IP over Ethernet (IPoE), Pointto-Point Protocol over ATM (PPPoA), or Point-to-Point Protocol over Ethernet (PPPoE).
By default, VMAC is disabled.
Run the pitp command to configure the PITP function to authenticate a user account
bound to an access port.
l Enabling or disabling a protocol
This feature enables or disables a protocol or some functions of the protocol.
Run the dhcp mode command to switch between the DHCP Layer 2 forwarding mode
and the Layer 3 forwarding mode.
Run the dhcp option82 command to configure the DHCP option 82 feature.
Run the dhcpv6 command to configure the DHCPv6 option 82 feature.
Issue 02 (2013-10-08)

80

Configuration Guide
NOTE
The CCUC and CCUE control boards support DHCPv6 function and the CCUB control board does
not support this function.
Run the dhcp proxy command to configure the DHCP proxy function. After the DHCP
proxy function is enabled, the server ID proxy function and lease time proxy function
will be enabled.
l Transparent transmission
This feature allows a specified type of protocol packet to be transmitted without being
processed during network interconnection.
Run the bpdu tunnel command to configure the bridge protocol data unit (BPDU)
transparent transmission function. After this function is enabled, the Layer 2 BPDUs of
a private network can be transparently transmitted over a public network.
Run the rip tunnel command to configure the Routing Information Protocol (RIP) Layer
2 transparent transmission function. After this function is enabled, RIP packets can be
transparently transmitted at Layer 2 based on the VLAN on the MA5616 on which no
RIP protocol is running.
Run the ospf tunnel command to configure the Open Shortest Path First (OSPF) Layer
2 transparent transmission function. After this function is enabled, OSPF packets can be
transparently transmitted at Layer 2 based on the VLAN on the MA5616 on which no
OSPF protocol is running.
Run the vtp-cdp tunnel command to configure the VTP/CDP packet transparent
transmission function. After this function is enabled, VTP/CDP packets are transparently
transmitted based on the VLAN. VTP is the acronym for VLAN Trunk Protocol. CDP is
the acronym for Cisco Discovery Protocol.
Step 3 Commit and save the configuration of the VLAN service profile.
Run the commit command to commit the current parameter configuration of the VLAN service
profile. After the configuration is complete, run the commit command to make the configuration
take effect.
Step 4 Bind the VLAN service profile to a VLAN.
Run the vlan bind service-profile command to bind the configured VLAN service profile to a
specified VLAN.
----End
Example
Assume that the profile parameters are planned as follows:
l
VLAN forwarding mode: VLAN+MAC address (vlan-mac)
BPDU transparent transmission: enabled
Unknown multicast packet: discarded
Other parameters use the default values. To add VLAN service profile 3 and bind it to VLAN
100, do as follows:
huawei(config-vlan-srvprof-3)#forwarding vlan-mac
huawei(config-vlan-srvprof-3)#bpdu tunnel enable
huawei(config-vlan-srvprof-3)#packet-policy multicast discard
Issue 02 (2013-10-08)

81

Configuration Guide
3.6 Configuring Basic IPv6 Information

This topic describes the IPv6 features supported by the MA5616. The basic IPv6 configuration
includes configuration of the IPv6 address, IPv6 neighbor, and path maximum transmission unit
(PMTU).
Context
Internet Protocol Version 6 (IPv6), also called IP next generation (IPNG), is the secondgeneration standard protocol of network layer protocols. As a set of specifications defined by
the Internet Engineering Task Force (IETF), IPv6 is the upgraded version of Internet Protocol
Version 4 (IPv4). The most obvious difference between IPv6 and IPv4 is that IP addresses are
lengthened from 32 bits to 128 bits. IPv6 radically solves the problem of IP address shortage.
Moreover, IPv6 has the following advantages: It is easy to deploy, compatible with various
applications, easy for IPv4 networks to transit to IPv6 networks, and coexists and interworks
with IPv4 networks.
NOTE
The CCUC and CCUE board supports the IPv6 function. The CCUB board does not support the IPv6
function.
The following table lists the IPv6 features supported by the MA5616.
Table 3-14 IPv6 features supported by the MA5616
Feature
Sub-feature
Configuration Process or
Command
IPv6 address
management
and assignment
Static configuration of IPv6 global

unicast addresses and IPv6 linklocal addresses
Configuring an IPv6 Address for

an Interface
Automatic configuration of IPv6

link-local addresses
ipv6 address auto link-local
DHCPv6 L2 Relay
Configuring Anti-Theft and

Roaming of User Accounts
Through DHCP
Management information base

(MIB) for IPv6 address
management
IPv6/IPv4 dual-stack to ensure

compatibility of IPv6 and IPv4
Basic IPv6 protocols, including

ICMPv6, TCP6, UDP6, and
RawIP6
IPv6 stack and

IPv6 host
function
Issue 02 (2013-10-08)

82

Configuration Guide
Feature
Sub-feature
Configuration Process or
Command
IPv6 Neighbor Discovery (ND)

protocol and static configuration
of IPv6 neighbors
Configuring IPv6 Neighbor

Discovery
IPv6 PMTU
Configuring PMTU
IPv6 ping and tracert
l ping ipv6
l tracert ipv6
IPv6 statistics query and clearance
l display ipv6 statistics

l reset ipv6 statistics
IPv6 route
IPv6 static routes
Configuring an IPv6 Static Route
IPv6 QoS and

security
IPv6 ACL
Configuring ACL
Anti-MAC spoofing
Configuring Anti-MAC Spoofing
Anti-IPv6 spoofing
Configuring Anti-IP Spoofing
Anti-denial of service (DoS) attack
Configuring Anti-Attack
Differentiation of service virtual

ports based on the IPv6 over
Ethernet (IPv6oE) type (0x86DD)
and defining of VLANs for service
virtual ports
service-port
Transparent transmission of IPv6

over PPPoE packets
VLAN-based transparent
transmission of IPv6 packets
IPv6 Layer 2
Transparent
Transmission
NOTE
In this manual:
l For the IPv6 features that are different from IPv4 features, configuration procedures and examples are
provided for both IPv6 and IPv4 features.
l For the IPv6 features that are similar with IPv4 features, configuration procedures and examples are
not provided for IPv6 features because they are the same as IPv4 features. To configure these IPv6
features, use IPv6 commands and follow the procedures of IPv4 features.
3.6.1 Configuring an IPv6 Address for an Interface

The MA5616 can communicate with other IPv6 equipment after its interface is configured with
an IPv6 address. Before an IPv6 global unicast address or IPv6 link-local address is configured
on an interface, the IPv6 packet forwarding function must be enabled on the device.
Issue 02 (2013-10-08)

83

Configuration Guide
Context
Each interface can be configured with a maximum of ten global unicast addresses and only one
link-local address.
l
The global unicast address is equivalent to the IPv4 public address. It is used for data
forwarding across the public network, which is necessary for the communication between
users. An EUI-64 address has the same function as a global unicast address. The difference
is that only the network bits need to be specified for the EUI-64 address and the host bits
are transformed from the media access control (MAC) addresses of the interface while a
complete 128-bit address needs to be specified for the global unicast address.
The link-local address is used in neighbor discovery (ND), and in the communication
between nodes on the local link in the stateless address auto-configuration. The packets
using the link-local address as the source or destination address are not forwarded to other
links.
The link-local address can be automatically generated or manually configured. It is
recommended to automatically generate a link-local address because the link-local address
is used to implement communication requirements of protocol and is not directly related
to the communication between users.
NOTE
In stateless address auto configuration, a host uses the prefix information and local interface ID
obtained from the router advertisement (RA) received to automatically generate an IPv6 address.
Instead, the host does not use stateful (DHCPv6) address configuration.
The MA5616 supports IPv6 address configuration on the virtual local area network (VLAN)
interface, MEth interface, and loopback interface. This topic uses the VLAN interface as an
example.
Procedure
Step 1 Enable IPv6 packet forwarding capability.
Enabling the IPv6 function of the device and the interface is a prerequisite for configuring IPv6
features. To enable a device to forward IPv6 packets, you must enable the IPv6 capability in
both the global config mode and the interface mode.
By default, the IPv6 function on the device and interface is disabled.
1.
In global config mode, run the ipv6 command to enable the IPv6 packet forwarding
capability.
2.
Run the interface vlanif command to enter the VLANIF mode.
3.
In VLANIF mode, run the ipv6 enable command to enable the IPv6 function on the
interface.
NOTE
Before configuring other IPv6 features on an interface, enable the IPv6 function in interface mode.
Step 2 Configure an IPv6 global unicast address for an interface.

In VLANIF mode, run the ipv6 address or ipv6 address eui-64 command to configure an IPv6
global unicast address on the interface.
Issue 02 (2013-10-08)

84

Configuration Guide
The EUI-64 address and the global unicast address can be configured simultaneously or
alternatively. However, the IPv6 addresses configured for one interface cannot be in the same
network segment.
Step 3 Configure an IPv6 link-Local address for an interface.
In VLAN interface mode, run the following commands based on the requirements:
l Run the ipv6 address auto link-local command to automatically generate a local-link
address of an interface.
After this command is executed, the deletion of the global unicast address does not affect
local link communication. If the device only needs to communicate with another device that
is directly connected to the device, using the link-local address saves global unicast address
resources.
l Run the ipv6 address link-local command to manually configure a link-local address of an
interface. The prefix of the IPv6 address configured by running this command must be
FE80::/10.
After this command is executed, the original link-local address is replaced by the new linklocal address. If possible, do not change the link-local address.
In addition to configuring a link-local address through the preceding two commands, you can
also configure an IPv6 global unicast address for automatically generating a link-local address.
Step 4 Query the address configuration information about an IPv6 interface.
l Run the display ipv6 interface command to query the IPv6 interface information.
l Run the display ipv6 statistics command to query the IPv6 packet statistics.
----End
Example
To create VLAN 10, set the IPv6 address of VLAN interface 10 to 2000::1/64, and configure
automatic configuration of a link-local address, run the following commands:
huawei(config)#vlan 10
huawei(config)#ipv6
huawei(config)#interface vlanif
huawei(config-if-vlanif10)#ipv6
10
enable
address 2000::1 64
address auto link-local
3.6.2 Configuring an IPv6 Address Selection Policy Table

If multiple IPv6 addresses are configured on an interface of the device, the IPv6 address selection
policy table can be used to select source and destination addresses for packets.
Context
IPv6 addresses can be classified into different types based on different applications.
l
Link local addresses and global unicast addresses based on the effective range of the IPv6
addresses
Temporary addresses and public addresses based on security levels
Issue 02 (2013-10-08)

85

Configuration Guide
Home addresses and care-of addresses based on the application in the mobile IPv6 field
Physical interface addresses and logical interface addresses based on the interface attributes
The preceding IPv6 addresses can be configured on the same interface of the equipment. In this
case, the device must select a source address or a destination addresses from multiple addresses
on the interface. If the device supports the IPv4/IPv6 dual-stack, it also must select IPv4
addresses or IPv6 addresses for communication. For example, if a domain name maps both an
IPv4 address and an IPv6 address, the system must select an address to respond to the domain
name server (DNS) request of the client.
An IPv6 address selection policy table solves the preceding problems. It defines a group of
address selection rules. The source and destination addresses of packets can be specified or
planned based on these rules. This table, similar to a routing table, can be queried by using the
longest matching rule. The address is selected based on the source and destination addresses.
l
The label parameter can be used to determine the result of source address selection. The
address whose label value is the same as the label value of the destination address is selected
preferably as the source address.
The destination address is selected based on both the label and the precedence parameters.
If label values of the candidate addresses are the same, the address whose precedence value
is largest is selected preferably as the destination address.
Procedure
Step 1 In global config mode, run the ipv6 address-policy command to configure the source and
destination address selection policy.
By default, only default address selection policy entries are contained. These entries are prefixed
with ::1, ::, 2002::, FC00::, and ::FFFF:0.0.0.0.
A maximum of 50 address selection policy entries are supported by the system.
Step 2 Query the IPv6 address selection policy.
Run the display ipv6 address-policy command to query the IPv6 address selection policy.
----End
Example
To create the IPv6 address selection policy for the IPv6 address 3::/64, set the precedence to 3,
and set the label to 2, run the following commands:
huawei(config)#ipv6 address-policy 3:: 64 3 2
huawei(config)#display ipv6 address-policy all
Policy Table :
Total:6
------------------------------------------------------------------------------Prefix
: ::
PrefixLength : 0
Precedence : 40
Label
: 1
Default
: Yes
Issue 02 (2013-10-08)
Prefix
: ::1
Precedence : 50
Default
: Yes
PrefixLength
Label
: 128
: 0
Prefix
: ::FFFF:0.0.0.0
Precedence : 10
PrefixLength
Label
: 96
: 4

86

Configuration Guide
Default
: Yes
Prefix
: 3::
Precedence : 3
Default
: No
PrefixLength
Label
: 64
: 2
Prefix
: 2002::
Precedence : 30
Default
: Yes
PrefixLength
Label
: 16
: 2
Prefix
: FC00::
Precedence : 20
Default
: Yes
PrefixLength
Label
: 7
: 3
-------------------------------------------------------------------------------
3.6.3 Configuring IPv6 Neighbor Discovery

IPv6 neighbor discovery (ND) is a packet transmission process to identify the relationship
between neighboring nodes. The Neighbor Discovery Protocol (NDP) is similar to the Address
Resolution Protocol (ARP), Internet Control Message Protocol (ICMP) router Discovery
messages, and ICMP redirect messages, and introduces neighbor reachability detection.
Prerequisite
The IPv6 address must be configured. For details, see Configuring an IPv6 Address for an
Interface.
Context
Most of the ND configurations are implemented based on the interfaces. The MA5616 supports
ND configurations on VLAN Layer 3 interfaces.
NOTE
For details about ND, see Neighbor Discovery in the Feature Description.
Procedure
l
Configure the static neighbors.

By configuring a static neighbor, you can obtain the mapping of the IPv6 address and media
access control (MAC) address of the neighbor. The statically configured neighbor entries
will overwrite the dynamically learned neighbor entries and they will not age.
1.
In global config mode, run the interface vlanif command to enter the VLAN interface
mode.
2.
In VLAN interface mode, run the ipv6 neighbor command to configure a static IPv6
neighbor.
Configure the parameters of router advertisement (RA) messages.

The device periodically sends router advertisement messages containing information such
as address prefixes, maximum number of hops, neighbor hold time, and keep-alive time.
The IPv6 node on the local link receives RA messages and updates information such as the
IPv6 prefix list and other information from the RA messages.
Issue 02 (2013-10-08)

87

Configuration Guide
1.
In global config mode, run the interface vlanif command to enter the VLAN interface
mode.
2.
Run the undo ipv6 nd ra halt command to enable RA message advertising.

When a device is connected to an IPv6 node, the RA message advertising function
needs to be enabled so that the device periodically sends RA messages to the IPv6
node.
When a device is not connected to an IPv6 node, the RA message advertising
function does not need to be enabled. By default, this function is disabled.
By default, RA message advertising is disabled on the devices.
3.
(Optional) Configure parameters carried in an RA message.

Select the following desired operations:
Run the ipv6 nd ra command to configure the interval for advertising RA
messages.
By default, the maximum interval is 600 seconds and the minimum interval is 200
seconds. The maximum interval cannot be shorter than the minimum interval.
When the maximum interval is less than 9 seconds, the minimum interval is set to
the same value as the maximum interval.
Run the ipv6 nd ra router-lifetime command to configure the lifetime of RA
messages.
By default, the lifetime is 1800 seconds. The lifetime of the messages advertised
by the device must be longer than or equal to the interval for the device to advertise
messages.
Run the ipv6 nd ra prefix command to configure the address prefixes to be
advertised in RA messages.
By default, RA messages contain only the address prefixes specified through the
ipv6 address command. Run this command when the device advertises only the
specified prefixes.
Configure the default router priority and route information in RA messages.
RA messages that carry the default router priority and route information can be
transmitted over the local link. In this manner, a proper device can be selected to
forward messages of a host.
Run the ipv6 nd ra preference command to configure the default router
priority in RA messages.
Run the ipv6 nd ra route-information command to configure the route
information in RA messages.
Set the flag bit for stateful auto configuration in RA messages.
Run the ipv6 nd autoconfig managed-address-flag command to set the flag
bit for stateful auto configuration addresses in RA messages.
If this flag is set, hosts use the stateful protocol for address auto-configuration
in addition to any automatically configured addresses using stateless address
auto-configuration.
Run the ipv6 nd autoconfig other-flag command to set the flag bit for other
stateful configurations.
Issue 02 (2013-10-08)

88

Configuration Guide
When this flag is set, hosts use the stateful protocol for auto-configuration of
other (non-address) information.
Run the ipv6 nd ns retrans-timer command to configure the interval for detecting
neighbor reachability in RA messages, that is, re-transmission timer of neighbor
solicitation (NS) messages.
Frequently sending NS packets helps to determine whether the neighbor is
reachable but affects the device performance. Therefore, you are recommended to
set the interval for sending NS messages to a greater value. The default interval,
1000 milliseconds, is recommended.
Run the ipv6 nd nud reachable-time command to configure the neighbor
reachable time in RA messages.
NUD is short for neighbor unreachability detection. A smaller neighbor reachable
time set on a device indicates that the device can probe the neighbor reachability
more quickly but more network bandwidth and CPU resources are occupied.
Therefore, you are recommended to set the interval for sending NS messages to a
greater value. The default interval, 30000 milliseconds, is recommended.
Configure the maximum number of hops for the route device.
Run the quit command to quit the VLANIF mode. In global config mode, run the
ipv6 nd hop-limit command to configure the maximum number of hops for the
route device, that is, the maximum number of hops for the IPv6 unicast packets
initiated by the host. The value for the maximum number of hops for the route
device is the same as that for the maximum number of hops in the RA messages.
The default value is 64.
l
Configure duplicate address detection (DAD).

DAD is used to check whether an IPv6 address is available. When a node is configured
with an IPv6 address, it immediately sends an NS message to check whether this address
is used by other neighboring nodes.
1.
In the global config mode, run the interface vlanif command to enter the VLANIF
mode.
2.
Run the ipv6 nd dad attempts to configure the number of DAD attempts, that is,
number of attempts to send neighbor request messages. The default value is 1.
3.
Run the ipv6 nd ns retrans-timer command to configure the interval of DAD, that
is, re-transmission timer of neighbor solicitation (NS) messages. The default interval,
1000 milliseconds, is recommended.
Query the IPv6 neighbor information.

Run the display ipv6 neighbors command to query the IPv6 neighbor information.
Run the display ipv6 interface command to query the IPv6 interface information.
Run the display ipv6 prefix command to query the IPv6 prefixes in the RA message
sent from the IPv6 interface.
Run the display ipv6 route-information command to query the route information in
the RA message sent from the IPv6 interface.
----End
Example
To configure the function of automatically generating a link-local unicast address on VLAN
interface 10, set the local unicast address of site EUI-64 and the prefix to be advertised by the
Issue 02 (2013-10-08)

89

Configuration Guide
RA message to 3000::/64, set the valid lifetime and preferred lifetime of the prefix to 1000s, and
enable RA message advertising, run the following commands:
huawei(config)#ipv6
huawei(config)#interface vlanif
huawei(config-if-vlanif10)#undo
10
enable
address auto link-local
address 3000::/64 eui-64
nd ra prefix 3000::/64 1000 1000
ipv6 nd ra halt
3.6.4 Configuring PMTU

By setting the path maximum transmission unit (PMTU), you can select a proper maximum
transmission unit (MTU) for packet transmission. In this manner, packets do not have to be
fragmented during transmission and loads on intermediate devices are reduced. In addition,
network resources are used more efficiently and the network throughput reaches the optimal
value.
Context
Dynamic PMTU values can be set on a device by default, ensuring the smallest value of MTU
values is used on all interfaces along the source to the destination nodes. Configuring a static
PMTU sets the maximum length of a packet that can be sent from the source end to the destination
end. This prevents attacks initiated by sending jumbo packets. When both static PMTUs and
dynamic PMTUs are configured, only static PMTUs take effect. In other words, the priority of
static PMTUs is higher than the priority of the dynamic PMTUs.
Procedure
Step 1 Configure a static PMTU.
In the global mode, run the ipv6 pathmtu command to configure a static PMTU for the path
destined for the specified IPv6 address. By default, the PMTU of the path destined for an IPv6
address is 1500 bytes.
Generally, the static PMTU value is smaller than or equal to the MTU value of all interfaces on
the same path. If the static PMTU value is larger than the MTU value of the interfaces, the system
segments packets according to the MTU value. If the static PMTU value is manually configured
based on the smallest MTU value of the patch that packets are transmitted, the packets will be
transmitted at a higher rate.
Step 2 Configure the aging time of dynamic PMTU entries.
Run the ipv6 pathmtu age command to configure the aging time of dynamic PMTU entries. By
default, the aging time of dynamic PMTU entries is 10 minutes.
The ipv6 pathmtu age command is used to change the life cycle of the dynamic PMTU entries
in the buffer. It is invalid for static PMTU entries, because static PMTU entries do not age.
Step 3 Query the PMTU information.
l Run the display ipv6 pathmtu command to query the PMTU information.
l Run the display ipv6 interface command to query the MTU value of the IPv6 interface.
----End
Issue 02 (2013-10-08)

90

Configuration Guide
Example
To set the PMTU for the IPv6 address 3001::1 to 1300 bytes, and to set the aging time of the
dynamic PMTU entries to 40 minute, run the following commands.
huawei(config)#ipv6 pathmtu 3001::1 1300
huawei(config)#ipv6 pathmtu age 40
3.7 Configuring a Route

This topic describes how to configure Internet Protocol version 4 (IPv4) or Internet Protocol
version 6 (IPv6) routes on the MA5616.
3.7.1 Configuring an IPv4 Static Route

This topic describes how to manually configure an Internet Protocol version 4 (IPv4) static route
for the communication between the MA5616 and devices that are in different network segments.
Context
l
When a network structure is simple, you can configure static routes for communication
between devices at Layer 3.
When a network changes or is faulty, you must manually modify or delete the static route.
Procedure
Step 1 Configure an IPv4 static route.
Run the ip route-static ip-addr { mask-ip-addr | mask-length } gateway-addr command to
configure the IPv4 static route on the MA5616.
Parameters in the preceding command are described as follows:
l ip-addr: indicates the destination IP address or network of the route.
l mask-ip-addr | mask-length: indicates the subnet mask and mask length of the destination IP
address. This parameter and the destination IP address identify the network segment address
of the peer device.
l gateway-addr: indicates the next-hop IP address of the route, which means the gateway IP
address.
Step 2 Verify that the route is successfully configured.
Run the display ip routing-table command to query the IPv4 route table to obtain information
about the configured static route. To verify the connectivity between the MA5616 and the
destination IP address, run the ping or tracert command.
----End
Example
Assume that the destination IP address is 10.10.10.0, the subnet mask is 255.255.255.0, and the
next-hop IP address is 10.144.78.1. To configure the IPv4 static route on the MA5616, run the
following command:
Issue 02 (2013-10-08)

91

Configuration Guide
huawei(config)#ip route-static 10.10.10.0 255.255.255.0 10.144.78.1

huawei(config)#display ip routing-table
Route Flags: R - relay, D - download to fib
-----------------------------------------------------------------------------Routing Tables: Public
Destinations : 7
Routes : 7
Destination/Mask
Proto
Pre
Cost
10.10.10.0/24 Static 60
0
10.71.0.0/16 Static 60
0
10.144.78.0/23 Direct 0
0
10.144.79.9/32 Direct 0
0
10.144.120.0/24 Static 60
0
127.0.0.0/8
Direct 0
0
127.0.0.1/32 Direct 0
0
huawei(config)#ping 10.10.10.10
PING 10.10.10.10: 56 data bytes,
Reply from 10.10.10.10: bytes=56
Flags NextHop
RD
RD
D
D
RD
D
D
Interface
10.144.78.1
10.144.78.1
10.144.79.9
127.0.0.1
10.144.78.1
127.0.0.1
127.0.0.1
press CTRL_C to break

Sequence=1 ttl=127 time
=
=
=
=
=
meth0
meth0
meth0
meth0
meth0
InLoopBack0
InLoopBack0
1
1
1
1
1
ms
ms
ms
ms
ms
--- 10.10.10.10 Ping statistics --5 packets transmitted

5 packets received
0.00% packet loss
Round-trip min/avg/max = 1/1/1 ms
3.7.2 Configuring an IPv6 Static Route

This topic describes how to manually configure an Internet Protocol version 6 (IPv6) static route
for the communication between the MA5616 and devices that are in different network segments.
Prerequisites
The IPv6 function has been enabled globally and in port mode. You can run the ipv6 command
to enable the IPv6 function globally, and the ipv6 enable command to enable the IPv6 function
in port mode.
Context
l
When a network structure is simple, you can configure static routes for communication
between devices at Layer 3.
When a network changes or is faulty, you must manually modify or delete the static route.
An IPv6 address contains 128 bits. For details, see the Usage Guidelines for the ipv6
address command.
NOTE
The CCUC/CCUE control board supports the IPv6 function, and the CCUB control board does not support the
IPv6 function.
Procedure
Step 1 Configure an IPv6 static route.
Run the ipv6 route-static dest-ipv6-address prefix-length nexthop-ipv6-address command to
configure the IPv6 static route on the MA5616.
Issue 02 (2013-10-08)

92

Configuration Guide
Parameters in the preceding command are described as follows:

l dest-ipv6-address: indicates the destination IP address or network of the route.
l prefix-length: indicates the IPv6 prefix length. This parameter and the destination IP address
identify the network segment address of the peer device.
l nexthop-ipv6-address: indicates the next-hop IP address of the route, which means the
gateway IP address.
Step 2 Verify that the route is successfully configured.
Run the display ipv6 routing-table verbose command to query the IPv6 route table to obtain
information about static routes (activated or deactivated). To verify the connectivity between
the MA5616 and the destination IP address, run the ping ipv6 or tracert ipv6 command.
----End
Example
Assume that the destination IP address is 3001::0, the subnet prefix length is 64, and the nexthop IP address is 2001::1. To configure the IPv6 static route on the MA5616, run the following
command:
huawei(config)#ipv6 route-static 3001::0 64 2001::1
huawei(config)#display ipv6 routing-table
{ <cr>|acl<K>|protocol<K>|statistics<K>|verbose<K>|x:x::x:x<IPV6><X:X::X:X>||<K>
}:
Command:
display ipv6 routing-table
Routing Table : Public
Destinations : 5
Routes : 5
Destination
NextHop
Cost
RelayNextHop
Interface
:
:
:
:
:
::1
::1
0
::
InLoopBack0
PrefixLength
Preference
Protocol
TunnelID
Flags
:
:
:
:
:
128
0
Direct
0x0
D
Destination
NextHop
Cost
RelayNextHop
Interface
:
:
:
:
:
2001::
2001::2001
0
::
vlanif100
PrefixLength
Preference
Protocol
TunnelID
Flags
:
:
:
:
:
64
0
Direct
0x0
D
Destination
NextHop
Cost
RelayNextHop
Interface
:
:
:
:
:
2001::2001
::1
0
::
vlanif100
PrefixLength
Preference
Protocol
TunnelID
Flags
:
:
:
:
:
128
0
Direct
0x0
D
Destination
NextHop
Cost
RelayNextHop
Interface
:
:
:
:
:
3001::
2001::1
0
::
vlanif100
PrefixLength
Preference
Protocol
TunnelID
Flags
:
:
:
:
:
64
60
Static
0x0
RD
PrefixLength :
Preference
:
Protocol
:
TunnelID
:
Flags
:
-tc 1 3001::1
10
0
Direct
0x0
D
Destination : FE80::
NextHop
: ::
Cost
: 0
RelayNextHop : ::
Interface
: null0
huawei(config)#ping ipv6 -c 3 -m 10 -s 88 -t 20
{ <cr>|-i<K> }:
Issue 02 (2013-10-08)

93

Configuration Guide
Command:
ping ipv6 -c 3 -m 10 -s 88 -t 20 -tc 1 3001::1
PING 3001::1 : 88 data bytes, press CTRL_C to break
Reply from 3001::1
Bytes=88 Sequence=1 Hop limit=64 Time=10 ms
Reply from 3001::1
Reply from 3001::1
--- 3001::1 ping statistics --3 packet(s) transmitted
3 packet(s) received
0.00% packet loss
round-trip min/avg/max = 10/10/10 ms
3.8 Configuring the System Clock

This topic describes how to configure the system clock to restrict the clock frequency and phase
of each node on a network within the preset tolerance scope. This prevents the deterioration of
the TDM service quality caused by inaccurate signal timing at both the transmit and receive ends
in the digital transmission system.
Context
l
The IP-based development is the trend of future network and service development.
Currently, certain difficulties exist in the transition of the access network (AN) from the
traditional network to the IP-based Ethernet bearer network. One of the difficulties is how
to carry the traditional TDM service on the IP network.
On the traditional telecommunications network, the TDM service carried on the AN is

mainly the voice service. Cumulative inconsistency between the clocks at both ends of the
bearer network over a long time causes frame slip, which reduces the quality of the voice
service. Moreover, the wireless application has more rigorous requirements on the clock
frequency. The frequencies of different base stations must be synchronized within a
specified precision. Otherwise, offline problems occur during base station switching.
Therefore, clock synchronization is very important in the TDM voice service.
3.8.1 Configuring the Reference Source of the System Clock

This topic describes how to configure the clock reference sources so that the system clock can
select a reference source when needed.
Context
l
To ensure that the MA5616 and other devices on a network use the unified time, the clock
signals of a certain port must be specified as the reference source of the system clock. The
system clock is also used as the system output clock.
The system supports a maximum of ten clock reference sources. The system selects a
reference source according to the priority level of each reference source.
The reference sources of the system clock include the , adaptive clock, and line clock.
The adaptive clock restores a clock from the PHS service at the upper layer as the
reference source of the system clock.
Issue 02 (2013-10-08)

94

Configuration Guide
The line clocks supported by the system include the GE line clock, GPON line clock.
That is, the system receives a line clock transferred by the upper-layer device through
the GPON/GE uplink interface, and restores the line clock as the reference source of
the system clock, thus implementing clock synchronization with the upper-layer device.
Configuring the Adaptive Clock Reference Source

The In the PHS service, the UA5000 sends a unidirectional E1 clock packet to the MA5616.
The MA5616 can use the clock in the packet as the clock reference source.
Procedure
Step 1 Run the vlan command to create the VLAN for carrying clock packets.
Step 2 Run the ip address command to set the IP address of the Layer 3 VLAN.
Step 3 Run the port vlan command to add an uplink port to the VLAN.
Step 4 Run the acm-clock-ip command to set the IP address of the Layer 3 interface for receiving
adaptive clock method (ACM) clock packets.
Step 5 Run the clock source command to set the ACM clock as the clock source of the system.
----End
Example
To configure system clock resource 0 for receiving ACM clock packets from Layer 3 interface
whose IP address is 20.20.20.20 (assume that the subnet mask length is 24), run the following
commands:
huawei(config-if-vlanif14)#ip address 20.20.20.20 24
huawei(config)#acm-clock-ip 20.20.20.20 0/2
huawei(config)#clock source 0 acm-clock 0/2/
Configuring the Line Clock Reference Source

The MA5616 supports tracing of the uplink GE, GPON line clock. The clock synchronized
through the physical layer and restored from the line code stream can serve as the reference
source of the system clock.
Context
The MA5616 supports the GE, GPON line clocks as the reference sources of the system clock.
Procedure
Step 1 Run the clock source srcindex frameid/slotid/portid command to configure the clock restored
at a certain GE, GPON port as the reference source of the system clock.
Issue 02 (2013-10-08)

95

Configuration Guide
Step 2 Run the display clock source command to check whether the line clock source information is
consistent with the data plan.
----End
Example
To configure clock source 0, set the reference source to the GPON line clock, and set the
reference source port to 0/0/1, do as follows:
huawei(config)#clock source 0 0/0/1
Clock source set succeeded
huawei(config)#clock priority system 0
Clock source priority set succeeded
huawei(config)#display clock source
------------------------------------------------------------------------Index Config
Type
Source
State
Priority
Output
------------------------------------------------------------------------0
YES
line
0/ 0/ 1
Failed
0
--1
NO
--/ -/ ------2
NO
--/ -/ ------3
NO
--/ -/ ------4
NO
--/ -/ ------5
NO
--/ -/ ------6
NO
--/ -/ ------7
NO
--/ -/ ------8
NO
--/ -/ ------9
NO
--/ -/ ------------------------------------------------------------------------------The current system clock source: local , index: 255
3.8.2 Configuring the Priority of the System Clock

This topic describes how to configure the priority for the clock reference source of the system.
The MA5616 selects the system clock according to the configured clock priorities.
Prerequisites
The system clock reference source must be configured.
Context
l
The added system clock source can be used in the system only after it is configured with a
priority.
The priority of the clock source takes effect immediately after it is configured. This
operation, however, may cause the clock switching in the system.
The system does not determine the quality of the clock source. Therefore, you need to
configure the clock reference source of high quality with a high priority.
Run the clock priority command to configure the priority of the clock source.
Procedure
The system supports 10 priorities for the clock reference source. The priorities are
represented in the form of p0/p1/p2/p3/p4/p5/p6/p7/p8/p9, in which p0 indicates the highest
priority and p9 indicates the lowest priority. For example, if p0-p9 is set to 3/7/8, it indicates
that the priority of the clock reference source with index 3 is the highest, the priority of the
Issue 02 (2013-10-08)

96

Configuration Guide
reference source with index 7 is lower, and the priority of the reference source with index
of 8 is the lowest.
----End
Example
To configure the priority of clock reference source 0 to the highest priority and the priority of
clock reference source 1 to the second highest priority, do as follows:
huawei(config)#clock priority system 0/1
Clock source priority set succeeded
3.9 Configuring the NTP Time

Configuring the NTP protocol to keep the time of all devices in the network synchronized, so
that the Context implement various service applications based on universal time, such as the
network management system and the network accounting system.
Context
Introduction to the NTP Protocol:
l
The Network Time Protocol (NTP) is an application layer protocol defined in RFC 1305,
which is used to synchronize the times of the distributed time server and the client. The
RFC defines the structures, arithmetics, entities and protocols used in the implementation
of NTP.
NTP is developed from the time protocol and the ICMP timestamp message protocol, with
special design on the aspects of accuracy and robustness.
NTP runs over UDP with port number as 123.
Any local system that runs NTP can be time synchronized by other clock sources, and also
act as a clock source to synchronize other clocks. In addition, mutual synchronization can
be done through NTP packets exchanges.
NTP is applied to the following situations where all the clocks of hosts or routers in a network
need to be consistent:
l
In the network management, an analysis of log or debugging information collected from

different routers needs time for reference.
The charging system requires the clocks of all devices to be consistent.
Completing certain functions, for example, timing restart of all the routers in a network
requires the clocks of all the routers be consistent.
When several systems work together on the same complicate event, they have to take the
same clock for reference to ensure correct implementation order.
Incremental backup between the backup server and clients requires clocks on them be
synchronized.
When all the devices on a network need to be synchronized, it is almost impossible for an
administrator to manually change the system clock by command line. This is because the work
load is heavy and clock accuracy cannot be ensured. NTP can quickly synchronize the clocks
of network devices and ensure their precision.
Issue 02 (2013-10-08)

97

Configuration Guide
There are four NTP modes: broadcast mode, multicast mode, unicast server mode, and peer
mode. The MA5616 supports all these modes.
Table 3-15 provides the default configuration for NTP.
Table 3-15 Default configuration for NTP
Parameter
Default Value
NTP-service authentication
function
Disable
NTP-service authentication
key
None
The maximum allowed

number of sessions
100
Clock stratum
16
3.9.1 (Optional) Configuring NTP Authentication

This topic describes how to configure NTP authentication. After NTP authentication is
configured, the function can be enabled in the network that has high requirements on security
to improve the network security and prevent unauthorized users from modifying the clock.
Prerequisites
Before configuring the NTP authentication, make sure that the network interface and the routing
protocol of the MA5616 are configured so that the server and the client are reachable to each
other at the network layer.
Context
In certain networks that have strict requirements on security, enable NTP authentication when
running the NTP protocol. Configuring NTP authentication is classified into configuring NTP
authentication on the client and configuring NTP authentication on the server.
Precaution
l
If NTP authentication is not enabled on the client, the client can synchronize with the server,
regardless of whether NTP authentication is enabled on the server.
If NTP authentication is enabled, a reliable key should be configured.
The configuration of the server must be the same as that of the client.
When NTP authentication is enabled on the client, the client can pass the authentication if
the server is configured with the same key as that of the client. In this case, you need not
enable NTP authentication on the server or declare that the key is reliable.
Issue 02 (2013-10-08)

98

Configuration Guide
The client synchronizes with only the server that provides the reliable key. If the key
provided by the server is unreliable, the client does not synchronize with the server.
The flow of configuring NTP authentication is as follows: start->enable NTP

authentication->configure the reliable NTP authentication key->declare the reliable key>end.
Procedure
Step 1 Run the ntp-service authentication enable command to enable NTP authentication.
Step 2 Run the ntp-service authentication-keyid command to set an NTP authentication key.
Step 3 Run the ntp-service reliable authentication-keyid command to declare that the key is reliable.
----End
Example
To enable NTP authentication, set the NTP authentication key as aNiceKey with the key number
42, and then define key 42 as a reliable key, do as follows:
huawei(config)#ntp-service authentication enable
huawei(config)#ntp-service authentication-keyid 42 authentication-mode md5
aNiceKey
huawei(config)#ntp-service reliable authentication-keyid 42
3.9.2 Configuring the NTP Broadcast Mode

This topic describes how to configure the MA5616 for clock synchronization in the NTP
broadcast mode. After the configuration is complete, the server periodically broadcasts clock
synchronization packets through a specified port, and functions as a client to snoop on the
broadcast packets sent from the server and synchronizes the local clock according to the received
broadcast packets.
Prerequisites
Before configuring the NTP broadcast mode, make sure that the network interface and the routing
Context
In the broadcast mode, the server periodically sends clock synchronization packets to the
broadcast address 255.255.255.255, with the Mode field set to 5 (indicating the broadcast mode).
The client snoops on the broadcast packets sent from the server. After receiving the first
broadcast packet, the client exchanges NTP packet whose interaction mode fields are set to 3
(on the client) and 4 (on the server) with the server to obtain the network delay between the
client and the server. The client then enters the broadcast client mode, continues to snoop on the
incoming broadcast packets, and synchronizes the local clock according to the incoming
broadcast packets, as shown in Figure 3-39.
Issue 02 (2013-10-08)

99

Configuration Guide
Figure 3-39 NTP broadcast mode
Precaution
1.
In the broadcast mode, you need to configure both the NTP server and the NTP client.
2.
The clock stratum of the synchronizing device must be smaller than or equal to that of the
synchronized device. Otherwise, the clock synchronization fails.
Configure the NTP broadcast client host.
Procedure
1.
(Optional) Configure NTP authentication.

In certain networks that have strict requirements on security, it is recommended that
you enable NTP authentication when running the NTP protocol. The configuration of
the server must be the same as that of the client.
2.
Issue 02 (2013-10-08)
a.
Run the ntp-service authentication enable command to enable NTP

authentication.
b.
Run the ntp-service authentication-keyid command to set an NTP

authentication key.
c.
Run the ntp-service reliable authentication-keyid command to declare that the

key is reliable.
Add a VLAN L3 interface.

a.
b.
Run the port vlan command to add an upstream port to the VLAN so that the
user packets carrying the VLAN tag are transmitted upstream through the
upstream port.
c.
In the global config mode, run the interface vlanif command to create a VLAN
interface, and then enter the VLAN interface mode to configure the L3 interface.
d.
Run the ip address command to configure the IP address and subnet mask of the
VLAN interface so that the IP packets in the VLAN can participate in the L3
forwarding.
100

Configuration Guide
3.
Run the ntp-service broadcast-client command to configure the host as the NTP
broadcast client.
----End
Example
Assume the following configurations: MA5616 functions as the NTP client, snooping on the
broadcast packets sent from the server through IP address 10.10.10.20/24 of the L3 interface of
VLAN 2 and synchronizing the local clock with the clock on the broadcast server. To perform
these configurations, do as follows:
huawei(config)#vlan 2 standard
huawei(config-if-vlanif2)#ntp-service broadcast-client
3.9.3 Configuring the NTP Multicast Mode

This topic describes how to configure the MA5616 for clock synchronization in the NTP
multicast mode. After the configuration is complete, the server periodically multicasts clock
synchronization packets through a specified port, and functions as a client to listen to the
multicast packets sent from the server and synchronizes the local clock according to the received
multicast packets.
Prerequisites
Before configuring the NTP multicast mode, make sure that the network interface and the routing
Context
In the multicast mode, the server periodically sends clock synchronization packets to the
multicast address configured by the user. The default NTP multicast address 224.0.1.1 is used
if the multicast address is not configured. The Mode field of clock synchronization packet is set
to 5 (multicast mode). The client listens to the multicast packets sent from the server. After
receiving the first multicast packet, the client exchanges NTP packet whose mode fields are set
to 3 (client mode) and 4 (server mode) with the server to estimate the network delay between
the client and the server. The client then enters the multicast client mode, continues to listen to
the incoming multicast packets, and synchronizes the local clock according to the incoming
multicast packets, as shown in Figure 3-40.
Issue 02 (2013-10-08)

101

Configuration Guide
Figure 3-40 NTP multicast mode
Precaution
1.
In the multicast mode, you need to configure both the NTP server and the NTP client.
2.
The clock stratum of the synchronizing device must be higher than or equal to that of the
Configure the NTP multicast client host.
Procedure
1.
(Optional) Configure NTP authentication.

In certain networks that have strict requirements on security, it is recommended that
you enable NTP authentication when running the NTP protocol. The configuration of
the server must be the same as that of the client.
2.
Issue 02 (2013-10-08)
a.
Run the ntp-service authentication enable command to enable NTP

authentication.
b.
Run the ntp-service authentication-keyid command to set an NTP

authentication key.
c.
Run the ntp-service reliable authentication-keyid command to declare that the

key is reliable.
Add a VLAN L3 interface.

a.
b.
Run the port vlan command to add an upstream port to the VLAN so that the
user packets carrying the VLAN tag are transmitted upstream through the
upstream port.
c.
In the global config mode, run the interface vlanif command to create a VLAN
interface, and then enter the VLAN interface mode to configure the L3 interface.
d.
Run the ip address command to configure the IP address and subnet mask of the
VLAN interface so that the IP packets in the VLAN can participate in the L3
forwarding.
102

Configuration Guide
3.
Run the ntp-service multicast-client command to configure the host as the NTP
multicast client.
----End
Example
Assume the following configurations: MA5616 functions as the NTP client, listening to the
multicast packets sent from the server through IP address 10.10.10.20/24 of the L3 interface of
VLAN 2 and synchronizing the local clock with the clock on the multicast server. To perform
these configurations, do as follows:
huawei(config-if-vlanif2)#ntp-service multicast-client
3.9.4 Configuring the NTP Unicast Server Mode

This topic describes how to configure the MA5616 as the NTP client to synchronize with the
NTP server in the network.
Prerequisites
Before configuring the NTP client/server mode, make sure that the network interface and the
routing protocol of the MA5616 are configured so that the server and the client are reachable to
each other at the network layer.
Context
In the client/server mode, the client sends a synchronization packet to the server, with the mode
field set to 3 (client mode). After receiving the packet, the server automatically enters the server
mode and sends a response packet with the mode field set to 4 (server mode). After receiving
the response from the server, the client filters and selects the clock, and synchronizes with the
preferred server, as shown in Figure 3-41.
Figure 3-41 NTP client/server mode
Issue 02 (2013-10-08)

103

Configuration Guide
Precaution
1.
In the client/server mode, you need to configure only the client, and need not configure the
server.
2.
The clock stratum of the synchronizing device must be lower than or equal to that of the
Procedure
Step 1 Add a VLAN L3 interface.
1.
2.
Run the port vlan command to add an upstream port to the VLAN so that the user packets
carrying the VLAN tag are transmitted upstream through the upstream port.
3.
In the global config mode, run the interface vlanif command to create a VLAN interface,
and then enter the VLAN interface mode to configure the L3 interface.
4.
Run the ip address command to configure the IP address and subnet mask of the VLAN
interface so that the IP packets in the VLAN can participate in the L3 forwarding.
Step 2 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 timer server and the interface
for transmitting and receiving NTP packets.
NOTE
l In this command, ip-address is a unicast address, which cannot be a broadcast address, a multicast address,
or the IP address of a local clock.
l After the source interface of the NTP packets is specified by source-interface, the source IP address of the
NTP packets is configured as the primary IP address of the specified interface.
l A server can function as a time server to synchronize other devices only after its clock is synchronized.
l You can run the ntp-service unicast-server command for multiple times to configure multiple servers.
Then, the client selects the best server according to clock priorities.
Step 3 (Optional) Configure the ACL rules.

Filter the packets that pass through the L3 interface. Only the IP packet from the clock server is
allowed to access the L3 interface. Other unauthorized packets are not allowed to access the L3
interface. It is recommended to use the ACL rules for the system that has high requirements on
security.
1.
Run the acl adv-acl-numbe command to create an ACL.
2.
Run the rule command to classify traffic according to the source IP address, destination IP
address, type of the protocol over IP, and features or protocol of the packet, allowing or
forbidding the data packets that meet related conditions to pass.
3.
Run the packet-filter command to configure an ACL filtering rule for a specified port, and
make the configuration take effect.
----End
Example
Assume the following configurations: The IP address of the NTP server is 10.20.20.20/24,
MA5616 (IP address of the L3 interface of VLAN 2: 10.10.10.10/24 and gateway IP address:
10.10.10.1) functions as the NTP client, the NTP client sends the clock synchronization request
Issue 02 (2013-10-08)

104

Configuration Guide
packet through the VLAN L3 interface to the NTP server, the NTP server responds to the request
packet, and ACL rules are configured to allow only IP packets from the clock server to access
the L3 interface. To perform these configurations, do as follows:
uawei(config)#vlan 2 standard
huawei(config)#ntp-service unicast-server 10.20.20.20 source-interface vlanif 2
huawei(config)#acl 3010
huawei(config-acl-adv-3010)#rule deny ip source any destination 10.10.10.10
0.0.0.0
huawei(config-acl-adv-3010)#rule permit ip source 10.20.20.20 0.0.0.0 destination
10.10.10.10 0.0.0.0
huawei(config-acl-adv-3010)#quit
huawei(config)#packet-filter inbound ip-group 3010 port 0/0/1
3.9.5 Configuring the NTP Peer Mode

This topic describes how to configure the MA5616 for clock synchronization in the NTP peer
mode. In the peer mode, configure only the active peer, and the passive peer need not be
configured. In the peer mode, the active peer and the passive peer can synchronize with each
other. The peer with a higher clock stratum is synchronized by the peer with a lower clock
stratum.
Prerequisites
Before configuring the NTP peer mode, make sure that the network interface and the routing
Context
In the peer mode, the active peer and the passive peer exchange NTP packets whose mode fields
are set to 3 (client mode) and 4 (server mode). Then, the active peer sends a clock synchronization
packet to the passive peer, with the mode field of the packet set to 1 (active peer). After receiving
the packet, the passive peer automatically works in the passive mode and sends a response packet
with the mode field set to 2 (passive peer). Through packet exchange, the peer mode is set up.
The active peer and the passive peer can synchronize with each other. If both the clock of the
active peer and that of the passive peer are synchronized, the clock on a lower stratum is used,
as shown in Figure 3-42.
Issue 02 (2013-10-08)

105

Configuration Guide
Figure 3-42 NTP peer mode
Precaution
1.
In the peer mode, you need to configure the NTP mode only on the active peer.
2.
The peers determine clock synchronization according to the clock stratum instead of
according to whether the peer is an active peer.
Procedure
Step 1 Configure the NTP active peer.
1.
Run the ntp-service refclock-master command to configure the local clock as the master
NTP clock, and specify the stratum of the master NTP clock.
2.
Run the ntp-service unicast-peer command to configure the NTP peer mode, and specify
the IP address of the remote server that functions as the local timer server and the interface
for transmitting and receiving NTP packets.
NOTE
l In this command, ip-address is a unicast address, which cannot be a broadcast address, a multicast
address, or the IP address of a reference clock.
l After the source interface of the NTP packets is specified by source-interface, the source IP address
of the NTP packets is configured as the primary IP address of the specified interface.
Step 2 Add a VLAN L3 interface.

1.
2.
Run the port vlan command to add an upstream port to the VLAN so that the user packets
carrying the VLAN tag are transmitted upstream through the upstream port.
3.
In the global config mode, run the interface vlanif command to create a VLAN interface,
and then enter the VLAN interface mode to configure the L3 interface.
4.
Run the ip address command to configure the IP address and subnet mask of the VLAN
interface so that the IP packets in the VLAN can participate in the L3 forwarding.
----End
Issue 02 (2013-10-08)

106

Configuration Guide
Example
Assume the following configurations: One MA5616 functions as the NTP active peer (IP address
of the L3 interface of VLAN 2: 10.10.10.10/24) and works on clock stratum 4, the other
MA5616 (IP address: 10.10.10.20/24) functions as the NTP passive peer, the active peer sends
a clock synchronization request packet through the VLAN L3 interface to the passive peer, the
passive peer responds to the request packet, and the peer with a higher clock stratum is
synchronized by the peer with a lower clock stratum. To perform these configurations, do as
follows:
huawei(config)#ntp-service refclock-master 4
huawei(config)#ntp-service unicast-peer
3.10 Configuring the User Security

Configuring the security mechanism can protect operation users and access users against user
account theft and roaming or from the attacks from malicious users.
Context
The user security mechanism includes:
l
PITP: The purpose of the PITP feature is to provide the user physical location information
for the upper-layer authentication server. After the BRAS obtains the user physical location
information, the BRAS binds the information to the user account for authentication, thus
protecting the user account against theft and roaming.
DHCP option82: The user physical location information is added to the option82 field in
the DHCP request sent by the user. The information is used by the upper-layer
authentication server for authenticating the user, thus protecting the user account against
theft and roaming.
DHCP option 18 and option 37: The user physical location information is added to the
option 18 and option 37 fields in the DHCP request sent by the user. The information is
used by the upper-layer authentication server for authenticating the user, thus protecting
the user account against theft and roaming.
IP address binding: The IP address of the user is bound to the corresponding service port
for authenticating the user, thus ensuring the security of the authentication.
MAC address binding: The MAC address is bound to the service port, thus preventing the
access of illegal users.
Anti-MAC spoofing: It is a countermeasure taken by the system to prevent a user from

attacking the system with a forged MAC address.
Anti-IP spoofing: It is a countermeasure taken by the system to prevent a user from attacking
the system with a forged IP address.
Table 3-16 lists the default settings of the user security mechanism.
Issue 02 (2013-10-08)

107

Configuration Guide
Table 3-16 Default settings of the user security mechanism

Parameter
Default Setting
Remarks
PITP
Global function: disabled
The PITP function can be enabled

only when the functions at all
levels are enabled.
VLAN-level function: enabled

DHCP option
82
DHCP option
18 and option
37
Anti-IP
spoofing
Anti-MAC
spoofing
VLAN-level function: disabled
VLAN-level function: disabled

Service-port-level status: enabled By
default, up to eight MAC addresses
can be bound.
The DHCP option 82 function can

be enabled only when the functions
at all levels are enabled.
The DHCP option 18 and option 37
function can be enabled only when
the functions at all levels are
enabled.
The anti-IP spoofing function can
be enabled only when the functions
at all levels are enabled.
The anti-MAC spoofing function
can be enabled only when the
functions at all levels are enabled.
3.10.1 Configuring Anti-Theft and Roaming of User Account

Through PITP
Policy Information Transfer Protocol (PITP) is mainly used for the user PPPoE dialup access.
It is a protocol defined for transferring policy information between the access device and the
Broadband Remote Access Server (BRAS) through L2 P2P communication. PITP can be used
for transferring the user physical port information and protecting the user account against theft
and roaming.
Context
PITP is used for providing the user port information for the BRAS. After the BRAS obtains the
user port information, the BRAS binds the user account to the user port, thus protecting the user
account against theft and roaming. PITP has two modes, the PPPoE+ mode (also called the PITP
P mode) and the VBAS mode (also called the PITP V mode).
l
PPPoE+ mode: It means during the PPPoE negotiation between the users and BRAS, the
device adds TAG to PPPoE packets and transmits the port information to the BRAS.
VBRAS mode: It means during the PPPoE negotiation between the users and BRAS, the
BRAS sends VBRAS enquiry packets to the device to request the device to report the port
information. The device sends the port information to the BRAS by VBRAS response
packets.
Issue 02 (2013-10-08)

108

Configuration Guide
PITP is applicable to the networking of a standalone MA5616 and the networking of subtended
MA5616s.
l
In the networking of a standalone MA5616: Two PCs (PC1 and PC2) are connected to
different ports of the MA5616 for the dialup access.
In the networking of subtended MA5616s: Two PCs (PC1 and PC2) are connected to
different MA5616s (PC1 is connected to the MA5616, and PC2 is connected to the
MA5616 through a subtended device) for the dialup access.
The principles in the two scenarios are similar. The user dials up from PC1 by using the
corresponding user account. The BRAS binds the user account to the user's physical port
information reported by the MA5616. When the user of PC2 dials up by using the user account
of PC1, the BRAS discovers that the user account does not match the physical port information
and thus rejects the dialup access request of PC2.
Table 3-17 lists the default settings related to PITP.
Table 3-17 Default settings related to PITP
Parameter
Default Setting
PITP function

PPPoE tag - DSL line characteristics

function
Disabled
User-side PPPoE packet carrying the

vendor tag information
Disabled
Procedure
Step 1 Configure the relay agent information option (RAIO). Before using the PITP function, you must
configure RAIO.
Two methods are available to config RAIO, the global mode and the RAIO profile mode. For
RAIO profile mode, the VLAN that bound with the RAIO profile, adopts the configuration of
the RAIO profile. For the VLAN that not bound with the RAIO profile, the global RAIO
configuration is adopted.
l
Configure RAIO in global mode:

1.
Configure the RAIO mode.

Run the raio-mode mode pitp-pmode command to configure the RAIO mode in
the PITP P mode.
Run the raio-mode mode pitp-vmode command to configure the RAIO mode in
the PITP V mode.
Issue 02 (2013-10-08)

109

Configuration Guide
NOTE
The PITP P mode supports all the RAIO modes; the PITP V mode currently supports only the
common and userdefine modes. When the auto-sensing traffic stream is configured, fill in
8191.35 as the VPI/VCI of the tag, regardless of whether the traffic stream has learned the VPI/
VCI or not.
The parameter user-defined indicates the user-defined RAIO mode. In this mode, you need to
run the raio-format command to configure the RAIO format. Select a corresponding keyword
for configuring the RAIO format according to the PITP mode.
2.
(Optional) Configure the RAIO format if the user-defined mode is selected.

In the PITP P mode, run the raio-format pitp-pmode command to configure the
RAIO format.
In the PITP V mode, run the raio-format pitp-vmode command to configure the
RAIO format.
NOTE
In the case of the user-defined RAIO format, configure the circuit ID (CID) and the remote ID
(RID). If the access mode is not selected, the configured format applies to all access modes. If
the access mode is selected, the configured format applies to only this access mode. The CID
format and RID format in the PITP V mode are the same:
l CID: Identifies the attribute information about the device.
l RID: Identifies the access information about the user.
In other modes, the RID format is fixed and therefore it need not be configured manually.
3.
(Optional) Run the raio sub-option command to configure PPPoE Tag - DSL line
characteristics function. By default, the DSL line characteristics function is disabled.
The PPPoE+ mode supports reporting the sub-option 0x81 - 0x91 line characteristics,
including link type and encapsulation information. Enable or disable DSL line
characteristics function according to actual requirements. The configuration of DSL
line characteristics function takes effect only in the PITP P mode; the PITP V mode
does not support reporting the line parameters.
Configure RAIO in RAIO profile mode:

1.
Run the raio-profile command to create a RAIO profile and enter the RAIO profile
mode.
2.
Configure the RAIO mode.

Run the raio-mode mode pitp-pmode command to configure the RAIO mode in
the PITP P mode.
Run the raio-mode mode pitp-vmode command to configure the RAIO mode in
the PITP V mode.
NOTE
The PITP P mode supports all the RAIO modes; the PITP V mode currently supports only the
common and userdefine modes. When the auto-sensing traffic stream is configured, fill in
8191.35 as the VPI/VCI of the tag, regardless of whether the traffic stream has learned the VPI/
VCI or not.
The parameter user-defined indicates the user-defined RAIO mode. In this mode, you need to
run the raio-format command to configure the RAIO format. Select a corresponding keyword
for configuring the RAIO format according to the PITP mode.
3.
(Optional) Configure the RAIO format if the user-defined mode is selected.

In the PITP P mode, run the raio-format pitp-pmode command to configure the
RAIO format.
Issue 02 (2013-10-08)

110

Configuration Guide
In the PITP V mode, run the raio-format pitp-vmode command to configure the
RAIO format.
NOTE
In the case of the user-defined RAIO format, configure the circuit ID (CID) and the remote ID
(RID). If the access mode is not selected, the configured format applies to all access modes. If
the access mode is selected, the configured format applies to only this access mode. The CID
format and RID format in the PITP V mode are the same:
l CID: Identifies the attribute information about the device.
l RID: Identifies the access information about the user.
In other modes, the RID format is fixed and therefore it need not be configured manually.
4.
(Optional) Run the raio sub-option command to configure PPPoE Tag - DSL line
characteristics function. By default, the DSL line characteristics function is disabled.
The PPPoE+ mode supports reporting the sub-option 0x81 - 0x91 line characteristics,
including link type and encapsulation information. Enable or disable DSL line
characteristics function according to actual requirements. The configuration of DSL
line characteristics function takes effect only in the PITP P mode; the PITP V mode
does not support reporting the line parameters.
5.
Run the quit command to quit the VLAN service profile mode.
6.
Run the vlan bind raio-profile command to bind the RAIO profile created in 1.1 to
the VLAN.
l In the PITP P mode, run the raio-format pitp-pmode command to configure the RAIO
format.
l In the PITP V mode, run the raio-format pitp-vmode command to configure the RAIO
format.
Step 2 Configure the PITP function.
The PITP function can be enabled or disabled at two levels. The PITP function is enabled only
when it is enabled at both levels.
1.
Global PITP function: Run the pitp enable pmode command to enable global PITP P mode.
By default, the global PITP function is disabled.
In the PITP V mode, run the pitp vmode ether-type command to set the Ethernet protocol
type to be the same as that of the BRAS. Then, run the pitp enable vmode command to
enable global PITP V mode.
NOTE
The Ethernet protocol type of the PITP V mode must be configured when the PITP V mode is disabled.
2.
Issue 02 (2013-10-08)
(Optional) VLAN-level PITP function:

a.
Run the vlan service-profile command to create a VLAN service profile and enter
the VLAN service profile mode.
b.
Run the pitp enable command to enable the PITP function of the VLAN. By default,
the PITP function of the VLAN is enabled.
c.
Run the commit command to make the profile configuration take effect. The
configuration of the VLAN service profile takes effect only after this command is
executed.
d.
111

Configuration Guide
e.
Run the vlan bind service-profile command to bind the VLAN service profile created
in 2.2.a to the VLAN.
Step 3 Configure the optional attributes of PITP.

Run the pitp permit-forwarding service-port command to set whether the service port allows
the user-side PPPoE packet carrying the vendor tag information. By default, this function is
disabled, that is, the user-side PPPoE packet carrying the vendor tag information is not allowed.
The system adds a tag containing the device name, shelf ID, slot ID, and port ID to the PPPoE
+ upstream PADI and PADR packets to generate new packets. If this function is enabled, tagged
packets are forwarded. If this function is disabled, tagged packets are discarded.
When the PITP function is applied to the OLT+MA5616 network, pay attention to the following
points:
l When the PITP function is enabled only on the OLT, the tag of the PADI packet contains
only the information about the PON port on the OLT.
l When the PITP function is enabled only on the MA5616, the tag of the PADI packet contains
only the information about the user port on the MA5616.
l If the PITP function is enabled on both the OLT and the MA5616, and the PPPoE tag is
required to contain the information about the user port on the MA5616, enable the forwarding
of the PPPoE packets with the PITP information (through the pitp permit-forwarding
service-port command on the OLT).
----End
Example
Assume the following configuration:
l
RAIO configuration mode: global mode
RAIO mode: user-defined mode
CID format for the ATM access mode: shelf ID/slot ID/port ID:VPI.VCI
CID format for the Ethernet access mode: shelf ID slot ID port ID:VLAN ID
To enable the PITP P function for the traffic stream with VLAN ID 30, do as follows:
huawei(config)#raio-mode user-defined pitp-pmode
huawei(config)#raio-format pitp-pmode cid atm anid atm frame/slot/port:vpi.vci
huawei(config)#raio-format pitp-pmode cid eth anid eth frame/slot/port:vlanid
huawei(config)#raio-format pitp-pmode rid atm plabel
huawei(config)#raio-format pitp-pmode rid eth plabel
huawei(config)#pitp enable pmode
huawei(config-vlan-srvprof-1)#pitp enable

l
RAIO configuration mode: RAIO profile mode
CID format for the Ethernet access mode: shelf ID slot ID port ID:VLAN ID
To enable the PITP P function for the traffic stream with VLAN ID 30, do as follows:
Issue 02 (2013-10-08)

112

Configuration Guide
huawei(config)#raio-profile index 1
huawei(config-raio-profile-1)#raio-mode user-defined pitp-pmode
huawei(config-raio-profile-1)#raio-format pitp-pmode cid atm anid atm frame/slot/
port:vpi.vci
huawei(config-raio-profile-1)#raio-format pitp-pmode cid eth anid eth frame/slot/
port:vlanid
huawei(config-raio-profile-1)#raio-format pitp-pmode rid atm plabel
huawei(config-raio-profile-1)#raio-format pitp-pmode rid eth plabel
huawei(config-raio-profile-1)#quit
huawei(config)#vlan bind raio-profile 30 index 1
To set the Ethernet protocol type of VBRAS packets to be the same as the Ethernet protocol
type of the upper-layer BRAS, namely, 0x8500, enable the PITP V function for the traffic stream
with VLAN ID 30, and configure the RAIO mode to common, do as follows:
huawei(config)#raio-mode common pitp-vmode
huawei(config)#pitp enable vmode
3.10.2 Configuring Anti-Theft and Roaming of User Accounts

Through DHCPv4
DHCPv4 improves the user authentication security by adding the user physical location
information to the option 82 field of the DHCP request packets initiated by the user, so as to
prevent theft and roaming of the user account.
Context
The option 82 field contains the circuit ID (CID), remote ID (RID), suboption 7 field
(optional), and suboption 9 field (optional), and provides the information such as the user subrack
ID, slot ID, port ID, VPI, and VCI.
The MA5616 can work in the L2 DHCP forwarding mode. In the mode, anti-theft and roaming
of user accounts through DHCP option 82 can be configured.
Table 3-18 lists the default settings related to DHCP option 82.
Table 3-18 Default settings related to DHCP option 82
Parameter
Default Setting
Status of the DHCP option 82 function
Global status: disabled

VLAN-level status: enabled
Issue 02 (2013-10-08)

113

Configuration Guide
Parameter
Default Setting
Status of the DHCP option 82

suboption 7 function
Disabled
NOTE
The CCUC and CCUE control board
supports this function, and the CCUB
control board does not support this
function.
Status of the DHCP option 82

suboption 9 function
Disabled
Status of forwarding the DHCP packets

with option 82 from the client side
Disabled
Procedure
Step 1 Configure the relay agent information option (RAIO). Before using the DHCP function, you
must configure the RAIO.
l

1.
Run the raio-mode mode dhcp-option82 command to set the RAIO mode.
2.
(Optional) If the user-defined mode is selected, run the raio-format dhcp-option82

command to configure the RAIO format.
To configure the user-defined format, mainly configure the RID in the CID.
If the access mode is not selected, the configured format is valid to all access
modes. If the access mode is selected, the configured format is valid to only this
access mode.
For details about the RAIO format, see the raio-format command.
NOTE
In other modes except the user-defined mode, the RID format is fixed and therefore it need not
be configured manually.
NOTE
l CID identifies the attribute information of the device.

l RID identifies the access information of the user.
3.
(Optional) Run the raio sub-option command to enable the DHCP option 82
suboption 9 function.
When DHCP needs to support the reporting of the line parameters related to sub
options 0x81-0x91 as defined in TR101, run this command to enable the DHCP option
82 suboption 9 function.
l
Issue 02 (2013-10-08)

114

Configuration Guide
1.
mode.
2.
Run the raio-mode mode dhcp-option82 command to set the RAIO mode.
3.
(Optional) If the user-defined mode is selected, run the raio-format dhcp-option82

access mode.
NOTE
NOTE

4.
(Optional) Run the raio sub-option command to enable the DHCP option 82
suboption 9 function.
When DHCP needs to support the reporting of the line parameters related to sub
options 0x81-0x91 as defined in TR101, run this command to enable the DHCP option
82 suboption 9 function.
5.
6.
Run the vlan bind raio-profile command to bind the RAIO profile created in 1.1 to
the VLAN.
Step 2 (Optional) Run the dhcp sub-option7 command to enable the DHCP option 82 suboption 7
function.
When the user name needs to be encapsulated in suboption 7 of DHCP option 82 and transmitted
to the DHCP server, you can enable the DHCP option 82 suboption 7 function.
Step 3 (Optional) Set the service port to allow or prohibit the user-side DHCP packets that carry the
option 82 information.
Run the dhcp-option82 permit-forwarding service-port command to set the service port to
allow or prohibit the DHCP packets that carry the option 82 information.
The system adds the device name, shelf ID, slot ID, and port ID to the option 82 field of DHCP
packets to generate new packets. If the service port is set to allow the packets carrying the option
82 information, tagged packets are forwarded. If the service port is set to prohibit the packets
carrying the option 82 information, tagged packets are dropped.
Step 4 Enable or disable the DHCP option 82 function.
Run the dhcp option82 command to enable the DHCP option 82 function on the port. By default,
the DHCP option 82 function is disabled globally.
The DHCP option 82 function can be enabled or disabled at two levels. The DHCP option 82
function takes effect only when it is enabled at both levels.
Issue 02 (2013-10-08)

115

Configuration Guide
1.
Global DHCP option 82 function: Run the dhcp option82 command to enable the DHCP
option 82 function globally. By default, the DHCP option 82 function is disabled globally.
2.
(Optional) VLAN-level DHCP option 82 function:

a.
b.
Run the dhcp option82 command to enable the DHCP option 82 function. By default,
the DHCP option 82 function is enabled.
c.
configuration of the VLAN service profile takes effect only after you run this
command.
d.
e.
Run the vlan bind service-profile command to bind the VLAN service profile created
in 4.2.a to the VLAN.
----End
Example
l
CID format for the Ethernet access mode: shelf ID/slot ID/sub slot ID/port ID:VLAN ID
RID format for all access modes: label of the service port
To enable the DHCPv4 option 82 function, do as follows:

huawei(config)#raio-mode user-defined dhcp-option82
huawei(config)#raio-format dhcp-option82 cid eth anid eth frame/slot/subslot/
port:vlanid
huawei(config)#raio-format dhcp-option82 cid atm anid frame/slot/port:vpi.vci
huawei(config)#raio-format dhcp-option82 rid eth splabel
huawei(config)#raio-format dhcp-option82 rid atm splabel
huawei(config)#dhcp option82 enable

l
To enable the DHCPv4 option 82 function for VLAN 30, do as follows:

huawei(config-raio-profile-1)#raio-mode user-defined dhcp-option82
huawei(config-raio-profile-1)#raio-format dhcp-option82 cid eth anid eth frame/
slot/subslot/port:vlanid
huawei(config-raio-profile-1)#raio-format dhcp-option82 cid atm anid frame/slot/
port:vpi.vci
huawei(config-raio-profile-1)#raio-format dhcp-option82 rid eth splabel
huawei(config-raio-profile-1)#raio-format dhcp-option82 rid atm splabel
Issue 02 (2013-10-08)

116

Configuration Guide

3.10.3 Configuring Anti-Theft and Roaming of User Accounts

Through DHCPv6
DHCPv6 improves the user authentication security by adding the user physical location
information to the option 18 and option 37 field of the DHCP request packets initiated by the
user, so as to prevent theft and roaming of the user account.
Context
The option 18 field contains the circuit ID (CID), and the option 37 field contains the remote ID
(RID). The option 18 field and option 37 field provides the information such as the user subrack
ID, slot ID, port ID, VPI, and VCI.
The MA5616 can work in the L2 DHCPv6 forwarding mode. In the mode, anti-theft and roaming
of user accounts through DHCPv6 option 18 and option 37 can be configured.
Table 3-19 lists the default settings related to DHCPv6 option 18 and option 37.
Table 3-19 Default settings related to DHCPv6 option 18 and option 37
Parameter
Default Setting
Status of the DHCPv6 option 18 and

option 37 function
Global status: disabled

VLAN-level status: enabled
Procedure
Step 1 Configure the relay agent information option (RAIO). Before using the DHCP function, you
must configure the RAIO.
l

1.
Run the raio-mode mode dhcpv6-option command to set the RAIO mode.
2.
(Optional) If the user-defined mode is selected, run the raio-format dhcpv6-option

access mode.
Issue 02 (2013-10-08)

117

Configuration Guide
NOTE
NOTE


1.
mode.
2.
Run the raio-mode mode dhcpv6-option command to set the RAIO mode.
3.
(Optional) If the user-defined mode is selected, run the raio-format dhcpv6-option

access mode.
NOTE
NOTE

4.
5.
Run the vlan bind raio-profile command to bind the RAIO profile to the VLAN.
Step 2 (Optional) Set the port to allow or prohibit the user-side DHCPv6 packets that carry the option
18 and option 37 information.
l Run the dhcpv6-option permit-forwarding command to set the port to allow or prohibit
the DHCPv6 packets that carry the option 18 and option 37 information.
The system adds the device name, shelf ID, slot ID, and port ID to the option 18 and option
37 field of DHCP packets to generate new packets. If the service port is set to allow the
packets carrying the option 18 and option 37 information, tagged packets are forwarded. If
the service port is set to prohibit the packets carrying the option 18 and option 37 information,
tagged packets are dropped.
Step 3 Enable or disable the DHCPv6 option 18 and option 37 function.
Run the dhcpv6 option command to enable the DHCPv6 option 18 and option 37 function on
the port. By default, the DHCPv6 option 18 and option 37 function is disabled globally.
The DHCPv6 option 18 and option 37 function can be enabled or disabled at two levels. The
DHCPv6 option 18 and option 37 function takes effect only when it is enabled at both levels.
1.
Issue 02 (2013-10-08)
Global DHCPv6 option 18 and option 37 function: Run the dhcpv6 option command to
enable the DHCPv6 option 18 and option 37 function globally. By default, the DHCPv6
option 18 and option 37 function is disabled globally.
118

Configuration Guide
2.
(Optional) VLAN-level DHCPv6 option 18 and option 37 function:

a.
b.
Run the dhcpv6 option command to enable the DHCPv6 option 18 and option 37
function. By default, the DHCPv6 option 18 and option 37 function is enabled.
c.
configuration of the VLAN service profile takes effect only after you run this
command.
d.
e.
Run the vlan bind service-profile command to bind the VLAN service profile to the
VLAN.
----End
Example
l
To enable the DHCPv6 option 18 and option 37 function, do as follows:

huawei(config)#raio-mode user-defined dhcpv6-option
huawei(config)#raio-format dhcpv6-option cid eth anid eth frame/slot/subslot/
port:vlanid
huawei(config)#raio-format dhcpv6-option cid atm anid frame/slot/port:vpi.vci
huawei(config)#raio-format dhcpv6-option rid eth splabel
huawei(config)#raio-format dhcpv6-option rid atm splabel
huawei(config)#dhcpv6 option enable

l
To enable the DHCPv6 option 18 and option 37 function for VLAN 30, do as follows:
huawei(config-raio-profile-1)#raio-mode user-defined dhcpv6-option
huawei(config-raio-profile-1)#raio-format dhcpv6-option cid eth anid eth frame/
slot/subslot/port:vlanid
huawei(config-raio-profile-1)#raio-format dhcpv6-option cid atm anid frame/slot/
port:vpi.vci
huawei(config-raio-profile-1)#raio-format dhcpv6-option rid eth splabel
huawei(config-raio-profile-1)#raio-format dhcpv6-option rid atm splabel
huawei(config)#dhcpv6 option enable
Issue 02 (2013-10-08)

119

Configuration Guide
3.10.4 Configuring the Anti-IP Address Attack

This topic describes how to configure IP address binding and anti-IP spoofing to prevent
malicious users from attacking the device or authorized users by forging the IP addresses of
authorized users.
Prerequisites
The service port to be bound to an IP address is created.
Context
IP address binding refers to binding an IP address to a service port. After the binding, the service
port permits only the packet whose source IP address is the bound address to go upstream, and
discards the packets that carry other source IP addresses.
Anti-IP spoofing is to dynamically trigger the IP address binding, preventing illegal users from
stealing the IP address of legal users. When anti-IP spoofing is enabled, a user port is bound to
an IP address after the user goes online. Then, the user cannot go online through this port by
using other IP addresses, and any user cannot go online through other ports by using this IP
address. Anti-IP spoofing is mainly applied to DHCP access users.
Procedure
l
Configure the IP address binding.

Run the bind ip command to bind an IP address to a service port.
To permit only the users of certain IP addresses to access the system so that illegal users
cannot access the system by using the IP addresses of legal users, configure the IP address
binding.
Configure anti-IPv4 spoofing.

The anti-IPv4 spoofing function can be enabled or disabled at two levels. The function
takes effect only when it is enabled at both levels.
Global function: Run the security anti-ipspoofing command to configure the global
function. By default, the global function is disabled.
VLAN-level function:
Issue 02 (2013-10-08)
1.
2.
Run the security anti-ipspoofing command to configure the VLAN-level

function. By default, the VLAN-level function is disabled.
3.
executed.
4.
5.
Run the vlan bind service-profile command to bind the VLAN to the VLAN
service profile configured in 1.
120

Configuration Guide
NOTE
When anti-IPv4 spoofing is enabled after a user is already online, the IPv4 address of this user is not bound
by the system. As a result, the service of this user is interrupted, this user goes offline, and the user needs
to go online again. Only the user who goes online after anti-IPv4 spoofing is enabled can have the IPv4
address bound.
Configure anti-IPv6 spoofing.

The anti-IPv6 spoofing function can be enabled or disabled at two levels. The function
takes effect only when it is enabled at both levels.
Global function: Run the security anti-ipv6spoofing command to configure the global
function. By default, the global function is disabled.
1.
2.
Run the security anti-ipv6spoofing command to configure the VLAN-level

3.
executed.
4.
5.
NOTE
When anti-IPv6 spoofing is enabled after a user is already online, the IPv6 address of this user is not bound
by the system. As a result, the service of this user is interrupted, this user goes offline, and the user needs
to go online again. Only the user who goes online after anti-IPv6 spoofing is enabled can have the IPv6
address bound.
----End
Example
To bind IP address 10.10.10.20 to service port 2, that is, service port 2 permits only the packet
whose source IP address is 10.10.10.20, do as follows:
huawei(config)#bind ip service-port 2 10.10.10.20
To bind IP address 2000::1/64 to service port 2, that is, service port 2 permits only the packet
whose source IP address is 2000::1/64, do as follows:
huawei(config)#bind ip service-port 2 2000::1/64
To enable anti-IPv4 spoofing for VLAN 10, do as follows:

huawei(config)#security anti-ipspoofing enable
huawei(config-vlan-srvprof-2)#security anti-ipspoofing enable
To enable anti-IPv6 spoofing for VLAN 10, do as follows:

huawei(config)#security anti-ipv6spoofing enable
Issue 02 (2013-10-08)

121

Configuration Guide
huawei(config-vlan-srvprof-2)#security anti-ipv6spoofing enable

3.10.5 Configuring the Anti-MAC Address Attack

This topic describes how to configure MAC address binding, anti-MAC spoofing, anti-MAC
duplicate, and virtual MAC (VMAC) address to prevent malicious users from attacking the
device or authorized users by forging the MAC addresses of authorized users.
Context
MAC address binding refers to binding a MAC address to a service port. After the binding, only
the user whose MAC address is the bound MAC address can access the network through the
service port. The MA5616 does not support the direct binding of a MAC address. Instead, the
binding between a service port and a MAC address is implemented through setting a static MAC
address entry of a port and setting the maximum number of learnable MAC addresses to 0.
The major function of anti-MAC spoofing is to prevent illegal users from forging the MAC
address of legal users. The purpose is to ensure that the service of legal users is not affected.
Anti-MAC spoofing is mainly applied to PPPoE and DHCP access users.
VMAC adopts the trusty virtual MAC address allocated by the MA5616 to replace the source
MAC addresses of terminal users and prevents untrusty MAC addresses from entering the
network, preventing MAC address conflict and MAC address spoofing from malicious users.
The anti-MAC-duplicate function does not allow dynamic MAC addresses to be duplicated
before they are aged. In this way, when MAC address conflicts occur between different users,
the user that goes online first will not be affected.
Procedure
l
Configure the MAC address binding.

1.
Run the mac-address static command to add a static MAC address.
2.
Run the mac-address max-mac-count command to set the maximum number of

learnable MAC addresses to 0.
This parameter is to limit the maximum number of the MAC addresses that can be
learned through one account, that is, to limit the maximum number of the PCs that
can access the Internet through one account.
Configure anti-MAC spoofing.
CAUTION
To ensure device security, it is recommended that you enable this function.
The anti-MAC spoofing function can be enabled or disabled at tow levels. The anti-MAC
spoofing function is enabled only when it is enabled at both the tow levels.
Global function: Run the security anti-macspoofing command to configure the global
function. By default, the global function is disabled. For IPv6 users, run the security
Issue 02 (2013-10-08)

122

Configuration Guide
anti-macspoofing control-protocol ipv6oe command to enable the anti-MAC

Spoofing for IPv6 users besides running the security anti-macspoofing command. By
default, the global anti-MAC spoofing function for IPv6 users is disabled.
1.
2.
Run the security anti-macspoofing command to configure the VLAN-level

3.
executed.
4.
5.
NOTE
When anti-MAC spoofing is enabled after a user is already online, the MAC address of this user is not
bound by the system. As a result, the service of this user is interrupted, this user goes offline, and the user
needs to go online again. Only the user who goes online after anti-MAC spoofing is enabled can have the
MAC address bound.
Configure 1:1 VMAC.

NOTE
The xPoE/xPoA MAC address can be allocated in multi-MAC mode. When VMAC is enabled, multiMAC is also 1:1 VMAC. In such a case, the device uses a unique VMAC address to replace the MAC
address of a single user. The relationship between the user MAC address and the device VMAC address
is 1:1.
l If VMAC is disabled, the PPPoA and IPoA MAC addresses are obtained from the configured MAC
address pool (by running the mac-pool command).
l IPoA does not support the obtaining of the MAC address using the VMAC and the MAC address can
only be obtained from the MAC address pool.
1.
Configure VMAC-related attributes.

a.
Run the vmac dslam-id command to configure the DSLAM ID.

The DSLAM ID is bits 21-39 of the VMAC address, 19 bits in total. VMAC can
be enabled only when dslam-id is in the range of 0x0-0x7ffff.
NOTE
The uniqueness of the DSLAM ID must be ensured by the configuration engineer to

prevent allocating the same VMAC address to two DSLAMs.
b.
(Optional) Run the vmac port-vmac-count command to configure the number

of VMAC addresses on each port.
To limit the number of VMAC addresses on each port, run this command. By
default, the number of VMAC addresses on each port is 8.
c.
(Optional) Run the vmac reserved-bits command to configure the reserved bits
of the VMAC address.
This command is used to set the value of the reserved bits (bits 47-42) in the
VMAC address generating format. The VMAC value is made up of the value of
reserved bits and other bits. To enable VMAC, the value of the reserved bits must
Issue 02 (2013-10-08)

123

Configuration Guide
be in the range of [0x0,0x3F]. Otherwise, VMAC fails to be enabled. By default,

the value is 0x0.
2.
Enable VMAC.
Run the vmac enable command to enable VMAC. After VMAC is enabled, the
VMAC address is generated according to the DSLAM ID, slot ID, and port ID.
VMAC can be enabled globally or at the VLAN service profile level.
a.
In the global config mode, run the vmac enable command to enable VMAC.
b.
Run the vlan service-profile command to enter the VLAN service profile mode.
c.
Run the vmac enable command to enable VMAC at the VLAN service profile
level.
d.
Run the commit command to commit the configuration.
Configure the anti-MAC-duplicate function.

After the anti-MAC-duplicate function is enabled and before the dynamic MAC address
learned by the system is aged, the packets transmitted from other ports will be discarded if
the packets carry the same MAC address.
NOTE
l By default, the anti-MAC-duplicate function is disabled.

l When anti-MAC duplicate and anti-MAC spoofing are enabled, anti-MAC spoofing is preferred and
anti-MAC duplicate does not take effect.
1.
Run the security anti-macduplicate command to enable anti-MAC duplicate.
2.
Run the display security config command to query the configuration.
----End
Example
To bind static MAC address 1010-1010-1010 to service port 1, and set the maximum number
of learnable MAC addresses to 0, that is, service port 1 permits only the packet whose source
MAC address is 1010-1010-1010, do as follows:
huawei(config)#mac-address static service-port 1 1010-1010-1010
huawei(config)#mac-address max-mac-count service-port 1 0
To enable anti-MAC spoofing for VLAN 10, and set the maximal number of MAC address
bound to service port 2 (related to VLAN 10) to 7.
huawei(config)#security anti-macspoofing enable
huawei(config)#security anti-macspoofing max-mac-count service-port 2 7
To enable the global VMAC function with DSLAM ID 0x0e02 and enable the 1:1 VMAC
function of VLAN service profile 2 bound to VLAN 10, do as follows:
huawei(config)#vmac dslam-id 0x0e02
huawei(config)#vmac enable
huawei(config-vlan-srvprof-2)#vmac enable
To enable anti-MAC duplicate so that the user that goes online first will not be affected when
MAC address conflicts occur between different users, do as follows:
Issue 02 (2013-10-08)

124

Configuration Guide
huawei(config)#security anti-macduplicate enable
3.11 Configuring System Security

This topic describes how to configure the network security and protection measures of the system
to protect the system from malicious attacks.
Context
With the system security feature, the MA5616 can be protected against the attacks from the
network side or user side, and therefore the MA5616 can run stably in the network. System
security includes the following items:
l
ACL/Packet filtering firewall
Blacklist
Anti-DoS attack
Anti-ICMP/IP attack
Source route filtering
Source MAC address filtering
User-side ring network detection
Allowed/Denied address segment
The following common inappropriate configurations affect the system security:

l
The ring network detection is not enabled.

Preventive methods or measures: Run the ring check command to enable the function of
checking user-side ring networks.
The anti-address spoofing functions is not enabled. If the anti-address spoofing function is
not enabled, an unauthorized user may forge the MAC address of an authorized user to
send PPPoE or DHCP control packets, threatening the system security.
Preventive methods or measures: Run the security anti-macspoofing enable command to
enable the anti-MAC spoofing.
Use a public network address to manage the device. The access rights are not strictly limited
when the ACL is configured. Therefore, the network may be attacked.
Preventive methods or measures:
Use a private network address to manage the device.
When configuring the ACL, apply the minimum authorization principle.
Configure the permitted IP address segment, and add only the necessary management
IP address segment. IP addresses other than have been specified are not permitted to
access the device through the management port.
Packets accessing the management interface of the device are not controlled. When a device
is attacked by packets, the system is busy and the services cannot be provided in the normal
state.
Preventive methods or measures: Run the firewall packet-filter command to apply the
firewall packet filtering rule on the interface to filter packets received on the interface and
prevent packet attacks.
Table 3-20 lists the default settings of system security.

Issue 02 (2013-10-08)

125

Configuration Guide
Table 3-20 Default settings of system security

Parameter
Default Setting
Firewall blacklist
Disabled
Anti-DoS attack
Disabled
Anti-ICMP attack
Disabled
Anti-IP attack
Disabled
Source route filtering
Disabled
User-side ring network detection
Disabled
3.11.1 Configuring Firewall

Configuring system firewall can control the packets that go through the management port of the
device so that unauthorized operators cannot access the system through the inband or outband
channel.
Context
Firewall includes the following items:
l
Blacklist: The blacklist function can be used to screen the packets sent from a specific IP
address. A major feature of the blacklist function is that entries can be dynamically added
or deleted. When firewall detects the attack attempt of a specific IP address according to
the characteristics of packets, firewall actively adds an entry to the blacklist and then filters
the packets from this IP address.
ACL/Packet filtering firewall: Configure an ACL to filter data packets. To set a port to
allow only one type of packets to go through, use the ACL to implement the packet filtering
function.
For example, to allow only the packets from source IP address 1.1.1.1 to go through a port
in the inbound direction, do as follows:
Issue 02 (2013-10-08)
1.
Configure an ACL rule1, which allows the packets with source IP address 1.1.1.1 to
pass.
2.
Configure an ACL rule2, which denies all packets.
3.
Run the firewall packet-filter command, and bind rule2 first and then rule1 to the
inbound direction.

126

Configuration Guide
NOTE
On the MA5616, an ACL can be activated in two modes. In two modes, the execution priorities on
the sub-rules in one ACL are different.
l Run the firewall packet-filter command to activate an ACL. This mode is mainly applied to
the NMS. For the sub-rules in one ACL, the execution priority is implemented by software. The
earlier the execution priority of the sub-rules in one ACL is configured, the higher the priority.
l Run the packet-filter command to activate an ACL. For the sub-rules in one ACL, the execution
priority is implemented by hardware. The later the execution priority of the sub-rules in one
ACL is configured, the higher the priority.
CAUTION
To ensure device security, firewall must be configured. This is to control the packets that go
through the management port of the device.
Procedure
l
Configure a firewall blacklist.

Two modes are supported: configuring a firewall blacklist by using ACLs or by adding the
source IP addresses of untrusted packets. Choose either mode, or both.
When two modes are configured, the priority of the firewall blacklist function is higher
than the priority of ACLs. That is, the system checks the firewall blacklist first, and then
matches ACLs.
Configure the firewall blacklist function by using advanced ACLs.

1.
Run the acl command to create an ACL. Only advanced ACLs can be used when
the black list function is enabled. Therefore, the range of the ACL ID is
3000-3999.
2.
Run the rule(adv acl) command to create an advanced ACL.
3.
Run the quit command to return to the global config mode.
4.
Run the firewall blacklist enable acl-number acl-number command to enable

the firewall blacklist function.
Configure the firewall blacklist function by adding the source IP addresses of untrusted
packets.
1.
Run the firewall blacklist item command to add the source IP addresses of
untrusted packets to the blacklist.
2.
Run the firewall blacklist enable command to enable the firewall blacklist
function.
Configure the firewall (filtering packets based on the ACL).

1.
Run the acl command to create an ACL. Only basic ACLs and advanced ACLs can
be used when packet filtering by firewall is configured. Therefore, the range of the
ACL ID is 2000-3999.
2.
Run different commands to create different types of ACLs.

Basic ACL: Run the rule(basic acl) command.
Issue 02 (2013-10-08)

127

Configuration Guide
Advanced ACL: Run the rule(adv acl) command.

3.
4.
Run the firewall enable command to enable the firewall blacklist function. By default,
the firewall blacklist function is disabled.
To filter the packets of a port based on the basic ACL, enable the firewall blacklist
function.
5.
Run the interface meth command to enter the METH mode to configure the firewall
packet filtering rules for an METH interface; run the interface vlanif command to
enter the VLANIF mode configure the firewall packet filtering rules for a VLAN
interface.
6.
Run the firewall packet-filter command to apply firewall packet filtering rules to an
interface.
----End
Example
To add IP address 10.10.10.18 to the firewall blacklist with the aging time of 100 min, do as
follows:
huawei(config)#firewall blacklist item 10.10.10.18 timeout 100
huawei(config)#firewall blacklist enable
To add the IP addresses in network segment 10.10.10.0 to the firewall blacklist and bind ACL
3000 to these IP addresses, do as follows:
huawei(config-acl-adv-3000)#rule deny ip source 10.10.10.0 0.0.0.255 destination
10.10.10.20 0
huawei(config)#firewall blacklist enable acl-number 3000
To deny the users in network segment 10.10.11.0 to access the maintenance Ethernet port with
IP address 10.10.11.28 on the device, do as follows:
huawei(config-acl-adv-3001)#rule 5 deny icmp source 10.10.11.0 0.0.0.255 destin
ation 10.10.11.28 0
huawei(config)#firewall enable
huawei(config)#interface meth 0
huawei(config-if-meth0)#firewall packet-filter 3001 inbound
ACL applied successfully
3.11.2 Configuring Anti-Attack

Enabling anti-DoS attack and anti-ICMP/IP attack, and configuring the source route filtering
and source MAC address filtering functions can prevent malicious users' attack on the system,
so as to improve system security.
Context
The MA5616 supports the following measures to prevent malicious users' attack on the system.
Choose measures according to actual requirements.
Issue 02 (2013-10-08)

128

Configuration Guide
Anti-DoS attack: indicates the defensive measures taken by the system to receive only a
certain number of control packets sent from a user.
Anti-ICMP attack: indicates the defensive measures taken by the system to drop the ICMP
packets sent from the user-side device to the MA5616. This is to prevent the user-side
device from pinging the VLAN interface of the MA5616.
Anti-IP attack: indicates the defensive measures taken by the system to drop the IP packets
sent from the user-side device to the MA5616.
Source route filtering: indicates the defensive measures taken by the system to filter the IP
packets that are sent by the user and carry the routing option field.
Source MAC address filtering: indicates the defensive measures taken by the system to
filter the packets that are sent by the user and carry certain source MAC addresses.
Configure anti-DoS attack.
Procedure
Run the security anti-dos enable command to enable global anti-DoS attack. With global
anti-DoS attack enabled, when the system receives attack packets from a user port, the
system adds the user port to the blacklist. When global anti-DoS attack is disabled, the
system deletes the blacklist.
Application scenario: Two PCs (PC1 and PC2) are connected to the network through the
MA5616. If a malicious user (PC1) sends a large number of protocol control packets to
attack the CPU of the MA5616, the CPU usage of the MA5616 will be over high, and then
the MA5616 is unable to process the services of another user (PC2). To implement antiDoS attack, shield the attack port or suppress the protocol packet sending to protect the
MA5616 from being attacked.
l
Configure anti-ICMP attack.

Run the security anti-icmpattack enable command to enable anti-ICMP attack. AntiICMP attack is mainly used to prevent the user-side device from pinging the VLAN
interface of the MA5616.
Application scenario: Two PCs (PC1 and PC2) are connected to the network through the
MA5616. When PC2 sends a large number of ICMP packets to the VLAN interface, the
services of the user (PC1) that obtains the upper-layer DHCP information through the same
VLAN interface will be abnormal. To implement anti-ICMP attack, directly drop the userside ICMP packets if the IP address of the VLAN interface on the MA5616 is its destination
IP address.
Enable anti-IP attack.

Run the security anti-ipattack enable command to enable anti-IP attack. The anti-IP attack
is used to prevent user-side IP packets from attacking the Layer 3 interface of the device
or to prevent illegal users from logging in to the device through telnet.
Application scenario: When a PC sends the packets with the address of VLAN x as the
destination IP address to VLANIF x, it may send a large number of packets to attack the
device, causing the device to fail to process normal services; when a user knows the address
of VLAN x, or the user name and password for logging in to the device, the user may log
in to the device through telnet to randomly change the configurations of the device. To
prevent the two preceding cases, the device needs to implement anti-IP attack. With this
Issue 02 (2013-10-08)

129

Configuration Guide
feature, the device drops the packets with the address of the device interface as the
destination IP address to prevent the user from attacking the device.
l
Enable the source route filtering function.

Run the security source-route enable command to enable the source route filtering
function. This function is mainly used to filter the packets that carry the routing information
and are reported to the Layer 3 switch.
Application scenario: In general, routes are dynamic and application does not control route
selection. The sender can add the routing information to IP packets through the source route
to perform route selection. In this case, packets go along a specific route in the network
according to the intention of the sender. To prevent the preceding cases, enable the source
route filtering function. Then the MA5616 performs validity check on IP packets and drops
the packets that match the source route options.
Configure the MAC address filtering function.

Run the security mac-filter command to enable the MAC address filtering function.
The MAC addresses that are dynamically learned by the host and the source MAC addresses
that are statically configured by running the security mac-filter source command share
the four entries for source MAC addresses on the board. The entries for the statically
configured MAC addresses are of a higher priority than that of the dynamically learned
MAC addresses.
Application scenario: To prevent users from forging the MAC address of the network-side
device, or forging certain renowned MAC addresses, set the MAC address of the networkside as the MAC address to be filtered.
----End
Example
To enable the global anti-DoS attack function, enable anti-IP attack function, and the function
of checking user-side ring networks, do as follows:
huawei(config)#security anti-dos enable
huawei(config)#security anti-ipattack enable
3.11.3 Preventing the Access of Illegal Users

Only the users of the permitted IP address segment can access the device, and the users of the
denied IP address segment cannot access the device. This prevents the users of illegal IP address
segments from logging in to the system, safeguarding the system.
Context
l
Each firewall can be configured with up to 10 address segments.
When adding an address segment, ensure that the start address does not repeat an existing
start address.
To delete an address segment, you only need to enter the start address of the address
segment.
Issue 02 (2013-10-08)

130

Configuration Guide
CAUTION
l To ensure the device security, apply the minimum authorization principles. That is, configure
the permitted IP address segment, and add only the necessary management IP address
segment. IP addresses other than have been specified are not permitted to access the device
through the management port.
l It is recommended that the permitted IP address segment and the denied IP address segment
should not overlap, and only the user whose IP address is in the permitted address segment
and is not in the denied address segment can access the device.
Procedure
l
Configure the permitted/denied IP address segment for the access through Telnet.
1.
Run the sysman ip-access telnet command to configure the IP address segment that
is permitted to access the device through Telnet.
2.
Run the sysman ip-refuse telnet command to configure the IP address segment that
is forbidden to access the device through Telnet.
3.
Run the sysman firewall telnet enable command to enable the firewall function for
the access through Telnet. By default, the firewall function of the system is disabled.
Configure the permitted/denied IP address segment for the access through SSH.
1.
Run the sysman ip-access ssh command to configure the IP address segment that is
permitted to access the device through SSH.
2.
Run the sysman ip-refuse ssh command to configure the IP address segment that is
forbidden to access the device through SSH.
3.
Run the sysman firewall ssh enable command to enable the firewall function for the
access through SSH. By default, the firewall function of the system is disabled.
Configure the permitted/denied IP address segment for the access through SNMP (NMS).
1.
Run the sysman ip-access snmp command to configure the IP address segment that
is permitted to access the device through SNMP.
2.
Run the sysman ip-refuse snmp command to configure the IP address segment that
is forbidden to access the device through SNMP.
3.
Run the sysman firewall snmp enable command to enable the firewall function for
the access through SNMP. By default, the firewall function of the system is disabled.
----End
Example
To enable the firewall function for the access through Telnet, and permit only the users of the
IP address segment 10.10.5.1-10.10.5.254 to log in to the device through Telnet, do as follows:
huawei(config)#sysman ip-access telnet 10.10.5.1 10.10.5.254
huawei(config)#sysman firewall telnet enable
To enable the firewall function for the access through SSH, and permit only the users of the IP
address segment 10.10.20.1-10.10.20.254 to log in to the device through SSH, do as follows:
huawei(config)#sysman ip-access ssh 10.10.20.1 10.10.20.254
huawei(config)#sysman firewall ssh enable
Issue 02 (2013-10-08)

131

Configuration Guide
To enable the firewall function for the access through SNMP, and permit only the users of the
IP address segment 10.10.20.1-10.10.20.254 to log in to the device through SNMP, do as follows:
huawei(config)#sysman ip-refuse snmp 10.10.20.1 10.10.20.254
huawei(config)#sysman firewall snmp enable
3.11.4 Enabling the Ring Network Detection on the User Side

This topic describes how to enable the ring network detection on the user side and network side
to prevent the services from being affected by the ring network.
Context
l
By default, the ring network detection is disabled.
After the ring network detection is enabled, the system automatically detects the ring
network.
CAUTION
To ensure the security of the device, it is recommended that the ring network detection is enabled.
Procedure
Step 1 Run the ring check enable command to enable the ring network detection.
Step 2 (Option) Run the ring check private-ethtype command to configure the private Ethernet
protocol type of ring network detection packets. If the default Ethernet protocol type of ring
network detection packets is the same as the existing protocol type on the network, change the
protocol type of the ring detection packets to be different from the protocol type on the network.
Step 3 (Option) Run the ring check resume-interval command to set the auto-activation interval for
the port in ring check.
After the auto-activation interval is set, when detecting a ring network, the system automatically
activates the port that sends the ring check packet.
Step 4 Run the display ring check config command to query the status of the ring network detection.
----End
Example
To enable the ring network detection, do as follows:
huawei(config)#ring check enable
huawei(config)#display ring check config
Ring check switch status
: enable
Ring check private ethtype : 0x8300
Ring check resume-interval(min) : -
Issue 02 (2013-10-08)

132

Configuration Guide
3.12 Configuring AAA

This topic describes how to configure the AAA on the MA5616, including configuring the
MA5616 as the local and remote AAA servers.
Context
AAA refers to authentication, authorization, and accounting. In the process that a user accesses
network resources, through AAA, certain rights are authorized to the user if the user passes
authentication, and the original data about the user accessing network resources is recorded.
l
Authentication: Checks whether a user is allowed to access network resources.
Authorization: Determines what network resources a user can access.
Accounting: Records the original data about the user accessing network resources.
Application Context
AAA is generally applied to the users that access the Internet in the PPPoA, PPPoE, 802.1X,
VLAN, WLAN, ISDN, or Admin Telnet (associating the user name and the password with the
domain name) mode.
NOTE
In the existing network, 802.1X and Admin Telnet correspond to the local AAA, that is, the MA5616
functions as a local AAA server; PPPoE corresponds to the remote AAA, that is, the MA5616 functions
as the client of a remote AAA server.
Figure 3-43 shows an example network of the AAA application.

Figure 3-43 Example network of the AAA application
RADIUS server
ONU
OLT
PC
HWTACACS server
The preceding figure shows that the AAA function can be implemented on the MA5616 in the
following three ways:
l
Issue 02 (2013-10-08)
The MA5616 functions as a local AAA server. In this case, the local AAA needs to be
configured. The local AAA does not support accounting.
133

Configuration Guide
The MA5616 functions as the client of a remote AAA server, and is connected to the
HWTACACS server through the HWTACACS protocol, thus implementing the AAA.
The MA5616 functions as the client of a remote AAA server, and is connected to the
RADIUS server through the RADIUS protocol, thus implementing the AAA. The RADIUS
protocol, however, does not support authorization.
Table 3-21 lists the differences between HWTACACS and RADIUS.

Table 3-21 Differences between HWTACACS and RADIUS
HWTACACS
RADIUS
Uses TCP to realize more reliable network

transmission.
Uses UDP for transmission.
Encrypts the body of HWTACACS packets,

except their header.
Encrypts only the password field of the

authenticated packets.
Separated authorization and authentication.
Concurrent processing of authentication and

authorization.
Applicable to security control.
Applicable to accounting.
Supports authorization of the configuration

commands on the router.
Does not support the authorization of the

configuration commands on the router.
3.12.1 Configuring the Local AAA

This topic describes how to configure the local AAA so that the user authentication can be
performed locally.
Context
l
The local AAA configuration is simple, which does not depend on the external server.
The local AAA supports only authentication.
Procedure
Step 1 Configure the AAA authentication scheme.
NOTE
l The authentication scheme specifies how all the users in an Internet service provider (ISP) domain are
authenticated. The system supports up to 16 authentication schemes.
l The system has a default authentication scheme named default. It can be modified, but cannot be deleted.
1.
Run the aaa command to enter the AAA mode.
2.
Run the authentication-scheme command to add an authentication scheme.
3.
Run the authentication-mode local command to configure the local authentication mode.
4.
Run the quit command to return to the AAA mode.
Step 2 Create a domain.

Issue 02 (2013-10-08)

134

Configuration Guide
NOTE
l A domain is a group of users of the same type.

l In the user name format userid@domain-name (for example, huawei20041028@huawei.net), "userid"
indicates the user name for authentication and "domain-name" followed by "@" indicates the domain
name.
l The domain name for user login cannot exceed 15 characters, and the other domain names cannot
exceed 20 characters.
1.
In the AAA mode, run the domain command to create a domain.
Step 3 Refer the authentication scheme.

NOTE
You can refer an authentication scheme in a domain only after the authentication scheme is created.
1.
In the domain mode, run the authentication-scheme command to reference the

authentication scheme.
2.
Step 4 Configure a local user.

In the AAA mode, run the local-user password command to create a local AAA user.
Step 5 Optional: Configure the user level.
In the AAA mode, run the local-userusernameprivilege levellevel command to configure the
user level. By default, the value is common user level.
----End
Example
User1 in the isp domain adopts the local server for authentication. The authentication scheme is
newscheme, the password is a123456, do as follows:
huawei(config)#aaa
huawei(config-aaa)#authentication-scheme newscheme
Info: Create a new authentication scheme
huawei(config-aaa-authen-newscheme)#authentication-mode local
huawei(config-aaa-authen-newscheme)#quit
huawei(config-aaa)#domain isp
Info: Create a new domain
huawei(config-aaa-domain-isp)#authentication-scheme newscheme
huawei(config-aaa-domain-isp)#quit
huawei(config-aaa)#local-user user1@isp password a123456
3.12.2 Configuring the Remote AAA (Based on the RADIUS

Protocol)
The MA5616 is interconnected with the RADIUS server through the RADIUS protocol to
implement authentication and accounting.
Context
l
Issue 02 (2013-10-08)
What is RADIUS:
135

Configuration Guide
Radius is short for the remote authentication dial-in user service. It is a distributed
information interaction protocol with the client-server structure. Generally, it is used to
manage a large number of distributed dial-in users.
Radius implements the user accounting by managing a simple user database.
The authentication and accounting requests of users can be passed on to the Radius
server through a network access server (NAS).
l
Working principles of RADIUS:

When a user tries to access another network (or some network resources) by setting up
a connection to the NAS through a network, the NAS forwards the user authentication
and accounting information to the RADIUS server. The RADIUS protocol specifies the
means of transmitting the user information and accounting information between the
NAS and the RADIUS server.
The RADIUS server receives the connection requests of users sent from the NAS,
authenticates the user account and password contained in the user data, and returns the
required data to the NAS.
Specification:
For the MA5616, the RADIUS is configured based on each RADIUS server group.
In actual networking, a RADIUS server group can be any of the following:
An independent RADIUS server
A pair of primary/secondary RADIUS servers with the same configuration but
different IP addresses
The following lists the attributes of a RADIUS server template:
IP addresses of primary and secondary servers
Shared key
RADIUS server type
The configuration of the RADIUS protocol defines only the essential parameters for the
information exchange between the MA5616 and the RADIUS server. To make the essential
parameters take effect, the RADIUS server group should be referenced in a certain domain.
Procedure
Step 1 Configure the authentication scheme.
NOTE
l The authentication scheme specifies how all the users in an ISP domain are authenticated.
l The system supports up to 16 authentication schemes. The system has a default accounting scheme
named default. It can only be modified, but cannot be deleted.
1.
2.
3.
Run the authentication-mode radius command to configure the authentication mode of

the authentication scheme.
4.
Run the quit command to quit the Authen mode.
Step 2 Configure the accounting scheme.

Issue 02 (2013-10-08)

136

Configuration Guide
NOTE
l The accounting scheme specifies how all the users in an ISP domain are charged.
l The system supports up to 128 accounting schemes. The system has a default accounting scheme named
default. It can be modified, but cannot be deleted.
1.
In the AAA mode, run the accounting-scheme command to add an AAA accounting
scheme.
2.
Run the accounting-mode radius command to configure the accounting mode.
3.
Run the accounting interim interval command to set the interval of real-time accounting.
By default, the interval is 0 minutes, that is, the real-time accounting is not performed.
4.
5.
Step 3 Configure the RADIUS server template.

1.
Run the radius-server template command to create an RADIUS server template and enter
the RADIUS server template mode.
2.
Run the radius-server authentication command to configure the IP address and the UDP
port ID of the RADIUS server for authentication.
NOTE
l To guarantee normal communication between the MA5616 and the RADIUS server, before
configuring the IP address and UDP port of the RADIUS server, make sure that the route between the
RADIUS server and the MA5616 is in the normal state.
l Make sure that the configuration of the RADIUS service port of the MA5616 is consistent with the
port configuration of the RADIUS server.
3.
Run the radius-server accounting command to configure the IP address and the UDP port
ID of the RADIUS server for accounting.
4.
(Optional) Run the radius-server shared-key command to configure the shared key of the
RADIUS server.
NOTE
l The RADIUS client (MA5616) and the RADIUS server use the MD5 algorithm to encrypt the
RADIUS packets. They check the validity of the packets by setting the encryption key. They can
receive the packets from each other and can respond to each other only when their keys are the
same.
l By default, the shared key of the RADIUS server is huawei.
5.
(Optional) Run the radius-server timeout command to set the response timeout time of
the RADIUS server. By default, the timeout time is 5 seconds.
The MA5616 sends the request packets to the RADIUS server. If the RADIUS server does
not respond within the response timeout time, the MA5616 re-transmits the request packets
to the RADIUS to ensure that users can get corresponding services from the RADIUS
server.
6.
(Optional) Run the radius-server retransmit command to set the maximum re-transmit
time of the RADIUS request packets. By default, the maximum re-transmit time is 3.
When the re-transmit time of the RADIUS request packets to a RADIUS server exceeds
the maximum re-transmit time, the MA5616 considers that its communication with the
RADIUS server is interrupted, and thus transmits the RADIUS request packets to another
RADIUS server.
Issue 02 (2013-10-08)

137

Configuration Guide
7.
(Optional) Run the (undo)radius-server user-name domain-included command to

configure the user name (not) to carry the domain name when transmitted to the RADIUS
server. By default, the user name of the RADIUS server carries the domain name.
l An access user is named in the format of userid@domain-name, and the part after @
is the domain name. The MA5616 classifies a user into a domain according to the
domain name.
l If an RADIUS server group rejects the user name carrying the domain name, the
RADIUS server group cannot be set or used in two or more domains. Otherwise, when
some access users in different domains have the same user name, the RADIUS server
considers that these users are the same because the names transmitted to the server are
the same.
8.

A domain is a group of users of the same type.
In the user name format userid@domain-name (for example, huawei20041028@huawei.net),
"userid" indicates the user name for authentication and "domain-name" followed by "@"
indicates the domain name.
The common domain name for login cannot exceed 15 characters, and the domain name for
802.1x authentication cannot exceed 20 characters.
1.
2.
Step 5 Use the authentication scheme.

You can use an authentication scheme in a domain only after the authentication scheme is
created.
In the domain mode, run the authentication-scheme command to use the authentication scheme.
Step 6 Use the accounting scheme.
You can use an accounting scheme in a domain only after the accounting scheme is created.
In the domain mode, run the accounting-scheme command to use the accounting scheme.
Step 7 Use the RADIUS server template.
NOTE
You can use a RADIUS server template in a domain only after the RADIUS server template is created.
1.
In the domain mode, run the radius-server template command to use the RADIUS server
template.
2.
----End
Example
User1 in the isp domain adopts the RADIUS protocol for authentication and accounting. The
accounting interval is 10 minutes, the authentication password is a123456, RADIUS server
129.7.66.66 functions as the primary authentication and accounting server, and RADIUS server
Issue 02 (2013-10-08)

138

Configuration Guide
129.7.66.67 functions as the standby authentication and accounting server. On the RADIUS
server, the authentication port ID is 1812, accounting port ID 1813, and other parameters adopt
the default values. To perform the preceding configuration, do as follows:
huawei(config)#aaa
huawei(config-aaa-authen-newscheme)#authentication-mode radius
huawei(config-aaa)#accounting-scheme newscheme
huawei(config-aaa-accounting-newscheme)#accounting-mode radius
huawei(config-aaa-accounting-newscheme)#accounting interim interval 10
huawei(config-aaa-accounting-newscheme)#quit
huawei(config-aaa)#quit
huawei(config)#radius-server template hwtest
huawei(config-radius-hwtest)#radius-server authentication 129.7.66.66 1812
secondary
huawei(config-radius-hwtest)#radius-server accounting 129.7.66.66 1813
huawei(config-radius-hwtest)#radius-server accounting 129.7.66.67 1813 secondary
huawei(config-radius-hwtest)#quit
huawei(config)#aaa
huawei(config-aaa-domain-isp)#accounting-scheme newscheme
huawei(config-aaa-domain-isp)#radius-server hwtest
3.12.3 Configuring the Remote AAA (Based on the HWTACACS

Protocol)
The MA5616 is interconnected with the HWTACACS server through the HWTACACS protocol
to implement authentication, authorization, and accounting.
Context
l
What is HWTACACS:
HWTACACS is a security protocol with enhanced functions on the base of TACACS
(RFC1492). Similar to the RADIUS protocol, HWTACACS implements multiple
subscriber AAA functions through communications with the HWTACACS server in
the client/server (C/S) mode.
HWTACACS is used for the authentication, authorization, and accounting for the 802.1
access users and management users.
Principle of HWTACACS:
Adopting the client/server architecture, HWTACACS is a protocol through which the NAS
(MA5616) transmits the encrypted HWTACACS data packets to communicate with the
HWTACACS database of the security server. The working mode is as follows:
HWTACACS authentication. When the remote user connects to the corresponding port
of the NAS, the NAS communicates with the daemon of the HWTACACS server, and
obtains the prompt of entering the user name from the daemon. Then, the NAS displays
the message to the user. When the remote user enters the user name, the NAS transmits
the user name to the daemon. Then, the NAS obtains the prompt of entering the
password, and displays the message to the user. After the remote user enters the
password, the NAS transmits the password to the daemon.
Issue 02 (2013-10-08)

139

Configuration Guide
HWTACACS authorization. After being authenticated, the user can be authorized. The
NAS communicates with the daemon of the HWTACACS server, and then returns the
accept or reject response of the authorization.
NOTE
l The HWTACACS configuration only defines the parameters used for data exchange between the
MA5616 and the HWTACACS server. To make these parameters take effect, you need to use the
HWTACACS server group in a domain.
l The settings of an HWTACACS server template can be modified regardless of whether the template
is bound to a server or not.
Procedure
Step 1 Configure the AAA authentication scheme.
The authentication scheme specifies how all the users in an ISP domain are authenticated.
The system supports up to 16 authentication schemes. The system has a default authentication
scheme named default. It can be modified, but cannot be deleted.
1.
2.
3.
Run the authentication-mode hwtacacs command to configure the authentication mode

of the authentication scheme. Use the HWTACACS protocol to authenticate users.
4.
Step 2 Configure the AAA authorization scheme.

The authorization scheme specifies how all the users in an ISP domain are authorized.
1.
In the AAA mode, run the authorization-scheme command to add an AAA authorization
scheme.
2.
Run the authorization-mode hwtacacs command to configure the authorization mode.
3.
4.
Step 3 Configure the AAA accounting scheme.

The accounting scheme specifies how all the users in an ISP domain are charged.
The system supports up to 128 accounting schemes. The system has a default accounting scheme
named default. It can be modified, but cannot be deleted.
1.
In the AAA mode, run the accounting-scheme command to add an AAA accounting
scheme.
2.
Run the accounting-mode hwtacacs command to configure the accounting mode. By

default, the accounting is not performed.
3.
Run the accounting interim interval command to set the interval of real-time accounting.
By default, the interval is 0 minutes, that is, the real-time accounting is not performed.
4.
Step 4 Configure the HWTACACS protocol.

The configuration of the HWTACACS protocol of the MA5616 is on the basis of the
HWTACACS server group. In actual networking scenarios, an HWTACACS server group can
Issue 02 (2013-10-08)

140

Configuration Guide
be an independent HWTACACS server or a combination of two HWTACACS servers, that is,

a primary server and a secondary server with the same configuration but different IP addresses.
Each HWTACACS server template contains the primary/secondary server IP address, shared
key, and HWTACACS server type.
Primary and secondary authentication, accounting, and authorization servers can be configured.
The IP address of the primary server, however, must be different from that of the secondary
server. Otherwise, the configuration of primary and secondary servers will fail. By default, the
IP addresses of the primary and secondary servers are both 0.0.0.0.
1.
Run the hwtacacs-server template command to create an HWTACACS server template

and enter the HWTACACS server template mode.
2.
Run the hwtacacs-server authentication command to configure a primary authentication

server. You can select secondary to configure a secondary authentication server.
NOTE
l To ensure normal communication between the MA5616 and the HWTACACS server, before
configuring the IP address and the UDP port of the HWTACACS server, make sure that the route
between the HWTACACS server and the MA5616 is in the normal state.
l Make sure that the HWTACACS server port of the MA5616 is the same as the port of the
HWTACACS server.
3.
Run the hwtacacs-server accounting command to configure a primary accounting server.

You can select secondary to configure a secondary accounting server.
4.
Run the hwtacacs-server authorization command to configure a primary authorization

server. You can select secondary to configure a secondary authorization server.
5.
(Optional) Run the hwtacacs-server shared-key command to configure the shared key of
the HWTACACS server.
NOTE
l The HWTACACS client (MA5616) and the HWTACACS server use the MD5 algorithm to
encrypt the HWTACACS packets. They check the validity of the packets by configuring the
encryption key. They can receive the packets from each other and can respond to each other only
when their keys are the same.
l By default, the HWTACACS server does not have a key.
6.
(Optional) Run the hwtacacs-server timer response-timeout to set the response timeout
time of the HWTACACS server.
NOTE
l If the HWTACACS server does not respond to the HWTACACS request packets within the
timeout time, the communication between the MA5616 and the current HWTACACS server is
considered interrupted.
l By default, the response timeout time of the HWTACACS server is 5s.
7.
(Optional) In the global config mode, run the hwtacacs-server accounting-stop-packet

command to configure the re-transmission mechanism of the accounting-stop packets of
the HWTACACS server.
NOTE
l To prevent the loss of the accounting packets, the MA5616 supports the re-transmission of the
accounting-stop packets of the HWTACACS server.
l By default, the re-transmit time of the accounting-stop packets of the HWTACACS server is 100.
Issue 02 (2013-10-08)

141

Configuration Guide
8.
(Optional) Run the (undo)hwtacacs-server user-name domain-included command to

configure the user name (not) to carry the domain name when transmitted to the
HWTACACS server.
l By default, the user name of the HWTACACS server carries the domain name.
l After the undo hwtacacs-server user-name domain-included command is executed,
the domain name is deleted from the user name when the client sends authentication
and authorization requests to the HWTACACS server. The domain name in the user
name of the accounting request is, however, reserved. This is to ensure that the users
can be distinguished from each other in the accounting.
9.

A domain is a group of users of the same type.
In the user name format userid@domain-name (for example, huawei20041028@huawei.net),
"userid" indicates the user name for authentication and "domain-name" followed by "@"
indicates the domain name.
The common domain name for login cannot exceed 15 characters, and the domain name for
802.1x authentication cannot exceed 20 characters.
1.
2.

created.
In the domain mode, run the authentication-scheme command to use the authentication scheme.
In the domain mode, run the accounting-scheme command to use the accounting scheme.
Step 8 Use the authorization scheme.
You can use an authorization scheme in a domain only after the authorization scheme is created.
In the domain mode, run the authorization-mode command to use the authorization scheme.
Step 9 Use the HWTACACS server template.
You can use an HWTACACS server template in a domain only after the HWTACACS server
template is created.
1.
In the domain mode, run the hwtacacs-server template command to use the HWTACACS
server template.
2.
----End
Issue 02 (2013-10-08)

142

Configuration Guide
Example
User1 in the isp domain adopts the HWTACACS protocol for authentication, authorization, and
accounting. The accounting interval is 10 minutes, the authentication password is a123456,
HWTACACS server 129.7.66.66 functions as the primary authentication, authorization, and
accounting server, and HWTACACS server 129.7.66.67 functions as the standby authentication,
authorization, and accounting server. On the HWTACACS server, the parameters adopt the
default values. To perform the preceding configuration, do as follows:
huawei(config)#aaa
huawei(config-aaa-authen-newscheme)#authentication-mode hwtacacs
huawei(config-aaa)#authorization-scheme newscheme
huawei(config-aaa-author-newscheme)#authorization-mode hwtacacs
huawei(config-aaa-author-newscheme)#quit
huawei(config-aaa-accounting-newscheme)#accounting-mode hwtacacs
huawei(config)#hwtacacs-server template hwtest
huawei(config-hwtacacs-hwtest)#hwtacacs-server authentication 129.7.66.66
huawei(config-hwtacacs-hwtest)#hwtacacs-server authentication 129.7.66.67
secondary
huawei(config-hwtacacs-hwtest)#hwtacacs-server authorization 129.7.66.66
huawei(config-hwtacacs-hwtest)#hwtacacs-server authorization 129.7.66.67 secondary
huawei(config-hwtacacs-hwtest)#hwtacacs-server accounting 129.7.66.66
huawei(config-hwtacacs-hwtest)#hwtacacs-server accounting 129.7.66.67 secondary
huawei(config-hwtacacs-hwtest)#quit
huawei(config)#aaa
huawei(config-aaa-domain-isp)#authorization-scheme newscheme
huawei(config-aaa-domain-isp)#accounting-scheme newscheme
huawei(config-aaa-domain-isp)#hwtacacs-server hwtest
3.12.4 Configuration Example of the AAA Based on the RADIUS

Protocol (802.1X Access Users)
The MA5616 is interconnected with the RADIUS server through the RADIUS protocol to
implement authentication and accounting.
Prerequisites
Service port 1 has been created.
Context
You can perform this configuration for the Internet access and multicast services in IPoE mode.
The authentication, authorization, and accounting (AAA) function can be implemented by the
RADIUS server through 802.1x authentication.
NOTE
The CCUC and CCUE control board support this function and the CCUB control board does not support
this function.
Issue 02 (2013-10-08)

143

Configuration Guide
Service Requirements
l
The MA5616 accesses services in IPoE mode.
The RADIUS server performs authentication and accounting for users in the ISP1 domain.
The RADIUS server with the IP address 129.7.66.66 functions as the primary server for
authentication and accounting.
The RADIUS server with the IP address 129.7.66.67 functions as the secondary server for
authentication and accounting.
The authentication port number is 1812, and the accounting port number is 1813.
Other parameters adopt the default settings.
Networking
Figure 3-44 shows the example network of the RADIUS authentication and accounting
application.
Figure 3-44 Example network of the RADIUS authentication and accounting application.
RADIUS server
(Master)
129.7.66.66
RADIUS server
(Backup)
129.7.66.67
user1@isp1
user2@isp2
OLT
user3@isp3
ONU
Procedure
Configure authentication scheme named newscheme (users are authenticated through RADIUS
protocol).
huawei(config)#aaa
Info: Create a new authentication scheme
huawei(config-aaa-authen-newscheme)#authentication-mode radius

Issue 02 (2013-10-08)

144

Configuration Guide
Configure accounting scheme named newscheme (users are accounted through RADIUS
protocol). the interval is 10 minutes.
Info: Create a new accounting scheme
huawei(config-aaa-accounting-newscheme)#accounting-mode radius
Step 3 Configure the RADIUS protocol.

Create RADIUS server template named hwtest with the RADIUS server 129.7.66.66 as the
primary authentication and accounting server, and the RADIUS server 129.7.66.67 as the
secondary authentication and accounting server.
huawei(config)#radius-server template hwtest
Note: Create a new server template
secondary
huawei(config-radius-hwtest)#radius-server accounting 129.7.66.66 1813
huawei(config-radius-hwtest)#radius-server accounting 129.7.66.67 1813 secondary
huawei(config-radius-hwtest)#quit
Step 4 Configure the 802.1X authentication.

Enable the 802.1X global switch. Enable the 802.1X authentication for port 1. The 802.1X needs
to be triggered by DHCP. Therefore, the DHCP-trigger authentication must be enabled.
NOTE
Service port 1 is already configured. For how to create a service port, see Creating the Ethernet Access
Service Port.
huawei(config)#dot1x enable
huawei(config)#dot1x service-port 1
huawei(config)#dot1x dhcp-trigger enable

Create a domain named isp1.
huawei(config)
#aaa
huawei(config-aaa)#domain isp1

created.
huawei(config-aaa-domain-isp1)#authentication-scheme newscheme

huawei(config-aaa-domain-isp1)#accounting-scheme newscheme
Step 8 Use the RADIUS server template.

You can use a RADIUS server template in a domain only after the RADIUS server template is
created.
Issue 02 (2013-10-08)

145

Configuration Guide
huawei(config-aaa-domain-isp1)#radius-server hwtest
huawei(config-aaa-domain-isp1)#quit
----End
Result
User 1 in ISP 1 can pass authentication only if both the user name and password are correct, and
then can log in to the MA5616. Then, the user starts to be accounted.
Configuration File
aaa
authentication-scheme newscheme
authentication-mode radius
quit
accounting-scheme
newscheme
accounting-mode
radius
accounting interim interval 10
quit
quit
radius-server template hwtest
radius-server authentication 129.7.66.66
1812
radius-server authentication 129.7.66.67 1812 secondary
radius-server accounting 129.7.66.66
1813
radius-server accounting 129.7.66.67 1813 secondary
quit
dot1x enable
dot1x service-port 1
dot1x dhcp-trigger enable
aaa
domain
isp1
accounting-scheme newscheme
radius-server
hwtest
quit
3.12.5 Configuration Example of the AAA Based on the

HWTACACS Protocol (802.1X Access Users)
The MA5616 is interconnected with the HWTACACS server through the HWTACACS protocol
to implement authentication, authorization, and accounting.
Context
You can perform this configuration for the Internet access and multicast services in IPoE mode.
The authentication, authorization, and accounting (AAA) function can be implemented by the
HWTACACS server through 802.1x authentication.
NOTE
The CCUC and CCUE control board support this function and the CCUB control board does not support
this function.
Issue 02 (2013-10-08)

146

Configuration Guide
l
The MA5616 accesses services in IPoE mode.
The HWTACACS server performs authentication, authorization, and accounting for

802.1X access users.
The user logs in to the server carrying the domain name.
The HWTACACS server with the IP address 129.7.66.66 functions as the primary server
for authentication, authorization, and accounting.
The HWTACACS server with the IP address 129.7.66.67 functions as the secondary server
for authentication, authorization, and accounting.
Networking
Figure 3-45 shows the example network of the HWTACACS authentication.
Figure 3-45 Example network of the HWTACACS authentication
HWTACACS server
(Master)
129.7.66.66
HWTACACS server
(Backup)
129.7.66.67
user1@isp1
user2@isp2
OLT
user3@isp3
ONU
Procedure
Step 1 Configure an authentication scheme.
Configure authentication scheme named newscheme (users are authenticated through
HWTACACS protocol).
huawei(config)#aaa
huawei(config-aaa-authen-newscheme)#authentication-mode hwtacacs
Step 2 Configure an authorization scheme.

Issue 02 (2013-10-08)

147

Configuration Guide
Configure authorization scheme named newscheme (users are authorized through HWTACACS
protocol).
huawei(config-aaa)#authorization-scheme newscheme
huawei(config-aaa-author-newscheme)#authorization-mode hwtacacs
huawei(config-aaa-author-newscheme)#quit

Configure accounting scheme named newscheme (users are accounted through HWTACACS
protocol), the interval is 10 minutes.
huawei(config-aaa-accounting-newscheme)#accounting-mode hwtacacs

Create HWTACACS server template named hwtest with the HWTACACS server 129.7.66.66
as the primary authentication, authorization and accounting server, and the HWTACACS server
129.7.66.67 as the secondary authentication, authorization and accounting server.
huawei(config)#hwtacacs-server template hwtest
Create a new HWTACACS-server template
huawei(config-hwtacacs-radtest)#hwtacacs-server authentication 129.7.66.66
huawei(config-hwtacacs-radtest)#hwtacacs-server authentication 129.7.66.67
secondary
huawei(config-hwtacacs-hwtest)#hwtacacs-server authorization 129.7.66.66
huawei(config-hwtacacs-hwtest)#hwtacacs-server authorization 129.7.66.67 secondary
huawei(config-hwtacacs-radtest)#hwtacacs-server accounting 129.7.66.66
huawei(config-hwtacacs-radtest)#hwtacacs-server accounting 129.7.66.67 secondary
huawei(config-hwtacacs-radtest)#quit
Step 5 Configure the 802.1X authentication.

Enable the 802.1X global switch. Enable the 802.1X authentication for port 1. The 802.1X needs
to be triggered by DHCP. Therefore, the DHCP-trigger authentication must be enabled.
NOTE
Service port 1 is already configured. For how to create a service port, see Creating the Ethernet Access
Service Port.
huawei(config)#dot1x enable
huawei(config)#dot1x service-port 1
huawei(config)#dot1x dhcp-trigger enable

Create a domain named isp1.
huawei(config)
#aaa

created.
huawei(config-aaa-domain-isp1)#authentication-scheme newscheme
Issue 02 (2013-10-08)

148

Configuration Guide
Step 8 Use the authorization scheme.

You can use an authorization scheme in a domain only after the authorization scheme is created.
huawei(config-aaa-domain-isp1)#authorization-scheme newscheme

huawei(config-aaa-domain-isp1)#accounting-scheme newscheme
Step 10 Bind the HWTACACS server template.

You can use a HWTACACS server template in a domain only after the HWTACACS server
huawei(config-aaa-domain-isp1)#hwtacacs-server hwtest
----End
Result
User 1 in ISP 1 can pass authentication only if both the user name and password are correct, and
then can log in to the MA5616. Then, the user starts to be accounted.
Configuration File
aaa
authentication-mode hwtacacs
quit
authorization-scheme newscheme
authorization-mode hwtacacs
quit
accounting-mode hwtacacs
accounting interim interval 10
quit
quit
hwtacacs-server template hwtest
hwtacacs-server authentication 129.7.66.66
hwtacacs-server authentication 129.7.66.67 secondary
hwtacacs-server authorization 129.7.66.66
hwtacacs-server authorization 129.7.66.67 secondary
hwtacacs-server accounting 129.7.66.66
hwtacacs-server accounting 129.7.66.67 secondary
quit
dot1x enable
dot1x service-port 1
dot1x dhcp-trigger enable
aaa
domain
isp1
authorization-scheme newscheme
hwtacacs-server hwtest
Issue 02 (2013-10-08)

149

Configuration Guide
3.12.6 Configuration Example of the Authentication Based on the

RADIUS Protocol (Device Management Users)
The MA5616 allows the management user of the device to log in to the system by preferring the
RADIUS authentication mode. Local authentication can be used only when the RADIUS server
is unreachable. This feature provides ISPs with flexible authentication strategies.
Prerequisites
l
The route from the MA5616 to the RADIUS server must be configured.
The management user information (user name@domain and password) must be configured
on the RADIUS server.
l
Prefer the RADIUS server to authenticate management user of domain isp1.
Local authentication can be used when the RADIUS server is unreachable.
The RADIUS server with the IP address 129.7.66.66 functions as the primary server for
authentication.
The RADIUS server with the IP address 129.7.66.67 functions as the secondary server for
authentication.
The authentication port ID is 1812.
Networking
Figure 3-46 shows the example network of RADIUS authentication.
Figure 3-46 Example network of RADIUS authentication
RADIUS server
(Backup)
129.7.66.67
RADIUS server
(Master)
129.7.66.66
user1@isp1
user2@isp2
OLT
user3@isp3
Issue 02 (2013-10-08)
ONU

150

Configuration Guide
Procedure
Configure authentication scheme named login-auth (users are authenticated through RADIUS
protocol).
huawei(config)#aaa
huawei(config-aaa)#authentication-scheme login-auth
huawei(config-aaa-authen-login-auth)#authentication-mode radius
huawei(config-aaa-authen-login-auth)#quit
Step 2 Configure the RADIUS protocol.

Create RADIUS server template named test-login with RADIUS server 129.7.66.66 as the
primary authentication server, and RADIUS server 129.7.66.67 as the secondary authentication
server.
huawei(config)#radius-server template test-login
huawei(config-radius-test-login)#radius-server authentication 129.7.66.66 1812
huawei(config-radius-test-login)#radius-server authentication 129.7.66.67 1812
secondary
huawei(config-radius-test-login)#quit
Step 3 Create a domain named isp1.

NOTE

l When the user name is in the format of userid@domain-name (for example,
huawei20041028@isp1.net), "domain-name" followed by "@" is the domain name, and "userid" is
the user name used for authentication.
l The common domain name for login cannot exceed 15 characters, and the domain name for 802.1x
authentication cannot exceed 20 characters.
huawei(config)#aaa
Step 4 Use the authentication scheme login-auth.

created.
huawei(config-aaa-domain-isp1)#authentication-scheme login-auth
Step 5 Bind the RADIUS server template test-login to the user.

You can use a RADIUS server template in a domain only after the RADIUS server template is
created.
huawei(config-aaa-domain-isp1)#radius-server test-login
Step 6 Configure the authentication mode of the management user.

In the global config mode, run the terminal user authentication-mode command to configure
the authentication of the management user to remote AAA.
Issue 02 (2013-10-08)

151

Configuration Guide
NOTE
l Only the root user can run this command.

l After the authentication of the management user is configured to remote AAA, the system prefers
RADIUS authentication (the root user is still forcible local authentication).
huawei(config)#terminal user authentication-mode aaa isp1
Step 7 (Optional) Configure the local management user of the device.

If the RADIUS server is unreachable, local authentication can be used to log in to the system.
If the RADIUS server is reachable, none of the management users can log in to the system
through local authentication, except the root user.
CAUTION
Ensure that the user name and password of the local management user are the same as those
specified on the RADIUS server. Otherwise, login to the system fails.
User Name(length<6,15>):test01
User Password(length<6,15>):
//password test01pwd, same as that on the RADIUS
server
Confirm Password(length<6,15>):
User's Level:
1. Common User 2. Operator 3. Administrator:
Error choice or the input level higher than owns
1. Common User 2. Operator 3. Administrator:3
----End
Result
l
When the RADIUS server is reachable, the management user can log in to the MA5616
through Telnet. After entering the user name and password specified on the RADIUS
server, the management user can successfully log in to the MA5616.
When the RADIUS server is unreachable:

If the local management user is configured through the terminal user name command,
the management user can successfully log in to the MA5616 through Telnet by entering
the user name and password specified on the RADIUS server.
If the local management user is not configured through the terminal user name
command, the management user cannot log in to the MA5616 through Telnet by entering
the user name and password specified on the RADIUS server.
Configuration File
aaa
authentication-scheme login-auth
authentication-mode radius
quit
quit
radius-server template test-login
Issue 02 (2013-10-08)

152

Configuration Guide
radius-server authentication 129.7.66.66 1812

radius-server authentication 129.7.66.67 1812 secondary
quit
aaa
domain isp1
radius-server test-login
quit
quit
terminal user authentication-mode aaa test-login
terminal user name
test01
//password test01pwd, same as that on the RADIUS
server
3.12.7 Configuration Example of the Authentication Based on the

HWTACACS Protocol (Device Management Users)
The MA5616 allows the management user of the device to log in to the system by preferring the
HWTACACS authentication mode. Local authentication can be used only when the
HWTACACS server is unreachable. This feature provides ISPs with flexible authentication
strategies.
Prerequisites
l
The route from the MA5616 to the HWTACACS server must be configured.
The management user information (user name@domain and password) must be configured
on the HWTACACS server.
l
Prefer the HWTACACS server to authenticate management user of domain isp1.
Local authentication can be used when the HWTACACS server is unreachable.
The HWTACACS server with the IP address 129.7.66.66 functions as the primary server
for authentication.
The HWTACACS server with the IP address 129.7.66.67 functions as the secondary server
for authentication.
The authentication port ID is 1812.
Networking
Figure 3-47 shows the example network of HWTACACS authentication.
Issue 02 (2013-10-08)

153

Configuration Guide
Figure 3-47 Example network of HWTACACS authentication

HWTACACS server
(Master)
129.7.66.66
HWTACACS server
(Backup)
129.7.66.67
user1@isp1
user2@isp2
Telnet
OLT
ONU
user3@isp3
Procedure
Configure authentication scheme named login-auth (users are authenticated through
HWTACACS protocol).
huawei(config)#aaa
huawei(config-aaa)#authentication-scheme login-auth
huawei(config-aaa-authen-login-auth)#authentication-mode hwtacacs
huawei(config-aaa-authen-login-auth)#quit

Create HWTACACS server template named test-login with HWTACACS server 129.7.66.66
as the primary authentication server, and HWTACACS server 129.7.66.67 as the secondary
authentication server.
huawei(config)#hwtacacs-server template test-login
Create a new HWTACACS-server template
huawei(config-hwtacacs-test-login)#hwtacacs-server authentication 129.7.66.66 1812
huawei(config-hwtacacs-test-login)#hwtacacs-server authentication 129.7.66.67 1812
secondary
huawei(config-hwtacacs-test-login)#quit
Step 3 Create a domain named isp1.

NOTE

l When the user name is in the format of userid@domain-name (for example,
huawei20041028@isp1.net), "domain-name" followed by "@" is the domain name, and "userid" is
the user name used for authentication.
l The common domain name for login cannot exceed 15 characters, and the domain name for 802.1x
authentication cannot exceed 20 characters.
Issue 02 (2013-10-08)

154

Configuration Guide
Step 4 Use the authentication scheme login-auth.

created.
huawei(config-aaa-domain-isp1)#authentication-scheme login-auth
Step 5 Bind the HWTACACS server template test-login to the user.

You can use a HWTACACS server template in a domain only after the HWTACACS server
huawei(config-aaa-domain-isp1)#hwtacacs-server test-login
Step 6 Configure the authentication mode of the management user.

In the global config mode, run the terminal user authentication-mode command to configure
the authentication of the management user to remote AAA.
NOTE
l Only the root user can run this command.

l After the authentication of the management user is configured to remote AAA, the system prefers
RADIUS authentication (the root user is still forcible local authentication).
huawei(config)#terminal user authentication-mode aaa isp1
Step 7 (Optional) Configure the local management user of the device.

If the HWTACACS server is unreachable, local authentication can be used to log in to the system.
If the HWTACACS server is reachable, none of the management users can log in to the system
through local authentication, except the root user.
CAUTION
Ensure that the user name and password of the local management user are the same as those
specified on the HWTACACS server. Otherwise, login to the system fails.
User Name(length<6,15>):user01
//Management user name:
user01
//Password:
test01pwd
User's Level:
1. Common User 2. Operator 3. Administrator:2
User's Appended Info(<=30 chars): aaa
----End
Issue 02 (2013-10-08)

155

Configuration Guide
Result
l
When the HWTACACS server is reachable, the management user can log in to the
MA5616 through Telnet. After entering the user name and password specified on the
HWTACACS server, the management user can successfully log in to the MA5616.
When the HWTACACS server is unreachable:

If the local management user is configured through the terminal user name command,
the management user can successfully log in to the MA5616 through Telnet by entering
the user name and password specified on the HWTACACS server.
If the local management user is not configured through the terminal user name
command, the management user cannot log in to the MA5616 through Telnet by entering
the user name and password specified on the HWTACACS server.
Configuration File
aaa
authentication-mode hwtacacs
quit
quit
hwtacacs-server template test-login
hwtacacs-server authentication 129.7.66.66 1812
hwtacacs-server authentication 129.7.66.67 1812 secondary
quit
aaa
domain isp1
hwtacacs-server test-login
quit
quit
terminal user authentication-mode aaa isp1
terminal user name
user1
//Password test01pwd, same as that on the
HWTACACS server
3.13 Configuring the ACL for Packet Filtering

This topic describes the type, rule, and configuration of the ACL on the MA5616.
Context
An access control list (ACL) is used to filter certain packets by a series of preset rules. In this
manner, the objects that need to be filtered can be identified. After the specific objects are
identified, the corresponding data packets are permitted to pass or prohibited from passing
according to the preset policy. The ACL-based traffic filtering process is a prerequisite for
configuring the QoS or user security.
Table 3-22 lists the ACL types.
Issue 02 (2013-10-08)

156

Configuration Guide
Table 3-22 ACL types

Type
Value
Range
Feature
Basic ACL
2000-2999
The rules of a standard ACL are only defined according

to the L3 source IP address for analyzing and processing
data packets.
Advanced ACL
3000-3999
The rules of an advanced ACL are defined according to

the source IP address, destination IP address, type of the
protocol over IP, and features of the protocol (including
TCP source port, TCP destination port, and ICMP
message type).
Compared with the basic ACL, the advanced ACL
contains more accurate, abundant, and flexible rules.
Link layer ACL
4000-4999
A link-layer ACL allows definition of rules according to

the link-layer information such as the source MAC
address, VLAN ID, link-layer protocol type, and
destination MAC address, and the data is processed
accordingly.
When an arrival traffic stream matches two or more ACL rules, the matching sequence is as
follows:
l
An ACL rule is valid only when it is within the period of time-range-name.
If the rules are all user-defined rules or non-user-defined rules, and are issued to the physical
port:
If the rules of an ACL are activated at the same time, the rule with larger rule-id has a
higher priority.
If the rules of an ACL are activated one by one, the rule activated later has higher priority
over the one activated earlier.
If the rules are issued to the port from different ACLs, the rule activated later has higher
priority over the one activated earlier.
If the rules are issued to the routing interface or firewall, the rule with smaller rule-id has
a higher priority. It is irrelative to the activation sequence. The rules are used to match the
packets based on rule-id in an ascending order. Once the rule with a smaller rule-id matches
the packets, its subsequent rules are not used. That is, the rules with a larger rule-id are
invalid.
Precaution
Because the ACL is flexible in use, Huawei provides the following suggestions on its
configuration:
l
Issue 02 (2013-10-08)
It is recommended that you define a general rule, such as permit any or deny any, in each
ACL, so that each packet has a matching traffic rule that determines to forward or filter the
unspecified packet.
157

Configuration Guide
The activated ACL rules share the hardware resources with the protocol modules (such as
DHCP module and IPoA module) . In this case, the hardware resources are limited and may
be insufficient. To prevent the failure of enabling other service functions due to insufficient
hardware resources, it is recommended you enable the protocol module first and then
activate ACL rules in the data configuration. If you fail to enable a protocol module, perform
the following steps:
1.
Check whether ACL rules occupy too many resources.
2.
If ACL rules occupy too many resources, deactivate or delete the unimportant or
temporarily unused ACL configurations, and then configure and enable the protocol
module.
3.13.1 Configuration Differences Between IPv4 ACLs and IPv6

ACLs
This topic describes differences regarding to Configuration between IPv4 ACLs and IPv6 ACLs.
It is recommended that you know well about how to configure IPv4 ACLs and then configure
IPv6 ACLs based on their differences.
Context
l
The configuration differences between IPv4 ACLs and IPv6 ACLs are as follows:
IPv6 and IPv4 have different IP address formats and packet formats, so the ipv6
parameter must be specified for configuring IPv6 basic ACLs and advanced ACLs. Use
the ipv6 parameter to choose between IPv4 ACLs and IPv6 ACLs.
IPv4 and IPv6 have the same link-layer packet encapsulation format, so configurations
do not differentiate IPv6 link-layer ACLs and IPv4 link-layer ACLs.
3.13.2 Configuring the Basic ACL for Packet Filtering

This topic is applicable to the scenario where the device needs to classify traffic for packets
according to the source IP address.
Context
The number of a basic ACL is in the range of 2000-2999.
A basic ACL is only defined according to the L3 source IP address for analyzing and processing
data packets.
IPv6 and IPv4 have different IP address formats and packet formats, so the ipv6 parameter must
be specified for configuring IPv6 ACLs.
Procedure
Step 1 (Optional) Set a time range.
Run the time-range command to create a time range, which can be used when an ACL rule is
created.
Step 2 Create a basic ACL.
Issue 02 (2013-10-08)

158

Configuration Guide
Run the acl command to create a basic ACL, and then enter the ACL mode. The number of a
basic ACL can only be in the range of 2000-2999.
Step 3 Configure a basic ACL rule.
In the acl-basic mode or the acl6-basic mode, run the rule command to create a basic ACL rule.
The parameters are as follows:
l rule-id: Indicates the ACL rule ID. To create an ACL rule with a specified ID, use this
parameter.
l permit: Indicates the keyword for allowing the data packets that meet related conditions to
pass.
l deny: Indicates the keyword for discarding the data packets that meet related conditions.
l time-range: Indicates the keyword of the time range during which the ACL rule will be
effective.
Step 4 Activate the ACL.
After an ACL is configured, only an ACL gets generated but it will not be functional. You need
to run other commands to activate the ACL. Some common commands are as follows:
l Run the packet-filter command to activate an ACL.
l Perform the QoS operation. For details, see Configuring Traffic Management Based on
ACL Rules.
----End
Example
To configure that from 00:00 to 12:00 on Fridays, port 0/1/0 on the MA5616 receives only the
packets from 2.2.2.2, and discards the packets from other addresses, do as follows:
huawei(config)#time-range time1 00:00 to 12:00 fri
huawei(config-acl-basic-2000)#rule deny time-range time1
huawei(config-acl-basic-2000)#rule permit source 2.2.2.2 0.0.0.0 time-range time1
huawei(config-acl-basic-2000)#quit
huawei(config)#packet-filter inbound ip-group 2000 port 0/1/0
huawei(config)#save
To configure that from 5:00 to 6:00 on Saturdays, port 0/1/0 on the MA5616 not to receive
packets from the addresses 2000::1/64, do as follows:
huawei(config)#time-range time2 5:00 to 6:00 sat
huawei(config)#acl ipv6 2001
huawei(config-acl6-basic-2001)#rule deny source 2000::1 64 time-range time2
huawei(config-acl6-basic-2001)#quit
huawei(config)#packet-filter inbound ipv6 ip-group 2001 port 0/1/0
huawei(config)#save
3.13.3 Configuring the Advanced ACL for Packet Filtering

This topic describes how to classify traffic for the data packets according to the source IP address,
destination IP address, protocol type over IP, and features for protocol, such as source port of
the TCP, destination port of the TCP, and ICMP type of the data packets.
Issue 02 (2013-10-08)

159

Configuration Guide
Context
IPv6 and IPv4 have different IP address formats and packet formats, so the ipv6 parameter must
be specified for configuring IPv6 ACLs.
The number of an advanced ACL is in the range of 3000-3999.
An advanced ACL can classify traffic according to the following information:
l
Protocol type
Source IP address
Destination IP address
Source port ID (source port of the UDP or TCP packets)
Destination port ID (destination port of the UDP or TCP packets)
ICMP packet type
Precedence value: priority field of the data packet
Type of service (ToS) value: ToS field of the data packet
Procedure
created.
Step 2 Create an advanced ACL.
Run the acl command to create an advanced ACL, and then enter the acl-adv mode. The number
of an advanced ACL can only be in the range of 3000-3999.
Step 3 Configure a rule of the advanced ACL.
In the acl-adv or the acl6-adv mode mode, run the rule command to create an ACL rule. The
parameters are as follows:
parameter.
pass.
l time-range: Indicates the keyword of the time range during which the ACL rules are
effective.
After an ACL is configured, only an ACL is generated and the ACL does not take effect. You
need to run other commands to activate the ACL. Some common commands are as follows:
l Perform the QoS operation. For details, see 3.14.4 Configuring Traffic Management Based
on ACL Rules.
----End
Issue 02 (2013-10-08)

160

Configuration Guide
Example
Assume that the port 0/1/0 of the MA5616 belongs to a VLAN, and the IP address of the VLAN
L3 interface is 10.10.10.101. To prohibit the ICMP (such as ping) and telnet operations from
the user side to the VLAN interface on the device, do as follows:
huawei(config-acl-adv-3001)rule 1 deny icmp destination 10.10.10.101 0
huawei(config-acl-adv-3001)rule 2 deny tcp destination 10.10.10.101 0 destinationport eq telnet
huawei(config-acl-adv-3001)quit
huawei(config)#packet-filter inbound ip-group 3001 rule 1 port 0/1/0
huawei(config)#packet-filter inbound ip-group 3001 rule 2 port 0/1/0
huawei(config)#save
To prohibit receiving the ICMPv6 packets from the address 2000::1/64 for the port 0/1/0 on
MA5616, do as follows.
huawei(config)#acl ipv6 3002
huawei(config-acl6-adv-3002)rule 1 deny icmpv6 source 2000::1 64
huawei(config-acl6-adv-3002)quit
huawei(config)#packet-filter inbound ipv6 ip-group 3002 rule 1 port 0/1/0
huawei(config)#packet-filter inbound ipv6 ip-group 3002 rule 2 port 0/1/0
huawei(config)#save
3.13.4 Configuring the Link Layer ACL for Packet Filtering

This topic describes how to classify traffic according to the link layer information such as source
MAC address, source VLAN ID, L2 protocol type, and destination MAC address.
Context
The number of a link layer ACL is in the range of 4000-4999.
A link layer ACL can classify traffic according to the following link layer information:
l
Protocol type over Ethernet
802.1p priority
VLAN ID
Source MAC address
Destination MAC address
Procedure
created.
Step 2 Create a link layer ACL.
Run the acl command to create a link layer ACL, and then enter the acl-link mode. The number
of a link layer ACL can only be in the range of 4000-4999.
Step 3 Configure a link layer ACL rule.
In the acl-link mode, run the rule command to create a link layer ACL rule. The parameters are
as follows:
Issue 02 (2013-10-08)

161

Configuration Guide
parameter.
pass.
l time-range: Indicates the keyword of the time range during which the ACL rule is effective.
After an ACL is configured, only an ACL is generated and the ACL does not take effect. You
need to run other commands to activate the ACL. Some common commands are as follows:
l Perform the QoS operation. For details, see 3.14.4 Configuring Traffic Management Based
on ACL Rules.
----End
Example
For port 0/1/0, to create a link layer ACL rule that allows data packets with protocol type 0x8863
(pppoe-control message), VLAN ID 12, CoS 1, source MAC address 2222-2222-2222, and
destination MAC address 00e0-fc11-4141 to pass, do as follows:
huawei(config-acl-link-4001)rule 1 permit type 0x8863 cos 1 source 12
2222-2222-2222 0000-0000-0000 destination 00e0-fc11-4141 0000-0000-0000
huawei(config-acl-basic-4001)quit
huawei(config)#packet-filter inbound link-group 4001 port 0/1/0
huawei(config)#save
3.14 Configuring QoS

This topic describes how to configure quality of service (QoS) on the MA5616 to provide endto-end quality assurance for user services.
Context
Configuring QoS in the system can provide different quality guarantees for different services.
QoS does not have a unified service model. Therefore, make the QoS plan for networkwide
services before making the configuration solution.
On the MA5616, the key points for implementing QoS are as follows:
l
Traffic management
Configuring traffic management can limit the traffic for a user service or user port.
Queue scheduling
For the service packets that are already configured with traffic management, through the
configuration of queue scheduling, the service packets can be placed into queues with
different priorities, thus implementing QoS inside the system.
In addition to the preceding key points, the MA5616 supports ACL-based traffic management.
Issue 02 (2013-10-08)

162

Configuration Guide
In the scenario where users have flexible requirements on implementing QoS for traffic streams,
the ACL can be used to implement flexible traffic classification (see 3.13 Configuring the ACL
for Packet Filtering), and then QoS can be implemented for traffic streams.
3.14.1 Configuring Traffic Management

This topic describes how to configure traffic management on the MA5616.
Overview
The MA5616 supports traffic management for the inbound and outbound traffic streams of the
system.
NOTE
For details on configuring traffic classification, see 4.6 Creating an xDSL Service Port.
In addition, the MA5616 supports rate limit on the Ethernet port and traffic suppression on
inbound broadcast packets and unknown (multicast or unicast) packets.
Configuring Traffic Management Based on Service Port

This topic describes how to configure traffic management based on service port. When
configuring a service port, you need to bind an IP traffic profile to the service port and manage
the traffic of the service port through the traffic parameters defined in the profile.
Context
Traffic management based on service port is implemented by creating an IP traffic profile and
then binding the IP traffic profile when creating the service port.
l
The system has seven default IP traffic profiles with the IDs of 06. You can run the display
traffic table ip command to query the traffic parameters of the default traffic profiles.
It is recommended that you use the default traffic profiles. A new IP traffic profile is created
only when the default traffic profiles cannot meet the requirements.
Table 3-23 lists the traffic parameters defined in the IP traffic profiles.
Issue 02 (2013-10-08)

163

Configuration Guide
Table 3-23 Traffic parameters defined in the IP traffic profiles

Item
Parameter Description
Parameters of two
rate three color
management
CIR: committed information rate

CBS: committed burst size
PIR: peak information rate
PBS: peak burst size
NOTE
l CIR is mandatory, and the other three parameters are optional. If you
configure only CIR, the system calculates the other three parameters based
on the formula. It is recommended that you configure only CIR.
l The system marks the service packets with colors according to the four
parameters. The red packet is discarded directly, and the packets of the other
two colors are marked on their DEI field in the VLAN tag, the yellow color
indicated as 1 and the green color indicated as 0.
Priority policies
The priority policies are classified into the following three types:
l user-cos: Copy the 802.1p priority in the outer VLAN tag of the
packet to the 802.1p priority in the VLAN tag of the upstream
packet.
l user-inner-cos: Copy the 802.1p priority in the inner VLAN tag
(CTag) of the packet to the 802.1p priority in the VLAN tag of the
upstream packet.
l user-tos: Copy the ToS priority in the packet to the 802.1p priority
in the VLAN tag of the upstream packet.
Scheduling
policies
There are two types of scheduling policies, which are available only to
the downstream packet:
l Tag-In-Package: The system performs scheduling according to the
802.1p priority of the packet.
l Local-Setting: It is the local priority. That is, the system performs
scheduling according to the 802.1p priority specified in the traffic
profile bound to the traffic stream.
NOTE
Upstream in this document refers to the direction from the user side to the network side, and downstream
refers to the direction from the network side to the user side.
Procedure
Step 1 Run the display traffic table ip command to query whether there is a proper traffic profile in
the system.
Check whether an existing traffic profile meets the planned traffic management parameters,
priority policy, and scheduling policy. If a proper traffic profile exists, select the profile by
specifying the profile ID. If the existing traffic profiles do not meet the requirements, create a
new IP traffic profile.
Issue 02 (2013-10-08)

164

Configuration Guide
Step 2 Run the traffic table ip command to create a traffic profile.

For the usage and parameters of this command, see the description in the Command Reference
in the related link. The following part describes only the key information in the configuration:
l The traffic management parameters must contain at least CIR, which must be assigned with
a value.
l Keyword priority must be entered to set the outer 802.1p priority of the packet. Two options
are available for setting the priority policy:
Enter a value in the range of 07 to specify a priority for the packet.
If the priority of the user-side packet is copied according to user-cos, user-inner-cos, or
user-tos, you need to enter the default 802.1p priority of the packet (a value in the range
of 07). If the user-side packet does not carry a priority, the specified default 802.1p
priority of the packet is adopted as the priority of the upstream packet.
l (Optional) Enter keyword inner-priority to set the inner 802.1p priority (the 802.1p priority
in the CTag) of the packet. Two options are available for setting the priority policy:
Enter a value in the range of 07 to specify a priority for the packet.
If the priority of the user-side packet is copied according to user-cos, user-inner-cos, or
user-tos, you need to enter the default 802.1p priority of the packet (a value in the range
of 07). If the user-side packet does not carry a priority, the specified default 802.1p
priority of the packet is adopted as the priority of the upstream packet.
l Keyword priority-policy must be entered to specify a scheduling policy for the downstream
packet. For details about the scheduling policies, see Table 3-23.
Step 3 Run the service-port command to bind a proper traffic profile.
For the usage and parameters of this command, see the description in the Command Reference
in the related link. The following part describes only the key information in the configuration:
l You need to enter parameters rx-cttr and tx-cttr and set values for the two parameters:
rx-cttr: Indicates the traffic ID in the connection receiving direction (from the network
side to the user side). When you need to set the traffic profile in the connection receiving
direction, use this parameter.
tx-cttr: Indicates the traffic ID in the connection transmitting direction (from the user
side to the network side). When you need to set the traffic profile in the connection
transmitting direction, use this parameter.
l (Optional) Enter keyword traffic-table to add or modify the traffic profile referenced by the
service port.
l (Optional) Enter keyword user-encap to select the encapsulation type of the packets on the
user side:
When the encapsulation type of the packets on the user side is IPoE, select ipoe.
When the encapsulation type of the packets on the user side is PPPoE, select pppoe.
----End
Example
Assume that the CIR is 2048 kbit/s, 802.1p priority of the upstream packet is 6, and the scheduling
policy of the downstream packet is Tag-In-Package. To add traffic profile 9 with these settings,
do as follows:
Issue 02 (2013-10-08)

165

Configuration Guide
huawei(config)#traffic table ip index 9 cir 2048 priority 6 priority-policy tag-InPackage

Create traffic descriptor record successfully
-----------------------------------------------TD Index
: 9
TD Name
: ip-traffic-table_9
Priority
: 6
Copy Priority
: Mapping Index
: CTAG Mapping Priority: CTAG Mapping Index
: CTAG Default Priority: 0
Priority Policy
: tag-pri
CIR
: 2048 kbps
CBS
: 67536 bytes
PIR
: 4096 kbps
PBS
: 133072 bytes
Color Mode
: color-blind
Referenced Status
: not used
-----------------------------------------------huawei(config)#display traffic table ip index 9
-----------------------------------------------TD Index
: 9
TD Name
Priority
: 6
Copy Priority
: Mapping Index
Priority Policy
: tag-pri
CIR
: 2048 kbps
CBS
: 67536 bytes
PIR
: 4096 kbps
PBS
: 133072 bytes
Color Mode
: color-blind
Referenced Status
: not used
------------------------------------------------
Configuring Rate Limitation on an Ethernet Port

This topic describes how to configure upstream rate limitation on a specified Ethernet port.
Prerequisites
The Ethernet board must be configured in the system.
Context
l
Rate limitation on an Ethernet port is valid only to the Ethernet board.
Traffic streams exceeding the specified rate are discarded.
Procedure
Step 1 In the global config mode, run the line-rate command to configure upstream rate limitation on
a specified Ethernet port.
The main parameters are as follows:
l inbound: Indicates the input direction of a port.
l outbound: Indicates the output direction of a port.
Issue 02 (2013-10-08)

166

Configuration Guide
l target-rate: Indicates the limited rate of the port, in the unit of kbit/s.
l port: Indicates the shelf ID/slot ID/port ID.
Step 2 You can run the display qos-info line-rate port command to query the configured rate limitation
on the specified Ethernet port
----End
Example
To limit the rate of Ethernet port 0/0/1 to 6400 kbit/s, do as follows:
huawei(config)#line-rate outbound 6400 port 0/0/1
huawei(config)#display qos-info line-rate port 0/0/1
line-rate:
port 0/0/1:
Outbound:
line rate: 6400 Kbps
Configuring Rate Limitation Based on a User

In the user-based rate limitation, the voice service, IPTV service, and Internet access service of
each user share a total user bandwidth. When either of the services carries no traffic, the other
services can hold a burst of the total user bandwidth so that the total user bandwidth can be
managed in a unified manner.
Context
The voice service, IPTV service, and Internet access service of each user share a total user
bandwidth. The service with the highest class of service (CoS) priority is ensured first. When
other services carry no traffic, the only service can hold a burst of the total user bandwidth. The
multicast bandwidth is determined by the bandwidth of ordered programs. The total bandwidth
of ordered programs cannot exceed the total user bandwidth. The voice service uses a fixed
bandwidth.
Procedure
l
For ADSL2+ and VDSL access users.

Each port corresponds to a user. By limiting the upstream/downstream rate of the port, set
the maximum upstream/downstream rate to the total user bandwidth.
1.
Set the maximum upstream/downstream rate to the total user bandwidth.

For the ADSL2+ access mode:
Issue 02 (2013-10-08)
a.
Run the adsl line-profile quickadd command to quickly add an ADSL2+

line profile, or run the interactive adsl line-profile add command to add an
ADSL2+ line profile.
b.
Run the adsl channel-profile quickadd command to quickly add an ADSL2

+ channel profile, or run the interactive adsl channel-profile add command
to add an ADSL2+ channel profile. In the channel profile, configure the
maximum upstream and downstream rates to limit the user bandwidth.
167

Configuration Guide
c.
Run the adsl line-template quickadd command to quickly add an ADSL+

line template, or run the interactive adsl line-template add command to add
an ADSL2+ line template.
For the VDSL (common mode) access mode:

a.
Run the vdsl line-profile quickadd command to quickly add a VDSL line
profile, or run the interactive vdsl line-profile add command to add a VDSL
line profile.
b.
Run the vdsl channel-profile quickadd command to quickly add a VDSL

channel profile, or run the interactive vdsl channel-profile add command to
add a VDSL channel profile. In the channel profile, configure the maximum
upstream and downstream rates to limit the user bandwidth.
c.
Run the vdsl line-template quickadd command to quickly add a VDSL2 line
template, or run the interactive vdsl line-template add command to add a
VDSL2 line template.
For the VDSL (TI mode) access mode:

a.
Run the vdsl service-profile quickadd command to quickly add a VDSL2

service profile, or run the interactive vdsl service-profile add command to
add a VDSL2 service profile.
b.
Run the vdsl spectrum-profile quickadd command to quickly add a VDSL2

spectrum profile, or run the interactive vdsl spectrum-profile add command
to add a VDSL2 spectrum profile.
For the VDSL (TR165 mode) access mode:

a.
Run the xdsl data-rate-profile quickadd command to quickly add a VDSL2

rate profile, or run the interactive xdsl data-rate-profile add command to
add a VDSL2 rate profile. Set the line rate in the rate profile.
b.
Run the xdsl mode-specific-psd-profile quickadd command to quickly add

a VDSL2 PSD profile, or run the interactive xdsl mode-specific-psd-profile
add command to add a VDSL2 PSD profile.
c.
Run the xdsl line-spectrum-profile quickadd command to quickly add a

VDSL2 spectrum profile, or run the interactive xdsl line-spectrum-profile
add command to add a VDSL2 spectrum profile.
2.
Run the traffic table ip command to create an IP traffic profile to configure the CoS
priority of each service and ensure the CIR and PIR. Here, the PIR is equal to the total
user bandwidth. When other services carry no traffic, each service can hold a burst of
the total user band width.
The CoS priorities of services are voice service, IPTV service, and Internet access
service in a descending order.
3.
Run the service-port command to create service ports of the services, using the IP
traffic profile created in Step 2.
4.
Run the queue-scheduler strict-priority command to configure queue scheduling

mode of the port to strict priority queue scheduling.
----End
Example
Assume that under ADSL port 0/2/0, a user is provided with the VoIP, IPTV, and Internet access
services. Set the total user bandwidth to 10 Mbit/s (that is, set the downstream maximum rate
Issue 02 (2013-10-08)

168

Configuration Guide
to 10 Mbit/s in the channel configuration profile). In the case that any two services carry no
traffic, the third service can hold a burst of the total user bandwidth. To perform such a
configuration with the following parameters, do as follows:
l
Service port 100 of the Internet access service uses traffic profile 10, with the CIR 2 Mbit/
s and the 802.1p priority 4.
Service port 101 of the VoIP service uses traffic profile 11, with the CIR 1 Mbit/s and the
802.1p priority 6.
Service port 102 of the IPTV service uses traffic profile 12, with the packet rate not limited
and the 802.1p priority 5.
huawei(config)#adsl line-profile quickadd 10

huawei(config)#adsl channel-profile quickadd 10 rate 32 32 10240 32 32 6000
huawei(config)#adsl line-template quickadd 10 channel1 10 10 60 channel2 10
huawei(config)#interface adsl 0/2
huawei(config-if-adsl-0/2)#deactivate 0
huawei(config-if-adsl-0/2)#activate 0 template-index 10
huawei(config-if-adsl-0/2)#quit
huawei(config)#traffic table ip index 10 cir 2048 pir 10240 priority 4 prioritypolicy local-Setting
huawei(config)#service-port 100 vlan 2 adsl 0/2/0 vpi 0 vci 35 multi-service uservlan 20 rx-cttr 10 tx-cttr 10
huawei(config)#traffic table ip index 11 cir 1024 pir 10240 priority 6 prioritypolicy local-Setting
huawei(config)#traffic table ip index 12 cir off priority 5 priority-policy localSetting
huawei(config)#queue-scheduler strict-priority
Configuring Traffic Suppression

This topic describes how to configure traffic suppression. The purpose of traffic suppression is
to ensure the provisioning of the normal service of system users by suppressing the broadcast,
unknown multicast, and unknown unicast packets received by the system.
Context
Traffic suppression can be configured based on the port of a board.
Procedure
Step 1 Run the interface eth command to enter the ETH mode.
Step 2 Query the thresholds of traffic suppression.
Run the display traffic-suppress all command to check whether the thresholds of traffic
suppression meets the service requirements.
Step 3 Run the traffic-suppress command to suppress the traffic of the port.
The main parameters are as follows:
l broadcast: Suppresses the broadcast traffic.
l multicast: Suppresses the unknown multicast traffic.
l unicast: Suppresses the unknown unicast traffic.
Issue 02 (2013-10-08)

169

Configuration Guide
l value value: Indicates the index of the traffic suppression level. The index value is the value
queried in Step 2.
----End
Example
To suppress the broadcast packets according to traffic suppression level 8 on port 0 on the board
in slot 0/0, do as follows:
huawei(config-if-eth-0/0)#display traffic-suppress 0
Traffic suppression ID definition:
--------------------------------------------------------------------NO. Min bandwidth(kbps) Max bandwidth(kbps) Package number(pps)
--------------------------------------------------------------------1
6
145
12
2
12
291
24
3
24
582
48
4
48
1153
95
5
97
2319
191
6
195
4639
382
7
390
9265
763
8
781
18531
1526
9
1562
37063
3052
10
3125
74126
6104
11
6249
148241
12207
12
12499
296483
24414
13
0
0
0
----------------------------------------------------------------------------------------------------------------------------------------Current traffic suppression index of broadcast
: 7
Current traffic suppression index of multicast
: 7
Current traffic suppression index of unknown unicast : 7
--------------------------------------------------------------------huawei(config-if-eth-0/0)#traffic-suppress all broadcast value 8
huawei(config-if-eth-0/0)#display traffic-suppress 0
Traffic suppression ID definition:
--------------------------------------------------------------------NO. Min bandwidth(kbps) Max bandwidth(kbps) Package number(pps)
--------------------------------------------------------------------1
6
145
12
2
12
291
24
3
24
582
48
4
48
1153
95
5
97
2319
191
6
195
4639
382
7
390
9265
763
8
781
18531
1526
9
1562
37063
3052
10
3125
74126
6104
11
6249
148241
12207
12
12499
296483
24414
13
0
0
0
----------------------------------------------------------------------------------------------------------------------------------------Current traffic suppression index of broadcast
: 8
Current traffic suppression index of multicast
: 7
Current traffic suppression index of unknown unicast : 7
---------------------------------------------------------------------
Issue 02 (2013-10-08)

170

Configuration Guide
3.14.2 Configuring Queue Scheduling

This topic describes how to configure the queue scheduling so that the services with different
priorities have different scheduling policies. Then, the corresponding QoS of these services can
be ensured.
Context
The queue scheduling policy of the MA5616 is configured according to the service type. That
is, the VoIP service priority is usually set to 6, the video service priority is usually set to 4, and
the Internet service priority is usually set to 0. When congestion occurs, the system ensures that
the traffic stream with a higher priority is processed in time, and also ensures the QoS of services
with a lower priority.
Configuring the Queue Scheduling Mode

This topic describes how to configure the queue scheduling mode for ensuring that packets in
the queue with a higher priority can be processed in time in case of congestion.
Context
The MA5616 supports three queue scheduling modes: strict-priority queue (PQ), weighted round
robin (WRR), and PQ+WRR.
l
PQ
The PQ gives preference to packets in a queue with a higher priority. The packets of a lower
priority queue can be transmitted only when a queue with a higher priority is empty.
By default, the system adopts the PQ mode.
WRR
The system supports WRR for eight queues. Each queue has a weight value for resource
acquisition. In the WRR scheduling mode, the queues are scheduled in turn, which ensures
that each queue can be scheduled.
Table 3-24 lists the mapping between the queue weights and the actual queues.
Table 3-24 Mapping between the queue weights and the actual queues
Issue 02 (2013-10-08)
Queue Number
Configured Weight
Actual Queue Weight (Port

Supporting Eight Queues)
W7
W7
W6
W6
W5
W5
W4
W4
W3
W3
W2
W2
W1
W1

171

Configuration Guide
Queue Number
Configured Weight
Actual Queue Weight (Port

Supporting Eight Queues)
W0
W0
Wn: Indicates the weight of queue n. The weight sum of the queues must be equal to 0 or
100, where 0 indicates that the strict PQ scheduling mode is used.
l
PQ+WRR
The system schedules some queues by PQ and schedules the other queues by WRR.
When the specified WRR value is 0, it indicates that the queue is scheduled in the PQ
mode.
The queue scheduled in the PQ mode should be the queue that has the highest priority.
The weight sum of the scheduled queues must be equal to 100.
Procedure
Step 1 Run the queue-scheduler command to configure the queue scheduling mode.
Step 2 Run the display queue-scheduler command to query the configuration information about the
queue scheduling mode.
----End
Example
To adopt the WRR scheduling mode and set the weight values of the eight WRR queues to 10,
10, 20, 20, 10, 10, 10, and 10 respectively, do as follows:
huawei(config)#queue-scheduler wrr 10 10 20 20 10 10 10 10
huawei(config)#display queue-scheduler
Queue scheduler mode : WRR
--------------------------------Queue Scheduler Mode WRR Weight
--------------------------------0 WRR
10
1 WRR
10
2 WRR
20
3 WRR
20
4 WRR
10
5 WRR
10
6 WRR
10
7 WRR
10
---------------------------------
To adopt the PQ+WRR scheduling mode and set the weight values of the six queues (0 to 5) to
20, 20, 10, 30, 10, and 10 respectively, do as follows:
huawei(config)#queue-scheduler wrr 20 20 10 30 10 10 0 0
huawei(config)#display queue-scheduler
Queue scheduler mode : WRR
--------------------------------Queue Scheduler Mode WRR Weight
--------------------------------0 WRR
20
1 WRR
20
2 WRR
10
Issue 02 (2013-10-08)

172

Configuration Guide
3 WRR
30
4 WRR
10
5 WRR
10
6 PQ
-7 PQ
----------------------------------
Configuring the Mapping Between the Queue and the 802.1p Priority
This topic describes how to configure the mapping between the queue and the 802.1p priority
so that packets with different 802.1p priorities are mapped to the specified queues based on the
configured mapping. This enhances the flexibility of mapping packets to queues.
Context
l
The configuration is valid to all the service boards in the system.
By default, the mapping between the queue and the 802.1p priority is as listed in Table
3-25.
Table 3-25 Mapping between the queue and the 802.1p priority
Queue Number
Actual Queue Number

(Port Supporting Eight
Queues)
802.1p Priority
Procedure
Step 1 Run the cos-queue-map command to configure the mapping between the 802.1p priority and
the queue.
Step 2 Run the display cos-queue-map command to query the mapping between the 802.1p priority
and the queue.
----End
Example
To map 802.1p priority 0 to queue 0, 802.1p priority 1 to queue 2, and the other 802.1p priorities
to queue 6, do as follows:
Issue 02 (2013-10-08)

173

Configuration Guide
huawei(config)#cos-queue-map cos0 0 cos1 2 cos2 6 cos3 6 cos4 6 cos5 6 cos6 6 cos7

6
huawei(config)#display cos-queue-map
CoS and queue map:
-----------------------CoS
Queue ID
-----------------------0
0
1
2
2
6
3
6
4
6
5
6
6
6
7
6
------------------------
Configuring the Queue Depth

This topic describes how to configure the queue depth (the queue buffer space) to re-allocate
buffer space to the queues, thus to improve the flexibility of QoS.
Context
The queue depth determines the capability of a queue for processing burst packets. The greater
the queue depth, the larger the buffer space, and the more capable is the queue in processing
burst packets.
The queue depth of the port is allocated on a percentage basis. Table 3-26 lists the default queue
depths of the system.
Table 3-26 Queue depth allocation
Queue Number
Queue Depth (Port Supporting Eight

Queues)
L7 (default: 6)
L6 (default: 25)
L5 (default: 12)
L4 (default: 12)
L3 (default: 13)
L2 (default: 13)
L1 (default: 6)
L0 (default: 13)
Ln: Indicates the depth of queue n. The sum of all the queue depths must be equal to 100.
Issue 02 (2013-10-08)

174

Configuration Guide
Procedure
Step 1 Run the queue-buffer command to configure the queue depth of the service board.
Step 2 Run the display queue-buffer command to query the queue depth of the current service board.
----End
Example
To set the queue depths to 20, 20, 10, 10, 10, 10, 10, and 10, do as follows:
huawei(config)#queue-buffer 20 20 10 10 10 10 10 10
huawei(config)#display queue-buffer
-----------------------Queue
Depth size ratio
-----------------------0
20
1
20
2
10
3
10
4
10
5
10
6
10
7
10
------------------------
3.14.3 Configuring Early Drop

This topic describes how to configure early drop. The early drop function enables a device to
discard packets based on the specified rule to provide bandwidth for required services. This
operation prevents network congestion deterioration.
Context
Early drop means that the system discards the packets that wait to enter the queue when
congestion occurs. This process occurs after traffic management. The MA5616 supports the
following early drop functions:
l
Early drop of color-based packets

Early drop based on the IP traffic profile: Packets transmitted at different rates are
identified by different colors based on the values of CIR and PIR defined in the IP traffic
profile. During network congestion, the packets identified in yellow are discarded first.
Early drop based on the weighted random early discard (WRED) profile: Packets
identified in green or yellow are discarded based on the early drop threshold and discard
rate.
Early drop of priority-based packets

Packets in a queue are discarded based on the early drop threshold (default value: 100%,
which cannot be configured) of class of service (CoS) priorities.
Configuring Priority-based Early Drop of Packets

This topic describes how to configure priority-based early drop of packets so that the
MA5616 discards packets in a queue based on different priorities during network congestion.
Issue 02 (2013-10-08)

175

Configuration Guide
Context
If the number of packets with a specified class of service (CoS) priority in a queue reaches the
threshold, which is also 100% of the queue depth, the other packets with the same priority are
not transmitted to the queue, but are discarded. The early drop threshold cannot be configured,
and the system uses the default value 100%.
NOTE
The CCUB and CCUE control board supports this function, and the CCUC control board does not support this
function.
Procedure
Step 1 Configure the early drop mode.
In global config mode, run the early-dropmode pri-base command to configure the early drop
mode to priority-based. After the configuration, the system enables the early drop function based
on the 802.1p priority at the outer layer of packets. When congestion occurs in a queue, the
system discards packets based on the discard threshold of each priority.
Step 2 Query the configured early drop mode.
Run the display early-drop mode command to verify that the early drop mode is successfully
configured.
----End
Example
To configure early drop of priority-based packets, run the following command:
huawei(config)#early-drop mode pri-base
huawei(config)#display early-drop mode
Current early-drop mode : pri-base
Configuring Color-based Early Drop of Packets (Based on an IP Traffic Profile)

This topic describes how to configure color-based early drop of packets so that the MA5616
discards packets identified in yellow in a queue during network congestion.
Prerequisites
The color mode of the IP traffic profile has been set to color-aware. You can run the traffic
table ip command to configure this parameter.
Context
The system identifies packets in different colors based on the values of CIR and PIR defined in
the IP traffic profile. You can run the display traffic table ip command to query parameters in
the IP traffic profile.
l
Issue 02 (2013-10-08)
If the transmission rate of a packet is greater than the value of PIR, the packet is identified
in red and is directly discarded.
176

Configuration Guide
If the transmission rate of a packet is less than or equal to the value of PIR and greater than
the value of CIR, the packet is identified in yellow and is discarded during network
congestion.
If the transmission rate of a packet is less than or equal to the value of CIR, the packet is
identified in green and is not discarded even during network congestion.
NOTE
The CCUB and CCUE control board supports this function, and the CCUC control board does not support this
function.
Procedure
Step 1 Configure the early drop mode.
In global config mode, run the early-drop mode color-base command to configure the early
drop mode to color-based.
After the configuration, the system transmits green packets at any time and yellow packets that
are transmitted at a rate within the specified range. If the transmission rate of a yellow packet
exceeds the rate range, the system discards the yellow packet.
Step 2 Query the configured early drop mode.
Run the display early-drop mode command to verify that the early drop mode is successfully
configured.
----End
Example
To configure early drop of color-based packets, run the following command:
huawei(config)#early-drop mode color-base
huawei(config)#display early-drop mode
Current early-drop mode : color-base
Configuring Color-based Early Drop of Packets (Based on a WRED Profile)

This topic describes how to configure early drop, which is based on a WRED profile and is
applicable to the dropping policy settings for the packets that wait to enter the queue. The
MA5616 supports early drop by color.
Context
Early drop means that the system drops the packets that wait to enter the queue when congestion
occurs. This process occurs after traffic management.
The MA5616 supports early drop by color according to the parameters in the IP traffic profile.
The system drops the yellow packets that wait to enter the queue when congestion occurs.
NOTE
The CCUC and CCUE control board supports this function, and the CCUB control board does not support this
function.
Issue 02 (2013-10-08)

177

Configuration Guide
Procedure
Step 1 Add the weighted random early detection (WRED) profile.
Run the wred-profile command to add the WRED profile.
Step 2 (Optional) Query the information about the WRED profile.
Run the display wred-profile command to verify that the WRED profile information is correct.
Step 3 Bind a queue with a WRED profile.
Run the queue-wred command to bind a queue with a WRED profile.
----End
Example
Assume the following configurations: The WRED profile ID is 0; the green packets are not
dropped; the lower threshold of dropping the yellow packets is 50; the upper threshold of
dropping the yellow packets is 80; the packet drop rate is 100. To bind such a WRED profile
with queue 0, do as follows:
huawei(config)#wred-profile index 0 green low-limit 100 high-limit 100 discardprobability 0
yellow low-limit 50 high-limit 80 discard-probability 100
huawei(config)#display wred-profile all
Command:
display wred-profile all
-----------------------------------------------------------------WRED profile index: 0
Low-limit(%)
High-limit(%)
Discard-probability(%)
Green:
100
100
0
Yellow:
50
80
100
Queue ID: -----------------------------------------------------------------huawei(config)#queue-wred queue0 0
{ <cr>|queue1<K>|queue2<K>|queue3<K>|queue4<K>|queue5<K>|queue6<K>|queue7<K> }:
Command:
queue-wred queue0 0
3.14.4 Configuring Traffic Management Based on ACL Rules

The ACL can be used to implement flexible traffic classification according to user requirements.
After traffic classification based on ACL rules is completed, you can perform QoS for the traffic
streams.
Controlling the Traffic Matching an ACL Rule

This topic describes how to control the traffic matching an ACL rule on a specified port, and
process the traffic that exceeds the limit.
Prerequisite
The ACL and the rule of the ACL are configured, and the port for traffic limit is working in the
normal state.
Issue 02 (2013-10-08)

178

Configuration Guide
Context
l
The traffic limit is only effective for the permit rules of an ACL.
The limited traffic must be an integer multiple of 64 kbit/s.
Procedure
Step 1 Run the traffic-limit command to control the traffic matching an ACL rule on a specified port.
Packets are discarded when the received traffic on a port exceeds the limit.
Step 2 Run the display qos-info traffic-limit port command to query the traffic limit information on
the specified port.
----End
Example
To limit the traffic that matches ACL 2001 received on port 0/1/0 to 512 kbit/s, do as follows:
huawei(config)#traffic-limit inbound ip-group 2001 512 port 0/1/0
huawei(config)#display qos-info traffic-limit port 0/1/0
traffic-limit:
port 0/1/0:
Inbound:
Matches: Acl 2001 rule 5
running
Target rate: 512 Kbps
Exceed action: drop
Adding a Priority Tag to the Traffic Matching an ACL Rule

This topic describes how to add a priority tag to the traffic matching an ACL rule on a specified
port so that the traffic can obtain the service that match the specified priority. The priority tag
type can be 802.1p.
Prerequisite
The ACL and the rule of the ACL are configured, and the port for traffic priority is working in
the normal state.
Context
The traffic priority is only valid to permit rules of an ACL.
Procedure
Step 1 Run the traffic-priority command to add a priority tag to the traffic matching an ACL rule on
a specified port.
Step 2 Run the display qos-info traffic-priority port command to query the configured priority.
----End
Issue 02 (2013-10-08)

179

Configuration Guide
Example
To add a priority tag to the traffic that matches ACL 2001 received on port 0/1/0, and the local
priority of the traffic is 0 , do as follows:
huawei(config)#traffic-priority inbound ip-group 2001 local-precedence 0 port 0/1/0
huawei(config)#display qos-info traffic-priority port 0/1/0
traffic-priority:
port 0/1/0:
Inbound:
Matches: Acl 2001 rule 5 running
Priority action: local-precedence 0
Enabling the Statistics Collection of the Traffic Matching an ACL Rule

This topic describes how to enable the statistics collection of the traffic matching an ACL rule,
thus analyzing and monitoring the traffic.
Prerequisite
The ACL and the rule of the ACL are configured, and the port for traffic statistics is working in
the normal state.
Context
The traffic statistics are only valid to permit rules of an ACL.
Procedure
Step 1 Run the traffic-statistic command to enable the statistics collection of the traffic matching an
ACL rule on a specified port.
Step 2 Run the display qos-info traffic-statistic port command to query the statistics information
about the traffic matching an ACL rule on a specified port.
----End
Example
To enable the statistics collection of the traffic that matches ACL 2001 received on port 0/0/1,
do as follows:
huawei(config)#traffic-statistic inbound ip-group 2001 port 0/0/1
huawei(config)#display qos-info traffic-statistic port 0/0/1
traffic-statistic:
port 0/0/1:
Inbound:
0 packet
running
Enabling the Mirroring of the Traffic Matching an ACL Rule

This topic describes how to mirror the traffic matching an ACL rule on a port to a specified port.
Mirroring does not affect packet receipt and transmission on the mirroring source port. You can
Issue 02 (2013-10-08)

180

Configuration Guide
monitor the traffic of the mirroring source port by analyzing the traffic that passes the mirroring
destination port.
Prerequisite
The ACL and the rule of the ACL are configured, and the port for traffic mirroring is working
in the normal state.
Context
l
The traffic mirror is only valid to permit rules of an ACL.
The destination mirroring port cannot be an aggregation port.
The system supports only one mirroring destination port and the mirroring destination port
can be the upstream port or the METH port.
Procedure
Step 1 Run the traffic-mirror command to enable the mirroring of the traffic matching an ACL rule
on a specified port.
Step 2 Run the display qos-info traffic-mirror port command to query the mirroring information
about the traffic matching an ACL rule on a specified port.
----End
Example
To mirror the traffic that matches ACL 2001 received on port 0/1/0 to port 0/0/1, do as follows:
huawei(config)#traffic-mirror inbound ip-group 2001 port 0/1/0 to port 0/0/1
huawei(config)#display qos-info traffic-mirror port 0/1/0
traffic-mirror:
port 0/1/0:
Inbound:
Mirror to: port 0/0/1
running
3.15 Configuring Environment Monitoring

This topic provides concepts associated with environment monitoring and describes how to
configure environment monitoring on the MA5616.
3.15.1 Configuring Monitoring Through the ESC

This topic describes how to configure the H831VESC and the ESCM (MiniESC on the CLI) on
the MA5616.
Configuring the Monitoring Through the H831VESC

You can monitor the environment status of the MA5616 through its built-in virtual EMU
(environment monitoring unit) H831VESC. This topic describes how to configure the
H831VESC.
Issue 02 (2013-10-08)

181

Configuration Guide
Context
l
The H831VESC is a built-in virtual EMU of the control board on the MA5616, and the
ALARM port on the control board is connected to the external sensor through a environment
monitoring cable.
The H831VESC can be deleted and added. By default, it is added. The subnode ID is 1.
The H831VESC supports four digital parameters, all of which can be defined by users.
Among the four digital parameters,
Digital parameter 0: Empty by default.
Digital parameter 1: Indicates the cabinet door by default.
Digital parameter 2: Indicates the lightning arrester by default.
Digital parameter 3: Indicates the wiring by default.
By default, the valid levels of default digital parameters are all high levels.
Procedure
Step 1 Query the status of the H831VESC.
Run the display emu command to query the status of the H831VESC. Ensure that it is running
properly.
Step 2 Configure the digital parameters.
Run the interface emu command to enter the EMU mode.
Run the esc digital command to configure the valid level, name, and alarm ID of the digital
parameters.
Step 3 Query the environment information about the H831VESC.
Run the display esc environment info command to query the environment information about
the H831VESC.
Run the quit command to quit the H831VESC mode, and then run the save command to save
the data.
----End
Result
After the configuration, the H831VESC works in the normal state and monitors the digital
parameters set on the MA5616. When the actual level of a monitored digital parameter is
different from the valid level preset in the system, the MA5616 reports an alarm.
Example
Table 3-27 shows the parameter plan for configuring the H831VESC.
Issue 02 (2013-10-08)

182

Configuration Guide
Table 3-27 Data plan for configuring the H831VESC

Item
Data
Remarks
Digital
parameters
Digital parameter ID: 0
In the F01S50 and F01S100 cabinets, digital

parameter 0 is used to monitor the
temperature. In the F01E50 cabinet, digital
parameter 0 does not take effect.
Valid level of digital

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

the MA5616 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.
User-defined alarm ID of
digital parameter 0: 6
When the temperature in the cabinet is

between 67C and 73C, the MA5616 reports
an alarm.
The meanings of the alarm IDs are as follows:
0: smoke ; 1: door; 2: arrester; 3: wiring; 4:
the AC power is off; 5: UPS 6: digital userdefined alarm
Issue 02 (2013-10-08)
In the F01S50, F01S100, and F01E50

cabinets, digital parameter 1 is used to
monitor door status.

parameter 1: high level
When the high level represents the valid level,

case of high level.

Door

parameter of the door sensor is set to monitor
the door status.
When the cabinet door is open, the MA5616

reports an alarm.
In the F01S50, F01S100, and F01E50

cabinets, digital parameter 2 is used to
monitor the lightning arrester.


case of low level.

Arrester

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

183

Configuration Guide
Item
Data
Remarks
When the lightning arrester is faulty, the

MA5616 reports an alarm.
In the F01S50 cabinet, digital parameter 3

does not take effect. In the F01S100 cabinet,
digital parameter 3 is used to monitor the
wiring.


case of low level.

Fan

parameter of the fan status sensor is set to
monitor the fan status.
When the fan is faulty, the MA5616 reports

an alarm.
huawei(config)#display emu 0
EMU ID: 0
---------------------------------------------------------------------------EMU name
: H831VESC
EMU type
: H831VESC
Used or not : Used
EMU state
: Normal
Frame ID
: 0
Subnode
: 1
COM port
: RS232
---------------------------------------------------------------------------huawei(config)#interface emu 0
huawei(config-if-h831vesc-0)#esc digital 0 available-level low-level digital-alarm
6 name Temperature
huawei(config-if-h831vesc-0)#esc digital 1 available-level high-level digitalalarm 1 name Door
2 name Arrester
6 name Fan
huawei(config-if-h831vesc-0)#display esc environment info
EMU ID: 0
ESC environment state
---------------------------Digital environment info------------------------ID Name
State Value |ID Name
State Value
0 Temperature
Normal 0
|1 Door
Alarm 0
2 Arrester
Normal 0
|3 Fan
Normal 0
---------------------------------------------------------------------------huawei(config-if-h831vesc-0)#quit
huawei(config)#save
Configuring the Monitoring Through the ESCM

The ESCM is an EMU that integrates the environment monitoring board, terminal blocks, and
DIP (dual in-line package) switches. The ESCM monitors the environment parameters such as
smoke, door status, wiring, temperature, and humidity of the device, and also provides extended
Issue 02 (2013-10-08)

184

Configuration Guide
monitoring ports. This topic provides the basic information about the ESCM and describes how
to configure analog and digital parameters of the ESCM.
Prerequisites
l
The ESCM must be connected to the ESC port of the MA5616 by using a straight-through
cable when the CCUB control board is used.
The ESCM must be connected to the CON/ESC port of the MA5616 by using a two-in-one
cable when the CCUC or CCUE control board is used.
The setting of the hardware DIP switch on the ESCM must be the same as the configured
EMU subnode ID.
NOTE
For details about the settings of DIP switches, see ESCM EMU.
The sixth DIP switch on the ESCM must be set to on, which indicates that the baud rate is
19200 bit/s.
The differences between an analog parameter and a digital parameter are as follows:
Context
An analog parameter is a consecutive parameter, such as the temperature, voltage, and
current.
A digital parameter is a discrete value that indicates a state.
l
In the case of the ESCM, the system supports the following analog and digital parameters:
Analog parameters 0-1: invariably allocated by the system. You cannot modify any
parameter in these two analog parameters, except the upper and lower alarm thresholds.
Analog parameters 2-3: user-defined.
Digital parameters 0, 1, 8, and 9: invariably allocated by the system. You cannot modify
any parameter in these digital parameters, except the valid level.
Digital parameters 2-7: user-defined.
Mapping Between Monitoring Parameters and Device Ports

Table 3-28 describes the mapping between the monitoring parameters displayed on the host and
the ports on the ESCM.
Table 3-28 Mapping between the monitoring parameters displayed on the host and the ports on
the ESCM
Issue 02 (2013-10-08)
Monitoring Parameter on Host
Device Port
Temperature
Temperature
Input_-48V_0
Voltage
Analog 2
N/A
Analog 3
N/A
Wiring
JTP1 (MDF)
185

Configuration Guide
Device Port
Door
JTM1 (door status)
Digital 2
JTD1
Digital 3
JTD2
Digital 4
JTD3
Digital 5
JTD4
Digital 6
JTD5
Digital 7
JTD6
Smoke
JTD7 (smoke)
Water_Alarm
JTS1 (water)
NOTE
Before adding a user-defined analog or digital monitoring parameter, make sure that the port corresponding
to this analog or digital monitoring parameter is properly connected with an environment monitoring cable.
Procedure
Step 1 Add an EMU.
Run the emu add command to add an EMU to monitor the environment parameters of the device
so that the device runs in a stable environment.
The EMU ID is 3, the type is ESCM (MiniESC on the CLI), the subnode ID is 8, and the serial
port type is RS485.
Step 2 Configure the analog parameters.
Run the esc analog command to configure the upper/lower alarm thresholds and measurement
thresholds, thus supporting the real-time monitoring of the device through the analog parameters.
Step 3 Configure the digital parameters.
Run the esc digital command to configure the valid level, name, and alarm ID of the digital
parameters.
Step 4 Query the environment information about the ESCM.
Run the display esc environment info command to query the environment information about
the ESCM.
Run the quit command to quit the miniesc mode, and then run the save command to save the
data.
----End
Issue 02 (2013-10-08)

186

Configuration Guide
Result
After the configuration, the ESCM works in the normal state and monitors the analog and digital
parameters set on the MA5616.
l
When an analog parameter measured is not within the upper and lower alarm thresholds
preset in the system, the MA5616 reports an alarm.
When the actual level of a monitored digital parameter is different from the valid level
preset in the system, the MA5616 reports an alarm.
Example
Table 3-29 shows the data plan for adding and configuring the ESCM.
Table 3-29 Data plan for configuring the ESCM
Item
Data
Remarks
EMU
Type: ESCM (MiniESC)
The ESCM is displayed as MiniESC on the CLI.
SN: 3
Subnode ID: 8
The hardware DIP switch on the ESCM is set to

8.
NOTE
The hardware DIP switch on
the ESCM ranges from 015
and therefore the subnode
ID ranges from 015.
Ensure that the hardware
DIP switch on the ESCM is
set the same as that of the
EMU subnode on the
device.
This topic uses value 8 as an
example.
Analog
parameters
Analog parameter ID: 0
This analog parameter is set according to the

actual requirements. The built-in analog
parameter is set here to monitor the ambient
temperature of the device.
For values and details of this parameter, see the
esc analog command.
Upper alarm threshold of

analog parameter 0: 54C
When the ambient temperature of the device is

higher than 54C, the device reports an alarm.
Lower alarm threshold of

analog parameter 0: 6C
When the ambient temperature of the device is

lower than 6C, the device reports an alarm.
Analog parameter ID: 2
The user-defined humidity monitoring analog

parameter is added to monitor the ambient
humidity of the device.
For values and details of this parameter, see the
esc analog command.
Issue 02 (2013-10-08)

187

Configuration Guide
Item
Digital
parameters
Data
Remarks
Upper alarm threshold of

analog parameter 2: 75%
RH
When the ambient humidity of the device is

higher than 75% RH, the device reports an alarm.
Lower alarm threshold of

analog parameter 2: 5%
RH
When the ambient humidity of the device is

lower than 5% RH, the device reports an alarm.
Name of analog parameter

2: humidity
Alarm ID of analog
parameter 2: 2
The user-defined humidity alarm of the system

is used.
Unit of analog parameter

2: % RH
Sensor type of analog

parameter 2: voltage type
This parameter is invariably allocated by the

system, and is used to monitor the door status of
the telecommunications room. You cannot
modify any parameter of this digital parameter,
except the valid level.

parameter 1: high level
When the high level represents the valid level,

the device does not report an alarm in the case of
high level.

When the low level represents the valid level, the

device does not report an alarm in the case of low
level.
Name of digital parameter

2: Fan
It is a user-defined digital parameter and is set

according to the actual requirements. The
monitoring digital parameter of the fan unit is set
here to monitor the fan unit.
When the fan unit is faulty, the device reports an

alarm.
The meanings of the alarm IDs are as follows:
1: AC voltage; 2: AC switch; 3: battery voltage;
4: battery fuse; 5: load fuse; 6: rectifier module;
7: DC power; 8: room door; 9: thief; 10: wiring ;
11: fan; 12: fire; 13: fog; 14: water; 15: diesel;
16: smell 17: air-condition; 18: arrester; 19: DC
voltage; 20 output switch; 21: digital userdefined alarm
Issue 02 (2013-10-08)

188

Configuration Guide
huawei(config)#emu add 3 MINIESC 0 8 RS485 MiniESC

huawei(config)#interface emu 3
huawei(config-if-miniesc-3)#esc analog 0 alarm-upper-limit 54 alarm-lower-limit 6
huawei(config-if-miniesc-3)#esc analog 2 alarm-upper-limit 75 alarm-lower-limit
5 name humidity sensor-type 0 analog-alarm 2 unit %RH
huawei(config-if-miniesc-3)#esc digital 1 available-level high-level
huawei(config-if-miniesc-3)#esc digital 2 available-level low-level
digital-alarm 11 name Fan
huawei(config-if-miniesc-3)#display esc environment info
EMU ID: 3
ESC environment state
---------------------------Analog environment info-------------------------ID Name
State
Value
AlmUpper
AlmLower
Unit
0 Temperature
Normal
30.00
54
6
C
1 Input_-48V_0
Normal
54.00
60
45
Volt
2 Humidity
Low
-128.00
75
5
%RH
3 Normal
-128.00
127
-128
State Value
0 Wiring
Normal 1
|1 Door
Alarm 0
2 Fan
Normal 0
|3 Normal 1
4 Normal 1
|5 Normal 1
6 Normal 1
|7 Normal 1
8 Smoke
Normal 1
|9 Water_Alarm
Normal 1
---------------------------------------------------------------------------huawei(config-if-miniesc-3)#quit
huawei(config)#save
3.15.2 Configuring Monitoring Through the Power System

This topic describes how to configure the Power4830, SMU and H831PMU on the MA5616.
Configuring the Monitoring Through the EPS30-4815AF

The EPS30-4815AF system converts the input 220 VAC into the -48 VDC to provide the -48
VDC power. In addition, the EPS30-4815AF system can manage one battery set and monitor
other environment parameters through its EPMU03 monitoring module. This topic provides the
basic information about the EPS30-4815AF and describes how to configure data associated with
environment monitoring.
Prerequisites
l
The EPS30-4815AF must be connected to the ESC port of the control board on the
MA5616 by using a cable when the CCUB control board is used.
The EPS30-4815AF must be connected to the serial port of the control board on the
MA5616 by using a two-in-one cable when the CCUC or CCUB control board is used.
The setting of the hardware DIP switch on the EPS30-4815AF must be the same as the
setting of the EMU subnode in the environment configuration.
The sixth DIP switch on the EPS30-4815AF must be set to off, which indicates that the
baud rate is 19200 bit/s.
Context
Issue 02 (2013-10-08)

189

Configuration Guide

current.
A digital parameter is a discrete value that indicates a state.
Mapping Between Monitoring Parameters and Device Ports

Table 3-30 describes the mapping between the monitoring parameters displayed on the host and
the ports on the sensor transfer box.
Table 3-30 Mapping between the monitoring parameters displayed on the host and the ports on
the sensor transfer box
Device Port
Temperature
Temperature
Humidity
humidity
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 digital monitoring parameter, make sure that the port corresponding
to this analog or digital monitoring parameter is properly connected with an environment monitoring cable.
Procedure
Step 1 Add the EPS30-4815AF, namely, Power4830.
Run the emu add command to add the Power4830.
Step 2 In the environment monitoring configuration mode, run the display power system
parameter command to query the default configuration.
Step 3 Configure the parameters of the lead battery.
Run the power battery parameter command to configure battery parameters, including battery
management parameters, charging parameters and battery set power-off parameters, and battery
high-temperature power-off parameters. You can also use the default settings.
Step 4 (Optional) Configure the battery discharging test parameters.
l Run the power battery-test command to configure the battery discharging test parameters,
including battery auto-discharging test, timed auto-test, battery auto-discharging test period,
Issue 02 (2013-10-08)

190

Configuration Guide
time of the discharging test, end voltage of the discharging test, number of batteries of the
battery group, duration of the discharging test, simple discharging test of the battery and
prealarm threshold for battery test efficiency. You can also use the default settings.
l Run the display power battery-test info command to query the battery discharging test
information.
Step 5 Configure the parameter of the rectifier unit.
Run the power module-num command to configure the parameter of the rectifier unit.
Step 6 Configure the environment parameters for power supply monitoring.
Run the power environment command to configure the upper and lower alarm thresholds and
measurement thresholds of temperature or humidity for power monitoring. In this manner, the
power module generates alarms when it works in a condition that does not meet the present
requirements.
Step 7 Configure the external extended digital parameters for power supply monitoring.
Run the power outside_digital command to configure the external extended digital parameters
for power supply monitoring.
Step 8 Query configuration parameters and environment parameters of the power system.
Run the display power system parameter command to query configuration parameters of the
power monitoring unit.
Step 9 Run the display power alarm command to query the alarm. Ensure that no alarm (except the
door status alarm) for the monitoring parameter is generated.
Run the quit command to quit the Power4830 mode, and then run the save command to save
the data.
----End
Result
After the configuration, the EPS30-4815AF works in the normal state and monitors parameters
set on the MA5616. When a monitored parameter is abnormal, the MA5616 reports an alarm.
Example
Table 3-31 provides the data plan for configuring the power monitoring through the
EPS30-4815AF.
Table 3-31 Data plan for configuring the power monitoring through the EPS30-4815AF
Issue 02 (2013-10-08)
Item
Data
Remarks
EMU
Type: Power4830
The selected type of the EPS30-4815AF

is Power4830.
SN: 2

191

Configuration Guide
Item
Data
Remarks
Subnode ID: 4
The DIP switch on the EPS30-4815AF

is set to 4.
NOTE
The hardware DIP switch on the
EPS30-4815AF ranges from 031
and therefore the subnode ID ranges
from 031. Ensure that the
hardware DIP switch on the
EPS30-4815AF is set the same as
that of the EMU subnode on the
device.
This topic uses value 4 as an
example.
Battery
management
parameters
Current-limiting coefficient for

battery charging: 0.15
Interval of battery equalized
charging: 60 days
Number of battery sets: 1
Capacity of the battery set:
75AH
Upper measurement threshold of
the battery set temperature: 80C
Lower measurement threshold of
the battery set temperature: -20
C
You can change the configuration by

running the power battery command
according to the actual requirements.
The MA5616 can be installed in the
F01E2OOE, F01E400, or F01S300
cabinet. A 26 AH battery set is
configured for the F01E200E cabinet, a
75 AH battery set is configured for the
F01E400 cabinet, and a 50 or 92 AH
battery set is configured for the
F01S300 cabinet.
NOTE
When a 92 AH battery set is configured for
the F01S300 cabinet, the charging currentlimiting coefficien of the battery must be set
to 0.1.
Upper alarm threshold of the

battery set temperature: 50C
Lower alarm threshold of the
battery set temperature: 0C
Temperature compensation
coefficient of the battery set: 80
mV
Charging
parameters of
the battery
Charging mode of the battery:

automatic
Equalized charging voltage of

the battery: 56.5 V
Float charging voltage of the
battery: 53.5 V
Battery set
power-off
parameters
Issue 02 (2013-10-08)
Battery set power-off permission

status: permit

running the power off command
according to the actual requirements.

192

Configuration Guide
Item
Data
Remarks
Battery set power-off voltage: 43

V
Hightemperature
power-off
parameters of
the battery
Battery high-temperature
power-off permission status:
permit
Rectifier unit
parameter
Number of rectifier units: 2
The EPS30-4815AF supports up to two

rectifier units.
Environment
monitoring
parameters

temperature: 68C

running the power environment
command according to the actual
requirements.
Temperature for battery hightemperature power-off: 53C

temperature: -5C

running the power temperature-off
command according to the actual
requirements.

the temperature: 80C
the temperature: -20C
humidity: 80% RH
humidity: 10% RH
the humidity: 100% RH
the humidity: 0% RH
External
extended
digital
parameters of
the power
Issue 02 (2013-10-08)
Extended digital parameter ID: 1
Valid level of extended digital

When the low level represents the valid

level, the device does not report an
alarm in the case of low level.
Name of extended digital

parameter 1: Fan
It is a user-defined digital parameter and

is set according to the actual
requirements. The monitoring digital
parameter of the fan status sensor is set
to monitor the fan status.

193

Configuration Guide
Item
Data
Remarks
extended digital parameter 1: 11
When the fan is faulty, the MA5616

reports an alarm.
The meanings of the alarm IDs are as
follows:
1: AC voltage; 2: AC switch; 3: battery
voltage; 4: battery fuse; 5: load fuse; 6:
rectifier; 7: DC power; 8: room door; 9:
thief; 10: wiring ; 11: fan; 12: fire; 13:
smoke; 14: water; 15: diesel; 16: smell
17: air-condition; 18: arrester; 19: DC
voltage; 20 output switch; 21: digital
user-defined alarm

When the low level represents the valid

level, the device does not report an
alarm in the case of low level.
Name of extended digital

parameter 3: Arrester
It is a user-defined digital parameter and

is set according to the actual
requirements. The monitoring digital
parameter of the arrester status sensor is
set to monitor the arrester status.
extended digital parameter 3: 19
When the lightning arrester is faulty, the

MA5616 reports an alarm.
huawei(config)#emu add 2 POWER4830 0 4 RS485 POWER4830

huawei(config-if-power4830-2)#display power system parameter
EMU ID: 2
Power system information
---------------------------------------------------------------------------Charge control state: Automatic control
Equalizing voltage : 56.50V
Floating voltage
: 53.50V
Charge Lmt quotiety : 0.15
Equalizing time
: 60 days
Battery number
: 1
Battery 0 capacity
: 12 AH
Battery temperature test upper : 80C Battery temperature test lower: -20C
Temperature redeem quotiety
: 80mV
Battery temperature alarm upper: 50C Battery temperature alarm lower: -15C
Battery off permit : Permit
Battery off voltage
: 43.00V
AC over alarm volt : 280V
AC lack alarm voltage : 180V
DC over alarm volt : 58 V
DC lack alarm voltage : 45 V
Power module number : 2
Module 0 address: 1
Module 0 switch state
: On
Module 1 address: 2
: On
Battery high-temperature-off permit
: Forbid
Battery high-temperature-off temperature: 53C
Battery Efficiency Prealarm threshold: 80%
---------------------------------------------------------------------------huawei(config-if-power4830-2)#display power environment parameter
EMU ID: 2
Issue 02 (2013-10-08)
power environment configration parameter

194

Configuration Guide
-----------------------------------------------------------------------------AnalogID Name
AlmUpper AlmLower TestUpper TestLower Unit
type
0
Temperature
68
-20
80
-20
C
Current
1
Humidity
80
0
100
0
%R.H. Current
-----------------------------------------------------------------------------DigitalID Name
Available Level|DigitalID Name
Available Level
0
1
|
1
1
2
1
|
3
1
4
1
|
5
1
6
1
---------------------------------------------------------------------------huawei(config-if-power4830-2)#power battery parameter 1 0.15 60 75
huawei(config-if-power4830-2)#power module-num 2
huawei(config-if-power4830-2)#power temperature-off battery-off-state permit
huawei(config-if-power4830-2)#power environment humidity 80 10 100 0
This command is invalid unless in the condition of install the sensor, would
you continue? (y/n)[n]:y
huawei(config-if-power4830-2)#power environment temperature 68 -5 80 -20
This command is invalid unless in the condition of install the sensor, would
huawei(config-if-power4830-2)#power outside_digital 1 available-level low-level
digital_alarm 11 name Fan
huawei(config-if-power4830-2)#power outside_digital 3 available-level low-level
digital_alarm 19 name Arrester
huawei(config-if-power4830-2)#display power system parameter
EMU ID: 2
Floating voltage
: 53.50V
Equalizing time
: 60 days
Battery number
: 1
Battery 0 capacity
: 75 AH
battery temperature test upper : 80C battery temperature test lower: -20C
temperature redeem quotiety
: 80mV
battery temperature alarm upper: 50C battery temperature alarm lower: 0C
Battery off voltage
: 43.00V
module 0 address: 1
module 0 switch state
: On
module 1 address: 2
module 1 switch state
: On
: Permit
Battery high-temperature-off temperature: 53 C
---------------------------------------------------------------------------huawei(config-if-power4830-2)#display power environment parameter
EMU ID: 2
Power environment configuration parameter
---------------------------------------------------------------------------AnalogID Name
Type
0
Temperature
68
-5
80
-20
C
Current
1
Humidity
80
10
100
0
%R.H.
Current
---------------------------------------------------------------------------DigitalID Name
available Level
|DigitalID Name
available Level
0
1
|
1
Fan
0
2
1
|
3
Arrester
0
4
1
|
5
1
6
1
---------------------------------------------------------------------------huawei(config-if-power4830-2)#display power alarm
EMU ID: 2
Power alarm information
---------------------------------------------------------------------------Mains supply yes : yes
Mains supply lack : normal
Total vol lack
: Normal
Load fuse 0
: Connect
Load off
: on
battery off
: on
Battery 1 loop
: connect
Environment Temperature : Normal
Environment Humidity
: Normal
Issue 02 (2013-10-08)

195

Configuration Guide
Door alarm
: Alarm
Water alarm
: Normal
//
The "Door alarm" alarm is generated because the door of the cabinet is not closed.
Smoke alarm
: Normal
Battery Temperature alarm
: Normal
Wiring alarm
: Normal
Acinput air switch
: Normal
Battery 1 Temp-Sensor
: Invalid Environment 1 Temp-Sensor
: Invalid
Environment Humidity-Sensor : Invalid
module 0
: normal
module 1
: normal
---------------------------------------------------------------------------DigitalID Name
Alarm State|DigitalID Name
Alarm State
0
Normal |
1
Fan
Normal
2
Normal |
3
Arrester
Normal
4
Normal |
5
Normal
6
Normal
---------------------------------------------------------------------------huawei(config-if-power4830-2)#quit
huawei(config)#save
Configuring the Monitoring Through the H831PMU (Backup Power Using the
VRLA Battery)
The H831PMU is a power monitoring control module and it works with the PAIB power board
to monitor relevant information about the power system. In addition, the H831PMU can manage
a VRLA battery set. This topic provides the basic information about the H831PMU and describes
how to configure data associated with environment monitoring.
Context
The H831PMU requires an RS-485 serial port for data communication.
Procedure
Step 1 Run the emu add command to add an environment monitoring unit (EMU).
Step 2 Configure the battery management parameters.
Run the power battery parameter command to configure battery parameters, such as charging
current-limiting coefficient, timed equalized charging time, number of battery sets, and capacity
of the battery set.
Step 3 Configure the battery charging parameters.
Run the power charge command to configure the battery charging mode.
Step 4 Run the power off command to configure the power supply load power-off and battery set poweroff parameters.
Step 5 Run the power supply-parameter command to configure the parameters of the power supply.
Step 6 Run the display power system parameter command to query the configuration parameters of
the power system.
Step 7 (Optional) Configure the battery discharging test parameters.
l Run the power battery-test command to configure the battery discharging test parameters,
including battery auto-discharging test, timed auto-test, battery auto-discharging test period,
time of the discharging test, end voltage of the discharging test, number of batteries of the
battery group, duration of the discharging test, simple discharging test of the battery and
prealarm threshold for battery test efficiency. You can also use the default settings.
Issue 02 (2013-10-08)

196

Configuration Guide
l Run the display power battery-test info command to query the battery auto-discharging
test information.
Step 8 (Optional) Configure the battery high temperature power-off parameters.
Run the power temperature-off command to configure the battery high temperature power-off
parameters, including high temperature power-off status for the battery and high temperature
power-off temperature for the battery. You can also use the default settings.
Run the quit command to quit the H831PMU mode, and then run the save command to save the
data.
----End
Result
After the configuration is completed, the H831PMU works in the normal state and monitors
parameters set on the MA5616. When a monitored parameter is abnormal, the MA5616 reports
an alarm.
Example
Table 3-32 provides the data plan for configuring the power monitoring through the H831PMU.
Table 3-32 Data plan for configuring the power monitoring through the H831PMU
Item
Data
Remarks
EMU
Type: H831PMU
SN: 3
Subnode ID: 0
For values and details of the

parameters, see the power
battery command.
Battery
management
parameters

Interval of battery equalized
charging: 90 days
Capacity of the battery set: 12 AH
Charging
parameters of the
battery
Issue 02 (2013-10-08)

floating
Equalized charging voltage of the
battery: 56.8 V


charge command.
When setting the equalized and
float charging voltages of the
battery, make sure that DC
overvoltage -1 V > equalized
charging voltage > float
charging voltage > DC
197

Configuration Guide
Item
Battery set poweroff parameters
Data
Remarks
Float charging voltage of the

battery: 53.5 V
undervoltage +2 V, and that DC

undervoltage > load power-off
voltage > battery power-off
voltage.

status: permit

parameters, see the power off
command.
Battery set power-off voltage: 44 V

Power distribution
parameters
DC overvoltage alarm threshold: 59

V
DC undervoltage alarm threshold:
48 V

supply-parameter command.
huawei(config)#emu add 3 H831PMU 0 0 RS485

huawei(config-if-h831pmu-3)#power battery parameter 1 0.15 90 12
Send command to environment monitor board ,please waiting for the ack
huawei(config-if-h831pmu-3)#
Execute command successful
huawei(config-if-h831pmu-3)#power charge mode floating
huawei(config-if-h831pmu-3)#power off battery-off-state permit battery-off-voltage
44
huawei(config-if-h831pmu-3)#power supply-parameter 59 48
huawei(config-if-h831pmu-3)#display power system parameter
EMU ID: 3
---------------------------------------------------------------------------Charge control state: Remote control
Charge mode
: Floating
Floating voltage
: 56.40V
Equalizing time
: 90 days
Battery number
: 1
Battery 0 capacity
: 12 AH
: 80mV
Battery temperature alarm upper: 50C Battery temperature alarm lower: -15C
Battery off voltage
: 44.00V
Issue 02 (2013-10-08)

198

Configuration Guide
Module 0 address: 1
: On
: Forbid
---------------------------------------------------------------------------huawei(config-if-h831pmu-3)#quit
huawei(config)#save
Configuring the Monitoring Through the H831PMU (Backup Power Using the PBL
02A Fe-lithium Battery)
The H831PMU is a power monitoring control module and it works with the PAIB power board
to monitor relevant information about the power system. In addition, the H831PMU can manage
a Fe-lithium battery set. This topic describes how to configure the power monitoring through
the H831PMU (backup power using the Fe-lithium battery).
Prerequisites
l
The Fe-lithium battery must be connected to the ESC port of the MA5616 control board
by using a single communication cable when the CCUB control board is used.
The Fe-lithium battery must be connected to the serial port of the MA5616 by using a twoin-one communication cable when the CCUC or CCUB control board is used.
Context
The MA5616 supports a Fe-lithium battery set for power backup. Compared with the lead-acid
battery, the Fe-lithium battery features long lifespan, large capacity, optimized discharging
function, fast charging, and flexible environment adaptability. In addition, it supports intelligent
management so that the battery can be automatically charged or discharged.
The Fe-lithium battery is connected to the input port of the power system through a power cable
and connected to the MA5616 through an RS485 serial port cable. When detecting a Fe-lithium
battery, the MA5616 issues a command to the power system to adjust the voltage. The equalized
charging voltage of a Fe-lithium battery is 56.5V and the floating charging voltage of a Felithium battery is 56.4V.
When the mains supply fails, the Fe-lithium battery provides power for the MA5616 to ensure
the normal running of the device in a certain period. When the mains supply recovers, the Felithium battery stops discharging and starts charging.
Procedure
Step 1 Run the emu add command to add an environment monitoring unit (EMU).
Step 2 Run the power supply-parameter command to configure the parameters of the power supply.
Step 3 Run the display power system parameter command to query the configuration parameters of
the power system.
Run the quit command to quit the H831PMU mode, and then run the save command to save the
data.
Step 5 Configure the Fe-lithium battery monitoring unit.
Issue 02 (2013-10-08)

199

Configuration Guide
1.
Run the emu add command to add a Fe-lithium battery monitoring unit.
NOTE
The subnode ID of the Fe-lithium battery is invariably 23.
2.
(Optional) Run the power batteryinstall command to set the time for installing the battery.
3.
Run the display power run info command to query the battery running information, such
as the charging status and remaining power.
4.
(Optional) Run the display power batteryinstalltime command to query the time for
installing the battery.
5.
----End
Example
Assume that:
l
The EMU ID of the H831PMU is 3 and the subnode ID is 0.
The power parameters are as follows: The DC overvoltage alarm threshold is 59 V and the
DC undervoltage alarm threshold is 48 V.
The EMU ID of the Fe-lithium battery is 4 and the subnode ID is 23.
The time for installing the battery is 2011-08-20.
To configure the power monitoring through the H831PMU (backup power using the Fe-lithium
battery) with such configurations, do as follows:
huawei(config)#emu add 3 H831PMU 0 0 RS485
huawei(config-if-h831pmu-3)#power supply-parameter 59 48
huawei(config-if-h831pmu-3)#quit
huawei(config)#emu add 4 liBATTERY 0 23 rs485 battery1
huawei(config-if-libattery-4)#power batteryinstall 2011-08-20
huawei(config-if-libattery-4)#display power run info
EMU ID: 4
LiBattery run information
---------------------------------------------------------------------------Battery charge state: Charge
Battery voltage: 54.01V
Battery current: 0.82A
Battery temperature: 29C
Battery capacity specification: 10A
Battery capacity remained percentage: 97%
Battery charge or discharge number: 13
The sum of discharge capacity: 106Ah
---------------------------------------------------------------------------huawei(config-if-libattery-4)#quit
huawei(config)#save
Configuring the Monitoring Using ETP4830-A1/ETP4890

The ETP4830-A1/ETP4890 power system can power the MA5616 and be used as an independent
system power. The ETP4830-A1/ETP4890 system converts the input alternating current (AC)
power (85 VAC to 300 VAC) to stable direct current (DC) power (-48 VDC). The system can
Issue 02 (2013-10-08)

200

Configuration Guide
also be connected to battery and manage battery using a monitoring module. In addition, the
system can connect to a sensor transfer box using a DB50 port to detect analog and digital
parameters, and output control signals. This topic describes the basic information about the
ETP4830-A1/ETP4890 power system and how to configure the monitoring using the ETP4830A1/ETP4890 system.
Prerequisites
l
If the MA5616 uses the CCUB control board, the ETP4830-A1/ETP4890 system must be
connected to the ESC port on the control board using a single communication cable, and
the serial port used for the connection must match the serial port cable in use.
If the MA5616 uses the CCUC control board, the ETP4830-A1/ETP4890 system must be
connected to the serial port on the control board using a two-in-one communication cable.
Note that the RS232 and the RS485 ports are the same, and therefore the configured serial
port type must match the serial port cable in use.
Context
current.
A digital parameter is a discrete value that indicates a status.
Procedure
Step 1 Add the ETP4830-A1/ETP4890, which is also called a site management unit (SMU).
Run the emu add command to add the SMU.
Step 2 Navigate to the environment monitoring configuration mode, and run the display power system
parameter command to check 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 hightemperature power-off parameters. You can use default values of these parameters for
configuration.
Step 4 (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.
l Run the display power battery-test info command to query the discharge testing
information about the batteries.
Step 5 Configure required parameters for the rectifier module.
Run the power module-num command to configure the required parameters for the rectifier
module.
Issue 02 (2013-10-08)

201

Configuration Guide
Step 6 Configure the environment monitoring parameters of the ETP4830-A1/ETP4890 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 7 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 8 Query the information about the configuration parameters and environment parameters of the
power system.
Run the display power system parameter command to query the configuration parameters of
the power system.
Step 9 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
Result
After the configuration, the ETP4830-A1/ETP4890 works properly and monitors the configured
parameters. If the status of a monitored parameter becomes abnormal, an alarm is generated on
the device.
Example
Table 3-33 provides the data plan for configuring the power monitoring using the ETP4830A1/ETP4890 system.
Table 3-33 Data plan for configuring the power monitoring using the ETP4830-A1/ETP4890
system
Configuration Item
Data
Remarks
EMU
Type: SMU
Set the type of the

ETP4830-A1/ETP4890
power to SMU.
SN: 2
Sub-node ID: 0
NOTE
The hardware DIP on ETP4830-A1/
ETP4890 can not be set, and it is always
0.
Issue 02 (2013-10-08)

202

Configuration Guide
Configuration Item
Data
Remarks
Management
parameters of the
battery

Run the power battery

command to change the
configured management
parameters as required.
Interval of the equalized charging of

the interval: 60 days
Capacity of the battery set: 75 AH
Upper threshold of temperature test
for the battery set: 80C
Lower threshold of temperature test
for the battery set: -20C
Upper threshold of temperature
alarm for the battery set: 50C
Lower threshold of temperature
alarm for the battery set: 0C
Temperature compensation
coefficient of the battery set: 80 mV
Charging parameters of
the battery

automatic
Equalized charging voltage of the
battery: 56.5 V
This example uses the

default values. You can use
the power charge
value as required.
Float charging voltage of the battery:

53.5 V
Power-off parameters
of the battery set

status: permit
Battery set power-off voltage: 43 V
High-temperature
power-off parameters
of the battery set
Battery high-temperature power-off

permission status: permit
Rectifier module
parameters
Number of rectifier modules: 2 or 3
High-temperature power-off
temperature: 53C
Run the power off

configured power-off
Run the power
temperature-off
configured hightemperature power-off
l The ETP4830-A1
system supports a
maximum of two
rectifier modules.
l The ETP4890 system
supports a maximum of
three rectifier modules.
Issue 02 (2013-10-08)

203

Configuration Guide
Configuration Item
Data
Remarks
Environment
monitoring parameters
for power monitoring
Upper threshold of temperature

alarm: 68C
Run the power

environment command to
change the configured
environment monitoring
parameter as required.
Lower threshold of temperature

alarm: -5C
Upper threshold of temperature test:
80C
Lower threshold of temperature test:
-20C
Upper threshold of humidity alarm:
80% RH
Lower threshold of humidity alarm:
10% RH
Upper threshold of humidity test:
100% RH
Lower threshold of humidity test: 0%
RH
External extended
digital variables of the
power system
Issue 02 (2013-10-08)

The low level represents

the valid level. The host
does not report an alarm in
the case of low level.
Name of extended digital parameter

1: Fan
This is a user-defined
digital parameter, which
needs to be set as required.
The monitoring digital
parameter of the fan tray is
configured here to monitor
the fan tray.

204

Configuration Guide
Configuration Item
Data
Remarks
User-defined alarm ID of digital

parameter 1: 11
When the fan tray is faulty,

the host reports an alarm.
The meanings of the
supported alarm IDs are as
follows:
1: AC voltage; 2: AC
switch; 3: battery voltage;
4: battery fuse; 5: load fuse;
6: rectifier; 7: DC power; 8:
room door; 9: thief; 10:
wiring ; 11: fan; 12: fire;
13: smoke; 14: water; 15:
diesel; 16: smell 17: aircondition; 18: arrester; 19:
DC voltage; 20 output
switch; 21: digital userdefined alarm

The low level represents

the valid level. The host
does not report an alarm in
the case of low level.
Name of extended digital parameter

3: Arrester
This is a user-defined
digital parameter, which
needs to be set as required.
The monitoring digital
parameter of the surge
protector is configured
here to monitor the surge
protector.
User-defined alarm ID of digital

parameter 3: 19
When the surge protector is

faulty, the host reports an
alarm.
huawei(config)#emu add 2 SMU 0 4 RS485 SMU

huawei(config-if-smu-2)#power battery parameter 1 0.15 60 75
huawei(config-if-smu-2)#power module-num 2
huawei(config-if-smu-2)#power temperature-off battery-off-state permit
huawei(config-if-smu-2)#power environment humidity 80 10 100 0
This command is invalid unless in the contition of install the sensor, would
huawei(config-if-smu-2)#power environment temperature 68 -5 80 -20
This command is invalid unless in the contition of install the sensor, would
huawei(config-if-smu-2)#power outside_digital 1 available-level low-level
digital_alarm 11
name Fan
Issue 02 (2013-10-08)

205

Configuration Guide
huawei(config-if-smu-2)#power outside_digital 3 available-level low-level

digital_alarm 19 name Arrester
huawei(config-if-smu-2)#display power system parameter
EMU ID: 2
Floating voltage
: 53.50V
Equalizing time
: 60 days
Battery number
: 1
Battery 0 capacity
: 75 AH
: 80mV
Battery temperature alarm upper: 53C Battery temperature alarm lower: 0C
Battery off voltage
: 43.00V
Module 0 address: No configured
: Module 1 address: No configured
: Battery high-temperature-off permit
: Permit
---------------------------------------------------------------------------huawei(config-if-smu-2)#display power environment parameter
EMU ID: 2
Power environment configuration paramete
r
---------------------------------------------------------------------------AnalogID Name
Type
0
Temperature
68
-5
80
-20
C
Current
1
Humidity
80
10
100
0
%R.H.
Current
---------------------------------------------------------------------------DigitalID Name
Available Level
|DigitalID Name
Available Level
0
1
|
1
Fan
0
2
1
|
3
Arrester
0
4
1
|
5
1
6
1
---------------------------------------------------------------------------huawei(config-if-smu-2)#display power alarm
EMU ID: 2
Power alarm information
---------------------------------------------------------------------------AC supply yes : Yes
AC supply overvoltage or undervoltage
: Normal
Main voltage overvoltage or undervoltage : Normal
Load fuse
: Connect
Battery off
: On
Battery 0 loop
: Disconnect
Environment Temperature : Normal
Environment Humidity
: Normal
Door alarm
: Alarm
Water alarm
: Normal
Smoke alarm
: Normal
Battery Temperature alarm
: Normal
Wiring alarm
: Normal
Acinput air switch
: Normal
Battery 1 Temp-Sensor : Invalid
Environment 1 Temp-Sensor
: Invalid
Environment Humidity-Sensor : Invalid
Module 0
: Normal
Module 1
: Normal
Charge over state
: normal
Battery Dectect : Normal
---------------------------------------------------------------------------DigitalID Name
State
|DigitalID Name
State
0
Normal |
1
Normal
2
Normal |
3
Normal
4
Normal |
5
Normal
6
Normal
---------------------------------------------------------------------------huawei(config-if-smu-2)#quit
huawei(config)#save
Issue 02 (2013-10-08)

206

Configuration Guide
3.15.3 Configuring the Heat Exchanger Environment Monitoring

Parameters
This section describes how to configure the heat exchanger environment monitoring parameters
through the command line interface (CLI).
Prerequisites
Only when the data of the TCU (Temperature control unit) board is successfully configured in
the system, the monitoring parameters can be reported to the control board and the service
processing board.
Context
Figure 3-48 shows the configuration process.
Figure 3-48 Configuration process of the TCU
Start
Add the EMU
Confirm the EMU status

Set the heating start/stop
temperature
Set the high-temperature/lowtemperature alarm threshold
Query the configuration
parameters
Query the running status
Query the alarm information
Quit and save
End
Procedure
Step 1 Log in to device through the maintenance terminal and add the TCU.
Run the emu add command to add the TCU.
Step 2 Navigate to the environment monitoring configuration mode, and run the display emu command
to query the heat exchanger status.
Issue 02 (2013-10-08)

207

Configuration Guide
Step 3 Set the heating start temperature of heat exchanger and the heating stop temperature of heat
exchanger.
NOTE
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.
l 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.
l 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 of heat
exchanger and the low-temperature alarm threshold of heat exchanger.
Step 5 Run the display tcu system parameter command to query the configuration parameters of heat
exchanger.
Run the quit command to exit the TCU mode, and run the save command to save the data.
----End
Result
After the configuration, the TCU works properly and monitors the configured parameters. If the
status of a monitored parameter becomes abnormal, an alarm is generated on the device.
Example
huawei(config)#emu add 2 TCU 0 7 rs232 tcu
huawei(config-if-tcu-2)#tcu heat temperature -10 30
huawei(config-if-tcu-2)#tcu temperature 60 -22
huawei(config-if-tcu-2)#display tcu system parameter
EMU ID: 2
---------------------------------------------------------------------------Tcu heat start-temperature
: -10
Tcu heat stop-temperature
: 30
Alarm upper-temperature
: 60
Alarm lower-temperature
: -22
---------------------------------------------------------------------------huawei(config-if-tcu-2)#display tcu environment info
EMU ID: 2
---------------------------------------------------------------------------Tcu exit temperature
: 27
Tcu external fan rev
: 0
Tcu internal fan rev
: 1520
---------------------------------------------------------------------------huawei(config-if-tcu-2)#display tcu alarm
EMU ID: 2
---------------------------Analog environment info-------------------------ID Name
State
Value
AlmUpper
AlmLower
Unit
1 Exit temperature
Normal
27.00
89
11
C
State Value
0 Tcu temp. sensor
Normal 0
|1 Exit temp. sensor
Normal 0
2 Enter temp. sensor Normal 0
|3 Internal-cycle fan Normal 0
4 External-cycle fan Normal 0
|5 Heater
Normal 0
----------------------------------------------------------------------------
Issue 02 (2013-10-08)

208

Configuration Guide
3.15.4 Configuring the Monitoring Through the Fan Tray

This topic describes how to configure the speed adjustment mode and the alarm function of the
fan tray. Thus, the fan speed of the MA5616 can be adjusted automatically, and the fan tray of
the MA5616 can be monitored.
Procedure
Step 1 Add an EMU.
The fan can be automatically found by the system. You can run the emu add command to add
an environment monitoring unit.
Step 2 Configure the speed adjustment mode of the fan.
Run the fan speed command to configure the speed adjustment mode of the fan. 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 adjust command to set
the fan speed. The speed level can be 0, 1, 2, 3, 4, or 5. Here, 5 stands for the highest level, and 0 stands for the
lowest level.
Step 3 Configure whether alarms associated with the fan tray are reported.
Run the fan alarmset command to configure the reporting of alarms related to the fan tray.
Step 4 Query the configuration parameters of the fan tray.
Run the display fan system parameter command to query the configuration parameters of the
fan tray.
Run the quit command to quit the FAN mode, and then run the save command to save the data.
----End
Example
Table 3-34 shows the data plan for configuring the speed adjustment mode and monitoring of
the fan.
Table 3-34 Data plan for configuring monitoring through the fan
Item
Data
Remarks
EMU
Type: FAN
SN: 1
Subnode ID: 2
Fan speed adjustment mode:

automatic
In this mode, the fan speed is

automatically adjusted according to
the temperature.
Fan parameters
Issue 02 (2013-10-08)

209

Configuration Guide
Item
Data
Remarks
Whether to report an alarm when the

fan stops rotation because of being
blocked: permit
When the fan stops rotation because

of being blocked, the device reports
an alarm automatically.
Whether to report an alarm when the

temperature is very high: permit
huawei(config)#emu add 1 FAN 0 2 RS485 FAN

huawei(config-if-fan-1)#fan speed mode automatic
huawei(config-if-fan-1)#fan alarmset block permit
huawei(config-if-fan-1)#fan alarmset tem-high permit
huawei(config-if-fan-1)#display fan system parameter
EMU ID: 1
FAN configration parameter:
---------------------------------------------------------------------------FAN timing mode: Auto timing by temperature
---------------------------------------------------------------------------Alarm_name
Permit/Forbid
Fan block
Permit
Temperature high
Permit
---------------------------------------------------------------------------huawei(config-if-fan-1)#quit
huawei(config)#save
Issue 02 (2013-10-08)

210

Configuration Guide
4 Configuring the xDSL Internet Access Service
Configuring the xDSL Internet Access

Service
About This Chapter

The x digital subscriber line (xDSL) technology applies to the broadband Internet services that
are transmitted over the existing twisted-pair copper lines. xDSL services provides high
bandwidth and require low investment cost. In xDSL services, a user can connect to the Internet
in Internet Protocol over Ethernet (IPoE), Point-to-Point Protocol over Ethernet (PPPoE),
Internet Protocol over ATM (IPoA), or Point-to-Point Protocol over ATM (PPPoA) mode. ATM
is the abbreviation for asynchronous transfer mode. This topic describes how to configure an
xDSL Internet access service on the MA5616.
Prerequisite
The Authentication, Authorization and Accounting (AAA) function is required only when the
Internet access mode is PPPoE or PPPoA.
l
To enable the AAA function on the device, see 3.12 Configuring AAA.
If the AAA function is implemented by the broadband remote access server (BRAS), a
connection to the BRAS must be established. The BRAS should be capable of identifying
the VLAN tag of the MA5616 in the upstream direction. For the identification purpose, the
user name and password for dial-up Internet access must be configured on the BRAS.
NOTE
The local authentication information, including the user name, password, and attributes of the local user,
is configured on the MA5616 for the MA5616 to authenticate users. The local authentication can be
implemented quickly but it uses a lot of resources.
Generally, the AAA function is implemented on the BRAS.
Users connect to the Internet in IPoE, PPPoE, IPoA, or PPPoA mode.

l
Issue 02 (2013-10-08)
In IPoE mode, the MA5616 encapsulates the IP packet payload to Ethernet frames and
sends the Ethernet packets to the upper layer network. IPoE is mostly used on a private line
network to meet operators' IP access requirements. An authentication is generally not
required for IPoE users.
211

Configuration Guide
In PPPoE mode, the MA5616 transmits PPPoE user packets to the upper layer Ethernetbased PPPoE server (BRAS). PPPoE is a common mode for Internet access. In this mode,
PPPoE users must be authenticated using Authentication, Authorization and Accounting
(AAA) policies before connecting to the Internet.
In IPoA mode, the MA5616 encapsulates the IP packet payload to Ethernet frames and
sends the Ethernet packets to the upper layer network. In the downstream, the MA5616
decapsulates the IPoE packets to IPoA packets and sends the packets to users. IPoA is
generally used on a private line network to meet operators' requirements for transferring
from an ATM network to the IP network. An authentication is generally not required for
IPoA users.
In PPPoA mode, the MA5616 transmits PPPoA user packets to the upper layer Ethernetbased PPPoE server (BRAS) to meet operators' requirements for transferring from an ATM
network to the IP network. PPPoA users must be authenticated using Authentication,
Authorization and Accounting (AAA) policies before connecting to the Internet.
Data preparation
Before configuring an xDSL Internet access service, plan the data items as listed in Table 4-1.
Table 4-1 Data plan for the xDSL Internet access service
Item
Data
Remarks
MA5616
Access rate
Specify an access rate according to the

user requirement.
Access port
Specify an access port according to the

specific network planning.
VPI/VCI
The VPI/VCI is valid only for the

ATM access and must be the same as
the VPI/VCI of the interconnected
device.
VLAN planning
The VLAN planning must ensure

proper cooperation with the upperlayer device and thus the upstream
VLAN must be consistent with the
upstream VLAN of the upper-layer
device.
QoS policy
According to the general QoS policy

for the entire network, the priority of
an ordinary Internet access service is
lower than the priority of a voice or
video service.
IP address
The default gateway IP address must

be consistent with the IP address of the
upper-layer route.
The IP address is required only when

the Internet access mode is IPoA.
Issue 02 (2013-10-08)

212

Configuration Guide
Item
Data
Remarks
Upperlayer
Device
The upper-layer device transparently

transmits the service packets of the
MA5616 on L2.
The user-side VLAN ID of upperlayer device must be consistent with

the VLAN ID of the upstream service
packets of the MA5616.
The BRAS performs the related

configurations according to the
authentication and accounting
requirements for dial-up users. For
example, the BRAS configures the
access user domain (including the
authentication plan, accounting plan,
and authorization plan bound to the
domain) and specifies the RADIUS
server.
OLT or
LAN
switch
BRAS
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 an IP address pool on the
BRAS.
Procedure
1.
4.1 Configuring the xDSL Profile

When configuring a service, you need to configure the service and quality parameters for
an x digital subscriber line (xDSL) port according to the service type, and also need to plan
other parameters such as activation and rate. An xDSL profile defines all required
parameters for activating an xDSL port. This topic describes how to configure asymmetric
digital subscriber line 2 plus (ADSL2+), single-pair high-speed digital subscriber line
(SHDSL), and very-high-speed digital subscriber line 2 (VDSL2) profiles.
2.

enhanced security and support expansion and flexible networking. Configuring VLAN is
a prerequisite for configuring a service. Hence, before configuring a service, make sure
that the VLAN configuration based on planning is complete.
3.
4.3 Configuring an Upstream Port

The uplink port on an access device connects to the upper layer device to forward access
device data to the upstream network and forward upper layer device data to users.
4.

To increase the network bandwidth of a user, you can bind multiple ports together.
5.
4.5 Configuring an xDSL Port
Issue 02 (2013-10-08)

213

Configuration Guide
An xDSL can transmit services only when it is activated. This topic describes how to
activate an xDSL port and bind the port to an xDSL profile.
6.
4.6 Creating an xDSL Service Port

A service port connects the user side to the network side and carries service data. To provide
services, a service port must be created.
7.
4.7 (Optional) Configuring the xPoA-xPoE Protocol Conversion

xPoA to xPoE conversion involves the conversion from IP over ATM (IPoA) to IP over
Ethernet (IPoE) and the conversion from Point-to-Point Protocol over ATM (PPPoA) to
Point-to-Point Protocol over Ethernet (PPPoE). ATM is the abbreviation for asynchronous
transfer mode (ATM). xPoA packets cannot be transmitted on an IP network and must be
converted into xPoE packets. IPoA packets must be converted into IPoE and PPPoA packets
must be converted into PPPoE packets to be transmitted on an IP network. Protocol
conversion is required when the packet encapsulation mode is IPoA or PPPoA and is not
required when the packet encapsulation mode is IPoE or PPPoE.
8.

This topic describes how to configure the Vectoring function on a very-high-speed digital
subscriber line 2 (VDSL2). This technology can cancel the far-end crosstalk (FEXT) on a
VDSL2 line and increases VDSL2 rates.
Issue 02 (2013-10-08)

214

Configuration Guide
4.1 Configuring the xDSL Profile

When configuring a service, you need to configure the service and quality parameters for an x
digital subscriber line (xDSL) port according to the service type, and also need to plan other
parameters such as activation and rate. An xDSL profile defines all required parameters for
activating an xDSL port. This topic describes how to configure asymmetric digital subscriber
line 2 plus (ADSL2+), single-pair high-speed digital subscriber line (SHDSL), and very-highspeed digital subscriber line 2 (VDSL2) profiles.
4.1.1 Configuring an ADSL2+ Profile

When configuring an asymmetric digital subscriber line 2 plus (ADSL2+) service, you need to
configure the service and quality parameters for an ADSL2+ port according to the service type,
and also need to plan other parameters such as activation and rate. An ADSL2+ profile defines
all required parameters for activating an ADSL2+ port. This topic describes how to configure
ADSL2+ profiles in different modes.
Context
The MA5616 supports three ADSL2+ modes: normal mode (RFC2662), new generation
asymmetric digital subscriber lines (NG-ADSL) mode (RFC4706), and TR165 mode. You can
run the switch adsl mode to command to select a mode. By default, the normal mode is used.
l
Normal mode: This mode is used for common ADSL2+ profiles, including ADSL2+ line
profiles, ADSL2+ line alarm profiles, and ADSL2+ extended line profiles.
NG-ADSL mode: In this mode, ADSL2+ line profile parameters are reorganized, and a
line template and a line alarm template are used. The line template uses the line profile and
the channel profile as references, and the line alarm template uses the line alarm profile
and the channel alarm profile as references.
TR165 mode: A line profile consists of 10 profiles, which are: xDSL rate profile, power
spectrum density (PSD) profile, xDSL spectrum profile, xDSL upstream power backoff
(UPBO) profile, xDSL downstream power backoff (DPBO) profile, radio frequency
interference (RFI) profile, xDSL noise margin profile, xDSL virtual noise profile, xDSL
impulsive noise protection profile, and xDSL impulsive noise monitoring profile. All these
profiles must be bound to an x digital subscriber line (xDSL) port for activating the xDSL
port. For the configuration of TR165 profiles, see 4.1.4 Configuring xDSL Profiles
(TR165 Mode).
Configuring ADSL2+ Profiles (in Normal Mode)

This topic describes how to configure asymmetric digital subscriber line 2 plus (ADSL2+)
profiles in normal mode. Before configuring the ADSL2+ service, check the line management
architecture supported by the system. ADSL2+ lines support the following architecture modes:
normal (RFC2622), NGADSL (RFC4706), and TR165. When configuring the ADSL2+ service,
you can configure a line profile on an ADSL2+ port according to the service type to plan the
required service and channel quality parameters and other parameters such as activation mode
and spectrum. When an ADSL2+ line uses the RFC2662 mode, configure ADSL2+ profiles in
normal mode.
Issue 02 (2013-10-08)

215

Configuration Guide
Prerequisites
The ADSL mode is set to the common ADSL mode( RFC2662 mode ) using the switch adsl
mode to rfc2662 command.
Context
Associated configuration in normal ADSL mode is described here.
l
Before activating an ADSL2+ port, bind a ADSL2+ line profile and alarm profile to the
port.
An ADSL2+ extended line profile contains extended line parameters for ADSL2+ port
activation.
In normal ADSL mode, physical-layer retransmission is supported. Physical-layer

retransmission can be configured in an ADSL2+ extended line profile and alarm profile to
achieve optimal multicast service quality.
Table 4-2 describes the default configurations of ADSL2+ profiles.

Table 4-2 Default configurations of ADSL2+ profiles
Profile
Default Settings
ADSL2+ line profile
Profile IDs: 1, 1022, 1023, and 1024

l Profile 1 is used to activate common ADSL2+
ports.
l Profile 1022 is used to activate ADSL2+ ports
in fast mode.
l Profile 1023 is used to activate existing ADSL
ports in a long distance.
l Profile 1024 is used to activate ports on an
ADSL2+ board.
ADSL2+ line alarm profile
Profile ID: 1
All parameters in the default profile are set to 0,
indicating that no alarm will be reported for the
device.
Procedure
l
Configure an ADSL2+ line profile.

Run the adsl line-profile quickadd command to quickly add an ADSL2+ line profile or
run the adsl line-profile add command (an interactive command) to add an ADSL2+ line
profile.
An ADSL2+ line profile contains the following parameters:
transmode (only for the preceding interactive command): It indicates the line
transmission mode. By default, all the transmission modes are supported. The default
Issue 02 (2013-10-08)

216

Configuration Guide
mode can be used. Then, the system automatically adapts to the transmission mode of
the peer end.
snr: Indicates the SNR margin, which refers to the idle space for carrying noise,
excluding the space for carrying signals. In general, the SNR margin of the minimum
tone is considered as the SNR margin of the entire ADSL connection.
rate: It indicates the line rate. During line activation, an appropriate rate is automatically
negotiated between the preset maximum rate and minimum rate based on the line
condition and profile configuration. This line rate or the rate configured in the traffic
profile bound to a port can be used to restrict a user rate on the port. When both rates
function, the lower rate is selected as the user rate.
After the ADSL2+ line profile is configured, ADSL2+ ports can use the profile when being
activated.
l
Configure an ADSL2+ alarm profile.

Run the adsl alarm-profile quickadd command to quickly add an ADSL2+ alarm profile
or run the adsl alarm-profile add command (an interactive command) to add an ADSL2
+ alarm profile.
After the ADSL2+ alarm profile is configured, ADSL2+ ports can be bound to the profile.
Configure an ADSL2+ extended line profile.

Run the adsl extline-profile quickadd command to quickly add an ADSL2+ extended line
profile or run the adsl extline-profile add command (an interactive command) to add an
ADSL2+ extended line profile.
An extended line profile is used in the same way as the line profile. An extended line profile
defines the parameters for certain enhanced features. Therefore, an extended line profile is
optional for port configuration and a line can be activated normally without an extended
line profile. When both an extended line profile and a line profile are configured at the same
time, their parameters do not conflict with each other.
An ADSL2+ extended line profile contains the following parameters:
missingtone: It indicates the missingtone function. When you set this parameter for a
specified sub-carrier of the line, the sub-carrier has no power output or assigned bit. The
missing tone function is used to measure the radio frequency interference (RFI) on a
line. This function can be used in the following conditions:
The noises on some frequencies are unstable. In this condition, you can use the
missing tone to disable these frequencies to prevent the line from running unstably
due to these frequencies.
Some frequencies have special usages in some areas. To protect these frequencies
against interference, you can use the missing tone function to disable these
frequencies or use TSSi to minimize the output power of these frequencies to the
lower limits.
g.998.4-rtx-mode: It indicates G.998.4 retransmission. It is of numeral type and ranges
from 0 to 3.
0: indicates RTX_FORBIDDEN.
1: indicates RTX_PREFERRED.
2: indicates RTX_FORCED.
Issue 02 (2013-10-08)

217

Configuration Guide
3: indicates RTX_TESTMODE.
After the ADSL2+ extended line profile is configured, ADSL2+ ports can be bound to the
profile.
----End
Example
Assume that:
l
Downstream minimum rate: 2048 kbit/s
Downstream maximum rate: 5120 kbit/s
Upstream rate: 512 kbit/s
All the thresholds of the central office (CO) end: 100s
Threshold for the difference between the current and previous transmission rates in channel
mode: 1000 kbit/s.
To configure an ADSL line profile and alarm profile with these parameters and their IDs both
being 3, do as follows:
huawei(config)#adsl line-profile quickadd 3 rate 1024 5120 512 512
huawei(config)#adsl alarm-profile quickadd 3 atu-c trap enable 100 100 100 100
100
100 100 100 interleaved 1000 1000 fast 1000 1000
Configuring the ADSL2+ Profile (NGADSL Mode)

When configuring the ADSL2+ service, you can configure a line profile on an ADSL2+ port
according to the service type to plan the required service and channel quality parameters and
other parameters such as activation mode and spectrum. When an ADSL2+ line uses the
RFC4706 mode, configure ADSL2+ profiles in normal mode.
Prerequisites
Run the switch adsl mode to rfc4706 command to switch to the ADSL mode NGADSL.
Context
In this task, the configuration specified is based on the NGADSL mode.
l
When activating an ADSL2+ port, you need to bind the ADSL2+ line template and alarm
template to the port.
An ADSL2+ line template should be formed by binding an ADSL2+ line profile with an
ADSL2+ channel profile.
An ADSL2+ line alarm template should be formed by binding an ADSL2+ line alarm
profile with an ADSL2+ channel alarm profile.
Table 4-3 describes the default configurations of ADSL2+ templates.
Issue 02 (2013-10-08)

218

Configuration Guide
Table 4-3 Default configurations of ADSL2+ templates

Template
Default Settings
ADSL2+ line template
Template ID: 1
ADSL2+ line alarm template
Template ID: 1
All parameters are set to 0 by default, indicating that
alarms will not be reported.
Figure 4-1 shows the flow for configuring an ADSL2+ template.

Figure 4-1 Flowchart for configuring an ADSL2+ template
Procedure
l
Configure an ADSL2+ line template.

1.
Run the adsl line-profile quickadd command to quickly add an ADSL2+ line profile,
or run the interactive adsl line-profile add command to add an ADSL2+ line profile.
Main parameters:
transmode and Transmission mode (in interactive mode): It indicates the line
transmission mode. By default, all the transmission modes are supported. The
default mode can be used. Then, the system automatically adapts to the
transmission mode of the peer end.
snr: Indicates the SNR margin, which refers to the idle space for carrying noise,
excluding the space for carrying signals. In general, the SNR margin of the
minimum tone is considered as the SNR margin of the entire ADSL connection.
2.
Run the adsl channel-profile quickadd command to quickly add an ADSL2+ channel
profile, or run the interactive adsl channel-profile add command to add an ADSL2
+ channel profile.
Main parameters:
Issue 02 (2013-10-08)

219

Configuration Guide
interleaved-delay and interleaving delay (in interactive mode): Indicates the

interleave delay. A zero interleave delay corresponds to the fast mode. In the fast
mode, the interleave delay is short, but the error correction capability is weak. A
non-zero interleave delay corresponds to the interleave mode. The interleave depth
increases directly to the interleave delay. In the interleave mode, higher interleave
depth indicates more powerful error correction capability.
inp: Indicates impulse noise protection. As a parameter that describes the line
capability of resisting impulse interference, INP affects the port rate. If INP is 1,
it indicates that the current channel can resist the impulse noise in 1 DMT character
length. The interleave delay is related to INP. In the fast mode, INP does not apply.
rate: Indicates the line rate. During line activation, a proper rate between the preset
maximum rate and minimum rate is determined through automatic negotiation
according to the line condition and the profile configuration. The user rate can be
restricted by this line rate or the rate set in the traffic profile bound to the user.
When both rates function, the lower one is adopted as the user rate.
3.
Run the adsl line-template quickadd command to quickly add an ADSL+ line
template, or run the interactive adsl line-template add command to add an ADSL2
+ line template.
After the ADSL2+ line template is configured, ADSL2+ ports can use the template
when being activated.
Configure an ADSL2+ line alarm template.

1.
Run the adsl alarm-profile quickadd command to quickly add an ADSL2+ line alarm
profile, or run the interactive adsl alarm-profileadd command to add an ADSL2+
line alarm profile.
2.
Run the adsl channel-alarm-profile quickadd command to quickly add an ADSL2

+ channel alarm profile, or run the interactive adsl channel-alarm-profile add
command to add an ADSL2+ channel alarm profile.
3.
Run the adsl alarm-template quickadd command to quickly add an ADSL2+ line
alarm template, or run the interactive adsl alarm-templateadd command to add an
ADSL2+ line alarm template.
After the ADSL2+ alarm template is configured, ADSL2+ ports can be bound to the
template.
----End
Example
Assume that an ADSL2+ line template with an index number of 3 is to be added. For the ADSL2
+ line template, 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. To configure such an
ADSL2+ line template, do as follows:
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
Issue 02 (2013-10-08)

220

Configuration Guide
4.1.2 Configuring the SHDSL Profile

This topic describes how to use most parameters of a single-pair high-speed digital subscriber
line (SHDSL) port to configure an SHDSL line profile. Users can directly use this SHDSL line
profile when activating SHDSL ports.
Context
An SHDSL line profile provides all parameters for activating an SHDSL port. If the statistical
duration configured in an SHDSL alarm profile is 15 minutes, an alarm is reported to the network
management system (NMS) when a statistical item reaches the alarm threshold within 15
minutes.
Table 4-4 lists the default SHDSL profiles.
Table 4-4 Default configurations of SHDSL profiles
Profile
Default Settings
SHDSL line profile
Profile IDs: 1, 100, 101, 102, and 103

l Profile 1 is used to activate a 2-wire SHDSL port
in asynchronous transfer mode (ATM) mode.
l Profile 100 is used to activate a 4-wire SHDSL
port in ATM mode.
l Profile 101 is used to activate a 6-wire SHDSL
port in ATM mode.
l Profile 102 is used to activate an 8-wire SHDSL
port in ATM mode.
l Profile 103 is used to activate an Ethernet in the
first mile (EFM)-bonding SHDSL port.
SHDSL alarm profile
Profile ID: 1
All parameters except the terminal power-off alarm
are set to 0 (disabled) by default.
Procedure
l
Configure an SHDSL line profile.

Run the shdsl line-profile quickadd command to quickly add an SHDSL line profile, or
run the shdsl line-profile add command to interactively add an SHDSL line profile.
Main parameters:
ptm: If the SHDSL channel mode is the ATM mode, do not select ptm. If the SHDSL
channel mode is the PTM mode, select ptm.
rate: Indicates the line rate. During line activation, a proper rate between the preset
Issue 02 (2013-10-08)

221

Configuration Guide
restricted by this rate or the rate set in the traffic profile that is bound to the user. When
both rates function, the lower rate is selected as the user rate.
transmission: Indicates the transmission mode. Set the transmission mode according
to line conditions and actual planning. Three transmission modes are supported: annex
A (mainly used in North America), annex B (mainly used in Europe), and annex A&B.
snr-margin: The larger the SNR margin, the better the line stability, and meanwhile
the lower the physical connection rate of the line after activation. For common Internet
access users, set the target SNR margin to 3; for users with higher priorities, set the
target SNR margin to 5.
NOTE
The H832SHLH board supports G.SHDSL.BIS and the maximum rate can be 5696 kbit/s.
After the SHDSL line profile is configured, SHDSL ports can use the profile when being
activated.
l
Configure an SHDSL alarm profile.

Run the shdsl alarm-profile quickadd command to quickly add an SHDSL alarm profile,
or run the shdsl line-profile add command to interactively add an SHDSL alarm profile.
After the SHDSL alarm profile is configured, SHDSL ports can be bound to the profile.
----End
Example
To add SHDSL line profile 3 with the line rate of 4096 kbit/s, which is used to activate the 4wire SHDSL port, do as follows:
huawei(config)#shdsl line-profile quickadd 3 line four-wire rate 4096
Assume that the loop attenuation threshold is 10 dB, SNR margin is 0 dB, ES threshold is 100s,
SES threshold is 100s, CRC abnormality duration threshold is 10000, LOSWS threshold is 100s,
UAS threshold is 100s. To quickly add SHDSL line alarm profile 3 with these parameters, do
as follows:
huawei(config-if-shl-0/3)#shdsl alarm-profile quickadd 3 loop-attenuation 10 snrmargin
0 es 100 ses 100 crc-anomaly 10000 losws 100 uas 100
4.1.3 Configuring the VDSL2 Profile

When configuring a very-high-speed digital subscriber line 2 (VDSL2) service, you need to
configure the service and quality parameters for a VDSL2 port according to the service type,
and also need to plan other parameters such as activation and rate. A VDSL2 profile defines all
required parameters for activating a VDSL2 port. This topic describes how to configure VDSL2
profiles in different modes.
Context
The MA5616 supports three VDSL2 modes, normal(TR129 mode), TI, and TR165, which are
selected by running switch vdsl mode to command. By default, the system supports the normal
VDSL2 mode(TR129 mode).
Issue 02 (2013-10-08)

222

Configuration Guide
Normal mode: It is the mode for VDSL2 general profiles. VDSL2 general profiles are
classified into the VDSL2 line profile, VDSL2 channel profile, and VDSL2 line template.
TI mode: In TI mode, the parameters in the VDSL2 profile are re-organized. Specifically,
the parameters are classified by type and frequency used. In TI mode, VDSL2 profiles are
classified into six types: VDSL2 service profile, VDSL2 frequency spectrum profile,
VDSL2 UPBO profile, VDSL2 DPBO profile, VDSL2 SNR margin profile, and VDSL2
delay INP profile.
TR165 mode: In TR165 mode, a line profile consists of 10 profiles: xDSL rate profile,
power spectrum density (PSD) profile, xDSL frequency spectrum profile, xDSL upstream
power back-of (UPBO) profile, xDSL downstream power back-of (DMBO) profile, radio
frequency interference (RFI) profile, xDSL signal to noise ratio (SNR) margin profile,
xDSL virtual noise profile, xDSL delay impulse noise protection (INP) profile, and xDSL
impulse noise monitor profile. You must bind these profiles to an xDSL port before
activating the port.
Configuring the VDSL2 Profile (TR129 Mode)

Before configuring very-high-speed digital subscriber line 2 (VDSL2) services, you need to
determine the management mode for VDSL2 lines. The management mode for VDSL2 lines is
TR129 or TR165. When configuring the VDSL2 services, you need to configure a line profile.
By doing so, you can set service parameters and channel quality of service parameters for VDSL2
ports based on service type, and plan parameters for activation mode and frequency spectrum.
When the TR129 management mode is used, you need to configure a VDSL2 mode in TR129
mode.
Prerequisites
The VDSL2 mode has been switched to TR129 by running the switch vdsl mode to tr129
command.
Context
The system supports the TR129 mode by default.
l
The VDSL2 line template binds to a VDSL2 line profile and a VDSL2 channel profile.
When activating a VDSL2 port, you need to bind the VDSL2 line template to the port.
Before activating a VDSL2 port, bind a VDSL2 line template to the port.
The VDSL2 alarm template binds to a VDSL2 line alarm profile and a VDSL2 channel
alarm profile. When activating a VDSL2 port, you need to bind the VDSL2 alarm template
to the port.
In TR129 mode, the downstream/upstream physical-layer retransmission is supported. This

feature can be configured in a VDSL2 line profile, VDSL2 channel profile, and VDSL2
alarm profile to achieve optimal multicast service quality.
Table 4-5 lists the default settings of VDSL2 profiles.
Issue 02 (2013-10-08)

223

Configuration Guide
Table 4-5 Default settings of VDSL2 profiles

Parameter
Default Value
VDSL2 line profile
Profile ID: 1
The settings in the default profile are for reference.
VDSL2 channel profile
Profile ID: 1
The settings in the default profile are for reference.
VDSL2 line alarm profile
Profile ID: 1
In the default profile, the terminal power-off alarm
reporting function is enabled, and other parameters
are set to 0.
VDSL2 channel alarm profile
Profile ID: 1
indicating that alarms will not be reported.
Figure 4-2 provides the configuration flow of a VDSL2 profile.

Figure 4-2 Flowchart for configuring a VDSL2 profile
Procedure
l
Configure a VDSL2 line template.

1.
Run the vdsl line-profile quickadd command to quickly add a VDSL2 line profile,
or run the vdsl line-profile add command to interactively add a VDSL2 line profile.
Main parameters:
transmode: indicates the line transmission mode. By default, the system supports
all transmission modes as follows:
Issue 02 (2013-10-08)

224

Configuration Guide
1: All
2: Full rate
3: G.DMT
4: G.HS
5: ADSL
6: VDSL
The default setting can be used. Then, the system automatically adapts to the
snr: indicates the signal to noise ratio (SNR) margin. It refers to the remaining
space for carrying noise, excluding the space for carrying signals. In general, the
minimum SNR margin of all the tones is used as the SNR margin of the entire
VDSL2 connection.
g.998.4-rtx-mode: indicates G.998.4 retransmission. It is of numeral type and
ranges from 0 to 3.
0: RTX_FORBIDDEN
1: RTX_PREFERRED
2: RTX_FORCED
3: RTX_TESTMODE
2.
Run the vdsl channel-profile quickadd command to quickly add a VDSL2 channel
profile, or run the vdsl channel-profile add command to interactively add a VDSL2
channel profile.
Main parameters:
path-mode: indicates the path mode. There are two VDSL2 path modes:
asynchronous transfer mode (ATM) and packet transfer mode (PTM). By default,
the system supports both modes. When the path mode supported by customer
premises equipment (CPE) is unknown, you do not need to configure the path mode
because the system automatically adapts to it based on the actual line mode. When
both central office (CO) and CPE support the ATM mode, set the path mode to
atm. When both CO and CPE support the PTM mode, set the path mode to ptm.
interleaved-delay: indicates the interleave delay. A zero interleave delay
corresponds to the fast mode. In fast mode, the interleave delay is short, but the
error correction capability is weak. The fast mode is applicable to delay-sensitive
services, such as video on demand (VOD) and video phone (VP) services. A nonzero interleave delay corresponds to the interleave mode. The longer the interleave
delay, the greater the interleave depth. In interleave mode, the greater the interleave
depth, the stronger the error correction capability, but the longer the delay. The
interleave mode is applicable to delay-insensitive services with high requirement
on reliability, such as the file download service.
inp: indicates the impulse noise protection. The INP is a parameter that describes
the line capability of resisting impulse interference. The INP affects the port rate.
If the INP is 1, it indicates that the current channel can resist the impulse noise in
1 DMT character length. The interleave delay is related to the INP. In fast mode,
the INP is meaningless.
rate: indicates the line rate. During line activation, a proper rate between the preset
Issue 02 (2013-10-08)

225

Configuration Guide
restricted by this rate or the rate set in the traffic profile bound to the user. When
g.998.4-rtx: indicates physical-layer retransmission. It contains various
parameters, such as the maximum/minimum delay, maximum/minimum expected
throughput rate, maximum net data rate, repetitive electrical impulse noise interarrival time, minimum impulse noise protection against repetitive electrical
impulse noise, minimum impulse noise protection against single high impulse
noise event, and single impulse noise event ratio.
3.
Run the vdsl line-template quickadd command to quickly add a VDSL2 line
template, or run the vdsl line-template add command to interactively add a VDSL2
line template.
A VDSL2 line template consists of a VDSL2 line profile and a VDSL2 channel profile.
Before activating a VDSL2 port, bind a VDSL2 line template to the port.
Configure a VDSL2 alarm template.

1.
Run the vdsl alarm-profile quickadd command to quickly add a VDSL2 line alarm
profile, or run the vdsl alarm-profile add command to interactively add a VDSL2
line alarm profile.
2.
Run the vdsl channel-alarm-profile quickadd command to quickly add a VDSL2

channel alarm profile, or run the vdsl channel-alarm-profile add command to
interactively add a VDSL2 channel alarm profile.
3.
Run the vdsl alarm-template quickadd command to quickly add a VDSL2 alarm
template, or run the vdsl alarm-template add command to interactively add a VDSL2
alarm template.
After the VDSL2 line template is configured, VDSL2 ports can be bound to the profile.
----End
Example
Assume that:
l
G.998.4 is used for the downstream/upstream G.998.4 retransmission in precedence over

other modes.
Downstream rate: 2048 kbit/s
Channel mode: interleave mode
Downstream maximum interleave delay: 8 ms
Upstream maximum interleave delay: 2 ms
SNR margin: 6 dB
Downstream minimum INP: 4
Upstream minimum INP: 2
Downstream/Upstream maximum delay: 50 ms in G.998.4 retransmission.
Downstream/Upstream rate adaptation carrying percentage of a channel: 100%
To add VDSL2 profiles with ID 3 in TR129 mode for configuring the VDSL2 Internet access
service with the preceding configurations to enhance the connection stability and impulse noise
protection (INP) capability, do as follows:
Issue 02 (2013-10-08)

226

Configuration Guide
huawei(config)#vdsl
1 1
huawei(config)#vdsl
128 10000 128 10000
huawei(config)#vdsl
line-profile quickadd 3 snr 60 0 300 60 0 300 g.998.4-rtx-mode

channel-profile quickadd 3 interleaved-delay 8 2 inp 4 2 rate
2048 2048 g.998.4-rtx delay-max 50 50
line-template quickadd 3 line 3 channel1 3 100 100
Configuring the VDSL2 Profile (TI Mode)

Before configuring very-high-speed digital subscriber line 2 (VDSL2) services, you need to
determine the management mode for VDSL2 lines. The management mode for VDSL2 lines is
TR129, TI, or TR165. When configuring the VDSL2 services, you need to configure a line
profile. By doing so, you can set service parameters and quality related parameters for VDSL2
ports based on service type, and plan parameters for activation mode and frequency spectrum.
When the TI management mode is used, you need to configure a VDSL2 mode in TI mode.
Prerequisites
The VDSL2 mode has been switched to TI by running the switch vdsl mode to timode
command.
Context
l
The VDSL2 line profile is re-organized to form six types of profiles. Before activating a
VDSL2 port, bind six types of VDSL2 profile configurations to the VDSL2 port.
A VDSL2 alarm template must be bound to a VDSL2 line alarm profile and a VDSL2
channel alarm profile. A VDSL2 port must be bound to a VDSL2 alarm template.
Table 4-6 describes the default configurations of VDSL2 profiles.

Table 4-6 Default configurations of VDSL2 profiles
Profile
Default Settings
VDSL2 delayed impulse noise

protection profile
Profile ID: 1
VDSL2 downstream power back off

profile
Parameters in the default profile are only for

reference.
VDSL2 noise margin profile

VDSL2 service profile
VDSL2 spectrum profile
VDSL2 upstream power back off
profile
VDSL2 line alarm profile
Profile ID: 1
All parameters except the terminal power-off alarm
are set to 0 (disabled) by default.
Issue 02 (2013-10-08)

227

Configuration Guide
Profile
Default Settings
VDSL2 channel alarm profile
Profile ID: 1
indicating that no alarm will be reported for the
device.
Figure 4-3 shows the procedure for configuring a VDSL2 profile.

Figure 4-3 Flowchart for configuring a VDSL2 profile
Procedure
l
Configure a VDSL2 line profile.

1.
Run the vdsl service-profile quickadd command to quickly add a VDSL2 service
profile, or run the vdsl service-profile add command to interactively add a VDSL2
service profile.
A VDSL2 service profile contains the most common parameters of a VDSL2 line. In
general, only the configuration of a VDSL2 service profile is required. In the case of
other profiles, adopt the default profiles.
Main parameters:
Issue 02 (2013-10-08)

228

Configuration Guide
path-mode: indicates the path mode. There are two VDSL2 path modes:
asynchronous transfer mode (ATM) and packet transfer mode (PTM). To set the
ATM mode as the VDSL2 path mode, select atm. To set the PTM mode as the
VDSL2 path mode, select ptm.
rate: indicates the line rate. During line activation, a proper rate between the preset
restricted by this rate or the rate set in the traffic profile bound to the user. When
2.
Run the vdsl delay-inp-profile quickadd command to quickly add a VDSL2 delay
INP profile, or run the vdsl delay-inp-profile add command to interactively add a
VDSL2 delay INP profile.
Main parameters:
bearer1-interleaved-delay: A zero interleave delay corresponds to the fast mode.
In fast mode, the interleave delay is short, but the error correction capability is
weak. The fast mode is applicable to delay-sensitive services, such as video on
demand (VOD) and video phone (VP) services. A non-zero interleave delay
corresponds to the interleave mode. The longer the interleave delay, the greater
the interleave depth. In interleave mode, the greater the interleave depth, the
stronger the error correction capability, but the longer the delay. The interleave
mode is applicable to delay-insensitive services with high requirement on
reliability, such as the file download service.
bearer1-inp: The INP is a parameter that describes the line capability of resisting
impulse interference. The INP affects the port rate. If the INP is 1, it indicates that
the current channel can resist the impulse noise in 1 DMT character length. The
interleave delay is related to the INP. In fast mode, the INP is meaningless.
3.
Run the vdsl noise-margin-profile quickadd command to quickly add a VDSL2 SNR
margin profile, or run the vdsl noise-margin-profile add command to interactively
add a VDSL2 SNR margin profile.
Main parameter:
snr-margin: indicates the SNR margin. It is the remaining space for carrying noise,
excluding the space for carrying signals. In general, the minimum SNR margin of all
the tones is used as the SNR margin of the entire VDSL2 connection.
4.
Run the vdsl spectrum-profile quickadd command to quickly add a VDSL2

spectrum profile, or run the vdsl spectrum-profile add command to interactively add
a VDSL2 spectrum profile.
Main parameter:
transmode: indicates the line transmission mode. By default, the system supports all
transmission modes as follows:
1: All
2: Full rate
3: G.DMT
4: G.HS
5: ADSL
6: VDSL
Issue 02 (2013-10-08)

229

Configuration Guide
The default setting can be used. Then, the system automatically adapts to the
5.
Run the vdsl upbo-profile quickadd command to quickly add a VDSL2 UPBO
profile, or run the vdsl upbo-profile add command to interactively add a VDSL2
UPBO profile.
6.
Run the vdsl dpbo-profile quickadd command to quickly add a VDSL2 DPBO
profile, or run the vdsl dpbo-profile add command to interactively add a VDSL2
DPBO profile.
After the VDSL2 line profile is configured, VDSL2 ports can use the profile when being
activated.
l
Configure a VDSL2 alarm template.

1.
Run the vdsl alarm-profile quickadd command to quickly add a VDSL2 line alarm
profile, or run the vdsl alarm-profile add command to interactively add a VDSL2
line alarm profile.
2.
Run the vdsl channel-alarm-profile quickadd command to quickly add a VDSL2

channel alarm profile, or run the vdsl channel-alarm-profile add command to
interactively add a VDSL2 channel alarm profile.
3.
Run the vdsl alarm-template quickadd command to quickly add a VDSL2 alarm
template, or run the vdsl alarm-template add command to interactively add a VDSL2
alarm template.
After the VDSL2 line template is configured, VDSL2 ports can be bound to the profile.
----End
Example
Assume that:
l
Path mode: PTM mode
Downstream minimum reserved rate: 4096 kbit/s
Channel mode: interleave mode
Downstream maximum interleave delay: 8 ms
Upstream maximum interleave delay: 2 ms
SNR margin: 10 dB
Downstream minimum INP: 4
Upstream minimum INP: 2
Downstream/Upstream noise margin: 60, 10, 310, 60, 10, and 310
To add VDSL2 profiles with ID 3 in TI mode for configuring the VDSL2 Internet access service
with the preceding configurations to enhance the connection stability and impulse noise
protection (INP) capability, do as follows:
huawei(config)#vdsl service-profile quickadd 3 path-mode ptm bearer1-rate 512
4096 8192 128 128 128 100000 128
huawei(config)#vdsl delay-inp-profile quickadd 3 bearer1-interleaved-delay 8 2
bearer1-inp 4 2
huawei(config)#vdsl noise-margin-profile quickadd 3 snr-margin 60 10 310 60 10
310
Issue 02 (2013-10-08)

230

Configuration Guide
4.1.4 Configuring xDSL Profiles (TR165 Mode)

When configuring an x digital subscriber line (xDSL) service, you can configure a line profile
based on the service type to plan the required service and channel parameters such as the
activation mode and spectrum. When an xDSL line uses the TR165 mode, configure xDSL
profiles in TR165 mode. This topic describes how to configure various xDSL profiles in TR165
mode. TR165 mode only supports asymmetric digital subscriber line 2 plus (ADSL2+) and veryhigh-speed digital subscriber line 2 (VDSL2) profiles.
Prerequisites
The ADSL2+ profile mode has been switched to TR165 by running the switch adsl mode to
tr165 command and the VDSL2 profile mode has been switched to TR165 by running the switch
vdsl mode to tr165 command.
NOTE
When both the ADSL2+ and VDSL2 work in the TR165 mode, a configured profile can be used by both the
ADSL2+ and VDSL2; if only one of them works in the TR165 mode, a configured profile is available for only
the one in the TR165 mode.
Context
l
In TR165 mode, a line profile consists of 10 profiles. You must bind these profiles to an
xDSL port before activating the port. Figure 4-4 shows the flow for configuring xDSL
profiles.
NOTE
The upstream power back off (UPBO) profile is not used for ADSL2+.
Figure 4-4 Flowchart for configuring xDSL profiles

Service-related profile
Spectrum-related profile
Service quality-related profile
Start
Start
Start
Configure an xDSL rate

profile
Configure a PSD profile
Configure an xDSL SNR

margin profile
End
Configure an xDSL spectrum

profile
Configure an xDSL virtual

noise profile
Configure an xDSL UPBO

profile
Configure an xDSL delay

INP profile
Configure an xDSL DPBO

profile
Configure an xDSL INM

profile
Configure an RFI profile
End
End
Issue 02 (2013-10-08)

231

Configuration Guide
In xDSL TR165 mode, the downstream/upstream physical-layer retransmission is

supported. This feature can be configured in an xDSL rate profile, an xDSL delay impulse
noise protection (INP) profile, and an xDSL frequency spectrum profile to achieve optimal
multicast service quality.
The INM implements the impulse noise monitor function. An INM profile monitors impulse
noise distribution during performance statistics. You can collect statistics of equivalent INP
and IAT based on the collected INM data and then set the INP_Min and Delay_Max to
proper values to increase line stability.
Configure the xDSL rate profile.
Procedure
1.
Run the xdsl data-rate-profile quickadd command to quickly add an xDSL rate
profile, or run the interactive xdsl data-rate-profile add command to add an xDSL
rate profile.
A rate profile contains the most common parameters on a xDSL line. The main
parameters are as follows:
path mode: Indicates the path mode. There are two VDSL2 path modes: ATM
mode and PTM mode. By default, the system supports both modes and
automatically adapts the path mode according to the modem. You may not
configure the path mode. If the modem supports the ATM mode, select ATM; if
the modem supports the PTM, select PTM; if the modem supports both modes and
the path mode is set to Both, the PTM mode is preferred to activate the line. The
ADSL2+ line works in only the ATM mode.
rate: Indicates the line rate. During line activation, an appropriate rate between
the preset maximum rate and minimum rate is automatically negotiated according
to the line condition and profile configuration. The user rate can be restricted by
this rate or the rate preset in the traffic profile bound to the user. When both rates
function, the user rate adopts the smaller value.
g.998.4-rtx: Indicates G.998.4 retransmission. It contains various parameters, such
as the maximum/minimum expected throughput rate and maximum net data rate.
After the xDSL rate profile is configured, ADSL2+ or VDSL2 can use the profile
when being activated.
Configure service quality-related profiles.

1.
Run the xdsl noise-margin-profile quickadd command to quickly add an xDSL SNR
margin profile, or run the interactive xdsl noise-margin-profile add command to add
an xDSL SNR margin profile. The main parameters are as follows:
snr-margin: Indicates the SNR margin. It is the remaining space for carrying noise,
except the space for carrying signals. In general, the minimum SNR margin of all the
tones is used as the SNR margin of the entire VDSL2 connection.
Issue 02 (2013-10-08)
2.
Run the xdsl virtual-noise-profile quickadd command to quickly add an xDSL

virtual noise profile, or run the interactive xdsl virtual-noise-profile add command
to add an xDSL virtual noise profile.
3.
Run the xdsl inp-delay-profile quickadd command to quickly add an xDSL delay
INP profile, or run the interactive xdsl inp-delay-profile add command to add an
xDSL delay INP profile. The main parameters are as follows:
232

Configuration Guide
impulse noise protection: Indicates the impulse noise protection. The INP is a
parameter that describes the line capability of resisting impulse interference. The
INP affects the port rate. INP = 1 indicates that the current channel can resist the
pulse noise with 1 DMT character length. The interleave delay is relevant to the
INP. In the fast mode, the INP is meaningless.
interleaving delay: Indicates the interleave delay. A zero interleave delay
corresponds to the fast mode. In the fast mode, the interleave delay is short, but
the error correction capability is weak. A non-zero interleave delay corresponds
to the interleave mode. The longer the interleave delay, the greater the interleave
depth. In the interleave mode, the greater the interleave depth, the stronger the error
correction capability, but the larger the delay.
g.998.4-rtx: Indicates G.998.4 retransmission. It contains various parameters, such
as the maximum/minimum delay, repetitive electrical impulse noise inter-arrival
time, minimum impulse noise protection against repetitive electrical impulse
noise, minimum impulse noise protection against single high impulse noise event,
and single impulse noise event ratio.
4.
Run the xdsl inm-profile quickadd command to quickly add an xDSL impulse noise
monitor profile or run the interactive xdsl inm-profile add command to add an xDSL
pulse noise monitor profile. The main parameters are as follows:
Users can determine the impulse noise protection (INP) parameters according to the
obtained INMAINPEQi and INMAIATi statistical chart to improve line stability.
INM inter arrival time offset: indicates the INM inter-arrival time offset
(INMIATO). It determines the INMAIATi histogram parameter range with
INMIATS. It also determines the start point of inter arrival time (IAT).
INM inter arrival time step: indicates the INM inter-arrival time step
(INMIATS). It determines the INMAIATi histogram parameter range with
INMIATO. It also determines the precision of IAT.
INM cluster continuation value: indicates the INM cluster continuation
(INMCC) value. It identifies a cluster and indicates the maximum number of
consecutive undamaged DMT symbols allowed in a cluster.
INM equivalent INP mode: indicates the INM equivalent impulse noise
protection (INP) mode. The method of calculating the equivalent INP varies
according to the mode. Mode 3 is recommended because the algorithm for the
mode is better than the algorithms for modes 0, 1, and 2.
After the service quality-related profiles are configured, ADSL2+ or VDSL2 ports can use
the profiles when being activated.
l
Configure spectrum-related profiles.

1.
Run the xdsl mode-specific-psd-profile quickadd command to quickly add an

xDSL-related PSD profile, or run the interactive xdsl mode-specific-psd-profile
add command to add an xDSL-related PSD profile.
2.
Run the xdsl line-spectrum-profile quickadd command to quickly add an xDSL

frequency spectrum profile, or run the interactive xdsl line-spectrum-profile add
command to add an xDSL frequency spectrum profile. The main parameters are as
follows:
transmode: Indicates the line transmission mode. By default, the system supports
all transmission modes. This parameter can adopt the default value for automatic
adaptation.
Issue 02 (2013-10-08)

233

Configuration Guide
mode specific PSD profile index: Indicates the PSD profile index. It specifies the
index of the PSD profile to be used.
g.998.4-rtx-mode: indicates G.998.4 retransmission. It is of numeral type and
ranges from 0 to 3.
0: RTX_FORBIDDEN
1: RTX_PREFERRED
2: RTX_FORCED
3: RTX_TESTMODE
3.
Run the xdsl upbo-profile quickadd command to quickly add an xDSL UPBO
profile, or run the interactive xdsl upbo-profile add command to add an xDSL UPBO
profile.
4.
Run the xdsl dpbo-profile quickadd command to quickly add an xDSL DPBO
profile, or run the interactive xdsl dpbo-profile add command to add an xDSL DPBO
profile.
5.
Run the xdsl rfi-profile quickadd command to quickly add an xDSL RFI profile, or
run the interactive xdsl rfi-profile add command to add an xDSL RFI profile.
After the spectrum-related profiles (except the PSD profile) are configured, ADSL2+ or
VDSL2 ports can use the profiles when being activated. The PSD profile is used in spectrum
profile and will not be directly bound to a port.
----End
Example
Assume that the following data plan is to be configured on VDSL2 profile 3 in TR165 mode for
VDSL2 Internet access service:
Service-related profile:
l
Channel mode: PTM
Minimum reserved downstream rate: 4096 kbit/s
Minimum expected throughput rate: 64 kbit/s (when the G.998.4 retransmission function
is enabled)
Service quality-related profile:

l
Maximum delay: 60 ms (when the G.998.4 retransmission is enabled)
Minimum delay is 1 ms (when the G.998.4 retransmission is enabled)
Channel mode: interleave
Maximum downstream interleave delay: 8 ms
Maximum upstream interleave delay: 2 ms
SNR margin: 6 dB
INMIATO: 3
INMIATS: 1
INMCC: 2
INM equivalent INP mode: 3
To add this VDSL2 profile in TR165 mode to enhance the connection stability and impulse noise
protection (INP) capability of the VDSL2 line, do as follows:
Issue 02 (2013-10-08)

234

Configuration Guide
huawei(config)#xdsl data-rate-profile quickadd 3 path-mode 2 rate 4096

4096 4096 4096 g.998.4-rtx etr-min 64
huawei(config)#xdsl inp-delay-profile quickadd 3 interleaved-delay 8 2
delay-max 60 60 delay-min 1 1
huawei(config)#xdsl noise-margin-profile quickadd 3 snr-margin 6 6 6 6
huawei(config)#xdsl inm-profile quickadd 3 inm-ds 3 1 2 3 inm-us 3 1 2
4096 4096
g.998.4-rtx
6 6
3

Prerequisites
VLAN application is specific to user types. For details on the VLAN application, see Table
4-7.
Table 4-7 VLAN application and plan
Usage
Scenarios
VLAN Plan
Remarks
The device
communicates
with a network
management
system (NMS) or
the devices are
cascaded.
VLAN type: standard VLAN
This plan is only applicable to

Ethernet ports.

+MAC
A standard VLAN only contains

multiple uplink ports. The Ethernet
ports in one VLAN can
communicate with each other and
the Ethernet ports in different
VLANs are separated.
N:1 access
This plan is used for converging

and transmitting the services of
multiple users to one VLAN. This
reduces the number of VLANs to
be used.

+MAC
A smart VLAN can contain

multiple uplink ports and multiple
service ports. The service ports in
one smart VLAN are separated.
The service ports in different
VLANs are also separated.
Issue 02 (2013-10-08)

235

Configuration Guide
Usage
Scenarios
VLAN Plan
Remarks
1:1 access
l Multi-ISP
wholesale
service (ISP is
the
abbreviation
of Internet
service
provider.)
VLAN attribute: stacking
A stacking VLAN packet contains

two VLAN tags (inner and outer
VLAN) assigned by the MA5616.
The outer VLAN identifies a
service (service VLAN) and the
inner VLAN identifies a user
(customer VLAN).

+MAC or S+C
The service used by a user is

identified by a unique VLAN ID (S
+C VLAN).
l VLAN ID
expansion
service
The upper layer broadband remote

access server (BRAS)
authenticates a service by the two
VLAN tags contained in the
service packets. In this manner, the
BRAS can receive packets from
more users.
On a Layer-2 upper layer network
of the MA5616, packets can also be
forwarded by the outer VLAN
+MAC ID. This function enables
ISPs to provide the wholesale
services.
Enterprise private
line service
access

+MAC or S+C
A QinQ VLAN contains an inner

VLAN tag from the user private
network, and an outer VLAN tag
assigned by the MA5616.
The outer VLAN forms a Layer 2
virtual private network (VPN) on
the user private network for
transparently transmitting user
services on the private network.

The uplink port on an access device connects to the upper layer device to forward access device
data to the upstream network and forward upper layer device data to users.
Prerequisites
The ID of the planned VLAN is already configured.
Issue 02 (2013-10-08)

236

Configuration Guide
Procedure
Step 1 Configure an upstream port for the VLAN.
Run port vlan command to add the upstream port to the VLAN.
Step 2 Configure the attribute of the upstream port.
If the default attribute of the upstream port does not meet the requirement for interconnection
of the upstream port with the upper-layer device, you need to configure the attribute. For
configuration details, see 3.3 Configuring the Attributes of the Upstream Port.
Step 3 (Optional) Configure redundancy backup for the uplink.
To ensure reliability of the uplink, two upstream ports must be available. That is, redundancy
backup of the upstream ports needs to be configured. For details, see 8.2 Configuring the Link
Aggregation of Uplink Ethernet Port .
----End
Example
Assume that the 0/0/1 and 0/0/0 upstream ports are to be added to VLAN 50. The 0/0/1 and
0/0/0 need to be configured into an aggregation group for double upstream accesses. For the two
upstream ports, the working mode is full-duplex (full) and the port rate is 100 Mbit/s. To
configure such upstream ports, do as follows:
huawei(config-if-eth-0/0)#speed 0 100
huawei(config-if-eth-0/0)#speed 1 100
huawei(config-if-eth-0/0)#quit
huawei(config)#link-aggregation 0/0 0 0/0 1 egress-ingress workmode lacp-static

To increase the network bandwidth of a user, you can bind multiple ports together.
Prerequisites
l
No traffic is carried on the ports to be bonded.
The ports to be bonded are in the deactivated state.
Context
The purpose of line bonding is to aggregate the services on multiple links to meet the high
bandwidth requirement of a single user. The following types of line bonding are supported:
l
Issue 02 (2013-10-08)
ADSL2+ port bonding. The device supports 2-pair bonding in the same chipset. The
operations on an ADSL2+ bonding group are performed on the active port in the group.
Currently, the ATM-based bonding is supported: It complies with ITU-T G998.1, which
defines an xDSL access bonding based on the ATM traffic stream.
237

Configuration Guide
VDSL2 port bonding. The device supports 2-pair bonding for VDSL2 ports on the same
or different boards.
SHDSL port bonding.

EFM bonding: applicable to the board whose chipset works in the PTM mode.
M-pair bonding: applicable to the board whose chipset works in the ATM mode.
Procedure
l
Configuring the ADSL2+ or VDSL2 line bonding.

When the bandwidth of an ADSL2+ or VDSL2 line cannot meet the actual user
requirements, bind multiple lines to increase bandwidth.
1.
In the global config mode, run the bonding-group add command to add a bonding
group.
scheme and peer-scheme support three modes: ATM, EFM, and TDIM. The mode
can only be set to ATM if the primary port is an ADSL2+ port, and the mode can only
be set to EFM if the primary port is a VDSL2 port.
scheme and peer-scheme must be set to the same mode.
NOTE
l A bonding group to be deleted must be in the disabled state.

l When a bonding group is enabled, its member ports must exist.
2.
Run the bonding-group link add command to add member ports to the bonding
group.
3.
Optional: Run the xdsl bonding-group-profile add command to create a bonding

group profile and configure line parameters for the bonding group.
NOTE
If a bonding group profile is configured for a bonding group and the port line profile is configured
for the member ports in the bonding group, the parameters take effect following the rules below:
l If the maximum and minimum transmission rates are set to 0 in the bonding group profile, the
transmission rates specified in the port line profile and the other parameters specified in the
bonding group profile take effect during the port activation.
l If the maximum and minimum transmission rates are not set to 0 in the bonding group profile,
all parameters specified in the bonding group profile take effect during the port activation.
4.
Run the active bonding-group command to enable the bonding group.
5.
Run the display bonding-group command to query the bonding group.
Configure the SHDSL line bonding.

When the bandwidth of an SHDSL line cannot meet the actual user requirements, bind
multiple lines to increase bandwidth.
Issue 02 (2013-10-08)
1.
In the global config mode, run the interface shl command to enter SHDSL mode.
2.
Run the port bind m-pair command to configure the SHDSL M-pair bonding. Run
the port bind efm command to configure the SHDSL EFM M-pair bonding.

238

Configuration Guide
NOTE
l Inter-chip bonding is not supported. On an SHDSL board, ports 0-3 share one chip, ports
4-7 share one chip, ports 8-11 share one chip, and ports 12-15 share one chip. The ports to
be bonded must be activated at the same time and must use the same line profile.
l Different line profiles can be applied to the ports in an EFM bonding group. When one port
goes offline, the status of the entire binding group remains unchanged.
l When the SHDSL board supports G.SHDSL.bis (including the extended standard annex
F), 1-pair bonding, 2-pair bonding, 3-pair bonding, and 4-pair bonding are supported,
corresponding to the maximum available bandwidth of 5696 x M (M is the pair number;
M is 1, 2, 3, or 4.) kbit/s. When the SHDSL board supports only G.991.2 (version 1), 2pair bonding and 4-pair bonding (two ports bonding and four ports bonding) are supported.
l To add or delete a bonding group, the member ports in the bonding group must be in the
deactivated state.
l After ports are bonded, all operations must be performed on the primary port.
l To delete a bonding group, only the ID of the primary port can be input.
----End
Example
huawei(config)#bonding-group add 1 primary-port 0/2/0 scheme atm
discovery-code 0100-0011-0110
huawei(config)#bonding-group link add 1 0/2/1
huawei(config)#active bonding-group 1
peer-scheme atm
The board chipset is in the ATM mode. To quadruple the bandwidth of a single port on SHDSL
board 0/4 through m-pair bonding, do as follows:
huawei(config)#interface shl 0/4
huawei(config-if-shl-0/4)#port bind m-pair 8-11
To add VDSL ports 0/1/0 and 0/1/1 to bonding group 1, with the discovery code of
0100-0011-0110, where port 0/1/0 is the primary port, the bonding group profile ID is 10, the
upstream and downstream target rates are both 200000 kbit/s, upstream and downstream
monitoring threshold rates are both 20000 kbit/s, and the rate alarm function is enabled, do as
follows:
huawei(config)#bonding-group add 1 primary-port 0/1/0 scheme efm peer-scheme efm
discovery-code 0100-0011-0110
huawei(config)#xdsl bonding-group-profile add 10 rate 64 200000 20000 20000 64
200000
20000 20000 monitoring-switch enable
huawei(config)#active bonding-group 1 profile-index 10

An xDSL can transmit services only when it is activated. This topic describes how to activate
an xDSL port and bind the port to an xDSL profile.
Prerequisites
An xDSL profile is created based on the data plan.
l
Issue 02 (2013-10-08)
Configuring ADSL2+ Profiles (in Normal Mode)

239

Configuration Guide
Configuring the ADSL2+ Profile (NGADSL Mode)
4.1.2 Configuring the SHDSL Profile
Configuring the VDSL2 Profile (TR129 Mode)
Configuring the VDSL2 Profile (TI Mode)
4.1.4 Configuring xDSL Profiles (TR165 Mode)
Activating (or activation) refers to the training between the xTU-C and the xTU-R. During
the training process, the system checks the line distance and conditions and performs a
negotiation between the xTU-C and the xTU-R to determine whether the port can work
under the conditions as preset in the line profile, such as upstream and downstream line
rates and noise margin.
If the training is successful, the communication connection is set up between the xTU-C
and the xTU-R, and the devices are ready for service transmission. This state is called the
activated state of a port. That is, services can be transmitted between the xDSL port and
the xTU-R.
If the xTU-R is online (powered on), the activating process is completed after the training
is successful. If the xTU-R is offline (powered on), the communication connection that is
set up during activation is terminated, and the xTU-C is in the listening state. When the
xTU-R goes online again, the training process begins automatically. When the training is
successful, the port is activated.
An xDSL port may be in the activating, activated, deactivated, or loopback state. Figure
4-5 shows the inter-conversion between xDSL port states.
Context
Figure 4-5 Inter-conversion between xDSL port states
NOTE
By default, the xDSL port is disconnected from the modem and is in the activating state. To bind an xDSL port
to an xDSL profile, deactivate the port first.
Procedure
l
Configure an asymmetric digital subscriber line 2 plus (ADSL2+) user port.

1.
Run the interface adsl command to enter ADSL mode.
2.
Activate the ADSL2+ port and bind the port to an xDSL profile.
In common ADSL mode (RFC2662 mode), run the activate command to activate
the ADSL2+ port and bind the port to an ADSL2+ line configuration profile.
Issue 02 (2013-10-08)

240

Configuration Guide
In NGADSL mode (RFC4706 mode), run the activate command to activate the
ADSL2+ port and bind the port to the ADSL2+ line template.
In ADSL TR165 mode, run the activate command to activate the ADSL2+ port
and bind the port to an ADSL2+ profile.
3.
Bind the ADSL2+ port to a line alarm profile or the line alarm template.
In common ADSL mode, run the alarm-config command to bind the ADSL2+
port to the line alarm profile.
In NGADSL mode, run the alarm-config command to bind the ADSL2+ port to
the line alarm template.
Configure a single-pair high-speed digital subscriber line (SHDSL) user port.

1.
Run the interface shl command to enter SHDSL mode.
2.
Run the activate command to activate the SHDSL port and bind the port to an SHDSL
line profile.
3.
Run the alarm-config command to bind the SHDSL port to an SHDSL line alarm
profile.
Configure a very-high-speed digital subscriber line 2 (VDSL2) user port.

1.
Run the interface vdsl command to enter VDSL mode.
2.
Activate the VDSL2 port and bind the port to a VDSL profile.
In common mode (TR129 mode), run the activate command to activate the VDSL2
port and bind the port to a VDSL2 line template.
In TI mode, run the activate command to activate the VDSL2 port and bind the
port to a VDSL2 profile.
In TR165 mode, run the activate command to activate the VDSL2 port and bind
the port to a VDSL2 profile.
3.
In common mode, run the alarm-config command to bind the VDSL2 port to the line
alarm template.
----End
Example
To activate ADSL2+ port 0/2/0 and bind line template 2 and alarm template 2 to it, do as follows:
huawei(config-if-adsl-0/2)#alarm-config 0 2
To activate SHDSL port 0/4/0 and bind line profile 2 and alarm profile 2 to it, do as follows:
huawei(config-if-shl-0/4)#deactivate 0
huawei(config-if-shl-0/4)#activate 0 2
huawei(config-if-shl-0/4)#alarm-config 0 2
In the common VDSL mode, to activate VDSL2 port 0/1/0 and bind line template 2 and alarm
template 2 to it, do as follows:
huawei(config)#interface vdsl 0/1
huawei(config-if-vdsl-0/1)#deactivate 0
huawei(config-if-vdsl-0/1)#activate 0 template-index 2
huawei(config-if-vdsl-0/1)#alarm-config 0 2
Issue 02 (2013-10-08)

241

Configuration Guide
In TR165 mode, to activate VDSL2 port 0/1/0 and bind DPBO profile 3, downstream rate profile
3, INP profile 3, INM profile 3, and alarm profile 2 to the port, do as follows:
huawei(config-if-vdsl-0/1)#activate 0 prof-idx dpbo 3 ds-rate 3 inm 3 inp-delay 3

A service port connects the user side to the network side and carries service data. To provide
services, a service port must be created.
Context
A service flow can carry a single service or multiple services. A multi-service flow is generally
used in the triple play service. A service port can carry a single service flow or multiple service
flows. The MA5616 can differentiate users or services based on the following modes if a service
port carries multiple service flows:
l
Based on the user virtual local area network (VLAN).
Based on the user packet encapsulation type. For example, the encapsulation type of the
dialup Internet service packet is Point-to-Point Protocol over Ethernet (PPPoE), and the
encapsulation type of the multicast service packet is Internet Protocol over Ethernet (IPoE).
Based on VLAN+user packet priority. For example, the priority of multicast services is
higher than that of the Internet access service.
Based on VLAN+user service encapsulation type.
Before creating a service port, run the display traffic table command to query whether the
expected service port already exists in the system. The system provides seven default traffic
profiles. The IDs of these profiles are numbered from 0 to 6.
If an expected service port does not exist in the system, run the traffic table ip command to
create a traffic profile based on site requirements. For details about how to configure a traffic
profile, see Configuring Traffic Management Based on Service Port.
Table 4-8 lists the default settings of a service port.
Table 4-8 Default settings of a service port
Issue 02 (2013-10-08)
Parameter
Default Setting
Traffic profile ID
0-6
Administration status
Activated
Maximum number of learnable MAC

addresses
CCUB: 255
CCUC: 600

242

Configuration Guide
Procedure
Step 1 Create a service port.
You can choose to create a single service port or multiple service ports in batches according to
requirements.
l
Run the service-port command to create a single service port. Service ports are classified
into single-service service ports and multi-service service ports.
Single-service service ports:
Select single-service or do not input multi-service to create a single-service service
port.
Multi-service service port based on the user-side VLAN:
Select multi-service user-vlan { untagged | user-vlanid | priority-tagged | otherall }.
untagged: When untagged is selected, user-side packets do not carry a tag.
user-vlanid: When user-vlanid is selected, user-side packets carry a tag and the value
of user-vlanid must be the same as the tag carried in user-side packets. The userside VLAN is the C-VLAN.
priority-tagged: When priority-tagged is selected, the VLAN tag is 0 and the
priorities of user-side packets are 0-7. (The highest priority is 7.)
other-all: If this parameter is specified, the created service port carries QinQ
transparent LAN service (TLS) services for enterprises. User packets are matched
based on the specified user VLAN (or untagged attribute) first. The unmatched
packets are transmitted on the TLS service port to the upstream network..
Multi-service service port based on user service encapsulation mode:
Specify multi-service user-encap user-encap.
user-encap: indicates the encapsulation type of the user packet.
The CCUB control board supports the IPoE and PPPoE encapsulation modes.
The CCUC control board supports the IPoE, PPPoE, IPv4oE, and IPv6oE
encapsulation modes. If the encapsulation mode of a packet is IPoE, the device can
transmit the packet whatever it is an IPv4 or IPv6 packet. If the encapsulation mode
of a packet is IPv4oE, the device can transmit the packet only when it is an IPv4
packet. If the encapsulation mode of a packet is IPv6oE, the device can transmit the
packet only when it is an IPv6 packet. Only one mode among IPoE, IPv4oE, and
IPv6oE can be set on a port.
Multi-service service port based on VLAN+user packet priority (802.1p):
Specify multi-service user-8021p user-8021p [ user-vlan user-vlanid ].
Multi-service service port based on VLAN+user packet encapsulation mode (userencap):
Specify multi-service user-vlan { untagged | user-vlanid | priority-tagged } userencap user-encap.
Issue 02 (2013-10-08)

243

Configuration Guide
NOTE
l The system supports creating service ports by index. One index maps one service port and the input
of a large number of traffic parameters is not required. Therefore, the configuration of service ports
is simplified. During the creation of a service port, index indicates the index of the service port and it
is optional. If it is not entered, the system starts to allocate an idle index from the currently configured
maximum index (regardless of whether it is deleted). After the maximum value range is exceeded, the
system searches from 0.
l vlan indicates the S-VLAN. An S-VLAN can only be a MUX VLAN or smart VLAN.
l The access mode can be ATM or PTM. In the ATM access mode, the VPI and VCI must be input and
must be the same as the VPI and VCI of the access terminal.
l rx-cttr is the same as outbound in terms of meanings and functions. Either of them indicates the index
of the traffic profile from the network side to the user side. tx-cttr is the same as inbound in terms of
meanings and functions. Either of them indicates the index of the traffic profile from the user side to
the network side.
Run the multi-service-port command to create service ports in batches.
Step 2 (Optional) Run the service-port desc command to configure description information about the
service port for facilitating maintenance. The information includes the use purpose and
application scenario of the service port.
Step 3 (Optional) Run the service-port index adminstatus command to configure the management
status of the service port. A service port is in activated state by default.
A service can be provided for a user only when the physical port connected to the user and the
corresponding service port are activated.
Step 4 (Optional) Run the mac-address max-mac-count service-port command to configure the
maximum number of MAC addresses that can be learned on the service port. This configuration
is used to limit the maximum number of PCs that can connect to the Internet using the same
account.
----End
Example
The MA5616 provides the Internet access service with the access rate 3072 kbit/s for the user
and up to 2 users can use the same account to access the Internet. The query result shows that
the system does not have a proper traffic profile and the user does not enable an account.
Therefore, the MA5616 does not provide the service for the user currently. To plan data for a
residential user who accesses the Internet in the ADSL2+ mode, do as follows:
huawei(config)#display traffic table ip from-index 0
{ <cr>|to-index<K> }:
Command:
display traffic table ip from-index 0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 512
18384
1024
36768
6 tag-pri
1 1024
34768
2048
69536
0 tag-pri
2 2048
67536
4096
135072
0 tag-pri
3 4096
133072
8192
266144
4 tag-pri
4 8192
264144
16384
528288
4 tag-pri
5 16384
526288
32768
1024000
4 tag-pri
6 off
off
off
off
0 tag-pri
---------------------------------------------------------------------------
Issue 02 (2013-10-08)

244

Configuration Guide
Total Num : 7
huawei(config)#traffic table ip index 8 cir 3072 priority 4 priority-policy localSetting
-----------------------------------------------TD Index
: 8
TD Name
Priority
: 4
Mapping Priority
: Mapping Index
Priority Policy
: local-pri
CIR
: 3072 kbps
CBS
: 100304 bytes
PIR
: 6144 kbps
PBS
: 198608 bytes
Referenced Status
: not used
-----------------------------------------------huawei(config)#service-port 3 vlan 100 adsl 0/2/0 vpi 1 vci 39 inbound traffictable index 8 outbound traffic-table index 8
huawei(config)#service-port 3 adminstatus disable
A residential user requests the Internet access service with the access rate 2048 kbit/s. To
facilitate service expansion in the future, the MA5616 uses the ADSL2+ mode to provide the
Internet access service, uses CVLAN 10 to identify users, and uses SVLAN 50 to identify
services. Query result shows that the system has a proper traffic profile to provide the Internet
access service. To facilitate maintenance, configure description for the service port.
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
//The
profile is a proper traffic profile.
6 off
off
off
off
0 tag-pri
---------------------------------------------------------------------------Total Num : 7
huawei(config)#service-port 4 vlan 50 adsl 0/2/0 vpi 1 vci 39 multi-service uservlan 10 inbound traffic-table index 5 outbound traffic-table index 5
huawei(config)#service-port desc 4 description HW_adsl/VlanID:50/uservlan/10
A residential user requests the Internet access service with the access rate 2048 kbit/s. To
facilitate service expansion in the future, the MA5616 adopts the SHDSL mode to provide the
Internet access service for the user. Query result shows that the system has a proper traffic profile.
Therefore, the system provides the Internet access service for the user immediately. To facilitate
maintenance, configure description for the service port.
Command:
Issue 02 (2013-10-08)

245

Configuration Guide
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 512
18384
1024
36768
6 tag-pri
1 1024
34768
2048
69536
0 tag-pri
2 2048
67536
4096
135072
0 tag-pri
//
The profile is a proper traffic profile.
3 4096
133072
8192
266144
4 tag-pri
4 8192
264144
16384
528288
4 tag-pri
5 16384
526288
32768
1024000
4 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
huawei(config)#service-port 5 vlan 50 shdsl mode ptm 0/4/0 inbound traffic-table
index 2 outbound traffic-table index 2
huawei(config)#service-port desc 5 description HW_shdsl/singleservice/VlanID:50
A commercial user requests the Internet access service with the access rate 8192 kbit/s. To
facilitate service expansion in the future, the MA5616 uses the VDSL mode to provide the
Internet access service, uses CVLAN 10 to identify users, and uses SVLAN 50 to identify
services. Query result shows that the system does not have a proper traffic profile. To configure
a required traffic profile and configure description information for facilitating maintenance, do
as follows:
Command:
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
Pri-Policy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------0 512
18384
1024
36768
6 tag-pri
1 1024
34768
2048
69536
0 tag-pri
2 2048
67536
4096
135072
0 tag-pri
3 4096
133072
8192
266144
4 tag-pri
4 8192
264144
16384
528288
4 tag-pri
5 16384
526288
32768
1024000
4 tag-pri
6 off
off
off
off
0 tag-pri
--------------------------------------------------------------------------Total Num : 7
-----------------------------------------------TD Index
: 9
TD Name
Priority
: 4
Copy Priority
: CTAG Mapping Priority: CTAG Default Priority: 0
Priority Policy
: local-pri
CIR
: 8192 kbps
CBS
: 264144 bytes
PIR
: 16384 kbps
PBS
: 526288 bytes
Color Mode
: color-blind
Referenced Status
: not used
-----------------------------------------------huawei(config)#service-port 6 vlan 50 vdsl mode ptm 0/1/0 multi-service user-vlan
10 inbound traffic-table index 9 outbound traffic-table index 9
huawei(config)#service-port desc 6 description HW_vdsl/VlanID:50/uservlan:10
Issue 02 (2013-10-08)

246

Configuration Guide
4.7 (Optional) Configuring the xPoA-xPoE Protocol

Conversion
xPoA to xPoE conversion involves the conversion from IP over ATM (IPoA) to IP over Ethernet
(IPoE) and the conversion from Point-to-Point Protocol over ATM (PPPoA) to Point-to-Point
Protocol over Ethernet (PPPoE). ATM is the abbreviation for asynchronous transfer mode
(ATM). xPoA packets cannot be transmitted on an IP network and must be converted into xPoE
packets. IPoA packets must be converted into IPoE and PPPoA packets must be converted into
PPPoE packets to be transmitted on an IP network. Protocol conversion is required when the
packet encapsulation mode is IPoA or PPPoA and is not required when the packet encapsulation
mode is IPoE or PPPoE.
Context
The principle of the IPoA protocol is different from that of the PPPoA protocol. In the PPPoA
mode, the BRAS automatically allocates a gateway address to the PPPoA user after the PPPoA
user passes the authentication on the BRAS and dialup is successful. Therefore, the default
gateway address need not be configured in the PPPoA mode. IPoA data is forwarded according
to the route to the destination IP address and the next hop IP address needs to be configured.
Therefore, the default gateway address needs to be configured in the IPoA mode.
Figure 4-6 provides the configuration flow for the xPoA-xPoE protocol conversion.
Figure 4-6 Flowchart for configuring the xPoA-xPoE protocol conversion
Table 4-9 lists the default settings of the xPoA-xPoE protocol conversion.
Issue 02 (2013-10-08)

247

Configuration Guide
Table 4-9 Default settings of the xPoA-xPoE protocol conversion

Parameter
Default Setting
Maximum number of the MAC addresses in the

MAC address pool
256
Status of the IPoA-IPoE protocol conversion
Disabled
Aging time of the IPoA user forwarding entry
1200s
Status of the PPPoA-PPPoE protocol conversion
Disabled
Status of the MRU negotiation function during the

PPPoA-PPPoE protocol conversion
Disabled
Procedure
l
Configure the IPoA-IPoE protocol conversion.

A user can access the Internet in the IPoA mode only after the IPoA-IPoE protocol
conversion is enabled.
1.
In the global config mode, run the mac-pool command to configure the MAC address
pool, which is used to allocate source MAC addresses to IPoA users. By default, the
number of the MAC addresses in the MAC address pool is 256, which can be changed
by setting parameter scope.
The MAC address encapsulated into packets during the IPoA-IPoE protocol
conversion is the MAC address allocated to the user from the MAC address pool.
2.
Run the ipoa enable command to enable the IPoA-IPoE protocol conversion. By
default, the IPoA-IPoE protocol conversion is disabled.
3.
Run the encapsulation command to set the user packet encapsulation mode (select
ipoa as the encapsulation mode).
NOTE
l IPoA encapsulation is not supported in the single-PVC for multiple services application.
l To switch the encapsulation mode from PPPoA to IPoA, you must change the encapsulation
mode to llc bridge first and then perform switching.
4.
Run the ipoa expire-time command to set the aging time of the IPoA user forwarding
entry. After receiving IPoA packets from users, the device refreshes IPoA forwarding
entry for the user. If the IPoA forwarding entry of a user is not refreshed within the
aging time, the device does not receive packets from the user and considers that the
user has gone offline by default. Therefore, the device will delete the forwarding entry
for the user. The default aging time of the IPoA user forwarding entry is 1200s. The
default value is recommended.
Configure the PPPoA-PPPoE protocol conversion.

A user can access the Internet through the PPPoA dialup only after the PPPoA-PPPoE
protocol conversion is enabled.
1.
Issue 02 (2013-10-08)
In the global config mode, run the mac-pool command to configure the MAC address
pool, which is used to allocate source MAC addresses to PPPoA users. By default, the
248

Configuration Guide
number of the MAC addresses in the MAC address pool is 256, which can be changed
by setting parameter scope.
The MAC address encapsulated into packets during the PPPoA-PPPoE conversion is
the MAC address allocated to the user from the MAC address pool.
2.
Run the pppoa enable command to enable the PPPoA-PPPoE protocol conversion.
By default, the PPPoA-PPPoE protocol conversion is disabled.
3.
Run the encapsulation command to set the user packet encapsulation mode (select
pppoa as the encapsulation mode).
NOTE
l PPPoA encapsulation is not supported in the single-PVC for multiple service or QinQ VLAN
application.
l To switch the encapsulation mode from IPoA to PPPoA, you must change the encapsulation
mode to llc bridge first and then perform switching.
4.
Run the pppoa mru command to enable PPPoA-PPPoE MRU negotiation. By default,
the PPPoA-PPPoE MRU negotiation is disabled. To avoid fragment and regrouping
of the PPPoA packets, enable the MRU negotiation function.
When the MRU negotiation is disabled, the PC initiates the PPPoE connection and
negotiates according to the 1492-byte MRU. In this case, packets need to be
segmented and reassembled.
When the MRU negotiation is enabled, the MA5616 identifies the PPPoA-PPPoE
converted packets, adds a tag to the packets and then sends them to the upper-layer
BRAS. Then, the BRAS negotiates with the CPE according to the 1500-byte MRU.
In this way, the MTU between the CPE and the BRAS is equal to the standard
Ethernet MTU. In this case, the packets need not be segmented or reassembled.
----End
Example
The MA5616 works in the L2 mode, the default gateway is the same as the IP address of the
upper-layer router, which is 10.1.1.1, the source IP address is 10.1.1.20, and the IPoA service
encapsulation mode is LLC. To enable the IPoA-IPoE conversion with the start MAC address
0000-0000-0001 in the MAC address pool that contains 200 MAC addresses, do as follows:
huawei(config)#mac-pool xpoa 0000-0000-0001 200
huawei(config)#ipoa enable
huawei(config)#encapsulation 0/1/0 vpi 0 vci 35 type ipoa llc srcIP 10.1.1.20 dstIP
10.1.1.1
The PPPoA service encapsulation mode is LLC. To enable the PPPoA-PPPoE protocol
conversion with the start MAC address 0000-1010-1000 in the MAC address pool that contains
200 MAC addresses, do as follows:
huawei(config)#pppoa enable
huawei(config)#encapsulation 0/1/0 vpi 0 vci 35 type pppoa llc

This topic describes how to configure the Vectoring function on a very-high-speed digital
subscriber line 2 (VDSL2). This technology can cancel the far-end crosstalk (FEXT) on a VDSL2
line and increases VDSL2 rates.
Issue 02 (2013-10-08)

249

Configuration Guide
Context
l
The Vectoring technology uses Vectoring groups to jointly transmit signals in the
downstream direction and receive signals in the upstream direction of a VDSL2 line.
The crosstalk on a VDSL2 line mainly comes from other lines in a bundle. Based on the
collected crosstalk values (which are Vectoring information), an access device performs
matrix calculation and outputs vectored crosstalk cancellation signals.
The Vectoring technology widely applies to fiber to the building (FTTB) and fiber to the
curb (FTTC) scenarios, because this technology has the best effect in increasing rates on a
VDSL2 line of 1000 meters or shorter.
The crosstalk among lines in a bundle is large. It is recommended that you set the lines in
a bundle to Vectoring group members.
Table 4-10 describes the default settings of the Vectoring function.

Table 4-10 Default settings of the Vectoring function
Parameter
Default Settings
Global Vectoring function
Disable
Global bandplan
998ade for bandplan type and type-a for US0 type
Activation policy for Vectoring legacy Limit

CPEs (CPE is the abbreviation for
customer premises equipment. A
Vectoring legacy CPE is a CPE that
does not support the Vectoring
function.)
Default Vectoring group ID
1
NOTE
l The system supports only one Vectoring group 1,
which is used to cancel the crosstalk on all frequency
bands of a VDSL2 line. The system currently does not
support modification of a Vectoring group.
l The system adds all VDSL2 ports to Vectoring group
1 by default. Adding members to or deleting members
from this group is not allowed.
Issue 02 (2013-10-08)
Default Vectoring profile ID
Upstream crosstalk cancellation

function specified in Vectoring profile
1
Enable
Downstream crosstalk cancellation

function specified in Vectoring profile
1
Enable

250

Configuration Guide
Procedure
Step 1 Run the xdsl vectoring bandplan-type command to set global bandplan type.
l As required by the Vectoring algorithm, the upstream and downstream frequency bands
cannot have duplicate bands in the entire system. Therefore, the bandplan type must be
configured globally.
l The global Vectoring bandplan type can be used only when the global Vectoring function is
not enabled.
l After the Vectoring function is enabled globally, if the bandplan in the line profile bound to
a VDSL2 port is not compatible with the globally configured bandplan, the upstream and
downstream frequency bands have duplicate bands, the port cannot be activated.
Step 2 (Optional) Run the xdsl vectoring legacy-cpe activate-policy command to configure the
Vectoring legacy CPE activation policy.
If a Vectoring legacy CPE (supporting G.993.2 and not supporting G.993.5) that is activated in
G.993.2 mode is connected to a Vectoring-enabled device, the crosstalk produced by this CPE
to other VDSL2 lines cannot be canceled, affecting the Vectoring performance in the entire
system. To minimize the impact, set the Vectoring legacy CPE activation policy based on site
requirements.
Step 3 Run the xdsl vectoring enable command to enable the global Vectoring function.
----End
Example
Assume that a device uses default bandplan values (998ade for bandplan type and type-a for
US0 type). In addition, the Vectoring legacy CPE activation policy is auto. To configure the
Vectoring function for the device as above, do as follows:
huawei(config)#xdsl vectoring bandplan-type 998ade us0-type type-a
uawei(config)#xdsl vectoring legacy-cpe activate-policy auto
huawei(config)#xdsl vectoring enable
Issue 02 (2013-10-08)

251

Configuration Guide
5 Configuring the Multicast Service (MVLAN Mode)
Configuring the Multicast Service (MVLAN

Mode)
About This Chapter

This topic describes how to configure the multicast service on the MA5616 in multicast virtual
local area network (MVLAN) mode.
Subscribers have high requirements on program playing time and diversity, bringing
opportunities to Internet service providers (ISPs) and carriers. The ISPs and carriers can meet
the requirements using Internet Protocol television (IPTV) multicast services. The multicast
feature of the MA5616 applies to live TV and near video on demand (NVOD) multicast video
services.
IP multicast supports point-to-multipoint (P2MP) and multipoint-to-multipoint transmissions,
improving transmission efficiency on the IP network, reducing network bandwidth consumption,
and reducing network load.
The MA5616 uses Internet Group Management Protocol (IGMP) proxy or IGMP snooping, and
the peer device uses IGMP proxy, IGMP snooping, or a multicast routing protocol.
Context
MVLAN refers to the VLAN carried by multicast data. MVLANs are classified by ISPs and
each multicast source is allocated with a unique VLAN for multicast domain control and
subscriber rights control. A device can provide independent multicast services using MVLANs.
The MA5616 supports Layer 2 multicast application. The data is forwarded by VLAN+multicast
MAC address, and each multicast program is identified by VLAN+multicast IP address uniquely
on the network.
5.1 Default Settings of the Multicast Service
This topic provides the default settings of the multicast service in the system, including the
configuration of multicast protocol, IGMP version, program configuration mode, bandwidth
management, program preview, and log function.
Issue 02 (2013-10-08)

252

Configuration Guide
5.2 Configuration Differences Between IPv4 Multicase and IPv6 Multicast

IPv6 multicast is the multicast service using IPv6 protocols. The configuration differences
between IPv4 multicase and IPv6 multicast lies on the commands. It is recommended that you
know well about how to configure IPv4 multicast and then configure IPv6 multicast based on
their differences.
5.3 Configuring the Multicast Service on a Single-NE Network
When the network topology is simple, the multicast service on a single NE can meet service
requirements. A single-NE network is stabler than a cascaded network and has a higher
bandwidth. However, a single-NE network requires more lines. The methods of configuring the
multicast service on a single NE are the same on a single-NE network and a cascaded network.
5.4 Configuring the Multicast Service on a Subtending Network
This topic describes how to configure the multicast service on the MA5616 on a subtending
network.
Issue 02 (2013-10-08)

253

Configuration Guide
5.1 Default Settings of the Multicast Service

This topic provides the default settings of the multicast service in the system, including the
configuration of multicast protocol, IGMP version, program configuration mode, bandwidth
management, program preview, and log function.
Table 5-1 lists the default settings of the multicast service of the MA5616.
Table 5-1 Default settings of the multicast service
Feature
Default Setting
Multicast protocol
Off
IGMP version
V3
Configuration mode of the multicast program
Configured statically
Multicast bandwidth management
Enabled
Multicast preview
Enabled
Multicast log function
Enabled
5.2 Configuration Differences Between IPv4 Multicase and

IPv6 Multicast
IPv6 multicast is the multicast service using IPv6 protocols. The configuration differences
between IPv4 multicase and IPv6 multicast lies on the commands. It is recommended that you
know well about how to configure IPv4 multicast and then configure IPv6 multicast based on
their differences.
Command Differences
Table 5-2 Command Differences Between IPv4 Multicase and IPv6 Multicast
NOTE
An en dash (-) indicates that IPv6 does not provide the commands provided in IPv4 and does not support the
multicast feature.
IPv4
IPv6
Supported or not by IPv6

Multicast
igmp leave-proxy
igmp ipv6 leave-proxy
Supported
igmp priority
igmp ipv6 priority
Supported
imgp report-proxy
igmp ipv6 report-proxy
Supported
Additional multicast function
Issue 02 (2013-10-08)

254

Configuration Guide
IPv4
IPv6

Multicast
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
display igmp policy
Not supported
igmp proxy router genquery-interval
igmp ipv6 router gen-queryinterval
Supported
igmp proxy router genresponse-time
igmp ipv6 router genresponse-time
Supported
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 initial-unsolicitedreport interval
Supported
igmp unsolicited-report
interval
igmp ipv6 unsolicited-report

interval
Supported
display igmp config vlan
display igmp ipv6 config

vlan
Supported
igmp proxy router timeout
Not supported
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
Protocol parameters
Multicast VLAN
Issue 02 (2013-10-08)

255

Configuration Guide
IPv4
IPv6

Multicast
display igmp config vlan
display igmp ipv6 config

vlan
Supported
igmp send global-leave
Not supported
Multicast users and privileges

debugging igmp
debugging igmp ipv6
Supported
igmp preview
Not supported
igmp preview auto-resettime
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 preview-profile
Not supported
igmp statistic reset
igmp ipv6 statistic reset
Supported
display igmp statistic
display igmp ipv6 statistic
Supported
display multicast flowstatistic
Not supported
display igmp log
Not supported
display igmp statistic
display igmp ipv6 statistic
Supported
Preview
Statistic
Logs
NOTE
The commands not listed are common both for IPv4 and IPv6.
Function Differences
Compared to IPv4 multicast, the IPv6 multicast does not support the following features.
l
Issue 02 (2013-10-08)
Transparent transmission of unknown IGMP multicast protocol packets

256

Configuration Guide
Preview of multicast programs
Statistic of the video flow
Global leave function
Transparent transmission policy and the IGMP policy for the VLAN not matched
Policy for transparent transmission and policy set in a VLAN service profile for processing
unmatched IGMP packets
Log report for IPv6 multicast
Configuration Differences
The IPv4 and IPv6 can use the same multicast VLANs. The IPv6 multicast can be deployed in
the existed IPv4 multicast VLANs. The IPv6 program can be added to the IPv4 multicast VLAN.
And the IPv6 program can be added to the privilege profiles. The configuration parameters for
users do not need to be changed.
5.3 Configuring the Multicast Service on a Single-NE

Network
When the network topology is simple, the multicast service on a single NE can meet service
requirements. A single-NE network is stabler than a cascaded network and has a higher
bandwidth. However, a single-NE network requires more lines. The methods of configuring the
multicast service on a single NE are the same on a single-NE network and a cascaded network.
Prerequisite
The upper-layer device and multicast source have been configured.
Data Plan
Before configuring the multicast video service, plan the data items as listed in Table 5-3.
Table 5-3 Data plan for configuring the multicast service on a standalone MA5616
Issue 02 (2013-10-08)
Device
Item
Remarks
MA5616
Multicast VLAN
Generally, a multicast VLAN is allocated

to each multicast ISP.
Layer 2 multicast protocol
IGMP proxy and IGMP snooping are

supported. An ONU generally uses IGMP
proxy.

257

Configuration Guide
Device
Item
Remarks
IGMP version
IGMP V3 and IGMP V2 are supported and

IGMP V3 is compatible with IGMP V2.
The version of the protocol supported by
the MA5616 cannot be later than that
supported by the upper-layer device, or
earlier than that supported by the user-side
device.
Configuration mode of the

multicast program
The multicast program can be configured

statically or generated dynamically.
Multicast general query and

group-specific query
parameters
The default values are adopted.
Program list
User authentication policy
Program bandwidth, uplink

port bandwidth, and user
bandwidth
Multicast log policy
Multicast logs can be reported to the log

server in syslog mode or in CDR mode.
Upper-layer
multicast router
IGMP version
The IGMP version of the upper-layer

multicast router cannot be earlier than the
IGMP version used by the MA5616.
Home gateway
or modem
IGMP version
The IGMP version of the CPE cannot be

later than the IGMP version used by the
MA5616.
5.3.1 Configuring Multicast Global Parameters

This topic describes the configuration of L2 multicast protocols (including IGMP proxy and
IGMP snooping). For IPv4, the MA5616 supports the global configuration and the configuration
based on the MVLAN. For IPv6, the MA5616 only supports the configuration based on the
MVLAN.
Context
Multicast parameters include general query, group-specific query, and policy of processing
multicast packets.
For the general query:
l
Issue 02 (2013-10-08)
Purpose: A general query packet is periodically sent by the MA5616 to check whether there
is any multicast user who leaves the multicast group without sending the leave packet.
258

Configuration Guide
Based on the query result, the MA5616 periodically updates the multicast forwarding table
and releases the bandwidth of the multicast user who has left the multicast group in time.
l
Principles: The MA5616 periodically sends the general query packet to all the online IGMP
users. If the MA5616 does not receive the response packet from a multicast user within a
specified time (robustness variable x interval of the general query + maximum response
time of the general query), it regards the user as having left the multicast group and deletes
the user from the multicast group.
For the group-specific query:

l
Purpose: A group-specific query packet is sent by the MA5616 after a multicast user who
is not configured with the quick leave attribute sends the leave packet. The group-specific
query packet is used to check whether the multicast user has left the multicast group.
Principles: When a multicast user leaves a multicast group, for example, switches to another
channel, the user sends a leave packet to the MA5616 in an unsolicited manner. If the
multicast user is not configured with the quick leave attribute, the MA5616 sends a groupspecific query packet to the multicast group. If the MA5616 does not receive the response
packet from the multicast user within a specified time (robustness variable x interval of the
group-specific query + maximum response time of the group-specific query), it deletes the
multicast user from the multicast group.
NOTE
The configuration steps for IPv4 multicast and IPv6 multicast are similar while the detailed commands are
different. This topic describes the configuration steps for IPv4 multicast, and provides the configuration
example for IPv6 multicast.
Table 5-4 lists the default settings of the multicast global parameters. In the actual application,
you can modify the values according to the data plan.
Table 5-4 Default settings of the multicast global parameters
Parameter
Default Value
General query parameter
Query interval: 125s

Maximum response time: 10s
Robustness variable (query times): 2
Group-specific query
parameter
Query interval: 1s
Maximum response time: 0.8s.
Robustness variable (query times): 2
Policy of processing multicast

packets
IGMP packet: normal (IGMP packets are processed as

controllable multicast)
Unknown multicast packet: discard
Procedure
Step 1 In global config mode, run the multicast-vlan command to enter MVLAN mode.
For IPv4, it is also to available to run the btv command to enter BTV mode.
Issue 02 (2013-10-08)

259

Configuration Guide
Step 2 Configure general query parameters.

1.
Run the igmp proxy router gen-query-interval command to set the interval of the general
query. By default, the interval is 125s.
2.
Run the igmp proxy router gen-response-time command to set the maximum response
time of the general query. By default, the time is 10s.
3.
Run the igmp proxy router robustness command to set the count of general queries. By
default, the count is 2.
Step 3 Configure group-specific query parameters.

1.
Run the igmp proxy router sp-query-interval command to set the interval of the groupspecific query. By default, the interval is 1s.
2.
Run the igmp proxy router sp-response-time command to set the maximum response
time of the group-specific query. By default, the time is 0.8s.
3.
Run the igmp proxy router sp-query-number command to set the count of group-specific
queries. By default, the count is 2.
Step 4 Configure the policy of processing multicast packets.

The default processing mode is as follows: The normal mode is adopted for IGMP packets, that
is, IGMP packets are processed under control. The discard mode is adopted for unknown
multicast packets, that is, unknown multicast packets are discarded.
The default policy is adopted for multicast packets. That is, the policy need not be changed.
When configuring other services, you can run the igmp policy command to configure the policy
of processing multicast packets if you need to control the forwarding of multicast packets.
Step 5 Run the display igmp config global command to check whether the parameters are configured
correctly.
----End
Example
To configure IPv4 multicast general query parameters by setting the query interval to 150s,
maximum response time to 20s(the time value to be set is 200), and query count to 3, do as
follows:
huawei(config)#btv
huawei(config-btv)#igmp proxy router gen-query-interval 150
huawei(config-btv)#igmp proxy router gen-response-time v3 200
huawei(config-btv)#igmp proxy router robustness 3
To configure IPv4 multicast group-specific query parameters by setting the query interval to
20s, maximum response time to 10s(the time value to be set is 100), and query count to 3, do as
follows:
huawei(config)#btv
huawei(config-btv)#igmp proxy router sp-query-interval 200
huawei(config-btv)#igmp proxy router sp-response-time v3 100
huawei(config-btv)#igmp proxy router sp-query-number 3
To configure IPv6 multicast general query parameters by setting the query interval to 150s,
maximum response time to 20s(the time value to be set is 200), and query count to 3, do as
follows:
huawei(config)#multicast-vlan 30
huawei(config-mvlan30)#igmp ipv6 router gen-query-interval 150
Issue 02 (2013-10-08)

260

Configuration Guide
huawei(config-mvlan30)#igmp ipv6 router gen-response-time v2 200

huawei(config-mvlan30)#igmp ipv6 router robustness 3
To configure IPv6 multicast group-specific query parameters by setting the query interval to
20s, maximum response time to 10s(the time value to be set is 100), and query count to 3, do as
follows:
huawei(config-mvlan30)#igmp ipv6 router sp-query-interval 200
huawei(config-mvlan30)#igmp ipv6 router sp-response-time v2 100
huawei(config-mvlan30)#igmp ipv6 router sp-query-number 3
Result
Check whether the IPv4 multicast general query parameters and group-specific query parameters
are configured correctly.
huawei(config)#btv
huawei(config-btv)#display igmp config global
---------------------------------------------------------------------Authorization
: enable
Robustness variable
: 3
//The count of general queries
is 3.
General query interval(s)
: 150
//The interval of the general
query is 150s.
V2 general query response time(0.1s) : 100
//The maximum response time of
the general query is 20s.
Specific query interval(0.1s)
: 200
//The interval of the groupspecific query is 10s.
V2 specific query response time(0.1s) : 8
//The maximum response time of
the group-specific query is 10s.
Specific query number
: 3
//The count of group-specific
queries is 3.
V2 router present timeout(s)
: 400
User action report switch
: disable
Preview switch
: enable
Recognition time(s)
: 30
The time of reset preview-count
: 04:00:00
Auto create log interval(h)
: 2
Uplink port mode
: default
Bandwidth management switch
: enable
CDR auto report interval(s)
: 600
CDR auto report number
: 200
CDR switch
: disable
IGMP Packet encapsulation
: all
IGMP ECHO switch
: disable
Router IP
: 192.168.1.1
Initial unsolicited report interval(s): 1
Query offline user switch
: disable
BTV Forward Mode
: MVLAN
IGMP process-preferred mode
: IGMP policy
----------------------------------------------------------------------
Check whether the IPv6 multicast general query parameters and group-specific query parameters
for MVLAN 30 are configured correctly.
huawei(config)#display igmp ipv6 config vlan 30
---------------------------------------------------------------------------IGMP IPv6 mode
: off
IGMP IPv6 version
: IGMP IPv6 v2
Log switch
: enable
Issue 02 (2013-10-08)

261

Configuration Guide
Default uplink port

: Report proxy switch
: disable
Leave proxy switch
: disable
Unsolicited report interval(s)
: 10
IGMP IPv6 priority
: 6
Program match mode
: enable
Program match group
: Robustness variable
: 3
//The count of general
queries is 3.
: 150
//The interval of the
general query is 150s.
V1 general query response time(0.1s)
: 100
: 200
//The maximum response time
of the general query is 20s.
: 200
//The interval of the groupspecific query is 10s.
//The maximum response time
of the group-specific query is 10s.
: 3
//The count of group-specific
queries is 3.
Initial unsolicited report interval(s) : 1
----------------------------------------------------------------------------
5.3.2 Configuring the Multicast Program

After the program is configured, the multicast user with the corresponding rights can watch or
preview the program.
Prerequisites
The multicast VLAN to which the multicast program belongs must exist. For the details on
configuring the VLAN, see 3.5 Configuring a VLAN.
Context
In multicast services, multicast VLANs are used to identify different multicast Internet service
providers (ISPs). Generally, a multicast VLAN is allocated to each multicast ISP for the VLANbased management of multicast programs, multicast protocols, and IGMP versions, and for the
control of multicast domain and user rights.
Create a common VLAN before creating a multicast VLAN.
l
A multicast VLAN can be the same as a unicast VLAN. In this case, the multicast VLAN
and the unicast VLAN share the same traffic channel.
A multicast VLAN can be different from a unicast VLAN. In this case, the multicast VLAN
and the unicast VLAN use different traffic channels.
NOTE
For MA5616, the configuration steps for IPv4 multicast and IPv6 multicast are similar while the detailed
commands are different. This topic describes the configuration steps for IPv4 multicast, and provides the
configuration example for IPv6 multicast.
Table 5-5 lists the default settings of the multicast VLAN attributes, including the Layer 2
multicast protocol, IGMP version, multicast program, and multicast upstream port.
Issue 02 (2013-10-08)

262

Configuration Guide
Table 5-5 Default settings of the multicast VLAN attributes

Parameter
Default Value
Program matching mode
enable (static configuration mode)
Multicast upstream port mode
default
Layer 2 multicast protocol
off (multicast function disabled)
IGMP version
v3
Priority of forwarding IGMP

packets by the upstream port
Procedure
Step 1 Configure multicast programs.
A multicast program in a multicast VLAN can be configured statically, generated dynamically
or by a combined mode of statically configuration and dynamically generation.
l
Static configuration mode: Configure a program list before the users watch video programs.
In this mode, the rights profile can be used to implement controllable multicast. The
program list and the rights profile, however, need to be maintained based on the change of
video services. The program host, program prejoin, and multicast bandwidth management
functions are supported.
1.
In multicast VLAN mode, run the igmp match mode enable command to set the static
configuration mode. In this case, you need to configure the multicast program in advance.
The program in the multicast VLAN is configured statically by default.
2.
In multicast VLAN mode, run the igmp program add [name name ] ip ip-addr [ sourceip
ip-addr ] [ hostip ip-addr ] command to add a multicast program.
NOTE
If the IGMP version of the multicast VLAN is V2, the source IP address of the program in the multicast
VLAN cannot be configured.
3.
Add a rights profile.

In BTV mode, run the igmp profile add command to add a rights profile.
4.
Bind the rights profile to the program.

In BTV mode, run the igmp profile command to bind the rights profile to the program and
set the rights to watch the program.
NOTE
If a user is bound with multiple rights profiles and the rights to a program are different in these
profiles, the user uses the rights with the highest priority. You can run the igmp right-priority
command to adjust the priorities of the four rights: watch, preview, forbidden, and idle. By default,
the priorities of the four rights are forbidden > preview > watch > idle.
Issue 02 (2013-10-08)
Dynamic generation mode: A program is generated according to the request of the user. In
this mode, the program list is not required; however, the functions such as program
management, user multicast bandwidth management, program preview, and program
prejoin are not supported.
263

Configuration Guide
1.
Run the igmp match mode disable command to configure the dynamic generation mode.
CAUTION
The igmp match mode { enable | disable } command can be executed only when the IGMP
mode is disabled.
2.
Run the igmp match group command to configure the IP address range of the program
group that can be dynamically generated in the multicast VLAN. After the configuration,
the user can request for only the programs whose IP addresses are within the specified
range.
A user port can join multiple multicast VLANs. Among all the multicast VLANs of a user
port, only one multicast VLAN is allowed to have dynamically generated programs.
Combined mode of statically configuration and dynamically generation. Configure part of

the programs statically for the multicast VLAN in advance. And other programs can be
generated according to the request of the user. In the combined, users can switch to the
statically configured programs more quickly.
1.
Run the igmp match mode disable command to configure the dynamic generation mode.
CAUTION
The igmp match mode { enable | disable } command can be executed only when the IGMP
mode is disabled.
2.
Run the igmp match group command to configure the IP address range of the program
group that can be dynamically generated in the multicast VLAN. After the configuration,
the user can request for only the programs whose IP addresses are within the specified
range.
3.
Run the igmp program add [name name ] ip ip-addr [ sourceip ip-addr ] [ hostip ipaddr ] command to add a statical multicast program.
NOTE
If the IP addresses of the static program and dynamic program overlap each other, the static program
is activated first.
Step 2 Configure the multicast uplink port.

1.
In multicast VLAN mode, run the igmp uplink-port command to configure the multicast
uplink port. After the configuration, all the packets from the multicast VLAN are forwarded
or received through this uplink port.
2.
In BTV mode, run the igmp uplink-port-mode command to change the mode of the
multicast uplink port. By default, the multicast uplink port is in default mode. On the MSTP
network, the multicast uplink port adopts the MSTP mode.
l Default mode: If a multicast VLAN contains only one uplink port, the IGMP packets
that go upstream can be sent only through this port. If a multicast VLAN contains
multiple uplink ports, the IGMP packets that go upstream are sent through all the uplink
ports.
Issue 02 (2013-10-08)

264

Configuration Guide
l MSTP mode: This mode is applicable to the MSTP network.In MSTP mode, run the
igmp default uplink-port command to set a default uplink port.
Step 3 Select the multicast protocol.
Run the igmp mode { proxy | snooping } command to select the L2 multicast protocol. By
default, the multicast function is disabled in the system.
In terms of multicast processing mode, the MA5616 supports IGMP proxy and IGMP snooping.
IGMP proxy and IGMP snooping both support multicast video data forwarding; however, the
two modes have different processing mechanisms.
l IGMP snooping obtains desired information and maintains the multicast forwarding entries
by listening to the IGMP packets in the communication between the user and the multicast
router.
l IGMP proxy intercepts the IGMP packets between the user and the multicast router, processes
the IGMP packets, and forwards the IGMP packets to the upper-layer multicast router. For
multicast users, the MA5616 is a multicast router. For multicast routers, the MA5616 is a
multicast user.
In IGMP snooping mode, proxy can be enabled for the report packet and leave packet. When a
multicast user joins or leaves a multicast program, the MA5616 can implement IGMP proxy.
IGMP snooping and IGMP proxy are controlled separately.
l Run the igmp report-proxy enable command to enable the proxy of the snooping report
packet. When the first user requests for a program, after authenticating the user, the
MA5616 sends the user report packet to the network side and obtains a corresponding
multicast stream from the multicast router. The MA5616 does not send the report packets
from the subsequent users for joining the same program to the network side any more.
l Run the igmp leave-proxy enable command to enable the proxy of the snooping leave
packet. When the last user requests for leaving a program, the MA5616 sends the user leave
packet to the network side and notifies the upper-layer device of stopping sending multicast
streams. The MA5616 does not send the leave packets from the users before the last user to
the network side.
Step 4 Configure the IGMP version.
Run the igmp version{ v2 | v3 } command to configure the IGMP version. By default, IGMPv3
is enabled in the system. If the upper-layer and lower-layer devices on the network are of the
IGMPv2 version and cannot recognize the IGMPv3 packets, run this command to switch the
IGMP version.
CAUTION
When you run the igmp version{ v2 | v3 } command to configure the IGMP version:
l This command can be executed only when the IGMP mode is disabled.
l The system will delete the programs with source IP addresses in this multicast VLAN. In
this case, if a user is online, the system will force the user to go offline.
IGMPv3 is compatible with IGMPv2 in packet processing. If IGMPv3 is enabled on the
MA5616 and the upper-layer multicast router switches to IGMPv2, the MA5616 automatically
Issue 02 (2013-10-08)

265

Configuration Guide
switches to IGMPv2 when receiving the IGMPv2 packets. If the MA5616 does not receive any
IGMPv2 packets within the preset IGMPv2 time to live (TTL) time, it automatically switches
back to IGMPv3. In BTV mode, run the igmp proxy router timeout command to set the
IGMPv2 TTL time. By default, the TTL time is 400s.
Step 5 Change the priority for forwarding IGMP packets.
Run the igmp priority command to change the priority for forwarding the IGMP packets on the
uplink port. By default, the priority is 6 and it need not be changed.
l In IGMP proxy mode, the IGMP packets sent to the network side adopt the priority set through
the igmp priority command in the multicast VLAN.
l In IGMP snooping mode, the IGMP packets forwarded to the network side adopt the priority
of the user traffic stream. The priority of the traffic stream is set through the traffic profile.
Step 6 Check whether the configuration is correct.
l Run the display igmp config vlan command to query the attributes of the multicast VLAN.
l Run the display igmp program vlan command to query the information about the multicast
program in the multicast VLAN.
----End
Example
Assume that the VLAN ID is 10, the program is configured statically, the IP address of the
program is 224.1.1.1, the program bandwidth is 5000 kbit/s, the multicast uplink port is 0/0/1,
the IGMP proxy is enabled, and the IGMP version is V3. To configure a multicast VLAN and
a program for IPv4 multicast with these attributes, do as follows:
huawei(config-mvlan10)#igmp match mode enable
Command has been executed successfully
huawei(config-mvlan10)#igmp version v3
huawei(config-mvlan10)#igmp mode proxy
Are you sure to change IGMP mode?(y/n)[n]:y
Command is being executed. Please wait...
huawei(config-mvlan10)#igmp program add name movie ip 224.1.1.1 sourceip
10.10.10.10
hostip 10.0.0.254 bandwidth 5000
huawei(config-mvlan10)#igmp uplink-port 0/0/1
Assume that the VLAN ID is 10, the program is generated dynamically, the IP address for the
dynamic program group ranges from 224.1.1.1 to 224.1.1.100, the multicast uplink port is
0/0/1, the IGMP proxy is enabled, and the IGMP version is V3. To configure a multicast VLAN
and a program for IPv4 multicast with these attributes, do as follows:
huawei(config-mvlan10)#igmp match mode disable
huawei(config-mvlan10)#igmp match group ip 224.1.1.1 to-ip 224.1.1.100
Issue 02 (2013-10-08)

266

Configuration Guide

Assume that the VLAN ID is 101, the program is generated in combined mode of static
configuration and dynamic generation. the IP address of the static program is 224.1.1.1, the
source IP address is 10.10.10.10, the program bandwidth is 5000 kbit/s, the IP address for the
dynamic program group ranges from 224.1.1.10 to 224.1.1.50, the multicast uplink port is
0/0/1, the IGMP proxy is enabled, and the IGMP version is V3. To configure a multicast VLAN
and a program for IPv4 multicast with these attributes, do as follows:
huawei(config-mvlan101)#igmp program add name movie ip 224.1.1.1 sourceip
10.10.10.10
hostip 10.0.0.254 bandwidth 5000
Assume that the VLAN ID is 101, the program is configured statically, the IP address of the
program is ffff::1, the IP address of the source IP is 2000::1, the program bandwidth is 5000
kbit/s, the multicast uplink port is 0/0/1, the IGMP proxy is enabled, and the MLD version is
V2. To configure a multicast VLAN and a program for IPv6 multicast with these attributes, do
as follows:
huawei(config-mvlan101)#igmp ipv6 match mode
enable
huawei(config-mvlan101)#igmp program add name movie ipv6 ffff::1 source-ipv6
2000::1
bandwidth 5000
huawei(config-mvlan101)#igmp ipv6 mode
proxy
Are you sure to change IGMP IPv6 mode?(y/n)
[n]:y
huawei(config-mvlan101)#igmp ipv6 version
v2
Result
Query the attributes and information of the program in the multicast VLAN for IPv4 multicast
in static configuration mode.
huawei(config)#display igmp config vlan 10
---------------------------------------------------------------------IGMP mode
: proxy
//IGMP proxy protocol
IGMP version
: IGMP V3
//IGMP V3
Log switch
:
enable
Issue 02 (2013-10-08)

267

Configuration Guide
Default uplink port

:
Report proxy switch

:
disable
Leave proxy switch
:
disable
:
10
IGMP priority
:
6
Send global leave switch
:
enable
Program match mode
: enable
//The program matching mode is
enabled and the multicast program is configured statically.
Program match group
:
Robustness variable
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
V2 specific query response time(0.1s) : NotConfig
: NotConfig
: NotConfig
Initial unsolicited report interval(s) : NotConfig
---------------------------------------------------------------------huawei(config)#display igmp program vlan 10 ip 224.1.1.1
{ <cr>||<K> }:
Command:
display igmp program vlan 10 ip 224.1.1.1
--------------------------------------------Program index
: 0
Create mode
: static
Program name
: movie
IP address
: 224.1.1.1
//IP address of the multicast program
VLAN ID
: 10
Host attribute
: enable
Log attribute
: enable
Prejoin attribute
: disable
Unsolicited attribute
: disable
Priority
: 7
Host IP
: 0.0.0.0
Bandwidth(kbps)
: 5000
//The bandwidth of the multicast program
is 5000 kbit/s.
SourceIP
: 10.10.10.10
Preview Profile
: 0
Numbers of watching
: 0
Program Grade
: ---------------------------------------------
in dynamic generation mode.
huawei(config-mvlan10)#display igmp config vlan 10
---------------------------------------------------------------------IGMP mode
:
proxy
IGMP version
: IGMP
V3
Log switch
:
enable
Default uplink port
:
Report proxy switch
:
disable
Issue 02 (2013-10-08)

268

Configuration Guide
Leave proxy switch

:
disable
:
10
IGMP priority
:
6
:
enable
Program match mode
: disable
//The program matching mode
is disabled and the multicast program is generated dynamically.
Program match group
: 224.1.1.1 ~ 224.1.1.100
Robustness variable
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
----------------------------------------------------------------------
in combined mode of static configuration and dynamic generation.
huawei(config)#display igmp config vlan 101
---------------------------------------------------------------------IGMP mode
: proxy
IGMP version
: IGMPv3
Log switch
: enable
Default uplink port
: disable
Leave proxy switch
: disable
: 10
IGMP priority
: 6
: enable
Program match mode
: disable
Program match group
: 224.1.1.10 ~ 224.1.1.50
Robustness variable
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
: NotConfig
---------------------------------------------------------------------huawei(config)#display igmp program vlan 101 ip 224.1.1.1
{ <cr>||<K> }:
Command:
display igmp program vlan 101 ip 224.1.1.1
--------------------------------------------Program index
: 0
Create mode
: static
Program name
: movie
IP address
: 224.1.1.1
VLAN ID
: 101
Host attribute
: enable
Log attribute
: enable
Prejoin attribute
: disable
: disable
Issue 02 (2013-10-08)

269

Configuration Guide
Priority
: 7
Host IP
: 10.0.0.254
Bandwidth(kbps)
: 5000
Source IP
: 10.10.10.10
Preview profile
: 0
Numbers of watching
: 0
Program grade
: ---------------------------------------------
in static configuration mode.
huawei(config)#display igmp ipv6 config vlan 101
---------------------------------------------------------------------------IGMP IPv6 mode
: proxy
IGMP IPv6 version
: IGMP IPv6 v2
Log switch
: enable
Default uplink port
: disable
Leave proxy switch
: disable
: 10
IGMP IPv6 priority
: 6
Program match mode
: enable
Program match group
: Robustness variable
: 2
: 125
: 100
: 100
: 10
: 2
Initial unsolicited report interval(s) : 1
---------------------------------------------------------------------------huawei(config)#display igmp program vlan 101 ipv6 ffff::1
{ <cr>||<K> }:
Command:
display igmp program vlan 101 ipv6 ffff::1
--------------------------------------------Program index
: 0
Create mode
: static
Program name
: movie
IP address
: FFFF::1
VLAN ID
: 101
Host attribute
: enable
Log attribute
: enable
Prejoin attribute
: disable
: disable
Priority
: 7
Host IP
: Bandwidth(kbps)
: 5000
Source IP
: 2000::1
Preview profile
: 0
Numbers of watching
: 0
Program grade
: ---------------------------------------------
5.3.3 Configuring the Multicast User

When a user needs to watch the multicast program, you need to configure the user as a multicast
user because only a multicast user can watch the multicast program.
Issue 02 (2013-10-08)

270

Configuration Guide
Prerequisites
Before configuring a user as a multicast user, you must create a service channel and ensure that
this channel is normal.
For an xDSL user, you must perform the following operations:
1.
2.
3.
4.
Context
Add a multicast user and bind the multicast user with the multicast VLAN to create a multicast
member. Bind the rights profile to the multicast user to implement multicast user authentication.
Table 5-6 lists the default settings of the attributes related to the multicast user.
Table 5-6 Default settings of the attributes related to the multicast user
Parameter
Default Value
Limitation on the number of

programs that can be watched by
the multicast user
Number of programs that can be watched concurrently:

32
Quick leave mode of the

multicast user
MAC-based
Global switch of multicast user

authentication
enable
Maximum number of programs of different priorities that

can be watched: no limit
Procedure
Step 1 In global config mode, run the btv command to enter BTV mode.
Step 2 Configure the multicast user and the multicast user attributes.
1.
Add the multicast user.

Run the igmp user add command to add the multicast user.
Issue 02 (2013-10-08)

271

Configuration Guide
NOTE
The igmp user add command supports adding the multicast user by using the following methods.
l Use the service-port or the service-port-list parameter to add the specified virtual service port as the
multicast user.
l Use the smart-vlan parameter to add the virtual service ports in the specified smart-vlan as the
multicast users.
l Use the virtual service port parameter (including port, slot, etc.) to add the matching virtual service
ports as the multicast users.
A user port can join multiple multicast VLANs. Among all the multicast VLANs of a user port, only one
multicast VLAN is allowed to have dynamically generated programs.
2.
Configure the maximum number of programs that can be watched by the multicast user.
l Run the igmp user add or the igmp user modify command with the max-program
parameter to configure the maximum number of programs that can be concurrently
watched by the multicast user. The maximum number is 32.
l Run the igmp user watch-limit command to configure the maximum number of
programs of different priorities that can be watched by the multicast user.
3.
Configure the quick leave mode of the multicast user.

Run the igmp user add or the igmp user modify command with the quickleave
{ immediate | disable | mac-based } parameter to configure the leave mode of the multicast
user. By default, the leave mode is the mac-based mode.
l immediate: After receiving the leave request packet of the multicast user, the system
immediately deletes the multicast user from the multicast group.
l disable: The quick leave function is disabled and a user can leave normally. The system
sends the specific group query packet after receiving the leave packet of the multicast
user. Within the set aging time, if the system does not receive the report packet of the
multicast user, the user is considered as offline and the system deletes the multicast user
from the multicast group. This is a standard mode defined in IGMP.
l mac-based: Indicates the quick leave mode based on the MAC address. The system
detects the MAC address in the leave packet of the user. If it is the same as the MAC
address in the report packet of the user and the user is the last one who watches the
multicast program in the multicast group, the system immediately deletes the multicast
user from the multicast group. Otherwise, the system does not delete the multicast user.
In this mode, the application scenario with multiple terminals is supported.
NOTE
For the quick leave principles and selection principles, see User-Side Interoperating Technologies in the
Feature Description.
Step 3 Configure the multicast user authentication.

To control the rights of a multicast user, you can enable the multicast user authentication
function. Binding the rights profile to the multicast user implements multicast user
authentication.
1.
Configure the multicast user authentication function.

Run the igmp user add or the igmp user modify command with the { auth | no-auth }
parameter to configure whether to authenticate a multicast user.
Issue 02 (2013-10-08)

272

Configuration Guide
NOTE
After configuring multicast user authentication, you need to enable the global authentication function to
make the configuration take effect. By default, the global authentication function of multicast user is
enabled. You can run the igmp proxy authorization command to change the configuration.
2.
Bind the rights profile to the multicast user. Binding the rights profile to the multicast user
implements user authentication.
Run the igmp user bind-profile command to bind the rights profile to the multicast user.
After the binding, the multicast user has the rights to the programs configured in the profile.
Step 4 Bind the multicast user to the multicast VLAN.

In multicast VLAN mode, run the igmp multicast-vlan member command to bind the user to
the multicast VLAN. Then, the multicast user becomes a multicast member of the multicast
VLAN and can request for the programs configured in the multicast VLAN.
Step 5 Run the display igmp user command to check whether the multicast user is configured correctly.
----End
Example
Assume that multicast user (port) 0/1/0 (with an index of the user traffic stream 100) is added
to multicast VLAN 10, the user authentication and the log report function are enabled, the
maximum number of programs that can be concurrently watched is 4, and rights profile music
is bound to the user. To perform the configurations, do as follows:
huawei(config)#btv
huawei(config-btv)#igmp user add service-port 100 auth log enable max-program 4
huawei(config-btv)#igmp user bind-profile service-port 100 profile-name music
huawei(config-btv)#quit
huawei(config-mvlan10)#igmp multicast-vlan member service-port 100
Assume that there are three virtual service ports (100, 101, and 102) in VLAN 10. These three
virtual service ports are separately on ports 0/1/0, 0/1/1, and 0/1/2. Add these three virtual service
ports as multicast users, set the user authentication and the log report function to enabled, set
the maximum number of programs that can be concurrently watched to 4, and bind the rights
profile music to the users, do as follows:
huawei(config)#btv
huawei(config-btv)#igmp user add smart-vlan 10 auth log enable max-program 4
huawei(config-mvlan10)#igmp multicast-vlan member service-port-list 100,101,102
Result
Check whether the multicast user is configured correctly.
l
Check the multicast users added by the index of the service-port.

huawei(config)#display igmp user 0 //0 is the index of the multicast user. You
can run the
//display igmp user all command
to query the index of the multicast user.
{ <cr>||
<K> }:
Issue 02 (2013-10-08)

273

Configuration Guide
Command:
display igmp user
0
User
State
offline
Authentication
Quick leave
based
IGMP flow ID
100
Video flow ID
100
Log switch
enable
Bind profiles
1
IGMP version
v3
Current version
Available programs
that can be
: 0/1/0
:
//Port of the multicast user
: auth
: MAC-
//Authentication is required.
:
:
:
:
: IGMP
: IGMP v3
: 4
//The maximum number of programs

//concurrently watched is 4.
Global Leave
disable
User MaxBandWidth
limit
Used bandwidth(kbps)
0
Used
bandwidth
to max bandwidth(%)
Total video bandwidth
Mcast video bandwidth
Bind profile
list
:
: no:
:
:
:
--------------------------------------------index
Profile name
Program
number
--------------------------------------------0
music
0
is music.
//The bound rights profile
--------------------------------------------Total: 1
Check the multicast users added by the smart-vlan.

huawei(config)#display igmp user smart-vlan 10
{ <cr>||
<K> }:
Command:
display igmp user smart-vlan
10
Command is being executed. Please
wait...
-----------------------------------------------------------------------------User index Bind
State
Auth
Quick
IGMP
Video
Log
Available
Issue 02 (2013-10-08)

274

Configuration Guide
profiles
leave
flow ID flow ID switch
programs
-----------------------------------------------------------------------------0
1
offline auth
MAC-based 100
100
enable
4
1
1
offline auth
MAC-based 101
101
enable
4
2
1
offline auth
MAC-based 102
102
enable
4
-----------------------------------------------------------------------------Total:
3
5.3.4 (Optional) Configuring the Multicast Bandwidth

To limit the multicast bandwidth of a user, you can enable the multicast bandwidth management
function, namely, connection admission control (CAC), and then control the bandwidth of the
multicast user by setting the program bandwidth and the user bandwidth.
Prerequisites
The program matching mode of the multicast VLAN must be the static configuration mode.
Context
If the CAC function, not the dynamic Access Node Control Protocol (ANCP) CAC function is
enabled, and a user requests for a multicast program, the system compares the remaining
bandwidth of the user (bandwidth configured for the user total bandwidth of the online
programs of the user) with the bandwidth of the multicast program. The system determines
whether the user can watch the multicast program based on the result:
l
If the remaining bandwidth of the user is sufficient, the system adds the user to the multicast
group.
If the bandwidth is insufficient, the system does not respond to the request of the user. That
is, the request of the user fails.
If the CAC function is not enabled, the system does not guarantee the bandwidth of the multicast
program. In this case, the picture quality of the requested program may be poor. For example,
mosaic and delay occur.
Table 5-7 lists the default settings of the CAC parameters.
Table 5-7 Default settings of the CAC parameters
Issue 02 (2013-10-08)
Parameter
Default Value
Global CAC function
enable
Bandwidth of the multicast

program
5000 kbit/s
Bandwidth of the multicast user
no-limit

275

Configuration Guide
Procedure
Step 2 Enable the CAC function globally.
l Run the igmp bandwidthcac enable function to enable the CAC function globally.
l By default, the CAC function is enabled globally.
Step 3 Configure the bandwidth of the multicast program.
l Run the igmp program add command to configure the bandwidth of the multicast program.
The bandwidth is an attribute of the multicast program and identifies the bandwidth required
for playing the program.
l By default, the bandwidth of the multicast program is 5000 kbit/s.
Step 4 Configure the bandwidth of the multicast user.
l Run the igmp user add service-port index max-bandwidth command to configure the
bandwidth of the multicast user.
l Before configuring the bandwidth of the multicast user, ensure that the service port of the
multicast user exists. You can run the display service-port command to query the service
port.
l By default, the bandwidth of the multicast user is not limited (no-limit).
Step 5 Check whether the multicast bandwidth is configured correctly.
l Run the display igmp config global command to check whether the CAC function is enabled
globally.
l Run the display igmp program command to query the bandwidth of the multicast program.
l Run the display igmp user command to query the bandwidth of the multicast user.
----End
Example
Assume that the CAC function is enabled globally, the bandwidth of multicast user 0/1/0 is 10
Mbit/s, and the bandwidth of the multicast program with IP address 224.1.1.1 is 1 Mbit/s. To
perform the configurations, do as follows:
huawei(config)#btv
huawei(config-btv)#igmp bandwidthcAC enable
huawei(config-btv)#igmp user add service-port 0 max-bandwidth 10240 //0 is the
service port ID of the multicast user.
huawei(config-btv)#multicast-vlan 10
huawei(config-mvlan10)#igmp program add ip 224.1.1.1 bandwidth 1024
Result
Check whether the bandwidths of the multicast user and multicast program are configured
correctly.
l
Check whether the bandwidth of the multicast user is configured correctly.

huawei(config)#display igmp user all
{ <cr>||
<K> }:
Command:
Issue 02 (2013-10-08)

276

Configuration Guide
display igmp user

all
Command is being executed, please
wait...
-----------------------------------------------------------------------------User Index Bind
State
Auth
Quick
IGMP
Video
Log
Available
profiles
leave
flow ID flow ID switch
programs
-----------------------------------------------------------------------------0
offline no-auth MAC-based 0
0
enable
8
-----------------------------------------------------------------------------Total: 1
huawei(config)#display igmp user 0
//0 is the index of the multicast user
queried in the preceding part.
{ <cr>||
<K> }:
Command:
display igmp user
0
User
:
0/1/0
State
:
offline
Authentication
: noauth
Quick leave
: MACbased
IGMP flow ID
:
0
Video flow ID
:
0
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 MaxBandWidth
: 10240
//The bandwidth of the multicast user
is 10 Mbit/s.
:
0
Used
bandwidth
to max bandwidth(%)
:
0.00
:
: -
Check whether the bandwidth of the multicast program is configured correctly.

huawei(config)#display igmp program all
{ <cr>||
<K> }:
Issue 02 (2013-10-08)

277

Configuration Guide
Command:
display igmp program
all
-----------------------------------------------------------------------------Index| Create |
IP
|
Program
|User |VLAN |Prejoin|
Priority
| Flag
|
Address
|
name
|num | ID |
|
-----------------------------------------------------------------------------0
S
224.1.1.1
PROGRAM-0
0
10
disable
7
-----------------------------------------------------------------------------Total: 1 program(s) (Static/Dynamic:
1/0)
huawei(config)#display igmp program index 0
<cr>||
<K> }:
Command:
display igmp program index 0
--------------------------------------------Program index
:
0
Create mode
:
static
Program name
:
PROGRAM-0
IP address
:
224.1.1.1
VLAN ID
:
10
Host attribute
:
enable
Log attribute
:
enable
Prejoin attribute
:
disable
:
disable
Priority
:
7
Host IP
:
0.0.0.0
Bandwidth(kbps)
: 1024
//The bandwidth of the multicast program is
1 Mbit/s.
SourceIP
:
Preview Profile
:
0
Numbers of watching
:
0
Program Grade
:
---------------------------------------------
5.3.5 (Optional) Configuring the Multicast Preview

Multicast preview is an advertising method provided by carriers for ISPs. The purpose is to allow
users to have an overview of a program so that the user can determine whether to request for the
Issue 02 (2013-10-08)

278

Configuration Guide
program. The MA5616 can control the duration, interval, and count of user previews through
the configuration of the multicast preview.
Prerequisites
Context
Multicast preview is an advertising method provided by carriers for ISPs. The purpose is to allow
users to have an overview of a program so that the user can determine whether to request for the
program. To protect the legitimate interests of ISPs, the duration, interval, and count of user
previews need to be controlled. The MA5616 controls the program preview of the user through
the configuration of the multicast preview.
l
Preview duration: After a user with the preview rights goes online, the user can watch the
program that can be previewed but the user is restricted by the preview duration. When the
preview time expires, the user will go offline.
Preview interval: When the preview time expires, the user who is previewing a multicast
program will go offline. The user can request for the program again only after the configured
preview interval expires.
Preview count: Refers to the count of program previews that a user can request for a
multicast program in a period of 24 hours (the start time can be set). If the preview count
reaches the configured preview count, the user cannot preview the program.
The multicast preview function is implemented through the binding of the preview profile to the
multicast program.
NOTE
One multicast program can be bound with only one preview profile, but one preview profile can be
referenced by multiple multicast programs.
The multicast for IPv6 protocols does not support the program preview.
Table 5-8 lists the default settings of the multicast preview parameters.
Table 5-8 Default settings of the multicast preview parameters
Parameter
Default Value
Global multicast preview

function
enable
Preview profile
Preview profile with index 0
Preview profile parameters
Maximum preview duration: 120s

Maximum preview count: 8
Minimum interval between two previews: 120s
Issue 02 (2013-10-08)
Time for resetting the preview

record
4:00:00 am
Valid duration of multicast

preview
30s

279

Configuration Guide
Procedure
Step 2 Enable the multicast preview function globally.
By default, the multicast preview function is enabled globally. You can run the igmp preview
{ enable | disable } command to change the configuration.
Step 3 Configure the preview profile.
Run the igmp preview-profile add command to configure the multicast preview profile.
The system has a default preview profile with index 0, which can only be modified and cannot
be deleted.
Step 4 Bind the multicast program with the preview profile.
In multicast VLAN mode, run the igmp program add ip ip-addr preview-profile index
command to bind the preview profile to the multicast program so that the multicast program has
the preview attributes defined in the preview profile.
By default, the multicast program is bound with the preview profile with index 0.
Step 5 Change the time for clearing the preview record.
Run the igmp preview auto-reset-time command to change the time for clearing the preview
record. The system records only the preview of the multicast user on the current day.
By default, the system clears the preview record at 04:00:00.
Step 6 Modify the valid duration of the multicast preview.
Run the igmp proxy recognition-time command to modify the valid duration of the multicast
preview. If the preview duration of the user is shorter than the valid duration, the preview is not
regarded as a valid one and is not added to the preview count.
By default, the valid duration of the multicast preview is 30s.
----End
Example
Assume that the preview function of the multicast program is enabled, preview profile 1 is
configured, the maximum preview duration is 150s, the maximum preview count is 10, this
preview profile is used when program 224.1.1.1 is added, and other parameters use the default
values. To perform the configurations, do as follows:
huawei(config)#btv
huawei(config-btv)#igmp preview enable
huawei(config-btv)#igmp preview-profile add index 1 duration 150 times 10
huawei(config-mvlan10)#igmp program add ip 224.1.1.1 preview-profile 1
Result
Check whether the preview function of the multicast program is configured correctly.
Issue 02 (2013-10-08)

280

Configuration Guide
Check whether the preview function of the multicast program is enabled.

huawei(config)#display igmp config global
---------------------------------------------------------------------Authorization
:
enable
Robustness variable
:
2
:
125
V2 General query response time(0.1s) :
100
V3 General query response time(0.1s) :
100
:
10
V2 specific query response time(0.1s) :
8
V3 specific query response time(0.1s) :
8
:
2
:
400
:
disable
Preview switch
: enable //The multicast preview
function is enabled.
Recognition time(s)
:
30
:
04:00:00
:
2
Uplink port mode
:
default
:
enable
:
600
:
200
CDR switch
:
disable
:
all
IGMP ECHO switch
:
disable
Router IP
:
192.168.1.1
Initial unsolicited report interval(s):
1
:
BTV Forward Mode
:
Mvlan
: IGMP policy
----------------------------------------------------------------------
Check the configuration of the preview profile of the multicast program.

huawei(config)#display igmp preview-profile index 1
Preview profile Index:
1
Preview duration(s):
150 //The maximum preview duration is 150s.
Preview interval(s):
120
Preview times:
10 //The maximum preview count is 10.
Program reference number:
1
Issue 02 (2013-10-08)

281

Configuration Guide
Query the preview profile bound to the multicast program.

{ <cr>||
<K> }:
Command:
display igmp program
all
-----------------------------------------------------------------------------Index| Create |
IP
|
Program
|User |VLAN |Prejoin|
Priority
| flag
|
address
|
name
|num | ID |
|
-----------------------------------------------------------------------------0
S
224.1.1.1
PROGRAM-0
0
10
disable
7
-----------------------------------------------------------------------------Total: 1 program(s) (Static/Dynamic:
1/0)
The queried program index is 0.
{ <cr>||
<K> }:
Command:
display igmp program index
0
--------------------------------------------Program index
:
0
Create mode
:
static
Program name
:
PROGRAM-0
IP address
:
224.1.1.1
VLAN ID
:
10
Host attribute
:
enable
Log attribute
:
enable
Prejoin attribute
:
disable
:
disable
Priority
:
7
Host IP
:
0.0.0.0
Bandwidth(kbps)
:
5000
SourceIP
:
Preview Profile
: 1
//The index of the preview profile bound to the
multicast program is 1.
Numbers of watching
:
0
Program Grade
:
---------------------------------------------
Issue 02 (2013-10-08)

282

Configuration Guide
5.3.6 (Optional) Configuring the Program Prejoin

A delay occurs when a user switches programs and the switching is processed by devices on the
network. In program prejoin, the MA5616 receives the multicast stream of a program from the
upper-layer multicast router to the uplink port before a user sends a request to join a program.
In this manner, the multicast stream can be directly transmitted from the uplink port to the user
port after the multicast user requests for a program, shortening the waiting time of the user for
requesting for the program and shortening the delay in program switching. Therefore, user
experience is enhanced.
Prerequisites
Context
Multicast program prejoin is the same as program request. The MA5616 plays the role of a user
and sends the report packet for receiving in advance the multicast stream from the upper-layer
multicast router to the uplink port.
After the prejoin function is enabled, if the upper-layer multicast router does not support static
multicast entry forwarding, you need to enable the unsolicited report function of IGMP packets
so that the user can request for the program quickly. Generally, the upper-layer multicast router
processes the user request by responding to the group-specific query and the general query.
NOTE
The configuration steps for IPv4 multicast and IPv6 multicast are similar while the detailed commands are
different. This topic describes the configuration steps for IPv4 multicast, and provides the configuration
example for IPv6 multicast.
Table 5-9 lists the default settings of the prejoin parameters.

Table 5-9 Default settings of the prejoin parameters
Parameter
Default Value
Prejoin function
disable
Unsolicited report of IGMP packets
disable
Procedure
Step 1 Enable the program prejoin function.
Run the igmp program add ip ip-addr prejoin enable command to enable the program prejoin
function.
By default, this function is disabled.
Step 2 After the program prejoin function is enabled, if the upper-layer multicast router does not support
static multicast entry forwarding, you need to enable the unsolicited report function of IGMP
packets.
Issue 02 (2013-10-08)

283

Configuration Guide
l Run the igmp program add ip ip-addr unsolicited enable command to enable the
unsolicited report function of IGMP packets. By default, this function is disabled.
l Run the igmp unsolicited-report interval command to change the interval of the unsolicited
report of IGMP packets. By default, the time is 10s.
Step 3 Check whether the prejoin function is configured correctly.
l Run the display igmp program command to query the status of the program prejoin function
and unsolicited report function.
l Run the display igmp config vlan command to query the interval of the unsolicited report
of IGMP packets.
----End
Example
To enable the program prejoin function when adding a program whose IP address is 224.1.1.1,
do as follows:
huawei(config-mvlan10)#igmp program add ip 224.1.1.1 prejoin enable
To enable the program prejoin function when adding a program whose IP address is ffff::1, do
as follows:
huawei(config-mvlan101)#igmp program add ipv6 ffff::1 prejoin enable
Result
Query the status of the program prejoin function for IPv4 multicast.
{ <cr>||<K> }:
Command:
display igmp program all
-----------------------------------------------------------------------------Index| Create |
IP
|
Program
|User |VLAN |Prejoin|Priority
| flag
|
address
|
name
|num | ID |
|
-----------------------------------------------------------------------------0
S
224.1.1.1
PROGRAM-0
0
10
enable
7
-----------------------------------------------------------------------------Total: 1 program(s) (Static/Dynamic: 1/0)
//The queried program index is 0.
huawei(config-mvlan10)#display igmp program index 0
{ <cr>||<K> }:
Command:
--------------------------------------------Program index
: 0
Create mode
: static
Program name
: PROGRAM-0
IP address
: 224.1.1.1
VLAN ID
: 10
Host attribute
: enable
Log attribute
: enable
Prejoin attribute
: enable
//The program prejoin function is enabled.
: disable
Issue 02 (2013-10-08)

284

Configuration Guide
Priority
: 7
Host IP
: 0.0.0.0
Bandwidth(kbps)
: 5000
SourceIP
: Preview Profile
: 0
Numbers of watching
: 0
Program Grade
: ---------------------------------------------
Query the status of the program prejoin function for IPv6 multicast.
{ <cr>||<K> }:
Command:
display igmp program all
-----------------------------------------------------------------------------Index| Create |
IP
|
Program
|User |VLAN |Prejoin|Priority
| flag
|
address
|
name
|num | ID |
|
-----------------------------------------------------------------------------0
S
FFFF::1
PROGRAM-0
0
101
enable
7
-----------------------------------------------------------------------------Total: 1 program(s) (Static/Dynamic: 1/0)
//The queried program index is 0.
{ <cr>||<K> }:
Command:
--------------------------------------------Program index
: 0
Create mode
: static
Program name
: PROGRAM-0
IP address
: FFFF::1
VLAN ID
: 101
Host attribute
: enable
Log attribute
: enable
Prejoin attribute
: enable
//The program prejoin function is enabled.
: disable
Priority
: 7
Host IP
: Bandwidth(kbps)
: 5000
Source IP
: Preview profile
: 0
Numbers of watching
: 0
Program grade
: ---------------------------------------------
5.3.7 (Optional) Configuring the Multicast Log

This topic describes how to configure the multicast log. Multicast log records the information
about multicast programs watched by the multicast user, which provides a criterion for carriers
to evaluate the viewership of multicast programs. The MA5616 can report the multicast log to
the multicast server.
Prerequisites
The communication between the MA5616 and the multicast log server must be normal.
Issue 02 (2013-10-08)

285

Configuration Guide
Context
The multicast log involves the multicast log of the multicast VLAN, multicast user, and multicast
program. The system generates logs only when the log functions of all the multicast VLAN,
multicast user, and multicast program are enabled.
If the online duration of the user is longer than the valid log generation time, the system generates
logs in any of the following conditions:
l
The user goes offline naturally, forcibly, or abnormally.
The user is blocked or deleted.
The program is deleted.
The priority of the program is changed.
The uplink port to which the program is bound is changed.
The VLAN of the uplink port to which the program is bound is changed.
The user preview times out.
The preview time is longer than the recognition time of the multicast preview, and the
preview is valid.
NOTE
Recognition time of the multicast preview: When a user previews a program, the recognition time is used
to determine whether the preview is valid. If the preview time of a multicast user is shorter than the
recognition time, the preview is invalid and is not added to the preview count. In addition, no multicast
log is generated. When a user watches a program, the recognition time is used to determine whether to
generate a multicast log. If the watch time of a multicast user is shorter than the recognition time, no
multicast log is generated.
The rights mode is switched.
The IGMP mode is switched.
The multicast CAC fails. For the principles of multicast CAC, see Multicast CAC in Service
Provisioning of Feature Description.
When a user goes online, the system records only the online date and time. The system generates
a complete log only when the user goes offline.
The MA5616 can report the multicast log to the log server in syslog mode or in call detailed
record (CDR) mode. By default, the MA5616 reports the log in syslog mode.
l
syslog mode: Logs are reported to the syslog server in the form of a single log.
CDR mode: Logs are reported to the log server in the form of a log file (.cvs). One log file
contains multiple logs.
Table 5-10 lists the default settings of the multicast logging parameters.
Table 5-10 Default settings of the multicast logging parameters
Issue 02 (2013-10-08)
Parameter
Default Value
Report mode of the multicast log
Syslog mode
Logging function at the multicast

VLAN level
enable

286

Configuration Guide
Parameter
Default Value

user level
enable

program level
enable
Action report function of the

multicast user
disable
Interval for automatically

logging
2 hours
Minimum online duration for

generating a valid log
30s
Parameters of the log report in the

CDR mode
Report interval: 600s

Maximum number of logs that can be reported each time:
200
Procedure
l
Configure the parameters of the multicast log generation function of the MA5616.
1.
Enable the multicast log generation function.

The multicast log involves the multicast log of the multicast VLAN, multicast user,
and multicast program. The system generates logs only when the log functions of all
the multicast VLAN, multicast user, and multicast program are enabled. By default,
the log functions of all the multicast VLAN, multicast user, and multicast program
are enabled.
In multicast VLAN mode, run the igmp log { enable | disable } command to
configure the status of the log function of the multicast VLAN.
In BTV mode, run the igmp user add service-portindexlog { enable | disable }
command to configure the status of the log function of the multicast user.
In multicast VLAN mode, run the igmp program add ipip-addrlog { enable |
disable } command to configure the status of the log function of the multicast
program.
2.
Change the interval of automatic log generation.

In BTV mode, run the igmp proxy log-interval command to change the interval of
automatic log generation.
NOTE
When the user stays online for a long time, the system generates logs at preset intervals. This prevents
the problem that a log is not generated when the user leaves the multicast group without sending the
leave packet, which can affect the accounting. By default, the interval is two hours.
3.
Change the minimum online duration for generating a valid log.

In BTV mode, run the igmp proxy recognition-time command to change the
minimum online duration for generating a valid log. If the user is in a multicast group
(such as to preview a program) for shorter than the preset duration, the user operation
Issue 02 (2013-10-08)

287

Configuration Guide
is not regarded as a valid one and a log is not generated. A log is generated only when
a user stays online for longer than the specified duration. By default, the duration is
30s.
l
(Optional) Configure the action report function of a multicast user.

By default, the system uses syslog mode to report multicast logs and you do not need to
configure the function. Run the igmp user-action-report command to configure the action
report function of a multicast user. By default, the function is disabled.
enable: enables the action report function of a multicast user. When the function is
enabled, the system reports syslog when the user goes online or offline.
disable: disables the action report function of a multicast user. When the function is
disabled, the system reports syslog only when the user goes offline.
Configure the multicast log report function in CDR mode.

NOTE
By default, the system uses syslog mode to report multicast logs. If this default mode is used, skip this
step. To configure the multicast log report function in CDR mode, perform the preceding step and this
step.
1.
Configure the multicast log server and the data transmission mode for the multicast
log report in CDR mode.
Run the file-server auto-backup cdr command to configure the active and standby
multicast log servers.
2.
Enable the multicast log report function in CDR mode.

In BTV mode, run the igmp cdr { enable | disable } command to configure the status
of the multicast log report function in CDR mode.
After the multicast log report function in CDR mode is enabled, the MA5616
reports local multicast logs to the multicast log server in the form of a file.
After the multicast log report function in CDR mode is disabled, the MA5616
reports each single log to the syslog server in the default syslog mode.
3.
Configure the parameters of the multicast log report in CDR mode.

In BTV mode, run the igmp cdr-interval command to configure the interval of
the multicast log report in CDR mode. By default, the interval is 600s.
In BTV mode, run the igmp cdr-number command to configure the maximum
number of logs that can be reported in CDR mode each time. When the number of
multicast logs in the CDR file reaches the preset value, the MA5616 reports the
logs. By default, the maximum number is 200.
4.
Check whether the configuration is correct.

Run the display file-server command to query the configuration of the multicast
log server for receiving the multicast log reported in CDR mode.
Run the display igmp config global command to query the status and other
parameters of the multicast log report in CDR mode.
----End
Example
To configure the multicast log to be reported to log server 10.10.10.10 (active multicast log
server) in CDR mode through SFTP transmission, do as follows:
Issue 02 (2013-10-08)

288

Configuration Guide
huawei(config)#file-server auto-backup cdr primary 10.10.10.10 sftp path temp user

User Name(<=40 chars):aaa
User Password(<=40 chars):
//Input the password.
huawei(config)#btv
huawei(config-btv)#igmp cdr enable
Result
Query the configuration of the multicast log server for receiving the multicast log reported in
CDR mode.
huawei(config)#display file-server auto-backup cdr
-----------------------------------------------------------------------------Server type: Primary
Trans mode : TFTP
//The transmission mode of the multicast log is
SFTP.
IP address : 10.10.10.10
//The IP address of the multicast log server is
10.10.10.10.
User name : aaa
Path
: temp
Port
: 22
-----------------------------------------------------------------------------Current Server: Primary server
Query the status and other parameters of the multicast log report in CDR mode.
huawei(config)#display igmp config global
---------------------------------------------------------------------Authorization
: enable
Robustness variable
: 2
: 125
: 10
: 2
: 400
: disable
Preview switch
: enable
Recognition time(s)
: 30
: 04:00:00
: 2
Uplink port mode
: default
: enable
: 600
: 200
CDR switch
: enable //The multicast log report in CDR
mode is enabled.
: all
IGMP ECHO switch
: disable
Router IP
: 192.168.1.1
: disable
BTV Forward Mode
: MVLAN
: IGMP policy
---------------------------------------------------------------------huawei(config)#display igmp config global
---------------------------------------------------------------------Authorization
: enable
Robustness variable
: 2
: 125
: 10
: 2
Issue 02 (2013-10-08)

289

Configuration Guide

: 400
: disable
Preview switch
: enable
Recognition time(s)
: 30
: 04:00:00
: 2
: enable
: 600
: 200
CDR switch
: enable //The multicast log report in CDR
mode is enabled.
: all
IGMP ECHO switch
: disable
Router IP
: 192.168.1.1
: disable
BTV Forward Mode
: MVLAN
: IGMP policy
----------------------------------------------------------------------
5.4 Configuring the Multicast Service on a Subtending

Network
This topic describes how to configure the multicast service on the MA5616 on a subtending
network.
Prerequisites
l
The multicast source must exist on the network and the IP address of the multicast source
must be known.
Context
When a subtended device needs to provide the multicast service, the subtending port on the
subtending device needs to be configured as the multicast subtending port. In this manner, the
subtended device regards the subtending device as an IGMP user.
Networking
Figure 5-1 shows the example network of the multicast service in subtending networking mode.
Issue 02 (2013-10-08)

290

Configuration Guide
Figure 5-1 Example network of the multicast service in subtending networking mode
Multicast source
ISP2
ISP1
Router
OLT
ONU_A
ONU_B
STB
TV
user1
user2
Data Plan
Table 5-11 provides the data plan for configuring the multicast service in subtending networking
mode.
Table 5-11 Data plan for configuring the multicast service in subtending networking mode
Device
Item
Data
MA5616_A
Smart VLAN
l VLAN type: Smart VLAN

l VLAN ID: 4002-4003
Issue 02 (2013-10-08)
Uplink port
0/0/1
Subtending
port
0/0/0
IGMP version
IGMP V3 (default multicast version of the system in

multicast VLAN mode)

291

Configuration Guide
Device
Item
Data
Multicast
source
There are two multicast sources, namely, ISP 1 and ISP 2.

l ISP 1: with IP address 10.10.10.10, providing the
multicast program with IP address 224.1.1.1
Program
library
Program in multicast VLAN 4002:

Program 1: with IP address 224.1.1.1 and the IP address
of the program source is the same as the IP address of ISP
1, namely, 10.10.10.10
2, namely, 10.10.10.11
MA5616_B
Smart VLAN

l VLAN ID: 4002-4005
Uplink port
0/0/0
IGMP version

Multicast
source

Program
library

1, namely, 10.10.10.10
2, namely, 10.10.10.11
Multicast user
Multicast user 1:
l VDSL2 port: 0/1/0
l Multicast VLAN: 4002
Multicast user 2:
l VDSL2 port: 0/1/1
Issue 02 (2013-10-08)

292

Configuration Guide
Procedure
l
Configure the multicast service on MA5616_A.

1.
Create VLANs.
huawei(config)#vlan 4002-4003 smart
2.
Add the uplink port and the subtending port to the VLANs.
huawei(config)#port vlan 4002-4003 0/0 1
3.
Configure multicast VLANs and the IGMP mode.

NOTE
The IGMP mode can be configured to IGMP proxy or IGMP snooping according to the
requirements. In this example, the IGMP mode is IGMP proxy. If the planned IGMP mode is
IGMP snooping, you can configure the IGMP snooping mode by running the igmp mode
snooping command in multicast VLAN mode.
If configuring the IGMP mode fails, check whether the IGMP function is disabled. That is, the
IGMP mode can be switched only when the IGMP function is disabled.
huawei(config-mvlan4002)#multicast-vlan 4003
4.
Configure the multicast uplink port.

5.
Configure multicast programs.

NOTE
l A multicast program can be configured statically or generated dynamically. In this example,

the multicast program is configured statically.
l In static configuration mode, you can run the igmp program add command to add
multicast programs in batches.
huawei(config-mvlan4002)#igmp program add name program1 ip 224.1.1.1
sourceip 10.10.10.10
6.
Configure the multicast subtending port.

huawei(config-mvlan4003)#btv
huawei(config-btv)#igmp cascade-port 0/0/0
7.
Save the data.

huawei(config)#save
Configure the multicast service on MA5616_B.

1.
Create VLANs and add an uplink port to the VLANs.

2.
Configure service ports.

huawei(config)#service-port 100 vlan
service user-vlan untagged rx-cttr 6
huawei(config)#service-port 101 vlan
service user-vlan untagged rx-cttr 6
Issue 02 (2013-10-08)
4004 vdsl mode ptm 0/1/0 multitx-cttr 6

4005 vdsl mode ptm 0/1/1 multitx-cttr 6

293

Configuration Guide
3.
Configure multicast VLANs and the IGMP mode.

NOTE
The IGMP mode can be configured to IGMP proxy or IGMP snooping according to the
requirements. In this example, the IGMP mode is IGMP proxy. If the planned IGMP mode is
IGMP snooping, you can configure the IGMP snooping mode by running the igmp mode
snooping command in multicast VLAN mode.
4.

5.
Configure multicast programs.

NOTE
l A multicast program can be configured statically or generated dynamically. In this example, the
multicast program is configured statically.
l In static configuration mode, you can run the igmp program add command to add multicast
programs in batches. You cannot name a program, instead the system automatically names a
program PROGRAM-M, in which M is the index of the added program.
6.
Configure multicast users.

huawei(config-btv)#igmp user add service-port 100
7.
Save the data.

huawei(config)#save
----End
Result
l
User 1 belongs to multicast VLAN 4002 and user 1 can watch the program with IP address
224.1.1.1 provided by ISP1.
Configuration File
The following part describes the configuration file of this configuration example. Note that
certain steps need to be performed manually and the configuration file cannot be imported
directly.
MA5616_A
Issue 02 (2013-10-08)

294

Configuration Guide
Create VLANs and add the uplink port and the subtending port to the VLANs. This step needs
to be performed manually.
vlan 4002 to 4003 smart
port vlan 4002 to 4003 0/0 1
port vlan 4002-4003 0/0 0
Configure multicast VLANs and the IGMP mode. This step needs to be performed manually.
multicast-vlan 4002
igmp mode proxy
multicast-vlan 4003
igmp mode proxy
Configure the multicast uplink port, multicast programs, and multicast subtending port.
igmp uplink-port 0/0/1
multicast-vlan 4002
igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10
multicast-vlan 4003
btv
igmp cascade-port 0/0/0
quit
save
MA5616_B
Create VLANs and add an uplink port to the VLANs. This step needs to be performed manually.
port vlan 4002 to 4005 0/0 0
Create service ports.

service-port 100 vlan 4004 vdsl mode ptm 0/1/0 multi-service user-vlan untagged rxcttr 6 tx-cttr 6
multicast-vlan 4002
igmp mode proxy
multicast-vlan 4003
igmp mode proxy
Configure the multicast uplink port, multicast programs, and multicast users.
multicast-vlan 4002
multicast-vlan 4003
btv
igmp user add service-port 100
multicast-vlan 4002
igmp multicast-vlan member service-port 100
multicast-vlan 4003
quit
save
Issue 02 (2013-10-08)

295

Configuration Guide
6 Configuring the Voice Service
Configuring the Voice Service
About This Chapter

The MA5616 supports user access through copper cables to provide the voice service.
Context
The MA5616 can provide the voice service through the H.248 or Session Initiation Protocol
(SIP) protocol.
l
The system communicates with the media gateway controller (MGC) through the H.248
protocol, and provides the voice service under the control of the MGC.
The system communicates with the IP multimedia subsystem (IMS) core network device
through the SIP protocol to provide the voice service.
The voice pre-configuraiton profile of the MA5616 supports the configuration of main voice
parameters through a single command.
l
Run the voice-para-template select command to select the parameter profile for an area
to quickly configure the voice service. Run the display voice-para-templatename (when
the SIP protocol is used) or display voice-para-template name (when the H.248 protocol
is used) command to query the parameter configurations for different areas.
When the parameter configurations defined in the system do not meet the requirements,
run the userdef-template-port-para command or the userdef-template-user-para
command to modify the parameter configurations in the user defined parameter profile.
Run the userdef-template-port-para command to modify user-defined parameters for
a port.
Run the userdef-template-user-para command to modify user-defined parameters for
a user.
If you do not use the voice configuration profile, configure the voice parameters one by
one by following the configuration steps in the next topics.
NOTE
In this document, the MG, AG, gateway, or SIP AG refers to the MA5616, unless otherwise stated.
6.1 Configuring the VoIP PSTN Service (Based on the H.248 Protocol)
Issue 02 (2013-10-08)

296

Configuration Guide
This topic describes how to configure the voice over IP (VoIP) public switched telephone
network (PSTN) service on the MA5616 when the H.248 protocol is used. VoIP transmits voice
services using the IP technology on the network without deteriorating service quality, providing
more valued-added functions for customers and reducing costs.
6.2 Configuring the VoIP PSTN Service (Based on the SIP Protocol)
The SIP-based VoIP technology makes the transport network evolve to the IP network without
decreasing the voice quality, provides more value-added functions for users, and saves expense.
6.3 Configuring the VoIP ISDN BRA Service (Based on the H.248 Protocol)
This topic describes how to configure the VoIP ISDN BRA service on an IP network. When the
MA5616 uses the H.248 protocol, the device supports the access of the ISDN BRA user. ISDN
technology provides end-to-end (E2E) digital connection and supports multiple types of voice
and non-voice telecom services.
6.4 Configuring the VoIP ISDN BRA Service (Based on the SIP Protocol)
After configuring the SIP interface, you can add VoIP ISDN BRA users on this interface to
implement the VoIP ISDN BRA service.
6.5 Configuring the FoIP Service (Based on the H.248 Protocol)
The fax service is still widely used in business life. This topic describes how to configure the
FoIP service when the H.248 protocol is used to transmit the fax data service over the IP network.
6.6 Configuring the FoIP Service (Based on the SIP Protocol)
FoIP service based on the SIP protocol to transmit the fax data service over the IP network.
6.7 Configuring the MoIP Service (Based on the H.248 Protocol)
Modem can provide access for services like point of sells (POS). This topic describes how to
configure the MoIP service when the H.248 protocol is used to transmit the modem data service
over the IP network.
6.8 Configuring the MoIP Service (Based on the SIP Protocol)
6.9 Configuring the Security and Reliability of the Voice Service
For the MA5616, the security configuration of the voice service includes the H.248-based, or
SIP-based device authentication configuration. The reliability configuration of the voice service
includes the dual-homing configuration and the emergency standalone configuration.
Issue 02 (2013-10-08)

297

Configuration Guide
6.1 Configuring the VoIP PSTN Service (Based on the H.248

Protocol)
This topic describes how to configure the voice over IP (VoIP) public switched telephone
network (PSTN) service on the MA5616 when the H.248 protocol is used. VoIP transmits voice
services using the IP technology on the network without deteriorating service quality, providing
more valued-added functions for customers and reducing costs.
Applicable Environment
Compared with a traditional circuit switching-based PSTN, an IP network is based on packet
switching at the transport layer, providing a higher bandwidth and bandwidth usage. A network
phone on an IP network transmits more messages than that on a circuit switching-based network
and can share a line with other services, reducing costs and improving line usage.
Context
The VoIP service uses the IP packet switching network for transmission after the traditional
analog voice signals are compressed and packetized, to reduce the cost of the voice service.
For details about the VoIP service based on the H.248 protocol, see VoIP (H.248) in the Feature
Description.
In the NGN network, the MA5616 functions as an access gateway (AG) and exchanges signaling
with the media gateway controller (MGC) through the media gateway control protocol (the H.
248 protocol). In this manner, the VoIP, FoIP, and MoIP services are implemented under the
control of the MGC.
H.248, also called MeGaCo, is a protocol developed based on the MGCP protocol by combining
the features of other media gateway control protocols.
Prerequisite
According to the actual network, a route from the MA5616 to the MGC must be configured
using the command ip route-static to ensure that the MA5616 and the MGC are reachable to
each other.
Precaution
The media gateway control protocols are master/slave protocols, and the MGC controls the AG
to implement the call connection. Therefore, the data on the AG for interconnection with the
MGC, including the attributes of the MG interface and the attributes of the VoIP user, must be
consistent with the corresponding data on the MGC. Before configuring the VoIP service, you
must make the data plan by considering interconnection with the MGC.
Data preparation
Table 6-1 provides the data plan for configuring the VoIP PSTN service.
Issue 02 (2013-10-08)

298

Configuration Guide
Table 6-1 Data plan for configuring the VoIP PSTN service based on the H.248 protocol
Item
Remarks
MG interface
data
(The data
configuration
must be
consistent with
the data
configuration
on the MGC.)
Parameter
s of the
media
stream and
signaling
stream
Attribute
parameter
s of the
MG
interface
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
MG
interface
fails to be
started if
these
parameter
s are not
configure
d.
Issue 02 (2013-10-08)
Media and
signaling
upstream VLAN
It is used as the upstream VLAN of the

VoIP service to be configured. Standard
VLAN is recommended.
Media and
signaling
upstream port
It is used as the upstream port of the

VoIP service to be configured.
Media IP address
and signaling IP
address
These IP addresses must be selected

from the media and signaling IP address
pools. The media and signaling IP
address pools consist of all the IP
addresses of the L3 interface of the
media and signaling upstream VLAN.
Default IP address
of the MG
It is the IP address of the next hop from

the MA5616 to the MGC.
MG interface ID
It is the MG interface ID used for the

VoIP service to be configured. The
MA5616 supports four virtual access
gateways (VAGs).
Signaling port ID
of the MG
interface
It is the transport layer protocol port ID

used for the signaling exchange
between the MA5616 (AG) and the
MGC.
Default signaling port ID specified in
the H.248 protocol: 2944 (text) and
2945 (binary)
IP address of the
primary MGC to
which the MG
interface belongs
Port ID of the
primary MGC to
which the MG
interface belongs
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
also need to be configured.
Coding mode of
the MG interface
Currently, only the text coding mode is

supported.
Transmission
mode of the MG
interface
The transmission mode is selected

according to the requirements on the
MGC side. Generally, UDP is adopted.

299

Configuration Guide
Item
Remarks
Domain name of
the MG interface
It corresponds to parameter
domainName of the MG interface.
When the H.248 protocol is used, this
parameter must be configured if
parameter MIDType of the H.248
message is configured as the domain
name. Otherwise, the MG interface fails
to be started. In other situations, this
parameter is optional.
Device name of
the MG interface
It is supported only by the H.248

protocol, and corresponds to parameter
deviceName of the MG interface that
uses the H.248 protocol.
When the H.248 protocol is used, this
parameter must be configured if
parameter MIDType of the H.248
message is configured as the domain
name. Otherwise, the MG interface fails
to be started. In other situations, this
parameter is optional.
Start negotiation
version of the H.
248 protocol for
the MG interface
It is recommended that you configure

this parameter to 0, which indicates the
negotiation is performed according to
the profile.
If an MG interconnects with a Huawei
MGC, set the profile ID to 1 or do not
set it. The default value is 1. If an MG
interconnects with a third party MGC,
the profile of the MGC must be set.
Issue 02 (2013-10-08)
Digitmap of an MG Interface
The digitmaps here are used for certain

special applications such as emergency
calls and emergency standalone. The
digitmaps for common phone services
are sent to the AG by the MGC, and
therefore such digitmaps need not be
configured on the AG. If the services
such as emergency calls and emergency
standalone are not required, the
digitmaps need not be configured.
Software Parameters of an
MG Interface
According to the service requirements,

the configuration of software
parameters determines whether the MG
interface supports the functions such as
dual homing and emergency
standalone.

300

Configuration Guide
Item
Remarks
Voice service
data
(The data
configuration
must be
consistent with
the data
configuration
on the MGC.)
Ringing Mode of an MG
Interface

the ringing modes of the MG interface
need to be determined.
TID Format of an MG
Interface
The TID format determines the

generation mode of various types of
user terminals on an MG interface.
Slot that houses the voice

service board
Specify the slot ID based on site

requirements.
User Data
Phone number
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.
TID
If the TID template with which the

PSTN user is bound does not support
terminal layering, this parameter needs
to be configured.
User priority

the user priority needs to be specified.
The user priorities are as follows:
l cat1: government1 (category 1
government users)
government users)
l cat3: normal (common users,
default priority in the system)
Priorities cat1, cat2, and cat3 are in an
descending order.
Issue 02 (2013-10-08)

301

Configuration Guide
Item
Remarks
User type

the user type needs to be specified. The
user types are as follows:
l DEL: direct exchange lines (default
type in the system)
l ECPBX: earth calling PBX
l LCPBX: loop calling PBX
l PayPhone: pay phone
DEL users are directly connecting to
device ports through user lines; PBX
users are connecting to device ports
through PBX; payphone users are
connecting to device ports through
accounting terminals.
System Parameters
The system parameters including the

overseas version flag and message
waiting indication (MWI) mode need to
be configured according to the local
standards to ensure that the response of
the user terminal complies with the
local standards.
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.
Local Digitmap
Configure a proper local digitmap

according to the local standards. If the
MGC does not send the detailed
digitmap to the MA5616, the MA5616
uses the local digitmap to match the
phone number.
CAUTION
If the H.248 protocol is used, the local
digitmap need not be configured by default.
You can configure the local digitmap
according to the requirements.
Attributes of a PSTN Port
Issue 02 (2013-10-08)
If the PSTN port needs to support the

polarity reversal charging, the PSTN
port needs to be configured to support
the polarity reversal pulse. Other
attributes need not be modified if there
is no special requirement.

302

Configuration Guide
Item
Remarks
Attributes of the Ringing
Current
You can adjust the ringing tone volume

by modifying the attributes of the
ringing current. Generally, the
attributes of the ringing current need not
be modified. You need to modify the
parameters of the ringing current
attributes according to the local
standards only when the default ringing
current attributes do not meet the local
standards.
6.1.1 Configuring an MG Interface

A media gateway (MG) interface is important to H.248-based voice over IP (VoIP) services, as
it enables communication between the MA5616 access gateway (AG) and the media gateway
controller (MGC). Therefore, configure an MG interface and ensure that it is working properly
before implementing H.248-based VoIP services. This topic describes how to configure an MG
interface.
Context
l
A virtual access gateway (VAG) simulates one physical AG into multiple logic AGs.
Multiple logic AGs can be connected to various user groups, providing different
convergence rates for these groups to meet differentiated service requirements. To
configure a VAG, configure a VAG interface (or an MG interface), enter VAG interface
mode, and set interface parameters using the command line interface (CLI).
Each MG interface supports independent signaling and media IP addresses, and signaling
and media IP addresses can be configured in different virtual local area networks (VLANs).
The MA5616 communicates with the MGC using the MG control protocol, or the H.248
protocol.
One MA5616 supports a maximum of four MG interfaces. The MG interfaces support

authentication and ring mapping settings.
Configuring the Upstream VLAN Interface

This topic describes how to specify the upstream VLAN interface for the media stream and
signaling stream, and how to configure the IP addresses of the L3 interface. These IP addresses
are the sources of the media and signaling IP address pools.
Context
Multiple IP addresses can be configured for the same VLAN L3 interface. Only one IP address
functions as the primary address, and other IP addresses function as the secondary addresses.
Issue 02 (2013-10-08)

303

Configuration Guide
Procedure
Step 1 Add an upstream VLAN.
Run the vlan command to add an upstream VLAN for the media stream and signaling stream.
Step 2 Add an upstream port to the VLAN.
Step 3 Configure the IP addresses of the VLAN L3 interface.
1.
Run the interface vlanif command to enter the L3 interface of the upstream VLAN for the
media stream and signaling stream.
2.
Run the ip address command to configure the IP addresses of the L3 interface.
Step 4 Check whether the IP addresses of the L3 interface are the same as those in the data plan.
Run the display interface vlanif command to check whether the IP addresses of the L3 interface
are the same as those in the data plan.
----End
Example
Assume that the media stream and signaling stream are transmitted upstream through upstream
port 0/0/1. To create media and signaling upstream VLAN 3 and configure IP addresses
10.13.4.116/16 and 10.13.4.117/16 of the L3 interfaces respectively, do as follows:
huawei(config-if-vlanif3)#ip address 10.13.4.117 16 sub
huawei(config)#display interface vlanif 3
vlanif3 current state : UP
Line protocol current state : UP
Description : HUAWEI, SmartAX Series, vlanif3 Interface
The Maximum Transmit Unit is 1500 bytes
Internet Address is 10.13.4.116/16
Internet Address is 10.13.4.117/16 Sub
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc32-1118
Configuring the Media and Signaling IP Address Pools

The media IP address pool defines all media IP addresses that can be used by an access gateway
(AG), and the signaling IP address pool defines all signaling IP addresses that can be used by
an AG. The media IP address pool saves the IP addresses of the signaling-controlled media
streams, and the signaling IP address pool saves the IP addresses of the media gateway (MG)
and Session Initiation Protocol (SIP) interfaces.
Prerequisites
The IP address of the L3 interface of the media and signaling upstream VLAN must be
configured. For details about how to configure the IP address, see Configuring the Upstream
VLAN Interface.
Issue 02 (2013-10-08)

304

Configuration Guide
Context
l
The media IP address and the signaling IP address for the MG or SIP interface must be
selected from the IP address pools configured here.
The media IP address pool and the signaling IP address pool can be the same. Similarly,
the media IP address and the signaling IP address can be the same.
The H.248 and SIP protocols support signaling and media stream separation. Specifically,
the signaling and media streams can use different IP addresses and VLANs and are
transmitted to different networks. The separation enables carriers to uses different control
policies, such as QoS and network monitoring, on signaling and media streams.
Procedure
Step 1 Run the voip command to enter the VoIP mode.
Step 2 Configure the media IP address pool.
1.
Run the ip address media command to add the media IP address to the media IP address
pool.
The media IP address needs to be selected from the IP addresses of the L3 interface of the
2.
Run the display ip address media command to check whether the media IP address pool
is the same as that in the data plan.
Step 3 Configure the signaling IP address pool.

1.
Run the ip address signaling command to add the signaling IP address to the signaling IP
address pool.
The signaling IP address needs to be selected from the IP addresses of the L3 interface of
the media and signaling upstream VLAN.
2.
Run the display ip address signaling command to check whether the signaling IP address
pool is the same as that in the data plan.
----End
Example
Assume that the IP address of the gateway is 10.13.1.1. To add IP addresses 10.13.4.116 and
10.13.4.117 of L3 interfaces of the media and signaling upstream VLAN to the media IP address
pool and the signaling IP address pool respectively, do as follows:
huawei(config)#voip
huawei(config-voip)#ip address media 10.13.4.116 10.13.1.1
huawei(config-voip)#ip address signaling 10.13.4.116
huawei(config-voip)#display ip address media
Media:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
MAC Address..........: 00-E0-FC-AF-91-33
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
Issue 02 (2013-10-08)

305

Configuration Guide

huawei(config-voip)#display ip address signaling
Signaling:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Adding an MG Interface
This topic describes how to add a media gateway (MG) interface and configure its attributes.
An MG interface enables communication between an MA5616 and a media gateway controller
(MGC).
Prerequisites
The media and signaling IP address pools have been configured. For details about how to
configure the address pools, see Configuring the Upstream VLAN Interface.
Context
Each MA5616 supports a maximum of four MG interfaces.
Procedure
Step 1 Add an MG interface.
Run the interface h248 command to add an MG interface that supports the H.248 protocol.
Step 2 Configure the MG interface attributes.
Run the if-h248 attribute command to configure MG interface attributes according to the data
plan.
MG interface attributes include three types of parameters: MG interface identifier parameters,
identifier parameters of the MGC to which the MG interface belongs, and H.248 message
negotiation parameters. The detailed description of the parameters is as follows:
l MG interface identifier parameters include domainName, deviceName, and mgip. mgip
includes the signaling and media IP addresses. You can reset an MG interface only after
setting mgip.
l Identifier parameters of the MGC to which the MG interface belongs include mgc-ip and
mgc-domain-name. You can reset an MG interface only after setting either of the two
parameters. When multi-homing is used, set the parameters for the active and standby MGCs,
as well as the disaster tolerance MGC identifier.
l H.248 message negotiation parameters include the message coding mode, message
transmission mode, protocol port ID at the transport layer, protocol negotiation version,
profile negotiation parameter, heartbeat negotiation parameter, and transaction reliability
function. You can reset an MG interface only after setting mgport, primary-mgc-port,
code, transfer, and start-negotiate-version.
Table 6-2 lists the MG interface parameters for communication between the MG and the MGC.
Issue 02 (2013-10-08)

306

Configuration Guide
Table 6-2 MG interface parameters

Parameter
Remarks
mgip
It can be statically configured or dynamically

obtained from the server.
signal-dhcp-vlan vlanid-signal: indicates
that the signaling IP address of a port is
obtained using the upstream VLAN ID of the
MG interface in Dynamic Host Configuration
Protocol (DHCP) mode. You can run the
dhcp-client enable command to configure
the IP address of the VLAN interface to be
dynamically obtained. The IP address is
allocated by the DHCP proxy.
NOTE
l When IP addresses are dynamically obtained,
each VLAN ID can only be used to obtain one
IP address. When IP addresses are obtained
statically, each VLAN ID can be used to obtain
a maximum of eight IP addresses.
l In signal-dhcp-vlan mode, you can configure
a static IP address. If you have configured a
static IP address, the static IP address is used
as the message identification (MID) header
when MIDType is IP.
mgport
Indicates the transport layer protocol port ID

used for the signaling exchange between the
MA5616 (AG) and the MGC.
In the H.248 protocol, the protocol port ID is
related to the coding type. The default
signaling port ID defined in H.248 is 2944
(text) and 2945 (binary).
NOTE
The MG interface ID must be the same as that
specified on an MGC.
Issue 02 (2013-10-08)

307

Configuration Guide
Parameter
Remarks
mg-media-ip1

media-dhcp-vlan vlanid-signal: indicates
that the media IP address of a port is obtained
using the upstream VLAN ID of the MG
interface in DHCP mode. You can run the
dhcp-client command to configure the IP
address of the VLAN interface to be
NOTE
when MIDType is IP.
primary-mgc-ip1
primary-mgc-port
When dual homing is not configured, you can

configure the parameters of only one MGC.
When dual homing is configured, configure
the IP address and port ID of the standby
MGC. You can configure data on the standby
MGC only after configuring data on the
active MGC. Otherwise, the configuration
fails.
code
The coding modes of the MG interface and

the MGC must be the same. Currently, only
text coding mode is supported.
transfer
The transmission mode is selected according

to the requirements of the MGC. Generally,
UDP is used.
start-negotiate-version
If the signaling process flow on the MG is

different from that on the MGC, set this
parameter to 0 (negotiated with the profile).
In addition, set parameter profile-index
index. The profile used on the MG interface
must be the same as that on the MGC.
If the profile file in the system cannot meet
requirements, contact Huawei for technical
support.
Issue 02 (2013-10-08)

308

Configuration Guide
Step 3 Check whether the attribute of the MG interface is the same as that in the data plan.
Run the display if-h248 attribute command to check whether the attribute of the MG interface
----End
Example
Assume that the MG interface ID is 0, the H.248 protocol is used for interconnecting with the
MGC, the signaling IP address of the MG interface is 10.13.4.117, the transport layer protocol
port ID is 2944, IP address 1 of the primary MGC is 10.13.2.118, the transport layer protocol
port ID of the primary MGC is 2944, the media IP address is 10.13.4.116, the start version is 1,
and the transaction reliability is enabled. To add such an MG interface, do as follows:
huawei(config)#interface h248 0
Are you sure to add MG interface?(y/n)[n]:y
huawei(config-if-h248-0)#if-h248 attribute mgip 10.13.4.117 mgport 2944 code tex
t transfer udp primary-mgc-ip1 10.13.2.118 primary-mgc-port 2944 mg-media-ip1 10
.13.4.116 start-negotiate-version 1 retrans enable
huawei(config-if-h248-0)#display if-h248 attribute
------------------------------------------------MGID
0
MG Description
MG DomainName
Protocol
H248
Start Negotiate Version
1
Profile Negotiation Parameter
Disable
Profile index
1:NoProfile("")
2833Encrypt
Codetype
Text
Transfer Mode
UDP
HeartBeatGenTimer(s)
60
HeartBeatRetransTimes
3
HeartBeatRetransTimer(s)
60
MG signalling IP
10.13.4.117
MG signalling Port
2944
MG media IP1
10.13.4.116
MG media IP2
MIDType
IP4_ADDR
DeviceName
Retrans
Enable
Active MGC
MGC Port
:2944
MGC
Active MGC
MGC Port
:2944
MGC
Active MGC
MGC Domain Name:Standby MGC
MGC Port
:MGC
Standby MGC
MGC Port
:MGC
Standby MGC
MGC Domain Name:-------------------------------------------------
IP1:10.13.2.118
IP2:IP1:IP2:-
(Optional) Configuring the Digitmap of an MG Interface

A digitmap is a set of digit collection descriptors. It is a dialing scheme residing in media
gateways (MGs) and is used for detecting and reporting the digit events received on a terminal.
This topic describes how to configure the digitmaps for certain special applications such as
emergency calls and emergency standalone. The digitmaps for common phone services are
issued to the AG by the MGC, and therefore such digitmaps need not be configured on the AG.
If the services such as emergency calls and emergency standalone are not required, the digitmaps
need not be configured.
Issue 02 (2013-10-08)

309

Configuration Guide
Prerequisites
The MG interface has been configured. For details about how to configure the MG interface,
see Adding an MG Interface.
Context
CAUTION
The digitmap configuration is relatively complicated. The information such as the meanings and
usage of the characters in a digitmap is defined in the protocol, and is not described here. This
topic provides only some basic information. It is recommended that you refer to the digitmap
description in ITU-T H248.1 (applicable to H.248) before configuring the digitmap.
l
A digitmap is used to improve the efficiency of the MG in sending the callee number. That
is, if the callee number matches a dialing scheme defined by the digitmap, the MG sends
the callee number collectively in a message.
A digitmap consists of strings of digits with certain meanings. When the received dialing
sequence matches one of the strings, it indicates that the digits are collected completely.
To configure the emergency standalone function, you must configure the internal digitmap.
The H.248-based MG interface supports the following types of digitmaps:

l
Internal digitmap: used for matching the telephone numbers of two internal subscribers on
an MG. The digitmap is issued by the MG and applies to the emergency standalone service.
Emergency call digitmap (due to call restriction in the case of an overload): When an MG
is overloaded or the bandwidth is insufficient, subscribers can still dial the telephone
numbers that match the digitmap, such as the police call and ambulance call, through
emergency channels. The digitmap applies to emergency calls when an MG is overloaded.
Automatic redial digitmap of card services: When a subscriber makes a call using a
telephone card, the subscriber can dial another telephone number by pressing the keys
defined in the automatic redial digitmap after the call is complete and the called party hooks
up. The digitmap applies to automatic redial services.
Table 6-3 provides the valid characters in the strings and their meanings in the H.248 protocol.
For details about the digitmap in the H.248 protocol, refer to ITU-T H248.1, which provides a
better guide to the digitmap configuration.
Table 6-3 Digitmap format in the H.248 protocol
Issue 02 (2013-10-08)
Digit or
Character
Description
0-9
Indicate dialed digits 0-9.
A-D
Indicate A-D.
Indicates * in the DTMF mode.
Indicates for # in the DTMF mode.

310

Configuration Guide
Digit or
Character
Description
Indicates for a wildcard, indicating any digit from 0 to 9.
Indicates the short timer. When detecting the timer timeout, the system reports
a phone number digit by digit if the phone number is detected after the dialing
scheme is matched. The short timer is applied when the collected number
matches at least one dialing scheme, but more numbers may be received and
these numbers match other dialing schemes.
Indicates the long timer. When detecting the timer timeout, the system reports
scheme is matched. The long timer is applied when the dialed number does
not match any dialing scheme.
Indicates the duration modifier, which indicates a dialing event of a long

duration. It is before the event character with a fixed location. When the event
duration exceeds the threshold, the dialing event fills the location.
Indicates that there can be multiple digits (including 0) or characters before

it.
Used to separate the strings and indicates that each string is an optional dialing
scheme.
[]
Indicates that one digit or string can be selected from the options.
Procedure
Step 1 Enter the MG interface mode.
In global config mode, run the interface h248 command to enter the MG interface mode.
Step 2 Configure the digitmap.
Run the digitmap set command to configure the digitmap required in the data plan.
Step 3 (Optional) Configure the digitmap timer.
Run the digitmap-timer command to configure the digitmpa timer.
Generally, the digitmap is issued by the MGC. In this case, the issued digitmap timer prevails
regardless of whether a timer is configured on the AG. When the MGC does not issue the
digitmap timer and the default digitmap timer does not meet the service requirements, you can
configure the digitmap timer in this step.
Step 4 Check whether the configuration of the digitmap timer is the same as that in the data plan.
l Run the display digitmap command to check whether the digitmap is configured correctly.
l Run the display digitmap-timer command to check whether the digitmap timer is configured
correctly.
----End
Issue 02 (2013-10-08)

311

Configuration Guide
Example
Assume that the inner digitmap of H.248-based MG interface 0 is configured and the telephone
numbers of two internal subscribers on an MG are matched. According to the data plan, the inner
digitmap format is 1234xxxx. To configure the inner digitmap, do as follows:
huawei(config-if-h248-0)#digitmap set inner 1234xxxx
huawei(config-if-h248-0)#display digitmap
---------------------------------------------------------------------Inner digitmap
: 1234xxxx
Urgent digitmap (for overload or bandwidth restrict)
: Dualdial digitmap for card service
: ----------------------------------------------------------------------
(Optional) Configuring the Software Parameters of an MG Interface

The software parameters of a media gateway (MG) interface mainly define certain common
service attributes of the MG interface. After the software parameter configuration, the parameters
take effect immediately and are valid only to the MG interface. Skip this topic if the system
configuration meets user requirements.
Prerequisites
Context
The details about the software parameters that can be configured of an MG interface that supports
H.248, see section Usage Guidelines in mg-software parameter. The other parameters are
reserved in the system.
Table 6-4 lists parameters that are usually configured to a non-default value. The other
parameters are not required.
Table 6-4 Software parameters usually configured of an MG interface that supports H.248
Parameter
Description
Default Setting
Indicates whether the MG

interface supports dual homing.
Numeral type. Range: 0-2.

l 0: Indicates that dual homing
is not supported.
rather than auto-switching is
supported.
and auto-switching is
supported.
Default: 0
This parameter is usually set to
2.
Issue 02 (2013-10-08)

312

Configuration Guide
Parameter
Description
Default Setting

interface supports device
authentication.

l 0: Indicates that device
authentication is supported.
authentication is not
supported.
Default: 1
11

interface supports emergency
standalone.

l 0: Indicates that no call is
permitted.
l 1: Indicates that only internal
call is permitted.
l 2: Indicates that only
emergency call is permitted.
l 3: indicates that internal call
and emergency call are
permitted.
Default: 0
Procedure
Step 2 Configure software parameters.
Run the mg-software parameter command the software parameters required in the data plan.
Step 3 Check whether the software parameters are the same as those in the data plan.
Run the display mg-software parameter command to check whether the software parameters
of the MG interface are the same as those in the data plan.
----End
Example
To configure software parameter 11 of H.248-based MG interface 0 to 1 so that the MG interface
supports emergency standalone and allows only internal calls, do as follows:
huawei(config-if-h248-0)#mg-software parameter 11 1
huawei(config-if-h248-0)#display mg-software parameter 11
------------------------------------------------Interface Id:0
para index:11 value:1
------------------------------------------------APPENDIX:
-------------------------------------------------
Issue 02 (2013-10-08)

313

Configuration Guide
Interface software parameter name:

11: Stand alone support
0: None
1: Inner
2: Emergency
3: Both
The MA5616 interconnects with an MGC from another vendor. The maximum RTP terminal
ID of the MGC is 64. To configure the MA5616 with its MG interface software parameter 24
set to 64 and the maximum RTP terminal ID of MG interface 0 to 64, do as follows:
------------------------------------------------Interface Id:0
------------------------------------------------APPENDIX:
------------------------------------------------Interface software parameter name:
24: Max. RTP terminal ID
(Optional) Configuring the Ringing Mode of an MG Interface

This topic describes how to configure the ringing mode of an MG interface to meet different
user requirements. If the default ringing mode (the cadence ringing and initial ringing both are
1:4) meets user requirements, skip this topic.
Context
Add the ringing mode mapping records of a specified MG interface. After the adding is
successful, the MG interface can obtains the ringing mode according to the peer parameters
issued by the MGC and then play the ringing to the user in this mode.
Procedure
Step 1 Check whether the ringing mode meets the requirements.
Check whether the preset ringing mode in the system meets the requirements according to the
Usage Guidelines of the mg-ringmode add command.
l If the preset ringing mode meets the requirements, go to Step 3.
l If the preset ringing mode does not meet the requirements, proceed to Step 2.
Step 2 Configure the user-defined ringing mode.
In the global config mode, run the user defined-ring modify command to configure the breakmake ratio of user-defined ringing mode to form a ringing mode that meets the user requirement.
CAUTION
The system supports 16 user-defined ringing modes, which can be modified but cannot be added
or deleted.
Issue 02 (2013-10-08)

314

Configuration Guide
Run the interface h248 command to enter the MG interface mode.

Step 4 Add a ringing mapping.
Run the mg-ringmode add command to add a ringing mapping.
CAUTION
1. The peer parameter mgcpara that is on the MG and issued by the MGC must be the same as
the parameter mgcpara on the MGC.
2. User-defined ringing modes 0 to 15 correspond to cadence ringing modes 128 to 143
respectively, and correspond to initial ringing modes 144 to 159 respectively. For example,
if the cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the initial
ringing mode is 144, user-defined ringing mode 0 is selected.
Step 5 Check whether the ringing mapping is the same as that in the data plan.
Run the display mg-ringmode attribute command to check whether the ringing mapping is the
same as that in the data plan.
----End
Example
Assume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 0, the cadence
ringing is 1:4 (the value of the corresponding parameter cadence is 0), and the initial ringing is
1:2 (the value of the corresponding parameter initialring is 17). To configure the ringing mode
of MG interface 0, do as follows:
huawei(config-if-h248-0)#mg-ringmode add 0 0 17
huawei(config-if-h248-0)#display mg-ringmode attribute
{ <cr>|mgcpara<0,15> }:
Command:
display mg-ringmode attribute
------------------------------------------------------MGID
PeerPara
CadenceRing
InitialRing
------------------------------------------------------0
0
0
17
-------------------------------------------------------
Assume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 1, the breakmake ratio of user-defined ringing mode 0 is 0.4sec On, 0.2sec Off, 0.4sec On, 2.0sec Off, and
the initial ringing and the cadence ringing use user-defined ringing mode 0 (the values of the
corresponding parameters cadence and initialring are 128 and 144 respectively). To configure
the ringing mode of MG interface 0, do as follows:
huawei(config)#user defined-ring modify 0 para1 400 para2 200 para3 400 para4 2000
huawei(config)#display user defined-ring
{ <cr>|ring-type<0,15> }:
Command:
display user defined-ring
-------------------------------------------------RingType Para1 Para2 Para3 Para4 Para5 Para6
--------------------------------------------------
Issue 02 (2013-10-08)

315

Configuration Guide
0
400
200
400
2000
0
0
1
0
0
0
0
0
0
2
0
0
0
0
0
0
3
0
0
0
0
0
0
......
14
0
0
0
0
0
0
15
0
0
0
0
0
0
-------------------------------------------------huawei(config)#interface h248 0
{ <cr>|mgcpara<0,15> }:
Command:
------------------------------------------------------MGID
PeerPara
CadenceRing
InitialRing
------------------------------------------------------0
1
128
144
-------------------------------------------------------
(Optional) Configuring the TID Format of an MG Interface

A terminal ID (TID) profile determines how various user terminal IDs on a media gateway (MG)
interface are generated. If the default TID profile in the system meets user requirements, skip
this topic.
Context
CAUTION
The configuration of the TID format is relatively complicated. The information such as the syntax
rules with which the terminal prefix must comply and the requirements for the character string
of the TID template is defined in the protocol, and is not described here. This topic describes
only some basic information. It is recommended that you refer to the TID description in ITU-T
H248.1 before configuring the TID format.
The TID format consists of the terminal prefix and the TID template. The TID template defines
the generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefix
and a character string generated by a TID template.
Terminal layering: indicates that a terminal user is identified by layered parameters, such as
subrack ID/slot ID/port (B channel) ID. Based on standards in different countries, you can
determine whether configure the feature for a user.
The TID templates that are bound to various types of users on the MG interface determine
whether the users support terminal layering.
l
If the parameter list of the TID template includes only keyword "G", it indicates that the
TID template is used by the non-layering users. Users bound with this template do not
support terminal layering.
If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" is
not available to PSTN users), it indicates that the TID template is used by the layering users.
Users bound with this template support terminal layering.
Issue 02 (2013-10-08)

316

Configuration Guide
NOTE
The meaning of each keyword is as follows:

l
F indicates the shelf ID.
S indicates the slot ID.
P indicates the port ID.
B indicates the B channel ID (only for ISDN BRA and ISDN PRA terminals).
G indicates the general permanent termination index.
R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, which
exists only when the system protocol is H.248. This termination is not involved unless special remarks
are provided.)
Procedure
Step 1 To query the template information.
Run the display tid-template command to query the information about the default TID profile
of the system.
The system defines 19 default TID profiles with IDs from 0 to 18. These profiles can only be
referenced, but cannot be added, modified, or deleted.
Step 2 Check whether the default TID template of the system meets the service requirements.
If the default 19 TID profiles cannot meet service requirements, run the tid-template add
command to add a TID profile. Otherwise, proceed to Step 3.
Step 4 Configure the TID templates and the terminal prefix of various types of users on the current MG
(VAG).
l In H248 mode, run the tid-format rtp command to configure the TID template and terminal
prefix of the RTP ephemeral termination.
l In H248 mode, run the tid-format pstn command to configure the TID template and terminal
prefix of the PSTN user.
l In H248 mode, run the tid-format bra command to configure the TID template and the
terminal prefix of the ISDN BRA user.
NOTE
l If certain type of terminal exists on an interface and the interface is not disabled, the terminal prefix of
this type of terminal cannot be modified.
l If a certain type of terminal exists on an interface, the TID format (including the terminal prefix and
the index of the TID profile) of this type of terminal cannot be modified.
l The terminal prefix must comply with the following syntax rules: The prefix supports a maximum of
64 characters and supports letters, digits, underscore (_), and slash (/); the first character must be a
letter, and the last character cannot be a digit.
l The length of the TID, which is generated by combining the configured TID profile and the terminal
prefix, cannot exceed 64 characters.
Step 5 Check whether the TID template and the terminal prefix are the same as those in the data plan.
Issue 02 (2013-10-08)

317

Configuration Guide
Run the display tid-format command to check whether the TID profiles and the terminal
prefixes of various types of users on the current MG interface are the same as those in the data
plan.
The configuration of terminal layering on the MG must be the same as that on the MGC.
l Run the display tid-format command to query the TID formats of various types of users on
the current MG interface. In the query result, template-index indicates the index of the TID
profile that is bound to the type of user. Then run the display tid-template command to
check whether the TID template supports the layering configuration. You can learn about
whether the user supports terminal layering.
l When adding a user that supports terminal layering, you do not need to specify parameter
terminalid because the system automatically allocates a terminal ID. When adding a user
that does not support terminal layering, you must specify parameter terminalid.
----End
Example
Assume that in the H.248 mode, the terminal prefix of the PSTN user on MG interface 1 is aln/,
and the layering TID template 3 is used. To add a PSTN user on port 0/3/0 and check whether
the system automatically allocates a TID generated according to the template, do as follows:
huawei(config)#display tid-template 3// Query the information about the TID
template 3.
------------------------------------------------Index
: 3
Format
: %u/%u/%u
Para-list : F+1,S+1,P+1 // Keywords in the parameter list of the TID template
are "F", "S", and "P".
Name
: Aln_Not_Fixed_1
------------------------------------------------huawei(config)#interface h248 1
huawei(config-if-h248-1)#tid-format pstn prefix aln/ template 3
huawei(config-if-h248-1)#quit
huawei(config)#esl user
huawei(config-esl-user)#mgpstnuser add 0/3/0 1
huawei(config-esl-user)#display mgpstnuser 0/3/0
{ <cr>|endframeid/slotid/portid<S><Length
1-15> }:
Command:
display mgpstnuser 0/3/0
---------------------------------------------------------------------------F /S /P
MGID
TelNo
Priority PotsLineType
TerminalID
---------------------------------------------------------------------------0 /3/0
1
Cat3
DEL
aln/1/3/1
----------------------------------------------------------------------------
The MA5616 interconnects with an MGC from another vendor. TID profiles pstn (index: 32)
and Z-RTP (index: 33) are added on the MA5616. The parameter list of profile pstn is G and
the character string display format is %02u. The parameter list of profile Z-RTP is R and the
character string display format is %05u.
To configure the terminal prefix to RTP/ and TID profile 33 for RTP users connected to MG
interface 1, and configure the terminal prefix to AG589 and TID profile 32 for PSTN users, do
as follows:
huawei(config)#tid-template add 32 format %02u parameter-list G name pstn
huawei(config)#tid-template add 33 format %05u parameter-list R name Z-RTP
Issue 02 (2013-10-08)

318

Configuration Guide
huawei(config-if-h248-1)#tid-format rtp prefix RTP/ template 33 pstn prefix AG589

template 32
Enabling an MG Interface
Enabling an MG interface is to reset an MG interface to make the MG interface register with
the MGC (or to make the modified attributes of the MG interface take effect) after the
configuration of the MG interface is complete, so that the MG interface can work in the normal
state.
Precaution
CAUTION
For the MG interface that has been in service, this operation interrupts the ongoing services
carried on the MG interface. Hence, exercise caution when performing this operation.
Procedure
Step 1 Enter the H248 mode.
Run the interface h248 command to enter the H248 mode.
Step 2 Enable the MG interface.
Run the reset coldstart command to enable the MG interface.
Step 3 Check the state of the MG interface.
You can query the status of the MG interface by using one of the following two methods.
l Run the display if-h248 state command to check whether the MG interface is in the normal
state.
l Run the quit command to quit the global config mode, and then run the display if-h248
all command to check whether the MG interface is in the normal state.
NOTE
The running states of an MG interface can be Local Closed, Remote Closed, Normal, Wait ack, and
Graceful Closed. For the state meanings, see parameter description of State in display if-h248 all of the
Command reference.
----End
Example
To enable H.248-based MG interface 0, do as follows:
huawei(config-if-h248-0)#reset coldstart
Are you sure to reset MG interface?(y/n)[n]:y
huawei(config)#display if-h248 all
-------------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
MGCPort MGCIP/DomainName
Issue 02 (2013-10-08)

319

Configuration Guide
-------------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.11
2944
10.10.20.11
--------------------------------------------------------------------------------
6.1.2 Configuring the VoIP PSTN User

After an MG interface is configured, you can add public switched telephone network (PSTN)
users on the MG interface to implement the VoIP service.
Configuring PSTN User Data

This topic describes how to configure the PSTN user data (the same as the corresponding data
on the MGC) on the MG interface so that the POTS terminal can access the network to implement
the VoIP service.
Prerequisites
The POTS service board can be detected and is working properly.
Context
Table 6-5 lists the default settings of the attributes of the PSTN user. When configuring the
attributes of the PSTN user, you need to modify them according to the service requirements.
Table 6-5 Default settings of the attributes of the PSTN user
Issue 02 (2013-10-08)
Parameter
Default Setting
Sequence of sending the phone

number of the calling party
Ringing and then sending the phone number
Format of the phone number of the

calling party
SDMF (FSK single data message format)
Whether to support the detection of

the ANSbar signal through
monophony
Not support
Whether to support the bell ANS

signal
Not support
Power-off interval
100 ms
FSK delay interval
800 ms
Whether to enable or disable VQE

automatic gain
Disable

noise suppression
Disable
Target value of VQE automatic gain
-22 dBm

320

Configuration Guide
Parameter
Default Setting
Target value of VQE noise

suppression
12 dB
Input gain of the DSP chip
0 dB
Output gain of the DSP chip
0 dB
Name of the DSP parameter profile
- (Indicates that the DSP parameter profile is not

configured.)
FSK mode of the caller ID display
BELL_202
TAS mode of the caller ID display
NO-TAS
Whether to enable or disable the force

send FSK
Not support
Duration between the time of

receiving an FSK end event and the
time of receiving a cadence ringing in
the onhook state when the H.248
protocol is used
40
Procedure
Step 1 Add a PSTN user.
1.
In global config mode, run the esl user command to enter the ESL user mode.
2.
Run the mgpstnuser add or mgpstnuser batadd command to add a PSTN user or add
PSTN users in batches.
Issue 02 (2013-10-08)

321

Configuration Guide
CAUTION
l When you add a PSTN user, terminalid must be configured and must be different from
the TID of an existing PSTN user if the TID template with which the PSTN user on the
MG interface is bound is not a layering template.
l When you add a PSTN user, the configuration of the TID is not required because the
system automatically allocates the TID if the TID template with which the PSTN user
on the MG interface is bound is a layering template.
l When adding a PSTN user, you can configure the phone number (parameter telno). The
configured phone number, however, can be used only as the paging number for
emergency standalone. It is recommended that you configure the phone number to be
the same as the phone number allocated by the MGC. In addition, the phone number
must be unique on the MG. This prevents number conflict when emergency standalone
is enabled. If this parameter is not set, the phone number is null by default. Phone
numbers for normal call services are allocated by the MGC, generally, no telephone
number (namely, parameter telno) is configured on the MG.
l For details about the relationship between the TID template and the terminal layering,
see the Context in (Optional) Configuring the TID Format of an MG Interface.
3.
Run the display mgpstnuser command to check whether the configured PSTN user data
is the same as the planned data.
Step 2 (Optional) Configure the attributes of a PSTN user.

The attributes of a PSTN user need to be configured only when the default settings are
inconsistent with the actual application.
1.
Run the mgpstnuser attribute set command to configure the attributes of a single PSTN
user, or run the mgpstnuser attribute batset command to configure the attributes of PSTN
users in batches.
2.
Run the display mgpstnuser attribute command to check whether the attributes of the
PSTN user are the same as the planned data.
----End
Example
Assume that the phone numbers of 16 PSTN users are 83110000-83110015, terminalid are 0-15
(the TID template with which the PSTN users on the MG interface are bound is not a layering
template and terminalid needs to be allocated manually), and the default values are used for
other attributes. To add the 16 PSTN users in slot 0/3 on MG interface 0 in batches, do as follows:
huawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/15 0 terminalid 0 telno
83110000
huawei(config-esl-user)#display mgpstnuser 0 0 10
---------------------------------------------------------------------------F /S /P
MGID
TelNo
TerminalID
---------------------------------------------------------------------------0 /3 /0
0
83110000
Cat3
DEL
A0
......
0 /3 /14
0
83110014
Cat3
DEL
A14
Issue 02 (2013-10-08)

322

Configuration Guide
0 /3 /15
0
83110015
Cat3
DEL
A15
----------------------------------------------------------------------------
(Optional) Configuring the System Parameters

This topic describes how to configure the system parameters including the overseas version flag
and message waiting indication (MWI) mode according to the local standards to ensure that the
response of the user terminal complies with the local standards. If the system default settings
meet local standards, skip this topic.
Context
Table 6-6 lists the system parameters supported by the MA5616.
Table 6-6 System parameters supported by the MA5616
Issue 02 (2013-10-08)
Parameter
Description
Default Setting
Indicates the howler tone

sending flag.
1: Indicates that the howler tone

is sent.
Indicates the overseas version

flag.
0: Indicates China.
Indicates the initial ringing stop

flag.
0: Indicates that the initial

ringing stop flag is not issued.
Indicates the MWI mode.
1: Indicates that the FSK is sent

with ringing.
Indicates the global digitmap

support flag.
1: Indicates that the global

digitmap is supported.
Indicates the media stream

forwarding mode on the same
device.
0: Indicates that the media stream

is forwarded within the device.
Indicates whether to send

power deny flag when
softswitch indicates block.
1: No send power deny.
7-11
Indicate the reserved

parameter.
12
Indicates the Howler tone

source.
0: Analog subscriber line board
13
Indicates the period of absent

DSP resource alarm control.
16
14
Indicates the count of tolerable

DSP resource insufficiencies in
the period configured by
parameter 13.
16

323

Configuration Guide
Parameter
Description
Default Setting
15-255

parameter.
Procedure
Step 1 Run the system parameters command to configure the system parameters.
Step 2 Run the display system parameters command to check whether the system parameters are the
same as the planned data.
----End
Example
To configure the overseas version flag (system parameter 1) to Hong Kong (parameter value 1),
do as follows:
huawei(config)#system parameters 1 1
huawei(config)#display system parameters 1
----------------------------------------------------------------------------Parameter name index: 1
Parameter value: 1
Mean: 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,
13:Poland, 14:Turkey, 20:Germany
-----------------------------------------------------------------------------
(Optional) Configuring the Overseas Parameters

By default, the overseas parameters are configured according to the Chinese standards. In the
actual service configuration, the attributes such as the upper and lower thresholds of the flashhooking duration can be configured according to the local standards to ensure that the response
of the user terminal complies with the local standards.
Context
Table 6-7 lists the overseas parameters supported by the MA5616.
Table 6-7 Overseas parameters supported by the MA5616
Issue 02 (2013-10-08)
Parameter
Description
Default Setting
Indicates the upper threshold of

the flash-hooking duration.
350 ms (in compliance with the

Chinese mainland standards)
Indicates the lower threshold of


Indicates whether the current is 0: Indicates that the current is not

limited when the user port is
limited.
locked.
324

Configuration Guide
Parameter
Description
Default Setting
Indicates the type of ring DC

offset.
Line B offset
indicates the type of the DTMF

detector tuning.
Indicates that the device

complies with ITU-T Q.24. The
value is the common
configuration for a detection
parameter.
4, 6-255
Indicate the reserved parameter
Procedure
Step 1 Configure the overseas parameters.
Run the oversea parameters command to configure overseas parameters.
Step 2 Check whether the overseas parameters are the same as the data plan.
Run the display oversea parameters command to check whether the overseas parameters are
the same as the data plan.
----End
Example
To set the upper flash-hooking threshold (overseas parameter 0) to 800 ms (in compliance with
the Hong Kong standards) and the lower flash-hooking threshold (overseas parameter 1) to 100
ms (in compliance with the Hong Kong standards), do as follows:
huawei(config)#oversea parameters 0 800
huawei(config)#display oversea parameters
{ <cr>|name<0,3> }:
Command:
display oversea parameters
Parameter value: 800
Mean: Hooking upper threshold(ms), reference: China:350, HongKong:800
Mean: Hooking lower threshold(ms), reference: China:100, HongKong:100
Parameter value: 0
Mean: Flag of applying PARKED LINE FEED or not when user port is locked, 0:not
apply, 1:apply
Parameter value: 1
Mean: Type of ring DC offset, 0:Line A offset, 1:Line B offset
Parameter value: 0
Mean: The standard of the DTMF signal tone detection parameter
0:means to comply with the ITU-T Q.24 protocol standard. It is the common
configuration for the detection parameter
7:means to avoid speech detected as DTMF
-----------------------------------------------------------------------------
Issue 02 (2013-10-08)

325

Configuration Guide
(Optional) Configuring the Local Digitmap

A local digitmap is also called a local preconfigured digitmap and is used to match telephone
numbers. When the H.248 protocol is used, the MA5616 prefers to use the digitmap sent by the
MGC to match the phone number. If the MGC does not send the detailed digitmap, the
MA5616 uses the local digitmap to match the phone number. When the SIP protocol is used,
the MA5616 has to use the local digitmap to match the phone number because the IMS network
does not send the digitmap. When configuring services on the MA5616, configure a proper local
digitmap according to the local standards.
Context
l
The MA5616 supports a maximum of eight local digitmaps.
For the meaning of each character in the digitmap body, see the Context in (Optional)
Configuring the Digitmap of an MG Interface.
When the H.248 protocol is used, the type of the local digitmap can only be normal.
When the SIP protocol is used, the type of the local digitmap can be normal, emergency,
scc, direct-centrex, or second-centrex. For the meaning of the digitmap type, see the
Parameter Description in the local-digitmap add command.
Precaution
Procedure
Step 1 Query the current protocol type.
In privilege mode, run the display protocol support command to query the current protocol
type used on the MA5616.
Step 2 Add a local digitmap according to the data plan.
Run the local-digitmap add command to add a local digitmap according to the data plan.
Step 3 Check whether the local digitmap is the same as the data plan.
Run the display local-digitmap command to check whether the local digitmap is the same as
the data plan.
Step 4 (Optional) Modify the local digitmap.
Run the local-digitmap modify command to modify the name, type, or body of the local
digitmap.
Step 5 (Optional) Add or modify the digitmap body.
Run the local-digitmap append command to add or modify the digitmap body in a configured
local digitmap.
----End
Example
Assume that the H.248 protocol is used on the MA5616. To add a local digitmap with the data
listed in Table 6-8, do as follows:
Issue 02 (2013-10-08)

326

Configuration Guide
Table 6-8 Local digitmap to be added

Digitmap Name
Digitmap Type
Digitmap Body
huawei
normal
([2-8]xxxxxxx|[2-8]
xxSxxxxxxx|13xxxxxxxxx|
0xxxxxxxxx|9xxxx|1
[0124-9]x|F|x.F|[0-9].S)
huawei(config)#local-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13

xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S) h248
huawei(config)#display local-digitmap all
-----------------------------------------Name: huawei
Body: ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|
x.F|[0-9].S)
Protocol: h248
------------------------------------------
Assume that the SIP protocol is used on the MA5616. The local digitmap exists in the system.
Table 6-9 lists the data of the local digitmap.
Table 6-9 Local digitmap existing in the system
Digitmap Name
Digitmap Type
Digitmap Body
huawei
normal
([2-8]xxxxxxx|[2-8]
0xxxxxxxxx|9xxxx|1
[0124-9]x|F|x.F|[0-9].S)
When an existing local digitmap is different from the data plan, you need to modify the local
digitmap. To change the name of the local digitmap to huawei0, add digitmap body
15xxxxxxxxx, and add a local best-effort digitmap according to data plan listed in Table 6-10
so that when an MG interface becomes faulty, other users on the MG can use the digitmap, do
as follows:
Digitmap Name
Digitmap Type
Digitmap Body
huawei1
emergency
(0E)

-----------------------------------------Name: huawei
x.F|[0-9].S)
-----------------------------------------huawei(config)#local-digitmap modify huawei name huawei0
huawei(config)#local-digitmap append huawei0 15xxxxxxxxx
Issue 02 (2013-10-08)

327

Configuration Guide
huawei(config)#local-digitmap add huawei1 emergency (11X|91X|0E) sip

-----------------------------------------Name: huawei0
Type: normal
x.F|[0-9].S|15xxxxxxxxx)
Protocol: sip
-----------------------------------------Name: huawei1
Type: emergency
Body: (11X|91X|0E)
Protocol: sip
------------------------------------------
(Optional) Configuring the Attributes of a PSTN Port

This topic describes how to configure the attributes of a PSTN port to ensure that the PSTN port
can meet the actual application requirements. The attributes include polarity-reversing pulse,
impedance, and KC accounting.
Context
The MA5616 supports the following attributes of a PSTN port:
l
Physical attributes (including whether to support the polarity reversal pulse, whether to
support the port locking, and dialing mode). For details about how to configure the physical
attributes of a PSTN port, see the command pstnport attribute set.
Electrical attributes (including the impedance and the current). For details about how to
configure the electrical attributes of a PSTN port, see the command pstnport electric
set.
KC attributes (including the KC charging mode and the valid voltage). For details about
how to configure the KC attributes of a PSTN port, see the command pstnport kc set.
Procedure
Step 1 Enter the PSTN port mode.
In global config mode, run the pstnport command to enter the PSTN port mode.
Step 2 Configure the physical attributes of a PSTN port.
l Run the pstnport attribute set command to configure the physical attributes of a single
PSTN port.
l Run the pstnport attribute batset command to configure the physical attributes of PSTN
ports in batches.
Step 3 Configure the electrical attributes of the PSTN port.
l Run the pstnport electric set command to configure the electrical attributes of a single PSTN
port.
l Run the pstnport electric batset command to configure the electrical attributes of PSTN
ports in batches.
Step 4 Configure the KC attributes of the PSTN port.
l Run the pstnport kc set command to configure the KC attributes of a single PSTN port.
Issue 02 (2013-10-08)

328

Configuration Guide
l Run the pstnport kc batset command to configure the KC attributes of PSTN ports in
batches.
Step 5 Check whether the attribute configuration of the PSTN port is the same as the planned data.
l
Run the display pstnport attribute command to query the physical attributes of the PSTN
port.
Run the display pstnport electric command to query the electrical attributes of the PSTN
port.
Run the display pstnport kc command to query the KC attributes of the PSTN port.
----End
Example
To configure PSTN ports 0-15 on the board in slot 0/3 to support the polarity reversal charging,
do as follows:
huawei(config)#pstnport
huawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse
enable
NOTE
When a call starts and ends, the MG shows the start time and the end time based on the polarity reversal
on the subscriber line. The billing terminal that supports the polarity reversal charging function, such as a
charging phone set, implements the polarity reversal charging function based on the start time and the end
time of a call.
(Optional) Configuring the Attributes of the Ringing Current

You can adjust the ringing volume and ringing tone by modifying the attributes of the ringing
current. Generally, the attributes of the ringing current need not be modified. You need to modify
the attributes of the ringing current according to the local standards only when the default ringing
current attributes do not meet the local standards.
Context
The attributes of the ringing current include the following two parameters:
l
Ringing current frequency: The higher the frequency is, the sharper the ringing tones are.
AC voltage amplitude: The greater the amplitude is, the louder the ringing tones are.
Procedure
Step 1 Enter the VoIP mode.
In global config mode, run the voip command to enter the VoIP mode.
Step 2 Configure the attributes of the ringing current.
Run the ring attribute set command to configure the attributes of the ringing current according
to the data plan.
Step 3 Check whether the attributes of the ringing current are the same as the data plan.
Issue 02 (2013-10-08)

329

Configuration Guide
Run the display ring attribute command to check whether the attributes of the ringing current
are the same as the data plan.
----End
Example
To set the ringing current frequency to 16 Hz (parameter value 0) and AC amplitude to 50 Vrms
(parameter value 2), do as follows:
huawei(config)#voip
huawei(config-voip)#ring attribute set frequency 0 acamplitude 2
huawei(config-voip)#display ring attribute
ringing current frequency : 16Hz
ringing current acamplitute: 50Vrms
6.2 Configuring the VoIP PSTN Service (Based on the SIP

Protocol)
The SIP-based VoIP technology makes the transport network evolve to the IP network without
decreasing the voice quality, provides more value-added functions for users, and saves expense.
Context
The voice over IP (VoIP) service uses the IP packet switching network for transmission after
the traditional analog voice signals are compressed and packetized, to reduce the cost of the
voice service.
For details about the VoIP service, see Voice in the Feature Description.
As shown in Figure 6-1, the MA5616 can also function as a voice over IP gateway (VGW)
component in the IMS architecture. In the downstream direction, it provides the access to PSTN
users; in the upstream direction, it is connected to the IMS system through the SIP interface,
providing the VoIP service by working with the IMS core based on SIP protocol.
Figure 6-1 Example network of the SIP voice service
PE-AGG
Access
Node
UPE
Phone
Metro Network
Phone
IMS Core
SIP
UPE
Phone
Issue 02 (2013-10-08)
PE-AGG

330

Configuration Guide
Prerequisite
l
The current protocol is SIP protocol. In privilege mode, run the display protocol
support command to query the current protocol type used on the MA5616. if the current
protocol is not SIP protocol, run the command protocol support to set the protocol to SIP
protocol.
According to the actual network, a route from the MA5616 to the IMS core network device
must be configured to ensure that the MA5616 and the IMS core network device are
reachable to each other.
Data preparation
Table 6-11 provides the data plan for configuring the VoIP service.
Table 6-11 Data plan for configuring the VoIP service based on the SIP protocol
Item
SIP interface
data
Remarks
Parameter
s of the
media
stream and
signaling
stream
Media and
signaling
upstream VLAN
It is used as the upstream VLAN of the

VoIP service to be configured. Note that
the media stream and the signaling
stream can use the same VLAN or
different VLANs. The result is
determined according to the negotiation
with the upstream device.
Signaling
upstream port
It is used as the upstream port for

configuring the SIP signaling.
Media IP address
and signaling IP
address

address pools consist of all the IP
Default IP address
of the MG
It is the IP address of the next hop from

the MA5616 to the IMS core network
device.
CAUTION
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 fail.
Attribute
parameter
s of the SIP
interface
Issue 02 (2013-10-08)
SIP interface ID
It is the SIP interface ID used for the

VoIP service to be configured. The
MA5616 supports four virtual access
gateways (VAGs).

331

Configuration Guide
Item
Remarks
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
SIP
interface
fails to be
started if
these
parameter
s are not
configure
d.
Signaling port ID
of the SIP
interface
The value range is 5000-5999. The

protocol specifies the port ID to be
5060.
IP address of the
primary IMS core
network device to
which the SIP
interface belongs

parameters of only the primary IMS
core network device are required. If
dual homing is configured, the IP
address and the port ID of the secondary
IMS core network device must be
configured.
Port ID of the
primary IMS core
network device to
which the SIP
interface belongs
Transmission
mode of the SIP
interface

according to the requirements on the
IMS core network device. Generally,
UDP is adopted.
Home domain of
the SIP interface
It corresponds to parameter homedomain in the MG interface attributes.
Index of the
profile used by the
SIP interface
It corresponds to parameter profileindex in the MG interface attributes.
IP address
obtaining mode of
the proxy server
l In IP mode, the IP address and the

port ID of the primary proxy server
must be configured.
l In DNS-A or DNS-SRV mode, the
domain of the primary proxy server
must be configured.
Voice service
data
(The data
configuration
must be
consistent with
the data
configuration
on the MGC.)
Issue 02 (2013-10-08)
Ringing Mode of the SIP

Interface
The ringing mode of the SIP interface

is determined by service requirements.

service board
Specify the slot ID based on site

requirements.
User Data
The phone number that the IMS core

network device allocates to the user
must be configured.
Phone number

332

Configuration Guide
Item
Remarks
User priority

the user priority needs to be specified.
The user priorities are as follows:
government users)
government users)
l cat3: normal (common users,
default priority in the system)
Priorities cat1, cat2, and cat3 are in an
descending order.
User type

the user type needs to be specified. The
user type includes the following:
l DEL: direct exchange lines (default
type in the system)
DEL users are directly connecting to
device ports through user lines; PBX
users are connecting to device ports
through PBX; payphone users are
connecting to device ports through
accounting terminals.
Issue 02 (2013-10-08)
Centrex
According to the local standards, the

out-centrex prefix and out-centrex
attributes need to be configured.
System Parameters

overseas version flag and message
be configured according to the local
the user terminal complies with the
local standards.
Overseas Parameters

according to the local standards to
ensure that the response of the user
terminal complies with the local
standards.

333

Configuration Guide
Item
Remarks
Local Digitmap
Configure a proper local digitmap

according to the local standards. After
the configuration, the local digitmap
can be directly used to match the phone
number after the user picks the phone
off the hook.
Attributes of a PSTN Port
If the PSTN port needs to support the

polarity reversal charging, the PSTN
port needs to be configured to support
the polarity reversal pulse. Other
attributes need not be modified if there
is no special requirement.

Current
You can adjust the ringing tone volume

by modifying the attributes of the
ringing current. Generally, the
parameters of the ringing current
attributes need not be modified. You
need to modify the parameters of the
ringing current attributes according to
the local standards only when the
default ringing current attributes do not
meet the local standards.
Procedure
6.2.1 Configuring the SIP Interface

As an interface used for the intercommunication between the MA5616 and the IMS core network
devices, the interface is vital to the SIP-based VoIP service. Therefore, to implement the VoIP
service, the SIP interface must be configured and must be in the normal state.
Procedure
Context
Issue 02 (2013-10-08)

334

Configuration Guide
Procedure
1.
2.
----End
Example

Prerequisites
VLAN Interface.
Issue 02 (2013-10-08)

335

Configuration Guide
Context
l
Procedure
1.
pool.
2.

1.
address pool.
2.
----End
Example
huawei(config)#voip
Media:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
Issue 02 (2013-10-08)

336

Configuration Guide

Signaling:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Adding an SIP Interface

This topic describes how to add a Session Initiation Protocol (SIP) interface and configure the
basic and optional attributes of the interface for the MA5616 to communicate with the IP
multimedia subsystem (IMS). The basic SIP interface attributes include the Media IP,
Signalling IP, Transfer mode, Signalling Port, and Home Domain Name. The optical
attributes include the MG Domain Name, Description, and Register URI.
Prerequisites
l
The MA5616 uses the SIP protocol.
The media and signaling IP addresses to be configured for the SIP interface have been
added to the media and signaling IP address pools.
Context
One MA5616 supports four SIP interfaces.
Procedure
Step 1 Run the interface sip command to add an SIP interface.
Step 2 Run the if-sip attribute basic command to configure the basic attributes of the SIP interface.
The basic attributes of a SIP interface include the following:
l Media IP and Signalling IP: specify the IP addresses used by the service stream and
signaling stream over the SIP interface.
l Signalling Port: specifies the port ID used for communication using the SIP interface. The
SIP-defined port ID 5060 is recommended.
l Transfer Mode: specifies the transmission mode, which can be Transmission Control
Protocol (TCP), User Datagram Protocol (UDP), or Stream Control Transmission Protocol
(STCP) mode. This mode must be the same as the mode configured on the IMS.
l Proxy IP and Proxy Domain Name: specify the address of the IMS. At least one of them
must be configured. The specified IP address or name must be the same as that configured
on the IMS.
l Proxy Address Mode: specifies the mode (IP address or domain name) used by the device
to recognize a proxy server.
l Proxy Port: specifies the port ID used by the device to communicate with the IMS. The port
ID must be the same as that configured on the IMS.
Issue 02 (2013-10-08)

337

Configuration Guide
l Home Domain Name: specifies the name of the home domain that provides services for SIP
users. If the optional attribute Register URI is not configured for the SIP interface, the
interface uses the home domain name (a mandatory attribute) to register with the server.
l SIP Profile Index: specifies a SIP profile that defines coding and decoding priorities, coding
and decoding types, and packetization duration.
Step 3 Run the if-sip attribute optional command to configure the optional attributes of the SIP
interface.
Optional attributes of a SIP interface include the following:
l Description: describes information about the SIP interface, facilitating interface
management and maintenance.
l Phone Context: specifies the range of local phone numbers. This attribute and a local phone
number identify a globally-unique resource. For information about the valid character set
and format, see RFC3966.
l Register URI: specifies the uniform resource identifier (URI) of the server with which a SIP
user registers.
l URI-Conference Factory URI: identifies a conference server that allocates conference
resources based on the received conference request. Configure this parameter if a SIP user
subscribes to the conference service. For information about the valid character set and format,
see RFC3261.
l SDP Negotiation Mode: specifies the preferential Session Description Protocol (SDP)
negotiation mode, which can be the local or remote mode.
l Mode of Supporting Proxy Dual-Homing: specifies whether the device supports IMS dualhoming and automatic switchback.
l Proxy Detection Mode: includes the option, probe, and register modes. The probe mode is
used if the device does not support IMS dual-homing. The option or register mode is used if
the device supports IMS dual-homing.
l Proxy Refresh Mode: includes three modes, that is, immediate, defer, and no-switch.
Step 4 Run the display if-sip attribute command to query the SIP interface attributes.
Step 5 After the configuration, you need to run the reset command to reset the SIP interface to make
the configuration take effect.
Step 6 After the configuration, run the display if-sip attribute running command to query the status
of the SIP interface.
----End
Example
Assume that the media IP address is 10.13.4.116, signaling IP address is 10.13.4.117,
transmission protocol is UDP, port ID is 5000, IP address 1 of the primary proxy server is
10.13.4.118, port ID of the primary proxy server is 5060, domain name of the primary proxy
server is proxy.domain, IP address 1 of the secondary proxy server is 10.13.4.119, port ID of
the secondary proxy server is 5060, home domain name is sip.huawei.com, and profile index is
1. To configure such attributes of SIP interface 0, do as follows:
huawei(config)#interface sip 0
huawei(config-if-sip-0)#if-sip attribute basic media-ip 10.13.4.116 signal-ip 10
.13.4.117 signal-port 5000 transfer udp primary-proxy-ip1 10.13.4.118 primary-pr
Issue 02 (2013-10-08)

338

Configuration Guide
oxy-port 5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.13.4.119

secondary-proxy-port 5060
huawei(config-if-sip-0)#if-sip attribute basic home-domain sip.huawei.com
sipprofile-index 1
huawei(config-if-sip-0)#reset
Are you sure to reset the SIP interface?(y/n)[n]:y
huawei(config-if-sip-0)#
Resetting SIP interface 0 succeeded
huawei(config-if-sip-0)#display if-sip attribute running
-----------------------------------------------------------MGID
0
Signalling IP
10.13.4.117
Signalling Port
5000
Media IP
10.13.4.116
Transfer Mode
UDP
Primary Proxy IP 1
10.13.4.118
Primary Proxy IP 2
Primary Proxy Port
5060
Secondary Proxy IP 1
10.13.4.119
Secondary Proxy Port
5060
Proxy Address Mode
IP
SIPProfile Index
1:Default
Service logic Index
0:Default
Server Address DHCP Option
0:None
Primary Proxy Domain Name
proxy.domain
Secondary Proxy Domain Name
Home Domain Name
sip.huawei.com
Description
MG Domain Name
Phone Context
Register URI
Conference Factory URI
Primary Proxy State
up
Secondary Proxy State
up
Current Proxy
Subscribe to UA-Profile
enable
Subscribe to REG-STATE
disable
Subscribe to MWI
disable
SDP negotiation mode
remote
Mode of supporting proxy dual-homing dualhome
Proxy detection mode
probe
Issue 02 (2013-10-08)

339

Configuration Guide
Proxy refresh mode

immediate
------------------------------------------------------------
(Optional) Configuring the Software Parameters of the SIP Interface

The software parameters of a SIP interface mainly define certain common service attributes of
the SIP interface. After the software parameter configuration, the parameters take effect
immediately and are valid only to the SIP interface. Skip this topic if the system default
Prerequisites
see Adding an SIP Interface.
Context
The details about the software parameters that can be configured of a SIP interface that supports
SIP, see section Usage Guidelines in mg-software parameter. The other parameters are
Table 6-12 Software parameters usually configured of a SIP interface
Parameter
Description
Default Setting
Indicates whether the

standalone mode is supported.

l 0: indicates that the
standalone function is not
supported.
standalone function is
supported.
Default: 0
1.
Indicates whether the heartbeat

message of the MG is disabled.

l 0: the heartbeat message of
the MG is disabled
the MG is enabled
Default value: 0.
Issue 02 (2013-10-08)

340

Configuration Guide
Procedure
Step 1 Enter the SIP interface mode.
In global config mode, run the interface sip command to enter the SIP interface mode.
----End
Example
To configure software parameter 2 of the SIP interface 0 to 1 so that the SIP interface supports
standalone, do as follows:
huawei(config-if-sip-0)#mg-software parameter 2 1
huawei(config-if-sip-0)#display mg-software parameter 2
------------------------------------------------MGID:0
para index:2
value:1
------------------------------------------------APPENDIX:
------------------------------------------------Parameter Index: Interface software parameter name:
2 : SAL Support
0: No
1: Yes
(Optional) Configuring the Ringing Mode of the SIP Interface

The ringing mode includes the initial ringing mode and cadence ringing mode. This topic
describes how to configure the ringing mode of the SIP interface to support the break-make
ratios of various new ringing modes and make the ringing mode meet the local standards.
Prerequisites
The SIP interface must be added successfully.
Context
l
Multiple initial ringing modes and cadence ringing modes have been embedded in the
system. You can refer to the usage guide of the ringmode add command to confirm whether
the system-defined ringing modes meet the user requirements.
If the system-defined ringing modes cannot meet the user requirements, you can use the
user-defined ringing mode.
You can configure the cadence duration for the user-defined ringing to form different
ringing modes.
The user-defined ringing modes are 0-15, which correspond to the cadence ringing modes
128-143 and initial ringing modes 144-159 defined by the user. For example, if the user-
Issue 02 (2013-10-08)

341

Configuration Guide
defined cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the userdefined initial ringing mode is 144, user-defined ringing mode 0 is selected.
l
The system supports a maximum of 16 records of the ringing mode mapping.
The ringing mapping name must be unique on the same SIP interface.
An index can be used for adding only one ringing mode on the same SIP interface.
The 16 user-defined ringing modes can be modified but cannot be added.
Precaution
Procedure
Step 1 (Optional) In the global config mode, run the user defined-ring modify command to configure
the user-defined ringing mode.
NOTE
l Perform this step only when the system-defined ringing modes do not meet the user requirements, and
you can define the ringing types numbered 0-15.
l After configuring the user-defined ringing mode, you need to reset the corresponding service board to
make the configuration data take effect, so that the user of the service board can use the new userdefined ringing mode. If the service board has been in service for a period, evaluate the impact on the
online users before resetting the service board, and then determine whether to perform this operation.
After the user-defined ringing mode is configured, run the display user defined-ring command
to query the user-defined ringing mode.
Step 2 Run the interface sip command to enter the SIP mode.
Step 3 Run the ringmode add command to add the ringing mapping.
Run this command to configure the ringing mode for the users on the same SIP interface. The
key parameters are described as follows:
l cadencering: Indicates the cadence ringing mode. The range 128-143 of this parameter
corresponds to user-defined ringing modes 0-15.
l initialring: Indicates the initial ringing mode. The range 144-159 of this parameter
Step 4 Run the display ringmode command to query ringing mapping records.
----End
Example
Assume that:
l
Index of the ringing mode mapping record: 1
Name of the ringing mode mapping record: alert-group
Cadence ringing mode: special ringing; break-make ratio: 1:2 (the corresponding parameter
value is 1.)
Initial ringing mode: normal ringing (FSK); break-make ratio: 1:4 (the corresponding
parameter value is 4.)
To add such a ringing mode mapping record on SIP interface 0, do as follows:

Issue 02 (2013-10-08)

342

Configuration Guide
huawei(config-if-sip-0)#ringmode add 1 alter-group cadencering 1 initialring 4
huawei(config-if-sip-0)#display ringmode 1
----------------------------------------------------------------MGID: 0
Index: 1
Ringmode-name: alter-group
CadenceRing: 1: Special Ring 1:2
InitialRing: 4: Normal Ring (FSK) 1:4
-----------------------------------------------------------------
6.2.2 Configuring the VoIP PSTN User

After an SIP interface is configured, you can add public switched telephone network (PSTN)
users on the SIP interface to implement the VoIP service.
Configuring the PSTN User Data

This topic describes how to configure the PSTN user data (the same as the corresponding data
on the IMS) on the SIP interface so that the POTS terminal can access the network to implement
the VoIP service.
Prerequisites
The POTS service board can be detected and is working properly.
Context
Table 6-13 lists the default settings of the attributes of the PSTN user. When configuring the
attributes of the PSTN user, you need to modify them according to the service requirements.
Table 6-13 Default settings of the attributes of the PSTN user
Issue 02 (2013-10-08)
Parameter
Default Setting
Priority
cat3
PotsLineType
DEL
Sequence of sending the phone

Ringing and then sending the phone number
Format of the phone number of the

calling party
SDMF(FSK)
Power-off interval
100ms
FSK delay interval
800ms

automatic gain
Disable

noise suppression
Disable
Target value of VQE automatic gain
-22 dBm0

343

Configuration Guide
Parameter
Default Setting
Target value of VQE noise

suppression
12 dB
Input gain of the DSP chip
0 dB
Output gain of the DSP chip
0 dB
Name of the DSP parameter profile
- (Indicates that the DSP parameter profile is not

configured.)
Whether to support the detection of

the ANSbar signal through
monophony
Not support
Whether to support the bell ANS

signal
Not support
Display mode of the FSK phone

BELL_202
TAS CID mode
NO-TAS
Force send FSK enable flag
disable
Procedure
Step 1 Add a PSTN user.
1.
In global config mode, run the esl user command to enter the ESL user mode.
2.
Run the sippstnuser add or sippstnuser batadd command to add a PSTN user or add
PSTN users in batches.
CAUTION
When adding a user, you can configure the phone number (parameter telno). When the
public ID is generated by phone number, you must enter the phone number. It is
recommended that you configure this phone number to be the same as the phone number
configured on the IMS. In addition, ensure that the phone number is unique on the AG.
3.
Run the display sippstnuser command to check whether the PSTN user data is the same
as the planned data.
Step 2 (Optional) Configure the attributes of a PSTN user.

The attributes of a PSTN user need to be configured when the default settings are inconsistent
with the actual application.
1.
Issue 02 (2013-10-08)
Run the sippstnuser attribute set or sippstnuser attribute batset command to configure
the attributes of a PSTN user.
344

Configuration Guide
2.
Run the display sippstnuser attribute command to check whether the attributes of the
PSTN user are the same as the planned data.
----End
Example
Assume that the phone numbers of 16 PSTN users are 83120000-83120015 and the default
values are used for other attributes. To add the 16 PSTN users in slot 0/3 on SIP interface 0 in
batches, do as follows:
huawei(config-esl-user)#sippstnuser batadd 0/3/0 0/3/15 0 telno 83120000 step 1
huawei(config-esl-user)#display sippstnuser 0/3
--------------------------------------F /S /P
MGID
TelNo
--------------------------------------0 /3 /0
0
83120000
......
0 /3 /14
0
83120014
0 /3 /15
0
83120015
---------------------------------------
(Optional) Configuring the Centrex

Centrex refers to a virtual user group. The MA5616 supports the following functions: Members
in a centrex can call each other by dialing short numbers, and members in a centrex can call the
members outside of the centrex by dialing centrex prefix + the complete phone number.
Generally, a softswitch issues centrex parameters. If a softswitch does not issue centrex
parameters, use the parameters preset on the MA5616. These parameter values must be the same
as these on the softswitch.
Context
l
Centrex prefix: When attempting to call a user in another centrex group, a user must dial
the centrex prefix before dialing the called number. A centrex prefix contains 0 to 9 digits.
The function that the members in a centrex can call each other by dialing short numbers
need not be configured on the MA5616 through the command line interface (CLI).
The function that the members in a centrex can call the members outside of the centrex by
dialing centrex prefix + the complete phone number can be supported only when the SIP
protocol is used.
The centrex attribute of a centrex can be direct centrex or two-stage centrex. The similarity
and difference are as follows:
Similarity: When the members in a centrex need to call the members outside of the
centrex, they must dial the centrex prefix.
Difference: If the centrex attribute is set to two-stage centrex, the members in a centrex
can hear the dial tone again after dialing the centrex prefix. If the centrex attribute is set
to direct centrex, no out-group dial tone is played.
Procedure
Step 1 Configure the centrex call function for a centrex group.
The MA5616 supports the configuration of the centrex prefix through one of two methods. In
method 1, configure the centrex prefix and centrex attributes for a single user in ESL user mode.
Issue 02 (2013-10-08)

345

Configuration Guide
In method 2, configure the centrex prefix and centrex attributes for all the users in global config
mode. When both methods are used, method 1 takes effect.
l
Use method 1:
1.
In ESL user mode, run the sippstnuser servicedata parameter set command to configure
the centrex prefix and centrex attributes of a centrex group.
2.
Run the display sippstnuser servicedata command to check whether the centrex parameter
settings of a centrex are the same as the data plan.
Use method 2:
NOTE
If method 2 is used, the MA5616 uses the centrex digitmap to match the centrex prefix, and uses the
call digitmap, or the normal digitmap, to match the phone number dialed by a user.
1.
In global config mode, run the local-digitmap add command to configure a direct centrex
digitmap or a two-stage centrex digitmap.
NOTE
l The system does not support the adding of a direct centrex digitmap and a two-stage centrex
digitmap at the same time. Add a digitmap based on site requirements.
l When you add a direct centrex digitmap, the system centrex attribute is direct centrex. When you
add a two-stage centrex digitmap, the system centrex attribute is two-stage centrex.
2.
Run the display local-digitmap command to check whether the local digitmap is the same
as the data plan.
Step 2 Check whether the value of the sipprofile control point 148 is the same as the data plan.
Run the display sipprofile syspara detail command to check whether the value of control point
148 is the same as the data plan. If they are different, run the sipprofile modify command in
SIP mode to change the control point value.
NOTE
l The sipprofile control point 148 can be set to 0 or 1. When it is set to 0, a phone number does not
contain a centrex prefix; when it is set to 1, a phone number contain a centrex prefix. By default, it is
1.
l Run the if-sip attribute basic sipprofile-index 0 command to specify a user-defined profile for the
current SIP interface, and run the sipprofile modify command to change the value for the sipprofile
control point 148.
----End
Example
Assume that the centrex prefix of the 0/3/0 user with phone number 88627792 is 8100, the
centrex attribute is two-stage centrex, and the control point of the Sipprofile uses the default
value.
To configure the centrex call function for such a user by using method 1, do as follows:
huawei(config-esl-user)#sippstnuser servicedata parameter set 0/3/0 telno 88627792
centrexprefix 8100 centrexflag dialsecondary
huawei(config-esl-user)#display sippstnuser servicedata 0/3/0 telno 88627792
---------------------------------------F /S /P
: 0/3/0
telno
: 88627792
centrexno
: -
Issue 02 (2013-10-08)

346

Configuration Guide
centrexprefix
: 8100
centrexflag
: dialsecondary
mwimode
: deferred
hottime(s)
: 100
hotlinenum
: dialtone
: normal
cfbnum
: cfnrnum
: cfunum
: cfnrtime(s)
: 100
displayname
: permanent-hold-mode
: norecall
permanent-hold-time(s) : 20
---------------------------------------------------
To configure the centrex call function for such a user by using method 2, and plan the digitmap
body to (8100) and the digitmap name to huawei1 for the two-stage centrex digitmap according
to the centrex prefix, do as follows:
huawei(config)#local-digitmap add huawei1 second-centrex (8100)
-----------------------------------------Name: DefaultNormalDmm
Type: normal
Body: x.S
Protocol: sip
-----------------------------------------Name: DefaultSccDmm
Type: scc
Body: ([EF]X[0-9E].F|[EF]X[0-9E].S|[EF][EF]X[0-9E].F|[EF][EF]X[0-9E].S)
Protocol: sip
-----------------------------------------Name: DefaultEmergencyDmm
Type: emergency
Body: (11X|91X)
Protocol: sip
-----------------------------------------Name: huawei1
Type: second-centrex
Body: (8100)
Protocol: sip
------------------------------------------

Context
Issue 02 (2013-10-08)
Parameter
Description
Default Setting

sending flag.

is sent.

347

Configuration Guide
Parameter
Description
Default Setting

flag.
0: Indicates China.

flag.


with ringing.

support flag.


device.


7-11

parameter.
12

source.
13

16
14

parameter 13.
16
15-255

parameter.
Procedure
----End
Example
do as follows:
Issue 02 (2013-10-08)

348

Configuration Guide

Parameter value: 1
-----------------------------------------------------------------------------

Context
Parameter
Description
Default Setting





limited.
locked.

offset.
Line B offset

detector tuning.

value is the common
parameter.
4, 6-255
Procedure
----End
Issue 02 (2013-10-08)

349

Configuration Guide
Example
{ <cr>|name<0,3> }:
Command:
Parameter value: 0
apply, 1:apply
Parameter value: 1
Parameter value: 0
-----------------------------------------------------------------------------
(Optional) Configuring the Local Digitmap

A local digitmap is also called a local preconfigured digitmap and is used to match telephone
numbers. When the H.248 protocol is used, the MA5616 prefers to use the digitmap sent by the
MGC to match the phone number. If the MGC does not send the detailed digitmap, the
MA5616 uses the local digitmap to match the phone number. When the SIP protocol is used,
the MA5616 has to use the local digitmap to match the phone number because the IMS network
does not send the digitmap. When configuring services on the MA5616, configure a proper local
digitmap according to the local standards.
Context
l
The MA5616 supports a maximum of eight local digitmaps.
For the meaning of each character in the digitmap body, see the Context in (Optional)
Configuring the Digitmap of an MG Interface.
When the H.248 protocol is used, the type of the local digitmap can only be normal.
When the SIP protocol is used, the type of the local digitmap can be normal, emergency,
scc, direct-centrex, or second-centrex. For the meaning of the digitmap type, see the
Parameter Description in the local-digitmap add command.
Precaution
Issue 02 (2013-10-08)

350

Configuration Guide
Procedure
Step 1 Query the current protocol type.
In privilege mode, run the display protocol support command to query the current protocol
type used on the MA5616.
Step 2 Add a local digitmap according to the data plan.
Run the local-digitmap add command to add a local digitmap according to the data plan.
Step 3 Check whether the local digitmap is the same as the data plan.
Run the display local-digitmap command to check whether the local digitmap is the same as
the data plan.
Step 4 (Optional) Modify the local digitmap.
Run the local-digitmap modify command to modify the name, type, or body of the local
digitmap.
Step 5 (Optional) Add or modify the digitmap body.
Run the local-digitmap append command to add or modify the digitmap body in a configured
local digitmap.
----End
Example
Assume that the H.248 protocol is used on the MA5616. To add a local digitmap with the data
listed in Table 6-16, do as follows:
Digitmap Name
Digitmap Type
Digitmap Body
huawei
normal
([2-8]xxxxxxx|[2-8]
0xxxxxxxxx|9xxxx|1
[0124-9]x|F|x.F|[0-9].S)
huawei(config)#local-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13

xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S) h248
-----------------------------------------Name: huawei
x.F|[0-9].S)
Protocol: h248
------------------------------------------
Assume that the SIP protocol is used on the MA5616. The local digitmap exists in the system.
Table 6-17 lists the data of the local digitmap.
Issue 02 (2013-10-08)

351

Configuration Guide
Table 6-17 Local digitmap existing in the system

Digitmap Name
Digitmap Type
Digitmap Body
huawei
normal
([2-8]xxxxxxx|[2-8]
0xxxxxxxxx|9xxxx|1
[0124-9]x|F|x.F|[0-9].S)
When an existing local digitmap is different from the data plan, you need to modify the local
digitmap. To change the name of the local digitmap to huawei0, add digitmap body
15xxxxxxxxx, and add a local best-effort digitmap according to data plan listed in Table 6-18
so that when an MG interface becomes faulty, other users on the MG can use the digitmap, do
as follows:
Digitmap Name
Digitmap Type
Digitmap Body
huawei1
emergency
(0E)

-----------------------------------------Name: huawei
x.F|[0-9].S)
-----------------------------------------huawei(config)#local-digitmap modify huawei name huawei0
huawei(config)#local-digitmap append huawei0 15xxxxxxxxx
huawei(config)#local-digitmap add huawei1 emergency (11X|91X|0E) sip
-----------------------------------------Name: huawei0
Type: normal
x.F|[0-9].S|15xxxxxxxxx)
Protocol: sip
-----------------------------------------Name: huawei1
Type: emergency
Body: (11X|91X|0E)
Protocol: sip
------------------------------------------
(Optional) Configuring the Attributes of a PSTN Port

This topic describes how to configure the attributes of a PSTN port to ensure that the PSTN port
can meet the actual application requirements. The attributes include polarity-reversing pulse,
impedance, and KC accounting.
Context
The MA5616 supports the following attributes of a PSTN port:
Issue 02 (2013-10-08)

352

Configuration Guide
Physical attributes (including whether to support the polarity reversal pulse, whether to
support the port locking, and dialing mode). For details about how to configure the physical
attributes of a PSTN port, see the command pstnport attribute set.
Electrical attributes (including the impedance and the current). For details about how to
configure the electrical attributes of a PSTN port, see the command pstnport electric
set.
KC attributes (including the KC charging mode and the valid voltage). For details about
how to configure the KC attributes of a PSTN port, see the command pstnport kc set.
Procedure
Step 1 Enter the PSTN port mode.
In global config mode, run the pstnport command to enter the PSTN port mode.
Step 2 Configure the physical attributes of a PSTN port.
l Run the pstnport attribute set command to configure the physical attributes of a single
PSTN port.
l Run the pstnport attribute batset command to configure the physical attributes of PSTN
ports in batches.
Step 3 Configure the electrical attributes of the PSTN port.
l Run the pstnport electric set command to configure the electrical attributes of a single PSTN
port.
l Run the pstnport electric batset command to configure the electrical attributes of PSTN
ports in batches.
Step 4 Configure the KC attributes of the PSTN port.
l Run the pstnport kc set command to configure the KC attributes of a single PSTN port.
l Run the pstnport kc batset command to configure the KC attributes of PSTN ports in
batches.
Step 5 Check whether the attribute configuration of the PSTN port is the same as the planned data.
l
Run the display pstnport attribute command to query the physical attributes of the PSTN
port.
Run the display pstnport electric command to query the electrical attributes of the PSTN
port.
Run the display pstnport kc command to query the KC attributes of the PSTN port.
----End
Example
To configure PSTN ports 0-15 on the board in slot 0/3 to support the polarity reversal charging,
do as follows:
enable
Issue 02 (2013-10-08)

353

Configuration Guide
NOTE
When a call starts and ends, the MG shows the start time and the end time based on the polarity reversal
on the subscriber line. The billing terminal that supports the polarity reversal charging function, such as a
charging phone set, implements the polarity reversal charging function based on the start time and the end
time of a call.
(Optional) Configuring the Attributes of the Ringing Current

You can adjust the ringing volume and ringing tone by modifying the attributes of the ringing
current. Generally, the attributes of the ringing current need not be modified. You need to modify
the attributes of the ringing current according to the local standards only when the default ringing
current attributes do not meet the local standards.
Context
The attributes of the ringing current include the following two parameters:
l
Ringing current frequency: The higher the frequency is, the sharper the ringing tones are.
AC voltage amplitude: The greater the amplitude is, the louder the ringing tones are.
Procedure
Step 1 Enter the VoIP mode.
In global config mode, run the voip command to enter the VoIP mode.
Step 2 Configure the attributes of the ringing current.
Run the ring attribute set command to configure the attributes of the ringing current according
to the data plan.
Step 3 Check whether the attributes of the ringing current are the same as the data plan.
Run the display ring attribute command to check whether the attributes of the ringing current
are the same as the data plan.
----End
Example
To set the ringing current frequency to 16 Hz (parameter value 0) and AC amplitude to 50 Vrms
(parameter value 2), do as follows:
huawei(config)#voip
huawei(config-voip)#ring attribute set frequency 0 acamplitude 2
huawei(config-voip)#display ring attribute
ringing current frequency : 16Hz
ringing current acamplitute: 50Vrms
6.3 Configuring the VoIP ISDN BRA Service (Based on the

H.248 Protocol)
This topic describes how to configure the VoIP ISDN BRA service on an IP network. When the
MA5616 uses the H.248 protocol, the device supports the access of the ISDN BRA user. ISDN
Issue 02 (2013-10-08)

354

Configuration Guide
technology provides end-to-end (E2E) digital connection and supports multiple types of voice
and non-voice telecom services.
Prerequisites
According to the actual network, a route from the MA5616 to the MGC must be configured to
ensure that the MA5616 communicates with the MGC normally.
Context
l
The ISDN is integrated services digital network. Defined by the International Telegraph
and Telephone Consultative Committee (CCITT), the ISDN technology provides two types
of user-network interfaces based on the user-network interface reference model.
ISDN basic rate interface (BRI), which supports a rate of 144 kbit/s and provides two
B channels (for carrying services) and one D channel (for transmitting call control
signaling and maintenance and management signaling). The rate of B channels is 64
kbit/s and the rate of D channel is 16 kbit/s. The service carried on the ISDN BRI is the
ISDN basic rate access (BRA) service.
ISDN primary rate interface (PRI), which supports a rate of 2.048 Mbit/s and provides
30 B channels and one D channel. The rates of the B channel and D channel are both
64 kbit/s. The service carried on the ISDN PRI is the ISDN primary rate access (PRA)
service.
The MA5616 supports only the VoIP ISDN BRA service.
The MA5616 provides the ISDN BRA service through the DSL port on the DSLD board.
For detailed description of the DSLD board, see DSLD - Eight-Channel ISDN Service
Board in the Hardware Description.
Precaution
The media gateway control protocol (MGCP) is a master/slave protocol. under which the MGC
controls the AG to implement call connection and disconnection. The data on the AG for the
interconnection with the MGC, such as the attributes of the MG interface and the attributes of
the VoIP user, must be the same as the corresponding data on the MGC. Therefore, before
configuring the VoIP service, you must contact MGC engineers to check and ensure that the
interconnection data plan for the AG is consistent with the corresponding plan for the MGC.
Data preparation
Table 6-19 provides the data plan for configuring the H.248-based VoIP ISDN BRA service.
Table 6-19 Data plan for configuring the H.248-based VoIP ISDN BRA service
Item
Remarks
MG interface data
(The data must be
consistent with the
data on the MGC.)
Issue 02 (2013-10-08)
Parameters of
the media
stream and
signaling
stream
Upstream
VLAN for
media and
signaling
streams

It is used as the upstream VLAN

of the VoIP service to be
configured. Standard VLAN is
recommended.
355

Configuration Guide
Item
Remarks
Attribute
parameters of
the MG
interface
Uplink port for

media and
signaling
streams
It is used as the uplink port for the

Media IP
address and
signaling IP
address
These IP addresses must be

contained in the media and
signaling IP address pools. The
media and signaling IP address
pools consist of all the IP
addresses of the L3 interface of
the upstream VLAN for media
and signaling streams.
Default IP
address of the
MG
It is the next hop IP address from

the MA5616 to the MGC.
MG interface
ID
It is the ID of the MG interface

used by the VoIP service to be
configured. The MA5616
supports four VAGs.
Signaling port
ID of the MG
interface
It is the transport layer protocol

port ID used for the signaling
exchange between the MA5616
(AG) and the MGC.
NOTE
There are
many MG
interface
parameters.
Only
mandatory
parameters
are listed here.
If the
mandatory
parameters
are not
configured,
the MG
interface
cannot be
started.
The default signaling port ID

defined in H.248 is 2944 (text)
and 2945 (binary).
Issue 02 (2013-10-08)

356

Configuration Guide
Item
Remarks
IP address of
the MGC to
which the MG
interface
belongs
The MGC can be specified by IP

address or the domain name. The
IP address is adopted here.
When dual homing is not

configured, you can configure the
parameters of only the primary
Port ID of the
MGC. When dual homing is
MGC to which
configured, you also need to
the MG
configure the IP address and port
interface
ID of the secondary MGC.
belongs
Domain name
of the MGC to
which the MG
interface
belongs
Coding mode
of the MG
interface
Only the text mode is supported.
Transmission
mode of the
MG interface
The transmission mode is

selected according to the
requirements of the MGC.
Generally, UDP is used.
Domain name
of the MG
interface
It corresponds to the
domainName parameter of the
MG interface.
When the H.248 protocol is used,
this parameter must be
configured if the MIDType
parameter of the H.248 message
is configured to domainName.
Otherwise, the MG interface
cannot be started. In other
situations, this parameter is
optional.
Issue 02 (2013-10-08)

357

Configuration Guide
Item
Remarks
Device name
of the MG
interface
It is supported by only the H.248

protocol, and it corresponds to the
deviceName parameter of the
MG interface that uses the H.248
protocol.
This parameter must be
configured if the MIDType
parameter of the H.248 message
is configured to domainName.
Otherwise, the MG interface
cannot be started. In other
situations, this parameter is
optional.
IUA link
Digitmap of the MG interface
The digitmaps are used for certain

special applications such as
emergency calls and emergency
standalone. The digitmaps for
common phone services are
issued to the AG by the MGC, and
therefore such digitmaps need not
be configured on the AG. If the
services such as emergency calls
and emergency standalone are
not required, this parameter need
not be configured.
Software parameters of the

MG interface
Whether the MG interface

supports the functions such as
dual homing and emergency
standalone is determined by the
service requirements.
Ringing mode of the MG

interface
Which ringing mode is used by

the MG interface is determined
by the service requirements.
Terminal ID (TID) format of

the MG interface
The TID format determines the

generation mode of various types
of user terminals on an MG
interface.
IUA link set
The IUA link can be configured

only after the IUA link set is
configured.
IUA link
Issue 02 (2013-10-08)
IUA link ID
It indicates the link for

transmitting the signaling.
IUA link set ID

358

Configuration Guide
Item
Remarks
NOTE
The local port
ID, local IP
address,
remote port
ID, and
remote IP
address of
different links
must not be
completely
same;
otherwise, the
service cannot
be
configured.
ISDN BRA user data

(The data must be
consistent with the
data on the MGC.)
Issue 02 (2013-10-08)
Local port ID
To activate the link normally, it

must be the same as the remote
port ID configured on the MGC.
Local IP
address
It must be the same as the remote

IP address of the link configured
on the MGC. In addition, the local
IP addresses of the links that are
in the same link set must be the
same. (The IP address must exist
in the media IP address pool.)
Remote port
ID
To activate the link normally, it

must be the same as the local port
ID configured on the MGC.
Remote IP
address
It must be the same as the local IP

address of the link configured on
the MGC. The SCTP protocol
supports the multi-homing
function. That is, one link can be
configured with the IP addresses
of multiple MGCs as the remote
IP addresses. When one MGC is
faulty, the link can be switched to
other MGCs automatically. This
ensures that the service is not
affected. The MA5616 supports
the configuration of the active
remote IP address and standby
remote IP address.
Slot that houses the DSLD

service board
1-4
User data
If the TID format bound to the

BRA user does not support
terminal layering function, this
parameter needs to be configured,
and the configuration must be
consistent with the configuration
on the MGC.
Termination
ID

359

Configuration Guide
Item
Remarks
User priority
The user priority must be

specified according to the service
requirements. There are three
categories of user priorities,
which are as follows:
l cat1: government1 (category
1 government user)
l cat2: government2 (category
2 government user)
l cat3: normal (common user,
default)
The priorities of cat1, cat2, and
cat3 are in descending order.
Without special requirements, the
default cat3 is adopted.
Interface ID
Issue 02 (2013-10-08)
It indicates the interface for the

BRA user data to pass through the
MG and MGC. The configuration
of this parameter must be
consistent with the corresponding
configuration on the MGC.
System parameters
The system parameters including

the oversea version flag and
message waiting indication
(MWI) mode need to be
configured according to the local
standards to ensure that the
response of the user terminal
complies with the local standards.
Overseas parameters
The attributes such as the upper

and lower thresholds of the flashhooking duration need to be
configured according to the local
standards to ensure that the
response of the user terminal
Attributes of an ISDN BRA

Port
The attributes such as the

working mode, remote power
supply status, and autodeactivation status of the port can
be configured. Modify such
attributes only if there is a special
requirement.

360

Configuration Guide
6.3.1 Configuring an MG Interface

A media gateway (MG) interface is important to H.248-based voice over IP (VoIP) services, as
it enables communication between the MA5616 access gateway (AG) and the media gateway
controller (MGC). Therefore, configure an MG interface and ensure that it is working properly
before implementing H.248-based VoIP services. This topic describes how to configure an MG
interface.
Context
l
A virtual access gateway (VAG) simulates one physical AG into multiple logic AGs.
Multiple logic AGs can be connected to various user groups, providing different
convergence rates for these groups to meet differentiated service requirements. To
configure a VAG, configure a VAG interface (or an MG interface), enter VAG interface
mode, and set interface parameters using the command line interface (CLI).
Each MG interface supports independent signaling and media IP addresses, and signaling
and media IP addresses can be configured in different virtual local area networks (VLANs).
The MA5616 communicates with the MGC using the MG control protocol, or the H.248
protocol.
One MA5616 supports a maximum of four MG interfaces. The MG interfaces support

authentication and ring mapping settings.

Context
Procedure
1.
2.
Issue 02 (2013-10-08)

361

Configuration Guide
----End
Example

Prerequisites
VLAN Interface.
Context
l
Procedure
Issue 02 (2013-10-08)

362

Configuration Guide

1.
pool.
2.

1.
address pool.
2.
----End
Example
huawei(config)#voip
Media:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
Signaling:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Adding an MG Interface
This topic describes how to add a media gateway (MG) interface and configure its attributes.
An MG interface enables communication between an MA5616 and a media gateway controller
(MGC).
Issue 02 (2013-10-08)

363

Configuration Guide
Prerequisites
The media and signaling IP address pools have been configured. For details about how to
configure the address pools, see Configuring the Upstream VLAN Interface.
Context
Each MA5616 supports a maximum of four MG interfaces.
Procedure
Run the interface h248 command to add an MG interface that supports the H.248 protocol.
Step 2 Configure the MG interface attributes.
Run the if-h248 attribute command to configure MG interface attributes according to the data
plan.
MG interface attributes include three types of parameters: MG interface identifier parameters,
identifier parameters of the MGC to which the MG interface belongs, and H.248 message
negotiation parameters. The detailed description of the parameters is as follows:
l MG interface identifier parameters include domainName, deviceName, and mgip. mgip
includes the signaling and media IP addresses. You can reset an MG interface only after
setting mgip.
l Identifier parameters of the MGC to which the MG interface belongs include mgc-ip and
mgc-domain-name. You can reset an MG interface only after setting either of the two
parameters. When multi-homing is used, set the parameters for the active and standby MGCs,
as well as the disaster tolerance MGC identifier.
l H.248 message negotiation parameters include the message coding mode, message
transmission mode, protocol port ID at the transport layer, protocol negotiation version,
profile negotiation parameter, heartbeat negotiation parameter, and transaction reliability
function. You can reset an MG interface only after setting mgport, primary-mgc-port,
code, transfer, and start-negotiate-version.
Table 6-20 lists the MG interface parameters for communication between the MG and the MGC.
Issue 02 (2013-10-08)

364

Configuration Guide
Table 6-20 MG interface parameters

Parameter
Remarks
mgip

signal-dhcp-vlan vlanid-signal: indicates
that the signaling IP address of a port is
obtained using the upstream VLAN ID of the
MG interface in Dynamic Host Configuration
Protocol (DHCP) mode. You can run the
dhcp-client enable command to configure
the IP address of the VLAN interface to be
NOTE
when MIDType is IP.
mgport
Indicates the transport layer protocol port ID

used for the signaling exchange between the
MA5616 (AG) and the MGC.
In the H.248 protocol, the protocol port ID is
related to the coding type. The default
signaling port ID defined in H.248 is 2944
(text) and 2945 (binary).
NOTE
The MG interface ID must be the same as that
specified on an MGC.
Issue 02 (2013-10-08)

365

Configuration Guide
Parameter
Remarks
mg-media-ip1

media-dhcp-vlan vlanid-signal: indicates
that the media IP address of a port is obtained
using the upstream VLAN ID of the MG
interface in DHCP mode. You can run the
dhcp-client command to configure the IP
address of the VLAN interface to be
NOTE
when MIDType is IP.
primary-mgc-ip1
primary-mgc-port
When dual homing is not configured, you can

configure the parameters of only one MGC.
When dual homing is configured, configure
the IP address and port ID of the standby
MGC. You can configure data on the standby
MGC only after configuring data on the
active MGC. Otherwise, the configuration
fails.
code
The coding modes of the MG interface and

the MGC must be the same. Currently, only
text coding mode is supported.
transfer

to the requirements of the MGC. Generally,
UDP is used.
start-negotiate-version
If the signaling process flow on the MG is

different from that on the MGC, set this
parameter to 0 (negotiated with the profile).
In addition, set parameter profile-index
index. The profile used on the MG interface
must be the same as that on the MGC.
If the profile file in the system cannot meet
requirements, contact Huawei for technical
support.
Issue 02 (2013-10-08)

366

Configuration Guide
Step 3 Check whether the attribute of the MG interface is the same as that in the data plan.
Run the display if-h248 attribute command to check whether the attribute of the MG interface
----End
Example
Assume that the MG interface ID is 0, the H.248 protocol is used for interconnecting with the
MGC, the signaling IP address of the MG interface is 10.13.4.117, the transport layer protocol
port ID is 2944, IP address 1 of the primary MGC is 10.13.2.118, the transport layer protocol
port ID of the primary MGC is 2944, the media IP address is 10.13.4.116, the start version is 1,
and the transaction reliability is enabled. To add such an MG interface, do as follows:
huawei(config-if-h248-0)#if-h248 attribute mgip 10.13.4.117 mgport 2944 code tex
t transfer udp primary-mgc-ip1 10.13.2.118 primary-mgc-port 2944 mg-media-ip1 10
.13.4.116 start-negotiate-version 1 retrans enable
huawei(config-if-h248-0)#display if-h248 attribute
------------------------------------------------MGID
0
MG Description
MG DomainName
Protocol
H248
Start Negotiate Version
1
Profile Negotiation Parameter
Disable
Profile index
1:NoProfile("")
2833Encrypt
Codetype
Text
Transfer Mode
UDP
HeartBeatGenTimer(s)
60
HeartBeatRetransTimes
3
HeartBeatRetransTimer(s)
60
MG signalling IP
10.13.4.117
MG signalling Port
2944
MG media IP1
10.13.4.116
MG media IP2
MIDType
IP4_ADDR
DeviceName
Retrans
Enable
Active MGC
MGC Port
:2944
MGC
Active MGC
MGC Port
:2944
MGC
Active MGC
MGC Domain Name:Standby MGC
MGC Port
:MGC
Standby MGC
MGC Port
:MGC
Standby MGC
MGC Domain Name:-------------------------------------------------
IP1:10.13.2.118
IP2:IP1:IP2:-
(Optional) Configuring the Digitmap of an MG Interface

A digitmap is a set of digit collection descriptors. It is a dialing scheme residing in media
gateways (MGs) and is used for detecting and reporting the digit events received on a terminal.
This topic describes how to configure the digitmaps for certain special applications such as
emergency calls and emergency standalone. The digitmaps for common phone services are
issued to the AG by the MGC, and therefore such digitmaps need not be configured on the AG.
If the services such as emergency calls and emergency standalone are not required, the digitmaps
need not be configured.
Issue 02 (2013-10-08)

367

Configuration Guide
Prerequisites
Context
CAUTION
The digitmap configuration is relatively complicated. The information such as the meanings and
usage of the characters in a digitmap is defined in the protocol, and is not described here. This
topic provides only some basic information. It is recommended that you refer to the digitmap
description in ITU-T H248.1 (applicable to H.248) before configuring the digitmap.
l
A digitmap is used to improve the efficiency of the MG in sending the callee number. That
is, if the callee number matches a dialing scheme defined by the digitmap, the MG sends
the callee number collectively in a message.
A digitmap consists of strings of digits with certain meanings. When the received dialing
sequence matches one of the strings, it indicates that the digits are collected completely.
To configure the emergency standalone function, you must configure the internal digitmap.
The H.248-based MG interface supports the following types of digitmaps:

l
Internal digitmap: used for matching the telephone numbers of two internal subscribers on
an MG. The digitmap is issued by the MG and applies to the emergency standalone service.
Emergency call digitmap (due to call restriction in the case of an overload): When an MG
is overloaded or the bandwidth is insufficient, subscribers can still dial the telephone
numbers that match the digitmap, such as the police call and ambulance call, through
emergency channels. The digitmap applies to emergency calls when an MG is overloaded.
Automatic redial digitmap of card services: When a subscriber makes a call using a
telephone card, the subscriber can dial another telephone number by pressing the keys
defined in the automatic redial digitmap after the call is complete and the called party hooks
up. The digitmap applies to automatic redial services.
Table 6-21 provides the valid characters in the strings and their meanings in the H.248 protocol.
For details about the digitmap in the H.248 protocol, refer to ITU-T H248.1, which provides a
better guide to the digitmap configuration.
Table 6-21 Digitmap format in the H.248 protocol
Issue 02 (2013-10-08)
Digit or
Character
Description
0-9
Indicate dialed digits 0-9.
A-D
Indicate A-D.
Indicates * in the DTMF mode.
Indicates for # in the DTMF mode.

368

Configuration Guide
Digit or
Character
Description
Indicates for a wildcard, indicating any digit from 0 to 9.
Indicates the short timer. When detecting the timer timeout, the system reports
scheme is matched. The short timer is applied when the collected number
matches at least one dialing scheme, but more numbers may be received and
these numbers match other dialing schemes.
Indicates the long timer. When detecting the timer timeout, the system reports
scheme is matched. The long timer is applied when the dialed number does
not match any dialing scheme.
Indicates the duration modifier, which indicates a dialing event of a long

duration. It is before the event character with a fixed location. When the event
duration exceeds the threshold, the dialing event fills the location.
Indicates that there can be multiple digits (including 0) or characters before

it.
Used to separate the strings and indicates that each string is an optional dialing
scheme.
[]
Indicates that one digit or string can be selected from the options.
Procedure
Step 2 Configure the digitmap.
Run the digitmap set command to configure the digitmap required in the data plan.
Step 3 (Optional) Configure the digitmap timer.
Run the digitmap-timer command to configure the digitmpa timer.
Generally, the digitmap is issued by the MGC. In this case, the issued digitmap timer prevails
regardless of whether a timer is configured on the AG. When the MGC does not issue the
digitmap timer and the default digitmap timer does not meet the service requirements, you can
configure the digitmap timer in this step.
Step 4 Check whether the configuration of the digitmap timer is the same as that in the data plan.
l Run the display digitmap command to check whether the digitmap is configured correctly.
l Run the display digitmap-timer command to check whether the digitmap timer is configured
correctly.
----End
Issue 02 (2013-10-08)

369

Configuration Guide
Example
Assume that the inner digitmap of H.248-based MG interface 0 is configured and the telephone
numbers of two internal subscribers on an MG are matched. According to the data plan, the inner
digitmap format is 1234xxxx. To configure the inner digitmap, do as follows:
huawei(config-if-h248-0)#digitmap set inner 1234xxxx
---------------------------------------------------------------------Inner digitmap
: 1234xxxx
: ----------------------------------------------------------------------
(Optional) Configuring the Software Parameters of an MG Interface

The software parameters of a media gateway (MG) interface mainly define certain common
service attributes of the MG interface. After the software parameter configuration, the parameters
take effect immediately and are valid only to the MG interface. Skip this topic if the system
Prerequisites
Context
The details about the software parameters that can be configured of an MG interface that supports
H.248, see section Usage Guidelines in mg-software parameter. The other parameters are
Table 6-22 Software parameters usually configured of an MG interface that supports H.248
Parameter
Description
Default Setting

interface supports dual homing.

is not supported.
rather than auto-switching is
supported.
and auto-switching is
supported.
Default: 0
2.
Issue 02 (2013-10-08)

370

Configuration Guide
Parameter
Description
Default Setting

interface supports device
authentication.

authentication is supported.
authentication is not
supported.
Default: 1
11

interface supports emergency
standalone.

l 0: Indicates that no call is
permitted.
l 1: Indicates that only internal
call is permitted.
l 2: Indicates that only
emergency call is permitted.
l 3: indicates that internal call
and emergency call are
permitted.
Default: 0
Procedure
----End
Example
To configure software parameter 11 of H.248-based MG interface 0 to 1 so that the MG interface
supports emergency standalone and allows only internal calls, do as follows:
------------------------------------------------Interface Id:0
------------------------------------------------APPENDIX:
-------------------------------------------------
Issue 02 (2013-10-08)

371

Configuration Guide
Interface software parameter name:

11: Stand alone support
0: None
1: Inner
2: Emergency
3: Both
The MA5616 interconnects with an MGC from another vendor. The maximum RTP terminal
ID of the MGC is 64. To configure the MA5616 with its MG interface software parameter 24
set to 64 and the maximum RTP terminal ID of MG interface 0 to 64, do as follows:
------------------------------------------------Interface Id:0
------------------------------------------------APPENDIX:
24: Max. RTP terminal ID
(Optional) Configuring the Ringing Mode of an MG Interface

This topic describes how to configure the ringing mode of an MG interface to meet different
user requirements. If the default ringing mode (the cadence ringing and initial ringing both are
1:4) meets user requirements, skip this topic.
Context
Add the ringing mode mapping records of a specified MG interface. After the adding is
successful, the MG interface can obtains the ringing mode according to the peer parameters
issued by the MGC and then play the ringing to the user in this mode.
Procedure
Step 1 Check whether the ringing mode meets the requirements.
Check whether the preset ringing mode in the system meets the requirements according to the
Usage Guidelines of the mg-ringmode add command.
l If the preset ringing mode meets the requirements, go to Step 3.
l If the preset ringing mode does not meet the requirements, proceed to Step 2.
Step 2 Configure the user-defined ringing mode.
In the global config mode, run the user defined-ring modify command to configure the breakmake ratio of user-defined ringing mode to form a ringing mode that meets the user requirement.
CAUTION
The system supports 16 user-defined ringing modes, which can be modified but cannot be added
or deleted.
Issue 02 (2013-10-08)

372

Configuration Guide

Step 4 Add a ringing mapping.
Run the mg-ringmode add command to add a ringing mapping.
CAUTION
1. The peer parameter mgcpara that is on the MG and issued by the MGC must be the same as
the parameter mgcpara on the MGC.
2. User-defined ringing modes 0 to 15 correspond to cadence ringing modes 128 to 143
respectively, and correspond to initial ringing modes 144 to 159 respectively. For example,
if the cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the initial
ringing mode is 144, user-defined ringing mode 0 is selected.
Step 5 Check whether the ringing mapping is the same as that in the data plan.
Run the display mg-ringmode attribute command to check whether the ringing mapping is the
same as that in the data plan.
----End
Example
Assume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 0, the cadence
ringing is 1:4 (the value of the corresponding parameter cadence is 0), and the initial ringing is
1:2 (the value of the corresponding parameter initialring is 17). To configure the ringing mode
of MG interface 0, do as follows:
{ <cr>|mgcpara<0,15> }:
Command:
------------------------------------------------------MGID
PeerPara
CadenceRing
InitialRing
------------------------------------------------------0
0
0
17
-------------------------------------------------------
Assume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 1, the breakmake ratio of user-defined ringing mode 0 is 0.4sec On, 0.2sec Off, 0.4sec On, 2.0sec Off, and
the initial ringing and the cadence ringing use user-defined ringing mode 0 (the values of the
corresponding parameters cadence and initialring are 128 and 144 respectively). To configure
the ringing mode of MG interface 0, do as follows:
huawei(config)#user defined-ring modify 0 para1 400 para2 200 para3 400 para4 2000
huawei(config)#display user defined-ring
{ <cr>|ring-type<0,15> }:
Command:
display user defined-ring
-------------------------------------------------RingType Para1 Para2 Para3 Para4 Para5 Para6
--------------------------------------------------
Issue 02 (2013-10-08)

373

Configuration Guide
0
400
200
400
2000
0
0
1
0
0
0
0
0
0
2
0
0
0
0
0
0
3
0
0
0
0
0
0
......
14
0
0
0
0
0
0
15
0
0
0
0
0
0
-------------------------------------------------huawei(config)#interface h248 0
{ <cr>|mgcpara<0,15> }:
Command:
------------------------------------------------------MGID
PeerPara
CadenceRing
InitialRing
------------------------------------------------------0
1
128
144
-------------------------------------------------------
(Optional) Configuring the TID Format of an MG Interface

A terminal ID (TID) profile determines how various user terminal IDs on a media gateway (MG)
interface are generated. If the default TID profile in the system meets user requirements, skip
this topic.
Context
CAUTION
The configuration of the TID format is relatively complicated. The information such as the syntax
rules with which the terminal prefix must comply and the requirements for the character string
of the TID template is defined in the protocol, and is not described here. This topic describes
only some basic information. It is recommended that you refer to the TID description in ITU-T
H248.1 before configuring the TID format.
The TID format consists of the terminal prefix and the TID template. The TID template defines
the generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefix
and a character string generated by a TID template.
Terminal layering: indicates that a terminal user is identified by layered parameters, such as
subrack ID/slot ID/port (B channel) ID. Based on standards in different countries, you can
determine whether configure the feature for a user.
The TID templates that are bound to various types of users on the MG interface determine
whether the users support terminal layering.
l
If the parameter list of the TID template includes only keyword "G", it indicates that the
TID template is used by the non-layering users. Users bound with this template do not
If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" is
not available to PSTN users), it indicates that the TID template is used by the layering users.
Users bound with this template support terminal layering.
Issue 02 (2013-10-08)

374

Configuration Guide
NOTE
The meaning of each keyword is as follows:

l
F indicates the shelf ID.
S indicates the slot ID.
P indicates the port ID.
B indicates the B channel ID (only for ISDN BRA and ISDN PRA terminals).
G indicates the general permanent termination index.
R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, which
exists only when the system protocol is H.248. This termination is not involved unless special remarks
are provided.)
Procedure
Step 1 To query the template information.
Run the display tid-template command to query the information about the default TID profile
of the system.
The system defines 19 default TID profiles with IDs from 0 to 18. These profiles can only be
referenced, but cannot be added, modified, or deleted.
Step 2 Check whether the default TID template of the system meets the service requirements.
If the default 19 TID profiles cannot meet service requirements, run the tid-template add
command to add a TID profile. Otherwise, proceed to Step 3.
Step 4 Configure the TID templates and the terminal prefix of various types of users on the current MG
(VAG).
l In H248 mode, run the tid-format rtp command to configure the TID template and terminal
prefix of the RTP ephemeral termination.
l In H248 mode, run the tid-format pstn command to configure the TID template and terminal
prefix of the PSTN user.
l In H248 mode, run the tid-format bra command to configure the TID template and the
terminal prefix of the ISDN BRA user.
NOTE
l If certain type of terminal exists on an interface and the interface is not disabled, the terminal prefix of
this type of terminal cannot be modified.
l If a certain type of terminal exists on an interface, the TID format (including the terminal prefix and
the index of the TID profile) of this type of terminal cannot be modified.
l The terminal prefix must comply with the following syntax rules: The prefix supports a maximum of
64 characters and supports letters, digits, underscore (_), and slash (/); the first character must be a
letter, and the last character cannot be a digit.
l The length of the TID, which is generated by combining the configured TID profile and the terminal
prefix, cannot exceed 64 characters.
Step 5 Check whether the TID template and the terminal prefix are the same as those in the data plan.
Issue 02 (2013-10-08)

375

Configuration Guide
Run the display tid-format command to check whether the TID profiles and the terminal
prefixes of various types of users on the current MG interface are the same as those in the data
plan.
The configuration of terminal layering on the MG must be the same as that on the MGC.
l Run the display tid-format command to query the TID formats of various types of users on
the current MG interface. In the query result, template-index indicates the index of the TID
profile that is bound to the type of user. Then run the display tid-template command to
check whether the TID template supports the layering configuration. You can learn about
whether the user supports terminal layering.
l When adding a user that supports terminal layering, you do not need to specify parameter
terminalid because the system automatically allocates a terminal ID. When adding a user
that does not support terminal layering, you must specify parameter terminalid.
----End
Example
Assume that in the H.248 mode, the terminal prefix of the PSTN user on MG interface 1 is aln/,
and the layering TID template 3 is used. To add a PSTN user on port 0/3/0 and check whether
the system automatically allocates a TID generated according to the template, do as follows:
huawei(config)#display tid-template 3// Query the information about the TID
template 3.
------------------------------------------------Index
: 3
Format
: %u/%u/%u
Para-list : F+1,S+1,P+1 // Keywords in the parameter list of the TID template
are "F", "S", and "P".
Name
: Aln_Not_Fixed_1
------------------------------------------------huawei(config)#interface h248 1
huawei(config-if-h248-1)#tid-format pstn prefix aln/ template 3
huawei(config-esl-user)#mgpstnuser add 0/3/0 1
huawei(config-esl-user)#display mgpstnuser 0/3/0
{ <cr>|endframeid/slotid/portid<S><Length
1-15> }:
Command:
display mgpstnuser 0/3/0
---------------------------------------------------------------------------F /S /P
MGID
TelNo
TerminalID
---------------------------------------------------------------------------0 /3/0
1
Cat3
DEL
aln/1/3/1
----------------------------------------------------------------------------
The MA5616 interconnects with an MGC from another vendor. TID profiles pstn (index: 32)
and Z-RTP (index: 33) are added on the MA5616. The parameter list of profile pstn is G and
the character string display format is %02u. The parameter list of profile Z-RTP is R and the
character string display format is %05u.
To configure the terminal prefix to RTP/ and TID profile 33 for RTP users connected to MG
interface 1, and configure the terminal prefix to AG589 and TID profile 32 for PSTN users, do
as follows:
huawei(config)#tid-template add 32 format %02u parameter-list G name pstn
huawei(config)#tid-template add 33 format %05u parameter-list R name Z-RTP
Issue 02 (2013-10-08)

376

Configuration Guide
huawei(config-if-h248-1)#tid-format rtp prefix RTP/ template 33 pstn prefix AG589

template 32
Enabling an MG Interface
Enabling an MG interface is to reset an MG interface to make the MG interface register with
the MGC (or to make the modified attributes of the MG interface take effect) after the
configuration of the MG interface is complete, so that the MG interface can work in the normal
state.
Precaution
CAUTION
For the MG interface that has been in service, this operation interrupts the ongoing services
carried on the MG interface. Hence, exercise caution when performing this operation.
Procedure
Step 1 Enter the H248 mode.
Run the interface h248 command to enter the H248 mode.
Step 2 Enable the MG interface.
Run the reset coldstart command to enable the MG interface.
Step 3 Check the state of the MG interface.
You can query the status of the MG interface by using one of the following two methods.
l Run the display if-h248 state command to check whether the MG interface is in the normal
state.
l Run the quit command to quit the global config mode, and then run the display if-h248
all command to check whether the MG interface is in the normal state.
NOTE
The running states of an MG interface can be Local Closed, Remote Closed, Normal, Wait ack, and
Graceful Closed. For the state meanings, see parameter description of State in display if-h248 all of the
Command reference.
----End
Example
To enable H.248-based MG interface 0, do as follows:
-------------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
Issue 02 (2013-10-08)

377

Configuration Guide
-------------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.11
2944
10.10.20.11
--------------------------------------------------------------------------------
6.3.2 Configuring the IUA Link

This topic describes how to configure the IUA link for signaling transmission between the
MA5616 and MGC in the VoIP ISDN BRA service.
Context
l
Simple Control Transmission Protocol (SCTP) is a connection-oriented protocol. Its most

fundamental function is to provide reliable transmission for interaction messages between
the MA5616 and MGC. The SCTP protocol implements services based on the association
between two SCTP endpoints. SCTP can be regarded as a transmission layer. Its upper
layer is called SCTP subscriber, and its lower layer is the IP network.
The IUA link is the carrier of the interaction signaling between the MA5616 and MGC.
Adding an IUA Link Set

This topic describes how to add an IUA link set. When configuring the VoIP ISDN service, you
need to configure the IUA link to carry the Q.931 call signaling. Before adding an IUA link, you
must add a corresponding link set. Otherwise, the link cannot be added.
Context
l
The system supports the configuration of a maximum of four IUA link sets.
After a link set is configured successfully, it is in the deactivated state by default.
Procedure
Step 1 In global config mode, run the commandsigtran to enter the Sigtran mode.
Step 2 Run the iua-linkset add command to add an IUA link set.
Step 3 You can run the display iua-linkset attribute command to check whether the configured IUA
link set information is the same as the data plan.
----End
Example
Assume that the link set ID is 0, working mode of the link set is active/standby mode, pending
duration is 20s, prefix of the IID is b/, IID generation mode is using the binary value that is
automatically generated in ffsspp mode, namely, parameter 2. To add such an IUA link set, do
as follows:
huawei(config)#sigtran
huawei(config-sigtran)#iua-linkset add 0 trafficmode override pendingtime 20 iidmap 2
braprefix b/
huawei(config-sigtran)#display iua-linkset attribute
{ <cr>|linksetno<L> }:
Command:
display iua-linkset attribute
Issue 02 (2013-10-08)

378

Configuration Guide
---------------------------------------------------------LinksetNo
:0
PendingTime
:20
TrafficMode
:override
C/S-Mode
:server
IID-Type
:integer
IID-Map
:2
BRA IID-Prefix
:b/
BRA IID-Suffix
:----------------------------------------------------------
Adding an IUA Link

This topic describes how to add an IUA link. After the link set is added, you can add an IUA
link to carry the Q.931 call signaling for the ISDN user.
Prerequisites
The IUA link set must be added.
Context
l
Make sure that a minimum of one item in the local port ID, local IP address, remote port
ID, and remote IP address of a link is different from the corresponding item of other links.
Only two links can be configured in the same link set. In addition, the local IP addresses
of the two links must be the same.
Procedure
Step 1 (This step is not required if the command line interface is already in the Sigtran mode.) In global
config mode, run the sigtran command to enter the Sigtran mode.
Step 2 Run the iua-link add command to add an IUA link.
Step 3 You can run the display iua-link attribute command to check whether the configured IUA link
information is the same as the data plan.
----End
Example
Assume that the link ID is 0, link set ID is 0, local port ID is 1402, local IP address is 10.10.10.10,
remote port ID is 1404, and remote IP address 1 is 10.10.10.20. To add such a link, do as follows:
huawei(config-sigtran)#iua-link add 0 0 1402 10.10.10.10 1404 10.10.10.20
huawei(config-sigtran)#display iua-link attribute
{ <cr>|linkno<L> }:
Command:
display iua-link attribute
---------------------------------------------------------------------LinkNo
: 0
LinksetNo
: 0
Local port
: 1402
Local IP address
: 10.10.10.10
Remote port
: 1404
Remote IP address
: 10.10.10.20
Remote IP address 2
: -
Issue 02 (2013-10-08)

379

Configuration Guide
Priority
: 0
----------------------------------------------------------------------
6.3.3 Configuring the VoIP ISDN BRA User

After the MG interface is configured, you can add the VoIP ISDN BRA user on this interface,
and configure the system parameters, oversea parameters, and attributes of the BRA port, to
Configuring the ISDN BRA User Data

This topic describes how to configure the ISDN BRA user data based on H.248 (including the
priority, flag of reporting the fault of UNI, etc., and the data must be the same as the
corresponding data on the MGC) so that the ISDN BRA user can access the network to use the
ISDN BRA service.
Prerequisites
The H832DSLD service board must be inserted into the planned slot correctly and the board
must be in the normal state.
The IUA link must be configured according to the requirements. For details about how to
configure the IUA link, see 6.3.2 Configuring the IUA Link.
Context
One H832DSLD board can be configured with a maximum of eight ISDN BRA users.
Table 6-23 lists the default settings of the attributes of the ISDN BRA user. When configuring
these attributes, you can modify the values according to the service requirements.
Table 6-23 Default settings of the attributes of the ISDN BRA user
Parameter
Default Settings
Priority of the ISDN BRA user
cat3: (common user)
Flag of reporting the UNI fault of the ISDN

BRA user
Disable
Threshold for the number of auto recoveries

from deterioration faults
20
Procedure
Step 1 In global config mode, run the esl user command to enter the ESL user mode.
Step 2 Run the mgbrauser add command to add an ISDN BRA.
Issue 02 (2013-10-08)

380

Configuration Guide
l When iid-map in the iua-linkset add command is configured to 1, interfaceid must be

configured and be different from the interfaceid of other users in the same link set.
l The terminal ID of an ISDN BRA user must be different from the terminal IDs of other users.
l If the MG interface does not support the terminal layering function, the terminal ID must be
configured when an ISDN BRA user is added. In addition, the terminal ID must differ from
the terminal ID of the existing ISDN BRA user by an integer multiple of 2. For example, to
add the first ISDN BRA user, the terminal ID is 2; to add the second ISDN BRA user, the
terminal ID is 4; to add the third ISDN BRA user, the terminal ID is 6; the rest may be deduced
by analogy.
l If the MG interface supports the terminal layering function, the terminal ID cannot be
configured when an ISDN BRA user is added on the MG interface. The system automatically
allocates a terminal ID for the user.
Step 3 Run the mgbrauser attribute set command to configure the attributes of the ISDN BRA user.
The attributes of an ISDN BRA user include the following:
l Priority of the ISDN BRA user. The priorities are classified to cat1 (the first class government
user), cat2 (the second class government user), and cat3 (common user) in the sequence of
descending. Without special requirements, the default cat3 is adopted.
l Flag of reporting the UNI fault of the ISDN BRA user. This attribute controls whether to
report the UNI fault to MGC. The default is not to report.
l Threshold for the number of auto recoveries from deterioration faults. This attribute indicates
the maximum times that the equipment attempts to recover from deterioration faults. Zero
indicates not to recover automatically. The number of 255 indicates not to limit the attempt
times. The default is 20.
Step 4 Run the display mgbrauser attribute command to query whether the configured attributes of
the ISDN BRA user are the same as the data plan.
----End
Example
Assume the following configurations:
l
Link set ID: 0
IUA interface ID: 0 (value of iid-map: 1)
Terminal ID: 2 (not supporting the terminal layering function)
User priority: cat3
Telephone number: 83110001 (Before configuring a emergency standalone number, ensure

that the emergency standalone function has been enabled on the MG interface. For details,
see (Optional) Configuring the Software Parameters of an MG Interface.)
UNI alarm report function: enable
Threshold for the number of auto recoveries from L1 deterioration faults: 30
To add an ISDN BRA user with such configurations on port 0/4/0 of MG interface 0, do as
follows:
huawei(config-sigtran)#quit
huawei(config-esl-user)#mgbrauser add 0/4/0 0 0 interfaceid 0 terminalid 2 priority
cat3 telno 83110001
Issue 02 (2013-10-08)

381

Configuration Guide
Are you sure to configure the working mode of the DSL board to normal and reset
the board automatically? (y/n)
[n]:y
huawei(config-esl-user)#display mgbrauser 0/4
-----------------------------------------------------------------------------F /S /P /B MGID
LinkSetNo UserIFID TelNo
Priority TerminalID
-----------------------------------------------------------------------------0 /4 /0 /0 0
0
0
83110001
Cat3
A2
-----------------------------------------------------------------------------huawei(config-esl-user)#mgbrauser attribute set 0/4/0 priority cat3 unireport
enable auto-resume-limit 30
huawei(config-esl-user)#display mgbrauser attribute 0/4/0
{ <cr>|endframeid/slotid/portid<S><Length 1-15> }:
Command:
display mgbrauser attribute 0/4/0
-------------------------------------------------------F /S /P UNIreport Prior Auto reservice times/limit
-------------------------------------------------------0 /4 /0 enable
Cat3
0/30
--------------------------------------------------------

Context
Issue 02 (2013-10-08)
Parameter
Description
Default Setting

sending flag.

is sent.

flag.
0: Indicates China.

flag.


with ringing.

support flag.


device.


382

Configuration Guide
Parameter
Description
Default Setting

7-11

parameter.
12

source.
13

16
14

parameter 13.
16
15-255

parameter.
Procedure
----End
Example
do as follows:
Parameter value: 1
-----------------------------------------------------------------------------

Issue 02 (2013-10-08)

383

Configuration Guide
Context
Parameter
Description
Default Setting





limited.
locked.

offset.
Line B offset

detector tuning.

value is the common
parameter.
4, 6-255
Procedure
----End
Example
{ <cr>|name<0,3> }:
Command:
-----------------------------------------------------------------------------
Issue 02 (2013-10-08)

384

Configuration Guide
Parameter name index: 0

Parameter value: 0
apply, 1:apply
Parameter value: 1
Parameter value: 0
-----------------------------------------------------------------------------
(Optional) Configuring the Attributes of an ISDN BRA Port

This topic describes how to configure the attributes of an ISDN BRA port to ensure that the
ISDN BRA port can meet the actual application requirements. You can configure the autodeactivation status, remote power supply status, UNI fault alarming function, and working mode
of the port.
Table 6-26 lists the default values of the attributes of an ISDN BRA port. When configuring the
attributes, you can change the values according to the service requirements.
Table 6-26 Default values of the attributes of an ISDN BRA port
Parameter
Default Setting
Autodeactive
Disable
Autodeactive-delay
30s
Activemode
unstable-active
Remotepower
Disable
Unialarm
Disable
Workmode
p2mp
Procedure
Step 1 In global config mode, run the braport command to enter braport mode.
Step 2 Run the braport attribute set command to configure the attributes such as the working mode,
auto-deactivation status, and remote power supply status of the port.
Issue 02 (2013-10-08)

385

Configuration Guide
If an ISDN BRA port needs to be connected to multiple terminal users, configure the working
mode of the port to p2mp. If an ISDN BRA port needs to be connected to only one terminal user,
configure the working mode of the port to p2p.
For detailed description of the braport attribute set command, see the parameter description
in braport attribute set.
----End
Example
Assume that the working mode is p2mp, the activation mode is stable, and the auto-deactivation
function is disabled. To configure such attributes of ISDN BRA port 0/4/0, do as follows:
huawei(config)#braport
huawei(config-braport)#braport attribute set 0/4/0 workmode p2mp activemode stableactive
huawei(config-braport)#display braport attribute
{ frameid/slotid/portid<S><Length 1-15>|frameid/slotid<S><Length 1-15> }:0/4/0
Command:
display braport attribute 0/4/0
----------------------------------------------------------------------------F /S /P Remotepower Workmode Autodeactive Deactivedelay Activemode Unialarm
----------------------------------------------------------------------------0 /4 /0 disable
p2mp
disable
30
stable
disable
-----------------------------------------------------------------------------
6.4 Configuring the VoIP ISDN BRA Service (Based on the

SIP Protocol)
After configuring the SIP interface, you can add VoIP ISDN BRA users on this interface to
Prerequisites
According to the actual network, a route from the MA5616 to the IMS must be configured to
ensure that the MA5616 communicates with the IMS normally.
Context
l
The ISDN is integrated services digital network. Defined by the International Telegraph
and Telephone Consultative Committee (CCITT), the ISDN technology provides two types
of user-network interfaces based on the user-network interface reference model.
ISDN basic rate interface (BRI), which supports a rate of 144 kbit/s and provides two
B channels (for carrying services) and one D channel (for transmitting call control
signaling and maintenance and management signaling). The rate of B channels is 64
kbit/s and the rate of D channel is 16 kbit/s. The service carried on the ISDN BRI is the
ISDN basic rate access (BRA) service.
ISDN primary rate interface (PRI), which supports a rate of 2.048 Mbit/s and provides
30 B channels and one D channel. The rates of the B channel and D channel are both
64 kbit/s. The service carried on the ISDN PRI is the ISDN primary rate access (PRA)
service.
Issue 02 (2013-10-08)

386

Configuration Guide
The MA5616 supports only the VoIP ISDN BRA service.
The MA5616 provides the ISDN BRA service through the DSL port on the DSLD board.
For detailed description of the DSLD board, see DSLD - Eight-Channel ISDN Service
Board in the Hardware Description.
The MA5616 can also function as a voice over IP gateway (VGW) in the IMS architecture. In
the downstream direction, it is connected to the ISDN BRA users; in the upstream direction, it
is connected to the IMS system through the SIP interface, providing the VoIP ISDN BRA service
by working with the IMS core.
The functions and applications of the SIP interface are the same as the functions and applications
of the MG interface.
Data preparation
Table 6-27 provides the data plan for configuring the VoIP ISDN BRA service.
Table 6-27 Data plan for configuring the VoIP ISDN BRA service when the SIP protocol is
used
Item
SIP interface
data
Remarks
Media and
signaling
parameter
s
Media and
signaling
upstream VLAN
It is used for the upstream VLAN of the

Signaling
upstream port
Uplink port for configuring the SIP

signaling.
Media IP address
and signaling IP
addresses

address pools consists of all the IP
Default IP address
of the MG
Next hop address from the MA5616 to

the IMS core network device.
CAUTION
Note that the media and the signaling can
use the same VLAN or different VLANs,
depending on the negotiation with the
upstream device.
CAUTION
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,
the call service may fail.
Attributes
of the SIP
interface
Issue 02 (2013-10-08)
SIP interface ID
It is used for the VoIP service to be

configured. The MA5616 supports four
VAG.

387

Configuration Guide
Item
Remarks
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
SIP
interface
cannot be
enabled if
these
parameter
s are not
configure
d.
Signaling port ID
of the SIP
interface
The value range is 5000-5999. The

protocol defines the port ID as 5060.
IP address of the
active IMS core
network device to
which the SIP
interface belongs

parameters of only one IMS core
network device are required. When dual
homing is required, the IP address and
the port ID of the standby IMS core
network device must be configured.
Port ID of the
active IMS core
network device to
which the SIP
interface belongs
Transmission
mode of the SIP
interface

according to the requirements of the
IMS core network device. Generally,
UDP is used.
Home domain of
the SIP interface
It corresponds to parameter homedomain in the MG interface attributes.
Index of the
profile used by the
SIP interface
It corresponds to parameter Profileindex in the MG interface attributes.
IP address
obtaining mode of
the proxy server
l In the IP mode, the IP address and

the port ID of the active proxy server
must be configured.
l In the DNS-A or DNS-SRV mode,
the domain name of the active proxy
server must be configured.
ISDN BRA user

data
(The data
configuration
must be
consistent with
the data
configuration
on the IMS.)
Issue 02 (2013-10-08)
Ringing mode of the SIP

interface
The ringing mode of the SIP interface

is determined according to the service
requirements.
Slot that houses the DSLD

service board
1-4
User data
The phone number that the IMS core

network device allocates to the user
must be configured.
Phone number

388

Configuration Guide
Item
Remarks
User priority

user priorities must be specified,
including:
government users)
government users)
l cat3: common (default priority,
namely, common users)
System parameters

oversea version flag and message
be configured according to local
the user terminal meets local standards.
Overseas parameters

according to local standards to ensure
that the response of the user terminal
meets local standards.
Attributes of an ISDN BRA

Port
The attributes such as the working

mode, remote power supply status, and
auto-deactivation status of the port can
be configured. Modify such attributes
only if there is a special requirement.
6.4.1 Configuring the SIP Interface

As an interface used for the intercommunication between the MA5616 and the IMS core network
devices, the interface is vital to the SIP-based VoIP service. Therefore, to implement the VoIP
service, the SIP interface must be configured and must be in the normal state.
Procedure
Issue 02 (2013-10-08)

389

Configuration Guide
Context
Procedure
1.
2.
----End
Example

Issue 02 (2013-10-08)

390

Configuration Guide
Prerequisites
VLAN Interface.
Context
l
Procedure
1.
pool.
2.

1.
address pool.
2.
----End
Example
huawei(config)#voip
huawei(config-voip)#ip address
huawei(config-voip)#display ip
Media:
Issue 02 (2013-10-08)
media 10.13.4.116 10.13.1.1

media 10.13.4.117 10.13.1.1
signaling 10.13.4.116
signaling 10.13.4.117
address media

391

Configuration Guide
IP Address...........:
Subnet Mask..........:
Gateway..............:
MAC Address..........:

10.13.4.116
255.255.0.0
10.13.1.1
00-E0-FC-AF-91-33
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Gateway..............: 10.13.1.1
Signaling:
IP Address...........: 10.13.4.116
Subnet Mask..........: 255.255.0.0
IP Address...........: 10.13.4.117
Subnet Mask..........: 255.255.0.0
Adding an SIP Interface

This topic describes how to add a Session Initiation Protocol (SIP) interface and configure the
basic and optional attributes of the interface for the MA5616 to communicate with the IP
multimedia subsystem (IMS). The basic SIP interface attributes include the Media IP,
Signalling IP, Transfer mode, Signalling Port, and Home Domain Name. The optical
attributes include the MG Domain Name, Description, and Register URI.
Prerequisites
l
The MA5616 uses the SIP protocol.
The media and signaling IP addresses to be configured for the SIP interface have been
added to the media and signaling IP address pools.
Context
One MA5616 supports four SIP interfaces.
Procedure
Step 1 Run the interface sip command to add an SIP interface.
Step 2 Run the if-sip attribute basic command to configure the basic attributes of the SIP interface.
The basic attributes of a SIP interface include the following:
l Media IP and Signalling IP: specify the IP addresses used by the service stream and
signaling stream over the SIP interface.
l Signalling Port: specifies the port ID used for communication using the SIP interface. The
SIP-defined port ID 5060 is recommended.
l Transfer Mode: specifies the transmission mode, which can be Transmission Control
Protocol (TCP), User Datagram Protocol (UDP), or Stream Control Transmission Protocol
(STCP) mode. This mode must be the same as the mode configured on the IMS.
l Proxy IP and Proxy Domain Name: specify the address of the IMS. At least one of them
must be configured. The specified IP address or name must be the same as that configured
on the IMS.
Issue 02 (2013-10-08)

392

Configuration Guide
l Proxy Address Mode: specifies the mode (IP address or domain name) used by the device
to recognize a proxy server.
l Proxy Port: specifies the port ID used by the device to communicate with the IMS. The port
ID must be the same as that configured on the IMS.
l Home Domain Name: specifies the name of the home domain that provides services for SIP
users. If the optional attribute Register URI is not configured for the SIP interface, the
interface uses the home domain name (a mandatory attribute) to register with the server.
l SIP Profile Index: specifies a SIP profile that defines coding and decoding priorities, coding
and decoding types, and packetization duration.
Step 3 Run the if-sip attribute optional command to configure the optional attributes of the SIP
interface.
Optional attributes of a SIP interface include the following:
l Description: describes information about the SIP interface, facilitating interface
management and maintenance.
l Phone Context: specifies the range of local phone numbers. This attribute and a local phone
number identify a globally-unique resource. For information about the valid character set
and format, see RFC3966.
l Register URI: specifies the uniform resource identifier (URI) of the server with which a SIP
user registers.
l URI-Conference Factory URI: identifies a conference server that allocates conference
resources based on the received conference request. Configure this parameter if a SIP user
subscribes to the conference service. For information about the valid character set and format,
see RFC3261.
l SDP Negotiation Mode: specifies the preferential Session Description Protocol (SDP)
negotiation mode, which can be the local or remote mode.
l Mode of Supporting Proxy Dual-Homing: specifies whether the device supports IMS dualhoming and automatic switchback.
l Proxy Detection Mode: includes the option, probe, and register modes. The probe mode is
used if the device does not support IMS dual-homing. The option or register mode is used if
the device supports IMS dual-homing.
l Proxy Refresh Mode: includes three modes, that is, immediate, defer, and no-switch.
Step 4 Run the display if-sip attribute command to query the SIP interface attributes.
Step 5 After the configuration, you need to run the reset command to reset the SIP interface to make
Step 6 After the configuration, run the display if-sip attribute running command to query the status
of the SIP interface.
----End
Example
Assume that the media IP address is 10.13.4.116, signaling IP address is 10.13.4.117,
transmission protocol is UDP, port ID is 5000, IP address 1 of the primary proxy server is
10.13.4.118, port ID of the primary proxy server is 5060, domain name of the primary proxy
server is proxy.domain, IP address 1 of the secondary proxy server is 10.13.4.119, port ID of
Issue 02 (2013-10-08)

393

Configuration Guide
the secondary proxy server is 5060, home domain name is sip.huawei.com, and profile index is
1. To configure such attributes of SIP interface 0, do as follows:
huawei(config-if-sip-0)#if-sip attribute basic media-ip 10.13.4.116 signal-ip 10
.13.4.117 signal-port 5000 transfer udp primary-proxy-ip1 10.13.4.118 primary-pr
oxy-port 5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.13.4.119
huawei(config-if-sip-0)#if-sip attribute basic home-domain sip.huawei.com
sipprofile-index 1
huawei(config-if-sip-0)#
Resetting SIP interface 0 succeeded
huawei(config-if-sip-0)#display if-sip attribute running
-----------------------------------------------------------MGID
0
Signalling IP
10.13.4.117
Signalling Port
5000
Media IP
10.13.4.116
Transfer Mode
UDP
Primary Proxy IP 1
10.13.4.118
Primary Proxy IP 2
Primary Proxy Port
5060
10.13.4.119
Secondary Proxy Port
5060
Proxy Address Mode
IP
SIPProfile Index
1:Default
Service logic Index
0:Default
Server Address DHCP Option
0:None
Primary Proxy Domain Name
proxy.domain
Secondary Proxy Domain Name
Home Domain Name
sip.huawei.com
Description
MG Domain Name
Phone Context
Register URI
Conference Factory URI
Primary Proxy State
up
Secondary Proxy State
up
Current Proxy
-
Issue 02 (2013-10-08)

394

Configuration Guide
Subscribe to UA-Profile
enable
Subscribe to REG-STATE
disable
Subscribe to MWI
disable
SDP negotiation mode
remote
Mode of supporting proxy dual-homing dualhome
Proxy detection mode
probe
Proxy refresh mode
immediate
------------------------------------------------------------
(Optional) Configuring the Software Parameters of the SIP Interface

The software parameters of a SIP interface mainly define certain common service attributes of
the SIP interface. After the software parameter configuration, the parameters take effect
immediately and are valid only to the SIP interface. Skip this topic if the system default
Prerequisites
see Adding an SIP Interface.
Context
The details about the software parameters that can be configured of a SIP interface that supports
SIP, see section Usage Guidelines in mg-software parameter. The other parameters are
Table 6-28 Software parameters usually configured of a SIP interface
Parameter
Description
Default Setting
Indicates whether the

standalone mode is supported.

standalone function is not
supported.
standalone function is
supported.
Default: 0
1.
Indicates whether the heartbeat

message of the MG is disabled.

the MG is disabled
the MG is enabled
Default value: 0.
Issue 02 (2013-10-08)

395

Configuration Guide
Procedure
Step 1 Enter the SIP interface mode.
In global config mode, run the interface sip command to enter the SIP interface mode.
----End
Example
To configure software parameter 2 of the SIP interface 0 to 1 so that the SIP interface supports
standalone, do as follows:
huawei(config-if-sip-0)#mg-software parameter 2 1
huawei(config-if-sip-0)#display mg-software parameter 2
------------------------------------------------MGID:0
para index:2
value:1
------------------------------------------------APPENDIX:
------------------------------------------------Parameter Index: Interface software parameter name:
2 : SAL Support
0: No
1: Yes
(Optional) Configuring the Ringing Mode of the SIP Interface

The ringing mode includes the initial ringing mode and cadence ringing mode. This topic
describes how to configure the ringing mode of the SIP interface to support the break-make
ratios of various new ringing modes and make the ringing mode meet the local standards.
Prerequisites
The SIP interface must be added successfully.
Context
l
Multiple initial ringing modes and cadence ringing modes have been embedded in the
system. You can refer to the usage guide of the ringmode add command to confirm whether
the system-defined ringing modes meet the user requirements.
If the system-defined ringing modes cannot meet the user requirements, you can use the
user-defined ringing mode.
You can configure the cadence duration for the user-defined ringing to form different
ringing modes.
The user-defined ringing modes are 0-15, which correspond to the cadence ringing modes
128-143 and initial ringing modes 144-159 defined by the user. For example, if the user-
Issue 02 (2013-10-08)

396

Configuration Guide
defined cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the userdefined initial ringing mode is 144, user-defined ringing mode 0 is selected.
l
The system supports a maximum of 16 records of the ringing mode mapping.
The ringing mapping name must be unique on the same SIP interface.
An index can be used for adding only one ringing mode on the same SIP interface.
The 16 user-defined ringing modes can be modified but cannot be added.
Precaution
Procedure
Step 1 (Optional) In the global config mode, run the user defined-ring modify command to configure
the user-defined ringing mode.
NOTE
l Perform this step only when the system-defined ringing modes do not meet the user requirements, and
you can define the ringing types numbered 0-15.
l After configuring the user-defined ringing mode, you need to reset the corresponding service board to
make the configuration data take effect, so that the user of the service board can use the new userdefined ringing mode. If the service board has been in service for a period, evaluate the impact on the
online users before resetting the service board, and then determine whether to perform this operation.
After the user-defined ringing mode is configured, run the display user defined-ring command
to query the user-defined ringing mode.
Step 2 Run the interface sip command to enter the SIP mode.
Step 3 Run the ringmode add command to add the ringing mapping.
Run this command to configure the ringing mode for the users on the same SIP interface. The
key parameters are described as follows:
l cadencering: Indicates the cadence ringing mode. The range 128-143 of this parameter
l initialring: Indicates the initial ringing mode. The range 144-159 of this parameter
Step 4 Run the display ringmode command to query ringing mapping records.
----End
Example
Assume that:
l
Index of the ringing mode mapping record: 1
Name of the ringing mode mapping record: alert-group
Cadence ringing mode: special ringing; break-make ratio: 1:2 (the corresponding parameter
value is 1.)
Initial ringing mode: normal ringing (FSK); break-make ratio: 1:4 (the corresponding
parameter value is 4.)
To add such a ringing mode mapping record on SIP interface 0, do as follows:

Issue 02 (2013-10-08)

397

Configuration Guide
huawei(config-if-sip-0)#ringmode add 1 alter-group cadencering 1 initialring 4
huawei(config-if-sip-0)#display ringmode 1
----------------------------------------------------------------MGID: 0
Index: 1
Ringmode-name: alter-group
CadenceRing: 1: Special Ring 1:2
InitialRing: 4: Normal Ring (FSK) 1:4
-----------------------------------------------------------------
6.4.2 Configuring the VoIP ISDN BRA User

This topic describes how to configure the VoIP ISDN BRA user. After the SIP interface is
configured, you can add the VoIP ISDN BRA user on this interface to implement the VoIP ISDN
BRA service.
Configuring the ISDN BRA User Data

This topic describes how to configure the ISDN BRA user data on the SIP interface (the data
must be the same as the corresponding data on the IMS) so that the ISDN BRA user can access
the network to use the ISDN BRA service.
Prerequisites
The H832DSLD service board must be inserted into the planned slot correctly and the board
must be in the normal state.
Context
One H832DSLD board can be configured with a maximum of eight ISDN BRA users.
Table 6-29 lists the default settings of the attributes of the ISDN BRA user. When configuring
the attributes of these attributes, you can modify the values according to the service requirements.
Table 6-29 Default settings of the attributes of the ISDN BRA user
Issue 02 (2013-10-08)
Parameter
Default Settings
Priority of the ISDN BRA user
cat3 (common users)
Flag of reporting the UNI fault of the ISDN

BRA user
disable
Threshold for the number of auto recoveries

from deterioration faults
20
The matching scheme of an outgoing calling

number
match
The voice bear capability of a port
speech+3.1k-audio

398

Configuration Guide
Parameter
Default Settings
The type of the called number sent to the

ISDN terminal when an incoming call is
initiated
unknown
The international prefix flag
disable
The national prefix flag
disable
The change plan of an incoming called

number used by the user on the port
The change plan of an outgoing calling

number used by the user on the port
The calling number
The digitmap group used by the user
Procedure
Step 1 In global config mode, run the esl user command to enter the ESL user mode.
Step 2 Run the sipbrauser add command to add an ISDN BRA user.
Step 3 Run the display sipbrauser command to check whether the ISDN BRA user data is the same
as the data plan.
Step 4 (Perform this step when you need to modify the attributes of an ISDN BRA user.) Run the
sipbrauser attribute set command to configure the attributes of the ISDN BRA user.
Step 5 (Perform this step only after you modify the attributes of the ISDN BRA user.) Run the display
sipbrauser attribute command to query whether the configured attributes of the ISDN BRA
user are the same as the data plan.
Step 6 (Perform this step only when you need to configure an extended phone number for the ISDN
BRA user.) Run the sipbrauser extend-telno add command to add multiple phone numbers or
a phone number containing non-digit characters for the ISDN BRA user.
Step 7 (Perform this step only after you configure the extended phone number for an ISDN BRA user.)
Run the display sipbrauser extend-telno command to query whether the configured extended
phone number of the ISDN BRA user is the same as the data plan.
----End
Example
Assume that:
l
SIP interface ID: 0
Phone number: 28780000
Call priority: cat3
Issue 02 (2013-10-08)

399

Configuration Guide
UNI fault report flag: disable
Number of auto recoveries from deterioration faults: 10
Voice bear capability: speech
Type of the called number: national
International prefix flag: enable
national prefix flag: enable
Digitmap group: DigitmapGroup1
Change plan of an incoming called number: NumberChange1
Change plan of an outgoing calling number: NumberChange2
Calling number is 12345678
Extended phone number: +86-755-28780000
To add such an ISDN BRA user connected to the 0/4/0 port, do as follows:
huawei(config)#esl-user
huawei(config-esl-user)#sipbrauser add 0/4/0 0 telno 28780000
huawei(config-esl-user)#display sipbrauser 0/4/0
Command:
display sipbrauser 0/4/0
--------------------------------------F /S /P
MGID
TelNo
--------------------------------------0 /4 /0
0
28780000
--------------------------------------huawei(config-esl-user)#sipbrauser attribute set 0/4/0 priority cat3 unireport d
isable auto-resume-limit 10 bc speech called-num-type national international-pre
fix-flag enable national-prefix-flag enable digitmap-group DigitmapGroup1 incomi
ngcall-numberchange NumberChange1 outgoingcall-numberchange NumberChange2 cli-nu
mber 12345678
huawei(config-esl-user)#display sipbrauser attribute 0/4/0
Command:
display sipbrauser attribute 0/4/0
---------------------------------------------------------------------------F /S /P
: 0 /4 /0
UNIreport
: disable
Priority
: cat3
Auto reservice times/limit
: 0/10
Digitmap group
: DigitmapGroup1
Incoming called number change plan : NumberChange1
Outgoing caller number change plan : NumberChange2
CLI number
: 12345678
CLI mode
: match
Bear capability
: speech
Called number type
: national
International prefix flag
: enable
National prefix flag
: enable
---------------------------------------------------------------------------huawei(config-esl-user)#sipbrauser extend-telno add 0/4/0 +86-755-28780000
huawei(config-esl-user)#display sipbrauser extend-telno 0/4/0
----------------------------------------------------------Index
Extend-telno
----------------------------------------------------------1
+86-755-28780000
2
28780000
3
0755-28780000
-----------------------------------------------------------
Issue 02 (2013-10-08)

400

Configuration Guide

Context
Issue 02 (2013-10-08)
Parameter
Description
Default Setting

sending flag.

is sent.

flag.
0: Indicates China.

flag.


with ringing.

support flag.


device.


7-11

parameter.
12

source.
13

16
14

parameter 13.
16
15-255

parameter.

401

Configuration Guide
Procedure
----End
Example
do as follows:
Parameter value: 1
-----------------------------------------------------------------------------

Context
Issue 02 (2013-10-08)
Parameter
Description
Default Setting





limited.
locked.

offset.
Line B offset

detector tuning.

value is the common
parameter.

402

Configuration Guide
Parameter
Description
Default Setting
4, 6-255
Procedure
----End
Example
{ <cr>|name<0,3> }:
Command:
Parameter value: 0
apply, 1:apply
Parameter value: 1
Parameter value: 0
-----------------------------------------------------------------------------
(Optional) Configuring the Attributes of an ISDN BRA Port

This topic describes how to configure the attributes of an ISDN BRA port to ensure that the
ISDN BRA port can meet the actual application requirements. You can configure the autodeactivation status, remote power supply status, UNI fault alarming function, and working mode
of the port.
Issue 02 (2013-10-08)

403

Configuration Guide
Table 6-32 lists the default values of the attributes of an ISDN BRA port. When configuring the
attributes, you can change the values according to the service requirements.
Table 6-32 Default values of the attributes of an ISDN BRA port
Parameter
Default Setting
Autodeactive
Disable
Autodeactive-delay
30s
Activemode
unstable-active
Remotepower
Disable
Unialarm
Disable
Workmode
p2mp
Procedure
Step 1 In global config mode, run the braport command to enter braport mode.
Step 2 Run the braport attribute set command to configure the attributes such as the working mode,
auto-deactivation status, and remote power supply status of the port.
If an ISDN BRA port needs to be connected to multiple terminal users, configure the working
mode of the port to p2mp. If an ISDN BRA port needs to be connected to only one terminal user,
configure the working mode of the port to p2p.
For detailed description of the braport attribute set command, see the parameter description
in braport attribute set.
----End
Example
Assume that the working mode is p2mp, the activation mode is stable, and the auto-deactivation
function is disabled. To configure such attributes of ISDN BRA port 0/4/0, do as follows:
huawei(config-braport)#braport attribute set 0/4/0 workmode p2mp activemode stableactive
huawei(config-braport)#display braport attribute
{ frameid/slotid/portid<S><Length 1-15>|frameid/slotid<S><Length 1-15> }:0/4/0
Command:
display braport attribute 0/4/0
----------------------------------------------------------------------------F /S /P Remotepower Workmode Autodeactive Deactivedelay Activemode Unialarm
----------------------------------------------------------------------------0 /4 /0 disable
p2mp
disable
30
stable
disable
-----------------------------------------------------------------------------
Issue 02 (2013-10-08)

404

Configuration Guide
6.5 Configuring the FoIP Service (Based on the H.248

Protocol)
FoIP service when the H.248 protocol is used to transmit the fax data service over the IP network.
Prerequisites
l
The communication between the MG and the MGC must be in the normal state, and the
fax mode on the MGC side must be consistent with the fax mode on the MG side.
The voice service port used by the FoIP service and the voice service on that port must be
Context
The FoIP service can be classified according to the following modes:
l
According to the coding/decoding mode: In this mode, the FoIP service is classified into
T.30 transparent transmission fax (using the G.711 coding) and T.38 fax (using the T.38
coding).
According to the role of the MGC: In this mode, the FoIP service is classified into the
SoftSwitch-controlled fax and the self-switch fax (the fax flow is controlled by the MGC
itself).
The MA5616 supports the self-switch mode and the negotiation mode:
l
Self-switch: If the self-switch mode is configured, the fax working mode of the MA5616
is not controlled by the MGC. Therefore, manual configuration is required.
Negotiation: If the negotiation mode is configured, the fax working mode of the
MA5616 is automatically configured during the negotiation with the MGC. Therefore,
manual configuration is not required.
The MA5616 supports the V2, V3, and V5 fax flows.

l
In the V2 negotiation flow, the MG determines the transmission mode to be used

(transparent transmission mode or T.38-based transmission mode), and determines whether
the fax port ID is increased by 2. No signaling negotiation is performed when the port ID
is increased by 2. Therefore, when the V2 T.38 is configured, the IDs of the local and peer
ports must be configured consistently. That is, the port IDs are both increased by 2 or neither
of the port IDs is increased by 2.
In the V3 negotiation flow, the softswitch determines the transmission mode to be used
(transparent transmission mode or T.38-based transmission mode). To be specific, if the
softswitch requires the T.38-based transmission mode, this transmission mode is used;
otherwise, the transparent transmission mode is used. In addition, the softswitch determines
whether the fax port ID is increased by 2 through signaling negotiation.
In the V5 negotiation flow, the softswitch determines the DSP and port ID. In addition, the
softswitch determines whether the fax port ID is increased by 2 through signaling
negotiation.
The MA5616 supports the 10 ms packing function and the RFC 2198 function.
Issue 02 (2013-10-08)

405

Configuration Guide
10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the fax

transparent transmission function is added with the 10 ms G.711 transparent transmission.
This reduces delay, improves the performance of transparent transmission, and decreases
the impact of packet loss on the transmission of the fax service data.
RFC 2198 function: Through the redundant transmission, the RFC 2198 function improves
the reliability of data transmission. When the network packet loss occurs, the RFC 2198
can ensure the service quality.
Table 6-33 lists the default configuration of the flows of the FoIP service:
Table 6-33 Default configuration of the flows of the FoIP service
Item
Default
Coding/decoding negotiation mode
Negotiation
Coding/decoding mode
Transparent transmission fax
Negotiation flow
V3 flow
10 ms packing switch
Disabled
RFC2198 startup mode
2198 intelligent startup function not enabled
Transmission mode of the modem event
ControlledByMGC
Coding/decoding mode for voice-band

data (VBD)
G.711A
Payload type for VBD
Static
T.38 port number
The same as the voice port number
Procedure
Step 1 Configure public fax and modem parameters.
1.
Run the fax-modem parameters negomode command to configure the negotiation mode.
2.
(Optional) Run the fax-modem parameters packet-interval-10ms command to enable or

disable the 10ms packing function.
3.
(Optional) Run the fax-modem parameters rfc2198-start-mode command to configure

the RFC2198 function.
4.
(Optional) Run the fax-modem parameters transevent command to configure the

transmission mode of the modem event.
5.
(Optional) Run the fax-modem parameters vbd-codec command to configure the codec
mode of the voice-band data (VBD).
6.
(Optional) Run the fax-modem parameters vbd-pt-type command to configure the

payload type of the VBD.
Issue 02 (2013-10-08)

406

Configuration Guide
Step 2 Configure the fax working mode.

l
If the negotiation mode is configured in Step 1.1, go to Step 2.1.
If the self-switch mode is configured in Step 1.1, run the fax parameters workmode
command to configure fax working mode.
1.
Run the fax parameters flow command to configure the fax flow.
2.
(Optional) Run the fax parameters is-port+2 command to configure the T.38 port ID.
NOTE
If the fax machines are not configured on the same MG interface, the configurations for whether the
T.38 fax port ID is added by 2 for the two sides must be consistent. That is, the T.38 fax port ID of
the two sides are both added by 2 or not added by 2.
Step 3 Query public fax and modem parameters and the codec mode of the fax.
Run the display fax-modem parameters and display fax parameters commands to query the
fax transmission parameters.
----End
Example
Assume that:
l
The negotiation mode of the MA5616 is self-switch.
The 10 ms packing function and the RFC2198 intelligent startup function are enabled.
The transmission mode of the modem event is ControlledByMGC (default).
The codec mode of the VBD is G.711A (default).
The payload type of the VBD is static payload (default).
The working mode of the fax is transparent transmission (thoroughly).
The fax working flow is V3 flow.
To configure the MA5616, do as follows:

huawei(config)#fax-modem parameters negomode selfswitch packet-interval-10ms ena
ble rfc2198-start-mode enableRfc2198SmartStartup transevent controlledByMGC vbdcodec G.711A vbdpt-type static
huawei(config)#fax parameters workmode thoroughly flow v3
huawei(config)#display fax-modem parameters
----------------------------------------------------------------------------Negomode
: Self switch
Packet-interval-10ms
: Enable
Rfc2198-start-mode
: Enable Rfc2198SmartStartup
TransEvent
: ControlledByMGC
Vbd-codec
: G.711A
Vbd-payload-type
: Static
----------------------------------------------------------------------------huawei(config)#display fax parameters
----------------------------------------------------------------------------FAX transfers mode
:Thoroughly
T38 Fax Port
:RTP port
FAX flow
:V3 Flow
-----------------------------------------------------------------------------
Issue 02 (2013-10-08)

407

Configuration Guide
6.6 Configuring the FoIP Service (Based on the SIP Protocol)

FoIP service based on the SIP protocol to transmit the fax data service over the IP network.
Prerequisites
l
The communication between the MA5616 and the IMS must be in the normal state.
The voice service port used by the FoIP service and the voice service on that port must be
Context
During the application of the fax service, the FoIP service can be classified into two modes
according to the participation of the SIP signaling in the transmission control process:
l
Self-switch: If the self-switch mode is configured, the fax working mode of the MA5616
needs to be configured manually.
Negotiation: If the negotiation mode is configured, the fax working mode of the
The FoIP service can be classified into two modes according to the fax coding:
l
Transparent transmission fax: The voice encoding (G.7xx encoding) is adopted.
T.38 fax: The T.38 encoding is adopted.
l
10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the fax

the impact of packet loss on the transmission of the modem service data.
RFC 2198 function: Through the redundant transmission, the RFC 2198 improves the
reliability of data transmission. When the network packet loss occurs, the RFC 2198 can
ensure the service quality.
Data preparation
It is recommended that you plan the working mode of the fax on the entire IP multimedia
subsystem (IMS) before configuring the data so that the working mode on the entire network is
consistent.
Table 6-34 Items involved in the FoIP service
Issue 02 (2013-10-08)
Item
Option
Remarks
Codec
negotiation
mode
Negotiation
The codec mode needs to be negotiated through the SIP

signaling.
Self-switch
The MG determines what codec mode is used.

408

Configuration Guide
Item
Option
Remarks
Codec mode
Transparent
transmission fax
The G.711 encoding is adopted.
T.38 flow
The T.38 encoding is adopted.
Table 6-35 lists the default configuration of the flows of the FoIP service.
Table 6-35 Default configuration of the flows of the FoIP service
Item
Default
Codec negotiation mode
Negotiation
Codec mode
Transparent transmission fax
Packing period
5 ms
RFC2198 intelligent startup

function
RFC2198 intelligent startup function not enabled
Coding/decoding mode for voiceband data (VBD)
G.711A
Payload type for VBD
Static
Transmission of FAX/Modem
event by RFC2833
Enabled
Procedure
1.
Run the interface sip command to enter the SIP mode.
2.
3.
(Optional) Run the fax-modem parameters rtp-interval command to enable or disable

the 10 ms packing function.
4.
(Optional) Run the rfc2198 set rfc2198-negomode command to configure the RFC2198
function.
5.
6.

7.
(Optional) Run the rfc2833 set rfc2833-fax-modem command to configure the mode for
reporting fax or modem events.
Issue 02 (2013-10-08)

409

Configuration Guide
Step 2 Configure the codec mode of the fax.

Run the fax parameters command to configure the fax working mode of the SIP interface.
Step 3 Check whether the fax transmission parameters are the same as the data plan.
Run the display fax-modem parameters and display fax parameters commands to check the
fax transmission parameters.
----End
Example
Assume that:
l
The RFC2198 negotiation mode is fixedstart.
The codec mode of the VBD is G.711A.
The payload type of the VBD is static payload.
The transmission mode of the fax is transparent transmission (thoroughly).

huawei(config-if-sip-0)#fax-modem parameters negomode self-switch rtp-interval 1
vbd-pt-type static
huawei(config-if-sip-0)#rfc2198 set rfc2198-negomode fixedstart rfc2198-startmode
smart2198
huawei(config-if-sip-0)#display fax-modem parameters
------------------------------------------------------------------------------MGID
:0
Nego-mode
:self-switch
Rtp-interval
:10ms
Vbd-codec
:G.711A
Vbd-pt-type
:static
Vbd-attribute-type
:v.152
------------------------------------------------------------------------------huawei(config-if-sip-0)#fax parameters transmode 0
huawei(config-if-sip-0)#quit
huawei(config)#display fax parameters 0
--------------------------------------MGID
Transmode
--------------------------------------0
Thoroughly
---------------------------------------
6.7 Configuring the MoIP Service (Based on the H.248

Protocol)
Prerequisites
l
Issue 02 (2013-10-08)
The communication between the MG and the MGC must be in the normal state.
410

Configuration Guide
The voice service port used by the MoIP service and the voice service on that port must be
Context
l
Self-switch: If the self-switch mode is configured, the modem working mode of the
MA5616 is not controlled by the MGC. Therefore, manual configuration is required.
Negotiation: If the negotiation mode is configured, the modem working mode of the
l
10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the modem

The MoIP service supports two transmission modes: the transparent transmission mode and the
relay (redundancy) mode. The MA5616 supports only the modem service in the transparent
transmission mode. In the transparent transmission mode, the MG uses the G.711 mode to encode
and decode the modem signal, and processes the signal like processing the common RTP data.
The transparent transmission mode depends on the bearer network to a great extent.
The report mode of the modem event:
l
Direct: In direct mode, the host reports the modem event to the MGC immediately when
the host receives a modem event.
Delay: In delay mode, the host does not report the modem event immediately after an event
is received, but waits for a period of time until the event times out and the fax signal is
detected. In this way, when the high-speed modem machine fails in the high-speed
transmission negotiation, it can transmit data in low-speed transmission mode.
Direct for high-speed signals: In the mode of the direct for high-speed signals, the host
reports the modem event with low speed signals to the MGC 5.5s after the host receives a
modem event; the host reports the modem event with high speed signals to the MGC
immediately when the host receives a modem event.
Procedure
1.
2.
(Optional) Run the fax-modem parameters packet-interval-10ms command to enable or

disable the 10 ms packing function.
3.
(Optional) Run the fax-modem parameters RFC2198-start-mode command to configure

the RFC2198 function.
Issue 02 (2013-10-08)

411

Configuration Guide
4.
(Optional) Run the fax-modem parameters transevent command to configure the

transmission mode of the modem event.
5.
6.

Step 2 Configure the event report mode of fax codec.

1.
Run the modem parameters tranmode command to configure the transmission mode of
the modem.
2.
(Optional) Run the modem parameters eventmode command to configure the report mode
of the modem event.
3.
(Optional) Run the modem parameters dtmf-fallback-voice command to configure the

function of switching the system service mode to voice when DTMF signals are detected
on the IP side.
NOTE
l To enable the MGC to quickly respond to a modem event, you need to configure the report mode
of the modem event as the direct report mode.
l By default, the transmission mode of the modem is the transparent transmission mode, the modem
event is reported in the direct mode, and disable the function of switching the system service
mode to voice when DTMF signals are detected on the IP side.
Step 3 Query public fax and modem parameters and the codec mode of the fax.
Run the display fax-modem parameters and display modem parameters commands to query
modem parameters.
----End
Example
Assume that:
l
The transmission mode of the modem event is ControlledByMGC (default).
The codec mode of the VBD is G.711A (default).
The payload type of the VBD is static payload (default).
The working mode of modem is transparent transmission (thoroughly).
The report mode of the modem event is direct.
The function of switching the system service mode to voice when DTMF signals are
detected on the IP side is disable.

huawei(config)#fax-modem parameters negomode selfswitch packet-interval-10ms ena
ble rfc2198-start-mode enableRfc2198SmartStartup transevent controlledByMGC vbdcodec G.711A vbdpt-type static
huawei(config)#modem parameters tranmode 0 eventmode 1 dtmf-fallback-voice disable
huawei(config)#display fax-modem parameters
----------------------------------------------------------------------------Negomode
: Self switch
Issue 02 (2013-10-08)

412

Configuration Guide
Packet-interval-10ms
: Enable
Rfc2198-start-mode
: Enable Rfc2198SmartStartup
TransEvent
: ControlledByMGC
Vbd-codec
: G.711A
Vbd-payload-type
: Static
----------------------------------------------------------------------------huawei(config)#display modem parameters
----------------------------------------------------------------------------MODEM transfers mode
: Thoroughly
MODEM event mode
: Direct
DTMF-Fallback-Voice
: Disable
-----------------------------------------------------------------------------
6.8 Configuring the MoIP Service (Based on the SIP

Protocol)
Prerequisites
l
The communication between the MA5616 and the IMS must be in the normal state.
The VoIP service must be configured, see 6.2.2 Configuring the VoIP PSTN User.
The voice service port used by the MoIP service and the voice service on that port must be
Context
l
Self-switch: If the self-switch mode is configured, you need to configure the fax working
mode of the MA5616 manually.
Negotiation: If the negotiation mode is configured, the modem working mode of the
l
10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the modem

The MoIP service supports two transmission modes: the transparent transmission mode and the
relay (redundancy) mode. The MA5616 supports only the modem service in the transparent
transmission mode. In the transparent transmission mode, the MG uses the G.711 mode to encode
and decode the modem signal, and processes the signal like processing the common RTP data.
The transparent transmission mode depends on the bearer network to a great extent.
Issue 02 (2013-10-08)

413

Configuration Guide
Procedure
1.
Run the interface sip command to enter the SIP interface mode.
2.
3.
(Optional) Run the fax-modem parameters rtp-interval 1 to enable or disable the 10 ms

packing function.
4.
5.

6.
(Optional) Run the rfc2198 set rfc2198-negomode command to configure the RFC 2198
function.
7.
(Optional) Run the rfc2198 set rfc2198-startmode command to configure the startup mode
of the RFC 2198 function.
8.
(Optional) Run the rfc2833 set rfc2833-fax-modem command to configure the mode for
reporting fax or modem events.
Step 2 Configure the transmission mode of the modem.

1.
Run the modem parameters tranmode command to configure the transmission mode of
the modem. Currently, only the modem service in the transparent transmission mode is
supported.
1.
(Optional) Run the modem parameters dtmf-fallback-voice command to configure the

function of switching the system service mode to voice when DTMF signals are detected
on the IP side.
Step 3 Check whether the modem parameters are the same as those in the data plan.
Run the display fax-modem parameters and display modem parameters commands to query
modem parameters.
----End
Example
Assume that:
l
The RFC2198 negotiation mode is fixedstart.
The codec mode of the VBD is G.711A.
The payload type of the VBD is static payload.
The transmission mode of the modem is transparent transmission (thoroughly).
The function of switching the system service mode to voice when DTMF signals are
detected on the IP side is disable.

huawei(config-if-sip-0)#fax-modem parameters negomode self-switch vbd-codec g.71
1a vbd-pt-type static rtp-interval 1
Issue 02 (2013-10-08)

414

Configuration Guide
huawei(config-if-sip-0)#rfc2198 set rfc2198-negomode fixedstart rfc2198-startmod

e smart2198
huawei(config-if-sip-0)#modem parameters transmode 0 dtmf-fallback-voice disable
huawei(config-if-sip-0)#display fax-modem parameters
------------------------------------------------------------------------------MGID
:0
Nego-mode
:self-switch
Rtp-interval
:10ms
Vbd-codec
:G.711A
Vbd-pt-type
:static
Vbd-attribute-type
:v.152
------------------------------------------------------------------------------huawei(config-if-sip-0)#display modem parameters
----------------------------------------------------------------------------MGID
Transmode
DTMF-Fallback-Voice
----------------------------------------------------------------------------0
Thoroughly
Disable
-----------------------------------------------------------------------------
6.9 Configuring the Security and Reliability of the Voice

Service
For the MA5616, the security configuration of the voice service includes the H.248-based, or
SIP-based device authentication configuration. The reliability configuration of the voice service
includes the dual-homing configuration and the emergency standalone configuration.
6.9.1 Configuring the Device Authentication

The purpose of authentication is to verify the validity of users and networks. The same
authentication algorithm is used on the MG and the MGC separately. Then, the calculation results
on the MG and the MGC are compared on either side. If the calculation results are the same, it
indicates that the authentication is successful. If the calculation results are different, it indicates
that the authentication fails.
Configuring the Device Authentication (Based on the H.248 Protocol)

This topic describes how to configure the device authentication parameters of the MA5616 to
prevent illegal devices from registering with the MGC when the H.248 protocol is used.
Prerequisites
l
The MG interface must be added successfully on the MA5616.
The parameters, including the encryption type, the initial key, and the DH authentication
MG ID, must be configured on the MGC. These parameters must be the same as the
parameters configured on the MA5616.
Precautions
When the MGC is Huawei SoftX3000, the authentication MG ID must be a string of more than
eight characters.
Issue 02 (2013-10-08)

415

Configuration Guide
Procedure
Step 1 In global config mode, run the interface h248 command to enter the MG interface mode.
Step 2 Run the mg-software parameter 4 command to configure the registration mode.
Step 3 Run the mg-software parameter 6 0 command to configure the MG interface to support the
device authentication.
Step 4 Run the auth command to configure the authentication MG ID and the initial key.
Step 5 Run the display auth command to query the device authentication parameters.
Step 6 Run the reset coldstart command to reset the MG interface.
----End
Example
To configure the device authentication parameters shown in the Table 6-36 for the MA5616,
do as follows:
Table 6-36 Data plan for configuring the authentication parameters (H.248)
Configuration Item
Value
MGID
Whether to use the wildcard in registration
Yes
Whether to support the device

authentication.
Yes
Authentication MG ID
MA5616
It must be the same as the configuration on the
MGC. Otherwise, the MG cannot register with
the MGC.
Initial key
Default: 0123456789ABCDEF.
It must be the same as the initial key configured
on the MGC.
------------------------------------------------Interface Id:0
para index:4
value:0
------------------------------------------------APPENDIX:
4: Whether MG uses wildcard in registration
0: Yes
1: No
Issue 02 (2013-10-08)

416

Configuration Guide
------------------------------------------------Interface Id:0
para index:6
value:0
------------------------------------------------APPENDIX:
6: Whether MG supports authentication
0: Yes
1: No
huawei(config-if-h248-0)#auth auth_mgid MA5616 initial_key 0123456789ABCDEF
huawei(config-if-h248-0)#display auth
[AUTH_PARA config]
Initial Key
: 0123456789ABCDEF
Auth MGid
: MA5616
Algorithm
: MD5
Configuring the Device Authentication (Based on the SIP Protocol)

This topic describes how to configure the authentication information for the SIP interface or a
single user of the MA5616 when the SIP protocol is used, preventing an unauthorized device
from registering with the information management system (IMS).
Prerequisites
l
The SIP interface has been added successfully on the MA5616.
The authentication user name and password have been configured on the IMS. These
parameters must be the same as the authentication user name and password configured on
the MA5616.
The authentication information can be configured for the SIP interface. The configuration
takes effect only after you run the reset command on the SIP interface.
The authentication information can be configured for a single user. The configuration takes
effect immediately after the configuration is complete.
In the actual application, whether the user uses the authentication information configured
for the SIP interface or a single user can be controlled through system parameter 81 in the
sipprofile modify command.
Configure the authentication information for the SIP interface.
Context
Procedure
1.
In the global config mode, run the interface sip command to enter the SIP interface
mode.
2.
Run the sip-auth-parameter command to configure the authentication user name and
password for an SIP interface.
3.
Run the display sip-auth command to query the authentication information of an SIP
interface.
4.
Run the reset command to reset the SIP interface.
Configure the authentication information for a single user.

1.
Issue 02 (2013-10-08)
Run the esl user command to enter the ESL user mode.
417

Configuration Guide
2.
Run the sippstnuser auth set command to configure the authentication user name
and password for a single user.
3.
Run the display sippstnuser authinfo command to query the authentication

information of a specified user.
----End
Example
l
To configure the authentication information for SIP interface 0 with the user name of
huawei.com and the password of 123456789, do as follows:
huawi(config)#interface sip 0
huawei(config-if-sip-0)#sip-auth-parameter
{ <cr>|auth-mode<K>|password-mode<K> }:password-mode
{ password-mode-value<E><password,ha1> }:password
{ <cr>|auth-mode<K> }:
Command:
sip-auth-parameter password-mode password
User Name(<=64 chars, "-" indicates deletion):huawei.com
User Password(<=64 chars, "-" indicates deletion):
The configuration will take effect after resetting the interface
The configuration will take effect after resetting the interface
To configure the authentication information for a single user on port0/3/0 with the user
name of user1.com and the password of 987654321, do as follows:
huawi(config)#esl user
huawei(config-esl-user)#sippstnuser auth set 0/3/0 telno 88442200 passwordmode
password
User Name(<=64 chars, "-" indicates deletion):user1.com
User Password(<=64 chars, "-" indicates deletion):
6.9.2 Configuring the Dual Homing

Dual-homing is a disaster recovery mechanism of emergency communication against softswitch
failure or unexpected disaster (such as fire in the equipment room, disconnection of the cable
connected to the equipment room, and abnormal power supply).
Configuring the Dual Homing (Based on the H.248 Protocol)

Based on the H.248 protocol, configuring the dual homing means registering one MA5616 with
two MGCs. When one MGC is faulty and cannot support the communication, the MA5616
automatically switches to the other MGC.
Prerequisites
l
The MGC1 and MGC2 must be configured on the attributes of the MG interface.
On the MGCs, the data for interconnecting with the MG interface must be configured.
Context
The MA5616 supports registering the MG interface with two MGCs (MGC1 and MGC2). MGC1
functions as the active MGC and MGC2 functions as the standby MGC. When MGC1 is down,
the MG automatically registers with MGC2 and works under the control of MGC2.
Issue 02 (2013-10-08)

418

Configuration Guide
Procedure
Step 1 In global config mode, run the interface h248 command to enter the MG interface mode.
Step 2 Run the mg-software parameter 2 command to configure the MG interface to support the dual
homing.
----End
Example
To configure MG interface 0 to support the dual homing, and not to automatically switch over
to the active MGC when the active MGC recovers, do as follows:
------------------------------------------------Interface Id:0
para index:2
value:1
------------------------------------------------APPENDIX:
2: Whether MG support dual-home function
0: Do not support the dual-homing
1: Support the dual-homing, but do not support the auto switchover
2: Support the dual-homing and auto switchover
Related Operation
Table 6-37 lists the related operation for configuring the dual homing when the H.248 protocol
is used.
Table 6-37 Related operation for configuring the dual homing (H.248)
To...
Run the Command...
Forcibly switch the MG to register with the

other MGC
mgc switch
Configuring the Dual Homing (Based on the SIP Protocol)

The SIP dual-homing means that the MA5616 supports the 1+1 mutual assistance mode of the
upstream PROXY, namely, the deployment in the active/standby mode. When one of the
upstream active/standby devices is faulty, the MA5616 service automatically switches to another
device, implementing the disaster recovery for the access reliability of the device when the SIP
protocol is used.
Prerequisites
On the IMS, the data for interconnecting with the SIP interface must be configured.
Issue 02 (2013-10-08)

419

Configuration Guide
Context
The MA5616 supports configuring the SIP interface on two proxy servers (Proxy 1 and Proxy
2), where, Proxy 1 functions as the active proxy server. After Proxy 1 fails, the MG can switch
to Proxy 2 to continue working.
Procedure
Step 1 In global config mode, run the interface sip command to enter the MG interface mode.
Step 2 (Optional) Run the if-sip attribute optional command to configure the proxy dual-homing
mode.
The default value is dualhome, you can modify the proxy dual-homing mode to
autoswitchover.
Step 3 Run the if-sip attribute basic command to configure the IP address of the active/standby proxy
server of the SIP interface and other mandatory attributes, including the media IP address,
signaling IP address, transfer protocol, port ID, domain name and port ID of the proxy server,
homing domain name, and profile index. The dual homing is implemented through the
configuration of the active/standby proxy server.
Step 4 Run the reset command to reset the SIP interface to validate the configuration data.
----End
Example
Assume that:
l
The media IP address is 10.10.10.13, signaling IP address is 10.10.10.13, transfer protocol

is UDP, and port ID is 5000.
The obtaining mode of the IP address of the proxy server is the IP mode, IP address 1 of
the active proxy server is 10.10.10.14, port ID of the active proxy server is 5060, IP address
1 of the standby proxy server is, 10.10.10.15, and the port ID of the standby proxy server
is 5060.
The profile index is 1.
To configure the dual homing of SIP interface 0, do as follows:

huawei(config-if-sip-0)#if-sip attribute basic media-ip 10.10.10.13
signal-ip 10.10.10.13 signal-port 5000 transfer udp primary-proxy-ip1
10.10.10.14 primary-proxy-port 5060 primary-proxy-domain proxy.domain
secondary-proxy-ip1 10.10.10.15 secondary-proxy-port 5060
{ <cr>|home-domain<K>|primary-proxy-ip2<K>|proxy-addr-mode<K>|secondary-proxy-do
main<K>|secondary-proxy-ip2<K>|server-dhcp-option<K>|sipprofile-index<K>|srvlogi
c-index<K> }:
Command:
if-sip attribute basic media-ip 10.10.10.13 signal-ip 10.10.10.13
signal-port 5000 transfer udp primary-proxy-ip1 10.10.10.14 primary-proxy-port
5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.10.10.15
huawei(config-if-sip-0)#if-sip attribute basic home-domain huawei.com sipprofileindex 1
{ <cr>|media-ip<K>|primary-proxy-domain<K>|primary-proxy-ip1<K>|primary-proxy-ip
2<K>|primary-proxy-port<K>|proxy-addr-mode<K>|secondary-proxy-domain<K>|secondar
Issue 02 (2013-10-08)

420

Configuration Guide
y-proxy-ip1<K>|secondary-proxy-ip2<K>|secondary-proxy-port<K>|server-dhcp-option
<K>|signal-ip<K>|signal-port<K>|srvlogic-index<K>|transfer<K> }:
Command:
if-sip attribute basic home-domain huawei.com sipprofile-index 1
6.9.3 Configuring the Emergency Standalone

This topic describes how to configure the emergency standalone function on the MA5616. When
the MA5616 and the MGC device fail to communicate with each other, the MA5616
independently processes the internal users connecting to the same MG interface; therefore, the
internal users can make calls normally without the control of MGC.
Prerequisites
l
The H.248 protocol must be used in the system.
The media IP address must exist in the IP address pool.
The voice users must be configured on the MG interface and the users can call each other
successfully.
If the device cannot communicate with the MG, run the system parametres 5 command
to configure the media stream forwarding mode as the mode in which the media stream is
forwarded within the device.
The phone number of the MG user is configured to be the same as the phone number on
the MGC.
When the MG interface works in the emergency standalone state, only the internal users
on the MG interface can communicate with each other properly.
To keep the user phone number in the emergency standalone state consistent with the phone
number in the normal condition, configure the phone number on the MG to be the same as
the phone number on the MGC.
Context
Procedure
Step 1 Run the mg-software parameter 11 1 command to configure the MG interface to support the
emergency standalone function.
Step 2 Run the digitmap set inner command to configure the digitmap for the internal calls.
Step 3 (Optional) Run the standalone parameters command to configure the parameters of the
emergency standalone timers.
NOTE
In general, the default parameters of the emergency standalone timers are used, and you need not configure
them.
----End
Issue 02 (2013-10-08)

421

Configuration Guide
Example
To configure MG0 to support the emergency standalone function and configure the digitmap
for internal calls as 8764XXXX, do as follows:
------------------------------------------------Interface Id:0
------------------------------------------------APPENDIX:
11: Stand alone flag
0: None
1: Inner
2: Emergency
3: Both
huawei(config-if-h248-0)#digitmap set inner 8764XXXX
----------------------------------------------------------------------------Inner digitmap
: 8764XXXX
: ----------------------------------------------------------------------------NOTE
The configured digitmap corresponds to the user phone number.
Issue 02 (2013-10-08)

422

Configuration Guide
7 Configuring the Ethernet OAM
Configuring the Ethernet OAM
About This Chapter

Operation, administration, and maintenance (OAM) refers to a method of monitoring and
diagnosing network faults. The Ethernet OAM feature includes two sub-features, namely,
Ethernet CFM OAM and Ethernet EFM OAM.
7.1 Configuring the Ethernet CFM OAM
On the Ethernet network, Ethernet connectivity fault management (CFM) OAM is defined as
connectivity fault management in IEEE 802.1ag to implement the OAM function of connectivity
detection on the Ethernet bearer network. Ethernet CFM OAM is applicable to the end-to-end
(E2E) network with a large scale and it is the network-level OAM.
7.2 Configuring the Ethernet EFM OAM
Ethernet in the First Mile (EFM) OAM is defined in IEEE 802.3ah to make the Ethernet physicallayer specifications in respect of the user access part and the Ethernet OAM in respect of the
access part. Ethernet EFM OAM is used for the link detection of the last mile and it is the linklevel OAM.
Issue 02 (2013-10-08)

423

Configuration Guide
7.1 Configuring the Ethernet CFM OAM

On the Ethernet network, Ethernet connectivity fault management (CFM) OAM is defined as
connectivity fault management in IEEE 802.1ag to implement the OAM function of connectivity
detection on the Ethernet bearer network. Ethernet CFM OAM is applicable to the end-to-end
(E2E) network with a large scale and it is the network-level OAM.
Prerequisites
l
The OLT must support the Ethernet CFM OAM function.
Context
OAM is a key method of reducing network maintenance cost.
Ethernet is a widely used local area network (LAN) technology. It provides rich bandwidth,
features low cost, and supports plug-and-play and multipoint operations. As the Ethernet
technology is developing from carriers' networks to metropolitan area networks (MANs) and
wide area networks (WANs), the network management and maintenance are increasingly
important. Currently, however, Ethernet does not support carrier-class management, and thus
L2 network faults cannot be detected on Ethernet networks.
Ethernet CFM OAM is an E2E fault detection technology, which can be used to monitor,
diagnose, and troubleshoot the Ethernet.
Networking
Figure 7-1 shows the example network of the Ethernet CFM OAM function.
Figure 7-1 Example network of the Ethernet CFM OAM function
Router
ONU_A
ONU_B
Procedure
Run the vlan command to create a VLAN that is associated with the object managed by a
maintenance association (MA).
Each MA corresponds to one VLAN. The Ethernet CFM checks the connectivity for each MA.
Issue 02 (2013-10-08)

424

Configuration Guide
Step 2 Configure a maintenance domain (MD).

An MD can be a network or a part of a network on which the Ethernet CFM is performed. All
the MDs are managed by a unified Internet service provider (ISP).
l Run the cfm md mdindex name-format { no-name | dns-name dns-name | mac-integer
mac-address | string string } level level [ mhf-creation { no-mhf | default-mhf | explicitmhf } ] command to create an MD.
l Run the display cfm md command to query the configuration information about an MD.
Step 3 Configure an MA.
An MA is a part of an MD. An MD can be divided into one or more MAs. Each MA corresponds
to one VLAN. The Ethernet CFM checks the connectivity for each MA.
l Run the cfm ma command to create an MA and configure the parameters of the MA.
l Run the cfm ma mdindex/maindex vlan vlanid command to configure the VLAN associated
with an MA.
l Run the cfm ma mdindex/maindex meplist mepid command to configure the maintenance
end point (MEP) list of an MA.
l Run the display cfm ma command to query the configuration information about an MA.
Step 4 Configure an MEP.
An MEP is the end point of a maintenance channel. Ethernet OAM tests the link connectivity
by using the MEPs on the two ends of a maintenance channel.
Run the cfm mep command to create an MEP.
NOTE
When configuring an MEP, note that the objects managed by the MEP are in two directions, namely, up and
down.
l Up refers to the direction facing packet forwarding at the device layer. That is, packets are forwarded through
the device.
l Down refers to the reverse direction of the up direction. That is, packets are directly forwarded through the
MEP port, instead of being forwarded through the device.
Step 5 Enable the local CFM function globally.

Run the cfm enable function to enable the local Ethernet CFM OAM function globally.
By default, the Ethernet CFM OAM function is disabled globally.
Step 6 Enable the remote CFM function globally.
Run the cfm remote-mep-detect enable function to enable the remote Ethernet CFM OAM
function globally.
By default, the remote Ethernet CFM OAM function is disabled globally.
Step 7 Query the configuration result.
l Run the display cfm command to query the configuration information about the CFM
globally.
l Run the display cfm mep command to query the configuration information about an MEP.
----End
Issue 02 (2013-10-08)

425

Configuration Guide
Example
Assume that:
l
ONU_A: VLAN 10 is associated with the MA; the MEP port is 0/0/0; the local MEP is
0/0/1; the remote MEP is 0/0/2; the name of the object managed by the MA is huawei-1;
the name of the object managed by the MD is huawei; the level of the object managed by
the MD is 7.
ONU_B: VLAN 10 is associated with the MA; the MEP port is 0/0/0; the local MEP is
0/0/2; the remote MEP is 0/0/1; the name of the object managed by the MA is huawei-1;
the name of the object managed by the MD is huawei; the level of the object managed by
the MD is 7.
Configure ONU_A
//Create a VLAN that is associated with the MA.
huawei(config)#cfm md 0 name-format string huawei level 7
huawei(config)#cfm ma 0/0 name-format string huawei-1
huawei(config)#cfm ma 0/0 vlan 10
//Configure the VLAN to be associated with the
MA.
huawei(config)#cfm ma 0/0 meplist 1
//Configure the MEP list of the MA.
huawei(config)#cfm mep 0/0/1 direction down port 0/0/0
huawei(config)#cfm enable
//Enable the local CFM function globally.
huawei(config)#cfm remote-mep-detect enable
//Enable the remote CFM function.
huawei(config)#save
To query the configuration information about the MA, do as follows:

huawei(config)#display cfm ma 0/0
----------------------------------------------------------------------MA
: 0/0
MA NameType
: string
MA Name
: huawei-1
MA CC Interval
: 1m
MA Remote-mep-detect : enable
MA VlanID
: 10
//VLAN 10 associated with the MA.
MHF Creation
: defer-mhf
MEP List
: 1,2
-----------------------------------------------------------------------
To query the configuration information about the MD, do as follows:

huawei(config)#display cfm md 0
----------------------------------------------------------------------MD
: 0
MD NameType : string
MD Name
: huawei
MD Level
: 7
MHF Creation : no-mhf
-----------------------------------------------------------------------
To query the configuration information about the MEP, do as follows:

huawei(config)#display cfm mep mdindex/maindex/mepid 0/0/1
----------------------------------------------------------------------MEP
: 0/0/1
MEP Direction
: down
MEP Port
: 0/0/0
VLAN Tag1
: VLAN Tag2
: MEP Admin Status
: enable
MEP Run Status
: up
MEP CC Status
: enable
MEP Priority
: 7
MEP Alarm Status
: remoteCCM
Issue 02 (2013-10-08)

426

Configuration Guide
Alarm lowest priority: 2

Alarm Time
: 2500(ms)
Reset Time
: 10000(ms)
MEP IfType
: port
Remote MEP ID/MAC
:
-----------------------------------------------------------------------
Configure ONU_B
//Create a VLAN that is associated with the MA.
huawei(config)#cfm md 0 name-format string huawei level 7
huawei(config)#cfm ma 0/0 name-format string huawei-1
huawei(config)#cfm ma 0/0 vlan 10
huawei(config)#cfm mep 0/0/2 direction down port 0/0/0
huawei(config)#cfm enable
huawei(config)#cfm remote-mep-detect enable
huawei(config)#save
7.2 Configuring the Ethernet EFM OAM

Ethernet in the First Mile (EFM) OAM is defined in IEEE 802.3ah to make the Ethernet physicallayer specifications in respect of the user access part and the Ethernet OAM in respect of the
access part. Ethernet EFM OAM is used for the link detection of the last mile and it is the linklevel OAM.
Prerequisites
l
The OLT must support the Ethernet EFM OAM function.
Context
OAM is a key method of reducing network maintenance cost.
Ethernet EFM OAM is defined in IEEE 802.3ah Clause 57 and it is a key component of Ethernet
OAM. Ethernet EFM OAM provides a mechanism for monitoring links, such as remote defect
indication (RDI) and remote loopback control. It is an L2 mechanism, as a complement to the
higher layer applications.
NOTE
The CCUC and CCUE control board supports this function and the CCUB control board does not support
this function.
Networking
Figure 7-2 shows the example network of the Ethernet EFM OAM function.
Issue 02 (2013-10-08)

427

Configuration Guide
Figure 7-2 Example network of the Ethernet EFM OAM function
Router
ONU_A
ONU_B
Procedure
Step 1 Run the efm oam mode command to configure the Ethernet EFM OAM mode of the port.
l The default Ethernet EFM OAM mode of the port is the active mode.
l After the Ethernet EFM OAM function is enabled on the port, the mode of the port cannot
be changed.
l When the Ethernet EFM OAM mode of both the local and peer devices is the passive mode,
the Ethernet EFM OAM function cannot be enabled. The Ethernet EFM OAM function can
be enabled only when the Ethernet EFM OAM mode of the device at one end is the active
mode.
Step 2 Run the efm oam { frameid/slotid | frameid/slotid/portid } enable command to enable the
Ethernet EFM OAM function on the port.
By default, the Ethernet EFM OAM function on the port is disabled.
Step 3 (Optional) Run the efm loopback command to configure the start, end, and control parameters
for the Ethernet EFM OAM loopback on the port.
l By default, the Ethernet EFM OAM loopback is not performed.
l After the Ethernet EFM OAM loopback is started, all the services are interrupted.
Step 4 Run the efm error-frame command to set error frame parameters and the status of the error
frame alarm function. In this manner, the link signals and data quality can be monitored.
Step 5 Query the configuration information about the Ethernet EFM OAM function.
l Run the display efm oam status command to query the status of the Ethernet EFM OAM
function.
l Run the display efm oam event config command to query the parameters of the Ethernet
EFM OAM event.
----End
Example
l
Issue 02 (2013-10-08)
ONU__A: The Ethernet EFM OAM function is enabled; the Ethernet EFM OAM mode is
in the active mode; the error frame alarm function is enabled; the local error frame window
is 1; the error frame threshold is 1.
428

Configuration Guide
ONU__B: The Ethernet EFM OAM function is enabled; the Ethernet EFM OAM mode is
in the passive mode; the error frame alarm function is enabled; the local error frame window
is 1; the error frame threshold is 1.
Configure ONU__A:
huawei(config)#efm
huawei(config)#efm
huawei(config)#efm
huawei(config)#efm
huawei(config)#efm
oam mode 0/0/1 active

oam 0/0/1 enable
error-frame 0/0/1 notification enable
error-frame 0/0/1 period 1
error-frame 0/0/1 threshold 1
Run the display efm oam status command to query the status of the Ethernet EFM OAM function.
huawei(config)#display efm oam status
{ frameid/slotid/portid<S><Length 1-15> }:0/0/1
{ local<K>|remote<K> }:local
Command:
display efm oam status 0/0/1 local
Admin Status
: Enable
Operation Status
: LinkFault
OAM Mode
: Active //The local Ethernet OAM mode is the
active mode.
Max OAM PDU Size
: 1514
Stable & Evaluation
: 1
Configuration Revision
: 0
Multiplexer Action
: Forward
Parser Action
: Forward
Unidirectional Support
: No
Loopback Support
: Yes
Event Support
: Yes
Variable Support
: No
Run the display efm oam event config command to query the parameters of the Ethernet EFM
OAM event.
huawei(config)#display efm oam event config
Command:
display efm oam event config 0/0/1
Errored Symbol Period Event
:Disable
Errored Symbol Period Event Window
:Errored Symbol Period Event Threshold
:Errored Frame Event
:Enable //The error frame alarm
Errored Frame Event Window
:1
//The error frame window
is 1.
Errored Frame Event Threshold
:1
//The error frame threshold
is 1.
Errored Frame Period Event
:Disable
Errored Frame Period Event Window
:Errored Frame Period Event Threshold
:Errored Frame Seconds Summary Event
:Disable
Errored Frame Seconds Summary Event Window
:Errored Frame Seconds Summary Event Threshold :Link Fault Event
:Enable
Dying Gasp Event
:Disable
Critical Link Event
:Disable
Configure ONU__B:
huawei(config)#efm oam mode 0/0/1 passive
huawei(config)#efm oam 0/0/1 enable
huawei(config)#efm error-frame 0/0/1 notification enable
Issue 02 (2013-10-08)

429

Configuration Guide
huawei(config)#efm error-frame 0/0/1 period 1

huawei(config)#efm error-frame 0/0/1 threshold 1
Run the display efm oam status command to query the status of the Ethernet EFM OAM function.
huawei#display efm oam status
{ local<K>|remote<K> }:local
//Query the local Ethernet OAM status. If you need
to query the remote Ethernet OAM status, select remote.
Command:
display efm oam status 0/0/1 local
Admin Status
: Enable
//The Ethernet OAM function is
enabled.
Operation Status
: Operational
OAM Mode
: Passive //The local Ethernet OAM mode is the
passive mode.
Max OAM PDU Size
: 1514
Stable & Evaluation
: 2
Configuration Revision
: 0
Multiplexer Action
: Forward
Parser Action
: Forward
Unidirectional Support
: No
Loopback Support
: No
Event Support
: Yes
Variable Support
: No
Run the display efm oam event config command to query the parameters of the Ethernet EFM
OAM event.
huawei(config)#display efm oam event config 0/0/1
Errored Symbol Period Event
:Disable
Errored Symbol Period Event Window
:Errored Symbol Period Event Threshold
:Errored Frame Event
:Enable //The error frame alarm
Errored Frame Event Window
:1
//The error frame window
is 1.
Errored Frame Event Threshold
:1
//The error frame threshold
is 1.
Errored Frame Period Event
:Disable
Errored Frame Period Event Window
:Errored Frame Period Event Threshold
:Errored Frame Seconds Summary Event
:Disable
Errored Frame Seconds Summary Event Window
:Errored Frame Seconds Summary Event Threshold :Link Fault Event
:Enable
Dying Gasp Event
:Disable
Critical Link Event
:Disable
Issue 02 (2013-10-08)

430

Configuration Guide
8 Configuring Network Protection
Configuring Network Protection
About This Chapter

The MA5616 provides a network protection mechanism to improve the system reliability. The
mechanism maximally secures the network and services of carriers and minimizes loss if an
exception occurs.
8.1 Configuring the MSTP
This topic describes how to configure MSTP on the MA5616.
8.2 Configuring the Link Aggregation of Uplink Ethernet Port
Port aggregation means aggregating the two uplink GE ports on the MA5616 to increase the
bandwidth through load balancing. When a certain aggregated GE port or GE link fails, data is
transmitted through another GE port. Therefore, the reliability of the transmission is enhanced.
Issue 02 (2013-10-08)

431

Configuration Guide
8.1 Configuring the MSTP

This topic describes how to configure MSTP on the MA5616.
Context
l
MSTP applies to a redundant network. It makes up for the drawback of STP and RSTP.
MSTP makes the network converge fast and the traffic of different VLANs distributed
along their respective paths, which provides a better load-sharing mechanism.
MSTP trims a loop network into a loop-free tree network. It prevents the proliferation and
infinite cycling of the packets in the loop network. In addition, MSTP provides multiple
redundant paths for VLAN data transmission to achieve the load-sharing purpose.
Figure 8-1 shows the flowchart for configuring the MSTP.
Figure 8-1 Flowchart for configuring the MSTP
Issue 02 (2013-10-08)

432

Configuration Guide
Procedure
Step 1 Enabling the MSTP function.
l By default, the MSTP function is disabled.
l After the MSTP function is enabled, the device determines whether it works in STP
compatible mode or MSTP mode based on the configured protocol.
l After the MSTP function is enabled, MSTP maintains dynamically the spanning tree of the
VLAN based on the received BPDU packets. After the MSTP function is disabled, if the
transparent transmission of BPDU packets is disabled, the MSTP device becomes a
transparent bridge and does not maintain the spanning tree.
1.
Run the stp enable command or the stp port frameid/slotid/portid enable command to
enable the MSTP function of the bridge or the port.
2.
Run the display stp command or the display stp port command to query the MPLS state
of the bridge or the port.
Step 2 Configuring the MST region name.

1.
Run the stp region-configuration command to enter MST region mode.
2.
Run the region-name command to configure the name of the MST region.
3.
Run the check region-configuration command to query the parameters of the current MST
region.
Step 3 Configuring the MSTP instance.

The MSTP protocol configures the VLAN mapping table (mapping between the VLAN and the
spanning tree), which maps the VLAN to the spanning tree.
l By default, all VLANs are mapped to CIST, that is, instance 0.
l One VLAN can be mapped to only one instance. If you re-map a VLAN to another instance,
the original mapping is disabled.
l A maximum of 10 VLAN sections can be configured for an MSTP instance.
1.
Run the instance instance-id vlan command to map the specified VLAN to the specified
MSTP instance.
2.
Run the check region-configuration command to query the parameters of the current MST
region.
Step 4 Activating the configuration of the MST region.

1.
Run the active region-configuration command to activate the configuration of the MST
region.
2.
Run the display stp region-configuration command to query the effective configuration
of the MST region.
3.
Run the quit command to quit MST region mode.
Step 5 Other optional configurations.

l Setting the priority of the device in the specified spanning tree instance.
Run the stp priority command to set the priority of the device in the specified spanning
tree instance.
Issue 02 (2013-10-08)

433

Configuration Guide
Run the display stp command to query the MSTP configuration of the device.
l Setting the MST region parameters.
Run the stp md5-key command to set the MD5-Key for the MD5 encryption algorithm
configured on the MST region.
In the MSTP region mode, run the vlan-mapping module command to map all VLANs
to the MSTP instances by modular arithmetic.
In the MSTP region mode, run the revision-level command to set the MSTP revision
level of the device.
Run the reset stp region-configuration command to restore the default settings to all
parameters of the MST region.
l Specifying the device as a root bridge or a backup root bridge.
Run the stp root command to specify the device as a root bridge or a backup root bridge.
l Setting the time parameters of the specified network bridge.
Run the stp timer forward-delay command to set the Forward Delay of the specified
network bridge.
Run the stp timer hello command to set the Hello Time of the specified network bridge.
Run the stp timer max-age command to set the Max Age of the specified network bridge.
Run the stp time-factor command to set the timeout time factor of the specified network
bridge.
l Setting the parameters of the specified port.
Run the stp port frameid/slotid/portid transmit-limit command to set the number of
packets transmitted by the port within the Hello Time.
Run the stp port frameid/slotid/portid edged-port enable command to set the port as an
edge port.
Run the stp port frameid/slotid/portid cost command to set the path cost of a specified
port.
Run the stp port frameid/slotid/portid port-priority command to set the priority of the
specified port.
Run the stp port point-to-point command to set whether the link that is connected to the
port is a point-to-point link.
l Configuring the device protection function.
Run the stp bpdu-protection enable command to enable the BPDU protection function
of the device.
Run the stp port frameid/slotid/portid loop-protection enable command to enable the
loop protection function of the port.
Run the stp port frameid/slotid/portid root-protection enable command to enable the
root protection function of the port.
l Setting the maximum number of hops of the MST region.
Run the stp max-hops command to set the maximum number of hops of the MST region.
l Setting the diameter of the switching fabric.
Run the stp bridge-diameter command to set the diameter of the switching fabric.
l Setting the calculation standard for the path cost.
Issue 02 (2013-10-08)

434

Configuration Guide
Run the stp pathcost-standard command to set the calculation standard for the path cost.
l Clear the MSTP protocol statistics.
Run the reset stp statistics command to clear the MSTP protocol statistics.
----End
Example
Assume that:
l
MSTP function: enabled
MST region name: hwrg1
VLAN 2-VLAN 10 and VLAN 12-VLAN 16 are mapped to MSTP instance 1.
Priority of the device in a specified spanning tree instance: 0.
Maximum number of hops in the MST region: 10
Diameter of the switching network: 6
BPDU protection function: enabled
To configure the MSTP with these parameters, do as follows:

huawei(config)#stp enable
huawei(config)#stp region-configuration
huawei(stp-region-configuration)#region-name hwrg1
huawei(stp-region-configuration)#instance 1 vlan 2 to 10 12 to 16
huawei(stp-region-configuration)#active region-configuration
huawei(stp-region-configuration)#quit
huawei(config)#stp instance 1 priority 0
huawei(config)#stp max-hops 10
huawei(config)#stp bridge-diameter 6
huawei(config)#stp bpdu-protection enable
8.2 Configuring the Link Aggregation of Uplink Ethernet

Port
Port aggregation means aggregating the two uplink GE ports on the MA5616 to increase the
bandwidth through load balancing. When a certain aggregated GE port or GE link fails, data is
transmitted through another GE port. Therefore, the reliability of the transmission is enhanced.
Prerequisites
l
The network device and the line must be normal.
The VLAN of the interface on the upper-layer device of the MA5616 must be consistent
with the VLAN configured for the uplink port on the MA5616.
Ensure that the configurations of the Ethernet port attributes on two aggregation ports are
the same.
No static MAC address is allowed on the aggregation ports. You can run the display macaddress command to query the configuration.
The ports to be aggregated cannot be destination mirroring ports.
Context
Issue 02 (2013-10-08)

435

Configuration Guide
Procedure
Step 1 Configure the Ethernet port aggregation.
Run the link-aggregation command to configure the Ethernet port aggregation.
Step 2 Configure the switchback function for the system to switch back from the Link Aggregation
Control Protocol (LACP) standby link to the active link.
Run the lacp preempt enable command to set the LACP to priority preemption mode. After
the setting, when the system is configured with the active and standby links, the system
automatically switches back to the active link if the active link recovers from a fault.
Step 3 Query the information about the aggregation group.
Run the display link-aggregation all command to query the type, number and working mode
of the aggregated Ethernet ports.
If the aggregation group is a static Link Aggregation Control Protocol (LACP) group, run the
display lacp link-aggregation portframe/slot/port command to query the type, role, and status
of an aggregated port.
----End
Result
In ETH mode, the PC can still access the Internet through PPPoE dialup after you run the
shutdown command to deactivate port 0/0/0 or 0/0/1.
Example
Assume that two uplink ports 0/0/0 and 0/0/1 on the same control board of the MA5616 is to be
configured as an aggregation group, and each port sends packets according to the source MAC
address in the static LACP aggregation mode. To perform the preceding configuration, do as
follows:
huawei(config)#link-aggregation 0/0 0-1 ingress workmode lacp-static
huawei(config)#lacp preempt enable
huawei(config)#display link-aggregation all
------------------------------------------------------------------------Master port Link aggregation mode Port NUM Work mode Max link number
------------------------------------------------------------------------0/0/0
ingress
2 lacp-static
------------------------------------------------------------------------Total: 1 link aggregation(s)
Issue 02 (2013-10-08)

436

Configuration Guide
9 Configuration Example of Services on the MA5616

Through GE Upstream Transmission
Configuration Example of Services on the
MA5616 Through GE Upstream Transmission
About This Chapter

This topic describes how to configure Internet access service, multicast service, voice service,
and triple play service on the MA5616 on different networks.
9.1 Configuration Example of the xDSL Internet Access Service
This topic describes how to configure the xDSL Internet access service in the PPPoE, IPoE,
PPPoA and IPoA modes.
9.2 Configuration Example of the Multicast Service (Multicast VLAN Mode)
This topic describes how to configure the multicast service on the MA5616 in multicast VLAN
mode.
9.3 Configuration Example of the VoIP Service
This topic describes how to configure the VoIP service based on the H.248 or SIP protocol.
9.4 Configuration Example of the VAG Service
The purpose of configuring virtual access gateways (VAGs) is to simulate multiple AGs by using
one AG and rent MG interfaces to different carriers, increasing the usage rate and flexibility of
the device.
9.5 Configuration Example of the VLAN Stacking Wholesale Service
This topic describes the VLAN stacking wholesale service and how to configure the VLAN
stacking wholesale service on the MA5616.
9.6 Configuration Example of the QinQ VLAN Private Line Service
This topic describes how to configure the private line service based on the QinQ feature. A
virtual local area network (VLAN) packet with the QinQ attribute has VLAN tags of two layers,
inner VLAN tag from the private network and outer VLAN tag from the MA5616. With the two
VLAN tags, a Layer 2 virtual private network (VPN) tunnel is formed between private
networks.This can achieve the interconnection and secure communication among branches in
different areas within the enterprise private network.
9.7 Configuring the Triple Play Service
Issue 02 (2013-10-08)

437

Configuration Guide

This topic describes the triple play service and how to configure the triple play service on the
MA5616 on the GE upstream transmission network.
Issue 02 (2013-10-08)

438

Configuration Guide

9.1 Configuration Example of the xDSL Internet Access

Service
This topic describes how to configure the xDSL Internet access service in the PPPoE, IPoE,
PPPoA and IPoA modes.
9.1.1 Configuration Example of the PPPoE xDSL Internet Access

Service
On a fiber to the x (FTTx) network, if the MA5616 provides x digital subscriber line (xDSL)
services for broadband users and the users connect to the Internet in point-to-point over Ethernet
(PPPoE) mode, you can configure the MA5616 by referring to this topic to provide users with
high-speed Internet (HIS) services. In this service, the MA5616 functions as an optical network
unit (ONU). PPPoE is a common mode for Internet access. In this mode, PPPoE users must be
authenticated using Authentication, Authorization and Accounting (AAA) policies before
connecting to the Internet.
l
Users connect to the Internet in PPPoE mode.
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.
Each subscriber has a unique account. The broadband remote access server (BRAS)
manages and authenticates subscribers. The Policy Information Transfer Protocol (PITP)
P mode, which is also known as PPPoE+ mode, is used to protect user accounts against
theft and roaming.
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 9-1 shows an example network of the PPPoE xDSL Internet access service.
Figure 9-1 Example network of the PPPoE xDSL Internet access service
Issue 02 (2013-10-08)

439


Configuration Guide
Prerequisite
l
The BRAS implements the Authentication, Authorization and Accounting (AAA) function.
The user information, including the user name and password for the Internet access, has
been configured on the BRAS.
Data Plan
Table 9-1 provides the data plan for the PPPoE xDSL Internet access service.
Table 9-1 Data plan for the PPPoE xDSL Internet access service
Device
Configuration
Item
Data
MA5616
Port
Uplink port: 0/0/1

User ports:
l ADSL2+ port: 0/2/0
l SHDSL port: 0/4/0
l VDSL port: 0/1/0
Service VLAN
Outer VLAN tag: 50, Inner VLAN tag: 10

VLAN type: smart (default)
VLAN attribute: stacking VLAN
Traffic profile
Profile ID: 2
Committed rate: 2 Mbit/s
Priority: 0
Upper
layer
device
VLAN
User-side VLAN: 50, which is the same as the service VLAN

configured on the MA5616
The upper layer device forwards the user packets to a
specified ISP BRAS based on the outer VLAN tags from the
MA5616.
Procedure
Step 1 Configure a VLAN.
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.
Issue 02 (2013-10-08)

440

Configuration Guide

Step 2 Configure upstream ports.

Add upstream ports 0/0/1 and 0/0/0 to VLAN 50. Two ports are added for the purpose of port
aggregation.
huawei(config)#port vlan 50 0/0 0-1
To aggregate the two upstream ports as one aggregation group, set the packet forwarding mode
of the aggregation group to ingress, and set the aggregation group to work in the LACP static
mode, do as follows:
huawei(config)#link-aggregation 0/0 0 0/0 1 ingress workmode lacp-static
NOTE
The aggregated ports must meet the following requirements:

l The ports must work in the full-duplex mode;
l The port rates must be the same and the rate of an electrical port must not be of the auto-negotiation
type;
l The attributes of the ports, such as the VLAN, must be the same;
l One port can belong to only one aggregation group;
l The port must not be a mirroring destination port;
l The start port ID must be smaller than the end port ID.
Step 3 In ADSL access mode, follow this step.

This step uses NGADSL mode as an example. For details about how to configure an ADSL
profile in normal ADSL mode, see Configuring ADSL2+ Profiles (in Normal Mode). For
details about how to configure an ADSL profile in ADSL TR165 mode, see 4.1.4 Configuring
xDSL Profiles (TR165 Mode).
1.
Configure an ADSL2+ profile. For details, see Configuring the ADSL2+ Profile
(NGADSL Mode). Here, 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.
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>|toindex<K> }:
Command:
display traffic table ip from-index
0
Issue 02 (2013-10-08)

441

Configuration Guide

--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
The service requires that the user access rate be 2048 kbit/s. The query result shows that
traffic profile 2 (for inbound and outbound rate limitation) meets the requirement.
NOTE
l If a matched traffic profile is not available in the system, run the traffic table ip command to configure
a new traffic profile.
l On the MA5616, 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.
4.
Run the service-port command to create a service port, adopt traffic profile 2, 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 multi-service
user-vlan untagged inbound traffic-table index 2 outbound traffic-table index
2
huawei(config)#service-port desc 1 description Vlanid:50/adsl/vpi:1vci:39
Step 4 In the SHDSL access mode, follow this step.

1.
Configure an SHDSL profile. For details, see 4.1.2 Configuring the SHDSL Profile. 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/4/0, 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.
Issue 02 (2013-10-08)

442

Configuration Guide

huawei(config-if-shl-0/4)#quit
3.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
NOTE
l On the MA5616, the user access rate can be limited by either a traffic profile or an SHDSL line profile.
4.
S-VLAN ID to 50. Set the SHDSL channel mode to PTM, and create service port 2 on
SHDSL port 0/4/0. 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/4/0 multi-service uservlan untagged inbound traffic-table index 2 outbound traffic-table index 2
huawei(config)#service-port desc 2 description Vlanid:50/shdsl/vpi:1vci:39
Step 5 In the VDSL access mode, follow this step.

This step uses the VDSL normal mode as an example. For details about how to configure a
VDSL profile in VDSL TI mode, see Configuring the VDSL2 Profile (TI Mode). For details
about how to configure a VDSL profile in VDSL TR165 mode, see 4.1.4 Configuring xDSL
Profiles (TR165 Mode).
Issue 02 (2013-10-08)

443

Configuration Guide
1.

Configure a VDSL profile. For details, see Configuring the VDSL2 Profile (TR129
Mode). 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 interleaved-delay
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
2.
Activate VDSL port 0/1/0, 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 deactivate
the port.
huawei(config-if-vdsl-0/1)#quit
3.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
The service requires the user access rate be 2048 kbit/s. The query result shows that traffic
profile 2 (for inbound and outbound rate limitation) meets the requirement.
Issue 02 (2013-10-08)

444

Configuration Guide

NOTE
l On the MA5616, the user access rate can be limited by either a traffic profile or a VDSL line profile.
4.
S-VLAN ID to 50. Set the VDSL channel mode to PTM, and create service port 3 on VDSL
port 0/1/0. To facilitate the maintenance of the service port, also configure the service port
description.
huawei(config)#service-port 3 vlan 50 vdsl mode ptm 0/1/0 multi-service uservlan untagged inbound traffic-table index 2 outbound traffic-table index 2
huawei(config)#service-port desc 3 description Vlanid:50/vdsl
Step 6 Configure the user account security.

The PITP P mode can be enabled to protect user accounts against theft and roaming. The RAIO
mode can be customized according to actual requirements. Here, the cntel is considered as an
example.
huawei(config)#raio-mode cntel pitp-pmode
NOTE
For details about the PITP configuration for user account security, see 3.10.1 Configuring Anti-Theft and
Roaming of User Account Through PITP.

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: Log in to the network rate test website and test the rate. The upstream and
downstream rates must be the same as these of the provided service.
Configuration File
Configuration File in the ADSL access mode:
vlan 50 smart
vlan attrib 50 stacking
vlan service-profile profile-id 5
forwarding vlan-connect
commit
quit
vlan bind service-profile 50 profile-id 5
port vlan 50 0/0 0
port vlan 50 0/0 1
link-aggregation 0/0 0 0/0 1 ingress workmode lacp-static
interface adsl 0/2
deactivate 0
activate 0 template-index 1
alarm-config 0 1
Issue 02 (2013-10-08)

445

Configuration Guide

quit
service-port 1 vlan 50 adsl 0/2/0 vpi 1 vci 39 inbound traffic-table index 2
outbound traffic-table index 2
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
commit
quit
port vlan 50 0/0 0
port vlan 50 0/0 1
shdsl line-profile quickadd 3 ptm rate 512 2048
interface shl 0/4
activate 0 3
alarm-config 0 1
quit
service-port 2 vlan 50 shdsl mode ptm 0/4/0 inbound traffic-table index 2 outbound
traffic-table index 2
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
commit
quit
port vlan 50 0/0 0
port vlan 50 0/0 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
vdsl line-template quickadd 3 line 3 channel1 3 100 100
interface vdsl 0/1
deactivate 0
alarm-config 0 1
quit
service-port 3 vlan 50 vdsl mode ptm 0/1/0 inbound traffic-table index 2 outbound
service-port desc 3 description Vlanid:50/vdsl/vpi:1vci:39/stacking
pitp enable pmode
save
Issue 02 (2013-10-08)

446

Configuration Guide

9.1.2 Configuration Example of the IPoE xDSL Internet Access

Service
services for broadband users and the users connect to the Internet in IP over Ethernet (IPoE)
mode, you can configure the MA5616 by referring to this topic to provide users with high-speed
Internet (HSI) services. In this service, the MA5616 functions as an optical network unit (ONU).
IPoE is mostly used on a private line network to meet operators' IP access requirements. In this
mode, broadband users are authenticated in DHCP Option82 method.
l
The ONU 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.
Users connect to the Internet in IPoE mode. The account authentication is implemented
through the DHCP option 82 field to prevent theft and roaming of the user accounts. And
the user IP addresses are obtained using the Dynamic Host Configuration Protocol (DHCP)
to ensure the security of the user accounts.
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 service access rate is 2048 kbit/s.
Dual GE ports are adopted for upstream transmission to ensure reliability. Link aggregation
is configured for the two upstream ports.
Figure 9-2 shows an example network of the IPoE xDSL Internet access service.
Figure 9-2 Example network of the IPoE xDSL Internet access service
Prerequisite
The user PC can obtain an IP address from the DHCP server.
Context
Data Plan
Table 9-2 provides the data plan for the IPoE xDSL Internet access service.
Issue 02 (2013-10-08)

447


Configuration Guide
Table 9-2 Data plan for the IPoE xDSL Internet access service
Device
Configuration
Item
Data
MA5616
Port
Uplink port: 0/0/1

User ports:
l ADSL2+ port: 0/2/0
l SHDSL port: 0/4/0
l VDSL port: 0/1/0
Service VLAN

Traffic profile
Profile ID: 2
Priority: 0
Upper
layer
device
VLAN

MA5616.
Procedure

aggregation.
Issue 02 (2013-10-08)

448

Configuration Guide

NOTE

type;

1.
(NGADSL Mode). Here, 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
In the ADSL access mode, bind the default ADSL2+ line template 1 and ADSL2+ alarm
template 1 to ADSL port 0/2/0.
3.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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 tag-
Issue 02 (2013-10-08)

449


Configuration Guide
pri
4 8192
264144
16384
528288
4 -
tag-
5 16384
526288
32768
1024000
4 -
tag-
6 off
off
off
off
0 -
tag-
pri
pri
pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
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.
user-vlan untagged inbound traffic-table index 2 outbound traffic-table index
2
huawei(config)#service-port desc 1 description Vlanid:50/adsl/vpi:1vci:39
Step 4 In the SHDSL access mode, follow this step.

1.
Configure an SHDSL profile. For details, see 4.1.2 Configuring the SHDSL Profile. 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/4/0, 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.
3.
0
Command:
0
---------------------------------------------------------------------------
Issue 02 (2013-10-08)

450


Configuration Guide
TID CIR
Policy
(kbps)
(bytes)
CBS
PIR
(bytes)
(kbps)
PBS
Pri Copy-policy
Pri-
--------------------------------------------------------------------------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
NOTE
4.
S-VLAN ID to 50. Set the SHDSL channel mode to PTM, and create service port 2 on
SHDSL port 0/4/0. 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/4/0 multi-service uservlan untagged inbound traffic-table index 2 outbound traffic-table index 2
huawei(config)#service-port desc 2 description Vlanid:50/shdsl/vpi:1vci:39
Step 5 In the VDSL access mode, follow this step.

1.
huawei(config)#vdsl channel-profile quickadd 3 path-mode ptm interleaved-delay
8 2 inp 4 2 rate 128 10000 128 10000 2048 2048
2.
Issue 02 (2013-10-08)
Activate VDSL port 0/1/0, and bind the preset VDSL line template 3 and the default VDSL
alarm template (alarm template 1) to the port.
451

Configuration Guide

NOTE
By default, a VDSL port is in the activated state. Before binding a template to the port, you must deactivate
the port.
3.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
The service requires the user access rate be 2048 kbit/s. The query result shows that traffic
profile 2 (for inbound and outbound rate limitation) meets the requirement.
NOTE
4.
S-VLAN ID to 50. Set the VDSL channel mode to PTM, and create service port 3 on VDSL
port 0/1/0. To facilitate the maintenance of the service port, also configure the service port
description.
huawei(config)#service-port 3 vlan 50 vdsl mode ptm 0/1/0 multi-service uservlan untagged inbound traffic-table index 2 outbound traffic-table index 2
huawei(config)#service-port desc 3 description Vlanid:50/vdsl
Issue 02 (2013-10-08)

452

Configuration Guide

Step 6 Configure the security of user accounts.

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)#raio-mode user-defined dhcp-option82
huawei(config)#raio-format dhcp-option82 cid anid frame/slot/port:vlanid
huawei(config)#raio-format dhcp-option82 rid splabel
NOTE
For the details about the security of DHCP accounts, see 3.10.2 Configuring Anti-Theft and Roaming of User
Accounts Through DHCPv4.

huawei(config)#save
----End
Verification
l
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.
Configuration File
Configuration File for the ADSL access mode:
vlan 50 smart
commit
quit
port vlan 50 0/0 0-1
link-aggregation 0/0 0 0/0 1 egress-ingress workmode lacp-static
interface adsl 0/2
deactivate 0
alarm-config 0 1
quit
service-port desc 1 description Vlanid:50/adsl/vpi:1vci:39/stacking
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
commit
Issue 02 (2013-10-08)

453

Configuration Guide

quit
shdsl line-profile quickadd 3 ptm rate 512 2048
interface shl 0/4
activate 0 3
alarm-config 0 1
quit
service-port 2 vlan 50 shdsl mode ptm 0/4/0 inbound traffic-table index 2 outbound
service-port desc 2 description Vlanid:50/shdsl/vpi:1vci:39/stacking
save
Configuration File for the VDSL access mode:

vlan 50 smart
commit
quit
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/1
deactivate 0
alarm-config 0 1
quit
service-port desc 3 description Vlanid:50/vdsl/vpi:1vci:39/stacking
save
9.1.3 Configuration Example of the PPPoA xDSL Internet Access

Service
services for broadband users and the users connect to the Internet in Point-to-Point Protocol over
ATM (PPPoA) mode, you can configure the MA5616 by referring to this topic to provide users
with high-speed Internet (HIS) services. The MA5616 functions as an optical network unit
(ONU) in this service. PPPoA is used to meet operators' requirements for transferring from an
asynchronous transfer mode (ATM) network to the IP network. PPPoA users must be
authenticated using Authentication, Authorization and Accounting (AAA) policies before
connecting to the Internet.
Issue 02 (2013-10-08)

454

Configuration Guide

l
Users connect to the Internet in 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.
The service access rate is 2048 kbit/s.
Figure 9-3 shows an example network of the PPPoA xDSL Internet access service.
Figure 9-3 Example network of the PPPoA xDSL Internet access service
Prerequisite
l
Procedure
Create smart VLAN 50.

aggregation.
Issue 02 (2013-10-08)

455


Configuration Guide
NOTE

type;

1.
(NGADSL Mode). 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
huawei(config)#adsl
1024 2048 3096 1024
3096
huawei(config)#adsl
3
2.
line-profile quickadd 3 snr 60 30 120 60 30 120

channel-profile quickadd 3 interleaved-delay 10 10 rate
2048
line-template quickadd 3 line 3 channel1 3 60 70 channel2
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
By default, an ADSL port is in the activated state. Before binding a template to the port, you must deactivate
the port.
3.
Run the display traffic table ip command to query the traffic profiles that exist in the
system.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
---------------------------------------------------------------------------
Issue 02 (2013-10-08)

456


Configuration Guide
0 512
18384
1024
36768
6 -
tag-
1 1024
34768
2048
69536
0 -
tag-
2 2048
67536
4096
135072
0 -
tag-
3 4096
133072
8192
266144
4 -
tag-
4 8192
264144
16384
528288
4 -
tag-
5 16384
526288
32768
1024000
4 -
tag-
6 off
off
off
off
0 -
tag-
pri
pri
pri
pri
pri
pri
pri
--------------------------------------------------------------------------Total Num : 7
traffic profile 2 meets the requirement.
NOTE
l If no traffic profile in the system meets the service requirement, run the traffic table ip command to
configure a new traffic 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.
4.
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 2 meets the service requirement, and the SVLAN 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 index 2 outbound traffic-table index 2
huawei(config)#service-port desc 1 description MA5616HW/Vlanid:50/adsl/smart
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.
Step 4 In SHDSL access mode, follow this step.

1.
Configure an SHDSL profile. For details, see 4.1.2 Configuring the SHDSL Profile. 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.
2.
Activate the SHDSL port. The port is port 0/4/0, and SHDSL line profile 3 and the default
alarm profile (alarm profile 1) are bound to the port.
NOTE
By default, an SHDSL port is in the activated state. Before binding a template to the port, you must
Issue 02 (2013-10-08)

457

Configuration Guide

3.
system.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
NOTE
4.
Run the service-port command to create a service port. The index of the new service virtual
port is 2, the access port is port 0/4/0, traffic profile 2 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 2 vlan 50 shdsl mode atm 0/4/0 vpi 1 vci 39 inbound
traffic-table index 2 outbound traffic-table index 2
huawei(config)#service-port desc 2 description MA5616HW/Vlanid:50/shdsl/smart
5.
Issue 02 (2013-10-08)
458

Configuration Guide

Step 5 In VDSL access mode, follow this step.

1.
huawei(config)#vdsl channel-profile quickadd 3 path-mode atm interleaved-delay
8 2 inp 4 2 rate 128 10000 128 10000 2048 2048
2.
Activate the VDSL port. The access port is port 0/1/0, and VDSL line template 3 and the
default VDSL alarm template (alarm template 1) are bound to the port.
NOTE
By default, a VDSL port is in the activated state. Before binding a template to the port, you must
3.
system.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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 tag-
Issue 02 (2013-10-08)

459


Configuration Guide
pri
--------------------------------------------------------------------------Total Num : 7
NOTE
4.
description.
huawei(config)#service-port 3 vlan 50 vdsl mode atm 0/1/0 vpi 1 vci 39 inbound
huawei(config)#service-port desc 3 description MA5616HW/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

The PITP P mode can be enabled to protect the user account against theft and roaming. The
RAIO mode can be customized based on actual requirements. This step uses common mode as
example. The common mode matches item common.
huawei(config)#raio-mode common pitp-pmode
NOTE
For details about the PITP configuration for the user account security, see 3.10.1 Configuring Anti-Theft and

huawei(config)#save
----End
Issue 02 (2013-10-08)

460

Configuration Guide

Verification
l
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.)
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.
Configuration File
Configuration File for the ADSL access mode:
vlan 50 smart
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 MA5616HW/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
shdsl line-profile quickadd 3 line four-wire rate 2048
interface shl 0/4
deactivate 0
activate 0 3
alarm-config 0 1
quit
service-port 2 vlan 50 shdsl mode atm 0/4/0 vpi 1 vci 39 inbound traffic-table index
2 outbound traffic-table index 2
service-port desc 2 description MA5616HW/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
Issue 02 (2013-10-08)

461

Configuration Guide


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/1
deactivate 0
alarm-config 0 1
quit
service-port 3 vlan 50 vdsl mode atm 0/1/0 vpi 1 vci 39 inbound traffic-table index
service-port desc 3 description MA5616HW/Vlanid:50/vdsl/smart
mac-pool xpoa 0000-1111-1010 300
pppoa enable
pitp enable pmode
save
9.1.4 Configuration Example of the IPoA xDSL Internet Access

Service
services for broadband users and the users connect to the Internet in IP over ATM (IPoA) mode,
you can configure the MA5616 by referring to this topic to provide users with high-speed Internet
(HIS) services. The MA5616 functions as an optical network unit (ONU) 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
Users connect to the Internet in IPoA 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.
The user access rate is 2048 kbit/s, which is restricted by the traffic profile.
Figure 9-4 shows an example network of the IPoA xDSL Internet access service.
Figure 9-4 Example network of the IPoA xDSL Internet access service
Issue 02 (2013-10-08)

462


Configuration Guide
Procedure
Create smart VLAN 50.

aggregation.
NOTE

type;

1.
(NGADSL Mode). 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
huawei(config)#adsl
1024 2048 3096 1024
3096
huawei(config)#adsl
3
2.
line-profile quickadd 3 snr 60 30 120 60 30 120

channel-profile quickadd 3 interleaved-delay 10 10 rate
2048
line-template quickadd 3 line 3 channel1 3 60 70 channel2
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
By default, an ADSL port is in the activated state. Before binding a template to the port, you must deactivate
the port.
Issue 02 (2013-10-08)

463

Configuration Guide

3.
system.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
NOTE
4.
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 2 meets the service requirement, and the SVLAN 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 index 2 outbound traffic-table index 2
huawei(config)#service-port desc 1 description MA5616HW/Vlanid:50/adsl/smart
5.
Issue 02 (2013-10-08)
464

Configuration Guide

Step 4 In SHDSL access mode, follow this step.

1.
Configure an SHDSL profile. For details, see 4.1.2 Configuring the SHDSL Profile. 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.
2.
Activate the SHDSL port. The port is port 0/4/0, and SHDSL line profile 3 and the default
alarm profile (alarm profile 1) are bound to the port.
NOTE
By default, an SHDSL port is in the activated state. Before binding a template to the port, you must
3.
system.
0
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
Issue 02 (2013-10-08)

465

Configuration Guide

NOTE
4.
description.
huawei(config)#service-port 2 vlan 50 shdsl mode atm 0/4/0 vpi 1 vci 39 inbound
huawei(config)#service-port desc 2 description MA5616HW/Vlanid:50/shdsl/smart
5.
Step 5 In VDSL access mode, follow this step.

1.
huawei(config)#vdsl channel-profile quickadd 3 path-mode atm interleaved-delay
8 2 inp 4 2 rate 128 10000 128 10000 2048 2048
2.
Activate the VDSL port. The access port is port 0/1/0, and VDSL line template 3 and the
default VDSL alarm template (alarm template 1) are bound to the port.
NOTE
By default, a VDSL port is in the activated state. Before binding a template to the port, you must
3.
system.
0
Issue 02 (2013-10-08)

466

Configuration Guide

Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
NOTE
4.
description.
huawei(config)#service-port 3 vlan 50 vdsl mode atm 0/1/0 vpi 1 vci 39 inbound
huawei(config)#service-port desc 3 description MA5616HW/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 000011111010, and the maximum number of the MAC addresses in the 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.
Issue 02 (2013-10-08)

467

Configuration Guide


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.
Configuration File
Configuration File in ADSL access mode:
vlan 50 smart
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 MA5616HW/Vlanid:50/adsl/smart
mac-pool xpoa 0000-1111-1010 300
ipoa enable
ipoa default gateway 192.168.1.20
encapsulation 0/2/0 vpi 1 vci 39 type ipoa llc srcIP 192.168.1.1
save
Configuration File in SHDSL access mode:

vlan 50 smart
shdsl line-profile quickadd 3 line four-wire rate 2048
interface shl 0/4
deactivate 0
activate 0 3
alarm-config 0 1
quit
service-port 2 vlan 50 shdsl mode atm 0/4/0 vpi 1 vci 39 inbound traffic-table index
service-port desc 2 description MA5616HW/Vlanid:50/shdsl/smart
mac-pool xpoa 0000-1111-1010 300
Issue 02 (2013-10-08)

468

Configuration Guide

ipoa enable
save
Configuration File in VDSL access mode:

vlan 50 smart
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/1
deactivate 0
alarm-config 0 1
quit
service-port 3 vlan 50 vdsl mode atm 0/1/0 vpi 1 vci 39 inbound traffic-table index
service-port desc 3 description MA5616HW/Vlanid:50/vdsl/smart
mac-pool xpoa 0000-1111-1010 300
ipoa enable
save
9.1.5 Configuration Example of VDSL2 Bonding Services

The MA5616 provides VDSL2 services for broadband users and the users connect to the Internet,
to increase the network bandwidth of a user, you can bind multiple ports together to connecting
to the Internet in a very-high-speed.
Prerequisites
l
l
Users connect to the Internet in PPPoE mode.
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.
Each subscriber has a unique account. The broadband remote access server (BRAS)
manages and authenticates subscribers. The Policy Information Transfer Protocol (PITP)
P mode, which is also known as PPPoE+ mode, is used to protect user accounts against
theft and roaming.
A traffic profile is adopted for rate limitation. The user access rate is 150000 kbit/s.
To ensure reliability, dual GE ports are adopted for upstream transmission, and link
aggregation is configured for the two upstream ports.
Figure 9-5 shows an example network for configuring VDSL2 bonding access service in PPPoE
mode.
Issue 02 (2013-10-08)

469


Configuration Guide
Figure 9-5 Example network for configuring VDSL2 bonding access service in PPPoE mode
Context
Data Plan
Table 9-3 provides the data plan for the PPPoE VDSL2 Internet access service.
Table 9-3 Data plan for the PPPoE VDSL2 Internet access service
Device
Configuration
Item
Data
MA5616
Port
Uplink port: 0/0/1

User ports: 0/1/0 and 0/1/1
Service VLAN

Traffic profile
Profile ID: 10
Committed rate: 165300Kbit/s
Priority: 0
Upper
layer
device
VLAN

MA5616.
Procedure
Issue 02 (2013-10-08)

470

Configuration Guide



aggregation.
NOTE

type;
Step 3 Configure a bonding group.

1.
Bond VDSL2 ports 0/1/0 and 0/1/1 into a bonding group. Set the bonding group profile ID
to 5 and bind the bonding group to a bonding group profile. The bonding group profile
contains the following parameters: minimum upstream and downstream transmission rates:
64 kbit/s, maximum upstream and downstream transmission rates: 200,000 kbit/s, target
upstream and downstream transmission rates: 153,600 kbit/s, upstream and downstream
transmission rate monitoring thresholds: 153,600 kbit/s, and rate alarm threshold function:
enable.
huawei(config)#xdsl bonding-group-profile add 5 rate 64 200000 153600 153600
64 200000 153600 153600 monitoring-switch enable
huawei(config)#bonding-group add 1 primary-port 0/1/0
huawei(config)#active bonding-group 1 profile-index 5
Step 4 Activate VDSL2 ports 0/1/0 and 0/1/1, and bind the two ports with VDSL line template 1 and
VDSL alarm template 1, which are the default templates.
NOTE
The two VDSL ports in a bonding group are activated by default. Ensure that the ports are deactivated before
binding a template to them.
Issue 02 (2013-10-08)

471

Configuration Guide

Step 5 Create a service port.

1.
Run the display traffic table command to query existing traffic profiles in the system.
NOTE
On the MA5616, the bonding group access rate can be set using a traffic profile, VDSL line profile, and
bonding group profile. After the three profiles are configured, the system selects the one that has the
minimum rate value for setting user bandwidth.
Command:
0
--------------------------------------------------------------------------TID CIR
CBS
PIR
PBS
Pri Copy-policy
PriPolicy
(kbps)
(bytes) (kbps)
(bytes)
--------------------------------------------------------------------------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
The service requires a user access rate of 150 Mbit/s. The preceding command output shows
that no traffic profile can be used for setting the user access rate. Create traffic profile 10
as required.
huawei(config)#traffic table ip index 10 cir 165300 pir 200000 priority 4
priority-policy tag-InPackage
Attention: CIR 165300 has been adjusted to rank of 165248
<kbps>
Create traffic descriptor record
successfully
-----------------------------------------------TD Index
:
10
TD Name
: ip-traffictable_10
Priority
:
4
Copy Priority
:
CTAG Mapping Priority:
CTAG Default Priority:
0
Issue 02 (2013-10-08)

472

Configuration Guide

Priority Policy
: tagpri
CIR
: 165248
kbps
CBS
: 1024000
bytes
PIR
: 200000
kbps
PBS
: 1024000
bytes
Color Mode
: colorblind
Referenced Status
: not
used
------------------------------------------------
2.
Run the service-port command to create a service port using traffic profile 10. Use the
service virtual local area network (SVLAN) ID 50 and set VDSL channel mode to packet
transfer mode (PTM) and service port ID on VDSL2 port 0/1/0 to 3. Configure service port
information for maintenance. In this example, it takes the single service stream for an
example.
huawei(config)#service-port 3 vlan 50 vdsl mode ptm 0/1/0 inbound traffictable index 10 outbound traffic-table index 10
huawei(config)#service-port desc 3 description Vlanid:50/vdsl/ptm/stacking
3.
Set customer VLAN (CVLAN) 10 for service port 3. Set the priority of important packets
to the highest so that these packets will be processed first, and set the priority of inner
VLAN to 4.
huawei(config)#stacking label service-port 3 10
huawei(config)#stacking inner-priority service-port 3 4

The PITP P mode can be enabled to protect user accounts against theft and roaming. The RAIO
mode can be customized according to actual requirements. Here, the cntel is considered as an
example.
huawei(config)#raio-mode cntel pitp-pmode
NOTE
For details about the PITP configuration for user account security, see 3.10.1 Configuring Anti-Theft and

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.
Configuration File
vlan 50 smart
Issue 02 (2013-10-08)

473

Configuration Guide


commit
quit
xdsl bonding-group-profile add 5 rate 64 200000 153600 153600 64 200000 153600
153600 monitoring-switch enable
bonding-group add 1 primary-port 0/1/0
bonding-group link add 1 0/1/1
active bonding-group 1 profile-index 5
interface vdsl 0/1
deactivate 0
deactivate 1
alarm-config 0 1
alarm-config 1 1
quit
traffic table ip index 10 cir 165300 pir 200000 priority 4 priority-policy tag-InPackage
service-port desc 3 description Vlanid:50/vdsl/ptm/stacking
pitp enable pmode
raio-mode common pitp-pmode
save
9.2 Configuration Example of the Multicast Service

(Multicast VLAN Mode)
This topic describes how to configure the multicast service on the MA5616 in multicast VLAN
mode.
Context
The program in the multicast VLAN can be configured statically or generated dynamically.
9.2.1 Configuration Example of the Multicast Video Service (Static

Configuration Mode)
The multicast video service in static configuration mode supports refined program configuration
and management service and provides the following functions: program and user multicast
bandwidth management, program previewing, and program prejoin. This service applies to the
scenario in which carriers have a high requirement on program and user management.
Prerequisites
l
Network devices and lines have been connected properly.
A multicast source is available on the network and the IP address of the multicast source
has been obtained.
Issue 02 (2013-10-08)

474


Configuration Guide
l
Independent service provider (ISP) 1 provides two hot music programs. ISP 2 provides one
hot music program and one hot video program. These programs can always be ordered in
real time.
The program ordering status can be recorded, collected, and reported for monitoring and
charging.
User 1 has only permissions to the music programs provided by ISP 1, and user 2 has only
permissions to the video program provided by ISP 2.
The maximum multicast bandwidths for users 1 and 2 are 10 Mbit/s and 5 Mbit/s
respectively.
Networking
Figure 9-6 shows the example network of the multicast service.
Figure 9-6 Example network of the multicast service
Multicast
Source
ISP2
ISP1
BRAS
Router
LAN Switch
ONU
Home Gateway
STB
TV
user1
user2
Data Plan
Table 9-4 provides the data plan for configuring the multicast service.
Issue 02 (2013-10-08)

475


Configuration Guide
Table 9-4 Data plan for configuring the multicast service

Device
Item
Data
ONU:
MA5616
Smart VLAN

l VLAN ID: 4002-4005
Uplink port
0/0/1
IGMP version

Multicast
source

Program
library

1, namely, 10.10.10.10
2, namely, 10.10.10.11
Multicast user
Multicast user 1:
l VDSL2 port: 0/1/0
Multicast user 2:
l VDSL2 port: 0/1/1
Procedure
Step 1 Create VLANs and add the uplink port to the VLANs.
Step 2 Configure service ports.

huawei(config)#service-port 100 vlan 4004 vdsl mode ptm 0/1/0 multi-service uservlan untagged
rx-cttr 6 tx-cttr 6
rx-cttr 6 tx-cttr 6
Step 3 Configure multicast VLANs and the IGMP mode.

Issue 02 (2013-10-08)

476

Configuration Guide

NOTE
The IGMP mode can be configured to IGMP proxy or IGMP snooping according to the requirements. In
this example, the IGMP mode is IGMP proxy. If the planned IGMP mode is IGMP snooping, configure
the IGMP snooping mode by running the igmp mode snooping command in multicast VLAN mode.
The IGMP mode can be switched only when the IGMP mode is off.


NOTE
l In static configuration mode, users can run the igmp program add command to add multicast programs.
l If the IGMP version of the multicast VLAN is V2, the source IP address of the program in the multicast
VLAN cannot be configured.
huawei(config-mvlan4002)#igmp program add name program1 ip 224.1.1.1 sourceip
10.10.10.10
huawei(config-mvlan4003)#igmp program add name program2 ip 224.1.1.2 sourceip
10.10.10.11
Step 6 Configure multicast users.

huawei(config-mvlan4003)#quit

huawei(config)#save
----End
Result
l
User 1 belongs to multicast VLAN 4002 and user 1 can watch the music program with IP
address 224.1.1.1 provided by ISP1.
User 2 belongs to multicast VLAN 4003 and user 2 can watch the video program with IP
address 224.1.1.2 provided by ISP2.
Configuration File
directly.
Create VLANs and add the uplink port to the VLANs. This step needs to be performed manually.
Issue 02 (2013-10-08)

477

Configuration Guide


port vlan 4002 to 4005 0/0 1

multicast-vlan 4002
igmp mode proxy
multicast-vlan 4003
igmp mode proxy
multicast-vlan 4002
multicast-vlan 4003
btv
multicast-vlan 4002
multicast-vlan 4003
quit
save
9.2.2 Configuration Example of the Multicast Video Service

(Dynamic Configuration Mode)
This topic describes how to configure the multicast video service in dynamic configuration
mode. This type of service simplifies configurations and reduces maintenance costs. However,
this type of service does not support the following functions: program and user multicast
bandwidth management, program previewing, and program prejoin. Therefore, the multicast
video service in dynamic configuration mode applies to the scenario in which carriers do not
have a high requirement on program and user management, or the program and user management
is implemented on the upper-layer device.
Prerequisites
l
A multicast source is available on the network and the IP address of the multicast source
has been obtained.
Multicast programs have been configured in dynamic mode.
Context
The program in the multicast VLAN can be configured statically or generated dynamically.
Dynamic generation mode: A program is dynamically generated according to the program
requested by the user.
Issue 02 (2013-10-08)

478

Configuration Guide

In this mode, the program list is not required. You need to configure the IP address range
of the program group that can be dynamically generated. The user can request for only the
program whose IP address is within this IP address range.
The following functions are not supported: bandwidth management of the multicast
program, user bandwidth management, program preview, and program prejoin.
The program in the multicast VLAN is configured statically by default. Run the igmp match
mode disable command to configure the dynamic generation mode.
NOTE
The igmp match mode command for configuring the mode of the multicast program can be executed only when
the IGMP mode is off.
l
Internet service providers (ISPs) 1 and 2 have a multicast program in an address segment
respectively. The multicast programs do not require strict program and user management,
and can be dynamically updated based on user requirements.
User 1 can watch programs provided only by ISP 1 and user 2 can watch programs provided
only by ISP 2.
Program ordering status can be recorded for monitoring and charging.
Figure 9-7 shows the example network of the multicast service.

Figure 9-7 Example network of the multicast service
Multicast
Source
ISP2
ISP1
BRAS
Router
LAN Switch
ONU
Home Gateway
STB
TV
user1
Issue 02 (2013-10-08)
user2

479


Configuration Guide
Data Plan
Table 9-5 provides the data plan for configuring the multicast service.
Table 9-5 Data plan for configuring the multicast service
Device
Item
Data
ONU:
MA5616
Smart VLAN

l VLAN ID: 4002-4005
Uplink port
0/0/1
IGMP version

Multicast
source

Program
library

1, namely, 10.10.10.10
2, namely, 10.10.10.11
Multicast user
Multicast user 1:
l VDSL2 port: 0/1/0
Multicast user 2:
l VDSL2 port: 0/1/1
Procedure
Step 1 Create VLANs and add the uplink port to the VLANs.
Step 2 Configure service ports.

Issue 02 (2013-10-08)

480

Configuration Guide

rx-cttr 6 tx-cttr 6
rx-cttr 6 tx-cttr 6
Step 3 Configure multicast VLANs and the multicast mode.

NOTE
The IGMP mode can be configured to IGMP proxy or IGMP snooping according to the requirements. In
this example, the IGMP mode is IGMP proxy. If the planned IGMP mode is IGMP snooping, you can
configure the IGMP snooping mode by running the igmp mode snooping command in multicast VLAN
mode.
The IGMP mode can be switched only when the IGMP mode is off.


Configure the program in the multicast VLAN in dynamic generation mode, and specify the IP
address range of the program that can be requested by the user to 224.1.1.1-224.1.1.2.
NOTE
The execution of the igmp match mode command for configuring the mode of the multicast program will cause
the user to go offline. Therefore, plan the multicast program mode before configuring the multicast program.
This command can be executed only when the IGMP function is disabled.
Step 6 Configure multicast users.


huawei(config)#save
----End
Result
l
Issue 02 (2013-10-08)
481

Configuration Guide

Configuration File
directly.
Create VLANs and add the uplink port to the VLANs. This step needs to be performed manually.
port vlan 4002 to 4005 0/0 1

multicast-vlan 4002
igmp mode proxy
multicast-vlan 4003
igmp mode proxy
multicast-vlan 4002
igmp match mode disable
igmp match group ip 224.1.1.1 to-ip 224.1.1.2
multicast-vlan 4003
igmp match mode disable
igmp match group ip 224.1.1.1 to-ip 224.1.1.2
btv
multicast-vlan 4002
multicast-vlan 4003
quit
save
9.3 Configuration Example of the VoIP Service

This topic describes how to configure the VoIP service based on the H.248 or SIP protocol.
9.3.1 Configuration Example of the VoIP PSTN Service (Based on

the H.248 Protocol)
This topic describes how to configure the VoIP service based on the H.248 protocol.
In an office, the MA5616 that adopts the H.248 protocol is newly deployed. Data plan and
configuration, however, are not performed on the MGC (softswitch) connected to the
MA5616. The following voice services are required:
Issue 02 (2013-10-08)

482

Configuration Guide

POTS service needs to be provided for phone 0-phone 15 for 16 users.
Polarity reversal charging is adopted.
According to the actual network, a route from the MA5616 to the MGC must be configured
to ensure that the MA5616 and the MGC are reachable to each other.
POTS service board ASRB must be inserted into the planned slot, and the RUN ALM
indicator on the board must be green and must be on for 1s and off for 1s repeatedly.
Prerequisite
Networking
Figure 9-8 shows the example network of the VoIP service based on the H.248 protocol.
Figure 9-8 Example network of the VoIP service based on the H.248 protocol
Data Plan
After the service requirements are further confirmed and analyzed with engineers of the office,
the data plan is made by considering the interconnection with the MGC and according to the
Issue 02 (2013-10-08)

483

Configuration Guide

data plan described in 6.1 Configuring the VoIP PSTN Service (Based on the H.248
Protocol). Table 9-6 provides the data plan for configuring the VoIP service based on the H.
248 protocol.
Table 9-6 Data plan for configuring the VoIP service based on the H.248 protocol
Item
Data
MG interface
data
(The data
configuration
must be
consistent with
the data
configuration
on the MGC.)
Issue 02 (2013-10-08)
Parameter
s of the
media
stream and
signaling
stream
Media and
signaling
upstream VLAN
Standard VLAN is recommended as the

upstream VLAN of the voice service. In
this section, standard VLAN 20 is
adopted.
Media and
signaling
upstream port
0/0/1
Media IP address
and signaling IP
address
These two IP addresses are both

10.10.10.10.
Default IP address
of the MG
The IP address of the next hop from the

MA5616 to the MGC is 10.10.10.1.
Attribute
parameter
s of the
MG
interface
MG interface ID
Signaling port ID
of the MG
interface
The signaling port ID is 2944.
NOTE
Parameter
s listed
here are
mandator
y, which
means
that the
MG
interface
fails to be
started if
these
parameter
s are not
configure
d.
IP address of the
primary MGC to
which the MG
interface belongs
The network of the office does not

support dual homing.
Port ID of the
primary MGC to
which the MG
interface belongs
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 MA5616.
Coding mode of
the MG interface
The text coding mode is adopted.
Transmission
mode of the MG
interface
UDP
Domain name of
the MG interface
The message ID (MID) adopts the IP

address (default), and may not be
configured with a domain name.
Device name of
the MG interface
The MID adopts the IP address

(default), and may not be configured
with a device name.

484

Configuration Guide

Item
Data
Start negotiation
version of the H.
248 protocol for
the MG interface
Digitmap of an MG Interface
Special applications such as emergency

calls and emergency standalone are not
configured. Therefore, the digitmap is
not configured.
Software Parameters of an
MG Interface
According to the Context in Software

Parameters of an MG Interface and
confirmed with the engineers of the
office, the default configuration can
meet the service requirements.
Therefore, the software parameters are
not configured.
Ringing Mode of an MG
Interface
The value of the ringing parameter

(corresponding to the users) specified
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.
TID Format of an MG
Interface
To differentiate users by terminal ID

(TID), the engineers of the office
require that the terminal prefix uses the
community name huawei and the TID
is automatically generated by the
system according to the slot ID/shelf
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.

service board
Voice service
data
The user is accessed through the 0/3

port on the ASRB board.
(The data
configuration
must be
consistent with
the data
configuration
on the MGC.)
Issue 02 (2013-10-08)

485

Configuration Guide

Item
Data
User Data
Phone number
The emergency standalone is not

supported. Therefore, you need not
configure the phone number when
adding a user.
Phone numbers allocated by the MGC
for phone 0-phone 15 are
83110000-83110015.
NOTE
Generally, No telephone number (namely,
parameter telno) is configured on the MG,
because telephone numbers are specified by
the MGC.
Issue 02 (2013-10-08)
TID
The terminal layering is supported.

Therefore, the TID need not be
allocated manually.
User priority
Users are common users, and the user

priority uses the default priority,
namely, cat3.
User type
Users are common users, and the user

type uses the default user type, namely,
DEL.
System Parameters
According to the Context in (Optional)

Configuring the System Parameters
and confirmed with the engineers of the
office, the default configuration can
meet the service requirements.
Therefore, the system parameters are
not configured.
Overseas Parameters
According to the Context in (Optional)

Configuring the Overseas
Parameters and confirmed with the
engineers of the office, the default
configuration can meet the service
requirements. Therefore, the overseas
parameters are not configured.
Local
Digitmap
Digitmap name
huawei
Digitmap type
Only the normal digitmap is supported

if the H.248 protocol is used.

486

Configuration Guide

Item
Data
CAUTION Digitmap body
By
default,
these
parameter
s need not
be
configure
d if the H.
248
protocol
is used.
You can
configure
these
parameter
s
according
to the
requireme
Attributes
of a PSTN Port
nts.
Plan this parameter according to the

prefix of the local phone number. In this
example, the ([2-8]xxxxxxx|[2-8]
0xxxxxxxxx) digitmap body is used.

Current
The ringing attribute need not be

configured unless otherwise specified.
The polarity reversal charging is

required for the service. Therefore, you
need to configure the PSTN port to
which the user belongs so that the PSTN
port supports the polarity reversal
impulse. The other attributes of the
PSTN port need not be modified.
Procedure
Step 1 Configure the upstream VLAN interface.
According to the data plan, configure standard VLAN 20 as the media and signaling upstream
VLAN, add upstream port 0/0/1 to the VLAN, and configure the IP address of the L3 interface
to 10.10.10.10, which facilitates the configuration of the media and signaling IP address pools.
huawei(config)#port vlan 20 0/0/1
Step 2 Configure the media and signaling IP address pools.

Add the IP address of the VLAN L3 interface configured in the previous step to the media and
signaling IP address pools respectively. Thus, 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
Issue 02 (2013-10-08)

487

Configuration Guide



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.
huawei(config-voip)#quit
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
start-negotiate-version 0
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 initial ringing are both 1:4. Therefore, the value of parameter cadence is 0,
and the value of parameter initialring is 4.
Step 5 Configure the TID template of the PSTN user on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix of the PSTN
user needs to be configured to huawei, and the TID template adopts layering template 6.
CAUTION
The MA5616 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
Step 6 Start 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 manners (see Parameter Description
of the reset command). For a newly configured MG interface, start the MG interface in a cold
start manner.
Step 7 Query the running status of the MG interface.

After the MG interface is interconnected with the MGC successfully, the MG interface needs to
be in the normal state, indicating that the MG interface works in the normal state.
-----------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
Issue 02 (2013-10-08)

488

Configuration Guide

-----------------------------------------------------------------------------0
UDP
Normal
2944 10.10.10.10
2944
10.10.20.20
------------------------------------------------------------------------------
Step 8 Confirm the service board.

Confirm the ASRB board that carries services to ensure that the board can work in the normal
state.
huawei(config)#board confirm 0/3
Step 9 Configure the PSTN user data.

Add POTS users phone 0-phone 15 so that the users can go online.
huawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/15 0
Step 10 Configure the local digitmap.

After the configuration, the MA5616 matches the phone number according to the local digitmap
if the MGC does not send the detailed digitmap to the MA5616.
huawei(config-esl-user)#quit
huawei(config)#local-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|
13xxxxxxxxx|0xxxxxxxxx)
Step 11 Configure the polarity reversal charging function.

Configure the physical attributes of the PSTN port to which the user belongs to support the
polarity reversal pulse, so that the user can support the polarity reversal charging.
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 service can be provided normally. In normal cases, phone
0-phone 15 can call each other.
l
The calling party can hear the dial tone after picking up the phone off the hook.
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 ringback tone.
Issue 02 (2013-10-08)

489

Configuration Guide

NOTE
When the calling party calls the number of a specified user, if the phone of the specified user does
not ring but the phone of another user connected to the MA5616 rings, and the calling party hears
the ringback tone, check whether the MGC is configured with the call forwarding service, causing
the line cross.
l If the MGC is configured with the call forwarding service, cancel the call forwarding service on
the MGC.
l If the MGC is not configured with the call forwarding service, contact Huawei technical support
engineer to handle the fault.
The calling party and the called party can communicate with each other normally.
After the called party places the phone on the hook, the calling party can hear the busy tone.
Configuration File
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/0/1
interface vlanif 20
ip address 10.10.10.10 24
Configure the media and signaling IP address pools.

quit
voip
ip address media 10.10.10.10 10.10.10.1
ip address signaling 10.10.10.10
Add an MG interface and then configure the attributes of the MG interface. An MG interface
must be added manually and the configuration file cannot be imported directly.
quit
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 primary-mgc-port 2944 code text transfer udp start-negotiate-version 0
Configure the ringing mapping of the MG interface.

mg-ringmode add 0 0 4
Configure the TID template of the PSTN user on the MG interface.

tid-format pstn prefix huawei template 6
An MG interface must be started manually and the configuration file cannot be imported directly.
reset coldstart
Query the running status of the MG interface.

quit
display if-h248 all
Confirm the service board.

board confirm 0/3
Configure the PSTN user data.

Issue 02 (2013-10-08)

490

Configuration Guide

esl user
mgpstnuser batadd 0/3/0 0/3/15 0
Configure the local digitmap.

quit
local-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|
0xxxxxxxxx)
Configure the polarity reversal charging function.

pstnport
pstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse enable
Save the data.

quit
save
9.3.2 Configuration Example of the VoIP PSTN Service (Based on

the SIP Protocol)
This topic describes how to configure the VoIP PSTN service based on the SIP protocol.
Prerequisites
l
The voice service board ASRB must be installed in the specified slot.
The SIP interface must be configured. For how to configure the SIP interface, see 6.2.1
Configuring the SIP Interface.
The PSTN user data corresponding to the SIP interface must be configured on the IMS.
Networking
Figure 9-9 shows the example network of the VoIP PSTN service based on the SIP protocol.
Issue 02 (2013-10-08)

491

Configuration Guide

Figure 9-9 Example network of the VoIP PSTN service based on the SIP protocol
Data Plan
Run the display system parameters and display oversea parameters commands to query the
system parameters and overseas parameters. If the parameter settings do meet the requirements,
run the system parameters and oversea parameters commands to set the parameters to the
required values.
In this example, the default configurations of system parameters and overseas parameters can
meet the standard and application requirements. Therefore, you need not configure these
parameters.
Table 9-7 provides the data plan for configuring the VoIP PSTN service based on the SIP
protocol.
Table 9-7 Data plan for configuring the VoIP PSTN service based on the SIP protocol
Item
SIP interface
Issue 02 (2013-10-08)
Data
SIP interface ID

492

Configuration Guide

Item
Data
Local digitmap
Digitmap name
huawei0 and huawei1
Digitmap type
The digitmap type of huawei0 is normal.

The digitmap type of huawei1 is secondcentrex.
NOTE
The parameters of the emergency digitmap use
default values.
Digitmap body
The digitmap body of huawei0 is ([2-8]

xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|
0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S).
The digitmap body of huawei1 is (8100).
Voice service
board ASRB
Slot that houses the board
0/3
Data of the
PSTN users in
slot 0/3
Numbers of phone 0phone 15
83110000-83110015
User priority
The priority of phone 0 is Cat2 and the priority

of phone 1-phone 15 is Cat3 (default priority).
User type
The type of phone 0 is DEL and the type of

phone 1-phone 15 is Payphone.
PSTN port attribute
Phone 1-phone 15 support polarity reversal

impulse.
Procedure
Step 1 Configure the local digitmap.
Configure the local call digitmap and two-stage dialing digitmap. The parameters of the
emergency digitmap use the default values.
huawei(config)#local-digitmap add huawei0 normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|
13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S)
huawei(config)#local-digitmap add huawei1 second-centrex (8100)

1.
Configure the data of the PSTN users (phone 0-phone 15) in slot 0/3.
huawei(config-esl-user)#sippstnuser batadd 0/3/0 0/3/15 0 telno 83110000
2.
Configure the priority of the PSTN user in slot 0/3/0 to Cat2.

huawei(config-esl-user)#sippstnuser attribute set 0/3/0 priority cat2
3.
Configure the type of the PSTN user in slot 0/3.

huawei(config-esl-user)#sippstnuser attribute batset 0/3/1 0/3/15 potslinetype
PayPhone
Step 3 Configure the PSTN port attribute.

Issue 02 (2013-10-08)

493

Configuration Guide

Configure the PSTN port in slot 0/3 so that the port supports polarity reversal impulse.
enable

huawei(config)#save
----End
Result
After the configuration, phone 0-phone 15 can call each other.
l
The calling party can hear the dial tone after picking up the phone off the hook.
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 ringback tone.
NOTE
When the calling party calls the number of a specified user, if the phone of the specified user does
not ring but the phone of another user connected to the MA5616 rings, and the calling party hears
the ringback tone, check whether the IMS is configured with the call forwarding service, causing the
line cross.
l If the IMS is configured with the call forwarding service, cancel the call forwarding service on
the IMS.
l If the IMS is not configured with the call forwarding service, contact Huawei technical support
engineer to handle the fault.
The calling party and the called party can communicate with each other normally.
After the called party places the phone on the hook, the calling party can hear the busy tone.
Configuration File
certain steps must be performed manually and the configuration file cannot be imported directly.
Configure the local digitmap.
local-digitmap add huawei0 normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|
0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S)
local-digitmap add huawei1 second-centrex (8100)

esl user
sippstnuser batadd 0/3/0 0/3/15 0 telno 83110000
sippstnuser attribute set 0/3/0 priority cat2
sippstnuser attribute batset 0/3/1 0/3/15 potslinetype PayPhone
Configure the PSTN port attribute.

quit
pstnport
pstnport attribute batset 0/3/1 0/3/15 reverse-pole-pulse enable
Save the data.

Issue 02 (2013-10-08)

494

Configuration Guide

quit
save
9.3.3 Configuration Example of the VoIP ISDN BRA Service (Based

on the H.248 Protocol)
When the H.248 protocol is used, the MA5616 can access the ISDN BRA service through the
DSLD service board. Then, the service is sent upstream to the IP network through the control
board, thus implementing the ISDN BRA service.
Prerequisites
l
The devices on the network must be connected properly and must work in the normal state.
The MA5616 must use the H.248 protocol to communicate with the MGC.
The data on the MGC side must be configured correctly.
NT1 must be connected properly and must work in the normal state.
When the MG interface does not support the terminal layering, the terminal ID must be
configured and must be different from the terminal ID of an existing PSTN user.
When the MG interface supports terminal layering, the terminal ID cannot be configured,
and the system automatically allocates the terminal ID according to the TID profile
configured for the interface of the PSTN user.
You can run the display tid-format to query the TID profile to which various users under
the MG interface are bound, and then run the display tid-template command to check
whether the TID profile supports the layering configuration. Hence, you can check whether
the user supports terminal layering.
Context
If the parameter list of the TID profile includes only keyword "G", it indicates that the
TID profile is used by the non-layering users. Users bound with this profile do not
If the parameter list of the TID profile includes only keywords "F", "S", "P", "B" ("B"
is unavailable for PSTN users), it indicates that the TID profile is used by the layering
users. Users bound with this profile support terminal layering.
Networking
Figure 9-10 shows the example network for configuring the ISDN BRA service.
Issue 02 (2013-10-08)

495

Configuration Guide

Figure 9-10 Example network for configuring the ISDN BRA service
Data Plan
Table 9-8 provides the data plan for configuring the ISDN BRA service.
Table 9-8 Data plan for configuring the ISDN BRA service
Item
Parameters of
the media
stream and
signaling
stream
Issue 02 (2013-10-08)
Data
IP address and mask of
the VLAN L3 interface
10.13.4.116/16
IP address of the media

stream and signaling
stream
10.13.4.116
Upstream interface of the

media stream and
signaling stream
0/0/1

496

Configuration Guide

Item
Data
TID profile
Static route
from the MG to
the MGC
Attribute
parameters of
the MG
interface
Issue 02 (2013-10-08)
Upstream VLAN of the

media stream and
signaling stream
VLAN ID: 10
Default media gateway of

the MG interface
10.13.1.1
ID of the TID profile used

by the ISDN BRA user
2 (default, no configuration is required)
TID terminal prefix used

by the ISDN BRA user
A (default, no configuration is required)
IP address of the
destination network
segment
10.14.0.0
IP address of the gateway
10.13.1.1
MG interface ID
Coding type of the MG

interface
text
Protocol supported by the

MG interface
H.248
Signaling port ID of the

MG interface
2944
Media/Signaling IP
address of the MG
interface
10.13.4.116

the MG interface
10.13.1.1
IP address of the primary

MGC to which the MG
interface belongs
10.14.1.2
Port ID of the primary

MGC to which the MG
interface belongs
2944
Transmission mode of
the MG interface
UDP
Start negotiation version

of the H.248 protocol for
the MG interface
Domain name
MA5616.com

497

Configuration Guide

Item
Data
Voice service
board DSLD
0/4
IUA link
parameters
ID of the IUA link set
IUA link ID
Local port ID
1401
Local IP address
10.13.4.116/16
MGC port ID
1400

MGC
10.14.1.2/16 (IP address of the primary MGC)
ISDN phone1 and ISDN

phone2
l Shelf/slot/port ID of the BRA user: 0/4/0
BRA user data
l Phone number: 83110001

l Working mode: point to multi-point
l Terminal ID: 2
l IUA interface ID: 0
l Priority of the user: Cat3 (default)
ISDN phone3

l Working mode: point to point
l Terminal ID: 4
l IUA interface ID: 2
l Priority of the user: Cat1
NOTE
In the point to point mode, the terminal endpoint
identifier (TEI) of the ISDN BRA digital phone is
always 0.
Procedure
Step 1 Add a DSLD service board.
huawei(config)#board add 0/4 H832DSLD
0 frame 4 slot board added successfully
Step 2 Create a VLAN and configure the VLAN L3 interface.

Step 3 Add the uplink port to the VLAN.

Issue 02 (2013-10-08)

498

Configuration Guide

Step 4 Configure the media/signaling IP address.

huawei(config)#voip
NOTE
Ensure that the to-be-configured media/signaling IP address of the MG interface must exist in the
corresponding address pool. You can run the display ip address command to query the in formation about
the media IP address pool or the signaling IP address pool.
Step 5 Configure the static route.


Step 7 Configure the attributes of the MG interface.

huawei(config-if-h248-0)#if-h248 attribute mgip 10.13.4.116 mgport 2944 code
text transfer udp MIDType domainName domainName MA5616.com primary-mgc-ip1
10.14.1.2 primary-mgc-port 2944 mg-media-ip1 10.13.4.116 start-negotiate-version 2
Step 8 Reset the MG interface.

Step 9 Configure the working mode of the ISDN BRA port.

huawei(config-braport)#braport attribute set 0/4/0 workmode p2mp
huawei(config-braport)#braport attribute set 0/4/1 activemode stable-active
workmode p2p
NOTE
In the point to point mode, the L1 activemode of the ISDN BRA port must be set to stable-active to make
Step 10 Add an IUA link set and IUA links.

huawei(config-braport)#quit
huawei(config-sigtran)#iua-linkset add 0
huawei(config-sigtran)#iua-link add 0 0 1401 10.13.4.116 1400 10.14.1.2
Step 11 Add an ISDN BRA user and configure the data.

huawei(config-sigtran)#quit
cat3 telno 83110001
Are you sure to configure the working mode of the DSL board to normal and reset
the board automatically? (y/n)
[n]:y
cat1 telno 83110002

huawei(config)#save
----End
Issue 02 (2013-10-08)

499

Configuration Guide

Result
l
ISDN phone1 and ISDN phone2 can communicate with ISDN phone3 by dialing number
83110002.
When ISDN phone3 dials number 83110001, ISDN phone1 and ISDN phone2 can hear the
ringing tone at the same time. In addition, ISDN phone1 and ISDN phone2 can
communicate with ISDN phone3 at the same time.
Configuration File
certain steps must be performed manually and the configuration file cannot be imported at a
time.
Add the DSLD service board.
board add 0/4 H832DSLD
Create a service VLAN and configure its L3 interface.

vlan 10
interface vlanif 10
ip address 10.13.4.116 16
quit
Add an uplink port to the service VLAN.

port vlan 10 0/0/1
Configure the media IP address pool and the signaling IP address pool.
voip
ip address media 10.13.4.116 10.13.1.1
Configure a static route.

quit
ip route-static 10.14.0.0 16 10.13.1.1
Add an MG interface.
interface h248 0
Configure the attributes of the MG interface.

if-h248 attribute mgip 10.13.4.116 mgport 2944 code text transfer udp MIDType
domainName domainName MA5616.com primary-mgc-ip1 10.14.1.2 primary-mgc-port 2944
mg-media-ip1 10.13.4.116 start-negotiate-version 2
Enable the MG interface.

reset coldstart
Configure the working mode of the ISDN BRA port.

quit
braport
braport attribute set 0/4/0 workmode p2mp
braport attribute set 0/4/1 activemode stable-active workmode p2p

Add an IUA link set and IUA links.
Issue 02 (2013-10-08)

500

Configuration Guide

quitsigtran
iua-linkset add 0
iua-link add 0 0 1401 10.13.4.116 1400 10.14.1.2
Add an ISDN BRA user and configure the data.

quit
esl user
mgbrauser add 0/4/0 0 0 interfaceid 0 terminalid 2 priority cat3 telno 83110001
mgbrauser add 0/4/1 0 0 interfaceid 2 terminalid 4 priority cat1 telno 83110002
Save the data.

quit
save
9.3.4 Configuration Example of the VoIP ISDN BRA Service (Based

on the SIP Protocol)
This topic describes how to configure the VoIP ISDN BRA service based on the SIP protocol.
Prerequisites
l
The devices on the network must be connected properly and must work in the normal state.
The ISDN BRA user data corresponding to the SIP interface must be configured on the
IMS.
NT1 must be connected properly and must work in the normal state.
Networking
Figure 9-11 shows the example network of the VoIP ISDN BRA service when the SIP protocol
is used.
Issue 02 (2013-10-08)

501

Configuration Guide

Figure 9-11 Example network of the VoIP ISDN PRA service when the SIP protocol is used
BRA
Router
LAN Switch
SIP
Access Node
NT1
ISDN phone1
ISDN phone2
PBX
ISDN phone3
Data Plan
Table 9-9 provides the data plan for configuring the ISDN BRA service.
Table 9-9 Data plan for configuring the ISDN BRA service
Item
Parameters of
the media
stream and
signaling
stream
Issue 02 (2013-10-08)
Data
IP address and mask of
the VLAN L3 interface
10.13.4.116/16
IP address of the media

stream and signaling
stream
10.13.4.116
Upstream interface of the

media stream and
signaling stream
0/0/1
Upstream VLAN of the

media stream and
signaling stream
VLAN ID: 10

502

Configuration Guide

Item
Data
the MG interface
10.13.1.1
IP address of the
destination network
segment
10.14.0.0
IP address of the gateway
10.13.1.1
SIP interface ID
Signaling port ID of the

SIP interface
5060
Media/Signaling IP
address of the SIP
interface
10.13.4.116

the SIP interface
10.13.1.1

proxy server
10.14.1.2
Port ID of the primary

proxy server
5060
Transmission mode of
the SIP interface
UDP
Home domain name
MA5616.com
Voice service
board DSLD
0/4
BRA user data
ISDN phone1 and ISDN

phone2
Static route
from the VAG
to the IMS
Attribute
parameters of
the SIP
interface

l Working mode: point to multi-point
l Priority of the user: Cat3 (default)
ISDN phone3

l Working mode: point to point
l Priority of the user: Cat1
NOTE
In the point to point mode, the terminal endpoint
identifier (TEI) of the ISDN BRA digital phone is
always 0.
Issue 02 (2013-10-08)

503

Configuration Guide

Procedure
Step 1 Add a DSLD service board.
huawei(config)#board add 0/4 H832DSLD
0 frame 4 slot board added successfully
Step 2 Create a VLAN and configure the VLAN L3 interface.

Step 3 Add the uplink port to the VLAN.

Step 4 Configure the media/signaling IP address.

huawei(config)#voip
NOTE
Ensure that the to-be-configured media/signaling IP address of the MG interface must exist in the
corresponding address pool. You can run the display ip address command to query the in formation about
the media IP address pool or the signaling IP address pool.
Step 5 Configure the static route.

Step 6 Add the SIP interface.

Are you sure to add the SIP interface?(y/n)[n]:y
Step 7 Configure the attributes of the SIP interface.

huawei(config-if-sip-0)#if-sip attribute basic signal-port 5060 media-ip 10.3.4.
116 signal-ip 10.3.4.116 primary-proxy-ip1 10.14.1.2 primary-proxy-port 5060 tra
nsfer udp home-domain MA5616.com srvlogic-index 1
Step 8 Reset the SIP interface.

Step 9 Configure the working mode of the ISDN BRA port.

huawei(config-braport)#braport attribute set 0/4/0 workmode p2mp
huawei(config-braport)#braport attribute set 0/4/1 activemode stable-active
workmode p2p
NOTE
In the point to point mode, the L1 activemode of the ISDN BRA port must be set to stable-active to make
Step 10 Add an ISDN BRA user and configure the data.

1.
Configure the ISDN BRA user data.

huawei(config-braport)#quit
Issue 02 (2013-10-08)

504

Configuration Guide
2.

Configure the call priority of the ISDN PRA user

huawei(config-esl-user)#sipbrauser attribute set 0/4/0 priority cat3
huawei(config-esl-user)#sipbrauser attribute set 0/4/1 priority cat1

huawei(config)#save
----End
Result
l
ISDN phone1 and ISDN phone2 can communicate with ISDN phone3 by dialing number
83110002.
When ISDN phone3 dials number 83110001, ISDN phone1 and ISDN phone2 can hear the
ringing tone at the same time. In addition, ISDN phone1 and ISDN phone2 can
communicate with ISDN phone3 at the same time.
Configuration File
certain steps must be performed manually and the configuration file cannot be imported at a
time.
Add the DSLD service board.
board add 0/4 H832DSLD
Create a service VLAN and configure its L3 interface.

vlan 10
interface vlanif 10
ip address 10.13.4.116 16
quit
Add an uplink port to the service VLAN.

port vlan 10 0/0/1
Configure the media IP address pool and the signaling IP address pool.
voip
ip address media 10.13.4.116 10.13.1.1
Configure a static route.

quit
ip route-static 10.14.0.0 16 10.13.1.1
Add a SIP interface.

interface sip 0
Configure the attributes of the SIP interface.

if-sip attribute basic signal-port 5060 media-ip 10.3.4.
116 signal-ip 10.3.4.116 primary-proxy-ip1 10.14.1.2 primary-proxy-port 5060 tra
nsfer udp home-domain MA5616.com srvlogic-index 1
Enable the MG interface.

reset
Issue 02 (2013-10-08)

505

Configuration Guide

Configure the working mode of the ISDN BRA port.

quit
braport
braport attribute set 0/4/0 workmode p2mp
braport attribute set 0/4/1 activemode stable-active workmode p2p

Add an ISDN BRA user and configure the data.
quit
esl user
sipbrauser
sipbrauser
sipbrauser
sipbrauser
add 0/4/0
add 0/4/1
attribute
attribute
0 telno 83110001
0 telno 83110002
set 0/4/0 priority cat3
set 0/4/1 priority cat1
Save the data.

quit
save
9.4 Configuration Example of the VAG Service

The purpose of configuring virtual access gateways (VAGs) is to simulate multiple AGs by using
one AG and rent MG interfaces to different carriers, increasing the usage rate and flexibility of
the device.
Context
The MA5616 supports H.248-based, and SIP-based VAGs.
The MA5616 supports up to four VAGs.
l
When the system protocol is H.248, up to four H.248 interfaces with different indexes can
be configured on the MA5616, and each H.248 interface can be considered as a VAG.
When the system protocol is SIP, up to four SIP interfaces with different indexes can be
configured on the MA5616, and each SIP interface can be considered as a virtual SIP AG.
9.4.1 Configuration Example of the VAG Service (Based on the H.

248 Protocol)
This topic describes how to configure and verify the VAG service by creating two H.248
interfaces on the MA5616 and configuring PSTN users on the two H.248 interfaces. This topic
is applicable to the scenario where multiple logical AGs are simulated on one physical AG.
Context
Configuring VAGs is literally to configure H.248 interfaces with different IDs on the same
device, and to configure user ports homing to different H.248 interfaces. Pay attention to the
following points:
l
When the system uses the H.248 protocol, up to four H.248 interfaces with different IDs
can be configured on the MA5616, and each H.248 interface can be considered as a VAG.
When configuring the parameters for interconnecting different H.248 interfaces with the
MGC, make sure that the values of the following parameters of the H.248 interfaces are
Issue 02 (2013-10-08)

506


Configuration Guide
not completely the same. The values of at least one of the following parameters must be
different on the H.248 interfaces.
Local IP address
Local port ID
Remote IP address
Remote port ID
Figure 9-12 shows an example network of the VAG service.
Figure 9-12 Example network of the VAG service
MGC2
MGC1
BRAS
Router
LAN Switch
H.248
MA5616
Phone
Phone
VAG1
Issue 02 (2013-10-08)
Phone
Phone
VAG2

507

Configuration Guide

The service requirements are as follows:

l
As shown in Figure 9-12, configure the users in slot 0/3 to belong to VAG1, which belongs
to MGC1; configure the users in slot 0/4 to belong to VAG2, which belongs to MGC2.
The MG communicates with the MGC through the H.248 protocol.
Configure the data plan of VAG1 as listed in Table 9-10.
The data plan of VAG2 is the same as that of VAG1 except for the following differences:
The MG interface ID is 1.
The upstream VLAN ID of VAG2 is 40.
The media IP address and signaling IP address of VAG2 are 10.20.10.10.
The MGC2 assigns phone numbers 85110000-85110031 to phones 0-31 of VAG2.
The IP address of MGC2 is 10.20.40.20.
MG0 indicates VAG1 in the figure, and MG1 indicates VAG2 in the figure.
Table 9-10 Data plan of VAG1

Item
Data
MG interface
data
(The data
configuration
must be the
same as the data
configuration
on the MGC.)
Media and
signaling
parameter
s
Attributes
of the MG
interface
Media and
signaling
upstream VLAN
Standard VLAN is recommended as the

upstream VLAN of the voice service.
Standard VLAN 20 is adopted.
Media and
signaling
upstream port
In this office, all the services are

transmitted upstream through the
control board. Therefore, port 0/0/1 is
used as the upstream port of the voice
service.
Media IP address
and signaling IP
addresses

10.10.10.10.
Default gateway
IP address

MA5616 to the MGC is 10.10.10.1.
H.248 interface ID
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, the
same as the port ID on the MA5616.
Port ID of the
primary MGC to
which the MG
interface belongs
Issue 02 (2013-10-08)

508


Configuration Guide
Item
Data
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.
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
To differentiate users according to the

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.
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.
Voice user data
Slot of the voice service board
(The data
configuration
must be the
same as the data
configuration
on the MGC.)
User access is implemented by the

ASRB board in slot 0/3.
Configuri
ng 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
The MGC assigns phone numbers

83110000-83110031 to phones 0-31.
TID
The terminal layering is supported, and

therefore the TIDs do not need to be
allocated manually.
Procedure
l
Configure VAG1.
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/0/1 to the VLAN, and configure the IP address
Issue 02 (2013-10-08)

509

Configuration Guide

of the Layer 3 interface to 10.10.10.10, which facilitates the configuration of the media
and signaling IP address pools.
2.

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
3.
Configure a static route to the MGC.

Make sure that the route between the local device and the MGC is reachable. The
static route is used as an example.
4.
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.
10.10.1
0.10 mgport 2944 primary-mgc-ip1 10.10.20.20 primary-mgc-port 2944 code
text tra
nsfer udp
5.
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.
CAUTION
The MA5616 requires that the terminal prefixes of PSTN users, and ISDN BRA users
on the same H.248 interface be either the same or different. Note this when configuring
the terminal prefix.
6.
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
Issue 02 (2013-10-08)

510

Configuration Guide

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.
7.

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
-----------------------------------------------------------------------------
8.

Confirm the ASPB service board that carries services so that the board can work in
the normal state.
9.

Add POTS users (phones 0-31) so that the users can go online.
10. Save the data.

huawei(config)#save
Configure VAG2.
1.

upstream VLAN, add upstream port 0/0/1 to the VLAN, configure the IP address of
the Layer 3 interface to 10.20.10.10, which facilitates the configuration of the media
2.

Issue 02 (2013-10-08)

511

Configuration Guide

is 10.20.10.1.
huawei(config)#voip
3.
Configure a static route to the MGC.

Make sure that the route between the local device and the MGC is reachable. The
static route is used as an example.
4.
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.
10.20.1
0.10 mgport 2944 primary-mgc-ip1 10.20.40.20 primary-mgc-port 2944 code
text tra
nsfer udp
5.
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.
CAUTION
The MA5616 requires that the terminal prefixes of PSTN users, and ISDN BRA users
on the same H.248 interface be either the same or different. Note this when configuring
the terminal prefix.
6.
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 ways (see
Parameters of the reset command). For a newly configured MG interface, enable the
MG interface through cold start.
7.

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.
Issue 02 (2013-10-08)

512

Configuration Guide

----------------------------------------------------------------------------MGID
Trans State
MGPort MGIP
MGCPort MGCIP/
DomainName
----------------------------------------------------------------------------0
UDP
Normal
2944
10.10.10.10
2944
10.10.20.20
1
UDP
Normal
2944
10.20.10.10
2944
10.20.40.20
-----------------------------------------------------------------------------
8.

Confirm the ASPB service board that carries services so that the board can work in
the normal state.
9.

Add POTS users (phones 0-31) so that the users can go online.
10. Save the data.

huawei(config)#save
----End
Result
When VAG1 and VAG2 communicate with the MGC in the normal state, phones 0-31 belonging
to VAG1 and phones 0-31 belonging to VAG2 can communicate with each other.
Configuration File
Configure VAG1.
vlan 20 standard
port vlan 20 0/0 1
interface vlanif 20
ip address 10.10.10.10 16
quit
voip
ip address media 10.10.10.10 10.10.10.1
quit
ip route-static 10.10.0.0 255.255.0.0 10.10.10.1
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 primary-mgc-port 2944 code text transfer udp
reset coldstart
quit
display if-h248 all
board confirm 0/3
esl user
quit
save
Issue 02 (2013-10-08)

513

Configuration Guide

Configure VAG2.
vlan 40 standard
port vlan 40 0/0 1
interface vlanif 40
ip address 10.20.10.10 16
quit
voip
ip address media 10.20.10.10 10.20.10.1
quit
ip route-static 10.20.0.0 255.255.0.0 10.20.10.1
interface h248 1
if-h248 attribute mg-media-ip1 10.20.10.10 mgip 10.20.10.1 mgport 2944 primary-mgcip1 10.20.40.20 primary-mgc-port 2944 code text transfer udp
reset coldstart
quit
display if-h248 all
board confirm 0/4
esl user
quit
save
9.4.2 Configuration Example of the VAG Service (Based on the SIP

Protocol)
This topic describes how to configure and verify the VAG service by creating two SIP interfaces
on the MA5616 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 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 four SIP interfaces with different IDs can be
configured on the MA5616, 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.
Local IP address
Local port ID
Remote IP address
Remote port ID
Figure 9-13 shows an example network of the SIP-based VAG service.
Issue 02 (2013-10-08)

514


Configuration Guide
Figure 9-13 Example network of the SIP-based VAG service
IMS2
IMS1
BRAS
Router
LAN Switch
SIP
MA5616
Phone
Phone
Phone
VAG1
Phone
VAG2
Data Plan
The service requirements are as follows:
l
As shown in Figure 9-13, configure the users in slot 0/3 to belong to VAG1, which belongs
to IMS1; configure the users in slot 0/4 to belong to VAG2, which belongs to IMS2.
The MA5616 communicates with the IMS through the SIP protocol.
Configure the data plan of VAG1 as listed in Table 9-11.
The data plan of VAG2 is the same as that of VAG1 except for the following differences:
The SIP interface ID of VAG2 is 1.
The media IP address and signaling IP address of VAG2 are 10.20.10.11.
Issue 02 (2013-10-08)

515

Configuration Guide

The IMS2 assigns phone numbers 85000000-85000031 to phones 0-31 of VAG2.

The IP address of IMS2 is 10.20.30.100.
l
MG0 indicates VAG1 in the figure, and MG1 indicates VAG2 in the figure.
Table 9-11 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.
Issue 02 (2013-10-08)
Media and
signaling
upstream VLAN
Standard VLAN 30 is adopted.
Media and
signaling
upstream port
In this office, all the services are

transmitted upstream through the
control board. Therefore, port 0/0/1 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

MA5616 to the IMS core network
device is 10.20.10.1.
SIP interface ID
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

516


Configuration Guide
Item
Remarks
Index of the
profile used by the
SIP interface
Voice user data

(The data
configuration
must be the
same as the data
configuration
on the IMS.)
Default profile (profile 1)
Slot of the voice service board
The ASRB service board in slot 0/3
Phone number
80000000-80000031
Procedure
l
Configure VAG1.
1.

upstream VLAN, add upstream port 0/0/1 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
2.

is 10.20.10.1.
huawei(config)#voip
3.
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.
4.

According to the data plan, add SIP interface 0, and configure the interface attributes.
Issue 02 (2013-10-08)

517

Configuration Guide

10.20.20.100 primary-proxy-port 5060 home-domain huawei sipprofile-index

1
5.
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.
Are you sure to reset SIP interface?(y/n)[n]:y
6.

Confirm the ASRB service board that carries services so that the board can work in
the normal state.
7.

Add POTS users (phones 0-31) to VAG1 so that the users can go online.
8.
Save the data.

huawei(config)#save
Configure VAG2.
1.

According to the data plan, use standard VLAN 30 as the media and signaling upstream
VLAN (the uplink port ID is 0/0/1), and 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.
In step Step 1, 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.
2.

is 10.20.10.1.
huawei(config)#voip
3.
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.
Issue 02 (2013-10-08)

518

Configuration Guide

4.

According to the data plan, add SIP interface 1, and configure the interface attributes.
10.20.30.100 primary-proxy-port 5060 home-domain huawei sipprofile-index
1
5.
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.
Are you sure to reset SIP interface?(y/n)[n]:y
6.

Confirm the ASRB service board that carries services so that the board can work in
the normal state.
7.

Add POTS users (phones 0-31) to VAG2 so that the users can go online.
8.
Save the data.

huawei(config)#save
----End
Result
When VAG1 and VAG2 communicate with the MGC in the normal state, phones 0-31 belonging
to VAG1 and phones 0-31 belonging to VAG2 can communicate with each other.
Example
Configure VAG1.
vlan 30 standard
port vlan 30 0/0 1
interface vlanif 30
ip address 10.20.10.10 16
quit
voip
ip address media 10.20.10.10 10.20.10.1
quit
ip route-static 10.20.0.0 255.255.0.0 10.20.10.1
interface sip 0
if-sip attribute basic media-ip 10.20.10.10 signal-ip 10.20.10.10 signal-port 5060
transfer udp primary-proxy-ip1 10.20.20.100 primary-proxy-port 5060 home-domain
Issue 02 (2013-10-08)

519

Configuration Guide

huawei sipprofile-index 1
reset
board confirm 0/3
esl user
quit
save
Configure VAG2.
interface vlanif 30
ip address 10.20.10.11 16 sub
quit
voip
ip address media 10.20.10.11 10.20.10.1
quit
ip route-static 10.20.0.0 255.255.0.0 10.20.10.1
interface sip 1
if-sip attribute basic media-ip 10.20.10.11 signal-ip 10.20.10.11 signal-port 5060
transfer udp primary-proxy-ip1 10.20.30.100 primary-proxy-port 5060 home-domain
huawei sipprofile-index 1
reset
board confirm 0/4
esl user
quit
save
9.5 Configuration Example of the VLAN Stacking

Wholesale Service
This topic describes the VLAN stacking wholesale service and how to configure the VLAN
stacking wholesale service on the MA5616.
9.5.1 Configuring the VLAN Stacking Wholesale Service

In a L2 switched 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.
The system is working properly.
l
The user accesses the Internet through the PPPoE dialup.
The device adds an outer VLAN tag to user packets to identify ISPs, and adds an inner
VLAN tag to identify users.
Issue 02 (2013-10-08)

520

Configuration Guide

Networking
Figure 9-14 shows an example network for configuring the VLAN stacking wholesale service.
Users 1 and 2, and users 3 and 4 obtain the broadband service from different ISPs. The
MA5616 supports the VLAN stacking function to implement the multi-ISP wholesale service.
The device adds an outer VLAN tag to user packets to identify ISPs and adds an inner VLAN
tag to identify users. Then, the device forwards the packets to the L2 network. The L2 switch
forwards the user packets to a specified ISP BRAS based on the outer VLAN tags. The ISP
BRAS removes the outer VLAN tags and identifies the user based on the inner VLAN tags.
After being authenticated by the ISP BRAS, the users can obtain the services provided by the
ISP.
Figure 9-14 Example network for configuring the VLAN stacking wholesale service
Data Plan
Table 9-12 provides the data plan for configuring the VLAN stacking wholesale service.
Table 9-12 Data plan for configuring the VLAN stacking wholesale service
Item
Data
ISP 1 user group
Uplink port: 0/0/1

Network-side VLAN ID (outer VLAN tag): 100
Issue 02 (2013-10-08)

521


Configuration Guide
Item
Data
User 1:
l Access port: 0/1/0
l Inner VLAN tag: 11
User 2:
ISP 2 user group
Uplink port: 0/0/1

Network-side VLAN ID (outer VLAN tag): 101
User 3:
User 4:
Procedure
Step 1 Create VLANs.
Network-side VLAN IDs are 100 and 101, and the VLAN type is smart VLAN.
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
The total of the VLANs having been processed is 2
The total of the added VLANs is 2
Step 2 Set the VLAN attribute to stacking VLAN.

NOTE
You can run the stacking outer-ethertype command to set the type of outer Ethernet protocol supported
by VLAN stacking on the MA5616. You can also run the stacking inner-ethertype command to set the
type of inner Ethernet protocol supported by VLAN stacking on the MA5616. To ensure that Huawei device
is interconnected with the device of other vendors, the type of the inner/outer Ethernet protocol must be
the same as that of the interconnect device.
huawei(config)#vlan attrib 100-101 stacking
Are you sure to continue? (y/n)[n]:y
The total of the VLAN(s) which have been operated successfully is 2
Step 3 Add an uplink port to the VLAN.

Add uplink port 0/0/1 to VLAN 100 and VLAN 101.
Issue 02 (2013-10-08)

522


Configuration Guide

Are you sure to add standard port(s)? (y/n)[n]:y
The total of the port VLAN(s) having been added is 2
Step 4 Add service ports to VLANs.

Create service ports for users 1, 2, 3, and 4, and then add the service ports to VLAN 100 and
VLAN 101.
huawei(config)#service-port
pppoe
rx-cttr 6 tx-cttr 6
encap pppoe
rx-cttr 6 tx-cttr 6
pppoe
rx-cttr 6 tx-cttr 6
pppoe
rx-cttr 6 tx-cttr 6
1 vlan 100 vdsl mode ptm 0/1/0 multi-service user-encap
2 vlan
100 vdsl mode ptm 0/1/1 multi-service user-
Step 5 Set the inner VLAN tag.

The inner VLAN tag is used to identify the user. An inner VLAN tag under the same ISP must
be unique. The VLAN tags under different ISPs can be the same with each other.
huawei(config)#display service-port all
{ <cr>|sort-by<K>||<K> }:
Command:
display service-port all
------------------------------------------------------------------------INDEX VLAN VLAN
PORT F/ S/ P VPI VCI
FLOW FLOW
RX TX STATE
ID
ATTR
TYPE
TYPE PARA
------------------------------------------------------------------------0 100 stacking vdl 0/1/ 0 encap pppoe
6
6 up
1 100 stacking vdl 0/1/ 1 encap pppoe
6
6 up
6
6 up
6
6 up
------------------------------------------------------------------------Total : 4 (Up/Down :
4/0)
NOTE
In the actual configuration, the index of the traffic stream may vary according to the number of traffic
streams in the system. You only need to ensure that the actual index corresponds to the inner VLAN tag.

huawei(config)#save
----End
Result
l
Issue 02 (2013-10-08)
After being authenticated by the ISP 1 BRAS, users 1 and 2 can obtain the services provided
by ISP 1.
523

Configuration Guide

After being authenticated by the ISP 2 BRAS, users 3 and 4 can obtain the services provided
by ISP 2.
Configuration File
vlan attrib 100 to 101 stacking
port vlan 100 to 101 0/0 1
service-port 1 vlan 100 vdsl mode
6 tx-cttr 6
6 tx-cttr 6
6 tx-cttr 6
6 tx-cttr 6
ptm 0/1/0 multi-service user-encap pppoe rx-cttr

9.5.2 Configuring the VLAN ID Extension Service

In the application of the VLAN ID extension, the inner VLAN tags are used to identify the user,
or the outer VLAN tag is used to identify the access device and the inner tag is used to identify
the users that access the device. The BRAS identifies the access users based on the L2 VLAN
tag to increase the number of users identified by the VLAN ID, thus increasing the number of
users that access the BRAS.
Prerequisites
l
l
The Internet access service is deployed on the network.
Two VLAN IDs are allocated on the BRAS to identify four access users.
The MA5616 is used on the GE upstream transmission network.
Networking
Figure 9-15 shows the example network for configuring the VLAN ID extension.
Broadband users through multiple MA5616s are authenticated on a BRAS to obtain the
broadband service provided by the carrier. The BRAS supports the user identification through
L2 VLAN. The outer VLAN tag identifies the MA5616 that accesses users, and the inner VLAN
tag identifies the users of the device.
Issue 02 (2013-10-08)

524

Configuration Guide

Figure 9-15 Example network for configuring the VLAN ID extension
Data Plan
Table 9-13 provides the data plan for configuring the VLAN ID extension.
Table 9-13 Data plan for configuring the VLAN ID extension
Item
Data
Uplink port: 0/0/1
Upstream VLAN ID (outer VLAN tag): 100
VLAN attribute: Stacking VLAN
ONU_A:
MA5616_A
User 1:
User 2:
Uplink port: 0/0/1
Upstream VLAN ID (outer VLAN tag): 101
ONU_B:
MA5616_B
VLAN attribute: Stacking VLAN

User 3:
Issue 02 (2013-10-08)

525


Configuration Guide
Item
Data
User 4:
Procedure
l
The procedure for configuring the VLAN ID extension on MA5616_A is as follows:

1.
Create a VLAN.
2.
Set the VLAN attribute to stacking VLAN.

3.
Add an uplink port to the VLAN.

4.
Add service ports to the VLAN.

huawei(config)#service-port vlan 100 vdsl mode ptm 0/1/1 multi-service
user-encap pppoe
rx-cttr 6 tx-cttr 6
huawei(config)#service-port vlan 100 vdsl mode ptm 0/1/2 multi-service
user-encap pppoe
rx-cttr 6 tx-cttr 6
5.
Set the inner VLAN tag.

huawei(config)#display service-port all
{ <cr>|sort-by<K>||<K> }:
Command:
display service-port all
------------------------------------------------------------------------INDEX VLAN VLAN
STATE
ID
ATTR
PARA
PORT F/ S/ P VPI
VCI
TYPE
FLOW
FLOW
RX
TX
TYPE
------------------------------------------------------------------------0
100 common
vdl
0/1/1
encap pppoe
100 common
vdl
0/1/2
encap pppoe
up
up
------------------------------------------------------------------------Total : 2 (Up/Down :
2/0)
NOTE
In the actual configuration, the index of the traffic stream may vary according to the number
of traffic streams in the system. You only need to ensure that the actual index corresponds to
the inner VLAN tag.
6.
Issue 02 (2013-10-08)
Save the data.

526

Configuration Guide

huawei(config)#save
The procedure for configuring the VLAN ID extension on MA5616_B is as follows:

The configuration procedure of MA5616_B is the same as the configuration procedure of
MA5616_A. The only difference lies in the upstream VLAN ID. Hence, it is not described
here.
----End
Result
After being authenticated by the BRAS, the users on MA5616_A and MA5616_B can access
the Internet.
Two users of the MA5616 can be identified according to one outer VLAN tag. In this manner,
the number of the access user based on one VLAN tag is increased.
Configuration File
Configuration file of MA5616_A
vlan 100 smart
port vlan 100 0/0 1
service-port 0 vlan 100 vdsl mode ptm 0/1/1 multi-service user-encap pppoe
6 tx-cttr 6
6 tx-cttr 6
save
rx-cttr
rx-cttr
Configuration file of MA5616_B

vlan 101 smart
port vlan 101 0/0 1
6 x-cttr 6
6 x-cttr 6
save
rx-cttr
rx-cttr
9.6 Configuration Example of the QinQ VLAN Private Line

Service
This topic describes how to configure the private line service based on the QinQ feature. A
virtual local area network (VLAN) packet with the QinQ attribute has VLAN tags of two layers,
inner VLAN tag from the private network and outer VLAN tag from the MA5616. With the two
VLAN tags, a Layer 2 virtual private network (VPN) tunnel is formed between private
networks.This can achieve the interconnection and secure communication among branches in
different areas within the enterprise private network.
Issue 02 (2013-10-08)

527


Configuration Guide
Prerequisite
l
The network devices and lines must be in the normal state.
The service boards must be in the normal state.
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
The two branches of the enterprise are connected to the (metropolitan area network) MAN
through the MA5616. 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 MA5616, 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 user
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.
Figure 9-16 shows an example network for configuring the private line service.
Figure 9-16 Example network for configuring the private line service
LSW
LSW
MAN
ONU_A
ONU_B
Modem
Modem
LAN Switch
LAN Switch
Branch_A
Branch_B
Data Plan
Table 9-14 lists data plan for configuring the private line service.
Issue 02 (2013-10-08)

528

Configuration Guide

Table 9-14 Data plan for configuring the private line service
Item
Data
ONU_A
VDSL port: 0/1/0

Upstream port: 0/0/1
Up stream VLAN ID: 50
BPDU transparent function: enable
Traffic profile index: 5 (default), with the permitted access rate
of 2 Mbit/s
VPI/VCI: 0/35 (the same as that of the modem)
ONU_B
The same as the data plan of MA5616_A
Figure 9-17 shows the flowchart for configuring the private line service.
Issue 02 (2013-10-08)

529

Configuration Guide

Figure 9-17 Flowchart for configuring the private line service
The configurations on both ONU_A and ONU_B are the same. The following considers the
configuration on ONU_A as an example, and describes how to configure the QinQ VLAN private
line service.
Procedure
Step 2 Set the VLAN attribute to QinQ.

huawei(config)#vlan attrib 50 q-in-q
Step 3 Enable transparent transmission of BPDUs.

huawei(config-vlan-srvprof-1)#bpdu tunnel enable

Issue 02 (2013-10-08)

530

Configuration Guide

Step 5 Add a service port to the VLAN by adopting the default traffic profile 5.
huawei(config)#service-port vlan 50 vdsl mode atm 0/1/0 vpi 0 vci 35 rx-cttr 5 txcttr 5

huawei(config)#save
----End
Result
After the configuration, the two branches of enterprise A can communicate with each other, and
various services between private networks are implemented.
Configuration File
vlan 50 smart
vlan attrib 50 q-in-q
bpdu tunnel enable
commit
quit
port vlan 50 0/0 1
service-port vlan 50 vdsl mode atm 0/1/0 vpi 0 vci 35 rx-cttr 5 tx-cttr 5
save
9.7 Configuring the Triple Play Service

This topic describes the triple play service and how to configure the triple play service on the
MA5616 on the GE upstream transmission network.
9.7.1 Configuration Example of the Triple Play Service - Single PVC

for Multiple Services Based on the User-Side VLAN
This topic describes how to configure the triple play service in the single-PVC for multiple
services mode based on the user-side VLAN.
Prerequisites
Before configuring the triple play service, ensure that:
l
The customer premises equipment (CPE) has been configured. Specifically, virtual local
area networks (VLANs) have been configured on the CPE for different services.
All boards of the device are running properly.
The very-high-speed digital subscriber line 2 (VDSL2) line template and alarm template
that need to be bound to ports have been configured. For details about how to configure
the VDSL2 line template or alarm template, see 4.1.3 Configuring the VDSL2 Profile.
l
Issue 02 (2013-10-08)

531


Configuration Guide
VDSL2 user 1 and VDSL2 user 2 are connected to the MA5616 to implement the triple
play.
The Internet service is accessed in the PPPoE mode.
After receiving different traffic streams through the same PVC, the MA5616 provides
different QoS guarantees to the traffic streams according to the user-side VLANs.
Networking
Figure 9-18 shows the example network for configuring the triple play service based on the
user-side VLAN.
Figure 9-18 Example network for configuring the triple play service based on the user-side
VLAN
OSS & RADIUS Server/
RADIUS Proxy
Multicase Sever
BMS
TG
Softswitch
Router
BRAS
LAN Switch
ONU
User1
User2
CPE
CPE
IAD Voice
Gateway
IAD Voice
Gateway
STB
IP Phone
PC
TV
STB
IP Phone
PC
TV
Data Plan
Table 9-15 provides the data plan of the triple play service based on the user-side VLAN.
Issue 02 (2013-10-08)

532

Configuration Guide

Table 9-15 Data plan of the triple play service based on the user-side VLAN
Item
Data
VDSL2
Service ports: 0/1/0 and 0/1/1

Index of the VDSL2 line template bound to the port: 2, where:
l Index of the VDSL2 line profile: 3
l Index of the VDSL2 channel profile: 3
Index of the VDSL2 alarm template bound to the port: 2, where:
l Index of the VDSL2 line alarm profile: 3
l Index of the VDSL2 channel alarm profile: 3
VPI/VCI: 0/35
Traffic
profile
parameters
Internet service: 1 Mbit/s
Uplink port
ID
0/0/1
Upstream
VLANs
Internet service: smart VLAN 102
VoIP service: 64 Kbit/s

IPTV service: no limit
VoIP service: smart VLAN 103

IPTV service: smart VLAN 104
User-side
VLANs

IGMP
version
IGMP v3 (default IGMP version in the multicast VLAN mode)
Multicast
source
Two multicast sources:

ISP 1: with IP address 10.10.10.10, providing the multicast program with IP
address 224.1.1.1
address 224.1.1.2
Multicast
program
library
Programs in multicast VLAN 104:

Program 1: with IP address 224.1.1.1, the program source IP address being
the same as the IP address of ISP 1 (10.10.10.10)
Issue 02 (2013-10-08)
Right profile
Set right profile 0. Profile 0 has the right to watch program 1 in the program
library.
Multicast
users
User 1: User 1 (on port 0/1/0) can watch all the programs.
User 2: User 2 (on port 0/1/1) can watch only program 1.

533

Configuration Guide

Item
Data
Upstream
priority
The 802.1p priorities are used. The VoIP service has priority 6, IPTV service
priority 5, and Internet service priority 1.
Figure 9-19 shows the flowchart for configuring the triple play service based on the user-side
VLAN.
Figure 9-19 Flowchart for configuring the triple play service based on the user-side VLAN
Procedure
l
Configure the Internet service.

1.
Create a VLAN and add an uplink port to the VLAN.

2.
Configure a traffic profile.

Because the VoIP, IPTV, and Internet services are provided through the same port,
you must set the 802.1p priority of each service.
Issue 02 (2013-10-08)

534

Configuration Guide

Generally, the priorities are in a descending order for the VoIP service, IPTV
service, and Internet service. In this example, set the traffic profile index to 7 and
the 802.1p priority of the Internet service to 1.
huawei(config)#traffic table ip index 7 cir 1024 priority 1 prioritypolicy loca
l-Setting
3.

Add service ports to the VLAN and use the traffic profile configured in the preceding
step.
huawei(config)#service-port vlan 102 vdsl mode atm 0/1/0 vpi 0 vci 35
multi-serv
ice user-vlan 2 rx-cttr 7 tx-cttr 7
multi-serv
4.
Save the data.

huawei(config)#save
Configure the VoIP service.

1.
Create a VLAN and add the uplink port to the VLAN.

2.

Set the traffic profile index to 8 and the 802.1p priority of the VoIP service to 6.
huawei(config)#traffic table ip index 8 cir 64 priority 6 priority-policy
localSetting
3.

step.
multi-serv
multi-serv
4.
Save the data.

huawei(config)#save
Configure the IPTV service.

1.

2.

Set the traffic profile index to 9 and the 802.1p priority of the IPTV service to 5.
huawei(config)#traffic table ip index 9 cir off priority 5 priority-policy
local-Setting
3.

step.
Issue 02 (2013-10-08)

535

Configuration Guide

huawei(config)#service-port 10 vlan 104 vdsl mode atm 0/1/0 vpi 0 vci 35

multi-serv
multi-serv
CAUTION
On the MA5616, if the PVC is configured with a priority, the priority of the multicast
packets carried by the PVC is not affected.
4.
Configure the multicast data.

To provision the multicast video service, you also need to configure IGMP proxy and
programs.
a.
Add a multicast VLAN and configure the multicast mode.

huawei(config-mvlan104)#igmp mode
proxy
NOTE
Select a multicast mode according to the actual requirements. In this example, the IGMP
proxy mode is considered.
b.

huawei(config-btv)#igmp uplink-port-mode
default
Are you sure to change the uplink port mode?(y/n)[n]:y
c.
Configure the program library.

sourceip 10.
10.10.10
sourceip 10.
10.10.11
d.
Configure the right profile.

huawei(config-btv)#igmp profile add profile-name profile0
huawei(config-btv)#igmp profile profile-name profile0 program-name
program1 watc
h
e.

huawei(config-btv)#igmp user add service-port 11 auth
huawei(config-btv)#igmp user bind-profile service-port 11 profilename profile0
5.
Save the data.

huawei(config)#save
----End
Issue 02 (2013-10-08)

536

Configuration Guide

Result
After the related upstream device and downstream device are configured, the triple play service
(Internet, VoIP, and IPTV services) is available.
l
Perform the PPPoE dialup on the PC. After the dialup is successful, the user can access the
Internet.
VoIP users 1 and 2 can call each other.
IPTV user 1 on port 0/1/0 can watch all the programs, and IPTV user 2 on port 0/1/1 can
watch program 1 only.
Configuration File
Internet:
vlan 102 smart
port vlan 102 0/0 1
traffic table ip index 7 cir 1024 priority 1 priority-policy local-Setting
service-port vlan 102 vdsl mode atm 0/1/0 vpi 0 vci 35 multi-serv
save
VoIP:
vlan 103 smart
port vlan 103 0/0 1
save
IPTV:
vlan 104 smart
port vlan 104 0/0 1
traffic table ip index 9 cir off priority 5 priority-policy local-Setting
service-port 10 vlan 104 vdsl mode atm 0/1/0 vpi 0 vci 35 multi-serv
multicast-vlan 104
igmp mode proxy
y
btv
igmp uplink-port-mode default
y
multicast-vlan 104
btv
igmp profile add profile-name profile0
igmp profile profile-name profile0 program-name program1 watch
igmp user add service-port 11 auth
igmp user bind-profile service-port 11 profile-name profile0
multicast-vlan 104
Issue 02 (2013-10-08)

537

Configuration Guide

quit
save
9.7.2 Configuration Example of the Triple Play Service - Single PVC

for Multiple Services Based on the User-Side 802.1p
This topic describes how to configure the triple play service in the single-PVC for multiple
services mode based on the user-side 802.1p priority.
Prerequisites
l
The customer premises equipment (CPE) has been configured. Specifically, user-side
802.1p priorities have been configured on the CPE for different services.
l
play.
The Internet service is accessed in the PPPoE mode.
After receiving different traffic streams through the same PVC, the MA5616 provides
different QoS guarantees to the traffic streams according to the user-side 802.1p priority.
Networking
Figure 9-20 shows the example network for configuring the triple play service in the singlePVC for multiple services mode based on the user-side 802.1p priority.
Issue 02 (2013-10-08)

538

Configuration Guide

Figure 9-20 Example network for configuring the triple play service in the single-PVC for
multiple services mode based on the user-side 802.1p priority
RADIUS Proxy
Multicase Sever
BMS
TG
Softswitch
Router
BRAS
LAN Switch
ONU
User1
User2
CPE
CPE
IAD Voice
Gateway
IAD Voice
Gateway
STB
IP Phone
PC
TV
STB
IP Phone
PC
TV
Data Plan
Table 9-16 provides the data plan for configuring the triple play service in the single-PVC for
multiple services mode based on the user-side 802.1p priority.
Table 9-16 Data plan for configuring the triple play service in the single-PVC for multiple
services mode based on the user-side 802.1p priority
Item
Data
VDSL2

VPI/VCI: 0/35
Traffic
profile
parameters
Issue 02 (2013-10-08)


539

Configuration Guide

Item
Data
Uplink port
ID
0/0/1
Upstream
VLANs

User-side
802.1p
priorities
Internet service: 2
IGMP
version
Multicast
source
VoIP service: 3
IPTV service: 4

address 224.1.1.1
address 224.1.1.2
Multicast
program
library

Right profile
library.
Multicast
users
Upstream
priority
Figure 9-21 shows the flowchart for configuring the triple play service in the single-PVC for
multiple services mode based on the user-side 802.1p priority.
Issue 02 (2013-10-08)

540

Configuration Guide

Figure 9-21 Flowchart for configuring the triple play service in the single-PVC for multiple
services mode based on the user-side 802.1p priority
Procedure
l

1.

2.

Because the VoIP, IPTV, and Internet services are provided through the same port,
you must set the 802.1p priority of each service.
l-Setting
3.

step.
multi-serv
ice user-8021p 2 rx-cttr 7 tx-cttr 7
Issue 02 (2013-10-08)

541

Configuration Guide


multi-serv
4.
Save the data.

huawei(config)#save

1.

2.

localSetting
3.

step.
multi-serv
multi-serv
4.
Save the data.

huawei(config)#save

1.

huawei(config)#vlan 104-105
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
The total of the VLANs having been processed is
2
The total of the added VLANs is 2
huawei(config)#port vlan 104-105 0/0
1
It will take several minutes, and console may be timeout, please use
command
idle-timeout to set time
limit
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
2.

Set the traffic profile index to 9 and the 802.1p priority of the IPTV service to 5.
local-Setting
Issue 02 (2013-10-08)

542

Configuration Guide
3.


step.
multi-serv
multi-serv
CAUTION
On the MA5616, if the PVC is configured with a priority, the priority of the multicast
packets carried by the PVC is not affected.
4.

To provision the multicast video service, you also need to configure IGMP proxy and
programs.
a.

proxy
NOTE
b.

default
c.

sourceip 10.
10.10.10
sourceip 10.
10.10.11
d.

huawei(config)#btv
program1 watc
h
e.

Issue 02 (2013-10-08)

543

Configuration Guide


5.
Save the data.

huawei(config)#save
----End
Result
l
Internet.
watch program 1 only.
Configuration File
Internet:
vlan 102 smart
port vlan 102 0/0 1
save
VoIP:
vlan 103 smart
port vlan 103 0/0 1
save
IPTV:
vlan 104-105 smart
y
port vlan 104-105 0/0 1
y
multicast-vlan 104
igmp mode proxy
y
btv
y
multicast-vlan 104
Issue 02 (2013-10-08)

544

Configuration Guide


btv
multicast-vlan 104
quit
save
9.7.3 Configuration Example of the Triple Play Service - Multiple

PVCs for Multiple Services
This topic describes how to configure the triple play service in the multi-PVC for multiple
services mode.
Prerequisites
l
The customer premises equipment (CPE) has been configured. Specifically, permanent
virtual channels (PVCs) have been configured on the CPE for different services.
l
play.
The Internet service is provided in the PPPoE mode.
After receiving different traffic streams, the MA5616 provides different QoS guarantees
to the traffic streams according to the traffic priorities in the PVC.
Networking
Figure 9-22 shows the example network of the triple play service in the multi-PVC for multiple
services mode.
Issue 02 (2013-10-08)

545

Configuration Guide

Figure 9-22 Example network of the triple play service in the multi-PVC for multiple services
mode
RADIUS Proxy
Multicase Sever
BMS
TG
Softswitch
Router
BRAS
LAN Switch
ONU
User1
User2
CPE
CPE
IAD Voice
Gateway
IAD Voice
Gateway
STB
IP Phone
PC
TV
STB
IP Phone
PC
TV
Data Plan
Table 9-17 provides the data plan for configuring the triple play service in the multi-PVC for
multiple services mode.
Table 9-17 Data plan for configuring the triple play service in the multi-PVC for multiple
services mode
Item
Data
VDSL2

VPI/VCI for the Internet service: 0/37
VPI/VCI for the VoIP service: 0/36
VPI/VCI for the IPTV service: 0/35
Issue 02 (2013-10-08)

546

Configuration Guide

Item
Data
Traffic
profile
parameters
Uplink port
ID
0/0/1
VLANs


IGMP
version
Multicast
source

address 224.1.1.1
address 224.1.1.2
Multicast
program
library

Right profile
library.
Multicast
users
Upstream
priority
Figure 9-23 shows the flowchart for configuring the triple play service in the multi-PVC for
multiple services mode.
Issue 02 (2013-10-08)

547

Configuration Guide

Figure 9-23 Flowchart for configuring the triple play service in the multi-PVC for multiple
services mode
Procedure
l

1.

2.

The VoIP, IPTV, and Internet services are provided through the same port.
Therefore, users must set the 802.1p priority of each service.
l-Setting
3.

step.
huawei(config)#service-port vlan 102 vdsl mode atm 0/1/0 vpi 0 vci 37 rxcttr 7 tx-cttr 7
Issue 02 (2013-10-08)

548

Configuration Guide
4.

Save the data.

huawei(config)#save

1.

2.

localSetting
3.

step.
4.
Save the data.

huawei(config)#save

1.

smart
huawei(config)#port vlan 104 0/0
1
2.

Set the traffic profile index to 9 and the priority of the IPTV service to 5.
local-Setting
3.

step.
rx-cttr 9 tx-cttr 9
rx-cttr 9 tx-cttr 9
NOTE
On the MA5616, if the PVC is configured with a priority, the priority of the multicast packets
carried by the PVC is not affected.
4.

To provide the multicast video service, users also need to configure IGMP proxy and
programs.
a.

Issue 02 (2013-10-08)

549

Configuration Guide

proxy
NOTE
b.

default
c.

sourceip 10.
10.10.10
sourceip 10.
10.10.11
d.

program1 watc
h
e.

5.
Save the data.

huawei(config)#save
----End
Result
l
Internet.
watch only program 1.
Configuration File
Internet:
vlan 102 smart
port vlan 102 0/0 1
Issue 02 (2013-10-08)

550

Configuration Guide

save
VoIP:
vlan 103 smart
port vlan 103 0/0 1
save
IPTV:
vlan 104-105 smart
y
port vlan 104-105 0/0 1
y
service-port 10 vlan 105 vdsl mode atm 0/1/0 vpi 0 vci 35 rx-cttr 9 tx-cttr 9
service-port 11 vlan 105 vdsl mode atm 0/1/1 vpi 0 vci 35 rx-cttr 9 tx-cttr 9
multicast-vlan 104
igmp mode proxy
y
btv
y
multicast-vlan 104
btv
multicast-vlan 104
quit
save
Issue 02 (2013-10-08)

551

Configuration Guide
10
10 FTTB and FTTC Service Overview
FTTB and FTTC Service Overview
About This Chapter

This topic describes FTTB and FTTC services from basic concepts, network scenarios, typical
configurations, and ONU capability sets to provide necessary background information for FTTB
and FTTC service configuration in different scenarios.
10.1 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.2 Scenario and Hardware Configuration
The typical FTTB and FTTC networking scenarios and their OLT and ONU hardware
configurations are listed in the table below.
10.3 Scenario and Hardware Configuration (10G GPON)
The typical 10G GPON FTTB and FTTC networking scenarios and their OLT and ONU
hardware configurations are listed in the table below.
10.4 GPON ONU Capability Sets
This topic describes the hardware capabilities, features, and positioning of GPON ONUs in
FTTB and FTTC networks.
10.5 10G GPON ONU Capability Sets
This topic describes the hardware capabilities, features, and positioning of 10G GPON ONUs
in FTTB and FTTC networks.
Issue 02 (2013-10-08)

552

Configuration Guide
10.1 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

PC
ONU
TV
PE-AGG
OLT
STB
NGN/IMS
UPE
Metro Network
Laptop
Splitter
Phone
STB
TV
Phone
Internet
UPE
HGW
PC
IPTV
Headend
PE-AGG
ONU
User Side
Access Side
Network Side
User Side
Issue 02 (2013-10-08)
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.

553

Configuration Guide
Access Side
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.
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.
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 are also called multi-dwelling units (MDUs).
This document uses name "ONU" in a unified manner.
Split Ratio
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.
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.
Issue 02 (2013-10-08)

554

Configuration Guide
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 UPEs, 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
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.
10.2 Scenario and Hardware Configuration

The typical FTTB and FTTC networking scenarios and their OLT and ONU hardware
configurations are listed in the table below.
Scenario
Description
OLT Typical
Configuration
MDU
Configuration
(Main Control Board

+
Service Board
+Upstream Board)
FTTB
Networki
ng (LAN
Access
Without
HGW)
Issue 02 (2013-10-08)
l The ONU is deployed in

the building and is
connected to the user's
home through the
category-5 cable.
l SCUN+GPBC/
GPBD+
GICF/GICG/X2CA
ONUs applicable to
this scenario:
MA5612, MA5616
l The ONU provides FE

and POTS ports for the
Internet access and VoIP
services.
555

Configuration Guide
Scenario
Description
OLT Typical
Configuration
MDU
Configuration
(Main Control Board

+
Service Board
+Upstream Board)
FTTB/C
Networki
ng (xDSL
Access
Without
HGW)

the building or street fiber
distribution terminal and
is connected to the user's
home through the twisted
pair cable.
ONUs applicable to
this scenario:
MA5616,
MA5622A,
MA5603T
l The ONU provides xDSL

services.
FTTB
+HGW
Networki
ng (ONU
Providin
g the
VoIP
Service)

uses LAN or xDSL to
connect to the HGW
deployed at user's home.
The HGW provides
service access interfaces
and the built-in IAD of
the ONU provides the
VoIP service.
l The HGW provides the
Internet access and IPTV
services by connecting to
the upstream ONU using
LAN or xDSL.
Issue 02 (2013-10-08)

ONUs applicable to
this scenario:
MA5612, MA5616,
MA5622A,
MA5603T. Among
these ONUs,
l ONUs with LAN
ports include
MA5612,
MA5616.
l ONUs with xDSL
ports include
MA5616,
MA5622A,
MA5603T.
556

Configuration Guide
Scenario
Description
OLT Typical
Configuration
MDU
Configuration
(Main Control Board

+
Service Board
+Upstream Board)
FTTB
+HGW
Networki
ng (HGW
Providin
g the
VoIP
Service)

uses LAN or xDSL to
connect to the HGW
placed at user's home.
Internet access, IPTV,
and VoIP services by
connecting to the
upstream ONU using
LAN or xDSL. The builtin IAD of the HGW
provides the VoIP
service.
ONUs applicable to
this scenario:
MA5612, MA5616,
MA5622A,
MA5623,
MA5623A,
MA5603T. Among
these ONUs,
l ONUs with LAN
ports include
MA5612,
MA5616.
l ONUs with
ADSL2+ ports
include MA5616,
MA5603T.
l ONUs with
VDSL2 ports
include MA5616,
MA5622A,
MA5623,
MA5623A,
MA5603T.
10.3 Scenario and Hardware Configuration (10G GPON)

The typical 10G GPON FTTB and FTTC networking scenarios and their OLT and ONU
hardware configurations are listed in the table below.
Issue 02 (2013-10-08)

557

Configuration Guide
Scenario
Description
OLT Typical
Configuration
MDU
Configuration
(Main Control Board

+
Service Board
+Upstream Board)
FTTB
Networki
ng (LAN
Access
Without
HGW)

the building and is
connected to the user's
home through the
category-5 cable.
FTTB/C
Networki
ng (xDSL
Access
Without
HGW)

is connected to the user's
home through the twisted
pair cable.
l The ONU provides FE

services.
l SCUN+XGBC
+GICF/GICG/
X2CA
ONUs applicable to
this scenario:
MA5616, MA5612
l SCUH+XGBC
+GICF/GICG/
X2CA
ONUs applicable to
this scenario:
MA5616
l The ONU provides xDSL

services.
FTTB/C
+HGW
Networki
ng (ONU
Providin
g the
VoIP
Service)

uses LAN or xDSL to
connect to the HGW
deployed at user's home.
The HGW provides
service access interfaces
and the built-in IAD of
the ONU provides the
VoIP service.
Internet access and IPTV
services by connecting to
the upstream ONU using
LAN or xDSL.
Issue 02 (2013-10-08)

ONUs applicable to
this scenario:
MA5616, MA5612.
Among these ONUs,
l ONUs with LAN
ports include
MA5616,
MA5612.
l ONUs with xDSL
ports include
MA5616.
558

Configuration Guide
Scenario
Description
OLT Typical
Configuration
MDU
Configuration
(Main Control Board

+
Service Board
+Upstream Board)
FTTB/C
+HGW
Networki
ng (HGW
Providin
g the
VoIP
Service)

uses LAN or xDSL to
connect to the HGW
placed at user's home.
Internet access, IPTV,
and VoIP services by
connecting to the
upstream ONU using
LAN or xDSL. The builtin IAD of the HGW
provides the VoIP
service.
ONUs applicable to
this scenario:
MA5616, MA5612.
Among these ONUs,
l ONUs with LAN
ports include
MA5616,
MA5612.
l ONUs with
ADSL2+ ports
include MA5616.
l ONUs with
VDSL2 ports
include MA5616.
10.4 GPON ONU Capability Sets

This topic describes the hardware capabilities, features, and positioning of GPON ONUs in
FTTB and FTTC networks.
ONU Capability Sets

Table 10-1 shows the ONU capability sets provided.
NOTE
The ONU Version Supported column in Table 10-1 lists only ONU versions supported for the FTTx
V100R006 and later versions.
Issue 02 (2013-10-08)

559

Configuration Guide
Table 10-1 ONU capability sets

ONU Type
User Port
ONU
Version
Supported
Feature and
Positioning
MA5620
The MA5620 has the following

specifications:
l V800R30
8C00
l 1: 8 FE electrical ports+8 POTS

ports
l V800R31
0C00
It is mainly used
in FTTB
networks.

ports
ports
MA5626

specifications based on the supporting
capabilities of service ports:
V800R308C
00
It is mainly used
in FTTB
networks.
l 1: 8 FE electrical ports
l 4: 4 FE electrical ports+4 GE
electrical ports (PoE)
V800R308C
01
l 1: 8 FE electrical ports (PoE)

V800R310C
00
l 5: 8 FE electrical ports (reverse PoE)
MA5622A
l 24 VDSL2 ports+24 POTS ports

l Support vectoring
MA5623
Issue 02 (2013-10-08)
24 VDSL2 ports

V800R311C
00
It is mainly used
in FTTB and
FTTC networks.
V800R311C
00
560

Configuration Guide
ONU Type
User Port
ONU
Version
Supported
MA5623A
l 24 VDSL2 ports
V800R311C
01
l Support vectoring
MA5612
For the bottom plate with POTS ports:

l Supports 2xGE electrical interfaces
+6xFE electrical interfaces
+48xPOTS interfaces+(optional)
1xRF interface when two ASNB
boards are configured.
+16xPOTS interfaces+(optional)
1xRF interface when two EIUC
boards are configured.
l V800R30
8C00
l V800R30
8C01
l V800R31
0C00
Feature and
Positioning
It is mainly used
in FTTB
networks and
some networks
carrying private
line access
services.
l V800R31
1C00

+6xFE electrical interfaces+16xE1/
T1 interfaces+16xPOTS interfaces+
(optional)1xRF interface when two
E81A boards are configured.
For the bottom plate without POTS
ports:
+32xPOTS interfaces when two
ASNB boards are configured.
+22xFE electrical interfaces when
two EIUC boards are configured.
+6xFE electrical interfaces+16xE1/
T1 interfaces when two E81A boards
are configured.
Issue 02 (2013-10-08)

561

Configuration Guide
ONU Type
User Port
ONU
Version
Supported
Feature and
Positioning
MA5616
(CCUB
control
board)
l Fully configured with four ADPE

boards: 256 ADSL2+ ports
l V800R30
8C01
l Fully configured with four VDLE

boards: 128 VDSL2 ports
l V800R30
9C00
It is mainly used
in FTTB and
FTTC networks.
l Fully configured with four SHLH

boards: 64 SHDSL ports
l V800R31
0C00
l Fully configured with four ASPB

boards: 256 POTS ports
l V800R31
1C00
l Fully configured with four DSLD

boards: 32 ISDN ports
l Fully configured with four CALE
boards: 128 ADSL2+ ports+128
POTS ports
MA5616
(CCUC
control
board)

l V800R30
8C02
l Fully configured with four VDMM

l V800R30
9C00

l V800R31
0C00

l V800R31
1C00
l Fully configured with four EIUA

boards: 64 FE ports
POTS ports
l Fully configured with two EIUD
boards (only in slots 1 and 2): 8 GE
optical ports (or 8 GE electrical
ports)+8 FE optical ports
Issue 02 (2013-10-08)

562

Configuration Guide
ONU Type
User Port
ONU
Version
Supported
MA5616
(CCUE
control
board)

V800R311C
01
Feature and
Positioning
l Fully configured with four VDMM

POTS ports
l Support vectoring
MA5652

specifications:
V800R310C
00
It is mainly used
in FTTB and
FTTC networks.
l Fully configured with six ADPD/

ADQD boards: 384 ADSL2+ ports
l V800R00
8C01
l Fully configured with six VDMF

l V800R01
1
It is mainly used
in FTTB and
FTTC networks.
FTTC networks
account for over
half of the total
applications.
l 1: 24 VDSL2 ports
l 2: 16 VDSL2 ports
l 3: 24 VDSL2 ports+1 RF port
l 4: 8 VDSL2 ports+1 RF port
MA5603T
l Fully configured with six SHLM

boards: 96 ATM SHDSL/EFM
SHDSL ports
l Fully configured with six
H802EDTB boards: 96 TDM
SHDSL ports
l Fully configured with six ASPB
l Fully configured with six DSRD
boards: 192 ISDN BRA ports
l Fully configured with six
H801EDTB boards: 96 ISDN PRA
ports
l Vectoring is supported in V800R011
Issue 02 (2013-10-08)

563

Configuration Guide
10.5 10G GPON ONU Capability Sets

This topic describes the hardware capabilities, features, and positioning of 10G GPON ONUs
in FTTB and FTTC networks.
10G GPON ONU Capability Sets

Table 10-2 shows the 10G GPON ONU capability sets provided.
NOTE
The ONU Version Supported column in Table 10-2 lists only ONU versions supported for the FTTx
V100R011 version.
Table 10-2 10G GPON ONU capability sets

ONU Type
User Port
ONU
Version
Supported
Feature and
Positioning
MA5612

specifications:
V800R311C
00
It is mainly used
in FTTB
networks and
some networks
carrying private
line access
services.
V800R311C
00
It is mainly used
in FTTB and
FTTC networks.
l Ethernet access board: EIUC

l E1 service board: E81A
MA5616
(CCUE
control
board)

specifications:
l Ethernet access board: EIUD, EIUA
l ADSL2 service boards: ADLE and
ADPE
l ADSL2+ + POTS combo service
board: CALE
l VDSL2 service boards: VDGE,
VDSH, VDTH, VDSE, VDLE, and
VDLF
l VDSL2 + POTS combo board:
CVLC
l Voice service boards: ASRB and
ASPB
l SHDSL service board: SHLH
l ISDN service board: DSLD
Issue 02 (2013-10-08)

564

Configuration Guide
11
11 Principle of FTTB and FTTC Data Plan
Principle of FTTB and FTTC Data Plan
About This Chapter

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.
11.1 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.
11.2 Principle of Device Management Data Plan
The device management plan includes channel management plan and the IP address plan.
11.3 Principle of QoS Data Plan
The QoS plan for FTTB is an E2E planning, and it can be divided into following policies: traffic
classification, marking, scheduling, traffic monitoring, and DBA policies.
11.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.
11.5 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.
11.6 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.
11.7 Principle of IPTV Service Data Plan
The IPTV service plan mainly includes the plan of VLANs and VLAN translation policies in
different network scenarios, and the plan of IPTV services.
Issue 02 (2013-10-08)

565

Configuration Guide
11.1 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 and
MDU.
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 and
MDU.
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 02 (2013-10-08)

566

Configuration Guide
User Security
Security
Vulnerability
Solution

Suggestion
MAC spoofing
Enable the anti-MACduplicate function for OLT

and MDU.
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
and MDU.
After anti-MAC spoofing is enabled,

the system can prevent users from
forging IP addresses to perform
malicious attacks.
deployment.
IP spoofing
Enable the anti-IP spoofing

function for MDU.
After anti-IP spoofing is enabled, the

system can prevent users from forging
IP addresses to perform malicious
attacks.
deployment.
Issue 02 (2013-10-08)

567

Configuration Guide
Service Security
Security
Vulnerability
Solution

Suggestion
Unauthorized
broadband access of
small enterprises
(IPoE)
DHCP option 82 is enabled

on OLT and MDU, 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
Internet access service.
Broadband access of
residential users
(PPPoE), user
account theft/
borrowing
PPPoE+ (PITP) is enabled

on OLT and MDU, 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.
l Implements anti-IP spoofing.
l Implements anti-user ID spoofing.
l Implements anti-MAC spoofing.
Use this solution for the PPPoE
Internet access service.
11.2 Principle of Device Management Data Plan

The device management plan includes channel management plan and the IP address plan.
Issue 02 (2013-10-08)
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.

568

Configuration Guide
Plan
Device/Service
Introduction
ONU
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 Itms.
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
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.
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).
11.3 Principle of QoS Data Plan

The QoS plan for FTTB is an E2E planning, and it can be divided into following policies: traffic
classification, marking, scheduling, traffic monitoring, and DBA policies.
Issue 02 (2013-10-08)

569

Configuration Guide
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 4
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's actual planning.
Traffic Monitoring and DBA Policies
Issue 02 (2013-10-08)
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
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.
Configure rate
limit by a traffic
profile as
required.
[Remark 2]
No rate limit

No rate limit
570

Configuration Guide
Items
Management
service
Internet
access service
VoIP service
IPTV service
Rate limit on
ONU upstream
port
Set ONU port rate limit or xDSL line rate limit as required. [Remark 2]
Rate limit on
ONU
downstream
port
Set ONU port rate limit or xDSL line rate limit as required. [Remark 2]
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.
Table 11-1 Reference Service Bandwidth of Each service for Each User
Issue 02 (2013-10-08)
Service
Type
Upstrea
m
Bandwi
dth
Downstream
Bandwidth
Bandwidth Description
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
VoIP
service
200 kbit/
s
200 kbit/s
The upstream bandwidth and the downstream

bandwidth of VoIP service are symmetrical.
The actual bandwidth varies with the coding
format. This bandwidth is calculated for two
POTS ports.
IPTV
service
(commo
n
program
)
2.5 Mbit/schannel
IPTV
service
(high
definitio
n
program
)
9.7 Mbit/s 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 multi STBs access).
The upstream bandwidth is mainly used for
transmitting IGMP packets, which requires
little bandwidth and can be neglected.

571

Configuration Guide
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.
Different service packets of ONUs are distinguished by 802.1p priorities and are mapped
to GEM ports based on 802.1p priorities so that 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 assured bandwidth of all ONTs under a PON port and the fixed bandwidth of
OMCI management channel is smaller than the GPON upstream bandwidth. Some
bandwidth must be reserved for future service expansion.
11.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.
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.
NOTE
The system does not support the grouping. All ports are added to the default
vectoring group 1.
Issue 02 (2013-10-08)

572

Configuration Guide
Item
Description
Policy for activating a

vectoring legacy
customer premises
equipment (CPE)
A vectoring 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 Auto: The vectoring legacy CPE can be activated in the
common VDSL2 mode. That is, the vectoring legacy CPE is
activated in the non-vectoring mode and the performance of the
vectoring system is affected. This activation policy is generally
used at the initial stage of the vectoring application. At this
stage, a lot of CPEs need to be upgraded or replaced and the
vectoring performance is unconcerned.
l Limit: The vectoring legacy CPE can be activated in the
common VDSL2 mode. However, the line is 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 at the medium stage of the vectoring
application. At this stage, some CPEs are not upgraded or
replaced.
l Force: The vectoring legacy CPE cannot be activated in the
common VDSL2 mode (G.993.2). This activation policy is
generally used at the mature stage of the vectoring application.
At this stage, the vectoring performance is concerned and
unnecessary crosstalk is better to be canceled.
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.
NOTE
Current vectoring does not support the VDSL2 line profile 30a.
11.5 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 02 (2013-10-08)

573

Configuration Guide
VLAN and VLAN Translation Policy

Application
Scenario
VLAN Plan
FTTB networking
(without HGWs)
Double-tagged
VLAN (S-VLAN
+C-VLAN)
FTTB+HGW
networking (ONU
providing the VoIP
service)
FTTB+HGW
networking (HGW
providing the VoIP
service)
VLAN Translation
ONU
OLT
The inner C-VLAN is

mapped based on user
port to ensure that
ONUs under the same
PON board do not
have the same CVLAN.
The OLT translates

VLANs and adds an SVLAN. C'-VLAN <->
S-VLAN + C-VLAN
HGWs (LAN
upstream
transmission)
l Untagged
upstream packets
of HGWs: ONUs
map C-VLANs
based on user port.
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.
TIP
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 02 (2013-10-08)
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.
574

Configuration Guide
11.6 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 and VLAN translation policy

Application
Scenario
VLAN
Plan
FTTB
networking
(without
HGWs)
VLAN Translation
Remarks
ONU
OLT
Singletagged
VLAN
ONUs provide the

VoIP service and
use the same SVLAN.
Transparently
transmits packets.
FTTB+HGW
networking
(ONU
providing the
VoIP service)
Singletagged
VLAN
ONUs provide the

VoIP service and
use the same SVLAN.
Transparently
transmits packets.
This solution is
recommended.
Doubletagged
VLAN (SVLAN+CVLAN)
ONUs provide the

VoIP service and
use the same CVLAN.
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 CVLANs.
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)
HGWs (xDSL
upstream
transmission):
ONUs translate
PVCs to C'VLANs.
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.
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
Issue 02 (2013-10-08)

575

Configuration Guide
the OLTs connected to one VoIP SR to avoid an excessively large broadcast domain of the
VoIP SR and convergence switch.
l
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.
VoIP data plan based on H.248 or SIP

Item
MG
interface/
SIP
interface
data
NOTE
(Must be
the same as
that on the
MGC or
IMS core
network
device.)
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
MG interface/SIP interface ID
Signaling port ID
Choose the transmission method according

to the requirement on the MGC/IMS side.
IP address of primary MGC

(H.248)/IP address of primary
IMS device (SIP)
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.
Port ID of primary MGC

(H248)/port ID of primary
IMS device (SIP)
Issue 02 (2013-10-08)
Codec mode
The codec mode is selected according to the

requirements on the MGC/IMS side.
Generally, the text mode is used.
Transmission mode

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
softswitches do not support V3.

576

Configuration Guide
Item
VoIP user
data
Remarks
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

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:
government users)
government users)
l cat3: normal (common users). This is the
default value.
User type
According to the service requirements, user

type needs to be specified. The user type
includes the following:
l DEL: direct exchange lines (default)
Common
Parameter
Issue 02 (2013-10-08)
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
International 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.

577

Configuration Guide
Item
Remarks
PSTN port attributes
If the PSTN port needs to support the polarity

reversal accounting, the PSTN port needs to
be configured to support the polarity reversal
pulse. Other attributes do not need to be
modified if there is no special requirement.
Ringing current attributes
When the attributes of ring current are

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.
11.7 Principle of IPTV Service Data Plan

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 02 (2013-10-08)

578

Configuration Guide
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
Single
tagged
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 02 (2013-10-08)
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.

579

Configuration Guide
Applicatio
n Scenario
Servic
e Type
VLA
N
Plan
VLAN Translation
ONU
OLT
VoD
Single
tagged
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.
Note
l
IPTV service is a closed service self-operated by carriers, and single-tagged S-VLAN is

recommended.
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
Issue 02 (2013-10-08)
Data Item
Remarks
Multicast protocol
The OLT and ONU generally use IGMP proxy. The ONT or HGW
generally uses IGMP snooping.

580

Configuration Guide
Data Item
Remarks
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 02 (2013-10-08)
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.

581

Configuration Guide
12
12 Configuring Services in Various FTTB and FTTC

Scenarios (GPON and 10G GPON Access)
Configuring Services in Various FTTB
and FTTC Scenarios (GPON and 10G GPON

Access)
About This Chapter

This topic describes how to configure the Internet access service, voice service and multicast
service in GPON/10G GPON access mode in FTTB/FTTC networking scenarios.
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, 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
service provisioning efficiency.
Generally, the xPON configuration mode is determined in a new deployment and will not be
changed.
NOTE
For commands for the distributed configuration mode, see PON distributed-mode commands in the Command
Reference.
The description of this topic is based on the mode below. You can query the current mode in the
diagnosis mode.
Issue 02 (2013-10-08)
Mode
Query Method
GPON profile mode (system

default)
huawei(config)#diagnose
huawei(diagnose)%%display xpon mode
------------------------------------------Current config mode: Profile-mode
-------------------------------------------

582

Configuration Guide

Mode
Query Method
ADSL2+ common mode

(RFC2662 mode)
huawei(config)#diagnose
huawei(diagnose)%%display xdsl mode
------------------------------------------ADSL Current mode : rfc2662
VDSL Current mode : tr129
--------------------------------------------
VDSL2 common mode (TR129

mode)
12.1 FTTB Networking (LAN Access Without HGW)

In FTTB networking (LAN access without the HGW), 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 FTTB networking.
12.2 FTTB/C Networking (xDSL Access, Without HGW)
In the Fiber-to-the-building/curb (FTTB/C) network, 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.
12.3 FTTB/FTTC+HGW 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.
12.4 FTTB/FTTC+HGW Networking (HGW Providing the VoIP Service)
In an FTTB/FTTC+HGW network, 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.
Issue 02 (2013-10-08)

583

Configuration Guide

12.1 FTTB Networking (LAN Access Without HGW)

In FTTB networking (LAN access without the HGW), 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 FTTB networking.
12.1.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 supported 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 12-1, 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.
ONU for FTTB networking: MA5612, MA5616.

Figure 12-1 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
PO
TS
Internet
UPE
LAN
PE-AGG
ONU
Phone
Issue 02 (2013-10-08)

584

Configuration Guide

12.1.2 Configuration Procedure

Figure 12-2 shows the configuration roadmap diagram in the FTTB and FTTC networking
scenarios using LAN access without HGWs.
Figure 12-2 Configuration Roadmap Diagram in the FTTB and FTTC Networking Scenarios
Using LAN Access Without HGWs
Configurations on the OLT:
Configurations on the ONU (logged

in from the OLT):
1 Adding an ONU to the OLT.
4 Configure the Internet

access service.
5
Configuring the management channel
2 between the OLT and the ONU.
Configure the VoIP

service.
Configuring the service channel
Configuring link
aggregation,
6 Configuring link aggregation, congestion
6 congestion control,
control, and security policies.
and security
policies.
Metro
Network
PC
VLAN
Phone
ONU
OLT
Upstream port
Downstream port
Internet service channel
Voice service channel
Management channel
Internet service flow
Voice service flow
Note:
VLAN in the figure contains management VLAN and different
service VLAN, and the specific service port should be added to the
corresponding VLAN.
The following table lists the detailed description steps..
Issue 02 (2013-10-08)
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.

585


Configuration Guide
Item
Procedure
Configure the
service channel
between the
OLT and the
ONU.
Remarks
l Configure
the Internet
access
service
channel.
l Configure
the VoIP
service
channel.
ONU
The ONU provides only the Internet access

service and the VoIP service in the FTTB
and FTTC network using xDSL access
without HGWs. Therefore, you need to
create an Internet access service channel and
a VoIP service channel on the OLT.
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.
Configure the
H.248 VoIP
service on the
ONU.
Configure the
SIP VoIP
service on the
ONU.
OLT
ONU
Configure the link aggregation,

congestion control, and security
policy.
The global configuration of link aggregation

and upstream queue scheduling based on
priorities ensures service reliability. The
global configuration of security policies
ensures service security.
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.
12.1.3 Adding an ONU to an OLT

Services can be configured for an ONU only after the ONU is successfully added to an OLT.
Issue 02 (2013-10-08)

586

Configuration Guide

Context
l
When an ONU is added, corresponding profiles need to be bound to the ONU, including
the dynamic bandwidth allocation (DBA) profile, line profile, and alarm profile. For details
about functions and configuration methods for these profiles, see Table 12-1.
Table 12-1 Introduction to ONU profiles
Profile
Type
Function
Command
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.
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 02 (2013-10-08)
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.

587


Configuration Guide
Data plan
Table 12-2 Data plan
Item
Data
DBA profile
Profile name: fttb_dba

Profile type: type3
Assured bandwidth: 8 Mbit/s
Maximum bandwidth: 20 Mbit/s
Line profile
Profile name: fttb(c)

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
Procedure
Step 1 Configure GPON ONU profiles.
1.
Configure a DBA profile.

huawei(config)#dba-profile add profile-name fttb_dba type3 assure 8192 max
20480
2.
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 T-CONT 4 to DBA profile fttb_dba.

huawei(config-gpon-lineprofile-10)#tcont 4 dba-profile-name fttb_dba
c.
In the line profile mode, bind the GEM port to the T-CONT.
l Add GEM port 11 to carry management service flows.
l Add GEM port 12 to carry Internet access service flows.
l Add GEM port 13 to carry VoIP service flows.
Bind GEM ports 11, 12, and 13 to T-CONT 4. In configuring, QoS policies for various
service flows also need to be configured. For details about QoS data plan, see 11.3
Principle of QoS Data Plan.
Issue 02 (2013-10-08)

588

Configuration Guide

huawei(config-gpon-lineprofile-10)#gem add 11 eth tcont 4 cascade on

d.
Configure mapping between the GEM port and the ONU-side service.
Set the mode for mapping the GEM port to the ONU-side service to the VLAN
mapping mode (default). Map management service flows (the CVLAN ID is 8) to
GEM port 11, Internet access service flows (the CVLAN ID is 1001) to GEM port 12,
and VoIP service flows (the CVLAN ID is 200) to GEM port 13.
huawei(config-gpon-lineprofile-10)#gem mapping 11 0 vlan 8
e.
After the configuration is completed, run the commit command to make the
configured parameters take effect.
huawei(config-gpon-lineprofile-10)#commit
huawei(config-gpon-lineprofile-10)#quit
3.
(Optional) Add an alarm profile.

l 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.
l In this example, the default alarm profile is used and therefore the configuration of the
alarm profile is not required.
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)#interface gpon 0/2
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)#port 1 ont-auto-find enable
huawei(config-if-gpon-0/2)#display ont autofind 1
huawei(config-if-gpon-0/2)#ont confirm 1 ontid 1 sn-auth 32303131B39FD641
snmp ont-lineprofile-name fttb(c)
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.
huawei(config-if-gpon-0/2)#display ont info 1 1
--------------------------------------------------------------------F/S/P
: 0/2/1
Issue 02 (2013-10-08)

589

Configuration Guide

ONT-ID
: 1
Control flag
: active
//The ONU
Run state
: online
//The ONU
Config state
: normal
//The ONU
normally.
...//The rest of the response information is
huawei(config-if-gpon-0/2)#quit
is activated.
is online.
configurations are recovered
not provided here.
----End
Follow-up Procedure
When Config state is failed, Run state is offline, or Match state is mismatch:
l
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.
12.1.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
Issue 02 (2013-10-08)
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
Management VLAN ID: 8
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
Management VLAN type:

smart VLAN
Inband management IP
address: 192.168.50.2/24

590

Configuration Guide

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.
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).
huawei(config-if-gpon-0/2)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask
255.255.255.0 gateway
192.168.50.254 vlan 8
huawei(config-if-gpon-0/2)#quit
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
user-vlan 8 rx-cttr 6 tx-cttr 6
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.
l On the OLT, you can remote log in to the ONU to perform the configuration.
----End
12.1.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 12-3. Select either mode as
required.
Issue 02 (2013-10-08)

591

Configuration Guide

Table 12-3 Adding service flows

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.
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

11.5 Principle of Internet Access
Service Data Plan.
OLT VLAN ID (VLAN

transparently transmitting the
ONU service): 200

11.6 Principle of VoIP Service
Data Plan.
ONU VLAN ID: 200

Procedure
l
Configure the channel for the Internet access service.

1.
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.
2.
Issue 02 (2013-10-08)
Configure the corresponding traffic profile.

592

Configuration Guide

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.
3.
Configure service flows to receive and transparently transmits the Internet access
service from the ONU.
According to the data plan,
For the OLT: The SVLAN ID is 100, inner VLAN ID is 258. The user-side VLAN
ID of the OLT is the same as the upstream VLAN ID of the ONU, that is, 1001.
The Internet access service uses GEM port 12.
For the ONU: The upstream VLAN ID is 1001.
huawei(config)#service-port 101 vlan 100 gpon 0/2/1 ont 1 gemport 12 multiservice
user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6 txcttr 6
Configure the channel for the VoIP service.

1.
Configure the SVLAN ID to 200 and VLAN type to smart VLAN. Add upstream port
0/19/0 to VLAN 200.
2.

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.
local-setting
3.
Configure service flows to receive and transparently transmits the VoIP service from
the ONU.
For the OLT: The SVLAN ID is 200. The user-side VLAN ID of the OLT is the
same as the upstream VLAN ID of the ONU, that is, 200. The VoIP service uses
GEM port 13.
----End
Issue 02 (2013-10-08)

593

Configuration Guide

12.1.6 Configuring 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 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 11.1 Principle of Security Data
Plan.
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.
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 11.3 Principle of QoS Data Plan.
huawei(config)#cos-queue-map cos0 0 cos4 4 cos5 5 cos6 6
Configure system security.
Enable deny of service (DoS) anti-attack on both the OLT and optical network units
(ONUs).
1.
Run the security anti-dos enable command to globally enable DoS anti-attack.
2.
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.
3.
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 both the OLT and ONUs.

Run the security anti-ipattack enable command to enable IP address anti-attack.
Configure user security.
Issue 02 (2013-10-08)
Enable MAC address anti-flapping on both the OLT and ONUs.

594

Configuration Guide

Run the security anti-macduplicate enable command to enable MAC address antiflapping.
Enable MAC address anti-spoofing on both the OLT and ONUs.

1.
In global config mode, run the security anti-macspoofing enable command to

globally enable MAC address anti-spoofing.
2.
Enable MAC address anti-spoofing at VLAN level in global config mode or

service profile mode:
a.
In global config mode, run the security anti-macspoofing vlan command

to enable MAC address anti-spoofing.
b.
Perform the following operations to enable MAC address anti-spoofing in

a.
Run the vlan service-profile command to create a VLAN service

profile.
b.
Run the security anti-macspoofing enable command to enable MAC

address anti-spoofing at VLAN level.
c.
Run the commit command to make the profile configuration take

effect.
d.
e.
Run the vlan bind service-profile command to bind the created VLAN
service profile to a VLAN.
3.
(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.
4.
(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 ONUs.

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.
1.
In global config mode, run the security anti-ipspoofing enable command to

enable IP address anti-spoofing at the global level.
2.
In VLAN service profile mode, run the security anti-ipspoofing enable

command to enable IP address anti-spoofing at the VLAN level.
3.
Run the security anti-ipspoofing service-port serviceport-id enable command

to enable IP address anti-spoofing at the service port level.
Configure service security.
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.
1.
Enable DHCP Option 82 on both the OLT and ONUs.

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.
Issue 02 (2013-10-08)

595

Configuration Guide

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.
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:
a.
In global config mode, run the vlan service-profile command to create

a VLAN service profile.
b.
Run the dhcp option82 enable command to enable DHCP Option 82 at

the VLAN level.
c.
Run the commit command to make the profile configuration take effect.
d.
e.
The service port level: In global config mode, run the dhcp option82 serviceport command to enable DHCP Option 82 at the service port level.
2.
On the OLT, run the dhcp-option82 permit-forwarding service-port command

with the enable parameter selected, to allow ONU DHCP packets to carry Option
82 information.
Enable Policy Information Transfer Protocol (PITP) on both the OLT and ONUs. This
configuration is recommended for the PPPoE-based Internet access service.
1.
Enable PITP on both the OLT and ONUs.

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:
Issue 02 (2013-10-08)
a.

b.
Run the pitp enable command to enable PITP at the VLAN level.
c.
d.

596

Configuration Guide
e.

The service port level: In global config mode, run the pitp service-port
command to enable PITP at the service port level.
2.
On the OLT, run the pitp permit-forwarding service-port command with the
enable parameter selected, to allow ONU PPPoE packets to carry a vendor tag.
----End
12.1.7 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.
Context
In this example, the ONU is in version V800R310C00. For ONU in other versions,
configurations are slightly different. For details, see the corresponding Configuration Guide.
Data plan
Item
Data
Remarks
Port
Upstream port: 0/0/1
Service port: 0/3/1

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.
For details about the data plan, see 11.5
Principle of Internet Access Service
Data Plan.
Traffic profile
Profile ID: 8
For details about the data plan, see 11.3

Principle of QoS Data Plan.
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 mduadmin.
Step 2 Create SVLANs.
Create smart SVLANs 1001-1016 in batches with attribute common.
Issue 02 (2013-10-08)

597

Configuration Guide

Step 3 Add the upstream port to SVLANs.

Add upstream port 0/0/1 to SVLANs.
Step 4 Configure a traffic profile.

Run the display traffic table ip command to query the existing traffic profiles in the system. If
the existing traffic profile in the system does not meet the requirement, run the traffic table ip
command to add a traffic profile.
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.
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

huawei(config)#save
----End
12.1.8 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 MG interface first and
run the protocol support command to switch the protocol. After the configuration is
Precautions
Issue 02 (2013-10-08)

598

Configuration Guide

complete, save the configuration and restart the system to make the configured protocol
take effect.
WARNING
This operation interrupts the ongoing services carried on the currently used MG interface. Hence,
exercise caution when performing this operation.
Data plan
For details about the data plan, see 11.6 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.
Voice user
data
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
17.10.10.10/24
Default gateway IP address
17.10.10.1/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

Cat3 for phone 2 to phone 24
(default)
Common
parameter
Issue 02 (2013-10-08)
User type
Common user (DEL user by default)
System parameter
Default value

599

Configuration Guide

Item
Data
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal
Ringing current attribute
Default value
Procedure
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.

Add upstream port 0/0/1 to VLAN 2000.
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
17.10.10.10

Configure both the media IP address and signaling IP address to 17.10.10.10 and the MG IP
address to 17.10.10.1.
huawei(config)#voip
NOTE
l 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.
l 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 17.10.10.1 to 200.200.200.0.
Issue 02 (2013-10-08)

600

Configuration Guide


Add an MG interface to communicate with the MGC, which ensures that the MGC can 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.
l 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 17.10.10.10 mgport
2944 code text transfer udp primary-mgc-ip1 200.200.200.200 primary-mgc-port
2944 mg-media-ip1 17.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 mgc-domainname1), mgcport_1, code, transfer, and mg-media-ip are correctly configured.

Configure phone numbers of users 0/3/0-0/3/23 to 83110001-83110024 in batches and terminal
identification to 0.
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.
l 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
Issue 02 (2013-10-08)

601

Configuration Guide


huawei(config)#save
----End
12.1.9 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
WARNING
Data Plan
For configuration rules and description of configuration items, see 11.6 Principle of VoIP
Service Data Plan.
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Issue 02 (2013-10-08)
Data
Media
and
signalin
g
paramet
ers
Media and
signaling upstream
VLAN
200
Media and
signaling upstream
port
0/0/1

602


Configuration Guide
Item
Voice user
data
Data
Media IP address
and signaling IP
address
17.10.10.10/24
Default gateway
IP address
17.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
Coding scheme
Text
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110024
User priority
Phone 1 indicates Cat2.

Phone 2 to phone 24 indicate Cat3 (default
value).
Common
Parameter
User type
Common user (the DEL user by default)
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-Reversing Pulse
Default value
Procedure
Issue 02 (2013-10-08)

603

Configuration Guide
1.


2.

3.

17.10.10.10

Set the media IP address and signaling IP address to 17.10.10.10, and the media gateway to
17.10.10.1.
huawei(config)#voip
NOTE
l Attributes of the MG interface can be configured only when the media IP address and the signaling IP
address exist in the media and signaling IP address pools.
l 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 17.10.10.1 to the
network segment 200.200.200.0.
Step 5 Add an SIP interface.

The SIP interface is used for IMS communication.
Step 6 Configure the basic attributes of the SIP interface.

huawei(config-if-sip-0)#if-sip attribute basic media-ip 17.10.10.10 signal-ip
17.10.10.10 signal-port 5060 transfer udp primary-proxy-ip1 200.200.200.200
primary-proxy-port 5060 home-domain huawei sipprofile-index 1
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.

Issue 02 (2013-10-08)

604

Configuration Guide

Configure in batches the phone numbers of users 0/3/0-0/3/23 to 83110001-83110024.

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
12.1.10 Verifying Services

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 02 (2013-10-08)

605

Configuration Guide

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.
The user name, password, and
authentication mode must be
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.
Data Plan
Issue 02 (2013-10-08)
Item
Data
Remarks
PPPoE
dialup
emulation
parameter

authentication mode required by the
emulation test must be consistent with
those configured on the BRAS.
Call
emulation
parameter
Caller port: 0/3/0
Emulation timer: 10s
Called port: 0/3/23

Called number: 83110024
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.

606

Configuration Guide

Procedure
l
Verify the Internet access service using PPPoE dialup emulation.

1.
Start an emulation test by running the simulate dhcp start command.

huawei(config)#pppoe simulate start
Command:
pppoe simulate start
Service-port(index<0-999>):101
User Password(length<0,16>):*******
Authentication Mode:
1. Chap 2. Pap [default 1]:1
Overtime Time(5-60s)[default 5]:10
2.
Query the emulation test information by running the display pppoe simulate info
command.
huawei(config)#display pppoe simulate info
PPPoE simulate information is:
----------------------------------------------------------------Service-port: 101
User name:
user0
Current phase: //*Emulation phase
Result:
Success
//*Emulation result
Start time:
2011-11-16 15:41:29+08:00
End time:
2011-11-16 15:41:34+08:00
Session ID:
591
User IP:
192.168.50.2
Gateway IP:
192.168.50.254
-----------------------------------------------------------------
3.
Terminate the emulation test by running the simulate dhcp start command.
huawei(config)#pppoe simulate stop
Verify the voice service using call emulation.

1.
Start an emulation test by running the ont emulational call command.

huawei(config)#test
huawei(config-test)#pots emulational-call caller-port 0/3/0 callee-port
0/3/23 callee-telno 83110024
2.
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.
huawei(config-test)#
Caller port
Callee port
Test result
:
:
:
0/3/0
0/3/23
Test Succeed
----End
12.2 FTTB/C Networking (xDSL Access, Without HGW)

In the Fiber-to-the-building/curb (FTTB/C) network, 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.
12.2.1 Service Requirements and Application Scenario

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
Issue 02 (2013-10-08)

607


Configuration Guide
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.
The FTTB/C application scenario only supports Internet access and voice services without
multicast demands.
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 12-3, 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, MA5622A, MA5603T.
Figure 12-3 FTTB/C networking diagram (xDSL)
Phone
PC
xD
SL
+P
OT
S
PE-AGG
Modem Splitter
OLT
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 12-4 shows the configuration roadmap diagram in the FTTB and FTTC networking
scenarios using xDSL access without HGWs.
Issue 02 (2013-10-08)

608

Configuration Guide

Figure 12-4 Configuration Roadmap Diagram in the FTTB and FTTC Networking Scenarios
Using xDSL Access Without HGWs
Configurations on the ONU (logged

in from the OLT):
Configuring the management channel
access service.
Configure the VoIP

service.
Configuring the service channel
Configuring link
aggregation,
6 congestion control,
and security
policies.
6 Configuring link aggregation, congestion

control, and security policies.
Metro
Network
PC
VLAN
Phone
ONU
OLT
Upstream port
Downstream port
Management channel
Voice service flow
Note:
VLAN in the figure contains management VLAN and different
service VLAN, and the specific service port should be added to the
corresponding VLAN.
The following table lists the configuration procedure.

Item
Procedure
Remarks
OLT
Add an ONU on the OLT.

OLT.

ONU.

ONU.
Configure the
service channel
between the
OLT and the
ONU.
l Configure
the Internet
access
service
channel.
l Configure
the VoIP
service
channel.
Issue 02 (2013-10-08)
The ONU provides only the Internet access

service and the VoIP service in the FTTB
and FTTC network using xDSL access
without HGWs. Therefore, you need to
create an Internet access service channel and
a VoIP service channel on the OLT.

609


Configuration Guide
Item
Procedure
ONU
Configure the
Internet access
service.
Remarks
Configure the
ADSL2+
Internet access
service on the
ONU.
NOTE
Different ONUs have different ports, including
ADSL2+, VDSL2, and VDSL2 vectoring ports,
for the Internet access. Select an appropriate
configuration method according to the port type.
Configure the
ADSL2
Internet access
service on the
ONU.
(Optional)
Configure
vectoring on
the ONU
Configure the
VoIP service.
Configure the
H.248 -based
VoIP service on
the ONU.
NOTE
Configure the
SIP-based
VoIP service on
the ONU.
OLT
ONU

policy.

ONU
Verify the service.

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.
12.2.3 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.
Issue 02 (2013-10-08)

610

Configuration Guide

Context
Service flows can be added in two modes, as described in Table 12-4. Select either mode as
required.
Table 12-4 Adding service flows
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.
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

11.5 Principle of Internet Access
Service Data Plan.
OLT VLAN ID (VLAN

transparently transmitting the
ONU service): 200

11.6 Principle of VoIP Service
Data Plan.
ONU VLAN ID: 200

Procedure
l
Configure the channel for the Internet access service.

1.
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.
Issue 02 (2013-10-08)

611

Configuration Guide


2.

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.
3.
Configure service flows to receive and transparently transmits the Internet access
service from the ONU.
For the OLT: The SVLAN ID is 100, inner VLAN ID is 258. The user-side VLAN
ID of the OLT is the same as the upstream VLAN ID of the ONU, that is, 1001.
The Internet access service uses GEM port 12.
user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6 txcttr 6
Configure the channel for the VoIP service.

1.
Configure the SVLAN ID to 200 and VLAN type to smart VLAN. Add upstream port
0/19/0 to VLAN 200.
2.

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
local-setting
3.
Configure service flows to receive and transparently transmits the VoIP service from
the ONU.
For the OLT: The SVLAN ID is 200. The user-side VLAN ID of the OLT is the
same as the upstream VLAN ID of the ONU, that is, 200. The VoIP service uses
GEM port 13.
Issue 02 (2013-10-08)

612

Configuration Guide


----End

Security Policies
Context
is recommended.
NOTE
Plan.
Procedure
l


Issue 02 (2013-10-08)
(ONUs).
1.
2.

3.

613

Configuration Guide




1.

2.

a.

b.

a.

profile.
b.

c.

effect.
d.
e.
3.

4.


level by default.

2.

3.

Issue 02 (2013-10-08)
1.
service.
614

Configuration Guide
1.


level by default.
The VLAN level:
a.

b.

the VLAN level.
c.
d.
e.
2.

82 information.
1.

global level.
pitp command.
The VLAN level:
Issue 02 (2013-10-08)

615

Configuration Guide

a.

b.
c.
d.
e.
2.
----End
12.2.5 Configuring the Internet Access Service (ADSL2+ 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 ADSL2
+ mode.
Context
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 12-5.
Issue 02 (2013-10-08)

616

Configuration Guide

Table 12-5 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.

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
VPI/VCI of
ADSL2+
users
Issue 02 (2013-10-08)
VPI: 0
VCI: 35
Internet service providers (ISPs) provide VPI/

VCI information.

617

Configuration Guide

Item
Data
Remarks
ADSL2+
line profile
ID: 1024 (default); key

parameters:
A traffic profile or an ADSL2+ line profile can

implement rate-limiting on ADSL2+ ports.
This example uses a default traffic profile.
l Working mode: full

compatibility
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: mduadmin (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 in
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.
huawei(config)#vlan 1001-1016 smart huawei(config)#port vlan 1001-1016 0/0 1

As packets from HGWs contain VPI/VCI information, the PVC needs to be mapped to the user
VLAN when a service flow is configured.
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
Step 5 (Optional) Configure an ADSL2+ line profile.

Issue 02 (2013-10-08)

618

Configuration Guide

l Configure an ADSL2+ line profile only when the default one does not meet requirements.
l 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.
huawei(config)#interface adsl 0/2 huawei(config-if-adsl-0/2)#deactivate 0 huawei
(config-if-adsl-0/2)#alarm-config 0 1 huawei(config-if-adsl-0/2)#activate 0
profile-index 1024
----End
12.2.6 Configuring the Internet Access Service (VDSL2 Access, on

the ONU)
on an optical network unit (ONU) when HGWs are connected upstream to the ONU in VDSL2
mode.
Context
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 12-6.
Table 12-6 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.
l To query: display vdsl linetemplate
l To add: vdsl line-template add or
vdsl line-template quickadd
A VDSL2 line profile provides the

l To query: display vdsl line-profile
following parameters: line
l To add: vdsl line-profile add or
transmission mode, adaptation mode of
vdsl line-profile quickadd
upstream/downstream transmit rates,
signal-to-noise ratio (SNR) margin,
upstream power back-off (UPBO), and
downstream power back-off (DPBO).
Issue 02 (2013-10-08)

619

Configuration Guide
Templ
ate
Type
VDSL2
alarm
template

Function
Configuration
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.
The system has one default VDSL2

alarm template (template 1).
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 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
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 channel-alarmprofile quickadd
Data Plan
Table 12-7 provides key information about the Internet access service (VDSL2 access).
Issue 02 (2013-10-08)

620

Configuration Guide

Table 12-7 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.
VDSL2 line
template
Line profile ID: 1 (default)

Channel profile ID: 1 (default)
Line template ID: 1 (default)
VDSL2 alarm
template
Line alarm profile ID: 1 (default)

Channel alarm profile ID: 1
(default)
A traffic profile or a VDSL2 line

template can implement rate-limiting
on VDSL2 ports. This example uses a
default traffic profile.
The system does not check whether
parameter thresholds are crossed and so
does not report alarms.
Alarm template ID: 1 (default)
Procedure
Issue 02 (2013-10-08)

621

Configuration Guide



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.

This example uses the default VDSL2 line template (ID: 1).
Step 6 Configure a VDSL2 alarm template.
This example uses the default VDSL2 alarm template (ID: 1).
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.
huawei(config)#interface vdsl 0/1 huawei(config-if-vdsl-0/1)#deactivate 0 huawei
(config-if-vdsl-0/1)#alarm-config 0 1 huawei(config-if-vdsl-0/1)#activate 0
template-index 1
----End
12.2.7 (Optional) Configuring Vectoring

Vectoring configurations on VDSL2 lines cancel the far-end crosstalk (FEXT) of VDSL2 lines
to improve the line rate.
Prerequisite
ForMA5616, MA5603T, the boards supporting vectoring are configured.
Context
For MA5622A/MA5623A/MA5616, when configuring vectoring, learn configuration item
functions and configuration methods beforehand by referring to Table 12-8.
Issue 02 (2013-10-08)

622

Configuration Guide

Table 12-8 Vectoring configuration items

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 Before enabling
vectoring, globally
configure the band
plan.
Global
vectoring
configurations
Issue 02 (2013-10-08)
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.
xdsl vectoring
NOTE
Services in a
vectoring group port
are interrupted
when the vectoring
function is enabled
or disabled.

623

Configuration Guide

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.
By default, the policy

for activating a legacy
CPE is set to limit.
xdsl vectoring legacycpe activate-policy
l auto: 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: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

624

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode is
used in Vectoring
mature phase when
its performance is
concerned and
unnecessary
crosstalk must be
prevented.
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.
By default, all ports are

bound to vectoring
profile 1.
Query a vectoring
profile: display xdsl
vectoring-profile
Default value:
l Upstream crosstalk
cancelation: enable
l Downstream
crosstalk
cancelation: enable
For MA5603T, when configuring vectoring, learn configuration item functions and
configuration methods beforehand by referring to Table 12-9.
Issue 02 (2013-10-08)

625

Configuration Guide


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
port are interrupted
when the vectoring
function is enabled
or disabled.
Issue 02 (2013-10-08)

626

Configuration Guide

Item
Function
Description
Commands

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.

l auto: 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: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

627

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
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.
By default, all ports

are bound to vectoring
profile 1.
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: xdsl
vectoring-profile
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)
Data Plan
The Table 12-10 lists key parameters of vectoring configurations.
Table 12-10 Key parameters of vectoring configurations
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l Band plan type: 998ade
l USO type: type-a

Issue 02 (2013-10-08)

628

Configuration Guide

Item
Data
Description

vectoring legacy
customer premises
equipment (CPE)
auto
The policy for activating a

vectoring legacy CPE is
configured as auto at the initial
stage of vectoring application.
Vectoring group
Group ID: 1
The system does not support the

grouping. All ports are added to
the default vectoring group 1.
Vectoring profile
For the MA5622A/MA5623A/

MA5616:
Profile ID: 1 The upstream/

cancelation function in default
Profile 1 are as follows:
cancelation: enable
l Downstream crosstalk
cancelation: disable
For MA5603T:
l Profile name: huawei
cancelation: enable
l The port to which a vectoring
profile is bound: all ports on
the0/1 board.
NOTE
The Vectoring is configured on the ONU, and the configuration between the MA5622A/MA5623A/
MA5616 and MA5603T is a little different, Here gives the configuring steps of MA5622A/MA5623A/
MA5616 and MA5603T respectively.
Procedure
l
Configuration procedure for the MA5622A/MA5623A/MA5616:

1.
Log in to the ONU remotely and start the configuration.

By default, the user name is root and the password is mduadmin.
2.
Globally configure the band plan type.

3.
Configure the policy for activating a vectoring legacy CPE.

huawei(config)#xdsl vectoring legacy-cpe activate-policy auto
4.
Issue 02 (2013-10-08)
Enable global vectoring.

629

Configuration Guide

5.
Save the data.

huawei(config)#save
Configuration procedure for the MA5603T:

1.

By default, the user name is root and the password is admin.
2.

3.
Configure the vectoring profile as huawei and bind it to the VDSL2 port in the
vectoring group.
huawei(config)#xdsl vectoring-profile add control disable enable name
huawei
huawei(config-if-vdsl-0/1)#vectoring-config all profile-name huawei
4.

5.
Enable the global vectoring.

6.
Save the data.

huawei(config)#save
----End

Prerequisites
l
board 0 command.
1.
2.
take effect.
Precautions
Issue 02 (2013-10-08)

630

Configuration Guide

WARNING
Data plan
Item
MG
interface
data
NOTE
The data
configurati
on must be
the same as
the data
configurati
on on the
MGC.
Voice user
data
Data
Media
and
signalin
g
paramet
ers
Media and signaling

upstream VLANs
200
Media and signaling

upstream port
0/0/1

17.10.10.10/24
17.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-83110024

User priority
Cat2 for phone 1

(default)
Common
parameter
Issue 02 (2013-10-08)
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal

631

Configuration Guide

Item
Data
Default value
Procedure
1.

2.

3.

17.10.10.10

huawei(config)#voip
NOTE
networking.

from gateway 17.10.10.1 to 200.200.200.0.

Issue 02 (2013-10-08)

632

Configuration Guide


the data plan:

NOTE

83110001


enable

Issue 02 (2013-10-08)

633

Configuration Guide

huawei(config)#save
----End

Prerequisites
l
board 0 command.)
1.
2.
take effect.
Precautions
WARNING
Data Plan
Service Data Plan.
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Issue 02 (2013-10-08)
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
17.10.10.10/24

634


Configuration Guide
Item
Data
Default gateway
IP address
Voice user
data
17.10.10.1/24
SIP interface ID
Signaling port ID
5060

equipment
200.200.200.200/24

equipment
5060
Coding scheme
Text
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110024
User priority

value).
Common
Parameter
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Default value
Procedure
1.

Issue 02 (2013-10-08)

635

Configuration Guide
2.


3.

17.10.10.10

17.10.10.1.
huawei(config)#voip
NOTE





Issue 02 (2013-10-08)

636

Configuration Guide

NOTE


enable

huawei(config)#save
----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 02 (2013-10-08)

637

Configuration Guide

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.

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.
Data Plan
Issue 02 (2013-10-08)
Item
Data
Remarks
PPPoE
dialup
emulation
parameter

authentication mode required by the
emulation test must be consistent with
those configured on the BRAS.
Call
emulation
parameter
Caller port: 0/3/0
Emulation timer: 10s
Called port: 0/3/23

Called number: 83110024
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.

638

Configuration Guide

Procedure
l

1.

Command:
2.
command.
----------------------------------------------------------------Service-port: 101
User name:
user0
Result:
Success
//*Emulation result
Start time:
2011-11-16 15:41:29+08:00
End time:
2011-11-16 15:41:34+08:00
Session ID:
591
User IP:
192.168.50.2
Gateway IP:
192.168.50.254
-----------------------------------------------------------------
3.

1.

huawei(config)#test
0/3/23 callee-telno 83110024
2.
test fails.
Caller port
Callee port
Test result
:
:
:
0/3/0
0/3/23
Test Succeed
----End
12.3 FTTB/FTTC+HGW 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.
Issue 02 (2013-10-08)

639

Configuration Guide


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 12-5, 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 MA5612, MA5616, MA5622A,
MA5603T.
l
LAN ports are available on MA5612, MA5616.
xDSL ports are available on MA5616, MA5622A, MA5603T.
Issue 02 (2013-10-08)

640

Configuration Guide

Figure 12-5 GPON FTTB+HGW networking Diagram (voice, Internet access and IPTV
services)
Laptop
PC
HGW
PE-AGG
LAN
STB
OLT
TV
UPE
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
Phone

Figure 12-6 shows the configuration roadmap diagram in the FTTB+HGW networking
scenarios (ONU providing the VoIP service).
Issue 02 (2013-10-08)

641

Configuration Guide

Figure 12-6 Configuration Roadmap Diagram in the FTTB+HGW Networking Scenarios (ONU
Providing the VoIP Service)
Configurations on the ONU (logged in from the OLT):
4 Configure the Internet access service.

5 Configure the VoIP service.
6 Configure the IPTV service (VoD and Multicast).
Configuring link aggregation, congestion
7 control, and security policies.

Configurations on the HGW:
Configuring the management
access service.
2 channel between the OLT
9 Configure the IPTV
and the ONU.
service.
Configuring the service

and the ONU.
Configuring link aggregation,
7 congestion control, and
security policies.
Metro
Network
PC
TV
STB
HGW
ONU
IPTV
Headend
VLAN
OLT
NGN/IMS
Phone
Upstream port
Downstream port
Voice service flow
Management channel
VoD service flow
VoD service channel
Multicast service flow
Multicast service channel
Note:
VLAN in the figure contains management VLAN and
different service VLAN, and the specific service port should
be added to the corresponding VLAN.
The following table lists the configuration procedure..
Issue 02 (2013-10-08)
Item
Procedure
Remarks
OLT

OLT.

ONU.

ONU.

642

Configuration Guide
Item

Procedure
Configure the
management
channel
between the
OLT and the
ONU.
Remarks
l Configure
the Internet
access
service
channel.
l Configure
the VoIP
service
channel.
In the FTTB+HGW networking (ONU

provides the voice service), the ONU
provides the Internet and voice services and
the HGW provides the IPTV service.
Therefore, you need to create specific
service channels for various services on the
OLT.
l Configure
the VoD
service
channel
l Configure
the multicast
service
channel.
ONU
Configure the
Internet access
service.
Configure the
LAN Internet
access service
on the ONU.
Configure the
ADLS2+
Internet access
service on the
ONU.
NOTE
LAN, ADSL2+, VDSL2, and VDSL2 vectoring
ports, for the Internet access. Select an
appropriate configuration method according to
the port type.
Configure the
VDSL2
Internet access
service on the
ONU.
(Optional)
Configure
vectoring on
the ONU
Configure the
VoIP service.
Configure the
H.248 -based
VoIP service on
the ONU.
NOTE
Configure the
SIP-based
VoIP service on
the ONU.
Issue 02 (2013-10-08)

643


Configuration Guide
Item
Procedure
Configure the
IPTV service.
Remarks
l Configure
the VoD
service.
l Configure
the multicast
service.
OLT
ONU
HGW
IPTV services include the VoD and

multicast services that are different in
configuration procedures and need to be
configured separately.

policy.


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.
ONU
Configure the IPTV service on the

HGW.
Verify the services.

methods including PPPoE dialup emulation,
call emulation and multicast emulation for
the commissioning and configuration
engineers to verify services remotely after
service configuration, avoiding a second onsite operation.
12.3.3 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.
12.1.3 Adding an ONU to an OLT is performed.
2.
12.1.4 Configuring the Management Channel Between the OLT and the ONU is
performed.
Issue 02 (2013-10-08)

644

Configuration Guide

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: 1000-1016
For details, see 11.5 Principle of Internet Access

Service Data Plan.
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 11.6 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 11.7 Principle of IPTV Service
Data Plan.
Multicast
service
Multicast VLAN ID:

1000
The multicast service is a carrier-operating, closed

service and primarily adopts only S-VLAN tags.
Multicast cascading port:

0/2/1

Data Plan.
IGMP version: IGMPv3

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.
Issue 02 (2013-10-08)

645

Configuration Guide

Procedure
l
Configure a channel for the Internet access service.

1.
Create an S-VLAN and add an upstream port to it.

Create S-VLAN 100 with the stacking attribute and add upstream port 0/19/0 to the
S-VLAN.
huawei(config)#vlan 100 smart huawei(config)#vlan attrib 100 stacking
2.

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.
3.
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 12 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 12 multiservice user-vlan 1001 tag-transform default rx-cttr 6 tx-cttr 6
Configure a channel for the VoIP service.

1.

Create S-VLAN 200 with the common attribute and add upstream port 0/19/0 to the
S-VLAN.
huawei(config)#vlan 200 smart huawei(config)#port vlan 200 0/19 0
2.

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.
local-setting
3.
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 13 multiservice user-vlan 200 rx-cttr 9 tx-cttr 9
Issue 02 (2013-10-08)

646

Configuration Guide

Configure a channel for the VoD service.

1.

S-VLAN.
2.

The 802.1p priority of the VoD service is 4, and rate limitation is not required. To
huawei(config)#traffic table ip index 10 cir off priority 4 prioritypolicy local-Setting
3.
Configure a service flow for the VoD service.

referenced.
Configure a channel for the multicast service.

1.

S-VLAN.
2.
Configure a service flow for the multicast service.

being 1000. ONT 1 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 10 is referenced.
3.
Configure a multicast cascading port.

Set GPON port 0/2/1 as a multicast cascading port, ONT ID to 1, and GEM port 14
to carry the multicast service.
huawei(config)#btv huawei(config-btv)#igmp cascade-port 0/2/1 ontid 1
gemport-index 14
4.
Set the IGMP version.

Set the IGMP version to IGMPv3.
huawei(config)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp version
v3
5.
Issue 02 (2013-10-08)
Set the IGMP mode.

647

Configuration Guide

Select the IGMP proxy mode.

huawei(config-mvlan1000)#igmp mode proxy Are you sure to change IGMP mode?
(y/n)[n]:y
6.
Configure an IGMP upstream port.

Set the IGMP upstream port to port 0/19/0.
7.
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.
huawei(config-mvlan1000)#igmp program add batch ip 224.1.1.10 to-ip
224.1.1.100 sourceip 10.10.10.10
----End

Security Policies
Context
is recommended.
NOTE
Plan.
Procedure
l


Issue 02 (2013-10-08)

648

Configuration Guide

(ONUs).
1.
2.

3.




1.

2.

a.

b.

a.

profile.
b.

c.

effect.
d.
e.
3.

4.


level by default.
Issue 02 (2013-10-08)

649

Configuration Guide

1.

2.

3.

service.
1.

level by default.
The VLAN level:
a.

b.

the VLAN level.
c.
d.
e.
2.

82 information.
1.

Issue 02 (2013-10-08)

650

Configuration Guide

global level.
pitp command.
The VLAN level:
a.

b.
c.
d.
e.
2.
----End
12.3.5 Configuring the Internet Access Service (LAN Access, on the

ONU)
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
Issue 02 (2013-10-08)
Untagged
User VLAN ID: 1, 2, 3...
HGWs can send untagged packets or packets

with user VLAN tags.

651

Configuration Guide

Procedure


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./ huawei(config)#serviceport 101 vlan 1001 eth 0/3/1 multi-service user-vlan untagged rx-cttr 8 tx-cttr
8
l 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./ huawei(config)#service-port 101
vlan 1001 eth 0/3/1 multi-service user-vlan 10 rx-cttr 8 tx-cttr 8
----End

the ONU)
+ mode.
Context
Table 12-11.
Issue 02 (2013-10-08)

652

Configuration Guide


Profile
Type
Function
Configuration
ADSL2+
line
profile



l Channel mode

common ADSL ports.
depth

l Noise margin


ADSL2+
alarm
profile


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 02 (2013-10-08)
VPI: 0
VCI: 35

VCI information.

653

Configuration Guide

Item
Data
Remarks
ADSL2+
line profile

parameters:


compatibility
interleaved
l Maximum upstream/
24544/1024
ADSL2+
alarm
profile
ID: 1 (default)

alarms.
Procedure


follows:

Issue 02 (2013-10-08)

654

Configuration Guide

+ port 0/2/0.
profile-index 1024
----End

the ONU)
mode.
Context
Table 12-12.
Templ
ate
Type
Function
Configuration
VDSL2
line
template



Issue 02 (2013-10-08)

655

Configuration Guide
Templ
ate
Type
VDSL2
alarm
template

Function
Configuration

retransmission.

the NMS.


CPEs:

(FECS)

quickadd



COs and CPEs:

Data Plan
Issue 02 (2013-10-08)

656

Configuration Guide

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.
VDSL2 line
template

VDSL2 alarm
template

(default)

Procedure
Issue 02 (2013-10-08)

657

Configuration Guide




port 0/1/0.
template-index 1
----End

Prerequisite
Context
Issue 02 (2013-10-08)

658

Configuration Guide


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
Vectoring
configurations take
effect only when
enabled.
l Before enabling
vectoring, globally
configure the band
plan.
Global
vectoring
configurations
Issue 02 (2013-10-08)
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
NOTE
Services in a
are interrupted
when the vectoring
function is enabled
or disabled.

659

Configuration Guide

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
based on site
requirements.

l auto: 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.
l force: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

660

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode is
used in Vectoring
mature phase when
its performance is
concerned and
unnecessary
crosstalk must be
prevented.
Vectoring
profile

of canceling the
upstream and
in the vectoring
the configured
ports, the system
implements the
the ports in the
on profile
configurations.

bound to vectoring
profile 1.
Query a vectoring
vectoring-profile
Default value:
cancelation: enable
l Downstream
crosstalk
cancelation: enable
Issue 02 (2013-10-08)

661

Configuration Guide


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 02 (2013-10-08)

662

Configuration Guide

Item
Function
Description
Commands

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.

l auto: The
Vectoring legacy
CPE is activated in
common VDSL2
mode (G.993.2
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: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

663

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
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.

profile 1.
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable
Commands:
l Add a vectoring
profile: xdsl
vectoring-profile
add
profile: xdsl
vectoring-profile
modify
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
l Bind a vectoring
vectoring-config
(VDSL mode)
Data Plan
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l USO type: type-a

Issue 02 (2013-10-08)

664

Configuration Guide

Item
Data
Description

vectoring legacy
customer premises
equipment (CPE)
auto

Vectoring group
Group ID: 1

Vectoring profile

MA5616:

cancelation: enable
For MA5603T:
cancelation: enable
the0/1 board.
NOTE
Procedure
l

1.

2.

3.

4.
Issue 02 (2013-10-08)

665

Configuration Guide

5.
Save the data.

huawei(config)#save

1.

2.

3.
vectoring group.
huawei
4.

5.

6.
Save the data.

huawei(config)#save
----End

Prerequisites
l
board 0 command.
1.
2.
take effect.
Precautions
Issue 02 (2013-10-08)

666

Configuration Guide

WARNING
Data plan
Item
MG
interface
data
NOTE
The data
configurati
on must be
the same as
the data
configurati
on on the
MGC.
Voice user
data
Data
Media
and
signalin
g
paramet
ers
Media and signaling

upstream VLANs
200
Media and signaling

upstream port
0/0/1

17.10.10.10/24
17.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-83110024

User priority
Cat2 for phone 1

(default)
Common
parameter
Issue 02 (2013-10-08)
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Polarity-reversal

667

Configuration Guide

Item
Data
Default value
Procedure
1.

2.

3.

17.10.10.10

huawei(config)#voip
NOTE
networking.

from gateway 17.10.10.1 to 200.200.200.0.

Issue 02 (2013-10-08)

668

Configuration Guide


the data plan:

NOTE

83110001


enable

Issue 02 (2013-10-08)

669

Configuration Guide

huawei(config)#save
----End

Prerequisites
l
board 0 command.)
1.
2.
take effect.
Precautions
WARNING
Data Plan
Service Data Plan.
Item
SIP
interface
data
NOTE
(It must be
the same as
that on the
IMS core
network
device.)
Issue 02 (2013-10-08)
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
17.10.10.10/24

670


Configuration Guide
Item
Data
Default gateway
IP address
Voice user
data
17.10.10.1/24
SIP interface ID
Signaling port ID
5060

equipment
200.200.200.200/24

equipment
5060
Coding scheme
Text
Transmission mode
UDP
huawei
Profile index (SIP)
Phone number
83110001-83110024
User priority

value).
Common
Parameter
User type
System parameter
Default value
Overseas parameter
Default value
PSTN port attribute
Default value
Procedure
1.

Issue 02 (2013-10-08)

671

Configuration Guide
2.


3.

17.10.10.10

17.10.10.1.
huawei(config)#voip
NOTE





Issue 02 (2013-10-08)

672

Configuration Guide

NOTE


enable

huawei(config)#save
----End
12.3.11 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 02 (2013-10-08)


673

Configuration Guide

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

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

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 02 (2013-10-08)

674

Configuration Guide

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:
1 rx-cttr 10 tx-cttr 10
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 multi-service
user-vlan untagged rx-cttr 10 tx-cttr 10
Configure the multicast service.

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.

huawei(config)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp version v3
Set the IGMP mode to IGMP proxy.

huawei(config-mvlan1000)#igmp mode proxy Are you sure to change IGMP mode?(y/n)
[n]:y

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 huawei(config-mvlan1000)#quit

Issue 02 (2013-10-08)

675

Configuration Guide

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:
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.
huawei(config-mvlan1000)#btv huawei(config-btv)#igmp user add service-port 401
no-auth huawei(config-btv)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp
multicast-vlan member service-port 401 huawei(config-mvlan1000)#quit
----End
12.3.12 Configuring the Internet Access Service (on the HGW)

This topic describes how to configure the Internet access service for residential users on a home
gateway (HGW) when the HGW is connected to an ONU upstream through a local area network
(LAN) or in xDSL mode.
Context
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 ONU upstream through a LAN and on an HG527 that is connected to an ONU
upstream in ADSL2+ mode.
Procedure
l
Configure the Internet access service (on an HG239).

1.
2.
Log in to the Web configuration window.

a.
Enter http://192.168.1.1/cu.html (default IP address) to the address bar of the

Internet Explorer (IE) and press Enter.
b.
In the login dialog box, enter the user name and password of the administrator
(the Internet service provider (ISP) provides the default user name and default
password). Then, click OK.
Set parameters for the Internet access service.

Assume that ports LAN1 and LAN2 are Internet access ports for PCs.
a.
Issue 02 (2013-10-08)
Choose Network > Bandwidth Configuration from the navigation tree.

676

Configuration Guide
b.

Create WAN connection 1 and set parameters based on the following table.
Parameter
Value
Bearing
service
INTERNET
VLAN
enabling
Enabled: Upstream packets contain VLAN tags.

Disabled: Upstream packets do not contain VLAN tags.
NOTE
If uservlan is set to untagged when you configure a service flow for
the Internet access service on the ONU, set this parameter to
Disabled; otherwise, set it to Enabled.
c.
3.
VLANID
[1-4094]
If VLAN enabling is set to Enabled, this parameter takes

the value of uservlan that is specified when you configure a
service flow for the Internet access service on the ONU.
Binding item
LAN1 and LAN2: PCs connected to ports LAN1 and LAN2

can simultaneously access the Internet.
Mode
Bridge: PCs access the Internet in PPPoE dial-up mode.
Click OK.
Restart the HGW.

Choose Management > Device Management and click Restarting the Device.

1.
2.

a.
Enter http://192.168.1.1/cnc.html (default IP address) to the address bar of the

IE and press Enter.
b.
In the login dialog box, enter the user name (default: admin) and password
(default: admin) of the administrator. Then, click OK.

Issue 02 (2013-10-08)
a.
b.
Parameter
Value
Bearing
service
INTERNET
Enabling
If this parameter is selected, WAN connection 1 is used.
VPI/VCI
Contact your carrier for the value ranges of VPIs and VCIs.
Ensure that the VPI/VCI setting (for example, 0/35) on an
HGW is consistent with that on the office to which the HGW
is connected.

677

Configuration Guide
c.
3.

Parameter
Value
Binding item

Mode
Bridge: PCs access the Internet in PPPoE dialup mode.
Encapsulation
mode
LLC
Click OK.
Restart the HGW.

----End
12.3.13 Configuring the IPTV Service (on the HGW)

This topic describes how to configure the IPTV service on the HGW that uses LAN or xDSL
for upstream transmission. This configuration enables home subscribers to watch IPTV
programs using STBs and TVs.
Context
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 that uses
ADSL2+ for upstream transmission as examples.
Procedure
l
Configure the IPTV service on the HG239.

1.
2.

a.

b.
Configure multicast parameters.

This example assumes LAN 4 as an IPTV port.
Issue 02 (2013-10-08)
a.
b.
In the right pane, create LAN connection 2 for the IPTV service. Set the
parameters as follows:
Parameter
Value
Bearing
service
OTHER: The connection is used for the IPTV service.

678

Configuration Guide
c.
3.

Parameter
Value
VLAN
enabling
Enable VLAN tags are added to upstream packets.
VLANID
[1-4094]
Multicast VLAN ID corresponding to the user VLAN value

for multicast service flows created on the ONU. In this
example, set this parameter to 43.
Binding item
LAN4
Mode
Bridge
DHCP
transparent
transmission
Enable
NOTE
When multicast service flows are created on the ONU, the value is
Disable if uservlan is untagged and the value is Enable if
uservlan is tagged.
Click OK to save the settings.
Restart the HGW.


1.
2.

a.

IE and press Enter.
b.

Issue 02 (2013-10-08)
a.
b.
In the right pane, create LAN connection 1 for dialup Internet access services.
Set the parameters as follows:
Parameter
Value
Bearing
service
Enabling
The LAN connection is enabled when this check box is

selected.
VLAN
enabling
Enable: VLAN tags are added to upstream packets.

NOTE
uservlan is tagged.

679


Configuration Guide
c.
3.
Parameter
Value
VLANID
[1-4094]
Multicast VLAN ID on the HGW when multicast service

flows are created on the ONU. In this example, set this
parameter to 43.
VPI/VCI
Set the VPI/VCI to the same as that configured on the devices

at the central office. In this example, set this parameter to
0/35.
Binding item
LAN4
Mode
Bridge
Encapsulation
mode
LLC
Restart the HGW.

----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.
Issue 02 (2013-10-08)

680

Configuration Guide

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
the connectivity between the ONT and
BRAS.

service flow which does not belong to
a QinQ VLAN.
A user name, password, and
configured on the BRAS for the
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.
l An ONU can emulate the caller 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.
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.
Item
Data
Remarks
PPPoE
dialup
emulation
parameter
The entered user name, password, and

consistent with those configured on
the BRAS.
Data plan
Issue 02 (2013-10-08)
Emulation timeout time: 10s

681

Configuration Guide

Item
Data
Remarks
Call
emulation
parameter
Caller port: 0/3/0

Callee telephone number: 83110024
The ONU emulates the caller and

callee at the same time using the
default emulation parameters. You
can view the parameters by running
the display pots emulational
configuration command.
Multicast
emulation
parameter
Multicast service flow ID: 401
Callee port: 0/3/23
Multicast VLAN: 1000

IP address of the multicast program:
224.1.1.10
Procedure
l

1.

Command:
2.
command.
----------------------------------------------------------------Service-port: 101
User name:
user0
Result:
Success
//*Emulation result
Start time:
2011-11-16 15:41:29+08:00
End time:
2011-11-16 15:41:34+08:00
Session ID:
591
User IP:
192.168.50.2
Gateway IP:
192.168.50.254
-----------------------------------------------------------------
3.

1.

huawei(config)#test
0/3/23 callee-telno 83110024
2.
test fails.
Issue 02 (2013-10-08)

682

Configuration Guide
Caller port
Callee port
Test result

:
:
:
0/3/0
0/3/23
Test Succeed
Verify the multicast service using multicast emulation.

1.
Run the igmp static-join command to order a multicast program by emulating a

multicast user.
huawei(config)#btv
huawei(config-btv)#igmp static-join service-port 401 ip 224.1.1.10 vlan
1000
2.
Run the display igmp use command to query the status of the multicast user.
huawei(config-btv)#display igmp user service-port 401
User
: 0/3/1 //*Use an ETH port as an example.
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 0
Video flow ID
: 0
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Available programs
: 91
Global Leave
: disable
User MaxBandWidth
: no-limit
: 5000
The percentage of used
bandwidth to port rate(%) : Total video bandwidth
: Mcast video bandwidth
: Active program list
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start-time
-------------------------------------------------------------------------program1
1000 224.1.1.10
watching
2011-07-13
14:41:18
-------------------------------------------------------------------------Total: 1
3.
Run the display multicast flow-statistic command to query the real-time traffic of
the multicast program.
huawei(config-btv)#display multicast flow-statistic ip 224.1.1.10 vlan
1000
Command is being executed, please wait...
Multicast flow statistic result: 360(kbps)
Verify the VoD service.

1.
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.
If the VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0, run the following command to
query the learned MAC addresses of VoD users:
huawei(config)#display mac-address service-port 301
Command:
display mac-address service-port 301
Issue 02 (2013-10-08)

683

Configuration Guide

------------------------------------------------------------------------SRV-P BUNDLE TYPE MAC

MAC TYPE F /S /P VPI VCI
VLANID
INDEX INDEX
------------------------------------------------------------------------301
adl 1010-1010-1000 dynamic 0 /2 /0 0
35
300
------------------------------------------------------------------------Total: 1
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,
ppp--pppoe, ip--ipoe, ip6--ipv6oe
2.
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
12.4 FTTB/FTTC+HGW Networking (HGW Providing the

VoIP Service)
In an FTTB/FTTC+HGW network, 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.

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
Issue 02 (2013-10-08)
Easy fault location and service maintenance

684


Configuration Guide
Figure 12-7 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: MA5612, MA5616, MA5622A, MA5623, MA5623A,

MA5603T. Among these ONUs,
l
ONUs with LAN ports include MA5612, MA5616.
ONUs with ADSL2+ ports include MA5616, MA5603T.
ONUs with VDSL2 ports include MA5616, MA5622A, MA5623, MA5623A,

MA5603T.
Figure 12-7 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 12-8 shows the configuration roadmap diagram in the FTTB+HGW networking
scenarios (HGW providing the VoIP service).
Issue 02 (2013-10-08)

685

Configuration Guide

Figure 12-8 Configuration Roadmap Diagram in the FTTB+HGW Networking Scenarios

(HGW providing the VoIP service)
Configurations on the ONU (logged in from the OLT):
4 Configure the Internet access service.

5 Configure the VoIP service channel.
6 Configure the IPTV service (VoD and Multicast).
Configuring link aggregation, congestion
7 control, and security policies.
Configurations on the HGW:
Configure the Internet
8 access service.
Configuring the management
Configure the VoIP
9 service.
and the ONU.

Configuring the service
10 Configure the IPTV

service.

and the ONU.
Configuring link aggregation,
7 congestion control, and

security policies.
Metro
Network
PC
STB
TV
HGW
Phone
ONU
IPTV
Headend
VLAN
OLT
Upstream port
Downstream port
Voice service flow
Management channel
VoD service flow
VoD service channel
Multicast service flow
Multicast service channel
NGN/IMS
Note:
VLAN in the figure contains management VLAN and
different service VLAN, and the specific service port
should be added to the corresponding VLAN.
The following table describes the configuration procedure.
Issue 02 (2013-10-08)
Config
ured
Device
Procedure
Configuration
OLT

OLT.

ONU.

ONU.

686

Configuration Guide
Config
ured
Device

Procedure
Configure the
service channel
between the
OLT and the
ONU.
Configuration
l Configure
the Internet
access
service
channel.
l Configure
the VoIP
service
channel.
In the FTTB+HGW networking (HGW

provides the VoIP service), the ONU
provides Internet access service and
provides VoIP and IPTV services using the
HGW. Therefore, service channels need to
be configured on the OLT for different
services.
l Configure
the VoD
service
channel.
l Configure
the multicast
service
channel.
ONU
Configure the
Internet access
service.
Configure the
LAN Internet
access service
on the ONU
Configure the
ADSL2+
Internet access
service on the
ONU.
NOTE
LAN, ADSL2+, VDSL2, and VDSL2 vectoring
ports, for the Internet access. Select an
appropriate configuration method according to
the port type.
Configure the
VDSL2
Internet access
service on the
ONU.
(Optional)
Configure
vectoring on
the ONU
Configure the VoIP service
channel on the ONU.
Issue 02 (2013-10-08)
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.

687


Configuration Guide
Config
ured
Device
Procedure
Configure the
IPTV service.
Configuration
l Configure
the VoD
service.
l Configure
the multicast
service.
OLT
ONU
HGW
IPTV services include VoD and multicast

services that are different in configuration
procedures and need to be configured
separately.

policy.


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.
ONU
HGW
Configure the IPTV services on

the HGW.
Configure the VoIP service on the

HGW.
This topic describes how to configure the

voice service on HGWs that use LAN or
xDSL for upstream transmission. This
configuration enables home subscribers to
enjoy the POTS service by using an analog
telephone.
Verify the services.
ONUs provide remote service verification

methods including PPPoE dialup 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.
Voice services on the HGW do no support
remote service verification.
12.4.3 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
Issue 02 (2013-10-08)

688

Configuration Guide

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.
12.1.3 Adding an ONU to an OLT is performed.
2.
12.1.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: 1000-1016
For details, see 11.5 Principle of Internet Access

Service Data Plan.
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 11.6 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.
Data Plan.
Issue 02 (2013-10-08)

689

Configuration Guide

Service
Type
VLAN Plan
Remarks
Multicast
service
Multicast VLAN ID:

1000
The multicast service is a carrier-operating, closed

service and primarily adopts only S-VLAN tags.
Multicast cascading port:

0/2/1

Data Plan.
IGMP version: IGMPv3

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.

1.

Create S-VLAN 100 with the stacking attribute and add upstream port 0/19/0 to the
S-VLAN.
huawei(config)#vlan 100 smart huawei(config)#vlan attrib 100 stacking
2.

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.
3.
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 12 multiservice user-vlan 1001 tag-transform default rx-cttr 6 tx-cttr 6
Configure a channel for the VoIP service.

1.
Issue 02 (2013-10-08)

690

Configuration Guide

S-VLAN.
2.

The 802.1p priority of the VoIP service is 5, and rate limitation is not required. To
local-setting
3.
Configure a service flow for receiving and transparently transmitting the VoIP service
from the ONU side.
referenced.
Configure a channel for the VoD service.

1.

S-VLAN.
2.

The 802.1p priority of the VoD service is 4, and rate limitation is not required. To
huawei(config)#traffic table ip index 10 cir off priority 4 prioritypolicy local-Setting
3.

referenced.
Configure a channel for the multicast service.

1.
Issue 02 (2013-10-08)

691

Configuration Guide

S-VLAN.
2.

being 1000. ONT 1 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 10 is referenced.
3.
Configure a multicast cascading port.

Set GPON port 0/2/1 as a multicast cascading port, ONT ID to 1, and GEM port 14
to carry the multicast service.
huawei(config)#btv huawei(config-btv)#igmp cascade-port 0/2/1 ontid 1
gemport-index 14
4.
Set the IGMP version.

Set the IGMP version to IGMPv3.
huawei(config)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp version
v3
5.
Set the IGMP mode.

Select the IGMP proxy mode.
huawei(config-mvlan1000)#igmp mode proxy Are you sure to change IGMP mode?
(y/n)[n]:y
6.

Set the IGMP upstream port to port 0/19/0.
7.
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
----End

Security Policies
Context
Issue 02 (2013-10-08)

692

Configuration Guide

is recommended.
NOTE
Plan.
Procedure
l


(ONUs).
1.
2.

3.



Issue 02 (2013-10-08)

1.

2.

a.

b.


693

Configuration Guide

a.

profile.
b.

c.

effect.
d.
e.
3.

4.


level by default.
1.

2.

3.

service.
1.

level by default.
The VLAN level:
Issue 02 (2013-10-08)

694

Configuration Guide

a.

b.

the VLAN level.
c.
d.
e.
2.

82 information.
1.

global level.
pitp command.
The VLAN level:
a.

b.
c.
d.
e.
2.
----End
Issue 02 (2013-10-08)

695

Configuration Guide

12.4.5 Configuring the Internet Access Service (LAN Access, on the

ONU)
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

Procedure


Configurations for untagged packets and packets with user VLAN tags are different.
Issue 02 (2013-10-08)

696

Configuration Guide

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./ huawei(config)#serviceport 101 vlan 1001 eth 0/3/1 multi-service user-vlan untagged rx-cttr 8 tx-cttr
8
l 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./ huawei(config)#service-port 101
vlan 1001 eth 0/3/1 multi-service user-vlan 10 rx-cttr 8 tx-cttr 8
----End

the ONU)
+ mode.
Context
Table 12-17.
Profile
Type
Function
Configuration
ADSL2+
line
profile



l Channel mode

common ADSL ports.
depth

l Noise margin


Issue 02 (2013-10-08)

Commands:

697

Configuration Guide

Profile
Type
Function
Configuration
ADSL2+
alarm
profile

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

VCI information.

interleaved
l Maximum upstream/
24544/1024
ADSL2+
alarm
profile
ID: 1 (default)

alarms.
Procedure
Issue 02 (2013-10-08)

698

Configuration Guide




follows:

+ port 0/2/0.
profile-index 1024
----End

the ONU)
mode.
Issue 02 (2013-10-08)

699

Configuration Guide

Context
Table 12-18.
Templ
ate
Type
Function
Configuration
VDSL2
line
template



VDSL2
alarm
template
Issue 02 (2013-10-08)

retransmission.

the NMS.


quickadd


700

Configuration Guide
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
Issue 02 (2013-10-08)

701

Configuration Guide

Item
Data
Remarks
VDSL2 line
mode
PTM

mode and PTM mode.
mode.
mode.
VDSL2 line
template

VDSL2 alarm
template

(default)

Procedure


Issue 02 (2013-10-08)

702

Configuration Guide


port 0/1/0.
template-index 1
----End

Prerequisite
Context
Issue 02 (2013-10-08)

703

Configuration Guide


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
Vectoring
configurations take
effect only when
enabled.
l Before enabling
vectoring, globally
configure the band
plan.
Global
vectoring
configurations
Issue 02 (2013-10-08)
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
NOTE
Services in a
are interrupted
when the vectoring
function is enabled
or disabled.

704

Configuration Guide

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
based on site
requirements.

l auto: 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.
l force: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

705

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode is
used in Vectoring
mature phase when
its performance is
concerned and
unnecessary
crosstalk must be
prevented.
Vectoring
profile

of canceling the
upstream and
in the vectoring
the configured
ports, the system
implements the
the ports in the
on profile
configurations.

bound to vectoring
profile 1.
Query a vectoring
vectoring-profile
Default value:
cancelation: enable
l Downstream
crosstalk
cancelation: enable
Issue 02 (2013-10-08)

706

Configuration Guide


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 02 (2013-10-08)

707

Configuration Guide

Item
Function
Description
Commands

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.

l auto: The
Vectoring legacy
CPE is activated in
common VDSL2
mode (G.993.2
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: The
Vectoring legacy
CPE cannot be
activated in
Issue 02 (2013-10-08)

708

Configuration Guide
Item
Function

Description
Commands
common VDSL2
mode. This mode
is used in
Vectoring mature
phase when its
performance is
concerned and
unnecessary
crosstalk must be
prevented.
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.

profile 1.
Default value:
l Upstream
crosstalk
cancelation:
enable
l Downstream
crosstalk
cancelation:
enable
Commands:
l Add a vectoring
profile: xdsl
vectoring-profile
add
profile: xdsl
vectoring-profile
modify
profile: xdsl
vectoring-profile
delete
l Query a vectoring
profile: display
l Bind a vectoring
vectoring-config
(VDSL mode)
Data Plan
Item
Data
Description
Global vectoring
configurations
enable
Global band plan
l USO type: type-a

Issue 02 (2013-10-08)

709

Configuration Guide

Item
Data
Description

vectoring legacy
customer premises
equipment (CPE)
auto

Vectoring group
Group ID: 1

Vectoring profile

MA5616:

cancelation: enable
For MA5603T:
cancelation: enable
the0/1 board.
NOTE
Procedure
l

1.

2.

3.

4.
Issue 02 (2013-10-08)

710

Configuration Guide

5.
Save the data.

huawei(config)#save

1.

2.

3.
vectoring group.
huawei
4.

5.

6.
Save the data.

huawei(config)#save
----End
12.4.9 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.
Traffic
profile
ID: 9
Committed rate: off
VLAN priority
For the VoIP service, it is

recommended to rate limit traffic on
the BRAS or SR without using traffic
profiles.
Priority policy: Local-Setting

Issue 02 (2013-10-08)

711

Configuration Guide

Item
Data
Remarks
User port
The HGW uses LAN for upstream

transmission:
Different types of HGWs establish

service flows in different ways.
The HGW uses ADSL2+ for

upstream transmission:
The HGW uses VDSL2 for upstream
transmission:
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:
user-vlan
For the HGW that uses VDSL2 for upstream transmission, the VoIP service is configured
as follows:
user-vlan
----End
Issue 02 (2013-10-08)

712

Configuration Guide

12.4.10 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 02 (2013-10-08)
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 information.
VCI: 35

713

Configuration Guide

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
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.
local-setting

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.
Issue 02 (2013-10-08)

714

Configuration Guide

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:
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:
user-vlan untagged rx-cttr 10 tx-cttr 10
Configure the multicast service.

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.

huawei(config)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp version v3
Set the IGMP mode to IGMP proxy.

huawei(config-mvlan1000)#igmp mode proxy Are you sure to change IGMP mode?(y/n)
[n]:y

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 huawei(config-mvlan1000)#quit

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:
Issue 02 (2013-10-08)

715

Configuration Guide


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.
huawei(config-mvlan1000)#btv huawei(config-btv)#igmp user add service-port 401
no-auth huawei(config-btv)#multicast-vlan 1000 huawei(config-mvlan1000)#igmp
multicast-vlan member service-port 401 huawei(config-mvlan1000)#quit
----End
12.4.11 Configuring the Internet Access Service (on the HGW)

This topic describes how to configure the Internet access service for residential users on a home
gateway (HGW) when the HGW is connected to an ONU upstream through a local area network
(LAN) or in xDSL mode.
Context
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 ONU upstream through a LAN and on an HG527 that is connected to an ONU
upstream in ADSL2+ mode.
Procedure
l

1.
2.

a.

b.

Issue 02 (2013-10-08)
a.
b.
Parameter
Value
Bearing
service
INTERNET

716

Configuration Guide

Parameter
Value
VLAN
enabling
Enabled: Upstream packets contain VLAN tags.

Disabled: Upstream packets do not contain VLAN tags.
NOTE
If uservlan is set to untagged when you configure a service flow for
the Internet access service on the ONU, set this parameter to
Disabled; otherwise, set it to Enabled.
c.
3.
VLANID
[1-4094]
If VLAN enabling is set to Enabled, this parameter takes

the value of uservlan that is specified when you configure a
service flow for the Internet access service on the ONU.
Binding item

Mode
Bridge: PCs access the Internet in PPPoE dial-up mode.
Click OK.
Restart the HGW.


1.
2.

a.

IE and press Enter.
b.

Issue 02 (2013-10-08)
a.
b.
Parameter
Value
Bearing
service
INTERNET
Enabling
If this parameter is selected, WAN connection 1 is used.
VPI/VCI
Contact your carrier for the value ranges of VPIs and VCIs.
Ensure that the VPI/VCI setting (for example, 0/35) on an
HGW is consistent with that on the office to which the HGW
is connected.
Binding item

Mode
Bridge: PCs access the Internet in PPPoE dialup mode.

717

Configuration Guide
c.
3.

Parameter
Value
Encapsulation
mode
LLC
Click OK.
Restart the HGW.

----End
12.4.12 Configuring the IPTV Service (on the HGW)

This topic describes how to configure the IPTV service on the HGW that uses LAN or xDSL
for upstream transmission. This configuration enables home subscribers to watch IPTV
programs using STBs and TVs.
Context
This topic uses the HG239 that uses LAN for upstream transmission and the HG527 that uses
ADSL2+ for upstream transmission as examples.
Procedure
l

1.
2.

a.

b.

Issue 02 (2013-10-08)
a.
b.
In the right pane, create LAN connection 2 for the IPTV service. Set the
parameters as follows:
Parameter
Value
Bearing
service
VLAN
enabling
Enable VLAN tags are added to upstream packets.

NOTE
uservlan is tagged.

718

Configuration Guide
c.
3.

Parameter
Value
VLANID
[1-4094]
Multicast VLAN ID corresponding to the user VLAN value

for multicast service flows created on the ONU. In this
example, set this parameter to 43.
Binding item
LAN4
Mode
Bridge
DHCP
transparent
transmission
Enable
Restart the HGW.


1.
2.

a.

IE and press Enter.
b.

Issue 02 (2013-10-08)
a.
b.
In the right pane, create LAN connection 1 for dialup Internet access services.
Set the parameters as follows:
Parameter
Value
Bearing
service
Enabling
The LAN connection is enabled when this check box is

selected.
VLAN
enabling
Enable: VLAN tags are added to upstream packets.
VLANID
[1-4094]
Multicast VLAN ID on the HGW when multicast service

flows are created on the ONU. In this example, set this
parameter to 43.
VPI/VCI

0/35.
NOTE
uservlan is tagged.

719

Configuration Guide
c.
3.

Parameter
Value
Binding item
LAN4
Mode
Bridge
Encapsulation
mode
LLC
Restart the HGW.

----End
12.4.13 Configuring the VoIP Service (on the HGW)

This topic describes how to configure the voice service on HGWs that use LAN or xDSL for
upstream transmission. This configuration enables home subscribers to enjoy the POTS service
by using an analog telephone.
Context
This topic uses the HG255 that uses LAN for upstream transmission and the HG555 that
usesADSL2+ for upstream transmission as examples.
The IADs use SIP as the voice protocol.
Procedure
l
Configure the VoIP service on the HG255.

1.
2.
Log in to the Web configuration interface.

a.
Enter http://192.168.1.1 (default IP address) in the address bar of the browser

and press Enter.
b.
In the login window, enter the user name and password (the default value is
provided by ISP) of the administrator and click OK.
Configure parameters of the voice service.

The configuration procedure is as follows:
Issue 02 (2013-10-08)
a.
In the Web page, choose Network > Bandwidth Configuration from the
navigation tree.
b.
Create WAN Connection 3 for the VoIP service and set the parameters as follows:
Parameter
Value
Bearing
service
VoIP
Enabling
status
Enable

720


Configuration Guide
3.
Parameter
Value
VLAN mode
VLAN Transparent Transmission
VLAN ID
VLAN ID corresponding to the user VLAN value for voice

service flows created on the ONU. In this example, set this
parameter to 200.
802.1p
Enabled
Mode
Route: route mode
DHCP
Enabled
NAT
Enabled
c.
d.
Choose Appliciation > Broadband Phone Configuration from the navigation

tree. Configure the parameters as follows:
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
Enabling
Enabled
User number
When logging in to a VoIP account, you can set the user

account to the user telephone number. In this example, set
the user telephone number to 83110001.
User
password
Restart the HGW.

Configure the VoIP service (HG555)

1.
2.
Log in to the Web configuration interface.

a.
Enter http://192.168.1.1 (default IP address) in the address bar of the browser

and press Enter.
b.
In the login window, enter the user name and password (the default value is
provided by ISP) of the administrator and click OK.
Configure parameters of the voice service.

The configuration procedure is as follows:
Issue 02 (2013-10-08)
a.
Click Appliciation > Broadband Phone Configuration from the navigation

tree.
b.
Create WAN Connection 3 for the VoIP service and set the parameters as follows:

721


Configuration Guide
3.
Parameter
Value
Bearing
service
VoIP
Enabling
status
Implement
VPI/VCI

0/35.
VLAN mode
VLAN Transparent Transmission
VLAN ID
VLAN ID corresponding to the user VLAN value for voice

service flows created on the ONU. In this example, set this
parameter to 200.
802.1p
Enabled
Mode
Route mode
DHCP
Enabled
NAT
Enabled
c.
Click OK.
d.
Choose Appliciation > Broadband Phone Configuration from the navigation

tree. Configure the parameters as follows:
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
Enabling
Enabled
User number
When logging in to a VoIP account, you can set the user

account to the user telephone number. In this example, set
the user telephone number to 83110001.
User
password
Restart the HGW.

----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
Issue 02 (2013-10-08)

722

Configuration Guide

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
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
configured on the BRAS for the
one PPPoE dialup emulation.
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.
Item
Data
Remarks
PPPoE
dialup
emulation
parameter
Referenced service flow ID: 101
The entered user name, password, and

consistent with those configured on
the BRAS.
Data plan
Issue 02 (2013-10-08)
Emulation timeout time: 10s

723

Configuration Guide

Item
Data
Remarks
Multicast
emulation
parameter
Multicast service flow ID: 401
Multicast VLAN: 1000

IP address of the multicast program:
224.1.1.10
Procedure
l

1.

Command:
2.
command.
----------------------------------------------------------------Service-port: 101
User name:
user0
Result:
Success
//*Emulation result
Start time:
2011-11-16 15:41:29+08:00
End time:
2011-11-16 15:41:34+08:00
Session ID:
591
User IP:
192.168.50.2
Gateway IP:
192.168.50.254
-----------------------------------------------------------------
3.
Verify the multicast service using multicast emulation.

1.
Run the igmp static-join command to order a multicast program by emulating a

multicast user.
huawei(config)#btv
huawei(config-btv)#igmp static-join service-port 401 ip 224.1.1.10 vlan
1000
2.
Run the display igmp use command to query the status of the multicast user.
huawei(config-btv)#display igmp user service-port 401
User
: 0/3/1 //*Use an ETH port as an example.
State
: online
Authentication
: no-auth
Quick leave
: MAC-based
IGMP flow ID
: 0
Video flow ID
: 0
Log switch
: enable
Bind profiles
: IGMP version
: IGMP v3
Available programs
: 91
Issue 02 (2013-10-08)

724

Configuration Guide
Global Leave
User MaxBandWidth
The percentage of used
bandwidth to port rate(%)
Active program list

: disable
: no-limit
: 5000
: : : -
-------------------------------------------------------------------------Program name
VLAN IP/MAC
State
Start-time
-------------------------------------------------------------------------program1
1000 224.1.1.10
watching
2011-07-13
14:41:18
-------------------------------------------------------------------------Total: 1
3.
Run the display multicast flow-statistic command to query the real-time traffic of
the multicast program.
huawei(config-btv)#display multicast flow-statistic ip 224.1.1.10 vlan
1000
Command is being executed, please wait...
Multicast flow statistic result: 360(kbps)
Verify the VoD service.

1.
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.
If the VPI/VCI is 0/35 and the ADSL2+ port is 0/2/0, run the following command to
query the learned MAC addresses of VoD users:
huawei(config)#display mac-address service-port 301
Command:
display mac-address service-port 301
------------------------------------------------------------------------SRV-P BUNDLE TYPE MAC
MAC TYPE F /S /P VPI VCI
VLANID
INDEX INDEX
------------------------------------------------------------------------301
adl 1010-1010-1000 dynamic 0 /2 /0 0
35
300
------------------------------------------------------------------------Total: 1
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,
ppp--pppoe, ip--ipoe, ip6--ipv6oe
2.
Verify the VoIP service.

1.
Issue 02 (2013-10-08)
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.
Log in to the HGW management web page.
725

Configuration Guide

For details, see the 12.4.13 Configuring the VoIP Service (on the HGW).
2.
Choose Status > Broadband VoIP Information to query the service registration
status and telephone number.
Expected service registration status: Register successfully.
----End
Issue 02 (2013-10-08)

726

Configuration Guide
A Acronyms and Abbreviations
Acronyms and Abbreviations
A
ADSL
Asymmetrical Digital Subscriber Line
AG
Access Gateway
B
BRAS
Broadband Remote Access Server
BTV
Broadband TV
C
CAR
Committed Access Rate
CIR
Committed Information Rate
CLI
Command Line Interface
D
DHCP
Dynamic Host Configuration Protocol
DHCP
option82
DHCP relay agent option 82
E
EPON
Ethernet Passive Optical Network
Issue 02 (2013-10-08)

727

Configuration Guide
FoIP
Fax over Internet Protocol
FTP
File Transfer Protocol
G
GE
Gigabit Ethernet
GEM
GPON Encapsulation Method
GPON
Gigabit-capable Passive Optical Networks
I
IP
Internet Protocol
IPoA
Internet Protocol Over ATM
IPoE
IP over Ethernet
L
LAN
Local Area Network
M
MAC
Medium Access Control
MG
Media Gateway
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MoIP
Modem over Internet Protocol
MTU
Maximum Transmission Unit
N
NGN
Next Generation Network
NMS
Network Management System
Issue 02 (2013-10-08)
OLT
Optical Line Terminal
ONT
Optical Network Terminal

728

Configuration Guide
ONU
Optical Network Unit
P
PITP
Policy Information Transfer Protocol
PON
Passive Optical Network
POTS
Plain Old Telephone Service
PPPoA
Point-to-Point Protocol Over ATM
PPPoE
Point-to-Point Protocol Over Ethernet
PSTN
Public Switched Telephone Network
Q
QoS
Quality of Service
R
RFC
Remote Feature Control
S
SNMP
Simple Network Management Protocol
SSH
Secure Shell
STB
Set Top Box
STP
Spanning Tree Protocol
T
T-CONT
Transmission Container
TCP/IP
Transmission Control Protocol/Internet Protocol
TFTP
Trivial File Transfer Protocol
U
UDP
User Datagram Protocol
Issue 02 (2013-10-08)

729

Configuration Guide
Issue 02 (2013-10-08)
VLAN
Virtual LAN
VOD
Video On Demand
VoIP
Voice over Internet Protocol

730

MA5616 V800R311C01 Configuration Guide 02

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MA5616 V800R311C01 Configuration Guide 02

Uploaded by

Copyright:

Available Formats

SmartAX MA5616 Multi-service Access Module

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

About This Document

About This Document

Installation and commissioning engineers

System maintenance engineers

Data configuration engineers

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

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 titles

Multi-level menus are in boldface and separated by the ">"

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

About This Document

Modified: 3.1.4 Configuring Inband Management (GE Upstream)

4.4 (Optional) Configuring Line Bonding

4.8 (Optional) Configuring the VDSL2 Vectoring Function

Configuring the Ethernet Access Service

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

2 Checking Before the Configuration.........................................................................................11

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

3.7 Configuring a Route.....................................................................................................................................................91

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

3.14.4 Configuring Traffic Management Based on ACL Rules.......................................................................................178

4 Configuring the xDSL Internet Access Service...................................................................211

5 Configuring the Multicast Service (MVLAN Mode)..........................................................252

6 Configuring the Voice Service................................................................................................296

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

6.3.2 Configuring the IUA Link.......................................................................................................................................378

7 Configuring the Ethernet OAM..............................................................................................423

8 Configuring Network Protection............................................................................................431

9 Configuration Example of Services on the MA5616 Through GE Upstream Transmission

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

9.5.2 Configuring the VLAN ID Extension Service........................................................................................................524

10 FTTB and FTTC Service Overview......................................................................................552

11 Principle of FTTB and FTTC Data Plan..............................................................................565

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

A Acronyms and Abbreviations................................................................................................727

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module

1 Deploying Network Devices

Deploying Network Devices

About This Chapter

Huawei Proprietary and Confidential

SmartAX MA5616 Multi-service Access Module