00423994-Configuration Guide(V100R001_06)

OptiX PTN 3900 Packet Transport Platform of PTN Series

V100R001

Configuration Guide

Issue 06

Date 2009-06-01

Part Number 00423994

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

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2009. 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 the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe 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 the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

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

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Starting the T2000.......................................................................................................................1-11.1 Starting or Shutting Down the T2000.............................................................................................................1-2

1.1.1 Starting the Computer............................................................................................................................1-21.1.2 Starting the T2000 Server......................................................................................................................1-31.1.3 Viewing the T2000 Process Status.........................................................................................................1-41.1.4 Logging In to the T2000 Client..............................................................................................................1-41.1.5 Exiting a T2000 Client...........................................................................................................................1-51.1.6 Shutting Down the T2000 Server...........................................................................................................1-61.1.7 Shutting Down the Computer.................................................................................................................1-6

1.2 Entering the T2000 Common Views...............................................................................................................1-71.2.1 Opening the Main Topology..................................................................................................................1-71.2.2 Opening the NE Explorer.......................................................................................................................1-8

2 Creating Network.......................................................................................................................2-12.1 Creating NEs...................................................................................................................................................2-3

2.1.1 Creating NEs in Batches........................................................................................................................2-32.1.2 Creating a Single NE..............................................................................................................................2-5

2.2 Creating an NE User.......................................................................................................................................2-62.3 Switching a Logged-In NM User....................................................................................................................2-82.4 Configuring NE Data......................................................................................................................................2-82.5 Adding Boards.................................................................................................................................................2-92.6 Adding Sub-Boards.......................................................................................................................................2-102.7 Configuring the Equipment-Level Protection...............................................................................................2-11

2.7.1 Creating a TPS Protection Group of Sub-Boards.................................................................................2-112.7.2 Querying the Board 1+1 Protection Group..........................................................................................2-12

2.8 Creating Fibers for PTN Equipment Manually.............................................................................................2-122.9 Creating a Topology Subnet..........................................................................................................................2-132.10 Configuring Inband DCN............................................................................................................................2-142.11 Configuring Clocks.....................................................................................................................................2-15

2.11.1 Setting the Frequency Selection Mode...............................................................................................2-162.11.2 Setting the PTP Clock........................................................................................................................2-162.11.3 Configuring the NE Clock Source.....................................................................................................2-16

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Contents

Issue 06 (2009-06-01) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

2.11.4 Configuring the Clock Source Protection..........................................................................................2-172.11.5 Configuring Switching Conditions for Clock Sources.......................................................................2-182.11.6 Configuring the Clock Source Reversion...........................................................................................2-192.11.7 Configuring the Phase-Locked Source for External Clock Output....................................................2-192.11.8 Setting the Clock Source Quality.......................................................................................................2-202.11.9 Configuring the SSM Output.............................................................................................................2-212.11.10 Switching a Clock Source................................................................................................................2-21

2.12 Configuring Linear MSP.............................................................................................................................2-222.12.1 Linear MSP........................................................................................................................................2-222.12.2 Configuring Linear MSP....................................................................................................................2-23

2.13 Parameter Description.................................................................................................................................2-24

3 Configuring the QoS Policy.....................................................................................................3-1

4 Configuring Interfaces..............................................................................................................4-14.1 Configuring SDH Interfaces............................................................................................................................4-5

4.1.1 Setting the General Attributes of SDH Interfaces..................................................................................4-74.1.2 Setting the Layer 2 Attributes of SDH Interfaces..................................................................................4-84.1.3 Setting the Layer 3 Attributes of SDH Interfaces..................................................................................4-84.1.4 Setting the Advanced Attributes of SDH Interfaces..............................................................................4-9

4.2 Configuring PDH Interfaces..........................................................................................................................4-104.2.1 Setting General Attributes of PDH Interfaces......................................................................................4-124.2.2 Setting the Layer 3 Attributes of PDH Interfaces................................................................................4-124.2.3 Setting the Advanced Attributes of PDH Interfaces............................................................................4-13

4.3 Configuring Ethernet Interfaces....................................................................................................................4-144.3.1 Setting the General Attributes of Ethernet Interfaces..........................................................................4-164.3.2 Setting the Layer 2 Attributes of Ethernet Interfaces...........................................................................4-174.3.3 Setting the Layer 3 Attributes of an Ethernet Interface........................................................................4-174.3.4 Setting the Advanced Attributes of Ethernet Interfaces.......................................................................4-184.3.5 Configuring Flow Control....................................................................................................................4-18

4.4 Configuring Serial Interfaces........................................................................................................................4-194.4.1 Creating Serial Interfaces.....................................................................................................................4-204.4.2 Setting the General Attributes of a Serial Interface.............................................................................4-214.4.3 Setting the Layer 3 Attributes of Serial Interfaces...............................................................................4-22

4.5 Configuring ML-PPP....................................................................................................................................4-234.5.1 Creating MP Groups.............................................................................................................................4-244.5.2 Configuring Member Interfaces of MP Groups...................................................................................4-26

4.6 Configuring an Ethernet Virtual Interface.....................................................................................................4-274.6.1 Setting the General Attributes of Ethernet Virtual Interfaces..............................................................4-274.6.2 Setting the Layer 3 Attributes of Ethernet Virtual Interfaces..............................................................4-27

4.7 Configuring Ethernet Link Aggregation Group............................................................................................4-284.8 Configuring the IMA.....................................................................................................................................4-284.9 Parameter Description...................................................................................................................................4-29

ContentsOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

5 Configuring the Control Plane................................................................................................5-15.1 Basic Concepts................................................................................................................................................5-3

5.1.1 IGP-ISIS Protocol..................................................................................................................................5-35.1.2 MPLS-LDP Protocol..............................................................................................................................5-45.1.3 MPLS-RSVP Protocol............................................................................................................................5-65.1.4 ARP Protocol..........................................................................................................................................5-7

5.2 Configuring the IGP-ISIS Protocol...............................................................................................................5-105.2.1 Setting Node Attributes........................................................................................................................5-105.2.2 Setting Port Attributes..........................................................................................................................5-115.2.3 Configuring Parameters of Route Importing........................................................................................5-125.2.4 Querying the Link TE Information......................................................................................................5-13

5.3 Configuring the MPLS-LDP Protocol...........................................................................................................5-135.3.1 Creating MPLS-LDP Peer Entities......................................................................................................5-135.3.2 Configuring the MPLS-LDP Protocol..................................................................................................5-14

5.4 Configuring the MPLS-RSVP Protocol........................................................................................................5-145.5 Configuring Static Routes.............................................................................................................................5-155.6 Configuring the Address Parse......................................................................................................................5-165.7 Parameter Description...................................................................................................................................5-17

6 Configuring an MPLS Tunnel.................................................................................................6-16.1 Basic Concepts................................................................................................................................................6-3

6.1.1 MPLS and MPLS Tunnel.......................................................................................................................6-36.1.2 Application of the MPLS Tunnel...........................................................................................................6-3

6.2 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail Function.............................6-56.3 Creating a Static MPLS Tunnel by Using the Trail Function.......................................................................6-106.4 Configuring Basic Attributes of the MPLS...................................................................................................6-126.5 Creating an MPLS Tunnel on a Per-NE Basis..............................................................................................6-136.6 Querying the Tunnel Label Information.......................................................................................................6-146.7 Configuring MPLS OAM..............................................................................................................................6-146.8 Creating an MPLS Tunnel Protection Group................................................................................................6-156.9 Configuration Case of the Dynamic MPLS Tunnel......................................................................................6-17

6.9.1 Networking Diagram............................................................................................................................6-176.9.2 Service Planning...................................................................................................................................6-186.9.3 Creating a Dynamic MPLS Tunnel......................................................................................................6-20

6.10 Configuration Case of the Static MPLS Tunnel..........................................................................................6-266.10.1 Networking Diagram..........................................................................................................................6-276.10.2 Service Planning.................................................................................................................................6-286.10.3 Creating a Static MPLS Tunnel by Using the Trail Function............................................................6-306.10.4 Configuring a Static MPLS Tunnel on a Per-NE Basis.....................................................................6-35

6.11 Parameter Description.................................................................................................................................6-40

7 Configuring an IP Tunnel........................................................................................................7-17.1 IP Tunnel.........................................................................................................................................................7-27.2 Creating IP Tunnels.........................................................................................................................................7-2



iii

7.3 Parameter Description.....................................................................................................................................7-3

8 Configuring a GRE Tunnel......................................................................................................8-18.1 GRE Tunnel.....................................................................................................................................................8-28.2 Creating GRE Tunnels....................................................................................................................................8-28.3 Parameter Description.....................................................................................................................................8-3

9 Configuring a CES Service.......................................................................................................9-19.1 CES Service Type........................................................................................................................................... 9-29.2 Configuration Flow of CES Services..............................................................................................................9-59.3 CES Service Operation Tasks.........................................................................................................................9-7

9.3.1 Creating a UNI-UNI CES Service by Using the Trail Function............................................................9-89.3.2 Creating a UNI-NNI CES Service by Using the Trail Function..........................................................9-109.3.3 Creating a UNI-UNI CES Service on a Per-NE Basis.........................................................................9-129.3.4 Creating a UNI-NNI CES Service on a Per-NE Basis.........................................................................9-13

9.4 Configuration Case of the UNI-UNI CES Service........................................................................................9-169.4.1 Case Description..................................................................................................................................9-169.4.2 Service Planning...................................................................................................................................9-179.4.3 Configuring CES Services by Using the Trail Function......................................................................9-189.4.4 Configuring CES Services on a Per-NE Basis.....................................................................................9-21

9.5 Configuration Case of the UNI-NNI CES Service........................................................................................9-249.5.1 Case Description..................................................................................................................................9-249.5.2 Service Planning...................................................................................................................................9-269.5.3 Configuring CES Services by Using the Trail Function......................................................................9-299.5.4 Configuring CES Services on a Per-NE Basis.....................................................................................9-38

9.6 Checking the Correctness of the Service Configuration...............................................................................9-499.7 Parameter Description...................................................................................................................................9-50

10 Configuring an ATM Service...............................................................................................10-110.1 Basic Information........................................................................................................................................10-2

10.1.1 ATM Service......................................................................................................................................10-210.1.2 ATM Traffic.......................................................................................................................................10-4

10.2 ATM Service Configuration Flow..............................................................................................................10-610.3 Operation Tasks Related to ATM Services...............................................................................................10-11

10.3.1 Creating ATM Services by Using the Trail Function......................................................................10-1110.3.2 Creating ATM Services on a Per-NE Basis.....................................................................................10-15

10.4 Configuration Case of the UNI-UNI ATM Service..................................................................................10-1910.4.1 Networking Diagram........................................................................................................................10-1910.4.2 Service Planning...............................................................................................................................10-2010.4.3 Configuring an ATM Service on a Route Basis...............................................................................10-2210.4.4 Configuring an ATM Service on a Per-NE Basis............................................................................10-27

10.5 Configuration Case of the UNIs-NNI ATM Service................................................................................10-3210.5.1 Networking Diagram........................................................................................................................10-3210.5.2 Service Planning...............................................................................................................................10-33


Configuration Guide

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

Issue 06 (2009-06-01)

10.5.3 Configuring an ATM Service on a Route Basis...............................................................................10-3610.5.4 Configuring an ATM Service on a Per-NE Basis............................................................................10-47

10.6 Verifying the Correctness of Service Configuration.................................................................................10-6610.7 Parameter Description...............................................................................................................................10-68

11 Configuring an E-Line Service............................................................................................11-111.1 E-Line Service.............................................................................................................................................11-311.2 Configuration Flow for the E-Line Service.................................................................................................11-611.3 Operation Tasks for the E-Line Service....................................................................................................11-12

11.3.1 Creating a UNI-UNI E-Line Service ...............................................................................................11-1311.3.2 Creating a UNI-NNI E-Line Service Carried by a Port...................................................................11-1411.3.3 Creating a UNI-NNI E-Line Service Carried by a PW....................................................................11-1511.3.4 Creating a QinQ Link.......................................................................................................................11-1711.3.5 Creating a UNI-NNI E-Line Service Carried by the QinQ Link.....................................................11-1811.3.6 Creating a V-UNI Group..................................................................................................................11-19

11.4 Configuration Case of the UNI-UNI E-Line Service................................................................................11-2111.4.1 Networking Diagram........................................................................................................................11-2111.4.2 Service Planning...............................................................................................................................11-2211.4.3 Configuring the E-Line Service at an NE........................................................................................11-24

11.5 Configuration Case of the UNI-NNI E-Line Service Carried by Ports.....................................................11-2711.5.1 Networking Diagram........................................................................................................................11-2711.5.2 Service Planning...............................................................................................................................11-2811.5.3 Configuring the E-Line Service at the Source NE...........................................................................11-29

11.6 Configuration Case of the UNI-NNI E-Line Service Carried by the PW.................................................11-3111.6.1 Case Description..............................................................................................................................11-3111.6.2 Service Planning...............................................................................................................................11-3211.6.3 Configuring the E-Line Service of the NE.......................................................................................11-34

11.7 Configuration Case of the UNI-NNI E-Line Service Carried by the QinQ Link......................................11-3911.7.1 Case Description..............................................................................................................................11-3911.7.2 Service Planning...............................................................................................................................11-4011.7.3 Configuring the E-Line Service ......................................................................................................11-42

11.8 Verifying the Correctness of Service Configuration.................................................................................11-4511.9 Parameter Description...............................................................................................................................11-48

12 Configuring an E-LAN Service............................................................................................12-112.1 E-LAN Service............................................................................................................................................12-212.2 Configuration Flow for E-LAN Service......................................................................................................12-312.3 Operation Tasks for the E-LAN Service.....................................................................................................12-4

12.3.1 Creating an E-LAN Service...............................................................................................................12-412.3.2 Managing the Blacklist.......................................................................................................................12-912.3.3 Setting the Broadcast Storm Suppression........................................................................................12-1012.3.4 Creating a V-UNI Group..................................................................................................................12-11

12.4 Configuration Case of the E-LAN Service...............................................................................................12-1212.4.1 Case Description..............................................................................................................................12-13



v

12.4.2 Configuring E-LAN Service for the NE..........................................................................................12-1512.5 Parameter Description...............................................................................................................................12-18

13 Configuring an E-AGGR Service........................................................................................13-113.1 E-AGGR Service.........................................................................................................................................13-213.2 Configuration Flow for the E-AGGR Service.............................................................................................13-213.3 Operation Tasks for the E-AGGR Service..................................................................................................13-4

13.3.1 Creating an E-AGGR Service............................................................................................................13-413.3.2 Creating a V-UNI Group....................................................................................................................13-6

13.4 Configuration Case of the E-AGGR Service..............................................................................................13-713.4.1 Case Description................................................................................................................................13-813.4.2 Configuring a UNIs-NNI E-AGGR Service for NEs.......................................................................13-1213.4.3 Configuring an NNIs-UNI E-AGGR Service for NEs.....................................................................13-13

13.5 Parameter Description...............................................................................................................................13-14

14 Configuring Services for the Offload Solution................................................................14-114.1 Basic Concepts............................................................................................................................................14-214.2 Service Configuration Flow for the Offload Solution.................................................................................14-514.3 ATM-Based Service Configuration Case....................................................................................................14-8

14.3.1 Case Description................................................................................................................................14-914.3.2 Configuration Process......................................................................................................................14-16

14.4 ETH-Based Service Configuration Case...................................................................................................14-2014.4.1 Case Description..............................................................................................................................14-2114.4.2 Configuration Process......................................................................................................................14-28

14.5 IP-Based Service Configuration Case.......................................................................................................14-3214.5.1 Case Description..............................................................................................................................14-3214.5.2 Configuration Process......................................................................................................................14-39

15 Configuring the External Environment Monitoring Interfaces....................................15-115.1 Application of the Environment Monitoring Interfaces..............................................................................15-215.2 Setting Attributes of the Input Relay...........................................................................................................15-315.3 Setting the Output Status of the Alarm Relay.............................................................................................15-315.4 Querying and Configuring the Board Temperature Monitoring.................................................................15-4

16 Backing up the Configuration Data....................................................................................16-116.1 Periodically Backing Up the T2000 MO Data............................................................................................16-216.2 Backing Up NE Databases..........................................................................................................................16-3

A Glossary..................................................................................................................................... A-1

B Acronyms and Abbreviations.................................................................................................B-1

C Parameter Reference................................................................................................................ C-1C.1 64KTs.............................................................................................................................................................C-7C.2 AF1 Schedule Weight....................................................................................................................................C-7C.3 AF2 Schedule Weight....................................................................................................................................C-8C.4 AF3 Schedule Weight....................................................................................................................................C-9


Configuration Guide

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

Issue 06 (2009-06-01)

C.5 AF4 Schedule Weight....................................................................................................................................C-9C.6 ATM Port Type............................................................................................................................................C-10C.7 ATM Cell Payload Scrambling....................................................................................................................C-11C.8 BPDU (E-Line)............................................................................................................................................C-12C.9 CBS..............................................................................................................................................................C-13C.10 CC Test Transmit Period...........................................................................................................................C-13C.11 CC Status...................................................................................................................................................C-14C.12 CIR.............................................................................................................................................................C-14C.13 CoS.............................................................................................................................................................C-15C.14 CRC Check Length....................................................................................................................................C-16C.15 IP Address Negotiation Result...................................................................................................................C-17C.16 IP Mask Negotiation Result.......................................................................................................................C-17C.17 Specify IP...................................................................................................................................................C-18C.18 LSP Mode..................................................................................................................................................C-19C.19 MAC Address Learning Mode...................................................................................................................C-19C.20 Self-learning MAC Address......................................................................................................................C-20C.21 MTU(byte).................................................................................................................................................C-21C.22 NNI (Ethernet Service)..............................................................................................................................C-22C.23 OAM Working Mode.................................................................................................................................C-22C.24 Enable OAM Protocol................................................................................................................................C-23C.25 PBS............................................................................................................................................................C-24C.26 PHB............................................................................................................................................................C-24C.27 PHY Loopback...........................................................................................................................................C-25C.28 PIR.............................................................................................................................................................C-26C.29 PPP Link Status..........................................................................................................................................C-27C.30 PW ID........................................................................................................................................................C-27C.31 PW Egress Label........................................................................................................................................C-28C.32 PW Direction.............................................................................................................................................C-28C.33 PW Type....................................................................................................................................................C-29C.34 PW Signaling Type....................................................................................................................................C-31C.35 QinQ Link ID.............................................................................................................................................C-31C.36 RTP Head...................................................................................................................................................C-32C.37 S-VLAN ID................................................................................................................................................C-33C.38 Tag Type....................................................................................................................................................C-33C.39 Tunnel........................................................................................................................................................C-34C.40 Enable Tunnel............................................................................................................................................C-35C.41 UNI (Ethernet Service)..............................................................................................................................C-36C.42 VCCV Verification Mode..........................................................................................................................C-36C.43 VLAN Forwarding Table Item..................................................................................................................C-37C.44 V-UNI ID...................................................................................................................................................C-37C.45 V-UNI Group Type....................................................................................................................................C-37C.46 WFQ Scheduling Policy............................................................................................................................C-38



vii

C.47 Packet Type................................................................................................................................................C-39C.48 Packet Color...............................................................................................................................................C-39C.49 Packet Loading Time.................................................................................................................................C-40C.50 Packet Loading Time (us)..........................................................................................................................C-41C.51 Duplicated Policy Name............................................................................................................................C-41C.52 Local Working Status................................................................................................................................C-42C.53 Test Result.................................................................................................................................................C-43C.54 Policy ID....................................................................................................................................................C-43C.55 Policy Name...............................................................................................................................................C-44C.56 Member Interface.......................................................................................................................................C-45C.57 Bearer Type................................................................................................................................................C-45C.58 Egress Port.................................................................................................................................................C-46C.59 Handling Mode..........................................................................................................................................C-47C.60 Handling Mode (Ethernet Unknown Frame).............................................................................................C-47C.61 Error Frame Monitor Threshold (frame)....................................................................................................C-48C.62 Error Frame Monitor Window (ms)...........................................................................................................C-49C.63 Error Frame Second Threshold (s).............................................................................................................C-49C.64 Error Frame Second Window (s)...............................................................................................................C-50C.65 Error Frame Signal Periodic Monitor Window (Entries)..........................................................................C-50C.66 Error Frame Signal Periodic Monitor Threshold (Entries)........................................................................C-51C.67 Error Frame Period Threshold (frame)......................................................................................................C-51C.68 Error Frame Period Window (frame).........................................................................................................C-52C.69 Enable Traffic Frame Discarding Flag.......................................................................................................C-52C.70 Unidirectional Operation...........................................................................................................................C-53C.71 Address Table Specified Capacity.............................................................................................................C-54C.72 Address Detection Upper Threshold (%)...................................................................................................C-54C.73 Address Detection Lower Threshold (%)..................................................................................................C-55C.74 Discard Lower Threshold (256 bytes).......................................................................................................C-56C.75 Discard Probability (%).............................................................................................................................C-57C.76 Discard Upper Threshold (256 bytes)........................................................................................................C-57C.77 Jitter Compensation Buffering Time.........................................................................................................C-59C.78 Port Transmit Status...................................................................................................................................C-59C.79 Port Receive Status....................................................................................................................................C-60C.80 Port Mode...................................................................................................................................................C-61C.81 Enable Port.................................................................................................................................................C-62C.82 Port Priority................................................................................................................................................C-63C.83 Peer IP........................................................................................................................................................C-64C.84 Transmitted Packet Length........................................................................................................................C-65C.85 Transmitted Packet Count..........................................................................................................................C-66C.86 Transmitted Packet Priority (Ethernet Service OAM)...............................................................................C-66C.87 Direction....................................................................................................................................................C-67C.88 Non-Autonegotiation Flow Control Mode (Ethernet Port)........................................................................C-68


Configuration Guide

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

Issue 06 (2009-06-01)

C.89 Encapsulation Type....................................................................................................................................C-69C.90 PIR.............................................................................................................................................................C-70C.91 Load Sharing Hash Algorithm...................................................................................................................C-71C.92 Load Sharing..............................................................................................................................................C-72C.93 Working Mode...........................................................................................................................................C-73C.94 Loopback Status (EFMOAM Parameter)..................................................................................................C-74C.95 Revertive Mode..........................................................................................................................................C-75C.96 Laser Interface Enabling Status.................................................................................................................C-77C.97 Laser Transmission Distance (m)..............................................................................................................C-77C.98 Activation Status........................................................................................................................................C-78C.99 Scrambling Capability (POS Port).............................................................................................................C-79C.100 Detection Result.......................................................................................................................................C-80C.101 Static MAC Address................................................................................................................................C-81C.102 LAG Type................................................................................................................................................C-82C.103 Control Channel Type..............................................................................................................................C-83C.104 Control Word (ATM Service)..................................................................................................................C-84C.105 Aging Ability...........................................................................................................................................C-85C.106 Aging Time (min)....................................................................................................................................C-86C.107 Connection Type......................................................................................................................................C-87C.108 Enable Differential Delay........................................................................................................................C-88C.109 Link Event Notification...........................................................................................................................C-89C.110 Traffic Classification Bandwidth Sharing...............................................................................................C-89C.111 Traffic Classification Rule.......................................................................................................................C-91C.112 Name........................................................................................................................................................C-92C.113 Default Packet Relabeling Color.............................................................................................................C-92C.114 Logical Relation Between Matched Rules...............................................................................................C-93C.115 Match Type..............................................................................................................................................C-94C.116 Match Value.............................................................................................................................................C-97C.117 Default Forwarding Priority...................................................................................................................C-100C.118 Coloration Mode....................................................................................................................................C-101C.119 Uplink Policy.........................................................................................................................................C-103C.120 Clock Mode............................................................................................................................................C-103C.121 Clock Mode (PDH/SDH Port)...............................................................................................................C-104C.122 Split Horizon Group...............................................................................................................................C-105C.123 Split Horizon Group ID.........................................................................................................................C-107C.124 Split Horizon Group Member................................................................................................................C-107C.125 Sink Interface Type................................................................................................................................C-108C.126 Sink Node...............................................................................................................................................C-109C.127 Destination Maintenance Point MAC Address......................................................................................C-110C.128 Used Port................................................................................................................................................C-110C.129 Hop Count..............................................................................................................................................C-111C.130 Wildcard.................................................................................................................................................C-112



ix

C.131 Maintenance Domain Level...................................................................................................................C-114C.132 Tail Drop Threshold (256bytes).............................................................................................................C-115C.133 Unknown Frame Processing..................................................................................................................C-116C.134 Location.................................................................................................................................................C-117C.135 Physical Port ID.....................................................................................................................................C-118C.136 System Priority (LAG)...........................................................................................................................C-118C.137 Downlink Policy....................................................................................................................................C-119C.138 Line Encoding Format...........................................................................................................................C-120C.139 Response Maintenance Point ID............................................................................................................C-120C.140 Signal Type............................................................................................................................................C-121C.141 CDVT (us).............................................................................................................................................C-122C.142 Service Type (ATM Service).................................................................................................................C-123C.143 Service Type (ATM Policy)...................................................................................................................C-124C.144 Service Type (Ethernet OAM)...............................................................................................................C-125C.145 Service Name.........................................................................................................................................C-126C.146 Source Interface Type............................................................................................................................C-127C.147 Remote OAM Parameter........................................................................................................................C-128C.148 Remote OAM Working Mode...............................................................................................................C-128C.149 Remote Side Loopback Response..........................................................................................................C-129C.150 Remote Working Status.........................................................................................................................C-130C.151 Used Timeslot........................................................................................................................................C-132C.152 Frame Format.........................................................................................................................................C-132C.153 Frame Type............................................................................................................................................C-133C.154 VC-Switching-Supported VPIs..............................................................................................................C-134C.155 Main Port...............................................................................................................................................C-135C.156 Main Port Status.....................................................................................................................................C-136C.157 Auto-Negotiation Flow Control Mode (Ethernet Port)..........................................................................C-137C.158 Compositive Working Status.................................................................................................................C-139C.159 Impedance..............................................................................................................................................C-140C.160 Max. OAM Packet Length (byte)..........................................................................................................C-140C.161 Max. VCI Bits........................................................................................................................................C-141C.162 Max. VPI Bits........................................................................................................................................C-142C.163 Max. Differential Delay (100 us)...........................................................................................................C-143C.164 Max. Concatenated Cell Count..............................................................................................................C-143C.165 Max Data Packet Size(byte)...................................................................................................................C-144C.166 MBS (Cells)...........................................................................................................................................C-145C.167 Max Frame Length(byte)-Ethernet interface.........................................................................................C-146C.168 Min. Activated Link Count....................................................................................................................C-146C.169 Direction................................................................................................................................................C-147

Index.................................................................................................................................................i-1


Configuration Guide

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

Issue 06 (2009-06-01)

Figures

Figure 2-1 Typical application...........................................................................................................................2-20Figure 2-2 SDH 1+1 linear MSP........................................................................................................................2-23Figure 2-3 SDH 1:1 linear MSP.........................................................................................................................2-23Figure 4-1 Procedure for configuring an SDH interface......................................................................................4-6Figure 4-2 Procedure for configuring a PDH interface......................................................................................4-11Figure 4-3 Procedure for configuring an Ethernet interface..............................................................................4-15Figure 4-4 Procedure for configuring a serial interface.....................................................................................4-20Figure 4-5 Procedure for configuring an MP group...........................................................................................4-24Figure 5-1 LSP tunnel created by using the MPLS-RSVP.................................................................................. 5-7Figure 5-2 ARP frame format.............................................................................................................................. 5-8Figure 5-3 ARP address resolution...................................................................................................................... 5-9Figure 5-4 Example of setting the route color....................................................................................................5-11Figure 6-1 MPLS tunnel in the MPLS network...................................................................................................6-3Figure 6-2 Transparent transmission of point-to-point data packets....................................................................6-4Figure 6-3 Protection principle for unicast tunnels..............................................................................................6-5Figure 6-4 Networking diagram of an MPLS tunnel.........................................................................................6-18Figure 6-5 NE planning......................................................................................................................................6-18Figure 6-6 Networking diagram of an MPLS tunnel.........................................................................................6-27Figure 6-7 NE planning......................................................................................................................................6-28Figure 7-1 ATM PWE3 over IP tunnel................................................................................................................7-2Figure 8-1 ATM PWE3 over GRE tunnel............................................................................................................8-2Figure 9-1 CES service networking sample.........................................................................................................9-3Figure 9-2 External Clock synchronization of CES service clock.......................................................................9-4Figure 9-3 UNI-UNI CES service configuration flow.........................................................................................9-5Figure 9-4 UNI-NNI CES service configuration flow.........................................................................................9-6Figure 9-5 Networking of the CES service........................................................................................................9-16Figure 9-6 NE planning diagram........................................................................................................................9-17Figure 9-7 Networking diagram of the CES service..........................................................................................9-25Figure 9-8 NE planning......................................................................................................................................9-25Figure 9-9 Checking the CES service................................................................................................................9-49Figure 10-1 ATM service networking sample...................................................................................................10-3Figure 10-2 ATM connection convergence sample...........................................................................................10-3Figure 10-3 Configuration flow of the UNI-UNI ATM service.........................................................................10-7

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Figures


xi

Figure 10-4 Configuration flow of the UNIs-NNI ATM service.......................................................................10-9Figure 10-5 Networking of the ATM service...................................................................................................10-20Figure 10-6 NE planning diagram....................................................................................................................10-20Figure 10-7 Networking of the ATM service...................................................................................................10-33Figure 10-8 NE planning diagram....................................................................................................................10-33Figure 10-9 Connection diagram for ATM service connectivity test...............................................................10-66Figure 11-1 UNI-UNI E-Line service................................................................................................................11-3Figure 11-2 UNI-NNI E-Line service carried by ports......................................................................................11-4Figure 11-3 UNI-NNI E-Line service carried by a PW.....................................................................................11-4Figure 11-4 UNI-NNI E-Line service carried by a QinQ link...........................................................................11-5Figure 11-5 Configuration flow for the UNI-UNI E-Line service.....................................................................11-6Figure 11-6 UNI-NNI E-Line service carried by ports......................................................................................11-7Figure 11-7 UNI-NNI E-Line service carried by PWs.......................................................................................11-9Figure 11-8 UNI-NNI E-Line service carried by QinQ Link...........................................................................11-11Figure 11-9 Networking diagram for the UNI-UNI E-Line service.................................................................11-21Figure 11-10 Networking diagram for the UNI-NNI E-Line service carried by ports....................................11-28Figure 11-11 Networking diagram for the UNI-NNI E-Line service carried by the PW.................................11-32Figure 11-12 Networking diagram for the UNI-NNI E-Line service carried by the QinQ link......................11-40Figure 11-13 OAM of the E-Line service........................................................................................................11-46Figure 12-1 E-LAN service................................................................................................................................12-2Figure 12-2 Flow diagram for configuring the E-LAN service.........................................................................12-3Figure 12-3 Networking diagram for the E-LAN service................................................................................12-13Figure 13-1 E-AGGR service.............................................................................................................................13-2Figure 13-2 Configuration flow for the E-AGGR service..................................................................................13-3Figure 13-3 E-AGGR service networking diagram............................................................................................13-9Figure 14-1 Offload solution..............................................................................................................................14-3Figure 14-2 Offload scenario for the ATM-based service.................................................................................14-3Figure 14-3 Offload scenario for the ETH-based service..................................................................................14-4Figure 14-4 Offload scenario for the IP-Based services....................................................................................14-5Figure 14-5 Configuration flow of the ATM-based service in the offload solution..........................................14-6Figure 14-6 Configuration flow of the ETH-based service in the offload solution...........................................14-7Figure 14-7 Configuration flow of the IP-based service in the offload solution................................................14-8Figure 14-8 Networking diagram of the offload application scenario based on the ATM forwarding and packetencapsulation format.........................................................................................................................................14-10Figure 14-9 Networking diagram of the offload application scenario based on the ETH forwarding and packetencapsulation format.........................................................................................................................................14-22Figure 14-10 Networking diagram of the offload application scenario based on the IP forwarding and packetencapsulation format.........................................................................................................................................14-33Figure 15-1 Application of the alarm input/output interfaces............................................................................15-2Figure C-1 Non-load sharing static LAG is created between NE A and NE B.................................................C-64

FiguresOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

Tables

Table 2-1 Attributes of NEs ...............................................................................................................................2-24Table 2-2 NE user parameters............................................................................................................................2-25Table 2-3 Descriptions of the parameters for Linear Multiplex Section Protection (LMSP) group..................2-27Table 4-1 Types of PTN service interfaces..........................................................................................................4-1Table 4-2 Application scenario of SDH interfaces...............................................................................................4-5Table 4-3 Application scenario of PDH interfaces.............................................................................................4-10Table 4-4 Application scenario of Ethernet interfaces.......................................................................................4-14Table 4-5 Application scenario of serial interfaces............................................................................................4-19Table 4-6 Descriptions of the parameters for SDH interface General Attributes...............................................4-29Table 4-7 Descriptions of the parameters for SDH interface Layer 2 Attributes...............................................4-30Table 4-8 Descriptions of the parameters for SDH interface Layer 3 Attributes...............................................4-31Table 4-9 Descriptions of the parameters for Advanced Attributes of the SDH interface.................................4-34Table 4-10 Descriptions of the parameters for PDH interface General Attributes.............................................4-34Table 4-11 Descriptions of the parameters for PDH interface Layer 3 Attributes.............................................4-35Table 4-12 Descriptions of the parameters for PDH interface Advanced Attributes.........................................4-37Table 4-13 Descriptions of the parameters for Ethernet interface General Attributes.......................................4-38Table 4-14 Descriptions of the parameters for Ethernet interface Layer 2 Attributes.......................................4-40Table 4-15 Descriptions of the parameters for Ethernet interface Layer 3 attributes........................................4-41Table 4-16 Descriptions of the parameters for Ethernet interface Advanced Attributes...................................4-43Table 4-17 Descriptions of the parameters for Ethernet interface Flow Control...............................................4-44Table 4-18 Descriptions of the parameters for Serial interface General Attributes...........................................4-45Table 4-19 Descriptions of the parameters for Serial interface Layer 3 Attributes............................................4-46Table 4-20 Descriptions of the parameters for Ethernet virtual interface General Attributes............................4-49Table 4-21 Descriptions of the parameters for Ethernet virtual interface Layer 3 Attributes............................4-50Table 4-22 Descriptions of the parameters for Link Aggregation Group Management.....................................4-51Table 4-23 Descriptions of the parameters for MP Group General Attributes...................................................4-53Table 5-1 Descriptions of the parameters for IGP-ISIS Configuration..............................................................5-17Table 5-2 Descriptions of the parameters for MPLS-LDP Configuration.........................................................5-21Table 5-3 Descriptions of the parameters for MPLS-RSVP Configuration.......................................................5-23Table 5-4 Descriptions of the parameters for Static Route Management...........................................................5-24Table 5-5 Descriptions of the parameters for Address Parse.............................................................................5-25Table 5-6 Parameters of the node configuration.................................................................................................5-25Table 5-7 Parameters of the port configuration..................................................................................................5-26

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Tables


xiii

Table 5-8 Parameters of the route importing......................................................................................................5-26Table 5-9 Parameters of the link TE information...............................................................................................5-26Table 6-1 Configuration parameters of NEs.......................................................................................................6-19Table 6-2 Configuration parameters of Tunnels.................................................................................................6-19Table 6-3 Configuration parameters of NEs.......................................................................................................6-28Table 6-4 Planning of Tunnel parameters.......................................................................................................... 6-29Table 6-5 Descriptions of the parameters for the Dynamic Tunnel in the General Attributes tab..................6-41Table 6-6 Descriptions of the parameters for the Dynamic Tunnel in the Select Node tab...............................6-41Table 6-7 Descriptions of the parameters for the Dynamic Tunnel in the Positive Route Constraint (ReverseRoute Constraint)tab.........................................................................................................................................6-42Table 6-8 Descriptions of the parameters for the Dynamic Tunnel in the Priority tab.....................................6-44Table 6-9 Descriptions of the parameters for the Dynamic Tunnel in the Fast Re-Route tab..........................6-44Table 6-10 Descriptions of the parameters for the Static Tunnel in the General Attributes tab......................6-45Table 6-11 Descriptions of the parameters for the Static Tunnel in the Select Nodes tab.................................6-45Table 6-12 Descriptions of the parameters for the static tunnel in the Route Information tab........................6-46Table 6-13 Descriptions of the parameters for the Static Tunnel in the Tunnel Information tab....................6-47Table 6-14 Descriptions of the parameters for Basic Configuration..................................................................6-47Table 6-15 Descriptions of the parameters for Static Tunnel.............................................................................6-48Table 6-16 Descriptions of the parameters for APS Protection......................................................................... 6-50Table 6-17 Descriptions of the parameters for OAM.........................................................................................6-52Table 7-1 Descriptions of the parameters for IP Tunnel Management................................................................7-3Table 8-1 Descriptions of the parameters for GRE Tunnel Management............................................................8-3Table 9-1 CES service clock type.........................................................................................................................9-4Table 9-2 Tasks for configuring the UNI-UNI CES service................................................................................9-5Table 9-3 Tasks for configuring the UNIs-NNI CES service..............................................................................9-6Table 9-4 Configuration parameters of NE1......................................................................................................9-17Table 9-5 Configuration parameters of NEs.......................................................................................................9-26Table 9-6 Planning of Tunnel parameters.......................................................................................................... 9-26Table 9-7 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots partially used)....................9-28Table 9-8 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots fully used)......................... 9-29Table 9-9 Descriptions of the parameters for CES Service Management.........................................................9-50Table 9-10 Descriptions of the parameters for Advanced Attributes of CES Service Management................ 9-53Table 9-11 Descriptions of the parameters for PW General Attributes of CES service management...............9-54Table 9-12 Descriptions of the parameters for QoS of CES Service Management............................................9-56Table 9-13 Descriptions of the parameters for Advanced Attributes of CES Service Management................. 9-57Table 10-1 ATM service type and traffic...........................................................................................................10-4Table 10-2 Tasks for configuring the UNI-UNI ATM service...........................................................................10-7Table 10-3 Tasks for configuring the UNIs-NNI ATM service.........................................................................10-9Table 10-4 Configuration parameters of NE1..................................................................................................10-20Table 10-5 Service types and QoS requirements..............................................................................................10-21Table 10-6 Configuration parameters of NEs...................................................................................................10-34Table 10-7 Planning of Tunnel parameters......................................................................................................10-34Table 10-8 Configuration parameters of NE1..................................................................................................10-35

TablesOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

Table 10-9 Configuration parameters of NE3..................................................................................................10-36Table 10-10 Descriptions of the parameters for Creating ATM Services.......................................................10-68Table 10-11 Descriptions of the parameters for PW Attributes.......................................................................10-69Table 10-12 Descriptions of the parameters for ATM Service Management by NE.......................................10-72Table 10-13 Descriptions of the parameters for ATM Connection Configuration by NE...............................10-73Table 10-14 Descriptions of the parameters for PW Configuration by NE.....................................................10-74Table 10-15 Descriptions of the parameters for CoS Mapping by NE............................................................10-77Table 10-16 Descriptions of the parameters for CoS Mapping........................................................................10-78Table 11-1 Tasks for configuring the UNI-UNI E-Line service........................................................................11-6Table 11-2 Tasks for configuring the UNI-UNI E-Line service carried by a port.............................................11-8Table 11-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs.............................................11-10Table 11-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link...................................11-12Table 11-5 Requirement of the E-Line service.................................................................................................11-22Table 11-6 Configuration parameters of NE1..................................................................................................11-22Table 11-7 Configuration parameters of QoS..................................................................................................11-22Table 11-8 Planning of the UNI-UNI E-Line service......................................................................................11-23Table 11-9 Configuration parameters of NEs...................................................................................................11-28Table 11-10 Planning of the UNI-NNI E-Line service carried by ports..........................................................11-28Table 11-11 Configuration parameters of NEs.................................................................................................11-32Table 11-12 Planning of the tunnel carrying the PW.......................................................................................11-33Table 11-13 Planning of the UNI-NNI E-Line service carried by the PW......................................................11-33Table 11-14 Planning of the PW......................................................................................................................11-34Table 11-15 Configuration parameters of NEs.................................................................................................11-40Table 11-16 Planning of the QinQ link carrying the service............................................................................11-41Table 11-17 Planning of the UNI-NNI E-Line service carried by the QinQ link............................................11-41Table 11-18 Descriptions of the parameters for V-UNI Group........................................................................11-48Table 11-19 Descriptions of the parameters for E-Line Service......................................................................11-49Table 11-20 Descriptions of the parameters for PW........................................................................................11-50Table 11-21 Descriptions of the parameters for QoS.......................................................................................11-51Table 12-1 Planning of the tunnel that carries the PW.....................................................................................12-14Table 12-2 Planning of the E-LAN service carried by a PW...........................................................................12-14Table 12-3 Planning of the UNI port................................................................................................................12-15Table 12-4 Planning of the PW........................................................................................................................12-15Table 12-5 Descriptions of the parameters for an UNI Port.............................................................................12-18Table 12-6 Descriptions of the parameters for NNI Port.................................................................................12-19Table 12-7 Descriptions of the parameters for PW..........................................................................................12-19Table 12-8 Descriptions of the parameters for QinQ Link...............................................................................12-21Table 12-9 Descriptions of the parameters for Split Horizon Group...............................................................12-22Table 12-10 Descriptions of the parameters for MAC Address Learning Parameters.....................................12-22Table 12-11 Descriptions of the parameters for Unknown Frame Processing.................................................12-23Table 12-12 Descriptions of the parameters for QoS.......................................................................................12-23Table 12-13 Descriptions of the parameters for Maintenance Association......................................................12-25

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Tables


xv

Table 12-14 Descriptions of the parameters for MEP Point............................................................................12-26Table 12-15 Descriptions of the parameters for E-LAN Service.....................................................................12-26Table 12-16 Descriptions of the parameters for Static MAC Address.............................................................12-28Table 13-1 Planning of the tunnel carrying the PW...........................................................................................13-9Table 13-2 Planning of the E-AGGR service carried by the PW.....................................................................13-10Table 13-3 Planning of the PW........................................................................................................................13-10Table 13-4 Planning of the VLAN forwarding tables of NE1 and NE2..........................................................13-11Table 13-5 Planning of the VLAN forwarding table of NE3...........................................................................13-11Table 13-6 Descriptions of the parameters for VLAN Forwarding Table Item...............................................13-14Table 13-7 Descriptions of the parameters for E-AGGR Service....................................................................13-14Table 14-1 VPI/VCI values of the Node B service..........................................................................................14-12Table 14-2 Planning of the UNIs......................................................................................................................14-12Table 14-3 Planning of the NNIs......................................................................................................................14-13Table 14-4 Planning of the MPLS tunnel.........................................................................................................14-14Table 14-5 Planning of the PW........................................................................................................................14-14Table 14-6 Planning of the ATM service on the OptiX PTN 1900..................................................................14-15Table 14-7 Planning of the ATM service on the OptiX PTN 3900..................................................................14-15Table 14-8 VPI/VCI values of the Node B service..........................................................................................14-24Table 14-9 Planning of the UNIs......................................................................................................................14-24Table 14-10 Planning of the NNIs....................................................................................................................14-25Table 14-11 Planning of the MPLS Tunnel......................................................................................................14-26Table 14-12 Planning of the PW......................................................................................................................14-26Table 14-13 Planning of the ATM service on the OptiX PTN 1900................................................................14-27Table 14-14 Planning of the ATM service on the OptiX PTN 3900................................................................14-27Table 14-15 VPI/VCI values of the Node B service........................................................................................14-35Table 14-16 Planning of the UNIs....................................................................................................................14-35Table 14-17 Planning of the NNIs....................................................................................................................14-36Table 14-18 Planning of the static routing table entries...................................................................................14-36Table 14-19 Planning of the Tunnel.................................................................................................................14-37Table 14-20 Planning of the PW......................................................................................................................14-38Table 14-21 Planning of the ATM service on the OptiX PTN 1900................................................................14-38Table 14-22 Planning of the ATM service on the OptiX PTN 3900................................................................14-39Table C-1 Default threshold for the port WRED policy....................................................................................C-56Table C-2 Port buffer size of each board for the OptiX PTN 3900...................................................................C-56Table C-3 Default threshold for the port WRED policy....................................................................................C-58Table C-4 Port buffer size of each board for the OptiX PTN 3900...................................................................C-58

TablesOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

About This Document

PurposeThis document describes how to configure various services on the equipment. In details, thisdocument describes the basic information and configuration process, and uses configurationexamples to show how to set specific parameters.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX PTN 3900 V100R001

OptiX iManager T2000 V200R007C03

Intended AudienceThe intended audience of this document are:

l Installation and Commissioning Engineer

l Data Configuration Engineer

l System Maintenance Engineer

OrganizationThis document is organized as follows.

Chapter Description

1 Starting the T2000 This chapter describes some basic operations on the T2000.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide About This Document


1

Chapter Description

2 Creating Network This chapter describes how to use the T2000 to create anNE, configure data, add boards, create fibers, create asubnet, configure the clock and configure protection.

3 Configuring the QoS Policy This chapter describes how to configure the QoS policy.

4 Configuring Interfaces This chapter describes how to configure interface attributesof boards. For PTN equipment, attributes for SDHinterfaces, PDH interfaces, Ethernet interfaces and Serialinterfaces can be configured. In addition, Trunk interfacescan be configured.

5 Configuring the ControlPlane

This chapter describes the IGP-ISIS, MPLS-LDP andMPLS-RSVP protocols on the control plane, and describeshow to configure these protocols.

6 Configuring an MPLSTunnel

This chapter describes the MPLS, MPLS tunnel andapplication scenarios for the MPLS tunnel. In addition, thischapter describes how to use the T2000 to create an MPLStunnel, an MPLS tunnel protection group and MPLS OAM.

7 Configuring an IP Tunnel This chapter describes the basic information on the IPtunnel, and how to use the T2000 to create an IP tunnel.

8 Configuring a GRE Tunnel This chapter describes the basic information on the GREtunnel, and how to use the T2000 to create a GRE tunnel.

9 Configuring a CES Service This chapter describes the basic information on the CESservice, and uses an example to show how to configure aCES service.

10 Configuring an ATMService

This chapter describes the basic information on the ATMservice, and uses an example to show how to configure anATM service.

11 Configuring an E-LineService

This chapter describes the basic information on the E-Lineservice, and uses an example to show how to configure anE-Line service.

12 Configuring an E-LANService

This chapter describes the basic information on the E-LANservice, and uses an example to show how to configure anE-LAN service.

13 Configuring an E-AGGRService

This chapter describes the basic information on the E-AGGR service, and uses an example to show how toconfigure an E-AGGR service.

14 Configuring Services forthe Offload Solution

This chapter describes the basic information on the Offload,and uses some examples to show how to configure theOffload.

15 Configuring the ExternalEnvironment MonitoringInterfaces

This chapter describes the basic information on the externalenvironment monitoring interfaces, and how to configurethe external environment monitoring.

About This DocumentOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

Chapter Description

16 Backing up theConfiguration Data

This chapter describes the operations to back up and restorethe NE configuration data.

A Glossary This appendix lists the terms used in this document.

B Acronyms andAbbreviations

This appendix lists the acronyms and abbreviations used inthis document.

C Parameter Reference This appendix lists some parameters in this document.

Conventions

Symbol ConventionsThe following symbols may be found in this document. They are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk which, if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which,if not avoided, could result in minor or moderate injury.

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

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

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

General ConventionsConvention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. Forexample, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.



3

GUI ConventionsConvention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles are inboldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. Forexample, choose File > Create > Folder.

Keyboard OperationFormat Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means thethree keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keysshould be pressed in turn.

Mouse OperationAction Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly withoutmoving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certainposition.

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 06 (2009-06-01) Based on Product Version V100R001The updated contents are as follows.l As the NMS interfaces about per-trail creation of CES services and ATM services are

changed, the related description is modified.l Chapter 6 Configuring an MPLS Tunnel: The configuration process is added.

l Chapter 9 Configuring a CES Service: The configuration process and the configurationexamples of the CES services are optimized.

About This DocumentOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

l Chapter 11 Configuring an E-Line Service: The configuration process and the configurationexamples of the E-Line services are optimized.

Updates in Issue 05 (2009-03-16) Based on Product Version V100R001The updated contents are as follows.l Chapter 6 Configuring an MPLS Tunnel: Information about the rerouting mode is modified.

Updates in Issue 04 (2009-02-20) Based on Product Version V100R001The updated contents are as follows.l Chapter 2 Creating Network: The setting of the frequency source selection mode and setting

of the PTP clock are added.l Chapter 10 Configuring an ATM Service: The configuration process and the configuration

examples of the ATM services are optimized.

Updates in Issue 03 (2008-10-20) Based on Product Version V100R001The updated contents are as follows.l Chapter 2 Creating Network: The configuration of a TPS protection group of sub-boards

is added.l Chapter 12 Configuring an E-LAN Service: Information about how to manage the blacklist

and how to set the broadcast storm suppression is added.

Updates in Issue 02 (2008-08-20) Based on Product Version V100R001The updated contents are as follows.l Chapter 9 Configuring a CES Service: The example of configuring the CES service is

optimized.l Chapter 14 Configuring Services for the Offload Solution: The configuration flow diagram

is optimized.

Updates in Issue 01 (2008-05-10) Based on Product Version V100R001This document of the V100R001 version is the first release.



5

1 Starting the T2000

About This Chapter

The following pages introduces some preparation operations that will ensure a smooth, trouble-free launch of the T2000.

1.1 Starting or Shutting Down the T2000The T2000 uses the standard client/server architecture and multiple-user mode. So, you arerecommended to start or shut down the T2000 by strictly observing the following procedure, inorder not to affect other users that are operating the T2000.

1.2 Entering the T2000 Common ViewsThe T2000 common views are the key interfaces to manage various network objects, forexample, Main Topology and NE Explorer. You can use these views to manage the topology,equipment.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 1 Starting the T2000


1-1

1.1 Starting or Shutting Down the T2000The T2000 uses the standard client/server architecture and multiple-user mode. So, you arerecommended to start or shut down the T2000 by strictly observing the following procedure, inorder not to affect other users that are operating the T2000.

Contextl You are recommended to start the computer and the T2000 application in the following

sequence: Start the computer, start the T2000 server, and then start the T2000 client.l You are recommended to shut down the T2000 application and the computer in the

following sequence: Exit the T2000 client, stop the T2000 server, and then shut down thecomputer.

1.1.1 Starting the ComputerTo avoid computer damage or data loss, strictly follow the procedure provided, to start thecomputer. The startup procedures of the workstation are different from those of a normal PC.Follow the correct procedure to perform the operations as required.

1.1.2 Starting the T2000 ServerAfter starting the computer, you need to start the T2000 server. Then you can log in to theT2000 to manage the network.

1.1.3 Viewing the T2000 Process StatusWhen you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use theSystem Monitor to view the T2000 process status to decide whether the server is faulty.

1.1.4 Logging In to the T2000 ClientYou can manage the network in the graphic user interface (GUI) only after logging in to theT2000 client.

1.1.5 Exiting a T2000 ClientBefore restarting the T2000 client or shutting down the T2000 server, you must exit theT2000 client.

1.1.6 Shutting Down the T2000 ServerWhen the T2000 server is managing the system normally, do not perform this operation. Inspecial circumstances, for example, when modifying the system time of the computer where theT2000 resides, or when upgrading the version, you can use the System Monitor Client to shutdown the T2000 server.

1.1.7 Shutting Down the ComputerNormally, do not shut down the computer. In special situations, for example, when the computerbecomes faulty, shut down the computer in the correct sequence. The shutdown procedures ofthe workstation are different from those of a normal PC. Follow the correct procedure to performthe operations as required.

1.1.1 Starting the ComputerTo avoid computer damage or data loss, strictly follow the procedure provided, to start thecomputer. The startup procedures of the workstation are different from those of a normal PC.Follow the correct procedure to perform the operations as required.

1 Starting the T2000OptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

Prerequisitel The T2000 must be installed correctly.

l The power cable of the workstation or the computer, the power cable of the monitor, dataline and Ethernet line must be connected correctly.

l If there is printer, modem or other peripherals, their power line and data line must beconnected correctly.

Background Information

The T2000 can run in the UNIX or Windows operating system. The functions are the same ineach operating system. To learn about the recommended hardware configuration, refer to theOptiX iManager T2000 Product Description.

Procedurel On UNIX

1. Power on the printer, modem and other peripherals.2. Power on the workstation and the Solaris is automatically started. The Prompt dialog

box is displayed.3. Enter the Username and the Password in the Login dialog box. For example, User:

t2000 (by default); Password: t2000 (by default).4. Click OK to open the Common Desktop Environment (CDE) window.

l On Windows1. Power on the printer, modem and other peripherals.2. Power on the computer and the Windows is automatically started. The Login dialog

box is displayed.3. Enter the Username and the Password in the Login dialog box. For example, User:

t2000 (by default); Password: t2000 (by default).4. Click OK to open the Windows user interface.

----End

1.1.2 Starting the T2000 ServerAfter starting the computer, you need to start the T2000 server. Then you can log in to theT2000 to manage the network.

Prerequisitel The computer where the T2000 is installed must be started correctly.

l The operating system of the T2000 server must be running correctly.

l The T2000 license must be in the server directory.

l The SQL Server must be started and work normally.

Procedure

Step 1 Double-click the T2000Server icon on the desktop of the T2000 server.



1-3

Step 2 In the Login dialog box, enter User Name, Password and Server. For example, User Name:admin, Password: T2000 (T2000 is the default password of the admin user.) and Server:Local.

NOTE

Periodically change the password and memorize it.

Step 3 Click Login. Wait until the database process, T2000 core process, and the processes that areoptional according to the actual situation are in the Running state. Now the T2000 server isstarted successfully.

NOTE

If the System Monitor application is started, you can restart the T2000 server on the System Monitor.Perform the following step:

Choose System > Start Server on the Main Menu of the System Monitor. Wait until the database process,T2000 core process, and the processes that are optional according to the actual situation are in theRunning state, the T2000 server is started properly.

----End

1.1.3 Viewing the T2000 Process StatusWhen you fail to log in to the T2000 client or abnormally exit the T2000 client, you can use theSystem Monitor to view the T2000 process status to decide whether the server is faulty.

Background InformationTo view the status of the T2000 processes by UNIX command line, run the following command:# /T2000/server/bin/showt2000serverIf each process entered has a corresponding process ID and the specific ID does not change, theT2000 processes are normal.

Procedure

Step 1 Start and log in to the System Monitor.

Step 2 In the user interface of the System Monitor, click the Process tab, and view whether the statusof each process is Running.l If the process status is Stopped, right-click on the process, and choose Start Process from

the shortcut menu. In this manner, the process is in the Running state.l If the manual startup fails, it indicates that the process is abnormal.

l To save resources, you can close unwanted processes. Set the startup mode of the desiredprocess to Manual, and then select Stop Process.

----End

1.1.4 Logging In to the T2000 ClientYou can manage the network in the graphic user interface (GUI) only after logging in to theT2000 client.

PrerequisiteThe T2000 server must be started correctly.


Configuration Guide


Issue 06 (2009-06-01)

Procedure

Step 1 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.

Step 2 Enter the User Name, Password of the T2000 client in the Login dialog box. For example,User Name: admin; Password: T2000.

NOTE

l By default, the initial user name is admin, and the password is T2000. To protect the T2000 fromunauthorized logins, you need to immediately change this password.

l The administrator needs to create new T2000 users and assign them to certain authority groups.

Step 3 Optional: Set the server parameters.

1. Click to display the Setting dialog box.2. Click New to display another Setting dialog box.3. In the Setting dialog box, specify the IP Address, Mode and Server Name.

NOTE

l The IP address is the IP address used by the T2000 server.

l The Mode has two options including Common and Security (SSL). When you choose theSecurity (SSL) mode, the communication between the client and the server is encrypted.

l The communication mode of the client must be consistent with that of the server. Otherwise, theclient cannot log in to the server. To view the communication mode of the server, chooseSystem > Communication Security Setting on the Main Menu of the System Monitor client.

l You need not enter the Port number. After the Mode is specified, the system selects a Portnumber automatically.

4. Click OK to complete adding a server.5. Click OK to complete the server settings.

Step 4 Select a server and click Login to access the T2000.

----End

1.1.5 Exiting a T2000 ClientBefore restarting the T2000 client or shutting down the T2000 server, you must exit theT2000 client.

PrerequisiteThe T2000 client must be started normally.

Procedure

Step 1 Choose File > Exit from the Main Menu.

Step 2 Click OK in the confirmation dialog box.

NOTE

If the layout of the view is changed and not saved, the Confirm dialog box appears asking you whether tosave the changes. After you confirm the dialog box, automatically exit the client.

----End



1-5

1.1.6 Shutting Down the T2000 ServerWhen the T2000 server is managing the system normally, do not perform this operation. Inspecial circumstances, for example, when modifying the system time of the computer where theT2000 resides, or when upgrading the version, you can use the System Monitor Client to shutdown the T2000 server.

PrerequisiteAll the T2000 clients connected to the T2000 server must be shut down.

Background InformationWhen performing the operations related to the database (such as initializing the T2000database, restoring T2000 databases and restoring T2000 MO data) or the operations related tothe T2000 (such as the upgrade, installing patches and re-installing the T2000), you need to shutdown the T2000 server first. You are recommended to shut down the T2000 server in the wayof "shut down the T2000 server and the System Monitor".

Procedurel Shut down the T2000 server only.

NOTE

In this case, the MDP process is not shut down and the database cannot be initialized.

1. In the System Monitor, choose System > Stop All NMS Service from the Main Menu.

2. Click OK in the confirmation dialog box. When all the processes are in theStopped status, the T2000 server is stopped normally.

l Shut down the T2000 server and the System Monitor.

NOTE

After all the T2000 processes are finished, you can initialize the database.

– On Windows, enter net stop imapservice under the prompt in the DOS window andpress Enter.

TIP

On Windows, click Start and then click Run. In the Run window, enter cmd and click OK. TheDOS window is displayed.

----End

1.1.7 Shutting Down the ComputerNormally, do not shut down the computer. In special situations, for example, when the computerbecomes faulty, shut down the computer in the correct sequence. The shutdown procedures ofthe workstation are different from those of a normal PC. Follow the correct procedure to performthe operations as required.

PrerequisiteThe T2000 server and client applications must be stopped.


Configuration Guide


Issue 06 (2009-06-01)

Precaution

CAUTIONTo avoid equipment damages or data loss, perform the following step one by one to shut downthe workstation.

Procedurel On UNIX platform

1. Enter the following commands in the terminal window, the UNIX workstation shutsdown automatically:% su rootPassword: rootkit# sync;sync;sync;sync;sync# shutdown -y -g0 -i5

NOTE

l rootkit is the default password of super user root. If the password is changed, enter thenew password.

l To restart the Sun workstation, the last command is # shutdown -y -g0 -i6.

2. Turn off the monitor and the peripheral equipment.l On Windows platform

1. Choose Start > Shut down from the Windows desktop.2. Choose Shut down and click OK in the dialog box. The computer shuts down

automatically.3. Turn off the monitor and the peripheral equipment.

----End

1.2 Entering the T2000 Common ViewsThe T2000 common views are the key interfaces to manage various network objects, forexample, Main Topology and NE Explorer. You can use these views to manage the topology,equipment.

1.2.1 Opening the Main TopologyAfter opening the Main Topology, you can manage the network topology, for example, creatinga topology object, creating a subnet, and locking the position of an NE icon in the topology.

1.2.2 Opening the NE ExplorerThe NE Explorer is the key interface for the T2000 to configure a single station. After openingthe NE Explorer, you can configure, manage and maintain each NE, board or port in a hierachicalmanner.

1.2.1 Opening the Main TopologyAfter opening the Main Topology, you can manage the network topology, for example, creatinga topology object, creating a subnet, and locking the position of an NE icon in the topology.



1-7

PrerequisiteYou must be a Network Management (NM) user with "NE and network monitor" authority orhigher.

Procedurel To open the Main Topology, log in to the T2000 client.l Choose Window > Main Topology from the Main Menu.

----End

1.2.2 Opening the NE ExplorerThe NE Explorer is the key interface for the T2000 to configure a single station. After openingthe NE Explorer, you can configure, manage and maintain each NE, board or port in a hierachicalmanner.

PrerequisiteYou must be an NM user with "NE and network monitor" authority or higher.

Background InformationYou can open a maximum of five NE Explorer windows at the same time.

ProcedureRight-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.

----End


Configuration Guide


Issue 06 (2009-06-01)

2 Creating Network

About This Chapter

NEs and fibers or cables can be managed on the T2000 only after their topologies are created.

2.1 Creating NEsEach equipment is represented as an NE on the T2000. Before the T2000 manages the actualequipment, you need to create the corresponding NEs on the T2000. There are two methods ofcreating NEs: creating a single NE and creating NEs in batches. When you need to create a largenumber of NEs, for example, during deployment, it is recommended that you create NEs inbatches. When you need to create only a few NEs, it is recommended that you create the NEsone by one.

2.2 Creating an NE UserThe default NE user is a system-level user. To ensure the data security of the NE, allocatedifferent authorities for different NE users according to their working content. This sectiondescribes how to create an NE user on the T2000 and how to allocate the authority. In this way,you can control the access and configuration of the NE operators.

2.3 Switching a Logged-In NM UserDifferent NM users have different authorities. You can log in as another user to performoperations of different levels.

2.4 Configuring NE DataThough an NE is successfully created, it is not configured. You need to configure the NE firstso that the T2000 can manage and operate the NE. There are two ways of configuring the NEdata: copy NE data and upload.

2.5 Adding BoardsWhen configuring the NE dataAfter the NE data is configured, if physical boards are added, youneed to add boards on the NE Panel. You can either add the physical boards that actually operateon the NE or add the logical boards that do not exist on the actual equipment.

2.6 Adding Sub-BoardsThe equipment can realize different functions after you add different sub-boards to a processingboard.

2.7 Configuring the Equipment-Level ProtectionThe equipment-level protection includes the subcard TPS protection and board 1+1 protection.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 2 Creating Network


2-1

2.8 Creating Fibers for PTN Equipment ManuallyNEs communicate with each other through fibers. After creating boards for each NE, you needto create fibers for further configuration of services. In this situation, you can manually createfibers one by one.

2.9 Creating a Topology SubnetThe subnet created here is based on a topological concept to facilitate management. In the caseof topology objects in the same network area or with similar attributes, you can allocate themin one topology subnet.

2.10 Configuring Inband DCNThe inband DCN refers to a DCN solution in which the service channels provided by the managedequipment are used to complete the network equipment management. When inband DCN isapplied, the T2000 information is transported through service channels of the equipment. Whenthe inband DCN is used for networking, no exclusive DCN channels are required. Hence, muchnetwork construction cost is saved.

2.11 Configuring ClocksThe stable clock is the basis to normal functioning of an NE. You must configure clocks for allNEs prior to configuring services. In addition, you need to configure clock protection forcomplex networks.

2.12 Configuring Linear MSPIn a chain network, you can configure a linear multiplex section protection (MSP) to protectservices in the link.

2.13 Parameter DescriptionThis section describes the parameters related to the network configuration.

2 Creating NetworkOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

2.1 Creating NEsEach equipment is represented as an NE on the T2000. Before the T2000 manages the actualequipment, you need to create the corresponding NEs on the T2000. There are two methods ofcreating NEs: creating a single NE and creating NEs in batches. When you need to create a largenumber of NEs, for example, during deployment, it is recommended that you create NEs inbatches. When you need to create only a few NEs, it is recommended that you create the NEsone by one.

2.1.1 Creating NEs in BatchesWhen the T2000 communicates properly with a GNE, you can search for all NEs thatcommunicate with the GNE by using the IP address of the GNE or the network segment to whichthe IP address is associated, or by using the NSAP address of the NE. Then, you can create NEsin batches. This method is quicker and more accurate than manual creation.

2.1.2 Creating a Single NEThe T2000 can manage an NE after the NE is created. Although creating a single NE is not asfast and accurate as creating NEs in batches, you can perform this operation regardless of whetherthe data is configured on the NE or not.

2.1.1 Creating NEs in BatchesWhen the T2000 communicates properly with a GNE, you can search for all NEs thatcommunicate with the GNE by using the IP address of the GNE or the network segment to whichthe IP address is associated, or by using the NSAP address of the NE. Then, you can create NEsin batches. This method is quicker and more accurate than manual creation.

PrerequisiteYou must be an NM user with "NE administrator" authority or higher.

The T2000 must communicate properly with the GNE.

The NE Explorer instance of the NEs must be created.

Procedure

Step 1 Choose File > Search for NE from the Main Menu. The Search for NE window is displayed.

Step 2 Click Add and the Input Search Domain dialog box is displayed.

Step 3 Set Address type to IP Address Range of GNE, IP Address of GNE, or NSAP Address, andenter Search Address, User Name, and Password. Then, click OK.



2-3

NOTEYou can repeat Steps 2 through 3 to add more search domains. You can delete the system default searchdomain.

l If you use IP address to search for NEs:

l Usually, the broadcast function is disabled on the routers on a network, to avoid network broadcaststorm. Therefore, by using the IP Address Range of GNE method, only the NEs in the samenetwork segment can be searched out.

l To search the network segments across routers, the IP Address of GNE method is recommended.Through a gateway NE, you can search out the NEs in the network segment of the gateway NE.

Step 4 Click Start. The Search for NE dialog box is displayed.

Step 5 In the Search for NE dialog box, you can perform the following operations:l Select Search for NE and click OK to search for all NEs in the selected domain.l Select Create device after search, and enter NE user and Password. Then, click OK.

NOTE

l The default NE user is root.

l The default password is password.

l Select Upload after create and click OK, so that the NE data can be uploaded to theT2000 after the NE is created.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

If you select all options in the Search for NE dialog box, you can search for NEs, create the NEs, andupload the NE data at one time.

Step 6 Optional: If you select Search for NE only, you can select the NEs, which are not yet created,in the Result list after the search for NEs is complete. Click Create and then the Create dialogbox is displayed. Enter User Name and Password in the Create dialog box, and then clickOK.

----End

Postrequisite

After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:

l The password for the NE user is incorrect. Enter the correct password for the NE user.

l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

2.1.2 Creating a Single NEThe T2000 can manage an NE after the NE is created. Although creating a single NE is not asfast and accurate as creating NEs in batches, you can perform this operation regardless of whetherthe data is configured on the NE or not.

Prerequisitel You must be an NM user with "NM operator" authority or higher.

l The license must be installed and the license must support creating the NE of the type.

l The NE Explorer instance of the NEs must be created.

Context

First create a GNE, and then create a non-gateway NE.

If the NE is not created properly or the communication between the NE and the T2000 isabnormal, the NE is displayed in gray color.

Procedure

Step 1 Right-click in the blank space of the Main Topology and choose New > Device from the shortcutmenu. The Add Object dialog box is displayed.

Step 2 Select the NE type from the Object Type tree.

Step 3 Complete the following information: ID, Extended ID, Name and Remarks.

Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.

Step 5 Choose Gateway Type, Protocol and set the IP address.

1. Select Gateway from the Gateway Type drop-down list.

2. Select the Protocol type.



2-5

If the T2000communicates withNEs through

Do...

IP protocol Select IP from the Protocol drop-down list. Enter the IPAddress and use the default value for the Port number ofthe GNE.

NOTE

The domain address that contains a maximum of 13 bytes is entered by the user. NSEL is the portnumber of the network-level protocol, with a fixed value of 1d (one byte).

Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NEis associated to from the Affiliated Gateway drop-down list.

Step 7 Enter the NE User and Password.

NOTEThe default NE user is root, and the default password is password.

Step 8 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in theposition where you clicked.

----End

ResultAfter an NE is successfully created, the system automatically saves the information, such as theIP address, subnet mask, and NE ID to the T2000 database.

Postrequisite

After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:

l The communication between the T2000 and the NE is abnormal. Check the settings ofcommunication parameters, such as the IP address of the NE and NE ID.

l The password for the NE user is incorrect. Enter the correct password for the NE user.

l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

2.2 Creating an NE UserThe default NE user is a system-level user. To ensure the data security of the NE, allocatedifferent authorities for different NE users according to their working content. This sectiondescribes how to create an NE user on the T2000 and how to allocate the authority. In this way,you can control the access and configuration of the NE operators.

Prerequisitel You must be an NM user with "NE and network administrator" authority or higher.

l The NE must be successfully created.


Configuration Guide


Issue 06 (2009-06-01)

Background Information

The default NE user has the system level authority. To guarantee NE data security, it isrecommended that you assign NE users with different authorities as required.

Procedure

Step 1 Choose System > NE Security Management > NE User Management from the Main Menu.

Step 2 In the Object Tree, select an NE and click .

Step 3 Click Add and the Add NE User dialog box is displayed.

NOTE

For details on the parameters for NE User attributes, seeTable 2-2.

Step 4 Enter the NE user name in the NE User field.

Step 5 Select the User Level as needed.

Step 6 In the NE User Flag field, select a user type according to the type of the terminal through whichthe user logs in to the NE.

Step 7 Enter the password in the New Password field and enter it again in the Confirm Passwordfield.

Step 8 In the NE Name field, select the NEs that this NE user is allowed to manage.



2-7

Step 9 Click OK.

----End

2.3 Switching a Logged-In NM UserDifferent NM users have different authorities. You can log in as another user to performoperations of different levels.

PrerequisiteYou have already logged in to the T2000.

Procedure

Step 1 Choose File > Logout from the Main Menu. The Confirm dialog box is displayed. Click OK.

Step 2 The Save coordinates dialog box is displayed. Click OK.

NOTEThis step is to executed when the view deploy is changed.

Step 3 Enter the user name and password in the Login dialog box.

Step 4 Click Login.

----End

2.4 Configuring NE DataThough an NE is successfully created, it is not configured. You need to configure the NE firstso that the T2000 can manage and operate the NE. There are two ways of configuring the NEdata: copy NE data and upload.

Prerequisitel You must be an NM user with "NE and network operator" authority or higher.


Configuration Guide


Issue 06 (2009-06-01)

l The NE must be created successfully.

Context

In the case of NE data copy, copy the configured NE data to the unconfigured NE so that theNE enters the configuration status. Then, you can manage the configuration of the NE by usingthe T2000. In the case of data upload, upload the user-side NE data to the T2000 so that you canmanage the configuration of the NE by using the T2000.

Procedurel To copy the NE data, do as follows:

NOTEThe NE type, NE software version and hardware configuration of the source NE must be consistentwith those of the copied NE.

1. Double-click the unconfigured NE on the Main Topology.The NE Configuration Wizard dialog box is displayed.

2. Choose Copy NE Data and click Next.The NE Replication dialog box is displayed.

3. Select the NE in the drop-down list and click Start.The Confirm dialog box is displayed indicating that the copy operation copies all thedata of the source NE.

4. Click OK.The Confirm dialog box is displayed indicating that the copy operation results in theloss of the original data of the NE to which the data is copied.

5. Click OK to start the copy.Wait for a few seconds. The Operation Result dialog box is displayed.

6. Click Close.

l Upload:

1. Double-click the unconfigured NE on the Main Topology.The NE Configuration Wizard dialog box is displayed.

2. Choose Upload and click Next.The Confirm dialog box is displayed indicating that the upload may take a long time.

3. Click OK to start the upload.Wait for a few seconds. The Operation Result dialog box is displayed.

4. Click Close.

----End

2.5 Adding BoardsWhen configuring the NE dataAfter the NE data is configured, if physical boards are added, youneed to add boards on the NE Panel. You can either add the physical boards that actually operateon the NE or add the logical boards that do not exist on the actual equipment.



2-9

Prerequisitel You must be an NM user with "NE operator" authority or higher.

l The NE must be created.

l There must be idle slot on the NE Panel.

ContextThe physical boards are the actual boards inserted in the subrack. A logical board refers to aboard that is created on the T2000. After a logical board is created, you can configure the relevantservices. If the corresponding physical board is online, the configured services can be available.

NOTE

The NE panel is able to indicate the mapping relation between slots that house processing boards andinterface boards. When you click a processing board that is paired with an interface board in the NE panel,the ID of the slot that houses the mapping interface board is displayed in orange.

Procedure

Step 1 Open the NE Panel.

For the PTN equipment, double-click the icon of the NE.

Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list.

----End

2.6 Adding Sub-BoardsThe equipment can realize different functions after you add different sub-boards to a processingboard.

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.

l Applies to only MP1 board.

ContextHot swappable service sub-board interfaces are provided on the MP1 board. When differentservice sub-boards are inserted, the TDM E1, IMA E1, ML-PPP E1, ATM STM-N andchannelized STM-N signals can be assessed and processed.

Procedure

Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface.

Step 2 Select the desired processing board, right-click in the blank area that displays sub-boards, andselect the desired sub-board.


Configuration Guide


Issue 06 (2009-06-01)

----End

2.7 Configuring the Equipment-Level ProtectionThe equipment-level protection includes the subcard TPS protection and board 1+1 protection.

2.7.1 Creating a TPS Protection Group of Sub-BoardsThe working board and protection board form a TPS protection group. If the working boardbecomes faulty after the creation of a TPS protection group is completed, the service isautomatically switched to the protection board.

2.7.2 Querying the Board 1+1 Protection GroupYou can create 1+1 protection for the SCC and cross-connect boards. When the working boardfails, the services are automatically switched to the protection board.

2.7.1 Creating a TPS Protection Group of Sub-BoardsThe working board and protection board form a TPS protection group. If the working boardbecomes faulty after the creation of a TPS protection group is completed, the service isautomatically switched to the protection board.


l Creation of the working and protection service sub-boards must be completed.

ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the

Function Tree.

Step 2 Click Create and the Create TPS Protection Group dialog box is displayed.

Step 3 Select the protection board and the working board, and set priorities in the working board list.For details on the parameters for TPS protection group of sub-boards, seeParameter Descriptionof "TPS Protection" in the Feature Description.

Step 4 Set the wait-to-restore (WTR) time.

Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close.

----End



2-11

2.7.2 Querying the Board 1+1 Protection GroupYou can create 1+1 protection for the SCC and cross-connect boards. When the working boardfails, the services are automatically switched to the protection board.

PrerequisiteYou must be an NM user with "NE monitor" authority or higher.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection fromthe Function Tree.

Step 2 Click Query to query the current primary and secondary status from the NE.

----End

2.8 Creating Fibers for PTN Equipment ManuallyNEs communicate with each other through fibers. After creating boards for each NE, you needto create fibers for further configuration of services. In this situation, you can manually createfibers one by one.

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.

l The boards to be connected with fibers or cables must be created.

Procedure

Step 1 Right-click in the Main Topology and choose New > Link. The Add Object dialog box isdisplayed.

Step 2 Choose Link > Fiber/Cable from the left pane.

Step 3 Click the button in Source NE. Select the source board and port in the Select the source endof the link dialog box.

Step 4 Click OK and the cursor changes to a + sign.

Step 5 Click the sink NE of the fiber or cable on the Main Topology.

Step 6 Click the button in Sink NE. Select the sink board and port in the Select the sink end of thelink dialog box.

TIPWhen selecting a wrong source or sink NE, right-click and click OK in the Object Selection dialog boxto exit.

Step 7 Click OK. Enter the information of the fiber or cable in the Create Fiber/Cable dialog box.


Configuration Guide


Issue 06 (2009-06-01)

Step 8 Click OK. The created fiber or cable appears between the source and sink NEs on the MainTopology.

Step 9 Select the fiber you create, right-click and choose Detect Link from the shortcut menu.The Operation Result dialog box is displayed indicating the fiber connection information.

----End

2.9 Creating a Topology SubnetThe subnet created here is based on a topological concept to facilitate management. In the caseof topology objects in the same network area or with similar attributes, you can allocate themin one topology subnet.

PrerequisiteYou must be an NM user with "NM operator" authority or higher.

Background InformationA topology subnet is created only to simplify the user interface and has no impact on the NEs.

Procedure

Step 1 Right-click in the blank space of the Main Topology and choose New > Subnet from the shortcutmenu.

Step 2 Click the Properties tab in the Add Object dialog box. Enter the attributes of the subnet.

Step 3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane.Click .



2-13

NOTE

In the case of a similar dialog box for selecting objects,

l indicates that to select the objects to be selected on the left to the selected objects on the right.

l indicates that to select all the objects to be selected on the left to the selected objects on the right.

Step 4 Click OK. Click in the blank space of the Main Topology, the icon appears in the positionwhere you clicked.

----End

2.10 Configuring Inband DCNThe inband DCN refers to a DCN solution in which the service channels provided by the managedequipment are used to complete the network equipment management. When inband DCN isapplied, the T2000 information is transported through service channels of the equipment. Whenthe inband DCN is used for networking, no exclusive DCN channels are required. Hence, muchnetwork construction cost is saved.

ContextThe PTN equipment can distinguish service channels and network management channelsaccording to the MPLS labels or VLAN IDs. When the channels are distinguished by the VLANIDs, see Operation Tasks of Configuring an Inband DCN to configure inband DCN in FeatureDescription.


Configuration Guide


Issue 06 (2009-06-01)

2.11 Configuring ClocksThe stable clock is the basis to normal functioning of an NE. You must configure clocks for allNEs prior to configuring services. In addition, you need to configure clock protection forcomplex networks.

2.11.1 Setting the Frequency Selection ModeThe OptiX PTN equipment supports two synchronization modes, that is, physicalsynchronization mode and PTP synchronization mode. The frequency source selection mode isused to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,you should set the frequency source selection mode to the PTP synchronization mode.

2.11.2 Setting the PTP ClockIEEE 1588 V2 is a standard for a precision clock synchronization protocol for networkedmeasurement and control systems. Each slave clock exchanges synchronization packets withthe master clock and thus maintains network-wide time/clock synchronization.

2.11.3 Configuring the NE Clock SourceBefore configuring services, you must configure the NE clock source and specify the prioritylevel to ensure that correct clock trace relations are created for all the NEs in the network.

2.11.4 Configuring the Clock Source ProtectionIn a complicated clock network, you need to configure the clock protection for all NEs. Afteryou set the clock source and specify the clock priority level for the NEs, you can enable thestandard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clocksource. This is how the clocks are protected.

2.11.5 Configuring Switching Conditions for Clock SourcesIf the traceable clock source of an NE is line clock, you can customize switching conditions forthe clock source, so that the NE switches to other clocks when the clock source fails. In thismanner, services are less affected.

2.11.6 Configuring the Clock Source ReversionWhen there are multiple clock sources for an NE, set the clock sources to automatic reversionmode, so that the deteriorated clock source automatically becomes the traceable timing referenceafter it recovers.

2.11.7 Configuring the Phase-Locked Source for External Clock OutputWhen a clock signal passes through 14 or more NEs, frequency offset and drift may occur. Asa result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signaldegrade, you need to set a 2M phase-locked source to optimize the clock signal.

2.11.8 Setting the Clock Source QualityIn a complex clock network, there may be some unknown clock sources. You can uniformlydefine these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.The NE obtains their quality information automatically for clock sources that are allocated toan NE. You should define the quality level of clock sources only during test and maintenance.

2.11.9 Configuring the SSM OutputIf the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messagesautomatically. You can prevent clock sources from sending SSM messages to other clocksubnets. This helps you to ensure that the equipment of different clock subnets do not affect eachother at the edge of clock networks.

2.11.10 Switching a Clock Source



2-15

When the traceable clock source in a network deteriorates, NEs may not be able to execute aswitch on the clock source. You need to manually switch the clock source to prevent clockdeterioration from affecting the normal running of NEs.

2.11.1 Setting the Frequency Selection ModeThe OptiX PTN equipment supports two synchronization modes, that is, physicalsynchronization mode and PTP synchronization mode. The frequency source selection mode isused to set the clock synchronization mode of the NE. Before configuring the IEEE 1588 clock,you should set the frequency source selection mode to the PTP synchronization mode.

PrerequisiteYou must be an NM user with "NE operator" authority or higher.

ProcedureStep 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the

Function Tree.

Step 2 In Frequency Selection Mode, you can select one of the clock synchronization mode.

CAUTIONl When the external time interface is set to the external time input interface, the NE can run

in only the physical synchronization mode. That is, the frequency selection mode of theequipment that accesses the external clock must be set to the physical synchronization mode.

l When the NE is running in the PTP synchronization mode, the external interface cannot beset to the external time input interface.

Step 3 Click Apply.

----End

2.11.2 Setting the PTP ClockIEEE 1588 V2 is a standard for a precision clock synchronization protocol for networkedmeasurement and control systems. Each slave clock exchanges synchronization packets withthe master clock and thus maintains network-wide time/clock synchronization.

ContextFor details of configuring the PTP clock , refer to PTP Clock in the Feature Description.

2.11.3 Configuring the NE Clock SourceBefore configuring services, you must configure the NE clock source and specify the prioritylevel to ensure that correct clock trace relations are created for all the NEs in the network.



Configuration Guide


Issue 06 (2009-06-01)

Context

To implement clock protection, you must configure at least two traceable clock sources for theequipment. Usually, the tributary clock is not used as the clock source for the equipment.

After you set the clock sources for all the NEs, query the networkwide clock trace statusagain. For details, see Viewing the Clock Trace Search.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > ClockSource Priority from the Function Tree.

Step 2 Click Query to query the existing clock source.

Step 3 Click Create. In the Add Clock Source dialog box, select a new clock source and click OK.

Step 4 Optional: If an external clock source is selected, select External Clock Source Mode accordingto the type of external clock signals. For 2 Mbit/s clocks, specify the Synchronous StatusByte to deliver SSM message.

Step 5 Select a clock source, and click or to adjust its priority level. The clock sources are arranged inthe descending order. The clock source on top is the preferred one for the NE.

NOTE

Internal clock sources have the lowest priority because of their low precision.

Step 6 Click Apply. In the Operation Result dialog box, click Close.

NOTE

If the clock trace relation changes because of the clock source change, the Prompt dialog box is displayed,asking you whether to refresh the clock trace relation. Usually you can click OK. If you select DisablePrompting Next Time, the Prompt dialog box is not displayed even when the clock trace relation changes.

----End

2.11.4 Configuring the Clock Source ProtectionIn a complicated clock network, you need to configure the clock protection for all NEs. Afteryou set the clock source and specify the clock priority level for the NEs, you can enable thestandard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clocksource. This is how the clocks are protected.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > ClockSubnet Configuration from the Function Tree.

Step 2 Click the Clock Subnet tab. Click Query to query the existing parameter settings.



2-17

Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.NOTE

The same SSM protection protocol must be used within the same clock protection subnet.

Step 4 Set the subnet number of the clock subnet to which the NE is associated.

NOTE

Allocate the same subnet number to NEs tracing the same clock source.

Step 5 Optional: If the extended SSM protocol starts, set the clock ID of the clock source.


Step 7 Optional: If the clock ID is specified for the line clock of an NE, click the Clock ID Status tab,and set the Enabled Status to Enabled. Click Apply. In the Operation Result dialog box, clickClose.

----End

2.11.5 Configuring Switching Conditions for Clock SourcesIf the traceable clock source of an NE is line clock, you can customize switching conditions forthe clock source, so that the NE switches to other clocks when the clock source fails. In thismanner, services are less affected.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock SourceSwitching from the Function Tree. Click the Clock Source Switching Condition tab.

Step 2 Click Query to query the existing parameter settings.

Step 3 Double-click the parameter column and set the alarms and performance events that are to beused as the clock source switching conditions to Yes.


----End


Configuration Guide


Issue 06 (2009-06-01)

2.11.6 Configuring the Clock Source ReversionWhen there are multiple clock sources for an NE, set the clock sources to automatic reversionmode, so that the deteriorated clock source automatically becomes the traceable timing referenceafter it recovers.


ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock

Source Switching from the Function Tree. Click the Clock Source Reversion Parameter tab.

Step 2 Double-click and set the reversion mode and the WTR time.

NOTE

Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.


----End

2.11.7 Configuring the Phase-Locked Source for External ClockOutput

When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. Asa result, the clock signal transmitted to the downstream NE is degraded. To avoid clock signaldegrade, you need to set a 2M phase-locked source to optimize the clock signal.


ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Phase-

Locked Source Output by External Clock from the Function Tree.


Step 3 Set the external clock attributes of the 2M phase-locked source. Set the parameters manuallysuch as External Clock Output Mode, External Clock Output Timeslot and so on.

Step 4 Click Apply.

----End

ExampleAs shown in Figure 2-1, n NEs comprise a long transmission chain and the external BITS1equipment is used as the clock synchronization source. After the transmission over several NEs,



2-19

the BITS1 clock signals are degraded to a certain degree. In this case, you can output the BITS1signals from NEm that requires clock quality compensation to the local BITS2 equipment forcompensating the signals. Then, after the compensation, the clock signals are transmitted fromthe BITS2 equipment to NEm, to function as the clock synchronization source of the downstreamequipment. The 2M phase-locked source of NEm should be the input clock source of the westline board, and the clock synchronization source should be the BITS2 PRC input externally.

Figure 2-1 Typical application

BITS1 BITS2

NE1 NEm NEnwest east

Clock Signal Flow

westwest

To make sure that the BITS2 equipment receives clock signals from NEm correctly, you needto set the output external clock of NEm. Perform the settings according to parameters of theBITS2 equipment and make sure that the settings on NEm are consistent with the settings onthe BITS2 equipment.

2.11.8 Setting the Clock Source QualityIn a complex clock network, there may be some unknown clock sources. You can uniformlydefine these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.The NE obtains their quality information automatically for clock sources that are allocated toan NE. You should define the quality level of clock sources only during test and maintenance.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > ClockSubnet Configuration from the Function Tree. Click the Clock Quality tab.


Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

Generally, use the default Automatic Extraction.


Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the ManualSetting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level.


----End

2.11.9 Configuring the SSM OutputIf the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messagesautomatically. You can prevent clock sources from sending SSM messages to other clocksubnets. This helps you to ensure that the equipment of different clock subnets do not affect eachother at the edge of clock networks.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > ClockSubnet Configuration from the Function Tree. Click the SSM Output Control tab.

Step 2 Set the Control Status of the clock source.


----End

2.11.10 Switching a Clock SourceWhen the traceable clock source in a network deteriorates, NEs may not be able to execute aswitch on the clock source. You need to manually switch the clock source to prevent clockdeterioration from affecting the normal running of NEs.


l The clock source has been created.



2-21

Context

CAUTIONPerforming clock source switching may cause service interruption.

ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Clock > Clock

Source Switching from the Function Tree. Click the Clock Source Switching tab.

Step 2 Click Query to query the current switching status of a clock source.

Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout.

Step 4 Right-click the clock source that you want to switch and choose a switching operation.NOTE

Before switching the clock source, make sure that the new clock source that is not locked and that is of agood quality is created in the priority table.

Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clocksource and choose Clear Switching.

----End

2.12 Configuring Linear MSPIn a chain network, you can configure a linear multiplex section protection (MSP) to protectservices in the link.

2.12.1 Linear MSPLinear multiplex section (MS) is an SDH protection mechanism to protect services in an SDHchain network.

2.12.2 Configuring Linear MSPFor a link network, you can configure a linear MSP to protect services in the link.

2.12.1 Linear MSPLinear multiplex section (MS) is an SDH protection mechanism to protect services in an SDHchain network.

Implementation PrincipleLinear multiplex section protection (MSP) includes 1+1 linear MSP and 1:1 linear MSP, whichuse the protection channel to protect services transmitted in the working channel. When a faultof the working channel occurs, services are switched to the protection channel. The linear MSPapplies to POS interface and structured STM-N interface.

The APS protocol of the MSP is transmitted by using the protection channel, and the two NEsat the two ends of an MS transmit the protocol status and switching status to each other. TheNEs perform a switching of services according to the protocol status and switching status.


Configuration Guide


Issue 06 (2009-06-01)

SDH 1+1 Linear MSP

See Figure 2-2. When the SDH 1+1 linear MSP is used, services are dual fed and selectivelyreceived. If a fault of the working channel occurs, the receive end of services uses the protectionchannel to receive the services, and thus a service switching is performed.

Figure 2-2 SDH 1+1 linear MSP

Service detection point Service detection point

Working path

Protection path

Access Cross-connect

Line board

Line board

AccessCross-connect

Line board

Line board

SDH 1:1 Linear MSP

See Figure 2-3. When the SDH 1:1 linear MSP is used, services are transmitted in the workingchannel. When a fault of the working channel occurs, services are switched to the protectionchannel and are single-fed and single-received. The APS protocol is transmitted by using theprotection channel, and the two NEs at the two ends of an MS transmit the protocol status andswitching status to each other. The NEs perform a switching of services and selectively receivethe services according to the protocol status and switching status.

Figure 2-3 SDH 1:1 linear MSP

Service detection point

Working path

Protection path

Access Cross-connect

Line board

Line board

AccessCross-connect

Line board

Line board

Service detection point

NOTE

In the case of the linear MSP, do not configure any extra service on the protection path.

2.12.2 Configuring Linear MSPFor a link network, you can configure a linear MSP to protect services in the link.



2-23


When the CD1 or POD41 is used to configure the linear MSP, disable the DCN for the portwhere the protection channel resides.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the FunctionTree.

Step 2 Click Create. The Create a Linear Multiplex Section dialog box is displayed.

Step 3 Set parameters, such as Protection Type, Switching Mode and Revertive Mode for the newlycreated linear MSP. For details on the parameters for linear MSP groups, see Table 2-3.

Step 4 In Slot Mapping Relation, click West Working Unit and select the board with the working

unit from the list of mapping modes. Then, click to finish the mapping of WestWorking Unit. Similarly, set the mapping of the west protection unit.

Step 5 Optional: Click Active check box.

Step 6 Click OK.

Step 7 Select a created protection group and click Start Protocol. Then, the protection group takeseffect.

Step 8 Optional: Select a created protection group and click Stop Protocol. The protection protocolstops running.

----End

2.13 Parameter DescriptionThis section describes the parameters related to the network configuration.

Descriptions of the parameters for NEs

Table 2-1 Attributes of NEs

Field Value Description

Type OptiX PTN 3900 The system searches the type automatically.

ID For example: 3900 Input the NE ID according to the networkingplanning.

Extended ID For example: 9 Input the extended ID of the NE.

Name For example: NE1 Enter the NE name, which contains a maximumof 64 characters. It is recommended that the nameis set in a format of "site name serial Number". Ifthe site name is very long, you can use anacronym.


Configuration Guide


Issue 06 (2009-06-01)


Remarks - Set extra notes of the NE if desired. The maximumlength is 32 characters.

Gateway Type Non-gateway,GatewayDefault: Non-gateway

The gateway type of an NE decides the mode ofcommunication between the NE and the NM. Agateway NE can communicate with the NMdirectly, but a non-gateway NE can onlycommunicate with the NM through a gatewayNE. The gateway type is set on the basis ofphysical connection.

Protocol IP, OSI Displays the protocol used for communicationbetween the Gateway NE and the NM.

IP Address For example:129.9.191.240

This parameter is available only when theprotocol of the gateway NE is the IP protocol.Input the IP address of the gateway NE accordingto the networking planning.

Port Default: 1400 This parameter is available only when thegateway is an IP gateway. Displays the port of thegateway NE.

Affiliated Gateway For example: NE2 When you are creating a Non-Gateway NE, youcan select a created gateway NE as its affiliatedGNE here.

Affiliated GatewayProtocol

IP, OSI Displays the protocol used for communicationbetween the affiliated Gateway NE and the NM.

NE User For example: root The NE name is used when logging in to the NE.Before the NE is configured, use the internallyreserved user name root for login.

Password For example:password

Corresponds to the above NE user password. Thecorresponding password for the reserved userroot is password.

Descriptions of the parameters for NE user

Table 2-2 NE user parameters


NE User For example:USER

The name of the NE user. The name consists of4-16 characters. It can be a combination of letters,digits, spaces and underlines. Note that at leastone letter must be included.



2-25


User Level Monitor level,Operation level,Maintenancelevel, Systemlevel, Debug level.

The operations carried out by the NE user areclassified into five levels, namely monitor level,operation level, maintenance level, system level,debug level from the lowest level to the highest.Each user of higher level can perform all thefunctions that a lower level user can do. Thedetailed right settings for each level are:l Monitor level: all query commands, log in/out,

and modification of its own password.l Operation level: all settings for fault and

performance, partial security settings, andpartial configuration.

l Maintenance level: partial security settings,partial configuration, communication settings,and log management.

l System level: all security settings, allconfiguration.

l Debug level: all security settings, allconfiguration, and all debug commands.Debug level is the highest level.

NE User Flag LCT NE User,EMS NE User,CMD NE User,General NE User

Different NM systems log in to the NE usingdifferent NE users.LCT NE User: The LCT is the local craft terminalof the T2000. This user is the one that the LCTuses for managing the NE.EMS NE User: The EMS is the T2000. This useris the one that the T2000 uses for managing theNE.CMD NE User: CMD is the command line NMS.This user is the one that is used for managing theNE by command line.General NE User: NE user without partition NM.

DetailedDescription

- Displays the user description. Up to 32 characterscan be Description entered.

New Password - New password of the user. The password consistsof 6-16 characters. It can be a combination ofEnglish characters, digits, space and underlines.Note that the password cannot be composed all bydigits or all by letters. It cannot contain specialcharacters.

Confirm Password - The new password of the user that you need toenter again.


Configuration Guide


Issue 06 (2009-06-01)


Whether thepassword isallowed to bemodifiedimmediately

Yes, No Sets whether the password is allowed to bemodified immediately.

Descriptions of the parameters for Linear Multiplex Section Protection (LMSP)group

Table 2-3 Descriptions of the parameters for Linear Multiplex Section Protection (LMSP) group


Protection Group ID For example: 1 The ID of the Linear MSprotection group.

Protection Group Type 1+1 Protection, 1:NProtection

The protection type of alinear MSP group.

Switching Mode Single-Ended Switching,Dual-Ended Switching

The switching mode of alinear MSP group.

Revertive Mode Non-Revertive, Revertive Sets whether the servicesprotected automaticallyswitches back to the workingchannel after the workingchannel recovers.

WTR Time(s) 300 to 720Default: 600

The WTR time of a linearMSP group.

SD enable Enabled, Disabled Whether to enable SD toserve as the MSP switchingcondition.



2-27


Protocol Type New Protocol, RestructureProtocolDefault: New Protocol

The type of MSP protocol.New Protocol: The protocolthat is previously supportedand is applicable to newequipment. Currently it is awidely used protocol.Restructure Protocol:Optimized based on the newprotocol and provides betterprotocol protection measuresto make the protocol stabler.A combination of the newprotocol and the restructureprotocol leads to an NEinterconnection failure.Hence, ensure the sameprotocol type is used by theinterconnected NEs.

Protocol Status Unknown, Already Started Displays the status of MSprotocol.

SD/SF PRI Switching Tag High priority, Low priority The priority of the SD/SF asa switching condition.

Switching Mode Indication Indicated, Not indicated Whether the switching modeis indicated.

Activation Status Active, Inactive Sets the activation status.

Protection Unit Working Unit, ProtectionUnit

Protection unit or workingunit.

West Line For example: 21-POD41-1(PORT-1)

West protection unit and westworking unit of a linear MSprotection group.

West Switching Status Unknown, Force to Standby,Manual to Standby, Exercise,Switch upon signaldegradation, Switch uponsignal failure, Lockout, Non-Revertive Request, Force toActive, Manual to Active,Signal Fail-Protection,Signal Degrade-Protection,Wait-To-Restore, Wait-To-Switch, Idle, Switching, NotLocked out

The switching status of thewest line.

Protected Unit For example: 21-POD41-2(PORT-2)

Displays the board that isunder protection.


Configuration Guide


Issue 06 (2009-06-01)


Remote/Local EndIndication

Remote, Local When the protection group isin Dual-Ended Switchingmode, displays whether theswitching request is from theremote end or the local end.



2-29

3 Configuring the QoS Policy

The PTN equipment supports the HQoS. For the PTN equipment, the configurable QoS policesinclude the port policy, V-UNI ingress policy, V-UNI egress policy, PW policy, QinQ policy,scheduling policy and discarding policy.

ContextFor details on how to configure the port policy, refer to Creating the Port Policy in the FeatureDescription.

For details on how to configure the V-UNI ingress policy, refer to Creating the V-UNI IngressPolicy in the Feature Description.

For details on how to configure the V-UNI egress policy, refer to Creating the V-UNI EgressPolicy in the Feature Description.

For details on how to configure the PW policy, refer to Creating the PW Policy in the FeatureDescription.

For details on how to configure the QinQ policy, refer to Creating the QinQ Policy in the FeatureDescription.

For details on how to configure the ATM policy, refer to Creating the ATM Policy in the FeatureDescription.

For details on how to configure the WFQ scheduling policy, refer to Creating the WFQScheduling Policy in the Feature Description.

For details on how to configure the service WRED policy, refer to Creating the Service WREDPolicy in the Feature Description.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 3 Configuring the QoS Policy


3-1

4 Configuring Interfaces

About This Chapter

This section describes how to set the interface attributes of the boards. In the case of the PTNequipment, the attributes of SDH interfaces, PDH interfaces, Ethernet interfaces, Ethernet virtualinterfaces, Serial interfaces and MP Group can be set.

ContextThe settings of the interface attributes of an interface depends on the application scenario. Fordetails, refer to Table 4-1.

Table 4-1 Types of PTN service interfaces

ServiceInterface

SupportedPort Mode/EncapsulationType

Port Type MP GroupSupported orNot

Function

SDH interface Generalattributes

Physical port Not supported Sets togetherwith the Layer 3attributes orconnects to theequipment asthe channelizedSTM serviceinterface.

Layer 2attributes

Physical port Not supported This interfacecan carry theATM services.

Layer 3attributes

Physical port Not supported This interfacecan carrytunnels after thePPP is enabled.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 4 Configuring Interfaces


4-1

ServiceInterface



Function

PDH interface Generalattributes

Physical port Not supported This interfacecan carry theTDM services.

Layer 2attributes

Physical port Not supported Carries the IMAsignals.

Layer 3attributes

Physical port Supported This interfacecan be addedinto a multilinkPPP (MP) groupafter the PPP isenabled.

Ethernetinterface

Generalattributes

None None Sets togetherwith the Layer 2and Layer 3attributes.

Layer 2attributes

Physical port Not supported Carries the user-side or network-side Ethernetservices.

Layer 3attributes

Physical port Not supported Carries tunnels.

Ethernet Virtualinterface

Generalattributes

Logical port Not supported Sets togetherwith the Layer 2and Layer 3attributes.

Layer 2attributes

Logical port Not supported Carries theEthernetservices forVLAN SubInterface.

Layer 3attributes

Logical port Not supported l EOA VirtualInterface:carries the IPor GREtunnels.

l VLAN SubInterface:applies to theBFD,L3VPN orTunnel

4 Configuring InterfacesOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

ServiceInterface



Function

Serial interface Generalattributes

None None Sets togetherwith the Layer 3attributes.

Layer 3attributes

Logical port Supported This interfacecan be added toan MP groupafter the PPP isenabled.

MP Group Generalattributes

None None Sets togetherwith the IPattributes.

IP attributes Logical port None Carries tunnels.

4.1 Configuring SDH InterfacesThis section describes how to set the attributes of SDH interfaces. In a packet switching network(PSN), set the attributes of the SDH interfaces for them to work in the channelized STM mode,ATM mode or POS mode. In a PSN network, the ATM interface can be used to connect to theuser-side equipment, and the POS interface can be used to carry the tunnel. The attributes ofSDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advancedattributes.

4.2 Configuring PDH InterfacesThis section describes how to set the attributes of PDH interfaces. In a PSN network, the PDHinterfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on differentsettings of the interface attributes. The attributes of a PDH interface include the generalattributes, layer 2 attributes, layer 3 attributes and advanced attributes.

4.3 Configuring Ethernet InterfacesThis section describes how to set the attributes of Ethernet interfaces. In a PSN network, theEthernet interfaces can be used to carry Ethernet packets or tunnels, depending on differentsettings of the interface attributes. The attributes of the Ethernet interface include the generalattributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.

4.4 Configuring Serial InterfacesThis topic describes how to set the attributes of serial interfaces.

4.5 Configuring ML-PPPThis section describes how to configure Multilink PPP (MP) group. MP is a technology used tobind multiple PPP links to increase the bandwidth. MP is applied to the interface that supportsPPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPPlinks in the MP group to the same destination.

4.6 Configuring an Ethernet Virtual InterfaceThis section describes how to configure an Ethernet virtual interface. After you configure theEthernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulated



4-3

Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3attributes.

4.7 Configuring Ethernet Link Aggregation GroupThe link aggregation makes the output and input load shared by the members of an LAG toincrease the bandwidth. In the meantime, the members of the LAG can dynamically back upeach other to enhance the connection reliability.

4.8 Configuring the IMAThe inverse multiplexing for ATM (IMA) technology is used to break up the stream of ATMcells and transport them over multiple lower-rate links, and to reconstruct these lower-rate linksat the destination to recover the stream of ATM cells. In this way, the multiple lower-rate linksare multiplexed in a flexible and convenient manner.

4.9 Parameter DescriptionThis section describes the parameters related to the interface configuration.


Configuration Guide


Issue 06 (2009-06-01)

4.1 Configuring SDH InterfacesThis section describes how to set the attributes of SDH interfaces. In a packet switching network(PSN), set the attributes of the SDH interfaces for them to work in the channelized STM mode,ATM mode or POS mode. In a PSN network, the ATM interface can be used to connect to theuser-side equipment, and the POS interface can be used to carry the tunnel. The attributes ofSDH interfaces include the general attributes, Layer 2 attributes, Layer 3 attributes and advancedattributes.

ContextThe attributes vary with the application scenarios of SDH interfaces. Table 4-2 lists theapplication scenarios.

Table 4-2 Application scenario of SDH interfaces

Application Scenario Interface Type Required InterfaceAttribute

Carrying the CES service Channelized STM-1interface

General attributes

Carrying the ATM service ATM interface General attributes, Layer 2attributes

Carrying the tunnel POS interface General attributes, Layer 3attributes

Follow the procedure shown in Figure 4-1 to configure an SDH interface.



4-5

Figure 4-1 Procedure for configuring an SDH interface

Configure cSTMinterface

Configure generalattributes

Start

Configure advancedattributes

End

Configure ATMinterface


Start


End

Configure layer 2attributes

Configure POSinterface


Start


End


Required

Optional

4.1.1 Setting the General Attributes of SDH InterfacesThe general attributes of an SDH interface define the physical-layer information, such as theport mode, encapsulation type, and maximum data packet length. An SDH interface can beconfigured as a channelized STM interface, ATM interface, or POS interface. Before youconfigure an SDH interface into a POS interface, set the general attributes of the SDH interface.

4.1.2 Setting the Layer 2 Attributes of SDH InterfacesBefore you create an ATM service, you need to set the layer 2 attributes of the correspondingSDH interface. The layer 2 attributes of a SDH interface define the related information of thedata link layer.

4.1.3 Setting the Layer 3 Attributes of SDH InterfacesBefore you run PPP on an SDH interface, you need to set the layer 3 attributes of the SDHinterface. The layer 3 attributes of an SDH interface define the related attributes of the networklayer.

4.1.4 Setting the Advanced Attributes of SDH InterfacesThe routine maintenance parameters can be set by setting the advanced attributes of SDHinterfaces.


Configuration Guide


Issue 06 (2009-06-01)

4.1.1 Setting the General Attributes of SDH InterfacesThe general attributes of an SDH interface define the physical-layer information, such as theport mode, encapsulation type, and maximum data packet length. An SDH interface can beconfigured as a channelized STM interface, ATM interface, or POS interface. Before youconfigure an SDH interface into a POS interface, set the general attributes of the SDH interface.


ContextPacket over SDH (POS) is a technology that is used to transport packet data in MAN and WANnetworks. POS adopts SDH and SONET as the physical layer protocols and directly maps thevariable-length data packets into SDH payload, thus providing a type of high-speed, reliable,and point-to-point data connection.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDHInterface from the Function Tree.

Step 2 Select the desired board.

Step 3 Set the parameters as required.

For details on the parameters for general attributes of an SDH interface, see Table 4-6.

NOTE

Note the following issues during parameter settings:

l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case,channelized STM-N services can be accessed.

l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATMservices can be accessed.

l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, theinterface does not enable the PPP, and thus the equipment bears less load. If you select PPP, the interfacecan access the MPLS or IP service.

l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packetcontains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packetsin the receive direction may be lost.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation issuccessful.

Step 5 Click Close.

----End



4-7

4.1.2 Setting the Layer 2 Attributes of SDH InterfacesBefore you create an ATM service, you need to set the layer 2 attributes of the correspondingSDH interface. The layer 2 attributes of a SDH interface define the related information of thedata link layer.


Procedure


Step 2 Click the Layer 2 Attributes tab.

Step 3 Select the board to be configured and set the parameters as required. For details on the parametersfor layer 2 attributes of the corresponding SDH interface,see Table 4-7.

NOTEAD1 sub-board: VPI ranges from 0 to 4095 and VCI ranges from 32 to 65535. The VPI range and VCIrange can be set for each port on the AD1. Each VP uses two items in the VP switch table and each VCuses one item in the VC switch table. For the AD1, the number of total items in the VP switch table andVC switch table is 88324.

CAUTIONIf any service is configured on the port, modifying the VPI or VCI range for the port causestransient interruption of the service.


Step 5 Click Close.

----End

4.1.3 Setting the Layer 3 Attributes of SDH InterfacesBefore you run PPP on an SDH interface, you need to set the layer 3 attributes of the SDHinterface. The layer 3 attributes of an SDH interface define the related attributes of the networklayer.


l In General Attributes, Encapsulation Type must be set to PPP.


Configuration Guide


Issue 06 (2009-06-01)

ContextIn a PSN network, the SDH interface is used to transport the PPP-encapsulated packet data.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >SDH Interface from the Function Tree.


Step 3 Select the desired board and set the parameters as required. For details on the parameters forlayer 3 attributes of the SDH interface, see Table 4-8.

NOTE


l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total of the maximumreserved bandwidth of the tunnels carried by port should be not more than the physical bandwidth ofthe port.

l When changing Specify IP from Manually to Unnumbered IP, manually specify the invalid IPaddress (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manuallyspecified.

l When modifying the IP address of the interface, make sure that the IP address of this interface and theIP addresses of other interfaces configured with services are not in the same subnet.

Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation issuccessful.

Step 5 Click Close.

----End

4.1.4 Setting the Advanced Attributes of SDH InterfacesThe routine maintenance parameters can be set by setting the advanced attributes of SDHinterfaces.


Procedure


Step 2 Click the Advanced Attributes tab.

Step 3 Select the board to be configured and set the parameters as required. For details on the parametersfor advanced attributes of the SDH interface, see Table 4-9.



4-9


Step 5 Click Close.

----End

4.2 Configuring PDH InterfacesThis section describes how to set the attributes of PDH interfaces. In a PSN network, the PDHinterfaces can be used to carry TDM signals, IMA signals, or tunnels, depending on differentsettings of the interface attributes. The attributes of a PDH interface include the generalattributes, layer 2 attributes, layer 3 attributes and advanced attributes.

ContextThe application scenario of a PDH interface depends on the setting of the interface attributes.For details, refer to Table 4-3.

Table 4-3 Application scenario of PDH interfaces


Carrying the CES service E1 interface General attributes, Advancedattributes

Carrying the ATM service E1 interface General attributes, Layer 2attributes

Carrying the tunnel E1 interface General attributes, Layer 3attributes


Configuration Guide


Issue 06 (2009-06-01)

NOTE

When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, thatis, frame format, to ensure that the frame format is the same as the service encapsulation format. When theemulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interfaceto CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interfaceshould be set to non-framing.

When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, theIMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer2 in 4.2.1 Setting General Attributes of PDH Interfaces.

When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create theML-PPP group, and configure the interface as an ML-PPP member.

Follow the procedure shown in Figure 4-2 to configure a PDH interface.

Figure 4-2 Procedure for configuring a PDH interface

Configure general attributes

Start

Configure advanced attributes

End

Carry CES service Carry ATM service


Start


End


Required

Optional

Carry Tunnel


Start


End

4.2.1 Setting General Attributes of PDH InterfacesBefore you create services, you need to set the general attributes of the corresponding PDHinterfaces. The general attributes of a PDH interface define the related information of the physicallayer.

4.2.2 Setting the Layer 3 Attributes of PDH InterfacesBefore you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.The layer 3 attributes of a PDH interface define the related attributes of the network layer.

4.2.3 Setting the Advanced Attributes of PDH InterfacesThe advanced attributes of PDH interfaces include frame format, line encoding format andloopback mode.



4-11

4.2.1 Setting General Attributes of PDH InterfacesBefore you create services, you need to set the general attributes of the corresponding PDHinterfaces. The general attributes of a PDH interface define the related information of the physicallayer.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDHInterface from the Function Tree.

Step 2 Select the desired board.


For details on the parameters for general attributes of the PDH interface, see Table 4-10.

NOTE


l When Port Mode is set to Layer 1, Encapsulation Type does not support the settings. In this case,TDM services can be accessed.

l When Port Mode is set to Layer 2, Encapsulation Type supports ATM only. In this case, ATMservices can be accessed.

l If the PDH interface is used for the inband DCN, the Port Mode cannot be set to Layer 1 or Layer2.

l If you set Port Mode to Layer 3, select Null or PPP for Encapsulation Type. If you select Null, theinterface does not enable the PPP protocol, and thus the equipment bears less load. If you select PPP,the interface can carry the MPLS.



Step 5 Click Close.

----End

4.2.2 Setting the Layer 3 Attributes of PDH InterfacesBefore you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.The layer 3 attributes of a PDH interface define the related attributes of the network layer.



Configuration Guide


Issue 06 (2009-06-01)

l In General Attributes, Port Mode must be set to Layer 3.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDHInterface from the Function Tree.


Step 3 Select the desired board and set the parameters as required. For details on the parameters forlayer 3 attributes of the PDH interface, see Table 4-11.

NOTE


l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reservedbandwidth of the tunnel carried by port should be not more than the physical bandwidth of the port.


Step 5 Click Close.

----End

4.2.3 Setting the Advanced Attributes of PDH InterfacesThe advanced attributes of PDH interfaces include frame format, line encoding format andloopback mode.


Procedure

Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDHInterface from the Function Tree.


Step 3 Select the board to be configured and set the parameters as required. For details on the parametersfor advanced attributes of the PDH interface, see Table 4-12.



4-13

NOTE

If the E1 interface carries the CES service whose emulation mode is CESoPSN, Frame Format of theinterfaces can be set to Double Frame or CRC-4 Multiframe. It is recommended that you set FrameFormat to CRC-4 Multiframe. If the emulation mode of the CES service is SAToP, Frame Format ofthe interface must be set to Unframe.If the E1 interface carries the ATM service, Frame Format of the interface can be set to Double Frameor CRC-4 Multiframe.In the case of the OptiX PTN 3900, OptiX PTN 1900, OptiX PTN 950, or OptiX PTN 910, FrameMode of the packets at the PDH interface can be set to 30 or 31. In the case of the OptiX PTN 912, FrameMode of the packets at the PDH interface can be set only to 30. In hybrid networking, make sure that theframe modes of the local port and opposite port should be the same.

l 30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data.

l 31: In the E1 frame format, timeslots 1-31 are used to transport service data.


Step 5 Click Close.

----End

4.3 Configuring Ethernet InterfacesThis section describes how to set the attributes of Ethernet interfaces. In a PSN network, theEthernet interfaces can be used to carry Ethernet packets or tunnels, depending on differentsettings of the interface attributes. The attributes of the Ethernet interface include the generalattributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.

ContextThe application scenario of an Ethernet interface depends on the setting of the interface attributes.For details, refer to Table 4-4.

Table 4-4 Application scenario of Ethernet interfaces


Accessing the Ethernetservice

Ethernet interface General attributes, Layer 2attributes

Carrying the QinQ Link Ethernet interface General attributes, Layer 2attributes

Carrying the tunnel Ethernet interface General attributes, Layer 3attributes

NOTE

When the Ethernet interface is used to carry the QinQ Link, the configuration procedure is similar to theconfiguration procedure when the Ethernet interface is used to carry the Ethernet service. In this case, however,the encapsulation types are different. For details, see 4.3.2 Setting the Layer 2 Attributes of EthernetInterfaces.


Configuration Guide


Issue 06 (2009-06-01)

Follow the procedure shown in Figure 4-3 to configure an Ethernet interface.

Figure 4-3 Procedure for configuring an Ethernet interface

Carry Ethernet Packets Carry Tunnel


Start


Start

Configure flow control

End


Required

Optional

Configure flow control

End




4.3.1 Setting the General Attributes of Ethernet InterfacesBefore you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need toconfigure the general attributes of the corresponding Ethernet interface. The general attributesof an Ethernet interface define the physical-layer information, such as the port mode,encapsulation type, and maximum frame length.

4.3.2 Setting the Layer 2 Attributes of Ethernet InterfacesAfter the layer 2 attributes of an Ethernet interface are set, the interface can be used for connectingto the client-side equipment at the edge of a PSN network or for forwarding Ethernet packetswithin the PSN network. The Layer 2 attributes of an Ethernet interface define the relatedinformation of the data link layer.

4.3.3 Setting the Layer 3 Attributes of an Ethernet Interface



4-15

When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributesof the Ethernet interface. The layer 3 attributes of an Ethernet interface define the relatedattributes of the network layer.

4.3.4 Setting the Advanced Attributes of Ethernet InterfacesThe routine maintenance parameters can be set through setting the advanced attributes ofEthernet interfaces.

4.3.5 Configuring Flow ControlIn the case that the flow control function is enabled, if congestion occurs on the link, the Ethernetinterface sends a PAUSE frame to the opposite end, and then the opposite end stops transmittingEthernet packets. As a result, congestion is avoided.

4.3.1 Setting the General Attributes of Ethernet InterfacesBefore you configure the layer 2 and layer 3 attributes of an Ethernet interface, you need toconfigure the general attributes of the corresponding Ethernet interface. The general attributesof an Ethernet interface define the physical-layer information, such as the port mode,encapsulation type, and maximum frame length.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >Ethernet Interface from the Function Tree.

Step 2 Click the General Attributes tab.

Step 3 Select the desired board and set the parameters as required. For details on the parameters forgeneral attributes of the Ethernet interface, seeTable 4-13.

NOTE

l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.

l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interfacecan be used by tunnel.



Step 5 Click Close.

----End


Configuration Guide


Issue 06 (2009-06-01)

4.3.2 Setting the Layer 2 Attributes of Ethernet InterfacesAfter the layer 2 attributes of an Ethernet interface are set, the interface can be used for connectingto the client-side equipment at the edge of a PSN network or for forwarding Ethernet packetswithin the PSN network. The Layer 2 attributes of an Ethernet interface define the relatedinformation of the data link layer.



Procedure



Step 3 Select the desired board and set the parameters as required. For details on the parameters forlayer 2 attributes of the Ethernet interface, seeTable 4-14.

NOTE


l QinQ Type Domain can be set only when Encapsulation Type is QinQ.

l TAG can be set only when Encapsulation Type is 802.1Q.

l Default VLAN ID and VLAN Priority are valid when TAG is access or hybrid.

Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that theoperation is successful.

Step 5 Click Close.

----End

4.3.3 Setting the Layer 3 Attributes of an Ethernet InterfaceWhen an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributesof the Ethernet interface. The layer 3 attributes of an Ethernet interface define the relatedattributes of the network layer.





4-17

Procedure



Step 3 Select the desired board and set the parameters as required. For details on the parameters forlayer 3 attributes of the Ethernet interface, see Table 4-15.

NOTE


l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reservedbandwidth of the tunnels carried by port cannot exceed the physical bandwidth of the port.



Step 5 Click Close.

----End

4.3.4 Setting the Advanced Attributes of Ethernet InterfacesThe routine maintenance parameters can be set through setting the advanced attributes ofEthernet interfaces.


Procedure

Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management >Ethernet Interface from the Function Tree.


Step 3 Select the board to be configured and set the parameters as required. For details on the parametersfor advanced attributes of the Ethernet interface, see Table 4-16.


Step 5 Click Close.

----End

4.3.5 Configuring Flow ControlIn the case that the flow control function is enabled, if congestion occurs on the link, the Ethernetinterface sends a PAUSE frame to the opposite end, and then the opposite end stops transmittingEthernet packets. As a result, congestion is avoided.


Configuration Guide


Issue 06 (2009-06-01)


Procedure


Step 2 Click the Flow Control tab.

Step 3 Select the desired board and set the parameters as required. For details on the parameters forflow control, see Table 4-17.


Step 5 Click Close.

----End

4.4 Configuring Serial InterfacesThis topic describes how to set the attributes of serial interfaces.

ContextTable 4-5 lists the application scenario of serial interfaces.

Table 4-5 Application scenario of serial interfaces

Application Scenario Required Interface Attribute

Carrying the tunnel Basic attributes, Layer 3 attributes

Carrying the CES service, ATM service Basic attributes

Follow the procedure shown in Figure 4-4 to configure the serial interface attributes.



4-19

Figure 4-4 Procedure for configuring a serial interface


Start

End


Required

Optional

Create Serial interface

4.4.1 Creating Serial InterfacesYou can create a serial interface at the VC12 level level.

4.4.2 Setting the General Attributes of a Serial InterfaceBefore you set the layer 3 attributes of a serial interface, you need to set the general attributesof the serial interface. The general attributes of a serial interface define the related informationof the physical layer.

4.4.3 Setting the Layer 3 Attributes of Serial InterfacesIn a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.The layer 3 attributes of a serial interface define the related attributes of the network layer.

4.4.1 Creating Serial InterfacesYou can create a serial interface at the VC12 level level.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SerialInterface from the Function Tree.


Configuration Guide


Issue 06 (2009-06-01)

Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed.

Step 3 Set the parameters as required. For details on the parameters for the serial interface, seeTable4-18.

NOTE

l In the case of the serial interface at the VC12 level, currently a serial interface can be bound to onlyone timeslot.


Step 5 Click Close.

----End

4.4.2 Setting the General Attributes of a Serial InterfaceBefore you set the layer 3 attributes of a serial interface, you need to set the general attributesof the serial interface. The general attributes of a serial interface define the related informationof the physical layer.


l A serial interface must be created.



4-21

Procedure


Step 2 Set the parameters as required.For details on the parameters for general attributes of the serialinterface, seeTable 4-18.

NOTE

When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMAbinding.

When you set Port Mode to Layer 3, you can set Encapsulation Type to PPP or Null. When you setEncapsulation Type to PPP, you can add the serial interface to an MP group. The serial interfaces thatare bound to the same MP group have the same E1 frame mode. When Encapsulation Type is Null, PortMode can be changed to Layer 2.

In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet containsa maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN packets in thereceive direction may be lost.

Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation wassuccessful.

Step 4 Click Close.

----End

4.4.3 Setting the Layer 3 Attributes of Serial InterfacesIn a PSN network, the serial interfaces are used to transport the PPP-encapsulated packet data.The layer 3 attributes of a serial interface define the related attributes of the network layer.



Procedure


Step 2 Click the Layer 3 Attributes tab and set the parameters as required.For details on the parametersfor layer 3 attributes of the serial interface, see Table 4-19.


Configuration Guide


Issue 06 (2009-06-01)

NOTE


l Max Reserved Bandwidth indicates the bandwidth used by tunnels. The total maximum reservedbandwidth of the tunnels carried by port should be not more than the physical bandwidth of the port.

l Modifying the IP address can cause the equipment to re-establish the link. As a result, the services areinterrupted.

l When changing Specify IP from Manually to Unnumbered IP, manually specify the invalid IPaddress (255.255.255.255) and invalid IP mask (255.255.255.255) to release the IP address manuallyspecified.



Step 4 Click Close.

----End

4.5 Configuring ML-PPPThis section describes how to configure Multilink PPP (MP) group. MP is a technology used tobind multiple PPP links to increase the bandwidth. MP is applied to the interface that supportsPPP. MP supports fragmented packets. The fragmented packets are transmitted on multiple PPPlinks in the MP group to the same destination.

ContextFollow the procedure shown in Figure 4-5 to configure an MP group.



4-23

Figure 4-5 Procedure for configuring an MP group

Enable the PPP at theinterface

Start

End

Create MPgroup

Required

Optional

Configure members to anMP group

4.5.1 Creating MP GroupsYou can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating anMP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carrytunnels.

4.5.2 Configuring Member Interfaces of MP GroupsTo modify the bandwidth of the MP group, add or delete the member interfaces into or from theMP group.

4.5.1 Creating MP GroupsYou can bind multiple serial interfaces or E1 interfaces on which PPP is enabled by creating anMP group, so that the bound serial interfaces or E1 interfaces are used as a logical port to carrytunnels.


l Multiple serial interfaces or E1 interfaces on which PPP is enabled must be created.

l The E1 Frame Format or VC12 Frame Format of the local MP group and the oppositeMP group should be consistent.


Configuration Guide


Issue 06 (2009-06-01)

ContextNOTE

The MP group can be bound only with the E1 interfaces of the same processing board, or the serial interfacesof the same physical interface.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MPGroup Management from the Function Tree.

Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed.

Step 3 Set the parameters as required. For details on the parameters for general attributes of the MPgroup, see Table 1.


Step 5 Click Close.

----End



4-25

4.5.2 Configuring Member Interfaces of MP GroupsTo modify the bandwidth of the MP group, add or delete the member interfaces into or from theMP group.


l An MP group must be configured.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MPGroup Management from the Function Tree.

Step 2 Select an MP group and click Configuration. The Config Member Interface dialog box isdisplayed.


Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interruptthe services.

NOTE

Deleting the member interface of the MP group may damage the service.

The member interface in the same MP group must have the same frame mode. That is, the values of FrameMode are all 30 or 31. for the parameters of Frame Mode, to see E1 Frame Format or VC12 FrameFormat.

Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful.

Step 6 Click Close.

----End


Configuration Guide


Issue 06 (2009-06-01)

4.6 Configuring an Ethernet Virtual InterfaceThis section describes how to configure an Ethernet virtual interface. After you configure theEthernet virtual interface, the NE can process ATM AAL5-encapsulated or VLAN-encapsulatedEthernet packets. The Ethernet virtual interface attributes include general attributes and layer 3attributes.

4.6.1 Setting the General Attributes of Ethernet Virtual InterfacesThe general attributes of an Ethernet virtual interface define the related information of the ATMadaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you needto configure the general attributes of the Ethernet virtual interface.

4.6.2 Setting the Layer 3 Attributes of Ethernet Virtual InterfacesYou can set the Tunnel attributes of an Ethernet virtual interface by setting the layer 3 attributesof the Ethernet virtual interface.

4.6.1 Setting the General Attributes of Ethernet Virtual InterfacesThe general attributes of an Ethernet virtual interface define the related information of the ATMadaptation layer (AAL) or VLAN. Before you configure an Ethernet virtual interface, you needto configure the general attributes of the Ethernet virtual interface.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >Ethernet Virtual Interface from the Function Tree.

Step 2 Click Query. The Operation Result dialog box is displayed dialog box is displayed indicatingthat the operation is successful.

Step 3 Click Close. The general attributes of an Ethernet virtual interface are displayed in the field. Fordetails on the parameters for general attributes of the Ethernet virtual interface, seeTable 4-20.


----End

4.6.2 Setting the Layer 3 Attributes of Ethernet Virtual InterfacesYou can set the Tunnel attributes of an Ethernet virtual interface by setting the layer 3 attributesof the Ethernet virtual interface.


l The general attributes of the Ethernet virtual interface must be set.



4-27

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >Ethernet Virtual Interface from the Function Tree.

Step 2 Click the Layer 3 Attributes tab and set the parameters as required. For details on the parametersfor layer 3 attributes of the Ethernet virtual interface, seeTable 4-21.

CAUTIONWhen modifying the IP address of the interface, make sure that the IP address of this interfaceand the IP addresses of other interfaces configured with services are not in the same subnet.

Step 3 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.

----End

4.7 Configuring Ethernet Link Aggregation GroupThe link aggregation makes the output and input load shared by the members of an LAG toincrease the bandwidth. In the meantime, the members of the LAG can dynamically back upeach other to enhance the connection reliability.

ProcedureFor details of configuring Ethernet LAG, refer to Creating an LAG in the FeatureDescription.

----End

4.8 Configuring the IMAThe inverse multiplexing for ATM (IMA) technology is used to break up the stream of ATMcells and transport them over multiple lower-rate links, and to reconstruct these lower-rate linksat the destination to recover the stream of ATM cells. In this way, the multiple lower-rate linksare multiplexed in a flexible and convenient manner.

Procedure

Step 1 For details of configuring bound channels in an ATM IMA group, refer to Configuring BoundChannels in an ATM IMA Group in the Feature Description.

Step 2 For details of configuring attributes of an ATM IMA group, refer to Configuring Attributes ofan ATM IMA Group in the Feature Description.

NOTE

After the IMA group is configured, the IMA protocol must be enabled.

Step 3 For details of configuring ATM interface attributes, refer to Configuring ATM InterfaceAttributes in the Feature Description.

----End


Configuration Guide


Issue 06 (2009-06-01)

4.9 Parameter DescriptionThis section describes the parameters related to the interface configuration.

Table 4-6 Descriptions of the parameters for SDH interface General Attributes


Port For example: 4-MP1-1-CD1-1(Port-1)

Display the port name.

Name For example: Port1 Enter the self-defined portname.

Port Mode Layer 1, Layer 2, Layer 3 Display the working mode ofthe SDH interface accordingto the type of the housedboard.Layer 1 indicates the currentchannelized STM interface.Layer 2 indicates the currentATM STM interface.Layer 3 indicates the currentPOS interface.

Encapsulation Type Null, ATM, PPP Select the encapsulationtype.When Port Mode is set toLayer 1, EncapsulationType defaults to Null, andcannot be modified.When Port Mode is set toLayer 2, EncapsulationType defaults to ATM, andcannot be modified.When Port Mode is set toLayer 3, set EncapsulationType to Null or PPP.Click C.89 EncapsulationType for more information.

Channelize Yes, No Display whether the interfaceis channelized.

Laser Interface EnablingStatus

Enabled, Shut DownDefault: Enabled

Enable or disable the laser.Click C.96 Laser InterfaceEnabling Status for moreinformation.



4-29


Max Data Packet Size (byte) 46 to 9000Default: 1620

Set the maximum packetlength.This parameter cannot be setwhen Port Mode is set toLayer 1 or Layer 2.Click C.165 Max DataPacket Size(byte) for moreinformation.

Table 4-7 Descriptions of the parameters for SDH interface Layer 2 Attributes


Port For example: 4-MP1-1-AD1-1(Port-1)


Port Type UNI, NNI Select the port type.UNI indicates the user-network interface, whichconnects to the client-sideequipment.NNI indicates the network-network interface, whichconnects to the ATMequipment in the corenetwork.Click C.6 ATM Port Typefor more information.

ATM Cell PayloadScrambling

Disabled, Enabled When the ATM cell payloadscrambling is enabled,several "0"s and "1"s in thedata are suppressed.Click C.7 ATM CellPayload Scrambling formore information.


Configuration Guide


Issue 06 (2009-06-01)


Max. VPI Bits UNI: 1 to 8NNI: 1 to 12

In the case ofinterconnection, if the VPIvalue of the oppositeequipment exceeds thedefault VPI value of the localequipment, manually set theVPI value range.Set Max. VPI Bits to set theVPI value range. Forexample, if Max. VPI Bits isset to 8, the VPI value rangesfrom 0 to 255.Click C.162 Max. VPI Bitsfor more information.

Max. VCI Bits 6 to 16 In the case ofinterconnection, if the VCIvalue of the oppositeequipment exceeds thedefault VPI value of the localequipment, manually set theVPI value range.Set Max. VCI Bits to set theVCI value range. Forexample, if Max. VCI Bits isset to 8, the VCI value rangesfrom 0 to 255.Click C.161 Max. VCI Bitsfor more information.

VCC-Supported VPI Count 0 to 4096 Set the count of VPIs thatsupport the VC switching.Click C.154 VC-Switching-Supported VPIs for moreinformation.

Table 4-8 Descriptions of the parameters for SDH interface Layer 3 Attributes


Port Example: 21-POD41-1(Port-1)




4-31


Enable Tunnel Disabled, Enabled After the Tunnel is enabled,the port can identify andprocess the MPLS label, andthus supports the dynamicsignaling and route.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.Click C.40 Enable Tunnelfor more information.

Max Reserved Bandwidth(kbit/s)

0 to 516096Default: 516096

Set the maximum bandwidthused by the tunnel.The maximum reservedbandwidth should not exceedthe physical bandwidth of thebearer port.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.

TE Measurement 0 to 16777215 Sets the TE measurement.You can intervene in theroute selection by adjustingthe TE measurement of thelink. The smaller the value ofthe TE measurement, thehigher the priority of the link.Thus, the traffic congestionof the shortest path thatoccurs in the traditional routeselection can be avoided.


Configuration Guide


Issue 06 (2009-06-01)


Admin Group 0 to 4294967295 Set the admin group.The admin group can specifythe link attributes. After theaffinity attributes of adynamic tunnel isconfigured, when thedynamic tunnel selects links,the dynamic tunnel comparesits affinity attributes with theadmin attributes of links anddetermines which links to beavoided.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.

Specify IP Manually, Unnumbered NEIP, Unnumbered Interface IP,Unspecified

Select the means of settingthe IP address for the port.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.

IP Address Example: 192.168.0.1 Set the IP address for the port.This parameter can be setonly when Specify IP is setto Manually.

IP Mask Example: 255.255.255.0 Set the subnet mask of theport.This parameter can be setonly when Specify IP is setto Manually.

Board for Unnumbered IP Example: 3-ETFC Select the board for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Unnumbered InterfaceIP.

Port for Unnumbered IP Example: 3-ETFC-3(Port-3) Select the port for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Unnumbered InterfaceIP.



4-33

Table 4-9 Descriptions of the parameters for Advanced Attributes of the SDH interface


Port For example: 4-MP1-1-CD1-1(Port-1)


Laser Transmission Distance(m)

For example: 1000 Display the transmissiondistance of the laser.Click C.97 LaserTransmission Distance (m)for more information.

Scrambling Capability Enabled, DisabledDefault: Enabled

When the ATM cell payloadscrambling is enabled,several "0"s and "1"s in thedata are suppressed.Click C.99 ScramblingCapability (POS Port) formore information.

CRC Check Length 16, 32 Select the CRC check length.Click C.14 CRC CheckLength for moreinformation.

Clock Mode Master Mode, Slave Mode Select the clock mode.Master Mode indicates thatthe internal clock signals areadopted.Slave Mode indicates thatthe line clock signals areadopted.Click C.121 Clock Mode(PDH/SDH Port) for moreinformation.

Loopback Mode Non-Loopback, Inloop,Outloop

Set the loopback status of theport.

Table 4-10 Descriptions of the parameters for PDH interface General Attributes


Port For example: Slot-BoardName-Port(Port No.)




Configuration Guide


Issue 06 (2009-06-01)


Port Mode Layer 1, Layer 2, Layer 3 Select the working mode ofthe PDH port.Layer 1: The port can carryTDM signals.Layer 2: The port can carryIMA signals.Layer 3: The port can carryPPP protocol packets.Click C.80 Port Mode formore information.

Encapsulation Type Null, ATM, PPP Select the encapsulationtype.When Port Mode is set toLayer 1, EncapsulationType defaults to Null, andcannot be modified.When Port Mode is set toLayer 2, EncapsulationType defaults to ATM, andcannot be modified.When Port Mode is set toLayer 3, set EncapsulationType to Null or PPP.Click C.89 EncapsulationType for more information.

Channelize Yes, No Set whether the interface ischannelized.

Max Data Packet Size (byte) 960 to 1900Default: 1620

Set the maximum data packetlength.This parameter can be setonly when Port Mode is setto Layer 3, andEncapsulation Type toPPP.

Table 4-11 Descriptions of the parameters for PDH interface Layer 3 Attributes






4-35


Enable Tunnel Default: Disabled The PDH interface does notsupport setting the EnableTunnel parameter.


0 to 2048Default: 2048



Admin Group 0 to 4294967295 Sets the admin group.The admin group can specifythe link attributes. After theaffinity attributes of adynamic tunnel isconfigured, when thedynamic tunnel selects links,the dynamic tunnel comparesits affinity attributes with theadmin attributes of links anddetermines which links to beavoided.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.

Specify IP Unspecified The PDH interface does notsupport setting the IPattributes.


Configuration Guide


Issue 06 (2009-06-01)


IP Address - The PDH interface does notsupport setting the IPattributes.

IP Mask - The PDH interface does notsupport setting the IPattributes.

Board for Unnumbered IP - The PDH interface does notsupport setting the IPattributes.

Port for Unnumbered IP - The PDH interface does notsupport setting the IPattributes.

Table 4-12 Descriptions of the parameters for PDH interface Advanced Attributes




Frame Format Unframe, Double Frame,CRC-4 Multiframe

Select the frame format.When the emulation mode ofa CES service is CESoPSN,the frame format at theinterface should be set toCRC-4 Multiframe. Whenthe emulation mode of a CESservice is SAToP, the frameformat at the interface shouldbe set to Unframe.NOTE

When you set Port Mode toLayer 2, you cannot set FrameFormat to Unframe for theOptiX PTN 1900 or OptiX PTN3900.

Click C.152 Frame Formatfor more information.

Line Encoding Format HDB3 Display the line encodingformat.

Clock Mode Master Mode, Slave Mode Select the clock mode.Click C.121 Clock Mode(PDH/SDH Port) for moreinformation.



4-37


Loopback Mode Non-Loopback, Inloop,Outloop

Set the loopback status of theport.

Impedance 75 ohm, 120 ohm Display the impedance of theinterface.Click C.159 Impedance formore information.

Frame Mode 30, 31 Set the value of the framemode.The frame modes of the localport and opposite port shouldbe the same.

Table 4-13 Descriptions of the parameters for Ethernet interface General Attributes


Port For example: 1-EG16-1(Port-1)



Enable Port Disabled, Enabled When the port is enabled, itindicates that the user usesthe port and the port hasservices. When the port isdisabled, it indicates that theport does not processservices. When configuringservices, enable the involvedports.Click C.81 Enable Port formore information.

Port Mode Layer 2, Layer 3, Layer Mix Select the working mode ofthe Ethernet port.Layer 2: The port can accessthe user-side equipment orcarry Ethernet services thatare based on the ports and usethe port exclusively.Layer 3: The port can carrytunnels.Layer Mix: The port cancarry layer 2 services andlayer 3 services.


Configuration Guide


Issue 06 (2009-06-01)


Encapsulation Type Null, 802.1Q, QinQ Select the means ofprocessing the accessedpackets.Null: The port transparentlytransmits the accessedpackets.802.1Q: The port identifiesthe 802.1Q standard packets.QinQ: The port identifies theQinQ standard packets.The Encapsulation Type isalways 802.1Q when you setPort Mode to Layer 3.Click C.89 EncapsulationType for more information.

Working Mode Auto-Negotiation, 10MHalf-Duplex, 10M Full-Duplex, 100M Half-Duplex,100M Full-Duplex, 1000MHalf-Duplex, 1000M Full-Duplex, 10G Full-DuplexLAN, 10G Full-DuplexWAN

Select the working mode ofthe Ethernet port. The auto-negotiation mode isrecommended, because it canautomatically find out thebest working mode tocombine a port and itsinterconnected port and thusis convenient formaintenance.Be careful to configure thesame working mode for theport and its interconnectedport. Otherwise, service willfail.Click C.93 Working Modefor more information.

Max Frame Length (byte) OptiX PTN 3900: 46 to 9000Default: 1620

The maximum frame lengthis also the maximumtransport unit (MTU).Click C.167 Max FrameLength(byte)-Ethernetinterface for moreinformation.



4-39

Table 4-14 Descriptions of the parameters for Ethernet interface Layer 2 Attributes




QinQ Type Domain 0x0600 to 0xFFFF Set the QinQ type domain.This parameter is availableonly when you setEncapsulation Type inGeneral Attributes toQinQ.

Tag Tag Aware, Access, Hybrid The tag indicates whichpackets can be processed.Tag Aware: The porttransparently transmits thedata packet with a VLAN ID(tag). If a data packet does nothave a VLAN ID (untag), theport discards this data packet.In this case, the DefaultVLAN ID and VLANPriority are meaningless.Access: The port adds thedefault VLAN ID to the datapacket without any VLAN ID(untag). If the data packet hasa VLAN ID (tag), the portdiscards this data packet.Hybrid: The port adds thedefault VLAN ID to the datapacket without any VLAN ID(untag). If the data packet hasa VLAN ID (tag), the porttransparently transmits thedata packet.This parameter is unavailablewhen you set EncapsulationType in General Attributesto QinQ.


Configuration Guide


Issue 06 (2009-06-01)


Default VLAN ID 1 to 4094 Set the default VLAN ID ofpackets that passes throughthe port.When you set Tag toAccess, packets that have thesame VLAN ID as the defaultVLAN ID are discarded, andpackets without a VLAN areadded with the default VLANID and then pass the port.When you set Tag toHybrid, tagged packets areallowed to pass, and packetswithout a tag are added withthe default VLAN ID andthen pass the port.

VLAN Priority 0 to 7 Set the QoS level. When thenetwork is busy, data packetsof higher VLAN priority areprocessed first and those oflower VLAN priority may bediscarded. 0 indicates thelowest priority and 7 thehighest.This parameter is availableonly when you set Tag toAccess or Hybrid.

Table 4-15 Descriptions of the parameters for Ethernet interface Layer 3 attributes



Displays the port name.

Enable Tunnel Enabled, Disabled After the Tunnel is enabled,the port can identify andprocess the MPLS label, andthus supports the dynamicsignaling and route.Click C.40 Enable Tunnelfor more information.



4-41



For example: 102400 Sets the maximumbandwidth used by thetunnel.The maximum reservedbandwidth should not exceedthe physical bandwidth of thebearer port.


Admin Group 0 to 4294967295 Sets the admin group.The admin group can specifythe link attributes. After theaffinity attributes of adynamic tunnel isconfigured, when thedynamic tunnel selects links,the dynamic tunnel comparesits affinity attributes with theadmin attributes of links anddetermines which links to beavoided.

Specify IP Manually, Unspecified Selects the means of settingthe IP address for the port.Click C.17 Specify IP formore information.

IP Address For example: 192.168.0.1 Sets the IP address for theport.This parameter can be setonly when Specify IP is setto Manually.

IP Mask For example: 255.255.255.0 Sets the subnet mask of theport.This parameter can be setonly when Specify IP is setto Manually.


Configuration Guide


Issue 06 (2009-06-01)


Board for Unnumbered IP - The parameter is notsupported.

Port for Unnumbered IP - The parameter is notsupported.

Table 4-16 Descriptions of the parameters for Ethernet interface Advanced Attributes



Displays the port name.

Port Physical parameters For example: Port Enable:Enabled, Working Mode:Auto-Negotiation, Non-Autonegotiation FlowControl Mode: Disabled,MAC Loopback: Non-Loopback, PHY Loopback:Non-Loopback

Displays physical parametersof the port.

MAC Loopback Non-Loopback, Inloop,Outloop

Sets the loopback state of theMAC layer.

PHY Loopback Non-Loopback, Inloop,Outloop

Sets the loopback state of thePHY layer.Click C.27 PHY Loopbackfor more information.

MAC Address For example:00-5A-3D-03-4C-1B

Displays the MAC address ofthe port.

Transmitting Rate(kbit/s) For example: 1024 Displays the rate at which thedata packets are transmitted.

Receiving Rate(kbit/s) For example: 1024 Displays the rate at which thedata packets are received.

Loopback Check Enabled, Disabled Sets the loop detection.When this function isenabled, the equipmentautomatically checkswhether a loop is generatedon the link. If a loop isgenerated, the relevant alarmis reported.



4-43


Loopback Port Shutdown Enabled, Disabled Sets the automatic shutdownof the port.When Loopback Check isset to Enabled and LoopbackPort Shutdown is set toEnabled, the equipmentautomatically checkswhether a loop is generatedon the link. If a loop isgenerated, the port isautomatically shut down torelease the loop.

Egress PIR Bandwidth(kbit/s)

For example: 10000 Sets the egress PIRbandwidth.Only OptiX PTN 912supports the egress PIRbandwidth.

Table 4-17 Descriptions of the parameters for Ethernet interface Flow Control




Non-Autonegotiation FlowControl Mode

Disabled, Enable SymmetricFlow Control, Send Only,Receive Only

If the working mode of theport is non-autosensing, youcan only choose the non-autonegotiation flow controlmode.Enable Symmetric FlowControl: The port can bothtransmit and receive PAUSEframes.Send Only: The port canonly send PAUSE frames.Receive Only: The port canonly receive PAUSE frames.Click C.88 Non-Autonegotiation FlowControl Mode (EthernetPort) for more information.


Configuration Guide


Issue 06 (2009-06-01)


Auto-Negotiation FlowControl Mode

Disabled, EnableDissymmetric Flow Control,Enable Symmetric FlowControl, Enable Symmetric/Dissymmetric Flow Control

If the working mode of theport is auto-negotiation, youcan only choose the auto-negotiation flow controlmode.NOTE

Enable Dissymmetric FlowControl: The port sendPAUSE frames only, notreceive.Enable Symmetric FlowControl: The port send andreceive PAUSE frames.Enable Symmetric/Dissymmetric FlowControl: The port determinea flow control mode(symmetric ordissymmetric).Click C.157 Auto-Negotiation Flow ControlMode (Ethernet Port) formore information.

Table 4-18 Descriptions of the parameters for Serial interface General Attributes


Port Example: 5-MP1-1-CD1-1(Serial-1)

Displays a port name.

Port Number Example: 1 Sets the port number.

Name Example: Site A Specifies a port name.Click C.112 Name for moreinformation.

Level VC12, 64K Timeslot Specifies the level of a serialinterface.l VC12: The VC12s in a

channelized STM-1 framecan be bound to a serialinterface.

l 64 kbit/s timeslot: Thetimeslots of an E1interface can be bound to aserial interface.



4-45


Used Board Example: 5-MP1 Selects the board carrying theserial interface.

Used Port Example: 5-MP1-1-CD1-1(Port-1)

Selects the physical portcarrying the serial interface.Click C.128 Used Port formore information.

High Channel VC4-1 Displays a higher orderchannel.

Used Timeslot 1-63 Sets the timeslots used by theserial interface. You cannotset the used timeslot for an E1interface.Click C.151 Used Timeslotfor more information.

64K Timeslot 1-31 Sets the 64 kbit/s timeslot ona serial interface. You cannotset the used timeslot for anSTM-1 interface.

Port Mode Layer 2, Layer 3 Sets the port mode. If you setPort Mode to Layer 2, youcan set Encapsulation Typeto ATM. If you set PortMode to Layer 3, you can setEncapsulation Type toPPP or Null.

Encapsulation Type ATM, Null, PPP Selects the encapsulationtype.Select PPP to add the serialinterface in the MP group.Click C.89 EncapsulationType for more information.

Max Data Packet Size (byte) 46-1900Default: 1620

Sets the maximum datapacket length.

Table 4-19 Descriptions of the parameters for Serial interface Layer 3 Attributes


Port Example: 5-MP1-1-CD1-1(Serial-1)



Configuration Guide


Issue 06 (2009-06-01)


Enable Tunnel Disabled, EnabledDefault: Disabled

After the Tunnel is enabled,the port can identify andprocess the MPLS label, andthus supports the dynamicsignaling and route.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.Click C.40 Enable Tunnelfor more information.


Example: 2048Default: 2048


TE Measurement 0 to 16777215 Sets the TE measurement.You can intervene in theroute selection by adjustingthe TE measurement of thelink. The smaller the value ofthe TE measurement, thehigher the priority of the link.Thus, the traffic congestionof the shortest path thatoccurs in the traditional routeselection can be avoided.This parameter is availableonly when you set theEncapsulation Type toPPPin the GeneralAttributes.



4-47


Admin Group 0 to 4294967295 Sets the admin group.The admin group can specifythe link attributes. After theaffinity attributes of adynamic tunnel isconfigured, when thedynamic tunnel selects links,the dynamic tunnel comparesits affinity attributes with theadmin attributes of links anddetermines which links to beavoided.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.


Select the means of settingthe IP address for the port.This parameter can be setonly when EncapsulationType in General Attributesis set to PPP.

IP Address Example: 192.168.0.1 Set the IP address for the port.This parameter can be setonly when Specify IP is setto Manually.

IP Mask Example: 255.255.255.0 Set the subnet mask of theport.This parameter can be setonly when Specify IP is setto Manually.

Board for Unnumbered IP Example: 3-ETFC Select the board for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Unnumbered InterfaceIP.

Port for Unnumbered IP Example: 3-ETFC-3(Port-3) Display the port for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Unnumbered InterfaceIP.


Configuration Guide


Issue 06 (2009-06-01)

Table 4-20 Descriptions of the parameters for Ethernet virtual interface General Attributes


Port Number 1 to 2047 Enters a port number.

Name For example: Port1 Enters the self-defined portname.

Port Mode Layer 2, Layer 3 When Port Type is set toEOA Virtual Interface, youcan select the layer at whichthe port works.When Port Type is set toVLAN Sub Interface, PortMode can only be set toLayer 3.

Port Type EOA Virtual Interface,VLAN Sub Interface,

Selects the type of the port.EOA Virtual Interface: Theport can carry the IP tunneland GRE tunnel.VLAN Sub Interface: Theport can carry the MPLSTunnel, IP tunnel and GREtunnel.

Associated Board For example: Slot-BoardName

Selects the board where theEthernet virtual interface islocated.

Associated Port For example: Slot-BoardName-Port(Port No.)

Selects the port where theEthernet virtual interface islocated.

VPI 0 to 4095 Sets the VPI used by theEthernet virtual interface.This parameter is valid onlyfor the EOA virtual interface.

VCI 0 to 65535 Sets the VCI used by theEthernet virtual interface.This parameter is valid onlyfor the EOA virtual interface.

AAL5 Encapsulation Type LLC BRIDGE, LLCROUTE, VCMUXBRIDGE, VCMUX ROUTE

Selects the AAL5encapsulation type.This parameter is valid onlyfor the EOA virtual interface.

VLAN 1 to 4094 Sets the VLAN used by theEthernet virtual interface.This parameter is valid onlyfor the VLAN sub-interface.



4-49



IP Address For example: 10.70.70.11 Set the IP address of the port.When Port Mode in GeneralAttributes is set to Layer 3,you can set this parameter.

IP Mask For example: 255.255.255.0 Set the IP address mask of theport.When Port Mode in GeneralAttributes is set to Layer 3,you can set this parameter.

MAC Address For example: 00-E0-4C-76-20-68

Displays the MAC address ofthe port.

Table 4-21 Descriptions of the parameters for Ethernet virtual interface Layer 3 Attributes


Port Number For example: 1 Display the port number.

Enable Tunnel Enabled, Disabled After the tunnel is enabled,the port can identify andprocess the MPLS label, andthus supports the dynamicsignaling and route. In thiscase, the port can also carrythe IP tunnels and GREtunnels.When Port Mode in GeneralAttributes is set to Layer 3,you can set this parameter.Click C.40 Enable Tunnelfor more information.


IP Address For example: 10.70.70.11 Set the IP address of the port.When Port Mode in GeneralAttributes is set to Layer 3,you can set this parameter.


Configuration Guide


Issue 06 (2009-06-01)


IP Mask For example: 255.255.255.0 Set the IP address mask of theport.When Port Mode in GeneralAttributes is set to Layer 3,you can set this parameter.

Table 4-22 Descriptions of the parameters for Link Aggregation Group Management


LAG No. Example: 1 Set the number of the LAG.You can also select theautomatic allocation.

LAG Name Example: LAG_1 Set the name of the LAG.

LAG Type Static, Manual Manual: The user manuallycreates a LAG, adds ordeletes member ports, anddisables the LACP protocol.Static: The user manuallycreates a LAG, adds ordeletes member ports, andenables the LACP protocol.Click C.102 LAG Type formore information.

Revertive Mode Revertive, Non-Revertive Select the revertive mode.Click C.95 Revertive Modefor more information.



4-51


Load Sharing Non-Sharing, Sharing Sharing: All member links inthe LAG bear traffic, andshare the load. The load isshared to increase thebandwidth of the links. Whenthe member links change orsome member links fail, thesystem automatically re-allocate the traffic.Non-Sharing: Only onemember link in the LAGbears traffic. The othermember link is in the standbystate. In this way, amechanism similar to hotbackup is available. Whenthe active link in the LAGfail, the system automaticallyselects the other link forprotection against the linkfailure. Hence, theinterruption of the upper-layer protocols is avoided.Click C.92 Load Sharing formore information.

Load Sharing HashAlgorithm

Automatic, Source MAC,Destination MAC, Sourceand Destination MAC,Source IP, Destination IP,Source and Destination IP,Source Port Number,Destination Port Number,Source and Destination PortNumbers, MPLS Label

Set Load Sharing HashAlgorithm properly toensure that the service flowsin compliance with thealgorithm are transportedover the same link. In thisway, the received datapackets are in the correctframe sequence.This parameter can be setonly when Load Sharing isset to Sharing.Click C.91 Load SharingHash Algorithm for moreinformation.


Configuration Guide


Issue 06 (2009-06-01)


System Priority 0 to 65535 The system priority andsystem MAC addressindicate the system ID, whichis used for negotiation withthe opposite equipment. Theequipment with a highersystem priority has thepriority for selection.Click C.136 System Priority(LAG) for more information.

Main Port Example: Slot-Board Name-Port(Port No.)

Select the main port of theLAG.Click C.155 Main Port formore information.

Main Port Status In Service, Out of Service Display the working state ofthe main port.Click C.156 Main PortStatus for more information.

Slave Port Example: Slot-Board Name-Port(Port No.)

Select the salve port of theLAG.

Slave Port Status In Service, Out of Service Display the working state ofthe slave port.

Table 4-23 Descriptions of the parameters for MP Group General Attributes


MP Group Number For example: 1 Set the MP group number.

Name For example: MP_1 Set the name of the MP.

Link Status Up, Down Display the link status.

Min Activated Link Count 1 to 16 Configure the minimumactivated link count for eachMP group. The MP group canbe activated only when thecount of activated links in theMP group reaches theminimum activated linkcount.Click C.168 Min. ActivatedLink Count for moreinformation.



4-53


Enable Differential Delay Enabled, Disabled Enable or disable detection ofthe differential delay.Click C.108 EnableDifferential Delay for moreinformation.

Max Differential Delay (100us)

25 to 500 Set the maximum delayvariation between links in anMP group.This parameter can be setonly when EnableDifferential Delay is set toEnabled.Click C.163 Max.Differential Delay (100 us)for more information.

Enable Tunnel Disabled, EnabledDefault: Disabled

After the Tunnel is enabled,the port can identify andprocess the MPLS label, andthus supports the dynamicsignaling and route.Click C.40 Enable Tunnelfor more information.


For example: 4096 Set the maximum bandwidthused by the tunnel.The maximum reservedbandwidth should not exceedthe physical bandwidth of thebearer port.



Configuration Guide


Issue 06 (2009-06-01)


Admin Group 0 to 4294967295 Sets the admin group.The admin group can specifythe link attributes. After theaffinity attributes of adynamic tunnel isconfigured, when thedynamic tunnel selects links,the dynamic tunnel comparesits affinity attributes with theadmin attributes of links anddetermines which links to beavoided.

IP Address NegotiationResult

For example: 192.168.0.1 Display the negotiated IPaddress.Click C.15 IP AddressNegotiation Result for moreinformation.

IP Mask Negotiation Result For example: 255.255.255.0 Display the negotiated IPmask.Click C.16 IP MaskNegotiation Result for moreinformation.

Member Interface For example: Slot-BoardName-Port(Port No.)

Select the members in the MPgroup.Click C.56 MemberInterface for moreinformation.

PPP Link Status Up, Down Display the link status.

Differential Delay CheckStatus

Unknown, Valid, Invalid Display the status ofchecking the differentialdelay.NOTE


Select the means of settingthe IP address for the port.

IP Address For example: 192.168.0.1 Set the IP address for the port.This parameter can be setonly when Specify IP is setto Manually.



4-55


IP Mask For example: 255.255.255.0 Set the subnet mask of theport.This parameter can be setonly when Specify IP is setto Manually.

Board for Unnumbered IP For example: Slot-BoardName

Select the board for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Manually.

Port for Unnumbered IP For example: Slot-BoardName-Port(Port No.)

Select the port for theunnumbered IP address.This parameter can be setonly when Specify IP is setto Manually.

Fragmentation Size(byte) 64, 128, 256, 512 Select the fragmentation size.


Configuration Guide


Issue 06 (2009-06-01)

5 Configuring the Control Plane

About This Chapter

The control plane, responsible for the call control and connection control, consists of a group ofcommunication entities. The control plane creates, releases, monitors and maintains theconnection through signaling, and it automatically recovers the connection upon failure.

5.1 Basic ConceptsThis section describes the related protocols of the control plane and application scenarios ofthese protocols when the control plane is configured.

5.2 Configuring the IGP-ISIS ProtocolIf the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGP-ISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, eachNE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with theRSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocolconfiguration includes the configuration of node and port attributes, query and configuration ofroute importing information, and query of the TE link information.

5.3 Configuring the MPLS-LDP ProtocolIf the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLS-LDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtainthe information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service,the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of theMPLS-LDP protocol. On the T2000, the MPLS-LDP peer entities can be created and the MPLS-LDP protocol can be configured.

5.4 Configuring the MPLS-RSVP ProtocolThe MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnellabel. On the T2000, the parameters of the MPLS-RSVP protocol can be queried. This protocoldoes not need special configuration, and thus the user can configure each parameter accordingto requirements.

5.5 Configuring Static RoutesThe static routes are selected according to the preset route options in the network. On theT2000, the static routes can be queried and created.

5.6 Configuring the Address Parse

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 5 Configuring the Control Plane


5-1

On the T2000, the IP address and MAC address of the ARP table items can be created andqueried.

5.7 Parameter DescriptionThis section describes the parameters related to the control plane configuration.

5 Configuring the Control PlaneOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

5.1 Basic ConceptsThis section describes the related protocols of the control plane and application scenarios ofthese protocols when the control plane is configured.

5.1.1 IGP-ISIS ProtocolThe intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,belongs to the internal gateway protocol and is applicable to the internal of the autonomoussystem. The equipment uses the IS-IS routing protocol, which is used with the label distributionprotocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.

5.1.2 MPLS-LDP ProtocolThe multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the labelswitched routers (LSR) to distribute labels in the network.

5.1.3 MPLS-RSVP ProtocolMulti-protocol label switch resource reservation protocol (MPLS-RSVP) supports thedistribution of MPLS labels. In addition, when transmitting the label binding message, it carriesthe resource reservation information, used as a signaling protocol to create, delete or modify thetunnel in the MPLS network.

5.1.4 ARP ProtocolAddress resolution protocol (ARP) is used to map the IP address (alias: logical address) at thenetwork layer into the MAC address (alias: physical address) at the data link layer.

5.1.1 IGP-ISIS ProtocolThe intermediate system to intermediate system (IS-IS) routing protocol, a link state protocol,belongs to the internal gateway protocol and is applicable to the internal of the autonomoussystem. The equipment uses the IS-IS routing protocol, which is used with the label distributionprotocols RSVP-TE and LDP to realize the dynamic creation of the MPLS LSP.

The IS-IS routing protocol used by the equipment creates and synchronizes the link state database(LSD) through routing protocol packets, such as link state PDUs. Based on the LSDB and pathcost, the equipment uses the optimized shortest path first (SPF) algorithm to generate the routingtable, and uses the IS-IS TE of the IS-IS routing protocol to generate the traffic engineeringdatabase (TEDB). The TEDB and routing table are the bases of creating the MPLS LSP. TheTEDB computes the route that the MPLS LSP travels through. The routing table forwards theRSVP-TE and LDP protocol packets to realize label distribution. In this way, the MPLS LSP isdynamically created.

Three features of the IS-IS routing protocol are supported by the equipment, that is, three typesof IS-IS routing protocol packets, optimized SPF algorithm, path cost, and IS-IS trafficengineering (IS-IS TE).

Three Types of IS-IS Routing Protocol Packets

The IS-IS routing protocol belongs to the network player of the OSI protocol model. The IS-ISrouting protocol runs directly at the data link layer. When the IS-IS routing protocol is processed,the decapsulation of the network layer is absent. With the preceding feature, the IS-IS routingprotocol is more applicable to the PTN transport network using the MPLS packet switchingtechnology.



5-3

The IS-IS routing protocol packets use the uniform encapsulation format. The length of thepackets is changeable and the extensibility is strong. The complexity of the protocol is decreased,because the types of the protocol packets are few. Thus, the running is more reliable and efficient.

The equipment realizes the following three types of IS-IS routing protocol packets:

l Hello packets

Hello packets are used to construct and maintain neighbor relation between network nodes.Hence, Hello packets are also called IS-to-IS hello (IIH) PDUs.

l Link state PDUs

Link state PDUs are used to exchange the link state information. In a network running theIS-IS routing protocol, each network node generates a link state PDU, which contains allthe link state information of this network node. To generate its own LSDB, each networknode collects all the link state PDUs within the local domain and between domains.

l SNP packets

Sequence number PDUs (SNP) describe the link state PDUs in all or part of the LSDB.The SNP is used to synchronize and maintain the LSDB of each network node in thePTN network.

Optimized SPF Algorithm

The IS-IS routing protocol realized by the equipment uses the optimized SPF algorithm for routecomputation and update. When the topology is changed, the resources (network bandwidth,processing capability of network nodes, and memory) for updating the new route are few, andthus the convergence rate of the entire network is improved.

Path Cost

The equipment supports the manual setting of path cost, and controls the route that the MPLSLSP travels through when it is dynamically created.

IS-IS TE

When the MPLS constructs the LSP, the traffic engineering information of all the links in thelocal domain should be known. The IS-IS TE realized by the equipment supports the constructionof the MPLS LSP. The equipment obtains the traffic engineering information (link utilizationand path cost) of all the links in the network through the IS-IS routing protocol. It constructsand synchronizes the TEDB, and uses the constrained shortest path first (CSPF) algorithm usedby the TEDB to compute the route that the MPLS LSP travels through.

5.1.2 MPLS-LDP ProtocolThe multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the labelswitched routers (LSR) to distribute labels in the network.

MPLS-LDP Peer Entities

The MPLS-LDP peer entities refer to two NEs, where LDP session exists, use the MPLS-LDPto exchange labels mapping relation.


Configuration Guide


Issue 06 (2009-06-01)

MPLS-LDP SessionThe MPLS-LDP session is used to exchange label mapping and releasing messages betweendifferent equipment. The MPLS-LDP session consists the following two types:l Local MPLS-LDP session, in which the two NEs used to set up the session is directly

connected.l Remote MPLS-LDP session, in which the two NEs used to set up the session is not directly

connected.

MPLS-LDP Message TypesThe MPLS-LDP protocol mainly uses the following four types of messages:l Discovery message, which is used to notify and maintain the existence of the equipment

in the network.l Session message, which is used to set up, maintain and end the session between MPLS-

LDP peer entities.l Advertisement message, which is used to create, change and delete the label mapping.

l Notification message, which is used to provide the constructive message and errornotification.

Working Mode of the MPLS-LDPThe label distribution process has two modes. The main difference between the two modes iswhether the label mapping is released in the upstream request mode or downstream unsoliciteddistribution mode. The two label releasing modes are as follows:l Upstream request mode, in which the equipment in the upstream sends the label request

message to the equipment in the downstream. The equipment in the downstream returnsthe bound labels to the equipment in the upstream through label mapping message. Whenthe equipment in the downstream returns the label mapping message is determined by thelabel control mode used by the equipment.– If the ordered mode is used, only when the equipment receives the label mapping

message returned by the equipment in the downstream, it sends the label mappinginformation to the upstream.

– If the independent mode is used, the equipment immediately sends the label mappingmessage to the upstream, regardless of whether it receives the label mapping messagereturned by the equipment in the downstream.

l Downstream unsolicited distribution mode, in which the equipment in the downstream takethe initiative to release the label mapping message to the equipment in the upstream afterthe MPLS-LDP session is successfully set up. The equipment in the upstream saves thelabel mapping information, and manages the received label mapping information accordingto the route table information.

Basic Operation of the MPLS-LDPIn sequence, the MPLS-LDP operation consists of the following four phases:l Development phase: In this phase, the equipment that expects to set up a session

periodically sends Hello message to the adjacent equipment to notify the adjacent node ofthe local peer relation. In this process, the equipment can automatically discover its LDPpeer entity without manual configuration.



5-5

l Session set-up and maintenance: After the peer relation is set up, the equipment begins toset up the session.

l PW set-up and maintenance: The set-up of the PW is based on the MPLS-LDP protocol.

l Session cancellation: A life state timer is set up for each session. When each LDP PDU isreceived, this timer is refreshed. If the timer times out before a new LDP PDU is received,the equipment takes that the session is interrupted and the peer relation is invalid. Theequipment shuts down the corresponding connection at the transmission layer to end thesession.

5.1.3 MPLS-RSVP ProtocolMulti-protocol label switch resource reservation protocol (MPLS-RSVP) supports thedistribution of MPLS labels. In addition, when transmitting the label binding message, it carriesthe resource reservation information, used as a signaling protocol to create, delete or modify thetunnel in the MPLS network.

Basic Concepts of the MPLS-RSVP

The MPLS-RSVP is a notification mechanism of the resource reservation in the network, whichrealizes the bandwidth reservation on the control plane. As a label distribution protocol, it isused to set up the LSP in the MPLS network.

For details of the MPLS-RSVP extension, refer to RFC3209.

Resource Reservation Style

The LSP set up by using the MPLS-RSVP is of a certain reservation style. When the RSVPsession is set up, the receive end determines which reservation style to be used, and thusdetermines which LSP to be used.l Fixed-filter (FF) style: When this style is used, resources are reserved for each transmit end

individually. Thus, transmit ends in the same session cannot share the resources with eachother.

l Shared-explicit (SE) style: When this style is used, resources are reserved for all transmitends in the same session. Thus, transmit ends can share the resources.

MPLS-RSVP Message Type

The MPLS-RSVP uses the following message types:l Path message: The transmit end sends this type of message in the transmission direction of

data packets. In addition, the path state is saved on all the nodes along the trail.l Resv message: The receive end sends this type of message in the reverse transmission

direction of data packets. In addition, the resource reservation is requested, and thereservation state is created and maintained on all the nodes along the trail.

Tunnel Created by Using the MPLS-RSVP

As shown in Figure 5-1, the creation process of the LSP tunnel by using the MPLS-RSVP islisted as follows:l The ingress equipment generates the Path message, which is transmitted in the direction of

the egress equipment.


Configuration Guide


Issue 06 (2009-06-01)

l After the egress equipment receives the Path message, the Resv message is generated andthen is returned to the ingress equipment. In addition, the Resv message reserves resourceson the equipment along the trail.

l When the ingress equipment receives the Resv message, the LSP is successfully created.The LSP created by using the MPLS-RSVP has the resource reservation function. Theequipment along the trail can distribute some resources to the LSP to ensure the serviceson the LSP.

Figure 5-1 LSP tunnel created by using the MPLS-RSVP

Path

ResvSender Receiver

Ingress EgressPath

Resv

Parameters of the MPLS-RSVP State Timer

The parameters of the MPLS-RSVP state timer include the refreshing period of the Path or Resvmessage, multiple of the path state block (PSB) timeout and reservation state block (RSB)timeout.

In the case of the creation of the LSP, the transmit end adds the LABEL_REQUEST object tothe Path message. When the receive end receives the Path message with the LABEL_REQUESTobject, it distributes one label and adds the label to the LABEL object of the Resv message.

The LABEL_REQUEST object is saved in the PSB of the upstream node, and the LABEL objectis saved in the RSB of the downstream node. When the message indicating that the number ofmessage refreshing times exceeds the multiple of the PSB or RSB timeout is not continuouslyreceived, the corresponding state in the PSB or RSB is deleted.

Assume that there is a resource reservation request, which does not pass the access control onsome nodes. In some cases, this request is not supposed to be immediately deleted, but it cannotstop other requests from using its reserved resources. In this case, the node enters the blockadestate, and the blockade state block (BSB) is generated on the node of the downstream. When themessage indicating that the number of the message refreshing times exceeds the multiple of thePSB or RSB timeout is continuously received, the corresponding state in the BSB is deleted.

5.1.4 ARP ProtocolAddress resolution protocol (ARP) is used to map the IP address (alias: logical address) at thenetwork layer into the MAC address (alias: physical address) at the data link layer.

ARP Frame Format

Figure 5-2 shows the ARP frame format.



5-7

Figure 5-2 ARP frame format

Destination MAC

address

Source MAC

address

Frame type ARP request/answer

MAC address

type

IP protocol

type

IP address length

OPMAC address at the transmit

end

MAC address length

IP address at the

transmit end

Destination MAC

address

Destination IP address

2 2 1 1 2 6 4 6 4

6 4 2

l Destination MAC address: six bytes. When an ARP request is sent, the destination MACaddress is the broadcast MAC address, that is, 0xFF.FF.FF.FF.FF.FF.

l Source MAC address: six bytes.

l Frame type: two bytes. The value of this field is 0x0806.

l MAC address type: two bytes. It defines the address type in the network that runs the ARP.Value 1 indicates the Ethernet address.

l IP protocol type: two bytes. It defines the protocol type. Value 0x0800 indicates the IPaddress.

l MAC address length: one byte. It defines the length of the physical address expressed inbytes. In the case of an ARP request or answer, the value of this field is 6.

l IP address length: one byte. It defines the length of the logical address expressed in bytes.In the case of an ARP request or answer, the value of this field is 4.

l OP: two bytes. It defines the ARP packet type. Value 1 indicates the ARP request and value2 indicates the ARP answer.

l MAC address at the transmit end: six bytes. It defines the MAC address of the transmitstation.

l IP address at the transmit end: four bytes. It defines the IP address of the transmit station.

l Destination MAC address: six bytes. It defines the destination MAC address. In the caseof an ARP request packet, the value of this field is all-zero.

l Destination IP address: four bytes. It defines the destination IP address.

Static ARP

Static ARP means that there is a fixed mapping relation between the IP address and the MACaddress, and thus you cannot adjust this relation dynamically on the equipment or the router.For the static ARP, you need to manually create a table that is stored on each equipment in thenetwork.

The static ARP table is used in the following scenarios:

l When a packet is transmitted to a destination address beyond the local network segment,this packet is bound with a specific network interface card (NIC) in order to be forwardedthrough this gateway.


Configuration Guide


Issue 06 (2009-06-01)

l To filter out certain illegal IP addresses, you can bind these addresses with an MAC addressthat does not exist to realize the filtering.

Dynamic ARPDynamic ARP means that the mapping relation between the IP address and the MAC address isconstantly refreshed and adjusted through address learning.

Changing the NIC or moving the host to another network usually changes the physical address.The corresponding MAC address can be obtained in a timely manner based on the dynamic ARPaddress resolution.

ARP PrincipleWhen a host or other network equipment needs to transmit data to another host or equipment,IP data packets must be encapsulated into frames to be transmitted in the physical network.During the transmission, the destination MAC address must be available.

When the equipment on the transmit station wants to obtain the MAC address of anotherequipment in the network, the transmit station searches for the MAC address corresponding tothe IP address in the ARP table. If the ARP table is available, the transmit station obtains theMAC address from the ARP table directly. Otherwise, the ARP function is enabled. As shownin Figure 5-3, host A sends data to host B to obtain the MAC address of host B.

To obtain the MAC address of the station whose IP address is 10.1.1.2, host A broadcasts anARP request packet in the network. The packet carries the information about the MAC addressand IP address of the transmit station, and the IP address of the destination station. All theequipment in the network receives and handles the ARP request packet. Only host B on thedestination station, however, can identify the IP address and return an ARP answer packet.According to the MAC address of the transmit station in the request packet, host B sends theARP answer packet to the request station in unicast mode. After receiving the ARP answerpacket, host A obtains the MAC address of host B.

Figure 5-3 ARP address resolution

ARP request packet

ARP answer packet

Host A Host B

Host C Host D

IP: 10.1.1.1MAC: A-A-A MAC: A-A-B

IP: 10.1.1.2

IP: 10.1.1.3MAC:A-A-C

IP: 10.1.1.4MAC:A-A-D

Transmit station: A-A-A;10.1.1.1Destination station: 10.1.1.2

Transmit station: A-A-B;10.1.1.2Destination station: A-A-A;10.1.1.1



5-9

5.2 Configuring the IGP-ISIS ProtocolIf the dynamic MPLS tunnel is required, the IGP-ISIS protocol must be configured. The IGP-ISIS protocol is used to discover the network topology. Through the IGP-ISIS protocol, eachNE can obtain the information of the adjacent NE. When the IGP-ISIS protocol is used with theRSVP-TE protocol, the creation of the MPLS tunnel is complete. The IGP-ISIS protocolconfiguration includes the configuration of node and port attributes, query and configuration ofroute importing information, and query of the TE link information.

5.2.1 Setting Node AttributesOn the T2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried andset.

5.2.2 Setting Port AttributesOn the T2000, the parameters of ports managed by the IGP-ISIS protocol can be queried andset.

5.2.3 Configuring Parameters of Route ImportingOn the T2000, the parameters of route importing can be queried and set.

5.2.4 Querying the Link TE InformationOn the T2000, the parameters of the link TE can be queried.

5.2.1 Setting Node AttributesOn the T2000, the parameters of nodes managed by the IGP-ISIS protocol can be queried andset.


Setting the Route ColorSet Route Color to divide a large autonomous domain into multiple logical sub-domains. Thesub-domains with different Route Color values cannot interconnect through the IS-IS routingprotocol. In this manner, the sub-domains are isolated for easy link management andmaintenance.

The network shown in Figure 5-4 is considered as an example. All the NEs are within the sameautonomous domain. The autonomous domain is divided into three logical domains by settingto different colors. Within logical domains 1, 2, and 3, services are available between stations.Services are also available between domain 1 and domain 2, and between domain 1 and domain3.

In domain 1, services are available between NE 1 and NE2, and between NE2 and NE3. RouteColor of NE1 is set to 1, 2, and 3, and Route Color of other NEs in domain 1 is set to 1. Indomain 2, services are available between NE2 and NE1. Route Color of NE2 is set to 1 and 2,and Route Color of other NEs in domain 2 is 3 set to 1. In domain 3, services are availablebetween NE1 and NE3. Route Color of NE3 is set to 1 and 3, and Route Color of other NEsin domain 3 is set to 3. In this manner, the IS-IS protocol packets are transmitted in each logicaldomain, between NE1 and NE2, and between NE1 and NE3.


Configuration Guide


Issue 06 (2009-06-01)

Figure 5-4 Example of setting the route color

Domain 1Domain 2

Domain 3

Route color: 1, 2, and 3

Route color: 1 and 3

Route color: 1 and 2

NE1 NE2

NE3

Route color: 1

NE4

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration> IGP-ISIS Configuration from the Function Tree.

Step 2 Click the Node Configuration tab.

NOTE

Currently, the equipment supports only one IS-IS instance.

Step 3 Optional: Select the ISIS Instance, you can modify the parameter of nodes managed by the IGP-ISIS protocol.

NOTE

Set Route Color to divide a large autonomous domain into multiple logical sub-domains. The sub-domainswith different Route Color values cannot interconnect through the IS-IS routing protocol. In this manner,the sub-domains are isolated for easy link management and maintenance.

Step 4 Click Apply to complete the setting of parameters.

Step 5 Click Query to query the parameters of a node.

----End

5.2.2 Setting Port AttributesOn the T2000, the parameters of ports managed by the IGP-ISIS protocol can be queried andset.




5-11

l Enable Tunnel of the layer 3 attributes must be set to Enabled.

Procedure


Step 2 Click the Port Configuration tab.

Step 3 Optional: Select the port, you can modify the parameter of ports managed by the IGP-ISISprotocol.

Step 4 Click Apply to complete the setting of port parameters.

Step 5 Click Query to query the parameters of each port.

----End

5.2.3 Configuring Parameters of Route ImportingOn the T2000, the parameters of route importing can be queried and set.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Control PlaneConfiguration > IGP-ISIS Configuration from the Function Tree.

Step 2 Click the Route Import tab.

Step 3 Click Import to display the Route Import dialog box, and then set parameters of the importedroutes.For details on the parameters for route import of IGP-ISIS protocol, see Table 5-1.

Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK.

Step 5 Click Query to query the parameters of the imported routes.


Configuration Guide


Issue 06 (2009-06-01)

CAUTIONWhen modifying the parameters of the imported routes, click Delete to delete the originalsettings, and then click Import to re-set. This operation, however, interrupts the services. Thus,exercise caution when performing this operation.

----End

5.2.4 Querying the Link TE InformationOn the T2000, the parameters of the link TE can be queried.


Procedure


Step 2 Click the Link TE Information tab.

Step 3 Click Query to query the information on the parameters of the link TE.For details on theparameters for link TE information of IGP-ISIS protocol, see Table 5-1.

----End

5.3 Configuring the MPLS-LDP ProtocolIf the dynamic PW need be configured, the MPLS-LDP protocol must be configured. The MPLS-LDP is used to create the dynamic PW and to distribute the PW label. The NE can only obtainthe information of the adjacent NE through the IGP-ISIS protocol. In the case of a single service,the NEs at the two ends can known each other by configuring the MPLS-LDP peer entity of theMPLS-LDP protocol. On the T2000, the MPLS-LDP peer entities can be created and the MPLS-LDP protocol can be configured.

5.3.1 Creating MPLS-LDP Peer EntitiesOn the T2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is availablebetween NEs, and the NEs can obtain the label mapping messages of each other.

5.3.2 Configuring the MPLS-LDP ProtocolOn the T2000, the parameters of the MPLS-LDP protocol can be set.

5.3.1 Creating MPLS-LDP Peer EntitiesOn the T2000, the LDP peer entities can be created. Thus, the MPLS-LDP session is availablebetween NEs, and the NEs can obtain the label mapping messages of each other.




5-13

ContextFor the local session and remote session, you only need to create bidirectional LDP peers betweenthe source equipment and sink equipment. That is, you need to create peers from the source tothe sink, and from the sink to source.

ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration

> MPLS-LDP Configuration from the Function Tree.

Step 2 Click Create to display the Create LDP Peer Entity dialog box.

Step 3 For the Local LSR ID and Opposite LSR ID fields, enter LSR ID of the opposite NE. Then,click Apply. For details on the parameters for MPLS-LDP peer entities, see Table 5-2.

Step 4 After the setting is complete, click OK.

Step 5 Click Query to query the parameters of the MPLS-LDP peer entities.NOTE

Click Delete to delete the MPLS-LDP peer entities.

----End

5.3.2 Configuring the MPLS-LDP ProtocolOn the T2000, the parameters of the MPLS-LDP protocol can be set.


ProcedureStep 1 In the NE Explorer, select an NE and choose Configuration > Control Plane

Configuration > MPLS-LDP Configuration from the Function Tree.

Step 2 Set the parameters of the MPLS-LDP protocol. For details on the parameters for MPLS-LDPprotocol, see Table 5-2.

Step 3 Click Apply to complete the setting of the parameters of the MPLS-LDP protocol.

Step 4 Click Query to query the parameters of the MPLS-LDP protocol.

----End

5.4 Configuring the MPLS-RSVP ProtocolThe MPLS-RSVP protocol is used to create dynamic MPLS tunnel and to distribute the tunnellabel. On the T2000, the parameters of the MPLS-RSVP protocol can be queried. This protocol


Configuration Guide


Issue 06 (2009-06-01)

does not need special configuration, and thus the user can configure each parameter accordingto requirements.


Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Control PlaneConfiguration > MPLS-RSVP Configuration from the Function Tree.

Step 2 Set the parameters of the MPLS-RSVP protocol. For details on the parameters for MPLS-RSVPprotocol, see Table 5-3.

Step 3 Click Apply to complete the setting of the parameters of the MPLS-RSVP protocol.

Step 4 Click Query to query the parameters of the MPLS-RSVP protocol.

----End

5.5 Configuring Static RoutesThe static routes are selected according to the preset route options in the network. On theT2000, the static routes can be queried and created.


l You must complete the setting of the basic attributes and Layer 3 attributes of the port.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration> Static Route Management from the Function Tree.

Step 2 Click Create to create the static routes, and then click Apply. For details on the parameters forstatic routes, see Table 5-4.

NOTE

l When selecting boards or ports, select those that have Layer 3 attributes.

l When the static route is configured, the port IP address and the next hop IP address must be in the samenetwork section.

l When the last digit of the IP address of the destination is not 0, the subnet mask is 255.255.255.255.For example, if the IP address is 193.168.3.2, the mask of the destination node is 255.255.255.255.

l When the last digit of the IP address of the destination is 0, the subnet mask is 255.255.255.0 or255.255.255.255. For example, if the IP address is 193.168.3.0, the mask of the destination node is255.255.255.255 or 255.255.255.0.


Step 4 Click Query to query the parameters of the static routes.



5-15

NOTE

Click Delete to delete the original static routes.

----End

5.6 Configuring the Address ParseOn the T2000, the IP address and MAC address of the ARP table items can be created andqueried.


Procedure

Step 1 In the NE Explorer, click the NE, and choose Configuration > Control PlaneConfiguration > Address Parse from the Function Tree.

Step 2 Click Create and the Add Address Parse dialogue box is displayed.

Step 3 Set the IP address and MAC address of the ARP table items separately, and then click Apply.For details on the parameters for the address parse, see Table 5-5.

WARNINGWhen configuring the MAC address of the ARP table items, the first digit of the address mustbe of an even number.


WARNINGThe configuration of the address resolution refers to the creation of the static ARP table items.To delete the dynamic ARP table items, click Clear. This operation, however, clears all thecontents in the ARP table items, and interrupts the services. Thus, exercise caution whenperforming this operation.

NOTE

Click Delete to delete the contents of the ARP table items.


Configuration Guide


Issue 06 (2009-06-01)

----End

5.7 Parameter DescriptionThis section describes the parameters related to the control plane configuration.

Table 5-1 Descriptions of the parameters for IGP-ISIS Configuration

Tab Parameter Value Description

NodeConfiguration

ISIS Instance ID 1-65535 Specify the ID of an ISISinstance.

Node Level level-1-2 Displays the level for thenode on the route in the IS-ISprotocol network. If the nodelevel is level-1-2, the nodetakes part in the routecomputation of L1 and L2,and also maintains the linkstate databases (LSDBs) ofL1 and L2.

Area ID Character string Set the area ID. The area IDis also the network entity title(NET), which includes theAREA ID and SYSTEM IDof the node.NOTE

The area ID of the node can bea maximum of 26 bytes. Eachbyte is a hexadecimal integerwith the high byte placed firstand the low byte placed last. Onthe T2000, the length of thecharacter string should be aneven number.

LSP Refresh Time(s)

30-65235 Set the time of refreshing thelink state packet (LSP).To keep all LSPs in the areasynchronous, the routerperiodically transmits all thecurrent LSPs. The period oftransmitting LSPs is the LSPrefresh time.



5-17


Maximum LSPValidity (s)

350-65535 Set the maximum periodwhen the LSP is valid.When generating the systemLSP, the LSP router writesthe life time in the LSP.When any other routerreceives the LSP, the lifetime decreases as the timegoes. If the router does notreceive the updated LSPwhen the life time of the LSPdecreases to 0s, the routerdirectly deletes the LSP fromthe LSDB. The life time is themaximum LSP validity.

Management Status Up, Down Displays the managementstatus.

Operating Status Up, Down Displays the operation status.

Route Color 1-16 Set the route color. you canset a maximum of 16 types ofroute color.

PortConfiguration

ISIS Instance ID 1-65535 Display the ID of an ISISinstance.

Port Example: Slot-BoardName-Port(Port No.)

Display the port where theIS-IS parameters need be set.The port includes Ethernetinterface and Ethernet virtualinterface.

Link Level level-1-2 Displays the link level of aport.If the link level is level-1-2,the port can establish both thelevel-1 neighbor relation andlevel-2 neighbor relation.


Configuration Guide


Issue 06 (2009-06-01)


LSPRetransmissionInterval(s)

1-300 Set the interval forretransmission of the LSP.In the case of a point-to-pointlink, if the local router fails toreceive any response in aperiod after transmitting theLSP, the local routerconsiders that the LSP is lostor discarded. To ensure thetransmission reliability, thelocal router transmits theLSP again.

Minimum LSPTransmissionInterval (ms)

1-65535 Set the minimum interval fortransmission of the LSP. Toset the interval is to set theminimum delay between twoconsecutive LSPs.

Link Overhead 1-16777215 Set the link overhead.

AuthenticationMode

OSI, IP Set the authentication mode.Authentication configuredon the port is used in theHello packet to confirm thevalidity and correctness ofneighbors.

AuthenticationType

the Mode of MD5Encryption, NoAuthentication

Select the authenticationtype.

Authentication Key Example: m3%A Set the authentication key.NOTE

The authentication key can beset only when theauthentication type is the Modeof MD5 Encryption.

Hello Send Interval(ms)

100-255000 Set the interval fortransmitting the hellopackets.The IS-IS protocolperiodically transmits thehello packets from the port.The router maintains theneighbor relations bytransmitting and receivingthe hello packets. Theinterval of transmitting thehello packets can be changed.



5-19


Hello Loss Count 2-100 Set the count of the lost hellopackets.The IS-IS protocol maintainsthe neighbor relations withthe neighbor routers bytransmitting and receivingthe hello packets. If the IS-ISprotocol fails to receive thespecified count of theconsecutive hello packets,the IS-IS protocol considersthat the neighbor router fails.The specified count is thehello loss count.

Route Import ISIS Instance ID 1-65535 Display the ID of an ISISinstance.

Source RouteProtocol Type

Static Route Display the type of the routeprotocol that imports routes.

Overhead 1-255 Set the overhead, also theroute weight, for theimported route.

Level level-1-2 Display the import level ofthe imported route.

Link TEInformation

ISIS Instance ID 1-65535 Display the ID of an ISISinstance.

Level level-1-2 Display the link level.

Local Node ID Example:10.70.73.22

Display the LSR ID of thelocal node.

Local Link IP Example:10.70.73.12

Display the IP address of thelocal link.

Opposite Node ID Example:10.70.73.20

Display the LSR ID of theopposite node.

Opposite Link IP Example:10.70.73.10

Display the IP address of theopposite link.

MaximumReservedBandwidth (kbit/s)

Example: 160000 Display the maximumbandwidth that can bereserved.

TE Measurement 0-0xFFFFFFFF Display the TE measurementvalue.

Management GroupAttribute

0-0xFFFFFFFF Display the managementgroup attribute.


Configuration Guide


Issue 06 (2009-06-01)


AvailableBandwidth of LinkPriority 0 (kbit/s)

Example: 16000 Display the availablebandwidth for link priority 0.















Table 5-2 Descriptions of the parameters for MPLS-LDP Configuration

Parameter Value Description

Local LSR ID Example: 1.1.1.3 Display the LSR ID of the local end.

Opposite LSR ID Example: 1.1.1.3 Set the LSR ID of the opposite end.

Local Label Space Node Label Space, PortLabel Space

Display the type of the local labelspace, which indicates the local labelrange.l Node Label Space: The labels are

distributed per NE. On one NE,one label should not repeatanother.

l Port Label Space: The labels aredistributed per port. On one port,one label should not repeatanother.



5-21


Opposite Label Space Node Label Space, PortLabel Space

Display the type of the opposite labelspace.

Status Example: OPENSENT Display the session statusinformation between labeldistribution protocol (LDP) peers.

Role Active Port, Passive Port Display the role that the labelswitching router (LSR) plays insession with the LDP peers.

GR Supporting Capacity Supported, NotSupported

Display whether the local endsupports the LDP graceful restart(GR).In the case of a fault in one router, theLDP GR function still maintains theneighbor relations and sessioninformation between routers, andrecovers the session connection andlabel information.

GR ReconnectionTiming Interval (s)

Example: 3000 Display the timing interval of the GRreconnection timer.

GR Forward StatusRestoration TimingInterval (s)

Example: 3000 Display the restoration timinginterval of the GR forward status.

Negotiated Send Intervalof KeepAlive Packets (s)

Example: 10 Display the negotiated interval fortransmitting the KeepAlive packets.

Hello Send Interval(s) 3-65535 Set the interval for transmitting thehello packets.The LDP entity discovers the LDPpeer by periodically transmitting thehello packets. In this way, the LDPentities establish sessionconnections.

KeepAlive Send Interval(s)

3-65535 Set the interval for transmitting theKeepAlive packets.The established LDP session shouldalso be maintained by the KeepAlivepackets periodically transmitted.


Configuration Guide


Issue 06 (2009-06-01)

Table 5-3 Descriptions of the parameters for MPLS-RSVP Configuration


Port Example: Slot-Board Name-Port(Port No.)

Display the port where theMPLS-RSVP can beconfigured. The port includesEthernet interface andEthernet virtual interface.

Retransmission TimerInterval (ms)

500-3000 Set the timing interval forretrying creating the standbypath.

Retransmission Increment(%)

0-100 Set the increment percentageof retransmission.

Congestion Status TimeoutMultiple

3-255 Set the timeout multiples ofthe RSVP congestion statusof the port.A request for reservingresources may fail to pass theentry control at a node.Sometimes such a request isstill necessary and is notdeleted. In this case, therequest should not blockother requests for reservingresources. As a result, thenode enters the blockadestate.

Status Timer Refresh Period(ms)

5000-2147483647 Set the period for refreshingthe status timer.

Status Timer TimeoutMultiple

3-255 Set the timeout multiples ofthe status timer. Whenconsecutive times of notreceiving the refreshmessages exceed the timeoutmultiples of the status, thestatus is deleted.

Authentication Type No Authentication, the Modeof MD5 Encryption

Set the RSVP authenticationtype.

Authentication Key Example: A9j* Set the authentication key.NOTE

The authentication key can beset only when theauthentication type is the Modeof MD5 Encryption.



5-23


Hello Send Interval(s) 1-60 Set the interval fortransmitting the hellopackets.The hello packets are used fordetecting loss of the neighbornodes or re-setting the RSVPstatus information of theneighbors.

Hello Loss Count 3-255 Set the count of the lost hellopackets.

FRR Retransmission TimerInterval(ms)

1-2147483647 Set the timing interval forretrying the FRR.Set the timing interval for thePLR node to periodicallyselect the bypass tunnel in theFRR protection.

Table 5-4 Descriptions of the parameters for Static Route Management


Route List ID Example: 3 Set the ID of the route list.

Board Example: Slot-Board Name Select a board.NOTE

Select the board that supportsLayer 3 ports.

Port Example: Port(Port No.) Select a port.NOTE

Select the port whose generalattributes and Layer 3 attributesare configured.

Next Hop IP Address Example: 10.70.1.3 Set the IP address of the nexthop.

Destination IP Example: 1.0.1.5 Set the LSR ID of thedestination.

Destination IP Subnet Mask Example: 255.255.255.0 Set the mask of thedestination IP address.


Configuration Guide


Issue 06 (2009-06-01)

Table 5-5 Descriptions of the parameters for Address Parse


ARP List IP Example: 129.9.1.23 Configure the IP address inthe ARP list.

ARP List MAC Example: 1C-C4-31-88-1C-C4

Configure the MAC addresscorresponding to the IPaddress in the ARP list.

ARP List Type Static, Dynamic Display the type of the ARPlist.

Table 5-6 Parameters of the node configuration


IGP-OSPF Instance ID 1-65535 Specifies the ID of the IGP-OSPFinstance. You can also set theautomatic allocation of IDs.

Management Status Up, Down Displays the management status ofthe IGP-OSPF instance.

Operating Status Up, Down, Going Up,Going Down, Failed

Displays the operation status of theIGP-OSPF instance.

GR Enable Enabled, Disabled Sets whether to enable GR.GR: graceful restartAfter you enable the OSPF GRfunction, if the equipment restartsbecause of an exception, theequipment can still ensure that dataare forwarded in normal state in theperiod during which the protocol isrestarted and route flapping is notcaused because of the equipmentrestart in a short time. Therefore, keyservices are not interrupted.

GR Time 3-3600 Sets the GR time. When a GR routerdetects that the opposite router isdown, the topology or routeinformation sent by the oppositerouter is not deleted within the GRtime.



5-25

Table 5-7 Parameters of the port configuration


IGP-OSPF Instance ID 1 to 65535 Specifies the ID of the IGP-OSPFinstance.


Displays the port whose IGP-OSPFparameters are required to be set.A port can be added to the instancesof different route protocols. A port,however, can be added to only oneinstance of each route protocol.

Hello Timer(s) 1 to 65535 Sets the timer of hello packets.The IGP-OSPF protocol periodicallytransmits hello packets from the port.The PTN equipment maintains theneighbor relations by transmittingand receiving the hello packets.

Table 5-8 Parameters of the route importing


IGP-OSPF Instance ID 1 to 65535 Specifies the ID of the IGP-OSPFinstance.

Source Route ProtocolType

Static Route, IGP-OSPFProtocol, ISIS Protocol,RIP Protocol, BGPProtocol

Sets the source route protocol type.Currently, only the static route can befully imported to the IGP-OSPF.

Overhead 1 to 255 Sets the overheads, that is, routemetric, for the imported route.

Table 5-9 Parameters of the link TE information


IGP-OSPF Instance ID 1 to 65535 Displays the ID of the IGP-OSPFinstance.

Local Node ID For example: 10.70.73.22 Displays the LSR ID of the localnode.

Local Link IP For example: 10.70.73.12 Displays the IP address of the locallink.

Opposite Node ID For example: 10.70.73.20 Displays the LSR ID of the oppositenode.


Configuration Guide


Issue 06 (2009-06-01)


Opposite Link IP For example: 10.70.73.10 Displays the IP address of theopposite link.

Maximum ReservedBandwidth(kbit/s)

For example: 160000 Displays the maximum reservedbandwidth.

TE Measurement 0 to 0xFFFFFFFF Displays the TE measurement value.

Available Bandwidth ofLink Priority 0 (kbit/s)

For example: 16000 Displays the available bandwidth ofthe link of priority 0.

















5-27

6 Configuring an MPLS Tunnel

About This Chapter

In a PSN network, the MPLS tunnel carries PWs where various services are encapsulated. Inthis way, data packets can be transparently transmitted among NEs. One MPLS tunnel can carryseveral PWs. Before configuring a service, first configure a MPLS tunnel that carries the service.On the T2000, you can use the trail function or per-NE configuration scheme to configure anMPLS tunnel.

6.1 Basic ConceptsBefore configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, andapplication scenarios of the MPLS tunnel.

6.2 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the Trail FunctionTo fast create a dynamic MPLS tunnel by using the trail function, just specify the Ingress andEgress nodes of the MPLS tunnel. During creation of the MPLS tunnel, fast rerouting can beconfigured.

6.3 Creating a Static MPLS Tunnel by Using the Trail FunctionTo create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLStunnel.

6.4 Configuring Basic Attributes of the MPLSIn the Basic Configuration interface, you can set LSR ID, Start of Global Label Space andStart of Multicast Label Space.

6.5 Creating an MPLS Tunnel on a Per-NE BasisYou can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,create a tunnel at each node involved in the tunnel.

6.6 Querying the Tunnel Label InformationOn the NE, the label for each tunnel is unique. By querying the tunnel label information, youcan learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating astatic tunnel.

6.7 Configuring MPLS OAMConfigure the MPLS OAM to enable the CV/FFD detection of a tunnel. In this way, theconnectivity of the MPLS tunnel can be monitored in a real-time manner and the MPLS tunnelswitching can be triggered.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 6 Configuring an MPLS Tunnel


6-1

6.8 Creating an MPLS Tunnel Protection GroupYou can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnelprotection group, the MPLS tunnel protection group must be configured at the source and sinkNEs of the MPLS tunnel.

6.9 Configuration Case of the Dynamic MPLS TunnelThis section describes how to configure a dynamic MPLS tunnel. The configuration case andconfiguration flowchart help you better understand the process of configuring a dynamic MPLStunnel. The configuration case includes tunnel planning and tunnel configuration.

6.10 Configuration Case of the Static MPLS TunnelThis section describes how to configure a static MPLS tunnel by using the trail function and ona per-NE basis. The configuration case and configuration flowchart help you better understandthe service configuration process. The configuration includes networking, service planning, andconfiguration process.

6.11 Parameter DescriptionThis section describes the parameters related to the MPLS Tunnel configuration.

6 Configuring an MPLS TunnelOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

6.1 Basic ConceptsBefore configuring the MPLS tunnel, familiar yourself with the MPLS and MPLS tunnel, andapplication scenarios of the MPLS tunnel.

6.1.1 MPLS and MPLS TunnelAs a transmission technology, the multi-protocol label switching (MPLS) can realize transparenttransmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLSprotocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmissionand carries the PWs related to the service.

6.1.2 Application of the MPLS TunnelAs the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmitservice packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLANand S-VLAN packets, MPLS packets, and ATM packets. The MPLS Tunnel is mainly used fortransparent transmission of point-to-point data service packets and Tunnel protection group.

6.1.1 MPLS and MPLS TunnelAs a transmission technology, the multi-protocol label switching (MPLS) can realize transparenttransmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLSprotocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmissionand carries the PWs related to the service.

Figure 6-1 shows how the MPLS tunnel is used as the service transmission channel.

Figure 6-1 MPLS tunnel in the MPLS network

IMA E1

FE

ATM STM-1MPLS tunnel

Ingress node Transit node Egress node IMA E1

FE

ATM STM-1

PW

The MPLS tunnel only provides an end-to-end channel, and does not care which service isencapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuckwith an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packetsare recovered and retain the original service features. In the tunnel, the intermediate nodes arecalled Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.

6.1.2 Application of the MPLS TunnelAs the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmitservice packets. The MPLS Tunnel can carry various services, such as IP packets, C-VLANand S-VLAN packets, MPLS packets, and ATM packets. The MPLS Tunnel is mainly used fortransparent transmission of point-to-point data service packets and Tunnel protection group.



6-3

Transparent Transmission of Point-to-Point Data PacketsCommonly, the MPLS tunnel is used to provide a point-to-point service channel for servicessuch as the E-Line service. In this way, provider edges (PEs) in a PSN network can transparentlytransmit services. Figure 6-2 shows how point-to-point data packets are transparentlytransmitted.

Figure 6-2 Transparent transmission of point-to-point data packets

Node BRNC

MPLS tunnel

MPLS tunnel

MPLS tunnel

Node B

Node B

PE

PE

PE

PE

An edge node in one network accesses the services from Node B, and transports the services tothe RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can beused. On the T2000, two schemes can be used to create such a unicast tunnel.l Configuration on a per-NE basis: Configure the ingress port and the IP address of the next

hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel iscreated.

l Configuration by trail: This configuration is classified into static configuration and dynamicconfiguration.– Static configuration: Specify the source and sink NEs for the MPLS tunnel, and each

NE involved in the tunnel. In this way, one unicast MPLS tunnel is created.– Dynamic configuration: Only specify the source and sink NEs of the MPLS tunnel. The

equipment then creates a unicast MPLS tunnel through signaling.

Tunnel Protection GroupThe MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1+1 or 1:1 protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, theTunnel protection group ensures that services can still normally run.


Configuration Guide


Issue 06 (2009-06-01)

By using the T2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carryimportant services.

Figure 6-3 shows the protection principle for unicast tunnels.

Figure 6-3 Protection principle for unicast tunnels

CE

CE

Ingressnode

Egressnode

Workingtunnel

Protectiontunnel

Configuration of sourceprotection group

Configuration of sinkprotection group

6.2 Creating a Dynamic MPLS Tunnel and the FRRProtection by Using the Trail Function

To fast create a dynamic MPLS tunnel by using the trail function, just specify the Ingress andEgress nodes of the MPLS tunnel. During creation of the MPLS tunnel, fast rerouting can beconfigured.


l You must complete the correct configuration of the port attributes.

l You must complete the correct setting of the LSR ID for each NE.

l You must complete the correct configuration of the control plan for each NE.

ContextFor details of FRR protection, refer to FRR in the Feature Description.

Procedure

Step 1 On the Main Topology, choose Trail > Tunnel > Tunnel Creation . The Create Tunnel dialogbox is displayed.

Step 2 Select Create Reverse Tunnel to configure the parameters for the forward and reverse dynamictunnels. When creating a dynamic MPLS tunnel by using the trail function, see Table 6-5 fordetails on the parameters for general attributes.



6-5

NOTE

Take the following precautions when setting each parameter.

l Tunnel ID: You can manually set this parameter, or select automatic allocation from the drop-downmenu to allocate a tunnel ID. When manually setting this parameter, enter the Tunnel ID manually.The value of the ID ranges from 1 to 65535.

l Signal type: Select dynamic. The signal type indicates that the MPLS Tunnel of this type is created.

Step 3 Click Next. In the Select Node dialog box, select Source Node and Sink Node. When creatinga dynamic MPLS tunnel by using the trail function, see Table 6-6 for details on the parametersfor selecting nodes.

Step 4 Optional: Click Add to add the route restriction conditions of the forward route and reverseroute. For route restrictions, set Route Constraint Port IP Address and Rerouting Mode.Whencreating a dynamic MPLS tunnel by using the trail function, see Table 6-7 for details on theparameters for route constraint.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

For Route Constraint Port IP Address, set the IP address of the port involved in the MPLS tunnel.

For Rerouting Mode, set the excluded node, loose explicit node or strict explicit node.

l Exclude indicates that the created MPLS tunnel does not involve the Route Constraint Port IPAddress.

l Include Loose indicates that the tunnel must traverse the ports with Route Constraint Port IPAddress and must traverse the constraint ports in the same sequence in which the ports are added intothe constraint list. There can be multiple hops between Include Loose constraint ports. That is, thenumber of hops along the tunnel can be larger than the number of constraint ports added in the constraintlist for the tunnel.

l Include Strict indicates that the tunnel must traverse the ports with Route Constraint Port IPAddress and must traverse the constraint ports in the same sequence in which the ports are added intothe constraint list. There can be only one hop between Include Strict ports. That is, the IncludeStrict constraint port must be directly connected to the existing constraint port.

Step 5 Click Next. Set Setup Priority, Hold Priority, Color(0x), Mask(0x), Tunnel Type and Re-Route.For details on the parameters for priority when creating a dynamic MPLS tunnel by usingthe trail function, see Table 6-8.



6-7

Step 6 Optional: If the tunnel is the bypass tunnel for fast rerouting, set Tunnel Type to BypassTunnel.


Configuration Guide


Issue 06 (2009-06-01)

Step 7 Optional: If the tunnel is the working tunnel for fast rerouting, set Tunnel Type to PrimaryTunnel first. Then select Fast Re-Route to activate the grey area and configure the parameters.When creating a dynamic MPLS tunnel by using the trail function, see Table 6-9 for details onthe parameters for FRR.

NOTE

In this case, you can set FRR Protection Type and FRR Bandwidth(kbit/s).

Step 8 Click Next. A dialog box is displayed to show information on the created tunnel.

Step 9 Click Finish. The progress bar is displayed to show the creation progress. The OperationResult dialog box is displayed, indicating that the dynamic tunnel is successfully created. Then,click Close.

Step 10 Optional: Set the protection port of the bypass tunnel.

1. In the Main Topology, choose Trail > Tunnel > Dynamic Tunnel Management. TheSet Dynamic Tunnel Filter Criteria dialog box is displayed.

2. Click Filter. Select a bypass tunnel in the tunnel list.

NOTE

If Tunnel Type is set to Bypass Tunnel for a tunnel, the tunnel is a bypass tunnel.

3. Click the Protected Port tab and click Modify. The Modify Protected Port dialog box isdisplayed.

4. Select the bypass tunnel protected port, and click . Then, click OK.



6-9

NOTE

When the protection port of the bypass tunnel is configured, all the working tunnels that pass through thisport and intersect with the sink node (MP node) of the bypass tunnel are protected by the bypass tunnel.To be protected by the bypass tunnel, the setup priority, hold priority, and color of the working tunnel mustbe consistent with the setup priority, hold priority, and color of the bypass tunnel. If these parameters ofthe working tunnel are inconsistent with that of the bypass tunnel, the working tunnel is not protected.

----End

6.3 Creating a Static MPLS Tunnel by Using the TrailFunction

To create a static MPLS tunnel by using the trail function, specify the NEs involved in the MPLStunnel.




Procedure

Step 1 On the Main Topology, choose Trail > Tunnel > Tunnel Creation . The Create Tunnel dialogbox is displayed.

Step 2 Select Create Reverse Tunnel to configure the parameters for the forward and reverse statictunnels. When creating a static MPLS tunnel by using the trail function, see Table 6-10 fordetails on the parameters.


Configuration Guide


Issue 06 (2009-06-01)

NOTE


l Tunnel ID: You can manually set this parameter, or select automatic allocation from the drop-downmenu to allocate a tunnel ID. When manually setting this parameter, enter the Tunnel ID manually.The value of the ID ranges from 1 to 65535.

l Signal Type: Select static. The signal type indicates that the MPLS Tunnel of this type is created.

Step 3 Click Next. Select nodes from the Available NE. Click to add each node as an Ingressnode, Egress node or Transit node. When creating a static MPLS tunnel by using the trailfunction, see Table 6-11 for details on the parameters.



6-11

NOTE

When adding the transit node, follow the sequence of NEs that the link traverses in the networking.

Step 4 Click Next. Set parameters for nodes selected in the previous step. When creating a static MPLStunnel by using the trail function, see Table 6-12 for details on the parameters for routeinformation.

1. Ingress node: Set Out Port, Out Label and Next Hop Address.

2. Egress node: Set In Port and In Label.3. Transit node: Set Out Port, Out Label, In Port, In Label and Next Hop Address.

NOTE

For Next Hop Address, set the IP address of the interface of the next node, or set the LSR ID for the nextnode.

The label value of the ingress node may be same as or different from the label value of the egress node.The label value of the egress node is signalled by the upstream node.

Step 5 Click Next. A dialog box is displayed to show information on the created tunnel. When creatinga static MPLS tunnel by using the trail function, see Table 6-13 for details on the parametersfor tunnel information.

Step 6 Click Finish. A progress bar is displayed to show the creation progress. When the creation iscomplete, the Operation Result is displayed, indicating that the MPLS tunnel is successfullycreated. Then, click Close.

----End

6.4 Configuring Basic Attributes of the MPLSIn the Basic Configuration interface, you can set LSR ID, Start of Global Label Space andStart of Multicast Label Space.


Procedure

Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > BasicConfiguration from the Function Tree.

Step 2 Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. For details onthe parameters for general attributes of MPLS, see Table 6-14.

CAUTIONIf there are services on the NE, modifying LSR ID may result in NE reset and serviceinterruption.

----End


Configuration Guide


Issue 06 (2009-06-01)

6.5 Creating an MPLS Tunnel on a Per-NE BasisYou can create an end-to-end unicast MPLS tunnel on a per-NE basis. To create such a tunnel,create a tunnel at each node involved in the tunnel.




Procedure

Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLSManagement > Unicast Tunnel Management from Function Tree.

Step 2 Click the Static Tunnel tab and click New. The New Unicast Tunnel dialog box is displayed.

Step 3 Select Create Reverse Tunnel to set parameters for the forward and reverse tunnels. Whencreating an MPLS tunnel on a per-NE basis, see Table 6-15 for details on the related parameters.



6-13

NOTE

When Node Type is set to Egress, Bandwidth(kbit/s) must be consistent with the tunnel bandwidth inthe Ingress direction and cannot be set.For Next Hop Address, select the IP address of the interface of the next node, or the LSR ID of the nextnode.

Step 4 Click OK to finish creation of the static tunnel.

Step 5 Follow Steps 1 - 4 to create static tunnels for Transit nodes and the Egress node.

Step 6 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate differenttunnels by adding a VLAN ID.

----End

6.6 Querying the Tunnel Label InformationOn the NE, the label for each tunnel is unique. By querying the tunnel label information, youcan learn the usage of tunnel labels. Thus, you can avoid the conflict of labels when creating astatic tunnel.


You must complete the creation of an MPLS tunnel.

Procedure

Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLSLabel Management from the Function Tree.

Step 2 In the Tunnel Label tab, click Query to view the tunnel label information.

----End

6.7 Configuring MPLS OAMConfigure the MPLS OAM to enable the CV/FFD detection of a tunnel. In this way, theconnectivity of the MPLS tunnel can be monitored in a real-time manner and the MPLS tunnelswitching can be triggered.

Prerequisitel You must complete the creation of an MPLS tunnel.

l You must be an NM user with "NE or network operator" authority or higher.

Procedure

Step 1 Click the NE in the NE Explorer interface. Choose Configuration > MPLS Management >Unicast Tunnel Management from Function Tree.

Step 2 Click the OAM Parameters tab and set the parameters.For details on the parameters for OAMof MPLS, see Table 6-17.


Configuration Guide


Issue 06 (2009-06-01)

NOTE


l Detection Packet Period: If CV is selected for Detection Packet Type, the Detection PacketPeriod is fixed as 1000 ms. If FFD is selected for Detection Packet Type, the Detection PacketPeriod can be set.

l Reverse Tunnel: The BDI packets that carry information on defects are sent to the ingress node, whichthen knows the defect states in time.

Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operationsucceeds.

Step 4 Click Close.

----End

6.8 Creating an MPLS Tunnel Protection GroupYou can create an MPLS tunnel protection group to protect MPLS tunnels. You can configure1+1 protection and 1:1 protection in an MPLS tunnel protection group. To create an MPLS tunnelprotection group, the MPLS tunnel protection group must be configured at the source and sinkNEs of the MPLS tunnel.


l The working and protection tunnels of an MPLS tunnel must be created.

l You must have enabled the MPLS OAM state of each MPLS tunnel in the protection group.

l The OAM packet type must be set to FFD and transmission period to 3.3 ms.

WARNINGl In the case of a network-side port configured with the MPLS tunnel 1+1 protection, the linear

multiplex section protection (LMSP) should not configured for the port.l The node that is configured with the MPLS APS protection cannot be configured with the

FRR protection.l The protection tunnel should not carry any extra service.

Procedure

Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APSProtection Management from the Function Tree.

Step 2 Click New. The New Tunnel Protection Group dialog box is displayed.



6-15

Step 3 Set parameters for the tunnel protection group.For details on the parameters for MPLS tunnelprotection group, seeTable 6-16.l Protection Type: You can select 1+1 or 1:1.

l Switching Mode: You can select Single-Ended or Dual-Ended. When the protection type is1:1, the switching mode must be dual-ended.

l Revertive Mode: You can select Non-revertive or Revertive.

l Hold-off Time(100ms): The unit is 100 millisecond. You can enter an integer from 0 to 100,that is, 0 to 10 seconds.

CAUTIONWhen creating an APS protection group, disable Protocol Status. Start the protocol only whenthe configuration of the APS protection group is complete at both nodes.

Step 4 Click OK. The MPLS tunnel protection group is successfully configured.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

The bandwidth of the protection tunnel should exceed that of the working tunnel. To increase the bandwidthof the working tunnel after the protection group is created, increase the bandwidth of the protection tunnelfirst.

Step 5 Refer to Steps 1 through 4 to configure the protection group on the sink NE of the tunnel.

Step 6 Start the protocol state of the MPLS APS protection group.

1. Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APSProtection Management from the Function Tree.

2. Right-click a created APS protection group, and select Start Protocol.3. A dialog box is displayed indicating that the operation is successful. Protocol Status of

the APS protection group turns to Enabled.

----End

6.9 Configuration Case of the Dynamic MPLS TunnelThis section describes how to configure a dynamic MPLS tunnel. The configuration case andconfiguration flowchart help you better understand the process of configuring a dynamic MPLStunnel. The configuration case includes tunnel planning and tunnel configuration.

6.9.1 Networking DiagramThis section describes the networking diagram for the example of configuring an MPLS tunnel.

6.9.2 Service PlanningThe services between the branches of Company A are carried by the primary tunnel. Bypasstunnel 1 and bypass tunnel 2 provide FRR protection for the primary tunnel.

6.9.3 Creating a Dynamic MPLS TunnelThis section describes how to configure the dynamic MPLS Tunnel in the example.

6.9.1 Networking DiagramThis section describes the networking diagram for the example of configuring an MPLS tunnel.

As shown in Figure 6-4, Company A has branches in City 1 and City 2. Real-time servicetransmission is required between the branches. In this case, an MPLS tunnel can be created tocarry the real-time services.

Real-time services require high network security. Hence, FRR protection should also beconfigured for the MPLS tunnel between NE1 and NE3.

l The NE1-to-NE3 primary tunnel is along the NE1-NE2-NE3 trail. NE2 is the transit node.

l The NE1-to-NE3 bypass tunnel 1 is along the NE1-NE4-NE3 trail. When the NE1-NE2link fails or the NE2 has a fault, bypass tunnel 1 protects the primary tunnel.

l The NE1-to-NE3 bypass tunnel 2 is along the NE2-NE4-NE3 trail. When the NE2-NE3link fails, bypass tunnel 2 protects the primary tunnel.



6-17

Figure 6-4 Networking diagram of an MPLS tunnel

A Company

City1A Company

City2

NE1

NE2

Bypass Tunnel 2

Bypass Tunnel 1

Primary Tunnel

NE4

NE3

Figure 6-5 shows the NE planning. NE1 is an OptiX PTN 1900 NE. NE2, NE3 and NE4 areOptiX PTN 3900 NEs.

Figure 6-5 NE planning

A Company

City1A Company

City2

NE1

NE2

NE3

NE4

Bypass Tunnel 2

Bypass Tunnel 1

Primary Tunnel

4-EFG2-2

4-EFG2-1

1-EG16-1 1-EG16-2

1-EG16-2

1-EG16-1

1-EG16-1 1-EG16-2

1-EG16-3

1-EG16-3

10.1.1.1 10.1.2.2

10.1.2.1

10.1.5.1

10.1.5.2

10.1.4.1

10.1.3.1

10.1.3.2

10.1.1.210.1.4.2

6.9.2 Service PlanningThe services between the branches of Company A are carried by the primary tunnel. Bypasstunnel 1 and bypass tunnel 2 provide FRR protection for the primary tunnel.

On the NNI side of the NEs, the GE boards are used and a GE ring is built on the boards. Table6-1 lists the planning details of NE parameters.


Configuration Guide


Issue 06 (2009-06-01)

Table 6-1 Configuration parameters of NEs

NEs LSR ID Interface IP Address of theInterface

Subnet Mask ofthe Interface

NE1 1.0.0.14-EFG2-1(Port-1) 10.1.1.2 255.255.255.252

4-EFG2-2(Port-2) 10.1.3.2 255.255.255.252

NE2 1.0.0.2

1-EG16-1(Port-1) 10.1.1.1 255.255.255.252

1-EG16-2(Port-2) 10.1.2.2 255.255.255.252

1-EG16-3(Port-3) 10.1.4.2 255.255.255.252

NE3 1.0.0.31-EG16-1(Port-1) 10.1.2.1 255.255.255.252

1-EG16-2(Port-2) 10.1.5.1 255.255.255.252

NE4 1.0.0.4

1-EG16-1(Port-1) 10.1.5.2 255.255.255.252

1-EG16-2(Port-2) 10.1.3.1 255.255.255.252

1-EG16-3(Port-3) 10.1.4.1 255.255.255.252

Since the service bandwidth is 10 Mbit/s, the bypass tunnel should have bandwidth more than10 Mbit/s. In addition, the service travels through several NEs. Hence, several bypass tunnelsare required to completely protect the tunnel for the service. According to the actual condition,two bypass tunnels are planned for the FRR.

Table 6-2 lists the planned parameters of the primary tunnel and the two bypass tunnels.

Table 6-2 Configuration parameters of Tunnels

Parameter Primary Tunnel Bypass Tunnel 1 Bypass Tunnel 2

Tunnel ID Positive: 1Reverse: 2

Positive: 3Reverse: 4

Positive: 5Reverse: 6

Name Positive:Tunnel-0001Reverse:Tunnel-0002

Positive:Tunnel-0003Reverse:Tunnel-0004

Positive:Tunnel-0005Reverse:Tunnel-0006

Signal Type Dynamic Dynamic Dynamic

Scheduling Type E-LSP E-LSP E-LSP

Bandwidth (kbit/s) 10240 10240 10240

Tunnel SourceNode

NE1 NE1 NE2

Tunnel Sink Node NE3 NE3 NE3



6-19

Parameter Primary Tunnel Bypass Tunnel 1 Bypass Tunnel 2

Positive RouteConstraint Port IPAddress

IP addresses ofingress port of NE2:1-EG16-1: 10.1.1.1IP addresses ofingress port of NE3:1-EG16-1: 10.1.2.1



Reverse RouteConstraint Port IPAddress

IP addresses ofingress port of NE2:1-EG16-2: 10.1.2.2IP addresses ofingress port of NE1:4-EFG2-1: 10.1.1.2

IP addresses ofingress port of NE4:1-EG16-2: 10.1.5.2IP addresses ofingress port of NE1:4-EFG2-2: 10.1.3.2


Rerouting Mode Include Strict Include Strict Include Strict

Note: In this case, the subnet mask at each NNI is 255.255.255.252.

6.9.3 Creating a Dynamic MPLS TunnelThis section describes how to configure the dynamic MPLS Tunnel in the example.

Prerequisite

You must be an NM user with "NE operator" authority or higher.

You must understand the networking, requirements and service planning of the example.

A network must be created.

Procedure

Step 1 Set LSR IDs.1. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management >

Basic Configuration from the Function Tree.2. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. Click

Apply.

The configuration parameters are as follows:l LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.)

l Start of Global Label Space: 0 (The minimum values of egress and ingress labels of theunicast tunnel.)

3. Display the NE Explorer for NE2, NE3, and NE4 separately. Set the parameters such asLSR ID of each NE by following the previous two steps.

The configuration parameters are as follows:l NE2 LSR ID: 1.0.0.2


Configuration Guide


Issue 06 (2009-06-01)

l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

Step 2 Configure NNI interfaces.1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure the network-side interface.2. In the General Attributes tab, select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2). Right

click the Port Mode filed, and select Layer 3. Set the parameters as required, and clickApply.

The configuration parameters are as follows:l Enable Port: Enabled

l Port Mode: Layer 3 (The port carries a tunnel.)

l Working Mode: Auto-Negotiation (Set the working modes of the local port and oppositeport as the same.)

l Max Frame Length (byte): 1620 (Set this parameter according to the length of datapackets. All the received data packets that contain more bytes than the maximum framelength are discarded.)

3. Select the 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Layer 3 Attributes tab. Rightclick the Enable Tunnel field and select Enabled. Right-click the Specify IP field andchoose Manually. Then, set the parameters such as IP Address and IP Mask. ClickApply.

The configuration parameters are as follows:l Enable Tunnel: Enabled

l Max Reserved Bandwidth (kbit/s): 1000000 (The maximum reserved bandwidth shouldnot exceed the physical bandwidth of the bearer port.)

l TE Measurement: 10 (The link with a smaller TE measurement value is preferred forroute selection of a tunnel. You can intervene in the route selection by adjusting the TEmeasurement of the link. The smaller the value of the TE measurement, the higher thepriority of the link. )

l Specify IP: Manually (Manually indicates that you can set the IP address of the port.)

l 4-EFG2-1(Port-1) IP Address: 10.1.3.2


l IP Mask: 255.255.255.252

4. Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 2.1 throughStep 2.3 to set parameters of each related interface.

The configuration parameters are as follows:

Set the parameters of each interface the same as NE1-4-EFG2 and set different IP addressesfor them.

l NE2-1-EG16-1(Port-1) IP Address: 10.1.1.1







6-21




Step 3 Configure the control plane.1. In the NE Explorer, select an NE1 and choose Configuration > Control Plane

Configuration > IGP-ISIS Configuration from the Function Tree.2. Select 4-EFG2-1(Port-1) and 4-EFG2-2(Port-2) in the Port Configuration tab. Right click

IS-IS Enable field, and select Enabled. Click Apply.

The configuration parameters are as follows:l IS-IS Enable: Enabled (After the IS-IS routing protocol is enabled, an MPLS LSP can

be dynamically created and PW labels can also be distributed dynamically.)l Link Level: level-1-2

l LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the localequipment fails to receive any response in a period after transmitting the LSP, the localequipment considers that the LSP is lost or discarded. To ensure the transmissionreliability, the local equipment transmits the LSP again.)

l Minimum LSP Transmission Interval (ms): 30

3. Optional: Choose Configuration > Control Plane Configuration > MPLS-LDPConfiguration from the Function Tree.

NOTE

When creating a dynamic PW to carry services, set the parameters related to MPLS-LDP.

4. Optional: Click Create. Enter the ID of the opposite NE in the Create LDP PeerEntity dialog box. Click OK.

The configuration parameters are as follows:l Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminal

NE on the PW, that is, NE3 in this case.)l Hello Send Interval(s): 10 (The Hello packets are periodically sent to maintain the

neighborship.)l KeepAlive Send Interval(s): 10 (The KeepAlive packets are periodically sent to

maintain the LDP session.)5. Display the NE Explorer for NE2 and NE3 separately. Perform Step 3.1 through Step

3.4 to set the parameters related to the control plane.

Set the IS-IS parameters of NE2 and NE3 as the same as the IS-IS parameters of NE1. Setthe LDP parameters as follows:l NE2 LDP parameters

– Opposite LSR ID: 1.0.0.3 (The opposite LSR ID indicates the LSR ID of the terminalNE on the PW, that is, NE3 in this case.)

l NE3 LDP parameters– NE3-NE1 peers

Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminalNE on the PW, that is, NE1 in this case.)

– NE3-NE2 peers


Configuration Guide


Issue 06 (2009-06-01)

Opposite LSR ID: 1.0.0.2 (The opposite LSR ID indicates the LSR ID of the terminalNE on the PW, that is, NE2 in this case.)

Step 4 Creating Primary MPLS Tunnel.1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box

is displayed.2. Select Create Reverse Tunnel, and configure parameters for the positive tunnel and

reverse tunnel in the General Attributes.

The configuration parameters are as follows:l Tunnel ID: 1 (Positive), 2 (Reverse)

l Name: Tunnel-0001 (Positive), Tunnel-0002 (Reverse)

l Signal Type: Dynamic (If you set signal type to dynamic, the LDP distributes labelsand the tunnel is a dynamic tunnel; if you set signal type to static, labels are manuallyadded and the tunnel is a static tunnel.)

l Scheduling Type: E-LSP– E-LSP indicates that the tunnel determines the scheduling priority and discard

priority of packets according to the EXP information. On one MPLS tunnel of theE-LSP type, there can be a maximum of eight types of PWs.

l EXP: none (When the EXP value of the tunnel is set, if the packets are at the egressport, this value is filled in the EXP filed of the MPLS packets. If it is set to none, theequipment searches for the corresponding EXP value in the mapping relation in theDiffserv domain according to the scheduling priority of user packets. When the packetsare at the egress port, this value is filled in the EXP filed of the MPLS packets. Thedownstream nodes determine the packet scheduling priority and discarding priorityaccording to the EXP information of the MPLS packets. The EXP value is set accordingto the networking planning, and it is not set in this example.)

l Bandwidth (kbit/s): 10240 (Set the bandwidth according to networking planning.)

3. Click Next, and select Source Node and Sink Node. Click Add to add route restrictions.



6-23

The configuration parameters are as follows:l Source Node: NE1

l Sink Node: NE3

l Positive Route Constraint Port IP Address: 10.1.1.1, 10.1.2.1, Include Strict

l Reverse Route Constraint Port IP Address: 10.1.2.2, 10.1.1.2, Include Strict

4. Click Next. Set the parameters such as Setup Priority and Hold Priority for the tunnelaccording to the planning. Then, click Next. Confirm the tunnel information and then clickFinish.


l Setup Priority: 7 (Setup priority is specified for an MPLS tunnel during creation. "0"indicates the highest priority. In the case insufficiency of resources, the MPLS tunnelof a higher setup priority can preempt the bandwidth of other MPLS tunnels and thuscan be created successfully.)

l Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0"indicates the highest priority. In the case of insufficiency of resources, the bandwidthfor the MPLS tunnel of a higher hold priority is less likely to be preempted by othertunnels. When creating a dynamic tunnel, make sure that the hold priority is higher orequal to the setup priority.)

l Color(0x): 0 (Set the affinity attribute of a link. When the primary tunnel is faulty, thelink with the same color is preferred during rerouting. When the affinity attribute oflinks is not required, adopt the default value.)

l Mask(0x): 0 (Set the number of bits of the mask. Match the number of bits of a maskwith the link color. Select the route of a matching link color.)

l Tunnel Type: Primary Tunnel (You can set the tunnel type to primary tunnel or bypasstunnel. According to the planning, the tunnel is a primary tunnel in this case.)

l Fast Re-Route: Selected


Configuration Guide


Issue 06 (2009-06-01)

l FRR Type: Facility Mode (In the facility mode, one LSP tunnel protects multiple LSPtunnels. Currently, the OptiX PTN equipment supports only the facility backup mode.)

l FRR Protection Type: Protection Node Mode– In the case of the protection node mode, the bypass tunnel selected by the PLR must

protect the downstream node adjacent to the PLR, and the links between them. Ifany other link is faulty, the FRR protection switching is triggered through the controlplane. This process takes a relatively long time.

– In the case of the protection link mode, the bypass tunnel selected by the PLR mustprotect the link between the PLR and downstream adjacent node.

l FRR Bandwidth(kbit/s): No Limit (Set the bandwidth according to networkingplanning.)

Step 5 Creating Primary MPLS Tunnel.1. Configure the General Attributes of Bypass Tunnel1 by following Step 4.1 to Step 4.2.


l Tunnel ID: 3 (Positive), 4 (Reverse)


l Signal Type: Dynamic

l Scheduling Type: E-LSP

l EXP:- (tunnel priority)




l Sink Node: NE3





l Setup Priority: 7 (The setup priority of the bypass tunnel must be the same as the setuppriority of the primary tunnel.)

l Hold Priority: 0 (The hold priority of the bypass tunnel must be the same as the holdpriority of the primary tunnel.)

l Color(0x): 0 (The link color of the bypass tunnel must be the same as the link color ofthe primary tunnel.)

l Mask(0x): 0 (Set this parameter the same as the primary tunnel.)

l Tunnel Type: Bypass Tunnel (According to the planning, the tunnel is a bypass tunnelin this case.)

l Re-Route: selected

4. Create Bypass Tunnel2 by following Step 5.1 to Step 5.3.



6-25


l General Attributes– Tunnel ID: 5(Positive), 6(Reverse)

– Name: Tunnel-0005(Positive), Tunnel-0006(Reverse)

– Signal Type: Dynamic

– Scheduling Type: E-LSP

– EXP: -

– Bandwidth(kbit/s): 10240

l Route Constraint– Source Node: NE2

– Sink Node: NE3

– Positive Route Constraint Port IP Address: 10.1.4.1, 10.1.5.1, Include Strict

– Reverse Route Constraint Port IP Address: 10.1.5.2, 10.1.4.2, Include Strict

l Tunnel Management Attributes– Setup Priority: 7

– Hold Priority: 0

– Color(0x): 0

– Mask(0x): 0

– Tunnel Type: Bypass Tunnel (According to the planning, the tunnel is a bypasstunnel in this case.)

– Re-Route: selected

----End

6.10 Configuration Case of the Static MPLS TunnelThis section describes how to configure a static MPLS tunnel by using the trail function and ona per-NE basis. The configuration case and configuration flowchart help you better understandthe service configuration process. The configuration includes networking, service planning, andconfiguration process.

6.10.1 Networking DiagramThis section shows the networking diagram for the example of configuring a static MPLS tunnel.

6.10.2 Service PlanningThere are services between NodeB and RNC. Two static MPLS tunnels are to be created. Oneis the working tunnel and the other is the protection tunnel. Then, the services can be securelytransmitted on the network.

6.10.3 Creating a Static MPLS Tunnel by Using the Trail FunctionThis section describes how to configure the static MPLS Tunnel in the example by using thetrail function.

6.10.4 Configuring a Static MPLS Tunnel on a Per-NE BasisThis section describes how to configure the static MPLS Tunnel in the example on a per-NEbasis.


Configuration Guide


Issue 06 (2009-06-01)

6.10.1 Networking DiagramThis section shows the networking diagram for the example of configuring a static MPLS tunnel.

As shown in Figure 6-6, the service between NodeB and RNC is to be carried by a static MPLStunnel. NE1 accesses the service from NodeB. Then, the service is transmitted to the 10GE ringon the convergence layer through the GE ring on the access layer. Finally, the service isconverged at NE3 and transmitted to RNC.

If the service requires high network security, configure the MPLS APS protection to ensureservice transmission. For details on how to configure the MPLS APS protection, refer to MPLSAPS in the Feature Description.l Working tunnel: NE1-NE2-NE3. NE2 is a transit node.

l Protection tunnel: NE1-NE6-NE5-NE4-NE3. NE6, NE5, NE4, and NE3 are transit nodes.When the working tunnel becomes faulty, the service on it is switched to the protectiontunnel for protection.

Figure 6-6 Networking diagram of an MPLS tunnel

Working Tunnel

Protection Tunnel

OptiX PTN 3900 OptiX PTN 1900

NodeB

RNC

NE1 NE2 NE3

NE4NE5

NE6GE ring on

access layer

10GE ring on convergence

layer

NE1 and NE6 are OptiX PTN 1900 NEs. NE2, NE3, NE4 and NE5 are OptiX PTN 3900 NEs.Figure 6-7 shows the planning details of boards on the NE and interfaces on the boards.



6-27


Protected tunnel

Bypass tunnel


NodeB

4-EFG2-1(Port-1)10.0.5.2

RNC

NE1 NE2 NE3

NE4NE5

NE6

4-EFG2-1(Port-1)10.0.0.1

4-EFG2-2(Port-2)10.0.5.1

3-EG16-1(Port-1)10.0.0.2

1-EX2-1(Port-1)10.0.1.2

1-EX2-1(Port-1)10.0.1.1

1-EX2-2(Port-2)10.0.2.1

4-EFG2-2(Port-2)10.0.4.1

3-EG16-1(Port-1)10.0.4.2

1-EX2-1(Port-1)10.0.3.2 1-EX2-1(Port-1)

10.0.2.2

1-EX2-2(Port-2)10.0.3.1

GE ring on access layer


layer

6.10.2 Service PlanningThere are services between NodeB and RNC. Two static MPLS tunnels are to be created. Oneis the working tunnel and the other is the protection tunnel. Then, the services can be securelytransmitted on the network.

Table 6-3 lists the configuration parameters of NEs.


NE LSR ID Port Port IP Address IP Mask

NE1 1.0.0.14-EFG2-1(Port-1) 10.0.0.1 255.255.255.252

4-EFG2-2(Port-2) 10.0.5.1 255.255.255.252

NE2 1.0.0.23-EG16-1(Port-1) 10.0.0.2 255.255.255.252

1-EX2-1(Port-1) 10.0.1.1 255.255.255.252

NE3 1.0.0.31-EX2-1(Port-1) 10.0.1.2 255.255.255.252

1-EX2-2(Port-2) 10.0.2.1 255.255.255.252

NE4 1.0.0.41-EX2-1(Port-1) 10.0.2.2 255.255.255.252

1-EX2-2(Port-2) 10.0.3.1 255.255.255.252

NE5 1.0.0.51-EX2-1(Port-1) 10.0.3.2 255.255.255.252

3-EG16-1(Port-1) 10.0.4.2 255.255.255.252

NE6 1.0.0.64-EFG2-1(Port-1) 10.0.5.2 255.255.255.252

4-EFG2-2(Port-2) 10.0.4.1 255.255.255.252


Configuration Guide


Issue 06 (2009-06-01)

Table 6-4 lists the configuration parameters of Tunnels.

Table 6-4 Planning of Tunnel parameters

Parameters Working Tunnel Protection Tunnel

Tunnel ID 100 101 120 121

Name WorkingTunnel-Positive

Working Tunnel-Reverse

ProtectionTunnel-Positive

ProtectionTunnel-Reverse

Signal Type Static Static Static Static

SchedulingType

E-LSP E-LSP E-LSP E-LSP

Bandwidth(kbit/s)

No Limit No Limit No Limit No Limit

Ingress Node NE1 NE3 NE1 NE3

Transit Node NE2 NE2 NE6, NE5, NE4 NE4, NE5, NE6

Egress Node NE3 NE1 NE3 NE1

Ingress NodeRouteInformation

NE1l Out Port: 4-

EFG2-1(Port-1)

l Out Label:20

NE3l Out Port: 1-

EX2-1(Port-1)l Out Label: 21

NE1l Out Port: 4-

EFG2-2(Port-2)

l Out Label: 22

NE3l Out Port: 1-

EX2-2(Port-2)

l Out Label: 23



6-29


Transit NodeRouteInformation

NE2l In Port: 3-

EG16-1(Port-1)

l In Label: 20

l Out Port: 1-EX2-1(Port-1)

l Out Label:30

NE2l In Port: 1-

EX2-1(Port-1)l In Label: 21

l Out Port: 3-EG16-1(Port-1)

l Out Label: 31

NE6l In Port: 4-

EFG2-1(Port-1)

l In Label: 22

l Out Port: 4-EFG2-2(Port-2)

l Out Label: 32

NE5l In Port: 3-

EG16-1(Port-1)

l In Label: 32


l Out Label: 42

NE4l In Port: 1-

EX2-2(Port-2)

l In Label: 42


l Out Label: 52

NE4l In Port: 1-

EX2-1(Port-1)

l In Label: 23


l Out Label: 33

NE5l In Port: 1-

EX2-1(Port-1)

l In Label: 33


l Out Label: 43

NE6l In Port: 4-

EFG2-2(Port-2)

l In Label: 43


l Out Label: 53

Egress NodeRouteInformation

NE3l In Port: 1-

EX2-1(Port-1)

l In Label: 30

NE1l In Port: 4-

EFG2-1(Port-1)

l In Label: 31

NE3l In Port: 1-

EX2-2(Port-2)

l In Label: 52

NE1l In Port: 4-

EFG2-2(Port-2)

l In Label: 53

6.10.3 Creating a Static MPLS Tunnel by Using the Trail FunctionThis section describes how to configure the static MPLS Tunnel in the example by using thetrail function.




Configuration Guide


Issue 06 (2009-06-01)


ProcedureStep 1 Set LSR IDs.

1. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management >Basic Configuration from the Function Tree.

2. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. ClickApply.



3. Display the NE Explorer of NE2, NE3, NE4, NE5, and NE6 separately and perform thepreceding two steps to set the parameters such as LSR ID.


l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6












6-31

l Enable Tunnel: Enabled






l IP Mask: 255.255.255.252


Set the parameters of each interface the same as NE1-4-EFG2-1(Port-1).

The layer 3 attributes of each ports are as follows:

l NE2-1-EX2-1(Port-1)Max Reserved Bandwidth (kbit/s): 10000000IP Address: 10.0.1.1

l NE2-3-EG16-1(Port-1)Max Reserved Bandwidth (kbit/s): 1000000IP Address: 10.0.0.2







l NE6-4-EFG2-1(Port-1)Max Reserved Bandwidth (kbit/s): 1000000


Configuration Guide


Issue 06 (2009-06-01)

IP Address: 10.0.5.2l NE6-4-EFG2-2(Port-2)

Max Reserved Bandwidth (kbit/s): 1000000IP Address: 10.0.4.1

Step 3 Creating Working MPLS Tunnels1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box



The configuration parameters are as follows:l Tunnel ID: 100(Positive), 101(Reverse)

l Name: Working Tunnel-Positive, Working Tunnel-Reverse

l Signal Type: Static (If you set signal type to dynamic, the LDP distributes labels andthe tunnel is a dynamic tunnel; if you set signal type to static, labels are manually addedand the tunnel is a static tunnel.)



l EXP:- (Set the tunnel priority according to networking planning.)

l Bandwidth (kbit/s): No Limit (Set the bandwidth according to networking planning.)

3. Click Next, and select Ingress Node, Egress Node and Transit Node to set route restrictions.



6-33

The configuration parameters are as follows:l Ingress Node: NE1 (The source node on a tunnel is referred to as ingress node, that is,

the node where the tunnel enters the network.)l Egress Node: NE3 (The sink node on a tunnel is referred to as egress node, that is, the

node where the tunnel exists the network.)l Transit Node: NE2 (The pass-through node on a tunnel is referred to as transmit node.)

4. Click Next. Set tunnel-related parameters and route constraints. Then, click Next. Confirmthe tunnel information and then click Finish.


l Positive Route Information– NE1 Ingress Node

– Out Port: 4-EFG2-1(Port-1) (the source port on the tunnel)

– Out Label: 20 (The local out label is the same as the downstream in label. Labelsare used to forward packets.)

– Next Hop Address: 10.0.0.2


Configuration Guide


Issue 06 (2009-06-01)

– NE2 Transit Node

– In Port: 3-EG16-1(Port-1)

– In Label: 20

– Out Port: 1-EX2-1(Port-1)

– Out Label: 30


– NE3 Egress Node

– In Port: 1-EX2-1(Port-1)

– In Label: 30

l Reverse Route Information

– NE3 Ingress Node

– Out Label: 21

– NE2 Transit Node

– In Label: 21

– Out Label: 31

– NE1 Egress Node

– In Label: 31

Step 4 Creating Protection Tunnel.

1. Create protection Tunnel by following Step 3.1 toStep 3.4.


l General Attributes

– Tunnel ID: 120 (Positive), 121 (Reverse)

– Name: Protection Tunnel-Positive, Protection Tunnel-Reverse

– Signal Type: Static


– EXP:-

– Bandwidth (kbit/s): No Limit

l Node Information

– Ingress Node: NE1

– Egress Node: NE3

– Transit Node: NE6, NE5, NE4

l For the route information, see Table 6-4.

----End

6.10.4 Configuring a Static MPLS Tunnel on a Per-NE BasisThis section describes how to configure the static MPLS Tunnel in the example on a per-NEbasis.



6-35




Procedure



Apply.





l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6









Configuration Guide


Issue 06 (2009-06-01)








l IP Mask: 255.255.255.252













6-37

l NE5-3-EG16-1(Port-1)

Max Reserved Bandwidth (kbit/s): 1000000

IP Address: 10.0.4.2

l NE6-4-EFG2-1(Port-1)






Step 3 Creating Working MPLS Tunnels.

1. Select NE1 in the NE Explorer . Choose Configuration > MPLS Management >Unicast Tunnel Management from Function Tree. Click New and the New UnicastTunnel dialog box is displayed.

2. Configure parameters for the positive tunnel and reverse tunnel such as Tunnel ID, Tunnelname, port and labels. Click OKto finish creating the ingress node.


l Tunnel ID: 100(Positive), 101(Reverse)

l Tunnel Name: Working Tunnel-Positive, Working Tunnel-Reverse

l Node Type: Ingress(Positive), Egress(Reverse)


l Out Board/Logic Interface Type: 4-EFG2 (The source board of the Tunnel.)

l Out Port: 1(Port-1) (The source port of the Tunnel.


Configuration Guide


Issue 06 (2009-06-01)

l Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on thetunnel.)

l Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.)

l Tunnel Type: E-LSP– E-LSP indicates that the tunnel determines the scheduling priority and discard


l EXP: none (Set the tunnel priority according to networking planning.)

3. In the NE Explorer, select NE2. Then, configure the Tunnel parameters of the transit nodeby following Step 3.1 to Step 3.2.

Set related parameters and ensure that the general information of the tunnel is the same asthat on NE1. The configuration parameters are as follows:l Node Type: Transit (NE2 is a transit node on the tunnel.)

l In Board/Logic Interface Type: 3-EG16

l In Port: 1(Port-1)

l In Label: 20 (Positive), 21 (Reverse)

l Out Board/Logic Interface Type: 1-EX2

l Out Port: 1(Port-1)

l Out Label: 30 (Positive), 31 (Reverse)

l Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse)

l Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node onthe tunnel.)

l Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4. In the NE Explorer, select NE3. Then, configure the Tunnel parameters of the egress nodeby following Step 3.1 to Step 3.2.



6-39

Set related parameters and ensure that the general information of the tunnel is the same asthat on NE1. The configuration parameters are as follows:l Node Type: Egress (NE3 is a terminal node on the tunnel.)

l In Board/Logic Interface Type: 1-EX2


l In Label: 30(Positive), Out Label: 31 (Reverse)

l Next Hop Address: -(Positive), 10.0.1.1 (Reverse)

l Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

Step 4 Creating Protection Tunnel.1. Display the NE Explorer for NE1, NE6, NE5, NE4, and NE3 separately. Perform Step

3.1 through Step 3.4 to create the ingress node, transit node, and egress node on the bypasstunnel.


l Tunnel Name: Protection Tunnel-Positive, Protection Tunnel-Reverse

l Bandwidth(kbit/s): No Limit

l Tunnel Type: E-LSP

l EXP: none


----End

6.11 Parameter DescriptionThis section describes the parameters related to the MPLS Tunnel configuration.


Configuration Guide


Issue 06 (2009-06-01)

Table 6-5 Descriptions of the parameters for the Dynamic Tunnel in the General Attributestab


Tunnel ID Example: 5 Set an ID for the tunnel.

Name Character string Set a name for the tunnel.

Direction Unidirectional The direction of the tunnel.The unidirectional tunnelindicates the tunnel from theingress node to the egressnode.

Signal Type Static, Dynamic Set the signal type of thetunnel to Dynamic.

Scheduling Type E-LSP Set the scheduling type.

EXP 0, 1, 2, 3, 4, 5, 6, 7, None The E-LSP supports the EXPpriority. 7 indicates thehighest priority.

Bandwidth (kbit/s) Example: 1024 Set the bandwidth of thetunnel.

Customer Character string Specify the customer.

Remarks Character string Make remarks.

Table 6-6 Descriptions of the parameters for the Dynamic Tunnel in the Select Node tab


Source Node Example: NE2 Set the source node of thetunnel.

Sink Node Example: NE3 Set the sink node of thetunnel.When Specify IP Address isselected, you can set the IPaddress for the sink node.NOTE

When you create a reversetunnel, Specify IP Addresscannot be selected.



6-41

Table 6-7 Descriptions of the parameters for the Dynamic Tunnel in the Positive RouteConstraint (Reverse Route Constraint)tab


Serial NO. Example: 1 Display the sequence forcreating the route constraint.

Route Constraint Port IPAddress

Example: 192.168.2.1 Set the IP address of the routeconstraint port.


Configuration Guide


Issue 06 (2009-06-01)


Rerouting Mode Excluded, Include Loose,Include StrictDefault: Excluded

Set the rerouting mode.l Excluded: The tunnel does

not involve the routeconstraint port.

l Include Loose indicatesthat the tunnel musttraverse the ports withRoute Constraint PortIP Address and musttraverse the constraintports in the same sequencein which the ports areadded into the constraintlist. There can be multiplehops between IncludeLoose constraint ports.That is, the number ofhops along the tunnel canbe larger than the numberof constraint ports addedin the constraint list for thetunnel.

l Include Strict indicatesthat the tunnel musttraverse the ports withRoute Constraint PortIP Address and musttraverse the constraintports in the same sequencein which the ports areadded into the constraintlist. There can be only onehop between IncludeStrict ports. That is, theInclude Strict constraintport must be directlyconnected to the existingconstraint port.

NOTEIf the rerouting mode is set toInclude Strict or Include Loose,the route constraint port IPaddress should be in sequence.



6-43

Table 6-8 Descriptions of the parameters for the Dynamic Tunnel in the Priority tab


Setup Priority 0-7Default: 7

Set the setup priority.The number 0 indicates thehighest priority.The setup priority indicatesthe sequence for setting updynamic tunnels in one link.

Hold Priority 0-7Default: 0

Set the hold priority.The number 0 indicates thehighest priority.NOTE

For a dynamic tunnel, the holdpriority should not be higherthan the setup priority.Otherwise, a priority error isreported.

Color (0x) Example: 4 Set the color of the dynamictunnel.

Mask (0x) Example: 1 Set the mask of the dynamictunnel.

Tunnel Type Primary Tunnel, BypassTunnel

Set the tunnel type.Meanwhile, if bypass tunnelis enabled, other parametersin the Fast Re-Route areacannot be set.

Re-Route Checked, Unchecked Set whether to enable theprotection function of thererouting.

Table 6-9 Descriptions of the parameters for the Dynamic Tunnel in the Fast Re-Route tab


Fast Re-Route Checked, Unchecked If this function is enabled, theservice can be rerouted to thebypass tunnel when thecurrent tunnel fails.If this function is not enabled,FRR Type, FRR ProtectionType, and FRR Bandwidthcannot be set.

FRR Type facility Mode Set the type of the FRR.


Configuration Guide


Issue 06 (2009-06-01)


FRR Protection Type Protection Link Mode,Protection Node Mode

Set the protection type of theFRR.

FRR Bandwidth (kbit/s) Example: 1024 Set the bandwidth of theFRR.

Table 6-10 Descriptions of the parameters for the Static Tunnel in the General Attributes tab


Tunnel ID Example: 51-65535

Sets an ID for the tunnel.The tunnel ID can beallocated automatically.

Name Character string64 bytes

Sets a name for the tunnel.

Direction Unidirectional Displays the direction of thetunnel.The unidirectional tunnelindicates the tunnel from theingress node to the egressnode.

Signal Type Static, Dynamic Sets the signal type of thetunnel to Static.

Scheduling Type E-LSP Sets the scheduling type.


Bandwidth (kbit/s) 128 to 4294967295 Sets the bandwidth of thetunnel.

Customer Character string Specifies the customer.

Remarks Character string Makes remarks.

Table 6-11 Descriptions of the parameters for the Static Tunnel in the Select Nodes tab


Available NE Example: NE2 Displays the NEs availablefor creating the tunnel.

Ingress Example: NE3 Sets the ingress node of thetunnel.



6-45


Egress Example: NE4 Sets the egress node of thetunnel.

Transit Example: NE5 Sets the transit node of thetunnel.

Table 6-12 Descriptions of the parameters for the static tunnel in the Route Information tab


Node Example: NE2 Displays the nodes where thetunnel is created.

Location Ingress, Egress, Transit Displays position of the node.l Ingress indicates the

ingress node.l Egress indicates the egress

node.l Transit indicates the pass-

through node.

In Port Example: 3-EG16-10(PORT-10)

Sets the ingress port.NOTE

The ingress node does notsupport the setting of theingress port.

In Label 16-1048575Default: 16

Sets the ingress label of thetunnel.An ingress label is unique onan NE.

Out Port Example: 3-EG16-10(PORT-10)

Sets the egress port.NOTE

The egress node does notsupport the setting of the egressport.

Out Label 16-1048575Default: 16

Sets the egress label of thetunnel.An egress label is unique onan NE.

Next Hop Address Example: 192.168.1.2 Sets the IP address of the nexthop.NOTE

The egress node does notsupport the setting of the nexthop address.


Configuration Guide


Issue 06 (2009-06-01)


Filter Ports by Port Type Checked, Unchecked Sets whether ports arefiltered by port type. WhenFilter Ports by Port Type ischecked, ports are filtered onthe next hop and only theports of the specified type aredisplayed. When FilterPorts by Port Type isunchecked, all ports aredisplayed and this setting isapplied to the pass-through ofNEs.

Auto assign label Checked, Unchecked After you select Auto assignlabel, the systemautomatically assigns the InLabel and Out Label for thestatic Tunnel.

Table 6-13 Descriptions of the parameters for the Static Tunnel in the Tunnel Information tab


Positive Tunnel Information Tunnel ID, Name, SignalType, Scheduling Type,Bandwidth (kbit/s), IngressNode, Egress Node, TransitNode

Display information on thecreated positive tunnel.

Reverse Tunnel Information Tunnel ID, Name, SignalType, Scheduling Type,Bandwidth (kbit/s), IngressNode, Egress Node, TransitNode

Display information on thecreated reverse tunnel.

Table 6-14 Descriptions of the parameters for Basic Configuration


LSR ID Example: 10.70.73.156 In a PSN network, each NE isallocated with a unique LSRID.



6-47


Start of Global Label Space PTN 3900: 0 to 1015808Increment: 32768

Set and display the start of theglobal label space.The start of the global labelspace is the minimum valueof the ingress and egresslabels of the unicast tunnel.

Global Label Space Size PTN 3900: 32768 Display the size of the globallabel space.The global label space size isthe number of unicast tunnellabels.

Start of Multicast LabelSpace

PTN 3900: 0 to 32767Increment: 1

Set and display the start of themulticast label space.The start of the multicastlabel space is the minimumvalue of the ingress andegress labels of the multicasttunnel.

Table 6-15 Descriptions of the parameters for Static Tunnel


ID For example: 5 Display and set the tunnel ID.

Name For example: name164 bytes

Display and set the name ofthe static tunnel.

Enable State Enabled, Disabled Display and set the enablestatus of the static tunnel.Only Ingress Tunnelsupports to set the enablestatus.

Node Type Ingress, Egress, Transit Display the node type.l Ingress: ingress node

l Egress: egress node

l Transit: pass-throughnode

Direction Unidirectional Display the direction of thetunnel. Currently, only theunidirectional tunnel issupported.


Configuration Guide


Issue 06 (2009-06-01)


Bandwidth (kbit/s) 128 to 4294967295 Display and set thebandwidth of the statictunnel.

In Board/Logic InterfaceType

For example: Slot-BoardName

Display and set the in boardor logic interface type.

Bandwidth Remaining (kbit/s)

For example: 10240 Display and set the remainingbandwidth of the statictunnel.

In Port For example: Slot-BoardName-Port(Port No.)

Display and set the ingressport of the static tunnel.The egress node and transmitnode support the setting ofthe ingress port, but theingress node does not.

In Label 16 to 1048575 Display and set the ingresslabel of the tunnel.The egress node and transmitnode support the setting ofthe ingress label, but theingress node does not.

Out Board/Logic InterfaceType

For example: Slot-BoardName

Display and set the out boardor logic interface type.

Out Port For example: Slot-BoardName-Port(Port No.)

Display and set the egressport of the static tunnel.The ingress node andtransmit node support thesetting of the egress port, butthe egress node does not.

Out Label 16 to 1048575 Display and set the egresslabel of the tunnel.The ingress node andtransmit node support thesetting of the egress label, butthe egress node does not.

Next Hop Address For example: 192.168.0.2 Display and set the IP addressof the egress next hop of thetunnel.The ingress node andtransmit node support thesetting of the egress next hopaddress, but the egress nodedoes not.



6-49


Source Node For example: 192.168.0.1 Display and set the sourcenode of the tunnel.The egress node and transmitnode support the setting ofthe source node, but theingress node does not.

Sink Node For example: 192.168.0.2 Display and set the sink nodeof the tunnel.The ingress node andtransmit node support thesetting of the sink node, butthe egress node does not.

Tunnel Type E-LSP Display the type of the statictunnel.


Protection Group For example: 5 Display the protection groupthat the tunnel belongs to.

Vlan ID For example: 3 Display the VLAN ID. In thecase of an ingress tunnel, theVLAN ID can be set

New Reverse Tunnel Checked, Unchecked Select New Reverse Tunnelto set parameters of theforward and reverse tunnels.

Query Actual Bandwidth Checked, Unchecked When this parameter isselected, the actual effectivebandwidth is queried. Whenthis parameter is not selected,the configured bandwidth isqueried.

Table 6-16 Descriptions of the parameters for APS Protection


Protection Group ID For example: 1 Displays the ID of theprotection group.The system automaticallyallocates IDs to protectiongroups according to thesequence for creating them.


Configuration Guide


Issue 06 (2009-06-01)


Protection Type 1+1, 1:1 Selects a protection type.

Switching Mode Single-Ended, Dual-Ended Sets the switching mode,which is adopted in the caseof a fault on the tunnel.

Revertive Mode Non-Revertive, Revertive Sets whether the servicereverts to the originalworking tunnel after the faultis rectified. In the case of theRevertive mode, the servicereverts to the originalworking tunnel. In the case ofthe Non-Revertive mode,the service does not revert tothe original working tunnel.

WTR Time (m) 1 to 12Default: 5

Sets the wait-to-restore(WTR) time for theprotection group.

Hold-off Time (100 ms) 0 to 100Default: 0

Sets the hold-off time of theprotection group.

Protocol Status Enabled, Disabled Enables or disables theprotocol.

Switching Status For example: Up Displays the switching statusof the protection group.

Unit Working, Protection Displays whether a tunnel isthe working or protectiontunnel.

Active Tunnel Active, Standby Displays the tunnel that iscurrently used.

Tunnel Status Available, Unavailable Displays the status of theworking or protection tunnel.

Tunnel Type MPLS Tunnel, IP Tunnel,GRE Tunnel

Sets the type of the workingtunnel. The working tunnelcan be an MPLS tunnel, an IPtunnel, or a GRE tunnel. Theprotection tunnel can be anMPLS tunnel.

Ingress Tunnel For example: IP Tunnel-1(Source Node:1.0.0.3,SinkNode:1.1.0.3)

Selects the working andprotection ingress tunnels.



6-51


Egress Tunnel For example: Tunnel005-MPLS Tunnel-5(SourceNode:1.0.0.14,Sink Node:1.1.1.2)

Selects the working andprotection egress tunnels.

Table 6-17 Descriptions of the parameters for OAM


Tunnel ID Example: 3 Display the tunnel ID.

Tunnel Name Character string Display the tunnel name.

Node Type Ingress, Egress Display the node type.l Ingress: ingress node

l Egress: egress node

OAM Status Enabled, Disabled Set and display the OAMstatus.l Enabled: OAM-related

operations can beperformed.

l Disabled: OAM-relatedoperations cannot beperformed.

Detection Mode Auto-Sending, Manual Set and display the detectionmode.l Manual: The frequency

set by the user is used totest the connectivity of thetunnel.

l Auto-Sending: Thefrequency of the receivedpackets is used to test theconnectivity of the tunnel.

Detection Packet Type CV, FFD Set the detection packet typeon the ingress node.l CV: The detection

frequency is always thesame and cannot be set.

l FFD: The detectionfrequency can be set.


Configuration Guide


Issue 06 (2009-06-01)


Detection Packet Period (ms) 3.3, 10, 20, 50, 100, 200, 500 Set and display the detectionpacket period.If Detection Packet Periodis set to FFD, the detectionpacket period can be set. IfDetection Packet Period isset to CV, the detectionpacket period is always 1000.

Reverse Tunnel Example: 3 Select the reverse tunnel ID.

CV/FFD Status Stop, Start Display the CV/FFD status.

LSP Status Near-End Available, Near-End Defect Available, Near-End Defect Unavailable,Near-End Unavailable,Remote Available, RemoteDefect Available, RemoteDefect Unavailable, RemoteUnavailable

Display the LSP status.

LSP Defect Type dServer, dLOCV,dTTSI_Mismatch,dTTSI_Mismerge, dExcess,dUnknown, SD, SF, BDI,FDI

Display the LSP defect type.

Disable LSP Duration (ms) 0-300000 Display the duration of thedisable status of the LSP.Disable LSP Durationindicates the duration whenthe tunnel is unavailable.

LSP Defect Location Example: 192.168.11.1 Display the LSP defectlocation.LSP Defect Locationidentifies the location of thedefect in the network byusing the IP address.

SD Threshold 0-100 Set and display the SDthreshold.This parameter can be setonly for the egress node of thetunnel.



6-53


SF Threshold 0-100 Set and display the SFthreshold.This parameter can be setonly for the egress node of thetunnel.SD ≤ SF

Source Node Example: 192.168.11.2 Display the Source Node ofthe tunnel.

Sink Node Example: 192.168.11.3 Display the Sink Node of thetunnel.


Configuration Guide


Issue 06 (2009-06-01)

7 Configuring an IP Tunnel

About This Chapter

When the services that cross an IP network need to be created, the OptiX PTN equipmentsupports carrying PWs over the IP tunnel. In this way, services can be transparently transmittedin an IP network.

7.1 IP TunnelIP tunnel can be used to carry the ATM PWE3 service or the CES service.

7.2 Creating IP TunnelsIn the offload scenario of a mobile communication system, you can transmit the client servicesby connecting an IP tunnel to the DSLAM.

7.3 Parameter DescriptionThis section describes the parameters related to the IP Tunnel configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 7 Configuring an IP Tunnel


7-1

7.1 IP TunnelIP tunnel can be used to carry the ATM PWE3 service or the CES service.

If ATM or CES emulation service that travels through an IP network is required, the PTNequipment can use the IP tunnel to carry the service. This complies with RFC 4023 as shown inFigure 7-1. In the case of the IP tunnel, the situation is similar to that where "IP header" replacesthe MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network. An ATMemulation service can be provided between NE A and NE B, even though the IP network betweenNE A and NE B does not support the MPLS.

Figure 7-1 ATM PWE3 over IP tunnel

ATMswitch

IP network

ATME1/STM-1

ATMPWE3

PW LabelIP

Ethernet

ATME1/STM-1

ATMswitchPTN Router PTN

ATMPWE3

PW LabelIP

Ethernet

Router

NE A NE B

7.2 Creating IP TunnelsIn the offload scenario of a mobile communication system, you can transmit the client servicesby connecting an IP tunnel to the DSLAM.


l The static route must be configured.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE TunnelManagement > IP Tunnel Management from the Function Tree.

Step 2 Click New and the Create IP Tunnel dialog box is displayed.

7 Configuring an IP TunnelOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

NOTESink Port IP Address must be consistent with Sink Node IP in Static Route Management.

Step 3 Set parameters. For details on the parameters for IP tunnel, see Table 7-1.

Step 4 Click OK. A prompt appears indicating that the operation was successful. Click Close.


Step 6 Click Apply.

----End

7.3 Parameter DescriptionThis section describes the parameters related to the IP Tunnel configuration.

Table 7-1 Descriptions of the parameters for IP Tunnel Management


Tunnel ID Example: 5 Set and display the tunnel ID.You can also select theautomatic allocation.

Source Board Example: Slot-Board Name Set and display the sourceboard.

Source Port Example: Port(Port No.) Set and display the sourceport.

Destination IP Example: 1.16.0.3 Set and display the LSR ID ofthe sink NE.

Vlan ID Example: 5 Set and display the VLANID.

Protection Group Examle: 1 Display the protection group.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 7 Configuring an IP Tunnel


7-3

8 Configuring a GRE Tunnel

About This Chapter

When the services that cross an IP network need to be created, the OptiX PTN equipmentsupports carrying ATM PWE3 services over generic routing encapsulation (GRE) tunnels. Inthis way, services can be transparently transmitted in an IP network.

8.1 GRE TunnelGRE tunnel can be used to carry the PWE3 service or the CES service.

8.2 Creating GRE TunnelsIn the offload scenario of a mobile communication system, you can transmit the client servicesby connecting an GRE tunnel to the digital subscriber line access multiplexer (DSLAM).

8.3 Parameter DescriptionThis section describes the parameters related to the GRE Tunnel configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 8 Configuring a GRE Tunnel


8-1

8.1 GRE TunnelGRE tunnel can be used to carry the PWE3 service or the CES service.

If ATM or CES emulation service that travels through an IP network is required, the PTNequipment can use the GRE tunnel to carry the service. This complies with RFC 4023 as shownin Figure 8-1. In the case of the GRE tunnel, the situation is similar to that where "GREencapsulation + IP header" replaces the MPLS external label (MPLS tunnel label) to establisha tunnel in the IP network. An ATM emulation service can be provided between NE A and NEB, even though the IP network between NE A and NE B does not support the MPLS.

Figure 8-1 ATM PWE3 over GRE tunnel

ATMswitch

IP network

ATMPWE3

PW LabelGRE

ATME1/STM-1

ATMswitchPTN Router PTNRouter

IPEthernet

ATMPWE3

PW LabelGRE

IPEthernet

ATME1/STM-1

NE A NE B

8.2 Creating GRE TunnelsIn the offload scenario of a mobile communication system, you can transmit the client servicesby connecting an GRE tunnel to the digital subscriber line access multiplexer (DSLAM).


l The static route must be configured.

Procedure

Step 1 In the NE Explorer, click an NE. Choose Configuration > IP/GRE Tunnel Management >GRE Tunnel Management from the Function Tree.

Step 2 Click New and the Create GRE Tunnel dialog box is displayed.

8 Configuring a GRE TunnelOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

NOTESink Port IP Address must be consistent with Sink Node IP in Static Route Management.

Step 3 Set parameters.For details on the parameters for GRE tunnel, seeTable 8-1.



Step 6 Click Apply.

----End

8.3 Parameter DescriptionThis section describes the parameters related to the GRE Tunnel configuration.

Table 8-1 Descriptions of the parameters for GRE Tunnel Management


Tunnel ID Example: 5 Display and set the tunnel ID.You can also select theautomatic allocation.

Source Board Example: Slot-Board Name Display and set the sourceboard.

Source Port Example: Port(Port No.) Display and set the sourceport.

Destination IP Example: 1.16.0.3 Display and set the LSR ID ofthe sink NE.

Vlan ID Example: 5 Display and set the VLANID.

Protection Group Example: 1 Display the protection group.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 8 Configuring a GRE Tunnel


8-3

9 Configuring a CES Service

About This Chapter

This section describes the basic information about the CES service and illustrates how toconfigure the CES service.

9.1 CES Service TypeCircuit emulation service (CES) applies the PWE3 emulation technology. For a CES service,the PWE3 packet headers contain the frame format information, alarm information, signalinginformation, and synchronous timing information of the TDM service flow. After encapsulatedby the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRETunnel in the PSN network. When reaching the PW egress, the PW packets are decapsulated torebuild the TDM circuit-switching service flow.

9.2 Configuration Flow of CES ServicesThis section describes the operation tasks for configuring CES services, and relations amongthese tasks. When configuring or managing CES services, follow the configuration flows.

9.3 CES Service Operation TasksThe main operation tasks of configuring CES services include fast creating point-to-point CESservices and creating point-to-point CES services on a per-NE basis.

9.4 Configuration Case of the UNI-UNI CES ServiceThis section describes the configuration case of the UNI-UNI CES service.

9.5 Configuration Case of the UNI-NNI CES ServiceThis section describes the configuration case of the UNI-NNI CES service.

9.6 Checking the Correctness of the Service ConfigurationAfter the CES service is configured, you need to check the correctness of the serviceconfiguration. You can check the correctness of the CES service configuration as follows: attacha 2M BER tester at the CES port and then perform loopbacks at the remote end.

9.7 Parameter DescriptionThis section describes the parameters related to the CES service configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 9 Configuring a CES Service


9-1

9.1 CES Service TypeCircuit emulation service (CES) applies the PWE3 emulation technology. For a CES service,the PWE3 packet headers contain the frame format information, alarm information, signalinginformation, and synchronous timing information of the TDM service flow. After encapsulatedby the protocol, the PW packets are transported over the MPLS tunnel, IP Tunnel, GRETunnel in the PSN network. When reaching the PW egress, the PW packets are decapsulated torebuild the TDM circuit-switching service flow.

Application ModeThe CES service allows a metropolitan Ethernet network (MEN) carrier to provide TDM servicesto customers that have only the TDM equipment. This enlarges the service range and the numberof users of the MEN carriers, and provides a way to transform the traditional circuit network tothe wideband data network.

The CES service mainly applies to the wireless service and the enterprise private line service.The application scenarios include UNI-NNI and UNI-UNI, as shown in Figure 9-1.l UNI-NNI CES service: The PTN equipment accesses the TDM services of customers by

using the TDM or channelized STM interface. The CES PW can be created between thePTN equipments to emulate the end-to-end TDM service. To customers, the CES servicesare similar to actual TDM services.

l UNI-UNI CES service: The PTN equipment accesses the TDM services by using a singlepoint.

NOTE

Now only the point-to-point service is supported. That is, the service of one E1 interface mapping to onePW is supported. But converged services of several TDM interfaces mapping to one PW are not supported.

9 Configuring a CES ServiceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

Figure 9-1 CES service networking sample

UNI-NNI

UNI-UNI

BTS

BSC

BTS

BTS

TDM Link

PWcSTM Link

PE

PE

PE

Tunnel

Emulation Mode

The PTN equipment supports two types of CES services: structure-aware TDM circuit emulationservice over packet switched network (CESoPSN) and structure-agnostic TDM over packet(SAToP).

In the CESoPSN mode:

l The PTN equipment senses frame structures, frame alignment modes and timeslots in theTDM circuit.

l The PTN equipment processes the overhead and extracts the payload in TDM frames. Then,the PTN equipment delivers the timeslot of each channel to the packet payload accordingto certain sequence. As a result, the service in each channel in the packet is fixed and visible.

l Each Ethernet frame that carries the CES service loads TDM frames of a fixed number.Usually the loading time is 0.125 to 5 ms.

In the SAToP mode:



9-3

l The equipment regards TDM signals as constant rate bit flows, instead of sensing structuresin the TDM signals. The entire bandwidth of TDM signals is emulated.

l The overhead and payload in the TDM signal are transparently transmitted.l The Ethernet frame carries the CES service. Usually the loading time is 1 ms.

In the CESoPSN mode, for the free 64 kbit/s timeslot in TDM E1 signal, the PTN equipmentprovides the compression function to save the transmission bandwidth. The timeslot numberranges from 0 to 31. The timeslot number of 0 indicates a reserved timeslot for transmittingsignaling.

Service ClockThe TDM service has high requirements for the clock synchronization. The PTN equipmentprovides solution to the CES service clock synchronization. See Table 9-1.

Table 9-1 CES service clock type

SynchronizationSolution

PRC AccessPosition

Whether the Clock isTransmitted inCarrying Ethernet

Description

ExternalClockSynchronization

PE equipment No Introduces the PRC/GPS clockto the PE equipment, and usesthis clock as the transmit clockof the CES port service(retiming).The CE system clocksynchronizes the PE serviceclock. This realizes thesynchronization of all PEs andCEs, and ensures that transmitclocks of TDM services on allCEs and PEs are synchronous,and indirectly realizes thetransfer of the TDM serviceclock.See Figure 9-2.

Figure 9-2 External Clock synchronization of CES service clock

CE CEPE PECES

PRC/GPS PRC/GPS

TDM+Clock TDM+Clock


Configuration Guide


Issue 06 (2009-06-01)

9.2 Configuration Flow of CES ServicesThis section describes the operation tasks for configuring CES services, and relations amongthese tasks. When configuring or managing CES services, follow the configuration flows.

Configure and manage UNI-UNI CES services by following the configuration flow shown inFigure 9-3.

Configure and manage UNI-NNI CES services by following the configuration flow shown inFigure 9-4.

Figure 9-3 UNI-UNI CES service configuration flow

Creating a Network

Configure UNI-UNI CES Service

StartRequired

Optional

Configure inferface

End

Table 9-2 Tasks for configuring the UNI-UNI CES service

Task Remarks

1. CreatingNetwork

To create a network, you need to create NEs, configure NE data, createfibers, and configure the clock.

2. Configuring theInterface

Use the E1 board or the channelized STM-1 board to access the CESservice from the BTS.

3. Configuring theUNI-UNI CESService

To configure the UNI-UNI CES service, you need to specify the serviceID and service name, select the source board and the sink board.



9-5

Figure 9-4 UNI-NNI CES service configuration flow

Creating a Network

Configure inferface

Configure Control Plan

Configure UNI-NNI CES Service

StartRequired

Optional

Configure Tunnel

End

Table 9-3 Tasks for configuring the UNIs-NNI CES service

Task Remarks

1. CreatingNetwork


2. Configuringthe LSR ID

Configure the LSR ID of the NE and start of global label space.

3. Configuringthe Network-Side Interface

Set the general attributes and Layer 3 attributes (tunnel enable status andIP address) for interfaces to carry the tunnel carrying.


Configuration Guide


Issue 06 (2009-06-01)

Task Remarks

4. Configuringthe ControlPlane

Set the protocol parameters related to the control plane to create thetunnel.l To create a static MPLS tunnel to transmit the ATM service, the

parameters related to the control plane need not be set.l To create a dynamic MPLS tunnel to transmit the ATM service, you

need to set the following protocol parameters:1. Set the IGP-ISIS protocol parameters.2. Set the MPLS-RSVP protocol parameters.To create a dynamic PW to transmit the service, you need to set theparameters related to the MPLS-LDP protocol.

l To create an IP Tunnel or GRE Tunnel to transmit the ATM service,you need to Configuring Static Routes.

5. Configuring theTunnel

A tunnel transmits the service.l If an static MPLS tunnel is required, configure an MPLS tunnel in the

per-NE or per-trail mode. Specify the tunnel ID, set signaling typeto static, name the service, and specify the ingress node, egress node,and transit node.

l If a dynamic MPLS Tunnel is required, name the service, setsignaling type to dynamic, and specify the source node and sink nodefor the tunnel.

l If an IP Tunnel or GRE Tunnel is required, select the source board,source port, and IP address of the sink port.

6. Configuringthe ServiceInterface

Use the E1 board or the channelized STM-1 board to access the CESservice from the BTS.

7. Configuringthe UNIs-NNICES service

1. Create a CES service: Set the service ID and specify a service name.2. Setting the source: Select the board and the specific channel.3. Configure a PW: Set the PW type, PW label, and tunnel type.4. Set advanced attributes: Set the jitter buffer time, packet loading time,

and clock mode.

9.3 CES Service Operation TasksThe main operation tasks of configuring CES services include fast creating point-to-point CESservices and creating point-to-point CES services on a per-NE basis.

9.3.1 Creating a UNI-UNI CES Service by Using the Trail FunctionIn an operation interface of the T2000, you can directly configure the attributes of the sourceand sink nodes and the PW of a CES service by using the T2000 trail function. In this way, aCES service can be fast created.

9.3.2 Creating a UNI-NNI CES Service by Using the Trail Function



9-7

In an operation interface of the T2000, you can directly configure the attributes of the sourceand sink nodes and the PW of a CES service by using the T2000 trail function. In this way, aCES service can be fast created.

9.3.3 Creating a UNI-UNI CES Service on a Per-NE BasisIf you create a CES service on a per-NE basis, you need to create relevant attributes of the serviceseparately on the source and sink nodes of the service.

9.3.4 Creating a UNI-NNI CES Service on a Per-NE BasisIf you create a CES service on a per-NE basis, you need to create relevant attributes of the serviceseparately on the source and sink nodes of the service. After the CES service is created, thecorresponding PW is automatically created.

9.3.1 Creating a UNI-UNI CES Service by Using the Trail FunctionIn an operation interface of the T2000, you can directly configure the attributes of the sourceand sink nodes and the PW of a CES service by using the T2000 trail function. In this way, aCES service can be fast created.


l The ports must be configured.

Procedure

Step 1 Choose Trail > PTN Service > CES Service Creation from the Main Menu. The Create CESService dialog box is displayed.

Step 2 In the Create CES Service dialog box, create the UNI-UNI service.


Configuration Guide


Issue 06 (2009-06-01)

NOTEFor the UNI-UNI service, you need not specify a PW and set parameters of the PW.

Step 3 Set attributes related to the UNI-UNI service.1. In Basic Information, set the basic attributes of the CES service. For details on the

parameters for general attributes of the CES service, see Table 9-9.

NOTE

Note the following when setting the parameters:

Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assignsthe service ID. If not, you need to manually assign the service ID.

2. In Source, click Browse. Then select source board, source port and lower order path of theservice in the Please select the source timeslot dialog box. In Sink, click Browse andselect the sink NE, sink port, higher order path and lower order path of the service. Fordetails on the parameters for source/sink port attributes of the CES service, see Table9-9.



9-9

NOTE


The source and sink NEs of the UNI-UNI service need to be the same.

3. Click Apply, and the Operation Result dialog box is displayed, indicating that theoperation is successful. Click Close.

----End

9.3.2 Creating a UNI-NNI CES Service by Using the Trail FunctionIn an operation interface of the T2000, you can directly configure the attributes of the sourceand sink nodes and the PW of a CES service by using the T2000 trail function. In this way, aCES service can be fast created.


l The DCN of the port with the CES service must be disabled.

l A tunnel must be created. For configuration method, see 6.3 Creating a Static MPLSTunnel by Using the Trail Function.

Procedure

Step 1 Choose Trail > PTN Service > CES Service Creation from the Main Menu. The Create CESService dialog box is displayed.

Step 2 In the Create CES Service dialog box, create the UNI-NNI service.


Configuration Guide


Issue 06 (2009-06-01)

NOTEFor the UNI-NNI service, you need specify a PW and set parameters of the PW.

Step 3 Set attributes related to the UNI-NNI service.1. In Basic Information, set the basic attributes of the CES service. For details on the

parameters for general attributes of the CES service, see Table 9-9.

NOTE


Service ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assignsthe service ID. If not, you need to manually assign the service ID.

2. In Source, click Browse and select the source NE, source port, higher path and lower pathof the service. In Sink, click Browse and select the sink NE, sink port, high path and lowpath of the service. For details on the parameters for source/sink port attributes of CESservice, see Table 9-9.

NOTE


When you create a UNI-NNI CES service, the source and sink NEs cannot be the same.

3. In PW, set the attributes of the PW. For details on the parameters for PW attributes of CESservice, see Table 9-11.



9-11

NOTE


l ID(e.g.1,3-6): After you select Automatically Assigned, the system automatically assigns theID for the PW that carries the services. If not, you need to manually assign the ID for the PW.

l When Protocol Type is set to Static, you need to set the uplink and downlink labels. When it isset to Dynamic, the system automatically assigns the uplink and downlink labels.

l The Emulation Mode includes structure-aware TDM circuit emulation service over packetswitched network (CESoPSN) and structure-agnostic TDM over packet (SAToP). You canconfigure the 64K Timeslot function for the CESoPSN but not for the SAToP.

l Uplink Label/Source Port(e.g.16,33-36): The label that indicates a service is encapsulated intoa PW.

l Downlink Label/Sink Port(e.g.16,33-36): The label that indicates the service is decapsulatedfrom the PW.

l After you select Auto assign label, the system automatically assigns the Uplink Label/SourcePort(e.g.16,33-36) and Downlink Label/Sink Port(e.g.16,33-36) for the PW.

4. Click Advanced and the Advanced Attribute dialog box is displayed. For details on theparameters for advanced attributes of CES service, see Table 9-10.

NOTE


Generally, Packet Loading Time(us) for carrying the CES service packets is 1 ms.

The value of Jitter Compensation Buffering Time(us) must be greater than the value of PacketLoading Time(us) on the opposite end.

5. Click OK.


----End

9.3.3 Creating a UNI-UNI CES Service on a Per-NE BasisIf you create a CES service on a per-NE basis, you need to create relevant attributes of the serviceseparately on the source and sink nodes of the service.

Prerequisite


The ports must be configured.


Configuration Guide


Issue 06 (2009-06-01)

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management fromthe Function Tree.

Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configurethe UNI-UNI service.

NOTE

l In the case of the UNI-UNI service, QoS and Advanced Attributes do not need to be set.

Step 3 Set attributes related to the UNI-UNI service. For details on the parameters for UNI-UNI serviceof CES, see Table 9-11.

1. Configure the parameters of the service.

NOTE


Mode: UNI-UNI.

2. Click Apply. A dialog box is displayed, indicating that the operation is successful. ClickClose.

----End

9.3.4 Creating a UNI-NNI CES Service on a Per-NE BasisIf you create a CES service on a per-NE basis, you need to create relevant attributes of the serviceseparately on the source and sink nodes of the service. After the CES service is created, thecorresponding PW is automatically created.



9-13


l The tunnel must be created. For configuration method, see 6.5 Creating an MPLS Tunnelon a Per-NE Basis.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management fromthe Function Tree.

Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configurethe UNI-NNI CES services.

NOTE

In the case of the UNI-NNI service, set QoS and Advanced Attributes.

Step 3 Set attributes related to the UNI-NNI service.1. Configure the parameters of the service. For details on the parameters for UNI-NNI service

of CES, see Table 9-11.


Configuration Guide


Issue 06 (2009-06-01)

NOTE


l Mode: UNI-NNI.

l In the case of PW Signaling Type, if you select Static, you need to set PW Ingress Label/Source Port(e.g.16,33-36) and PW Engress Label/Sink Port(e.g.16,33-36). If you selectDynamic, the system automatically allocates PW Ingress Label/Source Port(e.g.16,33-36) andPW Engress Label/Sink Port(e.g.16,33-36).

l PW Ingress Label/Source Port(e.g.16,33-36): the label that indicates a service is encapsulatedinto a PW.

l PW Engress Label/Sink Port(e.g.16,33-36): the label that indicates the service is decapsulatedfrom the PW.

l Tunnel: Select the tunnel to carry the services.

2. Click QoS and the QoS dialog box is displayed.

3. Set the parameters of QoS. For details on the parameters for QoS, see Table 9-12.

NOTE


EXP: Set the Ingress value only. 7 indicates the highest priority.

4. Click OK.5. Click Advanced Attributes, and the Advanced Attributes dialog box is displayed.

6. Configure parameters in the Advanced Attributes dialog box. For details on the parametersfor advanced attributes, see Table 9-13.



9-15

NOTE


Generally, Packet Loading Time(us) for carrying the CES service packets is 1 ms.

The value of Jitter Compensation Buffering Time(us) must be greater than the value of PacketLoading Time(us) on the opposite end.

7. Click OK.8. Click Apply. A dialog box is displayed, indicating that the operation is successful. Click

Close.

----End

9.4 Configuration Case of the UNI-UNI CES ServiceThis section describes the configuration case of the UNI-UNI CES service.

9.4.1 Case DescriptionThis section describes the application scenario of the UNI-UNI CES service, including thenetworking diagram and service planning.

9.4.2 Service PlanningTo transport the CES services between BTS and BSC, two CES services should be created.

9.4.3 Configuring CES Services by Using the Trail FunctionThis section describes how to configure the two CES services in the example by using the trailfunction.

9.4.4 Configuring CES Services on a Per-NE BasisThis section describes how to configure the two CES services in the example on a per-NE basis.

9.4.1 Case DescriptionThis section describes the application scenario of the UNI-UNI CES service, including thenetworking diagram and service planning.

Figure 9-5 shows the networking diagram of the UNI-UNI CES service. shows the networkingdiagram of the UNI-UNI CES service. A CES service is present between each BTS and BSC.On NE1, the OptiX PTN 1900 accesses the services from the base station.

Figure 9-5 Networking of the CES service

BSC

BTS

BTS

NE1


Configuration Guide


Issue 06 (2009-06-01)

Figure 9-6 shows the NE planning diagram.

Figure 9-6 NE planning diagram

BSC

BTS

BTS

NE1

1-CXP-MD1-3-L12 1-CXP-MD1-5-L12

9.4.2 Service PlanningTo transport the CES services between BTS and BSC, two CES services should be created.

The UNI-UNI is used to access the local service, and then the UNI-UNI transmits the accessedservice to BSC. A CES service is present between each BTS and BSC. Two E1 timeslots of theCES service are fully used. The service shown in Figure 9-5 is taken as an example.

Table 9-4 lists the configuration parameters of NE1.

Table 9-4 Configuration parameters of NE1

Attribute Value Value

NE NE1 NE1

Level E1 E1

Service ID 7 8

Service Name CES Local Service 1 CES Local Service 2

Mode UNI-UNI UNI-UNI

Source Board 3-L12 3-L12

Source High Channel - -

Source Low Channel 1 2

Sink Board 5-L12 5-L12

Sink High Channel - -



9-17


Sink Low Channel 1 2

9.4.3 Configuring CES Services by Using the Trail FunctionThis section describes how to configure the two CES services in the example by using the trailfunction.

Prerequisite




Procedure

Step 1 Configure E1 interface: BTS-side E1 interface and BSC-side E1 interface.1. Configure the BTS-side E1 interface.

a. In the NE Explorer, select an NE1 and choose Communication > DCNManagement from the Function Tree. Click the Port Settings tab.

b. Click E1. Select 3-L12-1(Port-1) and 3-L12-2(Port-2), and set the Enabled Status toDisabled.

c. Click Apply.d. In the NE Explorer, select NE1 and choose Configuration > Interface

Management > PDH Interface from the Function Tree. Then, configure the BTS-side interface.

e. Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set the Port Mode to Layer1. Set theparameters as required.

The configuration parameters are as follows:l Port: 3-L12-1(Port-1) and 3-L12-2(Port-2)

l Name: port1, port2 (Set the port name as required. The port name distinguishesthe port from other ports and helps to query the port.)

l Port Mode: Layer 1 (The port transmits E1 signals.)

l Encapsulation: Null

l Channelize: No

f. Click Apply, and the Operation Result dialog box is displayed, indicating that theoperation is successful. Click Close.

g. Click Advanced Attributes tab, Select 3-L12-1(Port-1) and 3-L12-2(Port-2). Set theFrame Format to Unframe.


Configuration Guide


Issue 06 (2009-06-01)

h. Click Apply, and the Operation Result dialog box is displayed, indicating that theoperation is successful. Click Close.

2. Configure the BSC-side E1 interface.




Management > PDH Interface from the Function Tree. Then, configure the BSC-side interface.

e. Select 5-L12-1(Port-1) and 5-L12-2(Port-2). Set the Port Mode to Layer1. Set theparameters as required.The configuration parameters are as follows:l Port: 5-L12-1(Port-1) and 5-L12-2(Port-2)




l Channelize: No




Step 2 Creating UNI-UNI CES Local service 1.1. On the Main Topology, choose Trail > Emulation Service Creation > CES Service

Creation, The Create CES Service dialog box is displayed.2. Set the parameters of CES service.



9-19

The configuration parameters are as follows:l Basic Information

– Service Level: E1

– Service Name: CES Local Service 1

– Service ID: 7

l Source– NE: NE1

– Port: 3-L12

– High Path: - (In the case of the line port, set the VC-4 higher order path number.)

– Low Path: 1(In the case of the E1 port, set the E1 port number. In the case of theline port, set the VC-12 lower order path number.)

l sink– NE: NE1

– Port: 5-L12

– High Path: -

– Low Path: 1

3. Click OK, and the Operation Result dialog box is displayed, indicating that the operationis successful. Click Close.

Step 3 Creating UNI-UNI CES Local service 1. Set the parameters related to the CES service byfollowing Step 2.1 to Step 2.3.



Configuration Guide


Issue 06 (2009-06-01)

l Basic Information– Service Level: E1

– Service Name: CES Local Service 2

– Service ID: 8

l Source– NE: NE1

– Port: 3-L12

– High Path: - (In the case of the line port, set the VC-4 higher order path number.)

– Low Path: 2 (In the case of the E1 port, set the E1 port number. In the case of the lineport, set the VC-12 lower order path number.)

l sink– NE: NE1

– Port: 5-L12

– High Path: -

– Low Path: 2

----End

9.4.4 Configuring CES Services on a Per-NE BasisThis section describes how to configure the two CES services in the example on a per-NE basis.




Procedure

Step 1 Configure E1 interface: BTS-side E1 interface and BSC-side E1 interface.1. Configure the BTS-side E1 interface.




Management > PDH Interface from the Function Tree. Then, configure the BTS-side interface.




9-21


l Port: 3-L12-1(Port-1) and 3-L12-2(Port-2)




l Channelize: No




2. Configure the BSC-side E1 interface.



c. Click Apply.

d. In the NE Explorer, select NE1 and choose Configuration > InterfaceManagement > PDH Interface from the Function Tree. Then, configure the BSC-side interface.



l Port: 5-L12-1(Port-1) and 5-L12-2(Port-2)




l Channelize: No




Step 2 Creating UNI-UNI CES Local service 1.

1. In the NE Explorer, Choose Configuration > CES Service Management from theFunction Tree.

2. Click New, Set the parameters of CES service.


Configuration Guide


Issue 06 (2009-06-01)

The configuration parameters are as follows:l Service Level: 7

l Service Name: CES Local Service 1

l Level: E1

l Mode: UNI-NNI

l Source Board: 3-L12

l Source High Channel: - (In the case of the line port, set the VC-4 higher order pathnumber.)

l Source Low Channel: 1 (In the case of the E1 port, set the E1 port number. In the caseof the line port, set the VC-12 lower order path number.)

l Sink Board: 5-L12

l Sink High Channel: -

l Sink Low Channel: 1


Step 3 Creating UNI-UNI CES Local service 2. Set the parameters related to the CES service byfollowing Step 2.1 to Step 2.3.




9-23

l Service Level: 8

l Service Name: CES Local Service 2

l Level: E1

l Mode: UNI-NNI


l Source High Channel: - (In the case of the line port, set the VC-4 higher order path number.)

l Source Low Channel: 2 (In the case of the E1 port, set the E1 port number. In the case of theline port, set the VC-12 lower order path number.)

l Sink Board: 5-L12

l Sink High Channel: -

l Sink Low Channel: 2

----End

9.5 Configuration Case of the UNI-NNI CES ServiceThis section describes the configuration case of the UNI-NNI CES service.

9.5.1 Case DescriptionThis section describes the UNI-NNI application scenarios of the CES service, including thenetworking diagram and service planning.UNI-NNI CES

9.5.2 Service PlanningThere are CES services between BTS and BSC. Two static MPLS tunnels are to be created. Oneis the working tunnel and the other is the protection tunnel. Then, the CES services can besecurely transmitted on the network.

9.5.3 Configuring CES Services by Using the Trail FunctionThis section describes how to configure the three CES services in the example by using the trailfunction.

9.5.4 Configuring CES Services on a Per-NE BasisThis section describes how to configure the three CES services in the example on a per-NE basis.

9.5.1 Case DescriptionThis section describes the UNI-NNI application scenarios of the CES service, including thenetworking diagram and service planning.UNI-NNI CES

Networking and Requirement

Between BTS and BSC, the CES service is transported through the PTN equipment, as shownin Figure 9-7. Two CES services are available between BTS and BSC that are connected toNE1. NE1 uses the OptiX PTN 1900 to access the services from the base stations, and NE2 andNE3 uses the OptiX PTN 3900. Tunnels should be configured between NE1 and NE3.

If the service requires high network security, configure the MPLS APS protection to ensureservice transmission.l Working tunnel: NE1-NE2-NE3. NE2 is a transit node.


Configuration Guide


Issue 06 (2009-06-01)

l Protection tunnel: NE1-NE6-NE5-NE4-NE3. NE6, NE5, NE4, and NE3 are transit nodes.When the working tunnel becomes faulty, the service on it is switched to the protectiontunnel for protection.

Figure 9-7 Networking diagram of the CES service


BTS

BSC

NE1NE2 NE3

NE4NE5 10GE ring on

convergence layerGE ring on

access layer

Working Tunnel

Protection Tunnel

Figure 9-8 shows the planning details of boards on the NE and interfaces on the boards.



BTS

BSC

NE1NE2

NE3

NE4NE5

NE6

4-EFG2-1(Port-1)10.0.0.16-L12

3-EG16-1(Port-1)10.0.0.2

1-EX2-1(Port-1)10.0.1.2

1-EX2-1(Port-1)10.0.1.1

6-MP1-1-CD1-1（Port-1）10.0.6.1

4-EFG2-2(Port-2)10.0.4.1

1-EX2-2(Port-2)10.0.2.1

1-EX2-1(Port-1)10.0.2.2

1-EX2-2(Port-2)10.0.3.11-EX2-2(Port-2)

10.0.3.23-EG16-1(Port-1)10.0.4.2

4-EFG2-1(Port-1)10.0.5.2

4-EFG2-2(Port-2)10.0.5.1



layer

Working Tunnel

Protection Tunnel



9-25

9.5.2 Service PlanningThere are CES services between BTS and BSC. Two static MPLS tunnels are to be created. Oneis the working tunnel and the other is the protection tunnel. Then, the CES services can besecurely transmitted on the network.




NE1 1.0.0.14-EFG2-1(Port-1) 10.0.0.1 255.255.255.252

4-EFG2-2(Port-2) 10.0.5.1 255.255.255.252

NE2 1.0.0.23-EG16-1(Port-1) 10.0.0.2 255.255.255.252

1-EX2-1(Port-1) 10.0.1.1 255.255.255.252

NE3 1.0.0.31-EX2-1(Port-1) 10.0.1.2 255.255.255.252

1-EX2-2(Port-2) 10.0.2.1 255.255.255.252

NE4 1.0.0.41-EX2-1(Port-1) 10.0.2.2 255.255.255.252

1-EX2-2(Port-2) 10.0.3.1 255.255.255.252

NE5 1.0.0.51-EX2-1(Port-1) 10.0.3.2 255.255.255.252

3-EG16-1(Port-1) 10.0.4.2 255.255.255.252

NE6 1.0.0.64-EFG2-1(Port-1) 10.0.5.2 255.255.255.252

4-EFG2-2(Port-2) 10.0.4.1 255.255.255.252

Table 9-6 lists the configuration parameters of Tunnels.



Tunnel ID 100 101 120 121





Signal Type Static Static Static Static

SchedulingType


Bandwidth(kbit/s)



Configuration Guide


Issue 06 (2009-06-01)


Ingress Node NE1 NE3 NE1 NE3

Transit Node NE2 NE2 NE6, NE5, NE4 NE4, NE5, NE6

Egress Node NE3 NE1 NE3 NE1

Ingress NodeRouteInformation

NE1l Out Port: 4-

EFG2-1(Port-1)

l Out Label:20

NE3l Out Port: 1-

EX2-1(Port-1)l Out Label: 21

NE1l Out Port: 4-

EFG2-2(Port-2)

l Out Label: 22

NE3l Out Port: 1-

EX2-2(Port-2)

l Out Label: 23

Transit NodeRouteInformation

NE2l In Port: 3-

EG16-1(Port-1)

l In Label: 20


l Out Label:30

NE2l In Port: 1-

EX2-1(Port-1)l In Label: 21


l Out Label: 31

NE6l In Port: 4-

EFG2-1(Port-1)

l In Label: 22


l Out Label: 32

NE5l In Port: 3-

EG16-1(Port-1)

l In Label: 32


l Out Label: 42

NE4l In Port: 1-

EX2-2(Port-2)

l In Label: 42


l Out Label: 52

NE4l In Port: 1-

EX2-1(Port-1)

l In Label: 23


l Out Label: 33

NE5l In Port: 1-

EX2-1(Port-1)

l In Label: 33


l Out Label: 43

NE6l In Port: 4-

EFG2-2(Port-2)

l In Label: 43


l Out Label: 53

Egress NodeRouteInformation

NE3l In Port: 1-

EX2-1(Port-1)

l In Label: 30

NE1l In Port: 4-

EFG2-1(Port-1)

l In Label: 31

NE3l In Port: 1-

EX2-2(Port-2)

l In Label: 52

NE1l In Port: 4-

EFG2-2(Port-2)

l In Label: 53



9-27

Table 9-7 lists the configuration parameters of CES services.

Table 9-7 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots partially used)


NE NE1 NE3

Level E1 E1

Service ID 4 4

Service Name CES Remote Service 1 CES Remote Service 1

Mode UNI-NNI UNI-NNI

Source Board 6-L12 -


Source Low Channel 2 -

PW ID 8 8

Tunnel Working Tunnel-Positive(Tunnel-0100)

Working Tunnel-Reverse(Tunnel-0101)

Sink Board - 6-MP1-1-CD1-1(Port-1)

Sink High Channel - VC4-1

Sink Low Channel - 2

Source 64K Timeslot 1-14,20 1-14,20

PW Signaling Type Static Static

PW Type CESoPSN CESoPSN

PW Ingress Label/SourcePort

36 36

PW Egress Label/Sink Port 36 36

Peer IP 10.0.1.2 10.0.0.1

RTP Head Disabled Disabled

Jitter CompensationBuffering Time(us)

8000 8000

Packet Loading Time(us) 1000 1000

Clock Mode External Clock Mode External Clock Mode

EXP 4 4


Configuration Guide


Issue 06 (2009-06-01)

Table 9-8 Configuration parameters of the CES service: NE1-NE3 (E1 timeslots fully used)


NE NE1 NE3

Level E1 E1

Service ID 5 5

Service Name CES Remote Service 2 CES Remote Service 2

Mode UNI-NNI UNI-NNI

Source Board 6-L12 -


Source Low Channel 3 -

PW ID 9 9

Tunnel Working Tunnel-Positive(Tunnel-0100)

Working Tunnel-Reverse(Tunnel-0101)

Sink Board - 6-MP1-1-CD1-1(Port-1)

Sink High Channel - VC4-1

Sink Low Channel - 3

Source 64K Timeslot 1-31 1-31


PW Type SAToP SAToP

PW Ingress Label/SourcePort

37 37

PW Egress Label/Sink Port 37 37

Peer IP 10.0.1.2 10.0.0.1

RTP Head Disabled Disabled


8000 8000

Packet Loading Time(us) 1000 1000

Clock Mode External Clock Mode External Clock Mode

EXP 4 4

9.5.3 Configuring CES Services by Using the Trail FunctionThis section describes how to configure the three CES services in the example by using the trailfunction.



9-29




Procedure



Apply.





l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6









Configuration Guide


Issue 06 (2009-06-01)








l IP Mask: 255.255.255.252













9-31










Step 3 Creating Working MPLS Tunnels

1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog boxis displayed.

2. Select Create Reverse Tunnel, and configure parameters for the positive tunnel andreverse tunnel in the General Attributes.


l Tunnel ID: 100(Positive), 101(Reverse)

l Name: Working Tunnel-Positive, Working Tunnel-Reverse

l Signal Type: Static (If you set signal type to dynamic, the LDP distributes labels andthe tunnel is a dynamic tunnel; if you set signal type to static, labels are manually addedand the tunnel is a static tunnel.)

l Scheduling Type: E-LSP

– E-LSP indicates that the tunnel determines the scheduling priority and discardpriority of packets according to the EXP information. On one MPLS tunnel of theE-LSP type, there can be a maximum of eight types of PWs.

l EXP:- (Set the tunnel priority according to networking planning.)


3. Click Next, and select Ingress Node, Egress Node and Transit Node to set route restrictions.


Configuration Guide


Issue 06 (2009-06-01)

The configuration parameters are as follows:l Ingress Node: NE1 (The source node on a tunnel is referred to as ingress node, that is,

the node where the tunnel enters the network.)l Egress Node: NE3 (The sink node on a tunnel is referred to as egress node, that is, the

node where the tunnel exists the network.)l Transit Node: NE2 (The pass-through node on a tunnel is referred to as transmit node.)

4. Click Next. Set tunnel-related parameters and route constraints. Then, click Next. Confirmthe tunnel information and then click Finish.


l Positive Route Information– NE1 Ingress Node

– Out Port: 4-EFG2-1(Port-1) (the source port on the tunnel)

– Out Label: 20 (The local out label is the same as the downstream in label. Labelsare used to forward packets.)




9-33

– NE2 Transit Node– In Port: 3-EG16-1(Port-1)

– In Label: 20

– Out Port: 1-EX2-1(Port-1)

– Out Label: 30


– NE3 Egress Node– In Port: 1-EX2-1(Port-1)

– In Label: 30

l Reverse Route Information– NE3 Ingress Node

– Out Label: 21

– NE2 Transit Node– In Label: 21

– Out Label: 31

– NE1 Egress Node– In Label: 31

Step 4 Creating Protection Tunnel.1. Create protection Tunnel by following Step 3.1 toStep 3.4.

The configuration parameters are as follows:l General Attributes

– Tunnel ID: 120 (Positive), 121 (Reverse)

– Name: Protection Tunnel-Positive, Protection Tunnel-Reverse

– Signal Type: Static


– EXP:-

– Bandwidth (kbit/s): No Limit

l Node Information– Ingress Node: NE1

– Egress Node: NE3

– Transit Node: NE6, NE5, NE4


Step 5 Configure BTS-side E1 interface.1. In the NE Explorer, select the NE1 and choose Configuration > Interface

Management > PDH Interface.2. Click General Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set the Port

Mode to Layer 1.

NOTE

Before setting the port mode, make sure that the port DCN is disabled.


Configuration Guide


Issue 06 (2009-06-01)


4. Click Advanced Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set theFrame Format to Unframe.

NOTEBefore setting the port mode, make sure that the port DCN is disabled.


Step 6 Configure BSC-side STM-1 interface.

1. In the NE Explorer, select the board 6-MP1 of NE1 and choose Configuration > InterfaceManagement > Path Configuration .

2. Select NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:2 and NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:3. Set VC12 Frame Format to Unframe.


Step 7 Creating CES Remote Service 1.

1. On the Main Topology, choose Trail > Emulation Service Creation > CES ServiceCreation, The Create CES Service dialog box is displayed.

2. Set the parameters of CES service. Select Auto Assign Label,the system automaticallyassigns the Uplink Label and Downlink Label for the PW.

Basic Information



9-35

l Service Level: E1

l Service Name: CES Remote Service 1

l Service ID: 4

Sourcel NE: NE1

l Port: 6-L12

l High Path: - (In the case of the line port, set the VC-4 higher order path number.)

l Low Path: 2 (In the case of the E1 port, set the E1 port number. In the case of the lineport, set the VC-12 lower order path number.)

l 64K Timeslot: 1-14,20 (The 64K Timeslot parameter indicates the timeslot compressionlist during the configuration of the structured emulation CES services. The selectedtimeslots are loaded to the PW packets, and then are transmitted to the opposite endthrough the Ethernet. The timeslot lists at the two ends can be inconsistent, but thenumber of timeslots must be consistent. Otherwise, the services are unavailable.)

sinkl NE: NE3

l Port: 6-MP1-1-CD1-1(Port-1)

l High Path: VC4-1

l Low Path: 2

l 64K Timeslot: 1-14,20

PWl ID: 8

l Emulation Mode: CESoPSN (The CESoPSN is of structuralized emulation, and youcan set the timeslot compression for it. The SAToP is of non-structuralized emulation,and you cannot set the timeslot compression for it.)

l Signaling Type: Static (The PW signaling type indicates whether the PW is static ordynamic. In the case of the dynamic PW, the services are available after the signalingnegotiation is successful. In the case of the static PW, the signaling negotiation is notneeded.)

l Encapsulation Type: MPLS

l Uplink Label/Source Port: 36 (The uplink label is the label attached on the packet headerwhen the TDM frames are encapsulated in the PW.)

l Downlink Label/Sink Port: 36 (The downlink label is the label attached on the packetheader when the TDM frames are encapsulated in the PW.)

l Tunnel Type: MPLS Tunnel

l Tunnel Name: Working Tunnel-Positive(Tunnel-0100)

3. Click Advanced and the Advanced Attribute dialog box is displayed. Configureparameters for advanced attribute, Click OK to finish configuring the advanced attributes..


Configuration Guide


Issue 06 (2009-06-01)


l RTP Head: Disabled (The RTP head carries the clock signals.)

l Jitter Compensation Buffering Time(us): 8000(The Jitter Compensation BufferingTime indicates the buffer size in the receive direction. The PSN is delayed, while theTDM network is plesiochronous. The packet needs to be saved temporarily so that itcan be transmitted to the PDH port smoothly. The buffer size is measured in time. Thisparameter can be set when the pseudo wire (PW) is used for the circuit emulation service(CES).)

l Packet Loading Time(us): 1000 (The Packet Loading Time parameter indicates the timethat the PW packet requires to load the TDM frames. That is, the parameter is used tospecify the number of the TDM frames that are loaded in the PW packet. The period ofthe TDM frame is 125 us. If Packet Loading Time is 1 ms, then eight TDM frames canbe loaded in a PW packet.)

l Uplink Clock Mode: External Clock Mode (The Clock Mode parameter indicateswhether the clocks of the PDH/SDH services accessed at both ends are synchronous.)

l Downlink Clock Mode: External Clock Mode


Step 8 Creating CES Remote Service 2. Set the parameters related to the CES service by followingStep 7.1 to Step 7.4.

Basic Information

l Service Level: E1


l Service ID: 5

Source

l NE: NE1

l Port: 6-L12

l High Path: -

l Low Path: 3



9-37

l 64K Timeslot: 1-31

sinkl NE: NE3

l Port: 6-MP1-1-CD1-1(Port-1)

l High Path: VC4-1

l Low Path: 3

l 64K Timeslot: 1-31

PWl ID: 9

l Emulation Mode: CESoPSN

l Signaling Type: Static

l Encapsulation Type: MPLS

l Uplink Label/Source Port: 37

l Downlink Label/Sink Port: 37


l Tunnel Name: Working Tunnel-Positive(Tunnel-0100)

Advancedl RTP Head: Disabled

l Jitter Compensation Buffering Time(us): 8000

l Packet Loading Time(us): 1000

l Uplink Clock Mode: External Clock Mode

l Downlink Clock Mode: External Clock Mode

----End

9.5.4 Configuring CES Services on a Per-NE BasisThis section describes how to configure the three CES services in the example on a per-NE basis.




Procedure



Apply.


Configuration Guide


Issue 06 (2009-06-01)





l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6















9-39



l IP Mask: 255.255.255.252




l NE2-1-EX2-1(Port-1)






























Step 3 Creating Working MPLS Tunnels.


Configuration Guide


Issue 06 (2009-06-01)

1. Select NE1 in the NE Explorer . Choose Configuration > MPLS Management >Unicast Tunnel Management from Function Tree. Click New and the New UnicastTunnel dialog box is displayed.

2. Configure parameters for the positive tunnel and reverse tunnel such as Tunnel ID, Tunnelname, port and labels. Click OKto finish creating the ingress node.

The configuration parameters are as follows:l Tunnel ID: 100(Positive), 101(Reverse)

l Tunnel Name: Working Tunnel-Positive, Working Tunnel-Reverse

l Node Type: Ingress(Positive), Egress(Reverse)


l Out Board/Logic Interface Type: 4-EFG2 (The source board of the Tunnel.)

l Out Port: 1(Port-1) (The source port of the Tunnel.

l Next Hop Address: 10.0.0.2 (The IP address of the interface on the next node on thetunnel.)

l Sink Node: 1.0.0.3 (The LSR ID of the interface on the sink node on the tunnel.)

l Tunnel Type: E-LSP– E-LSP indicates that the tunnel determines the scheduling priority and discard


l EXP: none (Set the tunnel priority according to networking planning.)

3. In the NE Explorer, select NE2. Then, configure the Tunnel parameters of the transit nodeby following Step 3.1 to Step 3.2.



9-41

Set related parameters and ensure that the general information of the tunnel is the same asthat on NE1. The configuration parameters are as follows:l Node Type: Transit (NE2 is a transit node on the tunnel.)

l In Board/Logic Interface Type: 3-EG16


l In Label: 20 (Positive), 21 (Reverse)

l Out Board/Logic Interface Type: 1-EX2

l Out Port: 1(Port-1)

l Out Label: 30 (Positive), 31 (Reverse)

l Next Hop Address: 10.0.1.2 (Positive), 10.0.0.1 (Reverse)

l Source Node: 1.0.0.1 (Positive), 10.0.1.2 (Reverse) (The LSR ID of the source node onthe tunnel.)

l Sink Node: 1.0.0.2. (The LSR ID of the sink node on the tunnel.)

4. In the NE Explorer, select NE3. Then, configure the Tunnel parameters of the egress nodeby following Step 3.1 to Step 3.2.


Configuration Guide


Issue 06 (2009-06-01)

Set related parameters and ensure that the general information of the tunnel is the same asthat on NE1. The configuration parameters are as follows:l Node Type: Egress (NE3 is a terminal node on the tunnel.)

l In Board/Logic Interface Type: 1-EX2


l In Label: 30(Positive), Out Label: 31 (Reverse)

l Next Hop Address: -(Positive), 10.0.1.1 (Reverse)

l Source Node: 1.0.0.1 (Positive) (The LSR ID of the source node on the tunnel.)

Step 4 Creating Protection Tunnel.1. Display the NE Explorer for NE1, NE6, NE5, NE4, and NE3 separately. Perform Step

3.1 through Step 3.4 to create the ingress node, transit node, and egress node on the bypasstunnel.


l Tunnel Name: Protection Tunnel-Positive, Protection Tunnel-Reverse

l Bandwidth(kbit/s): No Limit

l Tunnel Type: E-LSP

l EXP: none


Step 5 Configure BTS-side E1 interface.1. In the NE Explorer, select the NE1 and choose Configuration > Interface

Management > PDH Interface.2. Click General Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set the Port

Mode to Layer 1.



9-43

NOTE



4. Click Advanced Attributes tab, Select 6-L12-2(Port-2) and 6-L12-3(Port-3). Set theFrame Format to Unframe.

NOTEBefore setting the port mode, make sure that the port DCN is disabled.


Step 6 Configure BSC-side STM-1 interface.1. In the NE Explorer, select the board 6-MP1 of NE1 and choose Configuration > Interface

Management > Path Configuration .2. Select NE3-6-MP1-1-CD1-1(Port-1)-VC4:1-VC12:2 and NE3-6-MP1-1-CD1-1(Port-1)-

VC4:1-VC12:3. Set VC12 Frame Format to Unframe.3. Click Apply, and the Operation Result dialog box is displayed, indicating that the

operation is successful. Click Close.

Step 7 Creating CES Remote Service 1.1. In the NE Explorer, select NE1 and choose Configuration > CES Service

Management from the Function Tree.2. Click New and the Create CES Service dialog box is displayed. Configure parameters for

CES Remote Service 1.


Configuration Guide


Issue 06 (2009-06-01)

The configuration parameters are as follows:l Service ID: 4


l Level: E1

l Mode: UNI-NNI


l Source High Channel: - (In the case of the line port, set the VC-4 higher order pathnumber.)

l Source Low Channel: 2 (In the case of the E1 port, set the E1 port number. In the caseof the line port, set the VC-12 lower order path number.)

l Source 64K Timeslot: 1-14,20 (The 64K Timeslot parameter indicates the timeslotcompression list during the configuration of the structured emulation CES services. The



9-45

selected timeslots are loaded to the PW packets, and then are transmitted to the oppositeend through the Ethernet. The timeslot lists at the two ends can be inconsistent, but thenumber of timeslots must be consistent. Otherwise, the services are unavailable.)

l PW ID: 8l PW Signaling Type: Staticl PW Type: CESoPSN (The CESoPSN is of structuralized emulation, and you can set

the timeslot compression for it. The SAToP is of non-structuralized emulation, and youcannot set the timeslot compression for it.)

l PW Encapsulation Type: MPLSl PW Ingress Label/Source Port: 36 (The ingress label is the label attached on the packet

header when the TDM frames are encapsulated in the PW.)l PW Egress Label/Sink Port: 36 (The egress label is the label attached on the packet

header when the TDM frames are encapsulated in the PW.)l Peer IP: 10.0.1.2l Tunnel: Working Tunnel-Positive(Tunnel-0100)

3. Click QoS. Set the EXP to 4. Click OK to finish configuring the QoS.

4. Click Advanced Attributes. Then, configure the advanced attributes parameters of theCES service. Click OK to finish configuring the advanced attributes.

The configuration parameters are as follows:l RTP Head: Disabled (The RTP head carries the clock signals.)l Jitter Compensation Buffering Time(us): 8000 (The Jitter Compensation Buffering

Time indicates the buffer size in the receive direction. The PSN is delayed, while the


Configuration Guide


Issue 06 (2009-06-01)

TDM network is plesiochronous. The packet needs to be saved temporarily so that itcan be transmitted to the PDH port smoothly. The buffer size is measured in time. Thisparameter can be set when the pseudo wire (PW) is used for the circuit emulation service(CES).)

l Packet Loading Time(us): 1000 (The Packet Loading Time parameter indicates the timethat the PW packet requires to load the TDM frames. That is, the parameter is used tospecify the number of the TDM frames that are loaded in the PW packet. The period ofthe TDM frame is 125 us. If Packet Loading Time is 1 ms, then eight TDM frames canbe loaded in a PW packet.)

l Ingress Clock Mode: - (The Clock Mode parameter indicates whether the clocks of thePDH/SDH services accessed at both ends are synchronous.)

l Ingress Clock Mode: External Clock Mode


1. In the NE Explorer, select NE3. Then, configure the CES Remote Service 1 parameters ofNE3 by following Step 7.2 to Step 7.5.

The configuration parameters are as follows:l Service Level: E1


l Service ID: 4

l Mode: UNI-NNI

l Source Board: 6-MP1-1-CD1-1(Port-1)

l Source High Channel: VC4-1

l Source Low Channel: 2

l Source 64K Timeslot: 1-14,20

l PW ID: 8

l PW Signaling Type: Static

l PW Type: CESoPSN

l PW Ingress Label/Source Port: 36

l PW Egress Label/Sink Port: 36

l Peer IP; 10.0.0.1

l Tunnel: Working Tunnel-Positive(Tunnel-0101)

l EXP: 4

l RTP Head: Disabled



l Ingress Clock Mode: -

l Egress Clock Mode: External Clock Mode

Step 8 Creating CES Remote Service 2.1. In the NE Explorer, select NE1 and choose Configuration > CES Service

Management from the Function Tree.



9-47

2. Configure the CES Remote Service 2 parameters of the NE1 by following Step 7.2 to Step7.5.



l Service ID: 5

l Mode: UNI-NNI


l Source High Channel: -


l Source 64K Timeslot: 1-31

l PW ID: 9


l PW Type: SAToP



l Peer IP: 10.0.1.2

l Tunnel: Working Tunnel-Positive(Tunnel-0100)

l EXP: 4






3. In the NE Explorer, select NE3 and choose Configuration > CES ServiceManagement from the Function Tree.

4. Configure the CES Remote Service 2 parameters of the NE3 by following Step 7.2 to Step7.5.



l Service ID: 5

l Mode: UNI-NNI

l Source Board: 6-MP1-1-CD1-1(Port-1)

l Source High Channel: VC4-1


l Source 64K Timeslot: 1-31

l PW ID: 9



Configuration Guide


Issue 06 (2009-06-01)

l PW Type: SAToP



l Peer IP; 10.0.0.1

l Tunnel: Working Tunnel-Reverse(Tunnel-0101)

l EXP: 4






----End

9.6 Checking the Correctness of the Service ConfigurationAfter the CES service is configured, you need to check the correctness of the serviceconfiguration. You can check the correctness of the CES service configuration as follows: attacha 2M BER tester at the CES port and then perform loopbacks at the remote end.

ContextSee Figure 9-9. A CES service exists between NE1 and NE2. Attach a 2M BER tester at the 1-MP1-1-CD1-1 port on NE1. On the T2000, set the inloop of the 1-MP1-1-CD1-1 port on NE2.Check the correctness of the CES service.

Figure 9-9 Checking the CES service

NE1 NE2

2M BER tester

1-MP1-1-CD1-11-MP1-1-CD1-1

Tunnel

PW

Procedure

Step 1 Connect one end of the 2M cable to the 1-MP1-1-CD1-1 port on NE1 and the other end to in-service test interface of the 2M BER tester.



9-49

Step 2 In the NE Explorer, select NE2 and choose Configuration > Interface Management > SDHInterface , and set the Loopback Mode of 1-MP1-1-CD1-1(Port-1) to Inloop. On the T2000,configure the outloop of the 1-MP1-1-CD1-1 port on NE2.

Step 3 Start the test. Normally, there should be no bit error in 24 hours.

----End

9.7 Parameter DescriptionThis section describes the parameters related to the CES service configuration.

Table 9-9 Descriptions of the parameters for CES Service Management


Service Level E1 Indicate the level of theaccessed TDM frame.

Service Name 64 bytesDefault: CESService-0001

Indicate the name of theservice.

Service ID Example: 5 Set the ID of the service, orset to automatically allocatethe ID of the service.

Customer String Indicate the customer of theservice.

Remarks String Indicate the description of theservice.

NE Example: NE1 Set the source NE and sinkNE.l When configuring a UNI-

NNI service, selectdifferent NEs as the sourceand sink.

l When configuring a UNI-UNI service, select thesame NE as the source andsink.

Port Example: 6-MP-1 (PORT-1) Set the source port and sinkport.

High Path VC-4 supported by the board Set the high path.In the case of the line port, setthe VC-4 higher order pathnumber.


Configuration Guide


Issue 06 (2009-06-01)


Low Path Lower order timeslot numberor tributary port numbersupported by the board

Set the low path.In the case of the E1 port, setthe E1 port number. In thecase of the line port, set theVC-12 lower order pathnumber.

64K Timeslot Example: 1, 5 Set to compress the 64Ktimeslot.Timeslot compression can beset only when ProtocolType is set to CESoPSN.

ID Example: 5 Set the ID of the PW. You canalso select the automaticallocation.

Signaling Type Static, dynamic Set the PW signal type.If the PW signal type isStatic, set the PW ingresslabel and PW egress label. Ifthe PW signal type isDynamic, the systemautomatically sets the PWingress label and PW egresslabel.

Encapsulation Type MPLS, UDP Sets the PW encapsulationtype. When the PWEncapsulation Type is set toMPLS, the MPLS, IP, andGRE tunnels are supported;When the PWEncapsulation Type is set toUDP, only the IP tunnel issupported.

Emulation Mode CESoPSN, SAToP Set the PW emulation mode.CESoPSN is the structuralemulation, for which thetimeslot compression can beset. SAToP is the non-structural emulation, forwhich the timeslotcompression cannot be set.



9-51


Uplink Label/Source Port 16 to 1048575 Set the uplink label.When the TDM frame isencapsulated into the PW,labels are attached on thepacket header. The uplinklabel indicates that theservice enters the PW. Theuplink label and downlinklabel are different. When thePW encapsulation type is setto UDP, the value of theuplink label of PW rangesfrom 49152 to 65535.

Downlink Label/Sink Port 16 to 1048575 Set the downlink label.When the TDM frame isencapsulated into the PW,labels are attached on thepacket header. The downlinklabel indicates that theservice exits the PW. Theuplink label and downlinklabel are different. When thePW encapsulation type is setto UDP, the value of thedownlink label of PW rangesfrom 49152 to 65535.

Tunnel Type MPLS Tunnel, IP Tunnel,GRE Tunnel

Select the tunnel that carriesthe service.The uplink LSP is the ingressdirection of the tunnel thatcarries the service.

Tunnel Name For example, shenzhen(Tunnel-0001)

Select the tunnel that carriesthe service.The downlink LSP is theegress direction of the tunnelthat carries the service.


Configuration Guide


Issue 06 (2009-06-01)

Table 9-10 Descriptions of the parameters for Advanced Attributes of CES Service Management


RTP Head Enabled, Disabled Set the RTP head.The RTP head carries theclock signals.Click C.36 RTP Head formore information.

Packet Loading Time (us) PTN 3900: 125 to 3000 Set the packet loading time.Set the packet loading time toincrease the efficiency inencapsulation.Click C.49 Packet LoadingTime for more information.


PTN 3900: 375 to 64000 Set the jitter compensationbuffering time.The jitter compensationbuffering time is set to ensurethat the CES service is real-time.NOTE

Different PTN devices supportthe different ranges of jittercompensation buffering time.When the value exceeds therange, an error message isdisplayed.

The value of JitterCompensation BufferingTime(us) must be greater thanthe value of Packet LoadingTime(us) on the opposite end.

Click C.77 JitterCompensation BufferingTime for more information.

Uplink Clock Mode External Clock Mode, Null Set the uplink clock mode.The clock mode is set toensure correct restoration ofthe CES service at the sink.

Downlink Clock Mode External Clock Mode, Null Set the downlink clock mode.The clock mode is set toensure correct restoration ofthe CES service at the sink.



9-53

Table 9-11 Descriptions of the parameters for PW General Attributes of CES servicemanagement


Service ID Example: 5 Sets the ID of the service.

Service Name 64 bytes Sets the name of the service.

Level E1 Sets the level of the TDM frame.

Mode UNI-UNI, UNI-NNI Displays the mode of the CESservice.

Source Board Example: Slot-BoardName-Port(Port No.)

Sets the source board of the CESservice.

Source High Channel Example: VC4-1 Sets the source high channel.In the case of the line port, set theVC-4 higher order path number.

Source Low Channel Example: VC12-1 Sets the source low channel.In the case of the E1 port, set the E1port number. In the case of the lineport, set the VC-12 lower order pathnumber.

PW ID Example: 5 Sets the ID of the PW.

Enable State Enabled, Disabled Sets and display the enable status ofthe PW.You can right-click a PW and set theenable status of the PW with theshortcut menu.

Tunnel Type MPLS, GRE, IP Sets the type of Tunnel.

Tunnel Tunnel IDExample: 55

Sets the tunnel that carries the PW.The tunnel should be configured inadvance.Click C.39 Tunnel for moreinformation.

Sink Board Example: Slot-BoardName-Port(Port No.)

Sets the sink board of the CESservice.

Sink High Channel Example: VC4-1 Sets the sink high channel.In the case of the line port, set theVC-4 higher order path number.

Sink Low Channel Example: VC12-1 Sets the sink low channel.In the case of the E1 port, set the E1port number. In the case of the lineport, set the VC-12 lower order pathnumber.


Configuration Guide


Issue 06 (2009-06-01)


64K Timeslot Example: 1-31 Displays the compressed 64Ktimeslot.Click C.1 64KTs for moreinformation.

Source 64K Timeslot Example: 1-31 Displays the compressed source 64Ktimeslot.

PW Signaling Type Static, Dynamic Sets the PW signal type.If PW Signal Type is set to Static,manually set the PW ingress labeland PW egress label. If PW SignalType is set to Dynamic, the systemautomatically sets the PW ingresslabel and PW egress label.Click C.34 PW Signaling Type formore information.

PW Type CESoPSN, SAToP Sets the PW type.The CESoPSN is of structuralizedemulation, and you can set thetimeslot compression for it.The SAToP is of non-structuralizedemulation, and you cannot set thetimeslot compression for it.

PW Encapsulation Type MPLS, UDP Sets the PW encapsulation type.When the PW Encapsulation Typeis set to MPLS, the MPLS, IP, andGRE tunnels are supported; Whenthe PW Encapsulation Type is setto UDP, only the IP tunnel issupported.

PW Ingress Label 16 to 1048675 Sets the PW ingress label.The PW ingress label is the labelattached on the packet header whenthe TDM frames are encapsulated inthe PW. The PW ingress labelindicates that the service enters thePW. When the PW EncapsulationType is set to UDP, the value of theingress label of PW ranges from49152 to 65535.



9-55


PW Egress Label 16 to 1048675 Sets the PW egress label.The PW egress label is the labelattached on the packet header whenthe TDM frames are encapsulated inthe PW. The PW egress labelindicates that the service exits thePW. When the PW EncapsulationType is set to UDP, the value of theegress label of PW ranges from49152 to 65535.Click C.31 PW Egress Label formore information.

Peer IP Example: 192.168.0.1 Sets the peer IP.

Local Working Status Example: Up Displays the local working status.

Remote Working Status Example: Up Displays the remote working status.

Compositive WorkingStatus

Example: Up Displays the compositive workingstatus. When Local WorkingStatus and Remote WorkingStatus are set to Up, CompositiveWorking Status is Up. When LocalWorking Status or RemoteWorking Status is set to Down,Compositive Working Status isDown.

Table 9-12 Descriptions of the parameters for QoS of CES Service Management



Direction Egress, Ingress Sets the direction of the PW.Egress indicates the PW out-goingdirection.Ingress indicates the PW in-comingdirection.

EXP None, 0, 1, 2, 3, 4, 5, 6,7

Sets and displays the EXP priority.7 indicates the highest priority.

CIR (kbit/s) Example: 2048 Displays the committed bandwidthof the QoS.The committed bandwidth of theQoS indicates the minimumbandwidth available to the service.


Configuration Guide


Issue 06 (2009-06-01)

Table 9-13 Descriptions of the parameters for Advanced Attributes of CES Service Management


RTP Head Enabled, Disabled Set the RTP head.The RTP head carries the clocksignals.Click C.36 RTP Head for moreinformation.

Packet Loading Time(us) PTN 3900: 125 to 3000 Set the packet loading time.Set the packet loading time toincrease the efficiency inencapsulation.Click C.49 Packet Loading Timefor more information.

Jitter CompensationBuffering Time (us)

375 to 16000PTN 910: 375 to 16000PTN 950: 375 to 16000PTN 3900: 375 to64000

Set the jitter compensation buffertime.The jitter compensation buffer timeis set to ensure that the CES serviceis real-time.NOTE

Different PTN devices support thedifferent ranges of jitter compensationbuffering time. When the value exceedsthe range, an error message is displayed.

The value of Jitter CompensationBuffering Time(us) must be greaterthan the value of PacketisationBuffering Time(us) on the oppositeend.

Click C.77 Jitter CompensationBuffering Time for moreinformation.

Ingress Clock Mode External Clock Mode,Null

Set the ingress clock mode.The clock mode is set to ensurecorrect recovery of the CES serviceat the sink.

Egress Clock Mode External Clock Mode,Null

Set the egress clock mode.The clock mode is set to ensurecorrect recovery of the CES serviceat the sink.



9-57

10 Configuring an ATM Service

About This Chapter

This section describes basic information on the ATM service, and illustrates how to configurean ATM service with an example.

10.1 Basic InformationThis section describes the basic information about the ATM service and ATM traffic.

10.2 ATM Service Configuration FlowThis section describes the operation tasks for configuring the ATM service, and relations amongthese tasks. When configuring and managing the ATM services, follow the configuration flow.The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.

10.3 Operation Tasks Related to ATM ServicesThe operation tasks related to ATM services include the configuration of bound channels in anATM IMA group, setting of ATM IMA group attributes, fast configuration of an ATM serviceand configuration of an ATM service at a single station.

10.4 Configuration Case of the UNI-UNI ATM ServiceThis section describes a configuration case of the UNI-UNI ATM service. The configurationflow diagram is provided to describe the configuration process. The configuration case includesservice planning and ATM service configuration.

10.5 Configuration Case of the UNIs-NNI ATM ServiceThis section describes a configuration case of the UNIs-NNI ATM service. The configurationflow diagram is provided to describe the configuration process. The configuration case includesservice planning and ATM service configuration.

10.6 Verifying the Correctness of Service ConfigurationAfter the ATM service is configured, the correctness of service configuration should be verified.The ATM OAM is used for verifying the correctness of the ATM service configuration.

10.7 Parameter DescriptionThis section describes the parameters related to the ATM service configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 10 Configuring an ATM Service


10-1

10.1 Basic InformationThis section describes the basic information about the ATM service and ATM traffic.

10.1.1 ATM ServiceAsynchronous transfer mode (ATM) is a technology used to transport packets in cells withensured QoS. ATM meets the requirements of real-time services and non-real-time services.The OptiX PTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATMservice.

10.1.2 ATM TrafficThe ATM communicates through virtual connections, which are uniquely identified by the VPI/VCI in the cell header. During data transmission, you need to control the traffic of each virtualconnection to ensure the quality of service (QoS).

10.1.1 ATM ServiceAsynchronous transfer mode (ATM) is a technology used to transport packets in cells withensured QoS. ATM meets the requirements of real-time services and non-real-time services.The OptiX PTN equipment supports both the UNIs-NNI ATM service and UNI-UNI ATMservice.

ATM emulation services mainly apply to wireless services. The application scenarios includeUNIs-NNI and UNI-UNI, as shown in Figure 10-1.

l UNIs-NNI ATM service: The PTN equipment accesses the ATM services of customers byusing the IMA link or STM link respectively. You can create the ATM PW between thePTN equipment to emulate end-to-end ATM services. At the source end, the ATM cellsare encapsulated in the PW. Then, data packets are transparently transmitted in the MPLSnetwork. At the sink end, the ATM services are decapsulated and forwarded to theconnected customer network. To customers, the UNIs-NNI ATM services are similar toactual ATM services.

l UNI-UNI ATM services: The PTN equipment switches and transmits the ATM services ata single point.

10 Configuring an ATM ServiceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

Figure 10-1 ATM service networking sample

UNI-NNI

UNI-UNI

Node B

RNC

IMA Link

PW

STM-1 ATM Link

PE

PE

PE

Tunnel

Node B

Node B

The ATM UNIs-NNI emulation service supports the convergence of multiple ATM connectionsinto a PW for transmission. As shown in Figure 10-2, three ATM connections are encapsulatedinto a PW.

Figure 10-2 ATM connection convergence sample



10-3

10.1.2 ATM TrafficThe ATM communicates through virtual connections, which are uniquely identified by the VPI/VCI in the cell header. During data transmission, you need to control the traffic of each virtualconnection to ensure the quality of service (QoS).

ATM Traffic ModesAs shown in Table 10-1, the PTN equipment supports four traffic modes. During traffic control,you need to set different traffic parameters according to different service types.

Table 10-1 ATM service type and traffic

Application Type ApplicationInstance

Traffic Parameter Remarks

Constant bit rate(CBR) service

Voice services, videoservices of a constantbit rate, and circuitemulation services

PCR, CDVT The CBR supportsthe strictrequirements forCTD and CDV, butdoes not supportservices withvariable delay.

Unspecified bit rate(UBR) service

LAN emulation, IPover ATM, and non-special trafficservices

PCR, CDVT The UBR does notrequire a strict delayand the delayvariation. Besides, itdoes not provide aspecial QoS orensure the output.

UBR+ LAN emulation, IPover ATM, and non-special trafficservices

PCR, CDVT There are UBR+services on manyNodeBs. The UBR+services areconfigured with theMCR. When theservice rate does notexceed theconfigured MCR, thenormal servicetransmission isensured. The featuresof the UBR+ serviceother than the MCRare the same as thefeatures of the UBRservice.


Configuration Guide


Issue 06 (2009-06-01)

Application Type ApplicationInstance

Traffic Parameter Remarks

Real time variable bitrate (rtVBR) service

Audio services, andvideo services of avariable bit rate

PCR, SCR, CDVT,MBS

The rtVBR supportstime-sensitiveservice applicationsand have restrictionson the delay anddelay variation.

Non real timevariable bit rate(nrtVBR) service

Data packettransmission,terminal meeting,and file transmission

PCR, SCR, MBS The nrtVBR does nothave restrictions onthe delay and delayvariation butsupports applicationof services with thevariable rate andburst traffic features.

The meanings of the traffic parameters in the table are as follows:l Peak cell rate (PCR): It defines the maximum cell rate at which cells are transmitted to a

network.l Sustainable cell rate (SCR): It defines the maximum sustainable average cell rate at which

cells are transmitted to a network.l Cell delay variation tolerance (CDVT): When multiple connected cells are converged, at

the convergence egress, the transmission of a connected cell may be delayed because ofthe insertion of other connected cells. Similarly, the transmission delay may also be causedby the insertion of physical layer overheads and OAM cells. In other words. the cells donot evenly arrive at the receive station. The arrival intervals of consecutive cells aredifferent in different periods. The maximum tolerance of this difference is called CDVT.

l Maximum burst size (MBS): It limits the maximum cell burst amount within the maximumrate permitted.

Users require each service type to provide a certain QoS and comply with a certain trafficprotocol, which is realized by traffic control. During transmission, only user cells complyingwith the protocol can be successfully transmitted. Cells that do not comply with the protocol arelabelled or discarded according to different situations.

Basic Principle of Traffic ControlIn general, the control of ATM services combines the preventive control and reactive controlmethods. Preventive control is the main method, but when congestion occurs, the network cantake measures to clear the congestion.

In point of effect, the ATM traffic control can be classified into two parts as follows:l Traffic parameter control: preventive control

l Congestion control: reactive control



10-5

Traffic Parameter ControlThe function of traffic parameter control is used to set up proper connections and to control theconnected cell flow according to the traffic parameters. If the control of these parameters fails,traffic congestion may occur. The traffic parameter control includes the following methods:l Usage parameter control (UPC)/network parameter control (NPC)

l Traffic shaping

UPC/NPC

UPC/NPC monitors and controls the traffic to judge whether cell violation occurs according tothe negotiated parameters. If cell violation occurs, corresponding measures will be taken toprevent network resources from being invaded viciously or unintentionally. This ensures thatone link never violates the traffic control.

UPC is an act of connection monitoring at the UNI (dedicated or public), and NPC is an act ofconnection monitoring at the NNI (dedicated or public).

According to different traffic types. the UPC includes the following measures:l Allow cells to pass through: The cells are considered protocol-abiding by the UPC.

l Label cells: This operation is performed on the cell loss priority (CLP). The UPC labelsonly cells whose CLP values are 0 by changing the CLP values to 1. In this case, these cellsare in conflict with the traffic convention. If the bandwidth is sufficient, these cells areallowed to pass through. If the bandwidth is insufficient, however, these labeled cells arediscarded.

l Discard cells: The cells violate the protocol and thus cannot be transmitted continuously.

Traffic Shaping

Traffic shaping is a method of changing the traffic feature of a cell flow to realize a highernetwork efficiency and ensure the QoS index. Traffic shaping helps the cell flow to be transmittedmore evenly, maximize the efficiency, and eases the network burden.

Congestion ControlTraffic parameter control is based on the connection and cells, but congestion control relates todifferent service types.

If a network requires discarding cells, a better solution of congestion is to discard packets ratherthan cells. When an NE discards cells, it also discards a part of the packet. As a result, the upperlayer protocol, such as the TCP/IP protocol, is retransmitted, and thus congestion or even collapseoccurs.

10.2 ATM Service Configuration FlowThis section describes the operation tasks for configuring the ATM service, and relations amongthese tasks. When configuring and managing the ATM services, follow the configuration flow.The application scenarios of the ATM service include the UNI-UNI and UNIs-NNI services.

UNI-UNI ATM serviceFigure 10-3 shows the configuration flow of the UNI-UNI ATM service. For details of eachstep, see the related section.


Configuration Guide


Issue 06 (2009-06-01)

Figure 10-3 Configuration flow of the UNI-UNI ATM service

Creating Network

Configure the ATM Interface

Configure the UNI-UNI ATM Service

StartRequired

End

Configure the ATM Policy

Optional

Table 10-2 Tasks for configuring the UNI-UNI ATM service

Task Remarks

1. CreatingNetwork


2. Configure theATM Policy

The ATM policy is used for traffic management of the ATM service.

3. Configure theATM Interface

The ATM interface accesses services from NodeB.

4. Configure theUNI-UNI ATMService

To configure the UNI-UNI ATM service, you need to specify theservice ID and service name, select the connection type, and configurethe connection.



10-7

NOTE

The process of configuring an ATM interface varies with the board types.

l An ATM STM-1 board accesses ATM signals:

1. In General attributes for the SDH interface, set the port mode to Layer 2 and encapsulation typeto ATM.

2. In Layer 2 attributes for the SDH interface, set the port type, maximum VPI, and maximumVCI.

l An ATM STM-1 board accesses IMA signals:


2. Create tunnels bound to the ATM IMA group. For details, see Configuring Bound Channels inan ATM IMA Group in the Feature Description.

3. Set attributes of the ATM IMA group. In particular, enable the IMA protocol, specify the IMATransmit Frame Length, and set the IMA Symmetry Mode. For details, see ConfiguringAttributes of an ATM IMA Group in the Feature Description.

4. Set attributes of the ATM interface. In particular, set the interface type, maximum VPI, andmaximum VCI. For details, see Configuring ATM Interface Attributes in the FeatureDescription.

l An ATM E1 board accesses IMA signals:

1. In General attributes for the PDH interface, set the port mode to Layer 2 and encapsulation typeto ATM.

2. Create channels bound to the ATM IMA group. For details, see Configuring Bound Channels inan ATM IMA Group in the Feature Description.



UNIs-NNI ATM serviceFigure 10-4 shows the configuration flow of the UNIs-NNI ATM service. For details of eachstep, see the related section.


Configuration Guide


Issue 06 (2009-06-01)

Figure 10-4 Configuration flow of the UNIs-NNI ATM service

Creating Network

Configure the ATM Interface

Configure the control plane

Configure the UNIs-NNI ATM service

StartRequired

End

Configure the ATM Policy

Configure the Tunnel

Optional

Configure the network-side interface

Configure the LSR ID

Table 10-3 Tasks for configuring the UNIs-NNI ATM service

Task Remarks

1. CreatingNetwork


2. Configure theLSR ID




10-9

Task Remarks

3. Configure thenetwork-sideinterface


4. Configure thecontrol plane

Set the protocol parameters related to the control plane to create thetunnel.l To create a static MPLS tunnel to transmit the ATM service, the

parameters related to the control plane need not be set.l To create a dynamic MPLS tunnel to transmit the ATM service, you

need to set the following protocol parameters:1. Set the IGP-ISIS protocol parameters.2. Set the MPLS-RSVP protocol parameters.To create a dynamic PW to transmit the service, you need to set theparameters related to the MPLS-LDP protocol.

l To create an IP Tunnel or GRE Tunnel to transmit the ATM service,you need to Configuring Static Routes.

5. Configure theTunnel


per-NEor per-trailmode. Specify the tunnel ID, set signaling type to static, name theservice, and specify the ingress node, egress node, and transit node.



6. Configure theATM Policy

The ATM policy is used for traffic management of the ATM service.

7. Configure theATM Interface

The ATM interface accesses services from NodeB.

8. Configure theUNIs-NNI ATMservice

1. Create an ATM service: Specify the service ID, name the service, andselect the service type and connection type.

2. Configure the connection: Set the source information, PW ID, sinkinformation, and policy.

3. Configure a PW: Set the PW type, label, and tunnel type.4. Configure CoS mapping: Set the CoS policy for the PW.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

The process of configuring an ATM interface varies with the board types.

l An ATM STM-1 board accesses ATM signals:


2. In Layer 2 attributes for the SDH interface, set the port type, maximum VPI, and maximumVCI.

l An ATM STM-1 board accesses IMA signals:


2. Create tunnels bound to the ATM IMA group. For details, see Configuring Bound Channels inan ATM IMA Group in the Feature Description.



l An ATM E1 board accesses IMA signals:

1. In General attributes for the PDH interface, set the port mode to Layer 2 and encapsulation typeto ATM.

2. Create channels bound to the ATM IMA group. For details, see Configuring Bound Channels inan ATM IMA Group in the Feature Description.



10.3 Operation Tasks Related to ATM ServicesThe operation tasks related to ATM services include the configuration of bound channels in anATM IMA group, setting of ATM IMA group attributes, fast configuration of an ATM serviceand configuration of an ATM service at a single station.

10.3.1 Creating ATM Services by Using the Trail FunctionYou can create an ATM PWE3 service path for transmitting ATM signals by using the trailfunction. By using the trail function, you can directly configure the source and sink nodes of anATM service and the PW attributes in a user interface of the T2000. In this way, the ATM servicecan be fast created.

10.3.2 Creating ATM Services on a Per-NE BasisThis section describes how to create an ATM PWE3 service channel that transports ATM signalson a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you needto separately configure the service attributes at the source and sink ends of the service first.

10.3.1 Creating ATM Services by Using the Trail FunctionYou can create an ATM PWE3 service path for transmitting ATM signals by using the trailfunction. By using the trail function, you can directly configure the source and sink nodes of an



10-11

ATM service and the PW attributes in a user interface of the T2000. In this way, the ATM servicecan be fast created.


l You must complete the configuration of the control plane. For configuration method, see5 Configuring the Control Plane.

l If IMA services are accessed, you must complete the configuration of an IMA group. Forconfiguration method, see Configuring the IMA in Feature Description.

l You must complete the configuration of the ATM policy. For configuration method, seeCreating the ATM Policy in Feature Description.

l You must complete the creation of a tunnel. For configuration method, see 6.3 Creating aStatic MPLS Tunnel by Using the Trail Function.

Procedure

Step 1 Choose Trail > PTN Service > ATM Service Creation from the Main Menu.

Step 2 Create a UNI-UNI or UNIs-NNI service in the Create ATM Service window.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

For the UNI-UNI service, you need not specify a PW and set parameters of the PW. For the UNIs-NNIservice, you need specify a PW and set parameters of the PW.

Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5.

Step 4 Optional: Create a UNI-UNI service.1. Set basic attributes of the ATM service in General Attributes.For details on the parameters

for general attributes of the ATM service, see Table 10-10.

NOTE

For the ATM Service type, you can select the following.

l PVP: Only the VPI value of the ATM connection can be modified.

l PVC: The VPI and VCI values of the ATM connection can be modified.

2. In Source, click Browse and select the source NE and source port of the service. In Sink,click Browse and select the sink NE and sink port of the service. For details on theparameters for the source/sink port of the ATM service, see Table 10-10.

NOTE

For a UNI-UNI service, select the same source and sink NEs. Select one source port and one sinkport.

3. In ATM Connection, click Add to add an ATM connection. For details on the parametersfor ATM connection, see Table 10-10.

NOTE

l Modify the VPI and VCI or not, according to the ATM Service type.

l You can proceed with the next operation only after selecting the uplink and downlink ATMpolicies of the ATM connection.

Step 5 Optional: Create a UNIs-NNI service.1. Set basic attributes of the ATM service in General Attributes. For details on the parameters

for general attributes of the ATM service, see Table 10-10.

NOTE

For the ATM Service type, you can select the following.



2. In Source, click Browse and select the source NE and source port of the service. In Sink,click Browse and select the sink source and sink port of the service. For details on theparameters for the source/sink port of the ATM services, see Table 10-10.

NOTEFor a UNIs-NNI service, select different source and sink NEs.

3. In ATM Connection, click Add to add an ATM connection. For details on the parametersfor ATM connection, see Table 10-10.



10-13

NOTE

l Modify the VPI and VCI or not, according to the ATM Service type.

l The Sink VPI value ranges from 0 to (2MaxVPIbits-1). The Sink VCI value ranges from 32 to(2MaxVCIbits-1). For example, the value of Max. VPI Bits for the ATM interface is 8 and the valueof Max. VCI Bits is 7, the value of the sink VPI ranges from 0 to (28-1) (that is, 0 to 255) andthe value of the sink VCI ranges from 32 to (27-1) (that is, 32 to 127).

l If Encapsulation Type is set n-to-one, you can add several ATM connections.

l You can proceed with the next operation only after selecting the uplink and downlink ATMpolicies of the ATM connection.

4. Click Next. The Create ATM Service dialog box is displayed. Configure the PW and setthe parameters. For details on the parameters for PW attributes, see Table 10-11.

NOTE

In the ATM service management interface, select QoS Policy and configure the QoS policy for thePW. If the QoS policy is not otherwise set, the default policy is adopted.

Step 6 Click Finish. The Operation Result window is displayed. Click Close.

----End


Configuration Guide


Issue 06 (2009-06-01)

10.3.2 Creating ATM Services on a Per-NE BasisThis section describes how to create an ATM PWE3 service channel that transports ATM signalson a per-NE basis. The per-NE basis means that, to configure a complete ATM service, you needto separately configure the service attributes at the source and sink ends of the service first.


l You must complete the configuration of the control plane. For configuration method, see5 Configuring the Control Plane.

l If IMA services are accessed, you must complete the configuration of an IMA group. Forconfiguration method, see Configuring the IMA.

l You must complete the configuration of the ATM policy. For configuration method, seeCreating the ATM Policy.

l You must complete the creation of a tunnel. For configuration method, see 6.5 Creatingan MPLS Tunnel on a Per-NE Basis.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Managementfrom the Function Tree.

Step 2 Click the Connection tab. Click New. The New ATM Service window is displayed. In thewindow, configure a UNIs-NNI or UNI-UNI service.



10-15

NOTE

l For the UNIs-NNI service, set the attributes in the Connection, PW and CoS Mapping tabs.

l For the UNI-UNI service, set only the attributes in the Connection tab.

Step 3 To create a UNI-UNI service, go to Step 4. To create a UNIs-NNI service, go to Step 5.

Step 4 Optional: Create a UNI-UNI service.1. Set ATM-related general attributes. For details on the parameters for general attributes of

the ATM service, see Table 10-12.

NOTE

Select UNI-UNI for the service type.

For the connection type, select the following.



2. Click the Connection tab and click Add. The Configure Connection window is displayed.In the window, set connection attributes. For details on the parameters for connectionattributes of the ATM service, see Table 10-13.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

The Sink VPI value ranges from 0 to (2MaxVPIbits-1).

The Sink VCI value ranges from 32 to (2MaxVCIbits-1).

3. Click OK.

Step 5 Optional: Create a UNIs-NNI service.1. Set ATM-related general attributes. For details on the parameters for general attributes of

the ATM service, see Table 10-12.

NOTE

Select UNIs-NNI for the service type.

For the connection type, select the following.



2. Click the Connection tab and click Add. The Configure Connection window is displayed.In the window, set connection attributes. For details on the parameters for connectionattributes of the ATM service, see Table 10-13.



10-17

3. Click the PW tab and click Add. The Configure PW window is displayed. In the window,set attributes of the PW.

4. Click the General Attributes tab and set the general attributes of PW. For details on theparameters for general attributes of PW, see Table 10-14.


Configuration Guide


Issue 06 (2009-06-01)

5. Optional: Click the QoS tab and set the QoS attribute of PW. For details on the parametersfor QoS attributes of PW, see Table 10-14.

6. Optional: Click the Advanced Attributes tab and set the advanced attributes of PW. Fordetails on the parameters for advanced attributes of PW, see Table 10-14.

7. Click the CoS Mapping tab and click Add to configure the CoS mapping table. For detailson the parameters for the CoS mapping table, see Table 10-15 andTable 10-16.

NOTEYou can configure the CoS mapping only after configuring the parameters in the PW tab.

8. Click OK.

Step 6 In the New ATM Service window, click OK. A dialog box is displayed, indicating that theoperation is successful. Click Close.

----End

10.4 Configuration Case of the UNI-UNI ATM ServiceThis section describes a configuration case of the UNI-UNI ATM service. The configurationflow diagram is provided to describe the configuration process. The configuration case includesservice planning and ATM service configuration.

10.4.1 Networking DiagramThis section describes the networking diagram for the case where the R99 service, Signallingservice and HSDPA service are transported between Node B and RNC.

10.4.2 Service PlanningTo transport the R99 and HSDPA services between NodeB and RNC, three ATM connectionsshould be created.

10.4.3 Configuring an ATM Service on a Route BasisThis section describes the process of configuring a UNI-UNI ATM service on a route basis.

10.4.4 Configuring an ATM Service on a Per-NE BasisThis section describes the process of configuring a UNI-UNI ATM service on a per-NE basis.

10.4.1 Networking DiagramThis section describes the networking diagram for the case where the R99 service, Signallingservice and HSDPA service are transported between Node B and RNC.

Figure 10-5 shows the networking diagram of the UNI-UNI ATM service. The ATM service isrequired between Node B and RNC. Connection 1 is used for transmitting R99 services,Connection 2 is used for transmitting HSDPA services, and Connection 3 is used for transmittingSignalling services. Node B transmits services to RNC through NE1. NE1 uses the OptiX PTN3900 to access the services from the base station, and NE1 transmits services to RNC throughSTM-1.



10-19

Figure 10-5 Networking of the ATM service

UNI UNI

IMA 1 STM-1

VPI1

VCI100

1 101R99

Connection 2 HSDPA

VPI70

VCI32

71 32

Node B NE 1 RNC

Connection 1

1 102Connection 3 Signalling 72 32



IMA 1STM-1

Node B NE 1 RNC

2-MP1-AD11-MP1-MD1-19-D75

UNIUNI

10.4.2 Service PlanningTo transport the R99 and HSDPA services between NodeB and RNC, three ATM connectionsshould be created.

Node B accesses the ATM service through IMA1, and then transmits the service to RNC. threeservices that are connected to the N:1 VCC service should be created. Figure 10-5 shows theVPI/VCI switching. The service shown in Figure 10-5 is taken as an example.



Attribute Remarks

Base Station of Service NodeB

IMA Group IMA1


Configuration Guide


Issue 06 (2009-06-01)

Attribute Remarks

Port Accessing the IMA Group atNodeB

NE1-1-MP1-1-MD1-1(Trunk1)

Port Connected to RNC NE1-2-MP1-1-AD1-1(1-AD1.PORT-1)

Connection 1

Source VPI/VCI 1/100

Sink VPI/VCI 70/32

Connection 2


Sink VPI/VCI 71/32

Connection 3


Sink VPI/VCI 72/32

Table 10-5 lists the configuration parameters of Qos.

Table 10-5 Service types and QoS requirements

ApplicationScenario

ATM Policy PW Bandwidth TunnelBandwidth

Audio service,which is carried bythe RT-VBR type.

l Policy ID: 1

l Policy name: RT-VBR

l Service type: RT-VBR

l Traffic type:ClpNoTaggingScrCdvt

l Clp01Pcr(cell/s): 4000

l Clp0Scr(cell/s): 1000

l MBS(cell): 100

l CDVT(us): 10000

l Enable Traffic FrameDiscarding Flag: No

l UPC/NPC: Enabled

Bandwidth: 4 Mbit/s 30M bit/s



10-21

ApplicationScenario

ATM Policy PW Bandwidth TunnelBandwidth

Signal service,which is carried bythe CBR type.

l Policy ID: 2

l Policy name: CBR

l Service type: CBR

l Traffic type: NoClpNoScr

l Clp01Pcr(cell/s): 800


l UPC/NPC: Enabled

Bandwidth: 1 Mbit/s

Data service, whichis carried by theUBR type.

Policy name: Policy3Service type: UBRTraffic type: NoClpNoScrPCR: 9000 cell/sl Policy ID: 3

l Policy name: UBR

l Service type: UBR

l Traffic type:NoTrafficDescriptor


l UPC/NPC: Disabled

Bandwidth: 15 Mbit/s

10.4.3 Configuring an ATM Service on a Route BasisThis section describes the process of configuring a UNI-UNI ATM service on a route basis.




Procedure

Step 1 Configure three ATM policies: CBR, RT-VBR, UBR.1. Configure the CBR policy, refer to QoS Configuration Case of the ATM Service in Feature

Description.2. Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service in

Feature Description.


Configuration Guide


Issue 06 (2009-06-01)

3. Configure the UBR policy, refer to QoS Configuration Case of the ATM Service in FeatureDescription.

Step 2 Configure ATM interface: NodeB-side ATM interface and RNC-side ATM interface.1. Configure the NodeB-side ATM interface.

a. In the NE Explorer, select NE1 and choose Configuration > InterfaceManagement > PDH Interface from the Function Tree. Then, configure the NodeB-side interface.

b. Select 19-D75-3(Port-3) and 19-D75-4(Port-4). Right click the Port Mode field, andselect Layer 2. Set the parameters as required, and click Apply.

NOTE


The configuration parameters are as follows:l Port: 19-D75-3(Port-3), 19-D75-4(Port-4)

l Name: NodeB ATM (Set the port name as required. The port name distinguishesthe port from other ports and helps to query the port.)

l Port Mode: Layer 2 (The port transmits IMA signals.)

l Encapsulation: ATM

c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 19-D75-3(Port-3) and 19-D75-4(Port-4). Click Apply.The configuration parameters are as follows:l Port: 19-D75-3(Port-3) and 19-D75-4(Port-4)

l Frame Format: CRC-4 Multiframe (Set the Frame Format as the same as theparameter of NodeB.)

l Frame Mode: 31

d. Choose Configuration > Interface Management > ATM IMA Management fromFunction Tree, and click the Binding tab.

e. In the Binding tab, click Configuration and set the parameters such as AvailableBoards, Configuration Ports. Then, click OK.

The configuration parameters are as follows:l Available Boards: 1-MP1 (Set this parameter according to networking planning.)



10-23

l Configuration Ports: 1-MP1-1-MD1-1(Trunk-1) (Set this parameter according tonetworking planning.)

l Available Bound Paths Level: E1 (Select E1 for an ATM E1 board and VC12-xvfor an ATM STM-1 board. Herein, the board is an ATM E1 board.)

l Direction: Bidirectional (Default)

l Optical Interface: - (This parameter need not be set for E1, but need be set forVC12-xv. Herein, the path level is E1.)

l Available Resources: 19-D75-3(Port-3), 19-D75-4(Port-4)

l Available Timeslots: - (This parameter need not be set for E1, but need be set forVC12-xv.)

f. In the IMA Group Management tab, double-click the IMA Protocol EnableStatus field and select Enabled. Set the other parameters as required. Then, clickApply.

The configuration parameters are as follows:Set the IMA Protocol Version, IMA Transmit Frame Length, IMA SymmetryMode, Maximum Delay Between Links, Minimum Number of ActiveTransmitting Links, and Minimum Number of Active Receiving Links parametersas the same as these parameters of NodeB.

g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bitsand Max. VCI Bits for the interface. Then, click Apply.The configuration parameters are as follows:l Port Type: UNI (A UNI interface is connected to the client equipment and an NNI

interface is connected to ATM equipment in the core network.)l ATM Cell Payload Scrambling: Enabled

l Max. VPI Bits: 8 (Set this parameter according to networking planning. Set Max.VPI Bits to specify the value range of VPI. The VPI ranges from 0 to2MaxVPIbits-1.)

l Max. VCI Bits: 7 (Set this parameter according to networking planning. Set Max.VCI Bits to specify the value range of VCI. The VCI ranges from 0 to2MaxVCIbits-1.)

l VCC-Supported VPI Count: 32 (Set this parameter according to networkingplanning.)

l Loopback: Non-Loopback

2. Configure the RNC-side ATM interface.

a. In the NE Explorer, select NE1 and choose Configuration > InterfaceManagement > SDH Interface from the Function Tree. Configure the RNC-sideinterface.

b. In the Layer 2 Attributes tab, select 2-MP1-1-AD1-1(1-AD1.PORT-1), and set theparameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, clickApply.The configuration parameters are as follows:


Configuration Guide


Issue 06 (2009-06-01)

l Port Type: UNI

l ATM Cell Payload Scrambling: Enabled

l Max.VPI Bits: 8

l Max.VCI Bits: 7

l VCC-Supported VPI Count: 32

Step 3 Create a UNI-UNI ATM service, add three connections.1. Choose Trail > PTN Service > ATM Service Creation from the Main Menu.2. In the displayed Create ATM Service dialog box, set the parameters such as Service ID,

Service Name, Connection Type, Source NE, and Sink NE.


l Service Name: ATMService-10

l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connectioncan be modified; PVP indicates that only the VPI of the ATM connection can bemodified.)

l Source NE: NE1

l Source Port: 1-MP1-1-MD1-Trunk1

l Sink NE: NE1

l Sink Port: 2-MP1-1-AD1-1(Port-1)

3. In the Create ATM Service, click Add to add connections. Set the parameters as needed,and click Finish to complete the service configuration.



10-25

The configuration parameters are as follows:l Connection 1

– Name: Connection 1

– Source Port: NE1-1-MP1-1-MD1-Trunk1

– Source VPI: 1 (the VPI information transmitted with the service from NodeB)

– Source VCI: 100 (the VCI information transmitted with the service from NodeB)

– Sink Port: NE1-2-MP1-1-AD1-1(Port-1)

– Sink VPI: 70 (The VPI information transmitted with the service after VPI switching.The Sink VPI ranges from 0 to 2MaxVPIbits-1.)

– Sink VCI: 32 (The VCI information transmitted with the service after VCI switching.The Sink VCI ranges from 0 to 2MaxVCIbits-1.)

– Uplink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, becauseconnection 1 is an R99 service.)

– Downlink ATM Policy Name(ID): RT-VBR (Select the RT-VBR policy, becauseconnection 1 is an R99 service.)

– Transit VPI: -

– Transit VCI: -

l Connection 2


Configuration Guide


Issue 06 (2009-06-01)


– Source Port: NE1-1-MP1-1-MD1-Trunk1

– Source VPI: 1

– Source VCI: 101


– Sink VPI: 71

– Sink VCI: 32

– Uplink ATM Policy Name(ID): UBR (policy) (Select the UBR policy, becauseconnection 2 is an HSDPA service.)

– Downlink ATM Policy Name(ID): UBR (policy)(Select the UBR policy, becauseconnection 2 is an HSDPA service.)

– Transit VPI: -

– Transit VCI: -

l Connection 3– Source Port: NE1-1-MP1-1-MD1-Trunk1

– Source VPI: 1

– Source VCI: 102


– Sink VPI: 72

– Sink VCI: 32

– Uplink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, becauseconnection 3 is a signalling service.)

– Downlink ATM Policy Name(ID): CBR (policy) (Select the CBR policy, becauseconnection 3 is a signalling service.)

– Transit VPI: -

– Transit VCI: -

----End

10.4.4 Configuring an ATM Service on a Per-NE BasisThis section describes the process of configuring a UNI-UNI ATM service on a per-NE basis.




Procedure


Description.



10-27

2. Configure the RT-VBR policy, refer to QoS Configuration Case of the ATM Service inFeature Description.

3. Configure the UBR policy, refer to QoS Configuration Case of the ATM Service in FeatureDescription.

Step 2 Configure ATM interface: NodeB-side ATM interface and RNC-side ATM interface.1. Configure the NodeB-side ATM interface.


b. Select 19-D75-3(Port-3) and 19-D75-4(Port-4). Right click the Port Mode field, andselect Layer 2. Set the parameters as required, and click Apply.

NOTE


The configuration parameters are as follows:l Port: 19-D75-3(Port-3), 19-D75-4(Port-4)




c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 19-D75-3(Port-3) and 19-D75-4(Port-4). Click Apply.The configuration parameters are as follows:l Port: 19-D75-3(Port-3) and 19-D75-4(Port-4)


l Frame Mode: 31


e. In the Binding tab, click Configuration and set the parameters such as AvailableBoards, Configuration Ports. Then, click OK.


Configuration Guide


Issue 06 (2009-06-01)


l Available Boards: 1-MP1 (Set this parameter according to networking planning.)

l Configuration Ports: 1-MP1-1-MD1-1(Trunk-1) (Set this parameter according tonetworking planning.)

l Available Bound Paths Level: E1 (Select E1 for an ATM E1 board and VC12-xvfor an ATM STM-1 board. Herein, the board is an ATM E1 board.)



l Available Resources: 19-D75-3(Port-3), 19-D75-4(Port-4)


f. In the IMA Group Management tab, double-click the IMA Protocol EnableStatus field and select Enabled. Set the other parameters as required. Then, clickApply.


Set the IMA Protocol Version, IMA Transmit Frame Length, IMA SymmetryMode, Maximum Delay Between Links, Minimum Number of ActiveTransmitting Links, and Minimum Number of Active Receiving Links parametersas the same as these parameters of NodeB.

g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bitsand Max. VCI Bits for the interface. Then, click Apply.


l Port Type: UNI (A UNI interface is connected to the client equipment and an NNIinterface is connected to ATM equipment in the core network.)










10-29

b. In the Layer 2 Attributes tab, select 2-MP1-1-AD1-1(1-AD1.PORT-1), and set theparameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, clickApply.


l Port Type: UNI


l Max.VPI Bits: 8

l Max.VCI Bits: 7


Step 3 Configure a UNI-UNI ATM service.

1. Choose Configuration > ATM Service Management from the Function Tree.

2. In the Connection tab, click New. The New ATM Service window is displayed. In thewindow, configure a UNI-UNI service.


l Service ID: 10

l Service Name: ATMService-10

l Service Type: UNI-UNI


3. Click the Connection tab and click Add to add connection 1 and connection 2. Then, clickOK.



Configuration Guide


Issue 06 (2009-06-01)

l Connection 1– Connection Name: Connection 1

– Source Board: 1-MP1

– Source Port: 1-MD1-1(Trunk1)



– PW ID: -

– Sink Board: 2-MP1

– Sink Port: 1-AD1-1(Port-1)



– Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99service.)

– Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is anR99 service.)




– Source VPI: 1

– Source VCI: 101

– PW ID: -



– Sink VPI: 71

– Sink VCI: 32

– Uplink Policy: UBR (policy) (Select the UBR policy, because connection 2 is anHSDPA service.)

– Downlink Policy: UBR (policy) (Select the UBR policy, because connection 2 is anHSDPA service.)

l Connection 3– Source Board: 1-MP1


– Source VPI: 1

– Source VCI: 102

– PW ID: -





10-31

– Sink VPI: 72

– Sink VCI: 32

– Uplink Policy: CBR (Select the CBR policy, because connection 2 is a signallingservice.)

– Downlink Policy: CBR (Select the CBR policy, because connection 2 is a signallingservice.)

----End

10.5 Configuration Case of the UNIs-NNI ATM ServiceThis section describes a configuration case of the UNIs-NNI ATM service. The configurationflow diagram is provided to describe the configuration process. The configuration case includesservice planning and ATM service configuration.

10.5.1 Networking DiagramThis section describes the networking diagram for the case where the R99 service, Signallingservice and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC.

10.5.2 Service PlanningTo transport the R99, Signalling and HSDPA services between NodeB1 and RNC, NodeB2 andRNC respectively, three ATM services must be created.

10.5.3 Configuring an ATM Service on a Route BasisThis section describes the process of configuring a UNIs-NNI ATM service on a route basis.

10.5.4 Configuring an ATM Service on a Per-NE BasisThis section describes the process of configuring a UNIs-NNI ATM service on a per-NE basis.

10.5.1 Networking DiagramThis section describes the networking diagram for the case where the R99 service, Signallingservice and HSDPA service are transported between NodeB1 and RNC, NodeB2 and RNC.

Figure 10-7 shows the networking diagram of the UNIs-NNI ATM service. The 3G R99,signalling and HSDPA services are required between the two base stations and RNC. NE1accesses the MPLS network formed by the PTN equipment. Node B1 is connected to NE1through IMA1, and Node B2 is connected to NE1 through IMA2. The VPI/VCI switching isperformed on NE1, and the VPI/VCI transparent transmission is performed on NE2 and NE3.Between NE1 and NE3, three PWs are used to carry the R99, signalling and HSDPA servicesrespectively. At the remote end, to transparently transmit the ATM service in the MPLS network,NE3 is connected to RNC through STM-1. NE1 is an OptiX PTN 1900 NE, and NE2, NE3,NE4, NE5 are OptiX PTN 3900s, and NE6 is an OptiX PTN 950. The ATM services are carriedby the working tunnel. The protection tunnel can be created to protect the services that have highreal-time requirement.

The working tunnel is NE1-NE2-NE3, and the protection tunnel is NE1-NE6-NE5-NE4-NE3.


Configuration Guide


Issue 06 (2009-06-01)

Figure 10-7 Networking of the ATM service

Working Tunnel

NodeB 1

RNC

NE1 NE2

NE3

NE4NE5

NE6

NodeB 2

pw1

pw3

pw2

IMA1

IMA2

ATM STM-1

UNI NNIVPI1

VCI100

1 101R99

HSDPA

VPI50

VCI32

51 32Signalling 1 102 52 32

UNIVPI50

VCI32

51 3252 32

IMA1:

NNIVPI60

VCI32

61 3262 32

UNIVPI60

VCI32

61 3262 32

IMA2:

NNIVPI50

VCI32

51 3252 32

NNIVPI60

VCI32

61 3262 32

PW



layer

Connection1

Connection2

Connection3

UNIVPI1

VCI100

1 101R99

HSDPASignalling 1 102

Connection1

Connection2

Connection3

Protection Tunnel



3-MP1-AD1

Working tunnel

Protection tunnelNodeB 1

RNC

NE1 NE2 NE3

NE4NE5

NE6

4-EFG2-1(Port-1)10.0.0.1

4-EFG2-2(Port-2)10.0.5.1

3-EG16-1(Port-1)10.0.0.2

1-EX2-1(Port-1)10.0.1.2

1-EX2-1(Port-1)10.0.1.1

1-EX2-2(Port-2)10.0.2.1

2-EG2-2(Port-2)10.0.4.1

3-EG16-1(Port-1)10.0.4.2

1-EX2-1(Port-1)10.0.3.2 1-EX2-1(Port-1)

10.0.2.2

1-EX2-2(Port-2)10.0.3.1



layer

NodeB 2

1-CXP-MD1-3-L12

10.5.2 Service PlanningTo transport the R99, Signalling and HSDPA services between NodeB1 and RNC, NodeB2 andRNC respectively, three ATM services must be created.

Between NE1 and NE3, the R99 service is carried by PW1, the HSDPA service is carried byPW2, and the Signalling service is carried by PW3. Thus, three ATM services should be created.



10-33

At the two base stations, the R99 service is aggregated and the Signalling service and HSDPAservice is accessed. Thus, two ATM services connected to the N:1 VCC should be created. Theservice shown in Figure 10-7 is taken as an example.




NE1 1.0.0.14-EFG2-1(Port-1) 10.0.0.1 255.255.255.252

4-EFG2-2(Port-2) 10.0.5.1 255.255.255.252

NE2 1.0.0.23-EG16-1(Port-1) 10.0.0.2 255.255.255.252

1-EX2-1(Port-1) 10.0.1.1 255.255.255.252

NE3 1.0.0.31-EX2-1(Port-1) 10.0.1.2 255.255.255.252

1-EX2-2(Port-2) 10.0.2.1 255.255.255.252

NE4 1.0.0.41-EX2-1(Port-1) 10.0.2.2 255.255.255.252

1-EX2-2(Port-2) 10.0.3.1 255.255.255.252

NE5 1.0.0.51-EX2-1(Port-1) 10.0.3.2 255.255.255.252

3-EG16-1(Port-1) 10.0.4.2 255.255.255.252

NE6 1.0.0.64-EFG2-1(Port-1) 10.0.5.2 255.255.255.252

4-EFG2-2(Port-2) 10.0.4.1 255.255.255.252



Tunnel ID 100 101 120 121





Signal Type Dynamic Dynamic Dynamic Dynamic

SchedulingType


Bandwith(kbit/s)


Source Node NE1 NE1

Sink Node NE3 NE3


Configuration Guide


Issue 06 (2009-06-01)


RouteConstraintPort IPAddress

IP addresses ofingress port ofNE2: 3-EG16-1(Port-1)10.0.0.2IP addresses ofingress port ofNE3: 1-EX2-1(Port-1)10.0.1.2

IP addresses ofingress port ofNE2: 1-EX2-2(Port-2) 10.1.2.2IP addresses ofingress port ofNE1: 4-EFG2-1(Port-1) 10.1.1.2

IP addresses ofingress port ofNE6: 2-EG2-1(Port-1) 10.0.5.2IP addresses ofingress port ofNE5: 3-EG16-1(Port-1) 10.0.4.2IP addresses ofingress port ofNE4: 1-EX2-2(Port-2) 10.0.3.1IP addresses ofingress port ofNE3: 1-EX2-2(Port-2) 10.0.2.1

IP addresses ofingress port ofNE4: 1-EX2-1(Port-1) 10.0.2.2IP addresses ofingress port ofNE5: 1-EX2-2(Port-2) 10.0.3.2IP addresses ofingress port ofNE6: 2-EG2-2(Port-2) 10.0.4.1IP addresses ofingress port ofNE1: 4-EFG2-2(Port-2) 10.0.5.1


Attribute Remarks

BaseStation ofService

NodeB1 NodeB2

IMAGroup

IMA1 IMA2

SourcePort

1-CXP-1-MD1-1(Trunk1) 1-CXP-1-MD1-2(Trunk2)

Service R99 HSDPA Signalling R99 HSDPA Signalling

SourceVPI/VCI

1/100 1/101 1/102 1/100 1/101 1/102

Sink VPI/VCI

50/32 51/32 52/32 60/32 61/32 62/32

PW ofService

PW1 PW2 PW3 PW1 PW2 PW3

PW ID 35 36 37 35 36 37




10-35


Attribute

Remarks Remarks

Service R99 HSDPA Signalling R99 HSDPA Signalling

Source(VPI/VCI)

50/32 51/32 52/32 60/32 61/32 52/32

Sink(VPI/VCI)

50/32 51/32 52/32 60/33 61/33 52/32

PW ofService

PW1 PW2 PW3 PW1 PW2 PW3

PW ID 35 36 37 35 36 37

Sink Port 3-MP1-1-AD1-1(1-AD1.PORT-1)

10.5.3 Configuring an ATM Service on a Route BasisThis section describes the process of configuring a UNIs-NNI ATM service on a route basis.

Prerequisite




Procedure



Apply.






Configuration Guide


Issue 06 (2009-06-01)

l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6















l IP Mask: 255.255.255.252






10-37









l NE6-4-EFG2-1(Port-1)Max Reserved Bandwidth (kbit/s): 1000000IP Address: 10.0.5.2





The configuration parameters are as follows:l IS-IS Enable: Enabled (After the IS-IS routing protocol is enabled, PW labels can be

distributed dynamically.)l Link Level: level-1-2

l LSP Retransmission Interval(s): 5 (In the case of a point-to-point link, if the localequipment fails to receive any response in a period after transmitting the LSP, the local


Configuration Guide


Issue 06 (2009-06-01)

equipment considers that the LSP is lost or discarded. To ensure the transmissionreliability, the local equipment transmits the LSP again.)



NOTE






maintain the LDP session.)5. In the NE Explorer, select NE3. Set the parameters related to the control plane by following

Step 3.1 to Step 3.4.

Set the IS-IS parameters of NE3 as the same as the IS-IS parameters of NE1. Set the LDPparameters as follows:l Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal

NE on the PW, that is, NE1 in this case.)

Step 4 Creating Working MPLS Tunnel.1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box






10-39

l Tunnel ID: 1 (Positive), 2 (Reverse)





l EXP:- (tunnel priority.)




l Sink Node: NE3












Feature Description.3. Configure the UBR policy, refer to QoS Configuration Case of the ATM Service in Feature

Description.


Configuration Guide


Issue 06 (2009-06-01)

Step 6 Configure interfaces: NodeB-side ATM interface and RNC-side ATM interface.1. Configure the NodeB-side ATM interface.


b. Select 3-L12-1(Port-1) to 3-L12-8(Port-8). Right-click the Port Mode field andchoose Layer 2. Then, click Apply.

NOTE


The configuration parameters are as follows:l Port: 3-L12-1(Port-1) to 3-L12-8(Port-8)




c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3-L12-1(Port-1) to 3-L12-8(Port-8). Click Apply.The configuration parameters are as follows:l Port: 3-L12(Port-1) to 3-L12-8(Port-8)


l Frame Mode: 31


e. In the Binding tab, click Configuration and set the ports to be bound with 1-CXP-1-MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2). Then, click OK.Set the parameters related to 1-CXP-1-MD1-1(Trunk1) as follows:l Available Boards: 1-CXP

l Configuration Ports: 1-CXP-1-MD1-1(Trunk1)

l Available Bound Paths Level: E1– E1: In the case of the E1 boards, when the E1 level is selected, the entire E1

channel is used to transport ATM IMA signals.– VC12-xv: In the case of the ATM STM-1 boards, the STM-1 VC-4 path

contains 63xVC-12 lower order paths. When the VC12-xv level is selected,certain VC-12 lower order paths of the VC-4 path are used to transport ATMIMA signals.



l Available Resources: 3-L12-1(Port-1) to 3-L12-4(Port-4)


Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:



10-41

l Available Boards: 1-CXP


l Available Bound Paths Level: E1

l Direction: Bidirectional

l Optical Interface: -


l Available Timeslots: -

f. In the IMA Group Management tab, double-click the IMA Protocol EnableStatus field and select Enabled. Set the other parameters as required. Then, clickApply.The configuration parameters are as follows:Set the IMA Protocol Version, IMA Transmit Frame Length, IMA SymmetryMode, Maximum Delay Between Links, Minimum Number of ActiveTransmitting Links, and Minimum Number of Active Receiving Links parametersas the same as these parameters of NodeB.









b. In the Layer 2 Attributes tab, select 3-MP1-1-AD1-(1-AD1.PORT-1) and set theparameters such as Max. VPI Bits and Max. VCI Bits for the interface. Then, clickApply.

The configuration parameters are as follows:l Port Type: UNI



Configuration Guide


Issue 06 (2009-06-01)

l Max.VPI Bits: 8

l Max. VCI Bits: 7


Step 7 Create three UNIs-NNI ATM services.1. Choose Trail > PTN Service > ATM Service Creation from the Main Menu. Create an

R99 service from NE1 to NE3.2. In the displayed Create ATM Service dialog box, set the parameters such as Service ID,

Service Name, Connection Type, Source NE, and Sink NE.


l Service Name: ATMService-R99


l Source NE: NE1

l Source Port: 1-CXP-1-MD1-1(Trunk1) and 1-CXP-1-MD1-2(Trunk2)

l Sink NE: NE3

l Sink Port: 3-MP1-1-AD1-1(Port-1)

3. In the Create ATM Service, click Add to add connections.



– Source Port: NE1-1-CXP-1-MD1-Trunk1








– Transit VPI: -

– Transit VCI: -

l Connection 2– Name: Connection 2

– Source Port: NE1-1-CXP-1-MD1-2(Trunk2)

– Source VPI: 1



10-43

– Source VCI: 100


– Sink VPI: 60

– Sink VCI: 32



– Transit VPI: -

– Transit VCI: -

4. Click Next and set PW-related parameters.

The configuration parameters are as follows:l PW ID: 35

l Protocol Type: Dynamic (Dynamic indicates that the LDP protocol distributes the PWlabels; Static indicates that the ingress and egress labels are manually added.)

l Encapsulation Type: ATM n-to-one VPC cell transport (Select ATM n-to-one VPCcell transport if multiple ATM connections are mapped to one PW; select ATM one-to-one VCC Cell Mode if one ATM connection is mapped to one PW. Herein, twoATM connections are mapped to one PW.)



l Tunnel Name (ID): Tunnel-001(Uplink), Tunnel-002(Downlink)

l Control Word Use Policy: Must use

l Control Channel Type: CW (CW realizes connectivity check of the PW.)

l VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.)

l Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can beencapsulated in each packet)

l Packet Loading Time (us): 1000

l Bandwidth Enabled: Enabled

l CIR (kbit/s): 4096 (Set the bandwidth according to the service traffic.)

l CBS (byte): -

l PIR (kbit/s): 10240

l PBS (byte): -

l EXP: 1

l NE: NE1

l CoS Mapping Name(ID): 1(mapping1)

l NE: NE3

l CoS Mapping Name(ID): 1(mapping1)

5. Click Finish. The ATMService-R99 service is successfully created.6. Repeat the previous steps to create an ATMService-HSDPA service.


Configuration Guide


Issue 06 (2009-06-01)

l Set the general attributes of the ATM service as follows:– Service ID: 2

– Service Name: ATMService-HSDPA

– Connection Type: PVC

– Source NE: NE1

– Source Port: 1-CXP-1-MD1-1(Trunk1), 1-CXP-1-MD1-2(Trunk2)

– Sink NE: NE3

– Sink Port: 3-MP1-1-AD1-1(1-AD1.PORT-1)

l Configure ATM connections:– Connection 1



– Source VPI: 1

– Source VCI: 101

– Sink Port: NE3-3-MP1-1-AD1-1(1-AD1.PORT-1)

– Sink VPI: 51

– Sink VCI: 32

– Uplink ATM Policy Name (ID): UBR (policy)

– Downlink ATM Policy Name (ID): UBR (policy)

– Transit VPI: -

– Transit VCI: -

– Connection 2– Name: Connection 2


– Source VPI: 1

– Source VCI:101


– Sink VPI: 61

– Sink VCI: 32

– Uplink ATM Policy Name (ID): UBR (policy)

– Downlink ATM Policy Name (ID): UBR (policy)

– Transit VPI: -

– Transit VCI: -

l Set the PW-related parameters as follows:– PW ID: 36

– Protocol Type: Dynamic

– Encapsulation Type: ATM n-to-one VPC cell transport

– Direction: Bidirectional



10-45

– Tunnel Type: MPLS Tunnel

– Tunnel Name (ID): Tunnel-001

– Control Word Use Policy: Must use

– Control Channel Type: CW

– VCCV Verification Mode: Ping

– Max. Concatenated Cell Count: 20

– Packet Loading Time (us): 1000

– Bandwidth Enabled: Enabled

– CIR (kbit/s): 4096

– CBS (byte): -

– PIR (kbit/s): 10240

– PBS (byte): -

– EXP: 3

– NE: NE1

– CoS Mapping Name(ID): 1(mapping1)

– NE: NE3


7. Repeat the previous steps to create an ATMService-Sinalling service.l Set the general attributes of the ATM service as follows:

– Service ID: 23

– Service Name: ATMService-Sinalling


– Source NE: NE1

– Source Port: 1-1-CXP-1-MD1-1(Trunk1), 1-1-CXP-1-MD1-2(Trunk2)

– Sink NE: NE3

– Sink Port: 3-MP1-1-AD1-1(1-AD1.PORT-1)




– Source VPI: 1

– Source VCI: 102


– Sink VPI: 52

– Sink VCI: 32

– Uplink ATM Policy Name (ID): CBR

– Downlink ATM Policy Name (ID): CBR

– Transit VPI: -


Configuration Guide


Issue 06 (2009-06-01)

– Transit VCI: -

– Connection 2– Name: Connection 2


– Source VPI: 1

– Source VCI:102


– Sink VPI: 62

– Sink VCI: 32

– Uplink ATM Policy Name (ID): CBR

– Downlink ATM Policy Name (ID): CBR

– Transit VPI: -

– Transit VCI: -

l Set the PW-related parameters as follows:– PW ID: 37

– Protocol Type: Dynamic

– Encapsulation Type: ATM n-to-one VPC cell transport


– Tunnel Type: MPLS Tunnel

– Tunnel Name (ID): Tunnel-001

– Control Word Use Policy: Must use





– Bandwidth Enabled: Enabled

– CIR (kbit/s): 4096

– CBS (byte): -

– PIR (kbit/s): 10240

– PBS (byte): -

– EXP: 0

– NE: NE1


– NE: NE3


----End

10.5.4 Configuring an ATM Service on a Per-NE BasisThis section describes the process of configuring a UNIs-NNI ATM service on a per-NE basis.



10-47




Procedure



Apply.





l NE3 LSR ID: 1.0.0.3

l NE4 LSR ID: 1.0.0.4

l NE5 LSR ID: 1.0.0.5

l NE6 LSR ID: 1.0.0.6









Configuration Guide


Issue 06 (2009-06-01)








l IP Mask: 255.255.255.252













10-49







The configuration parameters are as follows:l IS-IS Enable: Enabled (After the IS-IS routing protocol is enabled, PW labels can be

distributed dynamically.)l Link Level: level-1-2




NOTE






maintain the LDP session.)5. In the NE Explorer, select NE3. Set the parameters related to the control plane by following


Set the IS-IS parameters of NE3 as the same as the IS-IS parameters of NE1. Set the LDPparameters as follows:l Opposite LSR ID: 1.0.0.1 (The opposite LSR ID indicates the LSR ID of the terminal

NE on the PW, that is, NE1 in this case.)


Configuration Guide


Issue 06 (2009-06-01)

Step 4 Creating Working MPLS Tunnel.1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box












l Sink Node: NE3







10-51








Feature Description.3. Configure the UBR policy, refer to QoS Configuration Case of the ATM Service in Feature

Description.




NOTE






c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3-L12-1(Port-1) to 3-L12-8(Port-8). Click Apply.The configuration parameters are as follows:l Port: 3-L12(Port-1) to 3-L12-8(Port-8)



Configuration Guide


Issue 06 (2009-06-01)

l Frame Mode: 31











Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:l Available Boards: 1-CXP












10-53










l Max.VPI Bits: 8

l Max. VCI Bits: 7





NOTE






c. In the Advanced Attributes tab, set the Frame Format, Frame Mode of the 3-L12-1(Port-1) to 3-L12-8(Port-8). Click Apply.


Configuration Guide


Issue 06 (2009-06-01)

The configuration parameters are as follows:l Port: 3-L12(Port-1) to 3-L12-8(Port-8)


l Frame Mode: 31











Set the parameters related to 1-CXP-1-MD1-2(Trunk2) as follows:l Available Boards: 1-CXP








g. In the ATM Interface Management tab, set the parameters such as Max. VPI Bitsand Max. VCI Bits for the interface. Then, click Apply.The configuration parameters are as follows:



10-55

l Port Type: UNI (A UNI interface is connected to the client equipment and an NNIinterface is connected to ATM equipment in the core network.)











l Max.VPI Bits: 8

l Max. VCI Bits: 7


Step 8 Configure three UNIs-NNI ATM services.1. In the NE Explorer, select NE1 and choose Configuration > ATM Service

Management from the Function Tree. Then, create an R99 service from NE1 to NE3.2. In the Connection tab, click New. The New ATM Service window is displayed. Then,

set Service ID, Service Name, Service Type, and Connection Type.


l Service Name: ATMService-R99

l Service Type: UNIs-NNI


3. Click the Connection tab and click Add. The Configure Connection window is displayed.Add connection 1 and connection 2.


Configuration Guide


Issue 06 (2009-06-01)


– Connection Name: Connection 1

– Source Board: 1-CXP




– PW ID: 35

– Sink Board: -

– Sink Port: -








– Source VPI: 1

– Source VCI: 100

– PW ID: 35

– Sink Board: -



10-57

– Sink Port: -

– Sink VPI: 60

– Sink VCI: 32



4. Click the PW tab and click Add. The Configure PW window is displayed. In the window,set attributes of the PW.

Set the parameters related to PW1 as follows:l General Attributes

– PW ID: 35

– PW Signaling Type: Dynamic (Dynamic indicates that the LDP protocol distributesthe PW labels; Static indicates that the ingress and egress labels are manually added.)

– PW Type: ATM n to one VCC cell transport (Select ATM n-to-one VPC celltransport if multiple ATM connections are mapped to one PW; select ATM one-to-one VCC Cell Mode if one ATM connection is mapped to one PW. Herein, twoATM connections are mapped to one PW.)


– PW Ingress Label: -

– PW Egress Label: -

– Tunnel Type: MPLS

– Tunnel: 1(Tunnel-00001)

– Peer IP: 1.0.0.3

l Advanced Attributes– Control Word: Must use

– Control Channel Type: CW (CW realizes connectivity check of the PW.)

– VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.)

– Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can beencapsulated in each packet)


l QoSIngress– EXP: 1

5. Click the CoS Mapping tab and set the QoS attribute of PW1.

Set the QoS mapping for PW1 as follows:l PW ID: 35

l CoS Mapping: mapping1(1)

6. In the NE Explorer, select NE3. Then, create an ATMService-R99 service by following1 to 5.



Configuration Guide


Issue 06 (2009-06-01)

l Set the general attributes of the ATM service as follows:– Service ID: 1

– Service Name: ATMService-R99

– Service Type: UNIs-NNI


l Configure ATM Connection:– Connection 1



– Source Port: 1-AD1-1(1-AD1.PORT-1)

– Source VPI: 50

– Source VCI: 32

– PW ID: 35

– Sink Board: -

– Sink Port: -

– Sink VPI: 50

– Sink VCI: 32

– Uplink ATM Policy Name (ID): RT-VBR

– Downlink ATM Policy Name (ID): RT-VBR

– Connection 2– Connection Name: Connection 2



– Source VPI: 60

– Source VCI: 32

– PW ID: 35

– Sink Board: -

– Sink Port: -

– Sink VPI: 60

– Sink VCI: 32

– Uplink ATM Policy Name (ID): RT-VBR

– Downlink ATM Policy Name (ID): RT-VBR

l Set the parameters related to PW1 as follows:– General Attributes

– PW ID: 35

– PW Signaling Type: Dynamic

– PW Type: ATM n to 1 VCC cell transport





10-59




– Peer IP: 1.0.0.1

– Advanced Attributes– Control Word: Must Use





– QoSIngress– EXP: 1

l The CoS mapping of PW1 should be configured:– PW ID: 35

– CoS Mapping: 1(mapping1)

7. Create an ATMService-HSDPA service by following 1 to 6.

Set the parameters related to NE1 as follows:l Set the general attributes of the ATM service as follows:

– Service ID: 2








– Source VPI: 1

– Source VCI: 101

– PW ID: 36

– Sink Board: -

– Sink Port: -

– Sink VPI: 51

– Sink VCI: 32

– Uplink Policy: UBR

– Downlink Policy: UBR

– Connection 2


Configuration Guide


Issue 06 (2009-06-01)




– Source VPI: 1

– Source VCI: 101

– PW ID: 36

– Sink Board: -

– Sink Port: -

– Sink VPI: 61

– Sink VCI: 32




– PW ID: 36








– Peer IP: 1.0.0.3










– Service ID: 2



10-61








– Source VPI: 51

– Source VCI: 32

– PW ID: 36

– Sink Board: -

– Sink Port: -

– Sink VPI: 51

– Sink VCI: 32






– Source VPI: 61

– Source VCI: 32

– PW ID: 36

– Sink Board: -

– Sink Port: -

– Sink VPI: 61

– Sink VCI: 332




– PW ID: 36







Configuration Guide


Issue 06 (2009-06-01)



– Peer IP: 1.0.0.1









8. Create an ATMService-Signalling service by following 1 to 6.


– Service ID: 3

– Service Name: ATMService-Signalling







– Source VPI: 1

– Source VCI: 102

– PW ID: 37

– Sink Board: -

– Sink Port: -

– Sink VPI: 52

– Sink VCI: 32






10-63



– Source VPI: 1

– Source VCI: 102

– PW ID: 37

– Sink Board: -

– Sink Port: -

– Sink VPI: 62

– Sink VCI: 32

– Uplink Policy: CBR

– Downlink Policy: CBR


– PW ID: 37








– Peer IP: 1.0.0.3










– Service ID: 3

– Service Name: ATMService-Signalling


Configuration Guide


Issue 06 (2009-06-01)







– Source VPI: 52

– Source VCI: 32

– PW ID: 37

– Sink Board: -

– Sink Port: -

– Sink VPI: 52

– Sink VCI: 32






– Source VPI: 62

– Source VCI: 32

– PW ID: 37

– Sink Board: -

– Sink Port: -

– Sink VPI: 62

– Sink VCI: 32




– PW ID: 37









10-65


– Peer IP: 1.0.0.1









----End

10.6 Verifying the Correctness of Service ConfigurationAfter the ATM service is configured, the correctness of service configuration should be verified.The ATM OAM is used for verifying the correctness of the ATM service configuration.

Case DescriptionThis case describes the ATM service carried by PWs. To verify the correctness of the service,the working state of the PW should be queried and the ATM OAM should be configured. Fordetails, see Figure 10-9. A UNIs-NNI ATM service from the base station to RNC is created.The service type is the N:1 VC switching. The source VPI/VCI is 32/33, and the sink VPI/VCIis 52/53. The correctness of the service should be verified.

Figure 10-9 Connection diagram for ATM service connectivity test

PSN

PE2

Inloop

PE1

Inloop

Procedure

Step 1 Set the loopback automatic disabling function to Disabled for the UNI interfaces accessing thetested ATM service on the PE1 and PE2 equipment.1. Choose Configuration > Automatic Disabling of NE Function from the Main Menu

to display the Automatic Disabling of NE Function dialog box.


Configuration Guide


Issue 06 (2009-06-01)

2. Select the PE1 and PE2 in the left-hand object tree and click . The selected NEsare displayed in Automatic Disabling of NE Function on the right.

3. Set Auto Disabling to Disabled for SDH Optical/Electrical Interface Loopback of thePE1 and PE2.

NOTE

When the automatic disabling function of SDH Optical/Electrical Interface Loopback on the NE is setto Disabled, the loopback automatic disabling function for all of the SDH optical interfaces (unavailableon the OptiX PTN 912), PDH electrical interfaces and ATM IMA groups on the NE is disabled.

Step 2 Set inloop for the UNI interface (to be tested) accessing the ATM service on PE1 by using theT2000.l The UNI interface accessing the ATM service is IMA group.

1. On the Main Topology, select and right-click the PE1 NE. In the shortcut menu,choose NE Explorer to display the NE Explorer window.

2. In the NE Explorer window, select the NE, and choose Configuration > InterfaceManagement > ATM IMA Management from the Function Tree.

3. Select the ATM Interface Management tab and then select the IMA group carryingthe tested ATM service.

4. Double-click the Loopback of the IMA group, and then select Inloop in the shortcutmenu.

5. Click Apply.l The UNI interface accessing the ATM service is AD1 interface.

1. On the Main Topology, select and right-click the PE1 NE. In the shortcut menu,choose NE Explorer to display the NE Explorer window.

2. In the NE Explorer window, select the AD1 carrying the tested ATM service, andchoose Configuration > Interface Management > SDH Interface from the FunctionTree.

3. Select the Advanced Attributes tab and then select the AD1 interface carrying theATM service.

4. Double-click the Loopback of AD1 interface, and then select Inloop in the shortcutmenu.

5. Click Apply.

Step 3 Set inloop for the UNI interface (to be tested) accessing the ATM service on PE2 with referenceto Step 2.

Step 4 In the NE Explorer window, select the PE1 NE, and choose Configuration > ATM OAMManagement from the Function Tree.

Step 5 Select the Remote Loopback Test tab, and then select the tested ATM service.

Step 6 Set the Segment End Attribute of the ATM service to Segment point or Endpoint.

NOTE

Segment End Attribute of ATM service specifies the type of the transmitted OAM cells during the LB test.

l If Segment End Attribute is set to Segment point, seg_LB cells is transmitted.

l If Segment End Attribute is set to Endpoint, e-t-e_LB cells is transmitted.

Step 7 Set the Loopback Point NE of the tested ATM service to PE2 NE.



10-67

Step 8 Click Test to start LB test.

Step 9 After the test is finished, check the Test Result of the tested ATM service.

Normally, the Test Result should be Test succeeded. If not, handle the fault with reference tothe OptiX PTN 3900 Packet Transport Platform of PTN Series Alarms and Performance EventsReference and OptiX PTN 3900 Packet Transport Platform of PTN Series Troubleshooting.

Step 10 Release the inloop of the UNI interface accessing the ATM service on PE1 and PE2 withreference to Step 2.

Step 11 Follow Step 2 - Step 10 to test the connectivity of all the other ATM services on PE1 and PE2.

Step 12 Set Automatic Disabling to Enabled for SDH Optical/Electrical Interface Loopback on PE1and PE2 with reference to Step 1.

Step 13 Test the connectivity of the ATM services on all the other NEs with reference to Step 1 - Step12.

----End

10.7 Parameter DescriptionThis section describes the parameters related to the ATM service configuration.

Table 10-10 Descriptions of the parameters for Creating ATM Services


Service ID Example: 5 Set the ID of the service, or set toautomatically assigned the ID of theservice.

Service Name 64 bytes Set the name of the service.

Connection Type PVP, PVC Select the switching type of the ATMservice.l PVP indicates that only the VPI values

of the source and sink are exchanged.l PVC indicates that both the VPI and

VCI values of the source and sink areexchanged.

Customer String Display the customer of the service.

Remarks String Indicate the description of the service.

NE Example: NE3 Display the source NE or sink NE of theservice.NOTE

l When configuring a UNIs-NNI service,select different NEs as the source and sink.

l When configuring a UNI-UNI service,select the same NE as the source and sink.


Configuration Guide


Issue 06 (2009-06-01)


Port Example: 1-MP1-1-MQ1(Trunk1)

Display the source port or sink port of theservice.

Name String Set the name of the ATM connection.

Source Port Example: NE3-1-MP1-1-MQ1(Trunk1)

Display the source port connected to theATM.

Source VPI 0-(2MaxVPIbits-1)For example, if the value ofMax. VPI Bits is 8, the VPIvalue ranges from 0 to(28-1), that is, 0 to 255.

Set the VPI value of the source port.

Source VCI 32-(2MaxVCIbits-1For example, if the value ofMax. VCI Bits 7, the VCIvalue ranges from 32 to(27-1), that is 32 to 127.

Set the VCI value of the source port.

Sink Port Example: NE3-1-MP1-1-MQ1(Trunk1)

Display the sink port connected to theATM.

Sink VPI 0-(2MaxVPIbits-1)Example: 25

Set the VPI value of the sink port.

Sink VCI 32-(2MaxVCIbits-1Example: 40

Set the VCI value of the sink port.

Uplink ATMPolicy Name (ID)

Example: Policy (NE2:12-NE3:12)

Select the QoS policy for the uplink ATMconnection. For details, see ATM Policy

Downlink ATMPolicy Name (ID)

Example: Policy (NE2:12-NE3:12)

Select the QoS policy for the downlinkATM connection. For details, see ATMPolicy

Transit VPI Example: 53 Set VPI at the network side.

Transit VCI Example: 53 Set VCI at the network side.

Table 10-11 Descriptions of the parameters for PW Attributes


PW ID Example: 5 Set the ID of the PW, or set toautomatically allocate the ID ofthe service.



10-69


Signaling Type Static, Dynamic Set the means for creating a PWand distributing the PW label.l Dynamic: The LDP protocol

is used to distribute the PWlabel. If you select Dynamic,Uplink Label and DownlinkLabel cannot be set.

l Static: The PW label isdistributed manually.

Working Status Example: Up Display the working status ofthe PW.

Type Example: ATM n-to-one VCCcell transport, ATM one-to-oneVCC

Set the PW type.The PW type corresponds to theservice type. In the case of theVPC and VPC services, twoencapsulation types areavailable, that is, 1:1 and N:1.

Encapsulation Type MPLS, UDP Sets the PW encapsulation type.When the PW EncapsulationType is set to MPLS, the MPLS,IP, and GRE tunnels aresupported; When the PWEncapsulation Type is set toUDP, only the IP tunnel issupported.

Direction Bidirectional Display the direction of the PW.

Uplink Label/SourcePort

16 to 1048575 Set the uplink label.When the TDM frame isencapsulated into the PW, labelsare attached on the packetheader. The uplink labelindicates that the service entersthe PW. The uplink label anddownlink label are different.When the PW encapsulationtype is set to UDP, the value ofthe uplink label of PW rangesfrom 49152 to 65535.


Configuration Guide


Issue 06 (2009-06-01)


Downlink Label/SinkPort

16 to 1048575 Set the downlink label.When the TDM frame isencapsulated into the PW, labelsare attached on the packetheader. The downlink labelindicates that the service exitsthe PW. The uplink label anddownlink label are different.When the PW encapsulationtype is set to UDP, the value ofthe downlink label of PW rangesfrom 49152 to 65535.

Tunnel Type MPLS Tunnel, IP Tunnel, GRETunnel

Set the tunnel type.

Tunnel Name (ID) Example: Uplink:Tunnel-10001(10001),Downlink:Tunnel-10002(10002)

Select the tunnel that carries thePW.

Control Word UsePolicy

Nonuse, Must Use Select whether to use the controlword.In an MPLS PSN network, thecontrol word carries the packetinformation.

Control Channel Type CW, None Set the type of the controlchannel.

VCCV VerificationMode

Ping, None Set the verification of theVCCV. You can verify theconnectivity of the PW.

Max. ConcatenatedCell Count

1 to 31 Set the maximum number ofconcatenation cells.

Packet Loading Time(us)

100 to 50000 Set the packet loading time.

Direction Example: Uplink PW (NE2->NE3)

Display the direction of the PWwhose bandwidth should be set,including the uplink directionand downlink direction.

Bandwidth Enabled Enabled, Disabled Enable or disable the bandwidthlimit.

CIR (kbit/s) Example: 100 Set the committed bandwidth ofthe PW.

CBS (byte) - This parameter is not supported.



10-71


PIR (kbit/s) Example: 100 Set the peak bandwidth of thePW.

PBS (byte) - This parameter is not supported.

EXP 0-7, None Set the priority flag of the PW.The priority ascends with thevalue. This parameter is used forpriority adjustment. For details,refer to the related informationof QoS parameter configuration.

NE Example: NE2 Display the NE which requiressetting of the CoS mapping.

ID (CoS MappingName)

Example: 1(Default AtmCosMap)

Select the mapping relationbetween the ATM service levelto the CoS.

Table 10-12 Descriptions of the parameters for ATM Service Management by NE


Service ID Example: 5 Set the ID of the service.

Service Name 64 bytes Set the name of the service.

Service Type UNIs-NNI, UNI-UNI Set the ATM service type.l UNIs-NNI: multi-point service

l UNI-UNI: single-point service

Click C.142 Service Type (ATMService) for more information.

Active Active Display the activation status of theservice.

Connection Type Example: PVP, PVC Select the connection type of theATM service.l PVP indicates that only the VPI

values of the source and sink areexchanged.

l PVC indicates that both the VPIand VCI values of the source andsink are exchanged.

Click C.107 Connection Type formore information.


Configuration Guide


Issue 06 (2009-06-01)

Table 10-13 Descriptions of the parameters for ATM Connection Configuration by NE


Connection Name Character string Display the name of the ATMconnection.

Connection ID Example: 1 Display the ID of the ATMconnection.

Source Board Example: Slot-Board Name Set the source board of the ATMservice.

Source Port Example: Slot-Board Name-Port(Trunk No.)

Set the source port of the ATMservice.

Source VPI 0 to 4095 Set the VPI value of the source port.

Source VCI 32 to 65535 Set the VCI value of the sourceport.

PW ID Example: 5 Select an ID for the PW that carriesthe service.

Sink Board Example: Slot-Board Name Set the sink board of the ATMservice.NOTE

In the case of the UNIs-NNI service,the sink board need not be set. In thecase of the NNI-NNI service, set thesink board, which should not be thesource board.

Sink Port Example: Slot-Board Name-Port(Trunk No.)

Set the sink port of the ATMservice.NOTE

In the case of the UNIs-NNI service,the sink board need not be set. In thecase of the NNI-NNI service, set thesink board, which should not be thesource board.

Sink VPI 0 to 4095 Set the VPI value of the sink port.

Sink VCI 32 to 65535 Set the VCI value of the sink port.

Uplink Policy Example: 3(Synchronize) Select the QoS policy for theupstream ATM connection. Fordetails, see ATM PolicyClick C.119 Uplink Policy formore information.

Down link Policy Example: 3(Synchronize) Select the QoS policy for thedownstream ATM connection. Fordetails, see ATM PolicyClick C.137 Downlink Policy formore information.



10-73

Table 10-14 Descriptions of the parameters for PW Configuration by NE

Tab Field Value Description

GeneralAttributes


Enable State Example: Enabled Display the enable state.

PW SignalingType

Static, Dynamic Sets the methods ofcreating a PW anddistributing the PW label.l Dynamic: The LDP

protocol is used todistribute the PW label.If you select Dynamic,PW Ingress Label andPW Egress Labelcannot be set.

l Static: The PW label isdistributed manually.

PW Type ATM n to one VCC celltransport, ATM one-to-one VCC Cell Mode,ATM n to one VPC celltransport, ATM one-to-one VPC Cell Mode

Sets the PW encapsulationtype.The PW type correspondsto the connection type. Inthe case of the PVP andPVC connections, twoencapsulation types areavailable, that is, 1:1 and N:1.

Direction Bidirectional Sets the direction of thePW.Click C.87 Direction formore information.

PWEncapsulationType

MPLS, UDP Sets the PW encapsulationtype. When the PWEncapsulation Type is setto MPLS, the MPLS, IP,and GRE tunnels aresupported; When the PWEncapsulation Type is setto UDP, only the IP tunnelis supported.


Configuration Guide


Issue 06 (2009-06-01)


PW IngressLabel

16 to 1048675 Sets the PW label attachedon the packet header whenthe service is transmittedfrom the source to the sink,and encapsulated in thePW. When the PWencapsulation type is set toUDP, the value of theingress label of PW rangesfrom 49152 to 65535.

PW Egress Label 16 to 1048675 Sets the PW label attachedon the packet header whenthe service is transmittedfrom the sink to the source,and encapsulated in thePW. When the PWencapsulation type is set toUDP, the value of theegress label of PW rangesfrom 49152 to 65535.Click C.31 PW EgressLabel for moreinformation.

Peer IP Example: 1.1.1.2 Sets the IP address of thedestination.Click C.83 Peer IP formore information.

Tunnel Type MPLS, IP, GRE Sets the type of the tunnel.


Selects the tunnel thatcarries the PW.

Local WorkingStatus

Example: CommonFault

Displays the local runningstatus of PW after you clickQuery.Click C.52 LocalWorking Status for moreinformation.

RemoteWorking Status

Example: CommonFault

Displays the remoterunning status of PW afteryou click Query.Click C.150 RemoteWorking Status for moreinformation.



10-75


CompositiveWorking Status

Up, Down Displays the compositiverunning status of PW afteryou click Query.Click C.158 CompositiveWorking Status for moreinformation.

QoS PW ID Example: 5 Sets the ID of the PW.

Direction Ingress, Egress Sets the direction of thePW.l Ingress: PW outgoing

direction of the portl Egress: PW incoming

direction of the port

Bandwidth Limit Enabled, Disabled Enables or disables thebandwidth limit.

CIR (kbit/s) 64 to 10000000 Sets the committedbandwidth of the PW.

CBS (byte) - This parameter is notsupported.

PIR (kbit/s) 64 to 10000000 Sets the peak bandwidth ofthe PW.Click C.90 PIR for moreinformation.

PBS (byte) - This parameter is notsupported.

EXP 0 - 7, None Sets the priority flag of thePW.

Policy Example: 2(Voice) Selects the QoS policy ofthe PW.

Query ActualBandwidth

Checked, Unchecked When this parameter isselected, the actualeffective bandwidth isqueried. When thisparameter is not selected,the configured bandwidthis queried.

AdvancedAttributes



Configuration Guide


Issue 06 (2009-06-01)


Control Word Must use, No use Displays that the controlword must be used.In an MPLS PSN network,the control word carries thepacket information.Click C.104 ControlWord (ATM Service) formore information.

Control ChannelType

CW, None Sets the type of the controlchannel.Click C.103 ControlChannel Type for moreinformation.

VCCVVerificationMode

Ping, None Sets the verification of theVCCV. You can verify theconnectivity of the PW.Click C.42 VCCVVerification Mode formore information.

Max.ConcatenatedCell Count

OptiX PTN 1900: 1 to31

Sets the maximum numberof concatenation cells.Click C.164 Max.Concatenated Cell Countfor more information.

Packet LoadingTime (us)

Example: 1000 Sets the packet loadingtime.Click C.50 PacketLoading Time (us) formore information.

Table 10-15 Descriptions of the parameters for CoS Mapping by NE


PW ID Example: 5 Displays the ID of the PW.

CoS Mapping Example: 1(DefaultAtmCosMap)

Selects the policy of mappingdifferent ATM service classes toCoS priorities. In this way,different quality assurance isprovided for different ATMservices.



10-77

Table 10-16 Descriptions of the parameters for CoS Mapping


Mapping ID Example: 3 Displays the ID of the table ofmapping the ATM serviceclasses to the CoS priorities.

Name Example: mapping_1 Displays the name of thetable of mapping the ATMservice classes to the CoSpriorities.


Configuration Guide


Issue 06 (2009-06-01)


Service Type UBR, CBR, RT-VBR, NRT-VBR

Displays the ATM serviceclasses.l UBR is the ATM service

with an unspecified bitrate. The UBR service isused in a non-real timemanner, but no quality ofservice (QoS) assurance isavailable. Therefore, it issuitable for transmitting IPdata packets.

l CBR is the ATM servicewith a constant bit rate.The CBR service appliesto the connection thatrequires static bandwidth.In general, it supports realtime services that requirestrict delay change (forexample, the audio,imaging, and circuitemulation services).

l RT-VBR is the ATMservice with a real timevariable bit rate. The RT-VBR service is used in areal time manner and has astrict restriction on thedelay. It mainly supportsthe audio and videoservices.

l NRT-VBR is the ATMservice with a non-realtime variable bit rate. TheNRT-VBR service is usedin a burst and non-realtime manner. It can ensurea very low ratio of cell lossbut has no restriction onthe delay.

CoS Example: BE Displays the CoS priority.



10-79

11 Configuring an E-Line Service

About This Chapter

This section describes basic information on E-Line services, and uses an example to illustratehow to configure an E-Line service.

11.1 E-Line ServiceIn the topology, the EPL service is a point-to-point service. The equipment transmits the packetsof a specific port or of specific VLANs of a specific port at the user side to a certain port at theuser or network side, a PW or a QinQ Link at the network side. In this way, the user data can betransparently transmitted in a point-to-point manner.

11.2 Configuration Flow for the E-Line ServiceThe configuration flow of the E-Line service include creating network, configuring the QoSpolicy, configuring interfaces, configuring the control plane and configuring the E-Line service.

11.3 Operation Tasks for the E-Line ServiceOperation tasks for the E-Line service include creation of E-Line services and creation of V-UNI groups.

11.4 Configuration Case of the UNI-UNI E-Line ServiceThis section uses a case to show the configuration of the UNI-UNI E-Line service, and theconfiguration flow. The configuration case covers the service planning and configuration of theEthernet service.

11.5 Configuration Case of the UNI-NNI E-Line Service Carried by PortsA case is provided here to show the configuration of the UNI-NNI E-Line service carried byports, and the configuration flow. The configuration case covers the service planning,configuration and verification of the Ethernet service.

11.6 Configuration Case of the UNI-NNI E-Line Service Carried by the PWA case is provided here to show the configuration of the UNI-NNI E-Line service carried by thePW, and the configuration flow. The configuration case covers the service planning,configuration and verification of the Ethernet service.

11.7 Configuration Case of the UNI-NNI E-Line Service Carried by the QinQ LinkThe configuration case illustrates how to configure a UNI-NNI E-Line service carried by theQinQ link. You can understand the configuration further by viewing the configuration flow

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 11 Configuring an E-Line Service


11-1

diagram. The configuration case covers the service planning, service configuration andverification of the E-Line service.

11.8 Verifying the Correctness of Service ConfigurationAfter the E-Line service is configured, the correctness of service configuration should beverified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.

11.9 Parameter DescriptionThis section describes the parameters related to the E-Line service configuration.

11 Configuring an E-Line ServiceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

11.1 E-Line ServiceIn the topology, the EPL service is a point-to-point service. The equipment transmits the packetsof a specific port or of specific VLANs of a specific port at the user side to a certain port at theuser or network side, a PW or a QinQ Link at the network side. In this way, the user data can betransparently transmitted in a point-to-point manner.

According to the service transmission mode, the E-Line service can be classified into thefollowing types:

l UNI-UNI E-Line service

l UNI-NNI E-Line service carried by ports

l UNI-NNI E-Line service carried by a PW

l UNI-NNI E-Line service carried by a QinQ link

UNI-UNI E-Line ServiceFigure 11-1 shows the networking diagram for the UNI-UNI E-Line service.

In City 1, Company A and Company B, connected to the PTN equipment, need communicationbetween each other. The communication requirement can be met by creating a UNI-UNI E-Lineservice.

In this case, the equipment equals a Layer 2 switch, which only exchanges data of Company Aand Company B. In the uplink direction of the user side at the two ends, complex trafficclassification can be performed for data packets, and different QoS policies can be usedaccording to the traffic classification.

Figure 11-1 UNI-UNI E-Line service

Package SwitchingNetwork

B Company

PE

PE

PE

PE

UNI

UNI

A Company

City1

UNI-NNI E-Line Service Carried by PortsFigure 11-2 shows the networking diagram for the UNI-NNI E-Line service carried by ports.

In City 1 and City 2, Company A has branches, which need communication. The communicationrequirement can be met by creating a UNI-NNI E-Line service carried by ports.



11-3

In this case, each branch of Company A can exclusively use the UNI. Each physical port involvedin the E-Line service network can be exclusively used by the E-Line service. In City 1, if smallbranches in Company A need service isolation, services at the same UNI can be differentiatedthrough "port + VLANs". For a single station, in the uplink direction of the user side, complextraffic classification can be performed for data packets, and different QoS policies can be usedaccording to the traffic classification.

Figure 11-2 UNI-NNI E-Line service carried by ports


A Company

City1

A Company

City2

UNI NNI NNI UNI

UNI-NNI E-Line Service Carried by a PWFigure 11-3 shows the networking diagram for the UNI-NNI E-Line service carried by a PW.

In City 1 and City 2, Company A and Company B have branches. Communication betweenbranches of the same company is needed, but services between the two companies need to beisolated. In this case, the communication between branches of Company A and Company B canbe realized by creating a UNI-NNI E-Line service carried by a PW. Services between the twocompanies are isolated because different services are carried by different PWs.

Hence, the company service accessed at the user side is encapsulated into a PW, and then iscarried by the Tunnel.

Different E-Line services of different companies are carried by different PWs, and then aretransmitted to the same NNI. As a result, the number of NNIs is saved, and the bandwidthutilization is increased. In the uplink direction of the user side, the hierarchical QoS can beperformed for data packets.

Figure 11-3 UNI-NNI E-Line service carried by a PW

A Company

City2

Tunnel

PW

B Company

A Company

City1B Company


NNIUNI

NE 1 NE2

NNI UNI


Configuration Guide


Issue 06 (2009-06-01)

UNI-NNI E-Line Service Carried by a QinQ LinkIn the case of the QinQ link carrying, the packets with the C-VLAN in the user-side networkare added with an S-VLAN header of the transport network. The packets then travel through thetransport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for theuser. Figure 11-4 shows the networking diagram for the UNI-NNI E-Line service carried by aQinQ link.

Both Company A and Company B have branches in City 1 and City 2. Branches of each companyneed to communicate with each other. The traffic from the two companies must be isolated. Theinternal VLANs of Company A range from 1 to 100 and the internal VLANs of Company Brange from 1 to 200. In this case, you can configure a UNI-NNI E-Line service carried by aQinQ link to meet the communication requirements. As different services are carried by QinQlinks of different values, traffic of different companies is isolated and the VLAN resources ofthe packet switch network (PSN) are also saved.

In this case, different packets accessed at the user side from different companies are added withdifferent VLANs, and then carried by the same link at the network side.

As the E-Line services of different companies are added with one VLAN and transported to thesame port, the network-side port resources are saved and the bandwidth utilization is increased.Also as only a small number of VLANs in the PSN are used, the VLAN resources of the networkare saved. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.

Figure 11-4 UNI-NNI E-Line service carried by a QinQ link

A Company

B Company

A Company

City1

B Company

PacketSwitchingNetwork

NE 1

NE2

The internal networkof A CompanyVLAN = 1-100

The internal networkof B CompanyVLAN = 1-200

A VLAN tag (VLAN = 30)is added to the packet of

A Company

City2A VLAN tag (VLAN = 40)is added to the packet of

B Company

The internal networkof A CompanyVLAN = 1-100

The internal networkof B CompanyVLAN = 1-200

QinQ Link



11-5

11.2 Configuration Flow for the E-Line ServiceThe configuration flow of the E-Line service include creating network, configuring the QoSpolicy, configuring interfaces, configuring the control plane and configuring the E-Line service.

UNI-UNI E-Line service

The complete process of configuring a UNI-UNI E-Line service is shown in Figure 11-5.

Figure 11-5 Configuration flow for the UNI-UNI E-Line service

Required

Optional

End

Creating a V-UNI Group

Configuring UNI-UNI E-Line Service

Creating Network

Configuring Interfaces

Configuring the QoS Policy

Start

Table 11-1 Tasks for configuring the UNI-UNI E-Line service

Task Remarks

1. CreatingNetwork


2. Configure theQoS Policy

The QoS policy is used for traffic management of the E-Line service.


Configuration Guide


Issue 06 (2009-06-01)

Task Remarks

3. Configure theuser-sideInterface

The Ethernet interface accesses services from NodeB.

4. Configure theUNI-UNI E-LineService

To configure the UNI-UNI E-Line service, you need to specify theservice ID, service name and service VLan.

5. Creating a V-UNI Group

Set parameters such as the peak bandwidth, maximum burst size, andmember ports of the V-UNI group.The V-UNI group can realize the bandwidth sharing and restriction ofmultiple Ethernet services.

UNI-NNI E-Line Service Carried by PortsThe complete process of configuring a UNI-NNI E-Line service carried by ports is shown inFigure 11-6.

Figure 11-6 UNI-NNI E-Line service carried by ports

Required

Optional

Configuring the UNI-NNI E-Line Service Carried by

Ports

End

(Source NE)

(Sink NE)


Configuring the UNI-NNI E-Line Service Carried by

Ports

Creating Network



Start



11-7

Table 11-2 Tasks for configuring the UNI-UNI E-Line service carried by a port

Task Remarks

1. CreatingNetwork




3. Configure theInterface


4. Configure theUNI-NNI E-LineService

To configure the UNI-NNI E-Line service, you need to specify theservice ID, service name and service VLan.



UNI-NNI E-Line Service Carried by PWsThe complete process of configuring a UNI-NNI E-Line service carried by PWs is shown inFigure 11-7.


Configuration Guide


Issue 06 (2009-06-01)

Figure 11-7 UNI-NNI E-Line service carried by PWs

Creating Network

Configuring the Control Plane

Configuration Case of the UNI-NNI E-Line Service

Carried by the PW


StartRequired

Optional

End

(Source NE)

(Sink NE)

Configuring a Tunnel


Configuration Case of the UNI-NNI E-Line Service

Carried by the PW

Configuring the LSR ID

Configuring the network-side Interfaces

Configuring the user-side Interfaces



11-9

Table 11-3 Tasks for configuring the UNI-NNI E-Line service carried by PWs

Task Remarks

1. CreatingNetwork


2. Configure theLSR ID


3. Configure thenetwork-sideinterface


4. Configure thecontrol plane

Set the protocol parameters related to the control plane to create thetunnel.l To create a static MPLS tunnel to transmit the E-Line service, the

parameters related to the control plane need not be set.l To create a dynamic MPLS tunnel to transmit the E-Line service, you

need to set the following protocol parameters:1. Set the IGP-ISIS protocol parameters.2. Set the MPLS-RSVP protocol parameters.To create a dynamic PW to transmit the service, you need to set theparameters related to the MPLS-LDP protocol and the IGP-ISISprotocol.

l To create an IP Tunnel or GRE Tunnel to transmit the E-Line service,you need to Configuring Static Routes.

5. Configure theTunnel


per-NE or per-trail mode. Specify the tunnel ID, set signaling typeto static, name the service, and specify the ingress node, egress node,and transit node.





7. Configure theuser-sideInterface


8. Configure theUNI-NNI E-Lineservice

1. Create an E-Line service: Specify the service ID, name the service,and set service VLan.

2. Configure a PW: Set the PW type, label, and tunnel type.3. Configure QoS: Set the QoS of UNI and PW.


Configuration Guide


Issue 06 (2009-06-01)

Task Remarks



UNI-NNI E-Line Service Carried by QinQ LinkThe complete process of configuring a UNI-NNI E-Line service carried by QinQ Link is shownin Figure 11-8.

Figure 11-8 UNI-NNI E-Line service carried by QinQ Link

Creating Network

ConfiguringInterfaces

Configuration Case of theUNI-NNI E-Line Service

Carried by QinQ Link

Configuring the QoSPolicy

StartRequired

Optional

End

(Source NE)

(Sink NE)

Configuring QinQLink

Creating a V-UNIGroup

Configuration Case of theUNI-NNI E-Line Service

Carried by QinQ Link



11-11

Table 11-4 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link

Task Remarks

1. CreatingNetwork



The E-Line policy is used for traffic management of the E-Line service.

3. Configure theInterface


4. ConfigureQinQ Link

Create the QinQ link, and set the ID, board, port, S-Vlan, and QoSinformation of the QinQ link.The QinQ link encapsulates multiple VLAN packets to a VLAN on thenetwork side for transmission. This saves the VLAN resources on thenetwork.

5. Configure theUNI-NNI E-Lineservice

Set the service ID, name, VLAN, and QinQ link ID.



11.3 Operation Tasks for the E-Line ServiceOperation tasks for the E-Line service include creation of E-Line services and creation of V-UNI groups.

11.3.1 Creating a UNI-UNI E-Line ServiceA UNI-UNI E-Line service indicates that users can be interconnected through equipment. TheEthernet data packets do not pass the network side, but are transparently transmitted at the userside.

11.3.2 Creating a UNI-NNI E-Line Service Carried by a PortThe service is accessed at the user side, and transported to one port at the network side forcarrying. In this way, user data can be transparently transmitted in a point-to-point manner. Inthis way, this port is exclusively used.

11.3.3 Creating a UNI-NNI E-Line Service Carried by a PWThe service is accessed at the user side, and transported to one PW at the network side forcarrying. In this way, user data can be transparently transmitted in a point-to-point manner. Forsuch a application, create a UNI-NNI E-Line service carried by a PW.

11.3.4 Creating a QinQ LinkThe QinQ link indicates that a VLAN is added on the accessed packets by using the QinQencapsulation mode. In this way, multiple VLAN packets from the user-side network areencapsulated into a VLAN in the transport network for transport. The VLAN resources in thetransport network are saved. Both the E-Line service and E-LAN service can be carried by theQinQ link at the network side.


Configuration Guide


Issue 06 (2009-06-01)

11.3.5 Creating a UNI-NNI E-Line Service Carried by the QinQ LinkThe services accessed on the user side are carried by the QinQ link on the network side. MultipleVLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transportnetwork. In this way, the VLAN resources in the transport network are saved.

11.3.6 Creating a V-UNI GroupThe creation of the V-UNI group includes the selection of V-UNI group members and settingof overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can berestrained by creating the V-UNI group.

11.3.1 Creating a UNI-UNI E-Line ServiceA UNI-UNI E-Line service indicates that users can be interconnected through equipment. TheEthernet data packets do not pass the network side, but are transparently transmitted at the userside.


If a port need be exclusively used, disable the DCN function of the port that carries the service.For details, see Enabling the Port DCN.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet ServiceManagement > E-Line Service from Function Tree.

Step 2 Click the UNI tab and click New. The New E-Line Service dialog box is displayed.

Step 3 Set parameters in the dialog box.For details on the parameters for UNI ports of E-Line service,see Table 11-19.



11-13

NOTE

When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. Thetransparently transmitted service does not support configuring the alarm performance, OAM and QoS.

For Direction, select UNI-UNI.

For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANswith ",". For example, "1,3,5,8-10".

Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.

Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default ForwardingPriority and Default Packet Relabeling Color for ports. Click OK. The New E-LineService dialog box is displayed.For details on the parameters for QoS of E-Line service, seeTable 11-21.

NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s), PIR (kbit/s). You can also selectthe QoS policy in Policy.

Step 6 Click OK. A dialog box is displayed for confirmation.

Step 7 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-relatedparameters.For details on the parameters for maintenance association of E-Line service, seeTable 12-13.For details on the parameters for MEP point of E-Line service, see Table 12-14.

NOTE

Before setting OAM-related parameters, configure the MD.

----End

11.3.2 Creating a UNI-NNI E-Line Service Carried by a PortThe service is accessed at the user side, and transported to one port at the network side forcarrying. In this way, user data can be transparently transmitted in a point-to-point manner. Inthis way, this port is exclusively used.



Procedure

Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management> E-Line Service from Function Tree.



Configuration Guide


Issue 06 (2009-06-01)

Step 3 Set parameters in the dialog box.For details on the parameters for the E-Line service, see Table11-19.

NOTE

l When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. Thetransparently transmitted service does not support configuring the alarm performance, OAM and QoS.

l For Direction, select UNI-NNI.

l For Bearer Type, select Port.

l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutiveVLANs with ",". For example, "1,3,5,8-10".


Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default ForwardingPriority and Default Packet Relabeling Color for ports. Click OK. The New E-LineService dialog box is displayed.For details on the parameters for QoS of the E-Line service, seeTable 11-21.

NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s), PIR (kbit/s). You can also selectthe QoS policy in Policy.

Step 6 Click OK. A dialog box is displayed for confirmation.

Step 7 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-relatedparameters.For details on the parameters for maintenance association of the E-Line service, seeTable 12-13.For details on the parameters for MEP point of the E-Line service, see Table12-14.

NOTE


----End

11.3.3 Creating a UNI-NNI E-Line Service Carried by a PWThe service is accessed at the user side, and transported to one PW at the network side forcarrying. In this way, user data can be transparently transmitted in a point-to-point manner. Forsuch a application, create a UNI-NNI E-Line service carried by a PW.



11-15


You must complete the creation of the MPLS tunnel that carries PWs.

If a port need be exclusively used, disable the DCN function of the port at the UNI side. Fordetails, see Enabling the Port DCN.

Procedure

Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management> E-Line Service from Function Tree.


Step 3 Set parameters in the dialog box.For details on the parameters for UNI port of the E-Line service,see Table 12-5.

NOTE


l For Direction, select UNI-NNI.

l For Bearer Type, select PW.

l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutiveVLANs with ",". For example, "1,3,5,8-10".

Step 4 Click Configure PW. The Configure PW dialog box is displayed. In the dialog box, set PW-related parameters.For details on the parameters for PW of the E-Line service, see Table 12-7.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

For PW ID, select the PW ID set in Step 3.

Step 5 Click OK and close the Configure PW dialog box.

Step 6 Click Configure QoS. The Configure QoS dialog box displayed.

Step 7 In the UNItab, set Policy, Default Forwarding Priority and Default Packet RelabelingColor for the ingress direction.

Step 8 Click the PW tab. Set EXP in the ingress direction and LSP Mode in the egress direction. ClickOK. The New E-Line Service dialog box is displayed.For details on the parameters for QoS ofthe E-Line service, see Table 11-21.

NOTE

If you select Enabled for Bandwidth Limit, you can set CIR (kbit/s) and PIR (kbit/s) for the PW. Youcan also select the QoS policy in Policy.

Step 9 Click OK to finish the creation.

Step 10 Optional: Click the Maintenance Association tab and MEP Point tab to set OAM-relatedparameters.For details on the parameters for maintenance association of the E-Line service, seeTable 12-13.For details on the parameters for MEP point of the E-Line service, see Table12-14.

NOTE


----End

11.3.4 Creating a QinQ LinkThe QinQ link indicates that a VLAN is added on the accessed packets by using the QinQencapsulation mode. In this way, multiple VLAN packets from the user-side network are



11-17

encapsulated into a VLAN in the transport network for transport. The VLAN resources in thetransport network are saved. Both the E-Line service and E-LAN service can be carried by theQinQ link at the network side.

Prerequisite


The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode mustbe the QinQ mode.

If the QoS parameters of the QinQ link need be configured, the QinQ policy must be configuredfirst.

Procedure

Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet ServiceManagement > QinQ Link from the Function Tree.

Step 2 Click New. The New QinQ Link window is displayed.

Step 3 Click the General Attributes tab. Set QinQ Link ID, Board, Port and S-Vlan ID.

Step 4 Click the QoS tab to set the QoS-related parameters.

NOTE

If Bandwidth Limit is set to Enabled, you can set CIR (kbit/s) and PIR (kbit/s) for the QinQ Link. Youcan also select a QinQ policy in Policy. Before selecting a policy, create a policy.

Step 5 Click OK.

----End

11.3.5 Creating a UNI-NNI E-Line Service Carried by the QinQ LinkThe services accessed on the user side are carried by the QinQ link on the network side. MultipleVLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transportnetwork. In this way, the VLAN resources in the transport network are saved.

Prerequisite


The QinQ link must be created for the network-side ports.

Procedure

Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet ServiceManagement > E-Line Service from the Function Tree.

Step 2 Click the UNI tab and then click New. The New E-Line Service dialog box is displayed.

Step 3 Set each parameter in the dialog box.


Configuration Guide


Issue 06 (2009-06-01)

NOTE


l Set Direction to UNI-NNI.

l Set Bearer Type to QinQ Link.

l Select a created QinQ link in QinQ Link ID.


Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Policy, Default ForwardingPriority and Default Packet Relabeling Color for ports. Click OK. The New E-LineService dialog box is displayed.For details on the parameters for QoS of E-Line service, seeTable 11-21.

Step 6 Click OK. The Operation Result dialog box is displayed, indicating that the operation issuccessful. Click Close.

Step 7 Click the QoS tab and click the QinQ Link tab.

Step 8 Select the QinQ policy for the ingress and egress directions of the QinQ link. Click Apply. TheOperation Result dialog box is displayed, indicating that the operation is successful.

NOTE

Before selecting the policy, the policy should be created. If Bandwidth Limit is set to enabled, CIR (kbit/s) and Peak Bandwidth (kbit/s) can be set.

Step 9 Click Close,

----End



You must complete the creation of multiple Ethernet services.



11-19

The PIR value of the V-UNI group should be set to a value that is higher than or equal to thetotal CIR value of the V-UNI members.

Procedure

Step 1 Select the NE in the NE Explorer . Choose Configuration > Ethernet ServiceManagement > V-UNI Group from the Function Tree.

Step 2 Click New to display the NEW V-UNI Group window.

Step 3 Set V-UNI Group ID, V-UNI Group Type, PIR(kbit/s) and PBS(byte). For details on theparameters for V-UNI group, seeTable 11-18.

Step 4 Select the interface to be added in Selecting Interface list. Click to add the port tothe Selected Interface list.

NOTE

The interfaces on the same interface board can be configured into the same V-UNI group.

The former eight interfaces on the EG16 can be configured into the same V-UNI group, and the latter eightinterfaces can be configured into the same V-UNI group.

Step 5 Click OK to display the Operation Result dialog box, which indicates the operation success.Then, click Close.

----End


Configuration Guide


Issue 06 (2009-06-01)

11.4 Configuration Case of the UNI-UNI E-Line ServiceThis section uses a case to show the configuration of the UNI-UNI E-Line service, and theconfiguration flow. The configuration case covers the service planning and configuration of theEthernet service.

11.4.1 Networking DiagramThis section describes the networking diagram for the service between Company A andCompany B.

11.4.2 Service PlanningThe voice service, video service, and common Internet access service are available betweenCompany A and Company B. Hence, an E-Line service should be created.

11.4.3 Configuring the E-Line Service at an NETo configure the UNI-UNI E-Line service is to configure the E-Line service at an NE. Thissection describes how to configure the UNI-UNI E-Line service.

11.4.1 Networking DiagramThis section describes the networking diagram for the service between Company A andCompany B.

Requirement and Networking DiagramAs shown in Figure 11-9, in City 1, Company A and Company B need communication betweeneach other. The switches of the two companies are connected to the local OptiX PTN 3900. Theswitches of Company A and Company B support VLAN.

The service available between Company A and Company B include the voice service, videoservice, and common Internet access service. The voice service and video service use the fixedbandwidth, and the common Internet access service can use all the bandwidth at a burst. Table11-5 lists the service requirement.

Figure 11-9 Networking diagram for the UNI-UNI E-Line service

B Company

UNI:1-EG16-19-ETFC-1

A Company

City1

UNI:1-EG16-19-ETFC-2

Packet Switching Network

PTN



11-21

Table 11-5 Requirement of the E-Line service

Service Type Requirement

Voice service (VLAN=100) Fixed bandwidth, CIR=PIR, 10 Mbit/s

Video service (VLAN=200) Fixed bandwidth, CIR=PIR, 40 Mbit/s

Common Internet access service(VLAN=300)

CIR=10 Mbit/s, PIR=50 Mbit/s

Total bandwidth 80 Mbit/s

11.4.2 Service PlanningThe voice service, video service, and common Internet access service are available betweenCompany A and Company B. Hence, an E-Line service should be created.

The three types of services should be differentiated through VLAN labels. In addition, differentservices use different QoS processing.



NE Interface Interface Attribute

NE1

19-ETFC-1(Port-1) Port Mode: Layer 2Tag: Tag Aware

19-ETFC-2(Port-2) Port Mode: Layer 2Tag: Tag Aware

Table 11-7 lists the configuration parameters of QoS.

Table 11-7 Configuration parameters of QoS

ServiceType

Policy ID TrafficClassificationID

BandwidthLimit

CIR(kbit/s)

PIR (kbit/s)

ColorationMode

Voiceservice

1 1 Enabled 10000 10000 ColorBlindness

Videoservice



Configuration Guide


Issue 06 (2009-06-01)

ServiceType

Policy ID TrafficClassificationID

BandwidthLimit

CIR(kbit/s)

PIR (kbit/s)

ColorationMode

OrdinaryInternetaccessservice


Table 11-8 lists the planning of the Ethernet service.

Table 11-8 Planning of the UNI-UNI E-Line service


Service ID 1 The service ID, ranges from1 to 65535, can be manuallyinput.

Service Direction UNI-UNI The service created is a UNI-UNI Ethernet service.

UNI 19-ETFC-1(Port-1) and -2(Port-2)

19-ETFC-1(Port-1) isconnected to Company A,and 19-ETFC-2(Port-2) isconnected to Company B.

VLANs 100, 200, 300 The VLAN value of the voiceservice is 100; the VLANvalue of the video service is200; the VLAN value of thecommon Internet accessservice is 300.

BPDU Not TransparentlyTransmitted

BPDU, used to transport theprotocol information of theMSTP, is a bridge protocoldata unit. Normally, set toNot TransparentlyTransmitted.

MTU(byte) 1526 MTU is the maximumtransport unit.

QoS Policy for Voice Service Fixed bandwidth, CIR=PIR,10000 kbit/s

-

QoS Policy for Video Service Fixed bandwidth, CIR=PIR,40000 kbit/s

-

QoS Policy for CommonInternet Access Service

CIR=10000 kbit/s,PIR=50000 kbit/s

-



11-23

11.4.3 Configuring the E-Line Service at an NETo configure the UNI-UNI E-Line service is to configure the E-Line service at an NE. Thissection describes how to configure the UNI-UNI E-Line service.

PrerequisiteYou must understand the networking, requirements and service planning of the example.

Procedure

Step 1 Configure the QoS policy1. In the NE explorer, select NE1 and choose > > Policy Management from the Function Tree.

Configuration > QoS Management > QoS Management.2. Select CAR Policy tab, and click New. Set the parameters such as Policy ID, CIR(kbit/

s), PIR(kbit/s) in the Create CAR Policy dialog box displayed. Click OK. Configure threeCAR policies separately.


l Policy 1– Policy: 1

– Policy Name: voice

– CIR(kbit/s): 10000 (Indicates the ensured bandwidth of the queue.)

– PIR(kbit/s): 10000 (Indicates the peak traffic rate.)

– CBS(byte): 16000 (Indicates the committed burst size. When the bandwidth isinsufficient, certain packets cannot enter the queue for forwarding in time. In thiscase, a buffer, where these packets are stored, is required. Then, after the bandwidthis sufficient, these packets are forwarded. Hence, the CBS indicates the ensured sizeof the buffer space.)

– PBS(byte): 16000 (Indicates the peak burst size.)

– Coloration Mode: Color Blindness


– Policy Name: video

– CIR(kbit/s): 40000

– PIR(kbit/s): 40000

– CBS(byte): 16000

– PBS(byte): 16000



– Policy Name: data

– CIR(kbit/s): 10000

– PIR(kbit/s): 50000


Configuration Guide


Issue 06 (2009-06-01)

– CBS(byte): 16000

– PBS(byte): 16000


CoS Configuration: Set the CoS according to networking planning. In this example, thedefault value is used.

3. Select V-UNI Ingress Policy tab, and click New. Set the policy parameters in the CreateV-UNI Ingress Policy dialog box displayed.


l Policy ID: 1

l Policy Name: E-Line

4. Click New in Traffic Classification Configuration. Set the parameters in Create TrafficClassification dialog box displayed. Click Add to add the math rules, and then clickOK. Create three different traffic classification polices.


l Voice service– Traffic Classification ID: 1

– Match Type: CVlan ID (The tag carried by the transmitted service packets is theCVlan tag. In this case, the mapping type is CVlan ID.)

– Match Value: 100 (The VLAN ID of the voice service is 100.)

– Wildcard: 0 (The number of digits of the wildcard is consistent with the number ofdigits of the match value. After the wildcard is converted to the binary format, digit0 in the match value should be matched, but digit 1 need not be considered. Whenthe wildcard is set to all "0"s, it indicates that the packets should strictly match thematch value.)

– CoS: EF (The voice service is the real-time service. In this case, the CoS is set toEF to ensure the service quality.)

– CAR Policy: 1

l Video service– Traffic Classification ID: 2

– Match Type: CVlan ID

– Match Value: 200

– Wildcard: 0

– CoS: AF4 (The video service has high requirement for delay. In this case, the CoSis set to AF4.)

– CAR Policy: 2

l Data service– Traffic Classification ID: 3

– Match Type: CVlan ID

– Match Value: 300

– Wildcard: 0



11-25

– CoS: BE (The common Internet access service is not the real-time service. In thiscase, the CoS is set to BE, and thus the common Internet access service is transmittedas possible.)

– CAR Policy: 3

Step 2 Configure interfaces:1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure the network-side interface.2. In the General Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set

the parameters such as Port Mode, Encapsulation Type as required, and click Apply.


l Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)

l Enable Port: Enabled

l Port Mode: Layer 2

l Encapsulation Type: 802.1Q


l Max Frame: 1620 (Set this parameter according to the length of data packets.)

3. In the Layer 2 Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Setthe TAG to Tag Aware. Click Apply.



l Tag: Tag Aware– If a port is set to Tag Aware, this port can transparently transmits the data packet

with the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag),this packet is discarded.

– If the port is set to Access, the port adds the default VLAN ID to the signal packetwithout the VLAN ID (Untag). If the signal contains the VLAN ID (Tag), this packetis discarded.

– If the port is set to Hybrid, the port adds the default VLAN ID (Untag) to the signalpacket without the VLAN ID (Untag). If the signal packet contains the VLAN ID(Tag), the packet is transparently transmitted.

Step 3 Create a UNI-UNI service.1. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line

Service.2. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in the

New E-Line Service dialog box displayed. Click Apply.


l Service ID: 1

l Service Name: CompanyA-CompanyB

l Direction: UNI-UNI

l BPDU: Not Transparently Transmitted


Configuration Guide


Issue 06 (2009-06-01)

l Port: 19-ETFC-1(Port-1) (Company A is connected to 19-ETFC-1(Port-1).)

l VLANs: 100, 200, 300 (The voice service, video service, and common Internet accessservice between Company A and Company B are differentiated through different VLANvalues carried by the services. This port can transmit only the services whose VLANvalues are 100, 200, and 300. Otherwise, the services are discarded.

l Port: 19-ETFC-2(Port-2) (Company B is connected to 19-ETFC-2(Port-2).)

l VLANs: 100, 200, 300

3. Click Configure QoS, set the parameters for the policy in the Configure QoS dialog boxdisplayed.


l Policy: 1

----End

11.5 Configuration Case of the UNI-NNI E-Line ServiceCarried by Ports

A case is provided here to show the configuration of the UNI-NNI E-Line service carried byports, and the configuration flow. The configuration case covers the service planning,configuration and verification of the Ethernet service.

11.5.1 Networking DiagramThis section describes the networking diagram for the service of the Company A between City1 and City 2.

11.5.2 Service PlanningTo transport the service between city 1 and city 2, an E-Line service must be created.

11.5.3 Configuring the E-Line Service at the Source NETo configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service atthe source NE and sink NE. This section describes how to configure the E-Line service at thesource NE.

11.5.1 Networking DiagramThis section describes the networking diagram for the service of the Company A between City1 and City 2.

Requirement and Networking DiagramAs shown in Figure 11-10, Company A has departments in City 1 and City 2, which needcommunicate with each other. The service is data service. The user requires exclusive usage ofthe UNI port. Each physical port that the private line passes through is exclusively occupied bythis private line. This example considers the direct communication of two cities as an example.All packets transported by the switch at the user egress carry VLANs, whose value is 100.



11-27

Figure 11-10 Networking diagram for the UNI-NNI E-Line service carried by ports

Packet Switching Network

A Company

City1

A Company

City2

NNI:1-EG16-19-ETFC-2

UNI:1-EG16-19-ETFC-1 UNI:1-EG16-19-ETFC-1

NNI:1-EG16-19-ETFC-2

NE 1 NE 2

11.5.2 Service PlanningTo transport the service between city 1 and city 2, an E-Line service must be created.




NE1

19-ETFC-1(Port-1) Port Mode: Layer 2Encapsulation Type: 802.1QTag: Tag Aware


NE2



Since the service is data service, and the ports are exclusively used, the QoS is not required.Table 11-10 lists details on the service planning.

Table 11-10 Planning of the UNI-NNI E-Line service carried by ports

Parameter NE 1 NE 2

Service ID 1 1

Service Name E-Line-1 E-Line-1


Configuration Guide


Issue 06 (2009-06-01)

Parameter NE 1 NE 2

Direction UNI-NNI UNI-NNI

UNI 1-EG16-19-ETFC-1(Port-1) 1-EG16-19-ETFC-1(Port-1)

NNI 1-EG16-19-ETFC-2(Port-2) 1-EG16-19-ETFC-2(Port-2)

Bearer Type Port Port

VLANs 100 100

BPDU Not Transparently Transmitted Not Transparently Transmitted

MTU(byte) 1526 1526

11.5.3 Configuring the E-Line Service at the Source NETo configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service atthe source NE and sink NE. This section describes how to configure the E-Line service at thesource NE.

Prerequisite



Procedure

Step 1 Configure the interfaces.1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure the network-side interface.2. In the General Attributes tab, select the 19-ETFC-1(Port-1) and 19-ETFC-2(Port-2). Set

the parameters such as Port Mode, Encapsulation Type as required, and click Apply.



l Enable Port: Enabled

l Port Mode: Layer 2

l Encapsulation Type: 802.1Q


l Max Frame: 1620 (Set this parameter according to the length of data packets.)





11-29


l Tag: Tag Aware

– If a port is set to Tag Aware, this port can transparently transmits the data packetwith the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag),this packet is discarded.



4. In the NE Explorer, select NE2. Then, configure the interface attributes by following Step1.1 to Step 1.3.

Step 2 Configure a UNI-NNI E-Line service.

1. In the NE explorer, select NE1 and choose Ethernet Service Management > E-LineService.

2. Click New. Set the parameters such as Service ID, Service Name, Port, VLANs in theNew E-Line Service dialog box displayed. Click Apply.


l Service ID: 1

l Service Name: E-Line-1

l Direction: UNI-NNI


l Port: 19-ETFC-1(Port-1) (Company A in City 1 is connected to 19-ETFC-1(Port-1).)

l VLANs: 100

l Bear Type: Port

l Port: 19-ETFC-2(Port-2) (19-ETFC-2(Port-2) transmits the service to NE2.)

3. In the NE Explorer, select NE2. Then, configure the E-Line service by following to .


l Service ID: 1




l Port: 19-ETFC-1(Port-1) (Company A in City 2 is connected to 19-ETFC-1(Port-1).)

l VLANs: 100

l Bear Type: Port

l Port: 19-ETFC-2(Port-2) (19-ETFC-2(Port-2) transmits the service to NE1.)

----End


Configuration Guide


Issue 06 (2009-06-01)

11.6 Configuration Case of the UNI-NNI E-Line ServiceCarried by the PW

A case is provided here to show the configuration of the UNI-NNI E-Line service carried by thePW, and the configuration flow. The configuration case covers the service planning,configuration and verification of the Ethernet service.

11.6.1 Case DescriptionThe case description covers the requirement, networking diagram and service planning.

11.6.2 Service PlanningThe Ethernet services between branches of a company are carried by a PW. When planning suchan Ethernet service, you need to plan the NE information, tunnel information, and serviceinformation.

11.6.3 Configuring the E-Line Service of the NETo configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service atthe source NE and sink NE. This section describes how to configure the E-Line service.

11.6.1 Case DescriptionThe case description covers the requirement, networking diagram and service planning.

As shown in Figure 11-11, Company A and Company B have departments in City 1 and City2, which need to communicate with each other respectively. The communication of CompanyA should be isolated from that of Company B. NE1 is connected to Company A and CompanyB in City 1. NE3 is connected to Company A and Company B in City 2. NE1 accesses the servicesfrom City 1 and transmits the services to NE2. Then, NE2 transparently transmits the servicesto NE3. Finally, NE3 transmits the services to City 2. Similarly, NE3 accesses the services fromCity 2 and transmits the services to NE2. Then, NE2 transparently transmits the services to NE1.Finally, NE1 transmits the services to City 1.

For such an application, the UNI-NNI E-Line service carried by the PW should be created. TwoPWs carry the services of Company A and Company B respectively. The two PWs sharebandwidth of one tunnel.

The service between departments of Company A is the ordinary Internet access service (CIR =10 Mbit/s, PIR = 30 Mbit/s).

The service between departments of Company B is the data service (CIR = 30 Mbit/s, PIR = 50Mbit/s).



11-31

Figure 11-11 Networking diagram for the UNI-NNI E-Line service carried by the PW

NE1 NE2

NE3

NE4NE5

Access layer

Company ACompany B

3-EFF8-1(Port-1)3-EFF8-2(Port-2)

20-EFF8-1(Port-1)10.0.0.2

5-EX2-1(Port-1)10.0.1.1

5-EX2-1(Port-1)10.0.1.2

20-EFF8-2(Port-2)3-EFF8-1(Port-1)

10.0.0.1

Company B

Company A

20-EFF8-1(Port-1)


layer

11.6.2 Service PlanningThe Ethernet services between branches of a company are carried by a PW. When planning suchan Ethernet service, you need to plan the NE information, tunnel information, and serviceinformation.



NE LSRID

Port Port Attribute Port IPAddress

IP Mask

NE1 1.0.0.1

3-EFF8-1(Port-1) Port Mode: Layer 2Tag: Tag Aware

- -


- -

3-EFF8-3(Port-3) Port Mode: Layer 3 10.0.0.1 255.255.255.252

NE2 1.0.0.2

20-EFF8-1(Port-1) Port Mode: Layer 3 10.0.0.2 255.255.255.252

5-EX2-1(Port-1) Port Mode: Layer 3 10.0.1.1 255.255.255.252

NE3 1.0.0.3


- -


- -

5-EX2-1(Port-1) Port Mode: Layer 3 10.0.1.2 255.255.255.252


Configuration Guide


Issue 06 (2009-06-01)

Table 11-12 lists details on the planning of the tunnel carrying the PW.

Table 11-12 Planning of the tunnel carrying the PW

Parameter Positive Tunnel Reverse Tunnel

Tunnel ID 1 2

Name Tunnel-0001(Positive) Tunnel-0002(Reverse)

Signal Type Dynamic Dynamic

Scheduling Type E-LSP E-LSP

Bandwidth (kbit/s) 80 Mbit/s 80 Mbit/s

Source Node NE1 NE3

Sink Node NE3 NE1

Route ConstraintPort IP Address

IP addresses of ingress port ofNE2:20-EFF8-1: 10.0.0.2IP addresses of ingress port ofNE3:5-EX2-1: 10.0.1.2

IP addresses of ingress port ofNE2:5-EX2-1: 10.1.2.2IP addresses of ingress port ofNE1:3-EFF8-2: 10.1.1.2

Table 11-13 lists details on the planning of the E-Line service.

Table 11-13 Planning of the UNI-NNI E-Line service carried by the PW

Parameter Company A Company B

Service ID 1 2



UNI 3-EFF8-1(Port-1) 3-EFF8-2(Port-2)

VLANs 100 200

Bearer Type PW PW

PW ID 35 45


Not TransparentlyTransmitted

MTU(byte) 1526 1526

Table 11-14 lists details on the planning of the PW.



11-33

Table 11-14 Planning of the PW

Parameter PW of Company A PW of Company B


PW Type Ethernet Ethernet

Direction Bidirectional Bidirectional

PW Ingress Label 20 30

PW Egress Label 20 30

Peer IP 1.0.0.3 1.0.0.1

Tunnel 1(E-Line) 1(E-Line)

Bandwidth Limit Enabled Enabled

CIR(kbit/s) 10000 30000

PIR(kbit/s) 30000 50000

11.6.3 Configuring the E-Line Service of the NETo configure a UNI-NNI E-Line service carried by ports is to configure the E-Line service atthe source NE and sink NE. This section describes how to configure the E-Line service.

Prerequisite


Procedure

Step 1 Set LSR IDs.

1. In the NE Explorer, select the NE1 and chooseConfiguration > MPLS Management >Basic Configuration from the Function Tree.

2. Set LSR ID, Start of Global Label Space and Start of Multicast Label Space. ClickApply.


l LSR ID: 1.0.0.1 (The LSR ID must be unique in the entire network.)


3. Display the NE Explorer of NE2 and NE3 separately and perform the preceding two stepsto set the parameters such as LSR ID.


l NE2 LSR ID: 1.0.0.2

l NE3 LSR ID: 1.0.0.3


Configuration Guide


Issue 06 (2009-06-01)

Step 2 Configure interfaces.1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure the interface.2. In the General Attributes tab, select the 3-EFF8-1(Port-1) 3-EF8F-2(Port-2) and 3-

EFF8-3(Port-3). Set the parameters such as Port Mode, Working Mode, and clickApply.


l Port: 3-EFF8-1(Port-1), 3-EFF8-2(Port-2)– Enable Port: Enabled

– Port Mode: Layer 2 (User-side interface, Company A is connected to 3-EFF8-1(Port-1), and Company B is connected to 3-EFF8-2(Port-2).)

– Encapsulation Type: 802.1Q

– Working Mode: Auto-Negotiation (Set the working modes of the local port andopposite port as the same.)

– Max Frame: 1620 (Set this parameter according to the length of data packets.)

l Port: 3-EFF8-3(Port-3)– Enable Port: Enabled

– Port Mode: Layer 3 (Network interface, the port carries a Tunnel.)

– Working Mode: Auto-Negotiation

– Max Frame: 1620

3. Select the 3-EFF8-3(Port-3) in the Layer 3 Attributes tab. Right click the EnableTunnel field and select Enabled. Right-click the Specify IP field and choose Manually.Then, set the parameters such as IP Address and IP Mask. Click Apply.




l IP Address: 10.0.0.1

l IP Mask: 255.255.255.252

4. Display the NE Explorer for NE2, and NE3 separately. Perform Step 2.1 to Step 2.3 to setparameters of each related interface.


l NE2– General Attribute

– Port: 20-EFF8-3(Port-3), 5-EX2-1(Port-1)

– Enable Port: Enabled

– Port Mode: Layer 3




11-35

– Max Frame: 1620

– Layer 3 Attribute– Enable Tunnel: Enabled

– TE Measurement: 10

– Specify IP: Manually

– 20-EFF8-3(Port-3) IP Address: 10.0.0.2

– 5-EX2-1(Port-1) IP Address: 10.0.1.1

– IP Mask: 255.255.255.252

l NE3– General Attribute

– Port: 20-EFF8-1(Port-1), 20-EFF8-2(Port-2)– Enable Port: Enabled




– Max Frame: 1620

– Port: 5-EX2-1(Port-1)– Enable Port: Enabled



– Max Frame: 1620

– Layer 3 Attribute– Enable Tunnel: Enabled

– TE Measurement: 10

– Specify IP: Manually

– IP Address: 10.0.1.2

– IP Mask: 255.255.255.252


Configuration > IGP-ISIS Configuration from the Function Tree.2. Select 3-EFF8-3(Port-3) in the Port Configuration tab. Right click IS-IS Enable field,

and select Enabled. Click Apply.

The configuration parameters are as follows:l IS-IS Enable: Enabled (After the IS-IS routing protocol is enabled, an MPLS LSP can

be dynamically created and PW labels can also be distributed dynamically.)l Link Level: level-1-2



Configuration Guide


Issue 06 (2009-06-01)


3. Display the NE Explorer for NE2, and NE3 separately. Set the parameters related to thecontrol plane by following Step 3.1 to Step 3.2. Set the IS-IS parameters of NE2 and NE3as the same as the IS-IS parameters of NE1.

Step 4 Creating MPLS Tunnels1. On the Main Topology, choose Trail > Tunnel Creation. The Create Tunnel dialog box








– L-LSP indicates that the tunnel determines the scheduling policy of packetsaccording to the MPLS labels and determines the discard policy of packets accordingto the EXP information. On one MPLS tunnel of the L-LSP type, there can be amaximum of one type of PWs. Currently, the OptiX PTN equipment does not supportthe L-LSP type.





l Sink Node: NE3






l Hold Priority: 0 (Hold priority is specified for an MPLS tunnel after creation. "0"indicates the highest priority. In the case of insufficiency of resources, the bandwidthfor the MPLS tunnel of a higher hold priority is less likely to be preempted by other



11-37

tunnels. When creating a dynamic tunnel, make sure that the hold priority is higher orequal to the setup priority.)




Step 5 Configure two UNI-NNI E-Line service.1. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line




l Service ID: 1




l Port: 3-EFF8-1(Port-1) (Company A is connected to 3-EFF8-1(Port-1).)

l VLANs: 100

l Bearer Type: PW

l PW ID: 35

3. Click Configure PW. Set the attributes of PW in Configure PW dialog box displayed,and click OK.


l General Attributes– PW ID: 35

– PW Signaling Type: Static

– PW Type: Ethernet


– PW Encapsulation Type: MPLS

– PW Ingress Label: 20

– PW Egress Label: 20

– Peer IP: 1.0.0.3

– Tunnel: 1

4. Click Configure QoS. Set QoS attributes of the PW in Configure QoS dialog boxdisplayed, and click OK.


l EXP: 4 (7 indicates the highest priority.)


Configuration Guide


Issue 06 (2009-06-01)

l LSP Mode: Uniform (The CoS of user packets should be recovered when the tunnellabel is stripped.)

5. Create the E-Line service of Company B at the source NE by following Step 5.1 to Step5.4.

For details of E-Line2 service, see Table 11-13.6. In the NE Explore select NE3, create the E-Line service from NE3 to NE1, by following


----End

11.7 Configuration Case of the UNI-NNI E-Line ServiceCarried by the QinQ Link

The configuration case illustrates how to configure a UNI-NNI E-Line service carried by theQinQ link. You can understand the configuration further by viewing the configuration flowdiagram. The configuration case covers the service planning, service configuration andverification of the E-Line service.

11.7.1 Case DescriptionThis section describes the networking diagram for transmission of isolated services betweencompanies.

11.7.2 Service PlanningThe Ethernet services between branches of a company are carried by the QinQ. When planningsuch an Ethernet service, you need to plan the NE information, QinQ information, and serviceinformation.

11.7.3 Configuring the E-Line ServiceConfigure the E-Line service at the source NE and sink NE to realize the UNI-NNI E-Lineservice carried by the QinQ link.

11.7.1 Case DescriptionThis section describes the networking diagram for transmission of isolated services betweencompanies.

As shown in Figure 11-12, both Company A and Company B have branches in City 1 and City2. Branches of each company need to communicate with each other. The traffic from the twocompanies must be isolated. The internal VLANs of Company A range from 1 to 100 and theinternal VLANs of Company B range from 1 to 200. To isolate the traffic of the two companies,different S-VLANs are added to packets from different companies at the network side.

The branches of Company A require the common Internet access service (CIR = 10 Mbit/s, PIR= 30 Mbit/s).

The branches of Company B require the data service (CIR = 30 Mbit/s, PIR = 50 Mbit/s).



11-39

Figure 11-12 Networking diagram for the UNI-NNI E-Line service carried by the QinQ link

A Company

City2

B Company

A Company

City1

B Company

PSN

NE 1

NE2

The internalnetwork of

Company AVLAN = 1-100


Company BVLAN = 1-200

A VLAN tag (VLAN = 30) is addedto the packet of Company A

City2

V-UNI for A Company : 19-ETFC-1V-UNI for B Company : 19-ETFC-2

NNI : 1-EG16-1

V-UNI for A Company : 19-ETFC-1V-UNI for B Company : 19-ETFC-2

NNI : 1-EG16-1


Company AVLAN = 1-100


Company BVLAN = 1-200

A VLAN tag (VLAN = 40) is addedto the packet of Company B

11.7.2 Service PlanningThe Ethernet services between branches of a company are carried by the QinQ. When planningsuch an Ethernet service, you need to plan the NE information, QinQ information, and serviceinformation.




NE1




Configuration Guide


Issue 06 (2009-06-01)


1-EG16-1(Port-1) Port Mode: Layer 2Encapsulation Type: QinQTag: Tag Aware

NE2



1-EG16-1(Port-1) Port Mode: Layer 2Encapsulation Type: QinQTag: Tag Aware

Table 11-16 lists the planning details on the QinQ link that carries the service.

Table 11-16 Planning of the QinQ link carrying the service

Parameter Service of Company A Service of Company B

QinQ Link ID 1 2

Board 1-EG16 1-EG16

Port 1(Port-1) 1(Port-1)

S-Vlan ID 30 40

Enable Bandwidth Enable Enable

CIR (kbit/s) 10000 30000

PIR (kbit/s) 30000 50000

Table 11-17 shows the planning details on the E-Line service.

Table 11-17 Planning of the UNI-NNI E-Line service carried by the QinQ link


Service ID 1 1





11-41


UNI 19-ETFC-1 19-ETFC-2

VLANs 1-100 1-200

Bearer Type QinQ Link QinQ Link

QinQ Link ID 1 2



MTU(byte) 1526 1526

11.7.3 Configuring the E-Line ServiceConfigure the E-Line service at the source NE and sink NE to realize the UNI-NNI E-Lineservice carried by the QinQ link.


Procedure

Step 1 Configure interfaces:1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure the network-side interface.2. In the General Attributes tab, select the 19-ETFC-1(Port-1), 19-ETFC-2(Port-2) and 1-

EG16-1(Port-1). Set the parameters such as Port Mode, Encapsulation Type as required,and click Apply.


l Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)– Enable Port: Enabled



– Working Mode: Auto-Negotiation (Set the working modes of the local port andopposite port as the same.)

– Max Frame: 1620 (Set this parameter according to the length of data packets.)

l Port: 1-EG16-1(Port-1)– Enable Port: Enabled


– Encapsulation Type: QinQ


– Max Frame: 1620


Configuration Guide


Issue 06 (2009-06-01)




l Tag: Tag Aware– If a port is set to Tag Aware, this port can transparently transmits the data packet

with the VLAN ID (Tag). If the data packet does not contain the VLAN ID (Untag),this packet is discarded.



4. In the NE Explorer select NE2, set the parameters of 1-EG16-1(Port-1), 19-ETFC-1(Port-1)and 19-ETFC-2(Port-2) by following Step 1.1 to Step 1.3.


l General Attributes– Port: 1-EG16-1(Port-1)

– Enable Port: Enabled


– Encapsulation Type: QinQ


– Max Frame: 1620

– Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)– Enable Port: Enabled




– Max Frame: 1620

l Layer 2 Attributes– Port: 19-ETFC-1(Port-1), 19-ETFC-2(Port-2)

– TAG: Tag Aware

Step 2 Create QinQ Links.1. In the NE explorer, select NE1 and choose Ethernet Service Management > QinQ

Link.2. Click New. Set the parameters of the link from NE1 to NE2 in Create QinQ Link dialog

box displayed, and click Apply.


l QinQ Link between branches of Company A



11-43

– QinQ Link ID: 1

– Board: 1-EG16

– Port: 1-(Port-1)

– S-Vlan ID: 30

l QinQ Link between branches of Company B– QinQ Link ID: 2

– Board: 1-EG16


– S-Vlan ID: 40

3. In the NE Explorer select NE2. Create the link from NE2-NE1 by following the previoustwo steps.


l QinQ Link between branches of Company A– QinQ Link ID: 1

– Board: 1-EG16


– S-Vlan ID: 30 (Add an S-Vlan tag with ID of 30 for the services between branchesof Company A so that the services of Company A are isolated from the services ofCompany B.)

l QinQ Link between branches of Company B– QinQ Link ID: 2

– Board: 1-EG16


– S-Vlan ID: 40 (Add an S-Vlan tag with ID of 40 for the services between branchesof Company B so that the services of Company B are isolated from the services ofCompany A.)

Step 3 Create two UNI-NNI E-Line services.1. In the NE explorer, select NE1 and choose Ethernet Service Management > E-Line




l Service between branches of Company A– Service ID: 1

– Service Name: E-Line-1

– Direction: UNI-NNI

– BPDU: Not Transparently Transmitted

– Port: 19-ETFC-1(Port-1)

– VLANs: 1-100

– Bearer Type: QinQ Link


Configuration Guide


Issue 06 (2009-06-01)

– QinQ Link ID: 1

l Service between branches of Company B

– Service ID: 2





– VLANs: 1-200


– QinQ Link ID: 2

3. In the NE Explore select NE2. Create an E-Line service from NE2 to NE1, by followingStep 3.1 to Step 3.2.


l Service between branches of Company A

– Service ID: 1





– VLANs: 1-100


– QinQ Link ID: 1

l Service between branches of Company B

– Service ID: 2





– VLANs: 1-200


– QinQ Link ID: 2

----End

11.8 Verifying the Correctness of Service ConfigurationAfter the E-Line service is configured, the correctness of service configuration should beverified. The Ethernet OAM is used to verify the correctness of Ethernet service configuration.



11-45

Context

The connectivity of the UNI-UNI E-Line service need no OAM verification. By default, theconfiguration is regarded as correct. In the case of the UNI-NNI E-Line service carried by a port,the OAM verification method is similar to that of the UNI-NNI E-Line service carried by PWs.

The UNI-NNI E-Line service carried by PWs is taken as an example. As shown in Figure11-13, to verify the correctness of service configuration, the Ethernet OAM should beconfigured.

Figure 11-13 OAM of the E-Line service

A Company

City2

Unicast Tunnel

B Company

A Company

City1B Company

MEP

MEP

MEP

MEP

MA

MD MA

NE 1 NE 2

PW MA: Maintenance Association

MD: Maintenance Domain

MEP: Maintenance End Point

As shown in the previous figure, E-Line services, which are carried and isolated by PWs, areavailable between branches of Company A and branches of Company B. To verify theconfiguration correctness of the two E-Line services, the Ethernet OAM should be configured.The verification of the E-Line service of Company A is taken as an example.

Procedure

Step 1 On the T2000, select NE1 to create the maintenance domain. For the creation method, seeCreating an MD.The parameters of the maintenance domain are as follows:

l Maintenance Domain Name: MD

l Maintenance Domain Level: 4

Step 2 On the T2000, select NE2 to create the maintenance domain. For the creation method, seeCreating an MD.The parameters of the maintenance domain are as follows:

l Maintenance Domain Name: MD

l Maintenance Domain Level: 4


Configuration Guide


Issue 06 (2009-06-01)

NOTEThe maintenance domain names and levels of NE1 and NE2 should be consistent, and then NE1 and NE2are in the same maintenance domain.

Step 3 On the T2000, select NE1 to create the maintenance association for Company A. For the creationmethod, see Creating an MA.The parameters of the maintenance association are as follows:l Maintenance Domain Name: MD

l Maintenance Association Name: MA

l Relevant Service: 1-E-Line-1

l CC Test Transmit Period (ms): 3.33 ms

Step 4 On the T2000, select NE2 to create the maintenance association for Company A. For the creationmethod, see Creating an MA.The parameters of the maintenance association are as follows:l Maintenance Domain Name: MD


l Relevant Service: 1-E-Line-1

l CC Test Transmit Period (ms): 3.33 ms

Step 5 On the T2000, select NE1 to create the MEP. For the creation method, see Creating a MEPMaintenance Point.The parameters of the MEP are as follows:l Maintenance Domain Name: MD


l Board: 19-ETFC

l Port: 1 (Port-1)

l VLAN: 100

l MP ID: 1

l Direction: Ingress

l CC Status: Active

Step 6 On the T2000, select NE2 to create the MEP. For the creation method, see Creating a MEPMaintenance Point.The parameters of the MEP are as follows:l Maintenance Domain Name: MD


l Board: 19-ETFC

l Port: 1 (Port-1)

l VLAN: 100

l MP ID: 2

l Direction: Ingress

l CC Status: Active



11-47

Step 7 On the T2000, select NE1 to perform the CC test. For the operation method, see Performing aContinuity Check.

NOTEIf the MEP of NE2 does not receive the CC packets from NE1 in a period of time (for example, 3.25 timesof the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If theETH_CFM_LOC alarm is not reported, the connectivity of the service from NE1 to NE2 is normal.

Step 8 On the T2000, select NE2 to perform the CC test. For the operation method, see Performing aContinuity Check.

NOTEIf the MEP of NE1 does not receive the CC packets from NE2 in a period of time (for example, 3.25 timesof the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If theETH_CFM_LOC alarm is not reported, the connectivity of the service from NE2 to NE1 is normal.

----End

11.9 Parameter DescriptionThis section describes the parameters related to the E-Line service configuration.

Table 11-18 Descriptions of the parameters for V-UNI Group


V-UNI GroupID

Example: 123 Set and query the ID of the V-UNI group.

V-UNI GroupType

Ingress, Egress Ingress indicates the in-coming networkdirection. Egress indicates the out-goingnetwork direction.Click C.45 V-UNI Group Type for moreinformation.

CIR (kbit/s) Example: 100000 Commit the rate for the service.

PIR (kbit/s) Example: 500000 Set the guaranteed rate for the service. The peakinformation rate should not be less than thecommitted information rate.

CBS (byte) - This parameter is not supported.

PBS (byte) - This parameter is not supported.

Service ID Example: 12 Set the ID of the created Ethernet service.

Interface Example: Slot-BoardName-Port(Port No)

Display the V-UNI interface selected by theservice in the format of Slot number - Boardname - Port number (VLAN ID).

SelectingInterface

- Display the available service IDs and V-UNIinterfaces for the service.

SelectedInterface

- Display the selected service ID and V-UNIinterface for the service.


Configuration Guide


Issue 06 (2009-06-01)



Checked, Unchecked When this parameter is selected, the actualeffective bandwidth is queried. When thisparameter is not selected, the configuredbandwidth is queried.

Table 11-19 Descriptions of the parameters for E-Line Service


Service ID Example: 11 Set and query the ID of the Ethernet service.

Service Name Example: test Set and query the name of the Ethernet service.

Source Node Example: Slot-BoardName-Port(Port No.)

Display the source node of the E-Line service.The format is Slot number - Board name - Portname (VLAN ID).

Sink Node Example: PW-0 Display the sink node of the E-Line service. Thesink node can be a port, PW or QinQ Link.

Direction UNI-UNI, UNI-NNI In the case of the UNI-NNI direction, select thenetwork-side bearer type as PW Port or QinQLink.

Service TagRole

User, Service Set the service tag role of E-line service.


Set and query the user-side port or network-sideport.

VLANs 1-4094 Set one or several VLAN IDs, or not set anyVLAN ID.

Bearer Type PW, Port, QinQ Link Set the bearer type when the service direction isset to UNI-NNI.Click C.57 Bearer Type for more information.

PW ID Example: 123 Set and query the PW ID of the service.Click C.30 PW ID for more information.

QinQ Link ID Example: 5 Select and display the QinQ Link ID.

BPDU Not TransparentlyTransmitted,TransparentlyTransmitted

Set whether the bridge protocol data unit(BPDU) packets are transparently transmitted.Click C.8 BPDU (E-Line) for moreinformation.



11-49


MTU(byte) 46 to 9000 Set the maximum transport unit (MTU). Whenreceiving packets of a length more than theMTU, the port divides the packets into segmentsand then transport these segments. If the packetscontain a flag indicating that packet division isnot allowed, the port discards the packet.After the service transmitted in a PW is created,the MTU value of the service cannot be changed.After the service transmitted through a port or inthe QinQ is created, however, the MTU value ofthe service can be changed. The reason is asfollows: In the case of the service transmitted ina PW, the MTU value needs to be negotiatedwhen the PW is created and cannot be changedafter creation.Click C.21 MTU(byte) for more information.

Table 11-20 Descriptions of the parameters for PW


ID Example: 1 Display the sequence of the PWs. Thisparameter is required for the E-AGGR service.

Location Source, Sink Set the location of the node on the PW. Thisparameter is required for the E-AGGR service.

PW ID Example: 123 Set the ID of the PW carrying the Ethernetservice.

Enable State Enable, Disable Set and display the enable status of the PW.

PW SignalingType

Static, Dynamic In the case of the dynamic PW, the label isautomatically allocated. In the case of the staticPW, the label is manually allocated. Theconfiguration at the two ends of a PW should beconsistent.

PW Type Ethernet, EthernetTagged Mode

PWs of different types process the borneservices differently. For example, the PW in theEthernet tagged mode attaches the tag on theservices on this PW.

Direction Bidirectional Set the direction of the PW.

PWEncapsulationType

MPLS, IP Display the encapsulation type of the PW.

PW IngressLabel

16 to 1048575 Set this parameter when the PW SignalingType is set to Static.


Configuration Guide


Issue 06 (2009-06-01)


PW EgressLabel


Peer IP Example:10.70.71.123

Set the peer IP of the PW.

Tunnel Type MPLS, IP, GRE Displays the type of the tunnel that carries thePW.NOTE

When you set PW Encapsulation Type to UDP, youcan set Tunnel Type to IP only.


Select a created tunnel. If no tunnel is available,creation of a PW fails.

Control Word Preferred Use, No Use The control word is the encapsulation packetheader of four bytes. The control word is usedto identify the packet sequence or be stuffingbits.

Control ChannelType

CW, None Set the type of the control channel used by thePW.


Ping, None Verify the connectivity of a PW. The VCCVverification mode is a tool used to manuallyverify the connectivity of a virtual circuit.

Local WorkingStatus

Up, Down Display the working status of the PW at the localend. Up indicates that the PW works normally.Down indicates that the PW work abnormally.


Up, Down Display the working status of the PW at theremote end. Up indicates that the PW worksnormally. Down indicates that the PW workabnormally.


Up, Down Display the compositive working status of thePW. Up indicates that the PW works normally.Down indicates that the PW work abnormally.

Request VLAN 1 to 4094 When the PW is in the Ethernet tagged mode,the PW attaches the VLAN set here on thepackets without any VLAN from the oppositeend.

Table 11-21 Descriptions of the parameters for QoS


Interface Example: Slot-BoardName-Port(Port No.)

Set the user-side interface.



11-51


PW ID Example: 123 Set the ID of the PW carrying the Ethernetservice.Click C.30 PW ID for more information.

QinQ Link ID Example: 5 The ID of the QinQ Link carrying the Ethernetservice.

Direction Ingress, Egress Set the direction of the interface, PW and QinQLink. Ingress indicates the in-coming direction.Egress indicates the out-going direction.

BandwidthLimit

Enabled, Disabled If Bandwidth Limit is set to Enabled, thebandwidth is limited according to the set CIR,PIR, CBS, PBS, tail drop threshold and WREDpolicy.

Policy Name Example: Qos-test Display the name of the QoS policy.Click C.55 Policy Name for more information.

Policy ID Example: 12 Display the ID of QoS policy.

CIR (kbit/s) 64 to 10000000 Commit the rate for the service.This field can be set after Bandwidth Limit isenabled.

CBS (byte) - This parameter is not supported..

PIR (kbit/s) 64 to 10000000 Set the maximum rate for the service. The peakinformation rate should not be less than thecommitted information rate.This field can be set after Bandwidth Limit isenabled.

PBS (byte) - This parameter is not supported..


Configuration Guide


Issue 06 (2009-06-01)


DefaultForwardingPriority

CS7, CS6,EF, AF4,AF3, AF2, AF1, BE,NONE

The CoS varies with the values.l CS6-CS7: Indicates the highest service class.

The CoS is applicable to transport ofsignaling.

l EF: Indicates fast forwarding. The CoS isapplicable to the service of little delay andpacket loss rate, such as the audio service.

l AF1-AF4: Indicates the guaranteedforwarding. The CoS is applicable to theservice that requires a certain rate, but doesnot limit the delay or jitter.

l BE: The CoS is applicable to the service thatneed not be processed exceptionally.

Ingress direction is configurable.Click C.117 Default Forwarding Priority formore information.

Default PacketRelabelingColor

none, red, yellow,green

Label packets with different colors according tothe label information carried with the packets.Ingress direction is configurable.Click C.113 Default Packet RelabelingColor for more information.

EXP 0-7, None Set the QoS priority labels in an MPLS network.These labels correspond to the eight classes.l 0 corresponds to BE.

l 1 corresponds to AF1.




l 5 corresponds to EF.

l 6 corresponds to CS6.


LSP Mode Uniform, Pipe Set and display the LSP mode.l Uniform: The CoS of user packets should be

recovered when the tunnel label is stripped.l Pipe: The CoS of user packets need not be

recovered when the tunnel label is stripped.Click C.18 LSP Mode for more information.





11-53


Configuration Guide


Issue 06 (2009-06-01)

12 Configuring an E-LAN Service

About This Chapter

This section describes the basic information about the E-LAN service, and uses an example todescribe how to configure an E-LAN service.

12.1 E-LAN ServiceIn topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwardsthe packets of a specific port or of specific VLANs of a specific port at the user side to multipleports at the network side, a PW or a QinQ Link at the network side. In this way, the user datacan be transparently transmitted in a multipoint-to-multipoint manner.

12.2 Configuration Flow for E-LAN ServiceThe configuration flow of the E-LAN service include creating network, configuring the QoSpolicy, configuring interfaces, configuring the control plane, configuring MPLS tunnel andconfiguring E-LAN service.

12.3 Operation Tasks for the E-LAN ServiceThe operation tasks for the E-LAN service include the creation of E-LAN services and creationof V-UNI groups.

12.4 Configuration Case of the E-LAN ServiceThis section describes a configuration example of the E-LAN service. A configuration flowdiagram is provided to describe the process of service configuration. The configuration exampleincludes the service planning and E-LAN service configuration.

12.5 Parameter DescriptionThis section describes the parameters related to the E-LAN service configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 12 Configuring an E-LAN Service


12-1

12.1 E-LAN ServiceIn topology, the E-LAN service is a multipoint-to-multipoint service. The equipment forwardsthe packets of a specific port or of specific VLANs of a specific port at the user side to multipleports at the network side, a PW or a QinQ Link at the network side. In this way, the user datacan be transparently transmitted in a multipoint-to-multipoint manner.

Figure 12-1 shows the networking diagram for the E-LAN service.

The three user side networks respectively access the carrier networks through the FE. Each userside network has its own VLAN label. The user side networks require access between each other.The user side networks can communicate with each other through the configuration of the E-LAN service.

On each PE node, the accessed data is forwarded through the target MAC address or target MACaddress + VLAN. At the network side, the data is transparently transmitted to the opposite PEequipment through the created MPLS tunnel.

In this case, the entire transport network, which exchanges different data at the user sides, equalsa Layer 2 switch. In other words, the transport network is transparent to the user network. In theuplink direction of user side of each PE node, complex traffic classification can be performedfor data packets, and different QoS policies can be used according to the traffic classification.

Figure 12-1 E-LAN service

NE 1

FE

MPLS Tunnel 2

MPLS Tunnel 3

NE 2

NE 3

CE 2

FE

FE

MPLSTunnel 1

CE 1

CE 3PSN

PE

At present, the equipment supports the C-VLAN packet, S-VLAN+C-VLAN packet, andEthernet packet without VLAN. At the network side, the accessed packets can be flexiblyprocessed through the configuration of PW attributes. For example, the dropping and additionof S-VLAN is available.

12 Configuring an E-LAN ServiceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

According to the conditions of the accessed user side network, the port attributes, serviceattributes, and PW attributes of the E-LAN service can be flexibly configured to meetrequirements of different application scenarios.

At the network-side port, the service can be carried by ports, a PW or a QinQ link for transport.In the case of the QinQ link carrying, the packets with the C-VLAN in the user-side networkare added with an S-VLAN header of the transport network. The packets then travel through thetransport network with two VLANs. In this way, a simple L2-VPN tunnel is provided for theuser. To realize the QoS for the service carried by a QinQ link, configure the QinQ policy.

12.2 Configuration Flow for E-LAN ServiceThe configuration flow of the E-LAN service include creating network, configuring the QoSpolicy, configuring interfaces, configuring the control plane, configuring MPLS tunnel andconfiguring E-LAN service.

Figure 12-2 shows the flow for configuring an E-LAN service.

Figure 12-2 Flow diagram for configuring the E-LAN service

Configuring E-LANService

Creating Network

ConfiguringInterfaces

Configuring theControl Plane

Configuring the QoSPolicy

StartRequired

Optional

End

Configuring an MPLSTunnel



End

Configuring QinQLink



End


The columns in the figure shows the three sub processes. From left to right, the sub systemsindicate the NNI carried by ports, NNI carried by PWs, and NNI carried by QinQ Linkrespectively.



12-3

Before configuring the E-LAN service, you should complete 2 Creating Network, and 4.3Configuring Ethernet Interfaces.

Perform the following operations according to the NNI bearer type.

l In the case that the operations mentioned above are completed, when the port is set to BearerType, the E-LAN service can be configured.

l When the PW is set to Bearer Type, the MPLS tunnel need be configured. See the followingcontents according to the MPLS tunnel type.– When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE

basis or by using the trail function. See 6.3 Creating a Static MPLS Tunnel by Usingthe Trail Function and 6.5 Creating an MPLS Tunnel on a Per-NE Basis. When thestatic MPLS tunnel is used, 5 Configuring the Control Plane can be skipped.

– When the dynamic MPLS tunnel is used, see 6.2 Creating a Dynamic MPLS Tunneland the FRR Protection by Using the Trail Function.

l If the network side is carried by the QinQ Link, 11.3.4 Creating a QinQ Link need becomplete.

When configuring the E-LAN service, see 12.4 Configuration Case of the E-LAN Service.

12.3 Operation Tasks for the E-LAN ServiceThe operation tasks for the E-LAN service include the creation of E-LAN services and creationof V-UNI groups.

12.3.1 Creating an E-LAN ServiceOn the T2000, the E-LAN service can be created. Multiple types of E-LAN services can berealized by configuring the UNI and NNI ports. The NNI port can carry the service by using theport, PW or QinQ link.

12.3.2 Managing the BlacklistManaging the blacklist can prevent the illegal packets from the network side or user side fromattacking the equipment. Hence, the equipment can run stably in the network. Managing theblacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist.

12.3.3 Setting the Broadcast Storm SuppressionThe broadcast storm suppression function can restrain the broadcast traffic on the port that carriesthe ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Settingthe broadcast storm suppression function includes enabling the broadcast storm suppression andsetting the broadcast suppression threshold.


12.3.1 Creating an E-LAN ServiceOn the T2000, the E-LAN service can be created. Multiple types of E-LAN services can berealized by configuring the UNI and NNI ports. The NNI port can carry the service by using theport, PW or QinQ link.


Configuration Guide


Issue 06 (2009-06-01)

Prerequisite


You must complete the correct configuration of the port attributes.

You must complete the creation of the MPLS tunnel that carries the PW.

If the port need be exclusively used, disable the DCN function of the port that carries the service.For the operation steps, see Enabling the Port DCN.

If the service need be carried by a QinQ link, you must configure a QinQ link first.

If a QoS policy is required for configuring the QoS, you must create a QoS policy first.

WARNINGl The ML-PPP line should not carry any E-LAN service.

l On the network side, the E-LAN service does not support the LMSP, FRR, MPLS APS, andLAG protection.

Procedure

Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet ServiceManagement > E-LAN Service from the Function Tree.

Step 2 Click New to display the New E-LAN Service dialog box. Then, set Service ID, ServiceName and MTU(byte).For details on the parameters for the E-LAN service, see Table 12-15.



12-5

NOTE

l Self-Learning MAC Address can be set to enabled or disabled. When Self-Learning MACAddress is set to enabled, the bridge supports the MAC address self-learning, the forwarding tableitems are generated through the MAC address self-learning. You can also manually configure the staticMAC address forwarding table items. When Self-Learning MAC Address is set to disabled, the bridgedoes not support the MAC address self-learning and you can manually configure the static MAC addressforwarding table items only.

l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates the shared VLAN learning.All VLANs share a MAC address forwarding table. Any MAC address is unique in the forwardingtable. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs areindependent from each other. It is acceptable that the MAC address forwarding tables for differentVLANs have the same MAC address.

l Tag Type can be set to C-Awared, S-Awared or Tag Transparent. C-Awared corresponds to theaccessed service packets with one C-VLAN. S-Awared corresponds to the accessed service packetswith one C-VLAN and one S-VLAN. Tag Transparent corresponds to the accessed service packetswithout any VLAN. Now, the S-Awared cannot be supported.

Step 3 Click OK to display the Operation Result dialog box, which indicates that the operation issuccessful. Then, click Close.

Step 4 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.Fordetails on the parameters for UNI ports the E-LAN service, see Table 12-5.

Step 5 In the Available Ports list, select the port. Then, click to add the port to the SelectedPorts list.

Step 6 In the Selected Ports list, set VLANs of the port, and then click OK.

Step 7 Click the NNI tab.l If configuring the NNI interface carried by the port, click the Port tab. See Step 4 to Step

6 to add and configure the NNI port. Then, click OK.For details on the parameters for theNNI ports of the E-LAN service, see Table 12-6.

l If configuring the NNI interface carried by the PW, click the PW tab. Click New, and setthe parameters related to the PW. Then, click OK.For details on the parameters for PW ofthe E-LAN service, see Table 12-7.


Configuration Guide


Issue 06 (2009-06-01)

l If configuring the NNI interface carried by the QinQ link, click the QinQ Link tab.Fordetails on the parameters for QinQ Link of the E-LAN service, see Table 12-8.

1. Click Add. The QinQ Link Management window is displayed.2. Select a QinQ link ID and click OK.3. Click Apply. The Operation Result dialog box is displayed, indicating that the

operation is successful. Click Close,



12-7

NOTE

The services carried by the QinQ link can not support to create MP.

Step 8 Click the Split Horizon Group tab. Then, click New to display the New Split HorizonGroup dialog box.For details on the parameters for split horizon group of the E-LAN service,see Table 12-9.

Step 9 Configure the split horizon group id, and add the interface that need be added into the splithorizon group to the Selected Interfaces pane. Click OK to display the Operation Result dialogbox, which indicates that the operation is successful. Then, click Close.

Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),Address Table Specified Capacity, Address Detection Upper Threshold(%) and AddressDetection Lower Threshold(%).For details on the parameters for MAC address learning of theE-LAN service, see Table 12-10.

NOTE

Address Detection Upper Threshold(%) and Address Detection Upper Threshold(%) indicate theupper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, theequipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.

Step 11 Click Apply. The Operation Result dialog box is displayed, indicating that the operation issuccessful. Click Close.

Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast framesand multicast frames. The default value is broadcast. For details on the parameters for unknownframe processing of the E-LAN service, see Table 12-11.

Step 13 Click Apply. The Operation Result dialog box is displayed, indicating that the operation issuccessful. Click Close.

Step 14 Optional: Click QoS tab. Set the parameters of the QoS.For details on the parameters for QoSof the E-LAN service, see Table 12-12.l Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling

Color of the port. Click Apply to display the Operation Result dialog box, which indicatesthat the operation is successful. Then, click Close.

l Click the PW tab. Set EXP and LSP Mode. Click Apply to display the OperationResult dialog box, which indicates that the operation is successful. Then, click Close.

NOTE

If Bandwidth Limit is set to enabled, CIR (kbit/s) and PIR (kbit/s) can be set. The QoS policy canalso be selected from Policy. Before selecting the policy, the policy should be created.

l Click the QinQ Link tab. Enable the bandwidth limit and select the QinQ policy for theingress and egress directions of the QinQ link. Click Apply. The Operation Result dialogbox is displayed, indicating that the operation is successful. Click Close,

NOTE

Before selecting the policy, the policy should be created. If Bandwidth Limit is set to enabled, CIR(kbit/s) and PIR (kbit/s) can be set.

Step 15 Optional: Click the Static MAC Address tab. Manually bind the VLAN ID, MAC Addressand Egress Interface.For details on the parameters for static MAC address of the E-LAN service,see Table 12-16.

NOTE

Set the VLAN ID only when MAC Address Learning Mode is set IVL.


Configuration Guide


Issue 06 (2009-06-01)

Step 16 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-relatedparameters.For details on the parameters for maintenance association of the E-LAN service, seeTable 12-13.For details on the parameters for MEP point of the E-LAN service, see Table12-14.

NOTE


----End

12.3.2 Managing the BlacklistManaging the blacklist can prevent the illegal packets from the network side or user side fromattacking the equipment. Hence, the equipment can run stably in the network. Managing theblacklist includes querying the blacklist, creating the blacklist, and deleting the blacklist.


You must complete the creation of E-LAN services.

ContextAfter the MAC address blacklist is created on a port that carries the ELAN service, if thedestination MAC or source MAC information carried by a packet enters this port is consistentwith a random MAC address created in the blacklist, this packet is discarded.

NOTE

The MAC address that is added to the static route should not be added to the MAC address of the blacklist.

Procedure


Step 2 In the Disabled MAC Address tab page, select Query to query the added MAC address of theblacklist.

Step 3 Click New and the Create Disabled MAC Address dialog box is displayed. Set VLAN ID andMAC Address.



12-9

Step 4 Click OK.

Step 5 Optional: In the interface, select the information of a MAC address, and then click Delete.Hence, the MAC address information is deleted from the blacklist.

----End

12.3.3 Setting the Broadcast Storm SuppressionThe broadcast storm suppression function can restrain the broadcast traffic on the port that carriesthe ELAN service. Hence, the bandwidth resource of the equipment can be properly used. Settingthe broadcast storm suppression function includes enabling the broadcast storm suppression andsetting the broadcast suppression threshold.

Prerequisite


You must complete the creation of E-LAN services.

Context

The broadcast suppression is enabled on a port that carries the ELAN service. In this case, whenthe packets that enter this port are unknown unicast packets, unknown multicast packets, orbroadcast packets, if the traffic exceeds the broadcast suppression threshold set for the port, thepackets that exceeds the bandwidth are discarded.

NOTE

Currently, the equipment supports the broadcast suppression function for the UNI only. The broadcastsuppression function for the NNI is not supported.

Procedure


Step 2 In the UNI tab page, select the corresponding port. Double-click the Enabled Broadcast PacketSuppression parameter field, and then select Enabled.


Configuration Guide


Issue 06 (2009-06-01)

Step 3 Double-click the Broadcast Suppression Threshold parameter field, and then set the thresholdvalue.

Step 4 Click Apply.

----End





Procedure






12-11


NOTE

The interfaces on the same interface board can be configured into the same V-UNI group.The former eight interfaces on the EG16 can be configured into the same V-UNI group, and the latter eightinterfaces can be configured into the same V-UNI group.


----End

12.4 Configuration Case of the E-LAN ServiceThis section describes a configuration example of the E-LAN service. A configuration flowdiagram is provided to describe the process of service configuration. The configuration exampleincludes the service planning and E-LAN service configuration.

12.4.1 Case DescriptionThis section describes the functional requirement, networking diagram, and service planning.

12.4.2 Configuring E-LAN Service for the NE


Configuration Guide


Issue 06 (2009-06-01)

This section describes how to configure the E-LAN service for the NE.

12.4.1 Case DescriptionThis section describes the functional requirement, networking diagram, and service planning.

Requirement and Networking DiagramAs shown in Figure 12-3, the three CE networks need communication with each other. EachCE network has the same VLAN value, that is, 100.

Among the CE networks, three types of services, including the voice service, data service, andcommon Internet access service, are available. Each CE requires a network bandwidth of 100Mbit/s. The complex traffic classification can be performed at the access side, and different QoSpolicies for assured bandwidth can be configured.

Figure 12-3 Networking diagram for the E-LAN service

NE 1

FE

MPLS Tunnel 3

MPLS Tunnel 2

NE 2

NE 3

CE 2

FE

FE

MPLS Tunnel 1

CE 1

CE 3

UNI for CE1: 1-EG16-19-ETFC-1NNI for CE2: 1-EG16-20-POD41-1NNI for CE3: 1-EG16-20-POD41-2



PSN

VLAN=100

VLAN=100

VLAN=100

Service PlanningIn the network, the service is carried by a PW. Thus, the parameters related to the PW and MPLStunnel should be planned. In this example, the tunnel is created in the manner of fast creation ofa dynamic tunnel.

Table 12-1 lists the planning of the tunnel that carries the PW.



12-13

Table 12-1 Planning of the tunnel that carries the PW

Field ForwardTunnel 1

ReverseTunnel 1

ForwardTunnel 2

ReverseTunnel 2

ForwardTunnel 3

ReverseTunnel 3

Tunnel ID 1 2 3 4 5 6

TunnelName

E-LAN E-LAN E-LAN E-LAN E-LAN E-LAN

SignalingType

Dynamic Dynamic Dynamic Dynamic Dynamic Dynamic

Scheduling Type

E-LSP E-LSP E-LSP E-LSP E-LSP E-LSP

Bandwidth

100 Mbit/s 100 Mbit/s 100 Mbit/s 100 Mbit/s 100 Mbit/s 100 Mbit/s

Source NE NE 1 NE 2 NE 2 NE 3 NE 1 NE 3

Sink NE NE 2 NE 1 NE 3 NE 2 NE 3 NE 1

RouteConstraintPort IPAddress

- - - - - -

Table 12-2 lists the planning of the Ethernet service.

Table 12-2 Planning of the E-LAN service carried by a PW

Field NE 1 NE 2 NE 3

Service ID 1 1 1

Service Name E-LAN E-LAN E-LAN




Tag Type C-Awared C-Awared C-Awared

Self-Learning MACAddress

Enabled Enabled Enabled

MAC AddressLearning Mode

SVL SVL SVL

MTU (byte) 1526 1526 1526

Table 12-3 lists the planning of the UNI port for each NE.


Configuration Guide


Issue 06 (2009-06-01)

Table 12-3 Planning of the UNI port


Port 1-EG16-19-ETFC-1 1-EG16-19-ETFC-1 1-EG16-19-ETFC-1

VLAN Value 100 100 100

Table 12-4 lists the planning of the NNI PW for each NE.



PW ID 10 20 20 30 30 10

PWSignalingType

Static Static Static Static Static Static

PW Type Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet

Direction Bidirectional

Bidirectional

Bidirectional

Bidirectional

Bidirectional

Bidirectional

PWIngressLabel

20 40 20 40 30 30

PW EgressLabel

30 20 40 30 40 20

Peer IP 1.1.1.3 1.1.1.2 1.1.1.1 1.1.1.3 1.1.1.2 1.1.1.1

Tunnel Tunnel 3 Tunnel 1 Tunnel 1 Tunnel 2 Tunnel 2 Tunnel 3

In the case of the split horizon group, the interfaces at the network side of each PE NE shouldbe configured into a split horizon group. In this way, the broadcast storm caused by the mutuallyforwarded data of the network side port can be prevented.

In the case of unknown frame processing, broadcast is planned.

12.4.2 Configuring E-LAN Service for the NEThis section describes how to configure the E-LAN service for the NE.




12-15

Procedure

Step 1 On the T2000, configure the E-LAN service for NE1. For the configuration method, see 12.3.1Creating an E-LAN Service.The parameters related to the E-LAN service are as follows:l Service ID: 1

l Service Name: E-LAN


l Tag Type: C-Awared

l Self-Learning MAC Address: Enabled

l MAC Address Learning Mode: SVL

l MTU (byte): 1526

l Split Horizon Group: 20-POD41-1, 20-POD41-2

l Unknown Frame Processing: Broadcast

l UNI:– Configure Port: 1-EG16-19-ETFC-1

– VLANs: 100

l NNI PW parameters:– PW ID: 10






– Peer IP: 1.1.1.3

– Tunnel: Tunnel 3

– PW ID: 20






– Peer IP: 1.1.1.2





Configuration Guide


Issue 06 (2009-06-01)





l MTU (byte): 1526




– VLANs: 100

l Parameters of the PW for the NNI:– PW ID: 20






– Peer IP: 1.1.1.1


– PW ID: 30






– Peer IP: 1.1.1.3








l MTU (byte): 1526




12-17



– VLANs: 100

l Parameters of the PW for the NNI:– PW ID: 10






– Peer IP: 1.1.1.1


– PW ID: 30






– Peer IP: 1.1.1.2


----End

12.5 Parameter DescriptionThis section describes the parameters related to the E-LAN service configuration.

Table 12-5 Descriptions of the parameters for an UNI Port


Port For example, 1-EG16-1 (port-1)(1-2)

Indicates the user-side port.

VLANs 1 to 4094 Queries and configures the VLAN ID. TheVLAN ID can be null; or you can set one or moreVLAN IDs.

EnabledBroadcastPacketSuppression

Enabled and Disabled Sets whether to enable the broadcast packetsuppression. Enabling the broadcast packetsuppression efficiently prevents the broadcaststorm and network congestion, and ensures thenormal running of services. The E-LAN servicesupports this parameter.


Configuration Guide


Issue 06 (2009-06-01)


BroadcastPacketSuppressionThreshold

0-100Default: 30

Configures the threshold of the broadcast packetsuppression. The E-LAN service supports thisparameter.When the broadcast packet suppression isenabled, the broadcast packets are suppressed ifthe following requirement is met: Occupancyrate of the broadcast packet to the bandwidth ofthe current port > the total bandwidth of the portx the suppression threshold x 1%. A lowoccupancy rate indicates that the number ofbroadcast packets that pass through the port issmall. If the occupancy rate is 100%, it indicatesthat the broadcast packets that pass through theport are not suppressed.

ID For example, 1 Displays the ID of the UNI port. The E-AGGRservice supports this parameter.

Location Source, Sink Displays the location of the UNI port. The E-AGGR service supports this parameter.

Table 12-6 Descriptions of the parameters for NNI Port


ID Example: 1 Display the sequence of the PWs. Thisparameter is required for the E-AGGR service.This parameter is required for the E-AGGRservice.

Location Source, Sink Set location of the port involved in the service.This parameter is required for the E-AGGRservice.This parameter is required for the E-AGGRservice.


Set the network-side port.This parameter is required for the E-AGGRservice.

Table 12-7 Descriptions of the parameters for PW


ID Example: 1 Display the sequence of the PWs. Thisparameter is required for the E-AGGR service.



12-19


Location Source, Sink Set the location of the node on the PW. Thisparameter is required for the E-AGGR service.

PW ID Example: 123 Set the ID of the PW carrying the Ethernetservice.

Enable State Enable, Disable Set and display the enable status of the PW.

PW SignalingType

Static, Dynamic In the case of the dynamic PW, the label isautomatically allocated. In the case of the staticPW, the label is manually allocated. Theconfiguration at the two ends of a PW should beconsistent.

PW Type Ethernet, EthernetTagged Mode

PWs of different types process the borneservices differently. For example, the PW in theEthernet tagged mode attaches the tag on theservices on this PW.

Direction Bidirectional Set the direction of the PW.

PWEncapsulationType

MPLS, IP Display the encapsulation type of the PW.

PW IngressLabel


PW EgressLabel


Peer IP Example:10.70.71.123

Set the peer IP of the PW.

Tunnel Type MPLS, IP, GRE Displays the type of the tunnel that carries thePW.NOTE

When you set PW Encapsulation Type to UDP, youcan set Tunnel Type to IP only.


Select a created tunnel. If no tunnel is available,creation of a PW fails.

Control Word Preferred Use, No Use The control word is the encapsulation packetheader of four bytes. The control word is usedto identify the packet sequence or be stuffingbits.

Control ChannelType

CW, None Set the type of the control channel used by thePW.


Ping, None Verify the connectivity of a PW. The VCCVverification mode is a tool used to manuallyverify the connectivity of a virtual circuit.


Configuration Guide


Issue 06 (2009-06-01)


Local WorkingStatus

Up, Down Display the working status of the PW at the localend. Up indicates that the PW works normally.Down indicates that the PW work abnormally.


Up, Down Display the working status of the PW at theremote end. Up indicates that the PW worksnormally. Down indicates that the PW workabnormally.


Up, Down Display the compositive working status of thePW. Up indicates that the PW works normally.Down indicates that the PW work abnormally.

Request VLAN 1 to 4094 When the PW is in the Ethernet tagged mode,the PW attaches the VLAN set here on thepackets without any VLAN from the oppositeend.

Table 12-8 Descriptions of the parameters for QinQ Link


QinQ Link ID Example: 5 Display the QinQ Link ID.

Port Example: Slot-Board Name-Port(Port No.)

Display the board and port.

S-Vlan ID Example: 4 Display the S-VLAN ID.

Direction Ingress, Egress Display the direction of theservice.

Bandwidth Limit Enabled, Disabled Display the bandwidth limit.When Bandwidth Limit isset to Enabled, you can setCommitted InformationRate and Peak InformationRate.

CIR (kbit/s) Example: 16000 Display the committedinformation rate, which is theguaranteed rate that can beprovided to the service.

CBS (byte) - Display the committed burstsize, which is the guaranteedflow size allowed for eachburst.



12-21


PIR (kbit/s) Example: 20000 Display the peak informationrate, which is the maximumrate that can be provided forthe service.

PBS (byte) - Display the peak burst size,which is the maximum flowsize allowed for eachexcessive burst.

Policy Policy ID + Policy NameExample: 1(policy1)

Display the QinQ policy.

Table 12-9 Descriptions of the parameters for Split Horizon Group


Split HorizonGroup ID

1 Display the ID of the split horizon group.Click C.123 Split Horizon Group ID for moreinformation.

Split HorizonGroup Member

Example: PW-100,3-EG16-PORT1[90,100]

Set members in the split horizon group. Severalmembers are separated by ",". You can set someUNIs or NNIs as a split horizon group.Click C.124 Split Horizon Group Member formore information.

Table 12-10 Descriptions of the parameters for MAC Address Learning Parameters


Aging Ability Enabled, Disabled If no packets of an MAC address listed in theMAC address table are received during a period,the MAC address is deleted from the MACaddress table.Click C.105 Aging Ability for moreinformation.

Aging Time(min)

1-640 If the aging ability is enabled, whether an MACaddress is aged is determined according to theset aging time.Click C.106 Aging Time (min) for moreinformation.

Address TableSpecifiedCapacity

0-65534 Set the capacity of the MAC address table.Click C.71 Address Table SpecifiedCapacity for more information.


Configuration Guide


Issue 06 (2009-06-01)


AddressDetection UpperThreshold (%)

80-100 Set the upper threshold for address detection.The upper threshold should be higher than thelower threshold. If the number of MACaddresses actually learned is more than the upperthreshold, the FDBSIZEALM_ELAN alarm isgenerated.Click C.72 Address Detection UpperThreshold (%) for more information.

AddressDetectionLowerThreshold (%)

60-100 Set the lower threshold for address detection.The lower threshold should be lower than theupper threshold.Click C.73 Address Detection LowerThreshold (%) for more information.

Table 12-11 Descriptions of the parameters for Unknown Frame Processing


Frame Type Unicast Display the type of the received unknownframes.Click C.153 Frame Type for more information.

Handing Mode Discard, BroadcastDefault: Broadcast

Select the mode for handling the unknownframes. Discard indicates that unknown framesare directly discarded. Broadcast indicates thatunknown frames are broadcast at the forwardingport.Click C.60 Handling Mode (EthernetUnknown Frame) for more information.

Total Example: 2 Display the count of unknown frames.

Selected Example: 1 Display the count of selected unknown frames.

Table 12-12 Descriptions of the parameters for QoS


Interface Example: Slot-BoardName-Port(Port No.)

Set the user-side interface.

PW ID Example: 123 Set the ID of the PW carrying the Ethernetservice.Click C.30 PW ID for more information.



12-23


QinQ Link ID Example: 5 The ID of the QinQ Link carrying the Ethernetservice.

Direction Ingress, Egress Set the direction of the interface, PW and QinQLink. Ingress indicates the in-coming direction.Egress indicates the out-going direction.

BandwidthLimit

Enabled, Disabled If Bandwidth Limit is set to Enabled, thebandwidth is limited according to the set CIR,PIR, CBS, PBS, tail drop threshold and WREDpolicy.

Policy Name Example: Qos-test Display the name of the QoS policy.Click C.55 Policy Name for more information.

Policy ID Example: 12 Display the ID of QoS policy.

CIR (kbit/s) 64 to 10000000 Commit the rate for the service.This field can be set after Bandwidth Limit isenabled.

CBS (byte) - This parameter is not supported..

PIR (kbit/s) 64 to 10000000 Set the maximum rate for the service. The peakinformation rate should not be less than thecommitted information rate.This field can be set after Bandwidth Limit isenabled.

PBS (byte) - This parameter is not supported..

DefaultForwardingPriority

CS7, CS6,EF, AF4,AF3, AF2, AF1, BE,NONE

The CoS varies with the values.l CS6-CS7: Indicates the highest service class.

The CoS is applicable to transport ofsignaling.

l EF: Indicates fast forwarding. The CoS isapplicable to the service of little delay andpacket loss rate, such as the audio service.

l AF1-AF4: Indicates the guaranteedforwarding. The CoS is applicable to theservice that requires a certain rate, but doesnot limit the delay or jitter.

l BE: The CoS is applicable to the service thatneed not be processed exceptionally.

Ingress direction is configurable.Click C.117 Default Forwarding Priority formore information.


Configuration Guide


Issue 06 (2009-06-01)


Default PacketRelabelingColor

none, red, yellow,green

Label packets with different colors according tothe label information carried with the packets.Ingress direction is configurable.Click C.113 Default Packet RelabelingColor for more information.

EXP 0-7, None Set the QoS priority labels in an MPLS network.These labels correspond to the eight classes.l 0 corresponds to BE.





l 5 corresponds to EF.



LSP Mode Uniform, Pipe Set and display the LSP mode.l Uniform: The CoS of user packets should be

recovered when the tunnel label is stripped.l Pipe: The CoS of user packets need not be

recovered when the tunnel label is stripped.Click C.18 LSP Mode for more information.



Table 12-13 Descriptions of the parameters for Maintenance Association


MaintenanceDomain Name

1-8 characters Set an MD name that is unique in the entirenetwork.

MaintenanceAssociationName

1-8 characters bytes Set an MA name that is unique in the same MD.

CC TestTransmit Period

3.33 ms, 10 ms, 100ms, 1s, 10s, 1m, 10m

Set the period for transmitting the CC packets.Click C.10 CC Test Transmit Period for moreinformation.



12-25

Table 12-14 Descriptions of the parameters for MEP Point


MaintenanceDomain Name

1-8 characters The name of an MD should be unique in theentire network.

MaintenanceAssociationName

1-8 characters The name of an MA should be unique in thesame MD.

Board Example: Slot-BoardName

Display the board where the MEP point islocated. The format is Slot number - Boardname.


Display the port where the MEP point is located.Slot number - Board name - Port information

Node Example: Slot-BoardName-Port(Port No.)

Set the node as an MEP point.

VLAN Example: 22 Set the current VLAN ID of the service.

MP ID 1-8191 Set a unique ID for each MP. The ID is requiredfor OAM operations.

Direction Ingress, Egress Ingress indicates the direction for packets toenter the board. Egress indicates the directionfor packets to exit the board.

CC Status Active, Inactive Activate or deactivate the CC function of theMEP point.

Table 12-15 Descriptions of the parameters for E-LAN Service





Set whether the bridge protocol data unit(BPDU) packets are transparently transmitted.Click BPDU (E-LAN) for more information.

Tag Type C-Awared, S-Awared,Tag-Transparent

C-Awared indicates that the learning is basedon the C-TAG (client-side VLAN tag).S-Awared indicates that the learning is based onthe S-TAG (operator service-layer VLAN tag).Now, the S-Awared cannot be supported.Tag-Transparent indicates that only theEthernet packets without VLAN tags can beaccessed.Click C.38 Tag Type for more information.


Configuration Guide


Issue 06 (2009-06-01)


Self-LearningMAC Address

Enabled, Disabled Add the self-learned MAC addresses to theMAC address forwarding table.Click C.20 Self-learning MAC Address formore information.

MAC AddressLearning Mode

SVL, IVL SVL indicates the shared VLAN learning. AllVLANs share a MAC address forwarding table.Any MAC address is unique in the forwardingtable.IVL indicates the independent VLAN learning.The forwarding tables for different VLANs areindependent from each other. It is acceptablethat the MAC address forwarding tables fordifferent VLANs have the same MAC address.When Tag Type is set to Tag-Transparent, theparameter value is SVL by default and youcannot set it manually.Click C.19 MAC Address Learning Mode formore information.

MTU (byte) 960 to 9000Default: 1500

Set the maximum transport unit (MTU). Whenreceiving packets of a length more than theMTU, the port divides the packets into segmentsand then transport these segments. If the packetscontain a flag indicating that packet division isnot allowed, the port discards the packet.Click C.21 MTU(byte) for more information.

Service TagRole

User Display the service tag role of E-LAN service.

Available Ports Example:Port: 11-EG16-1(Port-1)VLANs: 12

Display the available ports for configuring theEthernet service and the VLAN values.

Selected Ports Example:Port: 11-EG16-1(Port-1)VLANs: 12

Display the selected ports for configuring theEthernet service and the VLAN values.

AvailableInterfaces

- Display the available interfaces for configuringthe split horizon group.

SelectedInterfaces

- Display the selected interfaces for configuringthe split horizon group.



12-27

Table 12-16 Descriptions of the parameters for Static MAC Address


VLAN ID Example: 12 Set the ID of the service.

MAC Address Example: 00-e0-fc-39-80-34

Set the static MAC address.

Egress Interface Example: PW-100 Set the egress interface, which can be the PW,port or QinQ Link.


Configuration Guide


Issue 06 (2009-06-01)

13 Configuring an E-AGGR Service

About This Chapter

This section describes basic information on E-AGGR services, and uses an example to illustratehow to configure an E-AGGR service.

13.1 E-AGGR ServiceIn topology, the E-AGGR service is a multipoint-to-point service. The OptiX PTN equipmentcan aggregate the services accessed from multiple ports to one UNI port or aggregate the servicesaccessed from multiple ports to an NNI port. In addition, the OptiX PTN equipment canaggregate the services carried by PWs of multiple NNI ports to one UNI port.

13.2 Configuration Flow for the E-AGGR ServiceConfiguring an E-AGGR service contains creating the network, and configuring the QoS policy,interfaces, control plane, MPLS tunnel, and E-AGGR service.

13.3 Operation Tasks for the E-AGGR ServiceOperation tasks for the E-AGGR service include creation of E-AGGR services and creation ofV-UNI groups.

13.4 Configuration Case of the E-AGGR ServiceA case is provided here to show the configuration of the E-AGGR service, and the configurationflow. The configuration case covers the service planning and configuration of the E-AGGRservice.

13.5 Parameter DescriptionThis section describes the parameters related to the E-AGGR service configuration.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 13 Configuring an E-AGGR Service


13-1

13.1 E-AGGR ServiceIn topology, the E-AGGR service is a multipoint-to-point service. The OptiX PTN equipmentcan aggregate the services accessed from multiple ports to one UNI port or aggregate the servicesaccessed from multiple ports to an NNI port. In addition, the OptiX PTN equipment canaggregate the services carried by PWs of multiple NNI ports to one UNI port.

Figure 13-1 shows the networking diagram for the E-AGGR service.

One operator wants to construct a 3G network. Services of each Node B are aggregated andtransmitted to the RNC. At each station, the service of Node B that is connected to the stationis aggregated to the PW at the network side. The Tunnel that aggregates the Node B service withmultiple stations is aggregated again at the station that connects the RNC, and then the serviceis transmitted to the RNC.

Figure 13-1 E-AGGR service

RNC

NE 1

FE

GE

MPLS Tunnel 1

MPLS Tunnel 2

FE

FE

FE

Node B

NE 2

NE 3

13.2 Configuration Flow for the E-AGGR ServiceConfiguring an E-AGGR service contains creating the network, and configuring the QoS policy,interfaces, control plane, MPLS tunnel, and E-AGGR service.

Figure 13-2 shows the flow for configuring an E-AGGR service.

13 Configuring an E-AGGR ServiceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

Figure 13-2 Configuration flow for the E-AGGR service

Creating Network


Configuring the Control Plane


StartRequired

Optional

End

Configuring an MPLS Tunnel


Configuring a UNIs-NNI E-AGGR Service for NEs

Configuring a NNIs-UNI E-AGGR Service for NEs

End


Configuring a UNIs-NNI E-AGGR Service for NEs

Configuring a NNIs-UNI E-AGGR Service for NEs

End


Configuring a UNIs-UNI E-AGGR Service for NEs

The columns in the figure shows the three sub processes, which are for the configuration of aUNI-UNI E-AGGR service, the configuration of an E-AGGR service carried by ports on theNNI side, and the configuration of an E-AGGR service carried by PWs on the NNI side fromthe left to right.

For network creation, see 2 Creating Network.

For the QoS policy configuration, see QoS of Feature Description.

For the interface configuration, see 4.3 Configuring Ethernet Interfaces.

For the control plane configuration, see 5 Configuring the Control Plane. When the staticMPLS tunnel is used to carry the Ethernet service, this step can be skipped, because the staticMPLS tunnel does not need the configuration of the control plane.

When the MPLS tunnel is configured, see the following contents according to the MPLS tunneltype.

l When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NEbasis or by using the trail function. See 6.3 Creating a Static MPLS Tunnel by Using theTrail Function and 6.5 Creating an MPLS Tunnel on a Per-NE Basis.



13-3

l When the dynamic MPLS tunnel is used, see 6.2 Creating a Dynamic MPLS Tunnel andthe FRR Protection by Using the Trail Function.

When configuring the E-AGGR service, see 13.4 Configuration Case of the E-AGGRService.

13.3 Operation Tasks for the E-AGGR ServiceOperation tasks for the E-AGGR service include creation of E-AGGR services and creation ofV-UNI groups.

13.3.1 Creating an E-AGGR ServiceOn the T2000, the creation of an E-AGGR service can be complete in one interface. Theequipment supports the multipoint-to-point service aggregation, and supports the serviceaggregation from the NNI carried by multiple PWs to one UNI port.


13.3.1 Creating an E-AGGR ServiceOn the T2000, the creation of an E-AGGR service can be complete in one interface. Theequipment supports the multipoint-to-point service aggregation, and supports the serviceaggregation from the NNI carried by multiple PWs to one UNI port.

Prerequisite


You must complete the correct configuration of port attributes.

You must complete the creation of the MPLS tunnel that carries the PW.

If a port need be exclusively used, disable the DCN function of the port that carries the service.For detail, see Enabling the Port DCN.

Procedure

Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management> E-AGGR Service from the Function Tree.

Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID,Service Name and MTU(byte).For details on the parameters for E-AGGR service, see Table13-7.

Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.Fordetails on the parameters for UNI ports of E-AGGR service, see Table 12-5.

Step 4 In the Available Port list, select the desired port and click to add the port to theSelected Port list.


Configuration Guide


Issue 06 (2009-06-01)

NOTE

The port of the E-AGGR service does not support the S-Aware attribute.

Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.

NOTE

Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sinkend can be set. Otherwise, the E-AGGR service cannot be correctly configured.

Step 6 Click the NNI tab.l To configure the NNI interface carried by the port, click the Port tab. When adding and

setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.For details on theparameters for NNI ports of E-AGGR service, see Table 12-6.

l To configure the NNI interface carried by the PW, click the PW tab. Click New to setrelated parameters of the PW. Then, click OK.For details on the parameters for PW of E-AGGR service, see Table 12-7.

NOTE

l For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is usedto create a PW.

l For PW Type, select Ethernet or Ethernet Tagged Mode.

Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN ForwardingTable Item window to set the forwarding attributes. Then, click OK.For details on theparameters for VLAN forwarding tables of E-AGGR service, see Table 13-6.

NOTE

The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLANForwarding Table Item from each source interface to sink interface.

Step 8 Click OK to display the confirmation dialog box. Then, close the dialog box.

Step 9 Optional: Click QoS tab. Set the parameters of the QoS.For details on the parameters for QoSof E-AGGR service, see Table 12-12.l Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling

Color.l Click the PW tab to set EXP and LSP Mode.

NOTE

If Bandwidth Limit is set to enabled, CIR (kbit/s) and PIR (kbit/s) can be set. The QoS policy can alsobe selected from Policy.



13-5

Step 10 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-relatedparameters.For details on the parameters for maintenance association of the E-LAN service, seeTable 12-13.For details on the parameters for MEP point of the E-LAN service, see Table12-14.

NOTE


----End





Procedure





Configuration Guide


Issue 06 (2009-06-01)


NOTE

The interfaces on the same interface board can be configured into the same V-UNI group.

The former eight interfaces on the EG16 can be configured into the same V-UNI group, and the latter eightinterfaces can be configured into the same V-UNI group.


----End

13.4 Configuration Case of the E-AGGR ServiceA case is provided here to show the configuration of the E-AGGR service, and the configurationflow. The configuration case covers the service planning and configuration of the E-AGGRservice.

13.4.1 Case DescriptionThe case description covers the functional requirements, networking diagram and serviceplanning.



13-7

13.4.2 Configuring a UNIs-NNI E-AGGR Service for NEsThe E-AGGR service is accessed to the UNIs of multiple NEs and then aggregated at the NNI.This section describes how to configure the UNIs-NNI E-AGGR service for NEs.

13.4.3 Configuring an NNIs-UNI E-AGGR Service for NEsThe E-AGGR service is accessed to the NNIs of multiple NEs and then aggregated at the UNI.This section describes how to configure the NNIs-UNI E-AGGR service for NEs.

13.4.1 Case DescriptionThe case description covers the functional requirements, networking diagram and serviceplanning.

Networking and RequirementsAs shown in Figure 13-3, NE1 and Node B connected to NE2 need communicate with the RNCconnected to NE3. In this case, NE1 and NE2 can aggregate the services accessed from NodeB to two MPLS tunnels respectively. The two MPLS tunnel then transports the services to NE3,which then aggregates the services to the RNC. All services of Node B have VLAN, whose valueis 100.

Node B is connected to the equipment through the FE interface. RNC is connected to theequipment through the GE interface. The NEs are connected through the STM-4 POS interfacesfor networking.

Services on NodeB 1 are audio services (CIR = 15 Mbit/s, PIR = 30 Mbit/s).

Services on NodeB 2 are data services (CIR = 30 Mbit/s, PIR = 50 Mbit/s).

Services on NodeB 3 are audio services (CIR = 15 Mbit/s, PIR = 30 Mbit/s).

Services on NodeB 4 are data services (CIR = 30 Mbit/s, PIR = 50 Mbit/s).


Configuration Guide


Issue 06 (2009-06-01)

Figure 13-3 E-AGGR service networking diagram

RNC

NE 1

GE

MPLS Tunnel 1

MPLS Tunnel 2

Node B

NE 2

NE 3

UNI for NodeB 3:1-EG16-19-ETFC-1

Node B 2

Node B 4

Node B 3

UNI for NodeB 4:1-EG16-19-ETFC-2

UNI for NodeB 1:1-EG16-19-ETFC-1UNI for NodeB 2:1-EG16-19-ETFC-2NNI:1-EG16-20-POD41-1

NNI:1-EG16-20-POD41-1

UNI for RNC:1-EG16-1NNI for NE 1:1-EG16-20-POD41-1NNI for NE 2:1-EG16-20-POD41-2

Node B 1

Service Planning

Services are carried by the PW in the network. Configure related parameters of the PW andMPLS tunnel. In this case, a dynamic tunnel is quickly created by trail.

Table 13-1 lists details on planning of the tunnel that carries the PW.

Table 13-1 Planning of the tunnel carrying the PW

Parameter PositiveTunnel 1

ReverseTunnel 1

PositiveTunnel 2

ReverseTunnel 2

Tunnel ID 1 2 3 4

Tunnel Name E-AGGR E-AGGR E-AGGR E-AGGR

Signaling Type Dynamic Dynamic Dynamic Dynamic

Schedule Type E-LSP E-LSP E-LSP E-LSP

Bandwidth 45 Mbit/s 45 Mbit/s 45 Mbit/s 45 Mbit/s

Source NE NE1 NE3 NE2 NE3

Sink NE NE3 NE1 NE3 NE2



13-9

Parameter PositiveTunnel 1

ReverseTunnel 1

PositiveTunnel 2

ReverseTunnel 2

RouteConstraint PortIP Address

- - - -

Table 13-2 lists details on the planning of the Ethernet service.

Table 13-2 Planning of the E-AGGR service carried by the PW

Parameter NE1 NE2 NE3

Service ID 1 2 3

Service Name E-Aggr-1 E-Aggr-2 E-Aggr-3

MTU(byte) 1526 1526 1526

Table 13-3 lists details on planning of the PW at NNI.


Parameter NE1 NE2 NE3:NNI for NE1

NE3:NNI for NE2

Location Sink Sink Source Source

PW ID 10 20 10 20

PW SignalingType

Static Static Static Static

PW Type Ethernet Mode Ethernet Mode Ethernet Mode Ethernet Mode

Direction Bidirectional Bidirectional Bidirectional Bidirectional

PW IngressLabel

20 30 20 30

PW EgressLabel

20 30 20 30

Peer IP 1.1.1.3 1.1.1.3 1.1.1.1 1.1.1.2

Tunnel Tunnel 1 Tunnel 2 Tunnel 1 Tunnel 2

BandwidthLimit

Enabled Enabled Enabled Enabled

CIR (kbit/s) 45000 45000 45000 45000


Configuration Guide


Issue 06 (2009-06-01)

Parameter NE1 NE2 NE3:NNI for NE1

NE3:NNI for NE2

PIR (kbit/s) 80000 80000 80000 80000

Table 13-4 and Table 13-5 lists details on the planning of the VLAN forwarding table of eachNE.

Table 13-4 Planning of the VLAN forwarding tables of NE1 and NE2

Parameter NE1 NE2

Source InterfaceType

V-UNI V-UNI V-UNI V-UNI

Source Interface 1-EG16-19-ETFC-1

1-EG16-19-ETFC-2

1-EG16-19-ETFC-1

1-EG16-19-ETFC-2

Source VLANID

100 100 100 100

Sink InterfaceType

V-NNI V-NNI V-NNI V-NNI

Sink Interface 1-EG16-20-POD41-1

1-EG16-20-POD41-1

1-EG16-20-POD41-1

1-EG16-20-POD41-1

Sink VLAN ID 1 2 3 4

Table 13-5 Planning of the VLAN forwarding table of NE3

Parameter NE3: NNI for NE1 NE3: NNI for NE2


V-NNI V-NNI V-NNI V-NNI

Source Interface 1-EG16-20-POD41-1

1-EG16-20-POD41-1

1-EG16-20-POD41-2

1-EG16-20-POD41-2

Source VLANID

1 2 3 4

Sink InterfaceType

V-UNI V-UNI V-UNI V-UNI

Sink Interface 1-EG16-1 1-EG16-1 1-EG16-1 1-EG16-1

Sink VLAN ID 100 200 300 400



13-11

13.4.2 Configuring a UNIs-NNI E-AGGR Service for NEsThe E-AGGR service is accessed to the UNIs of multiple NEs and then aggregated at the NNI.This section describes how to configure the UNIs-NNI E-AGGR service for NEs.


Procedure

Step 1 On the T2000, configure a UNIs-NNI E-AGGR service for NE1. For details, see 13.3.1 Creatingan E-AGGR Service.Parameters related to the UNIs-NNI E-AGGR service are as follows.l UNI:

– Selected Port: 1-EG16-19-ETFC-1 and 1-EG16-19-ETFC-2

– VLANs: 100

l PW parameters of the NNI:– Location: Sink

– PW ID: 10


– PW Type: Ethernet Mode




– Peer IP: 1.1.1.3

– Bandwidth Limit: Enabled

– CIR (kbit/s): 45000

– PIR (kbit/s): 80000

l For details on parameters in the VLAN forwarding table, see Table 13-4.

Step 2 On the T2000, configure a UNIs-NNI E-AGGR service for NE2. For details, see 13.3.1 Creatingan E-AGGR Service.Parameters related to the UNIs-NNI E-AGGR service are as follows.l UNI:

– Selected Port: 1-EG16-19-ETFC-1 and 1-EG16-19-ETFC-2

– VLANs: 100

l PW parameters of the NNI:– Location: Sink

– PW ID: 2





Configuration Guide


Issue 06 (2009-06-01)



– Peer IP: 1.1.1.3


– CIR (kbit/s): 45000

– PIR (kbit/s): 80000


----End

13.4.3 Configuring an NNIs-UNI E-AGGR Service for NEsThe E-AGGR service is accessed to the NNIs of multiple NEs and then aggregated at the UNI.This section describes how to configure the NNIs-UNI E-AGGR service for NEs.


ProcedureOn the T2000, configure an NNIs-UNI E-AGGR service for NE3. For details, see 13.3.1Creating an E-AGGR Service.Parameters related to the NNIs-UNI E-AGGR service are as follows:l UNI:

– Selected Port: 1-EG16-1

– VLANs: 100, 200, 300, 400

l PW1 parameters of the NNI:– Location: Source

– PW ID: 10






– Peer IP: 1.1.1.1


– CIR (kbit/s): 45000

– PIR (kbit/s): 80000

l PW2 parameters of the NNI:– Location: Source

– PW ID: 20




13-13





– Peer IP: 1.1.1.2


– CIR (kbit/s): 45000

– PIR (kbit/s): 80000


----End

13.5 Parameter DescriptionThis section describes the parameters related to the E-AGGR service configuration.

Table 13-6 Descriptions of the parameters for VLAN Forwarding Table Item



V-UNI, V-NNI Select and query the type of the source interface.Click C.146 Source Interface Type for moreinformation.

Source Interface Example: [Port]11-EG16-1(Port-1)

Select and query the source interface. If SourceInterface Type is set to V-NNI, the sinkinterface can be a port or PW.

Source VLANID

1-4094 Set and query the source VLAN ID.

Sink InterfaceType

V-UNI, V-NNI Select and query the type of the sink interface.Click C.125 Sink Interface Type for moreinformation.

Sink Interface Example: [Port]11-EG16-2(Port-2)

Select and query the sink interface. If SinkInterface Type is set to V-NNI, the sinkinterface can be a port or PW.

Sink VLAN ID 1-4094 Set and query the sink VLAN ID.

Table 13-7 Descriptions of the parameters for E-AGGR Service





Configuration Guide


Issue 06 (2009-06-01)


MTU (byte) 46 to 9000Default: 1500

Set the maximum transport unit (MTU). Whenreceiving packets of a length more than theMTU, the port divides the packets into segmentsand then transport these segments. If the packetscontain a flag indicating that packet division isnot allowed, the port discards the packet.Click C.21 MTU(byte) for more information.

Service TagRole

User Display the service tag role of E-AGGR service.



13-15

14 Configuring Services for the OffloadSolution

About This Chapter

To provide high speed downlink packet access (HSDPA) services in a mobile communicationnetwork, the offload solution can be used to transmit data services through a xDSL wholesalemanaged service (WMS) network. In this way, the transmission cost is reduced.

14.1 Basic ConceptsThis section describes the three offload solutions, that is, ATM-based solution, ETH-basedsolution, and IP-based solution. In addition, this section covers the packet encapsulation formatand signal flow.

14.2 Service Configuration Flow for the Offload SolutionThis section describes the operational tasks for configuring services in the offload scenario andthe sequence in performing these tasks. When configuring or management services in the offloadscenario, see this section.

14.3 ATM-Based Service Configuration CaseThis section describes the offload solution for the case where ATM-based services traverse thewholesale ADSL network.

14.4 ETH-Based Service Configuration CaseThis section describes the offload solution for the case where ETH-based services traverse thewholesale ADSL network.

14.5 IP-Based Service Configuration CaseThis section describes the offload solution for the case where IP-based services traverse thewholesale ADSL network.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 14 Configuring Services for the Offload Solution


14-1

14.1 Basic ConceptsThis section describes the three offload solutions, that is, ATM-based solution, ETH-basedsolution, and IP-based solution. In addition, this section covers the packet encapsulation formatand signal flow.

Offload SolutionIn the mobile backhaul domain, there is one application scenario called offload. In the case ofoffload, the base station shunts the accessed service flow. The traditional audio service, such asthe 2G or 3G R99 CS service, is transported over the E1 private line. In this way, high QoS, lowdelay, and high reliability are achieved. In the case of the packet service that requires highbandwidth but no delay guarantee, such as the high speed downlink packet access (HSDPA)service, the ADSL-based mode is adopted for backhaul. For example, the ADSL wholesalemanaged service (WMS) is applicable. The ADSL network provides high bandwidth and costslittle. Hence, the ADSL network is well applicable to the packet service such as the HSDPAservice.

Generally, the PDH/SDH microwave is used or the TDM E1 private line is leased from the fixednetwork operator to transmit the backhaul service between the base station and base stationcontroller (BSC). This is the reason why the Offload solution is adopted. With servicedevelopment, the base station backhaul requires increasing bandwidth and the traditional audioservice takes a decreasing proportion. In this case, it is not economical to lease more E1 linksto increase the backhaul bandwidth, because the E1 links cost much.

The offload solution is applicable to transmission of the ATM services, CES services, andEthernet services.

Figure 14-1 shows a typical scenario where the offload solution is applied. Node B connects tothe OptiX PTN 1900 through the ATM IMA interface. The IMA E1 module of the OptiX PTN1900 accesses the services and distinguishes various service flows according to the VPI/VCIvalues carried by the packets.

l In the case of the HSDPA service flow, the OptiX PTN 1900 emulates the ATM PWE3 forthe service flow on the access side and then encapsulates the emulated service into thetunnel as required by the WMS network. Finally, the OptiX PTN 1900 transports the serviceto the ADSL modem through the FE interface. When the encapsulated service enters theADSL network, the service is transported to the OptiX PTN 3900. Then, the OptiX PTN3900 decapsulates the service and transports the service to the radio network controller(RNC).

l The OptiX PTN 1900 at the access station transports the signaling flow and R99 serviceflow in the form of IMA E1 to the OptiX PTN 3900 at the convergence station.

14 Configuring Services for the Offload SolutionOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

Figure 14-1 Offload solution

IMA

HSDPAflow

R99 flowNode B

Wholesale ADSLservice

ADSLmodem

OptiX PTN1900 OptiX PTN

3900RNC

DSLAM

Backhaulnetwork

ATMSTM-1

In the Wholesale ADSL network, packets are transported in three modes, that is, ATM-basedforward, ETH-based forward, and IP-based forward.

ATM-Based Services for the Offload SolutionFigure 14-2 shows the offload scenario for the ATM-based service.

Figure 14-2 Offload scenario for the ATM-based service

IMA

HSDPAflow

R99 flowNode B


ADSLmodem


3900RNC

DSLAM

PTN

ATMSTM-1

ATM ATMPWE3

PW LabelLSP LabelEthernet

ATMPWE3


AAL5ATMADSL

ATMPWE3


AAL5ATM

STM-1

ATMPWE3


AAL5ATM

STM-1

ATM

ATM based

E1 STM-1

In the application scenario for ATM-based forward services, the WMS works as an ATM switchnetwork. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets. Then, theADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, the DSLAMterminates the ADSL and transports the encapsulated ATM packets into the ATM switch



14-3

network. The OptiX PTN 3900 terminates the AAL5 layer, recovers the Ethernet packets, anddecapsulates the packets to obtain ATM packets.

ETH-Based Services for the Offload SolutionFigure 14-3 shows the offload scenario for the ETH-based forward service.

Figure 14-3 Offload scenario for the ETH-based service

IMA

HSDPAflow

R99 flowNode B


ADSLmodem


3900RNC

DSLAM

PTN

ATMSTM-1

ATM ATMPWE3


ATMPWE3


AAL5ATMADSL

ATMPWE3


ATMPWE3


ATM

Eth based

E1 STM-1

In the application scenario for ETH-based forward services, the WMS works as a Layer 2 ETHswitch network. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets.Then, the ADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, theDSLAM terminates the ADSL and ATM, and transports the encapsulated ATM packets into theLayer 2 ETH switch network. The OptiX PTN 3900 receives Ethernet packets and decapsulatesthe Ethernet packets to obtain ATM packets.

IP-Based Services for the Offload SolutionFigure 14-4 shows the offload scenario for the IP-based forward service.


Configuration Guide


Issue 06 (2009-06-01)

Figure 14-4 Offload scenario for the IP-Based services

IMA

HSDPAflow

R99 flowNode B


ADSLmodem


3900RNC

DSLAM

PTN

ATMSTM-1

ATM ATMPWE3

PW LabelGRE

IP

ATMPWE3

PW Label

AAL5ATMADSL

ATMPWE3

PW Label

IPEthernet

ATMPWE3

PW Label

IPEthernet

ATM

IP based

Ethernet

GREIP

Ethernet

GRE GRE

E1 STM-1

In the application scenario for IP-based forward services, the WMS works as an IP switchnetwork. The OptiX PTN 1900 encapsulates the ATM packets into Ethernet packets. Then, theADSL modem performs the AAL5 adaptation and ATM encapsulation. Finally, the DSLAMterminates the ADSL and ATM, and forwards (Layer 3) the packets to the OptiX PTN 3900.The OptiX PTN 3900 receives Ethernet packets and decapsulates the Ethernet packets to obtainATM packets. In this scenario, an IP/GRE tunnel should be set up between the OptiX PTN 1900and OptiX PTN 3900 to carry the PW.

In this figure, IP in the packet encapsulation format indicates that the packets are carried by theIP tunnel. In the case of PW carrying over the GRE tunnel, IP is replaced with GRE.

14.2 Service Configuration Flow for the Offload SolutionThis section describes the operational tasks for configuring services in the offload scenario andthe sequence in performing these tasks. When configuring or management services in the offloadscenario, see this section.

Figure 14-5, Figure 14-6, Figure 14-7 show the configuration flow of services in the offloadsolution. For details of each step, see the related section.



14-5

Figure 14-5 Configuration flow of the ATM-based service in the offload solution

Creat the network

Create MPLS/IP/GRE tunnel

Create the ATM policy

StartRequired

Optional

Configure the interface

End

Creat the IMA group

Create the ATM service

Create the ATM connection



Configuration Guide


Issue 06 (2009-06-01)

Figure 14-6 Configuration flow of the ETH-based service in the offload solution

Creat the network

Create MPLS/IP/GRE tunnel

Configure the QoS policy

StartRequired

Optional


End

Create the service




14-7

Figure 14-7 Configuration flow of the IP-based service in the offload solution

Creat the network

Create IP/GRE tunnel

Create the service

StartRequired

Optional


End

Configure the QoS policy

Create the static ARP table entry

Create the static route

14.3 ATM-Based Service Configuration CaseThis section describes the offload solution for the case where ATM-based services traverse thewholesale ADSL network.

14.3.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the ATM.

14.3.2 Configuration ProcessThis section describes the configuration process of the Offload application in an ATM-forwarding-based network.


Configuration Guide


Issue 06 (2009-06-01)

14.3.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the ATM.

Networking and RequirementTwo Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two NodeBs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end throughthe network. Services of Node B include the R99 voice service and high speed downlink packetaccess (HSDPA) service. The voice service, which is carried by the backhaul networkconstructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidthguarantee. The HSDPA service does not require low delay, but it only requires bandwidthguarantee. Hence, the ATM network of a third party operator is leased.

The OptiX PTN 1900 differentiates services according to the VPI and VCI values, and thendistributes the services to two different routes for transmission.

l HSDPA service: The HSDPA service is converged to the DSLAM equipment through theADSL modem, and then it enters the leased ATM network of the third party operator fortransmission. The HSDPA service requires only bandwidth guarantee, and thus the leasecost is low.

l R99 voice service: The R99 voice service is transported through the backhaul network. Theequipment in the network is the OptiX PTN equipment series. The R99 voice servicerequires QoS guarantee, low delay and bandwidth guarantee.

Figure 14-8 shows the networking diagram.

l HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the servicewith a VPI/VCI value of 1/101, and then transport the service to the FE interface of theETFC. After added with a new VPI/VCI through the ADSL modem, the service istransported to the OptiX PTN 3900 through the ATM network. The OptiX PTN 3900rearranges the service and then converges the service to the ATM STM-1 interface. Then,the service is transported to RNC. MPLS Tunnel 1 is set up between the OptiX PTN 1900and OptiX PTN 3900 for carrying the service. Figure 14-8 shows the encapsulation formatof packets at the interface of each equipment. The red lines indicate the VPI/VCI values atATM layers in the packets.

l R99 voice service: On the OptiX PTN 1900, perform the VPI/VCI switching on the servicewith a VPI/VCI value of 1/100, and then transport the service to the POS interface of thePOD41. The service is carried by MPLS Tunnel 2, and then is transported to the OptiXPTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service tothe ATM STM-1 interface. Then, the service is transported to RNC.



14-9

Figure 14-8 Networking diagram of the offload application scenario based on the ATMforwarding and packet encapsulation format

HSDPA flow

R99 flow

Node B 1

Wholesale ADSL service

RNC

PTN

ATM STM-1

Node B 2

CXP-1-MD1-3-L75:1-4

CXP-1-MD1-3-L75:5-8

4-POD41-1

7-ETFC-1

46/8046/81

1/1001/101

1/1001/101

56/8056/81

1-EG16-19-POD41-1

3-MP1-ASD1-14-MP1-AD1-1

MPLS Tunnel 2MPLS Tunnel 1

OptiX PTN 3900OptiX PTN 1900

ATM ATMPWE3


ATMPWE3


AAL5ATMADSL

ATMPWE3


AAL5ATM

STM-1

ATMPWE3


AAL5ATM

STM-1

ATM

ADSL modem

DSLAM46/8046/8156/8056/81

20/40

20/40

56/8056/81

E1 STM-1

The ADSL modem can work in the bridge or router mode.

l When the ADSL modem works in the bridge mode, the ADSL modem performs the EoAencapsulation on the accessed FE signals. The access node uses the MPLS tunnel or IPtunnel.

l When the ADSL modem works in the router mode, the ADSL modem performs the IPoAencapsulation on the accessed FE signals. The access node uses the IP tunnel or GRE tunnel.

In this example, the OptiX PTN 1900 uses the MPLS tunnel, and the ADSL modem works inthe bridge mode. If the ADSL modem works in the router mode, the configuration method isthe same. The difference is that the IP tunnel or GRE tunnel, instead of the MPLS tunnel, is usedto carry the HSDPA service.

NOTE

The ASD1 supports four AAL5 encapsulation types, that is, LLC bridge, LLC route, VCMUX bridge andVCMUX route. In the actual application, the encapsulation type should be consistent with the workingmode of the ADSL Modem.

Service PlanningThe offload is a solution instead of a service or feature. Hence, according to the user requirementand networking diagram of this example, this example uses the offload solution to perform thefollowing tasks.


Configuration Guide


Issue 06 (2009-06-01)

1. Configure the member interfaces and create the IMA group.On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of twoNode Bs.

2. Create the Ethernet virtual interface.On the OptiX PTN 3900, set the interface of the ASD1 to the Ethernet virtual interface, setthe port mode to Layer 3. In addition, the setting of the AAL5 encapsulation type shouldbe consistent with the working mode of the ADSL modem. After the Ethernet virtualinterface is created, the ATM interface of the ASD1 can be carried in the tunnel on thenetwork side.

3. Create MPLS tunnel 1.This tunnel is used for carrying the HSDPA service. Normally, the static MPLS tunnel iscreated on the OptiX PTN 1900 and OptiX PTN 3900, because the network is a leasednetwork of the third party operator.

4. Create MPLS tunnel 2.This tunnel is used for carrying the R99 voice service, which resides on the POS interfacesof the OptiX PTN 1900 and OptiX PTN 3900.

5. Create the ATM policy (CBR and UBR).Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 andOptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voiceservice, and UBR is used for the HSDPA service.

6. Create the ATM service.l On the OptiX PTN 1900, create two ATM services, and access the services of Node B.

l On the OptiX PTN 3900, create two ATM services, and access the services of RNC.

7. Create the ATM connection.l On the OptiX PTN 1900, create two ATM connections in each ATM service, and

encapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent MPLS tunnels for carrying the services.

l On the OptiX PTN 3900, create two ATM connections in each ATM service, andencapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent MPLS tunnels for carrying the services.

NOTE

In the leased network of the third party operator, the services are configured by the third party operator.

The parameter planning is as follows:

Table 14-1 lists the planning of the voice service and data service in the network.



14-11

Table 14-1 VPI/VCI values of the Node B service

Service ServiceBandwidth

User-SideVPI/VCIValue

Network-Side VPI/VCI Value

VPI/VCIValueAdded atthe ATMLayerAfter theAAL5Adaptation

VPI/VCIValue onthe RNCSide

R99 voice serviceof Node B 1

2 Mbit/s 1/100 56/80 - 56/80

HSDPA service ofNode B 1

5 Mbit/s 1/101 46/80 20/40 46/80


2 Mbit/s 1/100 56/81 - 56/81


5 Mbit/s 1/101 46/81 20/40 46/81

Table 14-2 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMA groupsto access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1-AD1-1 toRNC.

Table 14-2 Planning of the UNIs

Equipment Interface Binding Interface Interface Attribute

OptiX PTN 1900:1-MD1-1(Trunk-1)

3-L75-1 to 3-L75-4 The port mode of the PDH interface isset to Layer 2, and the encapsulationtype is ATM by default.



OptiX PTN 3900:4-MP1-AD1-1

- The port mode of the SDH interface isset to Layer 2, and the encapsulationtype is ATM by default.

Table 14-3 lists the planning of the NNIs.


Configuration Guide


Issue 06 (2009-06-01)

Table 14-3 Planning of the NNIs

EquipmentInterface

InterfaceType

Port Mode IP Addressand SubnetMask of theInterface

VPI/VCIValue (Onlyfor the EOAVirtualInterface)

OptiX PTN1900:7-ETFC-1

Ethernetinterface

Layer 3 192.168.1.5/30 -

OptiX PTN3900:3-MP1-ASD1-1

EOA virtualinterface

Layer 3 192.168.1.6/30 20/40

OptiX PTN1900:4-POD41-1

SDH interface Layer 3 192.168.2.5/30(In the backhaulnetwork, the IPaddress andmask of theinterface of theOptiX PTNequipmentinterconnectedto this SDHinterface is192.168.2.6/30.)

-



-

NOTE

ADSL The modem performs the AAL5 adaptation on the accessed services, and then adds a VPI/VCI tothe services. The VPI/VCI value for the Ethernet EOA virtual interface should be consistent with thepreceding VPI/VCI value.

Table 14-4 and Table 14-5 list the planning of the MPLS tunnel and related PW.



14-13

Table 14-4 Planning of the MPLS tunnel

MPLSTunnel

MPLSTunnel ID

Interface ofthe TunnelCarried bythe OptiXPTN 1900


MPLSTunnelType

TunnelBandwidth

MPLSTunnel 1

Forward: 50Reverse: 51

7-ETFC Ethernetvirtualinterface: 3-MP1-ASD1-1

Static Norestriction

MPLSTunnel 2

Dynamicdistribution

4-POD41-1 19-POD41-1 Dynamic Norestriction

NOTE

If the type of the MPLS tunnel 1 is static, manually specify the IP address of the next hop and the IPaddresses of the source and sink nodes.

If the type of the MPLS tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnelpasses through the specified interfaces.


PW

PWSignalingType

PWType

PWLabel

OppositeIPAddress

Max.Concatenated CellCount

PacketisationBufferingTime(us)

QoS Policy of theATM Connection

PW1

Static ATM nto oneVCCcelltransport

100 OptiX PTN1900:192.168.1.6OptiX PTN3900:192.168.1.5

10 1000 Service Type: UBRTraffic Type:NoTrafficDescriptor

PW2

Dynamic

ATM nto oneVCCcelltransport

Dynamicdistribution

OptiX PTN1900:192.168.10.6OptiX PTN3900:192.168.2.5

1 0 Service Type: CBR.Traffic Type:NoClpNoScrClp01Pcr(cell/s):10000

Table 14-6 and Table 14-7 list the planning of the ATM services on the OptiX PTN 1900 andOptiX PTN 3900.


Configuration Guide


Issue 06 (2009-06-01)

Table 14-6 Planning of the ATM service on the OptiX PTN 1900

Attribute ATM Service 1 ATM Service 2

Node B of theService

Node B 1 Node B 2 Node B 1 Node B 2

Source Port 1-MD1-1(Trunk-1)

1-MD1-2(Trunk-2)

1-MD1-1(Trunk-1)

1-MD1-2(Trunk-2)

ATMConnection(Two ATMConnections forEach ATMService)

HSDPA 1 HSDPA 2 R99 1 R99 2

Source VPI/VCI

1/101 1/101 1/100 1/100

Sink VPI/VCI 46/80 46/81 56/80 56/81

PW Carryingthe Service

PW1 PW1 PW2 PW2

TunnelCarrying thePW

MPLS Tunnel 1 MPLS Tunnel 1 MPLS Tunnel 2 MPLS Tunnel 2

Uplink Policy UBR UBR CBR CBR

DownlinkPolicy

UBR UBR CBR CBR



Source Port 4-MP1-AD1-1



Source VPI/VCI

46/80 46/81 56/80 56/81

Sink VPI/VCI 46/80 46/81 56/80 56/81


PW1 PW1 PW2 PW2



14-15





DownlinkPolicy

UBR UBR CBR CBR

14.3.2 Configuration ProcessThis section describes the configuration process of the Offload application in an ATM-forwarding-based network.


l You must know the networking and data planning of this case.

l Because the Offload solution involves configuration of many operation tasks, you aresupposed to learn how to configure interfaces and tunnels, how to create the QoS policy,and how to configure ATM services before the configuration.

Procedure

Step 1 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > InterfaceManagement > PDH Interface. Set Port Mode to Layer 2 and Encapsulation Type toATM for eight interfaces ranging from 3-L75-1 to 3-L75-8.

Step 2 Choose Configuration > Interface Management > ATM IMA Management , and click theBinding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3-L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively.

Step 3 Choose IMA Group Management. Then, set IMA Protocol Enable Status to Enabled for 1-CXP-1-MD1-1(Trunk-1) and 1-CXP-1-MD1-2(Trunk-2).

Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > InterfaceManagement > Ethernet Virtual Interface. Click New, set 3-MP1-ASD1-1 to EOA VirtualInterface in the Create Ethernet Virtual Interface dialog box. Then, set the parameters asfollows:l Basic attributes

– Set Port Mode to Layer 3.

– Set AAL5 Encapsulation Type to LLC BRIDGE.

– Set VPI to 20.

– Set VCI to 40.

l Layer 3 attributes– Set IP Address to 192.168.1.6.


Configuration Guide


Issue 06 (2009-06-01)

– Set IP Mask to 255.255.255.252.

– Set Enable Tunnel to Enabled.

NOTE

The AAL5 encapsulation type should be consistent with the working mode of the ADSL modem.

Step 5 Choose Configuration > Interface Management > SDH Interface . Set 19-POD41-1 as annetwork-side interface. Then, set the parameters as follows:l Basic attributes

– Set Encapsulation Type to PPP.

– Use the default values for other parameters.

l Layer 3 attributes– Set Enable Tunnel to Enabled.

– Set Specify IP to Manually.

– Set IP Address to 192.168.10.6.

– Set IP Mask to 255.255.255.252.

Step 6 In the NE Explorer, select OptiX PTN 1900. Choose Configuration > InterfaceManagement > Ethernet Interface. Set 7-ETFC-1 as an network-side interface. Then, set theparameters as follows:l Basic attributes





14-17




– Set IP Mask to 255.255.255.252.

Step 7 Choose Configuration > Interface Management > SDH Interface . Set 4-POD41-1 as annetwork-side interface. Then, set the parameters as follows:l Basic attributes






– Set IP Mask to 255.255.255.252.

Step 8 Create MPLS tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the typeof the tunnel is Static, you need to create a static MPLS tunnel on the OptiX PTN 1900 andOptiX PTN 3900 respectively. For the method of creating the tunnel in this case, see 6.5 Creatingan MPLS Tunnel on a Per-NE Basis.

Step 9 Create MPLS tunnel 2 between the OptiX PTN 1900 and OptiX PTN 3900. You can dynamicallycreate the MPLS tunnel because tunnel 2 passes the PTN equipment. Set attributes of eachinterface of the NEs involved properly before the creation. For the method of the tunnel in thiscase, see 6.2 Creating a Dynamic MPLS Tunnel and the FRR Protection by Using the TrailFunction.

Step 10 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NEExplorer, choose Configuration > QoS Management > Policy Management. Then, selectATM Policy and click New.l The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent.

l In the case of the CBR policy, set the parameters as follows:– Set Service Type to CBR.

– Set Traffic Type to NoClpNoScr.

– Set Clp01Pcr(cell/s) to 10000.

l In the case of the UBR policy, set the parameters as follows:– Set Service Type to UBR.

– Set Traffic Type to NoTrafficDescriptor.

Step 11 Create ATM service 1 on the OptiX PTN 1900. Create two ATM connections in ATM service1. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/101to respectively 46/80 and 46/81, encapsulate the services, and then send the services to MPLStunnel 1 carried by the 7-ETFC-1 interface. In the NE Explorer, choose Configuration > ATMService Management. Click the Connection tab, and click New. Set the parameters as follows:l Set Service Type to UNIs-NNI.


Configuration Guide


Issue 06 (2009-06-01)

l Set Connection Type to PVC.

l Set the parameters for connection 1 as follows:– Set Source Board to 1-CXP.

– Set Source Port to 1-MD1-1(Trunk-1).– Set Source VPI to 1.

– Set Source VCI to 101.

– Set Sink VPI to 46.

– Set Sink VCI to 80.

– Set Uplink Policy and Downlink Policy to the created UBR policy.


– Set Source Port to 1-MD1-2(Trunk-2).– Set Source VPI to 1.





l Setting the parameters of PW1 as follows:General Attributes:– Set PW ID to 1.

– Set PW Signaling Type to Static.

– Set PW Type to ATM n-to-one VCC cell transport.– Set PW Ingress Label and PW Egress Label to 100.

– Set Peer IP to 192.168.1.6.

– Set Tunnel Type to MPLS.

– Set Tunnel to created MPLS Tunnel 1.

– Set Max. Concatenated Cell Count to 10.

– Set Packet Loading Time(us) to 1000.

QoS– Ingress


– CIR (kbit/s): 10240

– CBS (byte): -

– PIR (kbit/s): 15000

– PBS (byte): -

– Policy:

– EXP: 1

Advanced Attributes:– Control Word: Must use



14-19

– Control Channel Type: CW (CW realizes connectivity check of the PW.)

– VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.)

– Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can beencapsulated in each packet)


NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Modeneed be set according to the user requirements.

For detailed configuration steps, refer to 10.3.2 Creating ATM Services on a Per-NE Basis.

Step 12 Create ATM service 2 on the OptiX PTN 1900. Create two ATM connections in ATM service2. Change the VPI/VCI values of the two services accessed by the two IMA groups from 1/100to respectively 56/80 and 56/81, encapsulate the services, and then send the services to MPLStunnel 2 carried by the 4-POD41-1 interface.

For the configuration parameters, see the service planning in the case description. Set theparameters according to Step 11. In the case of PW2, PW Signaling Type should be set toDynamic. In addition, PW Ingress Label and PW Egress Label need not be set.

Step 13 Create ATM service 1 on the OptiX PTN 3900. Create two ATM connections in ATM service1. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values arerespectively 46/80 and 46/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 1carried by the Ethernet virtual interface on the network side.

For the configuration parameters, see the service planning in the case description. Set theparameters according to Step 11.

Step 14 Create ATM service 2 on the OptiX PTN 3900. Create two ATM connections in ATM service2. The VPI/VCI exchange need not be performed. Send the services whose VPI/VCI values arerespectively 56/80 and 56/81 and accessed by the 4-MP1-AD1-1 interface to MPLS tunnel 2carried by the POS interface on the network side.

For the configuration parameters, see the service planning in the case description. Set theparameters according to Step 11.In the case of PW2, PW Signaling Type should be set toDynamic. In addition, PW Ingress Label and PW Egress Label need not be set.

----End

14.4 ETH-Based Service Configuration CaseThis section describes the offload solution for the case where ETH-based services traverse thewholesale ADSL network.

14.4.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the ETH.

14.4.2 Configuration ProcessThis section describes the configuration process of the Offload application in an ETH-forwarding-based network.


Configuration Guide


Issue 06 (2009-06-01)

14.4.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the ETH.

Networking and RequirementTwo Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two NodeBs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end throughthe network. Services of Node B include the R99 voice service and high speed downlink packetaccess (HSDPA) service. The voice service, which is carried by the backhaul networkconstructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidthguarantee. The HSDPA service does not require low delay, but it only requires bandwidthguarantee. Hence, the Layer 2 switching network of a third party operator is leased.


l HSDPA service: The HSDPA service is converged to the DSLAM equipment through theADSL modem, and then it enters the leased ETH network of the third party operator fortransmission. The HSDPA service requires only bandwidth guarantee, and thus the leasecost is low.



l HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the servicewith a VPI/VCI value of 1/101, and then transport the service to the FE interface of theETFC. The ADSL modem completes the AAL5 adaptation and ATM encapsulation, andthe DSLAM removes the ADSL and ATM layers. Then, the Ethernet packets are sent tothe ETH switching network. The ETH switching network sends the service to the OptiXPTN 3900. The OptiX PTN 3900 rearranges the service and then converges the service tothe ATM STM-1 interface. Then, the service is transported to RNC. MPLS Tunnel 1 is setup between the OptiX PTN 1900 and OptiX PTN 3900 for carrying the service. Figure14-9 shows the encapsulation format of packets at the interface of each equipment. The redlines indicate the VPI/VCI values at ATM layers in the packets.




14-21

Figure 14-9 Networking diagram of the offload application scenario based on the ETHforwarding and packet encapsulation format

HSDPA flow

R99 flow

Node B 1


RNC

PTN

ATMSTM-1

Node B 2

CXP-1-MD1-3-L75:1-4

CXP-1-MD1-3-L75:5-8

4-POD41-1

7-ETFC-1

46/8046/81

1/1001/101

1/1001/101

56/8056/81

1-EG16-19-POD41-1

4-MP1-AD1-1

MPLS Tunnel 2MPLS Tunnel 1


ATM ATMPWE3


ATMPWE3


AAL5ATMADSL

ATMPWE3


ATMPWE3


ATM

ADSLmodem

DSLAM46/8046/8156/8056/81

20/30

56/8056/81

E1 STM-1

1-EG16-1


l When the ADSL modem works in the bridge mode, the ADSL modem performs the EoAencapsulation on the accessed FE signals. The OptiX PTN 1900 on the access node usesthe MPLS Tunnel or IP Tunnel.

l When the ADSL modem works in the router mode, the ADSL modem performs the IPoAencapsulation on the accessed FE signals. The OptiX PTN 1900 at the access node uses theIP Tunnel or GRE Tunnel.

In this example, the OptiX PTN 1900 uses the MPLS Tunnel, and the ADSL modem works inthe bridge mode. If the ADSL modem works in the router mode, the configuration method isthe same. The difference is that the IP Tunnel or GRE Tunnel, instead of the MPLS Tunnel, isused to carry the HSDPA service. When the IP Tunnel or GRE Tunnel is used, you shouldconfigure the static route and static ARP on the OptiX PTN 1900 and OptiX PTN 3900. If theequipment cannot dynamically obtain the ARP, the static ARP still needs to be configured.

Service PlanningThe offload is a solution instead of a service or feature. Hence, according to the user requirementand networking diagram of this example, this example uses the offload solution to perform thefollowing tasks.


Configuration Guide


Issue 06 (2009-06-01)

1. Create the IMA group and configure the member interfaces.On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of twoNode Bs.

2. Configure attributes of the NNI.After the NNI is configured, you can create the MPLS Tunnel on the OptiX PTN 1900 andOptiX PTN 3900.

3. Configure the control plane.l Before creating a dynamic tunnel, configure the IS-IS protocol and set the parameters

related to the RSPF protocol.l To create a dynamic tunnel, you need to configure a static ARP.

After the static ARP is configured, the equipment finds the corresponding MAC addressin the ARP table entry according to the destination IP address, and then writes the MACaddress as the destination MAC to the ETH layer of the packet. The Layer 2 switchingnetwork forwards the packet to the destination according to this MAC address. StaticMPLS Tunnel 1 should use this table entry.

4. Create MPLS tunnel 1.This tunnel is used for carrying the HSDPA service. Normally, the static MPLS tunnel iscreated on the OptiX PTN 1900 and OptiX PTN 3900, because the network is a leasednetwork of the third party operator.

5. Create MPLS Tunnel 2.This tunnel is used for carrying the R99 voice service, which resides on the POS interfacesof the OptiX PTN 1900 and OptiX PTN 3900.

6. Create the QoS policy (CBR and UBR).Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 andOptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voiceservice, and UBR is used for the HSDPA service.

7. Create the ATM service.l On the OptiX PTN 1900, create two ATM services, and access the services of Node B.


8. Create the ATM connection.l On the OptiX PTN 1900, create two ATM connections in each ATM service, and

encapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent MPLS Tunnels for carrying the services.

l On the OptiX PTN 3900, create two ATM connections in each ATM service, andencapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent MPLS Tunnels for carrying the services.

NOTE






14-23





VPI/VCIValueAdded atthe ATMLayerAfter theAAL5Adaptation

VPI/VCIValue onthe RNCSide


2 Mbit/s 1/100 56/80 - 56/80


5 Mbit/s 1/101 46/80 20/30 46/80


2 Mbit/s 1/100 56/81 - 56/81


5 Mbit/s 1/101 46/81 20/30 46/81

Table 14-9 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMA groupsto access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1-AD1-1 toRNC.











Configuration Guide


Issue 06 (2009-06-01)


EquipmentInterface

InterfaceType

Port Mode IP Addressand SubnetMask of theInterface

MAC Addressof theInterface

OptiX PTN1900:7-ETFC-1

Ethernetinterface

Layer 3 192.168.1.5/30 00-00-00-00-00-01 (for creatingthe static ARP)

OptiX PTN3900:1-EG16-1

Ethernetinterface

Layer 3 192.168.1.6/30 00-00-00-00-00-02 (for creatingthe static ARP)



-



-

Table 14-11 and Table 14-12 list the planning of the MPLS Tunnel and related PW.



14-25

Table 14-11 Planning of the MPLS Tunnel

MPLSTunnel

MPLSTunnel ID



MPLSTunnelType

TunnelBandwidth

MPLSTunnel 1

Forward: 50Reverse: 51

7-ETFC 1-EG16-1 Static Norestriction

MPLSTunnel 2

Dynamicdistribution

4-POD41-1 19-POD41-1 Dynamic Norestriction

NOTE

If the type of the MPLS Tunnel 1 is static, manually specify the IP address of the next hop and the IPaddresses of the source and sink nodes.

If the type of the MPLS Tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnelpasses through the specified interfaces.


PW

PWSignalingType

PWType

PWLabel

OppositeIPAddress




PW1




PW2

Dynamic


Dynamicdistribution



Table 14-13 and Table 14-14 list the planning of the ATM services on the OptiX PTN 1900and OptiX PTN 3900.


Configuration Guide


Issue 06 (2009-06-01)






1-MD1-2(Trunk-2)

1-MD1-1(Trunk-1)

1-MD1-2(Trunk-2)



Source VPI/VCI

1/101 1/101 1/100 1/100

Sink VPI/VCI 46/80 46/81 56/80 56/81


PW1 PW1 PW2 PW2




DownlinkPolicy

UBR UBR CBR CBR






Source VPI/VCI

46/80 46/81 56/80 56/81

Sink VPI/VCI 46/80 46/81 56/80 56/81


PW1 PW1 PW2 PW2



14-27





DownlinkPolicy

UBR UBR CBR CBR

14.4.2 Configuration ProcessThis section describes the configuration process of the Offload application in an ETH-forwarding-based network.

Prerequisitel You must know the networking and data planning of this case.


Procedure


Step 2 Choose Configuration > Interface Management > ATM IMA Management, and click theBinding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3-L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively.


Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > InterfaceManagement > Ethernet Interface. Set 1-EG16-1 as an network-side interface. Then, set theparameters as follows:l Basic attributes


– Use the default values for other parameters




– Set IP Mask to 255.255.255.252.

Step 5 Choose Configuration > Interface Management > SDH Interface. Set 19-POD41-1 as annetwork-side interface. Then, set the parameters as follows:


Configuration Guide


Issue 06 (2009-06-01)

l Basic attributes– Set Encapsulation Type to PPP.





– Set IP Mask to 255.255.255.252.







– Set IP Mask to 255.255.255.252.

Step 7 Choose Configuration > Interface Management > SDH Interface. Set 4-POD41-1 as annetwork-side interface. Then, set the parameters as follows:l Basic attributes






– Set IP Mask to 255.255.255.252.

Step 8 Create static ARP on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, chooseConfiguration > Control Plane Configuration > Address Parse . Click Create.l OptiX PTN 1900

– Set ARP List IP to 192.168.10.6.

– Set ARP List MAC to 00-00-00-00-00-02.

l OptiX PTN 3900– Set ARP List IP to 192.168.1.5.


Step 9 Create MPLS tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the typeof the tunnel is Static, you need to create a static MPLS tunnel on the OptiX PTN 1900 and



14-29

OptiX PTN 3900 respectively. For the method of creating the tunnel in this case, see 6.5 Creatingan MPLS Tunnel on a Per-NE Basis.


Step 11 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NEExplorer, choose Configuration > QoS Management > Policy Management . Then, selectATM Policy and click New.l The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent.









– Set Source Port to 1-MD1-1(Trunk-1).

– Set Source VPI to 1.




– Set Uplink Policy and Downlink Policy to the created UBR policy







– Set Uplink Policy and Downlink Policy to the created UBR policy


Configuration Guide


Issue 06 (2009-06-01)

l Setting the parameters of PW1 as follows:General Attributes:– Set PW ID to 1.– Set PW Signaling Type to Static.– Set PW Type to ATM n-to-one VCC cell transport.– Set PW Ingress Label and PW Egress Label to 100.– Set Peer IP to 192.168.1.6.– Set Tunnel Type to MPLS.– Set Tunnel to created MPLS Tunnel 1.– Set Max. Concatenated Cell Count to 10.– Set Packet Loading Time(us) to 1000.QoS– Ingress

– Bandwidth Limit: Enabled– CIR (kbit/s): 10240– CBS (byte): -– PIR (kbit/s): 15000– PBS (byte): -– Policy:– EXP: 1

Advanced Attributes:– Control Word: Must use– Control Channel Type: CW (CW realizes connectivity check of the PW.)– VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.)– Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be

encapsulated in each packet)– Packet Loading Time (us): 1000

NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Modeneed be set according to the user requirements.For detailed configuration steps, refer to 10.3.2 Creating ATM Services on a Per-NE Basis.






14-31




----End

14.5 IP-Based Service Configuration CaseThis section describes the offload solution for the case where IP-based services traverse thewholesale ADSL network.

14.5.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the IP.

14.5.2 Configuration ProcessThis section describes the configuration process of the Offload application in an IP-forwarding-based network.

14.5.1 Case DescriptionThis section describes the offload solution to the wholesale ADSL network, which is forwardedaccording to the IP.

Networking and RequirementTwo Node Bs are accessed through two IMA groups of the OptiX PTN 1900, and the two NodeBs communicate with the RNC connected to the OptiX PTN 3900 at the opposite end throughthe network. Services of Node B include the R99 voice service and high speed downlink packetaccess (HSDPA) service. The voice service, which is carried by the backhaul networkconstructed by the OptiX PTN equipment, requires QoS guarantee, low delay and bandwidthguarantee. The HSDPA service does not require low delay, but it only requires bandwidthguarantee. Hence, the IP network of a third party operator is leased.


l HSDPA service: The HSDPA service is converged to the DSLAM equipment through theADSL modem, and then it enters the leased IP network of the third party operator fortransmission. The HSDPA service requires only bandwidth guarantee, and thus the leasecost is low.




Configuration Guide


Issue 06 (2009-06-01)

l HSDPA service: On the OptiX PTN 1900, perform the VPI/VCI switching on the servicewith a VPI/VCI value of 1/101, and then transport the service to the FE interface of theETFC. The ADSL modem completes the AAL5 adaptation and ATM encapsulation, andthe DSLAM removes the ADSL and ATM layers. Then, the Ethernet packets are sent tothe IP switching network. The OptiX PTN 3900 rearranges the service and then convergesthe service to the ATM STM-1 interface. Then, the service is transported to RNC. IP Tunnel1 is set up between the OptiX PTN 1900 and OptiX PTN 3900 for carrying the service.Figure 14-10 shows the encapsulation format of packets at the interface of each equipment.The red lines indicate the VPI/VCI values at ATM layers in the packets.


Figure 14-10 Networking diagram of the offload application scenario based on the IP forwardingand packet encapsulation format

HSDPA flow

R99 flow

Node B 1


RNC

PTN

ATMSTM-1

Node B 2

CXP-1-MD1-3-L75:1-4

CXP-1-MD1-3-L75:5-8

4-POD41-1

7-ETFC-1

46/8046/81

1/1001/101

1/1001/101

56/8056/81

1-EG16-19-POD41-1

1-EG16-14-MP1-AD1-1

MPLS Tunnel 2IP Tunnel 1


ATM ATMPWE3

PW LabelIP

Ethernet

ATMPWE3

PW LabelIP

EthernetAAL5ATMADSL

ATMPWE3

PW LabelIP

Ethernet

ATMPWE3

PW LabelIP

Ethernet

ATM

ADSLmodem

DSLAM46/8046/8156/8056/81

56/8056/81

E1 STM-1


l When the ADSL modem works in the bridge mode, the ADSL modem performs the EoAencapsulation on the accessed FE signals. The OptiX PTN 1900 on the access node usesthe MPLS Tunnel or IP Tunnel.



14-33

l When the ADSL modem works in the router mode, the ADSL modem performs the IPoAencapsulation on the accessed FE signals. The OptiX PTN 1900 at the access node uses theIP Tunnel or GRE Tunnel.

In this example, the OptiX PTN 1900 uses the MPLS Tunnel, and the ADSL modem works inthe bridge mode. If the ADSL modem works in the router mode, the configuration method isthe same. In this case, the GRE Tunnel is created to carry the HSDPA service.

Service Planning

The offload is a solution instead of a service or feature. Hence, according to the user requirementand networking diagram of this example, this example uses the offload solution to perform thefollowing tasks.

1. Create the IMA group and configure the member interfaces.

On the OptiX PTN 1900, create two IMA groups for accessing the IMA services of twoNode Bs.

2. Configure attributes of the interface.

The attributes of the interface carry the tunnel should be configured on the OptiX PTN1900 and OptiX PTN 3900.

3. Create the static route.

Create the static route on the OptiX PTN 1900 and OptiX PTN 3900. The static route isused for creating the IP Tunnel.

4. Create the static ARP table entry.

After the static ARP is configured, the equipment finds the corresponding MAC addressin the ARP table entry according to the destination IP address, and then writes the MACaddress as the destination MAC to the ETH layer of the packet. The Layer 2 switchingnetwork forwards the packet to the destination according to this MAC address. Static MPLSTunnel should use this table entry.

5. Create IP Tunnel 1.

This tunnel is used for carrying the HSDPA service. The ports where the tunnel resides arethe FE interface of the OptiX PTN 1900 and the GE interface of the OptiX PTN 3900.

6. Create MPLS Tunnel 2.

This tunnel is used for carrying the R99 voice service, which resides on the POS interfacesof the OptiX PTN 1900 and OptiX PTN 3900.

7. Create the QoS policy (CBR and UBR).

Create the ATM policy before creating the ATM service. On the OptiX PTN 1900 andOptiX PTN 3900, create two ATM policies respectively. CBR is used for the R99 voiceservice, and UBR is used for the HSDPA service.

8. Create the ATM service.

l On the OptiX PTN 1900, create two ATM services, and access the services of Node B.


9. Create the ATM connection.

l On the OptiX PTN 1900, create two ATM connections in each ATM service, andencapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent Tunnel for carrying the services.


Configuration Guide


Issue 06 (2009-06-01)

l On the OptiX PTN 3900, create two ATM connections in each ATM service, andencapsulate the services to different PWs according to the VPI/VCI value, and selectdifferent Tunnel for carrying the services.

NOTE








VPI/VCIValue on theRNC Side

R99 voice service ofNode B 1

2 Mbit/s 1/100 56/80 56/80


5 Mbit/s 1/101 46/80 46/80

R99 voice service ofNode B 2

2 Mbit/s 1/100 56/81 56/81


5 Mbit/s 1/101 46/81 46/81

Table 14-16 lists the planning of the UNIs. The OptiX PTN 1900 needs to create two IMAgroups to access two Node B services. The OptiX PTN 3900 needs to interconnect 4-MP1-AD1-1 to RNC.












14-35


EquipmentInterface

Interface Type Port Mode IP Address andSubnet Mask ofthe Interface

OptiX PTN 1900:7-ETFC-1

Ethernet interface Layer 3 192.168.1.5/30

OptiX PTN 3900:1-EG16-1

Ethernet interface Layer 3 192.168.20.6/30

OptiX PTN 1900:4-POD41-1

SDH interface Layer 3 192.168.2.5/30 (Inthe backhaulnetwork, the IPaddress and mask ofthe interface of theOptiX PTNequipmentinterconnected to thisSDH interface is192.168.2.6/30.)

OptiX PTN 3900:19-POD41-1

SDH interface Layer 3 192.168.10.6/30 (Inthe backhaulnetwork, the IPaddress and mask ofthe interface of theOptiX PTNequipmentinterconnected to thisSDH interface is192.168.10.5/30.)

Table 14-18 lists the planning of the static routing table entries.

Table 14-18 Planning of the static routing table entries

Parameter OptiX PTN 1900 OptiX PTN 3900

Route List ID 1 1

Board 7-ETFC 1-EG16

Port 1(PORT-1) 1(PORT-1)

Next Hop IP Address 192.168.1.6 (IP address ofthe interface of theequipment interconnected tothe DSLAM in the leasednetwork)

192.168.20.5 (IP address ofthe interface of theequipment interconnected tothe OptiX PTN 3900 in theleased network)

Destination Node IP 192.168.20.6 192.168.1.5


Configuration Guide


Issue 06 (2009-06-01)

Parameter OptiX PTN 1900 OptiX PTN 3900

Destination Node SubnetMask

255.255.255.255 255.255.255.255

Table 14-19 and Table 14-20 list the planning of the tunnel and related PW.

Table 14-19 Planning of the Tunnel

Tunnel TunnelID

Interfaceof theTunnelCarriedby theOptiXPTN 1900

Interfaceof theTunnelCarriedby theOptiXPTN 3900

TunnelType

Sink PortIPAddress

TunnelBandwidth

IP Tunnel1

50 7-ETFC 1-EG16-1 Static IPTunnel

OptiXPTN1900:192.168.20.6OptiXPTN3900:192.168.1.5

Norestriction

MPLSTunnel 2

Dynamicdistribution

4-POD41-1

19-POD41-1

DynamicMPLSTunnel

Norestriction

NOTE

As the type of the IP Tunnel 1 is static, you need to create the static ARP and manually specify Sink PortIP Address of the IP Tunnel.

If the type of the MPLS Tunnel 2 is dynamic, manually specify the restriction condition. Hence, the tunnelpasses through the specified interfaces.



14-37


PW

PWSignalingType

PWType

PWLabel

OppositeIPAddress




PW1




PW2

Dynamic


Dynamicdistribution



Table 14-21 and Table 14-22 list the planning of the ATM services on the OptiX PTN 1900and OptiX PTN 3900.






1-MD1-2(Trunk-2)

1-MD1-1(Trunk-1)

1-MD1-2(Trunk-2)



Source VPI/VCI

1/101 1/101 1/100 1/100

Sink VPI/VCI 46/80 46/81 56/80 56/81


PW1 PW1 PW2 PW2


Configuration Guide


Issue 06 (2009-06-01)





DownlinkPolicy

UBR UBR CBR CBR






Source VPI/VCI

46/80 46/81 56/80 56/81

Sink VPI/VCI 46/80 46/81 56/80 56/81


PW1 PW1 PW2 PW2




DownlinkPolicy

UBR UBR CBR CBR

14.5.2 Configuration ProcessThis section describes the configuration process of the Offload application in an IP-forwarding-based network.

Prerequisitel You must know the networking and data planning of this case.



14-39


Procedure


Step 2 Choose Configuration > Interface Management > ATM IMA Management, and click theBinding tab. Bind interfaces ranging from 3-L75-1 to 3-L75-4 and interfaces ranging from 3-L75-5 to 3-L75-8 to Trunk 1 and Trunk 2 respectively.


Step 4 In the NE Explorer, select OptiX PTN 3900. Choose Configuration > InterfaceManagement > Ethernet Interface. Set 1-EG16-1 as an network-side interface. Then, set theparameters as follows:l Basic attributes






– Set IP Mask to 255.255.255.252.







– Set IP Mask to 255.255.255.252.




l Layer 3 attributes


Configuration Guide


Issue 06 (2009-06-01)

– Set Enable Tunnel to Enabled.



– Set IP Mask to 255.255.255.252.







– Set IP Mask to 255.255.255.252.

Step 8 Create static routes on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, chooseConfiguration > Control Plane Configuration > Static Route Management . ClickCreate.l OptiX PTN 1900

– Set Board to 7-ETFC-1.

– Set Port to 1(PORT-1).

– Set Next Hop IP Address to 192.168.1.6.

– Set Destination Node IP to 192.168.20.6.

– Set Destination Node Subnet Mask to 255.255.255.255.

l OptiX PTN 3900– Set Board to 1-EG16-1.

– Set Port to 1(PORT-1).

– Set Next Hop IP Address to 192.168.20.5.

– Set Destination Node IP to 192.168.1.5.

– Set Destination Node Subnet Mask to 255.255.255.255.

Step 9 Create static ARP on the OptiX PTN 1900 and OptiX PTN 3900. In the NE Explorer, chooseConfiguration > Control Plane Configuration > Address Parse . Click Create.l OptiX PTN 1900

– Set ARP List IP to 192.168.10.6.


l OptiX PTN 3900– Set ARP List IP to 192.168.1.5.


Step 10 Create IP tunnel 1 between the OptiX PTN 1900 and the OptiX PTN 3900. Because the type ofthe tunnel is Static, you need to create the IP tunnels on the OptiX PTN 1900 and OptiX PTN



14-41

3900 respectively. For the method of creating the tunnel in this case, see 7.2 Creating IPTunnels.


Step 12 Create two ATM policies on the OptiX PTN 1900 and OptiX PTN 3900 respectively. In the NEExplorer, choose Configuration > QoS Management > Policy Management . Then, selectATM Policy and click New.l The ATM policies on the OptiX PTN 1900 and the OptiX PTN 3900 should be consistent.























Configuration Guide


Issue 06 (2009-06-01)

l Setting the parameters of PW1 as follows:General Attributes:– Set PW ID to 1.– Set PW Signaling Type to Static.– Set PW Type to ATM n-to-one VCC cell transport.– Set PW Ingress Label and PW Egress Label to 100.– Set Peer IP to 192.168.1.6.– Set Tunnel Type to MPLS.– Set Tunnel to created MPLS Tunnel 1.– Set Max. Concatenated Cell Count to 10.– Set Packet Loading Time(us) to 1000.QoS– Ingress

– Bandwidth Limit: Enabled– CIR (kbit/s): 10240– CBS (byte): -– PIR (kbit/s): 15000– PBS (byte): -– Policy:– EXP: 1

Advanced Attributes:– Control Word: Must use– Control Channel Type: CW (CW realizes connectivity check of the PW.)– VCCV Verification Mode: Ping ( PW Ping realizes connectivity check of the PW.)– Max. Concatenated Cell Count: 10 (the maximum number of ATM cells that can be

encapsulated in each packet)– Packet Loading Time (us): 1000

NOTE

PW advanced attributes such as Control Word, Control Channel Type and VCCV Verification Modeneed be set according to the user requirements.For detailed configuration steps, refer to 10.3.2 Creating ATM Services on a Per-NE Basis.






14-43




----End


Configuration Guide


Issue 06 (2009-06-01)

15 Configuring the External EnvironmentMonitoring Interfaces

About This Chapter

The OptiX PTN equipment provides the alarm input and output interfaces for monitoring theequipment alarms and environment alarms. The alarm input interface inputs the externalenvironment monitoring information to the OptiX PTN equipment, and the OptiX PTNequipment reports the information to the NMS center. Hence, the external environment ismonitored and managed on the T2000. The alarm output interface outputs the alarm informationto the alarm monitoring center, and then the alarm monitoring center manages the alarms in acentralized manner.

15.1 Application of the Environment Monitoring InterfacesOn the system control board, the alarm output interface and alarm input interface are calledenvironment monitoring interfaces on the T2000. The environment monitoring interfaces areused to transmit the information about the alarms for the OptiX PTN equipment and the externaloperating environment for the OptiX PTN equipment. Hence, the information about the alarmsfor the equipment and the external operating environment status are managed in a centralizedmanner.

15.2 Setting Attributes of the Input RelayOn the T2000, you can set the attributes of the input relay. You can monitor the status of theexternal environment where the equipment is operating through the environment monitoringinterface. When the operating environment is abnormal, an alarm is reported on the T2000.

15.3 Setting the Output Status of the Alarm RelayThe alarm information of the OptiX PTN equipment can be transmitted to the alarm monitoringcenter through the alarm output interface. Hence, the alarms can be easily managed.

15.4 Querying and Configuring the Board Temperature MonitoringOn the T2000, you can query and configure the upper threshold and lower threshold of the boardtemperature, and monitor the board temperature status. If the operating temperature of the boardis higher than the upper threshold or lower than the lower threshold, the TEMP_OVER alarmis reported. This ensures that the board is operating in the normal temperature.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide

15 Configuring the External Environment MonitoringInterfaces


15-1

15.1 Application of the Environment Monitoring InterfacesOn the system control board, the alarm output interface and alarm input interface are calledenvironment monitoring interfaces on the T2000. The environment monitoring interfaces areused to transmit the information about the alarms for the OptiX PTN equipment and the externaloperating environment for the OptiX PTN equipment. Hence, the information about the alarmsfor the equipment and the external operating environment status are managed in a centralizedmanner.

As shown in Figure 15-1, the alarm monitoring center monitors the operating status of theequipment in the equipment room, and manages the alarm information in a centralized manner.The alarm collection module detects the external operating environment status of the equipmentwith regard to temperature, humidity, and security of the equipment room.

l Alarm output interface (ALMO1): The ALMO interface is a common interface for twoalarm outputs and two alarm concatenations. As shown in Figure 15-1, the informationabout the alarms for the OptiX PTN equipment can be output through the alarm outputinterface to the alarm monitoring center, or the information about the alarms for multiplesets of OptiX PTN equipment is concatenated and then managed in a centralized mannerthrough the alarm output interface.

l Alarm Input interface (ALMI1/ALMI2): The ALMI1 interface is the interface for one tofour alarm inputs, and the ALMI2 interface is the interface for five to eight alarm inputs.The system control board supports a total of eight alarm inputs. As shown in Figure15-1, the information about the external operating status for the equipment that is collectedby the alarm collection module is input to the OptiX PTN equipment through the alarminput interface. When the external operating environment status is abnormal, an alarm isreported on the T2000. Hence, the external operating environment can be easily managedby the NMS.

Figure 15-1 Application of the alarm input/output interfaces

System control board

Alarm monitoring

center

NMS

OptiX PTN equipment

ALMO1

Alarm collection module

ALMI1

ALMI2




Issue 06 (2009-06-01)

15.2 Setting Attributes of the Input RelayOn the T2000, you can set the attributes of the input relay. You can monitor the status of theexternal environment where the equipment is operating through the environment monitoringinterface. When the operating environment is abnormal, an alarm is reported on the T2000.


Procedure

Step 1 Click the icon of the SCA in the NE Explorer, and choose Configuration > EnvironmentMonitor Configuration > Environment Monitor interface from the Function Tree.

Step 2 Select Input Relay from the drop-down menu. Set Using Status of the alarm input interface toUsed.

NOTE

In the case of the OptiX PTN 3900 equipment, you can set eight alarm inputs, and each alarm input canmonitor one external environment status.

For the description of the ALMI1/ALMI2 interface, see Front Panel of the SCA in the ProductDescription.

Step 3 Set Alarm Mode according to the monitored environment information.

NOTE

According to the alarm mechanism of the external environment, set the alarm mode as follows:

l An Alarm is Generated if the Relay Turns On and High Level is Caused: indicates that the relay turnson, and the alarm is reported when the high level is input to the alarm interface.

l An Alarm is Generated if the Relay Turns Off and Low Level is Caused: indicates that the relay turnsoff, and the alarm is reported when the low level is input to the alarm interface.

Step 4 Click Apply.

----End

15.3 Setting the Output Status of the Alarm RelayThe alarm information of the OptiX PTN equipment can be transmitted to the alarm monitoringcenter through the alarm output interface. Hence, the alarms can be easily managed.




15-3


Procedure

Step 1 Click the icon of the SCA in the NE Explorer, and choose Configuration > EnvironmentMonitor Configuration > Environment Monitor interface from the Function Tree.

Step 2 Select General Attributes from the drop-down menu.

Step 3 According to the actual requirement, set Relay Control to Auto Control or Manual Control.

NOTE

By default, the relay control mode is the automatic control mode.

Auto Control: In this mode, if an alarm is reported, the alarm information is automatically output.

Manual Control: In this mode, you should manually set the status of the alarm relay. The alarm informationis output to the alarm monitoring center through the alarm interface only when the replay status is set toEnabled.

Step 4 If you select Manual Control, you can set Relay Status in Major Alarm and Relay Status inCritical Alarm.

Step 5 Click Apply.

----End

15.4 Querying and Configuring the Board TemperatureMonitoring

On the T2000, you can query and configure the upper threshold and lower threshold of the boardtemperature, and monitor the board temperature status. If the operating temperature of the boardis higher than the upper threshold or lower than the lower threshold, the TEMP_OVER alarmis reported. This ensures that the board is operating in the normal temperature.


ContextThe equipment monitors the board temperature and reports the alarm only when the monitoringstatus is set to Monitor. By default, the board temperature monitoring status is Monitor. In thiscase, you can just use the default values of the upper threshold and lower threshold.

Procedure

Step 1 Click the icon of a board in the NE Explorer, and choose Configuration > EnvironmentMonitor Configuration > Environment Monitor Interface from the Function Tree.




Issue 06 (2009-06-01)

Step 2 Select Temperature Attributes from the drop-down menu, and then set Monitor Status.

Step 3 Set Temperature Upper Threshold(℃) and Temperature Lower Threshold(℃). ClickApply.

----End




15-5

16 Backing up the Configuration Data

About This Chapter

To back up the configuration data is to back up the data stored on the T2000 and that stored onthe NE. To back up the data stored on the T2000, back up the MO data of the T2000. To backup the data stored on the NE, backup the NE database.

16.1 Periodically Backing Up the T2000 MO DataYou can set a scheduled backup task for the database so that the T2000 automatically backs upthe T2000 database at a scheduled time. This facilitates the operation and the maintenance.

16.2 Backing Up NE DatabasesDuring routine maintenance, you need to back up the NE database so that the NE canautomatically recover the data if the NE software data is lost or a power failure occurs in theequipment.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 16 Backing up the Configuration Data


16-1

16.1 Periodically Backing Up the T2000 MO DataYou can set a scheduled backup task for the database so that the T2000 automatically backs upthe T2000 database at a scheduled time. This facilitates the operation and the maintenance.

PrerequisiteYou must be an NM user with "NM maintainer" authority or higher.

Context

NOTEIn a distributed system, back up T2000 data on the Master server.

NOTEIn a distributed system, back up T2000 data on the Master server of the active site.

l On Solaris, to back up the MO data periodically by using the command line, run thefollowing commands on the active server as user t2000:% suPassword: Password_of_user_root# cd /T2000/server/database# ./configTask.sh

Follow the instructions displayed on the terminal to perform operations.l On SUSE Linux, to back up the MO data periodically by using the command line, run the

following commands on the active server as user t2000:% suPassword: Password_of_user_root# cd /T2000/server/database# ./configTask.sh

Follow the instructions displayed on the terminal to perform operations.

Procedure

Step 1 Choose System > Schedule Task Management from the Main Menu.

Step 2 Click New, and the Task Creation Wizard is displayed.

NOTEIf you have not defined a scheduled task, a prompt is displayed.

Step 3 Select Database Backup in the Select task type field and enter the task name. Click Next.

Step 4 Set a backup directory for the server, and click Next.

NOTE

By self-defining a backup directory, you can avoid the impacts on the backup data that may be causedwhen you reinstall the system or format disk C. In this way, the maintainability of the system is improved.

Make sure that no space, punctuation or non-English character exists in the path.

Step 5 Set the running period and click Next.

NOTEThe interval of different scheduled tasks must be set above 20 minute.

l The scheduled time for a task is based on the server time.

16 Backing up the Configuration DataOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide


Issue 06 (2009-06-01)

l When creating or modifying a scheduled task, if the running period is set to Running onceor Daily, set the start time of the scheduled task at least five minutes later than the currenttime (the server time).

Step 6 Set the time to run the task.

Step 7 Click Finish. The system backs up the T2000 database according to the time settings.

----End

PostrequisiteUse the network management system maintenance suite to back up the deployment informationof the network management system immediately.

16.2 Backing Up NE DatabasesDuring routine maintenance, you need to back up the NE database so that the NE canautomatically recover the data if the NE software data is lost or a power failure occurs in theequipment.

Prerequisitel You must be an NM user with "NE and network operator" authority or higher.

l Log in to the NE as an NE user with "System Level" authority.

Procedure

Step 1 Choose Configuration > Configuration Data Management from the Main Menu.

Step 2 In the Object Tree on the left, select an NE and click the double-right-arrow button (red).

Step 3 Select one or more NEs in the Configuration Data Management List.

Step 4 Click Back Up NE Data.l If you need to back up the data to the SCC board, choose Back Up Database to SCC.l To manually back up the NE data to a CF card, select Manually Back Up Database to CF

Card.

Step 5 The Operation Result dialog box is displayed. After the backup is complete, click Close.

----End

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide 16 Backing up the Configuration Data


16-3

A Glossary

3G

3G stands for third generation, which indicates the mobilecommunication system of the next generation. In addition to the audioservice, the 3G mobile communication system can also provideenhanced services such as multimedia services and video services.

A

AsynchronousTransfer Mode

The asynchronous transfer mode (ATM) is designed to transfer cell inwhich multiple service types (such as voice, video, or data) are conveyedin fixed-length (53-byte) cells. Fixed-length cells allow cell processingto occur in hardware, thereby reducing transit delays.

B

bandwidth It is used to describe the rated throughput capacity of a given networkmedium or protocol.

broadcast A means of delivering information to all members in a network. Thebroadcast range is determined by the broadcast address.

Bypass Tunnel An LSP that is used to protect a set of LSPs passing over a commonfacility.

C

circuit emulationservice

A technology adapts the traditional narrowband services, that is, TDMservices, to the wideband.

committed burstsize

A parameter used to define the capacity of token bucket C, that is, themaximum burst IP packet size when the information is transferred at thecommitted information rate. This parameter must be larger than 0. It isrecommended that this parameter should be not less than the maximumlength of the IP packet that might be forwarded.

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide A Glossary


A-1

committedinformation rate

The rate at which a frame relay network agrees to transfer informationin normal conditions. Namely, it is the rate, measured in bit/s, at whichthe token is transferred to the leaky bucket.

constant bit rate A kind of service categories defined by the ATM forum. CBR transferscells based on the constant bandwidth. It is applicable to serviceconnections that depend on precise clocking to ensure undistortedtransmission.

control plane The control plane performs the call control and connection controlfunctions. Through signalling, the control plane sets up and releasesconnections, and may restore a connection in case of a failure. Thecontrol plane also performs other functions in support of call andconnection control, such as routing information dissemination.

D

downstream In an access network, where there is a clear indication in eachdeployment as to which end of a link is closer to a subscriber,transmission toward the subscriber end of the link.

E

Ethernet Line An point-to-point private service type that is provided for the userEthernet in different domains.

F

frame The packet data unit described in the OSI model. It consists of frameheader, user data and frame tail. The frame header and frame tail are usedfor synchronization and error control.

H

HSDPA The HSDPA can provide a high transmission rate for downlink data(from the wireless access network to mobile terminal).

Hold Priority The priority of the tunnel with respect to holding resources, ranging from0 (indicates the highest priority) to 7. It is used to determine whether theresources occupied by the tunnel can be preempted by other tunnels.

I

Inloop A method of looping the signals from the cross-connect unit back to thecross-connect unit.

intermediatesystem

A node that is capable of forwarding data packets in the OSI network.

A GlossaryOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

L

Label DistributionProtocol

A protocol defined in RFC 3036 for distributing labels in MPLS network.It is the set of procedures and messages by which Label Switched Routers(LSRs) establish Label Switched Paths (LSPs) through a network bymapping network-layer routing information directly to data-link layerswitched paths. More information about the applicability of LDP can befound in [RFC3037].

link aggregationgroup

A group in which multiple links connected to the same equipment arebundled together to increase the bandwidth and improve the linkreliability. An LAG can be regarded as one link.

loopback A troubleshooting technique that returns a transmitted signal to its sourceso that the signal or message can be analyzed for errors.

M

multicast A communication method used to copy and deliver data packets to anumber of destination members in a specified group. Multicast coverspoint-to-multipoint multicast and multipoint-to-multipoint multicast.

N

NodeB WCDMA Base Station

O

outloop A method of looping back the input signals received at an port to anoutput port without changing the structure of the signals.

P

PE Provider Edge. A PE is the name of the device or set of devices at theedge of the provider network with the functionality that is needed tointerface with the customer.

peak informationrate

A traffic parameter, expressed in bit/s, whose value should be not lessthan the committed information rate.

Protocol DataUnit

The unit of data output to, or received from, the network by a protocollayer.

Q



A-3

Quality of Service A set of service requirements to be met by the network while transportinga connection or flow; the collective effect of service performance whichdetermine the degree of satisfaction of a user of the service. (E.360.1)

R

route Path through an network.

S

Setup Priority The priority of the tunnel with respect to obtaining resources, rangingfrom 0 (indicates the highest priority) to 7. It is used to determine whetherthe tunnel can preempt the resources required by other tunnels.

T

Tail Drop A congestion management mechanism, in which packets arrive later arediscarded when the queue is full. This policy of discarding packets mayresult in network-wide synchronization due to the TCP slow startupmechanism.

traffic shaping A mechanism to control the traffic going out an interface in order tomatch its flow to the speed of the remote, target interface and to ensurethat the traffic conforms to policies contracted for it.

tunnel A secure communication path between two peers, such as two routers.

U

unspecified bitrate

A kind of service categories defined by the ATM forum. UBR requiresno specified traffic parameter. It allows any amount of data up to aspecified maximum to be transmitted over the network and does notprovide QoS guarantees.

upstream In an access network, where there is a clear indication in eachdeployment as to which end of a link is closer to a subscriber,transmission toward the subscriber end of the link.

V

variable bit rate A kind of service categories defined by the ATM forum. VBR issubdivided into a real time class (rt-VBR) and non-real time class (nrt-VBR). rt-VBR is applicable to services that are sensitive to delay or jitterand have the burst feature. nrt-VBR is applicable to services that areinsensitive to delay or jitter but need provide certain QoS guarantees forthe traffic.

A GlossaryOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

A-4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 06 (2009-06-01)

W

Wholesale ADSLService

Wholesale ADSL indicates the ADSL network service used to transmitHSDPA services for the offload solution. Compared with the TDM links,the Wholesale ADSL service provides higher data transmission rateswith lower cost.



A-5

B Acronyms and Abbreviations

A

ADSL Asymmetrical Digital Subscribe Line

ATM Asynchronous Transfer Mode

C

CBR constant bit rate

CBS committed burst size

D

DCN Data communication network

E

E-LAN Ethernet LAN

E-Line Ethernet Line

G

GPS Global Position System

I

IS-IS Intermediate system to intermediate system.

L

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide B Acronyms and Abbreviations


B-1

LAG link aggregation group

LDP Label Distribution Protocol

LSP label switch path.

LSR label switch router

M

ML-PPP Multilink Point-to-Point Protocol

MSTP Multiple Spanning Tree Protocol

N

NSAP network service access point.

O

OAM Operation, Administration and Maintenance

P

PBS peak burst size

PDU Protocol Data Unit

PIR peak information rate

PPP Point-to-Point Protocol

PRC Primary Reference Clock

PSN packet switching network

PW pseudo wire

PWE3 pseudo wire emulation edge to edge

Q

QoS Quality of Service

T

TDM Time Division Multiplexing

B Acronyms and AbbreviationsOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

V

VCI virtual channel identifier

VPI virtual path identifier

V-UNI virtual user-network interface

W

WFQ weighted fair queuing

WRED weighted random early detection

X

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide B Acronyms and Abbreviations


B-3

C Parameter Reference

When following the Configuration Guide and Feature Description to configure the relevantfunctions, you can read this document to learn about information such as description, valuerange, and setting rules of the parameters to be set.

C.1 64KTs

C.2 AF1 Schedule Weight




C.6 ATM Port Type

C.7 ATM Cell Payload Scrambling

C.8 BPDU (E-Line)

C.9 CBS

C.10 CC Test Transmit Period

C.11 CC Status

C.12 CIR

C.13 CoS

C.14 CRC Check Length

C.15 IP Address Negotiation Result

C.16 IP Mask Negotiation Result

C.17 Specify IP

C.18 LSP Mode

C.19 MAC Address Learning Mode

C.20 Self-learning MAC Address

C.21 MTU(byte)

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide C Parameter Reference


C-1

C.22 NNI (Ethernet Service)

C.23 OAM Working Mode

C.24 Enable OAM Protocol

C.25 PBS

C.26 PHB

C.27 PHY Loopback

C.28 PIR

C.29 PPP Link Status

C.30 PW ID

C.31 PW Egress Label

C.32 PW Direction

C.33 PW Type

C.34 PW Signaling Type

C.35 QinQ Link ID

C.36 RTP Head

C.37 S-VLAN ID

C.38 Tag Type

C.39 Tunnel

C.40 Enable Tunnel

C.41 UNI (Ethernet Service)

C.42 VCCV Verification Mode

C.43 VLAN Forwarding Table Item

C.44 V-UNI ID

C.45 V-UNI Group Type

C.46 WFQ Scheduling Policy

C.47 Packet Type

C.48 Packet Color

C.49 Packet Loading Time

C.50 Packet Loading Time (us)

C.51 Duplicated Policy Name

C.52 Local Working Status

C.53 Test Result

C.54 Policy ID

C Parameter ReferenceOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

C.55 Policy Name

C.56 Member Interface

C.57 Bearer Type

C.58 Egress Port

C.59 Handling Mode

C.60 Handling Mode (Ethernet Unknown Frame)

C.61 Error Frame Monitor Threshold (frame)

C.62 Error Frame Monitor Window (ms)

C.63 Error Frame Second Threshold (s)

C.64 Error Frame Second Window (s)

C.65 Error Frame Signal Periodic Monitor Window (Entries)

C.66 Error Frame Signal Periodic Monitor Threshold (Entries)

C.67 Error Frame Period Threshold (frame)

C.68 Error Frame Period Window (frame)

C.69 Enable Traffic Frame Discarding Flag

C.70 Unidirectional Operation

C.71 Address Table Specified Capacity

C.72 Address Detection Upper Threshold (%)

C.73 Address Detection Lower Threshold (%)

C.74 Discard Lower Threshold (256 bytes)

C.75 Discard Probability (%)

C.76 Discard Upper Threshold (256 bytes)

C.77 Jitter Compensation Buffering Time

C.78 Port Transmit Status

C.79 Port Receive Status

C.80 Port Mode

C.81 Enable Port

C.82 Port Priority

C.83 Peer IP

C.84 Transmitted Packet Length

C.85 Transmitted Packet Count

C.86 Transmitted Packet Priority (Ethernet Service OAM)

C.87 Direction



C-3

C.88 Non-Autonegotiation Flow Control Mode (Ethernet Port)

C.89 Encapsulation Type

C.90 PIR

C.91 Load Sharing Hash Algorithm

C.92 Load Sharing

C.93 Working Mode

C.94 Loopback Status (EFMOAM Parameter)

C.95 Revertive Mode

C.96 Laser Interface Enabling Status

C.97 Laser Transmission Distance (m)

C.98 Activation Status

C.99 Scrambling Capability (POS Port)

C.100 Detection Result

C.101 Static MAC Address

C.102 LAG Type

C.103 Control Channel Type

C.104 Control Word (ATM Service)

C.105 Aging Ability

C.106 Aging Time (min)

C.107 Connection Type

C.108 Enable Differential Delay

C.109 Link Event Notification

C.110 Traffic Classification Bandwidth Sharing

C.111 Traffic Classification Rule

C.112 Name

C.113 Default Packet Relabeling Color

C.114 Logical Relation Between Matched Rules

C.115 Match Type

C.116 Match Value

C.117 Default Forwarding Priority

C.118 Coloration Mode

C.119 Uplink Policy

C.120 Clock Mode


Configuration Guide


Issue 06 (2009-06-01)

C.121 Clock Mode (PDH/SDH Port)

C.122 Split Horizon Group

C.123 Split Horizon Group ID

C.124 Split Horizon Group Member

C.125 Sink Interface Type

C.126 Sink Node

C.127 Destination Maintenance Point MAC Address

C.128 Used Port

C.129 Hop Count

C.130 Wildcard

C.131 Maintenance Domain Level

C.132 Tail Drop Threshold (256bytes)

C.133 Unknown Frame Processing

C.134 Location

C.135 Physical Port ID

C.136 System Priority (LAG)

C.137 Downlink Policy

C.138 Line Encoding Format

C.139 Response Maintenance Point ID

C.140 Signal Type

C.141 CDVT (us)

C.142 Service Type (ATM Service)

C.143 Service Type (ATM Policy)

C.144 Service Type (Ethernet OAM)

C.145 Service Name

C.146 Source Interface Type

C.147 Remote OAM Parameter

C.148 Remote OAM Working Mode

C.149 Remote Side Loopback Response

C.150 Remote Working Status

C.151 Used Timeslot

C.152 Frame Format

C.153 Frame Type



C-5

C.154 VC-Switching-Supported VPIs

C.155 Main Port

C.156 Main Port Status

C.157 Auto-Negotiation Flow Control Mode (Ethernet Port)

C.158 Compositive Working Status

C.159 Impedance

C.160 Max. OAM Packet Length (byte)

C.161 Max. VCI Bits

C.162 Max. VPI Bits

C.163 Max. Differential Delay (100 us)

C.164 Max. Concatenated Cell Count

C.165 Max Data Packet Size(byte)

C.166 MBS (Cells)

C.167 Max Frame Length(byte)-Ethernet interface

C.168 Min. Activated Link Count

C.169 Direction


Configuration Guide


Issue 06 (2009-06-01)

C.1 64KTs

DescriptionThe 64KTs parameter indicates the timeslot compression list during the configuration of thestructured emulation CES services. The selected timeslots are loaded to the PW packets, andthen are transmitted to the opposite end through the Ethernet.

Impact on the SystemThis parameter does not affect the system operation.

ValuesValue Range Default Value

1-31 None

Value Description

1 Indicates timeslot 1 is compressed.

5-7 Indicates timeslots 5-7 are compressed.

3, 7-9 Indicates timeslots 3 and 7-9 are compressed.

Configuration GuidelinesThe timeslot lists at the two ends can be inconsistent, but the number of timeslots must beconsistent. Otherwise, the services are unavailable.

Relationship with Other ParametersWhen you create a CES service, 64KTs can be set only when PW Type is set to CESoPSN.

Related InformationNone.


DescriptionThe QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule theCS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queuesaccording to the weights of the queues > schedule the BE queue. The AF1 Schedule Weight



C-7

parameter indicates the percentage of the AF1 queue to the weight when the AF1-AF4 queuesare scheduled according to the weight.


ValuesValue Range Default Value Unit

1-100 25 %

Configuration GuidelinesThe bigger the value of the AF1 scheduling weight, the higher is scheduling priority of the AF1queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller. Reversely,the smaller the value of the AF1 scheduling weight, the lower is the scheduling priority of theAF1 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is bigger.

Relationship with Other ParametersThe sum of values of AF1, AF2, AF3, and AF4 scheduling weights cannot exceed 100.


DescriptionThe QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule theCS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queuesaccording to the weights of the queues > schedule the BE queue. The The AF2 ScheduleWeight parameter indicates the percentage of the AF2 queue to the weight when the AF1-AF4queues are scheduled according to the weight.



1-100 25 %

Configuration GuidelinesThe bigger the value of the AF2 scheduling weight, the higher is the scheduling priority of theAF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller.


Configuration Guide


Issue 06 (2009-06-01)

Reversely, the smaller the value of the AF2 scheduling weight, the lower is the schedulingpriority of the AF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratiois bigger.

Relationship with Other ParametersThe sum of values of the AF2, AF1, AF3, and AF4 scheduling weights cannot exceed 100.


DescriptionThe QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule theCS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queuesaccording to the weights of the queues > schedule the BE queue. The AF3 Schedule Weightparameter indicates the percentage of the AF3 queue to the weight when the AF1-AF4 queuesare scheduled according to the weight.



1-100 25 %

Configuration GuidelinesThe bigger the value of the AF3 scheduling weight, the higher is the scheduling priority of theAF3 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller.Reversely, the smaller the value of the AF3 scheduling weight, the lower is the schedulingpriority of the AF3 queue. In this case, when the bandwidth is insufficient, the packet loss ratiois bigger.



DescriptionThe QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule theCS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queuesaccording to the weights of the queues > schedule the BE queue. The AF4 Schedule Weighttparameter indicates the percentage of the AF4 queue to the weight when the AF1-AF4 queuesare scheduled according to the weight.



C-9



1-100 25 %

Configuration GuidelinesThe bigger the value of the AF4 scheduling weight, the higher is the scheduling priority of theAF4 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller.Reversely, the smaller the value of the AF4 scheduling weight, the lower is the schedulingpriority of the AF4 queue. In this case, when the bandwidth is insufficient, the packet loss ratiois bigger.


C.6 ATM Port Type

DescriptionThe ATM Port Type parameter identifies the ATM port type. This parameter is used for settingthe ATM port type.

The ATM port type includes the UNI and NNI. The UNI indicates the user network interface,and the NNI indicates the network node interface. These two types of interfaces are used indifferent network locations. Normally, the UNI is used in the location where the terminalaccesses the ATM network. The NNI is mainly used in the location between two ATM networks.The standard UNI interface has the flow control function, in which the higher four bits of theVPI reports back whether the congestion occurs. Hence, the range of the number of VPI bits ofthe UNI interface is four higher bits less than the range of the number of VPI bits of the NNIinterface.



UNI, NNI UNI

The following table lists the description of each value.


Configuration Guide


Issue 06 (2009-06-01)

Value Description

UNI Indicates the range of the number of VPI bits: 1-255.

NNI Indicates the range of the number of VPI bits: 1-4095.

Configuration Guidelines

By default, the ATM port type is UNI. If the port type is UNI, the maximum value of the VPIconfigured is 255. If a service whose VPI value exceeds 255 need be configured, set the porttype to NNI. In this case, the maximum VPI value is 4095.

Relationship with Other Parameters

When the ATM connection is available on the port, the user cannot modify the port type.

Related Information

None.

C.7 ATM Cell Payload Scrambling

Description

The ATM Cell Payload Scrambling parameter identifies whether the ATM cell load on theATM port is scrambled or descrambled. This parameter is used to set whether the load on theATM port is scrambled or descrambled.

Impact on the System

This parameter does not affect the system operation.

Values

Value Range Default Value

Enabled, Disabled Enabled


Value Description

Enabled Indicates that the ATM cell load is scrambled.

Disabled Indicates that the ATM cell load is descrambled.



C-11


When two ports are interconnected, if the opposite end is set to scrambled, the local end shouldalso be set to scrambled. The reverse case is similar.

C.8 BPDU (E-Line)

Description

The BPDU (E-Line) parameter sets whether the service needs transparently transmit the bridgeprotocol data unit (BPDU) packets. The BPDU is the information transmitted between bridges.It is used to switch information between bridges, and then the spanning tree of the network iscomputed.


If the BPDU transparent transmission identifier of the Ethernet service of an NE is enabled, theport where the service VUNI resides cannot process the BPDU packets, and the MSTP cannotbe enabled on this port. After the BPDU transparent transmission is enabled, the BPDU packetsare transmitted as service packets.

Values


Transparently Transmitted, NotTransparently Transmitted

Not Transparently Transmitted


Value Description

Transparently Transmitted The BPDU packets are transparently transmitted to theopposite end as service packets.


The BPDU packets are processed on the local NE as protocolpackets.


If the BPDU packets need be transparently transmitted to the opposite end of the network asservice packets, set the BPDU to Transparently Transmitted during the service creation.

If the BPDU packets need be processed on the local NE as protocol packets for computing thenetwork spanning tree, set the BPDU to Not Transparently Transmitted during the servicecreation.


Configuration Guide


Issue 06 (2009-06-01)

Relationship with Other ParametersIf the BPDU is set to Transparently Transmitted for the Ethernet services carried by anEthernet port, the MSTP cannot be enabled. After the MSTP is enabled on the port, the BPDUtransparent transmission services cannot be configured on the port.

C.9 CBS

DescriptionThe CBS parameter indicates the committed burst size (CBS). When the bandwidth isinsufficient, certain packets cannot enter the queue for forwarding in time. In this case, a buffer,where these packets are stored, is required. Then, after the bandwidth is sufficient, these packetsare forwarded. Hence, the CBS indicates the ensured size of the buffer space. When the size ofdata need be buffered is smaller than the CBS, this data that are temporarily buffered can befully transmitted without packet loss.



Port policy: 2-64000. - Byte

V-UNI ingress policy: 64-131072. - Byte

V-UNI egress policy: 64-1310722. - Byte

PW policy: 64-131072. - Byte

QINQ policy: 64-131072. - Byte

Configuration GuidelinesWhen the bandwidth is insufficient, the smaller the CBS is, the bigger the possibility of packetoverflow is. Thus, the packet loss of various degrees occurs.

When the bandwidth is insufficient, the bigger the CBS is, the bigger the number of packetsbuffered is. Thus, the packet loss ratio is smaller. The bigger the CBS is, however, the biggerthe jitter is during packet forwarding.

C.10 CC Test Transmit Period

DescriptionThe source end MEP constructs the CC frames, and then transmits them periodically to thedestination MEP. After the destination MEP receives the CCM messages from the source end,



C-13

the CC check function of the source MEP is directly started. Within a certain period (3.5 timesof the transmission period), if the destination MEP does not receive the CC packets from thesource end, an alarm is automatically reported. The CC Test Transmit Period parameterindicates the transmission period of the unidirectional connectivity check.

Impact on the SystemAfter the CC check is started, a portion of the bandwidth on the port is used.


3.33ms/10ms/100ms/1s/10s/1m/10m 1s

Configuration GuidelinesIt is recommended that you use three period values, that is, 3.33ms for protection switching,100ms for performance check, and 1s for connectivity check. The configuration should complywith user requirements. If the fast check is required, set to 3.33ms. Hence, the fault can bedetected quickly. The bandwidth used, however, descends with the period value.

C.11 CC Status

DescriptionThe CC Status parameter indicates whether the CC check function of this MEP is activated.

Impact on the SystemIf the CC is activated, the bandwidth is used. Otherwise, the bandwidth is not used.


Active, Inactive Active

Configuration GuidelinesIf the check is needed, select Active. Otherwise, select Inactive.

C.12 CIR

DescriptionThe CIR parameter indicates the ensured bandwidth of the queue. In other words, the packetswithin this bandwidth range can be completely forwarded. If the rate of the packets entering the


Configuration Guide


Issue 06 (2009-06-01)

queue is smaller than the CIR, all the packets are forwarded. If the rate of the packets enteringthe queue is bigger than the CIR, the scheduling algorithm discards packets according to a certainpacket loss policy.



Values

Value Range Default Value Unit

Port policy: 1000-1000000. - Kbit/s

V-UNI ingress policy: 320-10000000. - Kbit/s

V-UNI egress policy: 320-100000000. - Kbit/s

PW policy: 320-10000000. - Kbit/s

QINQ policy: 320-10000000. - Kbit/s


The bigger the bandwidth ensured by the CIR is, the higher the traffic rate can be accepted.Hence, the data packets can be better forwarded.


In the case of a random queue, the CIR value should not exceed the PIR value.

In the case of the CS7, CS6, and EF queues, the CIR value must be equal to the PIR value.

If the policy is applied to the effect point (PW, port, VUNI, or QINQ), the sum of CIR valuesof each policy bandwidth applied to this point should not exceed the CIR value of the bandwidthof this point.

C.13 CoS

Description

The CoS parameter indicates the class of service. Eight CoS values, that is, CS7, CS6, EF, AF4,AF3, AF2, AF1, and BE, are available according to the standard. Different CoS valuescorrespond to different queues. The equipment provides different QoS for queues of differentCoS.





C-15


CS7, CS6, EF, AF4, AF3,AF2, AF1, BE

-


Value Description

CS7 The CS7 queue is of the highest priority, and the packets are forwardedfirst.

CS6 After the packets of the CS7 queue are forwarded, the packets of the CS6queue are forwarded.

EF After the packets of the CS6 queue are forwarded, the packets of the EFqueue are forwarded.

AF4 After the packets of the preceding three queues are forwarded, packets ofAF1-AF4 queues are forwarded according to the WFQ weight.




BE After the packets of the preceding seven queues are forwarded, the packetsof the BE queue are forwarded as possible.

Configuration GuidelinesThe name of the queue is specified by the user.

C.14 CRC Check Length

DescriptionThe CRC Check Length parameter sets the length of the cyclical redundancy check (CRC)character for the POS port. Two lengths of the CRC character, that is, 16-bit and 32-bit, aresupported. The CRC Check Length parameter is used to check the error in the transmissiondata of the communication line.



Configuration Guide


Issue 06 (2009-06-01)


16, 32 32 Bit

Configuration GuidelinesThe length of the CRC character is set according to the size of the test block.

To ensure that 99.998% of the possible errors can be detected, the 16-bit CRC checks all thesingle-bit and two-bit errors. It is determined that this level is effective for data blocktransmission of 4 kbytes or smaller. In the case of transmission of bigger data blocks, the 32-bitCRC is applicable. In the Ethernet and token ring networks, the 32-bit CRC is applicable.

Related InformationThe CRC is a method of checking errors in the transmission data of the communication line. Ifthe transmission equipment adds a 16-bit or 32-bit polynomial, which is the CRC added in thedata block during the transmission. The receive terminal adds the same polynomial to the data,and then compare the result with the result of the polynomial added to the transmissionequipment. If the two results are consistent, it indicates that the data is successfully received. Ifnot, the transmit end sends the data block again.

C.15 IP Address Negotiation Result

DescriptionThe IP Address Negotiation Result parameter indicates that the negotiation result can bequeried after the MLPPP protocol is enabled. This parameter indicates the distributed IP addressafter the MLPPP link negotiates with the opposite end.


Valid IPV4 address None.

In the case of the OptiX PTN V100R001, the query result is the IP address during theconfiguration of MLPPP Layer 3 port.

C.16 IP Mask Negotiation Result

DescriptionThe IP Mask Negotiation Result parameter indicates that the negotiation result can be queriedafter the MLPPP protocol is enabled. This parameter indicates the IP address mask after theMLPPP link negotiates with the opposite end.



C-17

Values


Valid IPV4 address mask None.

C.17 Specify IP

Description

The Specify IP parameter, set by port, indicates the method of specifying the IP addressparameter of a specified port.


The IP address parameter of the port is the prerequisite for service creation. If the current IPaddress parameter is invalid, the services cannot be created.

Values


Manually, Unnumbered NE IP, UnnumberedInterface IP

Manually


Value Description

Manually Indicates the IP parameter of the specified port. If the IPaddress parameter is valid, specify an IP address to the currentport. If the IP address is invalid, release the IP address of thecurrent port.

Unnumbered NE IP Indicates that the current port uses the NE IP address as its IPaddress.

Unnumbered Interface IP Indicates that the current port uses the IP address of anotherport as its IP address.


Commonly, the IP address of the port is specified. If the current IP address resources areinsufficient, the current port can use the NE IP address or the IP address of another port. Inaddition, the port uses the NE IP address or the IP address of another port only in the PPP link.The IP address parameters of the NE and port whose IP addresses are used should be valid.


Configuration Guide


Issue 06 (2009-06-01)

Relationship with Other ParametersThe IP address parameter can be configured only when the port is in the Layer 3 mode. In thecase of the PPP link, the current link layer encapsulation type should be PPP.

C.18 LSP Mode

DescriptionWhen the PW is labeled, the CoS of the packets may be modified. Hence, when the PW label isremoved, you should determine whether the CoS of user packets need be written back. The LSPMode parameter specifies whether a writing back tag is required.



Pipe, Uniform Uniform


Value Description

Pipe Indicates the CoS of the packets written back when the PW label isremoved.

Uniform Indicates the CoS of the packets that is not written back when the PWlabel is removed.

Configuration GuidelinesThe user specifies whether to write back the CoS.

C.19 MAC Address Learning Mode

DescriptionMAC Address Learning Mode includes the IVL mode and SVL mode. IVL, which is theindependent VLAN learning mode, indicates that each VLAN can learn the MAC address. Inaddition, the MAC address table of each VLAN is independent, and the same MAC address canexist in multiple VLANs. SVL, which is the shared VLAN learning mode, indicates that theMAC address learned in a VLAN can be shared with other VLANs, and the MAC address isunique in the MAC address table.



C-19

Impact on the SystemIn the IVL mode, each VLAN has its own MAC forwarding table. During the forwarding, theMAC address is found according to the VLAN, and then the forwarding is performed accordingto the MAC address table. The broadcast packets are forwarded in this VLAN. In the SVL mode,all the VLANs share the same MAC forwarding table. During the forwarding, the egress port isfound according to the MAC address, and then the port determines whether this VLAN is allowedto pass.

If the same MAC address is in multiple VLANs, the IVL mode should be used. In this case, ifthe SVL mode is used, the service cannot differentiate the VLAN.


SVL, IVL IVL


Value Description

IVL Indicates the independent learning mode.

SVL Indicates the shared learning mode.

Configuration GuidelinesIf the same MAC address is in multiple VLANs, the IVL mode should be used. In other cases,the IVL and SVL modes have the same effect.

Relationship with Other ParametersIf the type of the E-LAN service is Tag-Transparent, the MAC address learning mode can onlybe SVL.

C.20 Self-learning MAC Address

DescriptionThe Self-learning MAC Address parameter indicates whether the MAC address is allowed tobe automatically learned. The MAC address self-learning indicates that the learning is performedaccording to the source MAC address of the packet, and then the MAC address forwarding tableis automatically updated.


Configuration Guide


Issue 06 (2009-06-01)

Impact on the SystemAfter the service with the MAC address self-learning capability is enabled, the MAC address isautomatically learned, and the MAC address forwarding table is updated. Otherwise, the staticMAC address table need be configured to forward service packets.

When the MAC address self-learning capability is set to disabled, if the static MAC addressforwarding table is not configured, the services cannot be normally forwarded.




Value Description

Enabled The MAC address can be automatically learned, and then the MACaddress forwarding table can be automatically updated.

Disabled The MAC address cannot be automatically learned, and then theMAC address forwarding table cannot be automatically updated.

Configuration GuidelinesIn most cases, the MAC address self-learning capability of the E-LAN service should be enabled.If the number of CEs accessed by the E-LAN service is small, the forwarding of the MAC addressis restrained. In this case, enable the MAC address self-learning capability before the static MACaddress forwarding items are configured. Hence, the packets forwarding is complete.

C.21 MTU(byte)

DescriptionThe MTU(byte) parameter indicates the maximum transmitted packet length, which is the lengthof the packet payload.

Impact on the SystemIf the length of the packet payload exceeds the value set by the MTU, the packets are discardedduring the forwarding.



C-21


46-9000 1500 Byte


MTU(byte) should not be less than the maximum length of the user packet payload. Otherwise,the packets whose length exceeds the service MTU are discarded. Hence, MTU(byte) shouldbe set to a value larger than the maximum length of the user packet payload.


The value of MTU(byte) and Max Frame Length(byte) of the port can be separatelyconfigured, and then the equipment processes the packets according to the minimum value.

C.22 NNI (Ethernet Service)

Description

The NNI (Ethernet Service) parameter, which indicates the Ethernet service network sideinterface, is used for configuring the Ethernet service network side parameters. The NNI can becarried by physical port, QinQ Link, and PW. If the NNI is carried by the physical port, thespecific slot ID, sub-slot ID, and port number should be specified. If the NNI is carried by theQinQ, the QinQ Link should be specified. If the NNI is carried by the PW, the PW ID shouldbe specified.

C.23 OAM Working Mode

Description

The OAM Working Mode parameter indicates the IEEE 802.3ah protocol mode of a port.




Active, Passive Active



Configuration Guide


Issue 06 (2009-06-01)

Value Description

Active The data terminal equipment (DTE) in the active modeinitializes the discovery process by transmitting the OAMprotocol data unit (PDU) packets.

Passive The DTE in the passive mode responds to the discoveryprocess of the remote DTE instead of initializing thediscovery process.


In the case of the port that needs to initialize the discovery process, set OAM Working Modeto Active.

In the case of the port that needs to respond to the initialization of the discovery process, setOAM Working Mode to Passive.

C.24 Enable OAM Protocol

Description

The Enable OAM Protocol parameter indicates whether the IEEE 802.3ah protocol is enabledat a port.



Values


Enabled, Disabled Disabled


Value Description

Enabled Indicates that the IEEE 802.3ah protocol is enabled at thisport.

Disabled Indicates that the IEEE 802.3ah protocol is disabled at thisport.



C-23


If the link OAM function of a port is required, set Enable OAM Protocol to Enabled.

If the link OAM function of a port need be disabled, set Enable OAM Protocol to Disabled.

C.25 PBS

Description

The PBS parameter indicates the peak burst size. When the bandwidth is insufficient and theCBS buffer is full, these packets are stored in the PBS buffer. When the PBS buffer is full, thesepackets are discarded. The packets stored in the PBS buffer may not be successfully forwarded.The packets in the queue of a rate higher than the CIR but lower than the PIR, the residualbandwidth is preempted according to the algorithm. If the preemption is successful, the data inthe PBS buffer is forwarded.



Values


Port policy: 2-64000 - Byte

V-UNI ingress policy: 64-16777216. - Byte

V-UNI egress policy: 64-16777216. - Byte

PW policy: 64-16777216. - Byte

QINQ policy: 64-16777216. - Byte


The data packets in the PBS buffer may not be successfully forwarded. The size of the PBS,however, may decrease the packet loss rate to some extent. The bigger the PBS buffer is, thesmaller the packet loss rate is. In this case, when a single packet is forwarded, the jitter is greater.

C.26 PHB

Description

The PHB parameter, per hop behavior, indicates a forwarding action applicable on the DS node.This forwarding action belongs to the per hop forwarding aggregation defined in the DiffServdomain.


Configuration Guide


Issue 06 (2009-06-01)



Values


BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,AF32, AF33, AF41, AF42, AF43, EF, CS6, CS7

The CoS defines different serviceclasses:l CS6-CS7: Highest service classes

applicable to transport of thesignaling.

l EF: Fast forwarding, applicable tothe service traffic with the shortestdelay and low packet loss ratio,such as the audio service andvideo service.

l AF1-AF4: Applicable to theservice traffic that requires acertain rate, but not a certain delayor jitter.

l BE: Applicable to the servicetraffic that does not requirespecial processing.

C.27 PHY Loopback

Description

The PHY Loopback parameter indicates the loopback status of the physical layer of an Ethernetport. This parameter is an advanced attribute of the Ethernet port.


If you set PHY Loopback to Inloop for an Ethernet port, services are interrupted. As a faultdiagnosis function, setting PHY loopback affects the services configured on the port. In the caseof loopback, services on the port are interrupted.

Values


Non-Loopback, Inloop, Outloop Non-Loopback




C-25

Value Description

Non-Loopback Indicates the normal status. When the equipment is operating normally,loopback is not required.

Inloop At the local equipment, the outgoing services of an Ethernet port arelooped back at the physical layer and input to this Ethernet port.

Outloop At the local equipment, the incoming services of an Ethernet port arelooped back at the physical layer and output to this Ethernet port.


The PHY loopback is mainly used to locate a fault. When setting this parameter, determine theloopback type according to the service flow direction.


None.

Related Information

The ETFC does not support the PHY outloop.

C.28 PIR

Description

The PIR parameter, a traffic parameter, indicates the peak traffic rate. This parameter isexpressed in kbit/s.



Values


Port policy: 1000-10000000. - Kbit/s

V-UNI ingress policy: 320-10000000. - Kbit/s

V-UNI egress policy: 320-10000000. - Kbit/s

PW policy: 320-10000000. - Kbit/s

QINQ policy: 320-10000000. - Kbit/s


Configuration Guide


Issue 06 (2009-06-01)


The value of the parameter should exceed or equal the CIR.

C.29 PPP Link Status

Description

The PPP Link Status parameter indicates that the configured PPP link protocol is started againor shut down.

When the protocol is shut down, the PPP path is not involved in packet segmentation.


Values


unshutdown shutdown unshutdown


Value Description

unshutdown The PPP protocol is started.

shutdown The PPP protocol is shut down.


The unshutdown working state is recommended.

C.30 PW ID

Description

The PW ID parameter and the PW Type parameter identify the unique PW in the entire network.On the same NE, the uniqueness of the PW is ensured through verification. In the entire network,the user should ensure the uniqueness of the PW.





C-27

Values


1-4294967295 None.


The PWs of the same type should not have the same ID, but the PWs of different types can havethe same ID.


None.

C.31 PW Egress Label

Description

The PW Egress Label parameter labels the specified ingress tunnel during the creation of thebidirectional PW.irection of service forwarding.



Values


16-1048575 None.


None.


C.32 PW Direction

Description

In the case of one PW, two directions, that is, the direction of entering the network and thedirection of exiting the network, are available. The PW Direction parameter indicates whetherthe PW processes one direction or two directions.


Configuration Guide


Issue 06 (2009-06-01)

Impact on the SystemIf the PW is set to unidirectional, the PW processes the packets in only one direction. If the userservices are bidirectional, the packets in another direction cannot be processed.


Bidirectional, Unidirectional -


Value Description

Bidirectional The PW processes packets in two directions, that is, thedirections of entering and exiting the network.

Unidirectional The PW processes packets that only enter or only exit thenetwork.

Configuration GuidelinesIf the PW need to process packets in two directions, that is, the directions of entering and exitingthe network, the value should be set to bidirectional. Otherwise, the value should be set tounidirectional. Generally, in the case of the broadcast PW, the value should be set tounidirectional. In the case of unicast PW, the value should be set to bidirectional.

C.33 PW Type

DescriptionThe PW Type parameter, which sets the PW type, indicates the type of service carried by thePW.

Impact on the SystemThe system is not affected.



C-29


EthernetEthernet TagATM n-to-one VCC cell transportATM n-to-one VPC cell transportATM one-to-one VCC Cell ModeATM one-to-one VPC Cell ModeSAToPCESoPSN


Value Description

Ethernet Indicates the PW of the Ethernet type.

Ethernet Tag Indicates the PW of the Ethernet tagged type.

ATM n-to-one VCC celltransport

Indicates the PW of the ATM n-to-one VCC cell transporttype.

ATM n-to-one VPC celltransport

Indicates the PW of the ATM n-to-one VPC cell transporttype.

ATM one-to-one VCC CellMode

Indicates the PW of the ATM one-to-one VCC cell type.

ATM one-to-one VPC CellMode

Indicates the PW of the ATM one-to-one VPC cell type.

SAToP Indicates the PW of the structure-agnostic E1 over packettype.

CESoPSN Indicates the PW of the CESoPSN basic type.

Configuration GuidelinesWhen creating the PW, select the PW type according to the type of service to be bound to thePW.

Relationship with Other ParametersNone.


Configuration Guide


Issue 06 (2009-06-01)

C.34 PW Signaling Type

Description

The PW Signaling Type parameter, a query parameter, indicates the returned parameter duringthe query of MPLS. This parameter indicates whether the PW is static or dynamic. In the caseof the dynamic PW, the services are available after the signaling negotiation is successful. Inthe case of the static PW, the signaling negotiation is not needed.



Values


Static, Dynamic None.


Value Description

Static Indicates that the PW is statically created.

Dynamic Indicates that the PW is dynamically created.


None.

Relationship with Other ParametersIf PW Signaling Type is set to Static, you need to manually set the value of the PW label.

C.35 QinQ Link ID

Description

The QinQ Link ID parameter indicates the unique identifier of a QinQ link.





C-31

Values


1-4294967295 -


A QinQ Link ID parameter indicates a QinQ link. When creating a QinQ link, you need specifyan unused ID for this QinQ link.

C.36 RTP Head

Description

The RTP Head parameter indicates a real-time transfer protocol that is mainly used for clocksynchronization. In the case of the PW that emulates the CES service, the RTP protocol head inthe packet is processed (including RTP packet head adding and RTP packet head receiving) ornot processed. When this parameter is set to Enabled, the RTP head is processed. Otherwise,the RTP head is not processed.


When the parameter is set to Enabled, the RTP protocol head is processed when packets aretransmitted or received through the PW. Also, the negotiation result is enabled only when bothends of the PW are set to Enabled.

Values




Value Description

Enabled Indicates that the PW processes the RTP head.

Disabled Indicates that the PW does not process the RTP head.


The negotiation result is enabled only when both ends of the PW are set to Enabled.


Configuration Guide


Issue 06 (2009-06-01)

C.37 S-VLAN ID

Description

The S-VLAN ID parameter is a 12-bit field, indicating the VLAN ID. If a switch supports the802.1Q protocol, all packets it transmitting contain this 12-bit field. In this case, a packet isidentified by its own VLAN.




1-4094 -


When creating the QinQ, you should define the port and S-LVAN ID. The port and S-LAN IDcannot be occupied by other services. Moreover, the S-LVAN ID must be set within the validrange.

C.38 Tag Type

Description

The Tag Type parameter sets the type of VLAN Tag learned by the E-LAN service MACaddress. This parameter can set the type of the VLAN Tag for the MAC address learning, thatis, MAC address learning not based on VLAN Tag, MAC address learning based on C-VLANTag, and MAC address learning based on S-VLAN Tag.


When the Tag type of the service is set, the MAC address learning and packet forwarding forthe E-LAN service are affected. If the Tag type of the accessed packets and Tag type of theservice mismatch, the MAC address cannot be learned, packets are discarded, and the servicesare interrupted.


Tag-Transparent, C-Awared, S-Awared C-Awared



C-33


Value Description

Tag-Transparent The MAC address learning is not based on VLAN Tag.

C-Awared The MAC address learning is based on C-VLAN Tag.

S-Awared The MAC address learning is based on S-VLAN Tag.


If the transparent transmission port is accessed, the service packets may not carry VLAN Tag.In this case, set to Tag-Transparent.

If port C is accessed, the service packets carry C-VLAN Tag. In this case, set to C-Awared.

If port S is accessed, the service packets carry S-VLAN Tag. In this case, set to S-Awared.


If the service Tag type is Tag-Transparent, only NULL port can be accessed.

If the service Tag type is C-Awared, only 802.1Q port can be accessed.

If the service Tag type is S-Awared, only QinQ port can be accessed.

If the service Tag type is T-Awared, only the SVL mode can be set to the MAC address learningmode.

C.39 Tunnel

Description

The Tunnel parameter indicates one or multiple tunnels that are bound with the PW. The PWcan be bound with the tunnel and it transmits the data to the remote end of the tunnel.



Values


OptiX PTN 3900 Tunnel number: 1-255OptiX PTN 3900 Tunnel index:1-4294967295

-


Configuration Guide


Issue 06 (2009-06-01)


The tunnel to be specified must be available already. The tunnel specified by a bidirectional PWshould be an ingress unicast tunnel. If the PW is carried by multiple tunnels, the tunnel type andopposite-end IP address (dynamic tunnel) of each tunnel must be consistent.

C.40 Enable Tunnel

Description

The Enable Tunnel parameter sets the MPLS enabling state of the port. When EnableTunnel is set to Enabled, it indicates that the port can identify and process the MPLS label, andsupport the dynamic signaling and routing.


If the MPLS is disabled, the services on the port are interrupted.

Values




Value Description

Enabled The MPLS is enabled.

Disabled The MPLS is disabled.


When the services are configured, the MPLS should not be disabled.


When Port Mode is set to Layer 3, and Encapsulation Type is set to PPP, this parameter canbe set. In the case of the Ethernet port, this parameter can be set only when Port Mode is set toLayer 3. In this case, Encapsulation Type of the port is PPP by default.

Related Information

The MPLS is a standard routing and switching technology platform, which supports varioushigh layer protocols and services.



C-35

The MPLS uses short and fixed-length tags to encapsulate various link layer packets. Based onthe IP routing and control protocol, the MPLS provides switching to the connection at thenetwork layer.

C.41 UNI (Ethernet Service)

Description

The UNI (Ethernet Service) parameter, which indicates the Ethernet service user side interface,is used for configuring the user side Ethernet service. The Ethernet service user side need becarried on the Ethernet port (currently, the E-LAN service UNI can be carried at the Ethernetvirtual interface). The Port and Port + VLAN modes are supported.

C.42 VCCV Verification Mode

Description

The VCCV Verification Mode parameter is used for PW continuity check. This parameter isused to set the verification mode of packet transmission.


If the verification mode of packet transmission is set to None, the PW cannot support the VCCV-Ping.

Values


None, Ping Ping


Value Description

None Indicates no verification mode.

Ping Indicates the ping verification mode.


If the VCCV-Ping need be supported, the VCCV verification parameter of the PW cannot beset to None.


Configuration Guide


Issue 06 (2009-06-01)

C.43 VLAN Forwarding Table Item

DescriptionIn the case of the E-AGGR service, the VLAN value of the packet is modified when the packetsenter or exit the NE. When VLAN Forwarding Table Item is configured, Source InterfaceType, Source VLAN ID, Sink Interface Type, and VLAN ID should be specified. If thepackets with the source VLAN ID accessed from the source interface exit from the sink interface,the VLAN is modified to the sink VLAN value.

Impact on the SystemIn the case of the E-AGGR service, the services are available only after the VLAN forwardingitems are created.

C.44 V-UNI ID

DescriptionThe V-UNI ID parameter identifies the unique V-UNI in the service.

ValuesValue Range

1-65535

C.45 V-UNI Group Type

DescriptionThe V-UNI Group Type parameter indicates that V-UNI groups are distinguished by the uplinkand downlink. Members in the uplink direction belong to the uplink V-UNI group, and membersin the downlink direction belong to the downlink V-UNI group. A V-UNI in a certain directioncan only be available in one V-UNI group.



Ingress, Egress Ingress



C-37


Value Description

Ingress Direction from the equipment to network side

Egress Direction from the equipment to client side

Configuration GuidelinesThe setting depends on the requirement.

C.46 WFQ Scheduling Policy

DescriptionThe WFQ Scheduling Policy parameter indicates that the weighted fair queuing is a packetscheduling technique allowing guaranteed bandwidth services. The WFQ queues all data trafficsand monitors their throughput rates, and then allocates weights according to transmittedinformation flows.


ValuesValue Range Description

Port Policy Indicates the port policy.

V-UNI Ingress Policy Indicates the policy of the ingress logicalinterface at the client side.

V-UNI Egress Policy Indicates the policy of the egress logicalinterface at the client side.

PW Policy Indicates the PW policy.

ATM Policy Indicates the ATM policy

QINQ Policy Indicates the QinQ policy.

Configuration GuidelinesThe policy type setting depends on different subjects.


Configuration Guide


Issue 06 (2009-06-01)

C.47 Packet Type

Description

The Packet Type is used to set the packet type.



Values

Value Range

cvlan, svlan, mpls-exp, ip-dscp


Value Description

cvlan Indicates the user vlan packet.

svlan (Not support the DEI.) Indicates the carrier vlan packet (Not support the discardingindicator).

ip-dscp Indicates the ip packet.

mpls-exp Indicates the mpls packet.


The value setting depends on the packet type.

C.48 Packet Color

Description

The Packet Color parameter indicates the color that is used to label the packet, which affectsthe forwarding priority of the packet.


This parameter affects the forwarding priority of the packet.



C-39

ValuesValue Range

Red, Yellow, Green


Value Description

Red Indicates the lowest packet forwarding priority.

Yellow Indicates that the packet forwarding priority is betweenGreen and Yellow.

Green Indicates the highest packet forwarding priority.

Configuration GuidelinesThe packet labeled in Green is of the highest packet forwarding priority. The second highestpacket forwarding priority is Yellow, and the lowest packet forwarding priority is Red.

C.49 Packet Loading Time

DescriptionThe Packet Loading Time parameter indicates the time that the PW packet requires to load theTDM frames. That is, the parameter is used to specify the number of the TDM frames that areloaded in the PW packet. The period of the TDM frame is 125 us. If Packet Loading Time is1 ms, then eight TDM frames can be loaded in a PW packet.

Impact on the SystemThe Packet Loading Time parameter affects the end-to-end delay of the CES service. Theconfiguration of the NEs at the two ends should be consistent. Otherwise, the services areunavailable.


OptiX PTN 3900: 125 to 3000with the step length of 125

1000 us


Configuration Guide


Issue 06 (2009-06-01)

Configuration GuidelinesWhen the PW is used to emulate the CES service, this parameter can be set. In addition, thepacketisation buffering time should not exceed the jitter buffer time.ime should not exceed thejitter buffer time.


C.50 Packet Loading Time (us)

DescriptionThe Packet Loading Time (us) parameter indicates the longest wait-to-restore (WTR) time forsetting the ATM concatenation. This parameter is only used for the PW of the ATM type. Thisparameter is used to set the WTR time before the encapsulated ATM cell is transmitted. Whenthe WTR time is due, even if the maximum number of concatenated cells does not achieve, thepacket is transmitted.



100-50000 1000 us

Configuration GuidelinesThe longest WTR time of ATM concatenation is only used for the PW of the ATM type. Thestep length of the parameter is 100 (us), and the value is a multiple of 100 within the value range.

Relationship with Other ParametersWhen the maximum number of concatenated cells is 1, the Packet Loading Time is invalid. Inthis case, the cells are transmitted immediately after they are encapsulated in packets. When themaximum number of the concatenation cells is any value from 2-31, the Packet Loading Timeof concentration can be any value within the valid range.

C.51 Duplicated Policy Name

DescriptionThe Duplicated Policy Name parameter indicates a unique identifier of a policy. This parameterhas the same meaning of the Policy Name parameter.



C-41


You can apply a specified policy to the original policy. As a result, the service scheduling policyof the original policy is changed by duplicating the service scheduling policy of the specifiedpolicy.

Values

The Duplicated Policy Name parameter should contain letters or numbers or both with amaximum length of 64 characters. The characters \ or / are not contained.


For changing the current policy, you can directly duplicate the existed policy that satisfies therequirement to the current policy. In this case, no extra setting is required for the current policy.

C.52 Local Working Status

Description

The Local Working Status parameter indicates the current PW status, and informs the userwhere faults occur.

Values


Value Description

UP Indicates that the link isnormal.

Common Fault -

Attachment Circuit Receive Fault -

Attachment Circuit Transmit Fault -

Attachment Circuit Transmit & Receive Fault -

PSN-facing PW Receive Fault -

Attachment Circuit Receive Fault AND PSN-facing PWReceive Fault

-

Attachment Circuit Transmit Fault AND PSN-facing PWReceive Fault

-

Attachment Circuit Transmit & Receive Fault AND PSN-facing PW Receive Fault

-

PSN-facing PW Transmit Fault -


Configuration Guide


Issue 06 (2009-06-01)

Value Description

Attachment Circuit Receive Fault AND PSN-facing PWTransmit Fault

-

Attachment Circuit Transmit Fault AND PSN-facing PWTransmit Fault

-

Attachment Circuit Transmit & Receive Fault AND PSN-facing PW Transmit Fault

-

PSN-facing PW Transmit & Receive Fault -

PSN-facing PW Transmit & Receive Fault AND AttachmentCircuit Receive Fault

-

PSN-facing PW Transmit & Receive Fault AND AttachmentCircuit Transmit Fault

-

C.53 Test Result

Description

The Test Result parameter indicates the trail information about the link connection from thesource maintenance point to the destination maintenance point during the LT test. If the trailfrom the source maintenance point to the destination maintenance point cannot be obtained, theoperation failure information is reported. If the trail from the source maintenance point to thedestination maintenance point transits the intermediate equipment or destination equipment, theoperation success information is reported.



Values


Operation succeed, Operation failed -

C.54 Policy ID

Description

The Policy ID parameter is used to identify a policy. Unlike the policy names, The policy IDsof different stations may be the same. A policy ID is unique to identify a policy on a per-NEbasis.



C-43



Values

Policy Type Value Range

Port policy 0-100

V-UNI ingress policy 0-2000

V-UNI egress policy 0-2000

PW policy 0-2000

ATM policy 0-1000

QinQ policy 0-2000

WFQ scheduling policy 1-256

Port WRED policy 0-7

Service WRED policy 0-127


None.

C.55 Policy Name

Description

The Policy Name parameter is unique to identify a policy.



Values

The policy name should contain letters or numbers or both with a maximum length of 64characters. The characters \ or / are not supported.


The policy name should be unique.


Configuration Guide


Issue 06 (2009-06-01)

C.56 Member Interface

DescriptionThe Member Interface parameter indicates the PPP member port in the MLPPP group.

ValuesIt is indicated as PPP link slot ID-PPP link sub-slot ID-PPP link port number, such as 23-D12-6(PORT-6).

Value Value Range Default Value

Slot ID Indicates the PPP link slot ID. None.

Sub-slot ID Indicates the PPP link sub-slot ID. None.

Port number Indicates the PPP link port number. None.

C.57 Bearer Type

DescriptionThe Bearer Type parameter indicates the bearers of the Ethernet V-NNI, including the port,PW, and QinQ Link.

Impact on the SystemIn the case of different interconnection modes for different services, the V-NNI is carried bydifferent bearers. If the bearer is a port, the service packets are encapsulated in a physical port,which is considered as a tunnel, and then are transmitted to the remote end. If a PW is the bearer,the service packets are encapsulated in a PW, and then are transmitted to the remote end. If thebearer is a QinQ Link, the service packets are encapsulated in the QinQ Link tunnel, and thenare transmitted to the remote end.


Port, PW, QinQ Link None.


Value Description

PW The bearer is the PW, and the PW index should be specified.



C-45

Value Description

Phy port The bearer is the physical port, and the slot ID, sub-slot ID,and port number should be specified.

QinQ link The bearer is the QinQ tunnel, and the QinQ index should bespecified.


The bearer of the E-LAN service V-NNI can be the PW, port, or QinQ Link.

The bearer of the E-Line service V-NNI can be the PW, port, or QinQ Link.

The bear of the E-AGGR service V-NNI can be the PW.

C.58 Egress Port

Description

The Egress Port parameter specifies the port used when the tunnel enters the network side,including the slot ID, sub-board, and port number, which indicate the information of a certainphysical or logical port.


If the specified egress port of the tunnel is inconsistent with the actual physical connection line,the services carried on the service tunnel are interrupted.

Values

The parameter is indicated as Slot ID-Sub-slot ID-Port number, such as 6-MP-1(PORT-1).

Value Value Range Default Value

Slot ID Indicates the slot ID of the egressport of the tunnel.

None.

Sub-slot ID Indicates the sub-slot ID of the egressport of the tunnel.

None.

Port number Indicates the egress port of thetunnel.

None.


The egress port of the tunnel should be configured according to actual requirements.


Configuration Guide


Issue 06 (2009-06-01)

C.59 Handling Mode

Description

The Handling Mode parameter indicates the handling mode for packets of different colors.


Packets of different colors are handled with different QoS.


Pass, Discard, Remark Green, yellow: PassRed: Discard


Value Description

Pass Indicates transparently transmitting or directly forwarding thepacket.

Discard Indicates discarding the packet.

Remark Indicates remarking the packet with a different color.


When a network congestion occurs or the color of the packet needs adjusting, packets of differentcolors can be configured with different handling modes.

C.60 Handling Mode (Ethernet Unknown Frame)

Description

The Handling Mode (Ethernet Unknown Frame) parameter, which can be set to Discard orBroadcast, is used for the Ethernet unknown frames. The handling modes can be set for theunknown unicast frames and unknown broadcast frames respectively.


The processing of service packets are affected. If this parameter is set to Discard, the unknownpackets in the service are directly discarded.



C-47


Discard, Broadcast Broadcast


Value Description

Discard The unknown frames are discarded.

Broadcast The unknown frames are broadcast.

Configuration GuidelinesBy default, in the case of the Ethernet service, the unknown frames are broadcast. Otherwise,the packets whose MAC address forwarding table items are not detected cannot be forwarded.

C.61 Error Frame Monitor Threshold (frame)

DescriptionThe Error Frame Monitor Threshold (frame) parameter indicates the error frame (in certainperiod) threshold for transmitting messages to inform the opposite end of a fault.



1-4294967295 1 Frame

Configuration GuidelinesEnter a value according to the size of the time window for monitoring error frames, and predictionof error frames.


Configuration Guide


Issue 06 (2009-06-01)

C.62 Error Frame Monitor Window (ms)

DescriptionThe Error Frame Monitor Window (ms) parameter indicates the specified time period formonitoring error frames.



1000-60000, 100 as thespacing

1000 ms

Configuration GuidelinesEnter a value within the range.

C.63 Error Frame Second Threshold (s)

DescriptionThe Error Frame Second Threshold (s) parameter indicates the threshold for the error frametime during the time period for monitoring the error frame seconds. When the error frame secondscross the threshold, the board reports an alarm.



1-time window formonitoring error frameseconds

1 s

Configuration GuidelinesThe threshold should be not more than the time window for monitoring error frame seconds.



C-49


None.

C.64 Error Frame Second Window (s)

Description

The Error Frame Second Window (s) parameter indicates the specified time period within thetime span with error frames.



Values


10-900 60 s


The value should be over the threshold for monitoring error frame seconds.


None.

C.65 Error Frame Signal Periodic Monitor Window (Entries)

Description

The Error Frame Signal Periodic Monitor Window (Entries) parameter indicates the timeperiod specified for monitoring error frame signals.



Values


1-60 1 Entry


Configuration Guide


Issue 06 (2009-06-01)


Enter a value within the range.

C.66 Error Frame Signal Periodic Monitor Threshold(Entries)

Description

The Error Frame Signal Periodic Monitor Threshold (Entries) parameter indicates thethreshold for error frame signals that occur during the time period for monitoring the error framesignals. When the error frame signals cross the threshold, the board reports an alarm.



Values


1-7500000000 1 Entry


Enter a value within the range.

C.67 Error Frame Period Threshold (frame)

Description

The Error Frame Period Threshold (frame) parameter indicates the threshold for error framesthat occur during the time period for monitoring error frames. When the error frames cross thethreshold, the board reports an alarm.



Values


1-time period for monitoringerror frames

1 Frame



C-51

Configuration GuidelinesEnter a value within the range.

Relationship with Other ParametersThe value should be less than the time period for monitoring error frames.

C.68 Error Frame Period Window (frame)

DescriptionThe Error Frame Period Window (frame) parameter indicates the specified number of framesfor monitoring the number of error frames.



Maxpps/10-Maxpps*60 Maxpps Frame

Port Rate Maxpps Value

10 Mbit/s 14880

100 Mbit/s 148800

1000 Mbit/s 1488000

10 Gbit/s 14880000

Configuration GuidelinesEnter a value according to the port rate and by referring to the table.

Relationship with Other ParametersThe value should be higher than the time period threshold for monitoring error frames.

C.69 Enable Traffic Frame Discarding Flag

DescriptionThe Enable Traffic Frame Discarding Flag parameter indicates the cell to be discarded whena network congestion occurs. This parameter can be set in the ATM policy. After this parameter


Configuration Guide


Issue 06 (2009-06-01)

is set, the cells to be discarded in the case of a network congestion are added with discardingflags.



Values


Yes, no No


Value Description

Yes Indicates enabling this function.

No Indicates disabling this function.

C.70 Unidirectional Operation

Description

The Unidirectional Operation parameter indicates the capability of the port to transmit theOAM PDU packets when the receive part of the DTE becomes faulty.



Values




Value Description

Enabled The port can transmit the OAM PDU packets when the receive part ofthe DTE becomes faulty.



C-53

Value Description

Disabled The port cannot transmit the OAM PDU packets when the receive partof the DTE becomes faulty.

C.71 Address Table Specified Capacity

Description

The Address Table Specified Capacity parameter indicates the maximum capacity of the MACaddress forwarding table that can be used by the E-LAN service.


If the number of MAC addresses dynamically learned exceeds the set MAC address tablecapacity, and the items in the address table are not aged, the new MAC address is not learned.In this case, the unknown frames are processed according to the unknown frame processingmode configured by the E-LAN service. If the unknown frame processing is configured asDisCard, the packets with unknown destination MAC address are discarded. If the unknownframe processing is configured as Broadcast, the packets with unknown destination MACaddress are broadcast. If the number of packets with unknown destination MAC address is large,the service bandwidth is affected.


0-65534 512 Piece


Set the capacity of the MAC address table to a proper value according to the number of the NEsin the L2VPN network.

C.72 Address Detection Upper Threshold (%)

Description

The Address Detection Upper Threshold (%) parameter indicates the upper capacity thresholdvalue of the detected MAC address forwarding table. It is indicated in percentage.


When the percentage of the number of dynamic MAC address forwarding tables in the totalcapacity exceeds the upper threshold value, the system reports the FDBSIZEALM_ELAN(ELAN forwarding table exhausted) alarm. After the dynamic MAC address forwarding table


Configuration Guide


Issue 06 (2009-06-01)

is full, the E-LAN service does not learn the unknown unicast packets in the service packets.Hence, the broadcast packets are increased, and the service bandwidth is affected.


80-100 95 %

Configuration GuidelinesThis parameter is valid only for the dynamic MAC address forwarding table. Set the properMAC address detection upper threshold value according to the number of NEs in the L2VPNnetwork.

C.73 Address Detection Lower Threshold (%)

DescriptionThe Address Detection Lower Threshold (%) parameter indicates the lower capacity thresholdvalue of the detected MAC address forwarding table. It is indicated in percentage.

Impact on the SystemThis parameter does not affect the system.

When the percentage of the number of dynamic MAC address forwarding tables to the totalcapacity exceeds the upper threshold value, the system reports the FDBSIZEALM_ELAN(ELAN forwarding table exhausted) alarm. If the number of dynamic MAC address forwardingtables is lower than the address detection lower threshold (%), the system reports that this alarmis cleared.


60-100 90 %

Configuration GuidelinesThis parameter is valid only for the dynamic MAC address forwarding table. Set the properMAC address detection lower threshold value according to the number of NEs in the L2VPNnetwork.



C-55

C.74 Discard Lower Threshold (256 bytes)

DescriptionThe Discard Lower Threshold (256 bytes) parameter indicates that the packet whosemeasurement result is undesirable is discarded during the QoS flow monitoring. The user canset Discard Lower Threshold and Discard Upper Threshold for the queue. If the length ofthe queue is less than Discard Lower Threshold, the packet is not discarded. If the length ofthe queue is between Discard Lower Threshold and Discard Upper Threshold, the weightedrandom early detection (WRED) starts to discard packets randomly. If the length of the queueis more than Discard Upper Threshold, all the packets are discarded.


ValuesFor the parameters in different templates, see Table C-1.

Table C-1 Default threshold for the port WRED policy

PacketColor

Lower Threshold Higher Threshold Discard Rate

Green Port buffer size * (3/6) Port buffer size 100

Yellow Port buffer size * (2/6) Port buffer size * (5/6) 100

Red Port buffer size * (1/6) Port buffer size * (4/6) 100

For the port buffer size of each board, see Table C-2.

Table C-2 Port buffer size of each board for the OptiX PTN 3900

PHB ServiceLevel

Port Buffer Size (256 Bytes)

EX2 EG16/POD41/EFG2

EFF8 ETFC

CS7 12800 1280 320 160

CS6 12800 1280 320 160

EF 12800 1280 320 160

AF4 25600 2560 640 320

AF3 25600 2560 640 320

AF2 25600 2560 640 320


Configuration Guide


Issue 06 (2009-06-01)

PHB ServiceLevel


EX2 EG16/POD41/EFG2

EFF8 ETFC

AF1 25600 2560 640 320

BE 51200 5120 1280 640

Configuration GuidelinesThe length of the queue that can be guaranteed decreases with the decrease in the value ofDiscard Lower Threshold. Discard Upper Threshold must not be less than Discard LowerThreshold.


C.75 Discard Probability (%)

DescriptionThe Discard Probability (%) parameter indicates that the packets are discarded in thisproportion if the length of the queues is between Discard Lower Threshold and Discard UpperThreshold.



1-100 100 %

Configuration GuidelinesNone.

C.76 Discard Upper Threshold (256 bytes)

DescriptionDiscard Upper Threshold (256 bytes) indicates that the packet whose measurement result is"undesirable" is discarded during the QoS flow monitoring. The user can set Discard Lower



C-57

Threshold and Discard Upper Threshold for the queue. When the length of the queue is lessthan Discard Lower Threshold, the packet is not discarded. If the length of the queue is betweenDiscard Lower Threshold and Discard Upper Threshold, the WRED starts to discard packetsrandomly. If the length of the queue is more than Discard Upper Threshold, all the packets arediscarded.


If Discard Upper Threshold is set to 0, all the packets in this queue are discarded and thus allthe services of this queue are interrupted.

Values

For the parameters in different templates, see Table C-3.

Table C-3 Default threshold for the port WRED policy

PacketColor

Lower Threshold Higher Threshold Discard Rate

Green Port buffer size * (3/6) Port buffer size 100

Yellow Port buffer size * (2/6) Port buffer size * (5/6) 100

Red Port buffer size * (1/6) Port buffer size * (4/6) 100

For the port buffer size of each board, see Table C-4.

Table C-4 Port buffer size of each board for the OptiX PTN 3900

PHB ServiceLevel


EX2 EG16/POD41/EFG2

EFF8 ETFC

CS7 12800 1280 320 160

CS6 12800 1280 320 160

EF 12800 1280 320 160

AF4 25600 2560 640 320

AF3 25600 2560 640 320

AF2 25600 2560 640 320

AF1 25600 2560 640 320

BE 51200 5120 1280 640


Configuration Guide


Issue 06 (2009-06-01)

Configuration GuidelinesDiscard Upper Threshold must not be less than Discard Lower Threshold.


C.77 Jitter Compensation Buffering Time

DescriptionJitter Compensation Buffering Time indicates the buffer size in the receive direction. ThePSN is delayed, while the TDM network is plesiochronous. The packet needs to be savedtemporarily so that it can be transmitted to the PDH port smoothly. The buffer size is measuredin time. This parameter can be set when the pseudo wire (PW) is used for the circuit emulationservice (CES).



375-16000, with the step length of 125 8000 us

Configuration GuidelinesThe minimum jitter compensation buffering time is 375 us. This parameter can be set when thepseudo wire (PW) is used for the circuit emulation service (CES).

In addition, the packet loading time should not exceed the jitter compensation buffering time.


C.78 Port Transmit Status

DescriptionThe Port Transmit Status parameter indicates whether the service packets and EFMOAMprotocol packets are allowed to transmit.

Impact on the SystemWhen the port is in the FWD state, it is the normal forwarding state.



C-59

When the port is in the DISCARD state, the service packets and upper layer protocol packets,except for EFMOAM protocol packets, cannot be discarded.

Values


FWD, DISCARD FWD


Value Description

FWD Indicates the normal forwarding state.

DISCARD The service packets and upper layer protocol packets, exceptfor EFMOAM protocol packets, cannot be discarded.


This parameter indicates the query result. No rules are provided for selecting a value.


None.

Related Information

None.

C.79 Port Receive Status

Description

The Port Receive Status parameter indicates whether to extract the service packets andEFMOAM protocol packets.


When the port is in the FWD state, it is the normal forwarding state.

When the port is in other states, service packets and upper layer protocol packets, except forEFMOAM packets, cannot be extracted.


Configuration Guide


Issue 06 (2009-06-01)


FWD, LB, DISCARD FWD


Value Application

FWD Indicates the normal forwarding state.

LB The service packets and upper layer protocol packets, exceptfor EFMOAM protocol packets, cannot be looped back.

DISCARD The service packets and upper layer protocol packets, exceptfor EFMOAM protocol packets, cannot be discarded.

Configuration GuidelinesThis parameter indicates the query result. No rules are provided for selecting a value.



C.80 Port Mode

DescriptionThe Port Mode parameter indicates the port mode in which the port can process packets. ThePort Mode parameter determines the headers of which service packets that can be identifiedand processed by the port.

Impact on the SystemSet the Port Mode parameter only when the port does not carry any service. If the port modedoes not match the service, the service is not available.



C-61

ValuesPort Type Value Range Default

Value

E1 port (D75/D12) Layer 1, Layer 2, Layer 3 Layer 3

Channelized STM-1 port (CD1) Layer 1 Layer 1

ATM port (AD1, ASD1) Layer 2 Layer 2

POS port (POD41) Layer 3 Layer 3

Ethernet port (EG16, ETFC, EFG2, EFF8) Layer 2, Layer 3 Layer 2

Ethernet virtual interface (EOA virtual interface) Layer 2, Layer 3 Layer 3

Ethernet virtual interface (VLAN sub-interface) Layer 3 Layer 3


Value Description

Layer 1 Indicates that the port can identify and process only the physical-layerinformation about the packets.

Layer 2 Indicates that the port can perform the packet encapsulation at the physicallayer and data link layer, but cannot perform the packet encapsulation at thenetwork layer.

Layer 3 Indicates that the port can perform the packet encapsulation at the physicallayer, data link layer, and network layer.

Configuration GuidelinesChange the port mode only when the port does not carry any service.

Relationship with Other ParametersSet the Port Mode parameter according to the required functions of the port. For example, toset the IP address for a port, set Port Mode to Layer 3 for this port.

C.81 Enable Port

DescriptionThe Enable Port parameter sets whether the Ethernet port is usable.


Configuration Guide


Issue 06 (2009-06-01)


When services are available on the Ethernet port, setting this port to disabled interrupts theservices.

Values


Enabled, Disabled. Enabled


Value Description

Enabled The port is usable.

Disabled The port is unusable.


When a port is used for transmitting services, enable this port first.


None.

C.82 Port Priority

Description

The Port Priority parameter indicates the priority of the Ethernet port. If other attributes, suchas the port rate and port working mode, are the same, in the LAG member ports that enable theLACP protocol, the port with a higher priority carries services first. This parameter is invalidfor the LAG (manual LAG, for example) that does not run the LACP protocol.



Values


0-65535 32768



C-63

Configuration GuidelinesThe port priority increases as the value decreases.

To make a port carry services with priority, set the priority of the port to a higher value.

Relationship with Other ParametersIn a LAG, which port has the priority to carry services is jointly determined by Port Priorityand System Priority of the LAG, and is first determined by .

For example, as shown in Figure C-1, the non-load sharing static LAG is created between NEA and NE B.

Figure C-1 Non-load sharing static LAG is created between NE A and NE B

NE A Port 1

Port 2

Port 1

Port 2NE B

LAG a LAG b

Working Link

Protection Link

Each port of LAG a and LAG b meets the requirements of carrying services. System Priorityof LAG a is higher than System Priority of LAG b. In LAG a, Port Priority of port1 is higherthan Port Priority of port2. In LAG b, Port Priority of port2 is higher than Port Priority ofport 1.

In this case, in LAG a, port 1 is the working port, port 2 protects port 1, and port 2 does not sharethe service traffic. The protection relation in LAG b is the same as the protection relation in LAGa, because System Priority of LAG a is higher than System Priority of LAG b. That is, in LAGb, port 1 is the working port, port 2 protects port 1, and port 2 does not share the service traffic,even if Port Priority of port 2 is higher than Port Priority of port1 in LAG b.

Related InformationFor the setting of this parameter, see System Priority.

C.83 Peer IP

DescriptionThe Peer IP parameter indicates the peer node ID that is set for the PW creation.

Impact on the SystemIf this parameter is set incorrectly, creating the dynamic PW fails.


Configuration Guide


Issue 06 (2009-06-01)

ValuesValue Description

Legal IP address The value is an IP address in the dotted decimal notationsystem. The unicast IP address cannot be any one of thefollowing addresses, that is, the 0 address 0.*.*.*, the localloopback address 127.*.*.*, the multicast address224.0.0.0-239.255.255.255, the network address *.*.*.0 orthe broadcast address *.*.*.255.

Configuration GuidelinesWhen the dynamic PW is used for the service, the peer IP address must be consistent with thepeer IP address of the tunnel.

The node IDs of the NEs at the two ends must be legal and unique IP addresses and cannot bethe same as the interface IP addresses of any other NEs.


C.84 Transmitted Packet Length

DescriptionThe Transmitted Packet Length parameter indicates the length of the transmitted loopbackmessage (LBM).



64-1400 64

Configuration GuidelinesThe default value is 64. Packets of different lengths may have different connectivity test results.




C-65

Related Information

None.

C.85 Transmitted Packet Count

Description

The Transmitted Packet Count parameter indicates the number of the transmitted LBMpackets.



Values


1-255 3


The time taken ascends with the number of transmitted packets.


None.

Related Information

None.

C.86 Transmitted Packet Priority (Ethernet Service OAM)

Description

The Transmitted Packet Priority (Ethernet Service OAM) parameter indicates the VLANpriority in the Ethernet service OAM protocol packets transmitted by the equipment.




Configuration Guide


Issue 06 (2009-06-01)


0-7 7


Value 0 indicates the lowest priority, and value 7 indicates the highest priority. By default, value7, the highest priority, is used.


None.

Related Information

None.

C.87 Direction

Description

The Direction parameter indicates whether the PW to be created is unidirectional orbidirectional.




Bidirectional Bidirectional


Value Description

Bidirectional Indicates that the PW is set to the bidirectional mode.


Currently, only the bidirectional mode is supported for the PW.



C-67

C.88 Non-Autonegotiation Flow Control Mode (EthernetPort)

DescriptionIn the case of the flow control, the data traffic that passes through a node or link is adjusted toavoid overload of the node or link.

Set the Non-Autonegotiation Flow Control Mode parameter to specify the flow control modeof an Ethernet port.


ValuesValue Range Default

Value

Disabled, Enable Symmetric Flow Control, Send Only, Receive Only Disabled


Value Description

Disabled The port disables the flow control function (in both the transmit andreceive directions).

Enable SymmetricFlow Control

The port transmits flow control frames and also responds to flowcontrol frames.

Send Only The port only transmits flow control frames.

Receive Only The port only responds to flow control frames.

Configuration GuidelinesSet the flow control mode of interconnected ports according to the flow control requirements.For example, port A and port B are interconnected. To realize the flow control in the receivedirection of port A (avoid congestion at port A), set Non-Autonegotiation Flow ControlMode to Enable Symmetric Flow Control or Send Only for port A, and to Enable SymmetricFlow Control or Receive Only for port B.

Relationship with Other Parametersl When Auto-Negotiation Flow Control Mode and Non-Autonegotiation Flow Control

Mode are set to Enabled at the same time, the flow control mode of the port is determined


Configuration Guide


Issue 06 (2009-06-01)

by the working mode of the port. When the working mode of the port is auto-negotiation,the flow control mode is auto-negotiation. When the working mode of the port is non-autonegotiation, the flow control mode is non-autonegotiation.

l When either Auto-Negotiation Flow Control Mode or Non-Auto-negotiation FlowControl Mode is set to Enabled, the flow control mode of the port is also determined bythe working mode of the port.

– When Auto-Negotiation Flow Control Mode is set to Enabled, if the working modeof the port is auto-negotiation, the flow control mode is auto-negotiation. If the workingmode of the port is non-autonegotiation, the flow control function cannot be realizedon the port.

– When Non-Autonegotiation Flow Control Mode is set to Enabled, if the workingmode of the port is non-autonegotiation, the flow control mode is non-autonegotiation.If the working mode of the port is auto-negotiation, the flow control function cannot berealized on the port.

C.89 Encapsulation Type

Description

The Encapsulation Type parameter sets the link layer encapsulation type of the port, andspecifies the link layer encapsulation type that can be identified by this port.

Values


Null, ATM, PPP, 802.1Q, QinQ For details, see configuration guidelines.


Value Description

Null No link layer is available, or the link layer encapsulation isnot processed.

ATM The ATM encapsulation is identified and processed.

PPP The PPP encapsulation is identified and processed.

802.1Q In the Layer 2 mode, the encapsulation type of the Ethernetport is 802.1Q by default.

QinQ When the Ethernet port is used for QinQ Link, the portattribute should be set to Layer 2, and the encapsulation typeshould be set to QinQ. In addition, QinQ Type Domain ofthe two interconnected Ethernet ports should be set to thesame value.



C-69


1. Currently, the encapsulation type of the Ethernet port, E1 port, POS port, and serial port canbe set.

In addition, the encapsulation type can be switched only when the port does not carry services.

2. In the Layer 2 mode, the encapsulation type of the Ethernet port can be Null, 802.1Q, andQinQ. In the Layer 3 mode, the encapsulation type of the Ethernet port, which is fixed to802.1Q, cannot be set.

3. In the Layer 1 mode, the encapsulation type of the E1 port is fixed to Null. In the Layer 2mode, the encapsulation type of the E1 port is fixed to ATM. In the Layer 3 mode, theencapsulation type of the E1 port is fixed to PPP.

4. The POS port is fixed to the Layer 3 mode, and thus the default encapsulation type is Null.Currently, only the PPP protocol is supported.

5. The serial port is fixed to the Layer 3 mode, and thus the default encapsulation type is Null.Currently, only the PPP protocol is supported.


None.

Related Information

For details, see the Port Mode parameter.

C.90 PIR

Description

The PIR parameter indicates the maximum rate at which the packet is allowed to be transmitted.


If this parameter is set incorrectly, the QoS cannot be guaranteed. If this parameter is set to anexcessively small value, the service flow that exceeds the PIR is discarded. If this parameter isset to 0, the service is unavailable.

Values


OptiX PTN 3900:64-10,000,000

None. kbit/s


Configuration Guide


Issue 06 (2009-06-01)

Configuration GuidelinesValue Description

OptiX PTN 3900:64-10,000,000

The PIR of the PW for OptiX PTN 1900 and OptiX PTN 3900ranges from 64 kbit/s to 10,000,000 kbit/s.The PIR of the PW for OptiX PTN 912 ranges from 64 kbit/sto 100,000 kbit/s.

C.91 Load Sharing Hash Algorithm

DescriptionThe Encapsulation Type parameter indicates the traffic distribution algorithm for differentports in the aggregation group.

Impact on the SystemIf multiple ports in the aggregation group can carry the services, the traffic distribution effectvaries with the Hash algorithms configured. If the Hash algorithm is properly configured, thetraffic on each port is evenly distributed. Otherwise, the traffic is not evenly distributed, and theport bandwidth cannot be fully used.


Automatic, Source MAC, Destination MAC,Source and Destination MACs, Source IP,Destination IP, Source and Destination IP,Source Port Number, Destination PortNumber, Source and Destination PortNumbers, MPLS Label

Automatic


Value Description

Automatic The traffic is distributed among ports according to the source anddestination MACs of the packets.

Source MAC The traffic is distributed among ports according to the sourceMAC of the packets.

Destination MAC The traffic is distributed among ports according to the destinationMAC of the packets.

Source and DestinationMACs

The traffic is distributed among ports according to the source anddestination MACs of the packets.



C-71

Value Description

Source IP The traffic is distributed among ports according to the source IPof the packets.

Destination IP The traffic is distributed among ports according to the destinationIP of the packets.

Source and Destination IP The traffic is distributed among ports according to the source anddestination IP of the packets.

Source Port Number The traffic is distributed among ports according to the sourceport number of the packets.

Destination Port Number The traffic is distributed among ports according to the destinationport number of the packets.

Source and DestinationPort Numbers

The traffic is distributed among ports according to the source anddestination port numbers of the packets.

MPLS Label The traffic is distributed among ports according to the MPLSlabel of the packets.


To evenly distribute the traffic on each port as possible, select a proper Hash algorithm accordingto different packets on the ports.


This parameter is valid only when Load Sharing is set to Non-Sharing.

C.92 Load Sharing

Description

The Load Sharing parameter indicates whether multiple ports are allowed to carry the servicesat the same time when multiple ports in the aggregation group can be used.


In the Non-Sharing mode, one active port and one standby port, which can back up each other,are available. In this case, only one port carries the services.

In the Sharing mode, multiple ports can carry the services at the same time.

When manually configuring the aggregation group, ensure that the load sharing modes at bothends are same.


Configuration Guide


Issue 06 (2009-06-01)


Sharing, Non-Sharing Indicates that the load is shared.


Value Description

Non-Sharing Indicates that only one port carries the services. Only oneslave port can be configured.

Sharing Indicates that multiple ports are allowed to carry the servicesat the same time. A maximum of 15 slave ports can be added.

Configuration GuidelinesWhen manually configuring the aggregation group, configure the load sharing modes at the twoends to the same. Otherwise, the services are interrupted.



C.93 Working Mode

DescriptionSet the Working Mode parameter to set the working mode of the Ethernet port on the board.The Working Mode parameter indicates the maximum transmission rate and communicationmode of a port.

Impact on the SystemIf the working modes of interconnected Ethernet ports are inconsistent, the services are notavailable or have a severe packet loss problem.



C-73

Values


Auto-Negotiation, 10M Half-Duplex, 10MFull-Duplex, 100M Half-Duplex, 100M Full-Duplex, 1000M Half-Duplex, 1000M Full-Duplex, 10G Full-Duplex LAN, 10G Full-Duplex WAN

Auto-NegotiationNOTE

The value is 100mfull for the port of EFF8board


The Auto-Negotiation working mode is recommended. If the communication fails and theworking mode of the port is set to Auto-Negotiation, you need specify the working mode of theport according to the working mode of the interconnected port.

If the working mode of the port is set to any other mode instead of Auto-Negotiation, the workingmode of the interconnected port should be the same. Otherwise, the communication is notavailable.

In the case of equipment interconnection, set the communication modes of the interconnectedports to full-duplex.


None.

Related Information

None.

C.94 Loopback Status (EFMOAM Parameter)

Description

The Loopback Status (EFMOAM Parameter) parameter indicates whether a port is in theloopback status, and, if yes, whether the port is in the Initiate Loopback at Local status orRespond Loopback of Remote status.


Set port loopback to diagnose the link. If a port is in the loopback status, the carried services areinterrupted when the port starts loopback or responds to loopback.

If the EFMOAM detects any failure when the command is issued to release the loopback orwhen the link becomes faulty, the two ports exit the loopback status and the services becomenormal.


Configuration Guide


Issue 06 (2009-06-01)


Initiate Loopback at Local, RespondLoopback of Remote, Non-Loopback

Non-Loopback


Value Description

Initiate Loopback at Local Indicates that the port can transmit services, but cannotreceive services.

Respond Loopback ofRemote

Indicates that the port cannot transmit or receive services, butcan retrace the packets to the opposite port.

Non-Loopback Indicates that the port is not in the loopback status that isstipulated in IEEE 802.3ah.

Configuration GuidelinesIf you issue the command at port A to start remote loopback when the connection between portA and port B is normal, port A is in the Initiate Loopback at Local status and port B is in theRespond Loopback of Remote status.

When you issue the command for port A to release the remote loopback, port A and port Bresume the Non-Loopback status.

Relationship with Other ParametersThe Loopback Status (EFMOAM Parameter) parameter is valid only when the RemoteLoopback Response parameter is set to Enabled.

Related InformationStart the loopback only when the finding succeeds.

C.95 Revertive Mode

DescriptionIn the case of the link aggregation group (LAG) that does not share the load, if both the mainand slave ports meet the requirements for carrying services, the Revertive Mode parameterdetermines whether the port with the smaller port ID carries the services.

If the Revertive Mode parameter is set to Revertive, the port with the smaller port carries theservices. The port ID indicates the numbering of the port on the board. For example, in the caseof the EG16, the 16 GE ports are numbered from 1 to 16.



C-75

If the Revertive Mode parameter is set to Non-Revertive, the port that carries services remainsunchanged.

Impact on the SystemIf the port with the smaller port ID recovers when the Revertive Mode parameter is set toRevertive, the services are switched to this port. During the switching, the services aretransiently interrupted for not more than 500 ms.


Revertive, Non-Revertive Revertive


Value Description

Revertive When both the main and slave ports meet the requirements ofcarrying services, the port with the smaller port ID carries theservices.

Non-Revertive When both the main and slave ports meet the requirements ofcarrying services, the port that carries the services remainsunchanged.

Configuration GuidelinesTo prevent frequent switching and to switch the services only when the service-carried port fails,set the Revertive Mode parameter to Non-Revertive.

To ensure that the port with the smaller port ID carry services whenever the port is fine, set theRevertive Mode parameter to Revertive.

Relationship with Other ParametersThe Revertive Mode parameter is valid only when the Load Sharing parameter is set to Non-Sharing.



Configuration Guide


Issue 06 (2009-06-01)

C.96 Laser Interface Enabling Status

Description

Set the Laser Interface Enabling Status parameter to enable or disable the laser of a physicalport. The Laser Interface Enabling Status parameter determines only whether the lasertransmits the optical signals, but not whether the laser receives optical signals.


When the physical port carries services, disabling the laser interrupts the services carried by theport.




Value Description

Enabled Indicates that the laser of the physical port normally transmits and receivesoptical signals.

Disabled Indicates that the laser of the physical port does not transmit optical signals,but only receives optical signals.


Do not enable or disable the laser unless necessary. When a laser is disabled, the laser stopstransmitting optical signals.


None.

C.97 Laser Transmission Distance (m)

Description

The Laser Transmission Distance (m) parameter indicates the effective distance for which theoptical signals transmitted by the optical module of the laser can travel. Hence, this parameteris a physical attribute of the optical module.



C-77

Impact on the SystemSetting this parameter does not affect the system operation.

ValuesThe value of the Laser Transmission Distance (m) parameter is a number whose unit is meter.



Related InformationRefer to the OptiX PTN 1900&3900 Packet Transport Platform of PTN Series HardwareDescription for specifications on boards.

C.98 Activation Status

DescriptionThe Activation Status parameter indicates whether to send the CC packet. The CC packet refersto service connectivity checking packet.

Impact on the SystemWhen the activation status is "Active", the NE where the maintenance association end point(MEP) is located starts to send the CC packet and the receive end, that is, the NE where theremote maintenance association end point (RMEP) is located checks whether the CC packet isreceived. If the receive end fails to receive the CC packet, the receive end reports correspondingalarms.

For example, if the receive ends fails to receive the CC packet within three cycles, the receiveend reports the LOCV alarm. If the attributes of the received CC packet are inconsistent withthe attributes of the packet in the maintenance association (MA) of the maintenance domain(MD), the receive end reports the Mismerge, Mismatch and other alarms.

When the activation status is "Inactive", the NE where the MEP is does not send any CC packetand the NE where the RMEP is does check for an alarm.


Active, Inactive Active



Configuration Guide


Issue 06 (2009-06-01)

Value Description

Active Indicates that the NE where the MEP is starts to send the CCpacket and the receive end, that is, the NE where the RMEPis checks whether the CC packet is received. If the receive endfails to receive the CC packet, the receive end reportscorresponding alarms.

Inactive Indicates that the NE where the MEP is does not send any CCpacket and the NE where the RMEP is does check for analarm.

Configuration GuidelinesThe activation status is "Active" after the MEP is created on the NE and the service connectivitycan be checked. The activation status can also be set to "Inactive".


Related InformationBefore setting this parameter, obtain the information about the MD, MA and MEP.

C.99 Scrambling Capability (POS Port)

DescriptionSet the Scrambling Capability parameter to determine whether to scramble or descramble thePPP frames of the POS port.

Impact on the SystemWhen the POS port carries services, setting this parameter causes bit error and packet loss.


Enabled, Disabled. Enabled




C-79

Value Description

Enabled Indicates that the PPP packets of the POS port are scrambled at the transmitend and descrambled at the receive end.

Disabled Indicates that the PPP packets of the POS port are not scrambled ordescrambled.

Configuration GuidelinesSet the Scrambling Capability parameter only for the POS port. If the ScramblingCapability parameter is set to Enabled for the POS port that transmits signals, set theScrambling Capability parameter to Enabled for the POS port that receives signals. Otherwise,the services are interrupted.


Related InformationIf you enable the frame scrambling for a POS port, the frame descrambling for the POS port isalso enabled.

C.100 Detection Result

DescriptionThe Detection Result parameter indicates the connectivity of the service flow from the sourceMP to the destination MP.



0, 1 None.


Value Description

0 Indicates that the service connectivity is normal.

1 Indicates that the service connectivity is abnormal.


Configuration Guide


Issue 06 (2009-06-01)


This parameter is used for query only. No rule is specified for selecting a value.


None.

Related Information

None.

C.101 Static MAC Address

Description

The Static MAC Address parameter indicates the packet forward MAC address that is manuallyconfigured for the E-LAN service. This MAC address is not automatically aged. When thedestination MAC address is the same as this MAC address, the packets are directly forwarded.


If the MAC address self-learning function is not enabled for the E-LAN service, and if thedestination MAC address carried with the packets does not match the configured static MACaddress, the services are not available.

Values

Create the static MAC address table.

Service ID


1-4294967294 None.

VLAN ID


1-4094 None.




C-81

Value Description

1-4094 If the E-LAN service is in the IVL mode, you can specify that thepackets are forwarded according to the VLAN and MAC address.

- If the E-LAN service is in the SVL mode, the VLAN learning isnot supported.

MAC Address


00-00-00-00-00-01 to FF-FF-FF-FF-FF-FE(The multicast MAC address similar to *1-**-**-**-**-** is notallowed.)

None.

Configuration GuidelinesThis broadcast MAC address (FF-FF-FF-FF-FF-FF) and the multicast MAC address similar to*1-**-**-**-**-** are not allowed.



C.102 LAG Type

DescriptionThe LAG Type parameter can be set to Manual or Static.

In the case of the manual LAG, the LACP protocol is not enabled. In the case of the static LAG,the LACP protocol is enabled and protocol packets are exchanged. The protocol state machinedetermines whether the port can carry services.

Impact on the SystemAs the LACP protocol is not enabled for the manual LAG, the LAG Type parameter should beset to Manual for the interconnected ports. In addition, the Load Sharing and RevertiveMode parameters should be set as the same for the interconnected ports. Otherwise, the workingports do not belong to the same link and services are interrupted.

If the manual LAG works in the full-duplex mode and a unidirectional fiber cut occurs, theservices are interrupted.


Configuration Guide


Issue 06 (2009-06-01)

When a static LAG is initially created, the services are interrupted until the two ends negotiateand determine a port that can carry the services.


Manual, Static Static


Value Description

Manual The LACP protocol is not enabled. The link status, rate, andduplex mode of a port determine whether the port can carryservices.

Static The LACP protocol is enabled and protocol packets areexchanged. The protocol state machine determines whetherthe port can carry services.

Configuration GuidelinesIf the user does not require the LACP protocol, set the LAG Type parameter to Manual.

If the user requires the LACP protocol and the two ends use the LACP protocol, set the LAGType parameter to Static.



C.103 Control Channel Type

DescriptionSet the Control Channel Type parameter to specify the mode for detecting the PW connectivity.Three modes are available for checking the PW connectivity, that is, control word (CW), routealarm label, and time to live (TTL) label. Currently, the equipment supports only the CW mode.

Impact on the SystemNone.



C-83

Values


CW, None CW


Value Description

None The CW is not supported, that is, the PW connectivity checkis not supported.

CW The CW is supported.


None.


None.

C.104 Control Word (ATM Service)

Description

The Control Word parameter is used to set the usage policy of the PW control word. Based onthe negotiation at the control layer, this parameter is used for the packet sequence test, packetsegmentation and reconstruction. When the Control Word parameter is enabled, the field ofthe four-byte control word is added to the head of packets to be transmitted. This field is usedfor testing packets. This parameter indicates whether the PW enables or disables the controlword function.



Values


No use, must use Depends on the PW type.



Configuration Guide


Issue 06 (2009-06-01)

Value Description

No use Indicates that the control word policy is not used.

Must use Indicates that the control word policy must be used.


When the Control Word parameter is enabled, the setting is valid only when the settings at twoends are consistent.


None.

C.105 Aging Ability

Description

The Aging Ability parameter indicates whether the learned MAC address is aged in a periodafter the MAC address is learned.

The MAC address aging helps increase the overall resource utilization and avoid that certainpackets use the system resources all the time.


When an MAC address is aged, the port clears the original unicast forward trails and broadcaststhe received packets whose destination MAC address is the aged MAC address. The portforwards these packets only when the port learns this aged MAC address again.

Values




Value Description

Enabled The MAC address is to be aged.

Disabled The MAC address is not to be aged.



C-85


If certain MAC addresses are not used within a period after the aging function is enabled, theseMAC address are aged. Then, the packets with these MAC addresses are broadcast until theunicast is formed.


None.

Related Information

None.

C.106 Aging Time (min)

Description

Set the Aging Time (min) parameter to set the aging time of the learned MAC address. TheAging Time (min) parameter indicates that the MAC address is automatically aged after thetiming is set.


When the Aging Time (min) parameter is reset, the MAC addresses learned before the resettingremains aged according to the original aging time, and the MAC addresses learned after theresetting are aged according to the current aging time. When the aging time is up, the originalunicast E-LAN services are broadcast.

Values


1-640 5 Minute as the unit and one as thespacing.


Set the aging time of MAC addresses according to the user requirements. The minimum time isone minute.


None.

Related Information

None.


Configuration Guide


Issue 06 (2009-06-01)

C.107 Connection Type

DescriptionThe connection types are classified into the VPC and VCC.

The virtual path connection (VPC) indicates that only the value of the virtual path identifier(VPI) is changed and that the value of virtual channel identifier is unchanged during theexchange. During the VPC configuration, only the VPI needs to be configured and the VCI doesnot need to be configured (The VCI is invalid). For the VPC, every connection can carry allservices with the same VPI, including different VCI services with the same VPI. The ATMservice on the PTN equipment is static. Hence, the VPC parameter is replaced by the PVPparameter on the T2000.

The virtual channel connection (VCC) indicates that an ATM connection is identified by botha VPI and a VCI. The VPI and VCI of an ATM connection can be changed during the exchange.Thus, both the VPI and VCI of an ATM need to be configured. For the VCC, every connectioncan carry the service that is identified by both the VPI and VCI. The ATM service on the PTNequipment is static, so the VPC parameter is replaced by the PVP parameter on the T2000.



PVP, PVC None.


Value Description

PVP Indicates that every connection can carry all services with the sameVPI, including different VCI services with the same VPI.

PVC Indicates that every connection can only carry a service that isidentified by a unique VPI and VCI.

Configuration GuidelinesPVP: To converge the services with the same VPI to one port, set the connection type to VPC.

PVC: To transmit a single service that is identified by a unique VPI and VCI, set the connectiontype to VCC.

As shown in the following figure, both the PVP and PVC are virtual and the PVC is containedin the PVP. If you choose to configure a VCC, the VCC indicates the smaller channel while the



C-87

VPC indicates the bigger channel. All the services in this virtual channel of this virtual path canbe transmitted.


Once a service is created, its connection type cannot be changed.

Related Information

None.

C.108 Enable Differential Delay

Description

Set the Enable Differential Delay parameter to set the delay detection for the MP group. Thisparameter is valid only for the E1 link.


If a member link has excessive delay after the delay detection is enabled, this link does notperform the data packet slicing and the MP_DELAY alarm is reported. In this case, thebandwidth for the MP group decreases. The reduced bandwidth is the bandwidth for this memberlink, that is, 2 Mbit/s.

Values




None.


None.


Configuration Guide


Issue 06 (2009-06-01)


C.109 Link Event Notification

DescriptionThe Link Event Notification parameter determines whether the local end sends the link eventnotification packets to the remote end when the local end detects that the bit errors cross thethreshold.





Value Description

Enabled Indicates that the local end is capable of sending the link eventnotification packets to the remote end.

Disabled Indicates that the local end is not capable of sending the linkevent notification packets to the remote end.

Configuration GuidelinesIf the local end need send the link event notification packets to the remote end, set the LinkEvent Notification parameter to Enabled.

If the local end need not send the link event notification packets to the remote end, set the LinkEvent Notification parameter to Disabled.

C.110 Traffic Classification Bandwidth Sharing

DescriptionSet the Traffic Classification Bandwidth Sharing parameter to enable or disable the trafficclassification bandwidth sharing.

Flow Classification of V-UNI Ingress Policy includes the preset Committed InformationRate. When packets on multiple V-UNIs that use this policy match this Flow Classification (in



C-89

other words, flows that match this Flow Classification are available on each V-UNI), if TrafficClassification Bandwidth Sharing is enabled, the total bandwidth of these flows is restrainedby the CIR set by Flow Classification. If Traffic Classification Bandwidth Sharing isdisabled, on each V-UNI, the flows that match Flow Classification are restrained by the CIRset by Flow Classification.


None.

Values




Value Description

Disabled It indicates that the traffic classification bandwidth sharing isdisabled.

Enabled It indicates that the traffic classification bandwidth sharing isenabled.


This parameter is set according to service requirements.

For example, packets on multiple V-UNIs that use a certain V-UNI Ingress Policy match FlowClassification of this policy (in other words, flows that match this Flow Classification areavailable on each V-UNI). In addition, the service packets of these flows have the same servicefeatures, such as the same destination IP address. In this case, if these service packets need sharethe CIR bandwidth set in Flow Classification of this policy, set Traffic ClassificationBandwidth Sharing to Enabled.


When configuring Flow Classification of V-UNI Ingress Policy, set Bandwidth Limit toEnabled. In addition, the CIR of Flow Classification should be configured. In this case, TrafficClassification Bandwidth Sharing is valid.

Related Information

For the setting of this parameter, see Traffic Classification Rule.


Configuration Guide


Issue 06 (2009-06-01)

C.111 Traffic Classification Rule

Description

The Traffic Classification Rule parameter indicates the rules for classifying service packets.

The necessary parameters should be set for Traffic Classification Rule, that is, Match Type(required), Logical Relation Between Matched Rules (required when two or more trafficclassification rules are available for one flow), Match Value (required), and Wilcard (optional).



Values

Set the traffic classification rule in the following formats:

[Match Type : Match Value : Wilcard]

And Logical Relation Between Matched Rules (the matched packets should meet all the trafficclassification rules)

[Match Type : Match Value : Wilcard] & [Match Type : Match Value : Wilcard] &...& [MatchType : Match Value : Wilcard]

Or Logical Relation Between Matched Rules: (the matched packets should meet one of thetraffic classification rule)

[Match Type : Match Value : Wilcard] / [Match Type : Match Value : Wilcard] /.../ [MatchType : Match Value : Wilcard]


The traffic classification rules are applicable only to the port policy or V-UNI ingress policy.

The character string of the match rule (match type, match value, and wilcard included) cancontain a maximum of 128 bytes.


None.

Related Information

Currently, the equipment cannot identify the IPv6 packets.

For details on how to set this parameter, see the description of the Match Type, MatchValue, Wilcard, and Logical Relation Between Matched Rules parameters.



C-91

C.112 Name

Description

Set the Name parameter to set a name for the physical port or virtual port.



Values

The port name should contain characters and numbers. The port name can have a maximum of64 characters.


None.


None.

C.113 Default Packet Relabeling Color

Description

The Default Packet Relabeling Color indicates the color that the NE sets to the user packetson the V-UNI side by default.

On a PTN NE, the packet color indicates the priority for discarding the packet. The packet colorsare red, yellow, and green. The red packet has the highest discard priority, and thus is discardfirst in the case of congestion. The green packet has the lowest discard priority. The yellowpacket has the middle discard priority.


Values


Red, Yellow, Green, None Green



Configuration Guide


Issue 06 (2009-06-01)

Value Description

Red By default, the user packets on the V-UNI side are set as red.

Yellow By default, the user packets on the V-UNI side are set asyellow.

Green By default, the user packets on the V-UNI side are set asgreen.

None. By default, the priority of the user packets on the V-UNI sideare set according to the mapping relation of the DS domain.

Configuration GuidelinesThe user packets of a higher priority should be marked green. The user packets of a lower priorityshould be marked red. The user packets of a medium priority should be marked yellow.

Relationship with Other ParametersIf a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI is markedaccording to Default Packet Relabeling Color. If the V-UNI ingress policy is used, the packetsthat do not match the Traffic classificationof this policy should be marked according to DefaultPacket Relabeling Color.

C.114 Logical Relation Between Matched Rules

DescriptionWhen multiple traffic classification rules are set for a flow, set the Logical Relation BetweenMatched Rules parameter to specify the logical relations among these traffic classification rules.



And, or And


Value Description

And The packet matches the flow only when the packet matcheseach traffic classification rule.



C-93

Value Description

Or The packet matches the flow when the packet matches one ofthe traffic classification rules.


Relationship with Other ParametersBefore setting the Logical Relation Between Matched Rules parameter, set the TrafficClassification Rule correctly.

C.115 Match Type

DescriptionEach data packet has many feature values such as the IP address, MAC address, and portnumber. These feature values can be considered as match types among the traffic classificationrules.



Source IPDestination IPSource MAC AddressDestination MAC AddressProtocol TypeSource PortDestination PortICMP Packet TypeDSCP ValueIP-Precedence ValueCVlan IDCVlan prioritySVlan IDSVlan priorityDEI

None.


Configuration Guide


Issue 06 (2009-06-01)


CVlan IDCVlan prioritySVlan IDSVlan priority

None.


Value Description

Source IP The source IP address is matched.The traffic classification rule that the source IP address matches is in theformat of [Source IP : Source IP Value : Wilcard].For example: [Source IP : 192.168.1.1 : 0.0.0.255].

Destination IP The destination IP address is matched.The traffic classification rule that the destination IP address matches isin the format of [Destination IP : Destination IP Value : Wilcard].For example, [Destination IP : 192.168.1.2 : 0.0.0.0].

Source MACAddress

The source MAC address is matched.The traffic classification rule that the source MAC address matches isin the format of [Source MAC Address : Source MAC Address Value :Wilcard].For example, [Source MAC Address : 00-e0-fc-54-aa-59 :00-00-00-00-00-00].

Destination MACAddress

The destination MAC address is matched.The traffic classification rule that the destination MAC address matchesis in the format of [Destination MAC Address : Destination MACAddress Value : Wilcard].For example, [Destination MAC Address : 00-e0-fc-54-ab-59 :00-00-00-00-00-00].

Protocol Type The protocol type is matched.The traffic classification rule that the protocol type matches is in theformat of [Protocol Type : Protocol Type Value].For example, [Protocol Type : icmp].

Source Port The source port is matched (available when the protocol type is TCP andUDP).The traffic classification rule that the source port matches is in the formatof [Source Port : Source Port Value : Wilcard].For example, [Source Port : 23 : 23].



C-95

Value Description

Destination Port The destination port is matched (available when the protocol type is TCPand UDP).The traffic classification rule that the destination port matches is in theformat of [Destination Port : Destination Port Value : Wilcard].For example, [Destination Port : 80 : 80].

ICMP PacketType

The ICMP packet type is matched (available when the protocol type isICMP).The traffic classification type that the ICMP packet type matches is inthe format of [ICMP Packet Type : ICMP Packet Type Value].For example, [ICMP Packet Type : echo].

DSCP Value The DSCP value is matched.The traffic classification rule that the DSCP value matches is in theformat of [DSCP Value : Value of DSCP : Wilcard].For example, [DSCP Value : 7 : 7].

IP-PrecedenceValue

The IP-Precedence Value is matched.The traffic classification rule that the IP-precedence value matches is inthe format of [IP-Precedence Value : Value of IP-Precedence : Wilcard].For example, [IP-Precedence Value : 6 : 6].

CVlan ID The CVlan ID is matched.The traffic classification rule that the CVlan ID matches is in the formatof [CVlan ID : CVlan ID Value : Wilcard].For example, [CVlan ID : 100 : 120].

CVlan priority The CVlan priority is matched.The traffic classification rule that the CVlan priority matches is in theformat of [CVlan priority : CVlan priority Value : Wilcard].For example, [CVlan priority : 4 : 6].

SVlan ID The SVlan ID is matched.The traffic classification rule that the SVlan ID matches is in the formatof [SVlan ID : SVlan ID Value : Wilcard].For example, [SVlan ID : 100 : 120].

SVlan priority The SVlan priority is matched.The traffic classification rule that the SVlan priority matches is in theformat of [SVlan priority : SVlan priority Value : Wilcard].For example, [SVlan priority : 5 : 6].

DEI The DEI is matched.The traffic classification rule that the DEI matches is in the format of[DEI : DEI Value].For example, [DEI : 1].


Configuration Guide


Issue 06 (2009-06-01)


To process different service packets accordingly (make ACL for packets, apply differentscheduling priorities or discard polices), perform traffic classification for the packets accordingto the varied feature values of packets. The feature value that can distinguish the packetsaccording to requirements is adopted to classify the packets.

For example, user A and user B access to a port. The PTN network should provide services ofdifferent QoS for the two users. Hence, the packets of user A and user B should be distinguishedat the port.

The analysis shows the following:

In the case of the service packets of user A, the prefix of the source IP address is 192.168.1.0and the subnet mask is 255.255.255.0.

In the case of the service packets of user B, the prefix of the source IP address is 192.168.2.0and the subnet mask is 255.255.255.0.

The packets of user A can be distinguished from the packets of user B according to the sourceIP address. Hence, two traffic classification rules should be set at the port.

[Source IP : 192.168.1.0 : 0.0.0.255]

[Source IP : 192.168.2.0 : 0.0.0.255]


None.

Related Information

For the setting of this parameter, see the description of the Traffic Classification Rule, MatchValue, Wilcard, and Logical Relation Between Matched Rules parameters.

C.116 Match Value

Description

The Match Value parameter indicates the value set for a specific match type among the trafficclassification rules. If certain bits of the match type value (source IP address, for example) areconsistent with the mapping bits of the match value of the traffic classification rule, the packetsmatch with the traffic classification rule.



Values




C-97

Value Description

Source IP Indicates the source IP value when the source IP address matchesthe traffic classification rule.For example: 192.168.1.1

Destination IP Indicates the destination IP value when the destination IP addressmatches the traffic classification rule.For example: 192.168.2.1

Source MAC Address Indicates the source MAC address value when the source MACaddress matches the traffic classification rule.For example: 00-0f-ef-54-aa-00


Indicates the destination MAC address value when the destinationMAC address matches the traffic classification rule.For example: 00-0f-ef-54-ab-00

Protocol Type Indicates the protocol type value when the protocol type matches thetraffic classification rule.Protocol type range: tcp, udp, icmp, igmp

Source Port Indicates the source port value when the source port (available whenthe protocol type is TCP and UDP) matches the traffic classificationrule.The source port value ranges from 0 to 65535.

Destination Port Indicates the destination port value when the destination port(available when the protocol type is TCP and UDP) matches thetraffic classification rule.The destination port value ranges from 0 to 65535.


Configuration Guide


Issue 06 (2009-06-01)

Value Description

ICMP Packet Type Indicates the ICMP packet type value when the ICMP packet type(available whether protocol type is ICMP) matches the trafficclassification rule.Value range of ICMP packet type:echoecho-replyfragmentneed-DFsethost-redirecthost-tos-redirecthost-unreachableinformation-replyinformation-requestnet-redirectnet-tos-redirectnet-unreachableparameter-problemport-unreachableprotocol-unreachablereassembly-timeoutsource-quenchsource-route-failedtimestamp-replytimestamp-requestttl-exceeded

DSCP Value Indicates the value of DSCP when the DSCP value matches thetraffic classification value.The DSCP value ranges from 0 to 63.

IP-Precedence Value Indicates the value of IP-Precedence when the IP-Precedence valuematches the traffic classification value.The IP-Precedence value ranges from 0 to 7.

CVlan ID Indicates the value of CVlan ID when the CVlan ID matches thetraffic classification value.The CVlan ID value ranges from 0 to 4095.

CVlan priority Indicates the value of CVlan priority when the CVlan prioritymatches the traffic classification value.The CVlan priority value ranges from 0 to 7.

SVlan ID Indicates the value of SVlan ID when the SVlan ID matches thetraffic classification value.The SVlan ID vale ranges from 0 to 4095.



C-99

Value Description

SVlan priority Indicates the value of SVlan priority when the SVlan prioritymatches the traffic classification value.The SVlan priority value ranges from 0 to 7.

DEI Indicates the value of DEI when the DEI matches the trafficclassification value.The DEI value can be 0 or 1.


The match value of each match type should be within the valid range.


None.

Related Information

For details on how to set this parameter, see the description of the Traffic ClassificationRule, Match Type, Wilcard, and Logical Relation Between Matched Rules parameters.

C.117 Default Forwarding Priority

Description

The Default Forwarding Priority parameter indicates the forwarding priority that the NE setsto the user packets on the V-UNI side by default.

The OptiX PTN NE forwards and schedules packets according to the priorities of the packets.The forwarding priorities supported by the OptiX PTN NE include CS7, CS6, EF, AF4, AF3,AF2, AF1, and BE (arranged from the highest priority to the lowest).


The system running is not affected.


BE, AF1, AF2, AF3, AF4, EF, CS6, CS7,NONE

BE



Configuration Guide


Issue 06 (2009-06-01)

Value Description

BE By default, the user packets on the V-UNI side are set to BE.

AF1 By default, the user packets on the V-UNI side are set to AF1.




CS6 By default, the user packets on the V-UNI side are set to CS6.

CS7 By default, the user packets on the V-UNI side are set to CS7.

NONE The priority of the user packets on the V-UNI side are set according to themapping relation in the DS domain.

Configuration GuidelinesCS7: Indicates the highest forwarding priority, for delivering the control packets (very importantprotocol packets) in the network.

CS6: Indicates the priority that is lower than CS7, for delivering the control packets (importantprotocol packets) in the network.

EF: Indicates the expedited forwarding priority that is lower than CS6, for the low delay services(for example, voice services).

AF4: Indicates the assured forwarding priority 4, whose forwarding priority is lower than EF.

AF3: Indicates the assured forwarding priority 3, whose forwarding priority is lower than AF4.



BE: Indicates the best effort forwarding priority that is the lowest forwarding priority, for theservices without QoS in the network.

Relationship with Other ParametersIf a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI areforwarded according to Default Forwarding Priority. If the V-UNI ingress policy is used, thepackets that do not match the Traffic classificationof this policy are forwarded according toDefault Forwarding Priority.

C.118 Coloration Mode

DescriptionCommitted access rate (CAR): When the packet rate is lower than the minimum allowed accessrate, the packets are marked green. When the packet rate is higher than the maximum allowed



C-101

access rate, the packets are marked red. When the packet rate is between the minimum allowedaccess rate and maximum allowed access rate, the packets are marked yellow.

The Coloration Mode parameter sets the coloration mode of a certain Traffic Classification.Two coloration modes are available, that is, Color Blindness and Color Sensitive.

Impact on the SystemThe system running is not affected.


Color Blindness, Color Sensitive Color Blindness


Value Description

Color Blindness Indicates the color blindness mode. The CAR is directlyperformed for the user packets, which are marked accordingto the CAR result.

Color Sensitive Indicates the color sensitive mode. The CAR is performed onthe packets, and then compare the CAR result with the colorof the packet. Then, select the color that is darker to mark thepackets. The darkness of the packet colors descends in thesequence of red, yellow, and green.

Configuration GuidelinesAfter the upstream DS domain marks the service packets accessed into the local DS domain, onthe ingress node of the local DS domain, if the coloration result of the upstream DS domain needbe considered, Color Sensitive is applicable to the Traffic Classification that matches theservice packets. Otherwise, Color Blindness is applicable.

Relationship with Other ParametersWhen the service packets from the upstream DS domain enter the ingress node of the local DSdomain, the color of packets is obtained according to the mapping relation between the packetpriority and color, which is defined in the local DS domain mapping relation. If ColorationMode is set to Color Sensitive, the color of service packets from the upstream DS domain shouldbe restored. Ensure that the mapping relations of the service packets in the upstream DS domainand local DS domain are consistent.


Configuration Guide


Issue 06 (2009-06-01)

C.119 Uplink Policy

Description

The Uplink Policy parameter indicates the traffic policy ID for the ATM connection in thespecific direction. For example, if the service for this connection is of the UNIs-NNI type, thespecific direction is UNI-to-PW; if the service for this connection is of the UNI-UNI type, thespecific direction is from the source UNI port to sink UNI port.


In the case of an ATM connection, the uplink policy determines the traffic policy in a specificdirection, such as the priority scheduling, leaky bucket processing mechanism, shapingprocessing, and network-side priority scheduling. If you select an improper uplink policy,packets may be lost or the QoS may not be ensured for services of higher priorities.

Values

Value Description

1-1024 Select one from the created policies and enter the index.


The uplink policy affects the traffic parameters and QoS parameters in the specific direction ofthe ATM connection. In addition, the network QoS sets the forward priority according to theuplink policy. Select a proper ATM policy according to the features of the data carried by theATM connection. In the case of the services that have high transmission quality requirements,select the ATM policy that ensures the transmission quality with priority.


Make sure that the entered index indicates an existing ATM policy.

Related Information

None.

C.120 Clock Mode

Description

Set the Clock Mode parameter to set the clock mode of the CES service. The Clock Modeparameter indicates whether the clocks of the PDH/SDH services accessed at both ends aresynchronous.



C-103


The clock mode setting affects the synchronization of the PDH/SDH services at both ends. Ifthe settings at both ends do not indicate that the service clocks are synchronous, alarms such asthe bit error alarms are generated for the CES service. The clock mode setting should be basedon the networking planning with respect to the clock synchronization.

Values


External Clock Mode, Adaptive Clock Mode External Clock Mode


Value Description

External Clock Mode Indicates that the clock of the CES service uses the system clockand thus is synchronous with the clock of the local NE.

Adaptive Clock Mode Indicates that the clock extracted from the received servicepackets in the MEN network is used as the clock for the CESservice. In this way, the clock of the CES service is synchronouswith the service clock of the opposite NE.


Currently, only the external clock mode is supported on the PTN equipment.


None.

Related Information

None.

C.121 Clock Mode (PDH/SDH Port)

Description

The Clock Mode parameter indicates whether the PDH/SDH port uses the internal clock or theline recovery clock as the working clock.


None.


Configuration Guide


Issue 06 (2009-06-01)

Values


Master, Slave Master


Value Description

Master Indicates that the port uses the internal clock as the working clock.

Slave Indicates that the port uses the line recovery clock as the working clock.


None.


None.

Related Information

Perform self-loop with a fiber for the POS port during the test (connect the transmit and receiveports of the same interface with a fiber directly). If the Clock Mode parameter is set to Slave,services are interrupted.

C.122 Split Horizon Group

Description

The Split Horizon Group parameter indicates a special group configured to isolate thecommunication of each member port. In the case of a split horizon group, the member portsshould not communicate with each other.


The member ports of a split horizon group do not communicate with each other.

Values

Create a split horizon group.

Service ID



C-105


1-4294967294 None.

Split Horizon Group ID


1 None.

Split Horizon Group Member


Slot number - board - port number - VLANs None.

Selectable Interface



Selected Interface


Slot - board - port - VLANs None.





Configuration Guide


Issue 06 (2009-06-01)

C.123 Split Horizon Group ID

Description

The Split Horizon Group ID parameter identifies the split horizon group.



Values



1 None.


None.


None.

Related Information

None.

C.124 Split Horizon Group Member

Description

The Split Horizon Group Member parameter indicates the logical port member in a splithorizon group.


The member ports added to the same split horizon group cannot communicate with each other.

Values

Service ID



C-107


1-4294967294 None.



1 None.

Split Horizon Group Member






C.125 Sink Interface Type

DescriptionSet the Sink Interface Type parameter to set the sink interface type of the VLAN switchingtable for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Impact on the SystemSet the sink interface type of the E-AGGR service same as the opposite logical interface type.Otherwise, the E-AGGR service is not available.


V-UNI, V-NNI None.


Configuration Guide


Issue 06 (2009-06-01)


Value Description

V-UNI Indicates that the sink interface is a V-UNI interface.

V-NNI Indicates that the sink interface is a V-NNI interface.


The logical interface type of the sink interface of the VLAN switching table for the E-AGGRservice can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, shouldbe of the same type.


None.

Related Information

None.

C.126 Sink Node

Description

One PW provides the emulation connection from the local NE to the opposite NE. This parameteridentifies the opposite NE of the PW, that is, the node ID of the opposite NE.


When the PW is dynamically created, this parameter indicates that a PW from the local NE toan NE at a specified opposite end is created. If this parameter is invalid or incorrect, the PWcreation fails, the PW creation succeeds but cannot be up, or the PW is connected to an incorrectNE.

Values

The IP address of the opposite NE of the PW, that is, the node ID of the remote NE.


The value should be a unicast IP address, and thus the following IP addresses are not applicable.

l All "0"s address (0.*.*.*)

l All "1"s address (255.255.255.255)

l Local computer loopback address (127.*.*.*)

l Multicast address (224.0.0.0-239.255.255.255)



C-109

l Reserved address (240.0.0.0-255.255.255.255)

l Network address (NE number field: all "0"s)

l Broadcast address (NE number field: all "1"s)

l Network address (network number field: all "0"s)

C.127 Destination Maintenance Point MAC Address

Description

The Destination Maintenance Point MAC Address parameter indicates the MAC address ofthe port where the maintenance point (MP) is located.



Values


Any valid destination unicast MAC address None.


Indicates the MAC address of the port where the destination MP is located.


None.

Related Information

None.

C.128 Used Port

Description

The Used Port parameter indicates the optical interface on the CD1 where the serial port isavailable.




Configuration Guide


Issue 06 (2009-06-01)


Example: 5-MP1-1-CD1-1(PORT-1) None.




C.129 Hop Count

DescriptionThe hop count, also called time to live (TTL), is carried with the OAM packets. The HopCount parameter indicates the connection from the response MP to the source MP. On the trailfrom the source MP to the destination MP, the hop count for the packets decreases by one whenthe packets pass through each maintenance intermediate point (MIP). For example, the packetspass through one MIP and reach the response MP, the returned hop count is 1. The maximumvalue of the Hop Count parameter is 64. If the packets pass through 64 MPs and fail to reachthe response MP, the OAM packets are discarded. In this case, value "/" is returned.



1-64, "/" "/"

Configuration GuidelinesThe Hop Count parameter cannot be set. When the loopback test (LT) is complete, a value isreturned. When the OAM packets pass through 64 MPs and fail to reach the response MP, the"/" value is returned.




C-111


C.130 Wildcard

DescriptionThe Wildcard parameter indicates that the packets need match only a portion of the matchvalues. The number of digits of the wildcard is consistent with the number of digits of the matchvalue. After the wildcard is converted to the binary format, digit 0 in the match value should bematched, but digit 1 need not be considered. For example, if the Match Type is Source IP, thematch value is 192.168.1.100. In this case, if the set wildcard is 0.0.0.255, it indicates that allthe packets whose source IP address starting from 192.168.1. comply with the flow classificationrule.

When the wildcard is set to all "0"s, it indicates that the packets should strictly match the matchvalue.

In the wildcard, digit 0 indicates the digit in the Match Type (for example, Source IP) that theuser need consider. In the user packets, if the value of the digit in the Match Type (for example,Source IP) that the user need consider is equal to the value of the corresponding digit in thematch value. In this case, the user packets match the flow classification rule. Otherwise, the userpackets do not match the flow classification rule.

The digits of the wildcard, user packet match type value, and match type value indicate the digitsafter the values of the wildcard, user packet match type value, and match type are converted tothe binary format.


ValuesThe following table lists the description of each value.

Match Type Description

Source IP Indicates the wildcard value when the source IP address matches.For example, 0.0.0.255.

Destination IP Indicates the wildcard value when the destination IP addressmatches. For example, 0.0.255.255.

Source MAC Address Indicates the wildcard value when the source MAC addressmatches.For example, 00-00-00-00-00-ff.


Indicates the wildcard value when the destination MAC addressmatches.For example, 00-00-00-00-0f-ff.


Configuration Guide


Issue 06 (2009-06-01)

Match Type Description

Protocol Type Indicates no wildcard.

Source Port Indicates the wildcard value when the source port matches.Value range: 0-65535.

Destination Port Indicates the wildcard value when the destination port matches.Value range: 0-65535.

ICMP Packet Type Indicates no wildcard.

DSCP Value Indicates the wildcard value when the DSCP value matches.Value range: 0-63.

IP-Precedence Value Indicates the wildcard value when the IP-Precedence valuematches.Value range: 0-7.

CVlan ID Indicates the wildcard value when the CVlan ID matches.Value range: 0-4095.

CVlan priority Indicates the wildcard value when the CVlan priority matches.Value range: 0-7.

SVlan ID Indicates the wildcard value when the SVlan ID matches.Value range: 0-4095.

SVlan priority Indicates the wildcard value when the SVlan priority matches.Value range: 0-7.

DEI Indicates no wildcard.

Configuration GuidelinesThe wildcard value of each match type should be within its own valid range. When the wildcardis set to all "0"s, it indicates that the packets should strictly match the match value.


Related InformationFor details on how to set this parameter, see the description of the Traffic ClassificationRule, Match Type, Match Value, and Logical Relation Between Matched Rules parameters.



C-113

C.131 Maintenance Domain Level

Description

The Maintenance Domain Level parameter indicates the level of the maintenance domain(MD). The MD level restricts the usage scope of the OAM.


In one MD, the OAM packets at the same MD level can be normally transmitted and received.The OAM packets at a higher MD level are not processed, but are transparently transmitted. TheOAM packets at a lower MD level are directly discarded.

Values


0-7 4

The following table lists the description of each value. You can also define the maintenancescope for an MD level as required.

Value Description

0 Customer

1 Customer

2 Customer

3 Service Provider

4 Service Provider

5 Operator

6 Operator

7 Operator


"0" indicates the lowest MD level and "7" the highest MD level. The parameter level definesthe maintenance scope of the OAM operations.


None.


Configuration Guide


Issue 06 (2009-06-01)

Related Information

Before setting this parameter, obtain the information about the MD.

C.132 Tail Drop Threshold (256bytes)

Description

The Tail Drop Threshold (256bytes) parameter sets the packet discarding threshold ofscheduling queue. When the buffer space used by all the packets in the queue exceeds the taildrop threshold, all the subsequent packets are discarded.


If the tail drop threshold is set to 0, the packets cannot pass through this queue, and the servicesare interrupted.

Values

The following table lists the trail drop threshold of the port policy.


0-960 960 256 bytes

The following table lists trail drop threshold of the service policy, including V-UNI ingresspolicy, V-UNI egress policy, PW policy, and QinQ policy.


0-4095 4095 256 bytes


If the tail drop threshold is set to a bigger value, more packets can be buffered, and the packetloss is decreased. The service delay, however, is increased. If the tail drop threshold is set to asmaller value, less packets can be buffered, and the packet loss is increased. The service delay,however, is decreased.


When you configure the port policy, only one of Tail Drop Threshold and Port WREDPolicy can be configured.

When you configure V-UNI ingress policy, V-UNI egress policy, PW policy, or QinQ policy,only one of Tail Drop Threshold and Service WRED Policy can be configured.



C-115


C.133 Unknown Frame Processing

DescriptionThe Unknown Frame Processing parameter indicates how to process the unknown frames inthe service packets. In the case of the E-LAN service packets, the frames whose MAC addressmatches neither the static MAC address configured by the user nor the self-learned dynamicMAC address are called unknown packets.

If you set the Unknown Frame Processing parameter to Broadcast, the unknown frames arebroadcast in the E-LAN service. If you set the Unknown Frame Processing parameter toDiscard, the unknown frames are discarded.

Impact on the SystemIn this case, the E-LAN service may be not available if the E-LAN service is not configuredwith any static MAC address.


Broadcast, Discard Broadcast


Value Application

Broadcast Indicates that the unknown packets are broadcast in the E-LAN service.

Discard Indicates that the unknown frames are discarded in the E-LANservice.

Configuration GuidelinesIf the E-LAN service is not configured with any static MAC address, set the Unknown FrameProcessing parameter to Broadcast. If the E-LAN service is configured with the static MACaddress and the unknown frames need not be processed, set the Unknown Frame Processingparameter to Discard.



Configuration Guide


Issue 06 (2009-06-01)

Related Information

None.

C.134 Location

Description

The Location parameter indicates the role of the logical interface for the Ethernet service.


The role determines the position of the logical interface in the service.

Values


Source, Sink None.


Value Description

Source Indicates that the logical interface is set as the source port forthe service.

Sink Indicates that the logical interface is set as the sink port forthe service.


The source port can be either the UNI interface or NNI interface.

The sink port can be either the UNI interface or NNI interface.

If the sink port is a UNI interface, the display format is "slot number - board name - port name".

If the sink port is an NNI interface, the logical port can be a port, PW or QinQ link.


None.

Related Information

None.



C-117

C.135 Physical Port ID

Description

The Physical Port ID parameter identifies the physical port that applies the QinQ policy.



Values

Slot number - board name - port number (PORT - number), for example, 1-EG16-11 (PORT-11)


None.

C.136 System Priority (LAG)

Description

The System Priority parameter indicates the priority level of a link aggregation group (LAG).This parameter affects the working state of the member ports in the LAG.


When the LAG at the local end negotiates with the LAG at the opposite end by using the LACPpackets, the LAGs can obtain the system priority information of each other. The result computedby the selection logic of the LAG with the higher priority is considered as the common resultfor both LAGs. If the two LAGs have the same system priority, the system MAC addresses ofthe two LAGs are compared. The LAG with the lower MAC address is adopted.

The system priority increases as the value decreases.


0-65535, 1 as the spacing 32768


To adopt the result computed by the selection logic of a static LAG, set a higher system priorityfor this static LAG.


Configuration Guide


Issue 06 (2009-06-01)

Relationship with Other ParametersThe System Priority (Link Aggregation) parameter is valid only when the LAG Typeparameter is set to Static.


C.137 Downlink Policy

DescriptionThe Downlink Policy parameter indicates the traffic policy ID for the ATM connection in thespecific direction. For example, if the service for this connection is of the UNIs-NNI type, thespecific direction is PW-to-UNI; if the service for this connection is of the UNI-UNI type, thespecific direction is from the sink UNI port to source UNI port.f the service for this connectionis of the UNI-UNI type, the specific direction is from the sink UNI port to source UNI port.

Impact on the SystemIn the case of an ATM connection, the downlink policy determines the traffic policy in a specificdirection, such as the priority scheduling, leaky bucket processing mechanism, shapingprocessing, and network-side priority scheduling. If you select an improper ATM policy, packetsmay be lost or the QoS is not ensured for services of higher priorities.


1-1024 Select one from the created policies and enter the index.

Configuration GuidelinesThe downlink policy affects the traffic parameters and QoS parameters in the specific directionof the ATM connection. In addition, the network QoS sets the forward priority according to thedownlink policy. Select a proper ATM policy according to the features of the data carried bythe ATM connection. In the case of the services that have high transmission quality requirements,select the ATM policy that ensures the transmission quality with priority.

Relationship with Other ParametersMake sure that the entered index indicates an existing ATM policy.




C-119

C.138 Line Encoding Format

Description

The Line Encoding Format parameter sets the line code type of the E1 link.


If the line codes of the two interconnected ports are inconsistent, the services are unavailable.

Values


HDB3 HDB3


Value Description

HDB3 Indicates that the HDB3 code is used on this E1 port.


This parameter must be set before the services are configured. In addition, the line codes of thetwo interconnected ports are consistent.


None.

C.139 Response Maintenance Point ID

Description

The Response Maintenance Point ID parameter identifies the response MP according to theMAC address.




Configuration Guide


Issue 06 (2009-06-01)


Indicates the MAC address of the port. None.

Configuration GuidelinesIndicates the MAC address of the port where the response MP is located.



C.140 Signal Type

DescriptionThe Signal Type parameter indicates the label allocation scheme of a PW, that is, dynamic orstatic.

When creating a PW service, adopt the dynamic or static scheme to allocate the PW label. Inthe case of the static scheme, the PW label is allocated manually. In the case of the dynamicscheme, the downlink node allocates the PW label by using the signaling.



Static, Dynamic None.


Value Description

Static Indicates that the PW label is allocated manually.

Dynamic Indicates that the downlink node allocates the PW label byusing the signaling.



C-121


C.141 CDVT (us)

DescriptionThe cell delay variation tolerance (CDVT) indicates the capability of tolerating the burst ATMcells. The CDVT unit is us. If certain cells arrive later than they are supposed to arrive, thesecells are considered as burst cells. The volume of these burst cells is measured based on thearrival time difference. If the volume sum of multiple consecutive ATM cells exceeds the CDVTof the leaky bucket, the coming violation cells are discarded.

Impact on the SystemIf the CDVT is set to a small value, the leaky bucket may lose packets in the case of a largevolume of burst cells.


0.7-1310000.0 None. us

Configuration GuidelinesTo reduce the lost packets to the minimum, set the CDVT to a proper large value.

For example, if the value is approximately 1000000, the services can tolerate most burst cells.

If the PCR/SCR value of the connection is relatively large, you can set the CDVT to a relativesmall value. The burst time decreases as the cell rate increases. Hence, the CDVT can be set toa small value.

If the PCR/SCR value is relatively large, the cell spacing is relatively large and the burst timemay be also relatively large. Hence, set the CDVT to a relative large value in this case.

Relationship with Other ParametersThe CDVT is converse with the PCR/SCR.



Configuration Guide


Issue 06 (2009-06-01)

C.142 Service Type (ATM Service)

DescriptionThe Service Type parameter indicates whether an ATM service passes through a packetswitching network (PSN). Two service types are available. The service of one type passesthrough the PSN network and the service of the other type does not. The former is created onone UNI (Layer 2) port and one NNI (PW) port, and the latter is created on two NNI ports ofthe same equipment.

Impact on the SystemIf the service type does not match the ATM connection to be created, the creation of the ATMconnection fails.


UNI-UNI, UNIs-NNI None.


Value Description

UNI-UNI Indicates the service traveling from one UNI (Layer 2) port toanother UNI (Layer 2) port.

UNIs-NNI Indicates the service traveling from one or more than one UNI(Layer 2) ports to one NNI (PW) port.

Configuration GuidelinesSelect a proper service type according to the application scenario. In the scenario where two setsof user equipment are interconnected, create one UNI-UNI service. Then, you can create anATM connection between two UNI (Layer 2) ports on the basis of the UNI-UNI service. In thescenario where the user equipment accesses the network, create one UNIs-NNI service. Then,you can create an ATM connection between any two UNI (Layer 2) ports on the basis of theUNIs-NNI service.





C-123

C.143 Service Type (ATM Policy)

Description

The service types are described as follows:

Constant bit rate (CBR)

In the case of the user end, also service applicant, the CBR service is extremely sensitive to thedelay variation of the service data stream, and requires that the data should be transmitted at aconstant rate. In the case of the network side, also service provider, certain static bandwidthshould be always available for the CBR service in consecutive periods, and the highest priorityshould be provided to the CBR service. The main feature of the CBR service lies in the stabilityof the service data stream. The user end transmits data with a regular period. Hence, the serviceburst seldom occurs. The circuit emulation and audio services are typical application cases.When applying for the CBR service from the network side, the user should provide the peak cellrate (PCR) parameter.

Real-time variable bit rate (RT-VBR)

The RT-VBR service is extremely sensitive to the delay and delay variation. The audio serviceand video exchange service are typical application cases. This is similar to the CBR service. TheRT-VBR service, however, can tolerate certain service burst. The data rate at the source can bedifferent in different periods. In addition, the service provider does not allocate any staticbandwidth for the RT-VBR service, but adopts the multi-path multiplexing mode. Whenapplying for the RT-VBR service from the service provider, the user should provide the PCR,sustainable cell rate (SCR), and maximum burst size (MBS) parameters.

Non-real-time variable bit rate (NRT-VBR)

Compared with the RT-VBR service, the NRT-VBR service does not require the real-timefeature. In the case of the NRT-VBR service, the service data is processed at the network endwith a lower priority than that for the RT-VBR service. The NRT-VBR service is similar to theRT-VBR service with respect to burst, statistics multiplexing and service parameters.

Unspecified bit rate (UBR)

The UBR service is also applicable to the scenario where there are high requirements for thereal-time feature and there is much service burst. The services as the FTP and E-mail are typicalapplication cases of the UBR. The UBR service, however, only requires that the network sideprovides the service with the best effort. When applying for the UBR service, the user need notspecify any QoS parameter. The network side does not provide any ensured QoS for the UBRservice. In the case of network congestion, the UBR cells are discarded first.


In the case of the CBR/RT-VBR/NRT-VBR service, the system allocates the switchingbandwidth specified by the PCR parameter.

In the case of the UBR service, the system does not ensure the service transmission when networkcongestion occurs. The bandwidth for the UBR service may be preempted by the service of ahigher priority.


Configuration Guide


Issue 06 (2009-06-01)

Values


CBR,,RT-VBR, NRT-VBR, UBR UBR

The traffic descriptor type and traffic parameter vary with the service type.


The service of a constant bit rate, such as the audio service, requires the real-time feature, lowdelay and low jitter. In the case of such a service, apply the CBR service, which has the highestpriority for transport in the network.

The service of a variable bit rate, such as the video service, requires the real-time feature andlow delay. In the case of such a service, apply the RT-VBR service, which has the second highestpriority for transport in the network.

The service, such as the file transfer service, does not require the real-time feature. In the caseof such a service, apply the NRT-VBR service, which has the priority lower than the priority ofthe RT-VBR service but higher than the priority of the UBR service for transport in the network.The NRT-VBR service can ensure the transport based on the SCR bandwidth.

The data service, such as the Internet access service, requires the best-effort transport. In thecase of such a service, apply the UBR service, which has the lowest priority for transport in thenetwork. When the network congestion occurs, the UBR service is discarded first.


None.

Related Information

None.

C.144 Service Type (Ethernet OAM)

Description

The Service Type parameter indicates the type of the service to be detected by the OAM duringthe creation of an MA.





C-125

Values


E-Line, E-LAN, E-AGGR None.


Value Description

E-Line Indicates the Ethernet private line service.

E-LAN Indicates the Ethernet private network service.

E-AGGR Indicates the Ethernet aggregation service.


The OAM performance statistics can be performed only for the E-Line service.


None.

Related Information

None.

C.145 Service Name

Description

The Service Name parameter indicates the type of the service to be detected by the OAM duringthe creation of an MA.



Values

Value Description

A character string of not more than 64characters

-


Configuration Guide


Issue 06 (2009-06-01)


None.


None.

C.146 Source Interface Type

Description

Set the Source Interface Type parameter to set the source interface type of the VLAN switchingtable for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.


Set the source interface type of the E-AGGR service as the same as the opposite logical interfacetype.


V-UNI, V-NNI None.


Value Description

V-UNI Indicates that the source interface is a V-UNI interface.

V-NNI Indicates that the source interface is a V-NNI interface.


The logical interface type of the source interface of the VLAN switching table for the E-AGGRservice can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, shouldbe of the same type.


None.

Related Information

None.



C-127

C.147 Remote OAM Parameter

DescriptionThe Remote OAM Parameter parameter indicates the configuration information about theremote port received by a port.



Example: 3-EG16-3(PORT-3) None.

Configuration GuidelinesOnly the port number of the port where the EFMOAM is enabled can be entered.



C.148 Remote OAM Working Mode

DescriptionThe Remote OAM working mode parameter indicates whether the remote OAM is in the activemode or passive mode. In the case of the passive mode, the remote OAM does not start thenegotiation or loopback.



Active, Passive Active


Configuration Guide


Issue 06 (2009-06-01)


In the case of the passive mode, the remote OAM does not actively transmit the protocol packets.Hence, if the remote OAM is in the passive mode, the local OAM should be in the active mode.


None.

Related Information

None.

C.149 Remote Side Loopback Response

Description

The Remote Side Loopback Response parameter indicates the capability of the 802.3ahprotocol of a port responding to the remote loopback.


If the Remote Side Loopback Response parameter is set to Enabled, the services are interruptedwhen the local end starts the loopback.

Values




Value Description

Enabled Indicates that the capability of responding to the remoteloopback is available.

Disabled Indicates that the capability of responding to the remoteloopback is unavailable.


When the remote loopback need be responded, this parameter is set to Enabled.

When the remote loopback need not be responded, this parameter is set to Disabled.



C-129

C.150 Remote Working Status

DescriptionCurrently, the equipment supports the bidirectional PW, but the tunnel is unidirectional. OnePW is carried in two tunnels of opposite directions. Hence, to know the running status of thePW, you should know the status of the two tunnels that carry this PW. This parameter is a queryparameter, which indicates the running status of the reverse (from the remote node to the localnode) tunnel that carries the PW.

Impact on the SystemWhen this parameter is down, it indicates that the reverse tunnel that carries the PW isunavailable. In this case, the PW is not up, and the services cannot be created. Determine whetherthe configuration parameters of the tunnel on the opposite NE are correct.

ValuesThe following table lists the description of each value.

Value Description

Up Indicates the service is normal.

Common Fault -

Attachment Circuit Receive Fault Indicates faults occur in the receivedirection on the user side.

Attachment Circuit Transmit Fault Indicates faults occur in the transmitdirection on the user side.

Attachment Circuit Transmit & Receive Fault Indicates faults occur in both receive andtransmit directions on the user side.

PSN-facing PW Receive Fault -

Attachment Circuit Receive Fault AND PSN-facing PW Receive Fault

Indicates faults occur in the receivedirection on the user side and in the transmitdirection on the network side.

Attachment Circuit Transmit Fault AND PSN-facing PW Receive Fault

Indicates faults occur in the transmitdirection on the user side and in the receivedirection on the network side.

Attachment Circuit Transmit & Receive FaultAND PSN-facing PW Receive Fault

Indicates faults occur in the receive andtransmit directions on the user side and inthe receive direction on the network side.

PSN-facing PW Transmit Fault -


Configuration Guide


Issue 06 (2009-06-01)

Value Description

Attachment Circuit Receive Fault AND PSN-facing PW Transmit Fault

Indicates faults occur in the receivedirection on the user side and in the transmitdirection on the network side.

Attachment Circuit Transmit Fault AND PSN-facing PW Transmit Fault

Indicates faults occur in the transmitdirection on the user side and in the transmitdirection on the network side.

Attachment Circuit Transmit & Receive FaultAND PSN-facing PW Transmit Fault

Indicates faults occur in the receive andtransmit directions on the user side and inthe transmit direction on the network side.

PSN-facing PW Transmit & Receive Fault -

PSN-facing PW Transmit & Receive FaultAND Attachment Circuit Receive Fault

Indicates faults occur in the receive andtransmit directions on the network side andin the receive direction on the user side.

PSN-facing PW Transmit & Receive FaultAND Attachment Circuit Transmit Fault

Indicates faults occur in the receive andtransmit directions on the network side andin the transmit direction on the user side.

PSN-facing PW Transmit & Receive FaultAND Attachment Circuit Transmit & ReceiveFault

Indicates faults occur in the receive andtransmit directions on the network side andin the transmit direction on the user side.

/ Indicates no PW parameter is queried on theT2000.


Relationship with Other ParametersLocal Working Status Remote Working Status Compositive Working Status

Non-up status Non-up status Down

Non-up status Up Down

Up Non-up status Down

Up Up Up



C-131

C.151 Used Timeslot

DescriptionThe Used Timeslot parameter indicates the VC-12 path number of the channelized STM-1 port.The path number corresponds to the 63 VC-12 timeslots in the STM-1.



1-63 None.




C.152 Frame Format

DescriptionThe Frame Format parameter sets the frame format of the E1 link.

Impact on the SystemIf the frame formats of the two interconnected ports are inconsistent, the services are unavailable.


CRC-4 Multiframe, Unframe, Double Frame CRC-4 Multiframe



Configuration Guide


Issue 06 (2009-06-01)

Value Description

DoubleFrame

32 bits form one G.704 basic frame. The double frame is a multiframe formedby two G.704 basic frames. The double frame is used for alignment.

CRC-4Multiframe

32 bits form one G.704 basic frame. The CRC-4 multiframe is formed by 16basic G.704 frames, which is defined in G.706 standard. The CRC-4multiframe carries the cyclical redundancy check (CRC) information and linemonitoring information. In the case of the CRC-4 multiframe flow, align theframes in the double frame mode. After the frames are successfully alignedin the double frame mode, align the frames in the CRC-4 multiframe mode.

Unframe The signals are continuous bit streams, which have no frame structure.


This value must be set before the services are configured. In addition, the frame formats of thetwo interconnected ports must be consistent.

When the IMA, MLPPP, or structure-aware CES service is configured in the E1 link, the frameformat of the E1 link should be set to Double Frame or CRC-4 Multiframe. When the structure-agnostic CES service is configured in the E1 link, the frame format of the E1 link should be setto Unframe.


None.

C.153 Frame Type

Description

The Frame Type parameter can be set to Unicast or Multicast.

In the case of the E-LAN service, the unicast packets whose source MAC address is not learnedare called unknown unicast frames.

In the case of the E-LAN service, the multicast packets whose source MAC address is not learnedare called unknown multicast frames.


If the unknown unicast frames are to be broadcast as configured, they are broadcast in the E-LAN service.

If the unknown unicast frames are to be discarded as configured, they are discarded in the E-LAN service.

If the unknown multicast frames are to be broadcast as configured, they are broadcast in the E-LAN service.



C-133

If the unknown multicast frames are to be discarded as configured, they are discarded in the E-LAN service.


Unicast Indicates the packet frames except the multicast frames andbroadcast frames.

Multicast The MAC address with the eighth bit of the first byte as 1 isspecified as the multicast MAC address (The FF-FF-FF-FF-FF-FF MAC address is excluded). If the destination MAC addressin the packets is the multicast MAC address, these packets aremulticast frames.




C.154 VC-Switching-Supported VPIs

DescriptionThe VC-Switching-Supported VPIs parameter indicates the count of VPIs that can be used forVC switching on an ATM port. For example, if you set this parameter to 2, it indicates that twoVPIs are available when you crate a VCC connection on an ATM port. In this case, the otherVPIs can be used only for the VP switching.

Impact on the SystemThis parameter affects the values of the VPIs for the VCC connection on an ATM port, and thecount of VPC connections.


0-64 32

The count of VPIs for VC switching ranges from 0 to 2VPIbits (VPIbits: the maximum numberof VIPI bits). Due to the limitation of the sub-board hardware resources, the maximum count


Configuration Guide


Issue 06 (2009-06-01)

cannot be achieved on certain conditions. Especially when the VPI/VCI bit number of certainATM port is set as 12/16, the count is extremely small.

Configuration GuidelinesThe count (VCX) of VPIs that support the VC switching depends on the values of the maximumnumber of VPI bits and maximum number of VCI bits. For example, if the number of VPI bitsis set to 5, the maximum number of VCX is 32. In addition, due to the limited sub-board hardwareresources, the VCX value is converse to the maximum number of VCI bits.

Relationship with Other ParametersEach sub-board has certain hardware resources, which are shared by all the ATM ports on thesub-board. The count of VPIs (VCX) that support the VC switching is affected by the VPI andVCI values on this ATM port, and also the values on other ATM ports. The VCX varies inverselyto the maximum number of VCI bits. The number of VCX x VCI varies directly to the sub-boardhardware resources on the equipment. In addition, do not change this parameter when the sub-board carries services.


C.155 Main Port

DescriptionThe Main Port parameter indicates the LAG member port available for creating services. EachLAG has only one main port. If the Load Sharing parameter is set to Non-Sharing, the mainport carries the services. When the main port becomes faulty, the services are switched to andcarried by the slave port.



Example: 3-EG16-3(PORT-3) None.

Configuration GuidelinesEvery Ethernet port on the NE can be used as the main port.




C-135


C.156 Main Port Status

DescriptionThe Main Port Status parameter indicates the port status computed by the selection logic forthe LAG.

Impact on the SystemIf one port is in the out-of-service state, the service cannot be loaded on this port.

If a port is in the in-service state, this port can be added to an LAG. When the load sharing isconfigured for this port, the service can be loaded on this port.


In-Service, Out-of-Service Out-of-Service


Value Description

In-Service Indicates that the port can be added to an LAG and can carrythe service.

Out-of-Service Indicates that the port cannot be added to an LAG and cannotcarry the service.

Configuration GuidelinesThis parameter is used for query only. No rule is specified for selecting a value.

Relationship with Other ParametersIn the case of the static LAG, the LACP protocol is used. The port status depends on the portworking mode, port working rate, port priority, and LAG priority.

In the case of the manual LAG, the LACP protocol is not used. The port status depends on theport working mode and port working rate.



Configuration Guide


Issue 06 (2009-06-01)

C.157 Auto-Negotiation Flow Control Mode (Ethernet Port)

DescriptionFlow control is a kind of function to adjust the volume of the data traffic passing through thenode or link to ensure that overloading does not occur on the node or in the link.

The Auto-Negotiation Flow Control Mode (Ethernet Port) parameter indicates the flowcontrol mode supported by the port. Finally, the two interconnected ports negotiate to obtain ausable flow control mode.

Impact on the SystemIf the port carries services, services are transiently interrupted when this parameter is modified.

ValuesValue Range Default

Value

Disabled, Enable Dissymmetric Flow Control, Enable Symmetric/Dissymmetric Flow Control

Disabled


Value Description

Disabled Indicates that the flow control function of the port is disabled. (Theflow control function at both the transmit and receive directions isdisabled.)

EnableDissymmetric FlowControl

Indicates that the dissymmetric flow control function is enabled in theauto-negotiation state. (The flow control frames can be transmitted,but the received flow control frames are not responded. The flowcontrol mode used is determined by auto-negotiation.)

Enable SymmetricFlow Control

Indicates that the symmetric flow control function is enabled in theauto-negotiation state. (The flow control frames can be transmitted,and the received flow control frames are responded. The flow controlmode used is determined by auto-negotiation.)

Enable Symmetric/Dissymmetric FlowControl

Indicates that the symmetric/dissymmetric flow control function isenabled in the auto-negotiation state. (The flow control mode used isdetermined by auto-negotiation.)

Configuration GuidelinesIf the flow control mode is auto-negotiation, the flow control function realized on the port isdetermined by the auto-negotiation flow control mode set on the interconnected ports at the two



C-137

ends. The following table lists the negotiation results when the interconnected ports at the twoends are set to various auto-negotiation modes.

Auto-Negotiation FlowControl Mode Set on theLocal Port

Auto-Negotiation FlowControl Mode Set on theOpposite Port

Negotiation Result (FlowControl FunctionRealized on the LocalPort)

Disabled Any auto-negotiation flowcontrol mode

Disabled.

Any auto-negotiation flowcontrol mode

Disabled Disabled.

Enable Dissymmetric FlowControl


Disabled.


Enable Symmetric FlowControl

Disabled.


Enable Symmetric/Dissymmetric Flow Control

The receive directionrealizes the flow controlfunction.



Disabled



Both the transmit and receivedirections realize the flowcontrol function.






The transmit directionrealizes the flow controlfunction.







Relationship with Other Parametersl When Auto-Negotiation Flow Control Mode and Non-Autonegotiation Flow Control

Mode are set to a value other than Disabled. at the same time, the flow control mode ofthe port is determined by the working mode of the port. When the working mode of theport is auto-negotiation, the flow control mode is auto-negotiation. When the working modeof the port is non-autonegotiation, the flow control mode is non-autonegotiation.


Configuration Guide


Issue 06 (2009-06-01)

l When either Auto-Negotiation Flow Control Mode or Non-Auto-negotiation FlowControl Mode is set to a value other than Disabled, the flow control mode of the port isalso determined by the working mode of the port.

– When Auto-Negotiation Flow Control Mode is set to a value other than Disabled, ifthe working mode of the port is auto-negotiation, the flow control mode is auto-negotiation. If the working mode of the port is non-autonegotiation, the flow controlfunction cannot be realized on the port.

– When Non-Autonegotiation Flow Control Mode is set to a value other thanDisabled, if the working mode of the port is non-autonegotiation, the flow control modeis non-autonegotiation. If the working mode of the port is auto-negotiation, the flowcontrol function cannot be realized on the port.

C.158 Compositive Working Status

Description

The Compositive Working Status parameter, a query parameter, indicates the PW status. Whenremote running status and local running status are both up, this parameter is up.


This parameter indicates whether the PW status is normal. When this parameter is down, theservices can be configured, but cannot be normally transmitted. Services can be normallytransmitted only when this parameter is up.

Values

Value Description

Down Indicates that the PW is not normally created, and the servicesare unavailable.

Up Indicates that the PW is successfully created, and the servicesare normal.


None.


The following table lists the relation between Compositive Working Status, Local WorkingStatus, and Remote Working Status.

Local Working Status Remote Working Status Queried CompositiveWorking Status

Non-up status Non-up status Down



C-139

Local Working Status Remote Working Status Queried CompositiveWorking Status

Non-up status Up Down

Up Non-up status Down

Up Up Up

C.159 Impedance

Description

The Impedance parameter indicates the impedance of the interface (electrical).



Values


75ohm, 120ohm -


None.


None.

C.160 Max. OAM Packet Length (byte)

Description

The Max. OAM Packet Length (byte) parameter indicates the maximum length of the OAMpacket. The near port and remote port compare the values of this parameter, and consider thesmaller value as the maximum length of protocol packets.




Configuration Guide


Issue 06 (2009-06-01)


64-1518 1518

Configuration GuidelinesThe smaller number of 1518 and the port MTU value is considered as the maximum packetlength. In this way, the protocol packets can be normally transmitted.



C.161 Max. VCI Bits

DescriptionThe virtual channel identifier (VCI) identifies the virtual channels of a virtual path. The VCIand the virtual path identifier (VPI) identify a virtual connection. The VCI uses 16 bits of theATM header. Due to the limitation of the hardware resources, the maximum VCI bits cannot beachieved at the same time for every ATM port. Hence, before configuring a service, set themaximum VCI bits for each ATM port. If the maximum number of VCI bits is set to 16, themaximum value of the VCI is 65535 (216-1).

Impact on the SystemThis parameter affects the value range of the VCI for setting up a connection. For example, ifthe maximum number of VCI bits of an ATM port is 8, the VCI value should be 255 or less forcreation of a connection on the ATM port. In addition, if a sub-board on the equipment carriesservices, do not change this parameter for any ATM port on the sub-board.


0-16 7

Configuration GuidelinesThe VCIs in each VPI are independent from each other. The VCI value ranges from 32 to2MaxVCIbits-1. The VCI value less than 32 is for exclusive use of the network management, and



C-141

cannot be used by the user cells. In the case of the OptiX PTN 1900&3900, set the VCI valueto 0xFFFFFFFF (invalid value) during creation of the VP connection.

Relationship with Other ParametersAs the hardware resources of each sub-board are limited, all ATM ports on the sub-board sharethe hardware resources. The valid value for the maximum VCI bits of an ATM port on the sub-board is affected by the values of other ATM ports on the sub-board. In addition, do not changethis parameter when the sub-board carries services.


C.162 Max. VPI Bits

DescriptionThe virtual path identifier (VPI) identifies the virtual path in the VPC/VCC connection. In thecase of the NNI cell format, the VPI takes 12 bits of the ATM cell header. In the case of the UNIcell format, the VPI takes 8 bits of the ATM cell header. Due to the limitation of the hardwareresources, the maximum VPI bits cannot be achieved at the same time for every ATM port.Hence, before configuring a service, set the maximum VPI bits for each ATM port. If themaximum number of VPI bits is set to 12, the maximum value of the VPI is 4095 (212 - 1).

Impact on the SystemThis parameter affects the value range of the VPI for creation of a connection. For example, ifthe maximum number of VPI bits of an ATM port is 8, the VPI value should be 255 or less forcreation of a connection on the ATM port. In addition, if a sub-board on the equipment carriesservices, do not change this parameter for any ATM port on the sub-board.


ATM port type (UNI): 1-8ATM port type (NNI): 1-12

8


The VPIs of each port are independent and the VPI value ranges from 0 to 2MaxVPIbits - 1. Duringcreation of an ATM service, the VPI value can be used for either the VP switching or VCswitching, but not both.

Relationship with Other ParametersTo set this parameter to a value larger than 8 for an ATM port, set the ATM port type as NNI.As the hardware resources of each sub-board are limited, all ATM ports on the sub-board share


Configuration Guide


Issue 06 (2009-06-01)

the hardware resources. The valid value for the maximum VPI bits of an ATM port on the sub-board is affected by the values of other ATM ports on the sub-board. In addition, do not changethis parameter when the sub-board carries services.


C.163 Max. Differential Delay (100 us)

DescriptionSet the Max. Differential Delay (100 us) parameter to set the delay difference of the MP groupmembers. This parameter is valid only for the E1 link. The Max. Differential Delay (100 us)parameter indicates the delay difference of each member link in the MP group. If the differencebetween the delay of a link and the delay of any other link exceeds the maximum differentialdelay, the link is not available.



25-500 30 100 us

Configuration GuidelinesThe spacing for the differential delay is 100 us. The differential delay should be multiples of100 us.

Relationship with Other ParametersThe Max. Differential Delay (100 us) parameter is valid only when the Enable DifferentialDelay parameter is set to Enabled.


C.164 Max. Concatenated Cell Count

DescriptionThe Max. Concatenated Cell Count parameter indicates the maximum number of concatenatedcells for an ATM service. This parameter is applicable only for the PW ATM type. Set this



C-143

parameter to set the maximum number of ATM cells that can be encapsulated in each packetwhen the concatenation is enabled.



OptiX PTN 1900: 1 to 31 10

Configuration GuidelinesIf this parameter is set to 1, it indicates that the ATM cell concatenation is not performed. Onlyone ATM cell is encapsulated in each service packet. If this parameter is set to a value rangingfrom 2 to 31, the value indicates the maximum number of cells that can be encapsulated in eachpacket.31, the value indicates the maximum number of cells that can be encapsulated in eachpacket.

Relationship with Other ParametersWhen the maximum concatenated cell count is 1, the maximum concatenation WTR time isinvalid.

C.165 Max Data Packet Size(byte)

DescriptionThe Max Data Packet Size (POS Port) parameter sets the maximum length of the data packeton the POS port.

Impact on the SystemAfter this parameter is set, all the packets of a length longer than this parameter are discarded.


Value range: 960-9000 1620

Configuration GuidelinesThe maximum data packet length has a filtering mechanism, through which this parameter is setto filter the data packets received on the POS port of a length longer than a certain length. Whensetting this parameter, consider the length of the data packets transmitted from the opposite end.


Configuration Guide


Issue 06 (2009-06-01)

If the parameter value is less than the length of the data packets transmitted from the oppositeend, this link cannot normally transmits service packets.

Relationship with Other ParametersWhen this parameter is set on the POS port, set the Encapsulation Type of the POS port toPPP.

C.166 MBS (Cells)

DescriptionThe MBS (2-200000 Cells) parameter indicates the maximum number of burst cells of the VBRservice that can be continually transported at the PCR higher than SCR, and do not lose packets.

Impact on the SystemAs the value of this parameter increases, the depth of the primary leaky bucket for the ATMconnection becomes deeper and thus the primary leaky bucket can tolerate more burst cells.

Values2-200000 cells


2-200000 None. Cell

Configuration GuidelinesTo reduce the loss of packets of the VBR service to the minimum, set the MBS to a proper largevalue.

Relationship with Other ParametersSet the MBS only for the RT-VBR/NRT-VBR service.

Related InformationThe formula for computing the burst tolerance (BT) of the primary leaky bucket is BT = (MBS- 1)(1/SCR - 1/PCR) + CDVT. The MBS varies directly to the BT of the primary leaky bucket.If MBS consecutive cells of the ATM traffic burst at the PCR, the overall burst time is (MBS -1)(1/SCR - 1/PCR).



C-145

C.167 Max Frame Length(byte)-Ethernet interface

DescriptionThe Max Frame Length (Ethernet Port) parameter sets the maximum length of the datapackets allowed to be received by the Ethernet port.

Impact on the SystemAfter this parameter is set, all the data packets of a length longer than this parameter arediscarded.


Value range: 960-9000 1620

Configuration GuidelinesThe maximum data packet length has a filtering mechanism, through which this parameter is setto filter the data packets received on the Ethernet port of a length longer than a certain length.When setting this parameter, consider the length of the data packets transmitted from the oppositeend. If the parameter value is less than the length of the data packets transmitted from the oppositeend, this link cannot normally transmits service packets.


C.168 Min. Activated Link Count

DescriptionThe Min. Activated Link Count parameter indicates the minimum count of activated links.

Set this parameter to set the minimum count of available links in an MP group. When the countof available member links of an MP group exceeds the minimum activated link count, theprotocol shuts down the entire MP group to remind the user of rectifying the fault. This is forprotection.

If you set the Min. Activated Link Count parameter, the MP group can work normally onlywhen the count of member links in the MP group equals or exceeds the specified value.

Impact on the SystemWhen the count of member links in the MP group is less than the minimum count of activatelinks, the dynamic service is interrupted. In addition, the MP_DOWN alarm is reported if theMP group is originally in the Up state.


Configuration Guide


Issue 06 (2009-06-01)

Values


1-16 1


None.


None.

Related Information

None.

C.169 Direction

Description

The Direction parameter indicates the direction for the policy application.



Values


Ingress, Egress None.


Value Description

Ingress Indicates that the policy application direction is uplink, thatis, from the UNI or NNI to the cross-connect board.

Egress Indicates that the policy application direction is downlink,that is, from the cross-connect board to the UNI or NNI.



C-147



Configuration Guide


Issue 06 (2009-06-01)

Index

Aadvanced attribute of Ethernet interfaces

setting, 4-18advanced attributes of PDH interfaces

setting, 4-13advanced attributes of SDH interfaces

setting, 4-9attribute of Ethernet interface

configuring, 4-14attribute of PDH interface

configuring, 4-10attribute of SDH interface

configuring, 4-5

Bbasic concept

linear MS, 2-22board

adding sub-board, 2-10board parameters

configuring, 4-1

CCES service

basic concept, 9-2creating on a per-NE basis, 9-12, 9-13

clockdefining uniform quality level for unknown clocksource, 2-20enabling extended SSM protocol, 2-17enabling standard SSM protocol, 2-17network interconnection clock setting, 2-21setting clock priority, 2-16setting phase-locked source for external clockoutput, 2-19setting protection switching condition, 2-18setting reversion mode and WTR time, 2-19setting SSM output, 2-21switching clock source manually, 2-21

configuring protectionlinear protection

MSP linear protection, 2-23control plane

address parse, 5-16creating a CES service

trail function, 9-8, 9-10creating by using trail function

bypassFRR, 6-5

dynamic MPLS tunnel, 6-5static MPLS tunnel, 6-10

creating subnet, 2-13creating V-UNI group, 11-19, 12-11, 13-6

EE-AGGR, 13-2E-AGGR service, 13-2E-LAN, 12-2E-LAN service, 12-2

creating, 12-4E-Line, 11-3

port carrying, 11-14PW carrying, 11-15QinQ link carrying, 11-18UNI-UNI, 11-13

E-Line service, 11-3equipment-level protection

creating TPS protection group of sub-boards, 2-11Ethernet aggregation, 13-4Ethernet virtual interface

configuring, 4-27

Ffiber

manual creation, 2-12flow control

configuring, 4-18

Ggeneral attribute of Ethernet interface, 4-16general attribute of Ethernet virtual interface

, 4-27

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Index


i-1

general attribute of PDH interfaceconfiguring, 4-12

general attribute of SDH interface, 4-7

general attribute of serial interface, 4-21

GNEcreating, 2-5

GRE tunnelcreating, 8-2

Iimporting route

parameters, 5-12inband DCN

configuring, 2-14IP tunnel

creating, 7-2IS-IS node attribute

setting node attribute, 5-10IS-IS port attribute

setting port attribute, 5-11

Llayer 2 attribute of Ethernet interface

configuring, 4-17layer 2 attribute of SDH interface

configuring, 4-8layer 3 attribute of Ethernet interface, 4-17layer 3 attribute of Ethernet virtual interface

configuring, 4-27layer 3 attribute of PDH interface

configuring, 4-12layer 3 attribute of SDH interface

configuring, 4-8layer 3 attribute of serial interface, 4-22LDP peer entity

creating LDP peer entity, 5-13LDP protocol

configuring LDP protocol, 5-14parameter of LDP protocol, 5-14

link TElink information, 5-13

LSR ID, 6-12

Mmember of MP group, 4-26MO data

scheduled backup, 16-2MP group

configuring, 4-23creating, 4-24

MPLS, 6-3MPLS Tunnel, 6-3

application, 6-4

point-to-point, 6-4MPLS tunnel

creating protection group, 6-15

NNE

searching and creating, 2-3NE configuration data

backup, 16-3NM user

switching, 2-8

OOffload solution

ATM forwarding, 14-16ETH forwarding, 14-28IP forwarding, 14-39

QQinQ Link

creating, 11-18querying board protection

SCC and cross-connect board protection, 2-12

RRSVP protocol

configuring RSVP protocol, 5-15

Sserial interface

configuring, 4-19Creating, 4-20

shutting down T2000shutting down T2000 client, 1-5shutting down T2000 server, 1-6

starting T2000logging in to T2000 client, 1-4starting T2000 server, 1-3

startingT2000startingT2000computer, 1-2

static routeconfiguring static route, 5-15

system monitor, 1-4

TT2000 client

exiting, 1-5login, 1-4switching NM user, 2-8

T2000 dataperiodically backing up MO data, 16-2

T2000 main topology

IndexOptiX PTN 3900 Packet Transport Platform of PTN Series

Configuration Guide

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

Issue 06 (2009-06-01)

main topology, 1-7T2000 main window

NE Explorer, 1-8T2000 server

running status, 1-4shutdown, 1-6starting, 1-3

topology objectfiber, 2-12GNE, 2-5NE, 2-3topology subnet, 2-13

OptiX PTN 3900 Packet Transport Platform of PTN SeriesConfiguration Guide Index


i-3

Documents

00423994-Configuration Guide(V100R001_06)