Ma5612 configuration guide(v800 r308c00 04)

International Communication Instrument Co., Ltd. (ICI) Network Expertise Helps You Succeed

Dear Sir. / Madam,

How are you doing? Thanks for downloading this document.

Our company, ICI is an international telecommunication and ICT system consultant and value add distributor. We operate

in Beijing, China. Our main business is selling fixed telecom network equipments to world-wide customers, e.g. telecom

service providers and system integrators. We are specialized in below product series,

A. Optic transmission network equipments

a) Huawei Metro 1000, OSN 1500, OSN 3500, and OSN 7500 SDH/MSTP equipments.

b) Cisco 15454 / 15454E series SDH/MSTP equipments.

c) Potevio and other major Chinese brands’ microwave transmission equipments.

B. Data / IP network equipments

a) Cisco routers

i. Cisco 1941/2901/2911/2921/2951/3925/3945 series ISR G2 access routers.

ii. Cisco ASR1000 / ASR9000 / CRS-1 series service provider core and edge routers.

b) Cisco and Huawei Ethernet switches

i. Cisco 2960/2960S/3560/3560E/3560X/3750/3750E/3750X series access switches

ii. Cisco 4900/4500/6500 & Cisco Nexus 7000/5000/2000/1000 core and data center switches

iii. Huawei 2300/3300/5300/2700/3700/5700 series access switches.

iv. Huawei 9300/6700/7700 series high-end switches.

C. Access network equipments

a) Huawei UA5000 and other integrated access equipments..

b) Huawei MA5680T/MA5683T series OLT and FTTx equipments.

c) Huawei MA5600 series MDU: MA5616 (ADSL2+&POTS), MA5620 (FE&POTS), MA5626 (POTS).

D. Other telecom project and system materials, e. g. fiber optic cables, CAT5E cables, and other bulk materials.

Our contact information and monthly-updated product catalog is as below,

Contact: Morris Hagen

Mobile: +86 1390 120 9254

Office Phone: +86 10 8893 7226

Email: [email protected]

MSN Messenger: [email protected]

Yahoo Messenger: [email protected]

Skype: morris.hagen.ici

Website: http://www.ici-cn.com

Monthly-updated Product Catalog: http://www.ici-cn.com/download/pricing/ICI_Catalog.xls

We sincerely wish that we could bring solid help to your business!

Best Regards,

Morris Hagen, Sales Team of ICI

Network Expertise Helps You Succeed

mailto:[email protected]



http://www.ici-cn.com/

http://www.ici-cn.com/download/pricing/ICI_Catalog.xls

http://www.ici-cn.com/

SmartAX MA5612 Multi-service Access ModuleV800R308C00

Configuration Guide

Issue 04

Date 2011-04-27

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 04 (2011-04-27) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com


About This Document

Intended AudienceThis document describes the configuration of important services supported by the MA5612. Thedescription covers the following topics:l Purposel Networkingl Data planl Prerequisite(s)l Notel Configuration flowchartl Operation procedurel ResultThis document helps users to know the configuration of important services on the MA5612.

This document is intended for:

l Installation and commissioning engineersl System maintenance engineersl Data configuration engineers

Symbol ConventionsThe 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 notavoided, 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.

Indicates a potentially hazardous situation that, if notavoided, could cause equipment damage, data loss, andperformance degradation, or unexpected results.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide About This Document


iii

Symbol Description

Indicates a tip that may help you solve a problem or saveyour time.

Provides additional information to emphasize orsupplement important points of the main text.

Command ConventionsConvention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in square brackets [ ] areoptional.

{ x | y | ... } Alternative items are grouped in braces and separated byvertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square bracketsand separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated byvertical bars. A minimum of one or a maximum of all canbe selected.

GUI ConventionsConvention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the “>”signs. For example, choose File > Create > Folder.

Update HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Updates in Issue 04 (2011-04-27)Based on issue 03 (2010-12-15), the document is updated as follows:

The following information is modified:

About This DocumentSmartAX MA5612 Multi-service Access Module

Configuration Guide

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

l 1 Deploying Network Devicesl 3.5.1 Configuring the Reference Source of the System Clock


The following information is modified:

3.1.3 Configuring Outband Management


The following information is added:l 2 Checking Before the Configurationl 3.1.2 Configuring Local Management (Through a Service Port)l 3.6 Configuring the System Timel 3.7 Configuring the ACL for Packet Filteringl 3.8 Configuring QoS

Issue 01 (2010-08-06)This is the first release.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide About This Document


v

Contents

About This Document...................................................................................................................iii

1 Deploying Network Devices....................................................................................................1-11.1 Introduction to the Network Device Deployment...........................................................................................1-21.2 Example of Deploying Network Devices........................................................................................................1-3

2 Checking Before the Configuration.......................................................................................2-12.1 Checking the Software Version.......................................................................................................................2-22.2 Checking the Board Status..............................................................................................................................2-2

3 Basic Configuration...................................................................................................................3-13.1 Configuring the Maintenance Terminal..........................................................................................................3-3

3.1.1 Configuring Management Through a Local Serial Port.........................................................................3-33.1.2 Configuring Local Management (Through a Service Port)....................................................................3-93.1.3 Configuring Outband Management......................................................................................................3-113.1.4 Configuring Inband Management (GPON Upstream).........................................................................3-153.1.5 Configuring Inband Management (GE Upstream)...............................................................................3-18

3.2 Configuring the NMS....................................................................................................................................3-223.2.1 Configuring the NMS (Based on SNMP V1).......................................................................................3-223.2.2 Configuring the NMS (Based on SNMP V2c).....................................................................................3-283.2.3 Configuring the NMS (Based on SNMP V3).......................................................................................3-32

3.3 Configuring the Attributes of the Upstream Port..........................................................................................3-373.3.1 Configuring the Attributes of the Upstream Ethernet Port..................................................................3-373.3.2 Configuring the Attributes of the Upstream PON Port........................................................................3-39

3.4 Configuring a VLAN....................................................................................................................................3-403.5 Configuring the System Clock......................................................................................................................3-46

3.5.1 Configuring the Reference Source of the System Clock......................................................................3-463.5.1.1 Configuring the Reference Source of the 1588V2 Clock..................................................................3-473.5.1.2 Configuring the Line Clock Reference Source.................................................................................3-493.5.2 Configuring the Priority of the System Clock......................................................................................3-50

3.6 Configuring the System Time.......................................................................................................................3-513.6.1 Configuring the 1588V2-Based Time..................................................................................................3-513.6.2 Configuring the NTP Time..................................................................................................................3-533.6.2.1 (Optional) Configuring NTP Authentication....................................................................................3-553.6.2.2 Configuring the NTP Broadcast Mode..............................................................................................3-56

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide Contents


vii

3.6.2.3 Configuring the NTP Multicast Mode..............................................................................................3-573.6.2.4 Configuring the NTP Unicast Server Mode......................................................................................3-593.6.2.5 Configuring the NTP Peer Mode......................................................................................................3-61

3.7 Configuring the ACL for Packet Filtering....................................................................................................3-633.7.1 Configuring the Basic ACL for Packet Filtering.................................................................................3-653.7.2 Configuring the Advanced ACL for Packet Filtering..........................................................................3-663.7.3 Configuring the Link Layer ACL for Packet Filtering........................................................................3-67

3.8 Configuring QoS...........................................................................................................................................3-683.8.1 Configuring Traffic Management........................................................................................................3-693.8.1.1 Configuring Traffic Management Based on Service Port.................................................................3-693.8.1.2 Configuring Rate Limitation on an Ethernet Port.............................................................................3-723.8.1.3 Configuring User-based Rate Limitation..........................................................................................3-733.8.1.4 Configuring Traffic Suppression.......................................................................................................3-743.8.2 Configuring Queue Scheduling............................................................................................................3-763.8.2.1 Configuring the Queue Scheduling Mode.........................................................................................3-763.8.2.2 Configuring the Mapping Between the Queue and the 802.1p Priority............................................3-783.8.3 Configuring Early Drop.......................................................................................................................3-793.8.4 Configuring Traffic Management Based on ACL Rules......................................................................3-803.8.4.1 Controlling the Traffic Matching an ACL Rule................................................................................3-803.8.4.2 Adding a Priority Tag to the Traffic Matching an ACL Rule...........................................................3-813.8.4.3 Enabling the Statistics Collection of the Traffic Matching an ACL Rule.........................................3-823.8.4.4 Enabling the Mirroring of the Traffic Matching an ACL Rule.........................................................3-83

3.9 Configuring Environment Monitoring..........................................................................................................3-833.9.1 Configuring Monitoring Through the ESC..........................................................................................3-843.9.1.1 Configuring the Monitoring Through the H831VESC.....................................................................3-843.9.1.2 Configuring the Monitoring Through the ESCM..............................................................................3-873.9.2 Configuring the Monitoring Through the EPS30-4815AF..................................................................3-913.9.3 Configuring the Monitoring Through the Fan......................................................................................3-97

4 Configuring the Ethernet OAM..............................................................................................4-14.1 Configuring the Ethernet CFM OAM.............................................................................................................4-24.2 Configuring the Ethernet EFM OAM.............................................................................................................4-4

5 Configuring the Ethernet Access Service..............................................................................5-15.1 Configuring a VLAN......................................................................................................................................5-25.2 Configuring the Upstream Port.......................................................................................................................5-85.3 Creating the Ethernet Access Service Port......................................................................................................5-8

6 Configuring the Multicast Service (Multicast VLAN Mode)............................................6-16.1 Default Settings of the Multicast Service........................................................................................................6-26.2 Configuring the Multicast Service on a Single-NE Network..........................................................................6-2

6.2.1 Configuring Global Multicast Parameters..............................................................................................6-46.2.2 Configuring the Multicast Program........................................................................................................6-66.2.3 Configuring the Multicast User............................................................................................................6-10

ContentsSmartAX MA5612 Multi-service Access Module

Configuration Guide

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

6.2.4 (Optional) Configuring the Multicast Bandwidth................................................................................6-136.2.5 (Optional) Configuring the Multicast Preview.....................................................................................6-166.2.6 (Optional) Configuring the Program Prejoin.......................................................................................6-206.2.7 (Optional) Configuring the Multicast Log...........................................................................................6-21

7 Configuring the Voice Service.................................................................................................7-17.1 Configuring the VoIP PSTN Service (Based on the H.248 Protocol)............................................................ 7-3

7.1.1 Configuring an MG Interface.................................................................................................................7-77.1.1.1 Configuring the Upstream VLAN Interface........................................................................................7-87.1.1.2 Configuring the Media and Signaling IP Address Pools.....................................................................7-97.1.1.3 Adding an MG Interface...................................................................................................................7-107.1.1.4 (Optional) Configuring the Digitmap of an MG Interface................................................................7-127.1.1.5 (Optional) Configuring the Software Parameters of an MG Interface..............................................7-147.1.1.6 (Optional) Configuring the Ringing Mode of an MG Interface........................................................7-197.1.1.7 (Optional) Configuring the TID Format of an MG Interface............................................................7-217.1.1.8 Enabling an MG Interface.................................................................................................................7-237.1.2 Configuring the VoIP PSTN User........................................................................................................7-247.1.2.1 Configuring the PSTN User Data......................................................................................................7-257.1.2.2 (Optional) Configuring the System Parameters................................................................................7-287.1.2.3 (Optional) Configuring the Overseas Parameters.............................................................................7-297.1.2.4 (Optional) Configuring the Local Digitmap......................................................................................7-307.1.2.5 (Optional) Configuring the Attributes of a PSTN Port.....................................................................7-337.1.2.6 (Optional) Configuring the Attributes of the Ringing Current.........................................................7-34

7.2 Configuring the VoIP PSTN Service (Based on the SIP Protocol)...............................................................7-357.2.1 Configuring the SIP Interface..............................................................................................................7-397.2.1.1 Configuring the Upstream VLAN Interface......................................................................................7-397.2.1.2 Configuring the Media and Signaling IP Address Pools...................................................................7-407.2.1.3 Adding an SIP Interface....................................................................................................................7-417.2.1.4 (Optional) Configuring the Ringing Mode of the SIP Interface.......................................................7-437.2.2 Configuring the VoIP PSTN User........................................................................................................7-457.2.2.1 Configuring the PSTN User Data......................................................................................................7-467.2.2.2 Configuring the Centrex....................................................................................................................7-487.2.2.3 (Optional) Configuring the System Parameters................................................................................7-507.2.2.4 (Optional) Configuring the Overseas Parameters.............................................................................7-517.2.2.5 (Optional) Configuring the Local Digitmap......................................................................................7-527.2.2.6 (Optional) Configuring the Attributes of a PSTN Port.....................................................................7-557.2.2.7 (Optional) Configuring the Attributes of the Ringing Current.........................................................7-57

7.3 Configuring the VoIP ISDN PRA Service (Based on the H.248 Protocol)..................................................7-587.3.1 Configuring an MG Interface...............................................................................................................7-637.3.1.1 Configuring the Upstream VLAN Interface......................................................................................7-647.3.1.2 Configuring the Media and Signaling IP Address Pools...................................................................7-657.3.1.3 Adding an MG Interface...................................................................................................................7-667.3.1.4 (Optional) Configuring the Digitmap of an MG Interface................................................................7-67



ix

7.3.1.5 (Optional) Configuring the Software Parameters of an MG Interface..............................................7-707.3.1.6 (Optional) Configuring the Ringing Mode of an MG Interface........................................................7-757.3.1.7 (Optional) Configuring the TID Format of an MG Interface............................................................7-777.3.1.8 Enabling an MG Interface.................................................................................................................7-797.3.2 Configuring the IUA Link....................................................................................................................7-807.3.2.1 Adding an IUA Link Set...................................................................................................................7-817.3.2.2 Adding an IUA Link.........................................................................................................................7-817.3.3 Configuring the VoIP ISDN PRA User...............................................................................................7-827.3.3.1 Configuring the Attributes of the E1 Port.........................................................................................7-837.3.3.2 Configuring the ISDN PRA User Data.............................................................................................7-847.3.3.3 (Optional) Configuring the System Parameters................................................................................7-867.3.3.4 (Optional) Configuring the Overseas Parameters.............................................................................7-87

7.4 Configuring the VoIP ISDN PRA Service (Based on the SIP Protocol)......................................................7-887.4.1 Configuring the SIP Interface..............................................................................................................7-917.4.1.1 Configuring the Upstream VLAN Interface......................................................................................7-927.4.1.2 Configuring the Media and Signaling IP Address Pools...................................................................7-937.4.1.3 Adding an SIP Interface....................................................................................................................7-947.4.1.4 (Optional) Configuring the Ringing Mode of the SIP Interface.......................................................7-967.4.2 Configuring the VoIP ISDN PRA User...............................................................................................7-987.4.2.1 Configuring the Attributes of the E1 Port.........................................................................................7-987.4.2.2 Configuring the ISDN PRA User Data.............................................................................................7-997.4.2.3 (Optional) Configuring the System Parameters..............................................................................7-1017.4.2.4 (Optional) Configuring the Overseas Parameters...........................................................................7-102

7.5 Configuring the FoIP Service (Based on the H.248 Protocol)....................................................................7-1047.6 Configuring the FoIP Service (Based on the SIP Protocol)........................................................................7-1067.7 Configuring the MoIP Service (Based on the H.248 Protocol)...................................................................7-1097.8 Configuring the MoIP Service (Based on the SIP Protocol).......................................................................7-1117.9 Configuring the Security and Reliability of the Voice Service...................................................................7-113

7.9.1 Configuring the Device Authentication.............................................................................................7-1137.9.1.1 Configuring the Device Authentication (Based on the H.248 Protocol).........................................7-1147.9.1.2 Configuring the Device Authentication (Based on the SIP Protocol).............................................7-1157.9.2 Configuring the Dual Homing............................................................................................................7-1167.9.2.1 Configuring the Dual Homing (Based on the H.248 Protocol).......................................................7-1177.9.2.2 Configuring the Dual Homing (Based on the SIP Protocol)...........................................................7-1187.9.3 Configuring the Emergency Standalone............................................................................................7-119

8 Configuration Examples of the MA5612................................................................................8-18.1 Configuration Example of the Ethernet Access Service in the Single-Port for Multi-Service Mode.............8-28.2 Configuration Example of the Multicast Service (Multicast VLAN Mode)...................................................8-8

8.2.1 Configuration Example of the Multicast Video Service (Static Configuration Mode)..........................8-88.2.2 Configuration Example of the Multicast Video Service (Dynamic Generation Mode).......................8-12

8.3 Configuration Example of the VoIP Service.................................................................................................8-168.3.1 Configuration Example of the VoIP PSTN Service (Based on the H.248 Protocol)...........................8-16

ContentsSmartAX MA5612 Multi-service Access Module

Configuration Guide

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

8.3.2 Configuration Example of the VoIP PSTN Service (Based on the SIP Protocol)...............................8-258.3.3 Configuration Example of the VoIP ISDN PRA Service (Based on the H.248 Protocol)...................8-288.3.4 Configuration Example of the VoIP ISDN PRA Service (Based on the SIP Protocol).......................8-36

8.4 Configuration Example of the VLAN Stacking Wholesale Service.............................................................8-398.4.1 Configuration Example of the VLAN Stacking Wholesale Service....................................................8-408.4.2 Configuration Example of the VLAN ID Extension Service...............................................................8-44

9 Configuration Examples of the FTTx.....................................................................................9-19.1 FTTx Network and Product.............................................................................................................................9-29.2 FTTx Data Plan (GPON Access)....................................................................................................................9-39.3 Configuring the FTTB and FTTC Access Services......................................................................................9-11

9.3.1 Configuring the FTTB and FTTC Internet Access Services (LAN Access)........................................9-129.3.2 Configuring the FTTB and FTTC VoIP Services (Based on the H.248 Protocol)..............................9-209.3.3 Configuring the FTTB and FTTC VoIP Services (Based on the SIP Protocol)..................................9-309.3.4 Configuring the FTTB and FTTC IPTV Multicast Services................................................................9-40

9.4 Configuring the FTTO Service.....................................................................................................................9-499.4.1 Configuring the TDM PBX Access Service........................................................................................9-499.4.2 Configuring the Enterprise Router Access Service..............................................................................9-519.4.3 Configuring the IP PBX Access Service..............................................................................................9-599.4.4 Configuring the POTS Access Service of the Enterprise.....................................................................9-60

9.5 Configuring the FTTM Service.....................................................................................................................9-689.5.1 Configuring FTTM Clock Synchronization.........................................................................................9-699.5.1.1 Overview of FTTM Clock Synchronization.....................................................................................9-709.5.1.2 Configuring BITS Clock Synchronization........................................................................................9-759.5.1.3 Configuring E1/STM-1 Line Clock Synchronization.......................................................................9-789.5.1.4 Configuring Ethernet Clock Synchronization...................................................................................9-809.5.1.5 Configuring 1588V2 Clock Synchronization....................................................................................9-839.5.2 Configuring FTTM Network Protection..............................................................................................9-919.5.3 Configuring the Native TDM Base station access Service (SDH-based)............................................9-939.5.4 Configuring the TDM PWE3 Base station access Service on the OLT (MPLS-based)....................9-1019.5.5 Configuring the TDM PWE3 Base station access Service on the OLT (IP-based)...........................9-1139.5.6 Configuring the ETH PWE3 Base station access Service on the OLT..............................................9-1259.5.7 Configuring the QinQ Private Line Base station access Service for the OLT...................................9-136

10 Configuring the P2P Optical Fiber Access Service..........................................................10-110.1 Configuring MDUs Subtended to an OLT..................................................................................................10-2

A Acronyms and Abbreviations................................................................................................A-1



xi

Figures

Figure 1-1 Example network of device deployment in the scenario with the NMS............................................1-4Figure 1-2 Example network of device deployment in the scenario without the NMS.......................................1-5Figure 3-1 Example network for configuring management through a local serial port.......................................3-3Figure 3-2 Flowchart for configuring management through a local serial port...................................................3-4Figure 3-3 Setting up a connection.......................................................................................................................3-5Figure 3-4 Selecting the serial port ID.................................................................................................................3-5Figure 3-5 Setting the parameters of the HyperTerminal.....................................................................................3-6Figure 3-6 HyperTerminal interface.....................................................................................................................3-7Figure 3-7 Setting the terminal emulation type....................................................................................................3-8Figure 3-8 Setting the line delay and the character delay....................................................................................3-9Figure 3-9 Example network for configuring the local maintenance mode through a local maintenance networkport......................................................................................................................................................................3-10Figure 3-10 Starting Telnet................................................................................................................................3-11Figure 3-11 Example network for configuring outband management over a LAN in the telnet mode.............3-12Figure 3-12 Example network for configuring outband management over a WAN in the telnet mode............3-13Figure 3-13 Flowchart for outband management in the telnet mode.................................................................3-14Figure 3-14 Starting Telnet................................................................................................................................3-15Figure 3-15 Example network for configuring inband management over a LAN in the GPON upstream mode.............................................................................................................................................................................3-16Figure 3-16 Example network for configuring inband management over a WAN in the GPON upstream mode.............................................................................................................................................................................3-16Figure 3-17 Flowchart for configuring inband management in the GPON upstream mode..............................3-17Figure 3-18 Example network for configuring inband management over a LAN in the telnet mode...............3-18Figure 3-19 Example network for configuring inband management over a WAN in the telnet mode..............3-19Figure 3-20 Flowchart for configuring inband management in the telnet mode................................................3-20Figure 3-21 Starting Telnet................................................................................................................................3-21Figure 3-22 Inband networking..........................................................................................................................3-23Figure 3-23 Outband networking.......................................................................................................................3-24Figure 3-24 Flowchart for configuring the NMS...............................................................................................3-24Figure 3-25 NTP broadcast mode......................................................................................................................3-56Figure 3-26 NTP multicast mode.......................................................................................................................3-58Figure 3-27 NTP client/server mode..................................................................................................................3-60Figure 3-28 NTP peer mode...............................................................................................................................3-62Figure 4-1 Example network of the Ethernet CFM OAM function.....................................................................4-2

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide Figures


xiii

Figure 4-2 Example network of the Ethernet EFM OAM function.....................................................................4-5Figure 8-1 Example network of the Ethernet access service (PON upstream)....................................................8-3Figure 8-2 Example network of the Ethernet access service (GE upstream).......................................................8-4Figure 8-3 Flowchart for configuring the Ethernet access service on the MA5612............................................8-5Figure 8-4 Example network of the multicast service..........................................................................................8-9Figure 8-5 Example network of the multicast service........................................................................................8-13Figure 8-6 Example network of the VoIP service based on the H.248 protocol................................................8-17Figure 8-7 Example network of the VoIP PSTN service based on the SIP protocol.........................................8-25Figure 8-8 Example network for configuring the H.248-based VoIP ISDN PRA service.................................8-29Figure 8-9 Example network of the VoIP ISDN PRA service when the SIP protocol is used..........................8-37Figure 8-10 Example network for configuring the VLAN stacking wholesale service.....................................8-41Figure 8-11 Example network for configuring the VLAN ID extension...........................................................8-45Figure 9-1 Example network of full access services in the FTTx scenario..........................................................9-2Figure 9-2 Example network of the multiple service in FTTB and FTTC service............................................ 9-11Figure 9-3 Example network of the TDM PBX access service..........................................................................9-50Figure 9-4 Example network of the enterprise router access service.................................................................9-51Figure 9-5 Example network of the IP PBX access service...............................................................................9-59Figure 9-6 Example network of the POTS access service of the enterprise...................................................... 9-61Figure 9-7 Clock synchronization solution in an FTTM network......................................................................9-71Figure 9-8 BITS clock synchronization............................................................................................................. 9-75Figure 9-9 E1/STM-1 line clock synchronization..............................................................................................9-78Figure 9-10 Ethernet clock synchronization.......................................................................................................9-81Figure 9-11 1588V2 time injection....................................................................................................................9-84Figure 9-12 E2E 1588V2................................................................................................................................... 9-84Figure 9-13 FTTM network protection..............................................................................................................9-92Figure 9-14 Native TDM base station access service........................................................................................ 9-94Figure 9-15 Example network of the TDM PWE3 base station access service on the OLT (MPLS-based)...........................................................................................................................................................................9-102Figure 9-16 Example network of the TDM PWE3 base station access service on the OLT (IP-based)..........9-114Figure 9-17 Example network of the ETH PWE3 base station access service on the OLT.............................9-125Figure 9-18 Example network of the QinQ private line base station access service.......................................9-137Figure 10-1 Network of MDUs subtended to an OLT.......................................................................................10-2

FiguresSmartAX MA5612 Multi-service Access Module

Configuration Guide

xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

Tables

Table 1-1 Activities involved in network device deployment in the scenario with the NMS..............................1-2Table 1-2 Activities involved in network device deployment in the scenario without the NMS.........................1-3Table 3-1 Data plan for configuring outband management over a LAN in the telnet mode..............................3-12Table 3-2 Data plan for configuring outband management over a WAN in the telnet mode.............................3-13Table 3-3 Data plan for configuring inband management over a LAN in the telnet mode................................3-19Table 3-4 Data plan for configuring inband management over a WAN in the telnet mode...............................3-19Table 3-5 Default settings of the attributes of an Ethernet port.........................................................................3-37Table 3-6 VLAN application and planning........................................................................................................3-41Table 3-7 Default parameter settings of VLAN.................................................................................................3-41Table 3-8 VLAN types and application scenarios..............................................................................................3-42Table 3-9 VLAN attributes and application scenarios.......................................................................................3-43Table 3-10 Default values of the 1588V2 clock reference source .....................................................................3-47Table 3-11 Default values of the 1588V2 clock reference source .....................................................................3-51Table 3-12 Default configuration for NTP.........................................................................................................3-54Table 3-13 ACL types........................................................................................................................................3-63Table 3-14 Traffic parameters defined in the IP traffic profiles.........................................................................3-70Table 3-15 Mapping between the queue weights and the actual queues............................................................3-76Table 3-16 Mapping between the queue and the 802.1p priority.......................................................................3-78Table 3-17 Data plan for configuring the H831VESC.......................................................................................3-85Table 3-18 Data plan for configuring the ESCM...............................................................................................3-88Table 3-19 Data plan for configuring the EPS30-4815AF.................................................................................3-92Table 3-20 Data plan for configuring monitoring through the fan.....................................................................3-98Table 5-1 VLAN application and planning..........................................................................................................5-2Table 5-2 Default parameter settings of VLAN...................................................................................................5-3Table 5-3 VLAN types and application scenarios................................................................................................5-3Table 5-4 VLAN attributes and application scenarios.........................................................................................5-4Table 6-1 Default settings of the multicast service..............................................................................................6-2Table 6-2 Data plan for configuring the multicast service on a standalone MA5612..........................................6-3Table 7-1 Data plan for configuring the VoIP PSTN service based on the H.248 protocol................................7-4Table 7-2 Digitmap format in the H.248 protocol..............................................................................................7-12Table 7-3 Software parameters of an MG interface that supports H.248...........................................................7-14Table 7-4 Default settings of the attributes of the PSTN user............................................................................7-26Table 7-5 System parameters supported by the MA5612..................................................................................7-28

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide Tables


xv

Table 7-6 Overseas parameters supported by the MA5612................................................................................7-29Table 7-7 Information about the default local digitmap when the SIP protocol is used....................................7-30Table 7-8 Local digitmap existing in the system................................................................................................7-31Table 7-9 Local digitmap existing in the system................................................................................................7-32Table 7-10 Local digitmap to be added..............................................................................................................7-32Table 7-11 Data plan for configuring the VoIP service based on the SIP protocol........................................... 7-36Table 7-12 Default settings of the attributes of the PSTN user..........................................................................7-46Table 7-13 System parameters supported by the MA5612................................................................................ 7-50Table 7-14 Overseas parameters supported by the MA5612..............................................................................7-52Table 7-15 Information about the default local digitmap when the SIP protocol is used..................................7-53Table 7-16 Local digitmap existing in the system..............................................................................................7-54Table 7-17 Local digitmap existing in the system..............................................................................................7-54Table 7-18 Local digitmap to be added..............................................................................................................7-55Table 7-19 Data plan for configuring the H.248-based VoIP ISDN BRA service.............................................7-59Table 7-20 Digitmap format in the H.248 protocol............................................................................................7-68Table 7-21 Software parameters of an MG interface that supports H.248.........................................................7-70Table 7-22 Default values of the E1 port........................................................................................................... 7-83Table 7-23 Default settings of the attributes of the ISDN PRA user................................................................. 7-84Table 7-24 System parameters supported by the MA5612................................................................................ 7-86Table 7-25 Overseas parameters supported by the MA5612..............................................................................7-87Table 7-26 Data plan for configuring the VoIP ISDN PRA service when the SIP protocol is used..................7-89Table 7-27 Default values of the E1 port........................................................................................................... 7-99Table 7-28 Default settings of the attributes of the ISDN PRA user...............................................................7-100Table 7-29 System parameters supported by the MA5612..............................................................................7-102Table 7-30 Overseas parameters supported by the MA5612............................................................................7-103Table 7-31 Default configuration of the flows of the FoIP service..................................................................7-105Table 7-32 Items involved in the FoIP service.................................................................................................7-107Table 7-33 Default configuration of the flows of the FoIP service..................................................................7-107Table 7-34 Data plan for configuring the authentication parameters (H.248).................................................7-114Table 7-35 Related operation for configuring the dual homing (H.248)..........................................................7-118Table 7-36 Related operation for configuring the dual homing.......................................................................7-119Table 8-1 Data plan for configuring the Ethernet access service.........................................................................8-4Table 8-2 Data plan for configuring the multicast service...................................................................................8-9Table 8-3 Data plan for configuring the multicast service.................................................................................8-13Table 8-4 Data plan for configuring the VoIP service based on the H.248 protocol.........................................8-18Table 8-5 Data plan for configuring the VoIP PSTN service based on the SIP protocol...................................8-26Table 8-6 Data plan for configuring the H.248-based VoIP ISDN PRA service...............................................8-30Table 8-7 Data plan for configuring the VoIP PSTN service when the SIP protocol is used............................8-38Table 8-8 Data plan for configuring the VLAN stacking wholesale service..................................................... 8-41Table 8-9 Data plan for configuring the VLAN ID extension............................................................................8-45Table 9-1 Configuration products for the FTTx solution.....................................................................................9-3Table 9-2 Data plan for the FTTx GPON access..................................................................................................9-4

TablesSmartAX MA5612 Multi-service Access Module

Configuration Guide

xvi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

Table 9-3 Data plan for configuring the enterprise router access service-OLT side..........................................9-51Table 9-4 Data plan for configuring the enterprise router access service-ONU side.........................................9-52Table 9-5 Comparison of clock synchronization solution..................................................................................9-72Table 9-6 Data plan for configuring the Native TDM base station access service-OLT side............................9-94Table 9-7 Data plan for configuring the Native TDM base station access service-ONU side...........................9-95Table 9-8 Data plan for configuring the TDM PWE3 base station access service-OLT side..........................9-102Table 9-9 Data plan for configuring the TDM PWE3 base station access service-ONU side.........................9-103Table 9-10 Data plan for configuring the TDM PWE3 base station access service-OLT side........................9-114Table 9-11 Data plan for configuring the TDM PWE3 base station access service-ONU side.......................9-116Table 9-12 Data plan for configuring the TDM PWE3 base station access service-OLT side........................9-126Table 9-13 Data plan for configuring the ETH PWE3 base station access service-ONU side........................9-127Table 9-14 Data plan for configuring the QinQ private line base station access service-OLT side................9-137Table 9-15 Data plan for configuring the QinQ private line base station access service-MA5612 side..........9-138Table 10-1 Data plan..........................................................................................................................................10-2

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide Tables


xvii

1 Deploying Network Devices

About This Chapter

Deploy the ONUs at sites according to network planning so that the NMS, OLT, and ONU cancommunicate with each other.

1.1 Introduction to the Network Device DeploymentThis topic describes how to deploy network devices, including optical network unit (ONU) dataplan, 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 DevicesThis topic describes how to deploy network devices in the scenario with or without the NMS.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 1 Deploying Network Devices


1-1

1.1 Introduction to the Network Device DeploymentThis topic describes how to deploy network devices, including optical network unit (ONU) dataplan, 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 withthe NMS.

Table 1-1 Activities involved in network device deployment in the scenario with the NMS

Activities Description

ONU data planNOTE

The ONU refers toMA5612.

Perform the data plan according to the network planning sheetprovided by the NMS. The resource deployment sheet will begenerated finally.

ONU offline deployment Import the resource deployment sheet through the NMS toimplement the predeployment for the ONU.

ONU installation The hardware installation engineer draws the ONU from thestorehouse and installs it at the destination site. After installing itand confirming that the hardware is fault-free, the hardwareinstallation engineer returns the ONU type, service portinformation, and ONU SN to the commissioning engineer.

ONU binding The IP address and the SN of the ONU are bound through theNMS.

Table 1-2 describes the activities involved in network device deployment in the scenario withoutthe NMS.

NOTE

In the scenario without the NMS, you can add the ONT through the OLT by using one of the followingmethods:

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 auto-discovery function.

3. The OLT discovers the ONU automatically.

4. Run the ont confirm command to in the GPON mode confirm the automatically discovered ONU.

l 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.

1 Deploying Network DevicesSmartAX MA5612 Multi-service Access Module

Configuration Guide

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

Table 1-2 Activities involved in network device deployment in the scenario without the NMS

Activities Description

ONU data planNOTE

The ONU refers toMA5612.

Perform the data plan for the OLT and ONU according to theactual FTTx service plan and the corresponding OLT version.

ONU installation The hardware installation engineer draws the ONU from thestorehouse and installs it at the destination site. After installing itand confirming that the hardware is fault-free, the hardwareinstallation engineer returns the ONU type, service portinformation, and ONU SN to the commissioning engineer.

ONU deployment Enable the auto-discovery function on the PON port through theCLI command of the OLT, confirm the automatically discoveredONU, and add the ONU by using the preconfigured profile.

Configuration of theservices of the ONU

You can telnet to the ONU according to the management IPaddress of the ONU to configure the services for the ONU.

1.2 Example of Deploying Network DevicesThis topic describes how to deploy network devices in the scenario with or without the NMS.

Prerequisitel Network devices and lines must be in the normal state.l The control board and the GPON service board of the OLT must be in the normal state.

ContextWhen the ONU adopts the GPON upstream transmission, the SN is used for authentication.

Scenario with the NMSFigure 1-1 shows an example network of device deployment in the scenario with the NMS.



1-3

Figure 1-1 Example network of device deployment in the scenario with the NMS

Router

OLT

Splitter

ONU_BONU_A ONU_DONU_C

NMS client_B

NMS client_A

NMS

Splitter

MGC

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 networkplanning sheet and obtains the resource deployment sheet.

2. The commissioning engineer imports the resource deployment sheet through the NMS toimplement 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 destinationsites.

4. The hardware installation engineer checks the running status of the ONU that is installedand 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.


Configuration Guide


Issue 04 (2011-04-27)

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 SNto 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 ONUthrough the NMS.

7. After being powered on, the ONU registers with the OLT automatically. Then, the OLTsends 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 forinforming the NMS that an ONU goes online.

8. The commissioning engineer receives the trap indicating that the ONU goes online reportedby the OLT on the NMS.After the trap indicating that the ONU goes online is received on the NMS, the ONUmanagement channel is enabled successfully. Then, you can remotely configure servicesfor the ONU through the NMS.

Scenario Without the NMSFigure 1-2 shows an example network of device deployment in the scenario without the NMS.

Figure 1-2 Example network of device deployment in the scenario without the NMS

Router

OLT

Splitter

ONU_BONU_A ONU_DONU_C

PC_B

PC_A

Splitter

MGC



1-5

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, thecommissioning 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 destinationsites.

3. The hardware installation engineer checks the running status of the ONU that is installedand 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.

4. After confirming that the ONU works in the normal state (the Link LED is on and the AuthLED blinks), the hardware installation engineer records the ONU SN and reports the SNto the commissioning engineer.

5. According to the data plan of the OLT and ONU, the commissioning engineer configuresdata 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. The commissioning engineer telnets to the ONU according to the management IP address

of the ONU to configure the services for the ONU.


Configuration Guide


Issue 04 (2011-04-27)

2 Checking Before the Configuration

About This Chapter

Before the service configuration, you need to check the software version and board status of theMA5612 to ensure that the service runs normally after the configuration.

2.1 Checking the Software VersionThis topic describes how to check whether the current software version meets the deploymentrequirement.

2.2 Checking the Board StatusThis topic describes how to check whether the inserted board is the same as the board specifiedin the data plan, and whether the boards are in the normal state.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 2 Checking Before the Configuration


2-1

2.1 Checking the Software VersionThis topic describes how to check whether the current software version meets the deploymentrequirement.

PrerequisiteYou must be logged in to the MA5612. For details about how to log in to the device, see 3.1Configuring the Maintenance Terminal.

Procedurel The procedure of checking the software version through the MA5612 is as follows:

1. In the user mode, run the display language command to check whether the multi-language information supported by the system and the system version meet thedeployment requirement.

2. In the user mode, run the display version command to check whether the versions ofthe host software and patch that is running in the system meet the deploymentrequirement.

l The procedure of checking the software version through the iManager U2000 is as follows:

1. In the Workbench window, double-click . The Main Topology window is

displayed. Click .2. In the Search dialog box, select NE from the Search Type drop-down list and enter

the description of the MA5612 to be queried. Then, click Search.3. In the search result, select the desired MA5612. Click Locate and select Locate to

NE Panel from the list. In the Device Detailed Info tab page, verify that the devicetype and activated patch meet the deployment requirement.

----End

Resultl The versions of the host software and patch meet the deployment requirement.l 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 theMA5612 Upgrade guide.

2.2 Checking the Board StatusThis topic describes how to check whether the inserted board is the same as the board specifiedin the data plan, and whether the boards are in the normal state.

Procedurel The procedure of checking the board status through the MA5612 is as follows:

1. Run the display board command to check whether the board information (includingthe board types and the slots housing the boards) meets the data plan and whether theboards are in the normal state.

2 Checking Before the ConfigurationSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

– If all the required boards are inserted correctly and all the boards are in the normalstate, the operation ends.

– If a required board is not inserted in the device, insert the board and run the boardconfirm command to confirm the board in the auto-find state. Then, run the displayboard command to query the status of all the boards.

l The procedure of checking the board status through the iManager U2000 is as follows:

1. In the Workbench window, double-click . The Main Topology window is

displayed. Click .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 MA5612. Click Locate to

Board. Then, verity that the board type and slot meet the requirements of the dataplanning and verify the board status.

----End

Resultl The status of all the boards is "Normal" in the result of the query on the MA5612.

l All the boards on the MA5612 are in the normal state, represented by , in the result ofthe query through the iManager U2000.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 2 Checking Before the Configuration


2-3

3 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 havedefinite logic relations between each other. Therefore, you can perform the configuration basedon actual requirements.

3.1 Configuring the Maintenance TerminalThis topic describes three modes of managing the MA5612 from the maintenance terminal.

3.2 Configuring the NMSThe MA5612 can be interconnected with Huawei iManager U2000 (hereinafter referred to asU2000). Hence, the administrator can maintain and manage the device through the U2000. TheMA5612 can be interconnected with the U2000 in inband or outband networking mode. Thefollowing part describes how to configure the inband networking and outband networking basedon SNMP V1, SNMP V2c, and SNMP V3 respectively.

3.3 Configuring the Attributes of the Upstream PortThe MA5612 can be interconnected with the OLT through upstream GPON/GE port. This topicdescribes how to configure the attributes of upstream GPON/GE port so that the devicecommunicates successfully with the upstream device.

3.4 Configuring a VLANConfiguring VLAN is a prerequisite for configuring a service. Hence, before configuring aservice, make sure that the VLAN configuration based on planning is complete.

3.5 Configuring the System ClockThis topic describes how to configure the system clock to restrict the clock frequency and phaseof each node on a network within the preset tolerance scope. This prevents the deterioration ofthe TDM service quality caused by inaccurate signal timing at both the transmit and receive endsin the digital transmission system.

3.6 Configuring the System TimeThis topic describes the features of the IEEE 1588 V2 protocol and NTP protocol and how toconfigure the 1588 V2 time and NTP time on the MA5612.

3.7 Configuring the ACL for Packet FilteringThis topic describes the type, rule, and configuration of the ACL on the MA5612.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 3 Basic Configuration


3-1

3.8 Configuring QoSThis topic describes how to configure quality of service (QoS) on the MA5612.

3.9 Configuring Environment MonitoringThis topic provides concepts associated with environment monitoring and describes how toconfigure environment monitoring on the MA5612.

3 Basic ConfigurationSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

3.1 Configuring the Maintenance TerminalThis topic describes three modes of managing the MA5612 from the maintenance terminal.

3.1.1 Configuring Management Through a Local Serial PortThis topic describes how to connect the maintenance terminal to the MA5612 through a localserial port, log in to the MA5612, and then manage the MA5612 from the maintenance terminal.

3.1.2 Configuring Local Management (Through a Service Port)This topic describes how to configure an Ethernet access port for local maintenance andmanagement of the device, with the Ethernet port functioning as the local maintenance networkport.

3.1.3 Configuring Outband ManagementThis topic describes how to connect the MA5612 to the maintenance terminal through an outbandmanagement port, log in to the MA5612, and then manage the MA5612.

3.1.4 Configuring Inband Management (GPON Upstream)This topic describes how to log in to the MA5612 through an OLT from the maintenance terminalto manage the MA5612.

3.1.5 Configuring Inband Management (GE Upstream)This topic describes how to use Telnet to log in to the MA5612 through an upstream port (inbandmanagement port) of the MA5612 for inband management.

3.1.1 Configuring Management Through a Local Serial PortThis topic describes how to connect the maintenance terminal to the MA5612 through a localserial port, log in to the MA5612, and then manage the MA5612 from the maintenance terminal.

NetworkingFigure 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

MA5612

RS-232 serial port cable

PC

Configuration FlowchartFigure 3-2 shows the flowchart for configuring management through a local serial port.



3-3

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

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 CONSOLEport (maintenance serial port) on the control board of the MA5612, as shown in Figure 3-1.

Step 2 Start the HyperTerminal.1. Set up a connection.

Choose Start > Programs > Accessories > Communications > HyperTerminal on thePC. The Connection Description dialog box is displayed. Enter the connection name, asshown in Figure 3-3, and click OK.


Configuration Guide


Issue 04 (2011-04-27)

Figure 3-3 Setting up a connection

2. Set the serial port.

On the PC that is connected to the MA5612, select the number of the standard characterterminal or PC terminal serial port. You can select "COM1" or "COM2". 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 parametersare as follows:



3-5

l Baud rate: 9600 bit/sl Data bit: 8l Parity: Nonel Stop bit: 1l Flow control: None

NOTE

l The baud rate of the HyperTerminal must be the same as that of the serial port on the MA5612. Bydefault, the baud rate of the serial port on the MA5612 is 9600 bit/s.

l There may be illegible characters in the displayed input information after you log in to the system. Thisis because the baud rates between the HyperTerminal and the MA5612 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, 19200bit/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.


Configuration Guide


Issue 04 (2011-04-27)

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 defaultvalues for other parameters. Then, click OK, as shown in Figure 3-7.



3-7

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 Characterdelay to 20 ms, and use default values for other parameters. Click OK, as shown in Figure3-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 ofcharacters occurs. When the pasted text is displayed abnormally, modify the delay.


Configuration Guide


Issue 04 (2011-04-27)

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 username. Enter the user name and the password for user registration (by default, the super username is root and the password is mduadmin), and wait until the CLI prompt character isdisplayed. For instructions on CLI, see CLI Operation Characteristics.

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

3.1.2 Configuring Local Management (Through a Service Port)This topic describes how to configure an Ethernet access port for local maintenance andmanagement of the device, with the Ethernet port functioning as the local maintenance networkport.

Prerequisitel You must be logged in to the system through the local serial port. For the configuration

procedure, see 3.1.1 Configuring Management Through a Local Serial Port.

NOTE

In the following operations, the configuration on the MA5612 must be performed through the localserial port.

l The IP address of the operation console must be configured correctly; that is, the IP addressmust be in the same network segment as the IP address of the Ethernet access port.

l The Ethernet access port must be in the idle state.



3-9

Context

The MA5612 provides a maintenance port that functions both as a maintenance serial port anda maintenance network port. When this port is used as the maintenance network port for devicemanagement, use non-standard cable to connect ports.

To reduce the maintenance costs and manufacturing process by using the existing networkcables, configure the Ethernet access port as the local maintenance network port to maintain andmanage the device locally.

Networking

Figure 3-9 shows the network of configuring the local maintenance mode through the localmaintenance network port.

Figure 3-9 Example network for configuring the local maintenance mode through a localmaintenance network port

MA5612

Network Cable

PC

Procedure

Step 1 Run the vlan command to create a VLAN.huawei(config)#vlan 30 smart

Step 2 In the VLANIF mode, run the ip address command to configure the IP address and subnet maskof the VLAN L3 interface.huawei(config)#interface vlanif 30huawei(config-if-vlanif30)#ip address 10.10.20.2 255.255.255.0

Step 3 (Optional) Run the traffic table ip command to create the traffic profile according to therequirements. There are seven default traffic profiles in the system, with profile IDs of 0 to 6. Itis recommended that traffic profile 6 is used, which does not limit the traffic rate.

Step 4 Run the service-port command to create a service port.huawei(config)#service-port 1 vlan 30 eth 0/4/1 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6

NOTE

You can also use the created inband network management VLAN as the service port VLAN.

user-vlan must be set to untagged.

Step 5 Start Telnet on the maintenance terminal.

Choose Start > Run on the operation console. In the Open address bar, enter telnet10.10.20.2 (10.10.20.2 is the IP address of the Ethernet access port on the MA5612), as shownin Figure 3-10 (considering the Windows OS as an example). Click OK to run the Telnetapplication. Then, the remote login dialog box is displayed.


Configuration Guide


Issue 04 (2011-04-27)

Figure 3-10 Starting Telnet

Step 6 Log in to the MA5612.

On the telnet window, enter the user name and the password. By default, the super user name isroot and the password is mduadmin. When the login is successful, the system displays thefollowing information:

>>User name:root >>User password: Huawei Integrated Access Software (MA5612). Copyright(C) Huawei Technologies Co., Ltd. 2002-2010. All rights reserved.

----End

ResultAfter logging in to the system through the Ethernet access port, you can maintain and managethe MA5612. For instructions on performing operation through the CLI, see CLI OperationCharacteristics.

3.1.3 Configuring Outband ManagementThis topic describes how to connect the MA5612 to the maintenance terminal through an outbandmanagement port, log in to the MA5612, and then manage the MA5612.

Prerequisitel 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.l The IP address of the maintenance terminal must be properly configured.

NOTE

In the following operations, the configurations of the MA5612 must be performed through a local serialport.

Networking - LANFigure 3-11 shows an example network for configuring outband management over a LAN inthe telnet mode.



3-11

Figure 3-11 Example network for configuring outband management over a LAN in the telnetmode

MA5612

PC PC PC

LAN

In this example network, the IP address of the maintenance Ethernet port on the MA5612 andthe IP address of the console are in the same network segment. The maintenance Ethernet porton the MA5612 uses non-standard cable sequence and thereby users need to use a non-standardcable to connect the maintenance Ethernet port and the console for managing the MA5612 inoutband network management mode.

NOTE

For the method of making a non-standard cable, see Making a console-Ethernet integrated cable in theMaintenance Guide.

Data Plan - LANTable 3-1 provides the data plan for configuring outband management over a LAN in the telnetmode.

Table 3-1 Data plan for configuring outband management over a LAN in the telnet mode

Item Data

Maintenance Ethernet port of theMA5612

IP address: 10.10.20.2/24

Ethernet port of the maintenanceterminal

IP address: 10.10.20.3/24

Networking - WANFigure 3-12 shows an example network for configuring outband management over a WAN inthe telnet mode.


Configuration Guide


Issue 04 (2011-04-27)

Figure 3-12 Example network for configuring outband management over a WAN in the telnetmode

PC PC

PCLAN

Router

MA5612

In this configuration network, the MA5612 is connected to the WAN through its maintenancenetwork port by a non-standard cable. In this manner, engineers can maintain and manage theMA5612 remotely through the operation console.

NOTE

For the method of making a non-standard cable, see Making a console-Ethernet integrated cable in theMaintenance Guide.

Data Plan - WAN

Table 3-2 provides the data plan for configuring outband management over a WAN in the telnetmode.

Table 3-2 Data plan for configuring outband management over a WAN in the telnet mode

Item Data

Maintenance Ethernet port of theMA5612

IP address: 10.10.20.2/24

Ethernet port of the maintenanceterminal

IP address: 10.10.21.3/24

Port of the router connected to theMA5612

IP address: 10.10.20.254/24

Configuration Flowchart

Figure 3-13 shows the flowchart for outband management in the telnet mode.



3-13

Figure 3-13 Flowchart for outband management in the telnet mode

End

Start Telnet on the maintenance terminal

Set up the configuration environment


Start

Add a route

Is it a WAN environment?

Yes

No

Configure the IP address and subnet mask of the

maintenance port

Procedure

Step 1 Set up the configuration environment.

Figure 3-11 or Figure 3-12 shows how to set up the configuration environment according tothe actual requirements and conditions.

Step 2 In the meth mode, run the ip address command to configure the IP address and subnet mask ofthe maintenance Ethernet port of the MA5612.

NOTE

The default IP address of the maintenance Ethernet port is 10.11.104.2, and the subnet mask is255.255.255.0. You can configure the IP address of the maintenance Ethernet port based on the actualnetwork planning.

huawei(config)#interface meth 0huawei(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-11, you need not add a route.


Configuration Guide


Issue 04 (2011-04-27)

l If the remote WAN management environment is set up as shown in Figure 3-12, run the iproute-static command to add a route to the next hop.

huawei(config-if-meth0)#quithuawei(config)#ip route-static 10.10.21.0 24 10.10.20.254

Step 4 Start Telnet on the maintenance terminal.

Choose Start > Run on the maintenance terminal. In the Open address bar, enter telnet10.10.20.2 (10.10.20.2 is the IP address of the maintenance Ethernet port of the MA5612), asshown in Figure 3-14 (considering the Windows OS as an example). Click OK, and the telnetinterface is displayed.



On the telnet interface, enter the user name and the password. By default, the super user nameis root and the password is mduadmin. When the login is successful, the system displays thefollowing information:

>>User name:root >>User password: Huawei Integrated Access Software (MA5612). Copyright(C) Huawei Technologies Co., Ltd. 2002-2009. All rights reserved.

----End

ResultAfter logging in to the MA5612, you can manage the MA5612. For instructions on CLI, see CLIOperation Characteristics.

3.1.4 Configuring Inband Management (GPON Upstream)This topic describes how to log in to the MA5612 through an OLT from the maintenance terminalto manage the MA5612.

Prerequisitel The physical connection between the MA5612 and the OLT must be normal.



3-15

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

Networking - LAN

Figure 3-15 Example network for configuring inband management over a LAN in the GPONupstream mode

MA5612

PC PC

LAN

OLT

Networking - WAN

Figure 3-16 Example network for configuring inband management over a WAN in the GPONupstream mode

MA5612

PC PC

LAN

OLT

Router

Configuration FlowchartFigure 3-17 shows the flowchart for managing the MA5612 through an inband channel in theGPON upstream mode.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

In the GPON upstream mode, the MA5612 and the OLT are interconnected to implement inbandmanagement. All required configurations are performed on the OLT. This document provides only theflowchart for configuring the OLT. For the detailed configuration process, see the configuration guidecorresponding to the OLT.

Figure 3-17 Flowchart for configuring inband management in the GPON upstream mode

End


Start

Add a route


Yes

No

Configure the L3 interface of the OLT

Configure corresponding profiles

Adding an ONU

Configure the IP address of the ONU and the corresponding information

Use Telnet to log in to the ONU through the OLT or maintenance terminal

ResultAfter logging in to the MA5612 through the OLT or maintenance terminal, you can configurethe MA5612. For instructions on CLI, see CLI Operation Characteristics.



3-17

3.1.5 Configuring Inband Management (GE Upstream)This topic describes how to use Telnet to log in to the MA5612 through an upstream port (inbandmanagement port) of the MA5612 for inband management.

Prerequisitel 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.l The IP address of the maintenance terminal must be properly configured.

NOTE

In the following operations, the configurations of the MA5612 must be performed through a local serialport.

Networking - LANFigure 3-18 shows an example network for configuring inband management over a LAN in thetelnet mode.

Figure 3-18 Example network for configuring inband management over a LAN in the telnetmode

MA5612

PC

PC

PC

LAN

LAN Switch

Data Plan - LANTable 3-3 provides the data plan for configuring inband management over a LAN in the telnetmode.


Configuration Guide


Issue 04 (2011-04-27)

Table 3-3 Data plan for configuring inband management over a LAN in the telnet mode

Item Data

Upstream port of theMA5612

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

Ethernet port of themaintenance terminal

IP address: 10.10.20.3/24

Networking - WAN

Figure 3-19 shows an example network for configuring inband management over a WAN inthe telnet mode.

Figure 3-19 Example network for configuring inband management over a WAN in the telnetmode

PC PC

PCLAN

Router

MA5612

LAN Switch

Data Plan - WAN

Table 3-4 provides the data plan for configuring inband management over a WAN in the telnetmode.

Table 3-4 Data plan for configuring inband management over a WAN in the telnet mode

Item Data

Upstream port of theMA5612

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



3-19

Item Data

Ethernet port of themaintenance terminal

IP address: 10.10.21.3/24

Port of the LANswitch connected tothe router

IP address: 10.10.20.3/24

Configuration Flowchart

Figure 3-20 shows the flowchart for configuring inband management in the telnet mode.

Figure 3-20 Flowchart for configuring inband management in the telnet mode

End

Start Telnet on the maintenance terminal



Start

Add a route


Yes

No

Configure the IP address of the VLAN L3 interface

Procedure

Step 1 Set up the configuration environment.


Configuration Guide


Issue 04 (2011-04-27)

Figure 3-18 or Figure 3-19 shows how to set up the configuration environment according tothe 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 0

3. In the VLANIF mode, run the ip address command to configure the IP address and subnetmask of the VLAN L3 interface.huawei(config)#interface vlanif 30huawei(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-18, you need not add a route.

l If the remote WAN management environment is set up as shown in Figure 3-19, run the iproute-static command to add a route to the next hop.

huawei(config-if-vlanif30)#quithuawei(config)#ip route-static 10.10.21.0 24 10.10.20.3

Step 4 Start Telnet.

Choose Start > Run on the maintenance terminal. In the Open address bar, enter telnet10.10.20.2 (10.10.20.2 is the IP address of the VLAN L3 interface of the MA5612), as shownin Figure 3-21 (considering the Windows OS as an example). Click OK, and the telnet interfaceis displayed.



On the telnet interface, enter the user name and the password. By default, the super user nameis root and the password is mduadmin. When the login is successful, the system displays thefollowing information:

>>User name:root >>User password: Huawei Integrated Access Software (MA5612).



3-21

Copyright(C) Huawei Technologies Co., Ltd. 2002-2009. All rights reserved.

----End

ResultAfter logging in to the MA5612, you can manage the MA5612. For instructions on CLI, see CLIOperation Characteristics.

3.2 Configuring the NMSThe MA5612 can be interconnected with Huawei iManager U2000 (hereinafter referred to asU2000). Hence, the administrator can maintain and manage the device through the U2000. TheMA5612 can be interconnected with the U2000 in inband or outband networking mode. Thefollowing part describes how to configure the inband networking and outband networking basedon SNMP V1, SNMP V2c, and SNMP V3 respectively.

3.2.1 Configuring the NMS (Based on SNMP V1)When SNMP V1 is used, the MA5612 can be interconnected with the NMS in inband or outbandnetworking mode.

3.2.2 Configuring the NMS (Based on SNMP V2c)When SNMP V2c is used, the MA5612 can be interconnected with the NMS in inband or outbandnetworking mode.



Prerequisitel If the device is interconnected with the NMS in outband networking mode, the

communication port (maintenance network port) must be configured. For detailedprocedure, see 3.1.3 Configuring Outband Management.

l If the device is interconnected with the NMS through the PON upstream port in inbandnetworking mode, the communication port (PON upstream port) must be configured. Fordetailed procedure, see 3.1.4 Configuring Inband Management (GPON Upstream).

l If the device is interconnected with the NMS through the GE upstream port in inbandnetworking mode, the communication port (GE upstream port) must be configured. Fordetailed procedure, see 3.1.5 Configuring Inband Management (GE Upstream).

Networking - Inband Networking ModeAs shown in Figure 3-22, the SNMP protocol is transmitted through the service channel. Servicepackets and management packets are transmitted through the same channel. The inband NMSmanagement is implemented through the upstream port.

l The MA5612 supports the GPON/GE upstream port.


Configuration Guide


Issue 04 (2011-04-27)

l A static route is used between the MA5612 and the U2000.

Figure 3-22 Inband networking

Integrated NMS Center

NMS Client A

MA5612

U2000

OLT

Service channel and Management channelMA5612

Opitical splitter

NMS Client B

Networking - Outband Networking ModeAs shown in Figure 3-23, the SNMP protocol is transmitted through the management channel.Service packets and management packets are transmitted through different channels. Theoutband NMS management is implemented through the maintenance network port.

l The local maintenance Ethernet port on the MA5612 uses a non-standard cable.

NOTE

For the method of making a non-standard cable, see Making a console-Ethernet integrated cable inthe Maintenance Guide.




3-23

Figure 3-23 Outband networking

MA5612

U2000

LAN Switch

BRAS

10.50.1.10/24

10.50.1.1/24

10.10.1.10/24

Service channelManagement channel

Integrated NMS Center

NMS client BNMS client A

Configuration FlowchartFigure 3-24 shows the flowchart for configuring the NMS.

Figure 3-24 Flowchart for configuring the NMS

Set the SNMP parameters

Set the source address for traps sending

Save the data

Set the IP address of the target host for traps

Start

End

Enable trap sending

Flowchart for configuring the MXU


Configuration Guide


Issue 04 (2011-04-27)

Procedurel Configuration procedure on the device

1. Configure the SNMP parameters.

(1) Configure the community names and the access rights.Run the snmp-agent community command to configure the community namesand 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 thesame as those configured on the U2000.

huawei(config)#snmp-agent community read publichuawei(config)#snmp-agent community write private

(2) (Optional) Set the information about the administrator.Run the snmp-agent sys-info command to set the contact of the SNMP Agentadministrator and the physical position of the device.Contact of the administrator: HW-075528780808. Physical position of thedevice: Shenzhen_China.huawei(config)#snmp-agent sys-info contact HW-075528780808huawei(config)#snmp-agent sys-info location Shenzhen_China

(3) 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

NOTEThe 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 for sending traps to theNMS.

huawei(config)#snmp-agent trap enable standard

3. Configure the IP address of the target host of the traps.

Run the 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 IPaddress 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 ABChuawei(config)#snmp-agent target-host trap-paramsname ABC v1 securityname private

4. Configure the source IP address of the traps.

Run the snmp-agent trap source command to configure the source IP address of thetraps.

– In inband networking mode, the IP address of the upstream port is used as thesource IP address of the traps.

– In outband networking mode, the IP address of the maintenance network port isused as the source IP address of the traps.



3-25

NOTE

This document considers the outband networking mode as an example.huawei(config)#snmp-agent trap source meth 0

5. Save the data.

Run the save command to save the data.

huawei(config)#save

l Configuration procedure on the NMS

NOTE

In inband networking mode, you only need to perform the configuration on the MA5612. This stepcan be omitted because the MA5612 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 segment10.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 routingtable.

– 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 aroute.Run the route print command to query the information about the current routingtable.

NOTE

If the IP address of the outband NMS port and the IP address of the U2000 are in the samenetwork segment, you need not configure the route.

2. Log in to the U2000.3. Configure the SNMP parameters.

NOTE

A default SNMP profile exists in the system and is used in this example. If you need to configurea new profile, do as follows:

(1) Choose Administration > NE Communicate > Default Access ProtocolParameters from the main menu.

(2) In Default Access Protocol Parameters, click the SNMPv1 Parameters tab,and then click Add.

(3) Set the profile name, and then set other parameters according to the plan.

(4) Click OK. Then, the SNMP parameters are configured.4. Add a device.


Configuration Guide


Issue 04 (2011-04-27)

(1) Right-click in the main topology, and then choose New > NE from the shortcutmenu.

(2) In the dialog box that is displayed, set relevant parameters.

NOTE

l The IP address is the management IP address of the MA5612.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 profileaccording to the plan.

(3) Click OK. Several seconds to some 10 minutes are required for uploading thedevice data. After reading the related data, the system automatically updates thedevice icon.

----End

ResultYou can maintain and manage the MA5612 through the U2000.

Configuration FileThe following part provides the script for configuring the outband NMS (on the device).

snmp-agent community read publicsnmp-agent community write privatesnmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent sys-info version v1snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v1 securityname privatesnmp-agent trap source meth 0save

The following part provides the script for configuring the inband NMS (on the device). Themanagement VLAN ID of the upstream port is 30.snmp-agent community read publicsnmp-agent community write private



3-27

snmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent sys-info version v1snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v1 securityname private

snmp-agent trap source vlanif 30save

3.2.2 Configuring the NMS (Based on SNMP V2c)When SNMP V2c is used, the MA5612 can be interconnected with the NMS in inband or outbandnetworking mode.





Networking - Inband Networking ModeAs shown in the inband networking in 3.2.1 Configuring the NMS (Based on SNMP V1), theSNMP protocol is transmitted through the service channel. Service packets and managementpackets are transmitted through the same channel. The inband NMS management is implementedthrough the upstream port.

l The MA5612 supports GPON/GE upstream port.l A static route is used between the MA5612 and the U2000.

Networking - Outband Networking ModeAs shown in the outband networking in 3.2.1 Configuring the NMS (Based on SNMP V1),the SNMP protocol is transmitted through the management channel. Service packets andmanagement packets are transmitted through different channels. The outband NMS managementis implemented through the maintenance network port.


NOTE



Configuration FlowchartTo configure the NMS, see the flowchart for configuring the NMS in 3.2.1 Configuring theNMS (Based on SNMP V1).


Configuration Guide


Issue 04 (2011-04-27)



(1) Configure the community names and the access rights.Run the snmp-agent community command to configure the community namesand 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 thesame as those configured on the U2000.

huawei(config)#snmp-agent community read publichuawei(config)#snmp-agent community write private

(2) (Optional) Set the information about the administrator.Run the snmp-agent sys-info command to set the contact of the SNMP Agentadministrator and the physical position of the device.Contact of the administrator: HW-075528780808. Physical position of thedevice: Shenzhen_China.huawei(config)#snmp-agent sys-info contact HW-075528780808huawei(config)#snmp-agent sys-info location Shenzhen_China

(3) Set the SNMP version.Run the snmp-agent sys-info command to set the required SNMP version.huawei(config)#snmp-agent sys-info version v2c




huawei(config)#snmp-agent trap enable standard

3. Configure the IP address of the target host of the traps.

Run the 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 IPaddress 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-hostname huawei address 10.10.1.10 trap-paramsname ABChuawei(config)#snmp-agent target-host trap-paramsname ABC v2c securityname private







3-29

NOTE


5. Save the data.


huawei(config)#save

l Configuration procedure on the NMS

NOTE

In inband networking mode, you only need to perform the configuration on the MA5612. This stepcan be omitted because the MA5612 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.




NOTE



NOTE

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






Configuration Guide


Issue 04 (2011-04-27)



NOTE

l The IP address is the management IP address of the MA5612.

l Select the SNMP parameters based on the selected SNMP version. This sectionconsiders the SNMP V2c default profile as an example. You can select the profilecorresponds to the actual planning.

(3) Click OK. Several seconds to some 10 minutes are required for uploading thedevice data. After reading the related data, the system automatically updates thedevice icon.

----End



snmp-agent community read public

snmp-agent community write private

snmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent sys-info version v2c

snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v2c securityname private

snmp-agent trap source meth 0

save



3-31

The following part provides the script for configuring the inband NMS (on the device). Themanagement VLAN ID of the upstream port is 30.

snmp-agent community read public

snmp-agent community write private

snmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent sys-info version v2c

snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v2c securityname private

snmp-agent trap source vlanif 30save






Networking - Inband Networking Mode

As shown in the inband networking in 3.2.1 Configuring the NMS (Based on SNMP V1), theSNMP protocol is transmitted through the service channel. Service packets and managementpackets are transmitted through the same channel. The inband NMS management is implementedthrough the upstream port.

l The MA5612 supports GPON/GE upstream port.


Networking - Outband Networking Mode

As shown in the outband networking in 3.2.1 Configuring the NMS (Based on SNMP V1),the SNMP protocol is transmitted through the management channel. Service packets andmanagement packets are transmitted through different channels. The outband NMS managementis implemented through the maintenance network port.



Configuration Guide


Issue 04 (2011-04-27)

NOTE



Configuration FlowchartTo configure the NMS, see the flowchart for configuring the NMS in 3.2.1 Configuring theNMS (Based on SNMP V1).



(1) Configure the SNMP user, group, and view.The user name is user1, the group name is group1, the user authentication modeis MD5, the authentication password is authkey123, the user encryption mode isdes56, the encryption password is prikey123, the read and write view names arehardy, and the view includes the Internet subtree.huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5 authkey123 privacy-mode des56 prikey123huawei(config)#snmp-agent group v3 group1 privacy read-view hardy write-view hardyhuawei(config)#snmp-agent mib-view hardy include internet

(2) (Optional) Set the information about the administrator and the device.Run the snmp-agent sys-info command to set the contact of the SNMP Agentadministrator and the physical position of the device.Contact of the administrator: HW-075528780808. Physical position of thedevice: Shenzhen_China.huawei(config)#snmp-agent sys-info contact HW-075528780808huawei(config)#snmp-agent sys-info location Shenzhen_China

(3) (Optional) Configure the engine ID of the SNMP entity.Run the snmp-agent local-engineid command to configure the engine ID of theSNMP environment to 0123456789.

NOTEThe engine ID of the SNMP environment must be the same as that configured on theU2000.

huawei(config)#snmp-agent local-engineid 0123456789(4) Set the SNMP version.

Run the snmp-agent sys-info command to set the required SNMP version.huawei(config)#snmp-agent sys-info version v3




huawei(config)#snmp-agent trap enable standard3. Configure the IP address of the target host of the traps.



3-33

Run the snmp-agent target-host command to configure the IP address of the targethost of the traps.

The host name is huawei, the IP address of the host is 10.10.1.10 (that is, the IP addressof the U2000), the name of the target host is ABC, the SNMP version is V3, the securityname 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-hostname huawei address 10.10.1.10 trap-paramsname ABChuawei(config)#snmp-agent target-host trap-paramsname ABC v3 securityname user1 privacy





NOTE


5. Save the data.


huawei(config)#save

l Configuration procedure on the NMS1. Add a route from the NMS to the device.




NOTE





Configuration Guide


Issue 04 (2011-04-27)



(4) Select corresponding protocol type in Priv Protocol and Auth Protocol, and

then click behind the parameter. In the Password dialog box, set thepasswords for Priv Protocol and Auth Protocol. Then, click OK.

NOTE

NE User, Context Engine ID, Priv Protocol and the password, and Auth Protocol andthe password must be the same as those configured on the MA5612. The display snmp-agent usm-user command is used to query the device user, data encryption protocol, andauthentication protocol configured on the MA5612. The display snmp-agent local-engineid command is used to query the environment engine ID configured on theMA5612.






3-35

NOTE

l The IP address is the management IP address of the MA5612.

l Select the SNMP parameters based on the selected SNMP version. This sectionconsiders the SNMP V3: huawei profile as an example. You can select the profileaccording to the plan.

(3) Click OK. Several seconds to some 10 minutes are required for uploading thedevice data. After reading the related, the system automatically updates thedevice icon.

----End



snmp-agent usm-user v3 user1 group1 authentication-mode md5 authkey123 privacy-mode des56 prikey123snmp-agent group v3 group1 privacy read-view hardy write-view hardysnmp-agent mib-view hardy include internetsnmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent local-engineid 0123456789snmp-agent sys-info version v3snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v3 securityname user1 privacysnmp-agent trap source meth 0save

The following part provides the script for configuring the inband NMS (on the device). Themanagement VLAN ID of the upstream port is 30.

snmp-agent usm-user v3 user1 group1 authentication-mode md5 authkey123 privacy-mode


Configuration Guide


Issue 04 (2011-04-27)

des56 prikey123snmp-agent group v3 group1 privacy read-view hardy write-view hardysnmp-agent mib-view hardy include internetsnmp-agent sys-info contact HW-075528780808snmp-agent sys-info location Shenzhen_Chinasnmp-agent local-engineid 0123456789snmp-agent sys-info version v3snmp-agent trap enable standardsnmp-agent target-host trap-hostname huawei address 10.10.1.10 trap-paramsname ABCsnmp-agent target-host trap-paramsname ABC v3 securityname user1 privacysnmp-agent trap source vlanif 30save

3.3 Configuring the Attributes of the Upstream PortThe MA5612 can be interconnected with the OLT through upstream GPON/GE port. This topicdescribes how to configure the attributes of upstream GPON/GE port so that the devicecommunicates successfully with the upstream device.

3.3.1 Configuring the Attributes of the Upstream Ethernet PortThis topic describes how to configure the attributes of a specified Ethernet port so that the systemcommunicates with the upstream device in the normal state.

3.3.2 Configuring the Attributes of the Upstream PON PortThis topic describes how to query the statistics for the port, set the working mode of the opticaltransceiver, and set the alarm thresholds for the receive optical power of the optical transceiverthrough the upstream PON port.

3.3.1 Configuring the Attributes of the Upstream Ethernet PortThis topic describes how to configure the attributes of a specified Ethernet port so that the systemcommunicates with the upstream device in the normal state.

Prerequisite

If you configure the MA5612 in offline mode, the port attribute can be configured only after theport mode is configured through the port mode command.

Context

The MA5612 should be interconnected with the upstream device through the Ethernet port.Therefore, pay attention to the consistency of port attributes.

Default configuration

Table 3-5 lists the default settings of the attributes of an Ethernet port.

Table 3-5 Default settings of the attributes of an Ethernet port

Parameter Default Setting (Optical Port) Default Setting (ElectricalPort)

Auto-negotiationmode of the port

Disabled Enabled



3-37

Parameter Default Setting (Optical Port) Default Setting (ElectricalPort)

Port rate l FE optical port: 100 Mbit/sl GE optical port: 1000 Mbit/s

NANOTE

After the auto-negotiation modeof the port is disabled, you canconfigure the port rate.

Duplex mode Full-duplex NANOTE

After the auto-negotiation modeof the port is disabled, you canconfigure the duplex mode.

Network cableadaptation mode

Not supported l FE electrical port: autol GE electrical port: normal

Flow control Disabled Disabled

Procedurel Configure the physical attributes of an Ethernet port.

1. (Optional) Set the auto-negotiation mode of the Ethernet port.Run the auto-neg command to set the auto-negotiation mode of the Ethernet port. Youcan enable or disable the auto-negotiation mode:

– After the auto-negotiation mode is enabled, the port automatically negotiates withthe peer port for the rate and working mode of the Ethernet port.

– After the auto-negotiation mode is disabled, the rate and working mode of the portare in the forced mode (adopt default values or are set through command lines).

2. (Optional) Set the rate of the Ethernet port.Run the speed command to set the rate of the Ethernet port. After the port rate is setsuccessfully, the port works at the set rate. Pay attention to the following points:

– Make sure that the rate of the Ethernet port is the same as that of the interconnectedport on the peer device. This prevents communication failure.

– The auto-negotiation mode needs to be disabled.

3. (Optional) Configure the duplex mode of the Ethernet port.Run the duplex command to configure the duplex mode of the Ethernet port. Theduplex mode of an Ethernet port can be full-duplex, half-duplex, or auto negotiation.Pay attention to the following points:

– Make sure that the ports of two interconnected devices work in the same duplexmode. This prevents communication failure.

– The auto-negotiation mode should be disabled.

4. (Optional) Configure the network cable adaptation mode of the Ethernet port.Run the mdi command to configure the network cable adaptation mode of the Ethernetport to match the actual network cable. The network adaptation modes are as follows:


Configuration Guide


Issue 04 (2011-04-27)

– normal: Specifies the adaptation mode of the network cable as straight throughcable. In this case, the network cable connecting to the Ethernet port must be astraight-through cable.

– across: Specifies the adaptation mode of the network cable as crossover cable. Inthis case, the network cable connecting to the Ethernet port must be a crossovercable.

– auto: Specifies the adaptation mode of the network cable as auto-sensing. Thenetwork cable can be a straight through cable or crossover cable.

Pay attention to the following points:– The Ethernet optical port does not support the network cable adaptation mode.– If the Ethernet electrical port works in forced mode (auto-negotiation mode

disabled), the network cable type of the port cannot be configured to auto.l Run the flow-control command to enable the flow control on the Ethernet port.l Run the mirror port command to mirror the Ethernet port.

----End

Example

Assume that:

l The port rate is 1000 Mbit/s.l The duplex mode is adopted.l The flow control is supported.l The auto-negotiation mode is not supported.To configure the Ethernet port (optical port) of the MA5612, do as follows:

huawei(config)#interface eth 0/0huawei(config-if-eth-0/0)#auto-neg 1 disablehuawei(config-if-eth-0/0)#speed 1 1000huawei(config-if-eth-0/0)#duplex 1 fullhuawei(config-if-eth-0/0)#flow-control 1

3.3.2 Configuring the Attributes of the Upstream PON PortThis topic describes how to query the statistics for the port, set the working mode of the opticaltransceiver, and set the alarm thresholds for the receive optical power of the optical transceiverthrough the upstream PON port.

Prerequisite

If you configure the MA5612 in offline mode, the port attribute can be configured only after theport mode is configured through the port mode command.

Procedurel (Optional) Set the password for registering with the OLT.

Run the password command to set the registration password of the current device thatfunctions as a PON ONU.

l (Optional) Set the alarm thresholds for the receive optical power of the optical transceiver.



3-39

Run the optical-module threshold (in the GPONNNI mode ) command to set the alarmthresholds for the receive optical power of the optical transceiver. After the alarm thresholdsare set successfully, if the receive optical power of the optical transceiver is beyond theupper or lower threshold, the system immediately generates an alarm indicating that theoptical power is abnormal.

l (Optional) Set the working mode of the optical transceiver of the upstream PON port.

Run the laser (in the GPONNNI mode ) command to set the optical transceiver to active,always active, or disabled.

– When disabling the optical transceiver of the upstream PON port, ensure that theupstream PON port is not carrying any services.

– After setting the optical transceiver of the upstream PON port to always active, you cantest the upstream optical power.

l (Optional) Query the statistics for the port.

Run the display gpon-port statistic command to query the traffic information and linestatus of the GPON port.

----End

Example

To set the password for registering with the OLT through the GPON port, set the lower limit forthe receive optical power of the optical transceiver to 5 dBm and the upper limit for the receiveoptical power of the optical transceiver to 50 dBm, set the working mode of the opticaltransceiver of the upstream PON port to auto, do as follows:

huawei(config-if-gponnni-0/0/0)#password{ passwordvalue<S><Length 1-10> }:huawei

Command: password huaweihuawei(config-if-gponnni-0/0/0)#optical-module threshold rx-power lower-limit 5 upper-limit 50{ <cr>|bias<K>|temperature<K>|tx-power<K>|voltage<K> }:

Command: optical-module threshold rx-power lower-limit 5 upper-limit 50huawei(config-if-gponnni-0/0/0)#laser auto


Prerequisite

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 Table3-6.


Configuration Guide


Issue 04 (2011-04-27)

Table 3-6 VLAN application and planning

User Type Application Scenario VLAN Planning

l Householduser of theInternetaccessservice

l Commercialuser of theInternetaccessservice

N:1 scenario, that is, thescenario of upstreamtransmission through asingle VLAN, where theservices of multiplesubscribers areconverged to the sameVLAN.

VLAN type: smartVLAN attribute: commonVLAN forwarding mode: by VLAN+MAC

1:1 scenario, that is, thescenario of upstreamtransmission throughdouble VLANs, wherethe outer VLAN tagidentifies a service andthe inner VLAN tagidentifies a user. Theservice of each user isindicated by a unique S+C.

VLAN type: smartAttribute: stackingVLAN forwarding mode: by S+C

Commercialuser of thetransparenttransmissionservice

Applicable only to thetransparent transmissionservice of a commercialuser.

VLAN type: smartVLAN attribute: QinQVLAN forwarding mode: by VLAN+MAC orS+C.

Default ConfigurationTable 3-7 lists the default parameter settings of VLAN.

Table 3-7 Default parameter settings of VLAN

Parameter Default Setting Remarks

Default VLAN ofthe system

VLAN ID: 1Type: smart VLAN

-

Reserved VLANof the system

VLAN ID range:4079-4093

You can run the vlan reserve command tomodify the VLAN reserved by the system.

Default attributeof a new VLAN

Common -

VLANforwarding mode

VLAN+MAC -



3-41

Procedure

Step 1 Create a VLAN.

Run the vlan command to create a VLAN. VLANs of different types are applicable to differentscenarios.

Table 3-8 VLAN types and application scenarios

VLANType

ConfigurationCommand

VLAN Description Application Scenario

StandardVLAN

To add a standardVLAN, run the vlanvlanid standardcommand.

Standard VLAN.One standard VLANcontains multipleupstream ports. Ethernetports in one standardVLAN areinterconnected with eachother but Ethernet portsin different standardVLANs are isolated fromeach other.

Only available toEthernet ports andspecifically to networkmanagement andsubtending.

SmartVLAN

To add a smart VLAN,run the vlan vlanidsmart command.

One smart VLAN maycontain multipleupstream ports andservice ports. The serviceports in one smart VLANare isolated from eachother. The service ports indifferent VLANs are alsoisolated. One VLANprovides access formultiple users and thussaves VLAN resources.

Smart VLANs areapplicable to FE serviceaccess. For example,Smart VLANs can beused in residentialcommunities.

MUXVLAN

To add a MUX VLAN,run the vlan vlanidmux command.

One MUX VLAN maycontain multipleupstream ports but onlyone service port. Theservice ports in differentVLANs are isolated.One-to-one mapping canbe set up between a MUXVLAN and an accessuser. Hence, a MUXVLAN can identify anaccess user.

MUX VLANs areapplicable to FE serviceaccess. For example,MUX VLANs can beused to identify users.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

l To add VLANs with consecutive IDs in batches, run the vlan vlanid to end-vlanid command.

l To add VLANs with inconsecutive IDs in batches, run the vlan vlan-list command.

Step 2 (Optional) Configure the VLAN attribute.

The default attribute for a new VLAN is "common". You can run the vlan attrib command toconfigure the attribute of the VLAN.

Configure the attribute according to VLAN planning.

Table 3-9 VLAN attributes and application scenarios

VLANAttribute


VLAN Type VLANDescription

ApplicationScenario

Common

The defaultattribute for a newVLAN is"common".

The VLAN withthis attribute canbe a standardVLAN, smartVLAN, or MUXVLAN.

A VLAN with thecommon attributecan function as acommon layer 2VLAN or functionfor creating a layer3 interface.

Applicable to theN:1 accessscenario.

QinQVLAN

To configure QinQas the attribute of aVLAN, run thevlan attrib vlanidq-in-q command.

The VLAN withthis attribute canonly be a smartVLAN or a MUXVLAN.

The packets from aQinQ VLANcontain two VLANtags, that is, innerVLAN tag fromthe private networkand outer VLANtag from theMA5612. Throughthe outer VLAN,an L2 VPN tunnelcan be set up totransparentlytransmit theservices betweenprivate networks.

Applicable to theenterprise privateline scenario.



3-43

VLANAttribute



ApplicationScenario

VLANStacking

To configurestacking as theattribute of aVLAN, run thevlan attrib vlanidstackingcommand.


The packets from astacking VLANcontain two VLANtags, that is, innerVLAN tag andouter VLAN tagfrom the MA5612.The upper-layerBRASauthenticates theaccess usersaccording to thetwo VLAN tags. Inthis manner, thenumber of accessusers is increased.On the upper-layernetwork in the L2working mode, apacket can beforwarded directlyby the outer VLANtag and MACaddress mode toprovide thewholesale servicefor ISPs.

Applicable to the1:1 access scenariofor the wholesaleservice orextension ofVLAN IDs.In the case of astacking VLAN, toconfigure the tag ofthe service port,run the stackinglabel command.You can run thestacking outer-ethertypecommand to set thetype of outerEthernet protocolsupported byVLAN stacking onthe MA5612. Youcan also run thestacking inner-ethertypecommand to set thetype of innerEthernet protocolsupported byVLAN stacking.To ensure thatHuawei device isinterconnectedwith the device ofother vendors, thetype of inner/outerEthernet protocolmust be the same asthat of theinterconnectdevice.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

l To configure attributes for the VLANs with consecutive IDs in batches, run the vlan attrib vlanid to end-vlanid command.

l To configure attributes for the VLANs with inconsecutive IDs in batches, run the vlan attrib vlan-listcommand.

Step 3 (Optional) Configure VLAN description.

To configure VLAN description, run the vlan desc command. You can configure VLANdescription to facilitate maintenance. The general VLAN description includes the usage andservice information of the VLAN.

Step 4 (Optional) Configure the VLAN forwarding policy.

vlan-connect corresponds to the S+C forwarding policy, which ensures higher security bysolving the problems of insufficiency in the MAC address space, MAC address aging, and MACaddress spoofing and attacks.

To configure the VLAN forwarding policy in the VLAN service profile, do as follows:

1. Run the vlan service-profile command to create a VLAN service profile and enter theVLAN service profile mode.

2. Run the forwarding command to configure the VLAN forwarding policy. The defaultVLAN forwarding policy is VLAN+MAC in the system.

3. Run the commit command to validate the profile configuration. The configuration of theVLAN service profile takes effect only after execution of this command.

4. Run the quit command to quit the VLAN service profile mode.5. Run the vlan bind service-profile command to bind the VLAN to the VLAN service profile

created in 4.1.

----End

ExampleAssume that a stacking VLAN with ID of 50 is to be configured for extension of the VLAN. Aservice port is added to VLAN 50. The outer VLAN tag 50 of the stacking VLAN identifies theaccess device and the inner VLAN tag 10 identifies the user with access to the device. For theVLAN, description needs to be configured for easy maintenance. To configure such a VLAN,do as follows:

huawei(config)#vlan 50 smart huawei(config)#vlan attrib 50 stackinghuawei(config)#service-port vlan 50 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6 tx-cttr 5huawei(config)#stacking label vlan 50 baselabel 10 huawei(config)#vlan desc 50 description stackingvlan/label10

Assume that a QinQ VLAN with ID of 100 is to be configured for an enterprise user to ensurehigher security and the VLAN forwarding policy is S+C. For the VLAN, description needs tobe configured for easy maintenance. To configure such a VLAN, do as follows:

huawei(config)#vlan 100 smart huawei(config)#vlan attrib 100 q-in-q huawei(config)#vlan desc 100 description qinqvlan/forhuawei huawei(config)#vlan service-profile profile-id 1huawei(config-vlan-srvprof-1)#forwarding vlan-connec Info: Please use the commit command to make modifications take effecthuawei(config-vlan-srvprof-1)#commit



3-45

huawei(config-vlan-srvprof-1)#quithuawei(config)#vlan bind service-profile 100 profile-id 1

3.5 Configuring the System ClockThis topic describes how to configure the system clock to restrict the clock frequency and phaseof each node on a network within the preset tolerance scope. This prevents the deterioration ofthe TDM service quality caused by inaccurate signal timing at both the transmit and receive endsin the digital transmission system.

Contextl 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 thetraditional network to the IP-based Ethernet bearer network. One of the difficulties is howto carry the traditional TDM service on the IP network.

l On the traditional telecommunications network, the TDM service carried on the AN ismainly the voice service. Cumulative inconsistency between the clocks at both ends of thebearer network over a long time causes frame slip, which reduces the quality of the voiceservice. Moreover, the wireless application has more rigorous requirements on the clockfrequency. The frequencies of different base stations must be synchronized within aspecified precision. Otherwise, re-sync occurs during the base station switching. Therefore,clock synchronization is very important in the TDM voice service.

3.5.1 Configuring the Reference Source of the System ClockThis topic describes how to configure the clock reference sources so that the system clock canselect a reference source when needed.

3.5.2 Configuring the Priority of the System ClockThis topic describes how to configure the priority for the clock reference source of the system.The MA5612 selects the system clock according to the configured clock priorities.

3.5.1 Configuring the Reference Source of the System ClockThis topic describes how to configure the clock reference sources so that the system clock canselect a reference source when needed.

Contextl To ensure that the MA5612 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. Thesystem clock is also used as the system output clock.

l The system supports a maximum of ten clock reference sources. The system selects areference source according to the priority level of each reference source.

l The reference sources of the system clock include the 1588V2 clock and line clock.– The 1588V2 clock mainly applies to mobile bearer networks and meets the requirements

for high-precision clock and time transfer. The clock quality at the transfer frequencycan meet the requirements for a stratum-3 clock. The precision of the transfer time canreach the submicrosecond level.

– The line clocks supported by the system include the GE line clock, GPON line clock,and E1 line clock. That is, the system receives a line clock transferred by the upper-layer device through the GE/GPON uplink interface, or E1 interface, and restores the


Configuration Guide


Issue 04 (2011-04-27)

line clock as the reference source of the system clock, thus implementing clocksynchronization with the upper-layer device.

3.5.1.1 Configuring the Reference Source of the 1588V2 ClockThe MA5612 supports the IEEE 1588V2 protocol to implement clock and time synchronization.The 1588V2 clock is precise, and thus is commonly used by services, such as mobile bearingservices, that have high requirements for clock precision.

3.5.1.2 Configuring the Line Clock Reference SourceThe MA5612 supports tracing of the uplink GE, GPONor E1 line clock. The clock synchronizedthrough the physical layer and restored from the line code stream can serve as the referencesource of the system clock.

3.5.1.1 Configuring the Reference Source of the 1588V2 ClockThe MA5612 supports the IEEE 1588V2 protocol to implement clock and time synchronization.The 1588V2 clock is precise, and thus is commonly used by services, such as mobile bearingservices, that have high requirements for clock precision.

Contextl The full name of IEEE 1588 is IEEE Standard for a Precision Clock Synchronization

Protocol for Networked Measurement and Control Systems, and the short name is PrecisionTime Protocol (PTP). 1588 calculates time and frequency offset through informationtransmission between the master clock and the slave clocks to implement time andfrequency synchronization of the master clock and the slave clocks.

l When the device mode is Transparent Clock (TC), the device does not support the 1588V2clock as a reference source of the system clock.

Default ConfigurationTable 3-10 lists the default values of the 1588V2 clock reference source. When configuring the1588V2 clock reference source, you can change the values of the parameters according to theservice requirements.

Table 3-10 Default values of the 1588V2 clock reference source

Parameter Default Setting

enable no

Region ID 0

VLAN 0

Source IP Address 0.0.0.0

Port Status master

Message Type PTPETH

Packet Mode multicast

Announce-timeout 128ms

Request-interval 1/8s



3-47


Announce-interval 1/8s

Interval for Sending SYNC Packet 1/8s

Fiber Deviation 0

Fiber Transmission Deviation length

Fiber Deviation Direction positive

PE Mode E2E

Device Type OC

Procedure

Step 1 Run the ptp port enable command to enable the 1588V2 function on the port.

Step 2 Run the ptp port command to configure associated parameters of the 1588V2 protocol on theport.

The Domain, VLAN, state, address, packet-encap, and packet-mode parameters aremandatory.

l When the port status is master (that is, the port works as the master port in clocksynchronization), the announce-interval, announce-timeout, and sync-intervalparameters need to be configured.

l When the port status is slave (that is, the port works as the slave port in clock synchronization),the req-interval parameter needs to be configured.

Step 3 Run the display ptp port info command to check whether the information associated with the1588V2 protocol is consistent with the data plan.

Step 4 Run the ptp source command to configure the priority level of the 1588V2 clock source andreference source.

The system supports a maximum of 10 reference sources. The reference sources cannot beconfigured at a same port, and the priority levels of the sources must be different.

Step 5 Run the display ptp source command to check whether the 1588V2 clock source informationis consistent with the data plan.

Step 6 (Optional; perform this step when you need to modify the PE mode of the system.) Run the ptppemode command to configure the PE mode of the PTP.

The system supports two PE modes, namely, E2E and P2P. By default, the E2E mode is used.For the differences between the two modes, see Parameters and Usage Guidelines in ptppemode.

Step 7 (Optional; perform this step after you modify the PE mode of the system.) Run the display ptppemode command to check whether the PE mode of the PTP is consistent with the data plan.

Step 8 (Optional; perform this step when you need to modify the PTP device type in the system.) Runthe ptp device-type command to configure the PTP device type in the system.


Configuration Guide


Issue 04 (2011-04-27)

The system supports the following PTP device types: Ordinary Clock (OC), Boundary Clock(BC), Transparent Clock (TC), and Transparent Clock and Ordinary Clock (TCOC). By default,OC is used. For the differences between these four device types, see Parameters and UsageGuidelines in ptp device-type.

Step 9 (Optional; perform this step after you modify the PTP device type in the system.) Run the displayptp device-type command to check whether the PTP device type is consistent with the data plan.

Step 10 Run the clock source srcindex 1588 frameid/slotid/portid command to set the 1588V2 clock asthe reference source of the system clock.

srcindex can be different from the clock source index created through the ptp source command.frameid/slotid/portid must be consistent with the frameid/slotid/portid of the referenced 1588V2clock.

Step 11 Run the display clock source command to check whether the configured 1588V2 clock sourceis consistent with the data plan and whether the status of the clock is normal.

----End

Example

To configure the 1588V2 clock restored on the 0/0/0 port as the 1588V2 clock reference sourceof the system, with the clock reference source ID set to 1, 1588V2 clock ID set to 0, clock priorityset to p0 (highest priority), packet encapsulation format set to ptpip, non-symmetric fibertransmission deviation type set to length, fiber deviation direction set to positive, and deviationset to 10, and use default values of other parameters, do as follows:

huawei(config)#ptp port 0/0/0 enablehuawei(config)#ptp port 0/0/0 packet-encap ptpiphawei(config)#ptp port 0/0/0 line-warp length positive 10huawei(config)#ptp source 0 0/0/0 p0huawei(config)#clock source 1 1588 0/0/0

3.5.1.2 Configuring the Line Clock Reference Source

The MA5612 supports tracing of the uplink GE, GPONor E1 line clock. The clock synchronizedthrough the physical layer and restored from the line code stream can serve as the referencesource of the system clock.

Context

The MA5612 supports the GE, GPON and E1 line clocks as the reference sources of the systemclock.

Procedure

Step 1 Run the clock source srcindex frameid/slotid/portid command to configure the clock restoredat a certain GE, GPON, or E1 port as the reference source of the system clock.

Step 2 Run the display clock source command to check whether the line clock source information isconsistent with the data plan.

----End



3-49

ExampleTo configure clock source 0, set the reference source to the GPON line clock, and set thereference source port to 0/0/0, do as follows:

huawei(config)#clock source 0 0/0/0 Clock source set succeededhuawei(config)#display clock source ------------------------------------------------------------------------- Index config type source state ------------------------------------------------------------------------- 0 YES line 0/ 1/ 0 Failed 1 NO -- -/ -/ - --- 2 NO -- -/ -/ - --- 3 NO -- -/ -/ - --- 4 NO -- -/ -/ - --- 5 NO -- -/ -/ - --- 6 NO -- -/ -/ - --- 7 NO -- -/ -/ - --- 8 NO -- -/ -/ - --- 9 NO -- -/ -/ - --- ------------------------------------------------------------------------- The current system clock source index is 255

3.5.2 Configuring the Priority of the System ClockThis topic describes how to configure the priority for the clock reference source of the system.The MA5612 selects the system clock according to the configured clock priorities.

PrerequisiteThe system clock reference source must be configured.

Contextl The added system clock source can be used in the system only after it is configured with a

priority.l The priority of the clock source takes effect immediately after it is configured. This

operation, however, may cause the clock switching in the system.l 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.

Procedurel Run the clock priority command to configure the priority of the clock source.

The system supports 10 priorities for the clock reference source. The priorities arerepresented in the form of p0/p1/p2/p3/p4/p5/p6/p7/p8/p9, in which p0 indicates the highestpriority and p9 indicates the lowest priority. For example, if p0-p9 is set to 3/7/8, it indicatesthat the priority of the clock reference source with index 3 is the highest, the priority of thereference source with index 7 is lower, and the priority of the reference source with indexof 8 is the lowest.

----End

ExampleTo configure the priority of clock reference source 0 to the highest priority and the priority ofclock reference source 1 to the second highest priority, do as follows:


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#clock priority system 0/1 Clock source priority set succeeded

3.6 Configuring the System TimeThis topic describes the features of the IEEE 1588 V2 protocol and NTP protocol and how toconfigure the 1588 V2 time and NTP time on the MA5612.

3.6.1 Configuring the 1588V2-Based TimeThe MA5612 supports the IEEE 1588 V2 protocol to implement time synchronization betweennetwork devices.

3.6.2 Configuring the NTP TimeConfiguring the NTP protocol to keep the time of all devices in the network synchronized, sothat the Context implement various service applications based on universal time, such as thenetwork management system and the network accounting system.

3.6.1 Configuring the 1588V2-Based TimeThe MA5612 supports the IEEE 1588 V2 protocol to implement time synchronization betweennetwork devices.

ContextContext

The full name of IEEE 1588 is IEEE Standard for a Precision Clock Synchronization Protocolfor Networked Measurement and Control Systems, and the short name is Precision TimeProtocol (PTP). 1588 calculates time and frequency offset through information transmissionbetween the master clock and the slave clocks to implement time and frequency synchronizationof the master clock and the slave clocks.

Default Configuration

Table 3-11 lists the default values of the 1588V2-based time. When configuring the attributesof the PSTN user, you can modify the values according to the service requirements.

Table 3-11 Default values of the 1588V2 clock reference source


enable no

Region ID 0

VLAN 0

Source IP Address 0.0.0.0

Port Status master

Message Type PTPETH

Packet Mode multicast

Announce-timeout 128ms



3-51


Request-interval 1/8s

Announce-interval 1/8s

Interval for Sending SYNC Packet 1/8s

Fiber Deviation 0

Fiber Transmission Deviation length

Fiber Deviation Direction positive

PE Mode E2E

Device Type OC

Procedure

Step 1 Run the ptp port enable command to enable the 1588V2 function on the port.

Step 2 Run the ptp port command to configure associated parameters of the 1588V2 protocol on theport.

The Domain, VLAN, state, address, packet-encap, and packet-mode parameters aremandatory.

l When the port status is master (that is, the port works as the master port in clocksynchronization), the announce-interval, announce-timeout, and sync-intervalparameters need to be configured.

l When the port status is slave (that is, the port works as the slave port in clock synchronization),the req-interval parameter needs to be configured.

Step 3 Run the display ptp port info command to check whether the information associated with the1588V2 protocol is consistent with the data plan.

Step 4 Run the ptp source command to configure the priority level of the 1588V2 clock source andreference source.

The system supports a maximum of 10 reference sources. The reference sources cannot beconfigured at a same port, and the priority levels of the sources must be different.

Step 5 Run the display ptp source command to check whether the 1588V2 clock source informationis consistent with the data plan.

Step 6 (Optional; perform this step when you need to modify the PE mode of the system.) Run the ptppemode command to configure the PE mode of the PTP.

The system supports two PE modes, namely, E2E and P2P. By default, the E2E mode is used.For the differences between the two modes, see Parameters and Usage Guidelines in ptppemode.

Step 7 (Optional; perform this step after you modify the PE mode of the system.) Run the display ptppemode command to check whether the PE mode of the PTP is consistent with the data plan.


Configuration Guide


Issue 04 (2011-04-27)

Step 8 (Optional; perform this step when you need to modify the PTP device type in the system.) Runthe ptp device-type command to configure the PTP device type in the system.

The system supports the following PTP device types: Ordinary Clock (OC), Boundary Clock(BC), Transparent Clock (TC), and Transparent Clock and Ordinary Clock (TCOC). By default,OC is used. For the differences between these four device types, see Parameters and UsageGuidelines in ptp device-type.

Step 9 (Optional; perform this step after you modify the PTP device type in the system.) Run the displayptp device-type command to check whether the PTP device type is consistent with the data plan.

----End

Example

To configure the 1588V2-based clock, set the packet encapsulation format to ptpip, non-symmetric fiber transmission deviation type to length, fiber deviation direction to positive,deviation to 10, the protocol for output of the panel to NMEA.clock ID to 0, and clock priorityto p0 (highest priority), and use default values of other parameters, do as follows:

huawei(config)#ptp port 0/0/0 enablehuawei(config)#ptp port 0/0/0 packet-encap ptpipuawei(config)#ptp port 0/0/1 line-warp length positive 10huawei(config)#ptp source 0 0/0/0 p0huawei(config)#clock bits-type 0 time 1pps protocol NMEA

3.6.2 Configuring the NTP TimeConfiguring the NTP protocol to keep the time of all devices in the network synchronized, sothat the Context implement various service applications based on universal time, such as thenetwork 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. TheRFC defines the structures, arithmetics, entities and protocols used in the implementationof NTP.

l NTP is developed from the time protocol and the ICMP timestamp message protocol, withspecial design on the aspects of accuracy and robustness.

l NTP runs over UDP with port number as 123.l 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 canbe done through NTP packets exchanges.

NTP is applied to the following situations where all the clocks of hosts or routers in a networkneed to be consistent:l In the network management, an analysis of log or debugging information collected from

different routers needs time for reference.l The charging system requires the clocks of all devices to be consistent.l Completing certain functions, for example, timing restart of all the routers in a network

requires the clocks of all the routers be consistent.



3-53

l When several systems work together on the same complicate event, they have to take thesame clock for reference to ensure correct implementation order.

l Incremental backup between the backup server and clients requires clocks on them besynchronized.

When all the devices on a network need to be synchronized, it is almost impossible for anadministrator to manually change the system clock by command line. This is because the workload is heavy and clock accuracy cannot be ensured. NTP can quickly synchronize the clocksof network devices and ensure their precision.

There are four NTP modes: broadcast mode, multicast mode, unicast server mode, and peermode. The MA5612 supports all these modes.

Default ConfigurationTable 3-12 provides the default configuration for NTP.

Table 3-12 Default configuration for NTP

Parameter Default Value

NTP-service authenticationfunction

Disable

NTP-service authenticationkey

None

The maximum allowednumber of sessions

100

Clock stratum 16

3.6.2.1 (Optional) Configuring NTP AuthenticationThis topic describes how to configure NTP authentication. After NTP authentication isconfigured, the function can be enabled in the network that has high requirements on securityto improve the network security and prevent unauthorized users from modifying the clock.

3.6.2.2 Configuring the NTP Broadcast ModeThis topic describes how to configure the MA5612 for clock synchronization in the NTPbroadcast mode. After the configuration is complete, the server periodically broadcasts clocksynchronization packets through a specified port, and functions as a client to snoop on thebroadcast packets sent from the server and synchronizes the local clock according to the receivedbroadcast packets.

3.6.2.3 Configuring the NTP Multicast ModeThis topic describes how to configure the MA5612 for clock synchronization in the NTPmulticast mode. After the configuration is complete, the server periodically multicasts clocksynchronization packets through a specified port, and functions as a client to listen to themulticast packets sent from the server and synchronizes the local clock according to the receivedmulticast packets.

3.6.2.4 Configuring the NTP Unicast Server ModeThis topic describes how to configure the MA5612 as the NTP client to synchronize with theNTP server in the network.


Configuration Guide


Issue 04 (2011-04-27)

3.6.2.5 Configuring the NTP Peer ModeThis topic describes how to configure the MA5612 for clock synchronization in the NTP peermode. In the peer mode, configure only the active peer, and the passive peer need not beconfigured. In the peer mode, the active peer and the passive peer can synchronize with eachother. The peer with a higher clock stratum is synchronized by the peer with a lower clockstratum.

3.6.2.1 (Optional) Configuring NTP Authentication

This topic describes how to configure NTP authentication. After NTP authentication isconfigured, the function can be enabled in the network that has high requirements on securityto improve the network security and prevent unauthorized users from modifying the clock.

Prerequisite

Before configuring the NTP authentication, make sure that the network interface and the routingprotocol of the MA5612 are configured so that the server and the client are reachable to eachother at the network layer.

Context

In certain networks that have strict requirements on security, enable NTP authentication whenrunning the NTP protocol. Configuring NTP authentication is classified into configuring NTPauthentication on the client and configuring NTP authentication on the server.

Precautionl 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.

l If NTP authentication is enabled, a reliable key should be configured.

l The configuration of the server must be the same as that of the client.

l When NTP authentication is enabled on the client, the client can pass the authentication ifthe server is configured with the same key as that of the client. In this case, you need notenable NTP authentication on the server or declare that the key is reliable.

l The client synchronizes with only the server that provides the reliable key. If the keyprovided by the server is unreliable, the client does not synchronize with the server.

l The flow of configuring NTP authentication is as follows: start->enable NTPauthentication->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



3-55

Example

To enable NTP authentication, set the NTP authentication key as aNiceKey with the key number42, and then define key 42 as a reliable key, do as follows:

huawei(config)#ntp-service authentication enablehuawei(config)#ntp-service authentication-keyid 42 authentication-mode md5 aNiceKeyhuawei(config)#ntp-service reliable authentication-keyid 42

3.6.2.2 Configuring the NTP Broadcast Mode

This topic describes how to configure the MA5612 for clock synchronization in the NTPbroadcast mode. After the configuration is complete, the server periodically broadcasts clocksynchronization packets through a specified port, and functions as a client to snoop on thebroadcast packets sent from the server and synchronizes the local clock according to the receivedbroadcast packets.

PrerequisiteBefore configuring the NTP broadcast mode, make sure that the network interface and the routingprotocol of the MA5612 are configured so that the server and the client are reachable to eachother at the network layer.

Context

In the broadcast mode, the server periodically sends clock synchronization packets to thebroadcast 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 firstbroadcast 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 theclient and the server. The client then enters the broadcast client mode, continues to snoop on theincoming broadcast packets, and synchronizes the local clock according to the incomingbroadcast packets, as shown in Figure 3-25.

Figure 3-25 NTP broadcast mode


Configuration Guide


Issue 04 (2011-04-27)

Precaution1. 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.

Procedurel Configure the NTP broadcast client host.

1. (Optional) Configure NTP authentication.In certain networks that have strict requirements on security, it is recommended thatyou enable NTP authentication when running the NTP protocol. The configuration ofthe server must be the same as that of the client.

(1) Run the ntp-service authentication enable command to enable NTPauthentication.

(2) Run the ntp-service authentication-keyid command to set an NTPauthentication key.

(3) Run the ntp-service reliable authentication-keyid command to declare that thekey is reliable.

2. Add a VLAN L3 interface.

(1) Run the vlan command to create a VLAN.(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 theupstream port.

(3) In the global config mode, run the interface vlan command to create a VLANinterface, 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 theVLAN interface so that the IP packets in the VLAN can participate in the L3forwarding.

3. Run the ntp-service broadcast-client command to configure the host as the NTPbroadcast client.

----End

ExampleAssume the following configurations: MA5612 functions as the NTP client, snooping on thebroadcast packets sent from the server through IP address 10.10.10.20/24 of the L3 interface ofVLAN 2 and synchronizing the local clock with the clock on the broadcast server. To performthese configurations, do as follows:huawei(config)#vlan 2 standardhuawei(config)#port vlan 2 0/0 0huawei(config)#interface vlanif 2huawei(config-if-vlanif2)#ip address 10.10.10.20 24huawei(config-if-vlanif2)#ntp-service broadcast-clienthuawei(config-if-vlanif2)#quit

3.6.2.3 Configuring the NTP Multicast ModeThis topic describes how to configure the MA5612 for clock synchronization in the NTPmulticast mode. After the configuration is complete, the server periodically multicasts clocksynchronization packets through a specified port, and functions as a client to listen to the



3-57

multicast packets sent from the server and synchronizes the local clock according to the receivedmulticast packets.

PrerequisiteBefore configuring the NTP multicast mode, make sure that the network interface and the routingprotocol of the MA5612 are configured so that the server and the client are reachable to eachother at the network layer.

ContextIn the multicast mode, the server periodically sends clock synchronization packets to themulticast address configured by the user. The default NTP multicast address 224.0.1.1 is usedif the multicast address is not configured. The Mode field of clock synchronization packet is setto 5 (multicast mode). The client listens to the multicast packets sent from the server. Afterreceiving the first multicast packet, the client exchanges NTP packet whose mode fields are setto 3 (client mode) and 4 (server mode) with the server to estimate the network delay betweenthe client and the server. The client then enters the multicast client mode, continues to listen tothe incoming multicast packets, and synchronizes the local clock according to the incomingmulticast packets, as shown in Figure 3-26.

Figure 3-26 NTP multicast mode

Precaution1. 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


Procedurel Configure the NTP multicast client host.

1. (Optional) Configure NTP authentication.In certain networks that have strict requirements on security, it is recommended thatyou enable NTP authentication when running the NTP protocol. The configuration ofthe server must be the same as that of the client.


Configuration Guide


Issue 04 (2011-04-27)

(1) Run the ntp-service authentication enable command to enable NTPauthentication.

(2) Run the ntp-service authentication-keyid command to set an NTPauthentication key.

(3) Run the ntp-service reliable authentication-keyid command to declare that thekey is reliable.

2. Add a VLAN L3 interface.

(1) Run the vlan command to create a VLAN.(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 theupstream port.

(3) In the global config mode, run the interface vlan command to create a VLANinterface, 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 theVLAN interface so that the IP packets in the VLAN can participate in the L3forwarding.

3. Run the ntp-service multicast-client command to configure the host as the NTPmulticast client.

----End

ExampleAssume the following configurations: MA5612 functions as the NTP client, listening to themulticast packets sent from the server through IP address 10.10.10.20/24 of the L3 interface ofVLAN 2 and synchronizing the local clock with the clock on the multicast server. To performthese configurations, do as follows:huawei(config)#vlan 2 standardhuawei(config)#port vlan 2 0/0 0huawei(config)#interface vlanif 2huawei(config-if-vlanif2)#ip address 10.10.10.20 24huawei(config-if-vlanif2)#ntp-service multicast-clienthuawei(config-if-vlanif2)#quit

3.6.2.4 Configuring the NTP Unicast Server ModeThis topic describes how to configure the MA5612 as the NTP client to synchronize with theNTP server in the network.

PrerequisiteBefore configuring the NTP client/server mode, make sure that the network interface and therouting protocol of the MA5612 are configured so that the server and the client are reachable toeach other at the network layer.

ContextIn the client/server mode, the client sends a synchronization packet to the server, with the modefield set to 3 (client mode). After receiving the packet, the server automatically enters the servermode and sends a response packet with the mode field set to 4 (server mode). After receivingthe response from the server, the client filters and selects the clock, and synchronizes with thepreferred server, as shown in Figure 3-27.



3-59

Figure 3-27 NTP client/server mode

Precaution1. 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. Run the vlan command to create a VLAN.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 vlan 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, andspecify the IP address of the remote server that functions as the local timer server and the interfacefor 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 theNTP 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 When the clock stratum of the server is higher than or equal to that of the client, the client does notsynchronize with the server.

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 isallowed to access the L3 interface. Other unauthorized packets are not allowed to access the L3


Configuration Guide


Issue 04 (2011-04-27)

interface. It is recommended to use the ACL rules for the system that has high requirements onsecurity.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 orforbidding 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, andmake the configuration take effect.

----End

ExampleAssume the following configurations: The IP address of the NTP server is 10.20.20.20/24,MA5612 (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 requestpacket through the VLAN L3 interface to the NTP server, the NTP server responds to the requestpacket, and ACL rules are configured to allow only IP packets from the clock server to accessthe L3 interface. To perform these configurations, do as follows:huawei(config)#vlan 2 standardhuawei(config)#port vlan 2 0/0 0huawei(config)#interface vlanif 2huawei(config-if-vlanif2)#ip address 10.10.10.10 24huawei(config-if-vlanif2)#quithuawei(config)#ntp-service unicast-server 10.20.20.20 source-interface vlanif 2huawei(config)#acl 3010huawei(config-acl-adv-3010)#rule deny ip source any destination 10.10.10.10 0.0.0.0huawei(config-acl-adv-3010)#rule permit ip source 10.20.20.20 0.0.0.0 destination 10.10.10.10 0.0.0.0huawei(config-acl-adv-3010)#quithuawei(config)#packet-filter inbound ip-group 3010 port 0/0/0

3.6.2.5 Configuring the NTP Peer ModeThis topic describes how to configure the MA5612 for clock synchronization in the NTP peermode. In the peer mode, configure only the active peer, and the passive peer need not beconfigured. In the peer mode, the active peer and the passive peer can synchronize with eachother. The peer with a higher clock stratum is synchronized by the peer with a lower clockstratum.

PrerequisiteBefore configuring the NTP peer mode, make sure that the network interface and the routingprotocol of the MA5612 are configured so that the server and the client are reachable to eachother at the network layer.

ContextIn the peer mode, the active peer and the passive peer exchange NTP packets whose mode fieldsare set to 3 (client mode) and 4 (server mode). Then, the active peer sends a clock synchronizationpacket to the passive peer, with the mode field of the packet set to 1 (active peer). After receivingthe packet, the passive peer automatically works in the passive mode and sends a response packetwith 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 theactive peer and that of the passive peer are synchronized, the clock on a lower stratum is used,as shown in Figure 3-28.



3-61

Figure 3-28 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 interfacefor transmitting and receiving NTP packets.

NOTE

l In this command, ip-address is a unicast address, which cannot be a broadcast address, a multicastaddress, 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 addressof the NTP packets is configured as the primary IP address of the specified interface.

Step 2 Add a VLAN L3 interface.

1. Run the vlan command to create a VLAN.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 vlan 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


Configuration Guide


Issue 04 (2011-04-27)

ExampleAssume the following configurations: One MA5612 functions as the NTP active peer (IP addressof the L3 interface of VLAN 2: 10.10.10.10/24) and works on clock stratum 4, the otherMA5612 (IP address: 10.10.10.20/24) functions as the NTP passive peer, the active peer sendsa clock synchronization request packet through the VLAN L3 interface to the passive peer, thepassive peer responds to the request packet, and the peer with a higher clock stratum issynchronized by the peer with a lower clock stratum. To perform these configurations, do asfollows:huawei(config)#ntp-service refclock-master 4huawei(config)#ntp-service unicast-peerhuawei(config)#vlan 2 standardhuawei(config)#port vlan 2 0/0 0huawei(config)#interface vlanif 2huawei(config-if-vlanif2)#ip address 10.10.10.10 24huawei(config-if-vlanif2)#quit

3.7 Configuring the ACL for Packet FilteringThis topic describes the type, rule, and configuration of the ACL on the MA5612.

Context

An access control list (ACL) is used to filter certain packets by a series of preset rules. In thismanner, the objects that need to be filtered can be identified. After the specific objects areidentified, the corresponding data packets are permitted to pass or prohibited from passingaccording to the preset policy. The ACL-based traffic filtering process is a prerequisite forconfiguring the QoS or user security.

Table 3-13 lists the ACL types.

Table 3-13 ACL types

Type ValueRange

Feature

Basic ACL 2000-2999 The rules of a standard ACL are only defined accordingto the L3 source IP address for analyzing and processingdata packets.

Advanced ACL 3000-3999 The rules of an advanced ACL are defined according tothe source IP address, destination IP address, type of theprotocol over IP, and features of the protocol (includingTCP source port, TCP destination port, and ICMPmessage type).Compared with the basic ACL, the advanced ACLcontains more accurate, abundant, and flexible rules.

Link layer ACL 4000-4999 A link-layer ACL allows definition of rules according tothe link-layer information such as the source MACaddress, VLAN ID, link-layer protocol type, anddestination MAC address, and the data is processedaccordingly.



3-63

Type ValueRange

Feature

User-definedACL

5000-5999 The rules of a user-defined ACL are defined according toany 32 bytes of the first 80 bytes in the L2 data frame foranalyzing and processing data packets.

When a packet reaches the port and matches two or more ACL rules, the matching sequence isas follows:l If the rules of an ACL are activated at the same time, the rule configured earlier has priority

over the one configured later.l If the rules of an ACL are activated one by one, the rule activated later has priority over

the one activated earlier.l If the rules are issued to the port from different ACLs, the rule activated later has priority

over the one activated earlier.

PrecautionBecause the ACL is flexible in use, Huawei provides the following suggestions on itsconfiguration:l 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 theunspecified packet.

l The activated ACL rules share the hardware resources with the protocol modules (such asDHCP module and IPoA module) . In this case, the hardware resources are limited and maybe insufficient. To prevent the failure of enabling other service functions due to insufficienthardware resources, it is recommended you enable the protocol module first and thenactivate ACL rules in the data configuration. If you fail to enable a protocol module, performthe 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 protocolmodule.

3.7.1 Configuring the Basic ACL for Packet FilteringThis topic is applicable to the scenario where the device needs to classify traffic for packetsaccording to the source IP address.

3.7.2 Configuring the Advanced ACL for Packet FilteringThis 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 ofthe TCP, destination port of the TCP, and ICMP type of the data packets.

3.7.3 Configuring the Link Layer ACL for Packet FilteringThis topic describes how to classify traffic according to the link layer information such as sourceMAC address, source VLAN ID, L2 protocol type, and destination MAC address.


Configuration Guide


Issue 04 (2011-04-27)

3.7.1 Configuring the Basic ACL for Packet FilteringThis topic is applicable to the scenario where the device needs to classify traffic for packetsaccording to the source IP address.

ContextThe 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 processingdata packets.

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 iscreated.

Step 2 Create a basic ACL.Run the acl command to create a basic ACL, and then enter the ACL mode. The number of abasic ACL can only be in the range of 2000-2999.

Step 3 Configure a basic ACL rule.In the acl-basic mode, run the rule command to create a basic ACL rule. The parameters are asfollows: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 needto 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

ExampleTo configure that from 00:00 to 12:00 on Fridays, port 0/1/0 on the 0/4/1 receives only thepackets 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 frihuawei(config)#acl 2000huawei(config-acl-basic-2000)#rule permit source 2.2.2.2 0.0.0.0 time-range time1huawei(config-acl-basic-2000)#rule deny time-range time1huawei(config-acl-basic-2000)#quithuawei(config)#packet-filter inbound ip-group 2000 port 0/4/1huawei(config)#save



3-65

3.7.2 Configuring the Advanced ACL for Packet FilteringThis 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 ofthe TCP, destination port of the TCP, and ICMP type of the data packets.

ContextThe 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 typel Source IP addressl Destination IP addressl Source port ID (source port of the UDP or TCP packets)l Destination port ID (destination port of the UDP or TCP packets)l ICMP packet typel Precedence value: priority field of the data packetl Type of service (ToS) value: ToS field of the data packetl Differentiated services code point (DSCP) value: DSCP of the data packet

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 iscreated.

Step 2 Create an advanced ACL.Run the acl command to create an advanced ACL, and then enter the acl-adv mode. The numberof 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 mode, run the rule command to create an 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


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 rules are

effective.

Step 4 Activate the ACL.After an ACL is configured, only an ACL is generated and the ACL does not take effect. Youneed 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 3.8.4 Configuring Traffic Management Based

on ACL Rules.

----End


Configuration Guide


Issue 04 (2011-04-27)

ExampleAssume that the service board of the MA5612 resides in slot 1 and belongs to a VLAN, and theIP address of the VLAN L3 interface is 10.10.10.101. To prohibit the ICMP (such as ping) andtelnet operations from the user side to the VLAN interface on the device, do as follows:huawei(config)#acl 3001huawei(config-acl-adv-3001)rule 1 deny icmp destination 10.10.10.101 0huawei(config-acl-adv-3001)rule 2 deny tcp destination 10.10.10.101 0 destination-port eq telnet huawei(config-acl-adv-3001)quithuawei(config)#packet-filter inbound ip-group 3001 rule 1 port 0/1/0huawei(config)#packet-filter inbound ip-group 3001 rule 2 port 0/1/0huawei(config)#save

3.7.3 Configuring the Link Layer ACL for Packet FilteringThis topic describes how to classify traffic according to the link layer information such as sourceMAC address, source VLAN ID, L2 protocol type, and destination MAC address.

ContextThe 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 Ethernetl 802.1p priorityl VLAN IDl Source MAC addressl Destination MAC address

ProcedureStep 1 (Optional) Set a time range.

Run the time-range command to create a time range, which can be used when an ACL rule iscreated.

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 numberof 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 areas follows:l rule-id: Indicates the ACL rule ID. To create an ACL rule with a specified ID, use this


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 is effective.

Step 4 Activate the ACL.After an ACL is configured, only an ACL is generated and the ACL does not take effect. Youneed to run other commands to activate the ACL. Some common commands are as follows:



3-67

l Run the packet-filter command to activate an ACL.l Perform the QoS operation. For details, see 3.8.4 Configuring Traffic Management Based

on ACL Rules.

----End

ExampleTo 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 destinationMAC address 00e0-fc11-4141 to pass, do as follows:huawei(config)#acl 4001huawei(config-acl-link-4001)rule 1 permit type 0x8863 cos 1 source 122222-2222-2222 0000-0000-0000 destination 00e0-fc11-4141 0000-0000-0000huawei(config-acl-basic-4001)quithuawei(config)#save

3.8 Configuring QoSThis topic describes how to configure quality of service (QoS) on the MA5612.

ContextConfiguring 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 networkwideservices before making the configuration solution.

On the MA5612, 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.l Queue scheduling

For the service packets that are already configured with traffic management, through theconfiguration of queue scheduling, the service packets can be placed into queues withdifferent priorities, thus implementing QoS inside the system.

In addition to the preceding key points, the MA5612 supports ACL-based traffic management.

ACL-based traffic managementIn the scenario where users have flexible requirements onimplementing QoS for traffic streams, the ACL can be used to implement flexible trafficclassification (see 3.7 Configuring the ACL for Packet Filtering), and then QoS can beimplemented for traffic streams.

3.8.1 Configuring Traffic ManagementThis topic describes how to configure traffic management on the MA5612.

3.8.2 Configuring Queue SchedulingThis topic describes how to configure the queue scheduling so that the services with differentpriorities have different scheduling policies. Then, the corresponding QoS of these services canbe ensured.

3.8.3 Configuring Early DropThis topic describes how to configure early drop, which is applicable to the dropping policysettings for the packets in the queue.

3.8.4 Configuring Traffic Management Based on ACL Rules


Configuration Guide


Issue 04 (2011-04-27)

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 trafficstreams.

3.8.1 Configuring Traffic ManagementThis topic describes how to configure traffic management on the MA5612.

OverviewThe MA5612 supports traffic management for the inbound and outbound traffic streams of thesystem.

NOTEFor details on configuring traffic classification, see 5.3 Creating the Ethernet Access Service Port.

In addition, the MA5612 supports rate limit on the Ethernet port and traffic suppression oninbound broadcast packets and unknown (multicast or unicast) packets.

3.8.1.1 Configuring Traffic Management Based on Service PortThis topic describes how to configure traffic management based on service port. Whenconfiguring a service port, you need to bind an IP traffic profile to the service port and managethe traffic of the service port through the traffic parameters defined in the profile.

3.8.1.2 Configuring Rate Limitation on an Ethernet PortThis topic describes how to configure upstream rate limitation on a specified Ethernet port.

3.8.1.3 Configuring User-based Rate LimitationIn the user-based rate limitation, the voice service, IPTV service, and Internet access service ofeach user share a total user bandwidth. When there is no one of the three services, the other twoservices can hold a burst of the total user bandwidth so that the total user bandwidth can bemanaged in a unified manner.

3.8.1.4 Configuring Traffic SuppressionThis topic describes how to configure traffic suppression. The purpose of traffic suppression isto ensure the provisioning of the normal service of system users by suppressing the broadcast,unknown multicast, and unknown unicast packets received by the system.

3.8.1.1 Configuring Traffic Management Based on Service PortThis topic describes how to configure traffic management based on service port. Whenconfiguring a service port, you need to bind an IP traffic profile to the service port and managethe traffic of the service port through the traffic parameters defined in the profile.

ContextTraffic management based on service port is implemented by creating an IP traffic profile andthen binding the IP traffic profile when creating the service port.

l The system has seven default IP traffic profiles with the IDs of 0–6. You can run the displaytraffic table ip command to query the traffic parameters of the default traffic profiles.

l It is recommended that you use the default traffic profiles. A new IP traffic profile is createdonly when the default traffic profiles cannot meet the requirements.

Table 3-14 lists the traffic parameters defined in the IP traffic profiles.



3-69

Table 3-14 Traffic parameters defined in the IP traffic profiles

Item Parameter Description

Parameters of tworate three colormanagement

CIR: committed information rateCBS: committed burst sizePIR: peak information ratePBS: peak burst sizeNOTEl CIR is mandatory, and the other three parameters are optional. If you

configure only CIR, the system calculates the other three parameters basedon the formula. It is recommended that you configure only CIR.

l The system marks the service packets with colors according to the fourparameters. The red packet is discarded directly, and the packets of the othertwo colors are marked on their DEI field in the VLAN tag, the yellow colorindicated 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 upstreampacket.

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 theupstream packet.

l user-tos: Copy the ToS priority in the VLAN tag of the packet to the802.1p priority in the VLAN tag of the upstream packet.

Schedulingpolicies

There are two types of scheduling policies, which are available only tothe 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 trafficprofile bound to the traffic stream.

NOTEUpstream in this document refers to the direction from the user side to the network side, and downstreamrefers 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 inthe 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 byspecifying the profile ID. If the existing traffic profiles do not meet the requirements, create anIP traffic profile.

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


Configuration Guide


Issue 04 (2011-04-27)

For the usage and parameters of this command, see the description in the Command Referencein 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 0–7 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 rangeof 0–7). If the user-side packet does not carry a priority, the specified default 802.1ppriority of the packet is adopted as the priority of the outbound packet.

l (Optional) Enter keyword inner-priority to set the inner 802.1p priority (the 802.1p priorityin the CTag) of the packet. Two options are available for setting the priority policy:– Enter a value in the range of 0–7 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 rangeof 0–7). If the user-side packet does not carry a priority, the specified default 802.1ppriority of the packet is adopted as the priority of the outbound packet.

l Keyword priority-policy must be entered to specify a scheduling policy for the inboundpacket. For details about the scheduling policies, see Table 3-14.

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 Referencein 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 networkside to the user side). When you need to set the traffic profile in the connection receivingdirection, use this parameter.

– tx-cttr: Indicates the traffic ID in the connection transmitting direction (from the userside to the network side). When you need to set the traffic profile in the connectiontransmitting direction, use this parameter.

l (Optional) Enter keyword traffic-table to add or modify the traffic profile referenced by theservice port.

l (Optional) Enter keyword user-encap to select the encapsulation type of the packets on theuser 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

ExampleAssume that the CIR is 2048 kbit/s, 802.1p priority of the outbound packet is 6, and thescheduling policy of the inbound packet is Tag-In-Package. To add traffic profile 9 with thesesettings, do as follows:

huawei(config)#traffic table ip index 9 cir 2048 priority 6 priority-policy tag-In-Package Create traffic descriptor record successfully ------------------------------------------------



3-71

TD Index : 9 TD Name : ip-traffic-table_9 Priority : 6 Copy Priority : - CTAG Mapping Priority: - 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 : ip-traffic-table_9 Priority : 6 Copy Priority : - CTAG Mapping Priority: - 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 ------------------------------------------------

3.8.1.2 Configuring Rate Limitation on an Ethernet Port

This topic describes how to configure upstream rate limitation on a specified Ethernet port.

PrerequisiteThe Ethernet board must be configured in the system.

Contextl Rate limitation on an Ethernet port is valid only to the Ethernet board.

l 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 ona 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.

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 limitationon the specified Ethernet port

----End


Configuration Guide


Issue 04 (2011-04-27)

ExampleTo limit the rate of Ethernet port 0/0/0 to 6400 kbit/s, do as follows:

huawei(config)#line-rate outbound 6400 port 0/0/0huawei(config)#display qos-info line-rate port 0/0/0

line-rate: port 0/0/0: Outbound: line rate: 6400 Kbps

3.8.1.3 Configuring User-based Rate LimitationIn the user-based rate limitation, the voice service, IPTV service, and Internet access service ofeach user share a total user bandwidth. When there is no one of the three services, the other twoservices can hold a burst of the total user bandwidth so that the total user bandwidth can bemanaged in a unified manner.

ContextWhen the user uses the Triple play service, the voice service, IPTV service, and Internet accessservice of each user share a total user bandwidth. All services of the user hold the total userbandwidth, and the service with the highest CoS priority is ensured first. When other servicescarry no traffic, each service can hold a burst of the total user band width. The multicastbandwidth is determined by the bandwidth of demanded programs. The total bandwidth ofdemanded programs cannot exceed the total user bandwidth.

Procedurel For the Ethernet access mode:

Each port corresponds to a user. By limiting the upstream/downstream rate of the port, setthe maximum upstream/downstream rate to the total user bandwidth. All triple play servicesof the user hold the total user bandwidth, and the service with the highest CoS priority isensured first. When other services carry no traffic, each service can hold a burst of the totaluser band width.

1. Run the traffic table ip command to create an IP traffic profile to configure the CoSpriority of each service and ensure the CIR and PIR. Here, the PIR is equal to the totaluser bandwidth. When other services carry no traffic, each service can hold a burst ofthe total user band width.The CoS priorities of services are voice service, IPTV service, and Internet accessservice in a descending order.

2. Run the service-port command to create service ports of the services, using the IPtraffic profile created in Step 1.

3. Run the queue-scheduler strict-priority command to configure queue schedulingmode of the port to strict priority queue scheduling.

----End

ExampleAssume that under Ethernet port 0/4/1, a user is provided with the VoIP, IPTV, and Internetaccess services. Set the total user bandwidth to 10 Mbit/s (that is, set the downstream maximum



3-73

rate to 10 Mbit/s in the channel configuration profile). In the case that any two services carry notraffic, the third service can hold a burst of the total user bandwidth. To perform such aconfiguration 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.

l Service port 101 of the VoIP service uses traffic profile 11, with the CIR 1 Mbit/s and the802.1p priority 6.

l Service port 100 of the IPTV service uses traffic profile 12, with the packet rate not limitedand the 802.1p priority 5.

huawei(config)#traffic table ip index 10 cir 2048 pir 10240 priority 4 priority-policy local-Settinghuawei(config)#service-port 100 vlan 2 adsl 0/4/1 vpi 0 vci 35 multi-service user-vlan 20 rx-cttr 10 tx-cttr 10huawei(config)#traffic table ip index 11 cir 1024 pir 10240 priority 6 priority-policy local-Settinghuawei(config)#service-port 101 vlan 2 adsl 0/4/1 vpi 0 vci 35 multi-service user-vlan 30 rx-cttr 11 tx-cttr 11huawei(config)#traffic table ip index 12 cir off priority 5 priority-policy local-Settinghuawei(config)#service-port 102 vlan 2 adsl 0/4/1 vpi 0 vci 35 multi-service user-vlan 40 rx-cttr 12 tx-cttr 12huawei(config)#queue-scheduler strict-priority

3.8.1.4 Configuring Traffic Suppression

This topic describes how to configure traffic suppression. The purpose of traffic suppression isto 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 on 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 trafficsuppression 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.

l value: Indicates the index of the traffic suppression level. The index value is the value queriedin step 2.

----End


Configuration Guide


Issue 04 (2011-04-27)

ExampleTo suppress the broadcast packets according to traffic suppression level 8 on port 0 on the ETHboard in slot 0/4, do as follows:

huawei(config)#interface eth 0/4huawei(config-if-eth-0/4)#display traffic-suppress all

Command: display traffic-suppress all 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 --------------------------------------------------------------------- --------------------------------------------------------------------- PortID Broadcast_index Multicast_index Unicast_index --------------------------------------------------------------------- 0 7 7 7 1 7 7 7 2 7 7 7 3 7 7 7 4 7 7 7 5 7 7 7 6 7 7 7 7 7 7 7 --------------------------------------------------------------------- huawei(config-if-eth-0/4)#traffic-suppress all broadcast value 8huawei(config-if-eth-0/4)#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 ---------------------------------------------------------------------



3-75

3.8.2 Configuring Queue SchedulingThis topic describes how to configure the queue scheduling so that the services with differentpriorities have different scheduling policies. Then, the corresponding QoS of these services canbe ensured.

ContextThe queue scheduling policy of the MA5612 is configured according to the service type. Thatis, the VoIP service priority is usually set to 6, the video service priority is usually set to 4, andthe Internet service priority is usually set to 0. When congestion occurs, the system ensures thatthe traffic stream with a higher priority is processed in time, and also ensures the QoS of serviceswith a lower priority.

3.8.2.1 Configuring the Queue Scheduling ModeThis topic describes how to configure the queue scheduling mode for ensuring that packets inthe queue with a higher priority can be processed in time in case of congestion.

3.8.2.2 Configuring the Mapping Between the Queue and the 802.1p PriorityThis topic describes how to configure the mapping between the queue and the 802.1p priorityso that packets with different 802.1p priorities are mapped to the specified queues based on theconfigured mapping. This enhances the flexibility of mapping packets to queues.

3.8.2.1 Configuring the Queue Scheduling ModeThis topic describes how to configure the queue scheduling mode for ensuring that packets inthe queue with a higher priority can be processed in time in case of congestion.

ContextThe MA5612 supports the three queue scheduling modes: strict-priority queue (PQ), weightedround robin (WRR), and PQ+WRR.

l PQThe PQ gives preference to packets in a queue with a higher priority. The packets of a lowerpriority queue can be transmitted only when a queue with a higher priority is empty.By default, the system adopts the PQ mode.

l WRRThe system supports WRR for eight queues. Each queue has a weight value (w7, w6, w5,w4, w3, w2, w1, and w0 in a descending order) for resource acquisition. In the WRRscheduling mode, the queues are scheduled in turn, which ensures that each queue can bescheduled.Table 3-15 lists the mapping between the queue weights and the actual queues.

Table 3-15 Mapping between the queue weights and the actual queues

QueueNumber

ConfiguredWeight

Actual QueueWeight (PortSupporting EightQueues)

Actual QueueWeight (PortSupporting FourQueues)

7 W7 W7 -


Configuration Guide


Issue 04 (2011-04-27)

QueueNumber

ConfiguredWeight

Actual QueueWeight (PortSupporting EightQueues)

Actual QueueWeight (PortSupporting FourQueues)

6 W6 W6 -

5 W5 W5 -

4 W4 W4 -

3 W3 W3 W7+W6

2 W2 W2 W5+W4

1 W1 W1 W3+W2

0 W0 W0 W1+W0

Wn: Indicates the weight of queue n. The weight sum of the queues (except the queue withweight value 255) must be equal to 0 or 100, where 0 indicates that the strict PQ schedulingmode is used and 255 indicates that the queue is not 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 PQmode.

– 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 thequeue scheduling mode.

----End

ExampleTo adopt the WRR scheduling mode and set the weight values of the eight 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 10huawei(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



3-77

6 WRR 10 7 WRR 10 ---------------------------------

To adopt the PQ+WRR scheduling mode and set the weight values of the six queues to 20, 20,10, 30, 10, and 10 respectively, do as follows:

huawei(config)#queue-scheduler wrr 20 20 10 30 10 10 0 0huawei(config)#display queue-scheduler Queue scheduler mode : WRR --------------------------------- Queue Scheduler Mode WRR Weight --------------------------------- 0 WRR 20 1 WRR 20 2 WRR 10 3 WRR 30 4 WRR 10 5 WRR 10 6 PQ -- 7 PQ -- ---------------------------------

3.8.2.2 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 priorityso that packets with different 802.1p priorities are mapped to the specified queues based on theconfigured mapping. This enhances the flexibility of mapping packets to queues.

Contextl The configuration is valid to all the service boards in the system.

l By default, the mapping between the queue and the 802.1p priority is as listed in Table3-16.

Table 3-16 Mapping between the queue and the 802.1p priority

Queue Number Actual QueueNumber (PortSupporting EightQueues)

Actual QueueNumber (PortSupporting FourQueues)

802.1p Priority

7 7 3 7

6 6 3 6

5 5 2 5

4 4 2 4

3 3 1 3

2 2 1 2

1 1 0 1

0 0 0 0


Configuration Guide


Issue 04 (2011-04-27)

Procedure

Step 1 Run the cos-queue-map command to configure the mapping between the 802.1p priority andthe queue.

Step 2 Run the display cos-queue-map command to query the mapping between the 802.1p priorityand 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 prioritiesto queue 6, do as follows:

huawei(config)#cos-queue-map cos0 0 cos1 2 cos2 6 cos3 6 cos4 6 cos5 6 cos6 6 cos7 6huawei(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 ------------------------

3.8.3 Configuring Early DropThis topic describes how to configure early drop, which is applicable to the dropping policysettings for the packets in the queue.

Context

Early drop means that the system drops the packets that wait to enter the queue when congestionoccurs. This process occurs after traffic management. The MA5612 supports early drop by color:

The MA5612 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.

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 check whether the configuration of the WRED profileis correct.

Step 3 Bind a queue with a WRED profile.



3-79

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 notdropped; the lower threshold of dropping the yellow packets is 50; the upper threshold ofdropping the yellow packets is 80; the packet drop rate is 100. To bind such a WRED profilewith queue 0, do as follows:

huawei(config)#wred-profile index 0 green low-limit 100 high-limit 100 discard-probability 0 yellow low-limit 50 high-limit 80 discard-probability 100huawei(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: 0 ------------------------------------------------------------------ huawei(config)#queue-wred queue0 0

3.8.4 Configuring Traffic Management Based on ACL RulesThe 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 trafficstreams.

3.8.4.1 Controlling the Traffic Matching an ACL RuleThis topic describes how to control the traffic matching an ACL rule on a specified port, andprocess the traffic that exceeds the limit, such as adding the DSCP tag or dropping the packetdirectly.

3.8.4.2 Adding a Priority Tag to the Traffic Matching an ACL RuleThis topic describes how to add a priority tag to the traffic matching an ACL rule on a specifiedport so that the traffic can obtain the service that match the specified priority. The priority tagtype can be ToS or 802.1p.

3.8.4.3 Enabling the Statistics Collection of the Traffic Matching an ACL RuleThis topic describes how to enable the statistics collection of the traffic matching an ACL rule,thus analyzing and monitoring the traffic.

3.8.4.4 Enabling the Mirroring of the Traffic Matching an ACL RuleThis 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 canmonitor the traffic of the mirroring source port by analyzing the traffic that passes the mirroringdestination port.

3.8.4.1 Controlling the Traffic Matching an ACL Rule

This topic describes how to control the traffic matching an ACL rule on a specified port, andprocess the traffic that exceeds the limit, such as adding the DSCP tag or dropping the packetdirectly.


Configuration Guide


Issue 04 (2011-04-27)

Prerequisite

The ACL and the rule of the ACL are configured, and the port for traffic limit is working in thenormal state.

Contextl The traffic statistics are only effective for the permit rules of an ACL.l 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.Run this command to set the action to be taken when the traffic received on the port exceeds thelimited value. Two options are available:l drop: Drop the traffic that exceeds the limited value.l remark-dscp value: To set the DSCP priority for the traffic that exceeds the limited value,

use this parameter.

Step 2 Run the display qos-info traffic-limit port command to query the traffic limit information onthe specified port.

----End

Example

To limit the traffic that matches ACL 2001 received on port 0/4/1 to 512 kbit/s, and add theDSCP priority tag (af1) to packets that exceed the limit, do as follows:

huawei(config)#traffic-limit inbound ip-group 2001 512 exceed remark-dscp af1 port 0/4/1//"af1" represents a dscp type: Assured Forwarding 1 service (10).huawei(config)#display qos-info traffic-limit port 0/4/1traffic-limit:port 0/4/1: Inbound: Matches: Acl 2001 rule 5 running Target rate: 512 Kbps Exceed action: remark-dscp af1

3.8.4.2 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 specifiedport so that the traffic can obtain the service that match the specified priority. The priority tagtype can be ToS or 802.1p.

Prerequisite

The ACL and the rule of the ACL are configured, and the port for traffic limit is working in thenormal state.

Context

The traffic statistics are only valid to permit rules of an ACL.



3-81

Procedure

Step 1 Run the traffic-priority command to add a priority tag to the traffic matching an ACL rule ona specified port.

Step 2 Run the display qos-info traffic-priority port command to query the configured priority.

----End

ExampleTo add a priority tag to the traffic that matches ACL 2001 received on port 0/2/0, and the localpriority of the traffic is 0 , do as follows:

huawei(config)#traffic-priority inbound ip-group 2001 local-precedence 0 port 0/4/1huawei(config)#display qos-info traffic-priority port 0/4/1 traffic-priority: port 0/4/1: Inbound: Matches: Acl 2001 rule 5 running Priority action: local-precedence 0

3.8.4.3 Enabling the Statistics Collection of the Traffic Matching an ACL RuleThis topic describes how to enable the statistics collection of the traffic matching an ACL rule,thus analyzing and monitoring the traffic.

PrerequisiteThe ACL and the rule of the ACL are configured, and the port for traffic statistics is working inthe normal state.

ContextThe 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 anACL rule on a specified port.

Step 2 Run the display qos-info traffic-mirror port command to query the statistics information aboutthe traffic matching an ACL rule on a specified port.

----End

ExampleTo enable the statistics collection of the traffic that matches ACL 2001 received on port 0/0/0,do as follows:

huawei(config)#traffic-statistic inbound ip-group 2001 port 0/0/0huawei(config)#display qos-info traffic-statistic port 0/0/0

traffic-statistic:port 0/0/0: Inbound:


Configuration Guide


Issue 04 (2011-04-27)

Matches: Acl 2001 rule 5 running 0 packet

3.8.4.4 Enabling the Mirroring of the Traffic Matching an ACL RuleThis 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 canmonitor the traffic of the mirroring source port by analyzing the traffic that passes the mirroringdestination port.

PrerequisiteThe ACL and the rule of the ACL are configured, and the port for traffic mirroring is workingin the normal state.

Contextl The traffic statistics are only valid to permit rules of an ACL.l The destination mirroring port cannot be an aggregation port.l The system supports only one mirroring destination port and the mirroring destination port

must be the upstream port.

Procedure

Step 1 Run the traffic-mirror command to enable the mirroring of the traffic matching an ACL ruleon a specified port.

Step 2 Run the display qos-info traffic-mirror port command to query the mirroring informationabout the traffic matching an ACL rule on a specified port.

----End

ExampleTo mirror the traffic that matches ACL 2001 received on port 0/4/1 to port 0/0/0, do as follows:

huawei(config)#traffic-mirror inbound ip-group 2001 port 0/4/1 to port 0/0/0huawei(config)#display qos-info traffic-mirror port 0/4/1 traffic-mirror: port 0/4/1: Inbound: Matches: Acl 2001 rule 5 running Mirror to: port 0/0/0

3.9 Configuring Environment MonitoringThis topic provides concepts associated with environment monitoring and describes how toconfigure environment monitoring on the MA5612.

3.9.1 Configuring Monitoring Through the ESCThis topic describes how to configure the H831VESC and the MiniESC on the MA5612.

3.9.2 Configuring the Monitoring Through the EPS30-4815AF



3-83

The EPS30-4815AF system converts the input 220 VAC into the -48 VDC to provide the -48VDC power. In addition, the EPS30-4815AF system can manage one battery set and monitorother environment parameters through its EPMU03 monitoring module. This topic provides thebasic information about the EPS30-4815AF and describes how to configure data associated withenvironment monitoring.

3.9.3 Configuring the Monitoring Through the FanThis topic describes how to configure the speed adjustment mode and the alarm function of thefan. Thus, the fan speed of the MA5612 can be adjusted automatically, and the fan tray of theMA5612 can be monitored.

3.9.1 Configuring Monitoring Through the ESCThis topic describes how to configure the H831VESC and the MiniESC on the MA5612.

3.9.1.1 Configuring the Monitoring Through the H831VESCYou can monitor the environment status of the MA5612 through its built-in virtual EMUH831VESC. This topic describes how to configure the H831VESC.

3.9.1.2 Configuring the Monitoring Through the ESCMThe ESCM is an EMU that integrates the environment monitoring board, terminal blocks, andDIP switches. The ESCM monitors the environment parameters such as smoke, water, doorstatus, MDF, temperature, and humidity of the device, and also provides extended monitoringports. This topic provides the basic information about the ESCM and describes how to configureanalog and digital parameters of the ESCM.

3.9.1.1 Configuring the Monitoring Through the H831VESC

You can monitor the environment status of the MA5612 through its built-in virtual EMUH831VESC. This topic describes how to configure the H831VESC.

Contextl The H831VESC is a built-in virtual EMU of the control board on the MA5612, and the

MONITOR port on the control board is connected to the external sensor through a cablesuch as a straight-through cable.

l The EMU ID of the H831VESC, and the ID of its subnode connected to the shelf areautomatically generated by the system. Therefore, you cannot change them.

l The H831VESC supports five digital parameters. Among the five digital parameters,

– Digital parameters 0-3: user-defined

– Digital parameter 0: Indicates the smoke 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 MDF by default.

By default, the valid levels of user-defined digital parameters are all low levels.

– Digital parameter 4: invariably allocated by the system. You cannot modify it.

It is used to monitor the AC power input. When the AC power fails, this digit parameterreports an alarm.


Configuration Guide


Issue 04 (2011-04-27)

Data Plan

Table 3-17 Data plan for configuring the H831VESC

Item Data Remarks

Digitalparameters

Digital parameter ID: 0 In the F01S100 cabinet, digital parameter 0 isused to monitor the temperature. In theF01E50 cabinet, digital parameter 0 does nottake effect.

Valid level of digitalparameter 0: low level

When the low level represents the valid level,the MA5612 does not report an alarm in thecase of low level.

Name of digital parameter 0:Temperature

This digital parameter is set according to theactual requirements. The monitoring digitalparameter of the temperature sensor is set tomonitor the temperature.

User-defined alarm ID ofdigital parameter 0: 5

When the temperature in the cabinet isbetween 67°C and 73°C, the MA5612 reportsan alarm.The meanings of the alarm IDs are as follows:0: fog; 1: door status; 2: arrester; 3: wiring; 4:power supply; 5: user-defined alarm for thedigital parameter

Digital parameter ID: 1 In the F01S100 and F01E50 cabinets, digitalparameter 1 is used to monitor door status.



Name of digital parameter 1:Door

This digital parameter is set according to theactual requirements. The monitoring digitalparameter of the door sensor is set to monitorthe door status.


When the cabinet door is open, the MA5612reports an alarm.

Digital parameter ID: 2 In the F01S100 and F01E50 cabinets, digitalparameter 2 is used to monitor the lightningarrester.



Name of digital parameter 2:SPD

This digital parameter is set according to theactual requirements. The monitoring digitalparameter of the SPD status sensor is set tomonitor the SPD status.



3-85

Item Data Remarks


When the lightning arrester is faulty, theMA5612 reports an alarm.

Digital parameter ID: 3 In the F01S100 cabinet, digital parameter 3 isused to monitor the fan. In the F01E50cabinet, digital parameter 3 is used to monitorthe MDF.



Name of digital parameter 3:Fan

This digital parameter is set according to theactual requirements. The monitoring digitalparameter of the fan status sensor is set tomonitor the fan status.


When the fan is faulty, the MA5612 reportsan alarm.

ProcedureStep 1 Query the status of the H831VESC.

Run the display emu command to query the status of the H831VESC.

Step 2 Configure the digital parameters.

Run the esc digital command to configure the valid level, name, and alarm ID of the digitalparameters.

Step 3 Query the environment information about the H831VESC.

Run the display esc environment info command to query the environment information aboutthe H831VESC.

Step 4 Save the data.

Run the quit command to quit the H831VESC mode, and then run the save command to savethe data.

----End

ResultAfter the configuration, the H831VESC works in the normal state and monitors the digitalparameters set on the MA5612. When the actual level of a monitored digital parameter isdifferent from the valid level preset in the system, the MA5612 reports an alarm.

ExampleTable 3-17 shows the parameter plan for configuring the H831VESC.

huawei(config)#display emu 0


Configuration Guide


Issue 04 (2011-04-27)

EMU ID: 0 ---------------------------------------------------------------------------- EMU name : H831VESC EMU type : H831VESC Used or not : Used EMU state : Normal Frame ID : 0 Subnode : 1 COM port : - ---------------------------------------------------------------------------- huawei(config)#interface emu 0 huawei(config-if-h831vesc-0)#esc digital 0 available-level low-level digital-alarm 5 name Temperaturehuawei(config-if-h831vesc-0)#esc digital 1 available-level high-level digital-alarm 1 name Doorhuawei(config-if-h831vesc-0)#esc digital 2 available-level low-level digital-alarm 2 name SPDhuawei(config-if-h831vesc-0)#esc digital 3 available-level low-level digital-alarm 5 name Fanhuawei(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 1 2 Arrester Normal 0 |3 Fan Normal 0 4 Power supply Normal 0 ----------------------------------------------------------------------------huawei(config-if-h831vesc-0)#quithuawei(config)#save

3.9.1.2 Configuring the Monitoring Through the ESCMThe ESCM is an EMU that integrates the environment monitoring board, terminal blocks, andDIP switches. The ESCM monitors the environment parameters such as smoke, water, doorstatus, MDF, temperature, and humidity of the device, and also provides extended monitoringports. This topic provides the basic information about the ESCM and describes how to configureanalog and digital parameters of the ESCM.

Prerequisitel The ESCM must be connected to the serial port of the MA5612 through a dedicated

environment monitoring cable. In addition, the working mode of the serial port must be setto EMU by running the serial-mode command.

l The setting of the hardware DIP switch on the ESCM must be the same as the configuredEMU subnode ID.

l The sixth DIP switch on the ESCM must be set to on, which indicates that the baud rate is19200 bit/s.

Contextl The differences between an analog parameter and a digital parameter are as follows:

– An analog parameter is a consecutive parameter, such as the temperature, voltage, andcurrent.

– A digital parameter is a discrete value that indicates a state.l The ESCM requires an RS-232 serial port for data communication.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 anyparameter in these two analog parameters, except the upper and lower alarm thresholds.



3-87

– 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 analog parameters, except the valid level.– Digital parameters 2-7: user-defined.

Data PlanTable 3-18 provides the data plan for configuring the ESCM.

Table 3-18 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 to8.

Analogparameters

Analog parameter ID: 0 This analog parameter is set according to theactual requirements. The built-in analogparameter is set here to monitor the ambienttemperature of the device.For values and details of this parameter, see theesc analog command.

Upper alarm threshold ofanalog parameter 0: 54°C

When the ambient temperature of the device ishigher than 54°C, the device reports an alarm.

Lower alarm threshold ofanalog parameter 0: 6°C

When the ambient temperature of the device islower than 6°C, the device reports an alarm.

Analog parameter ID: 2 The user-defined humidity monitoring analogparameter is added to monitor the ambienthumidity of the device.For values and details of this parameter, see theesc analog command.

Upper alarm threshold ofanalog parameter 2: 75%RH

When the ambient humidity of the device ishigher than 75% RH, the device reports an alarm.

Lower alarm threshold ofanalog parameter 2: 5%RH

When the ambient humidity of the device islower than 5% RH, the device reports an alarm.

Name of analog parameter2: humidity

-

Alarm ID of analogparameter 2: 2

The user-defined humidity alarm of the systemis used.

Unit of analog parameter2: % RH

-


Configuration Guide


Issue 04 (2011-04-27)

Item Data Remarks

Sensor type of analogparameter 2: voltage type

-

Digitalparameters

Digital parameter ID: 1 This parameter is invariably allocated by thesystem, and is used to monitor the door status ofthe telecommunications room. You cannotmodify any parameter of this digital parameter,except the valid level.

Valid level of digitalparameter 1: high level

When the high level represents the valid level,the device does not report an alarm in the case ofhigh level.

Name of digital parameter1: Door0

It is a user-defined digital parameter and is setaccording to the actual requirements. Themonitoring digital parameter is set here tomonitor the door status of the device.


When the door is open, the device reports analarm.

Digital parameter ID: 2 -


When the low level represents the valid level, thedevice does not report an alarm in the case of lowlevel.

Name of digital parameter2: Fan

It is a user-defined digital parameter and is setaccording to the actual requirements. Themonitoring digital parameter of the fan unit is sethere to monitor the fan unit.


When the fan unit is faulty, the device reports analarm.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: secondary power supply; 8: door status of theequipment room; 9: theft; 10: cable distributionframe; 11: fan; 12: fire; 13: smoke; 14: power;15: water; 16: diesel; 17: abnormal smell 18: airconditioner; 19: lightning arrester; 20: DCvoltage; 21 output control switch; 22: user-defined alarm for the digital parameter

ProcedureStep 1 Add an EMU.

Run the emu add command to add an EMU to monitor the environment parameters (such astemperature, humidity, power, and voltage) of the device so that the device runs in a stableenvironment.



3-89

The EMU ID is 3, the type is ESCM (MiniESC on the CLI), the subnode ID is 8, and the serialport type is RS-232.

Step 2 Configure the analog parameters.

Run the esc analog command to configure the upper/lower alarm thresholds and measurementthresholds, 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 digitalparameters.

Step 4 Query the environment information about the ESCM.

Run the display esc environment info command to query the environment information aboutthe ESCM.


Run the quit command to quit the H831VESC mode, and then run the save command to savethe data.

----End

ResultAfter the configuration, the ESCM works in the normal state and monitors the analog and digitalparameters set on the MA5612.l When an analog parameter measured is not within the upper and lower alarm thresholds

preset in the system, the MA5612 reports an alarm.l When the actual level of a monitored digital parameter is different from the valid level

preset in the system, the MA5612 reports an alarm.

ExampleTable 3-18 shows the data plan for configuring the ESCM.

huawei(config)#emu add 3 MINIESC 0 8 RS232 MiniESChuawei(config)#interface emu 3huawei(config-if-miniesc-3)#esc analog 0 alarm-upper-limit 54 alarm-lower-limit 6 Send command to environment monitor board ,please waiting for the ack huawei(config-if-miniesc-3)# Execute command successfulhuawei(config-if-miniesc-3)#esc analog 2 alarm-upper-limit 75 alarm-lower-limit 5 name humidity sensor-type 0:voltage analog-alarm 2 unit %RH Send command to environment monitor board ,please waiting for the ack huawei(config-if-miniesc-3)# Execute command successful huawei(config-if-miniesc-3)#esc digital 1 available-level high-level digital-alarm 8 name Door0 Send command to environment monitor board ,please waiting for the ack huawei(config-if-miniesc-3)# Execute command successful huawei(config-if-miniesc-3)#esc digital 2 available-level low-level digital-alarm 11 name Fan Send command to environment monitor board ,please waiting for the ack huawei(config-if-miniesc-3)#


Configuration Guide


Issue 04 (2011-04-27)

Execute command successful 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 - ---------------------------Digital environment info------------------------- ID Name State Value |ID Name State Value 0 Wiring Normal 1 |1 Door0 Alarm 0 2 Fan Normal 0 |3 - Normal 1 4 - Normal 1 |5 - Normal 1 6 - Normal 1 |7 - Normal 1 8 Fog Normal 1 |9 Water_Alarm Normal 1 ----------------------------------------------------------------------------

huawei(config-if-miniesc-3)#quithuawei(config)#save

3.9.2 Configuring the Monitoring Through the EPS30-4815AFThe EPS30-4815AF system converts the input 220 VAC into the -48 VDC to provide the -48VDC power. In addition, the EPS30-4815AF system can manage one battery set and monitorother environment parameters through its EPMU03 monitoring module. This topic provides thebasic information about the EPS30-4815AF and describes how to configure data associated withenvironment monitoring.

Prerequisitel The EPS30-4815AF must be connected to the serial port of the MA5612 through a dedicated

environment monitoring cable. In addition, the working mode of the serial port must be setto EMU by running the serial-mode command.

l The setting of the hardware DIP switch on the EPS30-4815AF must be the same as theconfigured EMU subnode ID.

l The sixth DIP switch on the EPS30-4815AF must be set to off, which indicates that thebaud rate is 19200 bit/s.

Contextl The differences between an analog parameter and a digital parameter are as follows:

– An analog parameter is a consecutive parameter, such as the temperature, voltage, andcurrent.

– A digital parameter is a discrete value that indicates a state.l The EPS30-4815AF requires an RS-232 serial port for data communication.

Data PlanTable 3-19 provides the data plan for configuring the EPS30-4815AF.



3-91

Table 3-19 Data plan for configuring the EPS30-4815AF

Item Data Remarks

EMU Type: Power4830 (Pwr4830) The selected type of the EPS30-4815AFis Power4830 (Pwr4830).

SN: 2 -

Subnode ID: 4 The DIP switch on the EPS30-4815AFis set to 4.

Batterymanagementparameters

Current-limiting coefficient forbattery charging: 0.15

You can change the configuration byrunning the power battery commandaccording to the actual requirements.

Interval of battery equalizedcharging: 60 days

Number of battery sets: 1

Capacity of the battery set:75AH

Upper measurement threshold ofthe battery set temperature: 80°C

Lower measurement threshold ofthe battery set temperature: -20°C

Upper alarm threshold of thebattery set temperature: 50°C

Lower alarm threshold of thebattery set temperature: 0°C

Temperature compensationcoefficient of the battery set: 80mV

Chargingparameters ofthe battery

Charging mode of the battery:automatic

In this topic, the default settings areadopted. You can run the powercharge command to modify parametersaccording to actual conditions.Equalized charging voltage of

the battery: 56.5 V

Float charging voltage of thebattery: 53.5 V

Power supplyload power-offand battery setpower-offparameters

Battery set power-off permissionstatus: permit

You can change the configuration byrunning the power charge commandaccording to the actual requirements.

Battery set power-off voltage: 43V

High-temperaturepower-off

Battery high-temperaturepower-off permission status:forbid

You can change the configuration byrunning the power charge commandaccording to the actual requirements.


Configuration Guide


Issue 04 (2011-04-27)

Item Data Remarks

parameters ofthe battery

Temperature for battery high-temperature power-off: 53°C

Rectifier unitparameter

Number of rectifier units: 2 The EPS30-4815AF supports up to tworectifier units.

Environmentmonitoringparameters

Upper alarm threshold of thetemperature: 57°C

You can change the configuration byrunning the power environmentcommand according to the actualrequirements.Lower alarm threshold of the

temperature: -5°C

Upper measurement threshold ofthe temperature: 80°C

Lower measurement threshold ofthe temperature: -20°C

Upper alarm threshold of thehumidity: 80% RH

Lower alarm threshold of thehumidity: 10% RH

Upper measurement threshold ofthe humidity: 100% RH

Lower measurement threshold ofthe humidity: 0% RH

Extendeddigitalparameter

Extended digital parameter ID: 1 -

Valid level of extended digitalparameter 1: low level

When the low level represents the validlevel, the device does not report analarm in the case of low level.

Name of extended digitalparameter 1: Fan

It is a user-defined digital parameter andis set according to the actualrequirements. The monitoring digitalparameter of the fan status sensor is setto monitor the fan status.



3-93

Item Data Remarks

User-defined alarm ID ofextended digital parameter 1: 11

The meanings of the alarm IDs are asfollows:1: AC voltage; 2: AC switch; 3: batteryvoltage; 4: battery fuse; 5: load fuse; 6:rectifier module; 7: secondary powersupply; 8: door status of the equipmentroom; 9: theft; 10: cable distributionframe; 11: fan; 12: fire; 13: smoke; 14:power; 15: water; 16: diesel; 17:abnormal smell 18: air conditioner; 19:lightning arrester; 20: DC voltage; 21output control switch; 22: user-definedalarm for the digital parameter

Extended digital parameter ID: 3 -

Valid level of extended digitalparameter 3: low level

When the low level represents the validlevel, the device does not report analarm in the case of low level.

Name of extended digitalparameter 3: SPD

It is a user-defined digital parameter andis set according to the actualrequirements. The monitoring digitalparameter of the SPD status sensor is setto monitor the SPD status.

User-defined alarm ID ofextended digital parameter 3: 19

When the lightning arrester is faulty, theMA5612 reports an alarm.

Procedure

Step 1 Add the Power4830.

Run the emu add command to add the Power4830.

Step 2 In the environment monitoring configuration mode, run the display power systemparameter command to query the default configuration.

Step 3 Configure battery parameters.

Run the power battery parameter command to configure battery parameters, including batterymanagement parameters, charging parameters, load power-off and battery set power-offparameters, and battery high-temperature power-off parameters. You can also use the defaultsettings.

Step 4 Configure the parameter of the rectifier unit.

Run the power module-num command to configure the parameter of the rectifier unit.

Step 5 Configure the environment parameters for power supply monitoring.

Run the power environment command to configure the upper/lower alarm thresholds andmeasurement thresholds of temperature or humidity for power monitoring. In this manner, the


Configuration Guide


Issue 04 (2011-04-27)

power module generates alarms when it works in a condition that does not meet the presentrequirements.

Step 6 Configure the external extended digital parameter for power supply monitoring.

Run the power outside_digital command to configure the external extended digital parameterfor power supply monitoring.

Step 7 Query configuration parameters and environment parameters of the power system.

Run the display power system parameter command to query configuration parameters of thepower monitoring unit.

Step 8 Run the display power alarm command to query the alarm. Ensure that no alarm (except thedoor 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 thedata.

----End

ResultAfter the configuration, the EPS30-4815AF works in the normal state and monitors parametersset on the MA5612. When a monitored parameter is abnormal, the MA5612 reports an alarm.

ExampleTable 3-19 shows the data plan for configuring the monitoring through the EPS30-4815AF.

huawei(config)#emu add 2 POWER4830 0 4 RS232 POWER4830huawei(config)#interface emu 2huawei(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 : 65 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 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 module 1 switch state : On Battery high-temperature-off permit : Forbid Battery high-temperature-off temperature: 53 C ----------------------------------------------------------------------------huawei(config-if-power4830-2)#display power environment parameter

EMU ID: 2 power environment configration parameter

---------------------------------------------------------------------------- AnalogID Name AlmUpper AlmLower TestHigh TestLow Unit type 0 Temperature 50 0 80 -20 C Current 1 Humidity 80 10 100 0 %R.H. Current ---------------------------------------------------------------------------- DigitalID Name Available Level|DigitalID Name Available Level 0 - 1 | 1 - 1



3-95

2 - 1 | 3 - 1 4 - 1 | 5 - 1 6 - 1 ----------------------------------------------------------------------------huawei(config-if-power4830-2)#power battery parameter 0.15 60 1 75huawei(config-if-power4830-2)#power module-num 2huawei(config-if-power4830-2)#power environment humidity 80 10 100 0 This command is invalid unless in the contition 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 contition of install the sensor, would you continue? (y/n)[n]:y huawei(config-if-power4830-2)#power outside_digital 1 available-level low-level digital_alarm 11 name Fanhuawei(config-if-power4830-2)#power outside_digital 3 available-level low-level digital_alarm 19 name SPDhuawei(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 : 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 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 module 1 switch state : On Battery high-temperature-off permit : Forbid Battery high-temperature-off temperature: 53 C ---------------------------------------------------------------------------- huawei(config-if-power4830-2)#display power environment parameter EMU ID: 2 Power environment configration parameter ---------------------------------------------------------------------------- AnalogID Name AlmUpper AlmLower TestUpper TestLower Unit 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 SPD 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 Door alarm : Alarm Water alarm : Normal //The "Door alarm" alarm is generated because the door of the cabinet is not closed. Fog 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


Configuration Guide


Issue 04 (2011-04-27)

0 - Normal | 1 Fan Normal 2 - Normal | 3 SPD Normal 4 - Normal | 5 - Normal 6 - Normal ----------------------------------------------------------------------------huawei(config-if-power4830-2)#quithuawei(config)#save

3.9.3 Configuring the Monitoring Through the FanThis topic describes how to configure the speed adjustment mode and the alarm function of thefan. Thus, the fan speed of the MA5612 can be adjusted automatically, and the fan tray of theMA5612 can be monitored.

ContextThe fan tray requires the and RS 232 serial ports for data communication.

The MA5612 supports fan monitoring unit, such as fan tray and fan of the network cabinet. Thesubnode ID of the fan tray is always 2 and the subnode ID of the fan of the network cabinet isalways 3.

Procedure

Step 1 Add an EMU.

Run the emu add command to add an EMU.

Step 2 Configure the speed adjustment mode of the fan.

Run the fan speed command to configure the speed adjustment mode of the fan.

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 thefan tray.


Run the quit command to quit the FAN mode, and then run the save command to save the data.

----End

ExampleTable 3-20 shows the data plan for configuring the speed adjustment mode and monitoring ofthe fan.



3-97

Table 3-20 Data plan for configuring monitoring through the fan

Item Data Remarks

EMU Type: FAN Fan parameter is based on the actualfan type. If the fan of the networkcabinet is used, the type isCABINET-FAN.

SN: 1 -

Subnode ID: 2 -

Fan parameters Fan speed adjustment mode:automatic

In this mode, the fan speed isautomatically adjusted according tothe temperature.

Whether to report an alarm when thefan stops rotation because of beingblocked: permit

When the fan stops rotation becauseof being blocked, the device reportsan alarm automatically.

Whether to report an alarm when thetemperature is very high: permit

When the temperature of the fantray is very high, the device reportsan alarm automatically.

huawei(config)#emu add 1 FAN 0 2 RS232 FANhuawei(config)#interface emu 1huawei(config-if-fan-1)#fan speed mode automatichuawei(config-if-fan-1)#fan alarmset block permit Execute command successfulhuawei(config-if-fan-1)#fan alarmset tem-high permit Execute command successfulhuawei(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)#quithuawei(config)#save


Configuration Guide


Issue 04 (2011-04-27)

4 Configuring the Ethernet OAM

About This Chapter

Operation, administration, and maintenance (OAM) refers to a method of monitoring anddiagnosing network faults. The Ethernet OAM feature includes two sub-features, namely,Ethernet CFM OAM and Ethernet EFM OAM.

4.1 Configuring the Ethernet CFM OAMOn the Ethernet network, Ethernet connectivity fault management (CFM) OAM is defined asconnectivity fault management in IEEE 802.1ag to implement the OAM function of connectivitydetection 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.

4.2 Configuring the Ethernet EFM OAMEthernet in the First Mile (EFM) OAM is defined in IEEE 802.3ah to make the Ethernet physical-layer specifications in respect of the user access part and the Ethernet OAM in respect of theaccess part. Ethernet EFM OAM is used for the link detection of the last mile and it is the link-level OAM.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 4 Configuring the Ethernet OAM


4-1

4.1 Configuring the Ethernet CFM OAMOn the Ethernet network, Ethernet connectivity fault management (CFM) OAM is defined asconnectivity fault management in IEEE 802.1ag to implement the OAM function of connectivitydetection 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.

Prerequisitel Network devices and lines must be in the normal state.l The OLT must support the Ethernet CFM OAM function.

ContextOAM 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 Ethernettechnology is developing from carriers' networks to metropolitan area networks (MANs) andwide area networks (WANs), the network management and maintenance are increasinglyimportant. Currently, however, Ethernet does not support carrier-class management, and thusL2 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.

NetworkingFigure 4-1 shows the example network of the Ethernet CFM OAM function.

Figure 4-1 Example network of the Ethernet CFM OAM function

OLT MA5612

0/1/0 0/0/1

Splitter

Procedure


Run the vlan command to create a VLAN that is associated with the object managed by amaintenance association (MA).

Each MA corresponds to one VLAN. The Ethernet CFM checks the connectivity for each MA.

Step 2 Configure a maintenance domain (MD).

4 Configuring the Ethernet OAMSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

An MD can be a network or a part of a network on which the Ethernet CFM is performed. Allthe MDs are managed by a unified Internet service provider (ISP).l Run the cfm md 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 correspondsto 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 connectivityby 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 anddown.

l Up refers to the direction facing packet forwarding at the device layer. That is, packets are forwarded throughthe device.

l Down refers to the reverse direction of the up direction. That is, packets are directly forwarded through theMEP 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 OAMfunction 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

ExampleAssume that 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



4-3

the object managed by the MD is huawei, and the level of the object managed by the MD is 7.To configure the Ethernet CFM OAM function on the MA5612, do as follows:huawei(config)#vlan 10 smart //Create a VLAN that is associated with the MA. huawei(config)#port vlan 10 0/0 0huawei(config)#cfm md 0 name-format string huawei level 7huawei(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 ma 0/0 meplist 2 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 Index : 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 Index : 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 mepindex 0/0/1 ----------------------------------------------------------------------- MEP Index : 0/0/1 MEP Direction : down MEP Port : 0/0/0 VLAN Tag1 : - VLAN Tag2 : - MEP Admin Status : enable MEP CC Status : enable MEP Priority : 7 MEP Alarm Status : RemoteCCM Alarm Time : 2500(ms) Reset Time : 10000(ms) MEP IfType : port Remote MEP ID/MAC : 2/0000-0000-0000 -----------------------------------------------------------------------

4.2 Configuring the Ethernet EFM OAMEthernet in the First Mile (EFM) OAM is defined in IEEE 802.3ah to make the Ethernet physical-layer specifications in respect of the user access part and the Ethernet OAM in respect of theaccess part. Ethernet EFM OAM is used for the link detection of the last mile and it is the link-level OAM.


Configuration Guide


Issue 04 (2011-04-27)

Prerequisitel Network devices and lines must be in the normal state.l The OLT must support the Ethernet EFM OAM function.

ContextOAM 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 EthernetOAM. Ethernet EFM OAM provides a mechanism for monitoring links, such as remote defectindication (RDI) and remote loopback control. It is an L2 mechanism, as a complement to thehigher layer applications.

NetworkingFigure 4-2 shows the example network of the Ethernet EFM OAM function.

Figure 4-2 Example network of the Ethernet EFM OAM function

OLT MA5612

0/1/0 0/0/1

Splitter

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 canbe enabled only when the Ethernet EFM OAM mode of the device at one end is the activemode.

Step 2 Run the efm oam 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 parametersfor 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 errorframe alarm function. In this manner, the link signals and data quality can be monitored.



4-5

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

ExampleAssume that the Ethernet EFM OAM mode is the passive mode, the error frame alarm functionis enabled, the local error frame window is 1, and the error frame threshold is 0. To enable theEthernet EFM OAM function on port 0/4/1, do as follows:huawei(config)#efm oam mode 0/4/1 passivehuawei(config)#efm oam 0/4/1 enablehuawei(config)#efm error-frame 0/4/1 notification enablehuawei(config)#efm error-frame 0/4/1 period 1huawei(config)#efm error-frame 0/4/1 threshold 0

Run the display efm oam status command to query the status of the Ethernet EFM OAMfunction.huawei#display efm oam status { frameid/slotid/portid<S><Length 1-15> }:0/4/1 { 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/4/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 EFMOAM event.huawei(config)#display efm oam event config 0/4/1 Errored Symbol Period Event :Disable Errored Symbol Period Event Window :- Errored Symbol Period Event Threshold :- Errored Frame Event :Enable //The error frame alarm function is enabled. Errored Frame Event Window :1 //The error frame window is 1. Errored Frame Event Threshold :0 //The error frame threshold is 0. 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


Configuration Guide


Issue 04 (2011-04-27)

5 Configuring the Ethernet Access Service

About This Chapter

This topic describes the features and specifications of the Ethernet access service and how toconfigure the Ethernet access service on the MA5612.

1. 5.1 Configuring a VLANConfiguring VLAN is a prerequisite for configuring a service. Hence, before configuringa service, make sure that the VLAN configuration based on planning is complete.

2. 5.2 Configuring the Upstream PortThis topic describes how to add the upstream port to a certain VLAN so that the user packetscarrying the VLAN ID can be transmitted to the upper-layer device through the upstreamport.

3. 5.3 Creating the Ethernet Access Service PortThe service port is used to connect the user side to the network side. To provision services,the service port must be created.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 5 Configuring the Ethernet Access Service


5-1


Prerequisite

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 Table5-1.

Table 5-1 VLAN application and planning

User Type Application Scenario VLAN Planning

l Householduser of theInternetaccessservice

l Commercialuser of theInternetaccessservice

N:1 scenario, that is, thescenario of upstreamtransmission through asingle VLAN, where theservices of multiplesubscribers areconverged to the sameVLAN.

VLAN type: smartVLAN attribute: commonVLAN forwarding mode: by VLAN+MAC

1:1 scenario, that is, thescenario of upstreamtransmission throughdouble VLANs, wherethe outer VLAN tagidentifies a service andthe inner VLAN tagidentifies a user. Theservice of each user isindicated by a unique S+C.

VLAN type: smartAttribute: stackingVLAN forwarding mode: by S+C

Commercialuser of thetransparenttransmissionservice

Applicable only to thetransparent transmissionservice of a commercialuser.

VLAN type: smartVLAN attribute: QinQVLAN forwarding mode: by VLAN+MAC orS+C.


Table 5-2 lists the default parameter settings of VLAN.

5 Configuring the Ethernet Access ServiceSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

Table 5-2 Default parameter settings of VLAN

Parameter Default Setting Remarks

Default VLAN ofthe system

VLAN ID: 1Type: smart VLAN

-

Reserved VLANof the system

VLAN ID range:4079-4093

You can run the vlan reserve command tomodify the VLAN reserved by the system.

Default attributeof a new VLAN

Common -

VLANforwarding mode

VLAN+MAC -

Procedure


Run the vlan command to create a VLAN. VLANs of different types are applicable to differentscenarios.

Table 5-3 VLAN types and application scenarios

VLANType



StandardVLAN

To add a standardVLAN, run the vlanvlanid standardcommand.

Standard VLAN.One standard VLANcontains multipleupstream ports. Ethernetports in one standardVLAN areinterconnected with eachother but Ethernet portsin different standardVLANs are isolated fromeach other.

Only available toEthernet ports andspecifically to networkmanagement andsubtending.

SmartVLAN

To add a smart VLAN,run the vlan vlanidsmart command.

One smart VLAN maycontain multipleupstream ports andservice ports. The serviceports in one smart VLANare isolated from eachother. The service ports indifferent VLANs are alsoisolated. One VLANprovides access formultiple users and thussaves VLAN resources.

Smart VLANs areapplicable to FE serviceaccess. For example,Smart VLANs can beused in residentialcommunities.



5-3

VLANType



MUXVLAN

To add a MUX VLAN,run the vlan vlanidmux command.

One MUX VLAN maycontain multipleupstream ports but onlyone service port. Theservice ports in differentVLANs are isolated.One-to-one mapping canbe set up between a MUXVLAN and an accessuser. Hence, a MUXVLAN can identify anaccess user.

MUX VLANs areapplicable to FE serviceaccess. For example,MUX VLANs can beused to identify users.

NOTE

l To add VLANs with consecutive IDs in batches, run the vlan vlanid to end-vlanid command.

l To add VLANs with inconsecutive IDs in batches, run the vlan vlan-list command.

Step 2 (Optional) Configure the VLAN attribute.

The default attribute for a new VLAN is "common". You can run the vlan attrib command toconfigure the attribute of the VLAN.

Configure the attribute according to VLAN planning.

Table 5-4 VLAN attributes and application scenarios

VLANAttribute



ApplicationScenario

Common

The defaultattribute for a newVLAN is"common".

The VLAN withthis attribute canbe a standardVLAN, smartVLAN, or MUXVLAN.

A VLAN with thecommon attributecan function as acommon layer 2VLAN or functionfor creating a layer3 interface.

Applicable to theN:1 accessscenario.


Configuration Guide


Issue 04 (2011-04-27)

VLANAttribute



ApplicationScenario

QinQVLAN

To configure QinQas the attribute of aVLAN, run thevlan attrib vlanidq-in-q command.


The packets from aQinQ VLANcontain two VLANtags, that is, innerVLAN tag fromthe private networkand outer VLANtag from theMA5612. Throughthe outer VLAN,an L2 VPN tunnelcan be set up totransparentlytransmit theservices betweenprivate networks.

Applicable to theenterprise privateline scenario.



5-5

VLANAttribute



ApplicationScenario

VLANStacking

To configurestacking as theattribute of aVLAN, run thevlan attrib vlanidstackingcommand.


The packets from astacking VLANcontain two VLANtags, that is, innerVLAN tag andouter VLAN tagfrom the MA5612.The upper-layerBRASauthenticates theaccess usersaccording to thetwo VLAN tags. Inthis manner, thenumber of accessusers is increased.On the upper-layernetwork in the L2working mode, apacket can beforwarded directlyby the outer VLANtag and MACaddress mode toprovide thewholesale servicefor ISPs.

Applicable to the1:1 access scenariofor the wholesaleservice orextension ofVLAN IDs.In the case of astacking VLAN, toconfigure the tag ofthe service port,run the stackinglabel command.You can run thestacking outer-ethertypecommand to set thetype of outerEthernet protocolsupported byVLAN stacking onthe MA5612. Youcan also run thestacking inner-ethertypecommand to set thetype of innerEthernet protocolsupported byVLAN stacking.To ensure thatHuawei device isinterconnectedwith the device ofother vendors, thetype of inner/outerEthernet protocolmust be the same asthat of theinterconnectdevice.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

l To configure attributes for the VLANs with consecutive IDs in batches, run the vlan attrib vlanid to end-vlanid command.

l To configure attributes for the VLANs with inconsecutive IDs in batches, run the vlan attrib vlan-listcommand.

Step 3 (Optional) Configure VLAN description.

To configure VLAN description, run the vlan desc command. You can configure VLANdescription to facilitate maintenance. The general VLAN description includes the usage andservice information of the VLAN.

Step 4 (Optional) Configure the VLAN forwarding policy.

vlan-connect corresponds to the S+C forwarding policy, which ensures higher security bysolving the problems of insufficiency in the MAC address space, MAC address aging, and MACaddress spoofing and attacks.

To configure the VLAN forwarding policy in the VLAN service profile, do as follows:

1. Run the vlan service-profile command to create a VLAN service profile and enter theVLAN service profile mode.

2. Run the forwarding command to configure the VLAN forwarding policy. The defaultVLAN forwarding policy is VLAN+MAC in the system.

3. Run the commit command to validate the profile configuration. The configuration of theVLAN service profile takes effect only after execution of this command.

4. Run the quit command to quit the VLAN service profile mode.5. Run the vlan bind service-profile command to bind the VLAN to the VLAN service profile

created in 4.1.

----End

ExampleAssume that a stacking VLAN with ID of 50 is to be configured for extension of the VLAN. Aservice port is added to VLAN 50. The outer VLAN tag 50 of the stacking VLAN identifies theaccess device and the inner VLAN tag 10 identifies the user with access to the device. For theVLAN, description needs to be configured for easy maintenance. To configure such a VLAN,do as follows:

huawei(config)#vlan 50 smart huawei(config)#vlan attrib 50 stackinghuawei(config)#service-port vlan 50 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6 tx-cttr 5huawei(config)#stacking label vlan 50 baselabel 10 huawei(config)#vlan desc 50 description stackingvlan/label10

Assume that a QinQ VLAN with ID of 100 is to be configured for an enterprise user to ensurehigher security and the VLAN forwarding policy is S+C. For the VLAN, description needs tobe configured for easy maintenance. To configure such a VLAN, do as follows:

huawei(config)#vlan 100 smart huawei(config)#vlan attrib 100 q-in-q huawei(config)#vlan desc 100 description qinqvlan/forhuawei huawei(config)#vlan service-profile profile-id 1huawei(config-vlan-srvprof-1)#forwarding vlan-connec Info: Please use the commit command to make modifications take effecthuawei(config-vlan-srvprof-1)#commit



5-7

huawei(config-vlan-srvprof-1)#quithuawei(config)#vlan bind service-profile 100 profile-id 1

5.2 Configuring the Upstream PortThis topic describes how to add the upstream port to a certain VLAN so that the user packetscarrying the VLAN ID can be transmitted to the upper-layer device through the upstream port.

Prerequisitel The MA5612 must be interconnected with the OLT.

l The VLAN must be configured on the MA5612. For detailed procedure, see ConfiguringA VLAN.

Procedure

Step 1 Add the upstream port to the VLAN.

Run the port vlan command to add the upstream port to the VLAN.

Step 2 (Optioal) Configure the attributes of the upstream port.

If the default attributes of the upstream port fail to meet the requirement for interconnecting theupstream port with the upper-layer device, you need to configure the attributes of the upstreamport. For detailed procedure, see 3.3 Configuring the Attributes of the Upstream Port.

----End

Example

To add upstream port 0/0/0 to VLAN 100, do as follows:

huawei(config)#port vlan { vlan-list<S><Length 1-256>|vlanid<1,4093> }:100{ frame/slot<S><Length 1-15>|to<K> }:0/0 { portlist<S><Length 1-256> }:0

Command: port vlan 100 0/0 0

5.3 Creating the Ethernet Access Service PortThe service port is used to connect the user side to the network side. To provision services, theservice port must be created.

Context

A service port can carry a single service or multiple services. When a service port on theMA5612 carries multiple services, the service streams can be classified as follows:

l By user-side VLAN

l By user-side service encapsulation mode

l By user-side packet priority


Configuration Guide


Issue 04 (2011-04-27)

Procedure

Step 1 Add a traffic profile.

Run the traffic table ip command to add a traffic profile. There are seven default traffic profilesin the system with the IDs of 0-6.

Before creating a service port, run the display traffic table command to check whether thetraffic profiles in the system meet the requirement. If no traffic profile in the system meets therequirement, add a traffic profile that meets the requirement.

Step 2 Create the service port.

You can create a single service port or multiple service ports in batches according torequirements.

l Run the service-port command to create a single service port.– Multi-service service port based on the user-side VLAN:

Select multi-service user-vlan { other-all | priority-tagged | untagged | user-vlanid }.– 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 is the same as the tag carried in user-side packets. The user-side VLANis the C-VLAN.

– priority-tagged: When priority-tagged is selected, the VLAN tag is 0 and thepriorities of user-side packets are 0-7.

– other-all: When other-all is selected, service ports of transparent LAN service(TLS) are created and are mainly used in the QinQ transparent transmission servicefor enterprises. All the traffic except known traffic in the system is carried on thischannel.

– By user-side packet priority (802.1p)Select multi-service user-8021p user-8021p.

– By user-side service encapsulation modeSelect multi-service user-encap user-encap.

NOTE

l The system supports creating service ports by index. One index maps one service port and the inputof a large number of traffic parameters is not required. Thus, the configuration of service ports issimplified. During the creation of a service port, index indicates the index of the service port and it isoptional. If you do not specify the index, the system automatically adopts the smallest idle index.

l vlan indicates the S-VLAN. An S-VLAN can only be a MUX VLAN or smart VLAN.

l rx-cttr is the same as outbound in terms of meanings and functions. Either of them indicates the indexof the traffic profile from the network side to the user side. tx-cttr is the same as inbound in terms ofmeanings and functions. Either of them indicates the index of the traffic profile from the user side tothe network side.

l Run the multi-service-port command to create service ports in batches.

Step 3 (Optional) Configure the attributes of the service port.

Run the service-port desc command to configure the description of the service port. To facilitatemaintenance, you can add information such as the function of the service port.

----End



5-9

ExampleAssume that the access service port is 0/1/1, the user-side VLAN is 2, the upstream port is0/0/0, and the upstream VLAN is 100; the traffic profile 8 is used, the specified profile name ishuawei, the CIR is 10240; the upstream priority is specified to 0, and packet priority policy isbased on the traffic profile that is scheduled according to the local priority setting. To configurea service port for Internet access service in Ethernet access mode, do as follows:

huawei(config)#traffic table ip{ cir<K>|index<K>|modify<K>|name<K> }:index{ row-index<0,127> }:8{ cir<K>|name<K> }:name{ name<S><Length 1-32> }:huawei{ cir<K> }:cir{ cir<64,524288>|off<K> }:10240{ cbs<K>|color-mode<K>|pbs<K>|pir<K>|priority<K> }:priority{ prival<0,7>|user-cos<K>|user-inner-cos<K>|user-tos<K> }:0{ inner-priority<K>|priority-policy<K> }:priority-policy{ priority-policy<E><Local-Setting,Tag-In-Package> }:local-Setting

Command: traffic table ip index 8 name net cir 10240 priority 0 priority-policy local-setting Create traffic descriptor record successfully ------------------------------------------------ TD Index : 8 TD Name : net Priority : 0 Copy Priority : - CTAG Mapping Priority: - CTAG Default Priority: 0 Priority Policy : local-pri CIR : 10240 kbps CBS : 329680 bytes PIR : 20480 kbps PBS : 657360 bytes Color Mode : color-blind Referenced Status : not used ------------------------------------------------

huawei(config)#service-port{ desc<K>|index<0,255>|remote-desc<K>|vlan<K> }:1{ adminstatus<K>|inbound<K>|outbound<K>|vlan<K> }:vlan{ transparent<K>|vlanid<1,4093> }:100{ eth<K> }:eth{ frameid/slotid/portid<S><Length 1-15> }:0/1/1{ multi-service<K> }:multi-service{ user-8021p<K>|user-encap<K>|user-vlan<K> }:user-vlan{ other-all<K>|priority-tagged<K>|untagged<K>|user-vlanid<1,4094> }:2{ bundle<K>|inbound<K>|rx-cttr<K> }:rx-cttr{ rx-index<0,63> }:8{ tx-cttr<K> }:tx-cttr{ tx-index<0,63> }:8

Command: service-port 1 vlan 2 eth 0/1/1 multi-service user-vlan 2 rx-cttr 8 tx-cttr 8


Configuration Guide


Issue 04 (2011-04-27)

6 Configuring the Multicast Service (MulticastVLAN Mode)

About This Chapter

This topic describes how to configure the multicast service on the MA5612 in multicast VLANmode.

6.1 Default Settings of the Multicast ServiceThis topic provides the default settings of the multicast service in the system, including theconfiguration of multicast protocol, IGMP version, program configuration mode, bandwidthmanagement, program preview, and log function.

6.2 Configuring the Multicast Service on a Single-NE NetworkThis topic describes how to configure the multicast service on a standalone MA5612.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 6 Configuring the Multicast Service (Multicast VLAN Mode)


6-1

6.1 Default Settings of the Multicast ServiceThis topic provides the default settings of the multicast service in the system, including theconfiguration of multicast protocol, IGMP version, program configuration mode, bandwidthmanagement, program preview, and log function.

Table 6-1 lists the default settings of the multicast service of the MA5612.

Table 6-1 Default settings of the multicast service

Feature Default Setting

Multicast protocol Off

IGMP version V3

Configuration mode of the multicastprogram

Configured statically

Multicast bandwidth management Enabled

Multicast preview Enabled

Multicast log function Enabled

6.2 Configuring the Multicast Service on a Single-NENetwork

This topic describes how to configure the multicast service on a standalone MA5612.

Service RequirementsThe multicast function of the MA5612 is used for multicast video services, such as live TV andnear-video on demand (NVOD). The MA5612 runs the IGMP proxy or IGMP snooping protocol,and the interconnected device can run the IGMP proxy, IGMP snooping, or multicast routerprotocol.

Currently, the multicast application of the MA5612 is oriented to L2, and the MA5612 forwardsdata based on VLAN ID + multicast MAC address. A multicast program on the network isuniquely identified by VLAN ID + multicast IP address. The MA5612 differentiates multicastsources by VLAN ID. It allocates a unique VLAN ID to each multicast source, controls themulticast domain and user rights based on the multicast VLAN ID, and provides a platform fordifferent ISPs to implement different multicast video services.

PrerequisiteThe license for the multicast program or multicast user must be applied for and installed.

Data PlanBefore configuring the multicast video service, plan the data items as listed in Table 6-2.

6 Configuring the Multicast Service (Multicast VLAN Mode)SmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

Table 6-2 Data plan for configuring the multicast service on a standalone MA5612

Device Item Remarks

MA5612 Multicast VLAN Generally, a multicast VLAN is allocatedto each multicast ISP.

L2 multicast protocol IGMP proxy and IGMP snooping aresupported.

IGMP version IGMP V3 and IGMP V2 are supported andIGMP V3 is compatible with IGMP V2.

Configuration mode of themulticast program

The multicast program can be configuredstatically or generated dynamically.

Multicast general query andgroup-specific queryparameters

The default values are adopted.

Program list -

User authentication policy -

Program bandwidth, uplinkport bandwidth, and userbandwidth

-

Multicast log policy Multicast logs can be reported to the logserver in syslog mode or in CDR mode.

Upper-layermulticast router

IGMP version The IGMP version of the upper-layermulticast router cannot be earlier than theIGMP version used by the MA5612.

Home gatewayor modem

IGMP version The IGMP version of the CPE cannot beearlier than the IGMP version used by theMA5612.

Procedure

----End

1. 6.2.1 Configuring Global Multicast ParametersThe general parameters of L2 multicast protocols (including IGMP proxy and IGMPsnooping) configured globally for a device are applicable to all the multicast VLANs ofthe device.

2. 6.2.2 Configuring the Multicast ProgramA multicast program can be configured statically or generated dynamically. After theprogram is configured, the multicast user with the corresponding rights can watch orpreview the program.

3. 6.2.3 Configuring the Multicast User



6-3

When a user needs to watch the multicast program, you need to configure the user as amulticast user because only a multicast user can watch the multicast program.

4. 6.2.4 (Optional) Configuring the Multicast BandwidthTo limit the multicast bandwidth of a user, you can enable the multicast bandwidthmanagement function, namely, connection admission control (CAC), and then control thebandwidth of the multicast user by setting the program bandwidth and the user bandwidth.

5. 6.2.5 (Optional) Configuring the Multicast PreviewMulticast preview is an advertising method provided by carriers for ISPs. The purpose isto allow users to have an overview of a program so that the user can determine whether torequest for the program. The MA5612 can control the duration, interval, and count of userpreviews through the configuration of the multicast preview.

6. 6.2.6 (Optional) Configuring the Program PrejoinIn program prejoin, the MA5612 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. Inthis manner, the multicast stream can be directly transmitted from the uplink port to theuser port after the multicast user requests for a program, thus shortening the waiting timeof the user for requesting for the program.

7. 6.2.7 (Optional) Configuring the Multicast LogThis topic describes how to configure the multicast log. Multicast log records theinformation about multicast programs watched by the multicast user, which provides acriterion for carriers to evaluate the viewership of multicast programs. The MA5612 canreport the multicast log to the multicast server.

6.2.1 Configuring Global Multicast ParametersThe general parameters of L2 multicast protocols (including IGMP proxy and IGMP snooping)configured globally for a device are applicable to all the multicast VLANs of the device.

ContextGlobal multicast parameters include general query, group-specific query, and policy ofprocessing multicast packets.

For the general query:

l Purpose: A general query packet is periodically sent by the MA5612 to check whether thereis any multicast user who leaves the multicast group without sending the leave packet.Based on the query result, the MA5612 periodically updates the multicast forwarding tableand releases the bandwidth of the multicast user who has left the multicast group in time.

l Principles: The MA5612 periodically sends the general query packet to all the online IGMPusers. If the MA5612 does not receive the response packet from a multicast user within aspecified time (robustness variable x interval of the general query + maximum responsetime of the general query), it regards the user as having left the multicast group and deletesthe user from the multicast group.

For the group-specific query:

l Purpose: A group-specific query packet is sent by the MA5612 after a multicast user whois not configured with the quick leave attribute sends the leave packet. The group-specificquery packet is used to check whether the multicast user has left the multicast group.

l Principles: When a multicast user leaves a multicast group, for example, switches to anotherchannel, the user sends a leave packet to the MA5612 in an unsolicited manner. If themulticast user is not configured with the quick leave attribute, the MA5612 sends a group-


Configuration Guide


Issue 04 (2011-04-27)

specific query packet to the multicast group. If the MA5612 does not receive the responsepacket from the multicast user within a specified time (robustness variable x interval of thegroup-specific query + maximum response time of the group-specific query), it deletes themulticast user from the multicast group.

Procedure

Step 1 In global config mode, run the btv command to enter BTV mode.

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 group-

specific 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, thatis, IGMP packets are processed under control. The discard mode is adopted for unknownmulticast 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 policyof 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 configuredcorrectly.

----End

ExampleTo configure multicast general query parameters by setting the query interval to 150s, maximumresponse time to 20s, and query count to 3, do as follows:

huawei(config)#btvhuawei(config-btv)#igmp proxy router gen-query-interval 150huawei(config-btv)#igmp proxy router gen-response-time v3 200huawei(config-btv)#igmp proxy router robustness 3

To configure multicast group-specific query parameters by setting the query interval to 20s,maximum response time to 10s, and query count to 3, do as follows:

huawei(config)#btvhuawei(config-btv)#igmp proxy router sp-query-interval 200huawei(config-btv)#igmp proxy router sp-response-time v3 100huawei(config-btv)#igmp proxy router sp-query-number 3



6-5

ResultCheck whether the multicast general query parameters and group-specific query parameters areconfigured correctly.

huawei(config)#btvhuawei(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 V3 General query response time(0.1s) : 200 //The maximum response time of the general query is 20s. Specific query interval(0.1s) : 200 //The interval of the group-specific query is 10s. V2 Specific query response time(0.1s) : 8 V3 Specific query response time(0.1s) : 100 //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 : - BTV Forward Mode : Mvlan ----------------------------------------------------------------------

6.2.2 Configuring the Multicast ProgramA multicast program can be configured statically or generated dynamically. After the programis configured, the multicast user with the corresponding rights can watch or preview the program.

PrerequisiteThe multicast VLAN to which the multicast program belongs must exist.

ContextIn multicast services, multicast VLANs are used to identify different multicast Internet serviceproviders (ISPs). Generally, a multicast VLAN is allocated to each multicast ISP for the VLAN-based management of multicast programs, multicast protocols, and IGMP versions, and for thecontrol 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.


Configuration Guide


Issue 04 (2011-04-27)

l A multicast VLAN can be different from a unicast VLAN. In this case, the multicast VLANand the unicast VLAN use different traffic channels.

Procedure

Step 1 Configure multicast programs.A multicast program in a multicast VLAN can be configured statically or generated dynamically.l Static configuration mode: Configure the program list for the multicast VLAN in advance

and bind the rights profile to the program to manage the programs.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 [ sourceipip-addr ] [ hostip ip-addr ] command to add a multicast program.

NOTE

If the IGMP version of the multicast VLAN is V3, the source IP address of the program in the multicastVLAN must be configured. If the IGMP version of the multicast VLAN is V2, the source IP addressof 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 andset 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 theseprofiles, the user uses the rights with the highest priority. You can run the igmp right-prioritycommand 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.

l Dynamic generation mode: A program is generated according to the request of the user. Inthis mode, the program list is not required; however, the functions such as programmanagement, user multicast bandwidth management, program preview, and programprejoin are not supported.

1. Run the igmp match mode disable command to configure the dynamic generation mode.

CAUTIONWhen you run the igmp match mode { enable | disable } command to switch the programmatching mode:l This command can be executed only when the IGMP mode is disabled.l The system will delete all the programs in this multicast VLAN. In this case, if a user

is online, the system will force the user to go offline.

2. Run the igmp match group command to configure the IP address range of the programgroup 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 specifiedrange.



6-7

Step 2 Configure the multicast uplink port.

1. In multicast VLAN mode, run the igmp uplink-port command to configure the multicastuplink port. After the configuration, all the packets from the multicast VLAN are forwardedor received through this uplink port.

2. In BTV mode, run the igmp uplink-port-mode command to change the mode of themulticast uplink port. By default, the multicast uplink port is in default mode. On the MSTPnetwork, the multicast uplink port adopts the MSTP mode.

l Default mode: If a multicast VLAN contains only one uplink port, the IGMP packetsthat go upstream can be sent only through this port. If a multicast VLAN containsmultiple uplink ports, the IGMP packets that go upstream are sent through all the uplinkports.

l MSTP mode: This mode is applicable to the MSTP network.

Step 3 Select the multicast protocol.

Run the igmp mode { proxy | snooping } command to select the L2 multicast protocol. Bydefault, the multicast function is disabled in the system.

In IGMP snooping mode, proxy can be enabled for the report packet and leave packet. When amulticast user joins or leaves a multicast program, the MA5612 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 reportpacket. When the first user requests for a program, after authenticating the user, theMA5612 sends the user report packet to the network side and obtains a correspondingmulticast stream from the multicast router. The MA5612 does not send the report packetsfrom 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 leavepacket. When the last user requests for leaving a program, the MA5612 sends the user leavepacket to the network side and notifies the upper-layer device of stopping sending multicaststreams. The MA5612 does not send the leave packets from the users before the last user tothe 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 ofthe IGMP V2 version and cannot recognize the IGMP V3 packets, run this command to switchthe IGMP version.

IGMP V3 is compatible with IGMP V2 in packet processing. If IGMP V3 is enabled on theMA5612 and the upper-layer multicast router switches to IGMP V2, the MA5612 automaticallyswitches to IGMP V2 when receiving the IGMP V2 packets. If the MA5612 does not receiveany IGMP V2 packets within the preset IGMP V2 time to live (TTL) time, it automaticallyswitches back to IGMP V3. In BTV mode, run the igmp proxy router timeout command to setthe IGMP V2 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 theuplink 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 throughthe igmp priority command in the multicast VLAN.


Configuration Guide


Issue 04 (2011-04-27)

l In IGMP snooping mode, the IGMP packets forwarded to the network side adopt the priorityof 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

ExampleAssume that the VLAN ID is 10, the program is configured statically, the IP address of theprogram is 224.1.1.1, the program bandwidth is 5000 kbit/s, the multicast uplink port is 0/0/0,the IGMP proxy is enabled, and the IGMP version is V3. To configure a program with theseattributes, do as follows:

huawei(config)#vlan 10 smart huawei(config)#multicast-vlan 10 huawei(config-mvlan10)#igmp match mode enable This operation will delete all the programs in current multicast vlan Are you sure to change current match mode? (y/n)[n]: y Command is being executed, please wait... Command has been executed successfully 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/0 huawei(config-mvlan10)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y Command has been executed successfullyhuawei(config-mvlan10)#igmp version v3 This operation will delete all programs in current multicast vlan Are you sure to change current IGMP version? (y/n)[n]: y

Assume that the VLAN ID is 10, the program is generated dynamically, the multicast uplinkport is 0/0/0, the IGMP proxy is enabled, and the IGMP version is V3. To configure a programwith these attributes, do as follows:

huawei(config)#vlan 10 smarthuawei(config)#multicast-vlan 10huawei(config-mvlan10)#igmp match mode disable This operation will delete all the programs in current multicast vlan Are you sure to change current match mode? (y/n)[n]: y Command is being executed, please wait... Command has been executed successfully huawei(config-mvlan10)#igmp uplink-port 0/0/0huawei(config-mvlan10)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y Command has been executed successfullyhuawei(config-mvlan10)#igmp version v3 This operation will delete all programs in current multicast vlan Are you sure to change current IGMP version? (y/n)[n]: y

ResultQuery the attributes and information of the program in the multicast VLAN in staticconfiguration mode.

huawei(config)#display igmp config vlan 10 ----------------------------------------------------------------------



6-9

IGMP mode : proxy //IGMP proxy protocol IGMP version : IGMP V3 //IGMP V3 Log switch : enable Default uplink port : - Report proxy switch : disable Leave proxy switch : disable Unsolicited report interval(s) : 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 : - ---------------------------------------------------------------------- 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 : - ---------------------------------------------

Query the attributes and information of the program in the multicast VLAN in dynamicgeneration 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 Leave proxy switch : disable Unsolicited report interval(s) : 10 IGMP priority : 6 Send global leave switch : enable Program match mode : disable //The program matching mode is disabled and the multicast program is generated dynamically. Program match group : - ----------------------------------------------------------------------

6.2.3 Configuring the Multicast UserWhen a user needs to watch the multicast program, you need to configure the user as a multicastuser because only a multicast user can watch the multicast program.

PrerequisiteBefore configuring a user as a multicast user, you must create a service channel and ensure thatthis channel is normal.


Configuration Guide


Issue 04 (2011-04-27)

For an Ethernet user, you must perform the following operations:

1. 3.4 Configuring a VLAN2. 5.2 Configuring the Upstream Port3. 5.3 Creating the Ethernet Access Service Port

ContextAdd a multicast user and bind the multicast user with the multicast VLAN to create a multicastmember. Bind the rights profile to the multicast user to implement multicast user authentication.

Procedure


Step 2 Configure the multicast user and the multicast user attributes.

1. Add a multicast user.

Run the igmp user add service-port index command to add a multicast user.

NOTE

You can run the display service-port command to query the index of the traffic stream of the multicastuser to be added.

2. Configure the maximum number of programs that can be watched by the multicast user.l Run the igmp user add service-port index max-program command to configure the

maximum number of programs that can be concurrently watched by the multicast user.The maximum number is 16.

Run the igmp user watch-limit command to configure the maximum number of programsof 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 service-port index quickleave { immediate | disable | mac-based } command to configure the leave mode of the multicast user. By default, the leavemode 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 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 receivethe report packet of the multicast user, the user is considered as offline and the systemdeletes the multicast user from the multicast group.

l mac-based: Indicates the quick leave mode based on the MAC address. The systemdetects the MAC address in the leave packet of the user. If it is the same as the MACaddress in the report packet of the user and the user is the last one who watches themulticast program in the multicast group, the system immediately deletes the multicastuser from the multicast group. Otherwise, the system does not delete the multicast user.In this mode, the application scenario with multiple terminals is supported.

Step 3 Configure the multicast user authentication.

To control the rights of a multicast user, you can enable the multicast user authenticationfunction. Binding the rights profile to the multicast user implements multicast userauthentication.



6-11

1. Configure the multicast user authentication function.

Run the igmp user add service-port index { auth | no-auth } command to configurewhether to authenticate a multicast user.

NOTEAfter configuring multicast user authentication, you need to enable the global authentication function tomake the configuration take effect. By default, the global authentication function of multicast user isenabled. 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 userimplements 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 tothe multicast VLAN. Then, the multicast user becomes a multicast member of the multicastVLAN 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

ExampleAssume that multicast user (port) 0/4/1 (with an index of the user traffic stream 100) is addedto multicast VLAN 10, the user authentication and the log report function are enabled, themaximum number of programs that can be concurrently watched is 4, and rights profile musicis bound to the user. To perform the configurations, do as follows:huawei(config)#btvhuawei(config-btv)#igmp user add service-port 100 auth log enable max-program 4huawei(config-btv)#igmp user bind-profile service-port 100 profile-name musichuawei(config-btv)#quithuawei(config)#multicast-vlan 10huawei(config-mvlan10)#igmp multicast-vlan member service-port 100

ResultCheck whether the multicast user is configured correctly.huawei(config)#display igmp user 0 //0 is the index of the multicast user. You can run the display igmp user command to query the index of the multicast user.{ <cr>||<K> }: Command: display igmp user 0 User : 0/4/1 //Port of the multicast user State : offline Authentication : auth //Authentication is required. Quick leave : MAC-based IGMP flow ID : 100 Video flow ID : 100 Log switch : enable Bind profiles : 1 IGMP version : IGMP v3 Available programs : 4 //The maximum number of programs that can be concurrently watched is 4. Global Leave : disable User MaxBandWidth : no-limit Used bandwidth(kbps) : 0


Configuration Guide


Issue 04 (2011-04-27)

Used bandwidth to max bandwidth(%) : - Total video bandwidth : - Mcast video bandwidth : - Bind profile list --------------------------------------------- index Profile name Program number --------------------------------------------- 0 music 0 //The bound rights profile is music. --------------------------------------------- Total: 1

6.2.4 (Optional) Configuring the Multicast BandwidthTo limit the multicast bandwidth of a user, you can enable the multicast bandwidth managementfunction, namely, connection admission control (CAC), and then control the bandwidth of themulticast user by setting the program bandwidth and the user bandwidth.

Prerequisite

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 isenabled, and a user requests for a multicast program, the system compares the remainingbandwidth of the user (bandwidth configured for the user - total bandwidth of the online programsof the user) with the bandwidth of the multicast program. The system determines whether theuser 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.l 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 multicastprogram. In this case, the picture quality of the requested program is poor. For example, mosaicand delay occur.

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.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.



6-13

l Before configuring the bandwidth of the multicast user, ensure that the service port of themulticast user exists. You can run the display service-port command to query the serviceport.

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

ExampleAssume that the CAC function is enabled globally, the bandwidth of multicast user 0/4/1 is 10Mbit/s, and the bandwidth of the multicast program with IP address 224.1.1.1 is 1 Mbit/s. Toperform the configurations, do as follows:huawei(config)#btvhuawei(config-btv)#igmp bandwidthcAC enablehuawei(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 10huawei(config-mvlan10)#igmp program add ip 224.1.1.1 bandwidth 1024

ResultCheck whether the bandwidths of the multicast user and multicast program are configuredcorrectly.l Check whether the bandwidth of the multicast user is configured correctly.

huawei(config)#display igmp user all { <cr>||<K> }: Command: 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 { all<K>|extended-attributes<K>|user-index<0,191> }:0 //0 is the index of the multicast user queried in the preceding part.{ <cr>||<K> }:


Configuration Guide


Issue 04 (2011-04-27)

Command: display igmp user 0 User : 0/4/1 State : offline 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 : 8 Global Leave : disable User MaxBandWidth : 10240 //The bandwidth of the multicast user is 10 Mbit/s. Used bandwidth(kbps) : 0 Used bandwidth to max bandwidth(%) : 0.00 Total video bandwidth : - Mcast video bandwidth : -

l Check whether the bandwidth of the multicast program is configured correctly.huawei(config)#display igmp program all { <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) Note : # The program data is valid, but it is no license. huawei(config)#display igmp program index 0 <cr>||<K> }: Command: display igmp program index 0



6-15

--------------------------------------------- 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 Unsolicited attribute : 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 : - ---------------------------------------------

6.2.5 (Optional) Configuring the Multicast PreviewMulticast preview is an advertising method provided by carriers for ISPs. The purpose is to allowusers to have an overview of a program so that the user can determine whether to request for theprogram. The MA5612 can control the duration, interval, and count of user previews throughthe configuration of the multicast preview.

Prerequisite

The program matching mode of the multicast VLAN must be the static configuration mode.

Context

Multicast preview is an advertising method provided by carriers for ISPs. The purpose is to allowusers to have an overview of a program so that the user can determine whether to request for theprogram. To protect the legitimate interests of ISPs, the duration, interval, and count of userpreviews need to be controlled. The MA5612 controls the program preview of the user throughthe configuration of the multicast preview.

l Preview duration: After a user with the preview rights goes online, the user can watch theprogram that can be previewed but the user is restricted by the preview duration. When thepreview time expires, the user will go offline.

l Preview interval: When the preview time expires, the user who is previewing a multicastprogram will go offline. The user can request for the program again only after the configuredpreview interval expires.


Configuration Guide


Issue 04 (2011-04-27)

l Preview count: Refers to the count of program previews that a user can request for amulticast program in a period of 24 hours (the start time can be set). If the preview countreaches the configured preview count, the user cannot preview the program.

The multicast preview function is implemented through the binding of the preview profile to themulticast program.

NOTE

One multicast program can be bound with only one preview profile, but one preview profile can be referencedby multiple multicast programs.

Procedure


Step 2 Enable the multicast preview function globally.

NOTE

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 cannotbe deleted.

Step 4 Bind the multicast program with the preview profile.

In multicast VLAN mode, run the igmp program add ipip-addrpreview-profileindexcommand to bind the preview profile to the multicast program so that the multicast program hasthe 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 previewrecord. 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 multicastpreview. If the preview duration of the user is shorter than the valid duration, the preview is notregarded as a valid one and is not added to the preview count.

By default, the valid duration of the multicast preview is 30s.

----End

ExampleAssume that the preview function of the multicast program is enabled, preview profile 1 isconfigured, the maximum preview duration is 150s, the maximum preview count is 10, thispreview profile is used when program 224.1.1.1 is added, and other parameters use the defaultvalues. To perform the configurations, do as follows:



6-17

huawei(config)#btvhuawei(config-btv)#igmp preview enablehuawei(config-btv)#igmp preview-profile add index 1 duration 150 times 10huawei(config-btv)#quithuawei(config)#multicast-vlan 10huawei(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.

l Check whether the preview function of the multicast program is enabled.huawei(config)#display igmp config global ---------------------------------------------------------------------- Authorization : enable Robustness variable : 2 General query interval(s) : 125 V2 General query response time(0.1s) : 100 V3 General query response time(0.1s) : 100 Specific query interval(0.1s) : 10 V2 Specific query response time(0.1s) : 8 V3 Specific query response time(0.1s) : 8 Specific query number : 2 V2 router present timeout(s) : 400 User action report switch : disable Preview switch : enable //The multicast preview function is enabled. 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 : - BTV Forward Mode : Mvlan ----------------------------------------------------------------------


Configuration Guide


Issue 04 (2011-04-27)

l 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

l Query the preview profile bound to the multicast program.huawei(config)#display igmp program all { <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) Note : # The program data is valid, but it is no license.

The queried program index is 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 Unsolicited attribute : disable Priority : 7 Host IP : 0.0.0.0 Bandwidth(kbps) : 5000 SourceIP :



6-19

- Preview Profile : 1 //The index of the preview profile bound to the multicast program is 1. Numbers of watching : 0 Program Grade : - ---------------------------------------------

6.2.6 (Optional) Configuring the Program PrejoinIn program prejoin, the MA5612 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 thismanner, the multicast stream can be directly transmitted from the uplink port to the user portafter the multicast user requests for a program, thus shortening the waiting time of the user forrequesting for the program.

PrerequisiteThe program matching mode of the multicast VLAN must be the static configuration mode.

ContextMulticast program prejoin is the same as program request. The MA5612 plays the role of a userand sends the report packet for receiving in advance the multicast stream from the upper-layermulticast router to the uplink port.

After the prejoin function is enabled, if the upper-layer multicast router does not support staticmulticast entry forwarding, you need to enable the unsolicited report function of IGMP packetsso that the user can request for the program quickly. Generally, the upper-layer multicast routerprocesses the user request by responding to the group-specific query and the general query.

ProcedureStep 1 Enable the program prejoin function.

Run the igmp program add ip ip-addr prejoin enable command to enable the program prejoinfunction.

By default, this function is disabled.

Step 2 After the program prejoin function is enabled, if the upper-layer multicast router does not supportstatic multicast entry forwarding, you need to enable the unsolicited report function of IGMPpackets.

l Run the igmp program add ip ip-addr unsolicited enable command to enable theunsolicited 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 unsolicitedreport 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 functionand unsolicited report function.

l Run the display igmp config vlan command to query the interval of the unsolicited reportof IGMP packets.

----End


Configuration Guide


Issue 04 (2011-04-27)

Example

To enable the program prejoin function when adding a program whose IP address is 224.1.1.1,do as follows:huawei(config)#multicast-vlan 10huawei(config-mvlan10)#igmp program add ip 224.1.1.1 prejoin enable

Result

Query the status of the program prejoin function and unsolicited report function.huawei(config)#display igmp program all { <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) Note : # The program data is valid, but it is no license. The queried program index is 0.huawei(config)#multicast-vlan 10huawei(config-mvlan10)#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 : enable //The program prejoin function is enabled. Unsolicited attribute : disable //The unsolicited report function of IGMP packets are disabled. Priority : 7 Host IP : 0.0.0.0 Bandwidth(kbps) : 5000 SourceIP : - Preview Profile : 0 Numbers of watching : 0 Program Grade : - ---------------------------------------------

6.2.7 (Optional) Configuring the Multicast LogThis topic describes how to configure the multicast log. Multicast log records the informationabout multicast programs watched by the multicast user, which provides a criterion for carriersto evaluate the viewership of multicast programs. The MA5612 can report the multicast log tothe multicast server.

Prerequisite

The communication between the MA5612 and the multicast log server must be normal.



6-21

ContextThe multicast log involves the multicast log of the multicast VLAN, multicast user, and multicastprogram. 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 generateslogs in any of the following conditions:l The user goes offline naturally, forcibly, or abnormally.l The user is blocked or deleted.l The program is deleted.l The priority of the program is changed.l The uplink port to which the program is bound is changed.l The VLAN of the uplink port to which the program is bound is changed.l The user preview times out.l The rights mode is switched.l The IGMP mode is switched.l The bandwidth CAC fails.

The system supports a maximum of 32 k (1 k = 1024) logs. When the user goes online, the systemrecords only the online date and time. The system generates a complete log only when the usergoes offline.

The MA5612 can report the multicast log to the log server in syslog mode or in call detailedrecord (CDR) mode. By default, the MA5612 reports the log in syslog mode.l syslog mode: Logs are reported to the syslog server in the form of a single log.l CDR mode: Logs are reported to the log server in the form of a log file (.cvs). One log file

contains multiple logs.

Procedurel Configure the parameters of the multicast log generation function of the MA5612.

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 allthe multicast VLAN, multicast user, and multicast program are enabled. By default,the log functions of all the multicast VLAN, multicast user, and multicast programare 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 multicastprogram.

2. Change the interval of automatic log generation.

In BTV mode, run the igmp proxy log-interval command to change the interval ofautomatic log generation.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

When the user stays online for a long time, the system generates logs at preset intervals. This preventsthe problem that a log is not generated when the user leaves the multicast group without sending theleave 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 theminimum 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 operationis not regarded as a valid one and a log is not generated. A log is generated only whena user stays online for longer than the specified duration. By default, the duration is30s.

l Configure the multicast log report function in CDR mode.

1. Configure the multicast log server and the data transmission mode for the multicastlog report in CDR mode.

Run the file-server auto-backup cdr command to configure the active and standbymulticast 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 statusof the multicast log report function in CDR mode.

– After the multicast log report function in CDR mode is enabled, the MA5612reports 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 MA5612reports 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 ofthe multicast log report in CDR mode. By default, the interval is 600s.

– In BTV mode, run the igmp cdr-number command to configure the maximumnumber of logs that can be reported in CDR mode each time. When the number ofmulticast logs in the CDR file reaches the preset value, the MA5612 reports thelogs. 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 multicastlog server for receiving the multicast log reported in CDR mode.

– Run the display igmp config global command to query the status and otherparameters 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 logserver) in CDR mode through TFTP transmission, do as follows:huawei(config)#file-server auto-backup cdr primary 10.10.10.10 tftphuawei(config)#btvhuawei(config-btv)#igmp cdr enable



6-23

ResultQuery the configuration of the multicast log server for receiving the multicast log reported inCDR mode.huawei(config)#display file-server auto-backup cdr ------------------------------------------------------------------------------ Server type: Primary Trans mode : TFTP //The transmission mode of the multicast log is TFTP. IP address : 10.10.10.10 //The IP address of the multicast log server is 10.10.10.10. ------------------------------------------------------------------------------ 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 General query interval(s) : 125 V2 General query response time(0.1s) : 100 V3 General query response time(0.1s) : 100 Specific query interval(0.1s) : 10 V2 Specific query response time(0.1s) : 8 V3 Specific query response time(0.1s) : 8 Specific query number : 2 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 : enable //The multicast log report in CDR mode is enabled. IGMP Packet encapsulation : all IGMP ECHO switch : disable Router IP : 192.168.1.1 Initial unsolicited report interval(s): 1 Query offline user switch : - BTV Forward Mode : Mvlan ----------------------------------------------------------------------


Configuration Guide


Issue 04 (2011-04-27)

7 Configuring the Voice Service

About This Chapter

The MA5612 supports user access through copper cables to provide the voice service.

Context

The MA5612 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.248protocol, and provides the voice service under the control of the MGC.

l The system communicates with the IP multimedia subsystem (IMS) core network devicethrough the SIP protocol to provide the voice service.

The MA5612 supports the following services:

l Voice over IP (VoIP) serviceSupports the voice over IP service through the H.248 or SIP protocol.

l VoIP integrated services digital network (ISDN) primary rate access (PRA) serviceSupports the ISDN PRA over IP service through the H.248 or SIP protocol.

l Fax over IP (FoIP) serviceSupports the fax over IP service through the H.248 or SIP protocol.

l Modem over IP (MoIP) serviceSupports the modem over IP service through the H.248 or SIP protocol.

To ensure the normal voice service, the MA5612 supports the following security and reliabilityconfigurations:

l Device authenticationSupports authentication of the MG interface through the H.248 protocol and authenticationof the SIP interface through the SIP protocol.

l Emergency standaloneSupports emergency standalone of the MG interface through the H.248 protocol.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 7 Configuring the Voice Service


7-1

l Dual homingSupports dual homing from the MG to the MGC through the H.248 protocol andauthentication from the SIP AG to the SIP proxy server through the SIP protocol.

NOTE

In this document, the MG, AG, gateway, or SIP AG refers to the MA5612, unless otherwise stated.

7.1 Configuring the VoIP PSTN Service (Based on the H.248 Protocol)This topic describes how to configure the VoIP PSTN service on the MA5612 when the H.248protocol is used.

7.2 Configuring the VoIP PSTN Service (Based on the SIP Protocol)This topic describes how to configure the VoIP PSTN service on the MA5612 through theSession Initiation Protocol (SIP).

7.3 Configuring the VoIP ISDN PRA Service (Based on the H.248 Protocol)This topic describes how to configure the VoIP ISDN PRA service on an IP network. When theMA5612 uses the H.248 protocol, the device supports the access of the ISDN PRA user. ISDNprovides end-to-end (E2E) digital connection and supports multiple types of voice and non-voicetelecom services.

7.4 Configuring the VoIP ISDN PRA Service (Based on the SIP Protocol)After configuring the SIP interface, you can add VoIP ISDN PRA users on this interface toimplement the VoIP ISDN PRA service.

7.5 Configuring the FoIP Service (Based on the H.248 Protocol)This topic describes how to configure the FoIP service when the H.248 protocol is used totransmit the fax data service over the IP network.

7.6 Configuring the FoIP Service (Based on the SIP Protocol)This topic describes how to configure the FoIP service based on the SIP protocol to transmit thefax data service over the IP network.

7.7 Configuring the MoIP Service (Based on the H.248 Protocol)This topic describes how to configure the MoIP service when the H.248 protocol is used totransmit the modem data service over the IP network.

7.8 Configuring the MoIP Service (Based on the SIP Protocol)This topic describes how to configure the MoIP service when the SIP protocol is used to transmitthe modem data service over the IP network.

7.9 Configuring the Security and Reliability of the Voice ServiceFor the MA5612, the security configuration of the voice service includes the H.248-based, orSIP-based device authentication configuration. The reliability configuration of the voice serviceincludes the dual-homing configuration and the emergency standalone configuration.

7 Configuring the Voice ServiceSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

7.1 Configuring the VoIP PSTN Service (Based on the H.248Protocol)

This topic describes how to configure the VoIP PSTN service on the MA5612 when the H.248protocol is used.

ContextThe voice over IP (VoIP) service uses the IP packet switching network for transmission afterthe traditional analog voice signals are compressed and packetized, to reduce the cost of thevoice service.

For details about the VoIP service, see Voice in the Feature Description.

In the NGN network, the MA5612 functions as an access gateway (AG) and exchanges signalingwith 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 thecontrol of the MGC. The MG interface, as an interface for the communication between theMA5612 (AG) and the MGC, plays a decisive role in the VoIP service based on the H.248protocol. Therefore, to implement the VoIP service, the MG interface must be configured andmust be in the normal state.

H.248, also called MeGaCo, is a protocol developed based on the MGCP protocol by combiningthe features of other media gateway control protocols. Compared with the MGCP protocol, theH.248 protocol supports more types of access technologies and supports mobility of terminals.The configuration of the VoIP service based on the H.248 protocol is the same as theconfiguration of the VoIP service base on the MGCP protocol.

PrerequisiteAccording to the actual network, a route from the MA5612 to the MGC must be configured toensure that the MA5612 and the MGC are reachable to each other.

PrecautionThe media gateway control protocols are master/slave protocols, and the MGC controls the AGto implement the call connection. Therefore, the data on the AG for interconnection with theMGC, including the attributes of the MG interface and the attributes of the VoIP user, must beconsistent with the corresponding data on the MGC. Before configuring the VoIP service, youmust make the data plan by considering interconnection with the MGC.

Data preparationTable 7-1 provides the data plan for configuring the VoIP PSTN service.



7-3

Table 7-1 Data plan for configuring the VoIP PSTN service based on the H.248 protocol

Item Remarks

MG interfacedata(The dataconfigurationmust beconsistent withthe dataconfigurationon the MGC.)

Parameters of themediastream andsignalingstream

Media andsignalingupstream VLAN

It is used as the upstream VLAN of theVoIP service to be configured. StandardVLAN is recommended.

Media andsignalingupstream port

It is used as the upstream port of theVoIP service to be configured.

Media IP addressand signaling IPaddress

These IP addresses must be selectedfrom the media and signaling IP addresspools. The media and signaling IPaddress pools consist of all the IPaddresses of the L3 interface of themedia and signaling upstream VLAN.

Default IP addressof the MG

It is the IP address of the next hop fromthe MA5612 to the MGC.

Attributeparameters of theMGinterfaceNOTE

Parameters listedhere aremandatory, whichmeansthat theMGinterfacefails to bestarted iftheseparameters are notconfigured.

MG interface ID It is the MG interface ID used for theVoIP service to be configured. TheMA5612 supports only one virtualaccess gateway (VAG).

Signaling port IDof the MGinterface

It is the transport layer protocol port IDused for the signaling exchangebetween the MA5612 (AG) and theMGC.Default signaling port ID specified inthe H.248 protocol: 2944 (text) and2945 (binary)

IP address of theprimary MGC towhich the MGinterface belongs

When dual homing is not configured,the parameters of the primary MGCneed to be configured. When dualhoming is configured, the IP addressand the port ID of the secondary MGCalso need to be configured.Port ID of the

primary MGC towhich the MGinterface belongs

Coding mode ofthe MG interface

Currently, only the text coding mode issupported.

Transmissionmode of the MGinterface

The transmission mode is selectedaccording to the requirements on theMGC side. Generally, UDP is adopted.


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

Domain name ofthe MG interface

It corresponds to parameterdomainName of the MG interface.When the H.248 protocol is used, thisparameter must be configured ifparameter MIDType of the H.248message is configured as the domainname. Otherwise, the MG interface failsto be started. In other situations, thisparameter is optional.

Device name ofthe MG interface

It is supported only by the H.248protocol, and corresponds to parameterdeviceName of the MG interface thatuses the H.248 protocol.When the H.248 protocol is used, thisparameter must be configured ifparameter MIDType of the H.248message is configured as the domainname. Otherwise, the MG interface failsto be started. In other situations, thisparameter is optional.

Start negotiationversion of the H.248 protocol forthe MG interface

It is recommended that you configurethis parameter to 0, which indicates thenegotiation is performed according tothe profile.

Digitmap of an MG Interface The digitmaps here are used for certainspecial applications such as emergencycalls and emergency standalone. Thedigitmaps for common phone servicesare sent to the AG by the MGC, andtherefore such digitmaps need not beconfigured on the AG. If the servicessuch as emergency calls and emergencystandalone are not required, thedigitmaps need not be configured.

Software Parameters of anMG Interface

According to the service requirements,the configuration of softwareparameters determines whether the MGinterface supports the functions such asdual homing and emergencystandalone.

Ringing Mode of an MGInterface

According to the service requirements,the ringing modes of the MG interfaceneed to be determined.

TID Format of an MGInterface

The TID format determines thegeneration mode of various types ofuser terminals on an MG interface.



7-5

Item Remarks

Voice servicedata(The dataconfigurationmust beconsistent withthe dataconfigurationon the MGC.)

Slot that houses the voiceservice board

-

User Data Phone number The phone numbers allocated by theMGC need to be determined, and thepaging numbers for users' emergencystandalone need to be planned if theemergency standalone function isprovided.

TID If the TID template with which thePSTN user is bound does not supportterminal layering, this parameter needsto be configured.

User priority According to the service requirements,the user priority needs to be specified.The user priorities are as follows:l cat1: government1 (category 1

government users)l cat2: government2 (category 2

government users)l cat3: normal (common users,

default priority in the system)

User type According to the service requirements,the user type needs to be specified. Theuser types are as follows:l DEL: direct exchange lines (default

type in the system)l ECPBX: earth calling PBXl LCPBX: loop calling PBXl PayPhone: pay phone

System Parameters The system parameters including theoverseas version flag and messagewaiting indication (MWI) mode need tobe configured according to the localstandards to ensure that the response ofthe user terminal complies with thelocal standards.

Overseas Parameters The attributes such as the upper andlower thresholds of the flash-hookingduration need to be configuredaccording to the local standards toensure that the response of the userterminal complies with the localstandards.


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

Local Digitmap Configure a proper local digitmapaccording to the local standards. If theMGC does not send the detaileddigitmap to the MA5612, the MA5612uses the local digitmap to match thephone number.CAUTION

If the H.248 protocol is used, the localdigitmap need not be configured by default.You can configure the local digitmapaccording to the requirements.

Attributes of a PSTN Port If the PSTN port needs to support thepolarity reversal charging, the PSTNport needs to be configured to supportthe polarity reversal pulse. Otherattributes need not be modified if thereis no special requirement.

Attributes of the RingingCurrent

You can adjust the ringing tone volumeby modifying the attributes of theringing current. Generally, theattributes of the ringing current need notbe modified. You need to modify theparameters of the ringing currentattributes according to the localstandards only when the default ringingcurrent attributes do not meet the localstandards.

1. 7.1.1 Configuring an MG InterfaceThis topic describes how to configure an MG interface for implementing thecommunication between the MA5612 (AG) and the MGC.

2. 7.1.2 Configuring the VoIP PSTN UserAfter an MG interface is configured, you can add public switched telephone network(PSTN) users on the MG interface to implement the VoIP service.

7.1.1 Configuring an MG InterfaceThis topic describes how to configure an MG interface for implementing the communicationbetween the MA5612 (AG) and the MGC.

Contextl The MA5612 communicates with the MGC through the MG control protocol, that is, the

H.248 protocol.l One MA5612 supports up to one MG interface. The MG interface can be configured with

the attributes such as authentication and ringing mapping.

1. 7.1.1.1 Configuring the Upstream VLAN Interface



7-7

This topic describes how to specify the upstream VLAN interface for the media stream andsignaling stream, and how to configure the IP addresses of the L3 interface. These IPaddresses are the sources of the media and signaling IP address pools.

2. 7.1.1.2 Configuring the Media and Signaling IP Address PoolsThe media IP address pool defines all media IP addresses that can be used by the AG, andthe signaling IP address pool defines all signaling IP addresses that can be used by the AG.

3. 7.1.1.3 Adding an MG InterfaceThis topic describes how to add an MG interface, through which the MA5612 cancommunicate with the MGC.

4. 7.1.1.4 (Optional) Configuring the Digitmap of an MG InterfaceThis topic describes how to configure the digitmaps for certain special applications suchas emergency calls and emergency standalone. The digitmaps for common phone servicesare issued to the AG by the MGC, and therefore such digitmaps need not be configured onthe AG. If the services such as emergency calls and emergency standalone are not required,the digitmaps need not be configured.

5. 7.1.1.5 (Optional) Configuring the Software Parameters of an MG InterfaceThe software parameters of an MG interface mainly define certain common serviceattributes of the MG interface. After the configuration of the software parameters of an MGinterface, the software parameters take effect immediately and the configuration is validonly to the MG interface.

6. 7.1.1.6 (Optional) Configuring the Ringing Mode of an MG InterfaceThis topic describes how to configure the ringing mode of an MG interface to meet differentuser requirements.

7. 7.1.1.7 (Optional) Configuring the TID Format of an MG InterfaceThe TID format determines how various user terminal IDs on the MG interface aregenerated.

8. 7.1.1.8 Enabling an MG InterfaceEnabling an MG interface is to reset an MG interface to make the MG interface registerwith the MGC (or to make the modified attributes of the MG interface take effect) after theconfiguration of the MG interface is complete, so that the MG interface can work in thenormal state.

7.1.1.1 Configuring the Upstream VLAN Interface

This topic describes how to specify the upstream VLAN interface for the media stream andsignaling stream, and how to configure the IP addresses of the L3 interface. These IP addressesare 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 addressfunctions as the primary address, and other IP addresses function as the secondary addresses.

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.


Configuration Guide


Issue 04 (2011-04-27)

Run the port vlan command to 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 interfaceare the same as those in the data plan.

----End

Example

Assume that the media stream and signaling stream are transmitted upstream through upstreamport 0/0/1. To create media and signaling upstream VLAN 3 and configure IP addresses10.13.4.116/16 and 10.13.4.117/16 of the L3 interfaces for the media IP address pool and thesignaling IP address pool respectively, do as follows:

huawei(config)#vlan 3 smarthuawei(config)#port vlan 3 0/0 1huawei(config)#interface vlanif 3huawei(config-if-vlanif3)#ip address 10.13.4.116 16huawei(config-if-vlanif3)#ip address 10.13.4.117 16 subhuawei(config-if-vlanif3)#quit huawei(config)#display interface vlanif 3vlanif3 current state : UPLine protocol current state : UPDescription : HUAWEI, SmartAX Series, vlanif3 InterfaceThe Maximum Transmit Unit is 1500 bytesInternet Address is 10.13.4.116/16Internet Address is 10.13.4.117/16 SecondaryIP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc32-1118

7.1.1.2 Configuring the Media and Signaling IP Address Pools

The media IP address pool defines all media IP addresses that can be used by the AG, and thesignaling IP address pool defines all signaling IP addresses that can be used by the AG.

Prerequisite

The IP address of the L3 interface of the media and signaling upstream VLAN must beconfigured. For details about how to configure the IP address, see 7.1.1.1 Configuring theUpstream VLAN Interface.

Contextl 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.l The signaling IP address pool is used to store the IP addresses of the MG or SIP interfaces,

and the media IP address pool is used to store the IP addresses of the media streamscontrolled by the signaling.

l 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.



7-9

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 themedia and signaling upstream VLAN.

2. Run the display ip address media command to check whether the media IP address poolis 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 ofthe media and signaling upstream VLAN.

2. Run the display ip address signaling command to check whether the signaling IP addresspool is the same as that in the data plan.

----End

ExampleAssume that the IP address of the gateway is 10.13.1.1. To add IP addresses 10.13.4.116 and10.13.4.117 of L3 interfaces of the media and signaling upstream VLAN to the media IP addresspool and the signaling IP address pool respectively, do as follows:

huawei(config)#voiphuawei(config-voip)#ip address media 10.13.4.116 10.13.1.1huawei(config-voip)#ip address media 10.13.4.117 10.13.1.1huawei(config-voip)#ip address signaling 10.13.4.116huawei(config-voip)#ip address signaling 10.13.4.117huawei(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 MAC Address..........: 00-E0-FC-AF-91-33 huawei(config-voip)#display ip address signaling Signaling: IP Address...........: 10.13.4.116 Subnet Mask..........: 255.255.0.0 MAC Address..........: 00-E0-FC-AF-91-33 IP Address...........: 10.13.4.117 Subnet Mask..........: 255.255.0.0 MAC Address..........: 00-E0-FC-AF-91-33

7.1.1.3 Adding an MG InterfaceThis topic describes how to add an MG interface, through which the MA5612 can communicatewith the MGC.


Configuration Guide


Issue 04 (2011-04-27)

ContextOne MA5612 supports up to one MG interface.

Procedure

Step 1 Add an MG interface.

Run the interface h248 command to add an MG interface that supports H.248 protocol.

Step 2 Configure the attribute of the MG interface.

Run the if-h248 attribute command to configure the attribute of the MG interface according tothe data plan.

NOTE

If the MGC interconnected with the MG is provided by Huawei, the profile (namely, parameter profile-index) need not be configured. If the MGC interconnected with the MG is provided by another vendor, theprofile must be configured. (The parameter value is prompted in the CLI.)

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 interfaceis the same as that in the data plan.

----End

ExampleAssume that the MG interface ID is 0 and the H.248 protocol is used for interconnecting withthe MGC. To add the MG interface, do as follows:

huawei(config)#interface h248 0 Are you sure to add MG interface?(y/n)[n]:yhuawei(config-if-h248-0)#if-h248 attribute mgip 10.13.4.116 mgport 2944 code text primary-mgc-ip1 10.13.2.118 primary-mgc-port 2944 mg-media-ip1 10.71.46.69 mg-media-ip2 10.13.4.117start-negotiate-version 0 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 0:Customizing_0/1("Customizing_0/1") 2833Encrypt - Codetype Text Transfer Mode UDP HeartBeatGenTimer(s) 60 HeartBeatRetransTimes 3 HeartBeatRetransTimer(s) 60 MG signalling IP 10.13.4.116 MG signalling Port 2944 MG media IP1 10.13.4.116 MG media IP2 10.13.4.117 MIDType IP4_ADDR DeviceName - Retrans Enable



7-11

Active MGC MGC Port :2944 MGC IP1:10.13.2.118 Active MGC MGC Port :2944 MGC IP2:- Active MGC MGC Domain Name:- Standby MGC MGC Port :- MGC IP1:- Standby MGC MGC Port :2944 MGC IP2:- Standby MGC MGC Domain Name:- -------------------------------------------------

7.1.1.4 (Optional) Configuring the Digitmap of an MG Interface

This topic describes how to configure the digitmaps for certain special applications such asemergency calls and emergency standalone. The digitmaps for common phone services areissued 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 digitmapsneed not be configured.

Context

CAUTIONThe digitmap configuration is relatively complicated. The information such as the meanings andusage of the characters in a digitmap is defined in the protocol, and is not described here. Thistopic provides only some basic information. It is recommended that you refer to the digitmapdescription in ITU-T H248.1 (applicable to H.248) before configuring the digitmap.

l A digitmap is a set of digit collection descriptors. It is a dialing scheme resident in the MGand is used for detecting and reporting digit events received on a termination. The digitmapis used to improve the efficiency of the MG in sending the callee number. That is, if thecallee number matches a dialing scheme defined by the digitmap, the MG sends the calleenumber collectively in a message.

l A digitmap consists of strings of digits with certain meanings. When the received dialingsequence matches one of the strings, it indicates that the digits are collected completely.

l 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 digitmapl Emergency call digitmap (due to call restriction in the case of an overload)l Automatic redial digitmap of the card service

Table 7-2 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 abetter guide to the digitmap configuration.

Table 7-2 Digitmap format in the H.248 protocol

Digit orCharacter

Description

0-9 Indicate dialed digits 0-9.


Configuration Guide


Issue 04 (2011-04-27)

Digit orCharacter

Description

A-D Indicate A-D.

E Indicates * in the DTMF mode.

F Indicates for # in the DTMF mode.

X Indicates for a wildcard, indicating any digit from 0 to 9.

S Indicates the short timer. When detecting the timer timeout, the system reportsa phone number digit by digit if the phone number is detected after the dialingscheme is matched.

L Indicates the long timer. When detecting the timer timeout, the system reportsa phone number digit by digit if the phone number is detected after the dialingscheme is matched.

Z Indicates the duration modifier, which indicates a dialing event of a longduration. It is before the event character with a fixed location. When the eventduration exceeds the threshold, the dialing event fills the location.

. Indicates that there can be multiple digits (including 0) or characters beforeit.

| Used to separate the strings and indicates that each string is an optional dialingscheme.

[] 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 prevailsregardless of whether a timer is configured on the AG. When the MGC does not issue thedigitmap timer and the default digitmap timer does not meet the service requirements, you canconfigure 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



7-13

Example

Assume that the inner digitmap of the H.248-based MG interface is configured. According tothe data plan, the inner digitmap format is 1234xxxx. The digitmap timer is not configuredbecause it is issued by the MGC. To configure the inner digitmap, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#digitmap set inner 1234xxxxhuawei(config-if-h248-0)#display digitmap ---------------------------------------------------------------------- Inner digitmap : 1234xxxx Urgent digitmap (for overload or bandwidth restrict) : - Dualdial digitmap for card service : - ----------------------------------------------------------------------

7.1.1.5 (Optional) Configuring the Software Parameters of an MG Interface

The software parameters of an MG interface mainly define certain common service attributesof the MG interface. After the configuration of the software parameters of an MG interface, thesoftware parameters take effect immediately and the configuration is valid only to the MGinterface.

Context

There are 32 software parameters (numbered from 0 to 31) of an MG interface that supports H.248. Table 7-3 lists the configurable parameters, and the other parameters are reserved in thesystem.

Table 7-3 Software parameters of an MG interface that supports H.248

Parameter Description Default Setting

2 Indicates whether the MGinterface supports dual homing.To configure an MG interfaceto or not to support dualhoming, use this parameter.If the MG interface does notsupport dual homing, even if thesecondary MGC is configured,the MG interface does notswitch to registering with thesecondary MGC when the MGinterface fails to register withthe primary MGC. If the MGinterface supports dual homingand auto-switching, even if theMG interface has registeredwith the secondary MGC, theMG interface can automaticallyswitch back to the primaryMGC if the primary MGCrecovers.

Numeral type. Range: 0-2.l 0: indicates that dual homing

is not supported.l 1: indicates that dual homing

rather than auto-switching issupported.

l 2: indicates that dual homingand auto-switching issupported.

Default: 0


Configuration Guide


Issue 04 (2011-04-27)


3 This parameter is reserved inthe system.

-

4 Indicates whether a wildcard isused for the registration of theMG interface.To configure whether awildcard is used for theregistration of an MG interface,use this parameter.Using a wildcard forregistration can reduce thequantity of messages betweenthe MG interface and the MGC.When the wildcard is not usedfor registration, all the terminalson the MG interface need toregister with the MGC in order.The registration without awildcard is also called "single-endpoint registration".

Numeral type. Range: 0-1.l 0: indicates that a wildcard is

used.l 1: indicates that a wildcard is

not used.Default: 0


-

6 Indicates whether the MGinterface supports deviceauthentication.To configure an MG interfaceto or not to supportauthentication, use thisparameter.After the device authenticationis supported, run the authcommand to configure theauthentication parameters, andthen run the reset command toreset the MG interface. In thisway, the MGC can manage thesecurity of the MGs and avoidillegal registration with theMGC.

Numeral type. Range: 0-1.l 0: indicates that device

authentication is supported.l 1: indicates that device

authentication is notsupported.

Default: 1

7 Indicates whether the MGinterface supports securityheader.To configure an MG interfaceto or not to support securityheader, use this parameter.

Numeral type. Range: 0-1.l 0: indicates that security

header is supported.l 1: indicates that security

header is not supported.Default: 1



7-15



-


-

11 Indicates whether the MGinterface supports emergencystandalone.To configure whether an MGinterface supports emergencystandalone, use this parameter.If the MG interface supportsemergency standalone, theusers on the MG interface canmake phone calls even if theMG fails to communicate withthe MGC.

Numeral type. Range: 0-3.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 arepermitted.

Default: 0

13 Indicates the maximumdigitmap matching flag of theMG interface.To configure digitmapmatching scheme of the MGinterface, use this parameter.Minimum matching indicatesthat the telephone number isreported if it matches thedigitmap completely. If there isno dialing within the duration ofthe short timer (default: 5s), thetelephone number is reportedafter the short timer times out.Otherwise, the system matchesother digitmap schemes.

Numeral type. Range: 0-1.l 0: indicates minimum match.l 1: indicates maximum match.Default: 0


-


Configuration Guide


Issue 04 (2011-04-27)


15 Indicates whether the functionof filtering media streams bysource port is enabled on an MGinterface.To enable or disable thefunction of filtering mediastreams by source port on anMG interface, use thisparameter.When the function of filteringmedia streams by source port isenabled on the MG interface,only the media streams from thespecific ports can be received.

Numeral type. Range: 0-1.l 0: indicates that media

streams are not filtered bysource port.

l 1: indicates that mediastreams are filtered by sourceport.

Default: 0

16 Indicates the length of the timerfor filtering the media streamsource port of the MG interface.To configure the length of thetimer for filtering the mediastream source port of an MGinterface, use this parameter.When an MG interface does notfilter the source port, the MGinterface automatically filtersthe source port if the filteringtimer times out.

Numeral type. Range: 0-30s.Default: 5s

22 Indicates the type of the prompttone after the communicationbetween the MG and the MGCis interrupted.

Numeral type. Range: 0-3.l 0: indicates the busy tone.l 1:indicates the device

congestion tone.l 2: indicates the voice prompt.Default: 0

23 Indicates the length of the timerfor synchronizing the portstatus.

Numeral type. Range: 0-120s.Default: 35s.

24 Indicates the maximum value ofthe Real-Time TransportProtocol (RTP) termination ID.


25 Indicates the maximum randomvalue for the protection againstavalanche of the H.248interface.

Numeral type. Range: 0-120 ms.Default: 60000s.



7-17


26 Indicates the type of localblocking play tone.

Numeral type. Range: 0-3.l 0: indicates the busy tone.l 1: indicates the device

congestion tone.l 2: indicates the mute.l 3: indicates the user-defined

tone 1.l 4: indicates the user-defined

tone 2.Default: 0

27 Indicates the type of remoteblocking play tone.




tone 2.Default: 0.

28 Indicates the duration of thehowler tone.


29 Indicates the duration ofmessage waiting tone.


30 Indicates the time limit of thealarm for extra long call.

Numeral type. Range: 1-65535min.Default: 60s

31 Indicates whether to report thealarm for extra long call.

Numeral type. Range: 0-3.l 0: indicates that the alarm is

reported.l 1: indicates that the alarm is

not reported.Default: 1

32 Indicates the minimum intervalfor automatic registration of theremote block port.

Numeral type. Range: 0-60000s.0 indicates that the port does notregister automatically.Default: 1800s


Configuration Guide


Issue 04 (2011-04-27)


33 Indicates whether the heartbeatmessage is disabled.

Numeral type:l 0: Indicates that the heartbeat

message is disabled.l 1: Indicates that the heartbeat

message is enabled.Default: 1

ProcedureStep 1 Enter the MG interface mode.


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 parametersof the MG interface are the same as those in the data plan.

----End

ExampleTo configure software parameter 11 of H.248-based MG interface 0 to 1 so that the MG interfacesupports emergency standalone and allows only internal calls, do as follows:huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-software parameter 11 1huawei(config-if-h248-0)#display mg-software parameter 11 ------------------------------------------------- Interface Id:0 para index:11 value:1 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 11: Stand alone support 0: None 1: Inner 2: Emergency 3: Both

7.1.1.6 (Optional) Configuring the Ringing Mode of an MG InterfaceThis topic describes how to configure the ringing mode of an MG interface to meet differentuser requirements.

ProcedureStep 1 Check whether the ringing mode meets the requirements.

Check whether the preset ringing mode in the system meets the requirements according to theUsage Guidelines of the mg-ringmode add command.



7-19

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 break-make ratio of user-defined ringing mode to form a ringing mode that meets the user requirement.

CAUTIONl The system supports 16 user-defined ringing modes, which can be modified but cannot be

added or deleted.


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.

CAUTION1. The parameter mgcpara on the MG 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 initialringing 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 thesame as that in the data plan.

----End

ExampleAssume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 0, the cadenceringing is 1:4 (the value of the corresponding parameter cadence is 0), and the initial ringing is1:2 (the value of the corresponding parameter initialring is 17). To configure the ringing modeof MG interface 0, do as follows:

huawei(config)#interface h248 0huawei(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 -------------------------------------------------------


Configuration Guide


Issue 04 (2011-04-27)

0 0 0 17 -------------------------------------------------------

Assume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 0, the break-make ratio of user-defined ringing mode 0 is 0.4sec On, 0.2sec Off, 0.4sec On, 2.0sec Off, andthe initial ringing and the cadence ringing use user-defined ringing mode 0 (the values of thecorresponding parameters cadence and initialring are 128 and 144 respectively). To configurethe ringing mode of MG interface 0, do as follows:

huawei(config)#user defined-ring modify 0 para1 400 para2 200 para3 400 para4 2000 Note: Please reset the service board to make configured parameter be validhuawei(config)#display user defined-ring -------------------------------------------------- RingType Para1 Para2 Para3 Para4 Para5 Para6 -------------------------------------------------- 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 0huawei(config-if-h248-0)#mg-ringmode add 1 128 144huawei(config-if-h248-0)#display mg-ringmode attribute{ <cr>|mgcpara<0,15> }: { <cr>|mgcpara<0,15> }: Command: display mg-ringmode attribute ------------------------------------------------------- MGID PeerPara CadenceRing InitialRing ------------------------------------------------------- 0 1 128 144 -------------------------------------------------------

7.1.1.7 (Optional) Configuring the TID Format of an MG Interface

The TID format determines how various user terminal IDs on the MG interface are generated.

Context

CAUTIONThe configuration of the TID format is relatively complicated. The information such as the syntaxrules with which the terminal prefix must comply and the requirements for the character stringof the TID template is defined in the protocol, and is not described here. This topic describesonly some basic information. It is recommended that you refer to the TID description in ITU-TH248.1 before configuring the TID format.

The TID format consists of the terminal prefix and the TID template. The TID template definesthe generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefixand a character string generated by a TID template.

The TID templates that are bound to various types of users on the MG interface determinewhether the users support terminal layering.



7-21

l If the parameter list of the TID template includes only keyword "G", it indicates that theTID template is used by the non-layering users. Users bound with this template do notsupport terminal layering.

l If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" isnot available to PSTN users), it indicates that the TID template is used by the layering users.Users bound with this template support terminal layering.

NOTE

The meaning of each keyword is as follows:

l F indicates the shelf ID.

l S indicates the slot ID.

l P indicates the port ID.

l B indicates the B channel ID (only for ISDN BRA and ISDN PRA terminals).

l G indicates the general permanent termination index.

l R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, whichexists only when the system protocol is H.248. This termination is not involved unless special remarksare provided.)

When adding a user that supports terminal layering, you cannot and do not have to specify theparameter terminalid because the system automatically allocates a terminal ID. When addinga user that does not support terminal layering, you must specify the parameter terminalid.

You can run the display tid-format command to query the TID formats of various types of userson the current MG interface. In the query result, template-index indicates the index of the TIDtemplate that is bound to the type of users. Then, run the display tid-template command tocheck whether the TID template supports the layering configuration. Hence, you can checkwhether the user supports terminal layering.

Precautionl There are 19 default TID templates (templates 0-18) in the system. The default TID

templates can be referenced, but cannot be added, modified, or deleted.l The configuration of terminal layering on the MG must be the same as that on the MGC.l If certain type of terminals exists on an interface and the interface is not disabled, the

terminal prefix of this type of terminals cannot be modified.l If a certain type of terminals exists on an interface, the TID format (including the terminal

prefix and the index of the TID template) of this type of terminals cannot be changed.l The terminal prefix must comply with the following syntax rules: The prefix must not

exceed 64 characters. Only letters, digits, "_", and "/" are the characters allowed for input.The first character must be a letter, and the last character must not be a digit.

l The length of the TID, which is generated by combining the TID template and the terminalprefix that you configured, must not exceed 64 characters.

Procedure

Step 1 To query the template information.

Run the display tid-template command to query the information about the default TID templateof the system.

Step 2 Check whether the default TID template of the system meets the service requirements.


Configuration Guide


Issue 04 (2011-04-27)

If the default TID template cannot meet the service requirements, run the tid-template addcommand to add a TID template that meets the service requirements. If the default TID templatemeets the service requirements, 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 pstn command to configure the TID template and the

terminal prefix of the ISDN BRA user.l In H248 mode, run the tid-format pstn command to configure the TID template and terminal

prefix of the ISDN PRA user.

Step 5 Check whether the TID template and the terminal prefix are the same as those in the data plan.

Run the display tid-format command to check whether the TID templates and the terminalprefixes of various types of users on the current MG interface are the same as those in the dataplan.

----End

ExampleAssume 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/15/0 and check whetherthe 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 1huawei(config-if-h248-1)#tid-format pstn prefix aln/ template 3huawei(config-if-h248-1)#quithuawei(config)#esl userhuawei(config-esl-user)#mgpstnuser add 0/15/0 1huawei(config-esl-user)#display mgpstnuser 0/15/0{ <cr>|endframeid/slotid/portid<S><1,15> }: Command: display mgpstnuser 0/15/0 ------------------------------------------------------------------------ F /S /P MGID TelNo Priority PotsLineType TerminalID ------------------------------------------------------------------------ 0 /15/0 1 - Cat3 DEL aln/1/16/1 ------------------------------------------------------------------------

7.1.1.8 Enabling an MG InterfaceEnabling an MG interface is to reset an MG interface to make the MG interface register withthe MGC (or to make the modified attributes of the MG interface take effect) after the



7-23

configuration of the MG interface is complete, so that the MG interface can work in the normalstate.

Precaution

CAUTIONFor the MG interface that has been in service, this operation interrupts the ongoing servicescarried 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 normalstate.

l Run the quit command to quit the global config mode, and then run the display if-h248all command to check whether the MG interface is in the normal state.

----End

Example

To enable H.248-based MG interface 0, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:yhuawei(config-if-h248-0)#quithuawei(config)#display if-h248 all --------------------------------------------------------------------------------MGID TransMode State MGPort MGIP MGCPort MGCIP/DomainName--------------------------------------------------------------------------------0 UDP Normal 2944 10.10.10.11 2944 10.10.20.11 --------------------------------------------------------------------------------

7.1.2 Configuring the VoIP PSTN UserAfter an MG interface is configured, you can add public switched telephone network (PSTN)users on the MG interface to implement the VoIP service.

1. 7.1.2.1 Configuring the PSTN User Data


Configuration Guide


Issue 04 (2011-04-27)

This topic describes how to configure the PSTN user data (the same as the correspondingdata on the MGC) on the MG interface so that the POTS terminal can access the networkto implement the VoIP service.

2. 7.1.2.2 (Optional) Configuring the System ParametersThis topic describes how to configure the system parameters including the overseas versionflag and message waiting indication (MWI) mode according to the local standards to ensurethat the response of the user terminal complies with the local standards.

3. 7.1.2.3 (Optional) Configuring the Overseas ParametersBy default, the overseas parameters are configured according to the Chinese standards. Inthe actual service configuration, the attributes such as the upper and lower thresholds ofthe flash-hooking duration can be configured according to the local standards to ensure thatthe response of the user terminal complies with the local standards.

4. 7.1.2.4 (Optional) Configuring the Local DigitmapLocal digitmap is also called local preconfigured digitmap. When the H.248 protocol isused, the MA5612 prefers to use the digitmap sent by the MGC to match the phone number.If the MGC does not send the detailed digitmap, the MA5612 uses the local digitmap tomatch the phone number. When the SIP protocol is used, the MA5612 has to use the localdigitmap to match the phone number because the IMS network does not send the digitmap.When configuring services on the MA5612, configure a proper local digitmap accordingto the local standards.

5. 7.1.2.5 (Optional) Configuring the Attributes of a PSTN PortThis topic describes how to configure the attributes of a PSTN port to ensure that the PSTNport can meet the actual application requirements.

6. 7.1.2.6 (Optional) Configuring the Attributes of the Ringing CurrentYou 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 modifythe attributes of the ringing current according to the local standards only when the defaultringing current attributes do not meet the local standards.

7.1.2.1 Configuring the PSTN User DataThis topic describes how to configure the PSTN user data (the same as the corresponding dataon the MGC) on the MG interface so that the POTS terminal can access the network to implementthe VoIP service.

PrerequisiteThe POTS service board must be inserted into the planned slot.

NOTE

You can add a service board in two ways (see the Usage Guideline of the board add command). It isrecommended that you insert the service board into the planned slot and then confirm the board.

ContextTable 7-4 lists the default settings of the attributes of the PSTN user. When configuring theattributes of the PSTN user, you need to modify them according to the service requirements.



7-25

Table 7-4 Default settings of the attributes of the PSTN user


Sequence of sending the phonenumber of the calling party

Ringing and then sending the phone number

Format of the phone number of thecalling party

SDMF (FSK single data message format)

Whether to support the detection ofthe ANSbar signal throughmonophony

Not support

Whether to support the bell ANSsignal

Not support

Power-off interval 100 ms

FSK delay interval 800 ms

Whether to enable or disable VQEautomatic gain

Disable

Whether to enable or disable VQEnoise suppression

Disable

Target value of VQE automatic gain -22 dBm

Target value of VQE noisesuppression

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 notconfigured.)

Procedure

Step 1 In global config mode, run the board confirm command to confirm the service board.

Step 2 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.


Configuration Guide


Issue 04 (2011-04-27)

CAUTIONl When you add a PSTN user, terminalid must be configured and must be different from

the TID of an existing PTSN user if the TID template with which the PSTN user on theMG interface is bound is not a layering template.

l When you add a PSTN user, the configuration of the TID is not required because thesystem automatically allocates the TID if the TID template with which the PSTN useron the MG interface is bound is a layering template.

l When adding a PSTN user, you can configure the phone number (parameter telno). Theconfigured phone number, however, can be used only as the paging number foremergency standalone. It is recommended that you configure the phone number to bethe same as the phone number allocated by the MGC. In addition, the phone numbermust be unique on the MG. This prevents number conflict when emergency standaloneis enabled. If this parameter is not set, the phone number is null by default. Phonenumbers for normal call services are allocated by the MGC, generally, no telephonenumber (namely, parameter telno) is configured on the MG.

l For details about the relation between the TID template and the terminal layering, seethe Context in 7.1.1.7 (Optional) Configuring the TID Format of an MGInterface.

3. Run the display mgpstnuser command to check whether the configured PSTN user datais the same as the planned data.

Step 3 (Optional) Configure the attributes of a PSTN user.

The attributes of a PSTN user need to be configured only when the default settings areinconsistent with the actual application.

1. Run the mgpstnuser attribute set or mgpstnuser attribute batset command to configurethe attributes of a PSTN user.

2. Run the display mgpstnuser attribute command to check whether the attributes of thePSTN user are the same as the planned data.

----End

ExampleAssume that the phone numbers of 16 PSTN users are 83110000-83110015, terminalid are0-15 (the TID template with which the PSTN users on the MG interface are bound is not alayering template and terminalid needs to be allocated manually), and the default values areused for other attributes. To add the 16 PSTN users in slot 0/3 on MG interface 0 in batches, doas follows:huawei(config)#board confirm 0/3huawei(config)#esl userhuawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/15 0 terminalid 0 telno 83110000huawei(config-esl-user)#display mgpstnuser 0 0 10 ---------------------------------------------------------------------------- F /S /P MGID TelNo Priority PotsLineType TerminalID ---------------------------------------------------------------------------- 0 /3 /0 0 83110001 Cat3 DEL A1 ...... 0 /3 /14 0 83110014 Cat3 DEL A14 0 /3 /15 0 83110015 Cat3 DEL A15 ----------------------------------------------------------------------------



7-27

7.1.2.2 (Optional) Configuring the System ParametersThis topic describes how to configure the system parameters including the overseas version flagand message waiting indication (MWI) mode according to the local standards to ensure that theresponse of the user terminal complies with the local standards.

ContextTable 7-5 lists the system parameters supported by the MA5612.

Table 7-5 System parameters supported by the MA5612


0 Indicates the howler tonesending flag.

1: Indicates that the howler toneis sent.

1 Indicates the overseas versionflag.

0: Indicates China.

2 Indicates the initial ringing stopflag.

0: Indicates that the initialringing stop flag is not issued.

3 Indicates the MWI mode. 1: Indicates that the FSK is sentwith ringing.

4 Indicates the global digitmapsupport flag.

1: Indicates that the globaldigitmap is supported.

5 Indicates the media streamforwarding mode on the samedevice.

0: Indicates that the media streamis forwarded within the device.

6 Indicates whether to sendpower deny flag whensoftswitch indicates block.

1: Send

ProcedureStep 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 thesame as the planned data.

----End

ExampleTo 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,


Configuration Guide


Issue 04 (2011-04-27)

4:Singapore, 5:Thailand, 6:France, 7:Britain MSFUK, 8:Britain ETSI, 9:Bulgaria -----------------------------------------------------------------------------

7.1.2.3 (Optional) Configuring the Overseas ParametersBy default, the overseas parameters are configured according to the Chinese standards. In theactual service configuration, the attributes such as the upper and lower thresholds of the flash-hooking duration can be configured according to the local standards to ensure that the responseof the user terminal complies with the local standards.

ContextTable 7-6 lists the overseas parameters supported by the MA5612.

Table 7-6 Overseas parameters supported by the MA5612


0 Indicates the upper threshold ofthe flash-hooking duration.

350 ms (in compliance with theChinese mainland standards)

1 Indicates the lower threshold ofthe flash-hooking duration.


2 Indicates whether the current islimited when the user port islocked.

0: Indicates that the current is notlimited.

3 Indicates the type of ring DCoffset.

Line B offset

Procedure

Step 1 Run the oversea parameters command to configure the overseas parameters.

Step 2 Run the display oversea parameters command to check whether the overseas parameters arethe same as the planned data.

----End

ExampleTo set the upper flash-hooking threshold (overseas parameter 0) to 800 ms (in compliance withthe Hong Kong standards) and the lower flash-hooking threshold (overseas parameter 1) to 100ms (in compliance with the Hong Kong standards), do as follows:

huawei(config)#oversea parameters 0 800huawei(config)#oversea parameters 1 100huawei(config)#display oversea parameters ----------------------------------------------------------------------------- Parameter name index: 0 Parameter value: 800 Mean: Hooking upper threshold(ms), reference: China:350, HongKong:800 ----------------------------------------------------------------------------- Parameter name index: 1 Parameter value: 100 Mean: Hooking lower threshold(ms), reference: China:100, HongKong:100 -----------------------------------------------------------------------------



7-29

Parameter name index: 2 Parameter value: 0 Mean: Flag of applying PARKED LINE FEED or not when user port is locked, 0:not apply, 1:apply ----------------------------------------------------------------------------- Parameter name index: 3 Parameter value: 1 Mean: Type of ring DC offset, 0:Line A offset, 1:Line B offset -----------------------------------------------------------------------------

7.1.2.4 (Optional) Configuring the Local Digitmap

Local digitmap is also called local preconfigured digitmap. When the H.248 protocol is used,the MA5612 prefers to use the digitmap sent by the MGC to match the phone number. If theMGC does not send the detailed digitmap, the MA5612 uses the local digitmap to match thephone number. When the SIP protocol is used, the MA5612 has to use the local digitmap tomatch the phone number because the IMS network does not send the digitmap. When configuringservices on the MA5612, configure a proper local digitmap according to the local standards.

Context

CAUTIONWhen the H.248 protocol is used, the local digitmap need not be configured by default. You canconfigure the local digitmap according to the requirements.

l When the H.248 protocol is used, the MA5612 is not configured with a default localdigitmap. You can configure a local digitmap if required.

l When the SIP protocol is used, the MA5612 is configured with three default local digitmaps,namely, normal digitmap, emergency digitmap, and SCC digitmap. You can change thename and type of the default local digitmaps, and add or change the digitmap body in thedefault local digitmaps. In addition, you can add a local digitmap according to therequirements. Table 7-7 lists the information about the default local digitmap.

Table 7-7 Information about the default local digitmap when the SIP protocol is used

Digitmap Name Digitmap Type Digitmap Body

DefaultNormalDmm normal x.S

DefaultSccDmm scc ([EF]X[0-9E].F|[EF]X[0-9E].S|[EF][EF]X[0-9E].F|[EF][EF]X[0-9E].S)

DefaultEmergencyDmm emergency (11X|91X)

l The MA5612 supports a maximum of eight local digitmaps.

l For the meaning of each character in the digitmap body, see the Context in 7.1.1.4(Optional) Configuring the Digitmap of an MG Interface.


Configuration Guide


Issue 04 (2011-04-27)

Precautionl When the H.248 protocol is used, the type of the local digitmap can only be normal.l 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 theParameter Description in the local-digitmap add command.

Procedure

Step 1 In privilege mode, run the display protocol support command to query the current protocoltype used on the MA5612.l When the H.248 protocol is used, go to Step 5.l When the SIP protocol is used, go to Step 2.

Step 2 In privilege mode, run the display local-digitmap command to query the default local digitmap.l If the default local digitmap can meet the requirements, the configuration is complete.l If the default local digitmap cannot meet the requirements, perform one or more operations

in Step 3, Step 4, and Step 5 to configure a proper local digitmap.

Step 3 Run the local-digitmap modify command to change the name, type, or body of the localdigitmap.

Step 4 Run the local-digitmap append command to add a digitmap body in the local digitmap.

Step 5 According to the data plan, run the local-digitmap add command to add a local digitmap.

Step 6 Run the display local-digitmap command to check whether the local digitmap is the same asthe planned local digitmap.

----End

Example

Assume that the H.248 protocol is used on the MA5612. To add a local digitmap with the datalisted in Table 7-8, do as follows:

Table 7-8 Local digitmap existing in the system


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|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S)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) ------------------------------------------



7-31

Assume that the SIP protocol is used on the MA5612. The local digitmap exists in the system.Table 7-9 lists the data of the local digitmap.




To change the existing local digitmap so that the name of the local digitmap is huawei0, adddigitmap body 15xxxxxxxxx, and add a local digitmap according to data plan listed in Table7-10, do as follows:

Table 7-10 Local digitmap to be added


huawei1 emergency (0E)

huawei(config)#display local-digitmap all ------------------------------------------ Name: DefaultNormalDmm Type: normal Body: x.S ------------------------------------------ Name: DefaultSccDmm Type: scc Body: (ExxFx.E|ExxFx.L|ExFx.E|ExFx.L|Exx.F|EFxx.F|Fxx.F|Ex.Ex.F) ------------------------------------------ Name: DefaultEmergencyDmm Type: emergency Body: (11X|91X) ------------------------------------------ Name: huawei Type: normal Body: ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S) ------------------------------------------huawei(config)#local-digitmap modify huawei name huawei0huawei(config)#local-digitmap append huawei0 15xxxxxxxxxhuawei(config)#local-digitmap add huawei1 emergency (11X|91X|0E)huawei(config)#display local-digitmap all ------------------------------------------ Name: DefaultNormalDmm Type: normal Body: x.S ------------------------------------------ Name: DefaultSccDmm Type: scc Body: (ExxFx.E|ExxFx.L|ExFx.E|ExFx.L|Exx.F|EFxx.F|Fxx.F|Ex.Ex.F) ------------------------------------------ Name: DefaultEmergencyDmm Type: emergency Body: (11X|91X) ------------------------------------------ Name: huawei0


Configuration Guide


Issue 04 (2011-04-27)

Type: normal Body: ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S|15xxxxxxxxx) ------------------------------------------ Name: huawei1 Type: emergency Body: (11X|91X|0E) ------------------------------------------

7.1.2.5 (Optional) Configuring the Attributes of a PSTN PortThis topic describes how to configure the attributes of a PSTN port to ensure that the PSTN portcan meet the actual application requirements.

ContextThe MA5612 supports the following attributes of a PSTN port:

l Physical attributes (including whether to support the polarity reversal pulse, whether tosupport the port locking, and dialing mode). For details about how to configure the physicalattributes of a PSTN port, see pstnport attribute set.

l Electrical attributes (including the impedance and the current). For details about how toconfigure the electrical attributes of a PSTN port, see pstnport electric set.

l KC attributes (including the KC charging mode and the valid voltage). For details abouthow to configure the KC attributes of a PSTN port, see pstnport kc set.

Procedure

Step 1 In global config mode, run the pstnport command to enter the PSTN port mode.

Step 2 Run the pstnport attribute batset or pstnport attribute set command to configure the physicalattributes of a PSTN port.

Step 3 Run the pstnport electric batset or pstnport electric set command to configure the electricalattributes of a PSTN port.

Step 4 Run the pstnport kc batset or pstnport kc set command to configure the KC attributes of thePSTN port.

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.l Run the display pstnport electric command to query the electrical attributes of the PSTN

port.l Run the display pstnport kc command to query the KC attributes of the PSTN port.

----End

ExampleTo configure the 16 PSTN ports on the board in slot 0/3 to support the polarity reversal charging,do as follows:

huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse enablehuawei(config-pstnport)#display pstnport attribute 0/3



7-33

-------------------------------------------------------------------- F /S /P 0 /3 /0 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable -------------------------------------------------------------------- F /S /P 0 /3 /1 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable -------------------------------------------------------------------- ...... -------------------------------------------------------------------- F /S /P 0 /3 /15 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable --------------------------------------------------------------------

NOTE

When a call starts and ends, the MG shows the start time and the end time based on the polarity reversalon the subscriber line. The billing terminal that supports the polarity reversal charging function, such as acharging phone set, implements the polarity reversal charging function based on the start time and the endtime of a call.

7.1.2.6 (Optional) Configuring the 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 theattributes of the ringing current according to the local standards only when the default ringingcurrent 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.

l AC voltage amplitude: The greater the amplitude is, the louder the ringing tones are.

The default settings of the attributes of the ringing current are as follows:

l Ringing current frequency: 25 Hz

l AC voltage amplitude: 50 Vrms

Procedure

Step 1 In the global config mode, run the voip command to enter the VoIP mode.


Configuration Guide


Issue 04 (2011-04-27)

Step 2 Run the ring attribute set command to configure the attributes of the ringing current accordingto the data plan.

Step 3 Run the display ring attribute command to check whether the attributes of the ringing currentare the same as the planned data.

----End

ExampleTo set the ringing current frequency to 16 Hz (parameter value 0) and AC amplitude to 65 Vrms(parameter value 1), do as follows:

huawei(config)#voiphuawei(config-voip)#ring attribute set frequency 0 acamplitude 1huawei(config-voip)#display ring attribute ringing current frequency : 16HZ ringing current acamplitute: 65VRMS

7.2 Configuring the VoIP PSTN Service (Based on the SIPProtocol)

This topic describes how to configure the VoIP PSTN service on the MA5612 through theSession Initiation Protocol (SIP).

ContextThe voice over IP (VoIP) service uses the IP packet switching network for transmission afterthe traditional analog voice signals are compressed and packetized, to reduce the cost of thevoice service.

For details about the VoIP service, see Voice in the Feature Description.

The function and application of the SIP interface are similar to the function and application ofthe MG interface. The MA5612 can also function as a voice over IP gateway (VGW) componentin the IMS architecture. In the downstream direction, it provides the access to PSTN users; inthe upstream direction, it is connected to the IMS system through the SIP interface, providingthe VoIP service by working with the IMS core.

PrerequisiteAccording to the actual network, a route from the MA5612 to the IMS core network device mustbe configured to ensure that the MA5612 and the IMS core network device are reachable to eachother.

Data preparationTable 7-11 provides the data plan for configuring the VoIP service.



7-35

Table 7-11 Data plan for configuring the VoIP service based on the SIP protocol

Item Remarks

SIP interfacedata



It is used as the upstream VLAN of theVoIP service to be configured. Note thatthe media stream and the signalingstream can use the same VLAN ordifferent VLANs. The result isdetermined according to the negotiationwith the upstream device.

Signalingupstream port

It is used as the upstream port forconfiguring the SIP signaling.


These IP addresses must be selectedfrom the media and signaling IP addresspools. The media and signaling IPaddress pools consist of all the IPaddresses of the L3 interface of themedia and signaling upstream VLAN.


It is the IP address of the next hop fromthe MA5612 to the IMS core networkdevice.CAUTION

If the media IP address and the signaling IPaddress are different and the media and thesignaling are transmitted upstream throughdifferent gateways, ensure that theycorrespond to correct gateways. Otherwise,normal calls may fail.

Attributeparameters of the SIPinterfaceNOTE

Parameters listedhere aremandatory, whichmeansthat theSIPinterfacefails to bestarted iftheseparameters are notconfigured.

SIP interface ID It is the SIP interface ID used for theVoIP service to be configured. TheMA5612 supports only one virtualaccess gateway (VAG).

Signaling port IDof the SIPinterface

The value range is 5000-5999. Theprotocol specifies the port ID to be5060.

IP address of theprimary IMS corenetwork device towhich the SIPinterface belongs

When dual homing is not configured,parameters of only the primary IMScore network device are required. Ifdual homing is configured, the IPaddress and the port ID of the secondaryIMS core network device must beconfigured.Port ID of the

primary IMS corenetwork device towhich the SIPinterface belongs


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

Transmissionmode of the SIPinterface

The transmission mode is selectedaccording to the requirements on theIMS core network device. Generally,UDP is adopted.

Home domain ofthe SIP interface

It corresponds to parameter home-domain in the MG interface attributes.

Index of theprofile used by theSIP interface

It corresponds to parameter profile-index in the MG interface attributes.

IP addressobtaining mode ofthe proxy server

l In IP mode, the IP address and theport ID of the primary proxy servermust be configured.

l In DNS-A or DNS-SRV mode, thedomain of the primary proxy servermust be configured.

Ringing Mode of the SIPInterface

The ringing mode of the SIP interfaceis determined by service requirements.

Voice servicedata(The dataconfigurationmust beconsistent withthe dataconfigurationon the MGC.)


-

User Data Phone number The phone number that the IMS corenetwork device allocates to the usermust be configured.

User priority According to the service requirements,the user priority needs to be specified.The user priorities are as follows:l cat1: government1 (category 1


government users)l cat3: normal (common users,

default priority in the system)

User type According to the service requirements,the user type needs to be specified. Theuser type includes the following:l DEL: direct exchange lines (default

type in the system)l ECPBX: earth calling PBXl LCPBX: loop calling PBXl PayPhone: pay phone

Centrex According to the local standards, theout-centrex prefix and out-centrexattributes need to be configured.



7-37

Item Remarks

System Parameters The system parameters including theoverseas version flag and messagewaiting indication (MWI) mode need tobe configured according to the localstandards to ensure that the response ofthe user terminal complies with thelocal standards.

Overseas Parameters The attributes such as the upper andlower thresholds of the flash-hookingduration need to be configuredaccording to the local standards toensure that the response of the userterminal complies with the localstandards.

Local Digitmap Configure a proper local digitmapaccording to the local standards. Afterthe configuration, the local digitmapcan be directly used to match the phonenumber after the user picks the phoneoff the hook.

Attributes of a PSTN Port If the PSTN port needs to support thepolarity reversal charging, the PSTNport needs to be configured to supportthe polarity reversal pulse. Otherattributes need not be modified if thereis no special requirement.


You can adjust the ringing tone volumeby modifying the attributes of theringing current. Generally, theparameters of the ringing currentattributes need not be modified. Youneed to modify the parameters of theringing current attributes according tothe local standards only when thedefault ringing current attributes do notmeet the local standards.

Procedure1. 7.2.1 Configuring the SIP Interface

This topic describes how to configure the SIP interface to implement the communicationbetween the MA5612 (SIP AG) and the IMS core network device.

2. 7.2.2 Configuring the VoIP PSTN UserAfter an SIP interface is configured, you can add public switched telephone network(PSTN) users on the SIP interface to implement the VoIP service.


Configuration Guide


Issue 04 (2011-04-27)

7.2.1 Configuring the SIP InterfaceThis topic describes how to configure the SIP interface to implement the communication betweenthe MA5612 (SIP AG) and the IMS core network device.

Contextl The MA5612 can communicate with the IMS core network device through the SIP protocol.l One MA5612 supports only one SIP interface.

Procedure1. 7.2.1.1 Configuring the Upstream VLAN Interface



3. 7.2.1.3 Adding an SIP InterfaceThis topic describes how to add an SIP interface so that the MA5612 can communicatewith the IMS through the SIP interface.

4. 7.2.1.4 (Optional) Configuring the Ringing Mode of the SIP InterfaceThis topic describes how to configure the ringing mode of the SIP interface to support thebreak-make ratios of various new ringing modes and make the ringing mode meet the localstandards.

7.2.1.1 Configuring the Upstream VLAN InterfaceThis topic describes how to specify the upstream VLAN interface for the media stream andsignaling stream, and how to configure the IP addresses of the L3 interface. These IP addressesare the sources of the media and signaling IP address pools.

ContextMultiple IP addresses can be configured for the same VLAN L3 interface. Only one IP addressfunctions as the primary address, and other IP addresses function as the secondary addresses.

Procedure









7-39



----End

ExampleAssume that the media stream and signaling stream are transmitted upstream through upstreamport 0/0/1. To create media and signaling upstream VLAN 3 and configure IP addresses10.13.4.116/16 and 10.13.4.117/16 of the L3 interfaces for the media IP address pool and thesignaling IP address pool respectively, do as follows:


7.2.1.2 Configuring the Media and Signaling IP Address PoolsThe media IP address pool defines all media IP addresses that can be used by the AG, and thesignaling IP address pool defines all signaling IP addresses that can be used by the AG.

PrerequisiteThe IP address of the L3 interface of the media and signaling upstream VLAN must beconfigured. For details about how to configure the IP address, see 7.1.1.1 Configuring theUpstream VLAN Interface.


selected from the IP address pools configured here.l The signaling IP address pool is used to store the IP addresses of the MG or SIP interfaces,

and the media IP address pool is used to store the IP addresses of the media streamscontrolled by the signaling.


Procedure



pool.


Configuration Guide


Issue 04 (2011-04-27)



Step 3 Configure the signaling IP address pool.

1. Run the ip address signaling command to add the signaling IP address to the signaling IPaddress pool.



----End

Example

Assume that the IP address of the gateway is 10.13.1.1. To add IP addresses 10.13.4.116 and10.13.4.117 of L3 interfaces of the media and signaling upstream VLAN to the media IP addresspool and the signaling IP address pool respectively, do as follows:


7.2.1.3 Adding an SIP Interface

This topic describes how to add an SIP interface so that the MA5612 can communicate with theIMS through the SIP interface.

Prerequisite

The to-be-configured media and signaling IP addresses of the SIP interface must be added tothe media and signaling IP address pools successfully.



7-41

Context

One MA5612 supports only one SIP interface.

Procedure

Step 1 Run the display protocol support command to query the current system protocol.

l If the system protocol is SIP, go to Step 8.

l If the system protocol is not SIP, go to Step 2.

Step 2 Run the display if-h248 all command to query whether an MG interface that supports the currentprotocol exists in the system.

Step 3 Run the display mgpstnuser command to check the user data, run the esl user command toenter ESL user mode, and then run the mgpstnuser batdel command to delete the voice serviceuser.

Step 4 Run the shutdown(h248) command to shut down the MG interface.

CAUTIONThis operation interrupts the ongoing services carried on the currently used MG interface. Hence,exercise caution when performing this operation. Before performing this operation, be sure tocheck whether the operation is allowed.

Step 5 Run the undo interface h248 command to delete the MG interface.

Step 6 Run the protocol support command to change the system protocol to SIP.

CAUTIONYou must delete the default and user-defined local digitmaps before switching the protocol.

Step 7 After saving the configuration data by running the save command, run the reboot systemcommand to reboot the system to make the new configuration take effect.

Step 8 Run the interface sip command to add an SIP interface.

Step 9 Run the if-sip attribute basic command to configure the basic attributes of the SIP interface.

NOTE

l Between proxy IP and proxy domain, which are basic attributes, at least one attribute must beconfigured. If both attributes are configured, the system determines which attribute is used accordingto the configured address mode of the proxy server.

l The profile index must be configured.

Step 10 Run the if-sip attribute optional command to configure the optional attributes of the SIPinterface.

Step 11 Run the display if-sip attribute command to query the SIP interface attributes.


Configuration Guide


Issue 04 (2011-04-27)

Step 12 After the configuration, you need to run the reset command to reset the SIP interface to makethe configuration take effect. Otherwise, the configuration is stored only in the database.

Step 13 After the configuration, run the display if-sip attribute running command to query the statusof 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 is10.13.4.118, port ID of the primary proxy server is 5060, domain name of the primary proxyserver is proxy.domain, IP address 1 of the secondary proxy server is 10.13.4.119, port ID ofthe secondary proxy server is 5060, home domain name is sip.huawei.com, and profile index is1. To configure such attributes of SIP interface 0, do as follows:

huawei(config)#interface sip 0huawei(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-proxy-port 5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.13.4.119secondary-proxy-port 5060 huawei(config-if-sip-0)#if-sip attribute basic home-domain sip.huawei.com sipprofile-index 1huawei(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 IP 2 - 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 - 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 ------------------------------------------------------------

7.2.1.4 (Optional) Configuring the Ringing Mode of the SIP Interface

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.



7-43

PrerequisiteThe SIP interface must be added successfully.

Contextl If the preset ringing modes of the system can meet the user requirements, you can select

the required ringing mode and configure the corresponding ringing mapping.l If the preset ringing modes cannot meet the user requirements, you can use the user-defined

ringing mode and configure the corresponding ringing mapping.l You can configure the cadence duration for the user-defined ringing to form different

ringing modes.l 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-defined cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the user-defined 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.

Precautionl The ringing mapping name must be unique on the same SIP interface.l An index can be used for adding only one ringing mode on the same SIP interface.l The 16 user-defined ringing modes can be modified but cannot be added.

Procedure

Step 1 According to the Usage Guidelines of the ringmode add command, check whether the presetringing mode in the system meets the requirement.l If the requirement is met, go to Step 4.l If the requirement is not met, go to Step 2.

Step 2 In the global config mode, run the user defined-ring modify command to configure the user-defined ringing mode.

NOTE

l To use the user-defined ringing mode, perform this step and you can define the 0-15 ringing types.

l After configuring the user-defined ringing mode, you need to reset the corresponding service board tomake the configuration take effect, so that the user of the service board can use the new ringing mode.If the service board has been in service for a period, evaluate the impact on the online users beforeresetting the service board, and then determine whether to perform this operation.

Step 3 Run the display user defined-ring command to query the user-defined ringing.

Step 4 Run the interface sip command to enter the SIP mode.

Step 5 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. Thekey 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

corresponds to user-defined ringing modes 0-15.


Configuration Guide


Issue 04 (2011-04-27)

Step 6 Run the display ringmode command to query ringing mapping records.

----End

ExampleAssume that:l Index of the ringing mode mapping record: 1l Name of the ringing mode mapping record: alert-groupl Cadence ringing mode: 1l Initial ringing mode: 4To add such a ringing mode mapping record on SIP interface 0, do as follows:

huawei(config)#interface sip 0huawei(config-if-sip-0)#ringmode add 1 alter-group cadencering 1 initialring 4huawei(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 -----------------------------------------------------------------

7.2.2 Configuring the VoIP PSTN UserAfter an SIP interface is configured, you can add public switched telephone network (PSTN)users on the SIP interface to implement the VoIP service.

1. 7.2.2.1 Configuring the PSTN User DataThis topic describes how to configure the PSTN user data (the same as the correspondingdata on the IMS) on the SIP interface so that the POTS terminal can access the network toimplement the VoIP service.

2. 7.2.2.2 Configuring the CentrexCentrex refers to a virtual user group. The MA5612 supports the following functions:Members in a centrex can call each other by dialing short numbers, and members in acentrex can call the members outside of the centrex by dialing centrex prefix + the completephone number.



5. 7.2.2.5 (Optional) Configuring the Local DigitmapLocal digitmap is also called local preconfigured digitmap. When the H.248 protocol isused, the MA5612 prefers to use the digitmap sent by the MGC to match the phone number.If the MGC does not send the detailed digitmap, the MA5612 uses the local digitmap tomatch the phone number. When the SIP protocol is used, the MA5612 has to use the localdigitmap to match the phone number because the IMS network does not send the digitmap.



7-45

When configuring services on the MA5612, configure a proper local digitmap accordingto the local standards.

6. 7.2.2.6 (Optional) Configuring the Attributes of a PSTN PortThis topic describes how to configure the attributes of a PSTN port to ensure that the PSTNport can meet the actual application requirements.

7. 7.2.2.7 (Optional) Configuring the Attributes of the Ringing CurrentYou 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 modifythe attributes of the ringing current according to the local standards only when the defaultringing current attributes do not meet the local standards.

7.2.2.1 Configuring the PSTN User Data

This topic describes how to configure the PSTN user data (the same as the corresponding dataon the IMS) on the SIP interface so that the POTS terminal can access the network to implementthe VoIP service.

Prerequisite

The POTS service board must be inserted into the planned slot.

NOTE

You can add a service board in two ways (see the Usage Guideline of the board add command). It isrecommended that you insert the service board into the planned slot and then confirm the board.

Context

Table 7-12 lists the default settings of the attributes of the PSTN user. When configuring theattributes of the PSTN user, you need to modify them according to the service requirements.

Table 7-12 Default settings of the attributes of the PSTN user


Sequence of sending the phonenumber of the calling party

Ringing and then sending the phone number

Format of the phone number of thecalling party

FSK single data message format

Power-off interval 10 ms

FSK delay interval 10 ms

Display mode of the FSK phonenumber of the calling party

BELL_202

Whether to enable or disable VQEautomatic gain

Disable

Whether to enable or disable VQEnoise suppression

Disable

Target value of VQE automatic gain -22 dBm0


Configuration Guide


Issue 04 (2011-04-27)


Target value of VQE noisesuppression

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 notconfigured.)

Whether to support the detection ofthe ANSbar signal throughmonophony

Not support

Whether to support the bell ANSsignal

Not support

TAS CID mode NO-TAS

Procedure

Step 1 In global config mode, run the board confirm command to confirm the service board.

NOTEYou need not run this command if the board is integrated in the mother board.

Step 2 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 addPSTN users in batches.

CAUTIONWhen adding a user, you can configure the phone number (parameter telno). When thepublic ID is generated by phone number, you must enter the phone number. It isrecommended that you configure this phone number to be the same as the phone numberconfigured 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 sameas the planned data.

Step 3 (Optional) Configure the attributes of a PSTN user.

The attributes of a PSTN user need to be configured when the default settings are inconsistentwith the actual application.

1. Run the sippstnuser attribute set or sippstnuser attribute batset command to configurethe attributes of a PSTN user.



7-47

2. Run the display sippstnuser attribute command to check whether the attributes of thePSTN user are the same as the planned data.

----End

Example

Assume that the phone numbers of 16 PSTN users are 83120000-83120015 and the defaultvalues are used for other attributes. To add the 16 PSTN users in slot 0/3 on SIP interface 0 inbatches, do as follows:

huawei(config)#esl userhuawei(config-esl-user)#sippstnuser batadd 0/3/0 0/3/15 0 telno 83120000 step 1huawei(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 ---------------------------------------

7.2.2.2 Configuring the Centrex

Centrex refers to a virtual user group. The MA5612 supports the following functions: Membersin a centrex can call each other by dialing short numbers, and members in a centrex can call themembers outside of the centrex by dialing centrex prefix + the complete phone number.

Contextl The function that the members in a centrex can call each other by dialing short numbers

need not be configured on the MA5612 through the command line interface (CLI).

l The function that the members in a centrex can call the members outside of the centrex bydialing centrex prefix + the complete phone number can be supported only when the SIPprotocol is used.

l The centrex attribute of a centrex can be direct centrex or two-stage centrex. The similarityand difference are as follows:

– Similarity: When the members in a centrex need to call the members outside of thecentrex, they must dial the centrex prefix.

– Difference: If the centrex attribute is set to two-stage centrex, the members in a centrexcan hear the dial tone again after dialing the centrex prefix.

l In the actual configuration, configure whether the phone number reported by theMA5612 contains the centrex prefix according to the local standards. This function iscontrolled by the one hundred and fourty-eighth control point of the Sipprofile. The optionsof the parameter are 0 and 1, where 0 indicates that the phone number does not contain thecentrex prefix and 1 indicates that the phone number contains the centrex prefix. By default,this parameter is configured to 1.

Precaution

The MA5612 supports the configuration of the centrex prefix through one of the following twomethods:


Configuration Guide


Issue 04 (2011-04-27)

l Method 1: Run the sippstnuser servicedata parameters set command to configure thecentrex prefix and centrex attributes of a centrex.

l Method 2: Run the local-digitmap add command to add a direct centrex digitmap or a two-stage centrex digitmap.

CAUTIONThe system does not support the adding of a direct centrex digitmap and a two-stage centrexdigitmap at the same time. Add the corresponding digitmap according to the requirements.When you add a direct centrex digitmap, the centrex attribute of the system is direct centrex.When you add a two-stage centrex digitmap, the centrex attribute of the system is two-stagecentrex.

l If both the operations are carried out successfully through the preceding methods, thesystem adopts the configuration obtained through the sippstnuser servicedata parametersset command.

l If method 2 is adopted, the MA5612 uses the centrex digitmap to match the centrex prefix,and then uses the call digitmap, namely, the normal digitmap, to match the phone numberdialed by the user.

ProcedureStep 1 Check whether the value of the control point of the Sipprofile needs to be changed. If the value

needs to be changed, run the interface sip command to enter the SIP interface mode, and thenrun the sipprofile modify command to change the value to the required one.

Step 2 Configure the centrex call function of a centrex.l Configure the centrex call function by using method 1 in Precaution:1. In ESL user mode, run the sippstnuser servicedata parameters set command to configure

the centrex prefix and centrex attributes of a centrex.2. Run the display sippstnuser servicedata command to check whether the configuration of

the centrex parameters of a centrex is the same the planned configuration.l Configure the centrex call function by using method 2 in Precaution:1. In global config mode, run the local-digitmap add command to configure a direct centrex

digitmap or a two-stage centrex digitmap.2. Run the display local-digitmap command to check whether the local digitmap is the same

as the planned local digitmap.

----End

ExampleAssume that the centrex prefix of the 0/3/0 user with phone number 88627792 is 8100, thecentrex attribute is two-stage centrex, and the control point of the Sipprofile uses the defaultvalue.

To configure the centrex call function for such a user by using method 1, do as follows:huawei(config)#esl userhuawei(config-esl-user)#sippstnuser servicedata parameter set 0/3/0 telno 88627792



7-49

centrexprefix 8100 centrexflag dialsecondaryhuawei(config-esl-user)#display sippstnuser servicedata 0/3/0 telno 88627792 ---------------------------------------- F /S /P : 0 /3 /0 telno : 88627792 centrexno : - centrexprefix : 8100 centrexflag : dialsecondary mwimode : deferred hottime(s) : 100 hotlinenum : - dialtone : normal cfbnum : - cfnrnum : - cfunum : - cfnrtime(s) : 100 ----------------------------------------

To configure the centrex call function for such a user by using method 2, and plan the digitmapbody to (8100) and the digitmap name to huawei1 for the two-stage centrex digitmap accordingto the centrex prefix, do as follows:

huawei(config)#local-digitmap add huawei1 second-centrex (8100)huawei(config)#display local-digitmap all ------------------------------------------ Name: DefaultNormalDmm Type: normal Body: x.S ------------------------------------------ Name: DefaultSccDmm Type: scc Body: (ExxFx.E|ExxFx.L|ExFx.E|ExFx.L|Exx.F|EFxx.F|Fxx.F|Ex.Ex.F) ------------------------------------------ Name: DefaultEmergencyDmm Type: emergency Body: (11X|91X) ------------------------------------------ Name: huawei1 Type: second-centrex Body: (8100) ------------------------------------------

7.2.2.3 (Optional) Configuring the System Parameters

This topic describes how to configure the system parameters including the overseas version flagand message waiting indication (MWI) mode according to the local standards to ensure that theresponse of the user terminal complies with the local standards.

Context

Table 7-13 lists the system parameters supported by the MA5612.






0: Indicates China.


Configuration Guide


Issue 04 (2011-04-27)










1: Send

Procedure

Step 1 Run the system parameters command to configure the system parameters.


----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 -----------------------------------------------------------------------------

7.2.2.4 (Optional) Configuring the Overseas Parameters

By default, the overseas parameters are configured according to the Chinese standards. In theactual service configuration, the attributes such as the upper and lower thresholds of the flash-hooking duration can be configured according to the local standards to ensure that the responseof the user terminal complies with the local standards.

Context

Table 7-14 lists the overseas parameters supported by the MA5612.



7-51










Line B offset

Procedure



----End


huawei(config)#oversea parameters 0 800huawei(config)#oversea parameters 1 100huawei(config)#display oversea parameters ----------------------------------------------------------------------------- Parameter name index: 0 Parameter value: 800 Mean: Hooking upper threshold(ms), reference: China:350, HongKong:800 ----------------------------------------------------------------------------- Parameter name index: 1 Parameter value: 100 Mean: Hooking lower threshold(ms), reference: China:100, HongKong:100 ----------------------------------------------------------------------------- Parameter name index: 2 Parameter value: 0 Mean: Flag of applying PARKED LINE FEED or not when user port is locked, 0:not apply, 1:apply ----------------------------------------------------------------------------- Parameter name index: 3 Parameter value: 1 Mean: Type of ring DC offset, 0:Line A offset, 1:Line B offset -----------------------------------------------------------------------------

7.2.2.5 (Optional) Configuring the Local DigitmapLocal digitmap is also called local preconfigured digitmap. When the H.248 protocol is used,the MA5612 prefers to use the digitmap sent by the MGC to match the phone number. If theMGC does not send the detailed digitmap, the MA5612 uses the local digitmap to match thephone number. When the SIP protocol is used, the MA5612 has to use the local digitmap tomatch the phone number because the IMS network does not send the digitmap. When configuringservices on the MA5612, configure a proper local digitmap according to the local standards.


Configuration Guide


Issue 04 (2011-04-27)

Context

CAUTIONWhen the H.248 protocol is used, the local digitmap need not be configured by default. You canconfigure the local digitmap according to the requirements.

l When the H.248 protocol is used, the MA5612 is not configured with a default localdigitmap. You can configure a local digitmap if required.

l When the SIP protocol is used, the MA5612 is configured with three default local digitmaps,namely, normal digitmap, emergency digitmap, and SCC digitmap. You can change thename and type of the default local digitmaps, and add or change the digitmap body in thedefault local digitmaps. In addition, you can add a local digitmap according to therequirements. Table 7-15 lists the information about the default local digitmap.

Table 7-15 Information about the default local digitmap when the SIP protocol is used


DefaultNormalDmm normal x.S

DefaultSccDmm scc ([EF]X[0-9E].F|[EF]X[0-9E].S|[EF][EF]X[0-9E].F|[EF][EF]X[0-9E].S)

DefaultEmergencyDmm emergency (11X|91X)

l The MA5612 supports a maximum of eight local digitmaps.l For the meaning of each character in the digitmap body, see the Context in 7.1.1.4

(Optional) Configuring the Digitmap of an MG Interface.

Precautionl When the H.248 protocol is used, the type of the local digitmap can only be normal.l 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 theParameter Description in the local-digitmap add command.

Procedure

Step 1 In privilege mode, run the display protocol support command to query the current protocoltype used on the MA5612.l When the H.248 protocol is used, go to Step 5.l When the SIP protocol is used, go to Step 2.

Step 2 In privilege mode, run the display local-digitmap command to query the default local digitmap.l If the default local digitmap can meet the requirements, the configuration is complete.



7-53

l If the default local digitmap cannot meet the requirements, perform one or more operationsin Step 3, Step 4, and Step 5 to configure a proper local digitmap.

Step 3 Run the local-digitmap modify command to change the name, type, or body of the localdigitmap.

Step 4 Run the local-digitmap append command to add a digitmap body in the local digitmap.

Step 5 According to the data plan, run the local-digitmap add command to add a local digitmap.

Step 6 Run the display local-digitmap command to check whether the local digitmap is the same asthe planned local digitmap.

----End

ExampleAssume that the H.248 protocol is used on the MA5612. To add a local digitmap with the datalisted in Table 7-16, do as follows:




huawei(config)#local-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S)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) ------------------------------------------

Assume that the SIP protocol is used on the MA5612. The local digitmap exists in the system.Table 7-17 lists the data of the local digitmap.




To change the existing local digitmap so that the name of the local digitmap is huawei0, adddigitmap body 15xxxxxxxxx, and add a local digitmap according to data plan listed in Table7-18, do as follows:


Configuration Guide


Issue 04 (2011-04-27)

Table 7-18 Local digitmap to be added


huawei1 emergency (0E)

huawei(config)#display local-digitmap all ------------------------------------------ Name: DefaultNormalDmm Type: normal Body: x.S ------------------------------------------ Name: DefaultSccDmm Type: scc Body: (ExxFx.E|ExxFx.L|ExFx.E|ExFx.L|Exx.F|EFxx.F|Fxx.F|Ex.Ex.F) ------------------------------------------ Name: DefaultEmergencyDmm Type: emergency Body: (11X|91X) ------------------------------------------ Name: huawei Type: normal Body: ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S) ------------------------------------------huawei(config)#local-digitmap modify huawei name huawei0huawei(config)#local-digitmap append huawei0 15xxxxxxxxxhuawei(config)#local-digitmap add huawei1 emergency (11X|91X|0E)huawei(config)#display local-digitmap all ------------------------------------------ Name: DefaultNormalDmm Type: normal Body: x.S ------------------------------------------ Name: DefaultSccDmm Type: scc Body: (ExxFx.E|ExxFx.L|ExFx.E|ExFx.L|Exx.F|EFxx.F|Fxx.F|Ex.Ex.F) ------------------------------------------ Name: DefaultEmergencyDmm Type: emergency Body: (11X|91X) ------------------------------------------ Name: huawei0 Type: normal Body: ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx|9xxxx|1[0124-9]x|F|x.F|[0-9].S|15xxxxxxxxx) ------------------------------------------ Name: huawei1 Type: emergency Body: (11X|91X|0E) ------------------------------------------

7.2.2.6 (Optional) Configuring the Attributes of a PSTN PortThis topic describes how to configure the attributes of a PSTN port to ensure that the PSTN portcan meet the actual application requirements.

ContextThe MA5612 supports the following attributes of a PSTN port:



7-55

l Physical attributes (including whether to support the polarity reversal pulse, whether tosupport the port locking, and dialing mode). For details about how to configure the physicalattributes of a PSTN port, see pstnport attribute set.

l Electrical attributes (including the impedance and the current). For details about how toconfigure the electrical attributes of a PSTN port, see pstnport electric set.

l KC attributes (including the KC charging mode and the valid voltage). For details abouthow to configure the KC attributes of a PSTN port, see pstnport kc set.

Procedure

Step 1 In global config mode, run the pstnport command to enter the PSTN port mode.

Step 2 Run the pstnport attribute batset or pstnport attribute set command to configure the physicalattributes of a PSTN port.

Step 3 Run the pstnport electric batset or pstnport electric set command to configure the electricalattributes of a PSTN port.

Step 4 Run the pstnport kc batset or pstnport kc set command to configure the KC attributes of thePSTN port.

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.l Run the display pstnport electric command to query the electrical attributes of the PSTN

port.l Run the display pstnport kc command to query the KC attributes of the PSTN port.

----End

ExampleTo configure the 16 PSTN ports on the board in slot 0/3 to support the polarity reversal charging,do as follows:

huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse enablehuawei(config-pstnport)#display pstnport attribute 0/3 -------------------------------------------------------------------- F /S /P 0 /3 /0 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable -------------------------------------------------------------------- F /S /P 0 /3 /1 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable -------------------------------------------------------------------- ......


Configuration Guide


Issue 04 (2011-04-27)

-------------------------------------------------------------------- F /S /P 0 /3 /15 ReversePolepulse Enable PulseLevel 100(ms) PolarityReverseMode Hard-polarity-reverse Dial-Mode DTMF-Pulse-Both LineLock Enable NlpMode Nlp normal mode PolarityReverseWhenCLIP Disable --------------------------------------------------------------------

NOTE

When a call starts and ends, the MG shows the start time and the end time based on the polarity reversalon the subscriber line. The billing terminal that supports the polarity reversal charging function, such as acharging phone set, implements the polarity reversal charging function based on the start time and the endtime of a call.

7.2.2.7 (Optional) Configuring the Attributes of the Ringing CurrentYou 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 theattributes of the ringing current according to the local standards only when the default ringingcurrent attributes do not meet the local standards.

ContextThe 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.l AC voltage amplitude: The greater the amplitude is, the louder the ringing tones are.

The default settings of the attributes of the ringing current are as follows:

l Ringing current frequency: 25 Hzl AC voltage amplitude: 50 Vrms

Procedure

Step 1 In the global config mode, run the voip command to enter the VoIP mode.

Step 2 Run the ring attribute set command to configure the attributes of the ringing current accordingto the data plan.

Step 3 Run the display ring attribute command to check whether the attributes of the ringing currentare the same as the planned data.

----End

ExampleTo set the ringing current frequency to 16 Hz (parameter value 0) and AC amplitude to 65 Vrms(parameter value 1), do as follows:

huawei(config)#voiphuawei(config-voip)#ring attribute set frequency 0 acamplitude 1huawei(config-voip)#display ring attribute ringing current frequency : 16HZ ringing current acamplitute: 65VRMS



7-57

7.3 Configuring the VoIP ISDN PRA Service (Based on theH.248 Protocol)

This topic describes how to configure the VoIP ISDN PRA service on an IP network. When theMA5612 uses the H.248 protocol, the device supports the access of the ISDN PRA user. ISDNprovides end-to-end (E2E) digital connection and supports multiple types of voice and non-voicetelecom services.

PrerequisiteAccording to the actual network, a route from the MA5612 to the MGC must be configured toensure that the MA5612 communicates with the MGC normally.

Contextl The voice over IP (VoIP) service uses the IP packet switched network for transmission

after the traditional analog voice signals are compressed and packetized. This service lowersthe cost of the voice service. For the detailed description of the VoIP service, see VoiceFeature in the Feature Description.

l Defined by the International Telegraph and Telephone Consultative Committee (CCITT),the ISDN is a communication network evolved from the Integrated Digital Network (IDN).The ISDN service provides the E2E digital connection and supports multiple types of voiceand non-voice telecom services. On the ISDN network, users can access the networkthrough the following two interfaces: (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 controlsignaling and maintenance and management signaling). The rate of B channels is 64kbit/s and the rate of D channel is 16 kbit/s. The service carried on the ISDN BRI is theISDN basic rate access (BRA) service.

– ISDN primary rate interface (PRI), which supports a rate of 2.048 Mbit/s and provides30 B channels and one D channel. The rates of the B channel and D channel are both64 kbit/s. The service carried on the ISDN PRI is the ISDN primary rate access (PRA)service.

l The MA5612 supports only the VoIP ISDN PRA service.l The MA5612 connects to the ISDN PRA users through the E1 port on the H831E81A board.

For details of the H831E81A board, see E81A Board in the Product Description.

PrecautionThe media gateway control protocol (MGCP) is a master/slave protocol, under which the MGCcontrols the AG to implement the call connection. The data on the AG for the interconnectionwith 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 VoIPservice, you must contact MGC engineers to check and ensure that the interconnection data planfor the AG is consistent with the corresponding plan for the MGC.

Data preparationTable 7-19 provides the data plan for configuring the H.248-based VoIP ISDN BRA service.


Configuration Guide


Issue 04 (2011-04-27)

Table 7-19 Data plan for configuring the H.248-based VoIP ISDN BRA service

Item Remarks

IUA link IUA link set The IUA link can be configuredonly after the IUA link set isconfigured.

IUA linkNOTE

The local portID, local IPaddress,remote portID, andremote IPaddress ofdifferent linksmust not becompletelysame;otherwise, theservice cannotbeconfigured.

IUA link ID It indicates the link fortransmitting the signaling.

IUA link set ID -

Local port ID To activate the link normally, itmust be the same as the remoteport ID configured on the MGC.

Local IPaddress

It must be the same as the remoteIP address of the link configuredon the MGC. In addition, the localIP addresses of the links that arein the same link set must be thesame. (The IP address must existin the media IP address pool.)

Remote portID

To activate the link normally, itmust be the same as the local portID configured on the MGC.

Remote IPaddress

It must be the same as the local IPaddress of the link configured onthe MGC. The SCTP protocolsupports the multi-homingfunction. That is, one link can beconfigured with the IP addressesof multiple MGCs as the remoteIP addresses. When one MGC isfaulty, the link can be switched toother MGCs automatically. Thisensures that the service is notaffected. The MA5612 supportsthe configuration of the activeremote IP address and standbyremote IP address.

MG interface data(The data must beconsistent with thedata on the MGC.)

Parameters ofthe mediastream andsignalingstream

UpstreamVLAN formedia andsignalingstreams

It is used as the upstream VLANof the VoIP service to beconfigured. Standard VLAN isrecommended.

Uplink port formedia andsignalingstreams

It is used as the uplink port for theVoIP service to be configured.



7-59

Item Remarks

Media IPaddress andsignaling IPaddress

These IP addresses must becontained in the media andsignaling IP address pools. Themedia and signaling IP addresspools consist of all the IPaddresses of the L3 interface ofthe upstream VLAN for mediaand signaling streams.

Default IPaddress of theMG

It is the next hop IP address fromthe MA5612 to the MGC.

Attributeparameters ofthe MGinterfaceNOTE

Parameterslisted here aremandatory,which meansthat the MGinterfacecannot bestarted if theseparametersare notconfigured.

MG interfaceID

It is the ID of the MG interfaceused by the VoIP service to beconfigured. The MA5612supports only one VAG.

Signaling portID of the MGinterface

It is the transport layer protocolport ID used for the signalingexchange between the MA5612(AG) and the MGC.The default signaling port IDdefined in H.248 is 2944 (text)and 2945 (binary).

IP address ofthe primaryMGC to whichthe MGinterfacebelongs

When dual homing is notconfigured, you can configure theparameters of only the primaryMGC. When dual homing isconfigured, you also need toconfigure the IP address and portID of the secondary MGC.

Port ID of theprimary MGCto which theMG interfacebelongs

Coding modeof the MGinterface

Currently, only the text mode issupported.

Transmissionmode of theMG interface

The transmission mode isselected according to therequirements of the MGC.Generally, UDP is used.


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

Domain nameof the MGinterface

It corresponds to thedomainName parameter of theMG interface.When the H.248 protocol is used,this parameter must beconfigured if the MIDTypeparameter of the H.248 messageis configured to domainName.Otherwise, the MG interfacecannot be started. In othersituations, this parameter isoptional.

Device nameof the MGinterface

It is supported by only the H.248protocol, and it corresponds to thedeviceName parameter of theMG interface that uses the H.248protocol.This parameter must beconfigured if the MIDTypeparameter of the H.248 messageis configured to domainName.Otherwise, the MG interfacecannot be started. In othersituations, this parameter isoptional.

Digitmap of the MG interface The digitmaps are used for certainspecial applications such asemergency calls and emergencystandalone. The digitmaps forcommon phone services areissued to the AG by the MGC, andtherefore such digitmaps need notbe configured on the AG. If theservices such as emergency callsand emergency standalone arenot required, this parameter neednot be configured.

Software parameters of theMG interface

Whether the MG interfacesupports the functions such asdual homing and emergencystandalone is determined by theservice requirements.

Ringing mode of the MGinterface

Which ringing mode is used bythe MG interface is determinedby the service requirements.



7-61

Item Remarks

Terminal ID (TID) format ofthe MG interface

The TID format determines thegeneration mode of various typesof user terminals on an MGinterface.

ISDN PRA user data(The data must beconsistent with thedata on the MGC.)

Slot that houses the E1 serviceboard

-

User data TerminationID

If the TID format bound to thePRA user does not supportterminal layering function, thisparameter needs to be configured,and the configuration must beconsistent with the configurationon the MGC.

User priority The user priority must bespecified according to the servicerequirements. There are threecategories 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)

Interface ID It indicates the interface for thePRA user data to pass through theMG and MGC. The configurationof this parameter must beconsistent with the correspondingconfiguration on the MGC.

System parameters The system parameters includingthe oversea version flag andmessage waiting indication(MWI) mode need to beconfigured according to the localstandards to ensure that theresponse of the user terminalcomplies with the local standards.

Overseas parameters The attributes such as the upperand lower thresholds of the flash-hooking duration need to beconfigured according to the localstandards to ensure that theresponse of the user terminalcomplies with the local standards.


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

E1 port attributes The attributes include the accessmode of the board, port mode,line coding mode, and portimpedance. Generally, if there isno requirement, these attributesneed not be modified.

1. 7.3.1 Configuring an MG InterfaceThis topic describes how to configure an MG interface for implementing thecommunication between the MA5612 (AG) and the MGC.

2. 7.3.2 Configuring the IUA LinkThis topic describes how to configure the IUA link for signaling transmission between theMA5612 and MGC in the VoIP ISDN PRA service.

3. 7.3.3 Configuring the VoIP ISDN PRA UserThis topic describes how to configure the VoIP ISDN PRA user. After the MG interface isconfigured, you can add the VoIP ISDN PRA user on this interface to implement the VoIPISDN PRA service.

7.3.1 Configuring an MG InterfaceThis topic describes how to configure an MG interface for implementing the communicationbetween the MA5612 (AG) and the MGC.

Contextl The MA5612 communicates with the MGC through the MG control protocol, that is, the

H.248 protocol.l One MA5612 supports up to one MG interface. The MG interface can be configured with

the attributes such as authentication and ringing mapping.

1. 7.3.1.1 Configuring the Upstream VLAN InterfaceThis topic describes how to specify the upstream VLAN interface for the media stream andsignaling stream, and how to configure the IP addresses of the L3 interface. These IPaddresses are the sources of the media and signaling IP address pools.


3. 7.3.1.3 Adding an MG InterfaceThis topic describes how to add an MG interface, through which the MA5612 cancommunicate with the MGC.

4. 7.3.1.4 (Optional) Configuring the Digitmap of an MG InterfaceThis topic describes how to configure the digitmaps for certain special applications suchas emergency calls and emergency standalone. The digitmaps for common phone servicesare issued to the AG by the MGC, and therefore such digitmaps need not be configured onthe AG. If the services such as emergency calls and emergency standalone are not required,the digitmaps need not be configured.

5. 7.3.1.5 (Optional) Configuring the Software Parameters of an MG Interface



7-63

The software parameters of an MG interface mainly define certain common serviceattributes of the MG interface. After the configuration of the software parameters of an MGinterface, the software parameters take effect immediately and the configuration is validonly to the MG interface.

6. 7.3.1.6 (Optional) Configuring the Ringing Mode of an MG InterfaceThis topic describes how to configure the ringing mode of an MG interface to meet differentuser requirements.

7. 7.3.1.7 (Optional) Configuring the TID Format of an MG InterfaceThe TID format determines how various user terminal IDs on the MG interface aregenerated.

8. 7.3.1.8 Enabling an MG InterfaceEnabling an MG interface is to reset an MG interface to make the MG interface registerwith the MGC (or to make the modified attributes of the MG interface take effect) after theconfiguration of the MG interface is complete, so that the MG interface can work in thenormal state.



Procedure









----End

ExampleAssume that the media stream and signaling stream are transmitted upstream through upstreamport 0/0/1. To create media and signaling upstream VLAN 3 and configure IP addresses


Configuration Guide


Issue 04 (2011-04-27)

10.13.4.116/16 and 10.13.4.117/16 of the L3 interfaces for the media IP address pool and thesignaling IP address pool respectively, do as follows:




Prerequisite



selected from the IP address pools configured here.

l The signaling IP address pool is used to store the IP addresses of the MG or SIP interfaces,and the media IP address pool is used to store the IP addresses of the media streamscontrolled by the signaling.


Procedure



pool.



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.



7-65



----End

Example



7.3.1.3 Adding an MG Interface

This topic describes how to add an MG interface, through which the MA5612 can communicatewith the MGC.

Context

One MA5612 supports up to one MG interface.

Procedure


Run the interface h248 command to add an MG interface that supports H.248 protocol.

Step 2 Configure the attribute of the MG interface.

Run the if-h248 attribute command to configure the attribute of the MG interface according tothe data plan.


Configuration Guide


Issue 04 (2011-04-27)

NOTE

If the MGC interconnected with the MG is provided by Huawei, the profile (namely, parameter profile-index) need not be configured. If the MGC interconnected with the MG is provided by another vendor, theprofile must be configured. (The parameter value is prompted in the CLI.)

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 interfaceis the same as that in the data plan.

----End

ExampleAssume that the MG interface ID is 0 and the H.248 protocol is used for interconnecting withthe MGC. To add the MG interface, do as follows:

huawei(config)#interface h248 0 Are you sure to add MG interface?(y/n)[n]:yhuawei(config-if-h248-0)#if-h248 attribute mgip 10.13.4.116 mgport 2944 code text primary-mgc-ip1 10.13.2.118 primary-mgc-port 2944 mg-media-ip1 10.71.46.69 mg-media-ip2 10.13.4.117start-negotiate-version 0 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 0:Customizing_0/1("Customizing_0/1") 2833Encrypt - Codetype Text Transfer Mode UDP HeartBeatGenTimer(s) 60 HeartBeatRetransTimes 3 HeartBeatRetransTimer(s) 60 MG signalling IP 10.13.4.116 MG signalling Port 2944 MG media IP1 10.13.4.116 MG media IP2 10.13.4.117 MIDType IP4_ADDR DeviceName - Retrans Enable

Active MGC MGC Port :2944 MGC IP1:10.13.2.118 Active MGC MGC Port :2944 MGC IP2:- Active MGC MGC Domain Name:- Standby MGC MGC Port :- MGC IP1:- Standby MGC MGC Port :2944 MGC IP2:- Standby MGC MGC Domain Name:- -------------------------------------------------

7.3.1.4 (Optional) Configuring the Digitmap of an MG InterfaceThis topic describes how to configure the digitmaps for certain special applications such asemergency calls and emergency standalone. The digitmaps for common phone services areissued 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 digitmapsneed not be configured.



7-67

Context

CAUTIONThe digitmap configuration is relatively complicated. The information such as the meanings andusage of the characters in a digitmap is defined in the protocol, and is not described here. Thistopic provides only some basic information. It is recommended that you refer to the digitmapdescription in ITU-T H248.1 (applicable to H.248) before configuring the digitmap.

l A digitmap is a set of digit collection descriptors. It is a dialing scheme resident in the MGand is used for detecting and reporting digit events received on a termination. The digitmapis used to improve the efficiency of the MG in sending the callee number. That is, if thecallee number matches a dialing scheme defined by the digitmap, the MG sends the calleenumber collectively in a message.

l A digitmap consists of strings of digits with certain meanings. When the received dialingsequence matches one of the strings, it indicates that the digits are collected completely.

l 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

l Emergency call digitmap (due to call restriction in the case of an overload)

l Automatic redial digitmap of the card service

Table 7-20 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 abetter guide to the digitmap configuration.

Table 7-20 Digitmap format in the H.248 protocol

Digit orCharacter

Description

0-9 Indicate dialed digits 0-9.

A-D Indicate A-D.

E Indicates * in the DTMF mode.

F Indicates for # in the DTMF mode.

X Indicates for a wildcard, indicating any digit from 0 to 9.

S Indicates the short timer. When detecting the timer timeout, the system reportsa phone number digit by digit if the phone number is detected after the dialingscheme is matched.

L Indicates the long timer. When detecting the timer timeout, the system reportsa phone number digit by digit if the phone number is detected after the dialingscheme is matched.


Configuration Guide


Issue 04 (2011-04-27)

Digit orCharacter

Description

Z Indicates the duration modifier, which indicates a dialing event of a longduration. It is before the event character with a fixed location. When the eventduration exceeds the threshold, the dialing event fills the location.

. Indicates that there can be multiple digits (including 0) or characters beforeit.

| Used to separate the strings and indicates that each string is an optional dialingscheme.

[] 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 prevailsregardless of whether a timer is configured on the AG. When the MGC does not issue thedigitmap timer and the default digitmap timer does not meet the service requirements, you canconfigure 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 configuredcorrectly.

----End

Example

Assume that the inner digitmap of the H.248-based MG interface is configured. According tothe data plan, the inner digitmap format is 1234xxxx. The digitmap timer is not configuredbecause it is issued by the MGC. To configure the inner digitmap, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#digitmap set inner 1234xxxxhuawei(config-if-h248-0)#display digitmap ---------------------------------------------------------------------- Inner digitmap : 1234xxxx Urgent digitmap (for overload or bandwidth restrict) : - Dualdial digitmap for card service : - ----------------------------------------------------------------------



7-69

7.3.1.5 (Optional) Configuring the Software Parameters of an MG InterfaceThe software parameters of an MG interface mainly define certain common service attributesof the MG interface. After the configuration of the software parameters of an MG interface, thesoftware parameters take effect immediately and the configuration is valid only to the MGinterface.

ContextThere are 32 software parameters (numbered from 0 to 31) of an MG interface that supports H.248. Table 7-21 lists the configurable parameters, and the other parameters are reserved in thesystem.

Table 7-21 Software parameters of an MG interface that supports H.248


2 Indicates whether the MGinterface supports dual homing.To configure an MG interfaceto or not to support dualhoming, use this parameter.If the MG interface does notsupport dual homing, even if thesecondary MGC is configured,the MG interface does notswitch to registering with thesecondary MGC when the MGinterface fails to register withthe primary MGC. If the MGinterface supports dual homingand auto-switching, even if theMG interface has registeredwith the secondary MGC, theMG interface can automaticallyswitch back to the primaryMGC if the primary MGCrecovers.

Numeral type. Range: 0-2.l 0: indicates that dual homing

is not supported.l 1: indicates that dual homing

rather than auto-switching issupported.

l 2: indicates that dual homingand auto-switching issupported.

Default: 0


-


Configuration Guide


Issue 04 (2011-04-27)


4 Indicates whether a wildcard isused for the registration of theMG interface.To configure whether awildcard is used for theregistration of an MG interface,use this parameter.Using a wildcard forregistration can reduce thequantity of messages betweenthe MG interface and the MGC.When the wildcard is not usedfor registration, all the terminalson the MG interface need toregister with the MGC in order.The registration without awildcard is also called "single-endpoint registration".

Numeral type. Range: 0-1.l 0: indicates that a wildcard is

used.l 1: indicates that a wildcard is

not used.Default: 0


-

6 Indicates whether the MGinterface supports deviceauthentication.To configure an MG interfaceto or not to supportauthentication, use thisparameter.After the device authenticationis supported, run the authcommand to configure theauthentication parameters, andthen run the reset command toreset the MG interface. In thisway, the MGC can manage thesecurity of the MGs and avoidillegal registration with theMGC.

Numeral type. Range: 0-1.l 0: indicates that device

authentication is supported.l 1: indicates that device

authentication is notsupported.

Default: 1

7 Indicates whether the MGinterface supports securityheader.To configure an MG interfaceto or not to support securityheader, use this parameter.

Numeral type. Range: 0-1.l 0: indicates that security

header is supported.l 1: indicates that security

header is not supported.Default: 1


-



7-71



-

11 Indicates whether the MGinterface supports emergencystandalone.To configure whether an MGinterface supports emergencystandalone, use this parameter.If the MG interface supportsemergency standalone, theusers on the MG interface canmake phone calls even if theMG fails to communicate withthe MGC.

Numeral type. Range: 0-3.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 arepermitted.

Default: 0

13 Indicates the maximumdigitmap matching flag of theMG interface.To configure digitmapmatching scheme of the MGinterface, use this parameter.Minimum matching indicatesthat the telephone number isreported if it matches thedigitmap completely. If there isno dialing within the duration ofthe short timer (default: 5s), thetelephone number is reportedafter the short timer times out.Otherwise, the system matchesother digitmap schemes.

Numeral type. Range: 0-1.l 0: indicates minimum match.l 1: indicates maximum match.Default: 0


-

15 Indicates whether the functionof filtering media streams bysource port is enabled on an MGinterface.To enable or disable thefunction of filtering mediastreams by source port on anMG interface, use thisparameter.When the function of filteringmedia streams by source port isenabled on the MG interface,only the media streams from thespecific ports can be received.

Numeral type. Range: 0-1.l 0: indicates that media

streams are not filtered bysource port.

l 1: indicates that mediastreams are filtered by sourceport.

Default: 0


Configuration Guide


Issue 04 (2011-04-27)


16 Indicates the length of the timerfor filtering the media streamsource port of the MG interface.To configure the length of thetimer for filtering the mediastream source port of an MGinterface, use this parameter.When an MG interface does notfilter the source port, the MGinterface automatically filtersthe source port if the filteringtimer times out.


22 Indicates the type of the prompttone after the communicationbetween the MG and the MGCis interrupted.

Numeral type. Range: 0-3.l 0: indicates the busy tone.l 1:indicates the device

congestion tone.l 2: indicates the voice prompt.Default: 0

23 Indicates the length of the timerfor synchronizing the portstatus.


24 Indicates the maximum value ofthe Real-Time TransportProtocol (RTP) termination ID.


25 Indicates the maximum randomvalue for the protection againstavalanche of the H.248interface.

Numeral type. Range: 0-120 ms.Default: 60000s.

26 Indicates the type of localblocking play tone.




tone 2.Default: 0



7-73


27 Indicates the type of remoteblocking play tone.




tone 2.Default: 0.

28 Indicates the duration of thehowler tone.


29 Indicates the duration ofmessage waiting tone.


30 Indicates the time limit of thealarm for extra long call.

Numeral type. Range: 1-65535min.Default: 60s

31 Indicates whether to report thealarm for extra long call.

Numeral type. Range: 0-3.l 0: indicates that the alarm is

reported.l 1: indicates that the alarm is

not reported.Default: 1

32 Indicates the minimum intervalfor automatic registration of theremote block port.

Numeral type. Range: 0-60000s.0 indicates that the port does notregister automatically.Default: 1800s

33 Indicates whether the heartbeatmessage is disabled.

Numeral type:l 0: Indicates that the heartbeat

message is disabled.l 1: Indicates that the heartbeat

message is enabled.Default: 1

Procedure




Configuration Guide


Issue 04 (2011-04-27)

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 parametersof the MG interface are the same as those in the data plan.

----End

ExampleTo configure software parameter 11 of H.248-based MG interface 0 to 1 so that the MG interfacesupports emergency standalone and allows only internal calls, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-software parameter 11 1huawei(config-if-h248-0)#display mg-software parameter 11 ------------------------------------------------- Interface Id:0 para index:11 value:1 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 11: Stand alone support 0: None 1: Inner 2: Emergency 3: Both

7.3.1.6 (Optional) Configuring the Ringing Mode of an MG InterfaceThis topic describes how to configure the ringing mode of an MG interface to meet differentuser requirements.

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 theUsage 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 break-make ratio of user-defined ringing mode to form a ringing mode that meets the user requirement.

CAUTIONl The system supports 16 user-defined ringing modes, which can be modified but cannot be

added or deleted.




7-75


Step 4 Add a ringing mapping.

Run the mg-ringmode add command to add a ringing mapping.

CAUTION1. The parameter mgcpara on the MG 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 initialringing 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 thesame as that in the data plan.

----End

ExampleAssume that the MG interface ID is 0, the peer parameter ID issued by the MGC is 0, the cadenceringing is 1:4 (the value of the corresponding parameter cadence is 0), and the initial ringing is1:2 (the value of the corresponding parameter initialring is 17). To configure the ringing modeof MG interface 0, do as follows:

huawei(config)#interface h248 0huawei(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 0, the break-make ratio of user-defined ringing mode 0 is 0.4sec On, 0.2sec Off, 0.4sec On, 2.0sec Off, andthe initial ringing and the cadence ringing use user-defined ringing mode 0 (the values of thecorresponding parameters cadence and initialring are 128 and 144 respectively). To configurethe ringing mode of MG interface 0, do as follows:

huawei(config)#user defined-ring modify 0 para1 400 para2 200 para3 400 para4 2000 Note: Please reset the service board to make configured parameter be validhuawei(config)#display user defined-ring -------------------------------------------------- RingType Para1 Para2 Para3 Para4 Para5 Para6 -------------------------------------------------- 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


Configuration Guide


Issue 04 (2011-04-27)

15 0 0 0 0 0 0 --------------------------------------------------huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-ringmode add 1 128 144huawei(config-if-h248-0)#display mg-ringmode attribute{ <cr>|mgcpara<0,15> }: { <cr>|mgcpara<0,15> }: Command: display mg-ringmode attribute ------------------------------------------------------- MGID PeerPara CadenceRing InitialRing ------------------------------------------------------- 0 1 128 144 -------------------------------------------------------

7.3.1.7 (Optional) Configuring the TID Format of an MG InterfaceThe TID format determines how various user terminal IDs on the MG interface are generated.

Context

CAUTIONThe configuration of the TID format is relatively complicated. The information such as the syntaxrules with which the terminal prefix must comply and the requirements for the character stringof the TID template is defined in the protocol, and is not described here. This topic describesonly some basic information. It is recommended that you refer to the TID description in ITU-TH248.1 before configuring the TID format.

The TID format consists of the terminal prefix and the TID template. The TID template definesthe generation mode of the TID excluding the terminal prefix. A TID consists of a terminal prefixand a character string generated by a TID template.

The TID templates that are bound to various types of users on the MG interface determinewhether 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 notsupport terminal layering.

l If the parameter list of the TID template includes only keywords "F", "S", "P", "B" ("B" isnot available to PSTN users), it indicates that the TID template is used by the layering users.Users bound with this template support terminal layering.

NOTE

The meaning of each keyword is as follows:

l F indicates the shelf ID.

l S indicates the slot ID.

l P indicates the port ID.

l B indicates the B channel ID (only for ISDN BRA and ISDN PRA terminals).

l G indicates the general permanent termination index.

l R indicates the RTP ephemeral termination index (only for the RTP ephemeral termination, whichexists only when the system protocol is H.248. This termination is not involved unless special remarksare provided.)



7-77

When adding a user that supports terminal layering, you cannot and do not have to specify theparameter terminalid because the system automatically allocates a terminal ID. When addinga user that does not support terminal layering, you must specify the parameter terminalid.

You can run the display tid-format command to query the TID formats of various types of userson the current MG interface. In the query result, template-index indicates the index of the TIDtemplate that is bound to the type of users. Then, run the display tid-template command tocheck whether the TID template supports the layering configuration. Hence, you can checkwhether the user supports terminal layering.

Precautionl There are 19 default TID templates (templates 0-18) in the system. The default TID

templates can be referenced, but cannot be added, modified, or deleted.l The configuration of terminal layering on the MG must be the same as that on the MGC.l If certain type of terminals exists on an interface and the interface is not disabled, the

terminal prefix of this type of terminals cannot be modified.l If a certain type of terminals exists on an interface, the TID format (including the terminal

prefix and the index of the TID template) of this type of terminals cannot be changed.l The terminal prefix must comply with the following syntax rules: The prefix must not

exceed 64 characters. Only letters, digits, "_", and "/" are the characters allowed for input.The first character must be a letter, and the last character must not be a digit.

l The length of the TID, which is generated by combining the TID template and the terminalprefix that you configured, must not exceed 64 characters.

Procedure

Step 1 To query the template information.

Run the display tid-template command to query the information about the default TID templateof the system.

Step 2 Check whether the default TID template of the system meets the service requirements.

If the default TID template cannot meet the service requirements, run the tid-template addcommand to add a TID template that meets the service requirements. If the default TID templatemeets the service requirements, 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 pstn command to configure the TID template and the

terminal prefix of the ISDN BRA user.l In H248 mode, run the tid-format pstn command to configure the TID template and terminal

prefix of the ISDN PRA user.


Configuration Guide


Issue 04 (2011-04-27)

Step 5 Check whether the TID template and the terminal prefix are the same as those in the data plan.

Run the display tid-format command to check whether the TID templates and the terminalprefixes of various types of users on the current MG interface are the same as those in the dataplan.

----End

ExampleAssume 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/15/0 and check whetherthe 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 1huawei(config-if-h248-1)#tid-format pstn prefix aln/ template 3huawei(config-if-h248-1)#quithuawei(config)#esl userhuawei(config-esl-user)#mgpstnuser add 0/15/0 1huawei(config-esl-user)#display mgpstnuser 0/15/0{ <cr>|endframeid/slotid/portid<S><1,15> }: Command: display mgpstnuser 0/15/0 ------------------------------------------------------------------------ F /S /P MGID TelNo Priority PotsLineType TerminalID ------------------------------------------------------------------------ 0 /15/0 1 - Cat3 DEL aln/1/16/1 ------------------------------------------------------------------------

7.3.1.8 Enabling an MG InterfaceEnabling an MG interface is to reset an MG interface to make the MG interface register withthe MGC (or to make the modified attributes of the MG interface take effect) after theconfiguration of the MG interface is complete, so that the MG interface can work in the normalstate.

Precaution

CAUTIONFor the MG interface that has been in service, this operation interrupts the ongoing servicescarried on the MG interface. Hence, exercise caution when performing this operation.

Procedure

Step 1 Enter the H248 mode.



7-79

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 normalstate.

l Run the quit command to quit the global config mode, and then run the display if-h248all command to check whether the MG interface is in the normal state.

----End

ExampleTo enable H.248-based MG interface 0, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:yhuawei(config-if-h248-0)#quithuawei(config)#display if-h248 all --------------------------------------------------------------------------------MGID TransMode State MGPort MGIP MGCPort MGCIP/DomainName--------------------------------------------------------------------------------0 UDP Normal 2944 10.10.10.11 2944 10.10.20.11 --------------------------------------------------------------------------------

7.3.2 Configuring the IUA LinkThis topic describes how to configure the IUA link for signaling transmission between theMA5612 and MGC in the VoIP ISDN PRA service.

Contextl Simple Control Transmission Protocol (SCTP) is a connection-oriented protocol. Its most

fundamental function is to provide reliable transmission for interaction messages betweenthe MA5612 and MGC. The SCTP protocol implements services based on the associationbetween two SCTP endpoints. SCTP can be regarded as a transmission layer. Its upperlayer is called SCTP subscriber, and its lower layer is the IP network.

l The IUA link is the carrier of the interaction signaling between the MA5612 and MGC.

1. 7.3.2.1 Adding an IUA Link SetThis 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 IUAlink, you must add a corresponding link set. Otherwise, the link cannot be added.

2. 7.3.2.2 Adding an IUA LinkThis topic describes how to add an IUA link. After the link set is added, you can add anIUA link to carry the Q.931 call signaling for the ISDN user.


Configuration Guide


Issue 04 (2011-04-27)

7.3.2.1 Adding an IUA Link Set

This topic describes how to add an IUA link set. When configuring the VoIP ISDN service, youneed to configure the IUA link to carry the Q.931 call signaling. Before adding an IUA link, youmust add a corresponding link set. Otherwise, the link cannot be added.

Contextl The system supports the configuration of a maximum of two IUA link sets.

l After a link set is configured successfully, the system is in the deactivated state by default.

Procedure

Step 1 In global config mode, run the sigtran command 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 IUAlink 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, pendingduration is 20s, prefix of the IID is b/, IID generation mode is using the binary value that isautomatically generated in ffsspp mode, namely, parameter 2. To add such an IUA link set, doas follows:

huawei(config)#sigtranhuawei(config-sigtran)#iua-linkset add 0 trafficmode override pendingtime 20 iid-map 2 prefix b/huawei(config-sigtran)#display iua-linkset attribute{ <cr>|linksetno<L> }: Command: display iua-linkset attribute ---------------------------------------------------------- LinksetNo :0 MGID :- PendingTime :20 TrafficMode :override C/S-Mode :server IID-Type :integer IID-Map :2 IID-Prefix :b/ Jointly-Work :disable ----------------------------------------------------------

7.3.2.2 Adding an IUA Link

This topic describes how to add an IUA link. After the link set is added, you can add an IUAlink to carry the Q.931 call signaling for the ISDN user.

Prerequisite

The IUA link set must be added.



7-81

Contextl 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.

l The local IP addresses of two links that belong to the same link set must be the same.

Procedure

Step 1 (This step is not required if the command line interface is already in the Sigtran mode.) In globalconfig 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 linkinformation 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)#sigtranhuawei(config-sigtran)#iua-link add 0 0 1402 10.10.10.10 1404 10.10.10.20huawei(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 : - Bound MGC : - Priority : 0 ----------------------------------------------------------------------

7.3.3 Configuring the VoIP ISDN PRA UserThis topic describes how to configure the VoIP ISDN PRA user. After the MG interface isconfigured, you can add the VoIP ISDN PRA user on this interface to implement the VoIP ISDNPRA service.

1. 7.3.3.1 Configuring the Attributes of the E1 PortThis topic describes how to configure the attributes of the E1 port to ensure that the ISDNPRA port meets the actual application requirements.

2. 7.3.3.2 Configuring the ISDN PRA User DataThis topic describes how to configure the ISDN PRA user data on the H.248 interface (thedata must be the same as the corresponding data on the MGC) so that the ISDN PRA usercan access the network to use the ISDN PRA service.

3. 7.3.3.3 (Optional) Configuring the System Parameters


Configuration Guide


Issue 04 (2011-04-27)

This topic describes how to configure the system parameters including the overseas versionflag and message waiting indication (MWI) mode according to the local standards to ensurethat the response of the user terminal complies with the local standards.


7.3.3.1 Configuring the Attributes of the E1 PortThis topic describes how to configure the attributes of the E1 port to ensure that the ISDN PRAport meets the actual application requirements.

ContextYou can configure the impedance, line coding mode, and working mode of the E1 port.

Default ConfigurationTable 7-22 lists the default values of the E1 port. When configuring the attributes of the E1 port,you need to modify the values according to the service requirements.

Table 7-22 Default values of the E1 port


Port impedance E1 mode: 75 ohm

Line coding mode E1 mode: HDB3

Port mode Idle

Board working mode E1 mode

Procedure

Step 1 In global config mode, run the interface tdm command to enter the TDM mode.

Step 2 (Optional; perform this step when you need to modify the port impedance) Run theimpedance command to configure the impedance of the E1 port.

Step 3 (Optional; perform this step when you need to modify the line coding mode of the port) Run theline-code command to configure the line coding mode of the E1 port.

NOTE

In E1 mode, the system supports two line coding modes, namely, HDB3 and AMI.

Step 4 Run the port command to configure the working mode of the E1 port.

For detailed description and usage precaution of the port command, see the Usage Guidelinesof the command.

----End



7-83

ExampleAssume that all E1 ports on H831E81A work in SDT mode, the transmit clock of the port usesthe ACM mode of the recovery clock, the clock ID is 1, and the service is transmitted in commonchannel signaling mode. To configure such E1 ports, do as follows:

huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port all sdt acm 1 ccshuawei(config-if-tdm-0/1)#display port state all -------------------------------------------------------------------------- Port State Mode Code Looptype Clock CRC4 Signaling ESF Impedance -------------------------------------------------------------------------- 0 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 1 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 2 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 3 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 4 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 5 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 6 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 7 fault SDT HDB3 - acm1 disable CCS - 120 Ohm --------------------------------------------------------------------------

7.3.3.2 Configuring the ISDN PRA User DataThis topic describes how to configure the ISDN PRA user data on the H.248 interface (the datamust be the same as the corresponding data on the MGC) so that the ISDN PRA user can accessthe network to use the ISDN PRA service.

PrerequisiteThe H831E81A service board must be inserted into the planned slot correctly and the board mustbe in the normal state.

NOTEYou can run the display board command to query the board status.

l If the query result is Normal, it indicates that the board is in the normal state.

l If the query result is Auto_find, you need to run the board confirm command to confirm the board.

l If the query result is Failed, handle the fault according to Service Board Is in the Failed State describedin the Maintenance Guide.

The E1 port mode must be configured to SDT. If the E1 port mode is not configured, configurethe mode by referring to the port command.

ContextOne H831E81A board can be configured with a maximum of eight ISDN PRA users.

Default ConfigurationTable 7-23 lists the default settings of the attributes of the ISDN PRA user. When configuringthese attributes, you can modify the values according to the service requirements.

Table 7-23 Default settings of the attributes of the ISDN PRA user

Parameter Default Settings

Priority of the ISDN PRA user cat3: (common user)


Configuration Guide


Issue 04 (2011-04-27)


Flag of reporting the UNI fault of the ISDNPRA user

Disable

Sub-channel active mask of the ISDN PRAuser

255.255.255.255

Threshold for the number of auto recoveriesfrom 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 mgprauser add command to add an ISDN PRA.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 PRA user must be unique.l Each ISDN PRA user occupies 32 terminal IDs. You need to input only the first terminal ID

when adding an ISDN PRA user. If the MG interface does not support the terminal layeringfunction, plus (or minus) at least 32 to (or from) the terminal ID of the previous ISDN PRAuser when adding an ISDN PRA user, and use the result as the first terminal ID of the currentISDN PRA user.

l If the MG interface supports the terminal layering function, the terminal ID cannot beconfigured when an ISDN PRA user is added on the MG interface. The system automaticallyallocates a terminal ID for the user.

Step 3 Run the display mgprauser command to check whether the ISDN PSTN user data is the sameas the data plan.

Step 4 (Perform this step only when you need to modify the attributes of the ISDN PRA user.) Run themgprauser attribute set command to configure the attributes of the ISDN PRA user.

Step 5 (Perform this step only after you modify the attributes of the ISDN PRA user.) Run the displaymgprauser command to query whether the configured attributes of the ISDN PRA user are thesame as the data plan.

----End

ExampleAssume that the MG interface ID is 0, link set ID is 0, IUA port ID is 0 (iid-map is 1), terminalID is 223 (does not support the terminal layering function), user priority is cat2, UNI alarm reportflag is enable, sub-channel active mask is 255.255.255.255, and the threshold for the number ofauto recoveries from L1 is 30. To add such an ISDN PRA user connected to the 0/1/0 port, doas follows:

huawei(config)#esl-userhuawei(config-esl-user)#mgprauser add 0/1/0 0 0 interfaceid 0 terminalid 223huawei(config-esl-user)#display mgprauser 0/1 ------------------------------------------------------------- F /S /P /B MGID LinkSetNo InterfaceID TerminalID -------------------------------------------------------------



7-85

0 /1 /0 /0 0 0 0 A223 -------------------------------------------------------------

huawei(config-esl-user)#mgprauser attribute set 0/1/0 priority cat2 unireport enable activemask 255.255.255.255 auto-resume-limit 30huawei(config-esl-user)#display mgprauser attribute 0/1/0{ <cr>|endframeid/slotid/portid<S><Length 1-15> }: Command: display mgprauser attribute 0/1/0 ------------------------------------------------------------------------------ F /S /P : 0 /1 /0 UNIreport : enable Prior : Cat2 Mask of sub channel : 255.255.255.255 Auto reservice times/limit : 0/30 ------------------------------------------------------------------------------








0: Indicates China.









1: Send


Configuration Guide


Issue 04 (2011-04-27)

Procedure



----End

Example





Context

Table 7-25 lists the overseas parameters supported by the MA5612.










Line B offset

Procedure




7-87


----End

Example

To set the upper flash-hooking threshold (overseas parameter 0) to 800 ms (in compliance withthe Hong Kong standards) and the lower flash-hooking threshold (overseas parameter 1) to 100ms (in compliance with the Hong Kong standards), do as follows:


7.4 Configuring the VoIP ISDN PRA Service (Based on theSIP Protocol)

After configuring the SIP interface, you can add VoIP ISDN PRA users on this interface toimplement the VoIP ISDN PRA service.

Prerequisite

According to the actual network, a route from the MA5612 to the IMS must be configured toensure that the MA5612 communicates with the IMS normally.

Contextl The voice over IP (VoIP) service uses the IP packet switched network for transmission

after the traditional analog voice signals are compressed and packetized. This service lowersthe cost of the voice service. For the detailed description of the VoIP service, see VoiceFeature in the Feature Description.

l Defined by the International Telegraph and Telephone Consultative Committee (CCITT),the ISDN is a communication network evolved from the Integrated Digital Network (IDN).The ISDN service provides the E2E digital connection and supports multiple types of voiceand non-voice telecom services. On the ISDN network, users can access the networkthrough the following two interfaces: (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 twoB channels (for carrying services) and one D channel (for transmitting call controlsignaling and maintenance and management signaling). The rate of B channels is 64


Configuration Guide


Issue 04 (2011-04-27)

kbit/s and the rate of D channel is 16 kbit/s. The service carried on the ISDN BRI is theISDN basic rate access (BRA) service.

– ISDN primary rate interface (PRI), which supports a rate of 2.048 Mbit/s and provides30 B channels and one D channel. The rates of the B channel and D channel are both64 kbit/s. The service carried on the ISDN PRI is the ISDN primary rate access (PRA)service.

l The MA5612 supports only the VoIP ISDN PRA service.

l The MA5612 connects to the ISDN PRA users through the E1 port on the H831E81A board.For details of the H831E81A board, see E81A Board in the Product Description.

The MA5612 can also function as a voice over IP gateway (VGW) in the IMS architecture. Inthe downstream direction, it is connected to the ISDN PRA users; in the upstream direction, itis connected to the IMS system through the SIP interface, providing the VoIP ISDN PRA serviceby working with the IMS core.

The functions and applications of the SIP interface are the same as the functions and applicationsof the MG interface.

Data preparation

Table 7-26 provides the data plan for configuring the VoIP ISDN PRA service.

Table 7-26 Data plan for configuring the VoIP ISDN PRA service when the SIP protocol is used

Item Remarks

SIP interfacedata

Media andsignalingparameters


It is used for the upstream VLAN of theVoIP service to be configured.CAUTION

Note that the media and the signaling canuse the same VLAN or different VLANs,depending on the negotiation with theupstream device.

Signalingupstream port

Uplink port for configuring the SIPsignaling.

Media IP addressand signaling IPaddresses

These IP addresses must be selectedfrom the media and signaling IP addresspools. The media and signaling IPaddress pools consists of all the IPaddresses of the L3 interface of themedia and signaling upstream VLAN.


Next hop address from the MA5612 tothe IMS core network device.CAUTION

If the media IP address and the signaling IPaddress are different and the media and thesignaling are transmitted upstream throughdifferent gateways, ensure that theycorrespond to correct gateways. Otherwise,the call service may fail.



7-89

Item Remarks

Attributesof the SIPinterfaceNOTE

Parameters listedhere aremandatory, whichmeansthat theSIPinterfacecannot beenabled iftheseparameters are notconfigured.

SIP interface ID It is used for the VoIP service to beconfigured. The MA5612 supports onlyone VAG.

Signaling port IDof the SIPinterface

The value range is 5000-5999. Theprotocol defines the port ID as 5060.

IP address of theactive IMS corenetwork device towhich the SIPinterface belongs

When dual homing is not configured,parameters of only one IMS corenetwork device are required. When dualhoming is required, the IP address andthe port ID of the standby IMS corenetwork device must be configured.

Port ID of theactive IMS corenetwork device towhich the SIPinterface belongs

Transmissionmode of the SIPinterface

The transmission mode is selectedaccording to the requirements of theIMS core network device. Generally,UDP is used.

Home domain ofthe SIP interface

It corresponds to parameter home-domain in the MG interface attributes.

Index of theprofile used by theSIP interface

It corresponds to parameter Profile-index in the MG interface attributes.

IP addressobtaining mode ofthe proxy server

l In the IP mode, the IP address andthe port ID of the active proxy servermust be configured.

l In the DNS-A or DNS-SRV mode,the domain name of the active proxyserver must be configured.

Ringing mode of the SIPinterface

The ringing mode of the SIP interfaceis determined according to the servicerequirements.

ISDN PRA userdata(The dataconfigurationmust beconsistent withthe dataconfigurationon the IMS.)

Slot that houses the E1 serviceboard.

-

User data Phone number The phone number that the IMS corenetwork device allocates to the usermust be configured.


Configuration Guide


Issue 04 (2011-04-27)

Item Remarks

User priority According to the service requirements,user priorities must be specified,including:l cat1: government1 (category 1


government users)l cat3: common (default priority,

namely, common users)

Centrex The out-centrex prefix and out-centrexattributes of a centrex need to beconfigured according to localstandards.

System parameters The system parameters including theoversea version flag and messagewaiting indication (MWI) mode need tobe configured according to localstandards to ensure that the response ofthe user terminal meets local standards.

Overseas parameters The attributes such as the upper andlower thresholds of the flash-hookingduration need to be configuredaccording to local standards to ensurethat the response of the user terminalmeets local standards.

Port attributes Board access mode, port mode, linecoding mode, and port impedance needto be configured, and need not bemodified if there is no specialrequirement.

1. 7.4.1 Configuring the SIP InterfaceThis topic describes how to configure the SIP interface to implement the communicationbetween the MA5612 (SIP AG) and the IMS core network device.

2. 7.4.2 Configuring the VoIP ISDN PRA UserThis topic describes how to configure the VoIP ISDN PRA user. After the MG interface isconfigured, you can add the VoIP ISDN PRA user on this interface to implement the VoIPISDN PRA service.

7.4.1 Configuring the SIP InterfaceThis topic describes how to configure the SIP interface to implement the communication betweenthe MA5612 (SIP AG) and the IMS core network device.



7-91

Contextl The MA5612 can communicate with the IMS core network device through the SIP protocol.l One MA5612 supports only one SIP interface.

Procedure1. 7.4.1.1 Configuring the Upstream VLAN Interface



3. 7.4.1.3 Adding an SIP InterfaceThis topic describes how to add an SIP interface so that the MA5612 can communicatewith the IMS through the SIP interface.

4. 7.4.1.4 (Optional) Configuring the Ringing Mode of the SIP InterfaceThis topic describes how to configure the ringing mode of the SIP interface to support thebreak-make ratios of various new ringing modes and make the ringing mode meet the localstandards.



Procedure









----End


Configuration Guide


Issue 04 (2011-04-27)

Example

Assume that the media stream and signaling stream are transmitted upstream through upstreamport 0/0/1. To create media and signaling upstream VLAN 3 and configure IP addresses10.13.4.116/16 and 10.13.4.117/16 of the L3 interfaces for the media IP address pool and thesignaling IP address pool respectively, do as follows:




Prerequisite



selected from the IP address pools configured here.

l The signaling IP address pool is used to store the IP addresses of the MG or SIP interfaces,and the media IP address pool is used to store the IP addresses of the media streamscontrolled by the signaling.


Procedure



pool.





7-93

Step 3 Configure the signaling IP address pool.

1. Run the ip address signaling command to add the signaling IP address to the signaling IPaddress pool.



----End

Example



7.4.1.3 Adding an SIP Interface

This topic describes how to add an SIP interface so that the MA5612 can communicate with theIMS through the SIP interface.

Prerequisite

The to-be-configured media and signaling IP addresses of the SIP interface must be added tothe media and signaling IP address pools successfully.

Context

One MA5612 supports only one SIP interface.


Configuration Guide


Issue 04 (2011-04-27)

ProcedureStep 1 Run the display protocol support command to query the current system protocol.

l If the system protocol is SIP, go to Step 8.l If the system protocol is not SIP, go to Step 2.

Step 2 Run the display if-h248 all command to query whether an MG interface that supports the currentprotocol exists in the system.

Step 3 Run the display mgpstnuser command to check the user data, run the esl user command toenter ESL user mode, and then run the mgpstnuser batdel command to delete the voice serviceuser.

Step 4 Run the shutdown(h248) command to shut down the MG interface.

CAUTIONThis operation interrupts the ongoing services carried on the currently used MG interface. Hence,exercise caution when performing this operation. Before performing this operation, be sure tocheck whether the operation is allowed.

Step 5 Run the undo interface h248 command to delete the MG interface.

Step 6 Run the protocol support command to change the system protocol to SIP.

CAUTIONYou must delete the default and user-defined local digitmaps before switching the protocol.

Step 7 After saving the configuration data by running the save command, run the reboot systemcommand to reboot the system to make the new configuration take effect.

Step 8 Run the interface sip command to add an SIP interface.

Step 9 Run the if-sip attribute basic command to configure the basic attributes of the SIP interface.NOTE

l Between proxy IP and proxy domain, which are basic attributes, at least one attribute must beconfigured. If both attributes are configured, the system determines which attribute is used accordingto the configured address mode of the proxy server.

l The profile index must be configured.

Step 10 Run the if-sip attribute optional command to configure the optional attributes of the SIPinterface.

Step 11 Run the display if-sip attribute command to query the SIP interface attributes.

Step 12 After the configuration, you need to run the reset command to reset the SIP interface to makethe configuration take effect. Otherwise, the configuration is stored only in the database.

Step 13 After the configuration, run the display if-sip attribute running command to query the statusof the SIP interface.

----End



7-95

ExampleAssume 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 is10.13.4.118, port ID of the primary proxy server is 5060, domain name of the primary proxyserver is proxy.domain, IP address 1 of the secondary proxy server is 10.13.4.119, port ID ofthe secondary proxy server is 5060, home domain name is sip.huawei.com, and profile index is1. To configure such attributes of SIP interface 0, do as follows:

huawei(config)#interface sip 0huawei(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-proxy-port 5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.13.4.119secondary-proxy-port 5060 huawei(config-if-sip-0)#if-sip attribute basic home-domain sip.huawei.com sipprofile-index 1huawei(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 IP 2 - 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 - 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 ------------------------------------------------------------

7.4.1.4 (Optional) Configuring the Ringing Mode of the SIP InterfaceThis 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.

PrerequisiteThe SIP interface must be added successfully.

Contextl If the preset ringing modes of the system can meet the user requirements, you can select

the required ringing mode and configure the corresponding ringing mapping.


Configuration Guide


Issue 04 (2011-04-27)

l If the preset ringing modes cannot meet the user requirements, you can use the user-definedringing mode and configure the corresponding ringing mapping.

l You can configure the cadence duration for the user-defined ringing to form differentringing modes.

l The user-defined ringing modes are 0-15, which correspond to the cadence ringing modes128-143 and initial ringing modes 144-159 defined by the user. For example, if the user-defined cadence ringing mode is 128, user-defined ringing mode 0 is selected. If the user-defined 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.

Precautionl The ringing mapping name must be unique on the same SIP interface.l An index can be used for adding only one ringing mode on the same SIP interface.l The 16 user-defined ringing modes can be modified but cannot be added.

Procedure

Step 1 According to the Usage Guidelines of the ringmode add command, check whether the presetringing mode in the system meets the requirement.l If the requirement is met, go to Step 4.l If the requirement is not met, go to Step 2.

Step 2 In the global config mode, run the user defined-ring modify command to configure the user-defined ringing mode.

NOTE

l To use the user-defined ringing mode, perform this step and you can define the 0-15 ringing types.

l After configuring the user-defined ringing mode, you need to reset the corresponding service board tomake the configuration take effect, so that the user of the service board can use the new ringing mode.If the service board has been in service for a period, evaluate the impact on the online users beforeresetting the service board, and then determine whether to perform this operation.

Step 3 Run the display user defined-ring command to query the user-defined ringing.

Step 4 Run the interface sip command to enter the SIP mode.

Step 5 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. Thekey 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

corresponds to user-defined ringing modes 0-15.

Step 6 Run the display ringmode command to query ringing mapping records.

----End

ExampleAssume that:



7-97

l Index of the ringing mode mapping record: 1l Name of the ringing mode mapping record: alert-groupl Cadence ringing mode: 1l Initial ringing mode: 4To add such a ringing mode mapping record on SIP interface 0, do as follows:

huawei(config)#interface sip 0huawei(config-if-sip-0)#ringmode add 1 alter-group cadencering 1 initialring 4huawei(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 -----------------------------------------------------------------

7.4.2 Configuring the VoIP ISDN PRA UserThis topic describes how to configure the VoIP ISDN PRA user. After the MG interface isconfigured, you can add the VoIP ISDN PRA user on this interface to implement the VoIP ISDNPRA service.

1. 7.4.2.1 Configuring the Attributes of the E1 PortThis topic describes how to configure the attributes of the E1 port to ensure that the ISDNPRA port meets the actual application requirements.

2. 7.4.2.2 Configuring the ISDN PRA User DataThis topic describes how to configure the ISDN PRA user data on the SIP interface (thedata must be the same as the corresponding data on the IMS) so that the ISDN PRA usercan access the network to use the ISDN PRA service.



7.4.2.1 Configuring the Attributes of the E1 Port

This topic describes how to configure the attributes of the E1 port to ensure that the ISDN PRAport meets the actual application requirements.

Context

You can configure the impedance, line coding mode, and working mode of the E1 port.


Table 7-27 lists the default values of the E1 port. When configuring the attributes of the E1 port,you need to modify the values according to the service requirements.


Configuration Guide


Issue 04 (2011-04-27)

Table 7-27 Default values of the E1 port


Port impedance E1 mode: 75 ohm

Line coding mode E1 mode: HDB3

Port mode Idle

Board working mode E1 mode

Procedure

Step 1 In global config mode, run the interface tdm command to enter the TDM mode.

Step 2 (Optional; perform this step when you need to modify the port impedance) Run theimpedance command to configure the impedance of the E1 port.

Step 3 (Optional; perform this step when you need to modify the line coding mode of the port) Run theline-code command to configure the line coding mode of the E1 port.

NOTE

In E1 mode, the system supports two line coding modes, namely, HDB3 and AMI.

Step 4 Run the port command to configure the working mode of the E1 port.

For detailed description and usage precaution of the port command, see the Usage Guidelinesof the command.

----End

ExampleAssume that all E1 ports on H831E81A work in SDT mode, the transmit clock of the port usesthe ACM mode of the recovery clock, the clock ID is 1, and the service is transmitted in commonchannel signaling mode. To configure such E1 ports, do as follows:

huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port all sdt acm 1 ccshuawei(config-if-tdm-0/1)#display port state all -------------------------------------------------------------------------- Port State Mode Code Looptype Clock CRC4 Signaling ESF Impedance -------------------------------------------------------------------------- 0 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 1 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 2 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 3 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 4 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 5 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 6 fault SDT HDB3 - acm1 disable CCS - 120 Ohm 7 fault SDT HDB3 - acm1 disable CCS - 120 Ohm --------------------------------------------------------------------------

7.4.2.2 Configuring the ISDN PRA User DataThis topic describes how to configure the ISDN PRA user data on the SIP interface (the datamust be the same as the corresponding data on the IMS) so that the ISDN PRA user can accessthe network to use the ISDN PRA service.



7-99

PrerequisiteThe H831E81A service board must be inserted into the planned slot correctly and the board mustbe in the normal state.

NOTEYou can run the display board command to query the board status.

l If the query result is Normal, it indicates that the board is in the normal state.

l If the query result is Auto_find, you need to run the board confirm command to confirm the board.

l If the query result is Failed, handle the fault according to Service Board Is in the Failed State describedin the Maintenance Guide.

The E1 port mode must be configured to SDT. If the E1 port mode is not configured, configurethe mode by referring to the port command.

ContextOne H831E81A board can be configured with a maximum of eight ISDN PRA users.

Default ConfigurationTable 7-28 lists the default settings of the attributes of the ISDN PRA user. When configuringthe attributes of these attributes, you can modify the values according to the service requirements.

Table 7-28 Default settings of the attributes of the ISDN PRA user


Priority of the ISDN PRA user cat3 (common users)

Flag of reporting the UNI fault of the ISDNPRA user

disable

Sub-channel active mask of the ISDN PRAuser

255.255.255.255

Threshold for the number of auto recoveriesfrom 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 sipprauser add command to add an ISDN PRA user.

Step 3 Run the display sipprauser command to check whether the ISDN PRA user data is the sameas the data plan.

Step 4 (Perform this step when you need to modify the attributes of an ISDN PRA user.) Run thesipprauser attribute set command to configure the attributes of the ISDN PRA user.

Step 5 (Perform this step only after you modify the attributes of the ISDN PRA user.) Run the displaysipprauser attribute command to query whether the configured attributes of the ISDN PRAuser are the same as the data plan.


Configuration Guide


Issue 04 (2011-04-27)

Step 6 (Perform this step only when you need to configure an extended phone number for the ISDNPRA user.) Run the sipprauser extend-telno add command to add multiple phone numbers ora phone number containing non-digit characters for the ISDN PRA user.

Step 7 (Perform this step only after you configure the extended phone number for an ISDN PRA user.)Run the display sipprauser extend-telno command to query whether the configured extendedphone number of the ISDN PRA user is the same as the data plan.

----End

ExampleAssume that the SIP interface ID is 0, phone number is 28780000, call priority is cat3, UNI faultreport flag is disable, number of auto recoveries from deterioration faults is 10, sub-channelactive mask is 255.255.1.3, and extended phone number is +86-755-28780000. To add such anISDN PRA user connected to the 0/1/0 port, do as follows:

huawei(config)#esl-userhuawei(config-esl-user)#sipprauser add 0/1/0 0 telno 28780000huawei(config-esl-user)#display sipprauser 0/1/0{ <cr>|endframeid/slotid/portid<S><Length 1-15> }: Command: display sipprauser 0/1/0 --------------------------------------- F /S /P MGID TelNo --------------------------------------- 0 /1 /0 0 28780000 --------------------------------------- huawei(config-esl-user)#sipprauser attribute set 0/1/0 priority cat3 unireport disable auto-resume-limit 10 activemask 255.255.1.3huawei(config-esl-user)#display sipprauser attribute 0/1/0{ <cr>|endframeid/slotid/portid<S><Length 1-15> }: Command: display sipprauser attribute 0/1/0 ------------------------------------------------------------------------ F /S /P : 0 /1 /0 UNIreport : disable Prior : cat3 Mask of sub channel : 255.255.1.3 Auto reservice times/limit : 0/10 ------------------------------------------------------------------------ huawei(config-esl-user)#sipprauser extend-telno add 0/1/0 +86-755-28780000huawei(config-esl-user)#display sipprauser extend-telno





7-101






0: Indicates China.









1: Send

Procedure



----End

Example






Configuration Guide


Issue 04 (2011-04-27)

ContextTable 7-30 lists the overseas parameters supported by the MA5612.










Line B offset

Procedure



----End





7-103

7.5 Configuring the FoIP Service (Based on the H.248Protocol)

This topic describes how to configure the FoIP service when the H.248 protocol is used totransmit the fax data service over the IP network.

Prerequisitel 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.l The voice service port used by the FoIP service and the voice service on that port must be

in the normal state.

ContextThe 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 intotransparent transmission fax (using the G.711 coding) and T.38 fax (using the T.38 coding).

l According to the role of the MGC: In this mode, the FoIP service is classified into theSoftSwitch-controlled fax and the self-switch fax (the fax flow is controlled by the MGCitself).

The MA5612 supports the self-switch mode and the auto-negotiation mode:

l Self-switch: If the self-switch mode is configured, the fax working mode of the MA5612is not controlled by the MGC. Therefore, manual configuration is required.

l Auto-negotiation: If the auto-negotiation mode is configured, the fax working mode of theMA5612 is automatically configured during the negotiation with the MGC. Therefore,manual configuration is not required.

The MA5612 supports the transparent transmission fax and the T.38 fax:

l Transparent transmission fax: The voice encoding (G.7xx encoding) is adopted.l T.38 fax: The T.38 encoding is adopted.

The MA5612 supports the V2, V3, and V5 fax flows.

The MA5612 supports the 10 ms packing function and the RFC 2198 function.

l 10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the faxtransparent transmission function is added with the 10 ms G.711 transparent transmission.This reduces delay, improves the performance of transparent transmission, and decreasesthe impact of packet loss on the transmission of the fax service data.

l RFC 2198 function: Through the redundant transmission, the RFC 2198 function improvesthe reliability of data transmission. When the network packet loss occurs, the RFC 2198can ensure the service quality.

Default ConfigurationTable 7-31 lists the default configuration of the flows of the FoIP service:


Configuration Guide


Issue 04 (2011-04-27)

Table 7-31 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

ProcedureStep 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.

Step 2 Configure the fax working mode.l If the auto-negotiation mode is configured in Step 1.1, go to Step 2.1.l 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 theT.38 fax port ID is added by 2 for the two sides must be consistent. That is, the T.38 fax port ID ofthe 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 thefax transmission parameters.

----End

ExampleAssume that:



7-105

l The negotiation mode of the MA5612 is self-switch.l The 10 ms packing function and the RFC2198 intelligent startup function are enabled.l The transmission mode of the modem event is ControlledByMGC (default).l The codec mode of the VBD is G.711A (default).l The payload type of the VBD is static payload (default).l The working mode of the fax is transparent transmission (thoroughly).l The fax working flow is V3 flow.To configure the MA5612, do as follows:huawei(config)#fax-modem parameters negomode selfswitch packet-interval-10ms enablerfc2198-start-mode enableRfc2198SmartStartup transevent controlledByMGCvbd-codec G.711A vbd-pt-type statichuawei(config)#fax parameters workmode thoroughly flow v3huawei(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 payload -----------------------------------------------------------------------------huawei(config)#display fax parameters ----------------------------------------------------------------------------- FAX transfers mode :Thoroughly T38 Fax Port :RTP port FAX flow :V3 Flow -----------------------------------------------------------------------------

7.6 Configuring the FoIP Service (Based on the SIP Protocol)This topic describes how to configure the FoIP service based on the SIP protocol to transmit thefax data service over the IP network.

Prerequisitel The communication between the MA5612 and the IMS must be in the normal state.l The voice service port used by the FoIP service and the voice service on that port must be


ContextDuring the application of the fax service, the FoIP service can be classified into two modesaccording 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 MA5612needs to be configured manually.

l Auto-negotiation: If the auto-negotiation mode is configured, the fax working mode of theMA5612 needs to be configured manually.

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.l T.38 fax: The T.38 encoding is adopted.



Configuration Guide


Issue 04 (2011-04-27)

l 10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the faxtransparent transmission function is added with the 10 ms G.711 transparent transmission.This reduces delay, improves the performance of transparent transmission, and decreasesthe impact of packet loss on the transmission of the modem service data.

l RFC 2198 function: Through the redundant transmission, the RFC 2198 improves thereliability of data transmission. When the network packet loss occurs, the RFC 2198 canensure the service quality.

Data preparationIt is recommended that you plan the working mode of the fax on the entire IP multimediasubsystem (IMS) before configuring the data so that the working mode on the entire network isconsistent.

Table 7-32 Items involved in the FoIP service

Item Option Remarks

Codecnegotiationmode

Negotiation The codec mode needs to be negotiated through the SIPsignaling.

Self-switch The MG determines what codec mode is used.

Codec mode Transparenttransmission fax

The G.711 encoding is adopted.

T.38 flow The T.38 encoding is adopted.

Default ConfigurationTable 7-33 lists the default configuration of the flows of the FoIP service.

Table 7-33 Default configuration of the flows of the FoIP service

Item Default

Codec negotiation mode Negotiation

Codec mode Transparent transmission fax

Procedure

Step 1 Configure public fax and modem parameters.1. Run the interface sip command to enter the SIP mode.2. Run the fax-modem parameters negomode command to configure the negotiation mode.3. (Optional) Run the fax-modem parameters packet-interval-10 command to enable or

disable the 10 ms packing function.4. (Optional) Run the fax-modem parameters rfc2198-negomode command to configure

the RFC2198 function.



7-107

5. (Optional) Run the fax-modem parameters transevent command to configure the reportmode of the Fax/Modem events.

6. (Optional) Run the fax-modem parameters vbd-codec command to configure the codecmode of the voice-band data (VBD).

7. (Optional) Run the fax-modem parameters vbd-pt-type command to configure thepayload type of the VBD.

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 thefax transmission parameters.

----End

ExampleAssume that:

l The negotiation mode of the MA5612 is self-switch.l The 10 ms packing function and the RFC2198 intelligent startup function are enabled.l The RFC2198 negotiation mode is fixedstart.l The transmission mode of the fax or modem event is fixedstart.l The codec mode of the VBD is G.711A.l The payload type of the VBD is static payload.l The transmission mode of the fax is transparent transmission (thoroughly).To configure the MA5612, do as follows:huawei(config)#interface sip 0huawei(config-if-sip-0)#fax-modem parameters negomode self-switch packet-interval-10ms enablerfc2198-negomode fixedstart rfc2198-startmode smart2198 transevent fixedstartvbd-codec g.711a vbd-pt-type statichuawei(config-if-sip-0)#display fax-modem parameters ------------------------------------------------------------------------------- MGID :0 Nego-mode :self-switch Packet-interval-10ms :enable Rfc2198-nego-mode :fixedstart Rfc2198-start-mode :smart2198 Vbd-codec :G.711A Vbd-pt-type :static Transfer-event :fixedstart -------------------------------------------------------------------------------huawei(config-if-sip-0)#fax parameters transmode 0huawei(config-if-sip-0)#quithuawei(config)#display fax parameters --------------------------------------- MGID Transmode --------------------------------------- 0 Thoroughly ---------------------------------------


Configuration Guide


Issue 04 (2011-04-27)

7.7 Configuring the MoIP Service (Based on the H.248Protocol)

This topic describes how to configure the MoIP service when the H.248 protocol is used totransmit the modem data service over the IP network.

Prerequisitel The communication between the MG and the MGC must be in the normal state.

l The voice service port used by the MoIP service and the voice service on that port must bein the normal state.

Context

The MA5612 supports the self-switch mode and the auto-negotiation mode:

l Self-switch: If the self-switch mode is configured, the modem working mode of theMA5612 is not controlled by the MGC. Therefore, manual configuration is required.

l Auto-negotiation: If the auto-negotiation mode is configured, the modem working modeof the MA5612 is automatically configured during the negotiation with the MGC.Therefore, manual configuration is not required.


l 10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the modemtransparent transmission function is added with the 10 ms G.711 transparent transmission.This reduces delay, improves the performance of transparent transmission, and decreasesthe impact of packet loss on the transmission of the modem service data.


The MoIP service supports two transmission modes: the transparent transmission mode and therelay (redundancy) mode. The MA5612 supports only the modem service in the transparenttransmission mode. In the transparent transmission mode, the MG uses the G.711 mode to encodeand 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 whenthe host receives a modem event.

l Delay: In delay mode, the host does not report the modem event immediately after an eventis received, but waits for a period of time until the event times out and the fax signal isdetected. In this way, when the high-speed modem machine fails in the high-speedtransmission negotiation, it can transmit data in low-speed transmission mode.

l Direct for high-speed signals: In the mode of the direct for high-speed signals, the hostreports the modem event with low speed signals to the MGC 5.5s after the host receives amodem event; the host reports the modem event with high speed signals to the MGCimmediately when the host receives a modem event.



7-109

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-10 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.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



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.

NOTE

l To enable the MGC to quickly respond to a modem event, you need to configure the report modeof the modem event as the direct report mode.

l By default, the transmission mode of the modem is the transparent transmission mode, and themodem event is reported in the direct mode.

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 querymodem parameters.

----End

ExampleAssume that:

l The negotiation mode of the MA5612 is self-switch.l The 10 ms packing function and the RFC2198 intelligent startup function are enabled.l The transmission mode of the modem event is ControlledByMGC (default).l The codec mode of the VBD is G.711A (default).l The payload type of the VBD is static payload (default).l The working mode of modem is transparent transmission (thoroughly).l The report mode of the modem event is direct.To configure the MA5612, do as follows:huawei(config)#fax-modem parameters negomode selfswitch packet-interval-10ms enablerfc2198-start-mode enableRfc2198SmartStartup transevent controlledByMGCvbd-codec G.711A vbd-pt-type statichuawei(config)#modem parameters tranmode 0 eventmode 1huawei(config)#display fax-modem parameters


Configuration Guide


Issue 04 (2011-04-27)

----------------------------------------------------------------------------- Negomode : Self switch Packet-interval-10ms : Enable Rfc2198-start-mode : Enable Rfc2198SmartStartup TransEvent : ControlledByMGC Vbd-codec : G.711A Vbd-payload-type : Static payload -----------------------------------------------------------------------------huawei(config)#display modem parameters ----------------------------------------------------------------------------- MODEM transfers mode :Thoroughly MODEM event mode :Direct -----------------------------------------------------------------------------

7.8 Configuring the MoIP Service (Based on the SIPProtocol)

This topic describes how to configure the MoIP service when the SIP protocol is used to transmitthe modem data service over the IP network.

Prerequisitel The communication between the MA5612 and the IMS must be in the normal state.l The VoIP service must be configured, see 7.2.2 Configuring the VoIP PSTN User.l The voice service port used by the MoIP service and the voice service on that port must be


ContextThe MA5612 supports the self-switch mode and the auto-negotiation mode:

l Self-switch: If the self-switch mode is configured, you need to configure the fax workingmode of the MA5612 manually.

l Auto-negotiation: If the auto-negotiation mode is configured, you need to configure the faxworking mode of the MA5612 manually.


l 10 ms packing function: In addition to the 20 ms G.711 transparent transmission, the modemtransparent transmission function is added with the 10 ms G.711 transparent transmission.This reduces delay, improves the performance of transparent transmission, and decreasesthe impact of packet loss on the transmission of the modem service data.


The MoIP service supports two transmission modes: the transparent transmission mode and therelay (redundancy) mode. The MA5612 supports only the modem service in the transparenttransmission mode. In the transparent transmission mode, the MG uses the G.711 mode to encodeand 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.



7-111

Procedure

Step 1 Configure public fax and modem parameters.1. Run the interface sip command to enter the SIP interface mode.2. Run the fax-modem parameters negomode command to configure the negotiation mode.3. (Optional) Run the fax-modem parameters packet-interval-10ms to enable or disable

the 10 ms packing function.4. (Optional) Run the fax-modem parameters rfc2198-negomode command to configure

the RFC 2198 function.5. (Optional) Run the fax-modem parameters rfc2198-start-mode command to configure

the startup mode of the RFC 2198 function.6. (Optional) Run the fax-modem parameters transevent command to configure the mode

for reporting fax or modem events.7. (Optional) Run the fax-modem parameters vbd-codec command to configure the codec



Step 2 Configure the transmission mode of the modem.

Run the modem parameters tranmode command to configure the transmission mode of themodem. Currently, only the modem service in the transparent transmission mode is supported.

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 querymodem parameters.

----End

ExampleAssume that:

l The negotiation mode of the MA5612 is self-switch.l The 10 ms packing function and the RFC2198 intelligent startup function are enabled.l The RFC2198 negotiation mode is fixedstart.l The mode for reporting fax or modem events is fixedstart.l The codec mode of the VBD is G.711A.l The payload type of the VBD is static payload.l The transmission mode of the modem is transparent transmission (thoroughly).To configure the MA5612, do as follows:huawei(config)#interface sip 0huawei(config-if-sip-0)#fax-modem parameters negomode self-switch packet-interval-10ms enablerfc2198-negomode fixedstart rfc2198-startmode smart2198 transevent fixedstartvbd-codec g.711a vbd-pt-type statichuawei(config-if-sip-0)#modem parameters transmode 0huawei(config-if-sip-0)#display fax-modem parameters ------------------------------------------------------------------------------- MGID :0 Nego-mode :self-switch Packet-interval-10ms :enable


Configuration Guide


Issue 04 (2011-04-27)

Rfc2198-nego-mode :fixedstart Rfc2198-start-mode :smart2198 Vbd-codec :G.711A Vbd-pt-type :static Transfer-event :fixedstart -------------------------------------------------------------------------------huawei(config-if-sip-0)#display modem parameters --------------------------------------- MGID Transmode --------------------------------------- 0 Thoroughly ---------------------------------------

7.9 Configuring the Security and Reliability of the VoiceService

For the MA5612, the security configuration of the voice service includes the H.248-based, orSIP-based device authentication configuration. The reliability configuration of the voice serviceincludes the dual-homing configuration and the emergency standalone configuration.

7.9.1 Configuring the Device AuthenticationThe purpose of authentication is to verify the validity of users and networks. The sameauthentication algorithm is used on the MG and the MGC separately. Then, the calculation resultson the MG and the MGC are compared on either side. If the calculation results are the same, itindicates that the authentication is successful. If the calculation results are different, it indicatesthat the authentication fails.

7.9.2 Configuring the Dual HomingDual-homing is a disaster recovery mechanism of emergency communication against softswitchfailure or unexpected disaster (such as fire in the equipment room, disconnection of the cableconnected to the equipment room, and abnormal power supply).

7.9.3 Configuring the Emergency StandaloneThis topic describes how to configure the emergency standalone function on the MA5612. Whenthe MA5612 and the MGC device fail to communicate with each other, the MA5612independently processes the internal users connecting to the same MG interface; therefore, theinternal users can make calls normally without the control of MGC.

7.9.1 Configuring the Device AuthenticationThe purpose of authentication is to verify the validity of users and networks. The sameauthentication algorithm is used on the MG and the MGC separately. Then, the calculation resultson the MG and the MGC are compared on either side. If the calculation results are the same, itindicates that the authentication is successful. If the calculation results are different, it indicatesthat the authentication fails.

7.9.1.1 Configuring the Device Authentication (Based on the H.248 Protocol)This topic describes how to configure the device authentication parameters of the MA5612 toprevent illegal devices from registering with the MGC when the H.248 protocol is used.

7.9.1.2 Configuring the Device Authentication (Based on the SIP Protocol)This topic describes how to configure the authentication information for the SIP interface or asingle user of the MA5612 when the SIP protocol is used.



7-113

7.9.1.1 Configuring the Device Authentication (Based on the H.248 Protocol)

This topic describes how to configure the device authentication parameters of the MA5612 toprevent illegal devices from registering with the MGC when the H.248 protocol is used.

Prerequisitel The MG interface must be added successfully on the MA5612.

l The parameters, including the encryption type, the initial key, and the DH authenticationMG ID, must be configured on the MGC. These parameters must be the same as theparameters configured on the MA5612.

Precautions

When the MGC is Huawei SoftX3000, the authentication MG ID must be a string of more thaneight characters.

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 thedevice 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 7-34 for the MA5612,do as follows:

Table 7-34 Data plan for configuring the authentication parameters (H.248)

Configuration Item Value

MGID 0

Whether to use the wildcard in registration Yes

Whether to support the deviceauthentication.

Yes

Authentication MG ID MA5612It must be the same as the configuration on theMGC. Otherwise, the MG cannot register withthe MGC.


Configuration Guide


Issue 04 (2011-04-27)

Configuration Item Value

Initial key Default: 0123456789ABCDEF.It must be the same as the initial key configuredon the MGC.

huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-software parameter 4 0huawei(config-if-h248-0)#display mg-software parameter 4 ------------------------------------------------- Interface Id:0 para index:4 value:0 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 4: Whether MG uses wildcard in registration 0: Yes 1: No huawei(config-if-h248-0)#mg-software parameter 6 0huawei(config-if-h248-0)#display mg-software parameter 6 ------------------------------------------------- Interface Id:0 para index:6 value:0 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 6: Whether MG supports authentication 0: Yes 1: No huawei(config-if-h248-0)#auth auth_mgid MA5612 initial_key 0123456789ABCDEFhuawei(config-if-h248-0)#display auth [AUTH_PARA config] Initial Key : 0123456789ABCDEF Auth MGid : MA5612 Algorithm : MD5 huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:y

7.9.1.2 Configuring the Device Authentication (Based on the SIP Protocol)

This topic describes how to configure the authentication information for the SIP interface or asingle user of the MA5612 when the SIP protocol is used.

Prerequisitel The SIP interface must be added successfully on the MA5612.

l The authentication user name and password must be configured on the IMS. Suchparameters must be the same as the authentication user name and password configured onthe MA5612.

Contextl 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.

l The authentication information can be configured for a single user. The configuration takeseffect immediately after the configuration is complete.



7-115

l In the actual application, whether the user uses the authentication information configuredfor the SIP interface or a single user can be controlled through system parameter 81 in thesipprofile modify command.

Procedurel Configure the authentication information for the SIP interface.

1. In the global config mode, run the interface sip command to enter the SIP interfacemode.

2. Run the sip-auth-parameter command to configure the authentication user name andpassword for an SIP interface.

3. Run the display sip-auth command to query the authentication information of an SIPinterface.

4. Run the reset command to reset the SIP interface.l Configure the authentication information for a single user.

1. Run the esl user command to enter the ESL user mode.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

Examplel 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>|password-mode<K> }:password-mode{ password-mode-value<E><password,ha1> }:password

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 interfacehuawei(config-if-sip-0)#reset Are you sure to reset the SIP interface?(y/n)[n]:y The configuration will take effect after resetting the interface

l To configure the authentication information for a single user on port0/3/0 with the username of user1.com and the password of 987654321, do as follows:huawi(config)#esl userhuawei(config-esl-user)#sippstnuser auth set 0/3/0 telno 88442200 password-modepassword Command: sippstnuser auth set 0/3/0 telno 88442200 password-mode password User Name(<=64 chars, "-" indicates deletion):user1.com User Password(<=64 chars, "-" indicates deletion):

7.9.2 Configuring the Dual HomingDual-homing is a disaster recovery mechanism of emergency communication against softswitchfailure or unexpected disaster (such as fire in the equipment room, disconnection of the cableconnected to the equipment room, and abnormal power supply).


Configuration Guide


Issue 04 (2011-04-27)

7.9.2.1 Configuring the Dual Homing (Based on the H.248 Protocol)Based on the H.248 protocol, configuring the dual homing means registering one MA5612 withtwo MGCs. When one MGC is faulty and cannot support the communication, the MA5612automatically switches to the other MGC.

7.9.2.2 Configuring the Dual Homing (Based on the SIP Protocol)The SIP dual-homing means that the MA5612 supports the 1+1 mutual assistance mode of theupstream P-CSCF/PROXY, namely, the deployment in the active/standby mode. When one ofthe upstream active/standby devices is faulty, the MA5612 service automatically switches toanother device, thus implementing the disaster recovery for the access reliability of the devicewhen the SIP protocol is used.

7.9.2.1 Configuring the Dual Homing (Based on the H.248 Protocol)

Based on the H.248 protocol, configuring the dual homing means registering one MA5612 withtwo MGCs. When one MGC is faulty and cannot support the communication, the MA5612automatically switches to the other MGC.

Prerequisitel The MGC1 and MGC2 must be configured on the attributes of the MG interface.l On the MGCs, the data for interconnecting with the MG interface must be configured.

Context

The MA5612 supports registering the MG interface with two MGCs (MGC1 and MGC2). MGC1functions 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.

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 dualhoming.

----End

Example

To configure MG interface 0 to support the dual homing, and not to automatically switch overto the active MGC when the active MGC recovers, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-software parameter 2 1huawei(config-if-h248-0)#display mg-software parameter 2 ------------------------------------------------- Interface Id:0 para index:2 value:1 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 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



7-117

Related OperationTable 7-35 lists the related operation for configuring the dual homing when the H.248 protocolis used.

Table 7-35 Related operation for configuring the dual homing (H.248)

To... Run the Command...

Forcibly switch the MG to register with theother MGC

mgc switch

7.9.2.2 Configuring the Dual Homing (Based on the SIP Protocol)The SIP dual-homing means that the MA5612 supports the 1+1 mutual assistance mode of theupstream P-CSCF/PROXY, namely, the deployment in the active/standby mode. When one ofthe upstream active/standby devices is faulty, the MA5612 service automatically switches toanother device, thus implementing the disaster recovery for the access reliability of the devicewhen the SIP protocol is used.

PrerequisiteOn the IMS, the data for interconnecting with the SIP interface must be configured.

ContextThe MA5612 supports configuring the SIP interface on two proxy servers ((Proxy 1 and Proxy2), where, Proxy 1 functions as the active proxy server. After Proxy 1 fails, the MG can switchto 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 Run the if-sip attribute basic command to configure the IP address of the active/standby proxyserver 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 theconfiguration of the active/standby proxy server.

Step 3 Run the reset command to reset the SIP interface to validate the configuration data.

----End

ExampleAssume that:

l The media IP address is 10.10.10.13, signaling IP address is 10.10.10.13, transfer protocolis UDP, and port ID is 5000.

l The obtaining mode of the IP address of the proxy server is the IP mode, IP address 1 ofthe active proxy server is 10.10.10.14, port ID of the active proxy server is 5060, IP address


Configuration Guide


Issue 04 (2011-04-27)

1 of the standby proxy server is, 10.10.10.15, and the port ID of the standby proxy serveris 5060.

l 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-domain<K>|secondary-proxy-ip2<K>|server-dhcp-option<K>|sipprofile-index<K>|srvlogic-index<K> }:

Command: if-sip attribute basic media-ip 10.10.10.13 signal-ip 10.10.10.13signal-port 5000 transfer udp primary-proxy-ip1 10.10.10.14 primary-proxy-port5060 primary-proxy-domain proxy.domain secondary-proxy-ip1 10.10.10.15secondary-proxy-port 5060

huawei(config-if-sip-0)#if-sip attribute basic home-domain huawei.com sipprofile-index 1{ <cr>|media-ip<K>|primary-proxy-domain<K>|primary-proxy-ip1<K>|primary-proxy-ip2<K>|primary-proxy-port<K>|proxy-addr-mode<K>|secondary-proxy-domain<K>|secondary-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

huawei(config-if-sip-0)#reset

Related Operation

Table 7-36 lists the related operation for configuring the dual homing.

Table 7-36 Related operation for configuring the dual homing

To... Run the Command...

Query the configuration of the SIPinterface

display if-sip attribute

7.9.3 Configuring the Emergency StandaloneThis topic describes how to configure the emergency standalone function on the MA5612. Whenthe MA5612 and the MGC device fail to communicate with each other, the MA5612independently processes the internal users connecting to the same MG interface; therefore, theinternal users can make calls normally without the control of MGC.

Prerequisitel The H.248 protocol must be used in the system.l The media IP address must exist in the IP address pool.l The voice users must be configured on the MG interface and the users can call each other

successfully.



7-119

l If the device cannot communicate with the MG, run the system parametres 5 commandto configure the media stream forwarding mode as the mode in which the media stream isforwarded within the device.

l The phone number of the MG user is configured to be the same as the phone number onthe MGC.

Contextl When the MG interface works in the emergency standalone state, only the internal users

on the MG interface can communicate with each other properly.l 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 asthe phone number on the MGC.

Procedure

Step 1 Run the mg-software parameter 11 1 command to configure the MG interface to support theemergency 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 theemergency standalone timers.

NOTE

In general, the default parameters of the emergency standalone timers are used, and you need not configurethem.

----End

Example

To configure MG0 to support the emergency standalone function and configure the digitmapfor internal calls as 8764XXXX, do as follows:

huawei(config)#interface h248 0huawei(config-if-h248-0)#mg-software parameter 11 1huawei(config-if-h248-0)#display mg-software parameter 11 ------------------------------------------------- Interface Id:0 para index:11 value:1 ------------------------------------------------- APPENDIX: ------------------------------------------------- Interface software parameter name: 11: Stand alone flag 0: None 1: Inner 2: Emergency 3: Both huawei(config-if-h248-0)#digitmap set inner 8764XXXX huawei(config-if-h248-0)#display digitmap ----------------------------------------------------------------------------- Inner digitmap : 8764XXXX Urgent digitmap (for overload or bandwidth restrict) : - Dualdial digitmap for card service : - -----------------------------------------------------------------------------

NOTE

The configured digitmap corresponds to the user phone number.


Configuration Guide


Issue 04 (2011-04-27)

8 Configuration Examples of the MA5612

About This Chapter

This topic describes how to configure Internet access service, multicast service, voice service,and triple play service on the MA5612 in different networkings.

8.1 Configuration Example of the Ethernet Access Service in the Single-Port for Multi-ServiceModeThe MA5612 supports the access of one or multiple services among video, voice, and dataservices through a single Ethernet port in multi-service mode. This topic describes how toconfigure the MA5612 to implement the Ethernet access service through GPON or GE port forupstream transmission.

8.2 Configuration Example of the Multicast Service (Multicast VLAN Mode)This topic describes how to configure the multicast service on the MA5612 in multicast VLANmode.

8.3 Configuration Example of the VoIP ServiceThis topic describes how to configure the VoIP service based on the H.248 or SIP protocol.

8.4 Configuration Example of the VLAN Stacking Wholesale ServiceThis topic describes the VLAN stacking wholesale service and how to configure the VLANstacking wholesale service on the MA5612.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 8 Configuration Examples of the MA5612


8-1

8.1 Configuration Example of the Ethernet Access Service inthe Single-Port for Multi-Service Mode

The MA5612 supports the access of one or multiple services among video, voice, and dataservices through a single Ethernet port in multi-service mode. This topic describes how toconfigure the MA5612 to implement the Ethernet access service through GPON or GE port forupstream transmission.

Prerequisitel The network device and the line must be normal.l The multicast source must exist in the network and the IP address must be known.

Service Requirementsl PON upstream mode

– The PC, Ephone, and STB are connected to the Ethernet port on the MA5612 throughthe LAN switch, implementing the Ethernet access in the single-port for multi-servicemode, and transmitting the data upstream to the OLT through GPON upstream port0/0/0.

– The OLT receives the traffic stream from the MA5612 through ports on the PON serviceboard. Then, the data is converged and transmitted upstream to the switch and thentransmitted to the Internet through the switch.

l GE upstream modeThe PC, Ephone, and STB are connected to the Ethernet port on the MA5612 through theLAN switch, implementing the Ethernet access in the single-port for multi-service mode,and transmitting the data upstream to the router through GE upstream port 0/0/0. Then, thedata is transmitted to the Internet.

NetworkingFigure 8-1 provides an example network of the Ethernet access service (PON upstream).

8 Configuration Examples of the MA5612SmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

Figure 8-1 Example network of the Ethernet access service (PON upstream)

Router

OLT

MA5612

PC

LAN Switch

TVEphone

LAN Switch

BRAS

GW

Multicast sourse

IPTV DHCP Server

VoIP DHCP Server

NMS

OSS & RADIUS Server/RADIUS Proxy

Figure 8-2 provides an example network of the Ethernet access service (GE upstream).



8-3

Figure 8-2 Example network of the Ethernet access service (GE upstream)

Data PlanTable 8-1 provides the data plan for configuring the Ethernet access service.

Table 8-1 Data plan for configuring the Ethernet access service

Item Data Remarks

Traffic profile l Internet service: index 7 (user defined)l IPTV service: index 8 (user defined)l VoIP service: index 9 (user defined)

-

Service port 0/4/1 -

Upstream port 0/0/0 -

Upstream VLAN l Internet service: VLAN 100l IPTV service: VLAN 101l VoIP service: VLAN 102

The upstream VLANmust be the same as theuser-side VLAN onthe OLT.


Configuration Guide


Issue 04 (2011-04-27)

Item Data Remarks

User-side VLAN l Internet service: VLAN 2l IPTV service: VLAN 3l VoIP service: VLAN 4

-

Internet mode PPPoE -

Program library Program 1, multicast IP address 224.1.1.1,program source IP address 10.10.10.10

-

Multicast user Port: 0/4/1Multicast VLAN ID: 101

-

Priority The 802.1p priority is used. The priority of theVoIP service is 6, the priority of the IPTVservice is 4, and the priority of the Internetservice is 0.

-

Requirements onthe LAN switchof the upper-layer device

l The LAN switch transparently transmits theservice packets of the MA5612.

l A VLAN must be configured for the serviceaccess of the MA5612. The VLAN ID mustbe the same as the VLAN ID of the upstreamVLAN of the MA5612.

For detailedconfiguration of theLAN switch, see theassociatedconfiguration manual.

Configuration FlowchartFigure 8-3 provides the flowchart for configuring the Ethernet access service on the MA5612.

Figure 8-3 Flowchart for configuring the Ethernet access service on the MA5612

Start

Add the service port to the VLAN

Save the data

End

Add the service port to the VLAN

Save the data

Configure the multicast data

Internet IPTV

Add a traffic profile (optional)

Create the VLAN

Add the upstream port to the VLAN



8-5

Procedure

Step 1 Configure the traffic profile.

The VoIP, IPTV, and Internet services are provided through the same port. Therefore, the 802.1ppriority must be set for each service. Generally, the priorities of the Internet, IPTV, and VoIPservices are in ascending order. Here, the indexes of the traffic profiles are 7, 8, and 9, and the802.1p priorities are 0, 4, and 6.

huawei(config)#traffic table ip index 7 name internet cir 10240 priority 0 priority-policy local-Settinghuawei(config)#traffic table ip index 8 name iptv cir 10240 priority 4 priority-policy local-Settinghuawei(config)#traffic table ip index 9 name voip cir 10240 priority 6 priority-policy local-Setting

Step 2 Create VLANs.

Create VLANs 100 - 103. VLAN 101 is the multicast VLAN.

huawei(config)#vlan 100-103 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 4 The total of the added VLANs is 4


Add an upstream port 0/0/0 to the VLAN.

huawei(config)#port vlan 100-103 0/0 0 // The VLAN of the upstream port on the ONU device must be the same as that of the access port on the upstream device. 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 4 The total of the port VLAN(s) having been added is 4

Step 4 Add service ports to the VLAN.

Create service port 2 that corresponds to user VLAN 2, smart VLAN 100, and traffic profile 7.Create service port 3 that corresponds to user VLAN 3, smart VLAN 103, and traffic profile 8.Create service port 4 that corresponds to user VLAN 4, smart VLAN 102, and traffic profile 9.

huawei(config)#service-port 2 vlan 100 eth 0/4/1 multi-service user-vlan 2 rx-cttr 7 tx-cttr 7huawei(config)#service-port 3 vlan 103 eth 0/4/1 multi-service user-vlan 3 rx-cttr 8 tx-cttr 8huawei(config)#service-port 4 vlan 102 eth 0/4/1 multi-service user-vlan 4 rx-cttr 9 tx-cttr 9

NOTE

Till now, the Internet service and VoIP service are configured. The following steps are used to configurethe multicast data of the IPTV service.

Step 5 Configure the multicast data.

1. Configure the multicast VLAN and IGMP mode.huawei(config)#multicast-vlan 101huawei(config-mvlan101)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y


Configuration Guide


Issue 04 (2011-04-27)

2. Configure the multicast uplink port.huawei(config-mvlan101)#igmp uplink-port 0/0/0

3. Configure the multicast program.huawei(config-mvlan101)#igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10

4. Configure the multicast user.huawei(config-mvlan101)#btvhuawei(config-btv)#igmp user add service-port 3huawei(config-btv)#multicast-vlan 101huawei(config-mvlan101)#igmp multicast-vlan member service-port 3

Step 6 Save the data.huawei(config-mvlan101)#quithuawei(config)#save

----End

ResultAfter the configurations on the related upstream device and downstream device, the triple playservice (Internet, VoIP, and IPTV services) on port 0/4/1 is available.l The users can access the Internet after the PPPoE dialup is successful on the PC.l The VoIP users can make and receive phone calls normally.l IPTV users: Users of port 0/4/1 can watch program 1.

Configuration FileConfigure the traffic profile.

traffic table ip index 7 name internet cir 10240 priority 0 priority-policy local-Settingtraffic table ip index 8 name iptv cir 10240 priority 4 priority-policy local-Settingtraffic table ip index 9 name voip cir 10240 priority 6 priority-policy local-Setting

Create VLANs.

vlan 100-103 smart

Add an upstream port to the VLAN.

port vlan 100-103 0/0 0

Add service ports to the VLAN.

service-port 2 vlan 100 eth 0/4/1 multi-service user-vlan 2 rx-cttr 7 tx-cttr 7service-port 3 vlan 103 eth 0/4/1 multi-service user-vlan 3 rx-cttr 8 tx-cttr 8service-port 4 vlan 102 eth 0/4/1 multi-service user-vlan 4 rx-cttr 9 tx-cttr 9

Configure the multicast data.

multicast-vlan 101igmp uplink-port 0/0/0igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10btvigmp user add service-port 3multicast-vlan 101igmp multicast-vlan member service-port 3quitsave



8-7

8.2 Configuration Example of the Multicast Service(Multicast VLAN Mode)

This topic describes how to configure the multicast service on the MA5612 in multicast VLANmode.

8.2.1 Configuration Example of the Multicast Video Service (Static Configuration Mode)This topic describes how to configure the multicast video service if the program in the multicastVLAN is configured statically.

8.2.2 Configuration Example of the Multicast Video Service (Dynamic Generation Mode)This topic describes how to configure the multicast video service if the program matching modeof the multicast VLAN is the dynamic generation mode.

8.2.1 Configuration Example of the Multicast Video Service (StaticConfiguration Mode)

This topic describes how to configure the multicast video service if the program in the multicastVLAN is configured statically.

Prerequisitel Network devices and lines must be in the normal state.l The multicast source must exist on the network and the IP address of the multicast source

must be known.

ContextThe program in the multicast VLAN can be configured statically or generated dynamically.

For the static configuration mode:l The program list needs to be configured for the multicast VLAN. Then, the user can request

for the program in this program list.l The following functions are supported: bandwidth management of the multicast program,

user bandwidth management, program preview, and program prejoin.l The program in the multicast VLAN is configured statically by default.

NetworkingFigure 8-4 shows the example network of the multicast service.


Configuration Guide


Issue 04 (2011-04-27)

Figure 8-4 Example network of the multicast service

Router

Multicast source

user1

STB

TV

ISP1 ISP2

user2

OLT

MA5612

Home Gateway

Data PlanTable 8-2 provides the data plan for configuring the multicast service.

Table 8-2 Data plan for configuring the multicast service

Device Item Data

ONU:MA5612

Smart VLAN l VLAN type: Smart VLANl VLAN ID: 4002-4005

Uplink port 0/0/0

IGMP version IGMP V3 (default multicast version of the system inmulticast VLAN mode)



8-9

Device Item Data

Multicastsource

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.1l ISP 2: with IP address 10.10.10.11, providing the

multicast program with IP address 224.1.1.2

Programlibrary

Program in multicast VLAN 4002:Program 1: with IP address 224.1.1.1 and the IP addressof the program source is the same as the IP address of ISP1, namely, 10.10.10.10


Multicast user Multicast user 1:l LAN port: 0/4/1l Multicast VLAN: 4002

Multicast user 2:l LAN port: 0/4/2l Multicast VLAN: 4003

Procedure

Step 1 Create VLANs and add an uplink port to the VLANs.huawei(config)#vlan 4002-4005 smarthuawei(config)#port vlan 4002-4005 0/0 0

Step 2 Configure service ports.huawei(config)#service-port 100 vlan 4004 eth 0/4/1 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6huawei(config)#service-port 101 vlan 4005 eth 0/4/2 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6

Step 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. Inthis example, the IGMP mode is IGMP proxy. If the planned IGMP mode is IGMP snooping, you canconfigure the IGMP snooping mode by running the igmp mode snooping command in multicast VLANmode.

The IGMP mode can be switched only when the IGMP mode is off.huawei(config)#multicast-vlan 4002huawei(config-mvlan4002)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:yhuawei(config-mvlan4002)#multicast-vlan 4003


Configuration Guide


Issue 04 (2011-04-27)

huawei(config-mvlan4003)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y

Step 4 Configure the multicast uplink port.huawei(config-mvlan4003)#igmp uplink-port 0/0/0huawei(config-mvlan4003)#multicast-vlan 4002huawei(config-mvlan4002)#igmp uplink-port 0/0/0

Step 5 Configure multicast programs.NOTE

l In static configuration mode, you can run the igmp program add command to add multicast programs inbatches. You cannot name a program, instead the system automatically names a program PROGRAM-M,in which M is the index of the added program.

l If the IGMP version of the multicast VLAN is V3, the source IP address of the program in the multicastVLAN must be configured. If the IGMP version of the multicast VLAN is V2, the source IP address of theprogram in the multicast VLAN cannot be configured.

huawei(config-mvlan4002)#igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10huawei(config-mvlan4002)#multicast-vlan 4003huawei(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)#btvhuawei(config-btv)#igmp user add service-port 100huawei(config-btv)#igmp user add service-port 101huawei(config-btv)#multicast-vlan 4002huawei(config-mvlan4002)#igmp multicast-vlan member service-port 100huawei(config-mvlan4002)#multicast-vlan 4003huawei(config-mvlan4003)#igmp multicast-vlan member service-port 101huawei(config-mvlan4003)#quit

Step 7 Save the data.huawei(config)#save

----End

Resultl User 1 belongs to multicast VLAN 4002 and user 1 can watch the program with IP address

224.1.1.1 provided by ISP1.l User 2 belongs to multicast VLAN 4003 and user 2 can watch the program with IP address

224.1.1.2 provided by ISP2.

Configuration FileThe following part describes the configuration file of this configuration example. Note thatcertain steps need to be performed manually and the configuration file cannot be importeddirectly.

Create VLANs and add an uplink port to the VLANs. This step needs to be performed manually.vlan 4002 to 4005 smartport vlan 4002 to 4005 0/0 0

Create service ports.service-port 100 vlan 4004 eth 0/4/1 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6service-port 101 vlan 4005 eth 0/4/2 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6

Configure multicast VLANs and the IGMP mode. This step needs to be performed manually.



8-11

multicast-vlan 4002igmp mode proxymulticast-vlan 4003igmp mode proxy

Configure the multicast uplink port, multicast programs, and multicast users.igmp uplink-port 0/0/0 multicast-vlan 4002 igmp uplink-port 0/0/0 igmp program add name program1 ip 224.1.1.1 sourceip 10.10.10.10 multicast-vlan 4003 igmp program add name program2 ip 224.1.1.2 sourceip 10.10.10.11 btv igmp user add service-port 100 igmp user add service-port 101 multicast-vlan 4002 igmp multicast-vlan member service-port 100multicast-vlan 4003igmp multicast-vlan member service-port 101quitsave

8.2.2 Configuration Example of the Multicast Video Service(Dynamic Generation Mode)

This topic describes how to configure the multicast video service if the program matching modeof the multicast VLAN is the dynamic generation mode.

Prerequisitel Network devices and lines must be in the normal state.l The multicast source must exist on the network and the IP address range of the multicast

program must be known.l The multicast program must be configured in dynamic generation mode.

ContextThe program in the multicast VLAN can be configured statically or generated dynamically.

Dynamic generation mode: A program is dynamically generated according to the programrequested by the user.l 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 theprogram whose IP address is within this IP address range.

l The following functions are not supported: bandwidth management of the multicastprogram, user bandwidth management, program preview, and program prejoin.

The program in the multicast VLAN is configured statically by default. Run the igmp matchmode 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 whenthe IGMP mode is off.

NetworkingFigure 8-5 shows the example network of the multicast service.


Configuration Guide


Issue 04 (2011-04-27)

Figure 8-5 Example network of the multicast service

Router

Multicast source

user1

STB

TV

ISP1 ISP2

user2

OLT

MA5612

Home Gateway

Data PlanTable 8-3 provides the data plan for configuring the multicast service.

Table 8-3 Data plan for configuring the multicast service

Device Item Data

ONU:MA5612

Smart VLAN l VLAN type: Smart VLANl VLAN ID: 4002-4005

Uplink port 0/0/0

IGMP version IGMP V3 (default multicast version of the system inmulticast VLAN mode)



8-13

Device Item Data

Multicastsource

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.1l ISP 2: with IP address 10.10.10.11, providing the

multicast program with IP address 224.1.1.2

Programlibrary



Multicast user Multicast user 1:l LAN port: 0/4/1l Multicast VLAN: 4002

Multicast user 2:l LAN port: 0/4/2l Multicast VLAN: 4003

Procedure

Step 1 Create VLANs and add an uplink port to the VLANs.huawei(config)#vlan 4002-4005 smarthuawei(config)#port vlan 4002-4005 0/0 0

Step 2 Configure service ports.huawei(config)#service-port 100 vlan 4004 eth 0/4/1 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6huawei(config)#service-port 101 vlan 4005 eth 0/4/2 multi-service user-vlan untagged 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. Inthis example, the IGMP mode is IGMP proxy. If the planned IGMP mode is IGMP snooping, you canconfigure the IGMP snooping mode by running the igmp mode snooping command in multicast VLANmode.

The IGMP mode can be switched only when the IGMP mode is off.huawei(config)#multicast-vlan 4002huawei(config-mvlan4002)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:yhuawei(config-mvlan4002)#multicast-vlan 4003


Configuration Guide


Issue 04 (2011-04-27)

huawei(config-mvlan4003)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y

Step 4 Configure the multicast uplink port.huawei(config-mvlan4003)#igmp uplink-port 0/0/0huawei(config-mvlan4003)#multicast-vlan 4002huawei(config-mvlan4002)#igmp uplink-port 0/0/0

Step 5 Configure multicast programs.

Configure the program in the multicast VLAN in dynamic generation mode, and specify the IPaddress 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 causethe 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.huawei(config-mvlan4002)#igmp match mode disablehuawei(config-mvlan4002)#igmp match group ip 224.1.1.1 to-ip 224.1.1.2huawei(config-mvlan4002)#multicast-vlan 4003huawei(config-mvlan4003)#igmp match mode disablehuawei(config-mvlan4003)#igmp match group ip 224.1.1.1 to-ip 224.1.1.2

Step 6 Configure multicast users.huawei(config-mvlan4002)#btvhuawei(config-btv)#igmp user add service-port 100huawei(config-btv)#igmp user add service-port 101huawei(config-btv)#multicast-vlan 4002huawei(config-mvlan4002)#igmp multicast-vlan member service-port 100huawei(config-mvlan4002)#multicast-vlan 4003huawei(config-mvlan4003)#igmp multicast-vlan member service-port 101huawei(config-mvlan4003)#quit


----End

Resultl User 1 belongs to multicast VLAN 4002 and user 1 can watch the program with IP address

224.1.1.1 provided by ISP1.l User 2 belongs to multicast VLAN 4003 and user 2 can watch the program with IP address

224.1.1.2 provided by ISP2.

Configuration FileThe following part describes the configuration file of this configuration example. Note thatcertain steps need to be performed manually and the configuration file cannot be importeddirectly.

Create VLANs and add an uplink port to the VLANs. This step needs to be performed manually.vlan 4002 to 4005 smartport vlan 4002 to 4005 0/0 0

Create service ports.service-port 100 vlan 4004 eth 0/4/1 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6 service-port 101 vlan 4005 eth 0/4/2 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6

Configure multicast VLANs and the IGMP mode. This step needs to be performed manually.



8-15

multicast-vlan 4002igmp mode proxymulticast-vlan 4003igmp mode proxy

Configure the multicast uplink port, multicast programs, and multicast users.igmp uplink-port 0/0/0 multicast-vlan 4002 igmp uplink-port 0/0/0 igmp match mode disableigmp match group ip 224.1.1.1 to-ip 224.1.1.2 multicast-vlan 4003 igmp match mode disableigmp match group ip 224.1.1.1 to-ip 224.1.1.2 btv igmp user add service-port 100 igmp user add service-port 101 multicast-vlan 4002 igmp multicast-vlan member service-port 100multicast-vlan 4003igmp multicast-vlan member service-port 101quitsave

8.3 Configuration Example of the VoIP ServiceThis topic describes how to configure the VoIP service based on the H.248 or SIP protocol.

8.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.

8.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.

8.3.3 Configuration Example of the VoIP ISDN PRA Service (Based on the H.248 Protocol)This topic describes how to configure the VoIP ISDN PRA service based on the H.248 protocol.

8.3.4 Configuration Example of the VoIP ISDN PRA Service (Based on the SIP Protocol)This topic describes how to configure the VoIP ISDN PRA service based on the SIP protocol.

8.3.1 Configuration Example of the VoIP PSTN Service (Based onthe H.248 Protocol)

This topic describes how to configure the VoIP service based on the H.248 protocol.

Service RequirementsIn an office located in China, the MA5612 that adopts the H.248 protocol is newly deployed.Data plan and configuration, however, are not performed on the MGC (softswitch) connectedto the MA5612. The following voice services are required:

l POTS service needs to be provided for phone 0-phone 15.l Polarity reversal charging is adopted.

Prerequisitel According to the actual network, a route from the MA5612 to the MGC must be configured

to ensure that the MA5612 and the MGC are reachable to each other.


Configuration Guide


Issue 04 (2011-04-27)

l POTS service board H831ASNB must be inserted into the planned slot, and the RUN ALMindicator on the board must be green and must be on for 1s and off for 1s repeatedly.

NetworkingFigure 8-6 shows the example network of the VoIP service based on the H.248 protocol.

Figure 8-6 Example network of the VoIP service based on the H.248 protocol

MGC Router

H.248

OLT

Phone 0Tel: 83110000

MA5612

Splitter

Phone 15Tel: 83110015

Community: huawei

...

Media and signaling uplink VLAN: Standard VLAN 20MG interface 0Media and signaling IP addresses: 10.10.10.10

Data PlanAfter 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



8-17

data plan described in 7.1 Configuring the VoIP PSTN Service (Based on the H.248Protocol). Table 8-4 provides the data plan for configuring the VoIP service based on the H.248 protocol.

Table 8-4 Data plan for configuring the VoIP service based on the H.248 protocol

Item Data

MG interfacedata(The dataconfigurationmust beconsistent withthe dataconfigurationon the MGC.)



Standard VLAN is recommended as theupstream VLAN of the voice service. Inthis section, standard VLAN 20 isadopted.

Media andsignalingupstream port

0/0/0


These two IP addresses are both10.10.10.10.


Confirmed with the engineers of thisoffice, the IP address of the next hopfrom the MA5612 to the MGC is10.10.10.1.

Attributeparameters of theMGinterfaceNOTE

Parameters listedhere aremandatory, whichmeansthat theMGinterfacefails to bestarted iftheseparameters are notconfigured.

MG interface ID 0, indicating that the negotiation isbased on the profile

Signaling port IDof the MGinterface

The signaling port ID is 2944.

IP address of theprimary MGC towhich the MGinterface belongs

The network of the office does notsupport dual homing.According to the network topology, theIP address of the primary MGC is10.10.20.20, and the port ID is 2944, thesame as the port ID on the MA5612.Port ID of the

primary MGC towhich the MGinterface belongs

Coding mode ofthe MG interface

The text coding mode is adopted.

Transmissionmode of the MGinterface

UDP

Domain name ofthe MG interface

The message ID (MID) adopts the IPaddress (default), and may not beconfigured with a domain name.


Configuration Guide


Issue 04 (2011-04-27)

Item Data

Device name ofthe MG interface

The MID adopts the IP address(default), and may not be configuredwith a device name.

Start negotiationversion of the H.248 protocol forthe MG interface

0

Digitmap of an MG Interface Special applications such as emergencycalls and emergency standalone are notconfigured. Therefore, the digitmap isnot configured.

Software Parameters of anMG Interface

According to the Context in SoftwareParameters of an MG Interface andconfirmed with the engineers of theoffice, the default configuration canmeet the service requirements.Therefore, the software parameters arenot configured.

Ringing Mode of an MGInterface

Confirmed with the engineers of theoffice, the value of the ringingparameter (corresponding to the users)specified on the MGC is 0 (value ofmgcpara), and the users have no specialrequirements for the ringing mode.Therefore, the normal ringing with thebreak-make ratio of 1:4 is adopted.

TID Format of an MGInterface

To differentiate users by terminal ID(TID), the engineers of the officerequire that the terminal prefix uses thecommunity name huawei and the TIDis automatically generated by thesystem according to the slot ID/shelfID/port ID of the user.Run the display tid-templatecommand to query the default TIDtemplate. It is found that default TIDtemplate (template 6) can meet therequirements.

Voice servicedata(The dataconfigurationmust beconsistent withthe data


The user is accessed through the 0/3port on the H831ASNB board.



8-19

Item Data

configurationon the MGC.)

User Data Phone number The emergency standalone is notsupported. Therefore, you need notconfigure the phone number whenadding a user.Phone numbers allocated by the MGCfor phone 0-phone 15 are83110000-83110015.NOTE

Generally, No telephone number (namely,parameter telno) is configured on the MG,because telephone numbers are specified bythe MGC.

TID The terminal layering is supported.Therefore, the TID need not beallocated manually.

User priority Users are common users, and the userpriority uses the default priority,namely, cat3.

User type Users are common users, and the usertype uses the default user type, namely,DEL.

System Parameters According to the Context in 7.1.2.2(Optional) Configuring the SystemParameters and confirmed with theengineers of the office, the defaultconfiguration can meet the servicerequirements. Therefore, the systemparameters are not configured.

Overseas Parameters According to the Context in 7.1.2.3(Optional) Configuring the OverseasParameters and confirmed with theengineers of the office, the defaultconfiguration can meet the servicerequirements. Therefore, the overseasparameters are not configured.

LocalDigitmap

Digitmap name huawei

Digitmap type Only the normal digitmap is supportedif the H.248 protocol is used.


Configuration Guide


Issue 04 (2011-04-27)

Item Data

CAUTIONBydefault,theseparameters need notbeconfigured if the H.248protocolis used.You canconfiguretheseparametersaccordingto therequirements.

Digitmap body Plan this parameter according to theprefix of the local phone number. In thisexample, the ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx) digitmap body is used.

Attributes of a PSTN Port The polarity reversal charging isrequired for the service. Therefore, youneed to configure the PSTN port towhich the user belongs so that the PSTNport supports the polarity reversalimpulse. The other attributes of thePSTN port need not be modified.


The ringing attribute need not beconfigured unless otherwise specified.

Procedure

Step 1 Configure the upstream VLAN interface.

According to the data plan, configure standard VLAN 20 as the media and signaling upstreamVLAN, add upstream port 0/0/0 to the VLAN, and configure the IP address of the L3 interfaceto 10.10.10.10, which facilitates the configuration of the media and signaling IP address pools.

huawei(config)#vlan 20 standardhuawei(config)#port vlan 20 0/0 0huawei(config)#interface vlanif 20huawei(config-if-vlanif20)#ip address 10.10.10.10 24

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 andsignaling IP address pools respectively. Thus, the media and signaling IP addresses used for theservices can be selected from the IP address pools. According to the data plan, IP address10.10.10.10 is added to the media and signaling IP address pools, and the gateway IP addresscorresponding to the media IP address is 10.10.10.1.

huawei(config-if-vlanif20)#quithuawei(config)#voiphuawei(config-voip)#ip address media 10.10.10.10 10.10.10.1huawei(config-voip)#ip address signaling 10.10.10.10



8-21


Add an MG interface for the MG to communicate with the MGC, which ensures that the MGCcan control the call connection through the MG interface. According to the data plan, add MGinterface 0 and configure the interface attributes.

huawei(config-voip)#quithuawei(config)#interface h248 0 Are you sure to add MG interface?(y/n)[n]:yhuawei(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 thecadence ringing and initial ringing are both 1:4. Therefore, the value of parameter cadence is 0,and the value of parameter initialring is 4.

huawei(config-if-h248-0)#mg-ringmode add 0 0 4

Step 5 Configure the TID template of the PSTN user on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix of the PSTNuser needs to be configured to huawei, and the TID template adopts layering template 6.

CAUTIONThe MA5612 requires that the terminal prefixes of PSTN users, ISDN BRA users, and ISDNPRA users on the same H.248 interface are either the same or different. Note this whenconfiguring 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 themodified attributes of the MG interface take effect) so that the MG interface can work in thenormal state. The MG interface can be started in different manners (see Parameter Descriptionof the reset command). For a newly configured MG interface, start the MG interface in a coldstart manner.

huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:y

Step 7 Query the running status of the MG interface.

After the MG interface is interconnected with the MGC successfully, the MG interface needs tobe in the normal state, indicating that the MG interface works in the normal state.

huawei(config-if-h248-0)#quithuawei(config)#display if-h248 all ------------------------------------------------------------------------------ MGID Trans State MGPort MGIP MGCPort MGCIP/DomainName ------------------------------------------------------------------------------ 0 UDP Normal 2944 10.10.10.10 2944 10.10.20.20 ------------------------------------------------------------------------------


Configuration Guide


Issue 04 (2011-04-27)

Step 8 Confirm the service board.

Confirm the H831ASNB board that carries services to ensure that the board can work in thenormal 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 userhuawei(config-esl-user)#mgpstnuser batadd 0/3/0 0/3/15 0

Step 10 Configure the local digitmap.

After the configuration, the MA5612 matches the phone number according to the local digitmapif the MGC does not send the detailed digitmap to the MA5612.

huawei(config-esl-user)#quithuawei(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 thepolarity reversal pulse, so that the user can support the polarity reversal charging.

huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse enable

Step 12 Save the data.huawei(config-pstnport)#quithuawei(config)#save

----End

ResultAfter the interface data and the PSTN user data corresponding to the MG interface are configuredon the MGC, check whether the VoIP service can be provided normally. In normal cases, phone0-phone 15 can call each other.

l The calling party can hear the dial tone after picking up the phone off the hook.l 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 doesnot ring but the phone of another user connected to the MA5612 rings, and the calling party hearsthe ringback tone, check whether the MGC is configured with the call forwarding service, causingthe line cross.

l If the MGC is configured with the call forwarding service, cancel the call forwarding service onthe MGC.

l If the MGC is not configured with the call forwarding service, contact Huawei technical supportengineer to handle the fault.

l The calling party and the called party can communicate with each other normally.l After the called party places the phone on the hook, the calling party can hear the busy tone.



8-23

Configuration FileThe following part describes the configuration file of this configuration example. Note thatcertain steps must be performed manually and the configuration file cannot be imported directly.

Configure the upstream VLAN interface.

vlan 20 standardport vlan 20 0/0 0interface vlanif 20ip address 10.10.10.10 24

Configure the media and signaling IP address pools.

quitvoipip address media 10.10.10.10 10.10.10.1ip address signaling 10.10.10.10

Add an MG interface and then configure the attributes of the MG interface. An MG interfacemust be added manually and the configuration file cannot be imported directly.

quitinterface h248 0if-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

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.

quitdisplay if-h248 all

Confirm the service board.

board confirm 0/3

Configure the PSTN user data.

esl usermgpstnuser batadd 0/3/0 0/3/15 0

Configure the local digitmap.

quitlocal-digitmap add huawei normal ([2-8]xxxxxxx|[2-8]xxSxxxxxxx|13xxxxxxxxx|0xxxxxxxxx)

Configure the polarity reversal charging function.

pstnportpstnport attribute batset 0/3/0 0/3/15 reverse-pole-pulse enable

Save the data.

quitsave


Configuration Guide


Issue 04 (2011-04-27)

8.3.2 Configuration Example of the VoIP PSTN Service (Based onthe SIP Protocol)

This topic describes how to configure the VoIP PSTN service based on the SIP protocol.

Prerequisitel The voice service board H831ASNB must be installed in the specified slot.l The SIP interface must be configured. For how to configure the SIP interface, see 7.2.1

Configuring the SIP Interface.l The PSTN user data corresponding to the SIP interface must be configured on the IMS.

NetworkingFigure 8-7 shows the example network of the VoIP PSTN service based on the SIP protocol.

Figure 8-7 Example network of the VoIP PSTN service based on the SIP protocol

Router

OLT

Phone Phone PhonePhone

MA5612

Splitter

SIP

Out-centrex prefix: 8100

... ...



8-25

Data Plan

In this example, the MA5612 is used in China. The default configurations of system parametersand overseas parameters can meet the standard and application requirements. Therefore, youneed not configure these parameters.

Table 8-5 provides the data plan for configuring the VoIP PSTN service based on the SIPprotocol.

Table 8-5 Data plan for configuring the VoIP PSTN service based on the SIP protocol

Item Data

SIP interface SIP interface ID 0

Local digitmap Digitmap name huawei0 and huawei1

Digitmap type The digitmap type of huawei0 is normal.The digitmap type of huawei1 is second-centrex.NOTE

The parameters of the emergency digitmap usedefault 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 serviceboardH831ASNB

Slot that houses the board 0/3

Data of thePSTN users inslot 0/3

Numbers of phone 0-phone 15

83110000-83110015

User priority The priority of phone 0 is Cat2 and the priorityof phone 1-phone 15 is Cat3 (default priority).

User type The type of phone 0 is DEL and the type ofphone 1-phone 15 is Payphone.

PSTN port attribute Phone 1-phone 15 support polarity reversalimpulse.

Procedure

Step 1 Configure the local digitmap.

Configure the local call digitmap and two-stage dialing digitmap. The parameters of theemergency digitmap use the default values.


Configuration Guide


Issue 04 (2011-04-27)

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)

Step 2 Configure the PSTN user data.1. Configure the data of the PSTN users (phone 0-phone 15) in slot 0/3.

huawei(config)#esl userhuawei(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.

Configure the PSTN port in slot 0/3 so that the port supports polarity reversal impulse.

huawei(config-esl-user)#quithuawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/3/1 0/3/15 reverse-pole-pulse enable

Step 4 Save the data.huawei(config-pstnport)#quithuawei(config)#save

----End

ResultAfter 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.l 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 doesnot ring but the phone of another user connected to the MA5612 rings, and the calling party hearsthe ringback tone, check whether the IMS is configured with the call forwarding service, causing theline 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.

l The calling party and the called party can communicate with each other normally.l After the called party places the phone on the hook, the calling party can hear the busy tone.


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)



8-27

Configure the PSTN user data.

esl usersippstnuser batadd 0/3/0 0/3/15 0 telno 83110000sippstnuser attribute set 0/3/0 priority cat2sippstnuser attribute batset 0/3/1 0/3/15 potslinetype PayPhone

Configure the PSTN port attribute.

quitpstnportpstnport attribute batset 0/3/1 0/3/15 reverse-pole-pulse enable

Save the data.

quitsave

8.3.3 Configuration Example of the VoIP ISDN PRA Service (Basedon the H.248 Protocol)

This topic describes how to configure the VoIP ISDN PRA service based on the H.248 protocol.

Prerequisitel According to the actual network, a route from the MA5612 to the MGC must be configured

to ensure that the MA5612 communicates with the MGC normally.l The E1 board H831E81A must be inserted into the planned slot correctly, and the RUN

ALM indicator on the board must be green and must be on for 1s and off for 1s repeatedly.

Service RequirementsWhen the MA5612 in an office is newly deployed and put into operation (the device uses theH.248 protocol and the data on the MGC is not planned and configured), the following ISDNPRA service is required:

l An enterprise user huawei is configured with 30 common phone users, who are connectedto the same PBX. The device must support the call between these users, and the call betweenthese users and other voice users on the PSTN network.

l The E1 board H831E81A is in the E1 mode and the E1 port mode is SDT. The E1 port usesthe system clock source and uses the common channel signaling for signaling transmission.

Figure 8-8 shows an example network for configuring the H.248-based VoIP ISDN PRAservice.


Configuration Guide


Issue 04 (2011-04-27)

Networking

Figure 8-8 Example network for configuring the H.248-based VoIP ISDN PRA service

MGC Router

H.248

OLT

Phone 0

MA5612

Splitter

Uplink VLAN: Standard VLAN 20MG interface 0Media and signaling IP addresses:10.10.10.10

Community: huawei

Phone 30

PBX

Data Plan

The service requirements are further confirmed and analyzed with the customer, and then thedata plan is made with the MGC engineers according to the data plan described in 7.3Configuring the VoIP ISDN PRA Service (Based on the H.248 Protocol). The final data planis as listed in Table 8-6.



8-29

Table 8-6 Data plan for configuring the H.248-based VoIP ISDN PRA service

Item Data

IUA link IUA link set ID It is confirmed with the customer engineersthat the planned value is 0.

Generation mode of theinterface ID (IID)

It is confirmed with the customer engineersthat the planned value is 2, that is, using thebinary value that is automatically generatedin ffsspp mode as the IID. ff indicates theshelf ID, ss indicates the slot ID, and ppindicates the port ID.

IUA link ID It is confirmed with the customer engineersthat the planned value is 0.

Local port ID The port ID is 1402.

Local IP address It is confirmed with the customer engineersthat the planned value is 10.10.10.30. (TheIP address must exist in the media IP addresspool.)

Remote port ID The port ID is 1404.

Remote IP address It is configured to 10.10.20.20, which is theIP address of the primary MGC.

MG interfacedata(The data mustbe consistentwith the data onthe MGC.)


UpstreamVLAN formedia andsignalingstreams

Standard VLAN is recommended as theupstream VLAN of the voice service. In thiscase, standard VLAN 20 is used.

Uplink portfor media andsignalingstreams

In this office, all the services are transmittedupstream through the control board.Therefore, port 0/0/0 is used as the uplinkport of the ISDN PRA service.

Media IPaddress andsignaling IPaddress

The two IP addresses are both 10.10.10.10.(The IP address must exist in the media IPaddress pool.)

Default IPaddress of theMG

It is confirmed with the customer engineersthat the next hop IP address from MA5612to the MGC is 10.10.10.1.

Attributeparameters of theMGinterface

MG interfaceID

0

Signaling portID of the MGinterface

The port ID is 2944.


Configuration Guide


Issue 04 (2011-04-27)

Item Data

NOTEParameters listedhere aremandatory, whichmeansthat theMGinterfacecannot bestarted iftheseparameters are notconfigured.

IP address ofthe primaryMGC towhich the MGinterfacebelongs

The network of the customer is notconfigured with the dual homing feature.According to the network topology, the IPaddress of the primary MGC is 10.10.20.20,and the port ID is 2944, which is the sameas the port ID on the MA5612.

Port ID of theprimary MGCto which theMG interfacebelongs

Coding modeof the MGinterface

The text coding mode is adopted.

Transmissionmode of theMG interface

UDP

Domain nameof the MGinterface

The message ID (MID) is indicated by theIP address (default setting), and may not beconfigured with the domain name.

Device nameof the MGinterface

The MID is indicated by the IP address(default setting), and may not be configuredwith a device name.

Digitmap of the MGinterface

Special applications such as emergencycalls and emergency standalone are notconfigured, and therefore this parameter isnot configured.

Software parameters ofthe MG interface

According to the "Background Information"in Software parameters of the MGinterface, the customer engineers confirmthat the default configuration can meet theservice requirements. Therefore, thisparameter is not configured.

Ringing mode of the MGinterface

It is confirmed with the customer engineersthat the value of the ringing parameterdefined by the MGC is 0 (value ofmgcpara), and the users have no specialrequirement on the ringing mode.Therefore, the normal ringing with thebreak-make ratio of 1:4 is used.



8-31

Item Data

Terminal ID (TID) formatof the MG interface

To differentiate users according to the TID,the customer requires that the terminalprefix uses the community name huawei,and the TID is automatically generated bythe system according to the slot ID/shelf ID/port ID of the user.The display tid-template command isexecuted to query the default TID formatprofile. It is found that default TID formatprofile (profile 6) can meet therequirements.

ISDN PRA userdata(The data mustbe consistentwith the data onthe MGC.)

Slot that houses the E1board

The users are connected to the H831E81Aboard in slot 0/1.

User data TerminationID

The terminal layering is supported, andtherefore the TIDs need not be allocatedmanually.

User priority The users are common users, and the userpriority is the default value cat3.

Interface ID The interface ID need not be configuredbecause the interface ID is generated by thesystem (the IID is configured to 2 when theIUA line set is configured).

System parameters According to the "Background Information"in 7.1.2.2 (Optional) Configuring theSystem Parameters, the customerengineers confirm that the defaultconfiguration can meet the servicerequirements. Therefore, these parametersare not configured.

Overseas parameters According to the "Background Information"in 7.1.2.3 (Optional) Configuring theOverseas Parameters, the customerengineers confirm that the defaultconfiguration can meet the servicerequirements. Therefore, these parametersare not configured.

E1 port attributes The E1 port mode needs to be configured toSDT. The other attributes need not bemodified.

Procedure

Step 1 Configure the MG interface.


Configuration Guide


Issue 04 (2011-04-27)

1. Configure the upstream VLAN interface.

According to the data plan, configure standard VLAN 20 as the media and signalingupstream VLAN, add upstream port 0/0/0 to the VLAN, and configure the IP address ofthe L3 interface to 10.10.10.10. This facilitates the configuration of the media and signalingIP address pools.

huawei(config)#vlan 20 standardhuawei(config)#port vlan 20 0/0 0huawei(config)#interface vlanif 20huawei(config-if-vlanif20)#ip address 10.10.10.10 24

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 mediaand signaling IP address pools respectively. Thus, you can select the media and signalingIP addresses used for the services from the IP address pools. According to the data plan,IP address 10.10.10.10 is added to the media and signaling IP address pools, and thegateway IP address corresponding to the media IP address is 10.10.10.1.

huawei(config-if-vlanif20)#quithuawei(config)#voiphuawei(config-voip)#ip address media 10.10.10.10 10.10.10.1huawei(config-voip)#ip address signaling 10.10.10.10

3. Add an MG interface.

Add an MG interface for communicating with the MGC. This ensures that the MGC cancontrol the call connection through the MG interface. According to the data plan, add MGinterface 0, and configure the interface attributes.

huawei(config-voip)#quithuawei(config)#interface h248 0 Are you sure to add MG interface?(y/n)[n]:yhuawei(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

4. Configure the ringing mapping of MG interface 0.

Configure the user ringing mode. According to the data plan, the break-make ratios of thecadence ringing and the initial ringing are both 1:4. Therefore, the value of parametercadence is 0, and the value of parameter initialring is 4.

huawei(config-if-h248-0)#mg-ringmode add 0 0 45. Configure the TID profile of the PRA users on MG interface 0.

Configure the TID generation mode. According to the data plan, the terminal prefix of thePRA users needs to be huawei, and the TID format profile uses layering profile 6.

CAUTIONThe MA5612 requires that the terminal prefixes of PSTN users, ISDN BRA users, andISDN PRA users on the same H.248 interface are either the same or different. Note thiswhen configuring the terminal prefix.

huawei(config-if-h248-0)#tid-format pra prefix huawei template 66. Reset the MG interface.



8-33

Reset the MG interface to make the MG interface register with the MGC (and to make themodified attributes of the MG interface take effect) so that the MG interface can work inthe normal state. The MG interface can be started in different manners (see Parameters ofthe reset command). For a new MG interface, start the MG interface by cold start.

huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:y

7. Query the running status of the MG interface.

After the MG interface interconnects with the MGC successfully, the MG interface statusneeds to be normal, that is, the MG interface works in the normal state.

huawei(config-if-h248-0)#quithuawei(config)#display if-h248 all ------------------------------------------------------------------------- MGID TransMode State MGPort MGIP/DomainName MGCPort MGCIP/DomainName ------------------------------------------------------------------------- 0 UDP Normal 2944 10.10.10.10 2944 10.10.20.20 -------------------------------------------------------------------------

Step 2 Configure the IUA linkhuawei(config)#sigtranhuawei(config-sigtran)#iua-linkset add 0 iid-map 2huawei(config-sigtran)#iua-link add 0 0 1402 10.10.10.30 1404 10.10.10.20

Step 3 Configure the ISDN PRA user data.1. Confirm the service board.

Confirm the H831E81A board that carries services and ensure that the board can work inthe normal state.

huawei(config)#board confirm 0/1

2. Configure the E1 port mode.

huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 sdt system ccs

3. Add an ISDN PRA user.huawei(config)#esl userhuawei(config-esl-user)#mgprauser add 0/1/0 0 0

Step 4 Save the data.huawei(config-if-tdm-0/1)#quithuawei(config)#save

----End

ResultAfter the interface data and the ISDN PRA user data corresponding to the MG interface areconfigured on the MGC, and all the voice service users are configured on the PBX, check whetherthe service can be provided normally. In normal cases, users phone 0 -phone 30 can call eachother normally, and any user among phone 0-phone 30 can call other users on the PSTN networknormally.

l The calling party can hear the dial tone after picking up the phone off the hook.l When the calling party dials the phone number of the called party, the phone of the called

party rings normally, and the calling party hears the ringback tone.l The calling party and the called party can communicate with each other successfully.


Configuration Guide


Issue 04 (2011-04-27)

l After the called party places the phone on the hook, the calling party hears the busy tone.

Configuration FileThe following section provides the configuration scripts of this configuration example. Notethat certain steps must be performed manually and the configuration scripts cannot be onceimported directly.

Configure the upstream VLAN interface.vlan 20 standardport vlan 20 0/0 0interface vlanif 20ip address 10.10.10.10 24

Configure the media and signaling IP address pools.quitvoipip address media 10.10.10.10 10.10.10.1ip address signaling 10.10.10.10

Add an MG interface and configure the attributes of the MG interface. You must add the MGinterface manually as the configuration scripts cannot be imported directly.quitinterface h248 0if-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

Configure the ringing mapping of the MG interface.mg-ringmode add 0 0 4

Configure the TID profile of the PRA users on the MG interface.tid-format pstn prefix huawei template 6

The MG interface must be started manually as the configuration scripts cannot be importeddirectly.reset coldstart

Query the running status of the MG interface.quitdisplay if-h248 all

Configure the IUA Linksigtraniua-linkset add 0 iid-map 2iua-link add 0 0 1402 10.10.10.30 1404 10.10.10.20

Confirm the service board.board confirm 0/1

Configure the E1 port mode.interface tdm 0/1port 0 sdt system ccs

Configure the ISDN PRA user data.esl usermgprauser add 0/1/0 0 0



8-35

Save the data.

quitsave

8.3.4 Configuration Example of the VoIP ISDN PRA Service (Basedon the SIP Protocol)

This topic describes how to configure the VoIP ISDN PRA service based on the SIP protocol.

Prerequisitel E1 board H831E81A must be inserted into the specified service slot.l The SIP interface must be configured. For detailed procedure, see 7.2.1 Configuring the

SIP Interface.l The ISDN PRA user data corresponding to the SIP interface must be configured on the

IMS.

Service RequirementsThe MA5612 that uses the SIP protocol is newly deployed in an office to meet the ISDN PRAservice requirements as follows:

Configure 30 common phone users that are connected to the same PBX for an enterprise userhuawei. The device must support the call service between these users, and the call servicebetween these users and other phone users on the PSTN network. In addition, the PBX must beconfigured with two phone numbers.

NetworkingFigure 8-9 shows the example network of the VoIP ISDN PRA service when the SIP protocolis used.


Configuration Guide


Issue 04 (2011-04-27)

Figure 8-9 Example network of the VoIP ISDN PRA service when the SIP protocol is used

Router

OLT

Phone 0 Phone 30

MA5612

Splitter

SIP

PBX

Data PlanConfirmed with the office, the default configuration of system parameters and overseasparameters can meet the standard and application requirement. Therefore, additionalconfiguration is not required. The data plan is made by analyzing the service requirement andby considering the interconnection with the IMS according to the data plan described in 7.4Configuring the VoIP ISDN PRA Service (Based on the SIP Protocol). Table 8-7 providesthe final data plan.



8-37

Table 8-7 Data plan for configuring the VoIP PSTN service when the SIP protocol is used

Item Data

SIP interface SIP interface ID 0

E1 boardH831E81A

Slot that houses the board 0/1

The ISDN PRAuser data in slot0/1

ID of the user port 0/1/0

User phone number 28780000

Extended phone number 28780001 (second phone number of the user)

User priority Cat2

Attributes of E1 port You need to set the working mode of the E1port to SDT, and need not modify otherattributes.

Procedure

Step 1 Configure E1 board (H831E81A).1. Run the display board command to check whether the E1 board is in the normal state.

huawei(config)#display board 0 ------------------------------------------------------------------------- SlotID BoardName Status SubType0 SubType1 Online/Offline ------------------------------------------------------------------------- 0 H832CCFE Active_normal UP2A ASDB 1 H831E81A Normal 2 H831EIUC Normal 3 H831ASNB Normal 4 H831EPFB Normal -------------------------------------------------------------------------

2. If the E1 board is in the to-be-confirmed state, run the board confirm command to confirmboard H831E81A.huawei(config)#board confirm 0/1

Step 2 Configure an E1 Port.

Configure port 0/1/0 to work in SDT mode, the system clock source is used, and the signal istransmitted in common channel signaling mode.

huawei(config-esl-user)#quithuawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 sdt system ccs

Step 3 Configure the ISDN PRA user data.1. Configure the ISDN PRA user data on port 0/1/0.

huawei(config)#esl userhuawei(config-esl-user)#sipprauser add 0/1/0 0 telno 28780000huawei(config-esl-user)#sipprauser extend-telno add 0/1/0 28780001

2. Configure the call priority of the ISDN PRA user on port 0/1/0 to Cat2.huawei(config-esl-user)#sipprauser attribute set 0/1/0 priority cat2



Configuration Guide


Issue 04 (2011-04-27)

huawei(config-if-tdm-0/1)#quithuawei(config)#save

----End

ResultAfter the interface data and the ISDN PRA user data corresponding to the SIP interface areconfigured on the IMS, and all the phone users are configured on the PBX, check whether theservice can be provided normally. In normal cases, users phone 0 - phone 30 can call each othersuccessfully, and any one user among phone 0 - phone 30 can call other users on the PSTNnetwork successfully.l The calling party can hear the dial tone after picking up the phone off the hook.l When the calling party dials the phone number of the called party, the phone of the called

party rings normally, and the calling party hears the ringback tone.l The calling party and the called party can communicate with each other successfully.l After the called party places the phone on the hook, the calling party hears the busy tone.


Configure the E1 board.

display board 0board confirm 0/1

Configure the attributes of the E1 port.

quitinterface tdm 0/1port 0 sdt system ccs

Configure the ISDN PRA user data.

esl usersipprauser add 0/1/0 0 telno 28780000sipprauser extend-telno add 0/1/0 8675528780000sipprauser attribute set 0/1/0 priority cat2

Save the data.

quitsave

8.4 Configuration Example of the VLAN StackingWholesale Service

This topic describes the VLAN stacking wholesale service and how to configure the VLANstacking wholesale service on the MA5612.

8.4.1 Configuration Example of the VLAN Stacking Wholesale ServiceThis topic describes how to configure the wholesale service so that the service provided by theISP can be delivered promptly to a specified user group.

8.4.2 Configuration Example of the VLAN ID Extension Service



8-39

This topic describes how to configure the VLAN ID extension for increasing the number of usersthat can be identified according to the VLAN ID by the BRAS.

8.4.1 Configuration Example of the VLAN Stacking WholesaleService

This topic describes how to configure the wholesale service so that the service provided by theISP can be delivered promptly to a specified user group.

Prerequisitel Network devices and lines must be in the normal state.l The authentication data of the access user must be configured on the BRAS.l The control board and the corresponding service boards must be in the normal state.

Service Requirementsl The user accesses the Internet through the PPPoE dialup.l The device adds an outer VLAN tag to user packets to identify ISPs, and adds an inner

VLAN tag to identify users.

NetworkingFigure 8-10 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. TheMA5612 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 VLANtag to identify users. Then, the device forwards the packets to the L2 network. The L2 switchforwards the user packets to a specified ISP BRAS based on the outer VLAN tags. The ISPBRAS 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 theISP.


Configuration Guide


Issue 04 (2011-04-27)

Figure 8-10 Example network for configuring the VLAN stacking wholesale service

OLT

BRAS

User1 User2 User3 User4

VLAN ID:100 VLAN ID:101

BRAS

MA5612

Splitter

ISP1 ISP2

LAN Switch

Data Plan

Table 8-8 provides the data plan for configuring the VLAN stacking wholesale service.

Table 8-8 Data plan for configuring the VLAN stacking wholesale service

Item Data

ISP 1 user group Upstream port: 0/0/0

Network-side VLAN ID (outer VLAN tag): 100

VLAN attribute: stacking VLAN

User 1:l Access port: 0/4/1l Inner VLAN tag: 11



8-41

Item Data


ISP 2 user group Upstream port: 0/0/0

Network-side VLAN ID (outer VLAN tag): 101

VLAN attribute: stacking VLAN



Procedure

Step 1 Create VLANs.

Network-side VLAN IDs are 100 and 101, and the VLAN type is smart VLAN.

huawei(config)#vlan 100-101 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

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 supportedby VLAN stacking on the MA5612. You can also run the stacking inner-ethertype command to set thetype of inner Ethernet protocol supported by VLAN stacking on the MA5612. To ensure that Huawei deviceis interconnected with the device of other vendors, the type of the inner/outer Ethernet protocol must bethe same as that of the interconnect device.

huawei(config)#vlan attrib 100-101 stacking It will take several minutes, and console may be timeout, please use command idle-timeout to set time limit Are you sure to continue? (y/n)[n]:y The total of the VLANs having been processed is 2 The total of the VLAN(s) which have been operated successfully is 2


Add upstream port 0/0/0 to VLAN 100 and VLAN 101.

huawei(config)#port vlan 100-101 0/0 0 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


Configuration Guide


Issue 04 (2011-04-27)

The total of the VLANs having been processed is 2 The total of the port VLAN(s) having been added is 2

Step 4 Add service ports to the VLAN.

Create service ports for users 1, 2, 3, and 4, and then add the service ports to VLAN 100 andVLAN 101.

huawei(config)#service-port 1 vlan 100 eth 0/4/1 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6huawei(config)#service-port 2 vlan 100 eth 0/4/2 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6huawei(config)#service-port 3 vlan 101 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6huawei(config)#service-port 4 vlan 101 eth 0/4/4 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6

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 mustbe unique. The VLAN tags under different ISPs can be the same with each other.

huawei(config)#display service-port all ------------------------------------------------------------------------- INDEX VLAN VLAN PORT F/ S/ P VPI VCI FLOW FLOW RX TX STATE ID ATTR TYPE TYPE PARA ------------------------------------------------------------------------- 1 100 stacking eth 0/4/ 1 - - encap pppoe 6 6 up 2 100 stacking eth 0/4/ 2 - - encap pppoe 6 6 up 3 101 stacking eth 0/4/ 3 - - encap pppoe 6 6 up 4 101 stacking eth 0/4/ 4 - - encap pppoe 6 6 up ------------------------------------------------------------------------- Total : 4 (Up/Down : 4/0)huawei(config)#stacking label service-port 1 11huawei(config)#stacking label service-port 2 12huawei(config)#stacking label service-port 3 11huawei(config)#stacking label service-port 4 12

NOTEIn the actual configuration, the index of the traffic stream may vary according to the number of traffic streamsin the system. You only need to ensure that the actual index corresponds to the inner VLAN tag.


----End

Resultl After being authenticated by the ISP 1 BRAS, users 1 and 2 can obtain the services provided

by ISP 1.l After being authenticated by the ISP 2 BRAS, users 3 and 4 can obtain the services provided

by ISP 2.

Configuration FileThe following describes the configuration file of this configuration example. Note that certainsteps must be performed manually and the configuration file cannot be imported directly.

Create VLANs.



8-43

vlan 100 to 101 smart

Set the VLAN attribute.

vlan attrib 100 to 101 stacking

Add an upstream port to VLANs.

port vlan 100 to 101 0/0 1

Add service ports to VLANs.

service-port 1 vlan 100 eth 0/4/1 multi-service user-encap pppoe rx-cttr 6tx-cttr 6service-port 2 vlan 100 eth 0/4/2 multi-service user-encap pppoe rx-cttr 6tx-cttr 6service-port 3 vlan 101 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6tx-cttr 6service-port 4 vlan 101 eth 0/4/4 multi-service user-encap pppoe rx-cttr 6tx-cttr 6

Set inner VLAN tag.

stacking label service-port 1 11stacking label service-port 2 12stacking label service-port 3 11stacking label service-port 4 12

8.4.2 Configuration Example of the VLAN ID Extension ServiceThis topic describes how to configure the VLAN ID extension for increasing the number of usersthat can be identified according to the VLAN ID by the BRAS.

Prerequisitel Network devices and lines must be in the normal state.l The authentication data of the access user must be configured on the BRAS.l The control board and the involved service boards must be in the normal state.

Service Requirementsl The Internet access service is deployed on the network.l Two VLAN IDs are allocated on the BRAS to identify four access users.

NetworkingFigure 8-11 shows an example network for configuring the VLAN ID extension.

Broadband users through multiple MA5612s are authenticated on a BRAS to obtain thebroadband service provided by the carrier. The BRAS supports the user identification throughL2 VLAN. The outer VLAN tag identifies the MA5612 that accesses users, and the inner VLANtag identifies the users of the device.


Configuration Guide


Issue 04 (2011-04-27)

Figure 8-11 Example network for configuring the VLAN ID extension

BRAS

User 1 User 2 User 3 User 4

VLAN 100 VLAN 101

OLT

LSW

MA5612_A MA5612_B

Data Plan

Table 8-9 provides the data plan for configuring the VLAN ID extension.

Table 8-9 Data plan for configuring the VLAN ID extension

Item Data

MA5612_A

Upstream port: 0/0/0

Upstream VLAN ID (outer VLAN tag): 100VLAN attribute: Stacking VLAN



MA5612_B


Upstream VLAN ID (outer VLAN tag): 101VLAN attribute: Stacking VLAN



8-45

Item Data



Procedurel The procedure for configuring the VLAN ID extension on MA5612_A is as follows:

1. Create a VLAN.huawei(config)#vlan 100 smart

2. Set the VLAN attribute to stacking VLAN.huawei(config)#vlan attrib 100 stacking

3. Add an upstream port to the VLAN.huawei(config)#port vlan 100 0/0 0

4. Add service ports to the VLAN.huawei(config)#service-port vlan 100 eth 0/4/2 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6huawei(config)#service-port vlan 100 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6 tx-cttr 6

5. Set the inner VLAN tag.huawei(config)#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 eth 0/4 /2 - - encap pppoe 6 6 up 1 100 stacking eth 0/4 /3 - - encap pppoe 6 6 up ------------------------------------------------------------------------- Total : 2 (Up/Down : 2/0)huawei(config)#stacking label service-port 0 11huawei(config)#stacking label service-port 1 12

NOTEIn the actual configuration, the index of the traffic stream may vary according to the number of trafficstreams in the system. You only need to ensure that the actual index corresponds to the inner VLANtag.

6. Save the data.huawei(config)#save

l The procedure for configuring the VLAN ID extension on MA5612_B is as follows:


Configuration Guide


Issue 04 (2011-04-27)

The configuration procedure of MA5612_B is the same as the configuration procedure ofMA5612_A. The only difference lies in the upstream VLAN ID. Hence, it is not describedhere.

----End

ResultAfter being authenticated by the BRAS, the users on MA5612_A and MA5612_B can accessthe Internet.

Two users of the MA5612 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 FileConfiguration file of MA5612_A

Create a VLAN.

vlan 100 smart

Set the VLAN attribute to stacking VLAN.

vlan attrib 100 stacking


port vlan 100 0/0 0


service-port 0 vlan 100 eth 0/4/2 multi-service user-encap pppoe rx-cttr 6tx-cttr 6service-port 1 vlan 100 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6tx-cttr 6

Set the inner VLAN tag.

stacking label service-port 0 11stacking label service-port 1 12

Configuration file of MA5612_B

Create a VLAN.

vlan 101 smart

Set the VLAN attribute to stacking VLAN.

vlan attrib 101 stacking


port vlan 101 0/0 0


service-port 0 vlan 101 eth 0/4/2 multi-service user-encap pppoe rx-cttr 6tx-cttr 6service-port 1 vlan 101 eth 0/4/3 multi-service user-encap pppoe rx-cttr 6tx-cttr 6



8-47

Set the inner VLAN tag.

stacking label service-port 0 11stacking label service-port 1 12


Configuration Guide


Issue 04 (2011-04-27)

9 Configuration Examples of the FTTx

About This Chapter

The FTTx solution configuration guide describes how to configure typical FTTH, FTTB/C,FTTO, and FTTM services (such as high-speed Internet access, multicast, VoIP, and mobilebackhaul services) on the OLT and the ONU step by step through examples.

9.1 FTTx Network and ProductFTTx applications include FTTH, FTTB, FTTC, FTTO, FTTM, and VIP P2P access.

9.2 FTTx Data Plan (GPON Access)This topic plans the data in a unified manner for connecting to the OLT in the FTTx GPONaccess mode for various example networks. The subsequent examples are configured based onthe following data plan.

9.3 Configuring the FTTB and FTTC Access ServicesThis topic describes how to configure the Internet access, voice and multicast in the FTTB andFTTC Access Services.

9.4 Configuring the FTTO ServiceThrough the "OLT+SBU" network, the fiber to the office (FTTO) solution is provided forenterprise users. This topic describes how to configure the TDM PBX access, IP PBX access,enterprise router access services, and enterprise POTS access services in the FTTO scenario.

9.5 Configuring the FTTM ServiceIn the FTTM network, the ONU, functioning as a cell backhaul unit (CBU), is connected to the2G or 3G base station in various modes. The OLT connects the MA5612/MA5628 to the basestation controller (BSC) or radio network controller (RNC), and transmits signals to the upper-layer network. In this way, the ONU implements the FTTM network application over the 2G or3G network.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 9 Configuration Examples of the FTTx


9-1

9.1 FTTx Network and ProductFTTx applications include FTTH, FTTB, FTTC, FTTO, FTTM, and VIP P2P access.

NetworkFigure 9-1 shows an example network of full access services in the FTTx scenario. FTTxapplications include FTTH, FTTB, FTTC, FTTO, FTTM, and VIP P2P access.

l FTTH indicates fiber to the home. The ONT is connected to the OLT in the PON mode toimplement FTTH. The voice, data, and video services are provided through a single opticalfiber.

l FTTB/FTTC indicates fiber to the building/fiber to the curb. The MDU is connected to theOLT in the PON mode or GE mode to implement FTTB/FTTC, and provides voice, data,and video services for the users in communities.

l FTTO indicates fiber to the office. The SBU is connected to the OLT in the PON mode toimplement FTTO. In this way, the Intranet TDM PBX, Intranet IP PBX, and Intranet privateline services are provided.

l FTTM indicates fiber to the mobile base station. The CBU is connected to the OLT in thePON mode to implement base station backhaul.

l P2P indicates point to point. The VIP household and enterprise users can be directlyconnected to the OLT through GE optical fibers to implement end-to-end QoS.

Figure 9-1 Example network of full access services in the FTTx scenario

9 Configuration Examples of the FTTxSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

Configuration ProductsTable 9-1 lists the configuration products for the FTTx solution.

Table 9-1 Configuration products for the FTTx solution

NetworkPositioning

Configuration Product Version Description

OLT MA5600T and MA5603T V800R008C01/C02

Supports functioning as anOLT in the FTTH, FTTB,FTTC, FTTM, or FTTOnetwork.

MDU MA5620, MA5626,MA5612, MA5652G

V800R308C00

Supports functioning as anMDU in the FTTB or FTTCnetwork.

MA5616, MA5628 V800R308C01

CBU MA5612 V800R308C00/C01

Supports functioning as aCBU in the FTTM network.

SBU MA5612 V800R308C00/C01

Supports functioning as anSBU in the FTTO network.

ONT HG series V100R001/V100R002

Supports functioning as anONT in the FTTH network.

9.2 FTTx Data Plan (GPON Access)This topic plans the data in a unified manner for connecting to the OLT in the FTTx GPONaccess mode for various example networks. The subsequent examples are configured based onthe following data plan.

Data PlanTable 9-2 provides the unified data plan for configuring the HSI, IPTV, VoIP, emulationservices, and private line services in an FTTx network.

NOTE

The ONU in the data plan refers to the ONT and the MDU collectively.



9-3

Table 9-2 Data plan for the FTTx GPON access

ServiceClassification

Item Data Remarks

Network data

FTTH OLT PON port:0/1/1ONT ID: 1-2

In the current network, FTTH, FTTB, andFTTC can be implemented on the sameOLT. Generally, different slots are used forthe implementation. Implementing variousFTTx networks concurrently, however, isnot recommended in general.

FTTB/C OLT PON port:0/2/1ONT ID: 1-2

FTTO/M OLT PON port:0/3/1ONT ID: 1

P2P FE ports of theOPFA board on theOLT:l 0/5/1l 0/5/2l 0/5/3

Devicemanagement

Inband NMSIP address ofthe OLT

192.168.50.1/24 To configure the MDU from the OLT bylogging in to the MDU through Telnet, themanagement VLAN of the OLT and that ofthe MDU must be the same, and themanagement IP address of the OLT and thatof the MDU must be in the same networksegment.In the GPON access, the networkmanagement protocol of the MDU adoptsSNMP and that of the ONT adopts OMCI.

ManagementVLAN of theOLT

8

Inband NMSIP address ofthe MDU

ONU 1:192.168.50.2/24ONU 2:192.168.50.3/24

ManagementVLAN of theMDU

8


Configuration Guide


Issue 04 (2011-04-27)


Item Data Remarks

ServiceVLAN

HSI service ONU upstreamVLAN: 1001-1024OLT VLANs:l CVLAN:

CVALN ID =256 x GPON portID + 256 xoptical ratio x(optical splitterport ID - 1) +ONU port ID + 1

l SVLAN: 100(stackingVLAN)

For the Internet access service, you can usetwo precisely-bound VLAN tags to extendVLANs and identify users. On the OLT,each OLT, each slot of the OLT, or eachPON port is allocated with an SVLAN.Each user is allocated with a CVLAN.CVLANs of the same OLT are planned ina unified manner and each VLAN ID isunique. The recommended allocation ruleis as follows:CVLAN ID = 256 x GPON port ID + 256x optical ratio x (optical splitter port ID - 1)+ ONU port ID + 1Upstream VLANs for ONUs of the sametype are recommended to be the same. Thisprevents configuration differences ofdifferent ONUs. This makes configurationand maintenance easier.

IPTV service Multicast VLAN:1000

Generally, multicast VLANs are dividedaccording to multicast sources.

VoIP service ONU VLAN: 200OLT VLAN (VLANtransparentlytransmitting theONU service): 200

Generally, the VoIP service can beidentified by a single VLAN tag.Each OLT, each slot of the OLT, or eachPON port can be allocated with a VLAN toreduce VLAN broadcast domains.

Emulationservice

TDM emulationSVLAN: 500ATM emulationSVLAN: 700ETH emulationSVLAN: 800

They are the SVLANs of the OLT thattransparently transmit the ONU service.

QinQ privateline service

ONU SVLAN: 2000OLT VLAN (VLANtransparentlytransmitting theONU service): 2000

QinQ is used to implement the Layer 2 VPNprivate line service. In the case of FTTH,enable QinQ on the OLT; in the case ofFTTB/FTTC, enable QinQ on the ONU.Each slot of the OLT can be allocated withan SVLAN to reduce VLAN broadcastdomains.

QoS(priority andqueue

HSI service Priority: 1; queuescheduling: WRR

Generally, the QoS priorities are NMSservice and IP voice service > private lineservice > IPTV service > Internet accessservice in a descending order.



9-5


Item Data Remarks

scheduling)

IPTV service Priority: 4; queuescheduling: WRR

The queue scheduling mode is configuredglobally. Queues with higher prioritiesadopt PQ mode and queues with lowerpriorites adopt WRR mode.In FTTH networks, service priorities are seton the OLT. In other FTTx networks,service priorities are set on ONUs and theOLT transparently transmits the priorities.

VoIP service Priority: 6; queuescheduling: PQ

Emulationservice

Priority: 6; queuescheduling: PQ


Priority: 5; queuescheduling: PQ

QoS(DBA)

HSI service l Profile name:PPPOE

l Profile type:Type4

l Maximumbandwidth(FTTH): 20Mbit/s

l Maximumbandwidth(FTTB/C): 100Mbit/s

l T-CONT ID: 4

DBA is used to control the upstreambandwidth of the ONU. DBA profiles arebound to TCONTs. Different TCONTs areplanned for different bandwidth assurancetypes.Generally, the service with a high priorityadopts a fixed bandwidth or an assuredbandwidth, and the service with a lowpriority adopts the maximum bandwidth orbest effort.

IPTV service l Profile name:IPTV


l Maximumbandwidth(FTTH): 1 Mbit/s


l T-CONT ID: 3


Configuration Guide


Issue 04 (2011-04-27)


Item Data Remarks

VoIP service l Profile name:VOIP


l Assuredbandwidth(FTTH): 0.1Mbit/s

l Maximumbandwidth(FTTH): 1 Mbit/s

l Assuredbandwidth(FTTB/C): 15Mbit/s


l T-CONT ID: 2

Emulationservice

l Profile name:– For TDM

emulation:TDM

– For ADMemulation:ATM

– For ETHemulation:ETH


l Fixed bandwidth32 Mbit/s

l T-CONT ID: 1



9-7


Item Data Remarks


l Profile name:PrivateLine


l Assuredbandwidth: 20Mbit/s

l Maximumbandwidth: 50Mbit/s

l T-CONT ID: 5

QoS(CAR)

Emulationservice

No rate limitation inthe upstream anddownstreamdirections

Traffic control can be implemented on theBRAS, or on the OLT or ONU by using portrate limitation or using a traffic profile tolimit the upstream and downstream traffic.Generally, in the case of FTTH, limit therate on the OLT; in the case of FTTB/FTTC, limit the rate on the ONU.

VoIP service No rate limitation inthe upstream anddownstreamdirections

IPTV service No rate limitation inthe upstream anddownstreamdirections

HSI service Upstream anddownstreambandwidth: 4 Mbit/s

IPTVservicedata

Multicastprotocol

OLT: IGMP proxyONU: IGMPsnooping

-

Multicastversion

IGMP V3 IGMP v3 and IGMP v2 are supported, andIGMP v3 is compatible with IGMP v2.

Multicastprogramconfiguration mode

Static configurationmode

The OLT can also generate a multicastprogram library, that is, dynamicallygenerate a program list according to theprograms requested by users. In this mode,the program list need not be configured ormaintained; however, the functions such asprogram management, user multicastbandwidth management, program preview,and program prejoin are not supported.


Configuration Guide


Issue 04 (2011-04-27)


Item Data Remarks

IP address ofthe multicastserver

10.10.10.10 -

Multicastprogram

224.1.1.10 -

VoIPservicedata

Signalingand media IPaddresses

17.10.10.10/24 H.248 and SIP support separate media andsignaling. The media and signaling IPaddress can be the same or different.

Gateway IPaddress

17.10.10.1/24 -

MGinterface (H.248)NOTE

Theparametersof the MGinterfacemust be thesame as theparameterson the MGC.H.248 hasmanynegotiationparameters,and theparametershere aremandatory.

MG interface ID: 0 It is the MG interface ID used for the VoIPservice to be configured, which determinesthe virtual access gateway (VAG) specifiedfor the user.

Signaling port ID ofthe MG interface:2944

It is the transport layer protocol port IDused for the signaling exchange betweenthe MG and the MGC.

IP address of theprimary MGC towhich the MGinterface belongs:200.200.200.200/24

When dual homing is configured, the IPaddress and the port ID of the secondaryMGC must also be configured.

Port ID of theprimary MGC towhich the MGinterface belongs:2944

Coding mode of theMG interface: text

-

Transmission modeof the MG interface:UDP

The transmission mode of the MG interfaceis selected according to the requirements onthe MGC. Generally, UDP is adopted.

SIP interface(SIP)

SIP interface ID: 0 It is the SIP interface ID used for the VoIPservice to be configured, which determinesthe virtual access gateway (VAG) specifiedfor the user.

Signaling port ID ofthe SIP interface:5056

-



9-9


Item Data Remarks

NOTETheparametersof the SIPinterfacemust be thesame as theparameterson thesoftswitch.SIP hasmanynegotiationparameters,and theparametershere aremandatory.

IP address of theprimary softswitchto which the SIPinterface belongs:200.200.200.200/24

When dual homing is configured, the IPaddress and the port ID of the secondarysoftswitch must also be configured.

Port ID of theprimary softswitchto which the SIPinterface belongs:5060/24

Coding mode of theSIP interface: text

-

Transmission modeof the SIP interface:UDP

The transmission mode is selectedaccording to the requirements on thesoftswitch. Generally, UDP is adopted.

Home domain of theSIP interface:huawei

-

Index of the profileused by the SIPinterface: 1

Different profile indexes are used forinterconnection with non-Huaweisoftswitches. You can run the if-h248attribute profile-index command to querythe profile index. For interconnection witha ZTE softswitch, use profile 5; forinterconnection with a Bell softswitch, noconstant profile is used. Profile 0 can beused and the data is negotiated with the Bellsoftswitch.

PSTN users phone1-phone24:83110001-83110024

-

User priorities:Phone 1: Cat2;Phone 2-Phone 24:Cat3 (default)

According to the service requirements, userpriorities must be specified. The userpriorities include the following:l cat1: government1 (category 1


government users)l cat3: common (common users)

Emulation

Local LSRID

10.10.10.10/32 Generally, the IP address of the loopbackinterface is used as the LSR ID.


Configuration Guide


Issue 04 (2011-04-27)


Item Data Remarks

servicedata

Remote(OLT) LSRID

10.20.20.20/32

Remote(PTN) LSRID

30.30.30.30/32

9.3 Configuring the FTTB and FTTC Access ServicesThis topic describes how to configure the Internet access, voice and multicast in the FTTB andFTTC Access Services.

ContextIn the FTTB and FTTC Access Services, the user can access to the ONU by LAN or xDSL. TheONU is connected to the MA5600T/MA5603T through an GPON port to provide users with thehigh-speed Internet access service, VoIP service and IPTV service.

Figure 9-2 Example network of the multiple service in FTTB and FTTC service

9.3.1 Configuring the FTTB and FTTC Internet Access Services (LAN Access)The MA5600T/MA5603T is connected to a remote ONU that supports LAN access by using aGPON port to provide users with the high-speed Internet access service.

9.3.2 Configuring the FTTB and FTTC VoIP Services (Based on the H.248 Protocol)The MA5600T/MA5603T is connected to a remote ONU that supports H.248 by using the GPONport to provide users with the VoIP service.



9-11

9.3.3 Configuring the FTTB and FTTC VoIP Services (Based on the SIP Protocol)The MA5600T/MA5603T is connected to a remote ONU that supports SIP by using the GPONport to provide users with the VoIP service.

9.3.4 Configuring the FTTB and FTTC IPTV Multicast ServicesThe MA5600T/MA5603T is connected to a remote ONU through the GPON port to provideusers with the high-speed Internet access service. This topic considers the MA5620 as anexample, and uses the GPBC board on the OLT.

9.3.1 Configuring the FTTB and FTTC Internet Access Services(LAN Access)

The MA5600T/MA5603T is connected to a remote ONU that supports LAN access by using aGPON port to provide users with the high-speed Internet access service.

Service Requirementsl VLANs are divided are isolated different user groups, preventing broadcast storms and

facilitating O&M.l Users perform PPPoE dialup on PCs to implement high-speed Internet access.l Two VLAN tags are used to precisely identify services and users.l The same QoS is used for the same type of services on the same type of ONUs, facilitating

management.

Prerequisitel The example network as shown in Figure 9-2 is complete.l Corresponding MA5620 version: V800R308. If another version is used, the configuration

differs slightly. For details, see the configuration guide of the corresponding ONU version.

Background Informationl ONUs that support LAN access include MA5620, MA5626, MA5610, MA5616, and

MA5612.l Boards that support GPON access on the OLT include the GPBC and GPBD.l This example uses MA5620 as the ONU and GPBD as the GPON access board.

Procedurel Configure the OLT.

1. Create an SVLAN and configure its upstream port.

On the OLT, each OLT, each slot of the OLT, or each PON port can be allocated withan SVLAN. In this example, an SVLAN is allocated to each slot. To precisely identifya user, stacking VLANs are used. This means to translate CVLANs on the OLTaccording to the planned VLAN IDs.

Configure the SVLAN ID to 100, VLAN type to smart VLAN, and VLAN attributeto stacking. Add upstream port 0/19/0 to VLAN 100.

huawei(config)#vlan 100 smarthuawei(config)#vlan attrib 100 stackinghuawei(config)#port vlan 100 0/19 0


Configuration Guide


Issue 04 (2011-04-27)

2. (Optional) Configure upstream link aggregation.In this example, a single upstream port is used. In the case of multiple upstream ports,upstream link aggregation can be configured to implement protection between portsand load sharing. For details, see Configuring Upstream Link Aggregation.

3. Configure GPON ONU profiles.

GPON ONU profiles include the DBA profile, line profile,and alarm profile.– DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT

is bound to a DBA profile for dynamic bandwidth allocation, improving theupstream bandwidth usage rate.

– Line profile: A line profile describes the binding between the T-CONT and theDBA profile, the QoS mode of the traffic stream, and the mapping between theGEM port and the ONU-side service.

– Alarm profile: An alarm profile contains a series of alarm thresholds to measureand monitor the performance of activated ONU lines. When a statistical valuereaches the threshold, the host is notified and an alarm is reported to the log hostand the NMS.

(1) Configure a DBA profile.You can run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to PPPoE, type to Type4, and maximumbandwidth to 100 Mbit/s.huawei(config)#dba-profile add profile-name PPPoE type4 max 102400

(2) Configure an ONU line profile.Create GPON ONU line profile 10 and bind T-CONT 4 to DBA profile PPPoE.In this way, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 4 dba-profile-name PPPoE

NOTE

The ID of the line profile to be created must not exist in the system. Please create proper ONUline profiles according to actual data plan. In this example, line profile 10 is used.

Add GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting Internet traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 4. Set the QoS mode to priority-queue (default).huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 4huawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 4



9-13

NOTE

a. To change the QoS mode, run the qos-mode command to configure the QoS mode to gem-car or flow-car, and run the gem add command to configure the ID of the traffic profilebound to the GEM port.

b. For the ONU V800R308, the QoS mode cannot be set to gem-car or flow-car. Toimplement QoS in the upstream and downstream directions, other modes are adopted. Forexample, bind a T-CONT to a DBA profile or bind a traffic profile when creating trafficstreams.

c. When the QoS mode is PQ, the default queue priority is 0; when the QoS is gem-car orflow-car, traffic profile 6 is bound to the port by default (no rate limitation).

d. Before running the multi-service-port command to create service ports in batches, ensurethat the number of GEM ports is the same as the number of CVLANs. Therefore, you mustcreate GEM ports according to the number of CVLANs. If there are 24 CVLANs,, 24GEM ports need to be created.

e. If you run the service-port command to create service ports one by one, note that oneGEM port can be bound to up to eight service ports. Create sufficient GEM ports accordingto the number of service ports. If there are 24 CVLANs, at least three GEM ports need tobe created. This example adopts this mode and only one GEM port is created. For differentservice ports within the same GEM port, you only need to replace the mapping-index andreplace the mapped VLAN with the CVLAN.

Configure the mapping between the GEM port and the ONU-side service to theVLAN mapping mode (default), map the service port of management serviceport ( the CVLAN ID is 8) to GEM port 0, and map the Internet service port (theCVLAN ID is 1001) to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 1001After the configuration is complete, run the commit command to make theconfigured parameters take effect.huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

(3) (Optional) Configure an alarm profile.– The ID of the default GPON alarm profile is 1. The thresholds of all the alarm

parameters in the default alarm profile are 0, which indicates that no alarm isgenerated.

– In this example, the default alarm profile is used, and therefore theconfiguration of the alarm profile is not required.

– Run the gpon alarm-profile add command to configure an alarm profile,which is used for monitoring the performance of an activated ONU line.

4. Add an ONU on the OLT.

(1) Add an ONU.ONU 1 and ONU 2 are connected to GPON port 0/2/1 through an optical splitter.The IDs of ONU 1 and ONU 2 are 1 and 2 respectively. The SN of ONU 1 is32303131B39FD641 and that of ONU 2 is 32303131B39FD642. Themanagement mode is SNMP and the line profile 10 is bound.There are two ways to add an ONU. Select either of the two ways according toactual conditions.– Add an ONU offline: If the password or SN of an ONU is obtained, you can

run the ont add command to add the ONU offline.– Automatically find an ONU: If the password or SN of an ONU is unknown,

run the port ont-auto-find command in the GPON mode to enable the ONU


Configuration Guide


Issue 04 (2011-04-27)

auto-find function of the GPON port. Then, run the ont confirm commandto confirm the ONU.

To add an ONU offline, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#ont add 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10huawei(config-if-gpon-0/2)#ont add 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10

To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/2)#display ont autofind 1 //LAN access ONU is used as an example. The system displayed slightly differs according to the ONU version for xDSL access. ------------------------------------------------------------------------ Number : 1 F/S/P : 0/2/1 Ont SN : 32303131B39FD641 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------ Number : 2 F/S/P : 0/2/1 Ont SN : 32303131B39FD642 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access

Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------huawei(config-if-gpon-0/2)#ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10huawei(config-if-gpon-0/2)#ont confirm 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10

(2) (Optional) Bind an alarm profile to the ONU.After an alarm profile is configured, bind it to the ONT. In this example, bindthe default alarm profile, namely alarm profile 1 to the ONU.huawei(config-if-gpon-0/2)#ont alarm-profile 1 1 profile-id 1huawei(config-if-gpon-0/2)#ont alarm-profile 1 2 profile-id 1

5. Confirm that the ONU goes online normally.

NOTE

In this step, query the status of ONU 1 as an example. The same method is applied for querying thestatus of ONU 2.



9-15

After an ONU is added, run the display ont info command to query the current statusof the ONU. Ensure that Control flag of the ONU is active, Run State is online,Config state is normal, and Match state is match.

huawei(config-if-gpon-0/2)#display ont info 1 1 --------------------------------------------------------------------- F/S/P : 0/2/1 ONT-ID : 0 Control flag : active //Indicates that the ONU is activated. Run state : online //Indicates that the ONU already goes online normally. Config state : normal //Indicates that the configuration status of the ONU is normal. Match state : match //Indicates that the capability profile bound to the ONU is consistent with the actual capability of the ONU....//The rest of the response information is omitted.

If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match,refer to the following suggestions to rectify the fault.– If Control flag is deactive, run the ont activate command in the GPON port mode

to activate the ONU.– If the ONU fails to be in the up state, that is, Run state is offline, the physical line

may be broken or the optical transceiver may be damaged. You need to check boththe material and the line.

– If the ONU state fails, that is, Config state is failed, the ONU capability setoutmatches the actual ONU capabilities. In this case, run the display ont failed-configuration command in the diagnosis mode to check the failed configurationitem and the failure cause. Then, rectify the fault according to actual conditions.

NOTEIf an ONT supports only four queues, the values of 4-7 of the priority-queue parameter in thegem add command are invalid. After configuration recovers, Config state will be failed.

– If the ONU does not match, that is, Match state is mismatch, the port types andnumber of ports undermatch the actual port types and number of ports supportedby the ONU. In this case, run the display ont capability command to query theactual capability of the ONU, and then select one of the following modes to modifythe 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 theONU.

– Modify the ONU profile according to the actual capability of the ONU and savethe modification. Then, the ONU automatically recovers the configurationsuccessfully.

6. Configure the management channel from the OLT to the ONU.

(1) Configure the inband management VLAN and IP address of the OLT.To telnet to the ONU from the OLT and then configure the ONU, you need toconfigure the inband management VLANs and IP addresses of the OLT and theONU on the OLT.Create management VLAN 8, add the upstream port to VLAN 8, and configurethe inband management IP address to 192.168.50.1/24.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

(2) Configure the inband management VLAN and IP address of the ONU.

Configure the static IP address of the ONU 1 to 192.168.50.2/24, the static IPaddress of the ONU 2 to 192.168.50.3/24 , the gateway to 192.168.50.254 andthe management VLAN ID to 8 (the same as that 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 8huawei(config-if-gpon-0/2)#ont ipconfig 1 2 static ip-address 192.168.50.3 mask 255.255.255.0 gateway 192.168.50.254 vlan 8huawei(config-if-gpon-0/2)#quit

(3) Configure an inband management service port.

Configure the management service port index to 0, management VLAN ID to 8,GEM port ID to 0, and CVLAN ID to 8. On the OLT, the rate of the inbandservice port is not limited. Therefore, use default traffic profile 6. To limit therate of a service port, run the traffic table ip command to create a traffic profileand then bind the profile to the service port.huawei(config)#service-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6huawei(config)#service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6

7. Confirm that the management channel between the OLT and the ONU is available.

– On the OLT, run the ping 192.168.50.2 and ping 192.168.50.3 command to checkthe connectivity to the ONU 1 and ONU 2. The ICMP ECHO-REPLY packet fromthe ONU should be received.

– You can run the telnet 192.168.50.2 and telnet 192.168.50.3 command to telnetto the ONU 1 and ONU 2 and then configure the ONU.

8. Create service ports.

Create service port 101 connected to ONU 1 and service port 102 connected to ONU2. Set the SVLAN ID to 100, GEM port ID to 1, and CVLAN ID to 1001. The trafficrate of upstream and downstream packets is limited on the ONU and not limited onthe OLT. Therefore, use default traffic profile 6. To limit the rate of a service port,run the traffic table ip command to create a traffic profile and then bind the profileto the service port.

Assume the split ratio is 1:128. ONU 1 is connected to port 1 on the optical splitterby using optical fiber and ONU 2 is connected to port 2. The user PC is connected toONU port 1. The inner VLAN IDs are 258 and 260 after they are calculated accordingto the formula.

huawei(config)#service-port 101 vlan 100 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6 tx-cttr 6huawei(config)#service-port 102 vlan 100 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 1001 tag-transform translate-and-add inner-vlan 260 rx-cttr 6 tx-cttr 6



9-17

NOTE

l The OLT's CVLAN must be the same as the upstream VLAN of the ONU.

l Run the service-port to create service ports one by one. In this example, only one service portis created as an example. When a service port is created, note that it must correspond to the GEMport configured with the ONU line-profile and the CVLAN.

l You can also run the multi-service-port command to create service ports in batches. In the caseof GPON access, you must set ontid+gemindex to specify a service port. In addition, the numberof GEM ports must be the same as the number of CVLANs.

9. Configure the queue scheduling mode.

Adopt the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode and theirweights are 10, 10, 20, 20, and 40 respectively. Queues 5-7 adopt the PQ mode. Thepriority of the Internet access service is 1, adopting the WRR mode.

NOTE

l The queue scheduling mode is configured globally, and you need to configure it only once onthe OLT. After the configuration is complete, the queue scheduling mode takes effect globally.When subsequent services are configured, you do not need to configure the queue schedulingmode again.

l For a board that supports only four queues, the default mapping between the 802.1p prioritiesand queue IDs are as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue 2;priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.

huawei(config)#queue-scheduler wrr 10 10 20 20 40 0 0 0

Configure the mapping between the queues and 802.1p priorities. Priorities 0-7 mapqueues 0-7 respectively.

huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7


l Configure the ONU.

NOTE

The configuration on ONU 1 and ONU 2 is the same. Take configuration on ONU 1 for example.

1. Log in to the ONU to perform the configuration.On the OLT, use the management IP address of the ONU to log in to the ONU throughTelnet. User name: root (default). Password: mduadmin (default).huawei(config)#telnet 192.168.50.2{ <cr>|service-port<0,4294967295> }:

Command: telnet 192.168.50.2 Press CTRL_] to quit telnet mode Trying 192.168.50.2 ... Connected to 192.168.50.2 ...>>User name:root>>User password:

2. Configure the traffic profile.

You can run the display traffic table ip command to query the traffic profiles existingin 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 CIR to 4 Mbit/s. The priority for upstream packetsis 1. The downstream priority policy is scheduled by the priority that the packets bear.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#traffic table ip index 8 cir 4096 priority 1 priority-policy tag-In-Package

3. Create an SVLAN.Create SVLANs 1001–1024 in batches whose type is smart and attribute is common.Add SVLANs to upstream port 0/0/1.

NOTE

The VLAN ID must be consistent with the CVLAN of the OLT.huawei(config)#vlan 1001-1024 smarthuawei(config)#port vlan 1001-1024 0/0 1

4. Add a service port.Create service port 101, bind port 0/1/1 to it, and configure the C-VLAN to be 1001.

NOTE

In this step, you need to create 24 service ports in batches. The following considers the creation ofone service port as an example. For the rest, replace the SVLANs, and corresponding ports.huawei(config)#service-port 101 vlan 1001 eth 0/1/1 multi-service user-encap untagged rx-cttr 8 tx-cttr 8


----End

ResultUsers can enjoy the high-speed Internet service with PC by PPPoE.

After configuration is complete, use PCs to perform PPPoE. If the system displays “Error 678”,troubleshoot the fault as follows:

1. Perform PPPoE dialup on a PC. On the ONU, run the display mac-address all commandto check whether there is a MAC address of the PC. If there is a MAC address of the PC,the PC is connected properly to the ONU. Proceed to 2. If there is not such a MAC address,check whether the ONU is configured properly as follows:

(1) Check the SVLAN of the service port created by running the service-port commandand check whether the port connected to the PC is properly configured. Ensure thatuser-vlan is set to untagged.

2. On the MA5600T/MA5603T, run the display mac-address all command to check whetherthere is a MAC address of the ONU connected to the PC. If there is such a MAC address,capture packets and mirror packets on the upper-layer switch to locate faults. If there is notsuch a MAC address, check whether the MA5600T/MA5603T is configured properly.l Check whether ONUs connected to the MA5600T/MA5603T have conflict MAC

addresses. If there are conflict MAC addresses, change the conflict MAC addresses.l Check the SVLAN of the service port created by running the service-port command

and check whether the port connected to the PC is properly configured. Ensure thatuser-vlan is consistent with ONU's upstream VLAN configuration.

Configuration FileOn the OLT side.vlan 100 smartvlan attrib 100 satcking



9-19

port vlan 100 0/19 0dba-profile add profile-name PPPOE type4 max 102400ont-lineprofile gpon profile-id 10tcont 4 dba-profile-name PPPOEgem add 0 eth tcont 4gem add 1 eth tcont 4mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 1001commitquitinterface gpon 0/2port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10ont confirm 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10ont alarm-profile 1 1 profile-id 1ont alarm-profile 1 2 profile-id 1vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitinterface gpon 0/2ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 gateway192.168.50.254 vlan 8ont ipconfig 1 2 static ip-address 192.168.50.3 mask 255.255.255.0 gateway192.168.50.254 vlan 8service-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 101 vlan 100 gpon 0/2/1 ont 1 gemport 1 multi-service user-vlan 1001 tag-transform translate-and-add inner-vlan 258 rx-cttr 6 tx-cttr 6service-port 102 vlan 100 gpon 0/2/1 ont 2 gemport 1 multi-service user-vlan 1001 tag-transform translate-and-add inner-vlan 260 rx-cttr 6 tx-cttr 6queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

On the ONU side.

traffic table ip index 8 cir 4096 priority 1 priority-policy tag-In-Packagvlan 1001-1024 smartport vlan 1001-1024 0/0 1service-port 101 vlan 1001 eth 0/1/1 multi-service user-vlan untagged rx-cttr 8 tx-cttr 8save

9.3.2 Configuring the FTTB and FTTC VoIP Services (Based on theH.248 Protocol)

The MA5600T/MA5603T is connected to a remote ONU that supports H.248 by using the GPONport to provide users with the VoIP service.

Service Requirementsl Users directly uses the existing phone sets for the voice service and no additional investment

is required.l The voice data is carried over the IP network, which reduces the communication costs to

a great extent without compromising the communication quality.l Compared with traditional PSTN networks, IP-based networks provide more powerful

service functions and richer user experience.


Configuration Guide


Issue 04 (2011-04-27)

l The polarity-reversal accounting is supported.

Prerequisitel The MGC interface data and the PSTN user data corresponding to the MG interface must

be configured on the MGC.l Run the display board 0 command to make sure the Status of the voice board of ONU is

Normal.

Background InformationONUs that support SIP include the MA5620, MA5612, MA5616, MA5606T, and MA5603T.

An ONU support either H.248 or SIP. To query the current voice protocol on an ONU, run thedisplay protocol support command. To change the voice protocol to the other one, delete theMG interface and run the protocol support command. After the configuration is complete, saveit and restart the system to make the configuration take effect.

WARNINGThis operation interrupts the ongoing services carried on the currently used MG interface. Hence,exercise caution when performing this operation.


1. Create an SVLAN and add an upstream port to it.

Create smart VLAN 200 and add upstream port 0/19/0 to it.

huawei(config)#vlan 200 smarthuawei(config)#port vlan 200 0/19 0







(1) Configure a DBA profile.



9-21

You can run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to VoIP, type to Type4, assure bandwidth to15 Mbit/s and maximum bandwidth to 30 Mbit/s.huawei(config)#dba-profile add profile-name VoIP type3 assure 15360 max 30720

(2) Configure an ONU line profile.Create GPON ONU line profile 10 and bind T-CONT 2 to DBA profile VoIP.In this way, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.

NOTE

The ID of the line profile to be created must not exist in the system. Please create proper lineprofiles according to actual data plan. In this example, line profile 10 is used.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 2 dba-profile-name VoIP

Add GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting VoIP service streams. Bind GEM port 0 and GEM port 1 to T-CONT 2. Set the QoS mode to priority-queue (default).huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 2huawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 2

NOTE



c. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car,traffic profile 6 is bound to the port by default (no rate limitation); when the QoS mode isgem-car, traffic profile 6 is bound to the port by default (no rate limitation).

d. Before running the multi-service-port command to create service ports in batches, ensurethat the number of GEM ports is the same as the number of CVLANs. Therefore, you mustcreate GEM ports according to the number of CVLANs. In this example, 24 GEM portsneed to be created.

e. If you run the service-port command to create service ports one by one, note that oneGEM port can be bound to up to eight service ports. Create sufficient GEM ports accordingto the number of service ports. In this example, three GEM ports need to be created. Thisexample adopts this mode and only one GEM port is created. For different service portswithin the same GEM port, you only need to replace the mapping-index and replace themapped VLAN with the CVLAN.

Configure the mapping between the GEM port and the ONU-side service to theVLAN mapping mode (default), map the service port of management (theCVLAN ID is 8) to GEM port 0, and map the service port of VoIP service (theCVLAN ID is 200) to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 200

After the configuration is complete, run the commit command to make theconfigured parameters take effect.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

(3) (Optional) Configure an alarm profile.– The ID of the default GPON alarm profile is 1. The thresholds of all the alarm







run the port ont-auto-find command in the GPON mode to enable the ONUauto-find function of the GPON port. Then, run the ont confirm commandto confirm the ONU.


To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/2)#display ont autofind 1 //LAN access ONU is used as an example. The system displayed slightly differs according to the ONU version for xDSL access. ------------------------------------------------------------------------ Number : 1 F/S/P : 0/2/1 Ont SN : 32303131B39FD641 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------ Number : 2



9-23

F/S/P : 0/2/1 Ont SN : 32303131B39FD642 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access




NOTE




If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match,refer to the following suggestions to rectify the fault.

– If Control flag is deactive, run the ont activate command in the GPON port modeto activate the ONU.

– If the ONU fails to be in the up state, that is, Run state is offline, the physical linemay be broken or the optical transceiver may be damaged. You need to check boththe material and the line.

– If the ONU state fails, that is, Config state is failed, the ONU capability setoutmatches the actual ONU capabilities. In this case, run the display ont failed-


Configuration Guide


Issue 04 (2011-04-27)

configuration command in the diagnosis mode to check the failed configurationitem and the failure cause. Then, rectify the fault according to actual conditions.






(1) Configure the inband management VLAN and IP address of the OLT.To telnet to the ONU from the OLT and then configure the ONU, you need toconfigure the inband management VLANs and IP addresses of the OLT and theONU on the OLT.Create management VLAN 8, add the upstream port to VLAN 8, and configurethe inband management IP address to 192.168.50.1/24.huawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

(2) Configure the inband management VLAN and IP address of the ONU.Configure the static IP address of the ONU 1 to 192.168.50.2/24, the static IPaddress of the ONU 2 to 192.168.50.3/24 , the gateway to 192.168.50.254 andthe management VLAN ID to 8 (the same as that 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 8huawei(config-if-gpon-0/2)#ont ipconfig 1 2 static ip-address 192.168.50.3 mask 255.255.255.0 gateway 192.168.50.254 vlan 8huawei(config-if-gpon-0/2)#quit

(3) Configure an inband management service port.Configure the management service port index to 0, management VLAN ID to 8,GEM port ID to 0, and CVLAN ID to 8. On the OLT, the rate of the inbandservice port is not limited. Therefore, use default traffic profile 6. To limit therate of a service port, run the traffic table ip command to create a traffic profileand then bind the profile to the service port.huawei(config)#service-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6huawei(config)#service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6




9-25





Add traffic profile 9, and no rate limitation on user packets. The priority is 6 and thepriority policy is scheduled by the priority that the packets bear.huawei(config)#traffic table ip index 9 cir off priority 6 priority-policy tag-In-Packag

9. Create a service port.

Create service port 200 connected to ONU 1 and service port 201 connected to ONU2. SVLAN ID to 200, GEM port ID to 1, bind traffic profile 9 and CVLAN ID to 200.

NOTEThe CVLAN must be consistent with the upstream VLAN of the ONU.

huawei(config)#service-port 200 vlan 200 gpon 0/2/1 ont 1 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9huawei(config)#service-port 201 vlan 200 gpon 0/2/1 ont 2 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9


Adopt the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode and theirweights are 10, 10, 20, 20, and 40 respectively. Queues 5-7 adopt the PQ mode. Thepriority of the VoIP service is 6, adopting the PQ mode.

NOTE

l The queue scheduling mode is configured globally, and you need to configure it only once onthe OLT. After the configuration is complete, the queue scheduling mode takes effect globally.When subsequent services are configured, you need not configure the queue scheduling modeagain.

l For a board that supports only four queues, the mapping between the 802.1p priorities and queueIDs are as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue 2; priorities 4and 5 map queue 3; priorities 6 and 7 map queue 4.


Configure the mapping between the queues and 802.1p priorities. Priorities 0-7 mapqueues 0-7 respectively.huawei(config)#cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7


l Configure the ONU.NOTE


1. Log in to the ONU to perform the configuration.On the OLT, use the management IP address of the ONU to log in to the ONU throughTelnet. User name: root. Password: mduadmin.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#telnet 192.168.50.2{ <cr>|service-port<0,4294967295> }:


2. Configure the upstream port of the media stream and the signaling stream.Create VLAN 10 and add upstream port 0/0/1 to the VLAN. Configure the IP addressof the VLAN Layer 3 interface to 17.10.10.10 and subnet mask to 255.255.255.0,

NOTE

l The VLAN ID of the default upstream Ethernet port is 1. Use the default VLAN if nospecific VLAN is required for the upstream transmission.

l If you need to use another VLAN to transmit packets in the upstream direction, run theport vlan command to add the specified upstream port to the VLAN.


3. Configure the media and signaling IP address pools.Configure both the media IP address, the signaling IP address to 17.10.10.10 and themedia gateway address to 17.10.10.1.huawei(config)#voiphuawei(config-voip)#ip address media 17.10.10.10 17.10.10.1huawei(config-voip)#ip address signaling 17.10.10.10huawei(config-voip)#quit

NOTE

l You can configure the attributes of the MG interface only when the media IP address andthe signaling IP address exist in the media and signaling IP address pools.

l The media IP address and the signaling IP address can be different. You can plan the IPaddresses according to the actual network.

4. Configure the static route.Because the IP address of the VLAN interface and the IP address of the MGC are indifferent network segments, you should configure a route for the network segmentfrom gateway 17.10.10.1 to 200.200.200.0.huawei(config)#ip route-static 200.200.200.0 24 17.10.10.1

5. Add an MG interface.Add MG interface 0.huawei(config)#interface h248 0 Are you sure to add MG interface?(y/n)[n]:y

6. Configure the attributes of the MG interface.– Signaling IP address: 17.10.10.10– Coding mode: text– Port number of the transport layer protocol: 2944– Transfer mode: UDP– IP address of the primary MGC: 200.200.200.200– Port number of the transport layer protocol of the primary MGC: 2944



9-27

– Media IP address 1: 17.10.10.10

NOTEYou must confirm these as follows before configuring the MG interface.

l The enrollment type of the MG interface: IP address or the domain name. It must be the samestrictly.

l The beginning negotiation version of H248 protocol: V1, V2 or V3 (default). Some softswitchesdo not support the V3 version, resulting in the MG interface cannot enroll.

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

7. Reset the MG interface.

NOTE

l You must reset the MG interface after configuring and set the type to cold reset. Otherwise theMG interface is invalid.

l Only the mgip, mgport, mgcip_1 (or mgc-domain-name1), mgcport_1, code, transfer, mg-media-ip parameters are set correctly, you can cold reset the MG interface.

huawei(config-if-h248-0)#reset coldstart Are you sure to reset MG interface?(y/n)[n]:yhuawei(config-if-h248-0)#quit

8. Configure the PSTN user data.Configure the telephone number of the user on port 0/2/1 to 0/2/24, telephone numberof the user from 83110001 to 83110024, and terminal ID to 0.

NOTE

l This telephone number is used to self-exchange, means the communication of extension. Thereal telephone numbers are ranged by MGC.

l MA5620 has three hardware type of 8/16/24 POTS. Here take configuration of 24 POTS devicefor example.

l To configure the PSTN data of a single user, run the mgpstnuser add command.

l To configure the PSTN data of multiple users in batches, run the mgpstnuser batadd command.

l If the user of the MG interface is configured to support terminal layering, you need not configurethe terminal ID and the system automatically allocates it. If the user of the MG interface doesnot support terminal layering, this parameter is mandatory. The terminal ID must be unique onone MG interface.

huawei(config)#esl userhuawei(config-esl-user)#mgpstnuser batadd 0/2/1 0/2/24 0 terminalid 0 telno 83110001

9. Change the call priority of the PSTN user.Configure the call priority of the user on port 0/2/1 to Cat2 and the users of 0/2/2 to0/2/24 to Cat3(Default)huawei(config-esl-user)#mgpstnuser modify 0/2/1 priority cat2huawei(config-esl-user)#quit

10. Modify the attributes of all the PSTN ports so that the PSTN ports support the polarityreversal.Modify the attributes of the PSTN port 0/2/1 to 0/2/24 so that the PSTN ports supportthe polarity reversal.huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/2/1 0/2/24 reverse-pole-pulse enablehuawei(config-pstnport)#quit


Configuration Guide


Issue 04 (2011-04-27)


----End

ResultAfter the configuration is completed, users can make calls between two phones.l The caller can hear the dial tone after picking up the phone.l When the caller dials the phone number of the callee, the phone of the callee can ring

normally, and the caller can hear the ringback tone.l The caller and the callee can communicate with each other successfully.l After the callee hangs up the phone, the caller can hear the busy tone.

Configuration FileOn the OLT side.vlan 200 smartport vlan 200 0/19 0dba-profile add profile-name VoIP type3 assure 15360 max 30720ont-lineprofile gpon profile-id 10tcont 2 dba-profile-name VoIPgem add 0 eth tcont 2gem add 1 eth tcont 2mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 200commitquitinterface gpon 0/2port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10ont confirm 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10ont alarm-profile 1 1 profile-id 1ont alarm-profile 1 2 profile-id 1quitvlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitinterface gpon 0/2ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont ipconfig 1 2 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8quittraffic table ip index 9 cir off priority 6 priority-policy tag-In-Packageservice-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 200 vlan 200 gpon 0/2/1 ont 1 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9service-port 201 vlan 200 gpon 0/2/1 ont 2 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

On the ONU side.vlan 200 smartport vlan 200 0/0 1



9-29

interface vlanif 200ip address 17.10.10.10 24quitvoipip address media 17.10.10.10 17.10.10.1ip address signaling 17.10.10.10quitip route-static 200.200.200.0 24 17.10.10.1interface h248 0if-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 2reset coldstartquitesl usermgpstnuser batadd 0/2/1 0/2/24 0 terminalid 0 telno 83110001mgpstnuser modify 0/2/1 priority cat2quitpstnportpstnport attribute batset 0/2/1 0/2/24 reverse-pole-pulse enablequitsave

9.3.3 Configuring the FTTB and FTTC VoIP Services (Based on theSIP Protocol)

The MA5600T/MA5603T is connected to a remote ONU that supports SIP by using the GPONport to provide users with the VoIP service.

Service Requirementsl Users directly uses the existing phone sets for the voice service and no additional investment

is required.l The voice data is carried over the IP network, which reduces the communication costs to

a great extent without compromising the communication quality.l Compared with traditional PSTN networks, IP-based networks provide more powerful

service functions and richer user experience.l The polarity-reversal accounting is supported.

Prerequisitel The PSTN user data corresponding to the SIP interface must be configured on the IMS.l Run the display board 0 command to ensure that the Status of the voice board of ONU is

Normal.

Background InformationONUs that support SIP include the MA5620, MA5612, MA5616, MA5606T, and MA5603T.

An ONU support either H.248 or SIP. To query the current voice protocol on an ONU, run thedisplay protocol support command. To change the voice protocol to the other one, delete theMG interface and run the protocol support command. After the configuration is complete, saveit and restart the system to make the configuration take effect.


Configuration Guide


Issue 04 (2011-04-27)


An ONU support either H.248 or SIP. To query the current voice protocol on an ONU, run thedisplay protocol support command. To change the voice protocol to the other one, delete theMG interface and run the protocol support command. After the configuration is complete, saveit and restart the system to make the configuration take effect. This operation interrupts theongoing services carried on the currently used MG interface. Hence, exercise caution whenperforming this operation.



Create smart VLAN 200 and add upstream port 0/19/0 to it.huawei(config)#vlan 200 smarthuawei(config)#port vlan 200 0/19 0







(1) Configure a DBA profile.You can run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to VoIP, type to Type4, assure bandwidth to15 Mbit/s and maximum bandwidth to 30 Mbit/s.huawei(config)#dba-profile add profile-name VoIP type3 assure 15360 max 30720

(2) Configure an ONU line profile.Create GPON ONU line profile 10 and bind T-CONT 2 to DBA profile VoIP.In this way, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.



9-31

NOTE

The ID of the line profile to be created must not exist in the system. Please create proper lineprofiles according to actual data plan. In this example, line profile 10 is used.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 2 dba-profile-name VoIP

Add GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting VoIP service streams. Bind GEM port 0 and GEM port 1 to T-CONT 2. Set the QoS mode to priority-queue (default).huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 2huawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 2

NOTE



c. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car,traffic profile 6 is bound to the port by default (no rate limitation); when the QoS mode isgem-car, traffic profile 6 is bound to the port by default (no rate limitation).



Configure the mapping between the GEM port and the ONU-side service to theVLAN mapping mode (default), map the service port of management (theCVLAN ID is 8) to GEM port 0, and map the service port of VoIP service (theCVLAN ID is 200) to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 200

After the configuration is complete, run the commit command to make theconfigured parameters take effect.huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

(3) (Optional) Configure an alarm profile.

– The ID of the default GPON alarm profile is 1. The thresholds of all the alarmparameters in the default alarm profile are 0, which indicates that no alarm isgenerated.





Configuration Guide


Issue 04 (2011-04-27)




To add an ONU offline, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#ont add 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10huawei(config-if-gpon-0/2)#ont add 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/2)#display ont autofind 1 //LAN access ONU is used as an example. The system displayed slightly differs according to the ONU version for xDSL access. ------------------------------------------------------------------------ Number : 1 F/S/P : 0/2/1 Ont SN : 32303131B39FD641 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------ Number : 2 F/S/P : 0/2/1 Ont SN : 32303131B39FD642 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access

Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------huawei(config-if-gpon-0/2)#ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10huawei(config-if-gpon-0/2)#ont confirm 1 ontid 2 sn-auth



9-33

32303131B39FD642 snmp ont-lineprofile-id 10



NOTE









– If the ONU does not match, that is, Match state is mismatch, the port types andnumber of ports undermatch the actual port types and number of ports supportedby the ONU. In this case, run the display ont capability command to query theactual capability of the ONU, and then select one of the following modes to modifythe ONU configuration:


Configuration Guide


Issue 04 (2011-04-27)

– 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 theONU.













9-35

Add traffic profile 9, and no rate limitation on user packets. The priority is 6 and thepriority policy is scheduled by the priority that the packets bear.huawei(config)#traffic table ip index 9 cir off priority 6 priority-policy tag-In-Packag


Create service port 200 connected to ONU 1 and service port 201 connected to ONU2. SVLAN ID to 200, GEM port ID to 1, bind traffic profile 9 and CVLAN ID to 200.




Adopt the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode and theirweights are 10, 10, 20, 20, and 40 respectively. Queues 5-7 adopt the PQ mode. Thepriority of the VoIP service is 6, adopting the PQ mode.

NOTE

l The queue scheduling mode is configured globally, and you need to configure it only once onthe OLT. After the configuration is complete, the queue scheduling mode takes effect globally.When subsequent services are configured, you need not configure the queue scheduling modeagain.







NOTE


1. Log in to the ONU to perform the configuration.On the OLT, use the management IP address of the ONU to log in to the ONU throughTelnet. User name: root. Password: mduadmin.huawei(config)#telnet 192.168.50.2{ <cr>|service-port<0,4294967295> }:


2. Configure the upstream port of the media stream and the signaling stream.


Configuration Guide


Issue 04 (2011-04-27)

Create VLAN 200 and add upstream port 0/0/1 to the VLAN. Configure the IP addressof the VLAN Layer 3 interface to 17.10.10.10 and subnet mask to 255.255.0.0,

NOTE

l The VLAN ID must be consistent with the CVLAN of the OLT.

l The VLAN ID of the default upstream Ethernet port is 1. Use the default VLAN if nospecific VLAN is required for the upstream transmission.

l If you need to use another VLAN to transmit packets in the upstream direction, run theport vlan command to add the specified upstream port to the VLAN.


3. Configure the media and signaling IP address pools.Configure both the media IP address, the signaling IP address to 17.10.10.10 and themedia gateway address to 17.10.10.1.huawei(config)#voiphuawei(config-voip)#ip address media 17.10.10.10 17.10.10.1huawei(config-voip)#ip address signaling 17.10.10.10huawei(config-voip)#quit

NOTE

l You can configure the attributes of the SIP interface only when the media IP address andthe signaling IP address exist in the media and signaling IP address pools.

l The media IP address and the signaling IP address can be different. You can plan the IPaddresses according to the actual network.

4. Configure the static route.Because the IP address of the VLAN interface and the IP address of the IMS are indifferent network segments, you should configure a route for the network segmentfrom gateway 17.10.10.1 to 200.200.200.0.huawei(config)#ip route-static 200.200.200.0 24 17.10.10.1

5. Add an SIP interface.Add SIP interface 0.huawei(config)#interface sip 0 Are you sure to add SIP interface?(y/n)[n]:y

6. Configure the basic attributes of the SIP interface.– Signaling IP address: 17.10.10.10– Coding mode: text– Signaling port ID: 5060– Transfer mode: UDP– IP address of the primary IMS: 200.200.200.200– Signaling port ID of the primary IMS: 5060– Media IP address 1: 17.10.10.10– Homing domain name of SIP interface: huawei– SIP profile ID: 1huawei(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



9-37

7. Configure the optional attributes of the SIP interface.You can configure the optional attributes such as the domain name, description,register server uniform resource identifier (URI), phone context and conferencefactory URI by running the if-sip attribute optional command. No configurationhere.

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

9. Configure the PSTN user data.Configure the telephone number of the user on port 0/2/1 to 0/2/24, telephone numberof the user from 83110001 to 83110024, and terminal ID to 0.

NOTE

l To configure the PSTN data of a single user, run the sippstnuser add command.

l To configure the PSTN data of multiple users in batches, run the sippstnuser batadd command.huawei(config)#esl userhuawei(config-esl-user)#sippstnuser batadd 0/2/1 0/2/24 0 telno 83110001

10. Change the call priority of the PSTN user.Configure the call priority of the user on port 0/2/1 to Cat2 and the users of 0/2/2 to0/2/24 to Cat3(Default)huawei(config-esl-user)#sippstnuser attribute set 0/2/1 priority cat2huawei(config-esl-user)#quit

11. Modify the attributes of all the PSTN ports so that the PSTN ports support the polarityreversal.Modify the attributes of the PSTN port 0/2/1 to 0/2/24 so that the PSTN ports supportthe polarity reversal.huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/2/1 0/2/24 reverse-pole-pulse enablehuawei(config-pstnport)#quit


----End



Configuration FileOn the OLT side.

vlan 200 smartport vlan 200 0/19 0dba-profile add profile-name VoIP type3 assure 15360 max 30720


Configuration Guide


Issue 04 (2011-04-27)

ont-lineprofile gpon profile-id 10tcont 2 dba-profile-name VoIPgem add 0 eth tcont 2gem add 1 eth tcont 2mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 200commitquitinterface gpon 0/2port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10ont confirm 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10ont alarm-profile 1 1 profile-id 1ont alarm-profile 1 2 profile-id 1quitvlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitinterface gpon 0/2ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont ipconfig 1 2 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8quittraffic table ip index 9 cir off priority 6 priority-policy tag-In-Packageservice-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 200 vlan 200 gpon 0/2/1 ont 1 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9service-port 201 vlan 200 gpon 0/2/1 ont 2 gemport 1 multi-service user-vlan 200 rx-cttr 9 tx-cttr 9queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

On the ONU side.

vlan 200 smartport vlan 200 0/0 1interface vlanif 200ip address 17.10.10.10 24quitvoipip address media 17.10.10.10 17.10.10.1ip address signaling 17.10.10.10quitip route-static 200.200.200.0 24 17.10.10.1interface sip 0if-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 1resetquitesl usersippstnuser batadd 0/2/1 0/2/24 0 telno 83110001quitpstnportpstnport attribute batset 0/2/1 0/2/24 reverse-pole-pulse enablequitsave



9-39

9.3.4 Configuring the FTTB and FTTC IPTV Multicast ServicesThe MA5600T/MA5603T is connected to a remote ONU through the GPON port to provideusers with the high-speed Internet access service. This topic considers the MA5620 as anexample, and uses the GPBC board on the OLT.

Service Requirementsl The user set-top box (STB) is connected to the ONU 1 and ONU 2 through FE port, and

the ONU 1 and ONU 2 are connected to the OLT and then to the upper-layer networkthrough GPON, implementing the IPTV service.

l The DBA of the IPTV service adopts the maximum bandwidth mode, and no rate limitationis performed on the upstream and downstream traffic.

l The OLT adopts IGMP proxy and the ONU adopts IGMP snooping.l Multicast programs are configured statically.l Multicast logs are reported to the log server in the CDR format.

PrerequisiteThe license for the multicast program or the multicast user must already be requested andinstalled.



Create smart VLAN 1000 and add upstream port 0/19/0 to it.huawei(config)#vlan 1000 smarthuawei(config)#port vlan 1000 0/19 0







(1) Configure a DBA profile.You can run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet the


Configuration Guide


Issue 04 (2011-04-27)

requirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to IPTV, type to Type4, and upstreambandwidth to 100 Mbit/s.huawei(config)#dba-profile add profile-name IPTV type4 max 102400

(2) Add an ONU line profile.Add GPON ONU line profile 10 and bind T-CONT 3 to DBA profile namedIPTV. In this way, the T-CONT can flexibly provide DBA solutions based ondifferent configurations in the DBA profile.

NOTE

The ONU line profile to be created must not exist in the system. Please create proper ONUline profile according to actual data plan. This topic considers creating the ONU line profile10 for example.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 3 dba-profile-name IPTV

Add GEM port 0 for carrying management traffic streams and GEM port 1 forcarrying traffic streams of the IPTV service. Bind GEM port 0 and GEM port 1to T-CONT 3. Configure the QoS mode to priority-queue (default).huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 3 cascade onhuawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 3 cascade on

NOTE

a. To change the default QoS mode, run the qos-mode command to configure the QoS modeto gem-car or flow-car, and run the gem add command to configure the index of the trafficprofile to which the GEM port is bound.


c. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car,traffic profile 6 is bound by default (no rate limitation); when the QoS mode is gem-car,traffic profile 6 is bound by default (no rate limitation).



Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management (CVLAN 8) to GEM port 0, andmap the service port of IPTV service port (CVLAN 1000) to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 1000


(3) (Optional) Configure an alarm profile.



9-41









To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/2huawei(config-if-gpon-0/2)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/2)#display ont autofind 1 //LAN access ONU is used as an example. The system displayed slightly differs according to the ONU version for xDSL access. ------------------------------------------------------------------------ Number : 1 F/S/P : 0/2/1 Ont SN : 32303131B39FD641 Password : VenderID : HWTC Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access Ont autofind time : 2009-08-21 16:51:45 ------------------------------------------------------------------------ Number : 2 F/S/P : 0/2/1 Ont SN : 32303131B39FD642 Password : VenderID : HWTC


Configuration Guide


Issue 04 (2011-04-27)

Ont Version : Ont SoftwareVersion : V8R308 C00 Ont EquipmentID : SmartAX MA5620G //Here display MA5616 for xDSL access


(2) (Optional) Bind an alarm profile to the ONU.

After an alarm profile is configured, bind it to the ONT. In this example, bindthe default alarm profile, namely alarm profile 1 to the ONU.huawei(config-if-gpon-0/2)#ont alarm-profile 1 1 profile-id 1huawei(config-if-gpon-0/2)#ont alarm-profile 1 2 profile-id 1


NOTE




If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match,refer to the following suggestions to rectify the fault.

– If Control flag is deactive, run the ont activate command in the GPON port modeto activate the ONU.

– If the ONU fails to be in the up state, that is, Run state is offline, the physical linemay be broken or the optical transceiver may be damaged. You need to check boththe material and the line.




9-43











Configuration Guide


Issue 04 (2011-04-27)




Create service port 1000 connected to ONU 1 and service port 1001 connected to ONU2. SVLAN ID to 1000, GEM port ID to 1, and CVLAN ID to 1001. Rate limitationfor upstream and downstream packets is performed on the ONU instead of on the OLT.Therefore, use traffic profile 6 (default). To limit the rate of the service port, run thetraffic table ip command to add a traffic profile and bind it to the service port.




Adopt the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode and theirweights are 10, 10, 20, 20, and 40 respectively. Queues 5-7 adopt the PQ mode. Thepriority of the IPTV service is 4, adopting the WRR mode.

NOTE

l The queue scheduling mode is configured globally, and you need to configure it only once onthe OLT. After the configuration is complete, the queue scheduling mode takes effect globally.When subsequent services are configured, you do not need to configure the queue schedulingmode again.





10. Configure a multicast subtending port.Configure port 0/2/1 connected to the ONU as a multicast subtending port.huawei(config)#btvhuawei(config-btv)#igmp cascade-port 0/2/1 ontid 1 gemport 1huawei(config-btv)#igmp cascade-port 0/2/1 ontid 2 gemport 1



9-45

NOTEIf no multicast subtending port is configured and multicast users are directly configured, themaximum number of multicast users that each multicast user can demand is limited. If multicastusers are directly configured:

l To set authentication of a multicast user, run the igmp profile add command to create a rightprofile, run the igmp profile command to modify right parameters in the profile, and then runthe igmp user bind-profile command to bind the right profile to the multicast user.

l To authenticate a multicast user, remove parameter no-auth when adding the multicast user.

The corresponding procedure is as follows:huawei(config-btv)#igmp user add service-port 1000 no-authhuawei(config-btv)#igmp user add service-port 1001 no-authhuawei(config-btv)#multicast-vlan 1000huawei(config-mvlan1000)#igmp multicast-vlan member service-port 1000huawei(config-mvlan1000)#igmp multicast-vlan member service-port 1001

11. Set the IGMP version.Use IGMP V3.huawei(config)#multicast-vlan 1000huawei(config-mvlan10000)#igmp version v3

12. Select the IGMP mode.Select the IGMP proxy mode.huawei(config-mvlan10000)#igmp mode proxy Are you sure to change IGMP mode?(y/n)[n]:y

13. Configure the IGMP upstream port.The IGMP upstream port is port 0/19/0 and works in the default mode, and protocolpackets are transmitted to all the IGMP upstream ports in the multicast VLAN.huawei(config-mvlan10000)#igmp uplink-port 0/19/0

14. Set the multicast global parameters.In this example, the default settings are used for all the multicast global parameters.

15. Configure the program library.The multicast IP address of the program is 224.1.1.10 and the IP address of the programsource is 10.10.10.10huawei(config-mvlan10000)#igmp program add name program1 ip 224.1.1.10 sourceip 10.10.10.10

16. Configure a log server.Enable CDR log reporting, and configure the IP address of the active server to10.10.10.20.huawei(config-mvlan10000)#btvhuawei(config-btv)#igmp cdr enablehuawei(config-btv)#quithuawei(config)#file-server auto-backup cdr primary 10.10.10.20 tftp


l Configure the ONU.1. Log in to the ONU to perform the configuration.

On the OLT, use the management IP address of the ONU to log in to the ONU throughTelnet. User name: root. Password: mduadmin.




Configuration Guide


Issue 04 (2011-04-27)

Add traffic profile 10, and no rate limitation on user packets. The priority is 4, bindthe traffic profile 8 and the priority policy is scheduled by the priority that the packetsbear.huawei(config)#traffic table ip index 10 cir off priority 4 priority-policy tag-In-Package

3. Configure a VLAN and add an upstream port to the VLAN.Create S-VLAN 1000 and add upstream port 0/0/1 to S-VLAN 1000.

NOTEThe CVLAN must be consistent with the upstream VLAN of the ONU.huawei(config)#vlan 1000huawei(config)#port vlan 1000 0/0 1

4. Configure a service port.Add service port 100, configure CVLAN to untagged, and bind VLAN 1000 and trafficprofile 10 to it.huawei(config)#service-port 100 vlan 1000 eth 0/1/1 multi-service user-vlan untagged rx-cttr 10 tx-cttr 10

5. Configure the multicast mode and multicast protocol version.Configure the multicast mode to IGMP snooping and adopt IGMP V3.huawei(config)#multicast-vlan 1000huawei(config-mvlan1000)#igmp version v3huawei(config-mvlan1000)#igmp mode snooping

6. Configure a multicast upstream port and a multicast program.Configure upstream port 0/0/1 as the upstream multicast port, and configure the IPaddress of the multicast to 224.1.1.10 and the source IP address to 10.10.10.10.huawei(config-mvlan1000)#igmp uplink-port 0/0/1huawei(config-mvlan1000)#igmp program add ip 224.1.1.10 sourceip 10.10.10.10

7. Configure a multicast user and add the user to the multicast VLAN.Configure service port 1000 as a multicast user, add the user to VLAN 1000, and adoptthe no-auth mode for the multicast user.

NOTE

l If set users to be authenticated, you can run the command igmp profile add to add a multicastauthority profile, and then use the command igmp profile to modify the authority parameters.At last, use the igmp user bind-profile command to bind this profile to the user need to beauthenticated.

l If set users to be authenticated, delete the no-auth parameter.huawei(config-mvlan1000)#btvhuawei(config-btv)#igmp user add service-port 1000 no-authhuawei(config-btv)#multicast-vlan 1000huawei(config-mvlan1000)#igmp multicast-vlan member service-port 100

8. Save the configuration.huawei(config)#save

----End

ResultThe user can watch program 1 on the TV.

Configuration FileOn the OLT side.



9-47

vlan 1000 smartport vlan 1000 0/19 0dba-profile add profile-name IPTV type4 max 61440ont-lineprofile gpon profile-id 10tcont 3 dba-profile-name IPTVgem add 0 eth tcont 3 cascade ongem add 1 eth tcont 3 cascade onmapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 1000commitquitinterface gpon 0/2port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 32303131B39FD641 snmp ont-lineprofile-id 10ont confirm 1 ontid 2 sn-auth 32303131B39FD642 snmp ont-lineprofile-id 10ont alarm-profile 1 1 profile-id 1ont alarm-profile 1 2 profile-id 1quitvlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 gateway 192.168.50.254 vlan 8ont ipconfig 1 2 static ip-address 192.168.50.3 mask 255.255.255.0 gateway 192.168.50.254 vlan 8service-port 1 vlan 8 gpon 0/2/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 2 vlan 8 gpon 0/2/1 ont 2 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 1000 vlan 100 gpon 0/2/1 ont 1 gemport 1 multi-service user-vlan 1000 rx-cttr 6 tx-cttr 6service-port 1001 vlan 100 gpon 0/2/1 ont 2 gemport 1 multi-service user-vlan 1000 rx-cttr 6 tx-cttr 6queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7btvigmp cascade-port 0/2/1 ontid 1 gemport 1igmp cascade-port 0/2/1 ontid 2 gemport 1multicast-vlan 1000igmp version v3igmp mode proxyigmp uplink-port 0/19/0igmp program add name program1 ip 224.1.1.10 sourceip 10.10.10.10btvigmp cdr enablequitfile-server auto-backup cdr primary 10.10.10.20 tftpsave

On the ONU side.

vlan 1000 smartport vlan 1000 0/0 1traffic table ip index 10 cir off priority 4 priority-policy tag-In-Packagservice-port 100 vlan 1000 eth 0/1/1 multi-service user-vlan untagged rx-cttr 10 tx-cttr 10multicast-vlan 1000igmp version v3igmp mode proxyigmp uplink-port 0/0/1igmp program add name program1 ip 224.1.1.10 sourceip 10.10.10.10btvigmp user add service-port 100 no-authmulticast-vlan 1000igmp multicast-vlan member service-port 100save


Configuration Guide


Issue 04 (2011-04-27)

9.4 Configuring the FTTO ServiceThrough the "OLT+SBU" network, the fiber to the office (FTTO) solution is provided forenterprise users. This topic describes how to configure the TDM PBX access, IP PBX access,enterprise router access services, and enterprise POTS access services in the FTTO scenario.

Context

In the FTTO solution, ONU provides flexible configurations and specifications through semi-slot boards and supports multiple network modes to meet networking requirements for variousservices in different environments. The ONU has the following features:

l Provides eight E1 ports through the E81A board for connecting to the enterprise TDM PBXto provide the TDM private line service.

l Provides eight FE electrical ports through the EIUC board, or provides two GE and six FEelectrical ports through the EPFB board for connecting to the LAN switch or enterpriserouter.

l Provides a 16-channel POTS port through the ASNB board for connecting to the analogphone sets of the enterprise, implementing the VoIP service (Only for MA5612).

l Supports upstream adaptation between three modes, flexibly providing the "dual GPON"and "single GE+single GPON" upstream ports and transmitting the data service to the SDHor PSN network through the OLT.

l Encapsulates the TDM voice service and data service using the PWE3 technology, ensuringthe reliable transmission of signals.

9.4.1 Configuring the TDM PBX Access ServiceThe ONU provides eight E1 ports for connecting to the enterprise TDM PBX, and the OLTtransmits signals of the TDM PBX upstream to the SDH or PSN network. The ONUs supportthis service are MA5612 and MA5628.

9.4.2 Configuring the Enterprise Router Access ServiceThe ONU provides FE/GE ports for connecting to the enterprise router or Layer 3 switch, andthe OLT transmits signals of the router or switch upstream to the IP network. The ONUs supportthis service are MA5612 and MA5628.

9.4.3 Configuring the IP PBX Access ServiceThe ONU provides GE/FE ports for connecting to the enterprise IP PBX, and the OLT transmitssignals of the IP PBX upstream to the PSN network. The ONUs support this service are MA5612and MA5628.

9.4.4 Configuring the POTS Access Service of the EnterpriseThe ASNB board of the ONU provides a 16-channel POTS port for connecting to the analogphone sets of the enterprise, implementing the VoIP service. The ONUs support this service isMA5612.

9.4.1 Configuring the TDM PBX Access ServiceThe ONU provides eight E1 ports for connecting to the enterprise TDM PBX, and the OLTtransmits signals of the TDM PBX upstream to the SDH or PSN network. The ONUs supportthis service are MA5612 and MA5628.



9-49

Service Requirementsl The E1 port of the ONU is connected to the enterprise TDM PBX.

l Through line emulation, the TDM service data can be transmitted in the GPON network.

l Signals are transmitted upstream to the OLT through GPON, and the OLT transmits thesignals upstream to the SDH or PSN network.

l Various PWE3 encapsulation modes are flexibly adopted.

Background Information

The TDM PBX access service is classified into two scenarios:

l The ONU provides the PBX access, and the OLT transmits signals upstream to the SDHnetwork through the E1 or STM-1 port.

l The ONU provides the PBX access, and the OLT transmits signals upstream to the PSNnetwork (MPLS or IP bearer network) through the FE or GE port.

Note that the service configurations are different in different network scenarios.

Figure 9-3 shows an example network of the TDM PBX access service.

Figure 9-3 Example network of the TDM PBX access service

Procedurel Scenario 1: The ONU provides the PBX access, and the OLT transmits signals upstream

to the SDH network through the E1 or STM-1 port.

For details about the configuration, see Configuring the TDM PWE3 Base station accessService Between the ONU and the OLT.

l Scenario 2: The ONU provides the PBX access, and the OLT transmits signals upstreamto the PSN network (MPLS or IP bearer network) through the FE or GE port.

According to different bearer networks (MPLS and IP bearer networks), this scenario issubdivided into the two cases. For details about the configuration, see the following topics:

– 9.5.4 Configuring the TDM PWE3 Base station access Service on the OLT (MPLS-based).

– 9.5.5 Configuring the TDM PWE3 Base station access Service on the OLT (IP-based).

----End


Configuration Guide


Issue 04 (2011-04-27)

9.4.2 Configuring the Enterprise Router Access ServiceThe ONU provides FE/GE ports for connecting to the enterprise router or Layer 3 switch, andthe OLT transmits signals of the router or switch upstream to the IP network. The ONUs supportthis service are MA5612 and MA5628.

Service RequirementsProvide a transparent and safe data channel for enterprise private networks that are located indifferent places, so that the service data and BPDUs between enterprise private networks can betransparently transmitted in the public network.

Figure 9-4 shows an example network of the enterprise router access service.

The FE/GE port of the ONU is connected to the enterprise router or Layer 3 switch. Configurethe QinQ VLAN encapsulation mode on both ONU_1 and ONU_2 so that data can betransparently transmitted in the GPON network. Signals are transmitted upstream to the OLTthrough GPON, and then the OLT transmits the signals upstream to the IP network.

Figure 9-4 Example network of the enterprise router access service

Data PlanTable 9-3 provides the data plan for the OLT, and Table 9-4 provides the data plan for the ONU.

Table 9-3 Data plan for configuring the enterprise router access service-OLT side

Item Data

VLAN Inband management VLAN: smart VLAN 8SVLAN: smart VLAN 2000 with the attribute QinQ

IP address Inband management IP address: 192.168.50.1/24



9-51

Item Data

GPON service board Port: 0/3/1ONU ID: 1ONU authentication mode: SNONU SN: 48575443E6D8B541

DBA profile Profile name: PrivateLineType: type3Assured bandwidth: 20 Mbit/sMaximum bandwidth: 50 Mbit/s

ONU line profile Profile ID: 10, bound to the DBA profile named PrivateLineGEM port IDs: 0 and 1T-CONT ID: 5

ONU management mode SNMP

Table 9-4 Data plan for configuring the enterprise router access service-ONU side

Item Data

VLAN Inband management VLAN: smart VLAN 8, adding GPONupstream port 0/0/0 to this VLANSVLAN: smart VLAN 2000 with the attribute QinQ, addingGPON upstream port 0/0/0 to the VLANPrivate VLANs of enterprise A and enterprise B: VLAN 50 andVLAN 60



NOTEOLT_1 and OLT_2 have the same configuration.



huawei(config)#vlan 2000 smarthuawei(config)#vlan attrib 2000 q-in-qhuawei(config)#port vlan 2000 0/19 0

2. (Optional) Configure upstream link aggregation.In this example, a single upstream port is used. In the case of multiple upstream ports,upstream link aggregation can be configured. For details, see Configuring UpstreamLink Aggregation.


Configuration Guide


Issue 04 (2011-04-27)


GPON ONU profiles include the DBA profile, line profile and alarm profile.– DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT




(1) Add a DBA profile.You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the profile name to PrivateLine, profile type to Type3, assuredbandwidth to 20 Mbit/s, and maximum bandwidth to 50 Mbit/s.huawei(config)#dba-profile add profile-name PrivateLine type3 assure 20480 max 51200

(2) Add an ONU line profile.Add GPON MDU line profile 10 and bind T-CONT 5 to the DBA profile namedPrivateLine. In this way, the T-CONT can provide flexible DBA solutions basedon different configurations in the DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name PrivateLineAdd GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting ETH traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 5. Configure the QoS mode to priority-queue (default) and the queuepriority to 3.

NOTE


b. When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car,traffic profile 6 is bound to the port by default (no rate limitation); when the QoS mode isgem-car, traffic profile 6 is bound to the port by default (no rate limitation).

huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 5 priority-queue 3huawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 5 priority-queue 3Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management VLAN 8 to GEM port 0, and mapthe service port of SVLAN 2000 to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 2000After the configuration is complete, run the commit command to make theconfigured parameters take effect.



9-53

huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

(3) (Optional) Add an alarm profile.



– Run the gpon alarm-profile add command to add an alarm profile, which isused for monitoring the performance of an activated ONU line.


The ONU is connected to the GPON port of the OLT through an optical fiber. Youcan perform the service configuration only after adding an ONU successfully on theOLT.

(1) Add an ONU.

Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound lineprofile ID is 10.

There are two ways to add an ONU. Select either of the two ways according toactual conditions.

– Add an ONU offline: If the password or SN of an ONU is obtained, you canrun the ont add command to add the ONU offline.

– Automatically find an ONU: If the password or SN of an ONU is unknown,run the port ont-auto-find command in the GPON mode to enable the ONUauto-find function of the GPON port. Then, run the ont confirm commandto confirm the ONU.

To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example. ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10


Configuration Guide


Issue 04 (2011-04-27)

NOTEIf multiple ONUs of the same type are connected to a port and the same line profile or serviceprofile (for an ONT) is bound to the ONUs, you can add ONUs in batches by confirming theauto-found ONUs in batches to simplify the operation and increase the configurationefficiency. For example, the preceding command can be modified as follows:ont confirm 1all sn-auth snmp ont-lineprofile-id 10 .

(2) (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.huawei(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 1



huawei(config-if-gpon-0/3)#display ont info 1 1 --------------------------------------------------------------------- F/S/P : 0/3/1 ONT-ID : 1 Control flag : active //Indicates that the ONU is activated. Run state : online //Indicates that the ONU already goes online normally. Config state : normal //Indicates that the configuration status of the ONU is normal. Match state : match //Indicates that the capability profile bound to the ONU is //consistent with the actual capability of the ONU. //The rest of the response information is omitted.










9-55



NOTEOnly when the OLT remotely manages the ONU through SNMP, the management channel needs tobe configured. When the OLT remotely manages the ONU through OMCI, the management channelneed not be configured.

(1) Configure the inband management VLAN and IP address of the OLT.

To log in to the ONU through Telnet and configure the ONU from the OLT, youmust configure the inband management VLANs and IP addresses of the OLTand the ONU on the OLT.

Create management VLAN 8 and add upstream port 0/19/0 to it. Configure theinband management IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

(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 and themanagement VLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

(3) Configure an inband management service port.

Configure the management service port ID to 0, management VLAN ID to 8,GEM port ID to 0, and CVLAN ID to 8. The rate of the inband service port onthe OLT is not limited. Therefore, use traffic profile 6 (default). To limit the rateof the service port, run the traffic table ip command to add a traffic profile andbind it to the service port.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6


– On the OLT, run the ping 192.168.50.2 command to check the connectivity to theONU. The ICMP ECHO-REPLY packet from the ONU should be received.

– You can run the telnet 192.168.50.2 command to telnet to the ONU and thenconfigure the ONU.


Configure the service port ID to 1, SVLAN ID to 2000, GEM port ID to 1, and CVLANID to 2000. Rate limitation for upstream and downstream packets is performed on theMDU instead of on the OLT. Therefore, use traffic profile 6 (default). To limit therate of the service port, run the traffic table ip command to add a traffic profile andbind it to the service port.

The CVLAN must be the same as the upstream VLAN of the ONU.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#service-port 1 vlan 2000 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 2000 rx-cttr 6 tx-cttr 6

9. Configure queue scheduling.

Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with theweights of 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode. Thepriority of the TDM emulation service is 6, adopting the PQ scheduling.

Queue scheduling is a global configuration. You need to configure queue schedulingonly once on the OLT, and then the configuration takes effect globally. In thesubsequent phases, you need not configure queue scheduling repeatedly whenconfiguring other services.


Configure the mapping between queues and 802.1p priorities. Priorities 0-7 mapqueues 0-7 respectively.

For the service board that supports only four queues, the mapping between 802.1ppriorities and queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and3 map queue 2; priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.




NOTEBecause the management VLAN and the management IP address have been configured, you can run thetelnet 192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You canalso log in to the ONU through a serial port to perform the configuration.

ONU_1 and ONU_2 have the same configuration.

1. Create an SVLAN and add an upstream port to it.Configure the SVLAN ID to 2000, type to smart, attribute to QinQ, and upstreamGPON port to 0/0/0.huawei(config)#vlan 2000 smarthuawei(config)#vlan attrib 2000 q-in-qhuawei(config)#port vlan 2000 0/0 0

2. (Optional) Enable transparent transmission of BPDUs, and bind VLAN service profile1 to the SVLAN.huawei(config)#vlan service-profile profile-id 1huawei(config-vlan-srvprof-1)#bpdu tunnel enable Info: Please use the commit command to make modifications take effecthuawei(config-vlan-srvprof-1)#commithuawei(config-vlan-srvprof-1)#quithuawei(config)#vlan bind service-profile 2000 profile-id 1

3. Create a service port.Create service ports for VLAN 2000 with the QinQ attribute. The outer VLAN ID is2000. The router or Layer 3 switch of enterprise A is connected to GE port 0/4/0 ofthe ONU, and the Intranet packets of enterprise A contain VLAN tag 50; the routeror Layer 3 switch of enterprise B is connected to GE port 0/4/1 of the ONU, and theIntranet packets of enterprise B contain VLAN tag 60.huawei(config)#service-port vlan 2000 eth 0/4/0 multi-service user-vlan 50 rx-cttr 6 tx-cttr 6



9-57

huawei(config)#service-port vlan 2000 eth 0/4/1 multi-service user-vlan 60 rx-cttr 6 tx-cttr 6


----End

ResultThe private networks distributed in two places can communicate with each other and variousservices can be provided between these private networks.

Configuration FileConfigure the OLT.

vlan 2000 smartvlan attrib 2000 q-in-qport vlan 2000 0/19 0vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name PrivateLine type3 assure 20480 max 51200ont-lineprofile gpon profile-id 10tcont 5 dba-profile-name PrivateLinegem add 0 eth tcont 5 priority-queue 3gem add 1 eth tcont 5 priority-queue 3mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 2000commitquitinterface gpon 0/3port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 1 vlan 2000 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 2000 rx-cttr 6 tx-cttr 6queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

Configure the ONU.

vlan 2000 smartvlan attrib 2000 q-in-qport vlan 2000 0/0 0vlan service-profile profile-id 1bpdu tunnel enablecommitquitvlan bind service-profile 2000 profile-id 1service-port vlan 2000 eth 0/4/0 multi-service user-vlan 50 rx-cttr 6 tx-cttr 6service-port vlan 2000 eth 0/4/1 multi-service user-vlan 60 rx-cttr 6 tx-cttr 6save


Configuration Guide


Issue 04 (2011-04-27)

9.4.3 Configuring the IP PBX Access ServiceThe ONU provides GE/FE ports for connecting to the enterprise IP PBX, and the OLT transmitssignals of the IP PBX upstream to the PSN network. The ONUs support this service are MA5612and MA5628.

Service Requirementsl The FE/GE port of the ONU is connected to the enterprise IP PBX.

l Data can be transparently transmitted in the GPON network.

l Signals are transmitted upstream to the OLT through GPON, and the OLT transmits thesignals upstream to the IP or MPLS network.

l L2 VPN adopts the QinQ VLAN or ETH PWE3 encapsulation mode.

Background Information

IP PBX is an IP network-based company telephone system. It can integrate voice communicationinto the data network of the company, setting up an integrated voice and data network that canconnect all offices and employees distributed all over the world. For example, the SoftCo seriesIP voice integrated switch of Huawei can function as a mini NGN system and IP-PBX.

The IP PBX access service is classified into two scenarios:

l The ONU provides the IP PBX access, and the OLT transmits data transparently to the IPnetwork in the QinQ VLAN mode.

l The ONU provides the IP PBX access, and the OLT transmits data transparently to theMPLS network in the ETH PWE3 mode.

Note that the service configurations vary with the network scenario.

Figure 9-5 shows an example network of the IP PBX access service.

Figure 9-5 Example network of the IP PBX access service

Procedurel Scenario 1: The ONU provides the IP PBX access, and the OLT transmits data transparently

to the IP network in the QinQ VLAN mode.

For details about the configuration, see 9.4.2 Configuring the Enterprise Router AccessService.

l Scenario 2: The ONU provides the IP PBX access, and the OLT transmits data transparentlyto the MPLS network in the ETH PWE3 mode.



9-59

For details about the configuration, see 9.5.6 Configuring the ETH PWE3 Base stationaccess Service on the OLT.

----End

9.4.4 Configuring the POTS Access Service of the EnterpriseThe ASNB board of the ONU provides a 16-channel POTS port for connecting to the analogphone sets of the enterprise, implementing the VoIP service. The ONUs support this service isMA5612.

Service Requirementsl The enterprise directly uses the existing phone sets for the voice service and no additional

investment is required.l The voice data is carried over the IP network, which reduces the communication costs of

the enterprise to a great extent without compromising the communication quality.l The extensions can call each other using the original internal extension numbers.l The DBA mode of the VoIP service is assured bandwidth + maximum bandwidth, and no

rate limitation is performed on the upstream and downstream traffic.l The polarity-reversal accounting is adopted.

Prerequisitel If H.248 is used as the voice protocol, the MGC interface data and the PSTN user data

corresponding to the MG interface must be configured on the MGC.l If SIP is used as the voice protocol, the SIP interface data and the PSTN user data

corresponding to the SIP interface must be configured on the IMS.

Background InformationThe ONU supports voice protocols H.248 and SIP, but only one is used at a time. You can runthe display protocol support command to query the currently used voice protocol of the system.To switch between the two voice protocols, ensure that the MG is deleted and run the protocolsupport command. After the configuration is complete, save the configuration and restart thesystem to make the configured protocol take effect.


In this example, SIP is used. For the configuration of H.248, see 9.3.2 Configuring the FTTBand FTTC VoIP Services (Based on the H.248 Protocol).

Figure 9-6 shows an example network of the POTS access service. The ONU is connected to16 analog phone sets through the POTS port. After the digital conversion of the voice signals(forming IP packets), the ONU encapsulates them into GEM frames and transmits the GEMframes upstream to the OLT through the GPON. The OLT decapsulates the GEM frames,recovers the IP packets, and forwards them to the MGC on the other side of the IP network. Forthe ONU, the OLT transparently transmits the voice service.


Configuration Guide


Issue 04 (2011-04-27)

Figure 9-6 Example network of the POTS access service of the enterprise

Procedure

Step 1 Configure the OLT:1. Create an SVLAN and add an upstream port to it.

Create smart SVLAN 200 with the attributed common and add upstream port 0/19/0 toVLAN 200.


2. (Optional) Configure upstream link aggregation.In this example, a single upstream port is used. In the case of multiple upstream ports,upstream link aggregation can be configured. For details, see Configuring Upstream LinkAggregation.

3. Configure the GPON ONU profiles.

GPON ONU profiles include the DBA profile, line profile and alarm profile.l DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT is

bound to a DBA profile for dynamic bandwidth allocation, improving the upstreambandwidth usage rate.

l Line profile: A line profile describes the binding between the T-CONT and the DBAprofile, the QoS mode of the traffic stream, and the mapping between the GEM portand the ONU-side service.

l Alarm profile: An alarm profile contains a series of alarm thresholds to measure andmonitor the performance of activated ONU lines. When a statistical value reaches thethreshold, the host is notified and an alarm is reported to the log host and the NMS.

a. Add a DBA profile.You can at first run the display dba-profile command to query the traffic profilesexisting in the system. If the traffic profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a traffic profile.Configure the DBA profile name to VOIP, type to Type3, assured bandwidth to 15Mbit/s, and maximal bandwidth to 30M bit/s.huawei(config)#dba-profile add profile-name VOIP type3 assure 15360 max 30720

b. Add an ONU line profile.Add GPON MDU line profile 10 and bind T-CONT 5 to the DBA profile named VOIP.In this way, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.



9-61

huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name VOIP

Add GEM port 0 for transmitting management traffic streams and GEM port 1 fortransmitting ETH traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 5.Configure the QoS mode to priority-queue (default) and the queue priority to 3.

NOTE

1) To change the QoS mode, run the qos-mode command to configure the QoS mode to gem-caror flow-car, and run the gem add command to configure the ID of the traffic profile bound tothe GEM port.

2) When the QoS mode is PQ, the default queue priority is 0; when the QoS is flow-car, trafficprofile 6 is bound to the port by default (no rate limitation); when the QoS mode is gem-car,traffic profile 6 is bound to the port by default (no rate limitation).

huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 5 priority-queue 3huawei(config-gpon-lineprofile-10)#gem add 1 eth tcont 5 priority-queue 3

Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management VLAN 8 to GEM port 0, and map theservice port of SVLAN 200 to GEM port 1.huawei(config-gpon-lineprofile-10)#mapping-mode vlanhuawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 vlan 200

After the configuration is complete, run the commit command to make the configuredparameters take effect.huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

c. (Optional) Add an alarm profile.l The ID of the default GPON alarm profile is 1. The thresholds of all the alarm


l In this example, the default alarm profile is used, and therefore the configurationof the alarm profile is not required.

l Run the gpon alarm-profile add command to add an alarm profile, which is usedfor monitoring the performance of an activated ONU line.


The ONU is connected to the GPON port of the OLT through an optical fiber. You canperform the service configuration only after adding an ONU successfully on the OLT.

a. Add an ONU.Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound line profile IDis 10.There are two ways to add an ONU. Select either of the two ways according to actualconditions.l Add an ONU offline: If the password or SN of an ONU is obtained, you can run

the ont add command to add the ONU offline.l Automatically find an ONU: If the password or SN of an ONU is unknown, run

the port ont-auto-find command in the GPON mode to enable the ONU auto-findfunction of the GPON port. Then, run the ont confirm command to confirm theONU.

To add an ONU offline, do as follows:


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

NOTEIf multiple ONUs of the same type are connected to a port and the same line profile or service profile(for an ONT) is bound to the ONUs, you can add ONUs in batches by confirming the auto-foundONUs in batches to simplify the operation and increase the configuration efficiency. For example,the preceding command can be modified as follows:huawei(config-if-gpon-0/3)#ont confirm 1 all sn-auth snmp ont-lineprofile-id 10

b. (Optional) Bind the alarm profile to the ONU.

The default profile (profile 1) is used.huawei(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 1


After an ONU is added, run the display ont info command to query the current status ofthe ONU. Ensure that Control flag of the ONU is active, Run State is online, Configstate is normal, and Match state is match.


If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match, referto the following suggestions to rectify the fault.



9-63

l If Control flag is deactive, run the ont activate command in the GPON port mode toactivate the ONU.

l If the ONU fails to be in the up state, that is, Run state is offline, the physical line maybe broken or the optical transceiver may be damaged. You need to check both thematerial and the line.

l If the ONU state fails, that is, Config state is failed, the ONU capability set outmatchesthe actual ONU capabilities. In this case, run the display ont failed-configurationcommand in the diagnosis mode to check the failed configuration item and the failurecause. Then, rectify the fault according to actual conditions.

NOTEIf an ONT supports only four queues, the values of 4-7 of the priority-queue parameter in the gemadd command are invalid. After configuration recovers, Config state will be failed.

l If the ONU does not match, that is, Match state is mismatch, the port types and numberof 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 ofthe 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.6. Configure the management channel from the OLT to the ONU.

NOTEOnly when the OLT remotely manages the ONU through SNMP, the management channel needs to beconfigured. When the OLT remotely manages the ONU through OMCI, the management channel neednot be configured.

a. Configure the inband management VLAN and IP address of the OLT.To log in to the ONU through Telnet and configure the ONU from the OLT, you mustconfigure the inband management VLANs and IP addresses of the OLT and the ONUon the OLT.Create management VLAN 8 and add upstream port 0/19/0 to it. Configure the inbandmanagement IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

b. 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 and the managementVLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

c. Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 8, GEMport ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT isnot limited. Therefore, use traffic profile 6 (default). To limit the rate of the serviceport, run the traffic table ip command to add a traffic profile and bind it to the serviceport.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-


Configuration Guide


Issue 04 (2011-04-27)

service user-vlan 8 rx-cttr 6 tx-cttr 6

7. 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 to the ONU.

The ICMP ECHO-REPLY packet from the ONU should be received.l You can run the telnet 192.168.50.2 command to telnet to the ONU and then configure

the ONU.8. Create a service port.

Configure the service port ID to 1, SVLAN ID to 200, GEM port ID to 1, and CVLAN IDto 200. Rate limitation for upstream and downstream packets is performed on the MDUinstead of on the OLT. Therefore, use traffic profile 6 (default). To limit the rate of theservice port, run the traffic table ip command to add a traffic profile and bind it to theservice port.


huawei(config)#service-port 1 vlan 200 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6


Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with the weightsof 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode. The priority of theTDM emulation service is 6, adopting the PQ scheduling.

Queue scheduling is a global configuration. You need to configure queue scheduling onlyonce on the OLT, and then the configuration takes effect globally. In the subsequent phases,you need not configure queue scheduling repeatedly when configuring other services.


Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map queues0-7 respectively.

For the service board that supports only four queues, the mapping between 802.1p prioritiesand queue IDs is as follows: priorities 0 and 1 map queue 1; priorities 2 and 3 map queue2; priorities 4 and 5 map queue 3; priorities 6 and 7 map queue 4.



Step 2 Configure the ONU:

NOTEBecause the management VLAN and the management IP address have been configured, you can run the telnet192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You can also log in tothe ONU through a serial port to perform the configuration.


The VLAN ID must be consistent with the CVLAN of the OLT.





9-65

2. Configure the upstream port of the media stream and the signaling stream.Create VLAN 200 and add upstream port 0/0/0 to the VLAN. Configure the IP address ofthe VLAN L3 interface to 17.10.10.10 and subnet mask to 255.255.255.0.huawei(config)#interface vlanif 200huawei(config-if-vlanif200)#ip address 17.10.10.10 24huawei(config-if-vlanif200)#quit

3. Configure the media and signaling IP address pools.

You can configure the attributes of the SIP interface only when the media IP address andthe signaling IP address exist in the media and signaling IP address pools.

The media IP address and the signaling IP address can be different. You can plan the IPaddresses according to the actual network.

Configure both the media IP address and the signaling IP address to 17.10.10.10, and themedia gateway to 17.10.10.1.

huawei(config)#voiphuawei(config-voip)#ip address media 17.10.10.10 17.10.10.1huawei(config-voip)#ip address signaling 17.10.10.10huawei(config-voip)#quit

4. Configure the static route.Because the IP address of the VLAN interface and the IP address of the IMS are in differentnetwork segments, you should configure a route for the network segment from gateway17.10.10.1 to 200.200.200.0.huawei(config)#ip route-static 200.200.200.0 24 17.10.10.1

5. Add an SIP interface.huawei(config)#interface sip 0 Are you sure to add SIP interface?(y/n)[n]:y

6. Configure the basic attributes of the SIP interface.l Signaling IP address: 17.10.10.10l Coding mode: textl Signaling port ID: 5060l Transfer mode: UDPl IP address of the primary IMS: 200.200.200.200l Signaling port ID of the primary IMS: 5060l Media IP address 1: 17.10.10.10l Homing domain name of SIP interface: huaweil SIP profile ID: 1huawei(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

7. (Optional) Configure the optional attributes of the SIP interface.You can configure the optional attributes such as the domain name, description, registerserver uniform resource identifier (URI), phone context and conference factory URI byrunning command if-sip attribute optional. No configuration here.

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


Configuration Guide


Issue 04 (2011-04-27)

9. Configure the PSTN user data.Configure the telephone number of the user on port 0/3/1 to 0/3/16 in batches, telephonenumber of the user from 83110001 to 83110016.

NOTE

l To configure the PSTN data of a single user, run the sippstnuser add command.

l To configure the PSTN data of multiple users in batches, run the sippstnuser batadd command.huawei(config)#esl userhuawei(config-esl-user)#sippstnuser batadd 0/3/1 0/3/16 0 telno 83110001

10. Change the call priority of the PSTN user.Configure the call priority of the user on port 0/3/1 to Cat2 and the users of 0/3/2 to 0/3/16to Cat3 (Default).huawei(config-esl-user)#sippstnuser attribute set 0/3/1 priority cat2huawei(config-esl-user)#quit

11. Modify the attributes of all the PSTN ports so that the PSTN ports support the polarityreversal.Modify the attributes of the PSTN port 0/3/1 to 0/3/16 so that the PSTN ports supports thepolarity reversal.huawei(config)#pstnporthuawei(config-pstnport)#pstnport attribute batset 0/3/1 0/3/16 reverse-pole-pulse enablehuawei(config-pstnport)#quit


----End




vlan 200 smartport vlan 200 0/19 0dba-profile add profile-name VoIP type3 assure 15360 max 30720ont-lineprofile gpon profile-id 10tcont 2 dba-profile-name VoIPgem add 0 eth tcont 5 priority-queue 3 cascade ongem add 1 eth tcont 5 priority-queue 3 cascade onmapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 200commitquitinterface gpon 0/3port 1 ont-auto-find enabledisplay ont autofind 1ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id



9-67

10 ont alarm-profile 1 1 profile-id 1quitvlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitinterface gpon 0/3ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8quitservice-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 1 vlan 200 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

Configure the ONU.vlan 200 smartport vlan 200 0/0 0interface vlanif 200ip address 17.10.10.10 24quitvoipip address media 17.10.10.10 17.10.10.1ip address signaling 17.10.10.10quitip route-static 200.200.200.0 24 17.10.10.1interface sip 0if-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 1resetquitesl usersippstnuser batadd 0/3/1 0/3/16 0 telno 83110001sippstnuser attribute set 0/3/1 priority cat2quitpstnportpstnport attribute batset 0/3/1 0/3/16 reverse-pole-pulse enablequitsave

9.5 Configuring the FTTM ServiceIn the FTTM network, the ONU, functioning as a cell backhaul unit (CBU), is connected to the2G or 3G base station in various modes. The OLT connects the MA5612/MA5628 to the basestation controller (BSC) or radio network controller (RNC), and transmits signals to the upper-layer network. In this way, the ONU implements the FTTM network application over the 2G or3G network.

ContextNOTE

The PTN refer to the CX 600 unless otherwise specified.

9.5.1 Configuring FTTM Clock SynchronizationThis topic describes the concept and principle of clock synchronization in FTTM network, clocksynchronization solutions supported by devices, and configuration differences.

9.5.2 Configuring FTTM Network Protection


Configuration Guide


Issue 04 (2011-04-27)

In the FTTM application, Type B protection is recommended between the ONU and the OLT,and link aggregation protection or STM-1 dual protection are recommended for upstream links.

9.5.3 Configuring the Native TDM Base station access Service (SDH-based)The ONU is connected to the 2G or 3G base station in the TDM E1 mode and the OLT in theNative TDM mode. The OLT is connected upstream to the SDH network through the E1 orSTM-1 port, carrying the traditional circuit switched service over the GPON network.

9.5.4 Configuring the TDM PWE3 Base station access Service on the OLT (MPLS-based)The ONU accesses the 2G/3G base station through the E1 port and sends the TDM servicepackets to the OLT through native TDM. The OLT restores the TDM signals, starts the TDMPWE3, and then sends the TDM signals to the MPLS network and peer PTN through the GEport. In this way, the traditional circuit switched service is implemented over the GPON network.The ONUs support this service are MA5612 and MA5628.

9.5.5 Configuring the TDM PWE3 Base station access Service on the OLT (IP-based)The ONU accesses the 2G/3G base station through the E1 port and sends the TDM servicepackets to the OLT through native TDM. The OLT restores the TDM signals, starts the TDMPWE3, and then sends the TDM signals to the IP network and peer PTN through the GE port.In this way, the traditional circuit switched service is implemented over the GPON network. TheONUs support this service are MA5612 and MA5628.

9.5.6 Configuring the ETH PWE3 Base station access Service on the OLTThe ONU accesses the 3G base station through the FE/GE port and sends the ETH service packetsto the OLT through GPON. The OLT restores the ETH packets, starts the ETH PWE3, and thensends the ETH packets to the IP network and peer PTN through the GE/10GE port. In this way,the ETH service is implemented over the GPON network. The ONUs support this service areMA5612 and MA5628.

9.5.7 Configuring the QinQ Private Line Base station access Service for the OLTThe ONU is connected to the IP-based station through the FE/GE port and the OLT transmitsthe QinQ private line service to the MAN device, implementing the base station access service.The ONUs support this service are MA5612 and MA5628.

9.5.1 Configuring FTTM Clock SynchronizationThis topic describes the concept and principle of clock synchronization in FTTM network, clocksynchronization solutions supported by devices, and configuration differences.

9.5.1.1 Overview of FTTM Clock SynchronizationThis topic describes the clock synchronization concept, clock synchronization solutionssupported by the system, and solution comparison. Proper clock synchronization solutions areselected for FTTM networks based on base station type and equipment layout.

9.5.1.2 Configuring BITS Clock SynchronizationThe OLT receives the clock through the BITS and transmits the clock to the ONU through thePON line and then downstream to the base station, implementing clock synchronization of theentire network.

9.5.1.3 Configuring E1/STM-1 Line Clock SynchronizationWhen optical line terminals (OLTs) access a base station that requires only frequencysynchronization, such as GSM/WCDMA, and when OLTs are connected upstream to thesynchronous digital hierarchy (SDH) network by using the E1/STM-1 port, the E1/STM-1 lineclock can be used for clock synchronization.

9.5.1.4 Configuring Ethernet Clock SynchronizationWhen optical line terminals (OLTs) access a base transceiver station (BTS) that requires onlyfrequency synchronization, such as GSM/WCDMA and when the OLTs are connected upstream



9-69

to the packet switched network (PSN) by using the GE/10GE port, the clock can be recoveredfrom the bit streams on the Ethernet link, implementing synchronization between over the entirenetwork.

9.5.1.5 Configuring 1588V2 Clock SynchronizationIn the base stations that require time synchronization, such as CDMA2000/TD-SCDMA/LTE,the OLT brings 1588V2 clocks in 1588V2 time injection or end-to-end (E2E) 1588V2 mode.The OLT transmits the clocks to the ONU through GPON lines and then downstream to the basestation, implementing clock synchronization of the entire network.

9.5.1.1 Overview of FTTM Clock SynchronizationThis topic describes the clock synchronization concept, clock synchronization solutionssupported by the system, and solution comparison. Proper clock synchronization solutions areselected for FTTM networks based on base station type and equipment layout.

Clock SynchronizationIn a narrow sense, clock synchronization refers to frequency synchronization and timesynchronization refers to frequency and phase synchronization. In a broad sense, clocksynchronization includes frequency synchronization and phase synchronization. Unlessotherwise stated, clock synchronization refers to frequency synchronization and phasesynchronization.

Clock synchronization means that all digital devices running in the communications networktrace the same average rate so that the written clock rate and the read clock rate are maintainedwithin the same error range, ensuring that data is correctly transmitted and processed.

In a traditional communications network architecture, the TDM service of the fixed network ismainly voice service. Cumulative inconsistency between the clocks at both ends of the bearernetwork over a long time causes frame slip. On a communications network, the wirelessapplication has the most rigorous requirements on the clock frequency. The frequencies ofdifferent base stations must be synchronized within a specified precision. Otherwise, re-syncoccurs during the base station switching.

The purpose of clock synchronization is to control the occurrence of controlled slip and todecrease the slip, burst bit error, sudden phase change, jitter, or drift of various device signalsin the telecommunications service network to the minimum, ensuring the high-quality and high-efficiency running of the telecommunications service network.

Clock Synchronization SolutionFigure 9-7 shows a clock synchronization solution in an FTTM network. The clocksynchronization principle is as follows: The clock obtained by the OLT serves as the clock sourceand transmits signals to the base station through xPON lines.


Configuration Guide


Issue 04 (2011-04-27)

Figure 9-7 Clock synchronization solution in an FTTM network

The figure shows that the OLT can obtain the following clock sources:l BITS clock sourcel E1/STM-1 line clock sourcel Synchronous Ethernet line clockl 1588V2 clock source, including the following:

– 1588V2 time injection– P2P 1588V2

l Internal clock sources are not recommended because they are in free oscillation state anddo not have advantages in precision.

Comparison of Clock Synchronization SolutionTable 9-5 shows a clock synchronization solution in an FTTM network.



9-71

Table 9-5 Comparison of clock synchronization solution

SynchronizationSolution

Usage Scenario Advantage Limitation orHardwareRequirements

BITS clock Applies to the basestation that requiresonly frequencysynchronization,such as GSM/WCDMA. Inaddition, the OLTmust have BITSclock inputresources.

1. Clock precisionmeets thefollowingrequirements:l G.8262

features whenCKMCstratum-3clock units areconfigured

l EECspecificationsdefined in G.8261 when nostratum-3clock units areconfigured

2. No requirementson delay, jitter, orpack loss of aPSN network

1. The OLT musthave BITS clockresources.

2. BITS clockscannot provideindependentservice clocks foreach E1 channel.

3. BITS clockssupport onlyfrequencysynchronization.

Board that supportthis feature:H801CITD(configured with theH801BITSBdaughter board)


Configuration Guide


Issue 04 (2011-04-27)



E1/STM-1 line clock Applies to the BTSthat requires onlyfrequencysynchronization,such as GSM/WCDMA. Inaddition, the OLTcan directly connectto an SDH network.




2. E1/STM-1 lineclocks are allobtained fromphysical lineclocks and theyhave the bestperformance interms of stabilityand reliability.

1. In E1/STM-1upstreamtransmission, theOLT must be inthe same office asSDH equipment.

2. E1/STM-1 lineclocks supportonly frequencysynchronization.

Boards that supportthis feature:l STM-1 line

clock:H801TOPA(configured withthe H801CSSAdaughter board)or H801TOPA(configured withthe H801O2CEdaughter board).

l E1 line clock:H801TOPA(configured withthe H801NH1Adaughter board)or H801TOPA(configured withthe H801EH1Adaughter board).



9-73



Ethernet clock Applies to the BTSthat requires onlyfrequencysynchronization,such as GSM/WCDMA. Inaddition, the OLTupstream networkhas the capability ofsynchronizingEthernet clocks.




2. No requirementson delay, jitter, orpack loss of aPSN network

1. Ethernet clocksrequire that MANPSN networkshave thecapability ofsynchronizingEthernet clocks.

2. Ethernet clockssupport onlyfrequencysynchronization.

Boards that supportthis feature:H801X2CS,H801GSCA,H801GICK, andH801SPUA

1588V2 clocksynchronization:time injection

Applies to the BTSthat requires timesynchronization,such as CDMA2000/TD-SCDMA/LTE.When the OLTupstream networkdoes not support1588V2, thissolution isrecommended.

1. This solutionsupports timesynchronizationand frequencysynchronizationand provideshigh-precisiontime. The clockquality meets G.813 and G.8262specifications.

2. This solutiondoes not haverequirements onPSN networks.

A 1588V2 servermust be at the sameplace as the OLT.


Configuration Guide


Issue 04 (2011-04-27)



1588V2 clocksynchronization:end-to-end 1588V2

Applies to the BTSthat requires timesynchronization,such as CDMA2000/TD-SCDMA/LTE.When the OLTupstream networksupports 1588V2 hopby hop, this solutionis recommended.

1. This solutionsupports timesynchronizationand frequencysynchronizationand provideshigh-precisiontime. The clockquality meets G.813 and G.8262specifications.

2. The entirenetwork sharesthe same timeequipment.

3. No additionalequipment isrequired at theOLT location.

The upstreamnetwork of the OLTmust support1588V2 hop by hop.

9.5.1.2 Configuring BITS Clock SynchronizationThe OLT receives the clock through the BITS and transmits the clock to the ONU through thePON line and then downstream to the base station, implementing clock synchronization of theentire network.

Application ContextAs shown in Figure 9-8, the OLT receives the clock from the BITS and the clock share the sameclock source with the BSC/RNC. Then the OLT transmits the clock to the ONU through thePON line clock. After recovering the clock, the ONU transmits the clock to the base stationthrough the E1 or FE/GE port.

Figure 9-8 BITS clock synchronization



9-75

Prerequisitel The clock daughter board CKMC of the SCU board must be in position.l The OLT must have the BITS clock input resource.l The CITD board (its BITS clock daughter board must be in position) must work in the

normal state.

Data Plan

Item Data

CITD board Ports: 0/0/0 and 0/0/1Clock type: BITS 2 MHz, 120 ohmsClock priority: p0 > p1

GIU upstream board Port: 0/19/0

E1 port of the ONU 0/1/0

ETH port of theONU

0/4/0

Configuration Concept1. The OLT uses the BITS line clock as the system clock.2. The system clock is issued to the ONU through the optical path of the PON service board.3. The ONU uses the line clock of the PON upstream port as the system clock.4. The E1 Tx clock of the ONU is synchronized to the system clock of the ONU.

Procedure

Step 1 Configure the OLT-side clock.1. Configure a system clock source.

Run the clock source command to configure BITS_IN ports 0/0/0 and 0/0/1 on the CITDboard as the system clock sources. Set their IDs to 0 and 1 respectively.

The clock module automatically judges the types of the specified clock sources (BITS),and sends them according to their priorities to the clock module, serving as clock sourcesfor phase lock.

huawei(config)#clock source 0 0/0/0huawei(config)#clock source 1 0/0/1

2. Set the priority of the system clock source.

Run the clock priority command to configure the priorities of clock sources 0 and 1 to p0> P1.

huawei(config)#clock priority system 0/1


Configuration Guide


Issue 04 (2011-04-27)

3. Query the configuration and status of the system clock source.

Run the display clock source command to query the configuration and status of the clocksource. Ensure that the configuration information about the system clock is matching andthe status is normal.

Step 2 Configure the ONU-side clock.1. Configure the PON line clock source as the system clock.

The system clock of the OLT is issued to the ONU through the optical path of the PONport, implementing the clock synchronization between the OLT and the ONU.

a. Run the clock source command to configure the clock recovered from the PONupstream port as the system clock source of the MA5612.

b. Run the clock priority command to configure the priority of the clock source.huawei(config)#clock source 0 0/0/0 Clock source set succeeded

huawei(config)#clock priority system 0

2. (Optional) Configure the system clock as the Tx clock of the E1 port.

NOTEThis step is required only when the base station is connected to the ONU through the E1 port. When thebase station is connected to the ONU through the FE/GE port, this step is not required. By default, it isthe system clock and cannot be modified.

a. Run the interface tdm command to enter the E1 port configuration mode.b. Run the tx clock or port portid udt system command to configure the Tx clock of

the port as the system clock.c. Run the display port state command to query the Tx clock of the E1 port.huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 udt systemhuawei(config-if-tdm-0/1)#display port state 0 --------------------------------------- Port : 0 State : normal Mode : UDT Code : HDB3 Looptype : - Timeslot : - Clock : system CRC4 : - Signaling : - ESF : - Impedance : 120 Ohm ---------------------------------------

3. Query the configuration and status of the system clock source.Run the display clock source command to query the configuration and status of the systemclock source.huawei(config-if-tdm-0/1)#quithuawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES line 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- --- 5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- ---



9-77

7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

----End

ResultAfter the FTTM service configuration is complete, use the test meter to perform tests on the E1/ETH access port of the ONU and the upstream GE/10GE port. The long-term bit error ratio(BER) and delay should be able to meet the requirements for actual applications.

9.5.1.3 Configuring E1/STM-1 Line Clock SynchronizationWhen optical line terminals (OLTs) access a base station that requires only frequencysynchronization, such as GSM/WCDMA, and when OLTs are connected upstream to thesynchronous digital hierarchy (SDH) network by using the E1/STM-1 port, the E1/STM-1 lineclock can be used for clock synchronization.

Application ContextAs shown in Figure 9-9, the OLT recovers the clock from the E1/STM-1 line. This clock istransmitted by the BSC/RNC through the SDH network and then transmitted to the ONU throughthe GPON line clock. After recovering the clock, the ONU transmits the clock to the base stationthrough the E1 line.

Figure 9-9 E1/STM-1 line clock synchronization

PrerequisiteThe clock daughter board CKMC of the SCU board must be in position.


Configuration Guide


Issue 04 (2011-04-27)

Data Plan

Item Data

TOPA board Port ID: 0/5/0Daughter board type:l When the OLT and the ONU adopt the Native TDM mode, NH1A

provides the E1 port and O2CE provides the STM-1 port.l When the OLT and the ONU adopt the TDM PWE3 mode, EH1A

provides the E1 port and CSSA provides the STM-1 port.


Configuration Concept1. The OLT traces the upstream E1/STM-1 line clock of the TOPA board as the system clock.2. The system clock is issued to the ONU through the optical path of the GPON service board.3. The ONU uses the line clock of the GPON upstream port as the system clock.4. The E1 Tx clock of the ONU is synchronized to the system clock of the ONU.

Procedure


Run the clock source command to configure the line clock of E1/STM-1 port 0/5/0 on theTOPA board as the system clock source. Set the clock source ID to 0.

The clock module automatically judges the types of the specified clock sources (E1/STM-1)and sends them according to their priority to the clock module, serving as the clock sourcesfor phase lock.

huawei(config)#clock source 0 0/5/0

2. Set the priority of the system clock source.

Run the clock priority command to configure clock source 0 to have the highest priority.

huawei(config)#clock priority system 0

3. Query the configuration and status of the system clock source.


Step 2 Configure the ONU-side clock.1. Configure the GPON line clock source as the system clock.

The system clock of the OLT is issued to the ONU through the optical path of the GPONport, implementing the clock synchronization between the OLT and the ONU.

a. Run the clock source command to configure the clock recovered from the GPONupstream port as the system clock source of the MA5612.



9-79


huawei(config)#clock priority system 02. Configure the system clock as the Tx clock of the E1 port.


the port as the system clock.c. Run the display port state command to query the Tx clock of the E1 port.huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 udt systemhuawei(config-if-tdm-0/1)#display port state 0 --------------------------------------- Port : 0 State : normal Mode : UDT Code : HDB3 Looptype : - Timeslot : - Clock : system CRC4 : - Signaling : - ESF : - Impedance : 120 Ohm ---------------------------------------

3. Query the configuration and status of the system clock source.Run the display clock source command to query the configuration and status of the systemclock source.huawei(config-if-tdm-0/1)#quithuawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES line 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- --- 5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- --- 7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

----End

ResultAfter the FTTM service configuration is complete, use the test meter to perform tests on the E1port of the ONU and the upstream E1/STM-1 port of the TOPA board. The long-term bit errorratio (BER) and delay should be able to meet the application requirements.

9.5.1.4 Configuring Ethernet Clock SynchronizationWhen optical line terminals (OLTs) access a base transceiver station (BTS) that requires onlyfrequency synchronization, such as GSM/WCDMA and when the OLTs are connected upstreamto the packet switched network (PSN) by using the GE/10GE port, the clock can be recovered


Configuration Guide


Issue 04 (2011-04-27)

from the bit streams on the Ethernet link, implementing synchronization between over the entirenetwork.

Application Context

As shown in Figure 9-10, the OLT receives the clock from the upstream synchronous Ethernetport. (This clock is transmitted through the PSN network and must be supported by allintermediate nodes.) Then the clock is transmitted to the ONU through the PON line clock. Afterrecovering the clock, the ONU transmits the clock to the base station through the synchronousEthernet or independent clock port.

Figure 9-10 Ethernet clock synchronization

Prerequisite

l The clock daughter board CKMC of the SCU board must be in position.l The GIU upstream board must be GICK/GSCA (GE port) or X2CS (10GE port).l The upstream MAN PSN of the OLT must feature the capability of Ethernet

synchronization.

Data Plan

Item Data

GIU UpstreamBoards

Port: 0/19/0


ETH port of theONU

0/4/0

Configuration Concept1. The OLT uses the synchronous Ethernet clock of the upstream slot as the system clock.2. The system clock is issued to the ONU through the optical path of the PON service board.



9-81

3. The ONU uses the line clock of the PON upstream port as the system clock.4. The Tx clock of the E1 or FE/GE port on the ONU is synchronized to the system clock of

the ONU.

Procedure


Run the clock source command to configure the line clock of the GE/10GE port on theGIU board as the system clock source. Set the clock source ID to 0.

The clock module automatically judges the types of the specified clock sources (ETH), andsends them according to their priorities to the clock module, serving as clock sources forphase lock.

huawei(config)#clock source 0 0/19/02. Set the priority of the system clock source.

Run the clock priority command to configure clock source 0 to have the highest priority.

huawei(config)#clock priority system 03. Query the configuration and status of the system clock source.


Step 2 Configure the ONU-side clock.1. Configure the PON line clock source as the system clock.

The system clock of the OLT is issued to the ONU through the optical path of the PONport, implementing the clock synchronization between the OLT and the ONU.

a. Run the clock source command to configure the clock recovered from the PONupstream port as the system clock source of the MA5612.


huawei(config)#clock priority system 02. (Optional) Configure the system clock as the Tx clock of the E1 port.

NOTEThis step is required only when the base station is connected to the ONU through the E1 port. When thebase station is connected to the ONU through the FE/GE port, this step is not required. By default, it isthe system clock and cannot be modified.


the port as the system clock.c. Run the display port state command to query the Tx clock of the E1 port.huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 udt systemhuawei(config-if-tdm-0/1)#display port state 0 --------------------------------------- Port : 0


Configuration Guide


Issue 04 (2011-04-27)

State : normal Mode : UDT Code : HDB3 Looptype : - Timeslot : - Clock : system CRC4 : - Signaling : - ESF : - Impedance : 120 Ohm ---------------------------------------

3. Query the configuration and status of the system clock source.Run the display clock source command to query the configuration and status of the systemclock source.huawei(config-if-tdm-0/1)#quithuawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES line 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- --- 5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- --- 7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

----End


9.5.1.5 Configuring 1588V2 Clock SynchronizationIn the base stations that require time synchronization, such as CDMA2000/TD-SCDMA/LTE,the OLT brings 1588V2 clocks in 1588V2 time injection or end-to-end (E2E) 1588V2 mode.The OLT transmits the clocks to the ONU through GPON lines and then downstream to the basestation, implementing clock synchronization of the entire network.

Background Information1588V2 is a time synchronization technology. The quality of clock transmitted by 1588V2 meetsthe stratum 3 clock requirement and the time quality reaches a submicrosecond precision, whichsolves the time and clock synchronization problems of the user. In addition, using 1588V2 canbetter reduce user's investment. Therefore, 1588V2 is applicable to the base station accessservices.

Application ContextAs shown in Figure 9-11, the OLT is injected with time through the 1588V2 server or directlythrough the 1PPS+ToD interface (the time source is obtained from the GPS). Then, the OLTtransmits the time signals to the ONU by means of the GPON time synchronization technology.



9-83

After recovering the time signals, the ONU transmits them to the base station by means of the1588V2 or time interface.

This scheme has no additional requirement for the PSN network, but the OLT must be deployedwith a 1588V2 server. Therefore, this scheme is recommended when the upstream network ofthe OLT does not support 1588V2.

Figure 9-11 1588V2 time injection

As shown in Figure 9-11, the OLT obtains the 1588V2 time by using the upstream networkinterface (the time is transmitted by the upstream network hop by hop). Then, the OLT transmitsthe time to the ONU through the GPON line. After recovering the time, the ONU transmits thetime to the base station by means of the 1588V2 or time interface.

This scheme does not require a 1588V2 server on the OLT. Therefore, this scheme isrecommended when the upstream network of the OLT supports 1588V2 hop by hop.

Figure 9-12 E2E 1588V2

Prerequisite

l The clock daughter board CKMC of the SCU control board must be in position.l The GE 1588V2 upstream board GICK must be in position.


Configuration Guide


Issue 04 (2011-04-27)

l If the time is injected by using the 1PPS+ToD interface, the CITD board (with the BITSBdaughter board) must be in position.

l The GPON service board must be GPBD.

Data Plan

Item Data

1588V2 clocksource

When the time is injected from the BITS IN port of the CITD boardto the 1PPS+ToD interface:l BITS IN ports of the CITD board: 0/0/0 and 0/0/1l Clock priority: p0 > p1When the 1588V2 clock packets are injected by using the GICK boardor the 1588V2 clock packets of the upstream network are transparentlytransmitted:l GE ports of the GICK board: 0/19/0 and 0/19/1l Clock priority: p0 > p1


ETH port of theONU

0/4/0

Configuration Concept1. On the OLT side, select the 1PPS+ToD clock signal or clock signal recovered from 1588V2

packets as the system clock source.2. The system clock is issued to the ONU through the optical path of the PON service board.3. The ONU uses the 1588V2 clock of the PON upstream port as the system clock.4. The Tx clock of the E1 or FE/GE port on the ONU is synchronized to the system clock of

the ONU.5. The ONU synchronizes the clock and time with the base station in the following three

modes:l The Tx clock of the E1 or FE/GE port on the ONU is synchronized to the system clock

of the ONU and then transmitted to the base stations for clock synchronization.l The ONU transmits 1588V2 packets to the base station by using the FE/GE port.l The ONU provides independent time signals to the base station by using the clock output

interface.

Procedurel Configure the OLT-side clock.

1. Add a 1588V2 clock source.

Run the ptp source command to specify the index and priority of the 1588V2 clocksource.

The system supports up to ten 1588V2 clock sources and specifies different prioritiesfor different clock sources. Priorities p0-p9 are in descending order.



9-85

– When the 1PPS+ToD clock signal obtained from the GPS is injected through theBITS IN port of the CITD board, the configuration command is as follows:huawei(config)#ptp source 0 0/0/0 p0huawei(config)#ptp source 1 0/0/1 p1

– When the 1588V2 clock packets are injected through the GICK board or the1588V2 clock packets of the upstream network are transparently transmitted, theconfiguration command is as follows:huawei(config)#ptp source 0 0/19/0 p0huawei(config)#ptp source 1 0/19/1 p1

2. (Optional) Configure the attributes of the 1588 V2 clock source.

When the default attributes of the 1588V2 clock source do not meet the actualrequirement, run the ptp config command to modify the attributes.

The default attributes of the 1588V2 clock source are as follows:– Interval for transmitting the request packet: 7 (that is, 1/8s)– PTP mode: E2E– PTP encapsulation type: PTP ETH encapsulation– Asymmetrical transmission windage of PTP optical fiber: windage mode 0

(calculated according to length), windage direction 0 (positive direction), windagevalue 0.

– VLAN ID carried in the PTP packet of the port: 1– Request and response packet type: multicast

NOTEBefore modification, ensure that the attributes of the 1588V2 clock source are the same as the actualones. In this example, assume that the default attributes of the system clock source meet theapplication requirements.

3. Configure the 1588V2 clock source as the system clock source.

(1) Run the clock source command to add the 1588V2 clock source as the systemclock source.huawei(config)#clock source 0 0/19/0 1588huawei(config)#clock source 1 0/19/1 1588

(2) Run the clock priority command to configure the priority of the 1588V2 clocksource.huawei(config)#clock priority system 0/1

4. Query the configuration and status of the 1588V2 clock source and system clocksource.– Run the display ptp source command to query the status of the 1588V2 clock

source.– Run the display clock source command to query the configuration and status of

the system clock source.huawei(config)#display ptp source --------------------------------------------------- Index Board Source State Priority Selected --------------------------------------------------- 0 H801GICK 0/19/ 0 Normal 0 YES 1 H801GICK 0/19/ 1 Normal 1 2 --- -/ -/ - --- --- --- 3 --- -/ -/ - --- --- --- 4 --- -/ -/ - --- --- --- 5 --- -/ -/ - --- --- --- 6 --- -/ -/ - --- --- --- 7 --- -/ -/ - --- --- ---


Configuration Guide


Issue 04 (2011-04-27)

8 --- -/ -/ - --- --- --- 9 --- -/ -/ - --- --- --- ---------------------------------------------------huawei(config)#display clock source system ----------------------------------------------------------------------- Index Board Source Clk-type State Priority QL Selected ----------------------------------------------------------------------- 0 H801GICK 0/19/ 0 --- Normal 0 --- YES 1 H801GICK 0/19/ 1 --- Normal 1 --- --- -----------------------------------------------------------------------

l Configure the ONU-side clock (the clock is connected to the base station by using E1ports to implement clock synchronization).This configuration is applicable to clock synchronization in the base station whereasynchronous base station technologies (GSM/WCDMA is a representative) are adopted.1. Configure the PON line clock source as the system clock.

The system clock of the OLT is issued to the ONU through the optical path of thePON port, implementing the clock synchronization between the OLT and the ONU.

(1) Run the clock source command to configure the clock recovered from the PONupstream port as the system clock source of the MA5612.

(2) Run the clock priority command to configure the priority of the clock source.huawei(config)#clock source 0 0/0/0 Clock source set succeeded

huawei(config)#clock priority system 02. Configure the system clock as the Tx clock of the E1 port.

(1) Run the interface tdm command to enter the E1 port configuration mode.(2) Run the tx clock or port portid udt system command to configure the Tx clock

of the port as the system clock.(3) Run the display port state command to query the Tx clock of the E1 port.huawei(config)#interface tdm 0/1huawei(config-if-tdm-0/1)#port 0 udt systemMA5612(config-if-tdm-0/1)#display port state 0 --------------------------------------- Port : 0 State : normal Mode : UDT Code : HDB3 Looptype : - Timeslot : - Clock : system CRC4 : - Signaling : - ESF : - Impedance : 120 Ohm ---------------------------------------

3. Query the configuration and status of the system clock source.Run the display clock source command to query the configuration and status of thesystem clock source.huawei(config-if-tdm-0/1)#quithuawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES line 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- ---



9-87

5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- --- 7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

l Configure the ONU-side clock (the clock is connected to the base station by using FE/GE port to implement time synchronization).This configuration is applicable to time synchronization in the base station wheresynchronous base station technologies (TDS-CDMA/CDMA2000/LTE is a representative)are adopted. The base station must provide ETH ports and support 1588V2 packets.1. Add a 1588V2 clock source.

The 1588V2 clock is issued to the ONU through the optical path of the PON port,implementing the clock synchronization between the OLT and the ONU.

(1) Run the ptp device-type command to modify the PTP device type to BC.Boundary clock (BC): The device has two or more physical ports forcommunicating with the network. Each physical port functions as an ordinaryclock (OC) port. A BC can be used to connect multiple sub-domains and can beconsidered as a network device such as repeater, switch, and router.huawei(config)#ptp device-type bc

(2) Run the ptp port enable command to enable the 1588V2 function on the PONport and the ETH port.huawei(config)#ptp port 0/0/0 enablehuawei(config)#ptp port 0/4/0 enable

(3) (Optional) Configure the attributes of the 1588 V2 clock source.When the default attributes of the 1588V2 clock source do not meet the actualrequirement, run the ptp port command to configure associated parameters ofthe 1588V2 protocol.The default attributes of the 1588V2 clock source are as follows:– Interval for transmitting the request packet: 7 (that is, 1/8s)– PTP mode: E2E– PTP encapsulation type: PTP ETH encapsulation– Asymmetrical transmission windage of PTP optical fiber: windage mode 0

(calculated according to length), windage direction 0 (positive direction),windage value 0.

– VLAN ID carried in the PTP packet of the port: 1– Request and response packet type: multicast

NOTEBefore modification, ensure that the attributes of the 1588V2 packets are the same as the actualones in the base station. In this example, assume that the default attributes of the 1588V2packets meet the application requirements.

(4) Run the ptp source command to specify the index and priority of the 1588V2clock source.The system supports up to ten 1588V2 clock sources and specifies differentpriorities for different clock sources. Priorities p0-p9 are in descending order.huawei(config)#ptp source 0 0/0/0 p0


(1) Run the clock source command to add the 1588V2 clock source as the systemclock source.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#clock source 0 1588 0/0/0(2) Run the clock priority command to configure the priority of the 1588V2 clock

source.huawei(config)#clock priority system 0



the system clock source.huawei(config)#display ptp source -------------------------------------------------------------- Index config source state priority output lock state -------------------------------------------------------------- 0 YES 0/ 0/ 0 Normal 0 YES successful 1 NO -/ -/ - --- --- --- --- 2 NO -/ -/ - --- --- --- --- 3 NO -/ -/ - --- --- --- --- 4 NO -/ -/ - --- --- --- --- 5 NO -/ -/ - --- --- --- --- 6 NO -/ -/ - --- --- --- --- 7 NO -/ -/ - --- --- --- --- 8 NO -/ -/ - --- --- --- --- 9 NO -/ -/ - --- --- --- --- --------------------------------------------------------------huawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES 1588 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- --- 5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- --- 7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

l Configure the ONU-side clock (the ONU provides the base station with a clock byusing the clock interface on the panel to implement time synchronization).This configuration is applicable to time synchronization in the base station wheresynchronous base station technologies (TDS-CDMA/CDMA2000/LTE is a representative)are adopted. If a base station provides the ETH port but does not support 1588V2 packets,the ONU outputs 1PPS+ToD time for the base station synchronization.1. Add a 1588V2 clock source.

The 1588V2 clock is issued to the ONU through the optical path of the PON port,implementing the clock synchronization between the OLT and the ONU.(1) Run the ptp device-type command to modify the PTP device type to boundary

clock (BC).Boundary clock (BC): The device has two or more physical ports forcommunicating with the network. Each physical port functions like an OC port.A BC can be used to connect multiple sub-domains and can be considered as anetwork device such as regenerator, switch, and router.huawei(config)#ptp device-type bc

(2) Run the ptp port enable command to enable the 1588V2 function on the PONport.



9-89

huawei(config)#ptp port 0/0/0 enable(3) Run the ptp source command to specify the index and priority of the 1588V2

clock source.The system supports a maximum of ten 1588V2 clock sources and specifiesdifferent priorities for different clock sources. Priorities p0-p9 are in descendingorder.huawei(config)#ptp source 0 0/0/0 p0


(1) Run the clock source command to add the 1588V2 clock source as the systemclock source.huawei(config)#clock source 0 1588 0/0/0

(2) Run the clock priority command to configure the priority of the 1588V2 clocksource.huawei(config)#clock priority system 0



the system clock source.huawei(config)#display ptp source -------------------------------------------------------------- Index config source state priority output lock state -------------------------------------------------------------- 0 YES 0/ 0/ 0 Normal 0 YES successful 1 NO -/ -/ - --- --- --- --- 2 NO -/ -/ - --- --- --- --- 3 NO -/ -/ - --- --- --- --- 4 NO -/ -/ - --- --- --- --- 5 NO -/ -/ - --- --- --- --- 6 NO -/ -/ - --- --- --- --- 7 NO -/ -/ - --- --- --- --- 8 NO -/ -/ - --- --- --- --- 9 NO -/ -/ - --- --- --- --- --------------------------------------------------------------huawei(config)#display clock source --------------------------------------------------------------- Index Config Type Source State Priority Output --------------------------------------------------------------- 0 YES 1588 0/ 0/ 0 Normal 0 YES 1 NO -- -/ -/ - --- --- --- 2 NO -- -/ -/ - --- --- --- 3 NO -- -/ -/ - --- --- --- 4 NO -- -/ -/ - --- --- --- 5 NO -- -/ -/ - --- --- --- 6 NO -- -/ -/ - --- --- --- 7 NO -- -/ -/ - --- --- --- 8 NO -- -/ -/ - --- --- --- 9 NO -- -/ -/ - --- --- --- ---------------------------------------------------------------

4. Configure the time output mode of the clock output interface.

The MA5612 provides an independent output clock through time output port 0 on thepanel. Configure the clock output signal to 2 MHz and time signal to 1pps+ubx.

NOTEConfigure the clock/time output mode according to actual conditions.

huawei(config)#clock bits-type 0 clock 2mhz BITS clock parameter set successfully


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#clock bits-type 0 time 1pps protocol ubx BITS clock parameter set successfully

----End


9.5.2 Configuring FTTM Network ProtectionIn the FTTM application, Type B protection is recommended between the ONU and the OLT,and link aggregation protection or STM-1 dual protection are recommended for upstream links.

Background InformationThe FTTM network can be protected on the device layer or service layer. There are four mainprotection modes:l Type B protection:

– Type B protection: Two PON ports on the same OLT protect each other. When one ofthe PON ports fails, the system automatically switches the services to the other PONport. Based on this protection mode, the protection in case of failure of the master porton one OLT is implemented.

l STM-1 protect group: Two upstream STM-1 ports can be configured as protect members.l Link aggregation: The link aggregation group aggregates multiple Ethernet ports as an

aggregation group to increase the bandwidth and share the incoming/outgoing load of eachmember port. At the same time, the ports in an aggregation group back up each other, whichincreases the link security.

Application ContextAs shown in Figure 9-13,l Type B networking mode can be adopted between the OLT and the ONU for redundancy

backup.l When the OLT transmits services upstream to the SDH network through the STM-1 ports,

the STM-1 port protect group can be adopted for redundancy backup.l When the OLT transmits services upstream to the SDH network through the GE/10GE

ports, link aggregation mode between GE/10GE ports can be adopted for redundancybackup.

In actual applications, select the proper protection mode according to the actual network.



9-91

Figure 9-13 FTTM network protection

Procedurel Configure Type B redundancy backup.

1. Run the protect-group command to add a protect group.Pay attention to the following points during the configuration:– Configure protect-target to gpon-uni-port.– The working mode of the GPON port protect group can be only timedelay.

2. Run the protect-group member command to add members to the protect group.Pay attention to the following points during the configuration:– When adding members to the protect group, add a working member, and then add

a protection member.– The member ports can be ports on different boards, but the board types must be

the same.3. Run the protect-group enable command to enable the protect group.4. Run the display protect-group command to query the information about the protect

group.l Configure link aggregation.

1. Run the link-aggregation command to add a link aggregation group.Configuration description: When you run the link-aggregation command, if frameid/slotid is entered twice, inter-board aggregation is configured; if frameid/slotid isentered only once, intra-board aggregation is configured.

2. (Optional) Run the link-aggregation add-member command to add members to theaggregation group.Configuration description: This step is optional and is recommended if you need tofurther increase the bandwidth of an aggregation group or improve the link reliability.

3. Run the display link-aggregation command to query the information about theaggregation group.

l Configure an STM-1 upstream port protect group.

1. Run the protect-group add a protect group.Pay attention to the following points during the configuration:– Configure protect-target to stm-nni-port.


Configuration Guide


Issue 04 (2011-04-27)

– The working mode of the STM-1 port protect group can be only unidirection.2. Run the protect-group member command to add members to the protect group.

Pay attention to the following points during the configuration:– When adding members to the protect group, add a working member, and then add

a protection member.– The member ports can be ports on different boards, but the board types must be

the same.3. Run the protect-group enable command to enable the protect group.4. Run the display protect-group command to query the information about the protect

group.

----End

ExampleTo configure Type B redundancy backup for ports 0/3/1 and 0/3/2 on the same GPON board ofthe OLT, so that when port 0/3/1 is faulty, the system can automatically switch the service toport 0/3/2 to continue service access, do as follows:

huawei(config)#protect-group 0 protect-target gpon-uni-port workmode timedelayhuawei(protect-group-0)#protect-group member port 0/3/1 role workhuawei(protect-group-0)#protect-group member port 0/3/2 role protecthuawei(protect-group-0)#protect-group enable

Configure link aggregation: The OLT transmits services upstream through the GIU board,upstream ports 0/19/0 and 0/19/1 on the same GIU board are configured as an upstream portaggregation group, packets are distributed to the member ports of the aggregation groupaccording to the source MAC address, and the working mode is the LACP static aggregationmode. To perform these configurations, do as follows:huawei(config)#link-aggregation 0/19 0-1 ingress workmode lacp-static

Configure an STM-1 upstream port protect group: Configure STM-1 ports 0/5/0 and 0/5/1 ofthe TOPA board as a protect group. When the protected port 0/5/0 has a fault or line fault, thesystem immediately and automatically switches the services from the faulty port to the standbyport 0/5/1.huawei(config)#protect-group 1 protect-target stm-nni-port workmode unidirectionhuawei(protect-group-0)#protect-group member port 0/5/0 role workhuawei(protect-group-0)#protect-group member port 0/5/1 role protecthuawei(protect-group-0)#protect-group enable

9.5.3 Configuring the Native TDM Base station access Service(SDH-based)

The ONU is connected to the 2G or 3G base station in the TDM E1 mode and the OLT in theNative TDM mode. The OLT is connected upstream to the SDH network through the E1 orSTM-1 port, carrying the traditional circuit switched service over the GPON network.

PrerequisiteThe corresponding hardware requirements must be met:l OLT adopting the E1 port for upstream transmission: TOPA+NH1Al OLT adopting the STM-1 port for upstream transmission: TOPA+O2CEl GPON boards: GPBC and GPBD



9-93

Service Requirementsl The E1 port is used for connecting to the 2G or 3G base station in a unified manner.

l GPON is adopted for bearing the mobile AN in a unified manner to meet mobile carriers'requirements for high bandwidth and high-density coverage of base stations.

l Make full use of existing SDH resources to transmit the TDM service with high quality.

Figure 9-14 shows an example network of the Native TDM base station access service.

The ONU is connected to the 2G or 3G base station through the E1 port to provide the TDMaccess, and then transmits the service data upstream to the GPON service board of the OLT inthe Native TDM mode. The OLT restores TDM signals, and then transmits the signals to theSDH network through the E1 port (provided by the NH1A daughter board) or STM-1 port(provided by the O2CE daughter board) of the TOPA board. In this way, the 2G or 3G basestation access service is implemented between the ONU and the OLT in the Native TDM mode.

Figure 9-14 Native TDM base station access service

Data Plan

Table 9-6 provides the data plan for the OLT, and Table 9-7 provides the data plan for the ONU.

Table 9-6 Data plan for configuring the Native TDM base station access service-OLT side

Item Data

VLAN Inband management VLAN: smart VLAN 8WARNING

When the ONU is connected to the E1 service in native TDM mode, thesystem always uses VLANs 4000–4007. Hence, these VLANs should notbe used in VLAN planning for the OLT or ONU. If these VLANs are used,ONU configuration fails. Consequently, services will be interrupted.




Configuration Guide


Issue 04 (2011-04-27)

Item Data

TOPA service board Port: 0/5/0Daughter board type: NH1A (providing E1 ports) or O2CE(providing STM-1 ports)VC12 ID: 2 (for only the STM-1 port)

DBA profile Profile name: TDMType: type1Fixed bandwidth: 32 Mbit/s

ONU line profile l Profile ID: 10l GEM port IDs: 0 and 1l T-CONT IDs: 1 and 10l Bind T-CONT 1 to the DBA profile named TDMl Bind T-CONT 10 to the DBA profile ID 1


Table 9-7 Data plan for configuring the Native TDM base station access service-ONU side

Item Data

VLAN Inband management VLAN: smart VLAN 8, adding GPONupstream port 0/0/0 to this VLAN


E1 port Port: 0/1/0Working mode of the port: UDTTransmit clock of the port: system



GPON ONU profiles include the DBA profile, line profile and alarm profile.

– DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONTis bound to a DBA profile for dynamic bandwidth allocation, improving theupstream bandwidth usage rate.


– Alarm profile: An alarm profile contains a series of alarm thresholds to measureand monitor the performance of activated ONU lines. When a statistical value



9-95

reaches the threshold, the host is notified and an alarm is reported to the log hostand the NMS.

(1) Add a DBA profile.You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to TDM, type to type1, fixed bandwidth to 32Mbit/s, and enable the bandwidth compensation.To configure the DBA profile of fixed bandwidth type to bear the TDM services,you must enable the bandwidth compensation function.huawei(config)#dba-profile add profile-name TDM type1 fix 32768 bandwidth_compensate yes

(2) Add an ONU line profile.Add GPON ONU line profile 10, bind T-CONT 10 to default DBA profile nameddba-profile_1 and T-CONT 1 to DBA profile named TDM. In this way, the T-CONT can provide flexible DBA solutions based on different configurations inthe DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 10 dba-profile-name dba-profile_1huawei(config-gpon-lineprofile-10)#tcont 1 dba-profile-name TDM

Add GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting TDM traffic streams. Bind GEM port 0 to T-CONT 10 and GEMport 1 to T-CONT 1. Configure the QoS mode to priority-queue (default) and thequeue priority to 0.

NOTE



huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 10 priority-queue 0huawei(config-gpon-lineprofile-10)#gem add 1 tdm tcont 1 priority-queue 0

Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management VLAN 8 to GEM port 0, and mapthe E1 port 1 of the ONU to GEM port 1.huawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 e1 1


(3) (Optional) Add an alarm profile.



Configuration Guide


Issue 04 (2011-04-27)





(1) Add an ONU.Connect the ONU to GPON port 0/3/1.There are two ways to add an ONU. Select either of the two ways according toactual conditions.– Add an ONU offline: If the password or SN of an ONU is obtained, you can



To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //Take MA5612 for example here. After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed.-------------------------------------- Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-07-27 16:14:33+08:00 ------------------------------------------------------------------------

huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

NOTEIf multiple ONUs of the same type are connected to a port and the same line profile or serviceprofile (for an ONT) is bound to the ONUs, you can add ONUs in batches by confirming theauto-found ONUs in batches to simplify the operation and increase the configurationefficiency. For example, the preceding command can be modified as follows: huawei(config-if-gpon-0/3)#ont confirm 1 all sn-auth snmp ont-lineprofile-id 10 desc ONU_0/3/1.

(2) (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.



9-97

huawei(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 13. Confirm that the ONU goes online normally.














Configuration Guide


Issue 04 (2011-04-27)

(1) Configure the inband management VLAN and IP address of the OLT.To log in to the ONU through Telnet and configure the ONU from the OLT, youmust configure the inband management VLANs and IP addresses of the OLTand the ONU on the OLT.Create management VLAN 8 and add upstream port 0/19/0 to it. Configure theinband management IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

(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 and themanagement VLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

(3) Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 8,GEM port ID to 0, and CVLAN ID to 8. The rate of the inband service port onthe OLT is not limited. Therefore, use traffic profile 6 (default). To limit the rateof the service port, run the traffic table ip command to add a traffic profile andbind it to the service port.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6

5. Confirm that the management channel between the OLT and the ONU is available.– On the OLT, run the ping 192.168.50.2 command to check the connectivity to the

ONU. The ICMP ECHO-REPLY packet from the ONU should be received.– You can run the telnet 192.168.50.2 command to telnet to the ONU and then

configure the ONU.6. Configure the TDM connection.

Set up a native TDM connection between GEM port 1 and upstream port 0/5/0 of theTPOA board.– In the case of the E1 upstream port, the configuration is as follows:

huawei(config)#tdm-connect connectid 1 tdm 0/5/0 gpon 0/3/1 ontid 1 gemportIndex 1

– In the case of the STM-1 upstream port, you must configure the VC12 parameter.VC12 is the virtual container that carries the E1 service. One STM-1 port contains63 E1 ports. Accordingly, there are 63 VC12 virtual containers. The configurationis as follows:huawei(config)#tdm-connect connectid 1 tdm 0/5/0 vc12 2 gpon 0/3/1 ontid 1 gemportIndex 1

7. Configure the system clock and time synchronization.For details, see 9.5.1.3 Configuring E1/STM-1 Line Clock Synchronization.

8. Configure network protection.For details, see 9.5.2 Configuring FTTM Network Protection.




9-99








l Configure the ONU.NOTE

Because the management VLAN and the management IP address have been configured, you can run thetelnet 192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You canalso log in to the ONU through a serial port to perform the configuration.

1. Configure the system clock synchronization.For details, see 9.5.1.3 Configuring E1/STM-1 Line Clock Synchronization.


----End

ResultMobile terminals (mobile phones) near the base station can obtain their network informationnormally and make calls and send messages to each other normally.

Configuration FileConfigure the OLT.vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name TDM type1 fix 32768 bandwidth_compensate yesont-lineprofile gpon profile-id 10tcont 10 dba-profile-name dba-profile_1tcont 1 dba-profile-name TDMgem add 0 eth tcont 10 priority-queue 0gem add 1 tdm tcont 1 priority-queue 0gem mapping 0 0 vlan 8gem mapping 1 1 e1 1commitquitinterface gpon 0/3


Configuration Guide


Issue 04 (2011-04-27)

port 1 ont-auto-find enableont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6tdm-connect connectid 1 tdm 0/5/0 gpon 0/3/1 ontid 1 gemportIndex 1 //E1 upstreamtdm-connect connectid 1 tdm 0/5/0 vc12 2 gpon 0/3/1 ontid 1 gemportIndex 1 //STM-1 upstreamqueue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

Configure the ONU.clock source 0 0/0/0clock priority system 0interface tdm 0/1port 0 udt systemquitsave

9.5.4 Configuring the TDM PWE3 Base station access Service on theOLT (MPLS-based)

The ONU accesses the 2G/3G base station through the E1 port and sends the TDM servicepackets to the OLT through native TDM. The OLT restores the TDM signals, starts the TDMPWE3, and then sends the TDM signals to the MPLS network and peer PTN through the GEport. In this way, the traditional circuit switched service is implemented over the GPON network.The ONUs support this service are MA5612 and MA5628.

PrerequisiteThe CSPA and SPUB boards must work in the normal state.

Service Requirementsl The ONU is connected to the 2G/3G base station and GPON is adopted for bearing the

mobile access network in a unified manner, meeting mobile carriers' requirements for highbandwidth and high-density coverage of base stations.

l The carrier can perform smooth evolution in the reconstruction to IP-based metropolitanarea network (MAN) without upgrading or replacing ONUs

l Resources are reserved so that carriers can accurately control the path that traffic traversesto avoid the node where congestion occurs and balance the network traffic.

Figure 9-15 shows an example network of the TDM PWE3 base station access service on theOLT.

The ONU receives the TDM service data from the 2G/3G base station through the E1 port,encapsulates the TDM packets into GEM frames, and then sends them to the OLT through nativeTDM. The OLT restores the TDM signals, starts the TDM PWE3, and then sends the TDMsignals to the MPLS network and peer PTN through the GE port. Finally, the PTN deviceterminates the emulation data and restores the TDM signals. In this way, the 2G/3G base stationaccess service is implemented between the OLT and the PTN in the TDM PW mode.



9-101

Figure 9-15 Example network of the TDM PWE3 base station access service on the OLT(MPLS-based)

Data PlanTable 9-8 provides the data plan for the OLT, and Table 9-9 provides the data plan for the ONU.

Table 9-8 Data plan for configuring the TDM PWE3 base station access service-OLT side

Item Data

VLAN Inband management VLAN: smart VLAN 8SVLAN: smart VLAN 500

IP address Inband management IP address: 192.168.50.1/24IP address of the L3 interface of VLAN 500: 10.50.50.50/24

CSPA board Shelf/slot: 0/1


DBA profile Profile ID: 1 (system default)Type: type1Fixed bandwidth: 5 Mbit/sBandwidth compensation: No

Profile name: TDMType: type1Fixed bandwidth: 32 Mbit/sBandwidth compensation: Yes


Configuration Guide


Issue 04 (2011-04-27)

Item Data

ONU line profile Profile ID: 10GEM port IDs: 0 and 1T-CONT IDs: 1 and 10Bind T-CONT 1 to the DBA profile named TDMBind T-CONT 10 to the DBA profile ID 1


MPLS MPLS LSR-ID: 20.20.20.20Global MPLS RSVP-TE: enabledMPLS RSVP-TE of the VLAN interface: enabledMPLS Layer 2 VPN: enabled

PW parameters PW ID: 2Peer IP address: 30.30.30.30PW type: TDM SAToP E1PW load time: 125 μsJitter buffer size: 2500 μsControl word: supportedRTP: enabledPW transmit label: 8448PW receive label: 8449

Tunnel Tunnel interface ID: 10Tunnel ID: 10Link layer encapsulation protocol of the tunnel interface: MPLS-TETunnel signaling protocol: RSVP-TEDestination IP address: 30.30.30.30Policy name: mpls-rsvp

Table 9-9 Data plan for configuring the TDM PWE3 base station access service-ONU side

Item Data



E1 port Port: 0/1/0



9-103






GPON ONU profiles include the DBA profile, line profile and alarm profile.– DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT




(1) Add a DBA profile.You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBAprofile.Configure the DBA profile name to TDM, type to type1, fixed bandwidth to 32Mbit/s, and enable the bandwidth compensation.To configure the DBA profile of fixed bandwidth type to bear the TDM services,you must enable the bandwidth compensation function.huawei(config)#dba-profile add profile-name TDM type1 fix 32768 bandwidth_compensate yes

(2) Add an ONU line profile.Add GPON MDU line profile 10, bind T-CONT 10 to default DBA profile nameddba-profile_1 and T-CONT 1 to DBA profile named TDM. In this way, the T-CONT can provide flexible DBA solutions based on different configurations inthe DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 10 dba-profile-name dba-profile_1huawei(config-gpon-lineprofile-10)#tcont 1 dba-profile-name TDMAdd GEM port 0 for transmitting management traffic streams and GEM port 1for transmitting TDM traffic streams. Bind GEM port 0 to T-CONT 10 and GEMport 1 to T-CONT 1. Configure the QoS mode to priority-queue (default) and thequeue priority to 3.


Configuration Guide


Issue 04 (2011-04-27)

NOTE



huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 10 priority-queue 3huawei(config-gpon-lineprofile-10)#gem add 1 tdm tcont 1 priority-queue 3Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management VLAN 8 to GEM port 0, and mapthe E1 port 1 of on the ONU to GEM port 1.huawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 e1 1After the configuration is complete, run the commit command to make theconfigured parameters take effect.huawei(config-gpon-lineprofile-10)#commithuawei(config-gpon-lineprofile-10)#quit

(3) (Optional) Add an alarm profile.– The ID of the default GPON alarm profile is 1. The thresholds of all the alarm






(1) Add an ONU.Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound lineprofile ID is 10.There are two ways to add an ONU. Select either of the two ways according toactual conditions.– Add an ONU offline: If the password or SN of an ONU is obtained, you can



To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 To automatically find an ONU, do as follows:



9-105

huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example. ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

NOTEIf multiple ONUs of the same type are connected to a port and the same line profile or serviceprofile (for an ONT) is bound to the ONUs, you can add ONUs in batches by confirming theauto-found ONUs in batches to simplify the operation and increase the configurationefficiency. For example, the preceding command can be modified as follows:ont confirm 1all sn-auth snmp ont-lineprofile-id 10 .

(2) (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.huawei(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 1








Configuration Guide


Issue 04 (2011-04-27)








(1) Configure the inband management VLAN and IP address of the OLT.To log in to the ONU through Telnet and configure the ONU from the OLT, youmust configure the inband management VLANs and IP addresses of the OLTand the ONU on the OLT.Create management VLAN 8 and add upstream port 0/19/0 to it. Configure theinband management IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

(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 and themanagement VLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

(3) Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 8,GEM port ID to 0, and CVLAN ID to 8. The rate of the inband service port onthe OLT is not limited. Therefore, use traffic profile 6 (default). To limit the rateof the service port, run the traffic table ip command to add a traffic profile andbind it to the service port.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6



9-107

6. Confirm that the management channel between the OLT and the ONU is available.– On the OLT, run the ping 192.168.50.2 command to check the connectivity to the

ONU. The ICMP ECHO-REPLY packet from the ONU should be received.– You can run the telnet 192.168.50.2 command to telnet to the ONU and then

configure the ONU.7. Configure the IP address of the loopback interface.

Configure the IP address of loopback interface 0 to 20.20.20.20/32.

huawei(config)#interface loopback 0huawei(config-if-loopback0)#ip address 20.20.20.20 32huawei(config-if-loopback0)#quit

8. Enable the MPLS basic function.

Configure the MPLS LSR ID. Set the local LSR ID to the IP address of loopbackinterface 0.

huawei(config)#mpls lsr-id 20.20.20.20

Globally enable MPLS, MPLS TE, MPLS RSVP-TE and CSPF functions.

huawei(config)#mplshuawei(config-mpls)#mpls tehuawei(config-mpls)#mpls rsvp-tehuawei(config-mpls)#mpls te cspfhuawei(config-mpls)#quit

Enable Layer 2 VPN function.

huawei(config)#mpls l2vpn

9. Enable the MPLS TE function for VLAN and VLAN interface.

Enable the MPLS function for VLAN 500.

huawei(config)#mpls vlan 500

Configure the IP address of VLAN interface 500 to 10.50.50.50/24, and enable theMPLS RSVP-TE function for VLAN interface 500.

huawei(config)#interface vlanif 500huawei(config-if-vlanif500)#ip address 10.50.50.50 24huawei(config-if-vlanif500)#mplshuawei(config-if-vlanif500)#mpls tehuawei(config-if-vlanif500)#mpls rsvp-tehuawei(config-if-vlanif500)#quit

10. Configure a route.

PWE3 has no special requirement for the routing policy. Either a static route or anOSPF dynamic route can be configured. Because OSPF supports MPLS RSVP-TEextension, an OSPF dynamic route is recommended.

Configure the OSPF process ID to 100 and OSPF area ID to 1. Then, configure theinterfaces (VLAN interface and loopback interface) that run OSPF and the areas ofthe interfaces.

huawei(config)#ospf 1huawei(config-ospf-1)#opaque-capability enable..//Enable the opaque capabilityhuawei(config-ospf-1)#area 100huawei(config-ospf-1-area-0.0.0.100)#mpls-te enable standard-complying //Enable MPLS TE for the OSPF areahuawei(config-ospf-1-area-0.0.0.100)#network 10.50.50.0 0.0.0.255


Configuration Guide


Issue 04 (2011-04-27)

huawei(config-ospf-1-area-0.0.0.100)#network 20.20.20.20 0.0.0.0huawei(config-ospf-1-area-0.0.0.100)#return

11. Configure a PWE3 outer tunnel.

Configure the tunnel ID to 10 and the encapsulation protocol of the tunnel interfaceat the data link layer to MPLS TE.

huawei(config)#interface tunnel 10huawei(config-if-tunnel10)#tunnel-protocol mpls te

Configure the destination IP address of the tunnel to 30.30.30.30.

NOTEThe destination IP address of the tunnel indicates the LSR ID of the tunnel termination (the nextLSR traversed by the ONU). To simplify the configuration, assume that no other LSRs exist betweenthe ONU and the PTN. The destination IP address is the LSR ID of the PTN, namely 30.30.30.30.

huawei(config-if-tunnel10)#destination 30.30.30.30

Configure the ID of the MPLS TE tunnel interface to 10. The tunnel ID and LSR IDuniquely identify an MPLS TE tunnel.

huawei(config-if-tunnel10)#mpls te tunnel-id 10

Configure the signaling protocol of the MPLS TE tunnel to RSVP-TE.

huawei(config-if-tunnel10)#mpls te signal-protocol rsvp-te

Configure the MPLS TE tunnel for being bound by a VPN instance.

huawei(config-if-tunnel10)#mpls te reserved-for-binding

Commit the configuration and quit the tunnel configuration.

huawei(config-if-tunnel10)#mpls te commithuawei(config-if-tunnel10)#quit

12. Configure the tunnel policy.

Configure the policy name to mpls-rsvp, bind the policy to tunnel 10, and configurethe destination IP address of the tunnel to 30.30.30.30.

NOTEThe destination IP address should be consistent with that configured in the MPLS TE tunnel.

huawei(config)#tunnel-policy mpls-rsvpInfo: New tunnel-policy is configured.huawei(config-tunnel-policy-mpls-rsvp)#tunnel binding destination 30.30.30.30 te tunnel 10huawei(config-tunnel-policy-mpls-rsvp)#quit

13. Configure the PW parameters.

(1) Configure the PW ID to 2.huawei(config)#pw-para 2

(2) Configure the loopback interface IP address of the remote PTN device.Configure the loopback interface IP address to 30.30.30.30.huawei(config-pw-para-2)#peer-address 30.30.30.30

(3) Configure the PW type to TDM SAToP E1.huawei(config-pw-para-2)#pw-type tdm satop e1

(4) Configure the PW load time.Configure the load time to 125 μs.huawei(config-pw-para-2)#tdm-load-time satop loadtime 125



9-109

(5) (Optional) Enable RTP. After RTP is enabled, PW packets of the TDM typecontain the RTP control header. By default, RTP is disabled.

NOTEThe RTP configuration must be the same as that on the PTN.huawei(config-pw-para-2)#rtp enable

(6) (Optional) Configure the jitter buffer size. The jitter buffer can effectivelyprevent jitter and delay. Only PW of the TDM type support the jitter bufferconfiguration. By default, the jitter buffer size is 2000 μs.

NOTEThe value range of the jitter buffer is 500-32000 and the value must be an integer multiple of125. You can configure this value according to actual conditions. In this example, the jitterbuffer size is configured to 2500 μs.huawei(config-pw-para-2)#jitter-buffer buffer-size 2500

(7) Configure the PW to support the control word.When the VCCV ping works in the control word mode, you need to enable thecontrol word. It is recommended that you enable the control word mode.huawei(config-pw-para-2)#control-word

(8) Enable the virtual circuit connectivity verification (VCCV) function.VCCV is an end-to-end PW fault detection and diagnosis mechanism. Simply,VCCV is a control channel for the PW to send verification messages betweenthe ingress and egress.huawei(config-pw-para-2)#vccv cc cw alert ttl cv lsp-ping

(9) Configure the tunnel policy used by the PW.Configure the tunnel policy name to mpls-rsvp.huawei(config-pw-para-2)#tnl-policy mpls-rsvphuawei(config-pw-para-2)#quit

14. Create a service port for converting the native TDM service into SAToP service.

The TDM signals are encapsulated into GEM frames through native TDM, transmittedupstream through GPON, and then forwarded to the CSPA board. The CSPA boardrestores the TDM signals and encapsulates them in the TDM PWE3 format.

The TDM connection ID is 10, the upstream transmission mode is PWE3, the CSPAboard resides in slot 0/1, and the TDM service is carried over GEM port 1.

huawei(config)#tdm-connect connectid 10 tdm pwe3-uplink 0/1 gpon 0/3/1 ontid 1 gemportIndex 1

15. Bind the TDM to the PW.

The static PW encapsulation mode is adopted. Such a PW does not use the signalingprotocol for parameter negotiation. You can manually specify the related informationby running the related command. The data of a static PW is transmitted between theprovider edges (PEs) through tunnels. Configure the TDM virtual channel connection(VCC) ID to 10, PW ID to 2, transmit label to 8448, and receive label to 8449.

huawei(config)#pw-ac-binding tdm 10 pw 2 static transmit-label 8448 receive-label 8449

NOTEWhen you configure a static TDM PW, the PW transmit-label on the OLT must be the same as thereceive-label on the peer PE, and the receive-label on the OLT must be the same as the PW transmit-label on the peer PE (the PTN in this example).


Configuration Guide


Issue 04 (2011-04-27)

16. Ensure that the PW is in the normal state.On the OLT, run the display pw or display pw-ac-binding command to query thePW status. Ensure that the PW state is normal (up).huawei(config)#display pw-ac-binding tdm 10 Total : 1 (Up/Down : 1/0 Static/LDP : 1/0) ---------------------------------------------------------------------------- TDM PW PW PROTO RECEIVE TRNS PW ID ID STATE TYPE LABEL LABEL INDEX ---------------------------------------------------------------------------- 10 2 up static 8449 8448 2 ---------------------------------------------------------------------------- Note : F--Frame, S--Slot, P--Port *: Secondary








18. Configure system clock synchronization.The following clock synchronization schemes are recommended. You can choose theclock synchronization scheme according to actual network and requirements.– Ethernet clock synchronization: The upstream MAN PSN of the OLT must feature

the capability of Ethernet synchronization. For details, see 9.5.1.4 ConfiguringEthernet Clock Synchronization.

– BITS clock synchronization: The OLT must have the BITS clock input resource.For details, see 9.5.1.2 Configuring BITS Clock Synchronization.

– 1588V2 clock synchronization: The OLT must be configured with an additional1588V2 server, or each hop on the upstream network of the OLT must support1588V2. For details, see 9.5.1.5 Configuring 1588V2 Clock Synchronization.

19. Configure network protection.



9-111

For details, see 9.5.2 Configuring FTTM Network Protection.20. Save the data.

huawei(config)#savel Configure the ONU.

NOTEBecause the management VLAN and the management IP address have been configured, you can run thetelnet 192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You canalso log in to the ONU through a serial port to perform the configuration.

1. Configure system clock synchronization.The following clock synchronization schemes are recommended. You can choose theclock synchronization scheme according to actual network and requirements.– Ethernet clock synchronization: The upstream MAN PSN of the OLT must feature

the capability of Ethernet synchronization. For details, see 9.5.1.4 ConfiguringEthernet Clock Synchronization.

– BITS clock synchronization: The OLT must have the BITS clock input resource.For details, see 9.5.1.2 Configuring BITS Clock Synchronization.

– 1588V2 clock synchronization: The OLT must be configured with an additional1588V2 server, or each hop on the upstream network of the OLT must support1588V2. For details, see 9.5.1.5 Configuring 1588V2 Clock Synchronization.


----End

ResultMobile terminals (mobile phones) near the base station can obtain their network informationnormally, make calls, and send messages to each other normally.

Configuration FileConfigure the OLT.vlan 500 smartport vlan 500 0/19 0vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name TDM type1 fix 32768 bandwidth_compensate yesont-lineprofile gpon profile-id 10tcont 10 dba-profile-id 1tcont 1 dba-profile-name TDMgem add 0 eth tcont 10 priority-queue 3gem add 1 tdm tcont 1 priority-queue 3gem mapping 0 0 vlan 8gem mapping 1 1 e1 1commitquitinterface gpon 0/3port 1 ont-auto-find enableont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6


Configuration Guide


Issue 04 (2011-04-27)

interface loopback 0ip address 20.20.20.20 32quitmpls lsr-id 20.20.20.20mplsmpls templs te rsvp-templs te cspfquitmpls l2vpninterface vlanif 500ip address 10.50.50.50 24mplsmpls templs te rsvp-tequitospf 1opaque-capability enablearea 100mpls-te enable standard-complyingnetwork 10.50.50.0 0.0.0.255network 20.20.20.20 0.0.0.0returninterface tunnel 10tunnel-protocol mpls tedestination 30.30.30.30mpls te tunnel-id 10mpls te signal-protocol rsvp-templs te reserved-for-bindingmpls te commitquittunnel-policy mpls-rsvptunnel binding destination 30.30.30.30 te tunnel 10quitpw-para 2peer-address 30.30.30.30pw-type tdm satop e1tdm-load-time satop loadtime 125rtp enablejitter-buffer buffer-size 2500control-wordtnl-policy mpls-rsvpquittdm-connect connectid 10 tdm pwe3-uplink 0/1 gpon 0/3/1 ontid 1 gemportIndex 1pw-ac-binding tdm 10 pw 2 static transmit-label 8448 receive-label 8449queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save


9.5.5 Configuring the TDM PWE3 Base station access Service on theOLT (IP-based)

The ONU accesses the 2G/3G base station through the E1 port and sends the TDM servicepackets to the OLT through native TDM. The OLT restores the TDM signals, starts the TDMPWE3, and then sends the TDM signals to the IP network and peer PTN through the GE port.In this way, the traditional circuit switched service is implemented over the GPON network. TheONUs support this service are MA5612 and MA5628.



9-113

PrerequisiteThe CSPA and SPUB boards must work in the normal state.



l The carrier can perform smooth evolution in the reconstruction to IP-based MAN withoutupgrading or replacing ONUs


Figure 9-16 shows an example network of the TDM PWE3 base station access service on theOLT.

The ONU receives the TDM service data from the 2G/3G base station through the E1 port,encapsulates the TDM packets into GEM frames, and then sends them to the OLT through nativeTDM. The OLT restores the TDM signals, starts the TDM PWE3, and then sends the TDMsignals to the MPLS network and peer PTN through the GE port. Finally, the PTN deviceterminates the emulation data and restores the TDM signals. In this way, the 2G/3G base stationaccess service is implemented between the OLT and the PTN in the TDM PW mode.

Figure 9-16 Example network of the TDM PWE3 base station access service on the OLT (IP-based)

Data Plan

Table 9-10 provides the data plan for the OLT, and Table 9-11 provides the data plan for theONU.


Item Data



Configuration Guide


Issue 04 (2011-04-27)

Item Data


CSPA board Shelf/Slot: 0/1


DBA profile Profile ID: 1 (system default)Type: type1Fixed bandwidth: 5Mbit/sBandwidth compensation: No

Profile name: TDMType: type1Fixed bandwidth: 32Mbit/sBandwidth compensation: Yes

ONU line profile Profile ID: 10GEM port IDs: 0 and 1T-CONT IDs: 1 and 10Bind T-CONT 1 to the DBA profile named TDMBind T-CONT 10 to the DBA profile ID 1


MPLS MPLS LSR-ID: 20.20.20.20Global MPLS function: enabledMPLS Layer 2 VPN: enabled

PW parameters PW ID: 2Peer IP address: 30.30.30.30PW type: TDM SAToP E1PW load time: 125 μsJitter buffer size: 2500 μsControl word: supportedRTP: enabledPW transmit label: 8448PW receive label: 8449



9-115

Item Data

Tunnel Tunnel interface ID: 10Tunnel ID: 10Link layer encapsulation protocol of the tunnel interface: IPPolicy name: ip_policy

Table 9-11 Data plan for configuring the TDM PWE3 base station access service-ONU side

Item Data



E1 port Port: 0/1/0

Procedure

Step 1 Configure the OLT.1. Create an SVLAN and add an upstream port to it.








a. Add a DBA profile.You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBA profile.Configure the DBA profile name to TDM, type to type1, fixed bandwidth to 32 Mbit/s, and enable the bandwidth compensation.To configure the DBA profile of fixed bandwidth type to bear the TDM services, youmust enable the bandwidth compensation function.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#dba-profile add profile-name TDM type1 fix 32768 bandwidth_compensate yes

b. Add an ONU line profile.Add GPON MDU line profile 10, bind T-CONT 10 to default DBA profile nameddba-profile_1 and T-CONT 1 to DBA profile named TDM. In this way, the T-CONTcan provide flexible DBA solutions based on different configurations in the DBAprofile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 10 dba-profile-name dba-profile_1huawei(config-gpon-lineprofile-10)#tcont 1 dba-profile-name TDM

Add GEM port 0 for transmitting management traffic streams and GEM port 1 fortransmitting TDM traffic streams. Bind GEM port 0 to T-CONT 10 and GEM port 1to T-CONT 1. Configure the QoS mode to priority-queue (default) and the queuepriority to 3.

NOTE



huawei(config-gpon-lineprofile-10)#gem add 0 eth tcont 10 priority-queue 3huawei(config-gpon-lineprofile-10)#gem add 1 tdm tcont 1 priority-queue 3

Configure the mapping mode from the GEM port to ONU-side service to VLAN(default), map the service port of management VLAN 8 to GEM port 0, and map theE1 port 1 of on the ONU to GEM port 1.huawei(config-gpon-lineprofile-10)#gem mapping 0 0 vlan 8huawei(config-gpon-lineprofile-10)#gem mapping 1 1 e1 1


c. (Optional) Add an alarm profile.

l The ID of the default GPON alarm profile is 1. The thresholds of all the alarmparameters in the default alarm profile are 0, which indicates that no alarm isgenerated.





a. Add an ONU.Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound line profile IDis 10.



9-117

There are two ways to add an ONU. Select either of the two ways according to actualconditions.l Add an ONU offline: If the password or SN of an ONU is obtained, you can run



To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example. ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

NOTEIf multiple ONUs of the same type are connected to a port and the same line profile or service profile(for an ONT) is bound to the ONUs, you can add ONUs in batches by confirming the auto-foundONUs in batches to simplify the operation and increase the configuration efficiency. For example,the preceding command can be modified as follows:ont confirm 1 all sn-auth snmp ont-lineprofile-id 10 .

b. (Optional) Bind the alarm profile to the ONU.The default profile (profile 1) is used.huawei(config-if-gpon-0/3)#ont alarm-profile 1 1 profile-id 1


After an ONU is added, run the display ont info command to query the current status ofthe ONU. Ensure that Control flag of the ONU is active, Run State is online, Configstate is normal, and Match state is match.huawei(config-if-gpon-0/3)#display ont info 1 1 --------------------------------------------------------------------- F/S/P : 0/3/1 ONT-ID : 1 Control flag : active //Indicates that the ONU is activated. Run state : online //Indicates that the ONU already goes online normally.


Configuration Guide


Issue 04 (2011-04-27)

Config state : normal //Indicates that the configuration status of the ONU is normal. Match state : match //Indicates that the capability profile bound to the ONU is //consistent with the actual capability of the ONU. //The rest of the response information is omitted.

If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match, referto the following suggestions to rectify the fault.

l If Control flag is deactive, run the ont activate command in the GPON port mode toactivate the ONU.

l If the ONU fails to be in the up state, that is, Run state is offline, the physical line maybe broken or the optical transceiver may be damaged. You need to check both thematerial and the line.



l If the ONU does not match, that is, Match state is mismatch, the port types and numberof 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 ofthe 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 thenrun 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 themodification. Then, the ONU automatically recovers the configuration successfully.



a. Configure the inband management VLAN and IP address of the OLT.

To log in to the ONU through Telnet and configure the ONU from the OLT, you mustconfigure the inband management VLANs and IP addresses of the OLT and the ONUon the OLT.

Create management VLAN 8 and add upstream port 0/19/0 to it. Configure the inbandmanagement IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

b. 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 and the managementVLAN ID to 8 (the same as the management VLAN of the OLT).



9-119

huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

c. Configure an inband management service port.Configure the management service port ID to 0, management VLAN ID to 8, GEMport ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT isnot limited. Therefore, use traffic profile 6 (default). To limit the rate of the serviceport, run the traffic table ip command to add a traffic profile and bind it to the serviceport.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6



the ONU.7. Configure the IP address of the loopback interface.




Configure the MPLS LSR ID. Set the local LSR ID to the IP address of loopback interface0.


Globally enable MPLS function.

huawei(config)#mplshuawei(config-mpls)#quit



9. Enable the MPLS function for VLAN and VLAN interface.



Configure the IP address of VLAN interface 500 to 10.50.50.50/24, and enable the MPLSfunction for VLAN interface 500.

huawei(config)#interface vlanif 500huawei(config-if-vlanif500)#ip address 10.50.50.50 24huawei(config-if-vlanif500)#mplshuawei(config-if-vlanif500)#quit


PWE3 has no special requirement for the routing policy. Either a static route or an OSPFdynamic route can be configured. Because OSPF supports MPLS RSVP-TE extension, anOSPF dynamic route is recommended.


Configuration Guide


Issue 04 (2011-04-27)

Configure the OSPF process ID to 100 and OSPF area ID to 1. Then, configure the interfaces(VLAN interface and loopback interface) that run OSPF and the areas of the interfaces.

huawei(config)#ospf 1huawei(config-ospf-1)#area 100huawei(config-ospf-1-area-0.0.0.100)#network 10.50.50.0 0.0.0.255huawei(config-ospf-1-area-0.0.0.100)#network 20.20.20.20 0.0.0.0huawei(config-ospf-1-area-0.0.0.100)#return


Configure the tunnel ID to 10 and the encapsulation protocol of the tunnel interface at thedata link layer to MPLS IP.

huawei(config)#interface tunnel 10huawei(config-if-tunnel10)#tunnel-protocol mpls ip


NOTEThe destination IP address of the tunnel indicates the LSR ID of the tunnel termination (the next LSRtraversed by the OLT). To simplify the configuration, assume that no other LSRs exist between the OLTand the PTN. The destination IP address is the LSR ID of the PTN, namely 30.30.30.30.



huawei(config-if-tunnel10)#mpls ip commithuawei(config-if-tunnel10)#quit

12. Configure the tunnel policy used by the PW template.

Configure the tunnel policy name to ip-policy.

huawei(config)#tunnel-policy ip_policyInfo: New tunnel-policy is configured.huawei(config-tunnel-policy-ip_policy)#tunnel select-seq ip load-balance-number 1huawei(config-tunnel-policy-ip_policy)#quit

13. Create the PW parameters.

a. Configure the PW ID to 2.huawei(config)#pw-para 2

b. Configure the loopback interface IP address of the remote PTN device in the PW.

Configure the loopback interface IP address to 30.30.30.30.huawei(config-pw-para-2)#peer-address 30.30.30.30

c. Configure the PW load time.

Configure the load time to 125 μs.huawei(config-pw-para-2)#tdm-load-time satop loadtime 125

d. (Optional) Enable RTP. After RTP is enabled, PW packets of the TDM type containthe RTP control header. By default, RTP is disabled.

NOTEThe RTP configuration must be the same as that on the PTN.huawei(config-pw-para-2)#rtp enable

e. (Optional) Configure the jitter buffer size. The jitter buffer can effectively preventjitter and delay. Only PW of the TDM type support the jitter buffer configuration. Bydefault, the jitter buffer size is 2000 μs.



9-121

NOTEThe value range of the jitter buffer is 500-32000 and the value must be an integer multiple of 125.You can configure this value according to actual conditions. In this example, the jitter buffer size isconfigured to 2500 μs.huawei(config-pw-para-2)#jitter-buffer buffer-size 2500

f. Configure the PW to support the control word.When the VCCV ping works in the control word mode, you need to enable the controlword. It is recommended that you enable the control word mode.huawei(config-pw-para-2)#control-word

g. Enable the VCCV function.VCCV is an end-to-end PW fault detection and diagnosis mechanism. Simply, VCCVis a control channel for the PW to send verification messages between the ingress andegress.huawei(config-pw-para-1)#vccv cc cw alert ttl cv lsp-ping

h. Configure the tunnel policy used by the PW.Configure the tunnel policy name to ip-policy.huawei(config-pw-para-2)#tnl-policy ip-policyhuawei(config-pw-para-2)#quit

14. Create a service port for converting the native TDM service into SAToP service.

The TDM signals are encapsulated into GEM frames through native TDM, transmittedupstream through GPON, and then forwarded to the CSPA board. The CSPA board restoresthe TDM signals and encapsulates them in the TDM PWE3 format.

The TDM connection ID is 10, the upstream transmission mode is PWE3, the CSPA boardresides in slot 0/1, and the TDM service is carried over GEM port 1.

huawei(config)#tdm-connect connectid 10 tdm pwe3-uplink 0/1 gpon 0/3/1 ontid 1 gemportIndex 1

15. Bind the TDM to the PW.

The static PW encapsulation mode is adopted. Such a PW does not use the signalingprotocol for parameter negotiation. You can manually specify the related information byrunning the related command. The data of a static PW is transmitted between the provideredges (PEs) through tunnels. Configure the TDM virtual channel connection (VCC) ID to10, PW ID to 2, transmit label to 8448, and receive label to 8449.

huawei(config)#pw-ac-binding tdm 10 pw 2 static transmit-label 8448 receive-label 8449

NOTEWhen you configure a static TDM PW, the PW transmit-label on the OLT must be the same as the receive-label on the peer PE, and the receive-label on the OLT must be the same as the PW transmit-label on thepeer PE (the PTN in this example).

16. Ensure that the PW is in the normal state.On the OLT, run the display pw or display pw-ac-binding command to query the PWstatus. Ensure that the PW state is normal (up).huawei(config)#display pw-ac-binding tdm 10 Total : 1 (Up/Down : 1/0 Static/LDP : 1/0) ---------------------------------------------------------------------------- TDM PW PW PROTO RECEIVE TRNS PW ID ID STATE TYPE LABEL LABEL


Configuration Guide


Issue 04 (2011-04-27)

INDEX ---------------------------------------------------------------------------- 10 2 up static 8449 8448 2 ---------------------------------------------------------------------------- Note : F--Frame, S--Slot, P--Port *: Secondary

17. Configure system clock synchronization.The following clock synchronization schemes are recommended. You can choose the clocksynchronization scheme according to actual network and requirements.l Ethernet clock synchronization: The upstream MAN PSN of the OLT must feature the

capability of Ethernet synchronization. For details, see 9.5.1.4 Configuring EthernetClock Synchronization.

l BITS clock synchronization: The OLT must have the BITS clock input resource. Fordetails, see 9.5.1.2 Configuring BITS Clock Synchronization.

l 1588V2 clock synchronization: The OLT must be configured with an additional 1588V2server, or each hop on the upstream network of the OLT must support 1588V2. Fordetails, see 9.5.1.5 Configuring 1588V2 Clock Synchronization.



Step 2 Configure the ONU.NOTE

Because the management VLAN and the management IP address have been configured, you can run the telnet192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You can also log in tothe ONU through a serial port to perform the configuration.






----End




9-123

Configuration File

Configure the OLT.vlan 500 smartport vlan 500 0/19 0vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name TDM type1 fix 32768 bandwidth yesont-lineprofile gpon profile-id 10tcont 10 dba-profile-id 1tcont 1 dba-profile-name TDMgem add 0 eth tcont 10 priority-queue 3gem add 1 tdm tcont 1 priority-queue 3gem mapping 0 0 vlan 8gem mapping 1 1 e1 1commitquitinterface gpon 0/3port 1 ont-auto-find enableont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service μser-vlan 8 rx-cttr 6 tx-cttr 6interface loopback 0ip address 20.20.20.20 32quitmpls lsr-id 20.20.20.20mplsquitmpls l2vpninterface vlanif 500ip address 10.50.50.50 24mplsquitospf 1area 100network 10.50.50.50 0.0.0.255network 20.20.20.20 0.0.0.0returninterface tunnel 10tunnel-protocol mpls ipdestination 30.30.30.30mpls te tunnel-id 10mpls te commitquittunnel-policy ip-policytunnel select-seq ip load-balance-number 1quitpw-para 2peer-address 30.30.30.30pw-type tdm satop e1tdm-load-time satop loadtime 125rtp enablejitter-buffer buffer-size 2500control-wordvccv cc cw alert ttl cv lsp-pingtnl-policy ip_policyquittdm-connect connectid 10 tdm pwe3-uplink 0/1 gpon 0/3/1 ontid 1 gemportIndex 1pw-ac-binding tdm 10 pw 2 static transmit-label 8448 receive-label 8449queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save


Configuration Guide


Issue 04 (2011-04-27)


9.5.6 Configuring the ETH PWE3 Base station access Service on theOLT

The ONU accesses the 3G base station through the FE/GE port and sends the ETH service packetsto the OLT through GPON. The OLT restores the ETH packets, starts the ETH PWE3, and thensends the ETH packets to the IP network and peer PTN through the GE/10GE port. In this way,the ETH service is implemented over the GPON network. The ONUs support this service areMA5612 and MA5628.

PrerequisiteThe SPUB board must work in the normal state.

Service Requirementsl The ETH port of the ONU is connected to the 3G base station and GPON is adopted for

bearing the mobile access network in a unified manner, meeting mobile carriers'requirements for high bandwidth and high-density coverage of base stations.

l Through PWE3 emulation, the ETH service data can be transmitted securely in the PSNnetwork.


Figure 9-17 shows an example network of the ETH PWE3 base station access service on theOLT.

The ONU receives the ETH service data from the 3G base station through the FE/GE port,encapsulates the ETH packets into GEM frames, and then sends them to the OLT through theGPON upstream port. The OLT restores the ETH signals, starts the ETH PWE3, and then sendsthe ETH signals to the MPLS network and peer PTN through the GE/10GE port. Finally, thePTN device terminates the emulation data and restores the ETH signals. In this way, the 3G basestation access service is implemented between the OLT and the PTN in the ETH PW mode.

Figure 9-17 Example network of the ETH PWE3 base station access service on the OLT



9-125

Data PlanTable 9-12 provides the data plan for the OLT, and Table 9-13 provides the data plan for theONU.


Item Data




DBA profile Profile name: ETHType: type1Fixed bandwidth: 100Mbit/s

ONU line profile Profile ID: 10GEM Port ID: 0 and 1T-CONT ID: 1Bind T-CONT 1 to the DBA profile named ETH


MPLS MPLS LSR-ID: 20.20.20.20Global MPLS RSVP-TE: enabledMPLS RSVP-TE of the VLAN interface: enabledMPLS Layer 2 VPN: enabled

PW parameters PW ID: 3Peer IP address: 30.30.30.30PW type: ethernet taggedControl word: supportedPW transmit label: 8500PW receive label: 8510


Configuration Guide


Issue 04 (2011-04-27)

Item Data

Tunnel Tunnel interface ID: 10Tunnel ID: 10Link layer encapsulation protocol of the tunnel interface: MPLS-TETunnel signaling protocol: RSVP-TEDestination IP address: 30.30.30.30Policy name: mpls-rsvp

Table 9-13 Data plan for configuring the ETH PWE3 base station access service-ONU side

Item Data



ETH service port Port: 0/4/0User VLAN: 20

Procedure

Step 1 Configure the OLT.1. Create an SVLAN and add an upstream port to it.








a. Add a DBA profile.You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBA profile.



9-127

Configure the DBA profile name to ETH, type to type1, and fixed bandwidth to 100Mbit/s.huawei(config)#dba-profile add profile-name ETH type1 fix 102400

b. Add an ONU line profile.Add GPON MDU line profile 10, bind T-CONT 1 to DBA profile named ETH. In thisway, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 1 dba-profile-name ETH

Add GEM port 0 for transmitting management traffic streams and GEM port 1 fortransmitting TDM traffic streams. Bind GEM port 0 and GEM port 1 to T-CONT 1.Configure the QoS mode to priority-queue (default) and the queue priority to 3.

NOTE






c. (Optional) Add an alarm profile.l The ID of the default GPON alarm profile is 1. The thresholds of all the alarm






a. Add an ONU.Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound line profile IDis 10.There are two ways to add an ONU. Select either of the two ways according to actualconditions.


Configuration Guide


Issue 04 (2011-04-27)

l Add an ONU offline: If the password or SN of an ONU is obtained, you can runthe ont add command to add the ONU offline.

l Automatically find an ONU: If the password or SN of an ONU is unknown, runthe port ont-auto-find command in the GPON mode to enable the ONU auto-findfunction of the GPON port. Then, run the ont confirm command to confirm theONU.

To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example. ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10




After an ONU is added, run the display ont info command to query the current status ofthe ONU. Ensure that Control flag of the ONU is active, Run State is online, Configstate is normal, and Match state is match.huawei(config-if-gpon-0/3)#display ont info 1 1 --------------------------------------------------------------------- F/S/P : 0/3/1 ONT-ID : 1 Control flag : active //Indicates that the ONU is activated. Run state : online //Indicates that the ONU already goes online normally. Config state : normal //Indicates that the configuration status of the ONU is normal. Match state : match //Indicates that the capability profile bound



9-129

to the ONU is //consistent with the actual capability of the ONU. //The rest of the response information is omitted.

If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match, referto the following suggestions to rectify the fault.l If Control flag is deactive, run the ont activate command in the GPON port mode to

activate the ONU.l If the ONU fails to be in the up state, that is, Run state is offline, the physical line may

be broken or the optical transceiver may be damaged. You need to check both thematerial and the line.







a. Configure the inband management VLAN and IP address of the OLT.To log in to the ONU through Telnet and configure the ONU from the OLT, you mustconfigure the inband management VLANs and IP addresses of the OLT and the ONUon the OLT.Create management VLAN 8 and add upstream port 0/19/0 to it. Configure the inbandmanagement IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

b. 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 and the managementVLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

c. Configure an inband management service port.


Configuration Guide


Issue 04 (2011-04-27)

Configure the management service port ID to 0, management VLAN ID to 8, GEMport ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT isnot limited. Therefore, use traffic profile 6 (default). To limit the rate of the serviceport, run the traffic table ip command to add a traffic profile and bind it to the serviceport.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6



the ONU.7. Configure the IP address of the loopback interface.




Configure the MPLS LSR ID. Set the local LSR ID to the IP address of loopback interface0.


Globally enable MPLS, MPLS TE, MPLS RSVP-TE and CSPF functions.

huawei(config)#mplshuawei(config-mpls)#mpls tehuawei(config-mpls)#mpls rsvp-tehuawei(config-mpls)#mpls te cspfhuawei(config-mpls)#quit



9. Enable the MPLS TE function for VLAN and VLAN interface.



Configure the IP address of VLAN interface 800 to 10.50.50.50/24, and enable the MPLSRSVP-TE function for VLAN interface 800.

huawei(config)#interface vlanif 800huawei(config-if-vlanif800)#ip address 10.50.50.50 24huawei(config-if-vlanif800)#mplshuawei(config-if-vlanif800)#mpls tehuawei(config-if-vlanif800)#mpls rsvp-tehuawei(config-if-vlanif800)#quit


PWE3 has no special requirement for the routing policy. Either a static route or an OSPFdynamic route can be configured. Because OSPF supports MPLS RSVP-TE extension, anOSPF dynamic route is recommended.



9-131

Configure the OSPF process ID to 100 and OSPF area ID to 1. Then, configure the interfaces(VLAN interface and loopback interface) that run OSPF and the areas of the interfaces.

huawei(config)#ospf 1huawei(config-ospf-1)#opaque-capability enable..//Enable the opaque capabilityhuawei(config-ospf-1)#area 100huawei(config-ospf-1-area-0.0.0.100)#mpls-te enable standard-complying //Enable MPLS TE for the OSPF areahuawei(config-ospf-1-area-0.0.0.100)#network 10.50.50.0 0.0.0.255huawei(config-ospf-1-area-0.0.0.100)#network 20.20.20.20 0.0.0.0huawei(config-ospf-1-area-0.0.0.100)#return


Configure the tunnel ID to 10 and the encapsulation protocol of the tunnel interface at thedata link layer to MPLS TE.

huawei(config)#interface tunnel 10huawei(config-if-tunnel10)#tunnel-protocol mpls te


NOTEThe destination IP address of the tunnel indicates the LSR ID of the tunnel termination (the next LSRtraversed by the OLT). To simplify the configuration, assume that no other LSRs exist between the OLTand the PTN. The destination IP address is the LSR ID of the PTN, namely 30.30.30.30.


Configure the ID of the MPLS TE tunnel interface to 10. The tunnel ID and LSR ID uniquelyidentify an MPLS TE tunnel.

huawei(config-if-tunnel10)#mpls te tunnel-id 10

Configure the signaling protocol of the MPLS TE tunnel to RSVP-TE.

huawei(config-if-tunnel10)#mpls te signal-protocol rsvp-te

Configure the MPLS TE tunnel for being bound by a VPN instance.

huawei(config-if-tunnel10)#mpls te reserved-for-binding


huawei(config-if-tunnel10)#mpls te commithuawei(config-if-tunnel10)#quit

12. Configure the tunnel policy.

Configure the policy name to mpls-rsvp, bind the policy to tunnel 10, and configure thedestination IP address of the tunnel to 30.30.30.30.

NOTEThe destination IP address should be consistent with that configured in the MPLS TE tunnel.

huawei(config)#tunnel-policy mpls-rsvpInfo: New tunnel-policy is configured.huawei(config-tunnel-policy-mpls-rsvp)#tunnel binding destination 30.30.30.30 te tunnel 10huawei(config-tunnel-policy-mpls-rsvp)#quit

13. Create the PW parameters.

a. Configure the PW ID to 3.huawei(config)#pw-para 3

b. Configure the loopback interface IP address of the remote PTN device in the PW.Configure the loopback interface IP address to 30.30.30.30.


Configuration Guide


Issue 04 (2011-04-27)

huawei(config-pw-para-3)#peer-address 30.30.30.30

c. Configure the PW type to ethernet tagged.huawei(config-pw-para-3)#pw-type ethernet tagged

d. Configure the PW to support control word.When the VCCV ping works in the control word mode, you need to enable the controlword. It is recommended that you enable the control word mode.huawei(config-pw-para-3)#control-word

e. Enable the VCCV function.VCCV is an end-to-end PW fault detection and diagnosis mechanism. Simply, VCCVis a control channel for the PW to send verification messages between the ingress andegress.huawei(config-pw-para-3)#vccv cc cw alert ttl cv lsp-ping

f. Configure the tunnel policy used by the PW.Configure the tunnel policy name to mpls-rsvp.huawei(config-pw-para-3)#tnl-policy mpls-rsvphuawei(config-pw-para-3)#quit

14. Configure an emulation service port.

Configure the service port ID to 1, SVLAN ID to 20, GEM port ID to 1, and CVLAN IDto 20. Rate limitation for upstream and downstream packets is performed on the MDUinstead of on the OLT. Therefore, use traffic profile 6 (default). To limit the rate of theservice port, run the traffic table ip command to add a traffic profile and bind it to theservice port.


huawei(config)#vlan 20 smarthuawei(config)#service-port vlan 20 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 20 tag-transform translate rx-cttr 6 tx-cttr 6

15. Bind the ETH service to the PW.

The static PW encapsulation mode is adopted. Such a PW does not use the signalingprotocol for parameter negotiation. You can manually specify the related information byrunning the related command. Set the emulation SVLAN ID to 20, PW ID to 3, transmit-label to 8500, and receive-label to 8510.

huawei(config)#pw-ac-binding vlan 20 pw 3 static transmit-label 8500 receive-label 8510

NOTEWhen you configure a static ETH PW, the PW transmit-label on the OLT must be the same as the receive-label on the peer PE, and the receive-label on the OLT must be the same as the PW transmit-label on thepeer PE (the PTN in this example).







9-133










Step 2 Configure the ONU.

NOTEBecause the management VLAN and the management IP address have been configured, you can run the telnet192.168.50.2 command on the OLT to log in to the ONU to perform the configuration. You can also log in tothe ONU through a serial port to perform the configuration.


The SVLAN must correspond to the CVLAN on the OLT.

Create smart SVLAN 20 and add upstream port 0/0/0 to it.


2. Configure an Ethernet access service port.Set the service port index to 1, SVLAN to 20, user-side GE port to 0/4/0, and user-side(base station side) VLAN to 20.huawei(config)#service-port 1 vlan 20 eth 0/4/0 multi-service user-vlan 20 rx-cttr 6 tx-cttr 6





Configuration Guide


Issue 04 (2011-04-27)



----End


Configuration FileConfigure the OLT.vlan 800 smartport vlan 800 0/19 0vlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name ETH type1 fix 102400ont-lineprofile gpon profile-id 10tcont 1 dba-profile-name ETHgem add 0 eth tcont 1 priority-queue 3gem add 1 eth tcont 1 priority-queue 3mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 20commitquitinterface gpon 0/3port 1 ont-auto-find enableont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6interface loopback 0ip address 20.20.20.20 32quitmpls lsr-id 20.20.20.20mplsmpls templs te rsvp-templs te cspfquitmpls l2vpninterface vlanif 800ip address 10.50.50.50 24mplsmpls templs te rsvp-tequitospf 1opaque-capability enablearea 100mpls-te enable standard-complyingnetwork 10.50.50.50 0.0.0.255network 20.20.20.20 0.0.0.0returninterface tunnel 10



9-135

tunnel-protocol mpls tedestination 30.30.30.30mpls te tunnel-id 10mpls te signal-protocol rsvp-templs te reserved-for-bindingmpls te commitquittunnel-policy mpls-rsvptunnel binding destination 30.30.30.30 te tunnel 10quitpw-para 3peer-address 30.30.30.30pw-type ethernet taggedcontrol-wordvccv cc cw alert ttl cv lsp-pingtnl-policy mpls-rsvpquitvlan 20 smartservice-port vlan 20 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 20 tag-transform translate rx-cttr 6 tx-cttr 6pw-ac-binding vlan 20 pw 3 static transmit-label 8500 receive-label 8510queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

Configure the ONU.vlan 20 smartport vlan 20 0/0 0service-port 1 vlan 20 eth 0/4/0 multi-service user-vlan 20 rx-cttr 6 tx-cttr 6save

9.5.7 Configuring the QinQ Private Line Base station access Servicefor the OLT

The ONU is connected to the IP-based station through the FE/GE port and the OLT transmitsthe QinQ private line service to the MAN device, implementing the base station access service.The ONUs support this service are MA5612 and MA5628.



l The service configuration adopts a simple and mature scheme, featuring a high transmissionefficiency in addition to ensuring the QoS.

Figure 9-18 shows an example network of the QinQ private line base station access service onthe OLT.

The ONU receives the ETH service data from the 3G base station through the FE/GE port,encapsulates the ETH packets into GEM frames, and then sends them to the OLT through theGPON upstream port. The OLT restores the ETH signals and configures the QinQ VLANencapsulation mode so that the base station data can be transparently transmitted to the peer PTNthrough the public network. Finally, the PTN device restores the original ETH signals.


Configuration Guide


Issue 04 (2011-04-27)

Figure 9-18 Example network of the QinQ private line base station access service

Data PlanTable 9-14 provides the data plan for the OLT and Table 9-15 provides the data plan for theONU.

Table 9-14 Data plan for configuring the QinQ private line base station access service-OLT side

Item Data

VLAN Inband management VLAN: smart VLAN 8SVLAN: smart VLAN 2000 with the attribute QinQ



DBA profile Profile name: PrivateLineType: type3Assured bandwidth: 20 Mbit/sMaximum bandwidth: 50 Mbit/s

ONU line profile Profile ID: 10GEM Port ID: 0 and 1T-CONT ID: 5Bind T-CONT 5 to the DBA profile named PrivateLine




9-137

Table 9-15 Data plan for configuring the QinQ private line base station access service-MA5612side

Item Data

VLAN Inband management VLAN: smart VLAN 8, adding GPONupstream port 0/0/0 to this VLANSVLAN: smart VLAN 2000 with the attribute common, addingGPON upstream port 0/0/0 to the VLANTab of the ETH packets on the base station side: VLAN tag 20

ETH service port 0/4/0


Procedure

Step 1 Configure the OLT.



huawei(config)#vlan 2000 smarthuawei(config)#vlan attrib 2000 q-in-qhuawei(config)#port vlan 2000 0/19 0

2. Enable the transparent transmission of protocol packets for VLAN 2000.

l Enable the protocol packet forwarding switch.

By default, the protocol packet forwarding switch is enabled. Therefore, you need notconfigure this function.huawei(config)#protocol permit-forwarding eapol enablehuawei(config)#protocol permit-forwarding efm enablehuawei(config)#protocol permit-forwarding lacp enablehuawei(config)#protocol permit-forwarding mstp enable

l Enable the transparent transmission of BPDUs.

Enable the transparent transmission of BPDUs so that the Layer 2 protocol packets ofa private network can be transparently transmitted through the public network.huawei(config)#bpdu tunnel vlan 2000 enable


GPON ONU profiles include the DBA profile, line profile, service profile, and alarmprofile.

l DBA profile: A DBA profile describes the GPON traffic parameters. A T-CONT isbound to a DBA profile for dynamic bandwidth allocation, improving the upstreambandwidth usage rate.


l Service profile: A service profile provides the service configuration channel for theONU that is managed through OMCI.


Configuration Guide


Issue 04 (2011-04-27)


a. Add a DBA profile.

You can at first run the display dba-profile command to query the DBA profilesexisting in the system. If the DBA profiles existing in the system do not meet therequirements, you need to run the dba-profile add command to add a DBA profile.

Configure the DBA profile name to PrivateLine, profile type to type1, assuredbandwidth to 20 Mbit/s and maximum bandwidth to 50 Mbit/s.huawei(config)#dba-profile add profile-name PrivateLine type3 assure 20480 max 51200

b. Add an ONU line profile.

Add GPON MDU line profile 10, bind T-CONT 5 to DBA profile named PrivateLine.In this way, the T-CONT can provide flexible DBA solutions based on differentconfigurations in the DBA profile.huawei(config)#ont-lineprofile gpon profile-id 10huawei(config-gpon-lineprofile-10)#tcont 5 dba-profile-name PrivateLine

Add GEM port 0 for transmitting management traffic streams and GEM port 1 fortransmitting ETH service streams. Bind GEM port 0 and GEM port 1 to T-CONT 5.Configure the QoS mode to priority-queue (default) and the queue priority to 3.

NOTE






c. (Optional) Add an alarm profile.

l The ID of the default GPON alarm profile is 1. The thresholds of all the alarmparameters in the default alarm profile are 0, which indicates that no alarm isgenerated.






9-139


a. Add an ONU.Connect the ONU to GPON port 0/3/1. The ONU ID is 1, the SN is48575443E6D8B541, the management mode is SNMP, and the bound line profile IDis 10.There are two ways to add an ONU. Select either of the two ways according to actualconditions.l Add an ONU offline: If the password or SN of an ONU is obtained, you can run



To add an ONU offline, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont add 1 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10

To automatically find an ONU, do as follows:huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#port 1 ont-auto-find enablehuawei(config-if-gpon-0/3)#display ont autofind 1 //After this command is executed, the information about all ONUs connected to //the GPON port through the optical splitter is displayed. Take the MA5612 for example. ------------------------------------------------------------ Number : 1 F/S/P : 0/3/1 Ont SN : 48575443E6D8B541 Password : VenderID : HWTC Ont Version : MA5612 Ont SoftwareVersion : V800R308C00 Ont EquipmentID : SmartAX MA5612 Ont autofind time : 2010-03-10 11:20:16 ------------------------------------------------------------huawei(config-if-gpon-0/3)#ont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10




After an ONU is added, run the display ont info command to query the current status ofthe ONU. Ensure that Control flag of the ONU is active, Run State is online, Configstate is normal, and Match state is match.


Configuration Guide


Issue 04 (2011-04-27)


If the ONU state fails, the ONU fails to be in the up state, or the ONU does not match, referto the following suggestions to rectify the fault.l If Control flag is deactive, run the ont activate command in the GPON port mode to

activate the ONU.l If the ONU fails to be in the up state, that is, Run state is offline, the physical line may

be broken or the optical transceiver may be damaged. You need to check both thematerial and the line.







a. Configure the inband management VLAN and IP address of the OLT.To log in to the ONU through Telnet and configure the ONU from the OLT, you mustconfigure the inband management VLANs and IP addresses of the OLT and the ONUon the OLT.Create management VLAN 8 and add upstream port 0/19/0 to it. Configure the inbandmanagement IP address to 192.168.50.1/24.huawei(config-if-gpon-0/3)#quithuawei(config)#vlan 8 smarthuawei(config)#port vlan 8 0/19 0huawei(config)#interface vlanif 8



9-141

huawei(config-if-vlanif8)#ip address 192.168.50.1 24huawei(config-if-vlanif8)#quit

b. 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 and the managementVLAN ID to 8 (the same as the management VLAN of the OLT).huawei(config)#interface gpon 0/3huawei(config-if-gpon-0/3)#ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8

c. Configure an inband management service port.

Configure the management service port ID to 0, management VLAN ID to 8, GEMport ID to 0, and CVLAN ID to 8. The rate of the inband service port on the OLT isnot limited. Therefore, use traffic profile 6 (default). To limit the rate of the serviceport, run the traffic table ip command to add a traffic profile and bind it to the serviceport.huawei(config-if-gpon-0/3)#quithuawei(config)#service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6


l On the OLT, run the ping 192.168.50.2 command to check the connectivity to the ONU.The ICMP ECHO-REPLY packet from the ONU should be received.

l You can run the telnet 192.168.50.2 command to telnet to the ONU and then configurethe ONU.

8. Add the service port.

Configure the service port ID to 1, SVLAN ID to 2000, GEM port ID to 1, and CVLANID to 20. Rate limitation for upstream and downstream packets is performed on the MDUinstead of on the OLT. Therefore, use traffic profile 6 (default). To limit the rate of theservice port, run the traffic table ip command to add a traffic profile and bind it to theservice port.

The CVLAN must be the same as the upstream VLAN of the MA5612.

huawei(config)#service-port 1 vlan 2000 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 20 tag-transform default rx-cttr 6 tx-cttr 6








Configuration Guide


Issue 04 (2011-04-27)




Step 2 Configure the ONU.NOTE

Because the management VLAN and the management IP address have been configured, you can run the telnet192.168.50.2 command on the OLT to log in to the MA5612 to perform the configuration. You can also log into the MA5612 through a serial port to perform the configuration.


The selection of SVLAN is flexible, which is mainly based on the VLAN switching policyof the MA5612 for base station packets.l After VLAN switching, if the VLAN tag of the MA5612 upstream packet is the same

as the VLAN tag of the base station, configure the SVLAN to be the same as the basestation VLAN.

l After VLAN switching, if the VLAN tag of the MA5612 upstream packet is not thesame as the VLAN tag of the base station, the SVLAN can be different from the basestation VLAN.

l In both cases, the SVLAN of the MA5612 must be the same as the user-side VLAN onthe OLT.

In this example, the MA5612 SVLAN is the same as the base station VLAN.

Configure the SVLAN ID to 20, type to smart, attribute to common, and upstream port to0/0/0.


2. Create a traffic profile.

You can run the display traffic table ip command to query the traffic profiles existing inthe system. If the traffic profiles existing in the system do not meet the requirements, youneed to run the traffic table ip command to add a traffic profile.

Add traffic profile 10, with the assured data rate 10240 kbit/s, priority 4, and prioritystrategy of scheduling by the priority in the packets.

huawei(config)#traffic table ip index 10 cir 10240 priority 4 priority-policy tag-In-Package

3. Create an ETH service port.

Create an ETH service port for VLAN 20. Perform VLAN switching (in this example, theVLAN tag remains the same after switched) on the base station packets from ETH port0/4/0 and then transmit them to the OLT through an upstream port. In addition, use trafficprofile 10.

huawei(config)#service-port vlan 20 eth 0/4/0 multi-service user-vlan 20 rx-cttr 10 tx-cttr 10


----End



9-143



vlan 2000 smartvlan attrib 2000 q-in-qport vlan 2000 0/19 0protocol permit-forwarding eapol enableprotocol permit-forwarding efm enableprotocol permit-forwarding lacp enableprotocol permit-forwarding mstp enablebpdu tunnel vlan 2000 enablevlan 8 smartport vlan 8 0/19 0interface vlanif 8ip address 192.168.50.1 24quitdba-profile add profile-name PrivateLine type3 assure 20480 max 51200ont-lineprofile gpon profile-id 10tcont 5 dba-profile-name PrivateLinegem add 0 eth tcont 5 priority-queue 3gem add 1 eth tcont 5 priority-queue 3mapping-mode vlangem mapping 0 0 vlan 8gem mapping 1 1 vlan 20commitquitinterface gpon 0/3port 1 ont-auto-find enableont confirm 1 ontid 1 sn-auth 48575443E6D8B541 snmp ont-lineprofile-id 10 desc MA5612_0/3/1/1_lineprofile10ont ipconfig 1 1 static ip-address 192.168.50.2 mask 255.255.255.0 vlan 8ont alarm-profile 1 1 profile-id 1service-port 0 vlan 8 gpon 0/3/1 ont 1 gemport 0 multi-service user-vlan 8 rx-cttr 6 tx-cttr 6service-port 1 vlan 2000 gpon 0/3/1 ont 1 gemport 1 multi-service user-vlan 20 tag-transform default rx-cttr 6 tx-cttr 6queue-scheduler wrr 10 10 20 20 40 0 0 0cos-queue-map cos0 0 cos1 1 cos2 2 cos3 3 cos4 4 cos5 5 cos6 6 cos7 7save

Configure the ONU.

vlan 20 smartport vlan 20 0/0 0traffic table ip index 10 cir 10240 priority 4 priority-policy tag-In-Packageservice-port vlan 20 eth 0/4/0 multi-service user-vlan 20 rx-cttr 10 tx-cttr 10save


Configuration Guide


Issue 04 (2011-04-27)

10 Configuring the P2P Optical Fiber AccessService

About This Chapter

This topic describes the P2P optical fiber access technology and how to configure the P2P opticalfiber access service on the OLT.

10.1 Configuring MDUs Subtended to an OLTMDUs are subtended to an OLT through the OPGD board, thereby saving upstream optical fibersand simplifying the network and service configuration.

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 10 Configuring the P2P Optical Fiber Access Service


10-1

10.1 Configuring MDUs Subtended to an OLTMDUs are subtended to an OLT through the OPGD board, thereby saving upstream optical fibersand simplifying the network and service configuration.

Service Requirementsl MDU_1 and MDU_2 are connected to an OLT through GE subtending, implementing the

Internet access service.l The Internet access service is provided in the PPPoE dialing mode.

Figure 10-1 Network of MDUs subtended to an OLT

Table 10-1 Data plan

Item Data

OLT SVLAN ID: 100SVLAN type: smart VLAN

CVLAN ID: 200


MDU_1 SVLAN ID: 200SVLAN type: smart VLAN


MDU_2 SVLAN ID: 200SVLAN type: smart VLAN



1. Configure the port role.Configure the port role of the OPGD board as a subtending port. The port roles of theOPGD board are user port and subtending port. By default, the port role is user port.

10 Configuring the P2P Optical Fiber Access ServiceSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

huawei(config)#interface opg 0/2huawei(config-if-opg-0/2)#network-role cascadehuawei(config-if-opg-0/2)#quit

2. Create a VLAN and add an upstream port to the VLAN.Create smart SVLAN 100. The upstream port is port 0/19/0.huawei(config)#vlan 100 smarthuawei(config)#port vlan 100 0/19 0

3. Configure a service port.Add the service port to the SVLAN by using default traffic profile 6. The CVLAN IDis 200, the same as the upstream VLAN ID of the MDU. MDU_1 and MDU_2 areconnected to ports 0/2/0 and 0/2/1 of the OLT respectively.huawei(config)#service-port vlan 100 eth 0/2/0 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6huawei(config)#service-port vlan 100 eth 0/2/1 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6


l Configure the MDUs.The configurations of MDU_1 and MDU_2 are the same. The configuration of MDU_1 isused as an example.1. Create a VLAN and add an upstream port to the VLAN.

Create smart SVLAN 200. The upstream port is port 0/8/0.

NOTEThe SVLAN of the MDU must be the same as the CVLAN of the OLT.huawei(config)#vlan 200 smarthuawei(config)#port vlan 200 0/8 0

2. Configure a service port.According to actual conditions, an MDU supports multiple access modes. In thisexample, the ETH access mode is used. For other access modes, see the correspondingconfiguration guide of the MDU.huawei(config)#service-port vlan 200 eth 0/3/0 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6


----End

ResultOn the PC, the Internet access service is provided in the PPPoE dialing mode.

Configuration FileConfigure the OLT:

interface opg 0/2network-role cascadequitvlan 100 smartport vlan 100 0/19 0service-port vlan 100 eth 0/2/0 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide 10 Configuring the P2P Optical Fiber Access Service


10-3

service-port vlan 100 eth 0/2/1 multi-service user-vlan 200 rx-cttr 6 tx-cttr 6save

Configure the MDU:

vlan 200 smartport vlan 200 0/19 0service-port vlan 200 eth 0/3/0 multi-service user-vlan untagged rx-cttr 6 tx-cttr 6save

10 Configuring the P2P Optical Fiber Access ServiceSmartAX MA5612 Multi-service Access Module

Configuration Guide


Issue 04 (2011-04-27)

A Acronyms and Abbreviations

A

AG Access Gateway

ATM Asynchronous Transfer Mode

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

DHCPoption82 DHCP relay agent option 82

E

EPON Ethernet Passive Optical Network

F

FoIP Fax over Internet Protocol

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide A Acronyms and Abbreviations


A-1

FTP File Transfer Protocol

G

GE Gigabit Ethernet

GEM GPON Encapsulation Method

GPON Gigabit-capable Passive Optical Networks

I

IP Internet Protocol

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

O

OLT Optical Line Terminal

ONT Optical Network Terminal

ONU Optical Network Unit

P

A Acronyms and AbbreviationsSmartAX MA5612 Multi-service Access Module

Configuration Guide

A-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 04 (2011-04-27)

PITP Policy Information Transfer Protocol

PON Passive Optical Network

POTS Plain Old Telephone Service

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

T

T-CONT Transmission Container

TCP/IP Transmission Control Protocol/Internet Protocol

TFTP Trivial File Transfer Protocol

U

UDP User Datagram Protocol

V

VLAN Virtual LAN

VOD Video On Demand

VoIP Voice over Internet Protocol

SmartAX MA5612 Multi-service Access ModuleConfiguration Guide A Acronyms and Abbreviations


A-3

Technology

Ma5612 configuration guide(v800 r308c00 04)