OptiX OSN 7500 II&7500&3500&1500 Configuration Guide (Packet Transport Domain)(V200R011)

OptiX OSN 7500 II/7500/3500/1500 V200R011C03

Configuration Guide (Packet Transport Domain) Issue

03

Date

2013-02-20

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 03 (2013-02-20)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

OptiX OSN 7500 II/7500/3500/1500 Configuration Guide (Packet Transport Domain)

About This Document

About This Document Related Versions The following table lists the product versions related to this document. Product Name

Version

OptiX OSN 7500 II

V200R011C03

OptiX OSN 7500

V200R011C03

OptiX OSN 3500

V200R011C03

OptiX OSN 1500

V200R011C03

iManager U2000

V100R006C00 and later

Intended Audience This document describes the configuration of different types of Ethernet services of the OptiX OSN equipments with regard to configuration flow, networking diagram, service planning, and configuration process. This document describes the methods of configuring different types of Ethernet services on the U2000. The intended audience of this document is: l

Installation and commissioning engineer

l

Data configuration engineer

Symbol Conventions The symbols that may be found in this document are defined as follows.

Issue 03 (2013-02-20)


ii


Symbol

About This Document

Description

DANGER

WARNING

CAUTION

DANGER indicates a hazard with a high level or medium level of risk which, if not avoided, could result in death or serious injury. WARNING indicates a hazard with a low level of risk which, if not avoided, could result in minor or moderate injury. CAUTION indicates a potentially hazardous situation that, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

TIP

Provides a tip that may help you solve a problem or save time.

NOTE

Provides additional information to emphasize or supplement important points in the main text.

GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.

>

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

Change History Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.

Updates in Issue 03 (2013-02-20) Based on Product Version V200R011C03 This document of the V200R011C03 version is of the third release. Compared with Issue 02, Issue 03 includes the following updates in V200R011C03SPC200: l

Issue 03 (2013-02-20)

"E-Line Service Parameters (Configuration on a Per-NE Basis)" is optimized in section "Parameter Description: E-Line Service." Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

iii


About This Document

Updates in Issue 02 (2012-03-15) Based on Product Version V200R011C03 This document of the V200R011C03 version is of the second release. Compared with the previous release, this version has the following new or optimized contents: l

Updated the document based on its supporting NMS.

Updates in Issue 01 (2012-01-30) Based on Product Version V200R011C03 This document of the V200R011C03 version is of the first release. Compared with the previous release, this version has the following new or optimized contents: l

In topic "Configuring E-Line Services", the description of "Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Priorities)" is added.

l

In topic "Configuring E-Line Services", the description of "Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Switching)" is added.

l

"Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis" is optimized.

l

"Configuring E-Line Services Carried by PWs in End-to-End Mode" is optimized.

l

"E-Line Service Parameters (Configuration on a Per-NE Basis)" is optimized.

l

"E-Line Service Parameters (Configuration in End-to-End Mode)" is optimized.


In topic "Configuration Example: E-AGGR Services Carried by PWs", the description of "Configuration Process (in End-to-End Mode)" is added.

l

In topic "Configuration Task Collection", the description of "Creating E-AGGR Services Carried by PWs in End-to-End Mode" is added.

l

In topic "Configuration Task Collection", the description of "Configuring an ATM Policy Profile" is added.

l

In topic "Configuration Task Collection", the description of "Configuring an ATM CoS Mapping Profile" is added.

l

In topic "Parameter Description", the description of "Parameters for Configuring E-AGGR Services (End-to-End Mode)" is added.

l

"Split Horizon Group" is optimized.

Issue 03 (2013-02-20)


iv


About This Document

Updates in Issue 01 (2011-07-15) Based on Product Version V200R011C02 This document of the V200R011C02 version is of the first release. Compared with the previous release, this version has the following new or optimized contents: l

"Configuring ATM Services" is added.

l

In topic "Configuration Task Collection", the description of "Configuring ATM PWE3 Services" is added.

l

In topic "Configuration Task Collection", the description of "Managing the Blacklist" is added.

l

In topic "Parameter Description", the description of "Parameter Description: ATM/IMA Services" is added.

l

In topic "Parameter Description", the description of "Parameter Description: Address Parse" is added.

l

"Creating the Network" is optimized.

l

"Configuration Example: E-Line Services Carried by PWs" is optimized.


In topic "Managing PWE3 Services", the description of "Searching for PWE3 Services" is added.

l

In topic "Configuration Task Collection", the description of "Configuring the NE-Level TPID" is added.

l

In topic "Parameter Description", the description of "Parameter Description: CES Port" is added.

l

In topic "Parameter Description", the description of "Parameter Description: MPLS OAM" is added.

l

In topic "Parameter Description", the description of "Parameter Description: MPLS Tunnel APS" is added.

l

"Creating Optical Fibers by Searching for the Optical Fibers on the NMS" is optimized.

l

"Verifying the Correctness of E-Line Service Configuration" is optimized.

l

"Configuring an MPLS Tunnel" is optimized.

Updates in Issue 01 (2011-01-25) Based on Product Version V200R011C01 This document of the V200R011C01 version is of the first release. Compared with the previous release, this version has the following new or optimized contents: Issue 03 (2013-02-20)


v


About This Document

l

In topic "Configuration Task Collection", the description of "Managing MPLS Tunnels" is added.

l

In topic "Configuration Task Collection", the description of "Managing MPLS Tunnel APS Protection Groups" is added.

l

In topic "Parameter Description", the description of "Parameter Description: CES Services" is added.

Updates in Issue 02 (2010-11-01) Based on Product Version V200R011C00 This document of the V200R011C00 version is of the second release. Compared with the first release, the contents of this document are modified or optimized as follows: l

In topic "Operation Task for Configuring E-LAN Services", the description of "Configuring E-LAN Services Carried by PWs in End-to-End Mode" is added.

l

In topic "Configuration Example: E-LAN Services Carried by PWs", the description of "Configuration Process (in End-to-End Mode)" is added.

l

"Configuring Cross-Domain Services" is optimized.

Updates in Issue 01 (2010-07-20) Based on Product Version V200R011C00 This document of the V200R011C00 version is of the first release. Compared with V100R009C03, this version has the following new or optimized contents: l

OptiX OSN 7500 is added.

l

"Starting the T2000" is deleted.

l

"Getting Started" is added.

l

"Creating the Network" is added.

l

"Configuring E-Line Services Carried by PWs in End-to-End Mode" is added.

l

"Configuring Cross-Plane Services" is added.

l

"Configuring CES Services" is added.

Issue 03 (2013-02-20)


vi


Contents

Contents About This Document.....................................................................................................................ii 1 Getting Started...............................................................................................................................1 1.1 Starting or Shutting Down the U2000................................................................................................................2 1.1.1 Starting the U2000 Server.........................................................................................................................2 1.1.2 Logging In to the U2000 Client.................................................................................................................2 1.1.3 Exiting a U2000 Client..............................................................................................................................3 1.1.4 Shutting Down the U2000 Server..............................................................................................................3 1.2 Main Windows and Common Operations of the U2000....................................................................................4 1.2.1 Components of the Client GUI..................................................................................................................4 1.2.2 Key GUI Components...............................................................................................................................6 1.2.3 Frequently Used Buttons...........................................................................................................................7 1.2.4 Shortcut Icon..............................................................................................................................................9 1.2.5 Common Shortcut Keys...........................................................................................................................11 1.2.6 Main Windows........................................................................................................................................12 1.2.6.1 Workbench......................................................................................................................................12 1.2.6.2 Main Topology...............................................................................................................................12 1.2.6.3 NE Explorer....................................................................................................................................14 1.2.6.4 Clock View.....................................................................................................................................15 1.2.6.5 NE Panel.........................................................................................................................................17 1.2.6.6 Browse Alarm.................................................................................................................................17 1.2.6.7 Browse Event..................................................................................................................................17 1.2.6.8 Browse Performance Window........................................................................................................18

2 Creating the Network.................................................................................................................19 2.1 Creating NEs, Fibers and Subnet......................................................................................................................20

3 Configuring E-Line Services.....................................................................................................21 3.1 Basic Concepts.................................................................................................................................................23 3.1.1 E-Line Services........................................................................................................................................23 3.1.2 UNI..........................................................................................................................................................27 3.1.3 NNI..........................................................................................................................................................28 3.2 Configuration Flow for the E-Line Services....................................................................................................28 3.2.1 Configuration Flow for the UNI-UNI E-Line Services ..........................................................................29 3.2.2 E-Line Services Carried by Ports ...........................................................................................................33 Issue 03 (2013-02-20)


vii


Contents

3.2.3 E-Line Services Carried by PWs ............................................................................................................35 3.2.4 E-Line Services Carried by QinQ Links .................................................................................................38 3.3 Configuration Example: UNI-UNI E-Line Services........................................................................................43 3.3.1 Networking Diagram...............................................................................................................................43 3.3.2 Service Planning......................................................................................................................................44 3.3.3 Configuration Process..............................................................................................................................45 3.4 Configuration Example: E-Line Services Carried by Ports..............................................................................48 3.4.1 Networking Diagram...............................................................................................................................48 3.4.2 Service Planning......................................................................................................................................49 3.4.3 Configuration Process..............................................................................................................................51 3.4.4 Verifying the Correctness of E-Line Service Configuration...................................................................53 3.5 Configuration Example: E-Line Services Carried by PWs (Newly Created)...................................................55 3.5.1 Networking Diagram...............................................................................................................................55 3.5.2 Service Planning......................................................................................................................................57 3.5.3 Configuration Process (in End-to-End Mode).........................................................................................60 3.5.4 Configuration Process (Configuration on a Per-NE Basis).....................................................................66 3.5.5 Verifying E-Line Services.......................................................................................................................74 3.6 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Priorities) ................................................................................................................................................................................75 3.6.1 Networking Diagram...............................................................................................................................75 3.6.2 Service Planning......................................................................................................................................77 3.6.3 Configuration Process (in End-to-End Mode).........................................................................................80 3.6.4 Configuration Process (Configuration on a Per-NE Basis).....................................................................87 3.6.5 Verifying E-Line Services.......................................................................................................................95 3.7 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Switching) ................................................................................................................................................................................97 3.7.1 Networking Diagram...............................................................................................................................97 3.7.2 Service Planning......................................................................................................................................99 3.7.3 Configuration Process (in End-to-End Mode).......................................................................................102 3.7.4 Configuration Process (Configuration on a Per-NE Basis)...................................................................108 3.7.5 Verifying the Correctness of E-Line Service Configuration.................................................................117 3.8 Configuration Example: E-Line Services Carried by QinQ links..................................................................118 3.8.1 Networking Diagram.............................................................................................................................118 3.8.2 Service Planning....................................................................................................................................120 3.8.3 Configuration Process............................................................................................................................121 3.8.4 Verifying the Correctness of E-Line Service Configuration.................................................................124

4 Configuring E-LAN Services...................................................................................................127 4.1 Basic Concepts...............................................................................................................................................128 4.1.1 E-LAN Services.....................................................................................................................................128 4.1.2 UNI........................................................................................................................................................131 4.1.3 NNI........................................................................................................................................................132 4.1.4 Split Horizon Group..............................................................................................................................132 4.2 Configuration Flow for the E-LAN Services.................................................................................................133 Issue 03 (2013-02-20)


viii


Contents

4.2.1 E-LAN Services Carried by Ports ........................................................................................................133 4.2.2 E-LAN Services Carried by PWs .........................................................................................................138 4.2.3 E-LAN Services Carried by QinQ Links ..............................................................................................142 4.3 Configuration Example: E-LAN Services Carried by Ports...........................................................................146 4.3.1 Networking Diagram.............................................................................................................................146 4.3.2 Service Planning....................................................................................................................................147 4.3.3 Configuration Process............................................................................................................................149 4.3.4 Verifying the Correctness of E-LAN Service Configuration................................................................153 4.4 Configuration Example: E-LAN Services Carried by PWs...........................................................................155 4.4.1 Networking Diagram.............................................................................................................................156 4.4.2 Service Planning....................................................................................................................................157 4.4.3 Configuration Process (in End-to-End Mode).......................................................................................161 4.4.4 Configuration Process (Configuration on a Per-NE Basis)...................................................................163 4.4.5 Verifying the E-LAN Service Configuration........................................................................................169 4.5 Configuration Example: E-LAN Services Carried by QinQ links.................................................................170 4.5.1 Networking Diagram.............................................................................................................................170 4.5.2 Service Planning....................................................................................................................................171 4.5.3 Configuration Process............................................................................................................................173 4.5.4 Verifying the Correctness of E-LAN Service Configuration................................................................177

5 Configuring E-AGGR Services...............................................................................................180 5.1 Basic Concepts...............................................................................................................................................181 5.1.1 E-AGGR Services..................................................................................................................................181 5.1.2 UNI........................................................................................................................................................183 5.1.3 NNI........................................................................................................................................................184 5.2 Configuration Flow for the E-AGGR Services..............................................................................................184 5.2.1 E-AGGR Services Carried by Ports .....................................................................................................185 5.2.2 E-AGGR Services Carried by PWs ......................................................................................................189 5.3 Configuration Example: E-AGGR Services Carried by Ports........................................................................195 5.3.1 Networking Diagram.............................................................................................................................195 5.3.2 Service Planning....................................................................................................................................197 5.3.3 Configuration Process............................................................................................................................198 5.4 Configuration Example: E-AGGR Services Carried by PWs........................................................................203 5.4.1 Networking Diagram.............................................................................................................................203 5.4.2 Service Planning....................................................................................................................................205 5.4.3 Configuration Process (in End-to-End Mode).......................................................................................208 5.4.4 Configuration Process (Configuration on a Per-NE Basis)...................................................................211 5.5 Verifying the Correctness of E-AGGR Service Configuration......................................................................217

6 Configuring Cross-Domain Services.....................................................................................221 6.1 Introduction to the Cross-Connect Board.......................................................................................................222 6.2 Configuration Flow for the Cross-Domain Services......................................................................................223 6.3 Configuration Example (Application Scenario 1)..........................................................................................226 6.3.1 Networking Diagram.............................................................................................................................226 Issue 03 (2013-02-20)


ix


Contents

6.3.2 Service Planning....................................................................................................................................227 6.3.3 Configuration Process............................................................................................................................231 6.4 Configuration Example (Application Scenario 2)..........................................................................................235 6.4.1 Networking Diagram.............................................................................................................................235 6.4.2 Service Planning....................................................................................................................................236 6.4.3 Configuration Process............................................................................................................................240 6.5 Configuration Example (Application Scenario 3)..........................................................................................244 6.5.1 Networking Diagram.............................................................................................................................244 6.5.2 Service Planning....................................................................................................................................245 6.5.3 Configuration Process............................................................................................................................251 6.6 Testing Cross-domain Services......................................................................................................................255 6.6.1 Using the Ping Commands to Test Cross-domain Services..................................................................256 6.6.2 Using Loopbacks to Test Cross-domain Services.................................................................................258

7 Configuring CES Services........................................................................................................260 7.1 Introduction to CES........................................................................................................................................261 7.2 Configuration Flow for the CES Services......................................................................................................263 7.2.1 Configuration Flow for UNI-UNI CES Services..................................................................................263 7.2.2 Configuration Flow for the UNI-NNI CES Services.............................................................................264 7.3 Configuration Example (UNI-UNI CES Services)........................................................................................266 7.3.1 Networking Diagram.............................................................................................................................266 7.3.2 Service Planning....................................................................................................................................266 7.3.3 Configuration Process............................................................................................................................267 7.4 Configuration Example (UNI-NNI CES Services)........................................................................................270 7.4.1 Networking Diagram.............................................................................................................................270 7.4.2 Service Planning....................................................................................................................................271 7.4.3 Configuration Process (Configuration on a Per-NE Basis)...................................................................275 7.4.4 Configuration Process (in End-to-End Mode).......................................................................................281 7.5 Verifying CES Service Configuration............................................................................................................289

8 Configuring ATM Services......................................................................................................292 8.1 Introduction to ATM......................................................................................................................................293 8.2 Configuration Flow for the ATM Services.....................................................................................................294 8.2.1 Configuration Flow for UNI-UNI ATM Services.................................................................................294 8.2.2 Configuration Flow for UNIs-NNI ATM Services...............................................................................295 8.3 Configuration Example (UNI-UNI ATM Services).......................................................................................297 8.3.1 Network Diagram..................................................................................................................................297 8.3.2 Service Planning....................................................................................................................................298 8.3.3 Configuring an ATM Service on a Per-NE Basis..................................................................................300 8.4 Configuration Example (UNIs-NNI ATM Services).....................................................................................304 8.4.1 Network Diagram..................................................................................................................................304 8.4.2 Service Planning....................................................................................................................................306 8.4.3 Configuration Process (in End-to-End Mode).......................................................................................310 8.4.4 Configuration Process (Configuration on a Per-NE Basis)...................................................................335 Issue 03 (2013-02-20)


x


Contents

8.5 Verifying ATM Service Configuration..........................................................................................................355

9 Configuration Task Collection............................................................................................... 357 9.1 Configuring an Ethernet Port..........................................................................................................................360 9.1.1 Setting the General Attributes of Ethernet Interfaces............................................................................361 9.1.2 Setting the Layer 2 Attributes of Ethernet Ports....................................................................................362 9.1.3 Setting the Layer 3 Attributes of Ethernet Ports....................................................................................362 9.1.4 Setting the Advanced Attributes of Ethernet Ports................................................................................363 9.1.5 Configuring the Flow Control...............................................................................................................363 9.2 Configuring CES Ports...................................................................................................................................364 9.2.1 Configuring Channelized STM-1 Ports.................................................................................................364 9.2.2 Configuring E1 Ports.............................................................................................................................365 9.3 Configuring the NNIs.....................................................................................................................................366 9.3.1 Configuring the NNIs for Ethernet Services Carried by Ports..............................................................366 9.3.2 Configuring the NNIs for Ethernet Services Carried by Static MPLS Tunnels....................................367 9.3.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links...................................................368 9.4 Configuring an MPLS Tunnel........................................................................................................................369 9.4.1 Configuring LSR ID..............................................................................................................................369 9.4.2 Configuring an MPLS Tunnel on a Per-NE Basis.................................................................................370 9.4.2.1 Configuring a Unidirectional Static MPLS Tunnel on a Per-NE Basis.......................................370 9.4.2.2 Configuring a Bidirectional Static MPLS Tunnel on a Per-NE Basis..........................................372 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode........................................................................373 9.4.3.1 Configuring a Static and Unidirectional MPLS Tunnel in End-to-End Mode.............................374 9.4.3.2 Configuring a Static and Bidirectional MPLS Tunnel in End-to-End Mode...............................376 9.5 Managing MPLS Tunnels...............................................................................................................................378 9.5.1 Searching for MPLS Tunnels................................................................................................................379 9.5.2 Checking the MPLS Tunnel Topology..................................................................................................379 9.5.3 Duplicating MPLS Tunnels...................................................................................................................380 9.5.4 Deploying MPLS Tunnels.....................................................................................................................381 9.5.5 Deleting MPLS Tunnels........................................................................................................................382 9.5.6 Managing Discrete MPLS Tunnels.......................................................................................................383 9.6 Configuring MPLS OAM...............................................................................................................................383 9.6.1 Configuring the MPLS OAM on a Per-NE Basis..................................................................................383 9.6.2 Configuring MPLS OAM in End-to-End Mode....................................................................................386 9.7 Configuring MPLS Tunnel APS.....................................................................................................................388 9.7.1 Configuring MPLS Tunnel APS on a Per-NE Basis.............................................................................389 9.7.2 Configuring an MPLS Tunnel APS in End-to-End Mode.....................................................................390 9.8 Managing MPLS Tunnel APS Protection Groups..........................................................................................392 9.8.1 Automatically Discovering Protection Groups......................................................................................392 9.8.2 Deploying MPLS Tunnel APS Protection Groups................................................................................393 9.8.3 Ranaming an MPLS Tunnel APS Protection Group.............................................................................393 9.8.4 Deleting MPLS Tunnel APS Protection Groups...................................................................................394 9.9 Operation Tasks for Configuring E-Line Services.........................................................................................395 Issue 03 (2013-02-20)


xi


Contents

9.9.1 Configuring UNI-UNI E-Line Services................................................................................................395 9.9.2 Configuring UNI-NNI E-Line Services Carried by Ports.....................................................................397 9.9.3 Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis........................................398 9.9.4 Configuring E-Line Services Carried by PWs in End-to-End Mode....................................................400 9.9.5 Creating UNI-NNI E-Line Services Carried by QinQ Links................................................................402 9.10 Operation Task for Configuring E-LAN Services........................................................................................403 9.10.1 Configuring E-LAN Services Carried by Ports...................................................................................404 9.10.2 Creating E-LAN Services Carried by PWs on a Per-NE Basis...........................................................406 9.10.3 Configuring E-LAN Services Carried by PWs in End-to-End Mode.................................................408 9.10.4 Configuring E-LAN Services Carried by QinQ Links........................................................................410 9.11 Configuring E-AGGR Services....................................................................................................................413 9.11.1 Configuring E-AGGR Services Carried by Ports................................................................................413 9.11.2 Creating E-AGGR Services Carried by PWs on a Per-NE Basis........................................................414 9.11.3 Creating E-AGGR Services Carried by PWs in End-to-End Mode....................................................416 9.12 Configuring Transit Nodes for Ethernet Services........................................................................................418 9.12.1 Configuring Transit NEs for Ethernet Services Carried by Ports........................................................418 9.12.2 Configuring Transit NEs for Ethernet Services Carried by PWs........................................................419 9.12.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links.............................................420 9.13 Operation Tasks for Configuring CES Services...........................................................................................421 9.13.1 Creating UNI-UNI CES Services on a Per-NE Basis..........................................................................421 9.13.2 Creating UNI-NNI CES Services on a Per-NE Basis..........................................................................422 9.13.3 Creating a CES Service in End-to-End Mode.....................................................................................424 9.14 Configuring Transit NEs for CES Services..................................................................................................428 9.15 Configuring ATM PWE3 Services...............................................................................................................428 9.15.1 Configuring ATM Interfaces...............................................................................................................428 9.15.2 Configuring an ATM Policy Profile....................................................................................................433 9.15.3 Configuring an ATM CoS Mapping Profile........................................................................................434 9.15.4 Creating an ATM Service by Using the Trail Function......................................................................436 9.15.5 Creating ATM Services on a Per-NE Basis.........................................................................................438 9.16 Managing PWE3 Services............................................................................................................................441 9.16.1 Searching for PWE3 Services..............................................................................................................442 9.16.2 Checking the PWE3 Service Status.....................................................................................................442 9.16.3 Deploying PWE3 Services..................................................................................................................443 9.16.4 Modifying PWE3 Services..................................................................................................................444 9.16.5 Deleting PWE3 Services.....................................................................................................................445 9.16.6 Managing Discrete PWE3 Services.....................................................................................................445 9.17 Managing Composite Services.....................................................................................................................446 9.17.1 Automatically Discovering Composite Services.................................................................................446 9.17.2 Deploying Composite Services...........................................................................................................447 9.18 Configuring Address Resolution..................................................................................................................448 9.19 Configuring the NE-Level TPID..................................................................................................................449 9.20 Creating a QinQ Link...................................................................................................................................449 Issue 03 (2013-02-20)


xii


Contents

9.21 Creating a V-UNI Group..............................................................................................................................450 9.22 Managing the Blacklist.................................................................................................................................451

10 Parameter Description............................................................................................................453 10.1 Parameter Description: Attributes of Ethernet Interface .............................................................................455 10.1.1 General Attributes................................................................................................................................455 10.1.2 Flow Control........................................................................................................................................456 10.1.3 Layer 2 Attributes................................................................................................................................459 10.1.4 Layer 3 Attributes................................................................................................................................461 10.1.5 Advanced Attributes............................................................................................................................462 10.2 Parameter Description: MPLS......................................................................................................................464 10.2.1 Basic Configuration.............................................................................................................................464 10.2.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis).......................................................464 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode).......................................................469 10.3 Parameter Description: E-Line Service........................................................................................................476 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis)..........................................................476 10.3.2 E-Line Service Parameters (Configuration in End-to-End Mode)......................................................478 10.3.3 UNI Parameters...................................................................................................................................489 10.3.4 NNI Parameters...................................................................................................................................490 10.3.5 Maintenance Association.....................................................................................................................493 10.3.6 MEP Point............................................................................................................................................494 10.4 Parameter Description: E-LAN Service.......................................................................................................495 10.4.1 E-LAN Service Parameters (Configuration on a Per-NE Basis).........................................................495 10.4.2 E-LAN Service Parameters (Configuration in End-to-End Mode).....................................................496 10.4.3 UNI Parameters...................................................................................................................................507 10.4.4 NNI Parameters...................................................................................................................................508 10.4.5 Split Horizon Group............................................................................................................................512 10.4.6 MAC Address Learning Parameters....................................................................................................512 10.4.7 Unknown Frame Processing................................................................................................................513 10.4.8 Static MAC Address............................................................................................................................514 10.4.9 Maintenance Association.....................................................................................................................514 10.4.10 MEP Point..........................................................................................................................................515 10.4.11 V-UNI Group.....................................................................................................................................516 10.5 Parameter Description: E-AGGR Service....................................................................................................517 10.5.1 E-AGGR Service Parameters (on a Per-NE Basis).............................................................................517 10.5.2 Parameters for Configuring E-AGGR Services (End-to-End Mode)..................................................517 10.5.3 UNI Parameters...................................................................................................................................522 10.5.4 NNI Parameters...................................................................................................................................523 10.5.5 VLAN Forwarding Table Item............................................................................................................526 10.5.6 Maintenance Association.....................................................................................................................527 10.5.7 MEP Point............................................................................................................................................528 10.6 Parameter Description: CES Port.................................................................................................................528 10.6.1 Channelized STM-1 Port.....................................................................................................................528 Issue 03 (2013-02-20)


xiii


Contents

10.6.2 E1 Port.................................................................................................................................................532 10.7 Parameter Description: CES Services..........................................................................................................535 10.7.1 Basic Configuration Parameters (UNI-UNI).......................................................................................535 10.7.2 Basic Configuration Parameters (UNI-NNI).......................................................................................536 10.7.3 QoS (UNI-NNI)...................................................................................................................................539 10.7.4 Advanced Attributes (UNI-NNI).........................................................................................................540 10.7.5 Parameters for Configuring CES Services (End-to-End Mode)..........................................................544 10.8 Parameter Description: ATM/IMA Services................................................................................................547 10.8.1 Creating an ATM Service....................................................................................................................547 10.8.2 Connection...........................................................................................................................................549 10.8.3 CoS Mapping.......................................................................................................................................552 10.8.4 Configuring an ATM Service Class Mapping Table...........................................................................552 10.8.5 ATM Policies.......................................................................................................................................553 10.8.6 SDH Interface......................................................................................................................................559 10.8.7 IMA Group Management....................................................................................................................562 10.9 Parameter Description: MPLS OAM...........................................................................................................567 10.9.1 Tunnel OAM Parameters.....................................................................................................................567 10.9.2 Ping Test..............................................................................................................................................570 10.9.3 Traceroute Test....................................................................................................................................570 10.10 Parameter Description: MPLS Tunnel APS...............................................................................................571 10.10.1 Parameters for Configuring MPLS Tunnel APS (on a Per-NE Basis)..............................................571 10.10.2 Parameters for Configuring MPLS Tunnel APS (in End-to-End Mode)..........................................572 10.11 Parameter Description: Inband DCN..........................................................................................................575 10.11.1 Port Settings.......................................................................................................................................575 10.11.2 Access Control...................................................................................................................................576 10.11.3 Bandwidth Management....................................................................................................................577 10.12 Parameter Description: QinQ Link Configuration Parameters...................................................................577 10.13 Parameter Description: Address Parse.......................................................................................................579

A List of Parameters.....................................................................................................................580 A.1 Ethernet Port Associated Parameters (Packet Mode)....................................................................................582 A.1.1 MAC Loopback(Ethernet Interface).....................................................................................................582 A.1.2 PHY Loopback(Ethernet Interface)......................................................................................................583 A.1.3 Enable Port(Ethernet Interface)............................................................................................................584 A.1.4 Encapsulation Type(Ethernet Interface)...............................................................................................585 A.1.5 Working Mode(Ethernet Interface)......................................................................................................586 A.1.6 Max Frame Length(byte) for an Ethernet Port.....................................................................................587 A.1.7 Enable Tunnel(Ethernet Interface)........................................................................................................588 A.1.8 Specify IP(Ethernet Interface)..............................................................................................................589 A.2 Ethernet Port Associated Parameters (TDM Mode)......................................................................................590 A.2.1 Port Attribute (Ethernet Port)...............................................................................................................590 A.2.2 Enable Port (Ethernet Port Attribute)...................................................................................................592 A.2.3 Max. Frame Length (Ethernet Port Attribute)......................................................................................592 Issue 03 (2013-02-20)


xiv


Contents

A.2.4 Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute)...................................................593 A.2.5 Autonegotiation Flow Control Mode (Ethernet Port Attribute)...........................................................594 A.2.6 MAC Loopback (Ethernet Port Attribute)............................................................................................595 A.2.7 PHY Loopback (Ethernet Port Attribute).............................................................................................596 A.2.8 QinQ Type Area...................................................................................................................................597 A.2.9 Loop Detection (Ethernet Port Attribute).............................................................................................598 A.2.10 Loop Port Shutdown (Ethernet Port Attribute)...................................................................................598 A.2.11 Traffic Threshold(Mpbs)(External Ethernet Port Attribute)..............................................................599 A.2.12 Broadcast Packet Suppression Threshold (Ethernet Interface Attributes)..........................................599 A.2.13 Enabling Broadcast Packet Suppression (Ethernet Interface Attributes)...........................................600 A.2.14 Zero-Flow Monitor (Ethernet Interface Attributes)............................................................................601 A.2.15 Port Traffic Threshold Time Window(Min).......................................................................................601 A.2.16 Jumbo Frame Type.............................................................................................................................602 A.2.17 Default VLAN ID (Ethernet Port Attribute).......................................................................................603 A.2.18 VLAN Priority (Ethernet Port Attribute)............................................................................................603 A.2.19 Entry Detection (Ethernet Port Attribute)...........................................................................................604 A.2.20 Tag Identifier......................................................................................................................................605 A.2.21 Mapping Protocol...............................................................................................................................606 A.2.22 Scramble.............................................................................................................................................608 A.2.23 Set Inverse Value for CRC.................................................................................................................609 A.2.24 Check Field Length.............................................................................................................................609 A.2.25 FCS Calculated Bit Sequence.............................................................................................................610 A.2.26 Extension Header Option....................................................................................................................612 A.3 Ethernet Service Associated Parameters (Packet Mode)...............................................................................613 A.3.1 PW Signaling Type(PW Management)................................................................................................613 A.3.2 Bearer Type (E-Line Service)...............................................................................................................614 A.3.3 PW ID(E-Line Service)........................................................................................................................614 A.3.4 BPDU....................................................................................................................................................615 A.3.5 MTU(bytes)(E-Line Service)................................................................................................................616 A.3.6 Static MAC Address (E-LAN Service)................................................................................................617 A.3.7 Self-Learning MAC Address (E-LAN Service)...................................................................................618 A.3.8 Aging Time (min)(E-LAN Service).....................................................................................................619 A.3.9 Default Forwarding Priority.................................................................................................................620 A.3.10 Default Packet Relabeling Color(E-LAN Service).............................................................................621 A.3.11 Split Horizon Group ID(E-LAN Service)...........................................................................................622 A.3.12 Split Horizon Group Member (E-LAN Service)................................................................................623 A.3.13 Source Interface Type(E-AGGR Service)..........................................................................................623 A.3.14 Sink Interface Type(E-AGGR Service)..............................................................................................624 A.4 CES Service Associated Parameters..............................................................................................................625 A.4.1 Packet Loading Time (us).....................................................................................................................625 A.4.2 RTP Header..........................................................................................................................................626 A.4.3 Jitter Compensation Buffering Time (us).............................................................................................627 Issue 03 (2013-02-20)


xv


Contents

A.4.4 Clock Mode..........................................................................................................................................629 A.5 Data Service Associated Parameters (TDM Mode).......................................................................................630 A.5.1 Operation Type (EPL Service).............................................................................................................630 A.5.2 Service Type (EPL Service).................................................................................................................632 A.5.3 Encapsulation Format of P Port (Network Attributes).........................................................................633 A.5.4 C-VLAN and S-VLAN.........................................................................................................................634 A.5.5 VLAN ID (For Creation of Ethernet Virtual Private Lines).................................................................635 A.5.6 MAC Address Aging Time / Aging Time Unit....................................................................................636 A.5.7 Hub/Spoke (Ethernet LAN Service).....................................................................................................637 A.5.8 Actual MAC Address Table Capacity (Ethernet LAN Service)...........................................................637 A.5.9 Specified MAC Address Table Capacity (Ethernet LAN Service)......................................................638 A.5.10 Bridge Learning Mode (Ethernet LAN Service)................................................................................640 A.5.11 Self-learning MAC Address (Ethernet LAN Service)........................................................................641 A.5.12 Tunnel.................................................................................................................................................641 A.5.13 VC.......................................................................................................................................................642 A.5.14 Operation Type(IEEE 802.1ad Bridge)..............................................................................................643 A.5.15 Bridge Type........................................................................................................................................644 A.5.16 SAN Service Type..............................................................................................................................645 A.5.17 Concatenation Level (SAN)...............................................................................................................646 A.5.18 Enabled Flow Control of FC Port.......................................................................................................646 A.5.19 Initial Value of CREDIT at the Client Side........................................................................................647 A.5.20 Initial Value of CREDIT at the WAN Side........................................................................................648 A.6 ETH OAM Associated Parameters (Packet Mode).......................................................................................649 A.6.1 CC Test Transmit Period(Ethernet Service OAM Management).........................................................649 A.6.2 Maintenance Domain Level(Ethernet Service OAM Management)....................................................650 A.6.3 CC Status(Ethernet Service OAM Management).................................................................................651 A.6.4 Service Name(Ethernet Service OAM Management)..........................................................................651 A.6.5 Service Type(Ethernet Service OAM Management)............................................................................652 A.6.6 Activation Status(Ethernet Service OAM Management).....................................................................653 A.6.7 Transmitted Packet Count(Ethernet Service OAM Management).......................................................654 A.6.8 Transmitted Packet Length(Ethernet Service OAM Management)......................................................655 A.6.9 Transmitted Packet Priority (Ethernet Service OAM Management)....................................................655 A.6.10 Destination Maintenance Point MAC Address(Ethernet Service OAM Management).....................656 A.6.11 Response Maintenance Point ID(Ethernet Service OAM Management)...........................................656 A.6.12 Hop Count(Ethernet Service OAM Management).............................................................................657 A.6.13 Test Result(Ethernet Service OAM Management).............................................................................658 A.7 ETH-OAM Associated Parameters (TDM Mode).........................................................................................658 A.7.1 MP ID (Ethernet OAM)........................................................................................................................658 A.7.2 Maintenance Point Type (Ethernet OAM)...........................................................................................659 A.7.3 CC Status (Ethernet OAM)...................................................................................................................660 A.7.4 CC Activate Flag..................................................................................................................................660 A.7.5 Test Result (LB and LT Test)...............................................................................................................661 Issue 03 (2013-02-20)


xvi


Contents

A.7.6 Responding MP Type (Ethernet LT Test)............................................................................................662 A.7.7 Hop Count (Ethernet LT Test)..............................................................................................................662 A.7.8 Send Mode (Ping Test).........................................................................................................................663 A.7.9 Packet Length (Ping Test)....................................................................................................................664 A.7.10 Timeout (Ping Test)............................................................................................................................664 A.7.11 Time To Live......................................................................................................................................665 A.7.12 Delay...................................................................................................................................................665 A.7.13 Average Delay....................................................................................................................................666 A.7.14 Max. Delay.........................................................................................................................................666 A.7.15 Min. Delay..........................................................................................................................................667 A.7.16 Detect Attempts..................................................................................................................................667 A.7.17 Send Direction (Ethernet Test)...........................................................................................................668 A.7.18 Error Frame Monitor Window(ms)....................................................................................................669 A.7.19 Error Frame Monitor Threshold (Entries)..........................................................................................669 A.7.20 Error Frame Period Window (Frame).................................................................................................670 A.7.21 Error Frame Monitor Threshold (Frame)...........................................................................................671 A.7.22 Error Frame Second Window(s).........................................................................................................671 A.7.23 Error Frame Second Threshold(s)......................................................................................................672 A.7.24 Enable OAM Protocol........................................................................................................................673 A.7.25 OAM Working Mode.........................................................................................................................673 A.7.26 Remote Alarm Support for Link Event..............................................................................................674 A.7.27 Unidirectional Operation....................................................................................................................674 A.7.28 Loopback Status (OAM Parameter)...................................................................................................675 A.8 PW Associated Parameters............................................................................................................................676 A.8.1 Control Word........................................................................................................................................676 A.8.2 Control Channel Type...........................................................................................................................677 A.8.3 VCCV Verification Mode.....................................................................................................................678 A.8.4 Request VLAN.....................................................................................................................................679 A.8.5 Competitive Working Status.................................................................................................................680 A.8.6 Associate AC State...............................................................................................................................681 A.8.7 Max.Concatenated Cell Count..............................................................................................................681 A.9 PW APS Protection Associated Parameters (Packet Mode)..........................................................................682 A.9.1 Protection Mode....................................................................................................................................682 A.9.2 Protection Mode....................................................................................................................................683 A.9.3 Switchover Status.................................................................................................................................684 A.9.4 Protocol Status......................................................................................................................................687 A.9.5 PW Type...............................................................................................................................................688 A.10 HQoS Associated Parameters......................................................................................................................689 A.10.1 Traffic Classification Rule(Policy Management)...............................................................................689 A.10.2 Match Type(Policy Management)......................................................................................................690 A.10.3 Match Value(Policy Management).....................................................................................................693 A.10.4 Wildcard(Policy Management)...........................................................................................................695 Issue 03 (2013-02-20)


xvii


Contents

A.10.5 PW Direction(PW Policy)..................................................................................................................698 A.10.6 Direction (PW Policy)........................................................................................................................698 A.10.7 Duplicated Policy Name(PW Policy).................................................................................................699 A.10.8 Policy ID(Policy Management)..........................................................................................................699 A.10.9 Policy Name (Policy Management)....................................................................................................700 A.10.10 QinQ Link ID(QinQ Policy).............................................................................................................701 A.10.11 Physical Port ID(QinQ Policy).........................................................................................................701 A.10.12 S-VLAN ID(QinQ Policy)................................................................................................................701 A.10.13 Traffic Classification Bandwidth Sharing(Policy Management)......................................................702 A.10.14 Coloring Mode (V-UNI Ingress Policy)...........................................................................................703 A.10.15 Logical Relation Between Matched Rules(V-UNI Ingress Policy)..................................................704 A.10.16 Processing Mode(V-UNI Ingress Policy).........................................................................................705 A.10.17 AF1 Schedule Weight(%)(WFQ Schedule Policy)..........................................................................706 A.10.18 AF2 Schedule Weight(%)(WFQ Schedule Policy)..........................................................................706 A.10.19 AF3 Schedule Weight(%)(WFQ Schedule Policy)..........................................................................707 A.10.20 AF4 Schedule Weight(%)(WFQ Schedule Policy)..........................................................................708 A.10.21 Discard Lower Threshold (256 bytes) (Service WRED Policy).......................................................708 A.10.22 Discard Upper Threshold (256 bytes) (Service WRED Policy).......................................................709 A.10.23 Discard Probability (%) (Service WRED Policy)............................................................................710 A.10.24 PHB (Diffserv domain Management)...............................................................................................710 A.10.25 Packet Type (Diffserv domain Management)...................................................................................711 A.10.26 Committed Information Rate (Kbit/s)..............................................................................................712 A.10.27 Committed Burst Size (byte)............................................................................................................713 A.10.28 Peak Information Rate (kbit/s)..........................................................................................................713 A.10.29 Peak Burst Size (byte)......................................................................................................................714 A.10.30 EXP...................................................................................................................................................715 A.10.31 LSP Mode.........................................................................................................................................716 A.11 QoS Associated Parameters.........................................................................................................................717 A.11.1 Flow Type (Flow Configuration)........................................................................................................717 A.11.2 Bound CAR (Flow Configuration).....................................................................................................718 A.11.3 Bound CoS (Flow Configuration)......................................................................................................719 A.11.4 CAR ID (CAR Configuration)............................................................................................................719 A.11.5 CAR Enabled/Disabled (CAR Configuration)...................................................................................720 A.11.6 Committed Information Rate (CAR Configuration)...........................................................................721 A.11.7 Committed Burst Size (CAR Configuration).....................................................................................722 A.11.8 Peak Information Rate (CAR Configuration).....................................................................................722 A.11.9 Maximum Burst Size (CAR Configuration).......................................................................................723 A.11.10 CoS ID (CoS Configuration)............................................................................................................724 A.11.11 CoS Type (CoS Configuration)........................................................................................................725 A.11.12 CoS Priority (CoS Configuration)....................................................................................................726 A.11.13 Shaping.............................................................................................................................................729 A.12 ATM Interface Associated Parameters (Packet Mode)...............................................................................730 Issue 03 (2013-02-20)


xviii


Contents

A.12.1 ATM Cell Payload Scrambling(ATM Interface Management)..........................................................730 A.12.2 Min.VPI(ATM Interface Management)..............................................................................................731 A.12.3 Min.VCI(ATM Interface Management).............................................................................................732 A.12.4 VCC-Supported VPI Count(ATM Interface Management)................................................................733 A.13 ATM/IMA Services Associated Parameters (Packet Mode).......................................................................734 A.13.1 IMA Transit Frame Length.................................................................................................................734 A.13.2 IMA Symmetry Mode.........................................................................................................................735 A.13.3 Maximum Delay Between Links(ms)(IMA Group Management).....................................................736 A.13.4 Minimum Number of Active Transmitting Links(IMA Group Management)...................................737 A.13.5 Minimum Number of Active Receiving Links(IMA Group Management).......................................738 A.13.6 Clock Mode(IMA Group Management).............................................................................................739 A.13.7 Near-End Group Status(IMA Group Status)......................................................................................740 A.13.8 Differential Delay Check Status(IMA Link States)............................................................................741 A.13.9 Connection Type(Per-NE ATM Service Management).....................................................................742 A.13.10 Uplink Policy(Per-NE Configuration for ATM Connections).........................................................743 A.13.11 Downlink Policy(Per-NE Configuration for ATM Connections)....................................................744 A.13.12 CoS Mapping(Per-NE Configuration for CoS Mapping).................................................................745 A.13.13 Traffic Service(ATM Policy)...........................................................................................................745 A.13.14 Clp01Pcr(cell/s)(ATM Policy).........................................................................................................749 A.13.15 Clp01Scr(cell/s)(ATM Policy).........................................................................................................751 A.13.16 Clp0Pcr(cell/s)(ATM Policy)...........................................................................................................753 A.13.17 Clp0Scr(cell/s)(ATM Policy)...........................................................................................................755 A.13.18 Clp01Mcr(cell/s)(ATM Policy)........................................................................................................757 A.13.19 Max.Cell Burst Size(cell)(ATM Policy)...........................................................................................759 A.13.20 Cell Delay Variation Tolerance(0.1us)(ATM Policy)......................................................................760 A.13.21 UPC/NPC(ATM Policy)...................................................................................................................762 A.14 ATM OAM Associated Parameters (Packet Mode)....................................................................................763 A.14.1 Connection Direction..........................................................................................................................763 A.14.2 Segment and End Attribute.................................................................................................................764 A.14.3 Country Code(Hexadecimal Code).....................................................................................................766 A.14.4 Network Code(Hexadecimal Code)....................................................................................................767 A.14.5 NE Code(Hexadecimal Code)............................................................................................................768 A.15 ATM/IMA Associated Parameters (TDM Mode).......................................................................................769 A.15.1 VCTRUNK Port (ATM Bound Path Management)...........................................................................769 A.15.2 Level (ATM Bound Path Management).............................................................................................772 A.15.3 Direction (ATM Bound Path Management).......................................................................................773 A.15.4 Port (ATM Port Management)............................................................................................................774 A.15.5 Port Type (ATM Port Management)..................................................................................................777 A.15.6 Max. VPI Bits.....................................................................................................................................777 A.15.7 Max. VCI Bits.....................................................................................................................................778 A.15.8 Max. VPC...........................................................................................................................................779 A.15.9 Max. VCC...........................................................................................................................................779 Issue 03 (2013-02-20)


xix


Contents

A.15.10 VPC Configured...............................................................................................................................780 A.15.11 VCC Configured...............................................................................................................................781 A.15.12 Number of VPI that Supports VCC..................................................................................................781 A.15.13 UPC/NPC Enabled/Disabled............................................................................................................782 A.15.14 Positive UPC/NPC(ATM Service Management).............................................................................783 A.15.15 ID (ATM Traffic Management)........................................................................................................784 A.15.16 Traffic Type (ATM Traffic Management)........................................................................................785 A.15.17 Service Type (ATM Traffic Management).......................................................................................789 A.15.18 PCR (ATM Traffic Management)....................................................................................................792 A.15.19 SCR (ATM Traffic Management)....................................................................................................793 A.15.20 MBS..................................................................................................................................................794 A.15.21 CDVT...............................................................................................................................................795 A.15.22 Open Flow Frame Discarding Flag...................................................................................................795 A.15.23 Positive Traffic Descriptor...............................................................................................................796 A.15.24 Connection ID (ATM Service Management)...................................................................................797 A.15.25 Connection Type (ATM Service Management)...............................................................................798 A.15.26 Spread Type (ATM Service Management).......................................................................................799 A.15.27 VPI and VCI (ATM Service Management)......................................................................................801 A.15.28 Positive Service Status(ATM Service Management).......................................................................803 A.15.29 Positive Service Failure Reason(ATM Service Management).........................................................804 A.15.30 Source/Sink Switching Cause...........................................................................................................805 A.15.31 Protection Type (ATM Service Management).................................................................................806 A.15.32 Switching Direction (ATM Service Management)...........................................................................808 A.15.33 Switching Status (ATM Service Management)................................................................................808 A.15.34 Switching Type (ATM Service Management).................................................................................809 A.15.35 Revertive Mode (ATM Service Management).................................................................................811 A.15.36 Pause Time(0-100) *100 ms (ATM Service Management)..............................................................811 A.15.37 WTR Time(0-30min) (ATM Service Management)........................................................................812 A.15.38 External Command (ATM Protection Group)..................................................................................812 A.15.39 IMA Group Number.........................................................................................................................813 A.15.40 IMA Protocol Version......................................................................................................................814 A.15.41 IMA Transmit Frame Length............................................................................................................815 A.15.42 IMA Group Configuration Mode......................................................................................................815 A.15.43 Minimum Number of Active Links..................................................................................................818 A.15.44 IMA Group Status.............................................................................................................................819 A.15.45 Protocol Mode (IMA1.0 Mode)........................................................................................................820 A.15.46 Enable/Disable Cell Payload Scramble............................................................................................821 A.15.47 Link Frame Format...........................................................................................................................821 A.15.48 Connection Direction (ATM Segment End Attribute).....................................................................822 A.15.49 Segment and End Attribute (ATM Segment End Attribute)............................................................823 A.15.50 LLID.................................................................................................................................................825 A.15.51 Maximum Ingress Bandwidth...........................................................................................................826 Issue 03 (2013-02-20)


xx


Contents

A.15.52 Maximum Egress Bandwidth...........................................................................................................826 A.16 RPR Associated Parameters........................................................................................................................827 A.16.1 RPR Node ID......................................................................................................................................827 A.16.2 RPR Protocol......................................................................................................................................828 A.16.3 RPR Node Protection Slow Timer Value(ms)....................................................................................829 A.16.4 RPR ATD Timer Value(s)..................................................................................................................830 A.16.5 RPR Protection Mode.........................................................................................................................830 A.16.6 RPR Hold-off Time(ms).....................................................................................................................833 A.16.7 RPR Protection Restoration Mode......................................................................................................834 A.16.8 RPR Protection Wait-to-restore(s)......................................................................................................835 A.16.9 RPR Send link weight.........................................................................................................................836 A.16.10 RPR Used and Reserved bandwidth of priority A............................................................................837 A.16.11 RPR Used bandwidth of priority B-CIR(Mbps)...............................................................................838 A.16.12 RPR Circle Name.............................................................................................................................839 A.16.13 RPR Node Reachability....................................................................................................................840 A.16.14 RPR Node Hop.................................................................................................................................841 A.16.15 RPR Adjacent node ID.....................................................................................................................841 A.16.16 RPR Node Direction.........................................................................................................................842 A.16.17 ECHO Path ID (RPR Node Information).........................................................................................843 A.16.18 ECHO Working Mode (RPR Node Information).............................................................................843 A.16.19 ECHO Request Loop (RPR Node Information)...............................................................................845 A.16.20 ECHO Response Loop (RPR Node Information).............................................................................845 A.16.21 ECHO Frame Service Type (RPR Node Information).....................................................................846 A.16.22 Is ECHO Path Protected (RPR Node Information)..........................................................................847 A.16.23 ECHO T1 Transmit Period (RPR Node Information)......................................................................848 A.16.24 ECHO T2 Response Time (RPR Node Information).......................................................................849 A.16.25 Number of Echo Messages Received (RPR Node Information)......................................................849 A.16.26 Successfully Processed (RPR Node Information)............................................................................850 A.16.27 Unsuccessfully Processed (RPR Node Information)........................................................................850 A.16.28 dLoc Detected (RPR Node Information)..........................................................................................851 A.16.29 Loc Detected (RPR Node Information)............................................................................................852 A.16.30 RPR Node Protection Status.............................................................................................................852 A.16.31 RPR Node Switching Status.............................................................................................................854 A.16.32 RPR Node Accumulated Protection Times......................................................................................854 A.16.33 RPR Node Accumulated Protection Time........................................................................................855 A.16.34 RPR Node Last Switch Request.......................................................................................................855 A.16.35 RPR Switch Request.........................................................................................................................856 A.17 LAG Associated Parameters (TDM Mode).................................................................................................857 A.17.1 LAG Type(Link Aggregation Group Management)...........................................................................857 A.17.2 Revertive Mode(Link Aggregation Group Management)..................................................................858 A.17.3 Load Sharing(Link Aggregation Group Management)......................................................................859 A.17.4 Load Sharing Hash Algorithm(Link Aggregation Group Management)............................................860 Issue 03 (2013-02-20)


xxi


Contents

A.17.5 System Priority(Link Aggregation Group Management)...................................................................861 A.17.6 Main Port(Link Aggregation Group Management)............................................................................862 A.17.7 Main Port Status(Link Aggregation Group Management).................................................................863 A.17.8 Port Priority(Link Aggregation Group Management)........................................................................864 A.18 MC-LAG Associated Parameters................................................................................................................865 A.18.1 Protocol Channel ID...........................................................................................................................865 A.18.2 Hello Packet Sending Interval (s).......................................................................................................866 A.18.3 Timeout Time (s)................................................................................................................................866 A.19 LAG/DLAG Associated Parameters (TDM Mode).....................................................................................867 A.19.1 Port Priority (Link Aggregation)........................................................................................................867 A.19.2 System Priority (Link Aggregation)...................................................................................................868 A.19.3 Slave Port (Link Aggregation)............................................................................................................868 A.19.4 Status (Link Aggregation)..................................................................................................................869 A.19.5 Branch Port.........................................................................................................................................870 A.19.6 Load Sharing(Ethernet Link Aggregation).........................................................................................871 A.19.7 Revertive Mode (DLAG)....................................................................................................................872 A.19.8 Main Port Priority (DLAG)................................................................................................................873 A.19.9 Slave Port Priority (DLAG)................................................................................................................874 A.20 STP/RSTP Associated Parameters..............................................................................................................874 A.20.1 Protocol Enabled (Spanning Tree)......................................................................................................874 A.20.2 Protocol Type (Spanning Tree Protocol)............................................................................................875 A.20.3 VB Priority (Bridge Parameters)........................................................................................................876 A.20.4 Max Age(s).........................................................................................................................................876 A.20.5 Hello Time(s) (Spanning Tree)...........................................................................................................877 A.20.6 Forward Delay(s) (Spanning Tree).....................................................................................................878 A.20.7 TxHoldCount(per second) (Spanning Tree).......................................................................................878 A.20.8 Root Path Cost....................................................................................................................................879 A.20.9 Hold Count (Spanning Tree)..............................................................................................................879 A.20.10 Port ID..............................................................................................................................................880 A.20.11 Port Path Cost...................................................................................................................................880 A.20.12 Designated Path Cost........................................................................................................................882 A.20.13 Designated Root Bridge Priority......................................................................................................883 A.20.14 Designated Bridge Priority(Spanning Tree).....................................................................................883 A.20.15 Designated Bridge MAC Address (Spanning Tree).........................................................................884 A.20.16 Protocol Enabled (Port Parameter of Spanning Tree)......................................................................884 A.20.17 Admin Edge Attribute.......................................................................................................................885 A.20.18 Edge Port Status (Spanning Tree).....................................................................................................886 A.20.19 VB Port Priority................................................................................................................................887 A.20.20 VB Port Status..................................................................................................................................887 A.20.21 Point to Point Attributes(External Ethernet Port Attributes)............................................................888 A.21 LCAS Associated Parameters......................................................................................................................889 A.21.1 Enabling LCAS...................................................................................................................................889 Issue 03 (2013-02-20)


xxii


Contents

A.21.2 LCAS Mode........................................................................................................................................890 A.21.3 Hold off Time(ms) (LCAS)................................................................................................................891 A.21.4 WTR Time(s) (LCAS)........................................................................................................................891 A.21.5 TSD (LCAS).......................................................................................................................................892 A.21.6 Minimum Number of Members in the Transmit Direction................................................................892 A.22 Packet LPT Associated Parameters.............................................................................................................893 A.22.1 Binding Status.....................................................................................................................................893 A.22.2 Primary Function Point.......................................................................................................................894 A.22.3 Secondary Function Point Type..........................................................................................................895 A.22.4 Secondary Function Point...................................................................................................................895 A.22.5 Fault Detection Mode.........................................................................................................................896 A.22.6 User-Side Port Status..........................................................................................................................897 A.23 LPT Associated Parameters (TDM Mode)..................................................................................................898 A.23.1 LPT.....................................................................................................................................................898 A.23.2 Bearer Mode.......................................................................................................................................899 A.23.3 Port-Type Port Hold-Off Time(ms)....................................................................................................899 A.23.4 VCTRUNK Port Hold-off Time(ms)..................................................................................................900 A.24 IGMP Snooping Associated Parameters......................................................................................................900 A.24.1 Protocol Enable (IGMP Snooping Protocol)......................................................................................900 A.24.2 Multicast Aging Time.........................................................................................................................901 A.25 Test Frame Associated Parameters..............................................................................................................902 A.25.1 Frames to Send...................................................................................................................................902 A.25.2 Status...................................................................................................................................................903 A.25.3 Counter of Frames Sent......................................................................................................................903 A.25.4 Counter of Received Response Test Frame........................................................................................904 A.25.5 Counter of Test Frames to Receive....................................................................................................904 A.25.6 Bearer Mode (Ethernet Test)..............................................................................................................905 A.25.7 Send Mode (Ethernet Test).................................................................................................................906 A.26 Orderwire Associated Parameters................................................................................................................906 A.26.1 Call Waiting Time(s)..........................................................................................................................907 A.26.2 Conference Call..................................................................................................................................907 A.26.3 Phone..................................................................................................................................................908 A.26.4 Available Orderwire Port....................................................................................................................909 A.26.5 Available Conference Call Port..........................................................................................................909 A.26.6 Subnet No. Length..............................................................................................................................910 A.26.7 Subnet (Subnet No. for the Optical Interface)....................................................................................911 A.26.8 No.(F1 Data Port)...............................................................................................................................912 A.26.9 Data Channel (F1 Data Port)..............................................................................................................912 A.26.10 Overhead Byte (Broadcast Data Port)..............................................................................................913 A.26.11 Working Mode (Broadcast Data Port)..............................................................................................914 A.26.12 Broadcast Data Source (Broadcast Data Port)..................................................................................915 A.26.13 Broadcast Data Sink (Broadcast Data Port)......................................................................................916 Issue 03 (2013-02-20)


xxiii


Contents

A.27 Clock Associated Parameters......................................................................................................................916 A.27.1 External Clock Output Mode..............................................................................................................917 A.27.2 External Clock Output Timeslot.........................................................................................................917 A.27.3 External Source Output Threshold.....................................................................................................919 A.27.4 2M Phase-Locked Source Fail Condition...........................................................................................920 A.27.5 2M Phase-Locked Source Fail Action................................................................................................921 A.27.6 Clock Source Priority Sequence (1 Is the Highest)............................................................................922 A.27.7 Clock Source Threshold.....................................................................................................................923 A.27.8 Protection Status.................................................................................................................................924 A.27.9 AIS Alarm Generated.........................................................................................................................925 A.27.10 B1 BER Threshold-Crossing Generated...........................................................................................926 A.27.11 B2-EXC Alarm Generated................................................................................................................927 A.27.12 Higher Priority Clock Source Reversion Mode................................................................................928 A.27.13 Clock Source WTR Time.................................................................................................................929 A.27.14 Switching Status (Clock)..................................................................................................................929 A.27.15 Lock Status (Clock)..........................................................................................................................930 A.27.16 Clock Source ID...............................................................................................................................931 A.27.17 Synchronous Source.........................................................................................................................932 A.27.18 Synchronous Status Byte..................................................................................................................933 A.27.19 S1 Byte Synchronization Quality Information.................................................................................934 A.27.20 NE Clock Working Mode.................................................................................................................935 A.27.21 Clock Source Quality........................................................................................................................936 A.27.22 S1 Byte Received..............................................................................................................................938 A.27.23 Line Port (Clock)..............................................................................................................................939 A.27.24 Control Status (Clock)......................................................................................................................940 A.27.25 Line Port (Clock ID).........................................................................................................................941 A.27.26 Enabled Status (Clock ID)................................................................................................................942 A.27.27 Data Output Method in Holdover Mode...........................................................................................943 A.27.28 Manual Setting of 0 Quality Level...................................................................................................944 A.27.29 Retiming Mode.................................................................................................................................945 A.28 Protection Associated Parameters................................................................................................................946 A.28.1 Switching Mode (MSP)......................................................................................................................946 A.28.2 Initiation Condition (SNCP)...............................................................................................................947 A.28.3 Group Type (SNCP)...........................................................................................................................948 A.28.4 Configure SNCP Tangent Ring..........................................................................................................949 A.28.5 Source(Sink)Timeslot Range(e.g.1,3-6).............................................................................................949 A.28.6 Switching Status (BPS).......................................................................................................................950 A.28.7 Switching Status (PPS).......................................................................................................................951 A.28.8 External Switching Command Type (BPS)........................................................................................952 A.28.9 External Switching Command Type (PPS)........................................................................................953 A.29 Other Parameters.........................................................................................................................................954 A.29.1 E1/T1 Interconnection........................................................................................................................954 Issue 03 (2013-02-20)


xxiv


Contents

A.29.2 T1 Frame Structure.............................................................................................................................955 A.29.3 E1 Frame Structure.............................................................................................................................956 A.29.4 Service Mode......................................................................................................................................957 A.29.5 Service Type.......................................................................................................................................958 A.29.6 Service Frame Format.........................................................................................................................959 A.29.7 Connection Mode (NE Attribute).......................................................................................................960 A.29.8 Enable Tandem Connection at the Source..........................................................................................961 A.29.9 APId to be Sent at the Source.............................................................................................................962 A.29.10 Optimize Higher Order Pass-Through..............................................................................................962

B Glossary......................................................................................................................................964

Issue 03 (2013-02-20)


xxv


1 Getting Started

1

Getting Started

About This Chapter The following topices introduce some preparation operations that will ensure a smooth, troublefree launch of the U2000. 1.1 Starting or Shutting Down the U2000 The U2000 uses the standard client/server architecture and multiple-user mode. So, you are recommended to start or shut down the U2000 by strictly observing the following procedure, in order not to affect other users that are operating the U2000. 1.2 Main Windows and Common Operations of the U2000 This topic describes the main windows of the U2000 client. Learning the main windows helps you to locate the entrances to operations quickly, which increased your operation efficiency.

Issue 03 (2013-02-20)


1


1 Getting Started

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

Context l

You are recommended to start the computer and the U2000 application in the following sequence: Start the computer, start the U2000 server, and then start the U2000 client.

l

You are recommended to shut down the U2000 application and the computer in the following sequence: Exit the U2000 client, stop the U2000 server, and then shut down the computer.

1.1.1 Starting the U2000 Server For network management first start the U2000 server, and then start the U2000 application.

Prerequisites l

The computer time must be set correctly.

l

The computer where the U2000 is installed must be started correctly.

l

The operating system of the U2000 server must be running correctly and the database must be started normally.

l

The instance must be deployed.

Procedure Step 1 Double-click the U2000 Server shortcut icon to start System Monitor Client. Step 2 In the Login dialog box, set the username (admin, by default) and the password (null, by default). You need to change the password when logging in for the first time. Then click Login. NOTE

Periodically change the password and memorize it.

You can login to the U2000 client, checking whether the status of each process is Running. ----End

1.1.2 Logging In to the U2000 Client To manage networks through the U2000 client graphical user interface, you need to use the U2000 client to log in to the U2000 server.

Prerequisites The U2000 server must be started correctly.

Issue 03 (2013-02-20)


2


1 Getting Started

Procedure Step 1 Double-click the U2000 Client shortcut icon. Step 2 In the Login dialog box, set the username (admin, by default) and the password (null, by default). You need to change the password when logging in for the first time. Then click Login. Step 3 Optional: For the first login, you need to configure the access control list of the system. ----End

1.1.3 Exiting a U2000 Client Before shutting down the U2000 server, you must exit the U2000 client.

Prerequisites The U2000 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 to save the changes. After you confirm the dialog box, automatically exit the client.

----End

1.1.4 Shutting Down the U2000 Server When the U2000 server is managing the system normally, do not perform this operation. In special circumstances, for example, when modifying the system time of the computer where the U2000 resides, or when upgrading the version, you can use the System Monitor Client to shut down the U2000 server.

Prerequisites All the U2000 clients connected to the U2000 server must be shut down.

Procedure Step 1 From the Main Menu of System Monitor Client, choose System > Stop All NMS Services to close all processes of the U2000 server. Step 2 Click OK in the confirmation dialog box. Wait until the U2000 core process, and the processes that are optional according to the actual situation are in the Stopped state. Now the U2000 server is shut down successfully. Now you cannot shut down the MDP process or initialize the database. ----End Issue 03 (2013-02-20)


3


1 Getting Started

1.2 Main Windows and Common Operations of the U2000 This topic describes the main windows of the U2000 client. Learning the main windows helps you to locate the entrances to operations quickly, which increased your operation efficiency.

1.2.1 Components of the Client GUI This topic describes the components of the client GUI. Figure 1-1 shows the client GUI. Figure 1-1 Client GUI

1: Menu bar

2: Toolbar

3: Workbench list

4: Output pane

5: Status bar

6: Workbench

Menu Bar The menu bar provides the entries to all the functions of the U2000 client. It consists of the following menus: File, Fault, Performance,Configuration, Service, Inventory, Administration, Window, and Help. In the topology window, the menu bar also provides the Edit and View menu items.

Issue 03 (2013-02-20)


4


1 Getting Started

Toolbar The toolbar provides the shortcut icons for major operation tasks. The shortcut icons are as follows: l

: Workbench.

l

: Exit.

l

: Lock Terminal.

l

: Log Out.

l

: Full Screen.

l

: Browse Current Alarm.

l

: Create Fiber.

l

: NE Explorer.

l

: Main Topology.

l

: Browse SDH performance.

l

: Browse WDM performance.

l

: SDH Protection Subnet Maintenance.

l

: WDM Trail Management.

l

: SDH Trail Creation.

l

: SDH Trail Management.

Workbench list You can create or modify a workbench through the shortcut icons.

Output Pane The output pane displays the returned information and other relevant information.

Status Bar The status bar displays the information such as the system status, the login users, and the IP address of the connected server. The information displayed from left to right is as follows: l

Connection information: Displays the name and IP address of the server.

l

Login user: Displays the name of the login user.

l

Connection duration: Displays the duration of the connection between the client and the server.

Issue 03 (2013-02-20)


5


1 Getting Started

l

Login mode: Displays the login mode. It can be single-user mode and multi-user mode.

l

Operation prompt: Displays the result of the operation.

l

Logo: Displays the logo of Huawei Technologies Co., Ltd.

Workbench The shortcut icons on the workbench help you perform operations.

1.2.2 Key GUI Components The key U2000 GUI components are as follows: Component

Example

Button Shortcut icon Radio button Check box Tab Field

Drop-down menu

Menu Function Tree

Issue 03 (2013-02-20)


6


Component

1 Getting Started

Example

Dialog box

1.2.3 Frequently Used Buttons The frequently used buttons on the U2000 GUI are as follows: Button

Functionality Selects the objects. Expands all available options. Collapses all available options. Displays or hides a dialog box.

Selects the objects.

Selects the objects as a batch.

Increases the priority of the selected object. Decreases the priority of the selected object. Displays a dialog box.

Issue 03 (2013-02-20)


7


Button

1 Getting Started

Functionality Queries results from the NE. Imposes the current settings. Displays the latest result(s). Exports the selected scheduled tasks to the browser of the operating system for printing. Saves selected data to the specified file. Makes the current setting effective and closes the dialog box. Cancels the current setting and closes the dialog box. Closes the operation wizard. Allows the user to view and select the board ports. Deletes the selected data or icon. Creates a new service, protection or physical inventory information etc. Proceeds to the next step. Returns to the previous step. Closes the dialog box. Expands the Object Tree. Collapses the Object Tree. Makes the current setting effective and closes the dialog box. Cancels the current setting and closes the dialog box. Search the correlative information.

Issue 03 (2013-02-20)


8


1 Getting Started

Button

Functionality Sets the correlative condition.

1.2.4 Shortcut Icon This topic describes the shortcut icons on the Main Topology. You can customize the toolbar so that only the frequently-used buttons are displayed on the toolbar. To customize the toolbar, right-click the toolbar and choose a menu item from the shortcut menu. Button

Issue 03 (2013-02-20)

Name

Description

Workbench

Adds the commonly used functions to the favorites folder.

Exit

Exits from the client.

Lock Terminal

Locks the current client.

Main Topology

Switches to the Main Topology.

Log Out

Logs out of the current session.

Full Screen.

Views the current window in full screen.

Browse Current Alarm

Displays the Current Alarms window.

SDH Protection Subnet Maintenance

Accesses the SDH Protection Subnet Common Attributes window.

SDH Trail Management

Accesses the SDH Trail Management window.

SDH Trail Creation

Accesses the SDH Trail Creation window.

WDM Trail Management

Accesses the WDM Trail Management window.

NE Explorer

Accesses the NE Explorer window of the selected NE.

Create Link

Creates fiber and radio links.


9


Button

1 Getting Started

Name

Description

Browse SDH Performance

Accesses the Browse SDH Performance window.

Browse WDM Performance

Accesses the Browse WDM Performance window.

New

Selects Custom View, NESubnet, or Link from the drop-down list box.

Up

Returns to the previous level.

Zoom out

Zooms out the Main Topology.

Zoom in

Zooms in the Main Topology.

Zoom in Partially

Zooms in an area selected in the Main Topology.

View Move

Moves the Main Topology. When you click this icon, the Main Topology can be moved. When you click the icon again, the Main Topology cannot be moved.

Alarm List Area

Views the alarm list area in the lower part of the Main Topology.

Search NE

Searches for an NE in the view.

Select

Selects the NE in the Main Topology.

Topology Navigator

Views the navigation tree in the Topology.

Filter Tree and Legend

Opens the setting area of the view to display the filter plane and legends.

Device Statistics

Views the quantity of the equipment on the network.

Save the Location of the Current Submap Icons

Saves the location of the current submap icons.

Refresh View

Refreshes the current view.

Lock View

Locks out the position of an NE icon in the active view.

Unlock View

Unlocks the position of an NE icon in the active view.

Issue 03 (2013-02-20)


10


Button

1 Getting Started

Name

Description

NE Time Sychronization

Synchronizes the NE time and NMS time.

Synchronize Current Alarms

Synchronizes the current alarms of an NE.

Browse Current ALarms

Browses the current alarms of an NE.

Clear ALarm Indication

Clears the current alarm indications of an NE.

Refresh NE Panel Status

Refreshes the NE panel status to make the NE panel display the latest data.

Back Up NE Database To SCC

Backs up the NE data to the SCC.

Display/Hide Extended Slot

Displays or hides the extended slot on the Extended Slot tab page.

Legend

Displays a legend and its description.

1.2.5 Common Shortcut Keys This topic describes the common shortcut keys. Using shortcut keys, you can increase the operation efficiency. The shortcut keys include Enter, Ctrl, Esc, and Tab.

Issue 03 (2013-02-20)

Shortcut Key

Description

F1

Opens the Help.

Enter

Confirms the operation or moves downward to the next line. If the cursor is on a button, pressing Enter means to confirm the operation. If the cursor is in the list box, press Enter once and the cursor then moves downward to the next line.

Esc

Closes a dialog box.

Tab

Switches between buttons if the cursor is on a button. Switch between text boxes if the cursor is in the list box.

Ctrl+F

Searches resources such as the NEs, subnets, cards, frames, interfaces, and VLANs in basic and rapid modes by pressing Ctrl+F in all views.

Ctrl+A

Selects all NEs or selects all contents in the list. If the cursor is in the view, press Ctrl+A to select all NEs. If the cursor is in the list box, press Ctrl+A to select all contents in the list.

Ctrl+C

Quickly copies the table texts.

Ctrl+V

Pastes the copied data to another text area. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

11


1 Getting Started

Shortcut Key

Description

Alt+F

Opens the File menu from the Main Menu.

Alt+E

Opens the Edit menu from the Main Menu.

Alt+V

Opens the View menu from the Main Menu.

Alt+U

Opens the Fault menu from the Main Menu.

Alt+P

Opens the Performance menu from the Main Menu.

Alt+C

Opens the Configuration menu from the Main Menu.

Alt+R

Opens the Service menu from the Main Menu.

Alt+I

Opens the Inventory menu from the Main Menu.

Alt+S

Opens the Administration menu from the Main Menu.

Alt+W

Opens the Window menu from the Main Menu.

Alt+H

Opens the Help menu from the Main Menu.

1.2.6 Main Windows This topic describes the main windows of the U2000 client. And tells you what you can do in the windows.

1.2.6.1 Workbench This topic describes the workbench. After a client is started, the system automatically accesses the default workbench. The default shortcut icons are displayed on the workbench. l

In the main window of the U2000, click the drop-down button to the right of the and then select Workbench to access the workbench.

l

You can do as follows to modify a workbench: Right-click the icon of the workbench and choose Modify Workbench from the shortcut menu to modify the name or description of a workbench.

l

You can expand and order workbenches to separate the customized workbenches from the default workbench.

l

You can view the description about the function of the workbench in the background picture of the workbench and press F1 to view the Help. Alternatively, you can choose Help > Workbench from the shortcut menu to view the Help.

icon

1.2.6.2 Main Topology This topic describes the items in the Main Topology. All topology management functions can be accessed through the Main Topology in . These functions include creating topological objects, subnets, searching for the existing equipment in the network. You can search, view, create, set, and manage subnets; and search, create, configure, and maintain management functions on trails. Issue 03 (2013-02-20)


12


1 Getting Started

GUI To open the Main Topology, log in to the U2000. If the preceding operation closes the Main Topology, you can choose Window > Main Topology from the main menu to open the Main Topology. Figure 1-2 shows the Main Topology of the U2000. Figure 1-2 Main Topology

2

1

6

8

7

1: Network management system name

Issue 03 (2013-02-20)

4

3

9

5

10

11 12

2: Menu bar

3: Shortcut button

You can operate the NM and the NE with submenu bar, include configure tasks, manage tasks and so on.

Click the button, you can perform a simple task quickly. For example: exit NM, lock terminal, log out, NMS user management, stop the current alarm sound, browse alarm, NE explorer, creating connections,, browse performance window.


13


1 Getting Started

4: Shortcut button

5: Alarm button bar

6: NMS status bar

Click the button, you can perform a simple task quickly on the Main Topology. For example: zoom in or zoom out or refresh or save the view, show or hide the navigators, search objects, see object attributes, lock or unlock the view.

The Alarm buttons for alarms at different severity levels are in different colors. You can click the button to view the number of the alarms generated on the current U2000. You can click the button to view current alarms. For example: browsing the alarm list, show alarm panel.

Views the running information of the NMS. For example, NMS login, and loading of each module.

When the U2000 has abnormal events, the Abnormal event indicator turn to red from green. You can click the indicator to view current abnormal events. 7: Views the current location 8: Physical Map of the cursor in the Main Views the managed Topology. equipment. On the Physics Map, you can perform operations, such as creating NEs, deleting topology objects, NE explorer, creating connections, browsing fibers/cables, configuring the NE data, browse performance window, and so on. 10: Views user name of the logged-in U2000 user currently.

11: Filter Tree and Legend In this area, you can set the display types of the objects in a view, and view the descriptions of legends in the view. To locate an operation object quickly.

9: Views the name which is set by the current U2000 client, and views the IP address of the current U2000 server.

12: Total elapsed time after the current user is logged in to the U2000.

1.2.6.3 NE Explorer The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE Explorer is the main user interface for commissioning and configuration on a per-NE basis. The NE Explorer contains a Function Tree that makes the operations easy. To display the configuration window for an object, the user can just select the object and then choose a desired function in the Function Tree. Issue 03 (2013-02-20)


14


1 Getting Started

NOTE

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

GUI l

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

l

In the left-hand pane of the Main Topology, right-click an NE and choose NE Explorer from the shortcut menu.

Correlation operation l

Click the

in NE Explorer window, display the NE Panel.

l

Click the

in NE Explorer window, switch to other NE.

1.2.6.4 Clock View The Clock View provides a visible platform to enable NE clock settings, networkwide clock synchronization status query, and clock tracing and search functions.

GUI Access the clock view. In the Main Topology window, select Clock View from the Current View drop-down list. Select the NE to be queried or configured from the object tree. Figure 1-3 shows the clock view.

Issue 03 (2013-02-20)


15


1 Getting Started

Figure 1-3 Clock View

Legends l

By choosing View > Display Setting > Legend from the main menu, you can learn meanings of various legends in different colors in the Clock View.

l

By choosing View > Display Setting > Filter from the main menu, you can display the required elements in the Clock View based on the filter function.

l

The Clock View uses continuous lines to represent the trace relations between NEs. Smaller number indicates higher priority. The number displayed on the continuous line indicates the priority of the traceable clock. The Clock View displays the line clock source numbers only. Internal and tributary clock sources are also numbered, but they are not displayed in the Clock View.

l

The arrow direction in the Clock View indicates the clock tracing direction. For example, if NE2 points to NE3, it indicates that NE3 traces the clock information transmitted from NE2, and that NE3 traces the primary PRC NE1-External 1.

l

The arrow direction in the Clock View indicates the clock tracing direction.

l

An internal clock source is the clock provided by an NE, and has no trace relations with other NEs. Therefore, internal clock sources are not displayed on the Clock View.

l

Tributary clock sources have no relation with the clock sources that are not provided by the U2000. Therefore, the clock trace relations are not displayed on the Clock View.

Issue 03 (2013-02-20)


16


l

1 Getting Started

In the Clock View, you can select multiple NEs, right-click, and query the clock synchronization status or search for clock trace relations. NOTE

The rule of verifying an invalid clock tracing relation is as follows: First, verify whether a clock source is in the SSM protocol mode. In the non-SSM protocol mode, verify the status of a clock source. The status directly determines whether a clock tracing relation is invalid. In the SSM protocol mode, verify the status of a clock source. If the status is unavailable, it indicates that the clock tracing relation is invalid. If the status is available, you also need to verify the S1 byte (clock quality). When you manually cancel settings of the quality of the S1 byte and the quality of the S1 byte is unknown, the clock tracing relation is invalid.

1.2.6.5 NE Panel The NE Panel displays boards and ports in different colors depending on their current status. In the U2000, most operations such as equipment configuration, monitoring, and maintenance are performed in the NE Panel window.

GUI Double-click an NE on the Main Topology to display the NE Panel. To add a new board, right-click an idle slot and choose a board type. NOTE

l Choose the Always On Top for the Slot Layout window to always remain on top. l When a board occupies multiple slots, the slot ID of the main slot is displayed in boldface, and the slot ID of the slave slot is grayed out. l In the NE panel, when you click the processing board that is accompanied by an interface board, the slot ID of this interface board is displayed in orange.

Click the icon on the toolbar, to view the legends of the boards and ports on the right of the Slot Layout. To select an operation related to an installed board, right-click the installed board and choose it from the shortcut menu. For example, right-click an AUX board and choose Path View to display the detailed path information.

1.2.6.6 Browse Alarm This topic describes the user interface for viewing the current and history alarms, Alarm Logs. In this user interface, buttons are provided, such as Filter, Synchronize, Refresh, and Acknowledge, to help you quickly locate the alarm cause.

GUI l

Choose Fault > Browse Current Alarm from the main menu.

l

Choose Fault > Browse History Alarm from the main menu.

l

Choose Fault > Query Alarm Logs from the main menu.

1.2.6.7 Browse Event In the Browse Event window, you can view events at different levels. This window provides buttons, such as Filter by Template, Filter and Refresh, to help you to quickly locate the alarm cause. Issue 03 (2013-02-20)


17


1 Getting Started

GUI Choose Fault > Browse Event Logs from the main menu.

1.2.6.8 Browse Performance Window You can view the current and history performance data, UAT events and performance threshold crossings.

GUI Choose Performance > Browse SDH Performance from the main menu.

Issue 03 (2013-02-20)


18


2 Creating the Network

2

Creating the Network

About This Chapter NEs and fibers/cables can be managed on the NMS only after their topologies are created. 2.1 Creating NEs, Fibers and Subnet Network services and protection schemes can be configured only after NEs, optical fibers, and topology subnets are created.

Issue 03 (2013-02-20)


19


2 Creating the Network

2.1 Creating NEs, Fibers and Subnet Network services and protection schemes can be configured only after NEs, optical fibers, and topology subnets are created. Item

Procedure

Creating NEs

Creating a Single NE Creating NEs in Batches Configuring the NE Data Manually Replicating the NE Data Uploading the NE Data

Creating optical fibers

Creating Fibers in the TDM Domain Automatically Creating Fibers Manually Creating Virtual Fibers Creating DCN Communication Cable

Creating topology subnets

Issue 03 (2013-02-20)

Creating a Topology Subnet


20


3

3 Configuring E-Line Services

Configuring E-Line Services

About This Chapter You can configure the E-Line services to realize the point-to-point transmission of Ethernet services. 3.1 Basic Concepts Learning about the basic concepts helps to further understand E-Line services. 3.2 Configuration Flow for the E-Line Services The flowchart for configuring an E-Line service differs according to the type of the E-Line service. 3.3 Configuration Example: UNI-UNI E-Line Services This topic uses an example to describe how to plan the engineering information and how to configure the UNI-UNI E-Line services for each NE according to the networking diagram. 3.4 Configuration Example: E-Line Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by ports for each NE according to the networking diagram. 3.5 Configuration Example: E-Line Services Carried by PWs (Newly Created) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs for each NE according to the networking diagram. 3.6 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Priorities) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs for each NE according to the networking diagram. In this example, services with a same VLAN ID but different VLAN priorities need to be mapped to different PWs. 3.7 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Switching) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs (network adjustment based on VLAN switching) for each NE according to the networking diagram. 3.8 Configuration Example: E-Line Services Carried by QinQ links Issue 03 (2013-02-20)


21



This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by QinQ links for each NE according to the networking diagram.

Issue 03 (2013-02-20)


22



3.1 Basic Concepts Learning about the basic concepts helps to further understand E-Line services.

3.1.1 E-Line Services In the topology, the E-Line services are point-to-point services. The E-Line services realize the point-to-point transmission of Ethernet services. According to the service transmission mode, the E-Line services can be classified into the following types: l

UNI-UNI E-Line services

l

E-Line services carried by ports

l

E-Line services carried by pseudo wires (PWs) (newly created)

l

E-Line services carried by PWs (network adjustment based on VLAN priorities)

l

E-Line services carried by PWs (network adjustment based on VLAN switching)

l

E-Line services carried by QinQ links

UNI-UNI E-Line Services Figure 3-1 shows the networking diagram of the UNI-UNI E-Line service. Company A and Company B are located in City 1 and need to communicate with each other. Company A and Company B are connected to the same NE. Hence, you can configure the Ethernet services from the UNI to the UNI to realize the communication between Company A and Company B. In this case, the equipment equals a Layer 2 switch, which only exchanges the data of Company A and Company B. In the uplink direction of the UNI at the two ends, complex traffic classification can be performed for data packets, and different QoS policies can be used according to the traffic types. Figure 3-1 UNI-UNI E-Line services NE2 UNI

Company A

Company B

PSN

UNI

City 1

Issue 03 (2013-02-20)

NE3

NE1

NE4


23



E-Line Services Carried by Ports Figure 3-2 shows the networking diagram of the E-Line services carried by ports. Branches of Company A are located in City 1 and City 2, and need to communicate with each other. Hence, you can configure the E-Line services that are carried by ports and from the UNI to the NNI, to realize the communication between the branches of Company A. In this case, each branch of Company A can use the UNI exclusively. An E-Line service exclusively occupies all the physical ports on the network across which the E-Line travels. If the services of the departments of Company A in City 1 need to be isolated from each other, you can distinguish different services on the same UNI by using the "port+VLANs" mode. On a single station, in the uplink direction of the UNI at the two ends, complex traffic classification can be performed for data packets, and different QoS policies can be used according to the traffic types. Figure 3-2 E-Line services carried by ports

NE1

NE2

PSN

Company A Company A

City 2

City 1 UNI

NNI

NNI

UNI

E-Line Services Carried by PWs (Newly Created) Figure 3-3 shows the networking diagram of the E-Line services carried by PWs. The branches of Company A and Company B are located in City 1 and City 2, and need to communicate with each other. The services of Company A and Company B need to be isolated from each other. In this case, you can configure the E-Line services that are carried by PWs and from the UNI to the NNI, to realize the communication between the branches of Company A or Company B. In addition, different services are carried by different PWs, realizing the isolation of the services of Company A from the services of Company B. The services that are accessed from the UNI are encapsulated and transmitted to the PWs. Then, the services are transmitted through the tunnel. The E-Line services of different companies are carried by different PWs and then to the same port on the NNI. In this manner, the port resources on the NNI are saved and the bandwidth utilization is increased. In the uplink direction of the UNI, layered QoS configuration can be performed for data packets.

Issue 03 (2013-02-20)


24



Figure 3-3 E-Line services carried by PWs (newly created)

PSN

NE1

NE2

Company A

Company A

Company B Company B

UNI

City 1

NNI

NNI

UNI

City2

Tunnel PW

E-Line Services Carried by PWs (Network Adjustment Based on VLAN Priorities) Figure 3-4 shows the networking diagram of the E-Line services carried by PWs (network adjustment based on VLAN priorities). This type of E-Line maps packets with a same VLAN ID but different VLAN priorities to different PWs. Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100 but different VLAN priorities, and need to be transported to a same RNC. Services from NodeB 1 have a VLAN priority of 3, and services from NodeB 2 have a VLAN priority of 2. To isolate services from NodeB 1 and services from NodeB 2, the services are mapped to different PWs based on Port+VLAN+VLAN PRI before being transported to the RNC. The services that are received from the UNI are encapsulated into PWs and then carried on tunnels. In the uplink direction of the UNI, hierarchical QoS configuration can be performed for data packets. Figure 3-4 E-Line services carried by PWs (network adjustment based on VLAN priorities) UNI

NNI

UNI

NNI

NNI PSN NodeB 1 VLAN: 100 PRI: 3 NE2

NE1

NodeB 2 VLAN: 100 PRI: 2

Issue 03 (2013-02-20)

NNI

NE3

NNI

RNC

NNI MPLS tunnel PW


25



E-Line Services Carried by PWs (Network Adjustment Based on VLAN Switching) Figure 3-5 shows the networking diagram of the E-Line services carried by PWs (network adjustment based on VLAN switching). To transport different NodeBs' services that have a same VLAN ID but are previously transported to different RNCs to a same RNC, this type of E-Line enables VLAN switching to isolate the services before they are transported to the RNC. Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100, and need to be transported to a same RNC. To isolate services from NodeB 1 and services from NodeB 2, VLAN switching is required. After VLAN switching, the VLAN ID of services from NodeB 1 remains unchanged, whereas the VLAN ID of services from NodeB 2 is changed to 200. The services that are received from the UNI are encapsulated into PWs and then carried on tunnels. In the uplink direction of the UNI, hierarchical QoS configuration can be performed for data packets. Figure 3-5 E-Line services carried by PWs (network adjustment based on VLAN switching) NodeB 1 VLAN: 100

NodeB 1 VLAN: 100

NodeB 2 VLAN: 100

NodeB 2 VLAN: 200 NNI

UNI

UNI NNI

NNI PSN NodeB 1 NE2

NE1

NodeB 2

NNI

NE3

NNI

RNC

NNI MPLS tunnel PW

E-Line Services Carried by QinQ Links During the transmission on QinQ links, the packets that carry C-VLAN tags on the user-side network are added with S-VLAN tags. Then the packets are sent across the network when carrying two layers of VLAN tags. In this manner, the L2-VPN tunnel which is simple is provided to the user. Figure 3-6 shows the networking diagram of the E-Line services carried by QinQ links. The branches of Company A and Company B are located in City 1 and City 2, and need to communicate with each other. The services of Company A and Company B need to be isolated from each other. The internal VLANs of Company A range from 1 to 100. The internal VLANs of Company B range from 1 to 200. In this case, you can configure the E-Line services that are carried by QinQ links and from the UNI to the NNI, to realize the communication between the branches of Company A or Company B. Different services are carried by QinQ links with different VLAN IDs, realizing the isolation of the services of Company A from the services of Company B and saving the VLAN resources on the packet switching network. The packets of different companies that are accessed from the UNI are added with different VLAN IDs and then transmitted on the same link on the NNI. Issue 03 (2013-02-20)


26



The E-Line services of different companies are added with a layer of VLAN tags each and then transmitted to the same port. In this manner, the port resources on the NNI are saved and the bandwidth utilization is increased. In addition, the E-Line services carried by QinQ links occupy few VLANs on the packet switching network, saving the VLAN resources on the packet switching network. You can configure the QinQ policy to realize the QoS for the services carried by QinQ links. Figure 3-6 E-Line services carried by QinQ links Intranet of Company A VLAN = 1-100 An outer tag (VLAN = 30) is added to the packets of Company A NE1 City 1

Company A

PSN Intranet of Company A VLAN = 1-100 NE2 Company B

Intranet of Company B VLAN = 1-200

An outer tag (VLAN = 40) is added to the packets of Company B

Company A

City 2

Company B

QinQ link

Intranet of Company B VLAN = 1-200

3.1.2 UNI A UNI refers to the Ethernet port that is connected to the user equipment. A UNI is used for the user-side configuration of an Ethernet service.

V-UNI A V-UNI is a virtual user-network interface. Each service on a UNI corresponds to a logical VUNI. A UNI can receive multiple services. That is, a UNI may correspond to multiple V-UNIs.

V-UNI Group A V-UNI group contains multiple V-UNIs, and limits the total bandwidth of the Ethernet services received on the member V-UNIs. For a user or an Ethernet service that has multiple access points, you can add the access points to a V-UNI group and set a total bandwidth for the V-UNI group. Bandwidth parameters include committed information rate (CIR), maximum burst size, peak bandwidth, and committed burst size. Issue 03 (2013-02-20)


27



V-UNIs in a V-UNI group share the total bandwidth but their bandwidths are limited by the total bandwidth. To be specific, when the bandwidth of member A does not reach the CIR, member B can use the remaining bandwidth; when the bandwidths of member A and member B do not reach the CIR but their sum exceeds the total bandwidth of the V-UNI group, member A and member B pre-empt the bandwidth based on service priorities. Multiple V-UNIs on a board can be added to a V-UNI group. V-UNIs in a V-UNI group can be changed/deleted at any time, and values of bandwidth parameters can also be modified at any time.

3.1.3 NNI An NNI refers to the Ethernet port that is connected to the packet transport network. An NNI is used for the network-side configuration of an Ethernet service. Based on the modes of carrying services, NNIs can be classified into three types, namely, NNIs carrying services by ports, NNIs carrying services by PWs, and NNIs carrying services by QinQ links.

Ethernet Services Carried by Ports In the case of the NNIs that carry Ethernet services by ports, the encapsulation type can be 802.1Q or QinQ. In this case, the NNIs that an Ethernet service traverses are exclusively occupied. The other physical ports that the Ethernet service traverses may be shared.

Ethernet Services Carried by PWs In the case of the NNIs that carry Ethernet services by PWs, you need to create static MPLS tunnels for the NNIs. To create the Ethernet services carried by PWs, you need to create the PWs first. In this case, different Ethernet services can be encapsulated into different PWs and transmitted in a tunnel to the same NNI. Therefore, the occupied NNIs are reduced and the bandwidth utilization is improved.

Ethernet Services Carried by QinQ Links In the case of the NNIs that carry Ethernet services by QinQ links, you need to create QinQ links for the NNIs. The port attribute and the encapsulation mode of the NNIs corresponding to the QinQ links are Layer 2 and QinQ, respectively. On a QinQ link, the packets that are accessed are encapsulated with one layer of VLAN tags in QinQ encapsulation mode at the access ports. In this manner, multiple packets with different VLAN tags from the user-side network can be encapsulated into the same VLAN for transport. Therefore, the occupied VLAN resources on the transport network are reduced. E-Line services and E-LAN services can be carried by the QinQ link on the network side. In this case, the packets of different companies that are accessed on the user side are added with different VLAN tags and then are transmitted by the same QinQ link on the network side.

3.2 Configuration Flow for the E-Line Services The flowchart for configuring an E-Line service differs according to the type of the E-Line service.

Issue 03 (2013-02-20)


28



3.2.1 Configuration Flow for the UNI-UNI E-Line Services You need not configure the NNIs when configuring the UNI-UNI E-Line services. Table 3-1 provides the process for configuring the UNI-UNI E-Line services. Figure 3-7 Configuration flow for the UNI-UNI E-Line services Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port

Configure the QoS

Create the UNI-UNI E-Line services

Create the V-UNI group End

Issue 03 (2013-02-20)


29



Table 3-1 Configuration flow for the UNI-UNI E-Line services Step

Operation

1

Configuring the UNI (when the UNI is an Ethernet port)

Remarks 9.1.1 Setting the General Attributes of Ethernet Interfaces

(Required) The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


30


Step


Operation

Remarks 9.1.2 Setting the Layer 2 Attributes of Ethernet Ports

(Optional) The parameters are set as follows: l Tag needs to be set according to the type of the packets that are transmitted from the equipment on the opposite end. – If all the packets are untagged frames, Tag is set to Access. – If all the packets are tagged frames, Tag is set to Tag Aware. – If the packets contain untagged frames and tagged frames, Tag is set to Hybrid. l When Tag is set to Access or Hybrid, the Default VLAN ID and VLAN Priority parameters need to be set for the untagged frames. VLAN Priority needs to be set according to the planned QoS.

Issue 03 (2013-02-20)


31


Step


Operation

Remarks 9.1.5 Configuring the Flow Control

(Optional) The parameters are set as follows: l Generally, the packet switched network (PSN) adopts the QoS scheme to prevent link congestion. Hence, AutoNegotiation Flow Control Mode and NonAutonegotiation Flow Control Mode need to be set to the default value Disabled, unless otherwise specified.

2


(Optional) This operation is applicable only when the UNI is an Ethernet port. The parameters are set as follows: l The UNI is used for connecting the external equipment and need not transmit in-band DCN information. Hence, DCN Enabled State needs to be set to Disabled for the UNI.

Issue 03 (2013-02-20)

3

Configuring the HQoS

(Optional) The parameters need to be set according to the service QoS planning.

4

9.9.1 Configuring UNI-UNI E-Line Services

(Required) The parameters need to be set according to the service planning.


32



Step

Operation

Remarks

5

9.21 Creating a V-UNI Group

(Optional) The parameters need to be set according to the service planning.

3.2.2 E-Line Services Carried by Ports You need not configure the MPLS tunnel or QinQ link when configuring the E-Line services carried by ports. Table 3-2 provides the process for configuring the E-Line services carried by ports. Figure 3-8 Configuration flow for the E-Line services carried by ports Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by ports

Configure the QoS

Create the E-Line services carried by ports Create the V-UNI group End

Issue 03 (2013-02-20)


33



Table 3-2 Configuration flow for the E-Line services carried by ports St e p

Operation

Remarks

1

Config uring the UNI (when the UNI is an Ethern et port)

(Required) The parameters are set as follows:

9.1.1 Setting the General Attributes of Ethernet Interfaces

l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value Auto-Negotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length(byte) is set to the maximum length of the transmitted JUMBO frames.

9.1.2 Setting the Layer 2 Attributes of Ethernet Ports

(Optional) The parameters are set as follows: l Tag needs to be set according to the type of the packets that are transmitted from the equipment on the opposite end. – If all the packets are untagged packets, Tag is set to Access. – If all the packets are tagged packets, Tag is set to Tag Aware. – If the packets contain untagged packets and tagged packets, Tag is set to Hybrid. l When Tag is set to Access or Hybrid, the Default VLAN ID and VLAN Priority parameters need to be set for the untagged frames. VLAN Priority needs to be set according to the planned QoS.

9.1.5 Configuring the Flow Control

Issue 03 (2013-02-20)

(Optional) The parameters are set as follows: l Generally, the PSN adopts the QoS scheme to prevent link congestion. Hence, Auto-Negotiation Flow Control Mode and Non-Autonegotiation Flow Control Mode need to be set to the default value Disabled, unless otherwise specified.


34



St e p

Operation

Remarks

2


(Required) The E-Line services carried by ports occupy the NNIs exclusively. Hence, you need to set DCN Enabled State of the NNIs to Disabled. (Optional) This operation is valid only when the UNI is an Ethernet port. The UNI is connected to the external equipment and thus does not need to transmit the inband DCN information. Hence, set DCN Enabled State of the UNIs to Disabled.

3

9.3.1 Configuring the NNIs for Ethernet Services Carried by Ports


4



5

9.9.2 Configuring UNI-NNI E-Line Services Carried by Ports


6



3.2.3 E-Line Services Carried by PWs You need to configure the MPLS tunnel before configuring the E-Line services carried by PWs. Table 3-3 provides the process for configuring the E-Line services carried by PWs.

Issue 03 (2013-02-20)


35



Figure 3-9 Configuration flow for the E-Line services carried by PWs Start Required Configure the UNI

Optional

Configuring the DCN Function of a Port Configure the NNI for the services carried by the static MPLS tunnel

Configure the MPLS tunnel

Create the E-Line services carried by PWs Create the V-UNI group End

Table 3-3 Configuration flow for the E-Line services carried by PWs Step

Operation

1

Configur ing the UNI (when the UNI is an Ethernet port)


(Required) The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value Auto-Negotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length(byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


36


Step

Operation





2


(Optional) The parameters are set as follows: l Generally, the PSN adopts the QoS scheme to prevent link congestion. Hence, Auto-Negotiation Flow Control Mode and Non-Autonegotiation Flow Control Mode need to be set to the default value Disabled, unless otherwise specified. (Optional) This operation is applicable only when the UNI is an Ethernet port. The parameters are set as follows: l The UNI is used for connecting the external equipment and need not transmit in-band DCN information. Hence, Enable Port needs to be set to Disabled for the UNI.

3

9.3.2 Configuring the NNIs for Ethernet Services Carried by Static MPLS Tunnels

(Required) Set the parameters as follows: l Set Port Mode to Layer 3. l Set Enable Tunnel to Enabled. l Set Specify IP Address to Manually, and set IP Address and IP Mask according to the service plan.

4

Issue 03 (2013-02-20)

Configur ing the MPLS tunnel

9.4 Configuring an MPLS Tunnel

(Required) The parameters need to be set according to the service planning information. For details on how to manage MPLS tunnels, see 9.5 Managing MPLS Tunnels.


37


Step

Operation


Remarks 9.6 Configuring MPLS OAM

(Optional) The parameters are set as follows: l OAM Status is set to Enabled. l Detection Mode is set to Manual. l Detection Packet Type is set to FFD. l Detection Packet Period(ms) is set to 3.3.

9.7 Configuring MPLS Tunnel APS

5

l 9.9.3 Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis l 9.9.4 Configuring E-Line Services Carried by PWs in End-to-End Mode

6


(Optional) Set the MPLS tunnel APS parameters according to the service planning information. For details on how to manage MPLS tunnel APS protection groups, see 9.8 Managing MPLS Tunnel APS Protection Groups. (Required) The parameters need to be set according to the service planning information. For details on how to manage Ethernet services carried by PWs, see 9.16 Managing PWE3 Services.


3.2.4 E-Line Services Carried by QinQ Links You need to configure the QinQ links before configuring the E-Line services carried by QinQ links. Table 3-4 provides the process for configuring the E-Line services carried by QinQ links.

Issue 03 (2013-02-20)


38



Figure 3-10 Configuration flow for the E-Line services carried by QinQ links Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by QinQ links Configure the QinQ links

Configure the QoS

Create the E-Line services carried by QinQ links Create the V-UNI group End

Issue 03 (2013-02-20)


39



Table 3-4 Configuration flow for the E-Line services carried by QinQ links Step

Operation

1



(Required) The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


40


Step


Operation



Issue 03 (2013-02-20)


41


Step


Operation


(Optional) The parameters are set as follows: l Generally, the PSN adopts the QoS scheme to prevent link congestion. Hence, AutoNegotiation Flow Control Mode and NonAutonegotiation Flow Control Mode need to be set to the default value Disabled, unless otherwise specified.

2


(Optional) This operation is applicable only when the UNI is an Ethernet port. The parameters are set as follows: l The UNI is used for connecting the external equipment and need not transmit in-band DCN information. Hence, DCN Enabled State needs to be set to Disabled for the UNI.

Issue 03 (2013-02-20)

3

9.3.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links


4

9.20 Creating a QinQ Link



42



Step

Operation

Remarks

5



6

9.9.5 Creating UNI-NNI E-Line Services Carried by QinQ Links


7



3.3 Configuration Example: UNI-UNI E-Line Services This topic uses an example to describe how to plan the engineering information and how to configure the UNI-UNI E-Line services for each NE according to the networking diagram.

3.3.1 Networking Diagram The networking diagram shows the requirements for the UNI-UNI E-Line services. On the network shown in Figure 3-11, the service requirements of User A are as follows: l

User A1 and User A2 need to communicate with each other. The services of User A1 are accessed onto the PSN through the 21-PETF8-1 port. The services of User A2 are accessed onto the PSN through the 21-PETF8-2 port.

l

The services between User A1 and User A2 contain the voice service, video service, and common Internet access service. The voice service and video service use the fixed bandwidth whereas the common Internet access service can use all the bandwidth at a burst. Table 3-5 lists the service requirements.

Figure 3-11 Networking diagram of the UNI-UNI E-Line services

UNI: 21-PETF8-1 User A1 PSN

NE1 UNI: 21-PETF8-2 User A2

Issue 03 (2013-02-20)


43



NOTE

This topic considers the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product.

Table 3-5 Requirements for the E-Line services Service Type

Requirement

Voice service (VLAN ID=100)

Fixed bandwidth, CIR=PIR, 10 Mbit/s

Video service (VLAN ID=200)


Common Internet access service (VLAN ID=300)

CIR=10 Mbit/s, PIR=50 Mbit/s

3.3.2 Service Planning To configure the UNI-UNI E-Line services, you only need to configure the data of the UNIs. The voice service, video service, and common Internet access service between User A1 and User A2 need to be separated from each other through VLAN tags. In addition, the voice service and video service use the fixed bandwidths whereas the common Internet access service can use all the bandwidths at a burst. Hence, different QoS processing operations need to be performed for different services. Table 3-6 provides the service planning information. Table 3-6 Planning information of the UNI-UNI E-Line services Parameter

Value

Description

Service ID

1, 2, 3

The service ID can be entered manually.

Service Direction

UNI-UNI

In this example, the UNI-UNI ELine services are created.

UNI

21-PETF8-1(Port-1), 21-PETF8-2 (Port-2)

The 21-PETF8-1 port (Port 1) accesses the E-Line service of User A1 and the 21-PETF8-2 port (Port 2) accesses the E-Line service of User A2.

VLANs

100, 200, 300

l The VLAN ID of the voice service is 100. l The VLAN ID of the video service is 200. l The VLAN ID of the common Internet access service is 300.

Issue 03 (2013-02-20)


44



Parameter

Value

Description

BPDU

Not Transparently Transmitted

BPDU packets are processed as service packets, which are processed differently according to port attributes. When the port attribute is Tag Aware, BPDU packets are discarded because they do not carry any VLAN IDs.

QoS Policy for Voice Service

Fixed bandwidth, CIR=PIR, 10000 kbit/s

-

QoS Policy for Video Service


-

QoS Policy for Common Internet Access Service

CIR=10000 kbit/s, PIR=50000 kbit/s

-

3.3.3 Configuration Process To configure the UNI-UNI E-Line services is to configure the E-Line services on an NE. This topic describes how to configure the UNI-UNI E-Line services.

Prerequisites l

You must be familiar with the networking requirements and service planning for the UNIUNI E-Line service.

l

The port attributes must be set correctly.

l

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

l

If the UNI-UNI E-Line service needs to occupy a port exclusively, disable the DCN function of the port. For the operations for disabling the DCN function of the port, see Configuring the DCN Function of a Port.

Procedure Step 1 Configure the voice service between User A1 and User A2. 1.

In the NE Explorer, select NE1, and then choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from the Function Tree.

2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the parameters of the voice service between User A1 and User A2. Table 3-7 Parameters of the voice service between User A1 and User A2

Issue 03 (2013-02-20)

Parameter

Value in This Example

Service ID

1


45



Parameter


Service Name

E-Line-1

Direction

UNI-UNI

Port

21-PETF8-1 (Port-1)

VLANs

100

Port

21-PETF8-2 (Port-2)

VLANs

100

BPDU


MTU (bytes)

1526

3.

Click Configure QoS. Then, the Configure QoS dialog box is displayed.

4.

Click the UNI tab. Set the QoS parameters for the voice service between User A1 and User A2. Table 3-8 QoS parameters of the voice service between User A1 and User A2 Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

10000

10000

PIR(kbit/s)

10000

10000

Other parameters

Default values

Default values

Step 2 Configure the video service between User A1 and User A2. Refer to Step 1 and configure the video service between User A1 and User A2. Table 3-9 Parameters of the video service between User A1 and User A2

Issue 03 (2013-02-20)

Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-UNI

Port

21-PETF8-1 (Port-1)

VLANs

200

Port

21-PETF8-2 (Port-2) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

46



Parameter


VLANs

200

BPDU


MTU (bytes)

1526

Table 3-10 QoS parameters of the video service between User A1 and User A2 Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

40000

40000

PIR(kbit/s)

40000

40000

Other parameters

Default values

Default values

Step 3 Configure the common Internet access service between User A1 and User A2. Refer to Step 1 and configure the common Internet access service between User A1 and User A2. Table 3-11 Parameters of the common Internet access service between User A1 and User A2

Issue 03 (2013-02-20)

Parameter


Service ID

3

Service Name

E-Line-3

Direction

UNI-UNI

Port

21-PETF8-1 (Port-1)

VLANs

300

Port

21-PETF8-2 (Port-2)

VLANs

300

BPDU


MTU (bytes)

1526


47



Table 3-12 QoS parameters of the common Internet access service between User A1 and User A2 Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

10000

10000

PIR(kbit/s)

50000

50000

Other parameters

Default values

Default values

----End

3.4 Configuration Example: E-Line Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by ports for each NE according to the networking diagram.

3.4.1 Networking Diagram The networking diagram shows the requirements for the E-Line services carried by ports. On the network shown in Figure 3-12, the service requirements of User A are as follows: l

User A1 and User A2 need to communicate with each other. The services of User A1 are accessed onto NE1 through the 21-PETF8-1 port. The services of User A2 are accessed onto NE2 through the 21-PETF8-1 port.

l

The E-Line services of User A exclusively occupy all the UNIs and physical ports that the E-Line services traverse on the network.

l

The services between User A1 and User A2 contain the voice service, video service, and common Internet service. The voice service and video service use the fixed bandwidths whereas the common Internet access service can use all the bandwidths at a burst. Table 3-13 lists the service requirements.

Issue 03 (2013-02-20)


48



Figure 3-12 Networking diagram of the E-Line services carried by ports Voice service (VLAN=100)

UNI: 21-PETF8-1

Video service (VLAN=200) Common Internet access service (VLAN=300)

UNI: 21-PETF8-1

NE1 User A1

PSN

NE2 User A2 NNI: 3-PEG16-1 NNI: 3-PEG16-1 NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for an Ethernet service carried by ports, see 9.12.1 Configuring Transit NEs for Ethernet Services Carried by Ports.

Table 3-13 Requirements for the E-Line services Service Type

Requirement

Voice service (VLAN ID=100)


Video service (VLAN ID=200)


Common Internet access service (VLAN ID=300)

CIR=0 Mbit/s, PIR=50 Mbit/s

Total bandwidth

100 Mbit/s

3.4.2 Service Planning To configure the E-Line services carried by ports, you need to configure the data of the UNI and the data of the NNI. The voice service, video service, and common Internet access service between User A1 and User A2 need to be separated from each other through VLAN tags. In addition, the voice service and video service use the fixed bandwidths whereas the common Internet access service can use all Issue 03 (2013-02-20)


49



the bandwidths at a burst. Hence, different QoS processing operations need to be performed for different services. Table 3-14 provides the service planning information. Table 3-14 Planning information of the E-Line services carried by ports Parameter

NE1

NE2

Description

Service ID

1, 2, 3

1, 2, 3

The service ID can be entered manually.

Service Direction

UNI-NNI

UNI-NNI

In this example, the UNI-NNI E-Line services are created.

UNI

21-PETF8-1(Port-1)

21-PETF8-1(Port-1)

The 21-PETF8-1 port (Port 1) of NE1 accesses the E-Line service of User A1 and the 21PETF8-1 port (Port 2) of NE2 accessed the ELine service of User A2.

VLANs

100, 200, 300

100, 200, 300

l The VLAN ID of the voice service is 100. l The VLAN ID of the video service is 200. l The VLAN ID of the common Internet access service is 300.

Issue 03 (2013-02-20)

BPDU




Bearer Type

Port

Port

In this example, the ELine services are configured to be carried by ports from the user side to the network side.

NNI

3-PEG16-1(Port-1)

3-PEG16-1(Port-1)

-

QoS Policy for Voice Service



-


50



Parameter

NE1

NE2

Description

QoS Policy for Video Service



-

QoS Policy for Common Internet Access Service



-

Total bandwidth



-

3.4.3 Configuration Process The E-Line services carried by ports need to occupy the NNI ports exclusively. Hence, you need to disable the DCN function of the NNI ports before configuring the E-Line services.

Prerequisites l

You must be familiar with the networking requirements and service planning for the UNINNI E-Line services carried by the ports.

l


l


l

The QoS policy must be configured according to the E-Line service planning. For the configuration method, see Creating the V-UNI Ingress Policy (OptiX OSN 3500/7500/7500 II).

l

The E-Line services carried by ports need to occupy the NNI ports exclusively. Hence, you need to disable the DCN function of the NNI ports. If the E-Line services carried by ports need to occupy the UNI ports, you also need to disable the DCN function of the UNI ports. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 On NE1, configure the voice service, video service, and common Internet access service between User A1 and User A2. 1.


2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the parameters of the E-Line services between User A1 and User A2.

Issue 03 (2013-02-20)


51



Table 3-15 Parameters of the E-Line services between User A1 and User A2 Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

Port

21-PETF8-1 (Port-1)

VLANs

100, 200, 300

Bearer Type

Port

Sink Port

3-PEG16-1 (Port-1)

BPDU


MTU (bytes)

1526

3.


4.

Click the UNI tab. Set the QoS parameters for the E-Line services between User A1 and User A2. Table 3-16 QoS parameters of the E-Line services between User A1 and User A2 Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy

Note: The QoS policy that is configured correctly is selected.

CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 2 On NE2, configure the voice service, video service, and common Internet access service between User A1 and User A2. Refer to Step 1 and configure the E-Line services between User A1 and User A2. ----End

Relevant Task See 3.4.4 Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by ports are configured correctly. Issue 03 (2013-02-20)


52



3.4.4 Verifying the Correctness of E-Line Service Configuration After the E-Line services are configured, the correctness of service configuration should be verified. The Ethernet OAM function is used to verify the correctness of E-Line service configuration.

Prerequisites The E-Line services must be already created.

Context In the case of UNI-UNI E-Line services, you need not perform the connectivity check by using the 802.1ag OAM function. By default, the UNI-UNI E-Line services are normal. The connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-Line services carried by ports and QinQ links is the same as the connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-Line services carried by PWs. This topic considers the E-Line services carried by PWs as the example to describe how to check whether the E-Line services are configured correctly. Before you perform the check, you need to configure the Ethernet OAM function. See Figure 3-13. Figure 3-13 OAM of the E-Line services MA

MD

MEP

User A1

NE1

NE2

MEP

User A2

MEP

MEP

MA

User B1

User B2

MEP: maintenance end point Unicast tunnel PW

MD: maintenance domain MA: maintenance association

As shown in the figure, two E-Line services are configured between User A1 and User A2 and between User B1 and User B2. The two E-Line services are carried and isolated by PWs. To check whether the two E-Line services are configured correctly, you need to configure the Ethernet OAM function. This topic considers the E-Line service between User A1 and User A2 as the example.

Procedure Step 1 At NE1 and NE2, create the maintenance domain for the E-Line service between User A1 and User A2. For the creation method, see Creating an MD. Issue 03 (2013-02-20)


53



Set the parameters of the maintenance domain. Parameter

NE1

NE2

Maintenance Domain Name

MD

MD

Maintenance Domain Level

4

4

NOTE

The maintenance domain names and levels of NE1 and NE2 need to be the same so that NE1 and NE2 belong to the same maintenance domain.

Step 2 At NE1 and NE2, create the maintenance association for the E-Line service between User A1 and User A2. For the creation method, see Creating an MA. Set the parameters of the maintenance association. Parameter

NE1

NE2


MD

MD

Maintenance Association Name

MA

MA

Relevant Service

1-E-Line-1

1-E-Line-1

CC Test Transmit Period (ms)

3.33 ms

3.33 ms

Step 3 At NE1 and NE2, create the maintenance end points (MEPs). For the creation method, see Creating an MEP. Set the parameters of the MEPs.

Issue 03 (2013-02-20)

Parameter

NE1

NE2


MD

MD


MA

MA

Board

21-PETF8

21-PETF8

Port

1(Port-1)

1(Port-1)

VLAN

100

100

MP ID

1

2

Direction

Ingress

Ingress

CC Status

Active

Active


54



Step 4 At NE1 and NE2, create the remote MEPs. Perform the CC test. For the test method, see Performing a Continuity Check. NOTE

l If the MEP of NE2 does not receive the CC packets from NE1 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE1 to NE2 is normal. l If the MEP of NE1 does not receive the CC packets from NE2 in a period of time (for example, 3.25 times of the transmission period), the MEP automatically reports the ETH_CFM_LOC alarm. If the ETH_CFM_LOC alarm is not reported, the connectivity of the service from NE2 to NE1 is normal.

----End

3.5 Configuration Example: E-Line Services Carried by PWs (Newly Created) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs for each NE according to the networking diagram.

3.5.1 Networking Diagram The networking diagram shows the requirements for the E-Line services carried by PWs. On the network shown in Figure 3-14, the service requirements of User A and User B are as follows: l

User A1 and User B1 are connected to NE1 through the 21-PETF8-1 and 21-PETF8-2 ports respectively.

l


l

The service between User A1 and User A2 is the common Internet access service of which the CIR is 10 Mbit/s and the PIR is 30 Mbit/s.

l

The service between User B1 and User B2 is the data service of which the CIR is 30 Mbit/ s and the PIR is 50 Mbit/s.

l

The services of User A and User B each are carried on different PW links.

l

The two PW links that carry the services of User A and User B share the bandwidth of one tunnel.

l

The services of User A and User B are protected.

Issue 03 (2013-02-20)


55



Figure 3-14 Networking diagram of the E-Line services carried by PWs UNI for A1:21-PETF8-1 UNI for B1:21-PETF8-2

NNI:3-PEG16-3

UNI for A2:21-PETF8-1 UNI for B2:21-PETF8-2

NNI:3-PEG16-1

NNI:3-PEG16-1 PSN

User A2

User A1 NE2

NE 1

User B1

NNI:3-PEG16-2

NE3

NNI:3-PEG16-4

User B2

NNI:3-PEG16-2 MPLS Tunnel PW NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for an Ethernet service carried by PWs, see 9.12.2 Configuring Transit NEs for Ethernet Services Carried by PWs.

NE NE1

NE2

NE3

Issue 03 (2013-02-20)

IP Address

IP Mask

LSR ID

3PEG16-1

18.1.1.1

255.255.255.252

130.0.0.1

3PEG16-2

18.1.2.1

255.255.255.252

3PEG16-1

18.1.1.2

255.255.255.252

3PEG16-2

18.1.2.2

255.255.255.252

3PEG16-3

18.1.1.5

255.255.255.252

3PEG16-4

18.1.2.5

255.255.255.252

3PEG16-1

18.1.1.6

255.255.255.252

3PEG16-2

18.1.2.6

255.255.255.252


130.0.0.2

130.0.0.3

56



NOTE

l The IP addresses of the Ethernet ports on an NE cannot be in the same network segment. l The IP addresses of the ports at both ends of a link must be in the same network segment.

3.5.2 Service Planning The engineering information for configuring the E-Line services carried by PWs contains the engineering information for configuring the tunnel carrying the PWs, the engineering information for configuring the PWs, and the engineering information for configuring the UNINNI E-Line services carried by the PWs. The PWs that carry the E-Line services are carried by a tunnel. Hence, you need to plan the tunnel during the service planning. Therefore, planning the E-Line services carried by PWs involves the following: l

Plan the tunnel that carries the PWs. Refer to Table 3-17 and Table 3-18.

l

Plan the MPLS Tunnel OAM. Refer to Table 3-19.

l

Plan the MPLS Tunnel APS. Refer to Table 3-20.

l

Plan the PWs. Refer to Table 3-21.

l

Plan the UNI-NNI E-Line services carried by PWs. Refer to Table 3-22.

Table 3-17 Basic attributes of a tunnel Param eter

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Paramet er Plannin g

NE1_NE3_w orking

10

MPLS

Static CR

Bidirectio nal

Unprotect ed

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirectio nal

Unprotect ed

Table 3-18 Planning information of the tunnels

Issue 03 (2013-02-20)

MPL S Tun nel ID

N o d e

No de Ty pe

In Inte rfac e

In Lab el

Rev erse In Lab el

Out Inte rfac e

Out Lab el

Rev ers e Out Lab el

Ne xt Ho p

Rev ers e Ne xt Ho p

Sour ce Nod e

Sink Nod e

Wor king Tunn el

N E 1

Ing res s

-

-

103

3PEG 16-1

100

-

18.1 .1.2

-

-

130.0 .0.3


57


MPL S Tun nel ID

Prote ction Tunn el


N o d e

No de Ty pe

In Inte rfac e

In Lab el

Rev erse In Lab el

Out Inte rfac e

Out Lab el


Ne xt Ho p


Sour ce Nod e

Sink Nod e

N E 2

Tra nsit

3PEG 16-1

100

102

3PEG 16-3

101

103

18.1 .1.6

18.1 .1.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-1

101

-

-

102

-

18.1 .1.5

130.0 .0.1

-

N E 1

Ing res s

-

-

203

3PEG 16-2

200

-

18.1 .2.2

-

-

130.0 .0.3

N E 2

Tra nsit

3PEG 16-2

200

202

3PEG 16-4

201

203

18.1 .2.6

18.1 .2.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-2

201

-

-

202

-

18.1 .2.5

130.0 .0.1

-

Table 3-19 Parameter planning for MPLS tunnel OAM

Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual

Detection Packet Type

FFD

FFD

Detection Packet Period (ms)

3.3

NOTE Detection Packet Period can be set only when Detection Packet Type is FFD.

3.3

NOTE Generally, the OAM packet is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.


58



Table 3-20 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Workin g

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Protect ion

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Revertive Mode

Revertive

WTR Time(min)

5

Hold-off Time (100ms)

0

Protocol State

Enabled

NOTE Services are not protected with multiple protection schemes. Therefore, the setting of Hold-off Time(100ms) is unnecessary.

Table 3-21 Planning information of the PWs

Issue 03 (2013-02-20)

Parameter

PW of User A

PW of User B

PW Signaling Type

Static

Static

PW Type

Ethernet Tagged Mode


PW Direction

Bidirectional

Bidirectional

PW Incoming Label/Source Port

20

30

PW Outgoing Label/Sink Port

20

30

Peer LSR ID

NE1

130.0.0.3

130.0.0.3

NE3

130.0.0.1

130.0.0.1

MPLS Tunnel name

NE1_NE3_working

NE1_NE3_working

Bandwidth Limit

Enabled

Enabled

CIR (kbit/s)

10000

30000

PIR (kbit/s)

30000

50000

Request VLAN

10

20


59



Table 3-22 Planning information of the E-Line services carried by the PWs from the user side to the network side Parameter

User A

User B

Service ID

1

2

Name

E-Line-1

E-Line-2

Direction

UNI-NNI

UNI-NNI

UNI

21-PETF8-1

21-PETF8-2

VLANs

100

100

Bearer Type

PW

PW

PW ID

35

45

BPDU



MTU (bytes)

1500

1500

3.5.3 Configuration Process (in End-to-End Mode) Before configuring E-Line services carried by PWs, you need to configure the tunnels that carry the PWs.

Prerequisites l

You must be familiar with the networking requirements and service planning information of the UNI-NNI E-Line services carried by the PWs.

l


l

If the E-Line services carried by PWs need to occupy the UNI ports exclusively, disable the DCN function of the UNI ports. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 Follow the instructions in 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode and configure tunnels for carrying PWs. Table 3-23 Basic attributes of a tunnel

Issue 03 (2013-02-20)

Param eter

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


60


Param eter


MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirectio nal

Unprotect ed

Table 3-24 Planning information of the tunnels MPL S Tun nel ID

N o d e

No de Ty pe

In Inte rfac e

In Lab el

Rev erse In Lab el

Out Inte rfac e

Out Lab el


Ne xt Ho p


Sour ce Nod e

Sink Nod e

Wor king Tunn el

N E 1

Ing res s

-

-

103

3PEG 16-1

100

-

18.1 .1.2

-

-

130.0 .0.3

N E 2

Tra nsit

3PEG 16-1

100

102

3PEG 16-3

101

103

18.1 .1.6

18.1 .1.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-1

101

-

-

102

-

18.1 .1.5

130.0 .0.1

-

N E 1

Ing res s

-

-

203

3PEG 16-2

200

-

18.1 .2.2

-

-

130.0 .0.3

N E 2

Tra nsit

3PEG 16-2

200

202

3PEG 16-4

201

203

18.1 .2.6

18.1 .2.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-2

201

-

-

202

-

18.1 .2.5

130.0 .0.1

-

Prote ction Tunn el

Step 2 Follow the instructions in 9.6 Configuring MPLS OAM and configure MPLS tunnel OAM. Table 3-25 Parameter planning for MPLS tunnel OAM

Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


61


Parameter

Parameter Planning


FFD


3.3


FFD


3.3


Step 3 Follow the instructions in 9.7 Configuring MPLS Tunnel APS and configure MPLS tunnel APS. Table 3-26 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Workin g

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Protect ion

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Revertive Mode

Revertive

WTR Time(min)

5


0

Protocol State

Enabled


Step 4 Configure the common Internet access service between User A1 and User A2 in end-to-end mode. 1.

Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu.

2.

Set the basic attributes of the common Internet access service between User A1 and User A2.

Issue 03 (2013-02-20)


62



Table 3-27 Parameters of the E-Line services between User A1 and User A2

3.

Parameter


Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

Unprotected

Configure the source NE and sink NE of the PWE3 service. a.

Under Node List, click Configure Source And Sink. Then, a dialog box is displayed.

b.

Select the source NE from Physical Topology on the left.

c.

Set the SAI attributes of the E-Line service in SAI Configuration. Then, click Add Node.

Table 3-28 Parameters of the service ports between User A1 and User A2 Parameter Source

Sink

4.

Value in This Example ID

1

VLAN ID

100

ID

1

VLAN ID

100

Click the PW tab and set the basic attributes of the PW. Table 3-29 Parameters of the PW between User A1 and User A2

Issue 03 (2013-02-20)

Parameter


PW ID

35

Signaling Type

Static

Forward Label

20

Reverse Label

20

Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working

Encapsulation Type

MPLS


63


5.


Click Detail, set the Advanced attributes of the PW. a.

Click the PW QoS tab and set the parameters of the PW QoS. Table 3-30 Parameters of the service bandwidth between User A1 and User A2 Parameter Forward

Reverse

b.

Value in This Example Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

30000

Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

30000

Click the Advanced PW Attribute tab and set the advanced attributes of the PW.

Table 3-31 Parameters of the advanced attributes of the PW between User A1 and User A2 Parameter


PW Type


Request VLAN

10

Other parameters

Default values NOTE For details on how to configure the TPID, see 9.19 Configuring the NE-Level TPID.

6.

Click OK.

Step 5 Configure the data service between User A1 and User A2 in end-to-end mode. Configure the data service between User B1 and User B2 according to Step 4. Table 3-32 Parameters of the E-Line services between User B1 and User B2

Issue 03 (2013-02-20)

Parameter


Service Type

ETH

Service ID

2

Service Name

E-Line-2

Protection Type

Unprotected


64



Table 3-33 Parameters of the service ports between User B1 and User B2 Parameter


Source

Sink

ID

2

VLAN ID

100

ID

2

VLAN ID

100

Table 3-34 Parameters of the PW between User B1 and User B2 Parameter


PW ID

45

Signaling Type

Static

Forward Label

30

Reverse Label

30

Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working

Encapsulation Type

MPLS

Table 3-35 Parameters of the service bandwidth between User B1 and User B2 Parameter Forward

Reverse

Issue 03 (2013-02-20)


Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000

Bandwidth Limit

Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000


65



Table 3-36 Parameters of the advanced attributes of the PW between User B1 and User B2 Parameter


PW Type


Request VLAN

20

Other parameters

Default values NOTE For details on how to configure the TPID, see 9.19 Configuring the NE-Level TPID.

----End

Relevant Task See 3.5.5 Verifying E-Line Services to check whether the E-Line services carried by PWs are configured correctly.

3.5.4 Configuration Process (Configuration on a Per-NE Basis) Before configuring the E-Line services carried by PWs, you need to configure the tunnels that carry the PWs.

Prerequisites l

You must be familiar with the networking requirements and service planning for the UNINNI E-Line services carried by the PWs.

l


l

If the UNI-NNI E-Line services need to occupy the UNI ports exclusively, disable the DCN function of the UNI ports. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 On NE1, NE2, and NE3, configure tunnels that carry PWs. For the configuration procedures, see 9.4 Configuring an MPLS Tunnel. Table 3-37 Basic attributes of a tunnel

Issue 03 (2013-02-20)

Param eter

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirectio nal

Unprotect ed

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirectio nal

Unprotect ed


66



Table 3-38 Planning information of the tunnels MPL S Tun nel ID

N o d e

No de Ty pe

In Inte rfac e

In Lab el

Rev erse In Lab el

Out Inte rfac e

Out Lab el


Ne xt Ho p


Sour ce Nod e

Sink Nod e

Wor king Tunn el

N E 1

Ing res s

-

-

103

3PEG 16-1

100

-

18.1 .1.2

-

-

130.0 .0.3

N E 2

Tra nsit

3PEG 16-1

100

102

3PEG 16-3

101

103

18.1 .1.6

18.1 .1.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-1

101

-

-

102

-

18.1 .1.5

130.0 .0.1

-

N E 1

Ing res s

-

-

203

3PEG 16-2

200

-

18.1 .2.2

-

-

130.0 .0.3

N E 2

Tra nsit

3PEG 16-2

200

202

3PEG 16-4

201

203

18.1 .2.6

18.1 .2.1

130.0 .0.1

130.0 .0.3

N E 3

Egr ess

3PEG 16-2

201

-

-

202

-

18.1 .2.5

130.0 .0.1

-

Prote ction Tunn el

Step 2 On NE1, NE2, and NE3, configure MPLS tunnel OAM. For the configuration procedures, see 9.6 Configuring MPLS OAM. Table 3-39 Parameter planning for MPLS tunnel OAM

Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD



67


Parameter

Parameter Planning


3.3


3.3


Step 3 On NE1 and NE3, configure MPLS tunnel APS. For the configuration procedures, see 9.7 Configuring MPLS Tunnel APS. Table 3-40 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Workin g

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Protect ion

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Revertive Mode

Revertive

WTR Time(min)

5


0

Protocol State

Enabled


Step 4 On NE1, configure the E-Line services of User A1. 1.


2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the parameters of the E-Line services of User A1.

Issue 03 (2013-02-20)


68



Table 3-41 Parameters of the E-Line services carried by PWs of User A1

3.

Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU


MTU (bytes)

1500

Port

21-PETF8-1

VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Click Configure PW. Then, the Configure PW dialog box is displayed. Set the PW parameters. Table 3-42 PW parameters of the E-Line services of User A1 Parameter General Attributes

Advanced Attributes

Value in This Example PW ID

35

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional

PW Incoming Label/ Source Port

20


20

Tunnel Type

MPLS

Tunnel No.

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

10

Other parameters

Default values

NOTE For details on how to configure the TPID, see 9.19 Configuring the NE-Level TPID.

4. Issue 03 (2013-02-20)

Click Configure QoS. Then, the Configure QoS dialog box is displayed. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

69


5.


Click the PW tab. Set the QoS parameters of the E-Line services of User A1. Table 3-43 QoS parameters of the E-Line services of User A1 Parameter


PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

30000

Other parameters

Default values

Step 5 On NE1, configure the E-Line services of User B1. Refer to Step 4 and configure the E-Line services of User B1. Table 3-44 Parameters of the E-Line services carried by PWs of User B1 Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU


MTU(bytes)

1500

Port

21-PETF8-2

VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Table 3-45 PW parameters of the E-Line services of User B1 Parameter


General Attributes

Issue 03 (2013-02-20)

PW ID

45

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


70



Parameter


Advanced Attributes


30


30

Tunnel Type

MPLS

Tunnel No.

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

20

Other parameters

Default values


Table 3-46 QoS parameters of the E-Line services of User B1 Parameter


PW ID

45

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000

Other parameters

Default values

Step 6 On NE3, configure the E-Line services of User A2 and User B2. Refer to Step 4 and configure the E-Line services of User A2 and User B2. Table 3-47 Parameters of the E-Line services carried by PWs of User A2

Issue 03 (2013-02-20)

Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU


MTU(bytes)

1500


71



Parameter


Port

21-PETF8-1

VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Table 3-48 PW parameters of the E-Line services of User A2 Parameter


General Attributes

Advanced Attributes

PW ID

35

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


20


20

Tunnel Type

MPLS

Tunnel No.

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

10

Other parameters

Default values


Table 3-49 QoS parameters of the E-Line services of User A2

Issue 03 (2013-02-20)

Parameter


PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

30000


72



Parameter


Other parameters

Default values

Table 3-50 Parameters of the E-Line services carried by PWs of User B2 Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU


MTU(bytes)

1500

Port

21-PETF8-2

VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Table 3-51 PW parameters of the E-Line services of User B2 Parameter


General Attributes

Advanced Attributes

PW ID

45

PW Signaling Type

Static

PW Type


Direction

Bidirectional

PW Ingress Label

30

PW Egress Label

30

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

20

Other parameters

Default values


Issue 03 (2013-02-20)


73



Table 3-52 QoS parameters of the E-Line services of User B2 Parameter


PW ID

45

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000

Other parameters

Default values

----End

Relevant Task If you configure PW-carried E-Line services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete PWE3 services to complete PWE3 services. See 3.5.5 Verifying E-Line Services to check whether the E-Line services carried by PWs are configured correctly.

3.5.5 Verifying E-Line Services After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Prerequisites l

End-to-end PW-carried E-Line services have been configured.

l

If you configure PW-carried E-Line services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete PWE3 services to complete PWE3 services.

Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to PW APS. Then, click Filter. Query all PWE3 services that meet the filter conditions. Step 3 Right-click the required PW-carried E-Line service and choose Ethernet OAM > LB Test from the shortcut menu. Step 4 In the dialog box that is displayed, select the source NE and sink NE, and click Run.

Step 5 After the test is complete, click the LB Statistic Information tab to check whether the service is available. Issue 03 (2013-02-20)


74



NOTE

If the number of received packets and the number of transmitted packets are the same, the service is available. If testing packet loss fails, troubleshoot it by referring to Troubleshooting Service Packet Loss.

----End

3.6 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Priorities) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs for each NE according to the networking diagram. In this example, services with a same VLAN ID but different VLAN priorities need to be mapped to different PWs.

3.6.1 Networking Diagram The networking diagram shows the requirements for the E-Line services carried by PWs (network adjustment based on VLAN priorities). On the network shown in Figure 3-15, services from NodeB 1 and services from NodeB 2 have a same VLAN ID, and need to be mapped to different PWs based on Port+VLAN+VLAN PRI before being transported to the RNC. Service requirements are as follows: l

Services from NodeB 1 and services from NodeB 2 are transported to NE1 through the 21PEFF8-1 and 21-PEFF8-2 ports respectively.

l

NE3 converges services from NodeB 1 and NodeB 2, and transports the services to the RNC.

l

Services from NodeB 1 are common Internet access services of which the CIR is 10 Mbit/ s and the PIR is 30 Mbit/s.

l

Services from NodeB 2 are data services of which the CIR is 30 Mbit/s and the PIR is 50 Mbit/s.

l

Services from NodeB 1 have a VLAN ID of 100 and VLAN priorities of 3, 4, and 5; services from NodeB 2 have a VLAN ID of 100 and a VLAN priority of 2. Services from NodeB 1 and NodeB 2 are mapped to two PWs based on Port+VLAN+VLAN PRI.

l

Services from NodeB 1 and NodeB 2 are protected by tunnel APS.

Issue 03 (2013-02-20)


75



Figure 3-15 Networking diagram of the E-Line services carried by PWs (network adjustment based on VLAN priorities) UNI for NodeB 1: 21-PEFF8-1 UNI for NodeB 2: 21-PEFF8-2

NNI: 3-PEG8-3

UNI for RNC: 3-PEG8-3

NNI: 3-PEG8-1

NNI: 3-PEG8-1 PSN NodeB 1 VLAN ID: 100 PRI: 3, 4, 5 NE2

NE1

NodeB 2 VLAN ID: 100 PRI: 2

NNI: 3-PEG8-2

NE3

RNC

NNI: 3-PEG8-4 NNI: 3-PEG8-2 MPLS tunnel PW

NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for the Ethernet services carried by PWs, see 9.12.2 Configuring Transit NEs for Ethernet Services Carried by PWs.

NE NE1

NE2

NE3

Issue 03 (2013-02-20)

IP Address

IP Mask

LSR ID

3PEG8-1

18.1.1.1

255.255.255.252

130.0.0.1

3PEG8-2

18.1.2.1

255.255.255.252

3PEG8-1

18.1.1.2

255.255.255.252

3PEG8-2

18.1.2.2

255.255.255.252

3PEG8-3

18.1.1.5

255.255.255.252

3PEG8-4

18.1.2.5

255.255.255.252

3PEG8-1

18.1.1.6

255.255.255.252

3PEG8-2

18.1.2.6

255.255.255.252


130.0.0.2

130.0.0.3

76



NOTE

l The IP addresses of the Ethernet ports on an NE must not be in the same network segment. l The IP addresses of the ports at both ends of a link must be in the same network segment.

3.6.2 Service Planning The engineering information for configuring the E-Line services carried by PWs (network adjustment based on VLAN priorities) contains the engineering information for configuring the tunnels carrying the PWs, the engineering information for configuring the PWs, and the engineering information for configuring the UNI-NNI E-Line services carried by the PWs. The PWs that carry the E-Line services are carried by tunnels. Therefore, you need to plan the tunnels during the service planning. Planning the E-Line services carried by PWs involves the following: l

Plan the tunnels that carry the PWs. Refer to Table 3-53 and Table 3-54.

l

Plan MPLS tunnel OAM. Refer to Table 3-55.

l

Plan MPLS tunnel APS. Refer to Table 3-56.

l


l

Plan the UNI-NNI E-Line services carried by PWs. Refer to Table 3-58. NOTE

The E-Line services carried by PWs (network adjustment based on VLAN priorities) do not apply to the following scenarios: l Service Tag Role is User; the service that a UNI receives contains an S-TAG. l PWs are in Ethernet tagged mode; Service Tag Role is Service. In addition: l The service that a UNI receives contains a C-TAG, and the TPID of the request VLAN is 0x88A8. l The service that a UNI receives contains an S-TAG, the TPID of the S-TAG is 0x8100, and the TPID of the request VLAN is 0x88A8. l The service that a UNI receives contains an S-TAG, the TPID of the S-TAG is 0x88A8, and the TPID of the request VLAN is 0x8100.

Table 3-53 Basic attributes of the MPLS tunnels

Issue 03 (2013-02-20)

Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type

Par ame ter Pla nni ng

NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


77



Table 3-54 Parameter planning for the MPLS tunnels MP LS Tu nn el ID

N o d e

10

20

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

203

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-


Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD


3.3


3.3

NOTE Generally, an OAM alarm is reported after three periods. When Detection Packet Period (ms) is set to 3.3, the switching time can meet the requirement (less than 50 ms) after a fault occurs.


78




Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Protecti on

Revertive Mode

Revertive

WTR Time (min)

5

Hold-off Time (100 ms)

0

Protocol State

Enabled

NOTE The services are not protected by multiple protection schemes. Therefore, the setting of Hold-off Time (100 ms) is unnecessary.

Table 3-57 Parameter planning for the PWs

Issue 03 (2013-02-20)

Parameter

NodeB 1 PW

NodeB 2 PW

PW ID

35

45

PW Signaling Type

Static

Static

PW Type



PW Direction

Bidirectional

Bidirectional


20

30


20

30

Peer LSR ID

NE1

130.0.0.3

130.0.0.3

NE3

130.0.0.1

130.0.0.1

MPLS Tunnel name

NE1_NE3_working

NE1_NE3_working

Bandwidth Limit

Enabled

Enabled

CIR (kbit/s)

10000

30000

PIR (kbit/s)

30000

50000


79



Parameter

NodeB 1 PW

NodeB 2 PW

Request VLAN

10

20

TPID

0x88A8

0x88A8

Table 3-58 Parameter planning for the UNI-NNI E-Line services carried by PWs Parameter

NodeB 1

NodeB 2

RNC

Service ID

1

2

1

2

Name

E-Line-1

E-Line-2

E-Line-1

E-Line-2

Direction

UNI-NNI

UNI-NNI

UNI-NNI

UNI-NNI

Service Tag Role

User

User

User

User

UNI

21-PEFF8-1

21-PEFF8-2

3-PEG8-3

3-PEG8-3

VLANs

100

100

100

100

PRI

3, 4, 5

2

3, 4, 5

2

Bearer Type

PW

PW

PW

PW

PW ID

35

45

35

45

BPDU





MTU (bytes)

1500

1500

1500

1500

3.6.3 Configuration Process (in End-to-End Mode) This section describes how to configure E-Line services carried by PWs in end-to-end mode.

Prerequisites l

You must be familiar with the networking requirements and service plan of the E-Line services carried by PWs (in the scenario of network adjustment based on VLAN priorities).

l


Procedure Step 1 See 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode to configure a tunnel for carrying PWs.

Issue 03 (2013-02-20)


80



Table 3-59 Basic attributes of the MPLS tunnels Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


N o d e

10

20

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

203

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-

Step 2 See 9.6 Configuring MPLS OAM to configure MPLS tunnel OAM.

Issue 03 (2013-02-20)


81



Table 3-61 Parameter planning for MPLS tunnel OAM Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD


3.3


3.3


Step 3 See 9.7 Configuring MPLS Tunnel APS to configure MPLS tunnel APS. Table 3-62 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Protecti on

Revertive Mode

Revertive

WTR Time (min)

5


0

Protocol State

Enabled


Step 4 Configure common Internet access services on NodeB 1 in end-to-end mode. 1. Issue 03 (2013-02-20)

Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

82


2.


Set general attributes for the common Internet access services on NodeB 1. Table 3-63 General attributes for the common Internet access services on NodeB 1

3.

Parameter


Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

Unprotected

Configure the source and sink NEs of the PWE3 service. a.

On the Node List tag page, click Configure Source And Sink. A dialog box is displayed.

b.

Select source and sink NEs in Physical Topology on the left.

c.

In SAI Configuration, set the parameters for the service port on NodeB 1 and click Add Node.

Table 3-64 Parameters for the service port on NodeB 1 Parameter Source

Sink

4.


1

VLAN ID

100

Priority Type

802.1p

Priority Field

3,4,5

ID

1

VLAN ID

100

Priority Type

802.1p

Priority Field

3,4,5

Click the PW tab, and set the general attributes for the PW on NodeB 1. Table 3-65 General attributes for the PW on NodeB 1

Issue 03 (2013-02-20)

Parameter


PW ID

35

Signaling Type

Static

Forward Label

20

Reverse Label

20


83


5.


Parameter


Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working

Encapsulation Type

MPLS

Click Detail and set the advanced attributes for the PW on NodeB 1. a.

Click the PW QoS tab and set the QoS parameters for the PW on NodeB 1. Table 3-66 QoS parameters for the PW on NodeB 1 Parameter Forward

Reverse

b.


Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Click the Advanced PW Attribute tab and set the advanced attributes for the PW on NodeB 1. Table 3-67 Advanced attributes for the PW on NodeB 1 Parameter


PW Type


Request VLAN

10

TPID

0x88A8 NOTE For details on how to configure the TPID, see 9.19 Configuring the NE-Level TPID.

Other parameters c.

Issue 03 (2013-02-20)

Default values

Click the Service Parameter tab and set the service tags for NodeB 1.


84



Table 3-68 Service tags for NodeB 1 Parameter

6.


Source

Service Tag

User

Sink

Service Tag

User

Click OK.

Step 5 Configure data services on NodeB 2 in end-to-end mode. See Step 4 to configure data services on NodeB 2. Table 3-69 General attributes for the data services on NodeB 2 Parameter


Service Type

ETH

Service ID

2

Service Name

E-Line-2

Protection Type

Unprotected

Table 3-70 Parameters for the service port on NodeB 2 Parameter


Source

Sink

ID

2

VLAN ID

100

Priority Type

802.1p

Priority Field

2

ID

2

VLAN ID

100

Priority Type

802.1p

Priority Field

2

Table 3-71 General attributes for the PW on NodeB 2

Issue 03 (2013-02-20)

Parameter


PW ID

45

Signaling Type

Static


85



Parameter


Forward Label

30

Reverse Label

30

Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working

Encapsulation Type

MPLS

Table 3-72 QoS parameters for the PW on NodeB 2 Parameter


Forward

Reverse

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Table 3-73 Advanced attributes for the PW on NodeB 2 Parameter


PW Type


Request VLAN

20

TPID


Other parameters

Default values

Table 3-74 Service tags for NodeB 2 Parameter Source Issue 03 (2013-02-20)

Value in This Example Service Tag Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

User 86



Parameter


Sink

Service Tag

User

----End

Related Task See 3.6.5 Verifying E-Line Services to check whether the E-Line services carried by PWs are configured correctly.

3.6.4 Configuration Process (Configuration on a Per-NE Basis) This topic describes the process for configuring the E-Line services carried by PWs.

Prerequisites l

You must be familiar with the networking requirements and service planning information of the E-Line services carried by PWs (network adjustment based on VLAN priorities).

l


Procedure Step 1 On NE1, NE2, and NE3, configure the tunnels that carry the PWs. For the configuration procedures, see 9.4 Configuring an MPLS Tunnel. Table 3-75 Basic attributes of the MPLS tunnels

Issue 03 (2013-02-20)

Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


87




N o d e

10

20

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

203

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-

Step 2 On NE1, NE2, and NE3, configure MPLS tunnel OAM. For the configuration procedures, see 9.6 Configuring MPLS OAM. Table 3-77 Parameter planning for MPLS tunnel OAM

Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD



88


Parameter

Parameter Planning


3.3


3.3


Step 3 On NE1 and NE3, configure MPLS tunnel APS. For the configuration procedures, see 9.7 Configuring MPLS Tunnel APS. Table 3-78 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Protecti on

Revertive Mode

Revertive

WTR Time (min)

5


0

Protocol State

Enabled


Step 4 On NE1, configure an E-Line service for NodeB 1. 1.


2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the displayed parameters.

Issue 03 (2013-02-20)


89



Table 3-79 Parameters of the E-Line service carried by PWs of NodeB 1

3.

Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

User

Source Port

21-PEFF8-1

Source VLANs

100

PRI

3, 4, 5

Bearer Type

PW

Protection Type

Unprotected

Click Configure PW. Then, the Configure PW dialog box is displayed. Set the PW parameters. Table 3-80 PW parameters of the E-Line service of NodeB 1 Parameter General Attributes

Advance d Attributes


35

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


20


20

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

10

TPID

0x88A8 NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

Issue 03 (2013-02-20)


90



Parameter

Value in This Example Other parameters

Default Values

4.


5.

Click the PW tab. Set the QoS parameters of the E-Line service of NodeB 1. Table 3-81 QoS parameters of the E-Line service of NodeB 1 Parameter


PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Other parameters

Default values

Step 5 On NE1, configure an E-Line service for NodeB 2. Refer to Step 4 and configure an E-Line service for NodeB 2. Table 3-82 Parameters of the E-Line service carried by PWs of NodeB 2

Issue 03 (2013-02-20)

Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

User

Source Port

21-PEFF8-2

Source VLANs

100

PRI

2

Bearer Type

PW

Protection Type

Unprotected


91



Table 3-83 PW parameters of the E-Line service of NodeB 2 Parameter


General Attributes

Advanced Attributes

PW ID

45

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


30


30

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

20

TPID


Other parameters

Default values

Table 3-84 QoS parameters of the E-Line service of NodeB 2 Parameter


PW ID

45

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Other parameters

Default values

Step 6 On NE3, configure an E-Line service between NodeB 1 and the RNC, and an E-Line service between NodeB 2 and the RNC. Refer to Step 4 and configure the E-Line services.

Issue 03 (2013-02-20)


92



Table 3-85 Parameters of the E-Line service carried by PWs between NodeB 1 and the RNC Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

User

Source Port

3-PEG8-3

Source VLANs

100

PRI

3, 4, 5

Bearer Type

PW

Protection Type

Unprotected

Table 3-86 PW parameters of the E-Line service between NodeB 1 and the RNC Parameter


General Attributes

Advanced Attributes

PW ID

35

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


20

PW Outgoing Label/ Sink Port

20

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

10

TPID


Other parameters

Issue 03 (2013-02-20)

Default values


93



Table 3-87 QoS parameters of the E-Line service between NodeB 1 and the RNC Parameter


PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Other parameters

Default values

Table 3-88 Parameters of the E-Line service carried by PWs between NodeB 2 and the RNC Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU (STP Packet)


Service Tag Role

User

MTU (bytes)

1500

Source Port

3-PEG8-3

Source VLANs

100

PRI

2

Bearer Type

PW

Protection Type

Unprotected



General Attributes

Issue 03 (2013-02-20)

PW ID

45

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


30


94



Parameter


Advanced Attributes


30

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

20

TPID

0x88A8 NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

Other parameters

Default values



PW ID

45

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Other parameters

Default values

----End

Relevant Task If you configure PW-carried E-Line services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete PWE3 services to complete PWE3 services. See 3.6.5 Verifying E-Line Services to check whether the E-Line services carried by PWs are configured correctly.

3.6.5 Verifying E-Line Services After configuring E-Line services, verify the E-Line services by using the SmartBits.

Prerequisites l Issue 03 (2013-02-20)

E-Line services carried by PWs are configured. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

95


l



Tools, Equipment, and Materials SmartBits and U2000

Test Connection Diagram Figure 3-16 shows the connections for testing E-Line services carried by PWs. Figure 3-16 Connections for testing E-Line services carried by PWs PSN

SmartBits

SmartBits

21-PEFF8-1 NE1

NE2

NE3

3-PEG8-3

MPLS tunnel PW NOTE

In this example, the SmartBits devices are connected to 21-PEFF8-1 on NE1 (source) and 3-PEG8-3 on NE3 (sink). In actual situations, determine the source and sink as required, and follow the same testing procedure.

Context

CAUTION l During a test, only test personnel are allowed in the testing environment. l Exercise caution when touching cables and optical fibers.

Procedure Step 1 Connect the SmartBits devices to 21-PEFF8-1 on NE1 and 3-PEG8-3 on NE3. Step 2 Log in to the U2000. See Enabling, Disabling and Setting Performance Monitoring of the NE to start the 15-minute and 24-hour performance monitoring on NE1 and NE3. NOTE

The performance monitoring tasks help analyze and locate a problem during the test.

Step 3 Use the SmartBits devices to perform a packet transmitting and receiving test.

Issue 03 (2013-02-20)


96



NOTE

l Packets whose bytes are all 0s are considered as special packets. Do not use those packets for a packet transmitting and receiving test. l In the first packet transmitting and receiving period, learning the MAC addresses of the packets may cause packet loss. l If the service is normal, the number of received packets is equal to the number of transmitted packets. If it is a VLAN-based service that involves VLAN switching, check whether VLAN switching functions properly for transmitted and received packets. l If packet loss occurred, rectify the fault. Then, perform 24-hour tests until no packet loss occurs.

----End

3.7 Configuration Example: E-Line Services Carried by PWs (Network Adjustment Based on VLAN Switching) This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by PWs (network adjustment based on VLAN switching) for each NE according to the networking diagram.

3.7.1 Networking Diagram The networking diagram shows the requirements for the E-Line services carried by PWs (network adjustment based on VLAN switching). On the network shown in Figure 3-17, services from NodeB 1 and services from NodeB 2 have a same VLAN ID, and need VLAN switching before being transported to the RNC. Service requirements are as follows: l

Services from NodeB 1 and services from NodeB 2 are transported to NE1 through the 21PEFF8-1 and 21-PEFF8-2 ports respectively.

l

NE3 converges services from NodeB 1 and NodeB 2, and transports the services to the RNC.

l

Services from NodeB 1 are common Internet access services of which the CIR is 10 Mbit/ s and the PIR is 30 Mbit/s.

l

Services from NodeB 2 are data services of which the CIR is 30 Mbit/s and the PIR is 50 Mbit/s.

l

Services from NodeB 1 and services from NodeB 2 have a same VLAN ID of 100, and are mapped to two PWs. After VLAN switching, the VLAN ID of services from NodeB 1 remains unchanged, whereas the VLAN ID of services from NodeB 2 is changed to 200.

l

Services from NodeB 1 and NodeB 2 are protected by tunnel APS.

Issue 03 (2013-02-20)


97



Figure 3-17 Networking diagram of the E-Line services carried by PWs (network adjustment based on VLAN switching) NodeB 1 VLAN: 100

NodeB 1 VLAN: 100

NodeB 2 VLAN: 100

NodeB 2 VLAN: 200

UNI for NodeB 1: 21-PEFF8-1 UNI for NodeB 2: 21-PEFF8-2

NNI: 3-PEG8-3

UNI for RNC: 3-PEG8-3

NNI: 3-PEG8-1

NNI: 3-PEG8-1 PSN NodeB 1 NE2

NE1

NodeB 2

NNI: 3-PEG8-2

NE3

RNC

NNI: 3-PEG8-4 NNI: 3-PEG8-2 MPLS tunnel PW

NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for the Ethernet services carried by PWs, see 9.12.2 Configuring Transit NEs for Ethernet Services Carried by PWs.

NE NE1

NE2

NE3

Issue 03 (2013-02-20)

IP Address

IP Mask

LSR ID

3PEG8-1

18.1.1.1

255.255.255.252

130.0.0.1

3PEG8-2

18.1.2.1

255.255.255.252

3PEG8-1

18.1.1.2

255.255.255.252

3PEG8-2

18.1.2.2

255.255.255.252

3PEG8-3

18.1.1.5

255.255.255.252

3PEG8-4

18.1.2.5

255.255.255.252

3PEG8-1

18.1.1.6

255.255.255.252

3PEG8-2

18.1.2.6

255.255.255.252


130.0.0.2

130.0.0.3

98



NOTE

l The IP addresses of the Ethernet ports on an NE must not be in the same network segment. l The IP addresses of the ports at both ends of a link must be in the same network segment.

3.7.2 Service Planning The engineering information for configuring the E-Line services carried by PWs (network adjustment based on VLAN switching) contains the engineering information for configuring the tunnels carrying the PWs, the engineering information for configuring the PWs, and the engineering information for configuring the UNI-NNI E-Line services carried by the PWs. The PWs that carry the E-Line services are carried by tunnels. Therefore, you need to plan the tunnels during the service planning. Planning the E-Line services carried by PWs involves the following: l

Plan the tunnels that carry the PWs. Refer to Table 3-91 and Table 3-92.

l

Plan MPLS tunnel OAM. Refer to Table 3-93.

l

Plan MPLS tunnel APS. Refer to Table 3-94.

l


l

Plan the UNI-NNI E-Line services carried by PWs. Refer to Table 3-96. NOTE

The E-Line services carried by PWs (network adjustment based on VLAN switching) do not apply to the following scenarios: l Service Tag Role is User; the service that a UNI receives contains an S-TAG. l PWs are in Ethernet tagged mode; Service Tag Role is ServiceIn addition: l The service that a UNI receives contains a C-TAG, and the TPID of the request VLAN is 0x88A8. l The service that a UNI receives contains an S-TAG, the TPID of the S-TAG is 0x8100, and the TPID of the request VLAN is 0x88A8. l The service that a UNI receives contains an S-TAG, the TPID of the S-TAG is 0x88A8, and the TPID of the request VLAN is 0x8100.

Table 3-91 Basic attributes of the MPLS tunnels

Issue 03 (2013-02-20)

Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


99




N o d e

10

20

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

203

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-


Issue 03 (2013-02-20)

Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD


3.3


3.3



100




Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Protecti on

Revertive Mode

Revertive

WTR Time (min)

5


0

Protocol State

Enabled


Table 3-95 Parameter planning for the PWs

Issue 03 (2013-02-20)

Parameter

NodeB 1 PW

NodeB 2 PW

PW ID

35

45

PW Signaling Type

Static

Static

PW Type



PW Direction

Bidirectional

Bidirectional


20

30


20

30

Peer LSR ID

NE1

130.0.0.3

130.0.0.3

NE3

130.0.0.1

130.0.0.1

MPLS Tunnel name

NE1_NE3_working

NE1_NE3_working

Bandwidth Limit

Enabled

Enabled

CIR (kbit/s)

10000

30000

PIR (kbit/s)

30000

50000


101



Parameter

NodeB 1 PW

NodeB 2 PW

Request VLAN

10

20

TPID

0x8100

0x8100

Table 3-96 Parameter planning for the UNI-NNI E-Line services carried by PWs Paramete r

NodeB 1

NodeB 2

RNC

Service ID 1

2

1

2

Name

E-Line-1

E-Line-2

E-Line-1

E-Line-2

Direction

UNI-NNI

UNI-NNI

UNI-NNI

UNI-NNI

Service Tag Role

User

Service

User

Service

UNI

21-PEFF8-1

21-PEFF8-2

3-PEG8-3

3-PEG8-3

VLANs

100

100

100

200

Bearer Type

PW

PW

PW

PW

PW ID

35

45

35

45

BPDU





MTU (bytes)

1500

1500

1500

1500

3.7.3 Configuration Process (in End-to-End Mode) This section describes how to configure E-Line services carried by PWs in end-to-end mode.

Prerequisites l

You must be familiar with the networking requirements and service plan of the E-Line services carried by PWs (in the scenario of network adjustment based on VLAN switching).

l


Procedure Step 1 See 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode to configure a tunnel for carrying PWs.

Issue 03 (2013-02-20)


102



Table 3-97 Basic attributes of the MPLS tunnels Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


N o d e

10

20

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

203

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-

Step 2 See 9.6 Configuring MPLS OAM to configure MPLS tunnel OAM.

Issue 03 (2013-02-20)


103



Table 3-99 Parameter planning for MPLS tunnel OAM Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD


3.3


3.3


Step 3 See 9.7 Configuring MPLS Tunnel APS to configure MPLS tunnel APS. Table 3-100 Parameter planning for MPLS tunnel APS Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

Tunnel ID

10

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Protecti on

Revertive Mode

Revertive

WTR Time (min)

5


0

Protocol State

Enabled


Step 4 Configure common Internet access services on NodeB 1 in end-to-end mode. 1. Issue 03 (2013-02-20)

Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

104


2.


Set general attributes for the common Internet access services on NodeB 1. Table 3-101 General attributes for the common Internet access services on NodeB 1

3.

Parameter


Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

Unprotected

Configure the source and sink NEs of the PWE3 service. a.

On the Node List tag page, click Configure Source And Sink. A dialog box is displayed.

b.


c.

In SAI Configuration, set the parameters for the service port on NodeB 1 and click Add Node.

Table 3-102 Parameters for the service port on NodeB 1 Parameter Source

Sink

4.


1

VLAN ID

100

ID

1

VLAN ID

100

Click the PW tab, and set the general attributes for the PW on NodeB 1. Table 3-103 General attributes for the PW on NodeB 1

Issue 03 (2013-02-20)

Parameter


PW ID

35

Signaling Type

Static

Forward Label

20

Reverse Label

20

Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working


105


5.


Parameter


Encapsulation Type

MPLS

Click Detail and set the advanced attributes for the PW on NodeB 1. a.

Click the PW QoS tab and set the QoS parameters for the PW on NodeB1. Table 3-104 QoS parameters for the PW on NodeB 1 Parameter Forward

Reverse

b.


Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Click the Advanced PW Attribute tab and set the advanced attributes for the PW on NodeB 1. Table 3-105 Advanced attributes for the PW on NodeB 1 Parameter


PW Type


Request VLAN

10

TPID

0x8100 NOTE For details on how to configure the TPID, see 9.19 Configuring the NE-Level TPID.

Other parameters

c.

Default values

Click the Service Parameter tab and set the service tags for NodeB 1. Table 3-106 Service tags for NodeB 1 Parameter

6. Issue 03 (2013-02-20)


Source

Service Tag

User

Sink

Service Tag

User

Click OK. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

106



Step 5 Configure data services on NodeB 2 in end-to-end mode. See Step 4 to configure data services on NodeB 2. Table 3-107 General attributes for the data services on NodeB 2 Parameter


Service Type

ETH

Service ID

2

Service Name

E-Line-2

Protection Type

Unprotected

Table 3-108 Parameters for the service port on NodeB 2 Parameter


Source

Sink

ID

2

VLAN ID

100

ID

2

VLAN ID

200

Table 3-109 General attributes for the PW on NodeB 2

Issue 03 (2013-02-20)

Parameter


PW ID

45

Signaling Type

Static

Forward Label

30

Reverse Label

30

Forward Type

Static Binding

Forward Tunnel

NE1_NE3_working

Reverse Type

Static Binding

Reverse Tunnel

NE1_NE3_working

Encapsulation Type

MPLS


107



Table 3-110 QoS parameters for the PW on NodeB 2 Parameter


Forward

Reverse

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

CIR (kbit/s)

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Table 3-111 Advanced attributes for the PW on NodeB 2 Parameter


PW Type


Request VLAN

20

TPID


Other parameters

Default values

Table 3-112 Service tags for NodeB 2 Parameter


Source

Service Tag

Service

Sink

Service Tag

Service

----End

Related Task See 3.7.5 Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by PWs are configured correctly.

3.7.4 Configuration Process (Configuration on a Per-NE Basis) This topic describes the process for configuring the E-Line services carried by PWs.

Issue 03 (2013-02-20)


108



Prerequisites l

You must be familiar with the networking requirements and service planning information of the E-Line services carried by PWs (network adjustment based on VLAN switching).

l


Procedure Step 1 On NE1, NE2, and NE3, configure the tunnels that carry the PWs. For the configuration procedures, see 9.4 Configuring an MPLS Tunnel. Table 3-113 Basic attributes of the MPLS tunnels Par am ete r

MPLS Tunnel Name

MPLS Tunnel ID

Protocol Type

Signaling Type

Direct ion

Protec ted Type


NE1_NE3_w orking

10

MPLS

Static CR

Bidirec tional

Unprot ected

NE1_NE3_pr otection

20

MPLS

Static CR

Bidirec tional

Unprot ected


N o d e

10

20

Issue 03 (2013-02-20)

No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Ingr E ess 1

-

-

103

3PEG 8-1

100

-

18.1. 1.2

-

-

130.0 .0.3

N Tra E nsit 2

3PEG 8-1

10 0

102

3PEG 8-3

101

103

18.1. 1.6

18.1. 1.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-1

10 1

-

-

102

-

18.1. 1.5

130.0 .0.1

-

N Ingr E ess 1

-

-

3PEG 8-2

200

-

18.1. 2.2

-

-

130.0 .0.3

203


109


MP LS Tu nn el ID

N o d e


No de Ty pe

In Inte rfac e

In L a b el

Rev erse In Lab el

Out Inte rfac e

Ou t La bel

Reve rse Out Labe l

Next Hop

Reve rse Next Hop

Sour ce Nod e

Sink Nod e

N Tra E nsit 2

3PEG 8-2

20 0

202

3PEG 8-4

201

203

18.1. 2.6

18.1. 2.1

130.0 .0.1

130.0 .0.3

N Egr E ess 3

3PEG 8-2

20 1

-

-

202

-

18.1. 2.5

130.0 .0.1

-

Step 2 On NE1, NE2, and NE3, configure MPLS tunnel OAM. For the configuration procedures, see 9.6 Configuring MPLS OAM. Table 3-115 Parameter planning for MPLS tunnel OAM Parameter

Parameter Planning

MPLS Tunnel ID

10

20

OAM Status

Enabled

Enabled

Detection Mode

Manual

Manual


FFD

FFD


3.3


3.3


Step 3 On NE1 and NE3, configure MPLS tunnel APS. For the configuration procedures, see 9.7 Configuring MPLS Tunnel APS. Table 3-116 Parameter planning for MPLS tunnel APS

Issue 03 (2013-02-20)

Parameter

Parameter Planning

Protection Type

1+1

Switching Mode

Single-Ended

Working

10

Tunnel ID


110


Parameter

Protecti on


Parameter Planning

Tunnel Name

NE1_NE3_working

Tunnel ID

20

Tunnel Name

NE1_NE3_protection

Revertive Mode

Revertive

WTR Time (min)

5


0

Protocol State

Enabled


Step 4 On NE1, configure an E-Line service for NodeB 1. 1.


2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the displayed parameters. Table 3-117 Parameters of the E-Line service carried by PWs of NodeB 1

3.

Issue 03 (2013-02-20)

Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

User

Source Port

21-PEFF8-1

Source VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Other parameters

Default values

Click Configure PW. Then, the Configure PW dialog box is displayed. Set the PW parameters. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

111



Table 3-118 PW parameters of the E-Line service of NodeB 1 Parameter General Attributes

Advance d Attributes


35

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


20


20

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

10

TPID

0x8100 NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

Other parameters

Default values

4.


5.

Click the PW tab. Set the QoS parameters of the E-Line service of NodeB 1. Table 3-119 QoS parameters of the E-Line service of NodeB 1 Parameter


PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Other parameters

Default values

Step 5 On NE1, configure an E-Line service for NodeB 2. Refer to Step 4 and configure an E-Line service for NodeB 2.

Issue 03 (2013-02-20)


112



Table 3-120 Parameters of the E-Line service carried by PWs of NodeB 2 Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

Service

Source Port

21-PEFF8-2

Source VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Other parameters

Default values

Table 3-121 PW parameters of the E-Line service of NodeB 2 Parameter


General Attributes

Advanced Attributes

PW ID

45

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


30


30

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.3

Request VLAN

20

TPID


Other parameters

Issue 03 (2013-02-20)


Default values

113



Table 3-122 QoS parameters of the E-Line service of NodeB 2 Parameter


PW ID

45

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Other parameters

Default values

Step 6 On NE3, configure an E-Line service between NodeB 1 and the RNC, and an E-Line service between NodeB 2 and the RNC. Refer to Step 4 and configure the E-Line services. Table 3-123 Parameters of the E-Line service carried by PWs between NodeB 1 and the RNC Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU (STP Packet)


MTU (bytes)

1500

Service Tag Role

User

Source Port

3-PEG8-3

Source VLANs

100

Bearer Type

PW

Protection Type

Unprotected

Other parameters

Default values



General Attributes

Issue 03 (2013-02-20)

PW ID

35

PW Signaling Type

Static

PW Type



114



Parameter


Advanced Attributes

PW Direction

Bidirectional


20


20

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

10

TPID


Other parameters

Default values



PW ID

35

Direction

Ingress

Bandwidth Limit

Enabled

CIR (kbit/s)

10000

PIR (kbit/s)

30000

Other parameters

Default values

Table 3-126 Parameters of the E-Line service carried by PWs between NodeB 2 and the RNC

Issue 03 (2013-02-20)

Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU (STP Packet)


Service Tag Role

Service


115



Parameter


MTU (bytes)

1500

Source Port

3-PEG8-3

Source VLANs

200

Bearer Type

PW

Protection Type

Unprotected

Other parameters

Default values



General Attributes

Advanced Attributes

PW ID

45

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


30


30

Tunnel Type

MPLS

Tunnel

NE1_NE3_working

Peer LSR ID

130.0.0.1

Request VLAN

20

TPID

0x8100 NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

Other parameters

Default values

Table 3-128 QoS parameters of the E-Line service between NodeB 2 and the RNC

Issue 03 (2013-02-20)

Parameter


PW ID

45

Direction

Ingress Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

116



Parameter


Bandwidth Limit

Enabled

CIR (kbit/s)

30000

PIR (kbit/s)

50000

Other parameters

Default values

----End

Relevant Task If you configure PW-carried E-Line services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete PWE3 services to complete PWE3 services. See 3.7.5 Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by PWs are configured correctly.

3.7.5 Verifying the Correctness of E-Line Service Configuration After configuring E-Line services, verify the E-Line services by using the SmartBits.

Prerequisites l

E-Line services carried by PWs are configured.

l


Tools, Equipment, and Materials SmartBits and U2000

Test Connection Diagram Figure 3-18 shows the connections for testing E-Line services carried by PWs. Figure 3-18 Connections for testing E-Line services carried by PWs PSN

SmartBits

SmartBits

21-PEFF8-1 NE1

NE2

NE3

3-PEG8-3

MPLS tunnel PW NOTE

In this example, the SmartBits devices are connected to 21-PEFF8-1 on NE1 (source) and 3-PEG8-3 on NE3 (sink). In actual situations, determine the source and sink as required, and follow the same testing procedure.

Issue 03 (2013-02-20)


117



Context

CAUTION l During a test, only test personnel are allowed in the testing environment. l Exercise caution when touching cables and optical fibers.

Procedure Step 1 Connect the SmartBits devices to 21-PEFF8-1 on NE1 and 3-PEG8-3 on NE3. Step 2 Log in to the U2000. See Enabling, Disabling and Setting Performance Monitoring of the NE to start the 15-minute and 24-hour performance monitoring on NE1 and NE3. NOTE

The performance monitoring tasks help analyze and locate a problem during the test.

Step 3 Use the SmartBits devices to perform a packet transmitting and receiving test. NOTE

l Packets whose bytes are all 0s are considered as special packets. Do not use those packets for a packet transmitting and receiving test. l In the first packet transmitting and receiving period, learning the MAC addresses of the packets may cause packet loss. l If the service is normal, the number of received packets is equal to the number of transmitted packets. If it is a VLAN-based service that involves VLAN switching, check whether VLAN switching functions properly for transmitted and received packets. l If packet loss occurred, rectify the fault. Then, perform 24-hour tests until no packet loss occurs.

----End

3.8 Configuration Example: E-Line Services Carried by QinQ links This topic uses an example to describe how to plan the engineering information and how to configure the E-Line services carried by QinQ links for each NE according to the networking diagram.

3.8.1 Networking Diagram The networking diagram shows the requirements for the E-Line services carried by QinQ links. On the network shown in Figure 3-19, the service requirements of User A and User B are as follows: l


l


Issue 03 (2013-02-20)


118



l

The services of user A and User B must be isolated from each other. The internal VLAN IDs of the services of User A range from 1 to 100. The internal VLAN IDs of the services of User B range from 1 to 200.

l

Different S-VLAN IDs need to be added to the services of User A and User B on the network side, thus realizing the service isolation. The S-VLAN of 30 is added to the services of User A and the S-VLAN of 40 is added to the services of User B.

l

The service between User A1 and User A2 is the common Internet access service of which the CIR is 10 Mbit/s and the PIR is 50 Mbit/s.

l

The service between User B1 and User B2 is the data service of which the CIR is 30 Mbit/ s and the PIR is 50 Mbit/s.

Figure 3-19 Networking diagram of the E-Line services carried by QinQ links V-UNI for User A1: 21-PETF8-1 V-UNI for User B1: 21-PETF8-2 Intranet of User A C-VLAN =1 to 100 NNI : 3-PEG16-1 The S-VLAN ID of 30 is added to the packets of User A.

NE 1 User A1

Intranet of User A C-VLAN =1 to 100 NE2 User B1 Intranet of User B C-VLAN =1 to 200

PSN User A2

The S-VLAN ID of 40 is added to the packets of User B. NNI: 3-PEG16-1

User B2 Intranet o User B C-VLAN =1 to 200

V-UNI for User A2: 21-PETF8-1 V-UNI for User B2: 21-PETF8-2 NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for an Ethernet service carried by QinQ links, see 9.12.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links.

Issue 03 (2013-02-20)


119



3.8.2 Service Planning The engineering information for configuring the E-Line services carried by QinQ links contains the engineering information for configuring the QinQ links carrying the E-Line services and the engineering information for configuring the UNI-NNI E-Line services carried by the QinQ links. The E-Line services need to be carried by QinQ links. Hence, the service planning includes the planning of the QinQ links. Planning the E-Line services carried by QinQ links involves the following: l

Plan the QinQ links that carry the E-Line services. Refer to Table 3-129.

l

Plan the UNI-NNI E-Line services carried by the QinQ links. Refer to Table 3-130.

Table 3-129 Planning information of the E-Line services carried by the QinQ links Parameter

User A(NE1-NE2)

User B(NE1-NE2)

QinQ Link ID

1

2

Board

3-PEG16

3-PEG16

Port

1 (NE1, NE2)

1 (NE1, NE2)

S-Vlan ID

30

40

Bandwidth Limit

Enabled

Enabled

Committed Information Rate (kbit/s)

10000

30000

Peak Information Rate(kbit/ s)

50000

50000

Table 3-130 Planning information of the E-Line services carried by the QinQ links from the user side to the network side

Issue 03 (2013-02-20)

Parameter

User A

User B

Service ID

1

1

Name

E-Line-1

E-Line-2

Direction

UNI-NNI

UNI-NNI

UNI

21-PETF8-1

21-PETF8-2

VLANs

1-100

1-200

Bearer Type

QinQ Link

QinQ Link

QinQ Link ID

1

2

BPDU



MTU (bytes)

1526

1526


120



3.8.3 Configuration Process Before configuring the E-Line services carried by QinQ links, you need to configure the QinQ links.

Prerequisites l

You must be familiar with the networking requirements and service planning for the UNINNI E-Line services carried by the QinQ links.

l


l

The QinQ links must be configured on NE1 and NE2. For the configuration method, see 9.20 Creating a QinQ Link.

Procedure Step 1 On NE1, configure the E-Line services carried by QinQ links of User A1. 1.


2.

Click New. Then, the New E-Line Service dialog box is displayed. Set the parameters of the E-Line services carried by QinQ links of User A1. Table 3-131 Parameters of the E-Line services carried by QinQ links of User A1 Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU


MTU(bytes)

1526

Port

21-PETF8-1

VLANs

1-100

Bearer Type

QinQ Link

QinQ Link ID

1

3.


4.

Click the UNI tab. Set the QoS parameters of the E-Line services carried by QinQ links of User A1.

Issue 03 (2013-02-20)


121



Table 3-132 QoS parameters of the E-Line services carried by QinQ links of User A1 Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

50000

Other parameters

Default values

Step 2 On NE1, configure the E-Line services carried by QinQ links of User B1. Refer to Step 1 and configure the E-Line services carried by QinQ links of User B1. Table 3-133 Parameters of the E-Line services carried by QinQ links of User B1 Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU


MTU(bytes)

1526

Port

21-PETF8-2

VLANs

1-200

Bearer Type

QinQ Link

QinQ Link ID

2

Table 3-134 QoS parameters of the E-Line services carried by QinQ links of User B1

Issue 03 (2013-02-20)

Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000

Other parameters

Default values


122



Step 3 On NE2, configure the E-Line services carried by QinQ links of User A2 and User B2. Refer to Step 1 and configure the E-Line services carried by QinQ links of User A2 and User B2. Table 3-135 Parameters of the E-Line services carried by QinQ links of User A2 Parameter


Service ID

1

Service Name

E-Line-1

Direction

UNI-NNI

BPDU


MTU(bytes)

1526

Port

21-PETF8-1

VLANs

1-100

Bearer Type

QinQ Link

QinQ Link ID

1

Table 3-136 QoS parameters of the E-Line services carried by QinQ links of User A2 Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

10000

PIR(kbit/s)

50000

Other parameters

Default values

Table 3-137 Parameters of the E-Line services carried by QinQ links of User B2

Issue 03 (2013-02-20)

Parameter


Service ID

2

Service Name

E-Line-2

Direction

UNI-NNI

BPDU

Not Transparently Transmitted Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

123



Parameter


MTU(bytes)

1526

Port

21-PETF8-2

VLANs

1-200

Bearer Type

QinQ Link

QinQ Link ID

2

Table 3-138 QoS parameters of the E-Line services carried by QinQ links of User B2 Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

CIR(kbit/s)

30000

PIR(kbit/s)

50000

Other parameters

Default values

----End

Relevant Task See 3.8.4 Verifying the Correctness of E-Line Service Configuration to check whether the E-Line services carried by QinQ links are configured correctly.

3.8.4 Verifying the Correctness of E-Line Service Configuration After the E-Line services are configured, the correctness of service configuration should be verified. The Ethernet OAM function is used to verify the correctness of E-Line service configuration.

Prerequisites The E-Line services must be already created.

Context In the case of UNI-UNI E-Line services, you need not perform the connectivity check by using the 802.1ag OAM function. By default, the UNI-UNI E-Line services are normal. The connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-Line services carried by ports and QinQ links is the same as the connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-Line services carried by PWs. Issue 03 (2013-02-20)


124



This topic considers the E-Line services carried by PWs as the example to describe how to check whether the E-Line services are configured correctly. Before you perform the check, you need to configure the Ethernet OAM function. See Figure 3-20. Figure 3-20 OAM of the E-Line services MA

MD

MEP

User A1

NE1

NE2

MEP

User A2

MEP

MEP

MA

User B1

User B2

MEP: maintenance end point Unicast tunnel PW

MD: maintenance domain MA: maintenance association

As shown in the figure, two E-Line services are configured between User A1 and User A2 and between User B1 and User B2. The two E-Line services are carried and isolated by PWs. To check whether the two E-Line services are configured correctly, you need to configure the Ethernet OAM function. This topic considers the E-Line service between User A1 and User A2 as the example.

Procedure Step 1 At NE1 and NE2, create the maintenance domain for the E-Line service between User A1 and User A2. For the creation method, see Creating an MD. Set the parameters of the maintenance domain. Parameter

NE1

NE2


MD

MD


4

4

NOTE


Step 2 At NE1 and NE2, create the maintenance association for the E-Line service between User A1 and User A2. For the creation method, see Creating an MA. Issue 03 (2013-02-20)


125



Set the parameters of the maintenance association. Parameter

NE1

NE2


MD

MD


MA

MA

Relevant Service

1-E-Line-1

1-E-Line-1


3.33 ms

3.33 ms

Step 3 At NE1 and NE2, create the maintenance end points (MEPs). For the creation method, see Creating an MEP. Set the parameters of the MEPs. Parameter

NE1

NE2


MD

MD


MA

MA

Board

21-PETF8

21-PETF8

Port

1(Port-1)

1(Port-1)

VLAN

100

100

MP ID

1

2

Direction

Ingress

Ingress

CC Status

Active

Active

Step 4 At NE1 and NE2, create the remote MEPs. Perform the CC test. For the test method, see Performing a Continuity Check. NOTE


----End

Issue 03 (2013-02-20)


126


4

4 Configuring E-LAN Services

Configuring E-LAN Services

About This Chapter You can configure the E-LAN services to realize the multipoint-to-multipoint transmission of Ethernet services. 4.1 Basic Concepts Learning about the basic concepts helps to further understand E-LAN services. 4.2 Configuration Flow for the E-LAN Services The flowchart for configuring an E-LAN service differs according to the type of the E-LAN service. 4.3 Configuration Example: E-LAN Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by ports for each NE according to the networking diagram. 4.4 Configuration Example: E-LAN Services Carried by PWs This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by PWs for each NE according to the networking diagram. 4.5 Configuration Example: E-LAN Services Carried by QinQ links This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by QinQ links for each NE according to the networking diagram.

Issue 03 (2013-02-20)


127



4.1 Basic Concepts Learning about the basic concepts helps to further understand E-LAN services.

4.1.1 E-LAN Services As shown in the networking topology, the E-LAN services are multipoint-to-multipoint services. The equipment realizes the multipoint-to-multipoint transmission of Ethernet services through the E-LAN. According to the service transmission mode on the network side, the E-LAN services can be classified into the following types: l

E-LAN services carried by ports

l

E-LAN services carried by PWs

l

E-LAN services carried by QinQ links

E-LAN Services Carried by Ports Figure 4-1 shows the networking diagram of the E-LAN services carried by ports. Three user-side networks, namely, CE1, CE2, and CE3 access the operator network through the FE ports. CE1, CE2, and CE3 have their own VLAN tags and must be able to visit each other. You can configure the E-LAN services to realize the communication between different userside networks. You need to configure the services to be carried by ports on the network side to realize the transmission of the Ethernet services from the user side. In the uplink direction of the user side on each NE node, complex traffic classification can be performed for data packets and different QoS policies can be used according to the traffic types.

Issue 03 (2013-02-20)


128



Figure 4-1 E-LAN services carried by ports UNI

CE1

NNI

FE NE1 NNI

NE3 PSN

FE

CE3

NE2 FE CE2

E-LAN Services Carried by PWs Figure 4-2 shows the networking diagram of the E-LAN services carried by PWs. Three network-side networks, namely, CE1, CE2, and CE3 access the operator network through the FE ports. CE1, CE2, and CE3 have their own VLAN tags and must be able to visit each other. You can configure the E-LAN services to realize the communication between different users. On the network side, the accessed user services are carried by PWs after PW encapsulation, and then are transmitted through the tunnel. In this manner, the transmission of Ethernet services is realized. In the uplink direction of the user side on each NE node, complex traffic classification can be performed for data packets and different QoS policies can be used according to the traffic types.

Issue 03 (2013-02-20)


129



Figure 4-2 E-LAN services carried by PWs

CE1 FE NE1

NE3 PSN

FE

CE3

NE2 PW FE

Tunnel

CE2

E-LAN Services Carried by QinQ Links Figure 4-3 shows the networking diagram of the E-LAN services carried by QinQ links. Three network-side networks, namely, CE1, CE2, and CE3 access the supplier network through the FE ports. CE1, CE2, and CE3 have their own VLAN tags and must be able to visit each other. You can configure the E-LAN services to realize the communication between different user-side networks. On the network side, the Ethernet services are transmitted over QinQ links. When the services are carried by QinQ links, the packets that carry C-VLAN tags from the user-side network are added with the S-VLAN header of the transport network. That is, the packets from the user-side network traverse the transport network, carrying two layers of tags. In the uplink direction of the user side on each NE node, complex traffic classification can be performed for data packets and different QoS policies can be used according to the traffic types.

Issue 03 (2013-02-20)


130



Figure 4-3 E-LAN services carried by QinQ links C-VLAN

CE1

S-VLAN

FE NE1 S-VLAN

NE3 PSN

FE

CE3

NE2 FE CE2

QinQ link



V-UNI Group A V-UNI group contains multiple V-UNIs, and limits the total bandwidth of the Ethernet services received on the member V-UNIs. For a user or an Ethernet service that has multiple access points, you can add the access points to a V-UNI group and set a total bandwidth for the V-UNI group. Bandwidth parameters include committed information rate (CIR), maximum burst size, peak bandwidth, and committed burst size. V-UNIs in a V-UNI group share the total bandwidth but their bandwidths are limited by the total bandwidth. To be specific, when the bandwidth of member A does not reach the CIR, member B can use the remaining bandwidth; when the bandwidths of member A and member B do not reach the CIR but their sum exceeds the total bandwidth of the V-UNI group, member A and member B pre-empt the bandwidth based on service priorities. Issue 03 (2013-02-20)


131



Multiple V-UNIs on a board can be added to a V-UNI group. V-UNIs in a V-UNI group can be changed/deleted at any time, and values of bandwidth parameters can also be modified at any time.





4.1.4 Split Horizon Group A split horizon group consists of some specified ports. The ports in one split horizon group cannot forward packets to each other. To better isolate E-LAN services and to prevent a broadcast storm resulting from a service loop, you can configure a split horizon group for the E-LAN services at the specified nodes. Figure 4-4 shows a typical application of the split horizon group. NEs on the network are configured with E-LAN services, and the east and west NNI ports and service access ports are configured as mounted ports of a bridge. In this case, if a split horizon group is not configured at NE1, a broadcast storm occurs due to a network loop as the east and west NNI ports can forward packets to each other. If a split horizon group is configured at NE1 and the east and Issue 03 (2013-02-20)


132



west NNI ports are configured as members of the split horizon group, the east and west NNI ports do not forward packets to each other. Therefore, a service loop is prevented. Figure 4-4 Service model that applies a split horizon group NE1 BSC

Split horizon group

NodeB NE4

NE2

NodeB

NE3 NodeB

NodeB

4.2 Configuration Flow for the E-LAN Services The flowchart for configuring an E-LAN service differs according to the type of the E-LAN service.

4.2.1 E-LAN Services Carried by Ports You need to configure the NNI to ensure the normal transmission of the E-LAN services carried by ports. Table 4-1 provides the process for configuring the E-LAN services carried by ports.

Issue 03 (2013-02-20)


133



Figure 4-5 Configuration flow for the E-LAN services carried by ports Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by ports

Configure the QoS

Create the E-LAN services carried by ports Create the V-UNI group End

Issue 03 (2013-02-20)


134



Table 4-1 Configuration flow for the E-LAN services carried by ports Step

Operation

1



(Required) The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


135


Step


Operation


(Optional) The parameters are set as follows: l Tag needs to be set according to the type of the packets that are transmitted from the equipment on the opposite end. If all the packets are untagged packets, Tag is set to Access. If all the packets are tagged packets, Tag is set to Tag Aware. If the packets contain untagged packets and tagged packets, Tag is set to Hybrid. l When Tag is set to Access or Hybrid, the Default VLAN ID and VLAN Priority parameters need to be set for the untagged frames. VLAN Priority needs to be set according to the planned QoS.

Issue 03 (2013-02-20)


136


Step


Operation



2


(Required) The ELAN services carried by ports occupy the NNIs exclusively. Hence, you need to set Enable State of the NNIs to Disabled. (Optional) This operation is valid only when the UNI is an Ethernet port. The UNI is connected to the external equipment and thus does not need to transmit the in-band DCN information. Hence, set Enable State of the UNIs to Disabled.

3

Issue 03 (2013-02-20)




137



Step

Operation

Remarks

4



5

9.10.1 Configuring E-LAN Services Carried by Ports


6



4.2.2 E-LAN Services Carried by PWs You need to configure the MPLS tunnel before configuring the E-LAN services carried by PWs. Table 4-2 provides the process for configuring the E-LAN services carried by PWs.

Issue 03 (2013-02-20)


138



Figure 4-6 Configuration flow for the E-LAN services carried by PWs Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by static MPLS tunnel Configure the MPLS tunnel

Configure the QoS

Configure the E-LAN services carried by PWs Create the V-UNI group End

Issue 03 (2013-02-20)


139



Table 4-2 Configuration flow for the E-LAN services carried by PWs Step

Operation

1

Configur ing the UNI (when the UNI is an Ethernet port)


(Required) The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value Auto-Negotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length(byte) is set to the maximum length of the transmitted JUMBO frames.

9.1.2 Setting the Layer 2 Attributes of Ethernet Ports



Issue 03 (2013-02-20)

(Optional) The parameters are set as follows: l Generally, the PSN adopts the QoS scheme to prevent link congestion. Hence, Auto-Negotiation Flow Control Mode and Non-Autonegotiation Flow Control Mode need to be set to the default value Disabled, unless otherwise specified.


140



Step

Operation

Remarks

2


(Optional) This operation is applicable only when the UNI is an Ethernet port. The parameters are set as follows: l The UNI is used for connecting the external equipment and need not transmit in-band DCN information. Hence, Enable Port needs to be set to Disabled for the UNI.

3

4


(Required) Set the parameters as follows:

Configur ing the MPLS tunnel

9.4 Configuring an MPLS Tunnel


9.6 Configuring MPLS OAM

(Optional) The parameters are set as follows:

l Set Port Mode to Layer 3. l Set Enable Tunnel to Enabled.

l OAM Status is set to Enabled. l Detection Mode is set to Manual. l Detection Packet Type is set to FFD. l Detection Packet Period(ms) is set to 3.3.


5



6

l 9.10.2 Creating E-LAN Services Carried by PWs on a Per-NE Basis

(Required) The parameters need to be set according to the service planning information. For details on how to manage Ethernet services carried by PWs, see 9.16 Managing PWE3 Services.

l 9.10.3 Configuring E-LAN Services Carried by PWs in End-to-End Mode 7

Issue 03 (2013-02-20)

(Optional) Set the MPLS tunnel APS parameters according to the service planning information. For details on how to manage MPLS tunnel APS protection groups, see 9.8 Managing MPLS Tunnel APS Protection Groups.




141



4.2.3 E-LAN Services Carried by QinQ Links You need to configure the QinQ links before configuring the E-LAN services carried by QinQ links. Table 4-3 provides the process for configuring the E-LAN services carried by QinQ links. Figure 4-7 Configuration flow for the E-LAN services carried by QinQ links Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Confiure the NNI for the services carried by QinQ links Configure the QinQ links

Configure the QoS

Create the E-LAN services carried by QinQ links Create the V-UNI group End

Issue 03 (2013-02-20)


142



Table 4-3 Configuration flow for the E-LAN services carried by QinQ links Step

Operation

1



The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


143


Step


Operation


(Optional) The parameters are set as follows: l Tag needs to be set according to the type of the packets that are transmitted from the equipment on the opposite end. If all the packets are untagged packets, Tag is set to Access. If all the packets are tagged packets, Tag is set to Tag Aware. If the packets contain untagged packets and tagged packets, Tag is set to Hybrid. When Encapsulation Type is set to QinQ, the Tag parameter cannot be set. l When Tag is set to Access or Hybrid, the Default VLAN ID and VLAN Priority parameters need to be set for the untagged frames. VLAN Priority needs to be set according to the planned QoS.

Issue 03 (2013-02-20)


144


Step


Operation



2



Issue 03 (2013-02-20)

3

9.3.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links


4

9.20 Creating a QinQ Link

The parameters need to be set according to the service planning.


145



Step

Operation

Remarks

5



6

9.10.4 Configuring E-LAN Services Carried by QinQ Links


7



4.3 Configuration Example: E-LAN Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by ports for each NE according to the networking diagram.

4.3.1 Networking Diagram The networking diagram shows the requirement for the E-LAN services carried by ports. On the network as shown in Figure 4-8, the service requirements of each customer edge (CE) are as follows: l

CE1, CE2, and CE3 are connected to NE1, NE2, and NE3 through the 21-PETF8-1 ports on NE1, NE2, and NE3 respectively.

l

Three types of services, which are the voice service (VLAN=100), data service (VLAN=200), and common Internet access service (VLAN=300) in the descending order of priority, are configured between the three CE networks.

l

The voice service requires a fixed bandwidth, of which the CIR and PIR are 10 Mbit/s.

l

The data service requires a fixed bandwidth, of which the CIR and PIR are 40 Mbit/s.

l

In the case of the normal Internet access service, the CIR is 0 Mbit/s and the PIR is 100 Mbit/s.

Issue 03 (2013-02-20)


146



Figure 4-8 Networking diagram of the E-LAN services carried by ports UNI for CE1: 21-PETF8-1 NNI for CE2: 3-PEG16-1 NNI for CE3: 3-PEG16-2 CE 1 UNI for CE3: 21-PETF8-1 NNI for CE1: 3-PEG16-1 NNI for CE2: 3-PEG16-2

FE NE 1

FE

PSN

CE 3

NE 3 NE 2 FE CE 2

UNI for CE2: 21-PETF8-1 NNI for CE3: 3-PEG16-1 NNI for CE1: 3-PEG16-2

NOTE


4.3.2 Service Planning The engineering information for configuring the E-LAN services carried by ports contains the engineering information for configuring the UNIs and the engineering information for configuring the NNIs. On the network, the E-LAN services are carried by ports. Hence, you need to plan the parameters related to the ports. Planning the E-LAN services carried by ports involves the following: l

Plan the E-LAN services carried by ports. Refer to Table 4-4.

l

Plan the UNI of each NE. Refer to Table 4-5.

l

Plan the NNI of each NE. Refer to Table 4-6.

Issue 03 (2013-02-20)


147


l


Plan the QoS of each NE. Refer to Table 4-7. NOTE

You can set one split horizon group for each E-LAN service. You need to configure the NNI of each node with a split horizon group to prevent the data from being forwarded between the UNIs, which may result in a broadcast storm. You can set the unknown frames to be broadcast.

Table 4-4 Planning information of the E-LAN services carried by ports Parameter

NE1

NE2

NE3

Service ID

1

2

3

Name

E-LAN

E-LAN

E-LAN

Tag Type

C-Awared

C-Awared

C-Awared

Self-Learning MAC Address

Enabled

Enabled

Enabled

MAC Address Learning Mode

IVL

IVL

IVL

MTU (bytes)

1526

1526

1526

Table 4-5 Planning information of the UNI Parameter

NE1

NE2

NE3

Port

21-PETF8-1

21-PETF8-1

21-PETF8-1

VLAN Value

100,200,300

100,200,300

100,200,300

Table 4-6 Planning information of the NNI Parameter

NE1

NE2

NE3

Port

3-PEG16-1

3-PEG16-1

3-PEG16-1

3-PEG16-2

3-PEG16-2

3-PEG16-2

Table 4-7 Planning information of the QoS

Issue 03 (2013-02-20)

Parameter

voice service

data service

common Internet access service

CIR(kbit/s)

10000

40000

0

PIR(kbit/s)

10000

40000

100000


148



4.3.3 Configuration Process You can configure the relevant information of the E-LAN services carried by ports according to the engineering information.

Prerequisites l

You must be familiar with the networking requirements and service planning for the ELAN services carried by the ports.

l


l


l

The QoS policy must be configured according to the E-LAN service planning. For the configuration method, see Creating the V-UNI Ingress Policy (OptiX OSN 3500/7500/7500 II).

l

The E-LAN services carried by ports need to occupy the NNIs exclusively. Hence, you need to disable the DCN function of the NNIs. If the E-LAN services carried by ports need to occupy the UNIs exclusively, you also need to disable the DCN function of the UNIs. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 On NE1, configure the E-LAN services carried by ports. 1.

In the NE Explorer, select NE1, and then choose Configuration > Packet Configuration > Ethernet Service Management > E-LAN Service from the Function Tree.

2.

Click New. Then, the New E-LAN Service dialog box is displayed. Set the parameters of the E-LAN services carried by ports. Table 4-8 Parameters of the E-LAN services carried by ports

3.

Issue 03 (2013-02-20)

Parameter


Service ID

1

Service Name

E-LAN

Tag Type

C-Awared


Enabled


IVL

MTU (bytes)

1526

Click the UNI tab. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the UNIs. After setting the parameters, click OK.


149



Table 4-9 Parameters of the UNIs

4.

Parameter


Port

21-PETF8-1

VLANs

100,200,300

Choose NNI > Port. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the NNIs. After setting the parameters, click OK. Table 4-10 Parameters of the NNIs Parameter


Port

3-PEG16-1 3-PEG16-2

5.

Click the Split Horizon Group tab. Click New. Then, the New Split Horizon Group dialog box is displayed. Set the parameters of the split horizon group. After setting the parameters, click OK. Table 4-11 Parameters of the split horizon group Parameter


Selected Interfaces

3-PEG16-1 3-PEG16-2

6.


7.

Click the UNI tab. Set the QoS parameters of the E-LAN services carried by ports. Table 4-12 QoS parameters of the E-LAN services carried by ports Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 2 On NE2, configure the E-LAN services carried by ports. Issue 03 (2013-02-20)


150



Refer to Step 1 and configure the E-LAN services carried by ports. Table 4-13 Parameters of the E-LAN services carried by ports Parameter


Service ID

2

Service Name

E-LAN

Tag Type

C-Awared


Enabled


IVL

MTU (bytes)

1526

Table 4-14 Parameters of the UNIs Parameter


Port

21-PETF8-1

VLANs

100,200,300

Table 4-15 Parameters of the NNIs Parameter


Port

3-PEG16-1 3-PEG16-2

Table 4-16 Parameters of the split horizon group Parameter


Selected Interfaces

3-PEG16-1 3-PEG16-2

Table 4-17 QoS parameters of the E-LAN services carried by ports

Issue 03 (2013-02-20)

Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress


151



Parameter


Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 3 On NE3, configure the E-LAN services carried by ports. Refer to Step 1 and configure the E-LAN services carried by ports. Table 4-18 Parameters of the E-LAN services carried by ports Parameter


Service ID

3

Service Name

E-LAN

Tag Type

C-Awared


Enabled


IVL

MTU (bytes)

1526



Port

21-PETF8-1

VLANs

100,200,300



Port

3-PEG16-1 3-PEG16-2



Selected Interfaces

3-PEG16-1 3-PEG16-2

Issue 03 (2013-02-20)


152



Table 4-22 QoS parameters of the E-LAN services carried by ports Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

----End

Relevant Task See 4.3.4 Verifying the Correctness of E-LAN Service Configuration to check whether the E-LAN services carried by ports are configured correctly.

4.3.4 Verifying the Correctness of E-LAN Service Configuration After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Prerequisites The E-LAN services must be already created.

Context The connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-LAN services carried by ports and QinQ links is the same as the connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-LAN services carried by PWs. This topic considers the E-LAN services carried by PWs as the example to describe how to check whether the E-LAN services are configured correctly. Before you perform the check, you need configure the Ethernet OAM function. See Figure 4-9.

Issue 03 (2013-02-20)


153



Figure 4-9 OAM of the E-LAN services CE1 VLAN=100, 200,300

FE

MEP NE1

FE

PSN

CE3 VLAN=100, 200,300

NE3

MD 1 MA 1 FE

NE2

CE2 VLAN=100, 200,300

MEP MEP: maintenance end point PW

MD: maintenance domain

Tunnel

MA: maintenance association

As shown in the figure, the E-LAN services are configured between CE1, CE2, and CE3. The services are carried and isolated by PWs. To check whether the E-LAN services are configured correctly, you need to configure the Ethernet OAM function. This topic considers the E-LAN service between CE1 and CE2 as the example.

Procedure Step 1 At NE1 and NE2, create the maintenance domain for the E-LAN service between CE1 and CE2. For the creation method, see Creating an MD. Set the parameters of the maintenance domain. Parameter

NE1

NE2


MD 1

MD 1


4

4

NOTE


Step 2 At NE1 and NE2, create the maintenance association for the E-LAN service between CE1 and CE2. For the creation method, see Creating an MA. Issue 03 (2013-02-20)


154




NE1

NE2


MD 1

MD 1


MA 1

MA 1

Relevant Service

1-E-Lan-1

1-E-Lan-1


3.33 ms

3.33 ms

Step 3 At NE1 and NE2, create the MEPs. For the creation method, see Creating an MEP. Set the parameters of the MEPs. Parameter

NE1

NE2


MD 1

MD 1


MA 1

MA

Board

21-PETF8

21-PETF8

Port

1(Port-1)

1(Port-1)

VLAN

100

100

MP ID

1

2

Direction

Ingress

Ingress

CC Status

Active

Active

Step 4 At NE1 and NE2, create the remote MEPs. perform the CC test. For the test method, see Performing a Continuity Check. NOTE


----End

4.4 Configuration Example: E-LAN Services Carried by PWs This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by PWs for each NE according to the networking diagram.

Issue 03 (2013-02-20)


155



4.4.1 Networking Diagram The networking diagram shows the requirement for the E-LAN services carried by PWs. On the network as shown in Figure 4-10, the service requirements of each CE are as follows: l


l


l


l


l


Figure 4-10 Networking diagram of the E-LAN services carried by PWs UNI for CE1: 21-PETF8-1 NNI for CE2: 3-PEG16-1 NNI for CE3: 3-PEG16-2 CE 1 FE MPLS Tunnel 3

NE 1


PSN

MPLS Tunnel 1

MPLS Tunnel 2

FE

CE 3

NE 3

NE 2 PW FE CE 2

Issue 03 (2013-02-20)

Tunnel UNI for CE2: 21-PETF8-1 NNI for CE3: 3-PEG16-1 NNI for CE1: 3-PEG16-2


156



NOTE


NE NE1

NE2

NE3

IP Address

IP Mask

LSR ID

3PEG16-1

18.1.1.1

255.255.255.252

130.0.0.1

3PEG16-2

18.1.3.2

255.255.255.252

3PEG16-1

18.1.2.1

255.255.255.252

3PEG16-2

18.1.1.2

255.255.255.252

3PEG16-1

18.1.3.1

255.255.255.252

3PEG16-2

18.1.2.2

255.255.255.252

130.0.0.2

130.0.0.3

NOTE


4.4.2 Service Planning The engineering information for configuring the E-LAN services carried by PWs contains the engineering information for configuring the tunnel carrying the PWs, the engineering information for configuring the UNIs, the engineering information for configuring the PWs, and the engineering information for configuring the E-LAN services carried by the PWs. On the network, the E-LAN services are carried by PWs. Hence, you need to plan the parameters related to the PWs and the MPLS tunnel. Planning the E-LAN services carried by PWs involves the following: l

Plan the tunnel that carries the PWs. Refer to Table 4-23.

l

Plan the E-LAN services carried by PWs. Refer to Table 4-24.

l


l

Plan the PW on the NNI of each NE. Refer to Table 4-26.

l

Plan the QoS of each NE. Refer to Table 4-27.

Issue 03 (2013-02-20)


157



NOTE


Table 4-23 Planning information of the tunnel carrying the PWs

Issue 03 (2013-02-20)

Par am eter

NE1

NE2

NE3

Tun nel ID

1

2

3

4

2

1

5

6

6

5

4

3

Tun nel Na me

NE1 NE2 #1

NE2 NE1 #1

NE1 NE3 #3

NE3 NE1 #3

NE2 NE1 #1

NE1 NE2 #1

NE2 NE3 #2

NE3 NE2 #2

NE3 NE2 #2

NE2 NE3 #2

NE3 NE1 #3

NE1 NE3 #3

Nod e Typ e

Ingr ess

Egr ess

Ingr ess

Egr ess

Ingr ess

Egre ss

Ingr ess

Egr ess

Ingr ess

Egr ess

Ingr ess

Egr ess

Ban dwi dth (kbi t/s)

100 Mbi t/s

-

100 Mbi t/s

-

100 Mbi t/s

-

100 Mbi t/s

-

100 Mbi t/s

-

100 Mbi t/s

-

In Boa rd/ Log ic Inte rfac e Typ e

-

3PE G16

-

3PE G16

-

3PEG 16

-

3PE G16

-

3PE G16

-

3PE G16

In Port

-

1

-

2

-

2

-

1

-

2

-

1

In Lab el

-

17

-

19

-

16

-

21

-

20

-

18


158



Par am eter

NE1

NE2

NE3

Out Boa rd/ Log ic Inte rfac e Typ e

3PE G16

-

3PE G16

-

3PE G16

-

3PE G16

-

3PE G16

-

3PE G16

-

Out Port

1

-

2

-

2

-

1

-

2

-

1

-

Out Lab el

16

-

18

-

17

-

20

-

21

-

19

-

Nex t Hop Add ress

18.1 .1.2

-

18.1 .3.1

-

18.1 .1.1

-

18.1 .2.2

-

18.1 .2.1

-

18.1 .3.2

-

Sou rce Nod e

-

130. 0.0. 2

-

130. 0.0. 3

-

130. 0.0. 1

-

130. 0.0. 3

-130 .0.0.

18.1 .1.2

-

130. 0.0. 1

Sink Nod e

130. 0.0. 2

-

130. 0.0. 3

-

130. 0.0. 1

-

130. 0.0. 3

-

130. 0.0. 2

-

130. 0.0. 1

-

Table 4-24 Planning information of the E-LAN services carried by PWs

Issue 03 (2013-02-20)

Parameter

NE1

NE2

NE3

Service ID

1

2

3

Service Name

E-LAN-1

E-LAN-2

E-LAN-3

Tag Type

C-Awared

C-Awared

C-Awared


Enabled

Enabled

Enabled


SVL

SVL

SVL

MTU (bytes)

1526

1526

1526


159



Table 4-25 Planning information of the UNIs Parameter

NE1

NE2

NE3

Port

21-PETF8-1

21-PETF8-1

21-PETF8-1

VLAN Value

100,200,300

100,200,300

100,200,300

Table 4-26 Planning information of the PWs Paramete r

NE1

NE2

NE3

PW ID

10

11

20

21

30

31

PW Signaling Type

Static

Static

Static

Static

Static

Static

PW Type







PW Direction

Bidirectio nal

Bidirectio nal

Bidirectio nal

Bidirectio nal

Bidirectio nal

Bidirectio nal


20

30

20

40

40

30


21

31

21

41

41

31

Peer LSR ID

130.0.0.2

130.0.0.3

130.0.0.1

130.0.0.3

130.0.0.2

130.0.0.1

Tunnel No.

Tunnel 1

Tunnel 3

Tunnel 1

Tunnel 2

Tunnel 2

Tunnel 3

Request VLAN

10

30

10

20

20

30

Table 4-27 Planning information of the QoS

Issue 03 (2013-02-20)

Parameter

voice service

data service


CIR(kbit/s)

10000

40000

0


160



Parameter

voice service

data service


PIR(kbit/s)

10000

40000

100000

4.4.3 Configuration Process (in End-to-End Mode) This section describes how to configure E-LAN services carried by PWs in end-to-end mode.

Prerequisites l

You must be familiar with the networking requirements and service planning for the ELAN services carried by the PWs.

l


l

The tunnels that carry the PWs must be configured on NE1, NE2, and NE3. For the configuration method, see 9.4 Configuring an MPLS Tunnel.

l

The QoS policy must be configured according to the E-LAN service planning. For the configuration method, see Creating the V-UNI Ingress Policy(OptiX OSN 3500).

l

If the E-LAN services carried by PWs need to occupy the UNIs exclusively, disable the DCN function of the UNIs. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 Choose Service > VPLS Service > Create VPLS Service from the Main Menu. Step 2 In the Basic Attribute tab, set the parameters of the VPLS services. Table 4-28 Basic attributes of the VPLS services Parameter


Service Name

E-LAN

Signal Type

LDP

Networking Mode

Full-Mesh VPLS

Service Type

Service VPLS

Step 3 Select the VPLS service nodes. 1.

On the right of "Node List", choose Add > NPE. Then, a dialog box is displayed.

2.

In Physical Topology, select NE1, NE2, and NE3.

Step 4 Set the parameters of the VPLS service nodes. 1.

In "Node List", select an NE. Then, click Detail.

2.

Click the VSI Configuration tab and set the relevant parameters of the VPLS service nodes.

Issue 03 (2013-02-20)


161



Table 4-29 Parameters of the VPLS services Parameter


MTU

1526

Tag Type

C-Awared

MAC Address Learning

Enable

Learning Mode

Unqualify(SVL)

Enable BPDU Transparent Transmission


Other parameters

Default values

Step 5 Select the tunnel for carrying the VPLS services. 1.

Click the PW Configuration tab and select the PW between NE1 and NE2.

2.

Click Modify. In the dialog box that is displayed, set the PW parameters.

3.

Refer to steps a and b and set the PW between NE2 and NE3 and the PW between NE1 and NE3.

Table 4-30 PW parameters Parameter

Genera l

Advanc ed

Value in This Example NE1-NE2

NE2-NE3

NE1-NE3

PW ID

10

21

31

In Label

20

40

30

Out Label

20

40

30

In Tunnel

Tunnel 1

Tunnel 2

Tunnel 3

Encapsulati on Type




Request VLAN ID

10

20

30

Other parameters

Default values NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

Step 6 Configure the service access ports. 1.

Click the SAI Configuration tab and select NE1 in "Node List".

2.

Click Create. In the dialog box that is displayed, set the parameters of the service ports.

3.

Refer to steps a and b and set the service access ports on NE2 and NE3.

Issue 03 (2013-02-20)


162



Table 4-31 Parameters of the service ports Parame ter

Value in This Example NE1

NE2

NE3

Interface

21-PETF8-1

21-PETF8-1

21-PETF8-1

VLAN ID

100,200,300

100,200,300

100,200,300

Step 7 Configure QoS. 1.

Click the SAI QoS tab.

2.

Select the ports for which you need to configure QoS and then set the QoS parameters.

Table 4-32 Parameters of the service ports Parameter

Value in This Example NE1

NE2

NE3

Interface

21-PETF8-1

21-PETF8-1

21-PETF8-1

Direction

Ingress

Ingress

Ingress

Global QoS Policy Template

Note: Select the global QoS policy template that is already configured.

Bandwidth Limit

Enable

Enable

Enable

CIR(kbit/s)

50000

50000

50000

PIR(kbit/s)

100000

100000

100000

----End

Relevant Task See 3.4.4 Verifying the Correctness of E-Line Service Configuration to check whether the services are configured correctly.

4.4.4 Configuration Process (Configuration on a Per-NE Basis) You can configure the relevant information of the E-LAN services carried by PWs according to the engineering information.

Prerequisites l

You must be familiar with the networking requirements and service planning for the ELAN services carried by the PWs.

l


Issue 03 (2013-02-20)


163



l


l

The QoS policy must be configured according to the E-LAN service planning. For the configuration method, see Creating the V-UNI Ingress Policy(OptiX OSN 3500).

l


Procedure Step 1 On NE1, configure the E-LAN services carried by PWs. 1.


2.

Click New. Then, the New E-LAN Service dialog box is displayed. Set the parameters of the E-LAN services carried by PWs. Table 4-33 Parameters of the E-LAN services carried by PWs

3.

Parameter


Service ID

1

Service Name

E-LAN-1

Tag Type

C-Awared


Enabled


SVL

MTU (bytes)

1526

Protection Type

Unprotected

MAC Address Withdrawal

Disabled

Click the UNI tab. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the UNIs. After setting the parameters, click OK. Table 4-34 Parameters of the UNIs

4.

Issue 03 (2013-02-20)

Parameter


Port

21-PETF8-1

VLANs

100,200,300

Choose NNI > Port. Click New. Then, the Configure PW dialog box is displayed. Set the parameters of the PWs. After setting the parameters, click OK.


164



Table 4-35 Parameters of the PWs Parameter General Attributes

Advanced Attributes


10

11

PW Signaling Type

Static

Static

PW Type



PW Direction

Bidirectional

Bidirectional


20

30


20

30

Tunnel Type

MPLS

MPLS

Tunnel No.

NE1-NE2#1

NE1-NE3#3

Peer LSR ID

130.0.0.2

130.0.0.3

Request VLAN

10

30

Other parameters

Default values

Default values

NOTE For details on how to configure the TPID, see 9.19 Configuring the NELevel TPID.

5.



Selected Interfaces

PW (Ethernet Tagged Mode, 10) PW (Ethernet Tagged Mode, 11)

6.


7.

Click the UNI tab. Set the QoS parameters of the E-LAN services carried by PWs. Table 4-37 QoS parameters of the E-LAN services carried by PWs

Issue 03 (2013-02-20)

Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled


165



Parameter


Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 2 On NE2, configure the E-LAN services carried by PWs. Refer to Step 1 and configure the E-LAN services carried by PWs. Table 4-38 Parameters of the E-LAN services carried by PWs Parameter


Service ID

2

Service Name

E-LAN-2

Tag Type

C-Awared


Enabled


SVL

MTU (bytes)

1526

Protection Type

Unprotected

MAC Address Withdrawal

Disabled



Port

21-PETF8-1

VLANs

100,200,300

Table 4-40 Parameters of the PWs Parameter


General Attributes

Issue 03 (2013-02-20)

PW ID

20

21

PW Signaling Type

Static

Static

PW Type




166


Parameter



Advanced Attributes

PW Direction

Bidirectional

Bidirectional


20

40


20

40

Tunnel Type

MPLS

MPLS

Tunnel No.

NE2-NE1#1

NE2-NE3#2

Peer LSR ID

130.0.0.1

130.0.0.3

Request VLAN

10

20

Other parameters

Default values

Default values




Selected Interfaces


Table 4-42 QoS parameters of the E-LAN services carried by PWs Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 3 On NE3, configure the E-LAN services carried by PWs. Refer to Step 1 and configure the E-LAN services carried by PWs. Issue 03 (2013-02-20)


167



Table 4-43 Parameters of the E-LAN services carried by PWs Parameter


Service ID

3

Service Name

E-LAN-3

Tag Type

C-Awared


Enabled


SVL

MTU (bytes)

1526



Port

21-PETF8-1

VLANs

100,200,300



General Attributes

Advanced Attributes

PW ID

30

31

PW Signaling Type

Static

Static

PW Type



PW Direction

Bidirectional

Bidirectional


40

30


40

30

Tunnel Type

MPLS

MPLS

Tunnel No.

NE3-NE2#2

NE3-NE1#3

Peer LSR ID

130.0.0.2

130.0.0.1

Request VLAN

20

30

Other parameters

Default values

Default values


Issue 03 (2013-02-20)


168





Selected Interfaces


Table 4-47 QoS parameters of the E-LAN services carried by PWs Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

----End

Relevant Task If you configure PW-carried E-LAN services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete Ethernet services to complete Ethernet services. See 4.4.5 Verifying the E-LAN Service Configuration to check whether the E-LAN services carried by PWs are configured correctly.

4.4.5 Verifying the E-LAN Service Configuration After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Prerequisites l

End-to-end PW-carried E-LAN services have been configured.

l

If you configure PW-carried E-LAN services on a per-NE basis, see 9.16.1 Searching for PWE3 Services and convert discrete Ethernet services to complete Ethernet services.

Procedure Step 1 Choose Service > VPLS Service > Manage VPLS Service from the Main Menu. Issue 03 (2013-02-20)


169



Step 2 In the dialog box that is displayed, set filter conditions; for example, set Service Type to Service VPLS. Then, click Filter. Query all E-LAN services that meet the filter conditions. Step 3 Right-click the required PW-carried E-Line service and choose Ethernet OAM > LB Test from the shortcut menu. Step 4 In the dialog box that is displayed, set filter conditions and click Filter. Step 5 In the dialog box that is displayed, select the source NE and sink NE, and click Run.

Step 6 After the test is complete, click the LB Statistic Information tab to check whether the service is available.

NOTE

If the number of received packets and the number of transmitted packets are the same, the service is available. If testing packet loss fails, troubleshoot it by referring to Troubleshooting Service Packet Loss.

----End

4.5 Configuration Example: E-LAN Services Carried by QinQ links This topic uses an example to describe how to plan the engineering information and how to configure the E-LAN services carried by QinQ links for each NE according to the networking diagram.

4.5.1 Networking Diagram The networking diagram shows the requirement for the E-LAN services carried by QinQ links. On the network as shown in Figure 4-11, the service requirements of each CE are as follows: l


l

The three CE networks can communicate with each other. The VLAN ID of the three CE networks is 100.

l


l


l


l


Issue 03 (2013-02-20)


170



Figure 4-11 Networking diagram of the E-LAN services carried by QinQ links UNI for CE1: 21-PETF8-1 NNI for CE2: 3-PEG16-1 NNI for CE3: 3-PEG16-2 CE1 S-VLAN

FE C-VLAN

NE1


S-VLAN

NE3 PSN

FE

CE 3

NE2 PE

FE CE2


QinQ link

NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for an Ethernet service carried by QinQ links, see 9.12.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links.

4.5.2 Service Planning The engineering information for configuring the E-LAN services carried by QinQ links contains the engineering information for configuring the QinQ links carrying the E-LAN services, the engineering information for configuring the UNIs, and the engineering information for configuring the E-LAN services carried by the QinQ links. On the network, the E-LAN services are carried by QinQ links. Hence, you need to plan the parameters related to the ports. Planning the E-LAN services carried by QinQ links involves the following: l

Plan the QinQ links that carry the E-LAN services. Refer to Table 4-48.

l

Plan the E-LAN services carried by QinQ links. Refer to Table 4-49.

l


Issue 03 (2013-02-20)


171



l


l

Plan the QoS of each NE. Refer to Table 4-52. NOTE


Table 4-48 Planning information of the QinQ links carrying the services Parameter

NE1-NE2

NE2-NE3

NE3-NE1

QinQ Link ID

1

2

3

Board

3-PEG16

3-PEG16

3-PEG16

Port

1(NE1)

1(NE2)

1(NE3)

2(NE2)

2(NE3)

2(NE1)

10

20

30

S-Vlan ID

Table 4-49 Planning information of the E-LAN services carried by the QinQ links Parameter

NE1

NE2

NE3

Service ID

1

2

3

Service Name

E-LAN-1

E-LAN-2

E-LAN-3

Tag Type

C-Awared

C-Awared

C-Awared


Enabled

Enabled

Enabled


IVL

IVL

IVL

MTU (bytes)

1526

1526

1526

Table 4-50 Planning information of the UNIs

Issue 03 (2013-02-20)

Parameter

NE1

NE2

NE3

Port

21-PETF8-1

21-PETF8-1

21-PETF8-1

VLAN Value

100,200,300

100,200,300

100,200,300


172



Table 4-51 Planning information of the NNIs Parameter

NE 1

NE 2

NE 3

QinQ Link ID

1,3

1,2

2,3

Table 4-52 Planning information of the QoS Parameter

voice service

data service


CIR(kbit/s)

10000

40000

0

PIR(kbit/s)

10000

40000

100000

4.5.3 Configuration Process You can configure the relevant information of the E-LAN services carried by QinQ links according to the engineering information.

Prerequisites l

You must be familiar with the networking requirements and service planning for the ELAN services carried by the QinQ links.

l


l

The QoS policy must be configured according to the E-LAN service planning. For the configuration method, see Creating the V-UNI Ingress Policy (OptiX OSN 3500/7500/7500 II).

l

The QinQ links must be configured on NE1, NE2, and NE3. For the configuration method, see 9.20 Creating a QinQ Link.

Procedure Step 1 On NE1, configure the E-LAN services carried by QinQ links. 1.


2.

Click New. Then, the New E-LAN Service dialog box is displayed. Set the parameters of the E-LAN services carried by QinQ links. Table 4-53 Parameters of the E-LAN services carried by QinQ links

Issue 03 (2013-02-20)

Parameter


Service ID

1

Service Name

E-LAN-1

Tag Type

C-Awared


173


3.


Parameter



Enabled


IVL

MTU (bytes)

1526

Click the UNI tab. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the UNIs. After setting the parameters, click OK. Table 4-54 Parameters of the UNIs

4.

Parameter


Port

21-PETF8-1

VLANs

100,200,300

Choose NNI > QinQ Link. Click Add. Then, the QinQ Link Management dialog box is displayed. Select the QinQ link according to the planning information. Then, click OK. Table 4-55 Parameters of the QinQ link

5.

Parameter


QinQ Link ID

1, 3



Selected Interfaces

QinQ Link-1 QinQ Link-3

6.


7.

Click the UNI tab. Set the QoS parameters of the E-LAN services carried by QinQ links. Table 4-57 QoS parameters of the E-LAN services carried by QinQ links

Issue 03 (2013-02-20)

Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled


174



Parameter


Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 2 On NE2, configure the E-LAN services carried by QinQ links. Refer to Step 1 and configure the E-LAN services carried by QinQ links. Table 4-58 Parameters of the E-LAN services carried by QinQ links Parameter


Service ID

2

Service Name

E-LAN-2

Tag Type

C-Awared


Enabled


IVL

MTU (bytes)

1526



Port

21-PETF8-1

VLANs

100,200,300

Table 4-60 Parameters of the QinQ link Parameter


QinQ Link ID

1, 2



Selected Interfaces


Issue 03 (2013-02-20)


175



Table 4-62 QoS parameters of the E-LAN services carried by QinQ links Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

Step 3 On NE3, configure the E-LAN services carried by PWs. Refer to Step 1 and configure the E-LAN services carried by QinQ links. Table 4-63 Parameters of the E-LAN services carried by QinQ links Parameter


Service ID

3

Service Name

E-LAN-3

Tag Type

C-Awared


Enabled


IVL

MTU (bytes)

1526



Port

21-PETF8-1

VLANs

100,200,300

Table 4-65 Parameters of the QinQ link

Issue 03 (2013-02-20)

Parameter


QinQ Link ID

2, 3 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

176





Selected Interfaces


Table 4-67 QoS parameters of the E-LAN services carried by QinQ links Parameter


Interface

21-PETF8-1 (Port-1)

Direction

Ingress

Bandwidth Limit

Enabled

Policy


CIR(kbit/s)

50000

PIR(kbit/s)

100000

Other parameters

Default values

----End

Relevant Task See 4.5.4 Verifying the Correctness of E-LAN Service Configuration to check whether the E-LAN services carried by QinQ links are configured correctly.

4.5.4 Verifying the Correctness of E-LAN Service Configuration After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Prerequisites The E-LAN services must be already created.

Context The connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-LAN services carried by ports and QinQ links is the same as the connectivity check method (by using the 802.1ag OAM function) of the UNI-NNI E-LAN services carried by PWs. This topic considers the E-LAN services carried by PWs as the example to describe how to check whether the E-LAN services are configured correctly. Before you perform the check, you need configure the Ethernet OAM function. See Figure 4-12. Issue 03 (2013-02-20)


177



Figure 4-12 OAM of the E-LAN services CE1 VLAN=100, 200,300

FE

MEP NE1

FE

PSN

CE3 VLAN=100, 200,300

NE3

MD 1 MA 1 FE

NE2

CE2 VLAN=100, 200,300

MEP MEP: maintenance end point PW

MD: maintenance domain

Tunnel

MA: maintenance association

As shown in the figure, the E-LAN services are configured between CE1, CE2, and CE3. The services are carried and isolated by PWs. To check whether the E-LAN services are configured correctly, you need to configure the Ethernet OAM function. This topic considers the E-LAN service between CE1 and CE2 as the example.

Procedure Step 1 At NE1 and NE2, create the maintenance domain for the E-LAN service between CE1 and CE2. For the creation method, see Creating an MD. Set the parameters of the maintenance domain. Parameter

NE1

NE2


MD 1

MD 1


4

4

NOTE


Step 2 At NE1 and NE2, create the maintenance association for the E-LAN service between CE1 and CE2. For the creation method, see Creating an MA. Issue 03 (2013-02-20)


178




NE1

NE2


MD 1

MD 1


MA 1

MA 1

Relevant Service

1-E-Lan-1

1-E-Lan-1


3.33 ms

3.33 ms


NE1

NE2


MD 1

MD 1


MA 1

MA

Board

21-PETF8

21-PETF8

Port

1(Port-1)

1(Port-1)

VLAN

100

100

MP ID

1

2

Direction

Ingress

Ingress

CC Status

Active

Active

Step 4 At NE1 and NE2, create the remote MEPs. perform the CC test. For the test method, see Performing a Continuity Check. NOTE


----End

Issue 03 (2013-02-20)


179


5

5 Configuring E-AGGR Services

Configuring E-AGGR Services

About This Chapter You can configure E-AGGR services to realize the multipoint-to-point service aggregation. 5.1 Basic Concepts Learning about the basic concepts helps to further understand E-AGGR services. 5.2 Configuration Flow for the E-AGGR Services The flowchart for configuring an E-AGGR service differs according to the type of the E-AGGR service. 5.3 Configuration Example: E-AGGR Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-AGGR services carried by ports for each NE according to the networking diagram. 5.4 Configuration Example: E-AGGR Services Carried by PWs This topic uses an example to describe how to plan the engineering information and how to configure the E-AGGR services carried by PWs for each NE according to the networking diagram. 5.5 Verifying the Correctness of E-AGGR Service Configuration After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Issue 03 (2013-02-20)


180



5.1 Basic Concepts Learning about the basic concepts helps to further understand E-AGGR services.

5.1.1 E-AGGR Services As shown in the networking topology, the E-AGGR services are multipoint-to-point services. The equipment aggregates Ethernet services accessed by multiple UNIs to the same UNI or to the same NNI of which the Ethernet services are carried by ports or PWs, or aggregates the Ethernet services that are carried by ports or PWs of multiple NNIs to the same UNI. According to the service transmission mode on the network side, the E-AGGR services can be classified into the following types: l

E-AGGR services carried by ports

l

E-AGGR services carried by PWs

E-AGGR Services Carried by Ports Figure 5-1 shows the networking diagram of the E-AGGR services carried by ports. An operator constructs a 3G network. On the 3G network, the services of each node need to be aggregated and then transmitted to the RNC. The services that are transmitted from a NodeB are accessed to any other node through the UNI. On the network side, you need to configure the services to be carried by ports, thus realizing the aggregation and transmission of the Ethernet services from the user side.

Issue 03 (2013-02-20)


181



Figure 5-1 E-AGGR services carried by ports

FE FE

UNI NNI NE1

UNI

UNI NE3

RNC

PSN GE

FE

NE2 FE

NodeB

E-AGGR Services Carried by PWs Figure 5-2 shows the networking diagram of the E-AGGR services carried by PWs. An operator constructs a 3G network. On the 3G network, the services of each node need to be aggregated and then transmitted to the RNC. The services that are transmitted from a NodeB are accessed to any other node through the UNI. On the network side, you need to configure the services to be carried by PWs, thus aggregating the Ethernet services from the user side to the PWs on the network side. On the node that is connected to the RNC, the tunnels that carry different services are aggregated again and then transmitted to the RNC.

Issue 03 (2013-02-20)


182



Figure 5-2 E-AGGR services carried by PWs

FE FE NE1

NE3

RNC

PSN GE

FE

NE2 FE

NodeB PW Tunnel



V-UNI Group A V-UNI group contains multiple V-UNIs, and limits the total bandwidth of the Ethernet services received on the member V-UNIs. For a user or an Ethernet service that has multiple access points, you can add the access points to a V-UNI group and set a total bandwidth for the V-UNI group. Bandwidth parameters include committed information rate (CIR), maximum burst size, peak bandwidth, and committed burst size. Issue 03 (2013-02-20)


183



V-UNIs in a V-UNI group share the total bandwidth but their bandwidths are limited by the total bandwidth. To be specific, when the bandwidth of member A does not reach the CIR, member B can use the remaining bandwidth; when the bandwidths of member A and member B do not reach the CIR but their sum exceeds the total bandwidth of the V-UNI group, member A and member B pre-empt the bandwidth based on service priorities. Multiple V-UNIs on a board can be added to a V-UNI group. V-UNIs in a V-UNI group can be changed/deleted at any time, and values of bandwidth parameters can also be modified at any time.





5.2 Configuration Flow for the E-AGGR Services The flowchart for configuring an E-AGGR service differs according to the type of the E-AGGR service.

Issue 03 (2013-02-20)


184



5.2.1 E-AGGR Services Carried by Ports You need to configure the NNI to ensure the normal transmission of the E-AGGR services carried by ports. Table 5-1 provides the process for configuring the E-AGGR services carried by ports. Figure 5-3 Configuration flow for the E-AGGR services carried by ports Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by port

Configure the QoS

Create the E-AGGR services carried by ports Create the V-UNI group End

Issue 03 (2013-02-20)


185



Table 5-1 Configuration flow for the E-AGGR services carried by ports Step

Operation

1



The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


186


Step


Operation



Issue 03 (2013-02-20)


187


Step


Operation



2


(Required) The EAGGR services carried by ports occupy the NNIs exclusively. Hence, you need to set Enable State of the NNIs to Disabled. (Optional) This operation is valid only when the UNI is an Ethernet port. The UNI is connected to the external equipment and thus does not need to transmit the in-band DCN information. Hence, set Enable State of the UNIs to Disabled.

3

Issue 03 (2013-02-20)




188



Step

Operation

Remarks

4



5

9.11.1 Configuring E-AGGR Services Carried by Ports


7



5.2.2 E-AGGR Services Carried by PWs You need to configure the MPLS tunnel before configuring the E-AGGR services carried by PWs. Table 5-2 provides the process for configuring the E-AGGR services carried by PWs.

Issue 03 (2013-02-20)


189



Figure 5-4 Configuration flow for the E-AGGR services carried by the MPLS tunnel Start Required Optional

Configure the UNI

Configuring the DCN Function of a Port Configure the NNI for the services carried by static MPLS tunne Configure the MPLS tunnel

Configure the QoS

Create the E-AGGR services carried by PWs Create the V-UNI group End

Issue 03 (2013-02-20)


190



Table 5-2 Configuration flow for the E-AGGR services carried by the MPLS tunnel Step

Operation

1



The parameters are set as follows: l Enable Port is set to Enabled. l Port Mode is set to Layer 2. l Generally, Encapsulation Type is set to 802.1Q. When the packets do not need to be distinguished according to the VLAN tags, Encapsulation Type is set to Null. l Working Mode of the UNI needs to be the same as the working mode of the Ethernet equipment on the opposite end. Generally, this parameter takes the default value AutoNegotiation. l When JUMBO frames need not be transmitted, Max Frame Length(byte) takes the default value 1620. In other cases, Max Frame Length (byte) is set to the maximum length of the transmitted JUMBO frames.

Issue 03 (2013-02-20)


191


Step


Operation



Issue 03 (2013-02-20)


192


Step


Operation



2



3


(Required) Set the parameters as follows: l Set Port Mode to Layer 3. l Set Enable Tunnel to Enabled.

Issue 03 (2013-02-20)


193


Step

Operation

4

Configuring the MPLS tunnel


Remarks 9.4 Configuring an MPLS Tunnel


9.6 Configuring MPLS OAM

(Optional) The parameters are set as follows: l OAM Status is set to Enabled. l Detection Mode is set to Manual. l Detection Packet Type is set to FFD. l Detection Packet Period (ms) is set to 3.3.


5

Issue 03 (2013-02-20)



(Optional) Set the MPLS tunnel APS parameters according to the service planning information. For details on how to manage MPLS tunnel APS protection groups, see 9.8 Managing MPLS Tunnel APS Protection Groups. (Optional) The parameters need to be set according to the service QoS planning.

194



Step

Operation

Remarks

6

9.11.2 Creating E-AGGR Services Carried by PWs on a Per-NE Basis

(Required) The parameters need to be set according to the service planning information. For details on how to manage Ethernet services carried by PWs, see 9.16 Managing PWE3 Services. NOTE You can selectively configure MPLS PW APS according to the service planning information. MPLS tunnel APS and MPLS PW APS cannot be configured for the same service. Therefore, do not configure MPLS PW APS if you already configure MPLS tunnel APS.

7



5.3 Configuration Example: E-AGGR Services Carried by Ports This topic uses an example to describe how to plan the engineering information and how to configure the E-AGGR services carried by ports for each NE according to the networking diagram.

5.3.1 Networking Diagram The networking diagram shows the requirements for the E-AGGR services carried by ports. On the network shown in Figure 5-5, the NodeBs that are connected to NE1 and NE2 respectively need to communicate with the RNC that is connected to NE3. The services are transmitted from Node B to any other node through the UNIs. On the network side, you need to configure the services to be carried by ports, thus realizing the aggregation and transmission of the Ethernet services from the user side. The services of all the NodeBs carry the VLAN ID of 100. Issue 03 (2013-02-20)


195



The service requirements are as follows: l

NodeB 1 and NodeB 2 are connected to NE1 through the 21-PETF8-1 and 21-PETF8-2 ports respectively.

l


l

The RNC, NE1, and NE2 are connected to NE3 through the 3-PEG16-1, 3-PEG16-2, and 3-PEG16-3 ports respectively.

l

The NodeBs and the equipment are interconnected through FE ports. The RNC and the equipment are interconnected through GE ports.

l

The services on NodeB 1 and NodeB 3 are the voice services that require the CIR of 15 Mbit/s and the PIR of 30 Mbit/s.

l

The services on NodeB 2 and NodeB 4 are the data services that require the CIR of 30 Mbit/ s and the PIR of 50 Mbit/s.

Figure 5-5 Networking diagram of the E-AGGR services carried by ports NodeB 1 NodeB 2

UNI for NodeB 1: 21-PETF8-1 UNI for NodeB 2: 21-PETF8-2 NNI: 3-PEG16-1 UNI for RNC: 1-PEG16-1 NNI for NE1: 1-PEG16-2 NNI for NE2: 1-PEG16-3

NE1

RNC GE NE3 NodeB 3

NE2

NodeB 4 UNI for NodeB 3: 21-PETF8-1 UNI for NodeB 4: 21-PETF8-2 NNI: 3-PEG16-1

Issue 03 (2013-02-20)


NodeB

196



NOTE


5.3.2 Service Planning The engineering information for configuring the E-AGGR services carried by ports contains the engineering information for configuring the UNIs, the engineering information for configuring the E-AGGR services carried by the ports, and the engineering information for configuring the VLAN forward tables. On the network, the E-AGGR services are carried by ports. Hence, you need to plan the parameters related to the ports. Planning the E-AGGR services carried by ports involves the following: l

Plan the E-AGGR services carried by ports. Refer to Table 5-3.

l


l


l

Plan the VLAN forward table entries of NE1 and NE2. Refer to Table 5-6.

l

Plan the VLAN forward table entries of NE3. Refer to Table 5-7.

Table 5-3 Planning information of the E-AGGR services carried by ports Parameter

NE1

NE2

NE3

Service ID

1

2

3

Service Name

E-Aggr-1

E-Aggr-2

E-Aggr-3

MTU (bytes)

1526

1526

1526


NE1

NE2

NE3

Port

21-PETF8-1

21-PETF8-1

1-PEG16-1

21-PETF8-2

21-PETF8-2

100

100

VLANs

Issue 03 (2013-02-20)


100,200,300,400

197



Table 5-5 Planning information of the NNIs Parameter

NE1

NE2

NE3

Port

3-PEG16-1

3-PEG16-1

1-PEG16-2 1-PEG16-3

Table 5-6 Planning information of the VLAN forward table entries of NE1 and NE2 Parameter

NE1

NE2

Source Interface Type

V-UNI

V-UNI

V-UNI

V-UNI

Source Interface

21-PETF8-1

21-PETF8-2

21-PETF8-1

21-PETF8-2

Source VLAN ID

100

100

100

100

Sink Interface Type

V-NNI

V-NNI

V-NNI

V-NNI

Sink Interface

3-PEG16-1

3-PEG16-1

3-PEG16-1

3-PEG16-1

Sink VLAN ID

1

2

3

4

Table 5-7 Planning information of the VLAN forward table entries of NE3 Parameter

NE3:

NE3:

NNI for NE1

NNI for NE2


V-NNI

V-NNI

V-NNI

V-NNI

Source Interface

1-PEG16-2

1-PEG16-2

1-PEG16-3

1-PEG16-3

Source VLAN ID

1

2

3

4

Sink Interface Type

V-UNI

V-UNI

V-UNI

V-UNI

Sink Interface

1-PEG16-1

1-PEG16-1

1-PEG16-1

1-PEG16-1

Sink VLAN ID

100

200

300

400

5.3.3 Configuration Process You can configure the relevant information of the E-AGGR services carried by ports according to the engineering information. Issue 03 (2013-02-20)


198



Prerequisites l l l l

You must be familiar with the networking requirements and service planning for the EAGGR services carried by the ports. The port attributes must be set correctly. You must be an NM user with NE administrator authority or higher. The E-AGGR services carried by ports need to occupy the NNIs exclusively. Hence, you need to disable the DCN function of the NNIs. If the E-AGGR services carried by ports need to occupy the UNIs exclusively, you also need to disable the DCN function of the UNIs. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 On NE1, configure the E-AGGR services carried by ports. 1. In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree. 2. Click New. Then, the New E-AGGR Service dialog box is displayed. Set the parameters of the E-AGGR services carried by ports. Table 5-8 Parameters of the E-AGGR services carried by ports

3.

Parameter


Service ID

1

Service Name

E-Aggr-1

MTU (bytes)

1526

Click the UNI tab. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the UNIs. After setting the parameters, click OK. Table 5-9 Parameters of the UNIs Parameter


Location

Source

Port

21-PETF8-1 21-PETF8-2

VLANs 4.

100

Choose NNI > Port. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the NNIs. After setting the parameters, click OK. Table 5-10 Parameters of the NNIs

Issue 03 (2013-02-20)

Parameter


Location

Sink

Port

3-PEG16-1 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

199


5.


Click the VLAN Forwarding Table Item tab. Click New. Then, the New VLAN Forwarding Table Item dialog box is displayed. Set the parameters of the VLAN forwarding table item. After setting the parameters, click OK. Table 5-11 Parameters of the VLAN forwarding table item Parameter



V-UNI

V-UNI

Source Interface

21-PETFF8-1

21-PETF8-2

Source VLAN ID

100

100

Sink Interface Type

V-NNI

V-NNI

Sink Interface

3-PEG16-1

3-PEG16-1

Sink VLAN ID

1

2

6.


7.

Click the UNI tab. Set the QoS parameters of the E-AGGR services carried by ports. Table 5-12 QoS parameters of the E-AGGR services carried by ports Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

15000

30000

PIR(kbit/s)

30000

50000

Other parameters

Default values

Default values

Step 2 On NE2, configure the E-AGGR services carried by ports. Refer to Step 1 and configure the E-AGGR services carried by ports. Table 5-13 Parameters of the E-AGGR services carried by ports

Issue 03 (2013-02-20)

Parameter


Service ID

2

Service Name

E-Aggr-2

MTU (bytes)

1526


200





Location

Source

Port

21-PETF8-1 21-PETF8-2

VLANs

100



Location

Sink

Port

3-PEG16-1

Table 5-16 Parameters of the VLAN forwarding table item Parameter



V-UNI

V-UNI

Source Interface

21-PETR8-1

21-PETR8-2

Source VLAN ID

100

100

Sink Interface Type

V-NNI

V-NNI

Sink Interface

3-PEG16-1

3-PEG16-1

Sink VLAN ID

3

4

Table 5-17 QoS parameters of the E-AGGR services carried by ports

Issue 03 (2013-02-20)

Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

15000

30000

PIR(kbit/s)

30000

50000

Other parameters

Default values

Default values


201



Step 3 On NE3, configure the E-AGGR services carried by ports. Refer to Step 1 and configure the E-AGGR services carried by ports. Table 5-18 Parameters of the E-AGGR services carried by ports Parameter


Service ID

3

Service Name

E-Aggr-3

MTU (bytes)

1526



Location

Sink

Port

1-PEG16-1

VLANs

100,200,300,400



Location

Source

Port

1-PEG16-2 1-PEG16-3

Table 5-21 Parameters of the VLAN forwarding table item

Issue 03 (2013-02-20)

Parameter



V-NNI

V-NNI

V-NNI

V-NNI

Source Interface

1-PEG16-2

1-PEG16-2

1-PEG16-3

1-PEG16-3

Source VLAN ID

1

2

3

4

Sink Interface Type

V-UNI

V-UNI

V-UNI

V-UNI

Sink Interface

1-PEG16-1

1-PEG16-1

1-PEG16-1

1-PEG16-1

Sink VLAN ID

100

200

300

400


202



----End

Relevant Task See 5.5 Verifying the Correctness of E-AGGR Service Configuration to check whether the E-AGGR services carried by ports are configured correctly.

5.4 Configuration Example: E-AGGR Services Carried by PWs This topic uses an example to describe how to plan the engineering information and how to configure the E-AGGR services carried by PWs for each NE according to the networking diagram.

5.4.1 Networking Diagram The networking diagram shows the requirements for the E-AGGR services carried by PWs. On the network shown in Figure 5-6, the NodeBs that are connected to NE1 and NE2 need to communicate with the RNC that is connected to NE3. The services that are transmitted from a NodeB are accessed to any other node through the UNI. On the network side, you need to configure the services to be carried by PWs, thus aggregating the Ethernet services from the user side to the PWs on the network side. On the node that is connected to the RNC, the tunnels that carry different services are aggregated again and then transmitted to the RNC. The services of all the NodeBs carry the VLAN ID of 100. The service requirements are as follows: l


l


l

The RNC, NE1, and NE2 are connected to NE3 through the 1-PEG16-1, 1-PEG16-2, and 1-PEG16-3 ports respectively.

l

The NodeBs and the equipment are interconnected through FE ports. The RNC and the equipment are interconnected through GE ports.

l

The services of NodeB 1 and NodeB 3 are the voice services that require the CIR of 15 Mbit/s and the PIR of 30 Mbit/s.

l

The services of NodeB 2 and NodeB 4 are the data services that require the CIR of 30 Mbit/ s and the PIR of 50 Mbit/s.

Issue 03 (2013-02-20)


203



Figure 5-6 Networking diagram of the E-AGGR services carried by PWs NodeB 1 UNI for NodeB 1: 21-PETF8-1 UNI for NodeB 2: 21-PETF8-2 FE NNI: 3-PEG16-1 FE NodeB 2

NE1

UNI for RNC: 1-PEG16-1 NNI for NE1: 1-PEG16-2 NNI for NE2: 1-PEG16-3

RNC

MPLS tunnel 1 PSN GE

MPLS tunnel 2

FE

NE3

NE2

NodeB 3

FE

NodeB

UNI for NodeB 3: 21-PETF8-1 UNI for NodeB 4: 21-PETF8-2 NNI: 3-PEG16-1

PW Tunnel

NodeB 4 NOTE


NE

Issue 03 (2013-02-20)

IP Address

IP Mask

LSR ID

NE1

3PEG16-1

18.1.1.1

255.255.255.252

130.0.0.1

NE2

3PEG16-1

18.1.2.1

255.255.255.252

130.0.0.2

NE3

3PEG16-2

18.1.1.2

255.255.255.252

130.0.0.3

3PEG16-3

18.1.2.2

255.255.255.252


204



NOTE


5.4.2 Service Planning The engineering information for configuring the E-AGGR services carried by PWs contains the engineering information for configuring the tunnel carrying the PWs, the engineering information for configuring the UNIs, the engineering information for configuring the PWs, the engineering information for configuring the E-AGGR services carried by the PWs, and the engineering information for configuring the VLAN forward table. On the network, the E-AGGR services are carried by PWs. Hence, you need to plan the parameters related to the PWs and the PLS tunnel. Planning the E-AGGR services carried by PWs involves the following: l

Plan the tunnel that carries the PWs. Refer to Table 5-22.

l

Plan the E-AGGR services carried by PWs. Refer to Table 5-23.

l


l


l

Plan the VLAN forward table entries of NE1 and NE2. Refer to Table 5-26.

l

Plan the VLAN forward table entries of NE3. Refer to Table 5-27.

Table 5-22 Planning information of the tunnel carrying the PWs

Issue 03 (2013-02-20)

Param eter

NE1

Tunnel ID

1

2

3

4

2

1

4

3

Tunnel Name

NE1NE3#1

NE3NE1#1

NE2NE3#2

NE3NE2#2

NE3NE1#1

NE1NE3#1

NE3NE2#2

NE2NE3#2

Node Type

Ingress

Egress

Ingress

Egress

Ingress

Egress

Ingress

Egress

Bandwi dth (kbit/s)

100 Mbit/s

-

100 Mbit/s

-

100 Mbit/s

-

100 Mbit/s

-

In Board/ Logic Interfac e Type

-

3PEG16

-

3PEG16

-

1PEG16

-

1PEG16

In Port

-

1

-

1

-

2

-

3

In Label

-

17

-

19

-

16

-

18

NE2

NE3


205



Param eter

NE1

NE2

NE3

Out Board/ Logic Interfac e Type

3PEG16

-

3PEG16

-

1PEG16

-

1PEG16

-

Out Port

1

-

1

-

2

-

3

-

Out Label

16

-

18

-

17

-

19

-

Next Hop Addres s

18.1.1. 2

-

18.1.2. 2

-

18.1.1. 1

-

18.1.2. 1

-

Source Node

-

130.0.0 .3

-

130.0.0 .3

-

130.0.0 .1

-

130.0.0 .2

Sink Node

130.0.0 .3

-

130.0.0 .3

-

130.0.0 .1

-

130.0.0 .2

-

Table 5-23 Planning information of the E-AGGR services carried by PWs Parameter

NE1

NE2

NE3

Service ID

1

2

3

Service Name

E-Aggr-1

E-Aggr-2

E-Aggr-3

MTU (bytes)

1526

1526

1526


NE1

NE2

NE3

Port

21-PETF8-1

21-PETF8-1

1-PEG16-1

21-PETF8-2

21-PETF8-2

100

100

VLANs

Issue 03 (2013-02-20)


100

206



Table 5-25 Planning information of the PWs Parameter

NE1

NE2

NE3:

NE3:

NNI for NE1

NNI for NE2

Location

Sink

Sink

Source

Source

PW ID

10

20

10

20

PW Signaling Type

Static

Static

Static

Static

PW Type





PW Direction

Bidirectional

Bidirectional

Bidirectional

Bidirectional


20

30

20

30


20

30

20

30

Peer LSR ID

130.0.0.3

130.0.0.3

130.0.0.1

130.0.0.2

Tunnel No.

Tunnel 1

Tunnel 2

Tunnel 1

Tunnel 2

Bandwidth Limit

Enabled

Enabled

Enabled

Enabled

CIR(kbit/s)

45000

45000

45000

45000

PIR(kbit/s)

80000

80000

80000

80000

Request VLAN

10

20

10

20

Table 5-26 Planning information of the VLAN forward table entries of NE1 and NE2

Issue 03 (2013-02-20)

Parameter

NE1


V-UNI

V-UNI

V-UNI

V-UNI

Source Interface

21-PETF8-1

21-PETF8-2

21-PETF8-1

21-PETF8-2

Source VLAN ID

100

100

100

100

Sink Interface Type

V-NNI

V-NNI

V-NNI

V-NNI

NE2


207



Parameter

NE1

NE2

Sink Interface

PW( Ethernet Tagged Mode, 10 )




Sink VLAN ID

1

2

3

4

Table 5-27 Planning information of the VLAN forward table entries of NE3 Parameter

NE3:

NE3:

NNI for NE1

NNI for NE2


V-NNI

V-NNI

V-NNI

V-NNI

Source Interface





Source VLAN ID

1

2

3

4

Sink Interface Type

V-UNI

V-UNI

V-UNI

V-UNI

Sink Interface

1-PEG16-1

1-PEG16-1

1-PEG16-1

1-PEG16-1

Sink VLAN ID

100

200

300

400

5.4.3 Configuration Process (in End-to-End Mode) You can configure the relevant information of the E-AGGR services carried by PWs according to the engineering information.

Prerequisites l

You must be familiar with the networking requirements and service planning for the EAGGR services carried by the PWs.

l


l


l

If the E-AGGR services carried by PWs need to occupy the UNIs exclusively, disable the DCN function of the UNIs. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Issue 03 (2013-02-20)


208



Procedure Step 1 Configure an E-AGGR service from NodeB 1, NodeB 2, NodeB 3, and NodeB 4 to the RNC. 1.

Choose Service > E-AGGR Service > Create E-AGGR Service from the Main Menu.

2.

Set basic attributes for the E-AGGR service. Table 5-28 Basic attributes for the E-AGGR service

3.

Parameter


Service ID

1

Service Name

E-Aggr-1

MTU (bytes)

1526

Configure source and sink NEs for the E-AGGR service. a.

Click the Node List tab, and choose Add > Source or Add > Sink. Then, a dialog box is displayed.

b.


c.

Configure boards and ports that receive services, and set attributes for the ports in SAI Configuration. Then, click OK.

Table 5-29 Parameters for the ports that receive services Parameter


NE

NE1

NE2

NE3

Location

Source

Source

Sink

Port

21-PETF8-1

21-PETF8-1

1-PEG16-1

21-PETF8-2

21-PETF8-2

100

100

VLAN ID

4.

100, 200, 300, 400

Click the PW tab, and set basic attributes for the PWs. Table 5-30 Basic attributes for the PWs

Issue 03 (2013-02-20)

Sour ce NE

Sink NE

PW ID

Sign alin g Typ e

For war d Labe l

Rev erse Labe l

For war d Typ e

For war d Tun nel

Rev erse Typ e

Rev erse Tun nel

Enca psul atio n Typ e

NE1

NE3

10

Stati c

20

20

Stati c bindi ng

NE1NE3 #1

Stati c bindi ng

NE3NE1 #1

MPL S


209


5.


Sour ce NE

Sink NE

PW ID

Sign alin g Typ e

For war d Labe l

Rev erse Labe l

For war d Typ e

For war d Tun nel

Rev erse Typ e

Rev erse Tun nel

Enca psul atio n Typ e

NE2

NE3

20

Stati c

30

30

Stati c bindi ng

NE2NE3 #2

Stati c bindi ng

NE3NE2 #2

MPL S

Click the VLAN Forwarding Table tab, and click Add to set parameters. Table 5-31 Parameters in the VLAN forwarding table

6.

Source SAI

Source VLAN ID

PW ID

Transit VLAN ID

Sink SAI

Sink VLAN ID

NE1-21PETF8-1 (Port-1)

100

10

1

NE3-1PEG16-1 (Port-1)

100


100

10

2


200


100

20

3


300


100

20

4


400

Click Advanced to set advanced attributes for the E-AGGR service. a.

Click SAI QoS tab to set QoS parameters for the ingress direction. Table 5-32 QoS parameters for the ingress direction

Issue 03 (2013-02-20)

SAI

Direction

Bandwidt h Enabled

CIR (kbit/ s)

PIR (kbit/ s)

Other Paramete rs


Ingress

Enabled

15000

30000

Default values


Ingress

Enabled

30000

50000

Default values


210


b.


SAI

Direction

Bandwidt h Enabled

CIR (kbit/ s)

PIR (kbit/ s)

Other Paramete rs


Ingress

Enabled

15000

30000

Default values


Ingress

Enabled

30000

50000

Default values

Click the Advanced PW Attribute tab, and set advanced attributes for the PWs. Table 5-33 Advanced attributes for the PWs PW Trail

PW Type

Request VLAN

Other Parameters

(NE1<--->NE3)


10

Default values

(NE2<--->NE3)


20

Default values

----End

Relevant Task See 5.5 Verifying the Correctness of E-AGGR Service Configuration to check whether the E-AGGR service is configured correctly.

5.4.4 Configuration Process (Configuration on a Per-NE Basis) You can configure the relevant information of the E-AGGR services carried by PWs according to the engineering information.

Prerequisites l

You must be familiar with the networking requirements and service planning for the EAGGR services carried by the PWs.

l


l


l

If the E-AGGR services carried by PWs need to occupy the UNIs exclusively, disable the DCN function of the UNIs. For the method of disabling the DCN function of a port, see Configuring the DCN Function of a Port.

Procedure Step 1 On NE1, configure the E-AGGR services carried by ports. Issue 03 (2013-02-20)


211



1.

In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree.

2.

Click New. Then, the New E-AGGR Service dialog box is displayed. Set the parameters of the E-AGGR services carried by PWs. Table 5-34 Parameters of the E-AGGR services carried by PWs

3.

Parameter


Service ID

1

Service Name

E-Aggr-1

MTU (bytes)

1526

Click the UNI tab. Click Configuration. Then, the Configure Port dialog box is displayed. Set the parameters of the UNIs. After setting the parameters, click OK. Table 5-35 Parameters of the UNIs Parameter


Location

Source

Port

21-PETF8-1 21-PETF8-2

VLANs 4.

100

Choose NNI > PW. Click New. Then, the Configure PW dialog box is displayed. Set the parameters of the PWs. After setting the parameters, click OK. Table 5-36 Parameters of the PWs Parameter General Attributes

Issue 03 (2013-02-20)

Value in This Example Location

Sink

PW ID

10

PW Signaling Type

Static

PW Type


PW Direction

Bidirectional


20


20

Tunnel No.

NE1-NE3#1

Peer LSR ID

130.0.0.3


212



Parameter Advanced Attributes

Value in This Example Request VLAN

10

Other parameters

Default values


5.

Click the VLAN Forwarding Table Item tab. Click New. Then, the New VLAN Forwarding Table Item dialog box is displayed. Set the parameters of the VLAN forwarding table item. After setting the parameters, click OK. Table 5-37 Parameters of the VLAN forwarding table item Parameter



V-UNI

V-UNI

Source Interface

21-PETF8-1

21-PETF8-2

Source VLAN ID

100

100

Sink Interface Type

V-NNI

V-NNI

Sink Interface

PW (Ethernet Tagged Mode, 10)


Sink VLAN ID

1

2

6.


7.

Click the UNI tab. Set the QoS parameters of the E-AGGR services carried by PWs. Table 5-38 QoS parameters of the E-AGGR services carried by PWs Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

15000

30000

PIR(kbit/s)

30000

50000

Other parameters

Default values

Default values

Step 2 On NE2, configure the E-AGGR services carried by PWs. Refer to Step 1 and configure the E-AGGR services carried by PWs.

Issue 03 (2013-02-20)


213



Table 5-39 Parameters of the E-AGGR services carried by PWs Parameter


Service ID

2

Service Name

E-Aggr-2

MTU (bytes)

1526



Location

Source

Port

21-PETF8-1 21-PETF8-2

VLANs

100



General Attributes

Advanced Attributes

Location

Sink

PW ID

20

PW Signaling Type

Static

PW Type

Ethernet

PW Direction

Bidirectional


30


30

Tunnel No.

NE2-NE3#2

Peer LSR ID

130.0.0.3

Request VLAN

20

Other parameters

Default values


Issue 03 (2013-02-20)


214



Table 5-42 Parameters of the VLAN forwarding table item Parameter



V-UNI

V-UNI

Source Interface

21-PETF8-1

21-PETF8-2

Source VLAN ID

100

100

Sink Interface Type

V-NNI

V-NNI

Sink Interface



Sink VLAN ID

3

4

Table 5-43 QoS parameters of the E-AGGR services carried by PWs Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

15000

30000

PIR(kbit/s)

30000

50000

Other parameters

Default values

Default values

Step 3 On NE3, configure the E-AGGR services carried by PWs. Refer to Step 1 and configure the E-AGGR services carried by PWs. Table 5-44 Parameters of the E-AGGR services carried by PWs Parameter


Service ID

3

Service Name

E-Aggr-3

MTU (bytes)

1526

Table 5-45 Parameters of the UNIs

Issue 03 (2013-02-20)

Parameter


Location

Sink

Port


215



Parameter


VLANs

100



General Attributes

Advanced Attributes

Location

Source

Source

PW ID

10

20

PW Signaling Type

Static

Static

PW Type



PW Direction

Bidirectional

Bidirectional


20

30


20

30

Tunnel No.

NE3-NE1#1

NE3-NE2#2

Peer LSR ID

130.0.0.1

130.0.0.2

Request VLAN

10

20

Other parameters

Default values

Default values


Table 5-47 Parameters of the VLAN forwarding table item

Issue 03 (2013-02-20)

Parameter



V-NNI

V-NNI

V-NNI

V-NNI

Source Interface





Source VLAN ID

1

2

3

4


216



Parameter


Sink Interface Type

V-UNI

V-UNI

V-UNI

V-UNI

Sink Interface

1-PEG16-1

1-PEG16-1

1-PEG16-1

1-PEG16-1

Sink VLAN ID

100

200

300

400

Table 5-48 QoS parameters of the E-AGGR services carried by PWs Parameter


Interface

21-PETF8-1 (Port-1)

21-PETF8-2 (Port-2)

Direction

Ingress

Ingress

Bandwidth Limit

Enabled

Enabled

CIR(kbit/s)

15000

30000

PIR(kbit/s)

30000

50000

Other parameters

Default values

Default values

----End

Relevant Task See 5.5 Verifying the Correctness of E-AGGR Service Configuration to check whether the E-AGGR services carried by PWs are configured correctly.

5.5 Verifying the Correctness of E-AGGR Service Configuration After the data configuration is complete, you need to check whether data configuration is correct by verifying the configured services.

Prerequisites The E-AGGR services must be already created.

Context The connectivity check method (by using the 802.1ag OAM function) of the E-AGGR services carried by ports is the same as the connectivity check method (by using the 802.1ag OAM function) of the E-AGGR services carried by PWs. Issue 03 (2013-02-20)


217



This topic considers the E-AGGR services carried by PWs as the example to describe how to check whether the E-AGGR services are configured correctly. Before you perform the check, you need configure the Ethernet OAM function. See Figure 5-7. Figure 5-7 OAM of the E-AGGR services

NodeB1 FE

MEP

FE NodeB2

MD 1

NE1

MEP

MEP MA 1

MA 2

RNC PSN GE NE3

FE

NE2

NodeB3

FE NodeB4

MEP: maintenance end point MD: maintenance domain MA: maintenance association

NodeB PW Tunnel

As shown in the figure, the services of NodeB 1 and NodeB 2 are aggregated on NE1, the services of NodeB 3 and NodeB 4 are aggregated on NE2, and then all the services are aggregated to the RNC through NE3. The services are carried and isolated by PWs. To check whether the E-AGGR services are configured correctly, you need to configure the Ethernet OAM function. This topic considers the E-AGGR service between NodeB 1 and RNC as the example.

Procedure Step 1 At NE1 and NE3, create the maintenance domain for the E-AGGR service between NodeB 1 and NodeB 2. For the creation method, see Creating an MD. Set the parameters of the maintenance domain.

Issue 03 (2013-02-20)

Parameter

NE1

NE3


MD 1

MD 1


218



Parameter

NE1

NE3


4

4

NOTE


Step 2 At NE1 and NE3, create the maintenance association for the E-AGGR service between NodeB 1 and NodeB 2. For the creation method, see Creating an MA. Set the parameters of the maintenance association. Parameter

NE1

NE3


MD 1

MD 1


MA 1

MA 1

Relevant Service

1-E-Line-1

1-E-Line-1


3.33 ms

3.33 ms


NE1

NE3


MD 1

MD 1


MA 1

MA 1

Board

21-PETF8

21-PETF8

Port

1(Port-1)

1(Port-1)

VLAN

100

100

MP ID

1

2

Direction

Ingress

Ingress

CC Status

Active

Active

Step 4 At NE1 and NE3, create the remote MEPs. perform the CC test. For the test method, see Performing a Continuity Check.

Issue 03 (2013-02-20)


219



NOTE


----End

Issue 03 (2013-02-20)


220


6

6 Configuring Cross-Domain Services

Configuring Cross-Domain Services

About This Chapter You can configure cross-domain services to achieve the service transmission from the TDM domain to the packet domain and vice versa. 6.1 Introduction to the Cross-Connect Board The OptiX OSN equipment supports the EoD board, which enables service conversion between the TDM domain and the packet domain. 6.2 Configuration Flow for the Cross-Domain Services This topic describes the operation tasks of cross-domain service configuration and the flow relationships between the operation tasks. The flows of configuring cross-domain services in different scenarios are similar, and therefore This topic describes the general-purpose configuration model only. For application scenario 3, This topic describes the configuration flow for cross-domain service configuration only. 6.3 Configuration Example (Application Scenario 1) The EoS services from the TDM domain are received and processed at the EoD board, and then are transmitted to the packet domain. 6.4 Configuration Example (Application Scenario 2) The EoS services from the TDM domain are received on the SDH line board, and then are transmitted to the EoD board for processing before entering the packet domain. 6.5 Configuration Example (Application Scenario 3) The SDH services (including the pure SDH service and EoS service) from the TDM domain are processed on the EoD board. Then, pure SDH services are transmitted to the TDM domain, and EoS services are transmitted to the packet domain. 6.6 Testing Cross-domain Services Cross-domain services refer to the services that are transmitted from the TDM domain to the packet domain by using the EoD board. After configuring cross-domain services, you need to test whether the configuration is correct.

Issue 03 (2013-02-20)


221



6.1 Introduction to the Cross-Connect Board The OptiX OSN equipment supports the EoD board, which enables service conversion between the TDM domain and the packet domain. Figure 6-1 shows the typical networking and application of the EDQ41. Figure 6-1 Networking and application of the EDQ41

RNC

BSC

STM-16/STM-64 ring

10GE ring

E1

GE ring

FE FE STM-1/STM-4 ring Networking in the TDM domain

Networking in the packet domain

TDM traffic direction

Packet traffic direction

The EDQ41 is applicable in four typical networking scenarios. Figure 6-2 shows the service signal flow in each application scenario. l

Application 1: The EDQ41 receives EoS services from other NEs and then converts the EoS services to packet services, therefore implementing transition from the STM-1/STM-4 SDH network to the GE/10GE packet network.

l

Application 2: The EDQ41 receives EoS services from line boards on the same NE and then converts the EoS services to packet services, therefore implementing transition from the SDH network to the GE/10GE packet network.

l

Application 3: The EDQ41 board receives SDH services (including SDH services and EoS services) from SDH line board, processes and then distributes the services to GE/10GE packet networks and STM-1/STM-4 SDH networks.

Issue 03 (2013-02-20)


222


l


Application 4: The EDQ41 board receives SDH services (including pure SDH services and EoS services) from SDH line boards, processes and then sends the services directly to the SDH network. In this case, the EDQ41 board functions like an SDH line board. NOTE

The EDQ41 supports the maximum processing capacity of 2.5 Gbit/s. Therefore, only 2.5 Gbit/s services of the services received from STM-N (1≤N≤64) line boards can be processed and sent to the packet network.

Figure 6-2 Service signal flow on the EDQ41 Application 2:

Application 1: STM-1/STM-4 ring

EDQ41 borad

Packet core

Packet board

GE/10GE ring

EDQ41 borad

TDM core

Application 3: STM-1/STM-4 ring

Packet core

Packet board

TDM core

SDH board

GE/10GE ring

STM-N

Application 4:

EDQ41 borad

Packet core

Packet board

TDM core

SDH board

GE/10GE ring

STM-1/STM-4 ring

STM-N

EDQ41 borad

Packet core

Packet board

TDM core

SDH board

STM-N

6.2 Configuration Flow for the Cross-Domain Services This topic describes the operation tasks of cross-domain service configuration and the flow relationships between the operation tasks. The flows of configuring cross-domain services in different scenarios are similar, and therefore This topic describes the general-purpose configuration model only. For application scenario 3, This topic describes the configuration flow for cross-domain service configuration only. Table 6-1 provides the procedures for configuring cross-domain services.

Issue 03 (2013-02-20)


223



Figure 6-3 Configuration flow for cross-domain services Start Required

1. Configure network ports

Optional

4. Configure MPLS tunnel 2. Configure services on the TDM domain

5. Configure protection on the packet domain

6. Configure HQoS 3. Configure protection on the TDM domain 7. Configure E-Line service on the packet domain

8. Configure Composite Service

End NOTE

The service configuration procedures on the TDM domain and the packet domain are not in sequence. In the figure, the sequence numbers are presented to facilitate description.

Issue 03 (2013-02-20)


224



Table 6-1 Configuration flow for inter-NE service conversion Ste p

Ser vic e Do ma in

Operation

Remarks

1

-

Configuring network ports

Required. Including the following parameters: l Configuring network ports on the TDM domain – Configuring Ethernet external ports – Configure Ethernet internal ports l Configuring network ports on the packet domain – Configuring general attributes of Ethernet ports – Configuring Layer 3 attributes of Ethernet ports

2

TD M

Configuring services on the TDM domain

Required. The services on the TDM domain generally are Ethernet private line (EPL) services on the TDM domain, and you need to specify such information as the service source and sink. NOTE In the case of cross-domain NEs, pure SDH services can be configured on the TDM domain when the EDQ41 board accomplishes TDMdomain and packet-domain service distribution.

Configuring protection on the TDM domain

3

Optional. By configuring SNCP services on the TDM domain, the services on the TDM domain can be transmitted through the specified timeslots on the transmission lines, and are under 1+1 protection. NOTE Currently, only SNCP is supported.

4

Pac ket

Configuring an MPLS tunnel

Required. An MPLS tunnel can be created in two manners: perNE and end-to-end. Set the tunnel ID, service name, tunnel label, ingress node, egress node, and transit node according to the network planning. NOTE MPLS tunnels are not configured on the EDQ41 board.

5

Configuring protection on the packet domain

Optional. MPLS tunnel APS can be used to protect packet services. NOTE l MPLS tunnel APS and MPLS PW APS are not configured on the EDQ41 board. l In the case of EDQ41 board, you can configure LAG of VCTRUNKs between boards to protect cross-domain services.

6

Issue 03 (2013-02-20)

Configuring HQoS

Optional. The parameters need to be set according to the service QoS planning.


225


Ste p

Ser vic e Do ma in

7

8

TD M/ Pac ket


Operation

Remarks

Configuring E-Line services on the packet domain

Required. The parameters need to be set according to the service planning.

Configuring composite services

Optional. If no protection is configured, you can configure the composite service, implementing end-to-end management of services on the TDM domain and packet domain. For details about composite service management, see 9.17 Managing Composite Services.

6.3 Configuration Example (Application Scenario 1) The EoS services from the TDM domain are received and processed at the EoD board, and then are transmitted to the packet domain.

6.3.1 Networking Diagram By configuring services on the dual-domain bridging board, you can shift EoS services from a non-local NE on the TDM domain to the packet domain and vice versa. On a cross-domain network as shown in Figure 6-4, NE2 is the intersecting node between the TDM domain and the packet domain. The EoS services are received on the EDQ41 boards on NE2, and are then converted through the EDQ41 boards. In this manner, network communication is achieved between the TDM domain and the packet domain. l

The NodeB receives 2 Mbit/s services, and transmits the services to the TDM domain.

l

The EDQ41 board converges the services from the TDM domain, and transmits the services to the packet domain.

l

The service between the NodeB and the RNC uses the VLAN ID of 100.

Issue 03 (2013-02-20)


226



Figure 6-4 Networking diagram of cross-domain services NodeB

TDM domain 7-EDQ41-1 2-EFS4

11-SL1

3-PEG8-1

3-PEG8-1

8-SL1

NE3

RNC

Packet domain

3-PEG8-2

12-EDQ41-1

3-PEG8-3

3-PEG8-2 NE1

NE2

NE NE1

NE2

IP Address

IP Mask

LSR ID

3-PEG8-1

18.1.1.1

255.255.255.252

130.0.0.1

3-PEG8-2

18.1.2.1

255.255.255.252

3-PEG8-1

18.1.1.2

255.255.255.252

3-PEG8-2

18.1.2.2

255.255.255.252

130.0.0.2

NOTE


6.3.2 Service Planning The engineering information of application scenario 1 includes parameters of the services on the TDM domain and the packet domain. As shown in Figure 6-5, application scenario 1 mainly involves the following parameters on the TDM domain: l

Parameter planning for EPL services

l

Parameter planning for binding paths on the EDQ41 board

l

Parameter planning for SDH service cross-connections

Issue 03 (2013-02-20)


227



Figure 6-5 Planning information of TDM service parameters EDQ41 bound paths EPL service TDM domain

EDQ41 (PORT5)

NodeB NE3

NE2

SDH service cross-connections

Table 6-2 Parameter planning for EPL services Parameter

Parameter Planning

Board

2-EFS4

External Port

PORT1

Internal Port

VCTRUNK1

Level

VC12

Bound Path

VC4-4-VC12(1)

Type of Service

EPL

Service Direction

Bidirectional

Source Port

PORT1

Source VLAN

100

Sink Port

VCTRUNK1

Sink VLAN

100

Table 6-3 Parameter planning for binding paths on the EDQ41 board

Issue 03 (2013-02-20)

Parameter

Parameter Planning

Board

7-EDQ41

Configurable Ports

VCTRUNK1

Level

VC12


228



Parameter

Parameter Planning

Bound Path

VC4-5-VC12(1)

Table 6-4 Parameter planning for SDH service cross-connections Parameter

NE3

NE2

Service Direction

Bidirectional

Bidirectional

Level

VC-12

VC-12

Source Slot

8-SL1-1(SDH-1)

7-EDQ41-1(SDH-1)

Source VC4

1

1

Source Timeslot Range(e.g.1,3-6)

1

1

Sink Slot

2-EFS4-1(SDH-1)

7-EDQ41-5(SDH-5) NOTE 7-EDQ41-5 corresponds to VCTRUNK1.

Sink VC4

1

5

Sink Timeslot Range(e.g.1,3-6)

1

1

As shown in Figure 6-6, application scenario 1 mainly involves the following parameters on the packet domain: l

Parameter planning for tunnels carrying PWs

l

Parameter planning for the UNI-NNI E-Line services carried by PWs

Figure 6-6 Service parameter planning on the packet domain UNI-NNI E-Line services carried by PWs

Packet domain RNC

NE2

NE1 MPLS tunnel

Issue 03 (2013-02-20)


229



Table 6-5 Basic attributes of a tunnel Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed

Table 6-6 Planning information of the tunnels N od e

Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1


Issue 03 (2013-02-20)

Parameter Planning NE2

NE1

Service ID

1

1

Service Name

E-Line-1

E-Line-1

Service Direction

UNI-NNI

UNI-NNI

BPDU



MTU (bytes)

This parameter adopts the default value.


Source Port

7-EDQ41-1(PORT1)

3-PEG8-1(PORT1)

NOTE PORT1 corresponds to VCTRUNK1.

NOTE PORT1 corresponds to External Port 1.

Souce VLANs

100

100

Bearer Type

PW

PW

Protection Type

Unprotected

Unprotected


230



Table 6-8 Parameter planning for PWs Parameter

Parameter Planning

PW ID

1

PW Signaling Type

Static

PW Type


Direction

Bidirectional

PW Ingress Label

20

PW Egress Label

20

Tunnel Type

MPLS

Tunnel

NE2-NE1

Request VLAN

10

6.3.3 Configuration Process Inter-domain services include EPL services in the TDM domain and PWE3 services in the packet domain. It is easier to configure EPL services in the TDM domain and PWE3 services in the packet domain in end-to-end mode than on a per-NE basis.

Prerequisites l


l

Automatic Laser Shutdown of the optical port on the TDM domain is enabled.

Procedure Step 1 Configure VC-4 server trails between NE2 and NE3. 1.

Choose Service > SDH Trail > Create SDH Trail from the main menu. In the dialog box that is displayed, set the following trail parameters: l Direction: Bidirectional l Level: VC4 Server Trail l Other parameters: default settings

2.

Click Browse and select NE3 as the source NE and select NE2 as the sink NE.

3.

Click Calculate Route.

4.

Click Apply.

5.

Create the other VC-4 server trail by referring to Step 1.1-Step 1.4.

Issue 03 (2013-02-20)


231



NOTE

l If you select Calculate Route, the SDH trail is automatically computed after the source and sink NEs are specified. l After selecting Set Route Timeslot, you can specify timeslots for the SDH trail. Normally, the SDH trail uses its default timeslots. l If you select Activate the trail, the SDH trail is created on the NMS and deployed to the corresponding NEs. l If you select Copy after Creation, you can duplicate the created SDH trail to other timeslots.

Step 2 Create SDH cross-connections. 1.

Choose Service > SDH Trail > Create SDH Trail from the main menu. In the dialog box that is displayed, set the following trail parameters: l Direction: Bidirectional l Level: VC12 l Other parameters: default settings

2.

Click Browse and select the source and sink timeslots. l Source: NE3-2-EFS4-1(SDH-1)-VC4:4-VC12:1[1-1-1] l Sink: NE2-7-EDQ41-5(SDH-5)-VC4:5-VC12:1[1-1-1]

3.


4.

Click Apply.

Step 3 Create trunk links between NE2 and NE3. 1.

Choose Service > MSTP Trail > Create Trunk Link from the main menu. In the dialog box that is displayed, set the following trunk link parameters: l Bandwidth: 1 l Level: VC12 NOTE

The server trails have been created in Step 1. Therefore, you do not need to select Auto Create Server Trail in this step.

2.

Click Browse. In the dialog box that is displayed, select NE3 as the source NE; in the slot layout view, select the 2-EFS4 board and then select VCTRUNK1.

3.

Click Browse. In the dialog box that is displayed, select NE2 as the sink NE; in the slot layout view, select the 7-EDQ41 board and then select VCTRUNK1.

4.

Select Server Layer Trail.

5.

Click Apply.

Step 4 Create an unterminated EPL service between NE2 and NE3. 1.

Choose Service > MSTP Trail > Create Unterminated EPL from the main menu. Set Port Usage Strategy of the EPL service to Port+VLAN.

2.

Click Browse . Select NE3-2-EFS4-PORT1 as Port and select VLAN as 100.

3.

Click Next and set parameters such as the port attribute and service name. l Parameters for the EFS4 board external ports: – Port: PORT1 – TAG: Tag Aware – Working Mode: Auto-Negotiating

Issue 03 (2013-02-20)


232



l Parameters for the EFS4 board internal ports: – Port: VCTRUNK1 – TAG: Tag Aware l Name: EPL_01 Step 5 Follow the instructions in 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode and configure a tunnel for carrying PWs. Table 6-9 Basic attributes of a tunnel Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1

Step 6 Follow the instructions in 9.9.4 Configuring E-Line Services Carried by PWs in End-to-End Mode and configure a PWE3 service. Table 6-11 Basic attributes of a PWE3 service Parameter


Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

UNprotected

Table 6-12 Parameters for PWE3 service ports

Issue 03 (2013-02-20)

Parameter


Source Port

7-EDQ41-1

Sink Port


233





PW ID

1

Signaling Type

Static

Forward Label

20

Reverse Label

20

Forward Type

Static Binding

Forward Tunnel

NE2-NE1#1

Reverse Type

Static Binding

Reverse Tunnel

NE1-NE2#1

Encapsulation Type

MPLS

Request VLAN

10

Step 7 Create a composite service. 1.

Choose Service > Composite Service > Create Composite Service from the main menu. Set Service Name of the composite service to EPL+PWE3_01.

2.

In Service Component, click Select > EPL. In the Ethernet Trail Management dialog box that is displayed, select the EPL service whose Name is EPL_01.

3.

In Service Component, click Select > PWE3. In the Manage PWE3 Service dialog box that is displayed, select the EPL service whose Service Name is E-Line-1.

4.

In Connection Point, click Create > Interface. In the dialog box that is displayed, set Type to PWE3+EPL.

5.

In Interface Information List, select port information and click information. Then, click OK.

Issue 03 (2013-02-20)


to add the port

234



l EPL service: – Service Name: EPL_01 – Service Type: EPL l PWE3 service: – Service Name: E-Line-1 – Service Type: PWE3 6.

Click OK.

----End

Related Task Follow the instructions in Testing Cross-domain Services to check whether services are configured correctly.

6.4 Configuration Example (Application Scenario 2) The EoS services from the TDM domain are received on the SDH line board, and then are transmitted to the EoD board for processing before entering the packet domain.

6.4.1 Networking Diagram By configuring services on the dual-domain bridging board, you can shift EoS services of the line boards on the local NE to the packet domain and vice versa. On a cross-domain network as shown in Figure 6-7, NE2 is the intersecting node of the TDM domain and the packet domain. The EoS services are received on the SL1 board on NE2, and are then converted through the EDQ41 board. In this manner, network communication is achieved between the TDM domain and the packet domain. l Issue 03 (2013-02-20)

The NodeB receives 2 Mbit/s services, and transmits the services to the TDM domain. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

235



l

The SL1 board receives the EoS services, and transmits the services to the EDQ41 board for conversion.

l

The EDQ41 board converges the services from the TDM domain, and transmits the services to the packet domain.

Figure 6-7 Networking diagram of service conversion NodeB

TDM domain 2-EFS4

8-SL1

NE3

11-SL1

11-SL1

8-SL1

7-EDQ41 (PORT5)

RNC

Packet domain 3-PEG8-1

3-PEG8-1

3-PEG8-2 12-EDQ41 (PORT5)

3-PEG8-3

3-PEG8-2 NE1

NE2

NE NE1

NE2

IP Address

IP Mask

LSR ID

3-PEG8-1

18.1.1.1

255.255.255.252

130.0.0.1

3-PEG8-2

18.1.2.1

255.255.255.252

3-PEG8-1

18.1.1.2

255.255.255.252

3-PEG8-2

18.1.2.2

255.255.255.252

130.0.0.2

NOTE


l

PORT5 of the EDQ41 board in the figure corresponds to the internal port.

6.4.2 Service Planning The engineering information of application scenario 2 includes parameters of the services on the TDM domain and the packet domain. As shown in Figure 6-8, application scenario 2 mainly involves the following parameters on the TDM domain: l


l


l


Issue 03 (2013-02-20)


236



Figure 6-8 Planning information of TDM service parameters EPL service TDM domain

EDQ41 (PORT5)

NodeB NE3

NE2 SDH service cross-connection SNCP


Parameter Planning

Board

2-EFS4

External Port

PORT1

Internal Port

VCTRUNK1

Level

VC12

Bound Path

VC4-4-VC12(1)

Type of Service

EPL

Service Direction

Bidirectional

Source Port

PORT1

Source VLAN

100

Sink Port

VCTRUNK1

Sink VLAN

100

Table 6-15 Parameter planning for SDH service cross-connections

Issue 03 (2013-02-20)

Parameter

NE3

NE2

Level

VC12

VC12

Direction

Bidirectional

Bidirectional

Source Slot

8-SL1-1 (SDH-1)

11-SL1-1 (SDH-1)

Source VC4

1

1


237



Parameter

NE3

NE2

Source Timeslot Range(e.g. 1, 3-6)

1

1

Sink Slot

2-EFS4-1 (SDH-1)

7-EDQ41-5 (SDH-5) NOTE 7-EDQ41-5 corresponds to VCTRUNK1.

Sink VC4

1

1

Sink Timeslot Range (e.g. 1, 3-6)

1

1



l



Packet domain RNC

NE2

NE1 MPLS tunnel

Table 6-16 Basic attributes of a tunnel

Issue 03 (2013-02-20)

Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


238




Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1



NE1

Service ID

1

1

Service Name

E-Line-1

E-Line-1

Service Direction

UNI-NNI

UNI-NNI

BPDU



MTU (bytes)



Source Port

7-EDQ41-1(PORT1)

3-PEG8-1(PORT1)



Souce VLANs

100

100

Bearer Type

PW

PW

Protection Type

Unprotected

Unprotected

Table 6-19 Parameter planning for PWs

Issue 03 (2013-02-20)

Parameter

Parameter Planning

PW ID

1

PW Signaling Type

Static

PW Type


Direction

Bidirectional Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

239



Parameter

Parameter Planning

PW Ingress Label

20

PW Egress Label

20

Tunnel Type

MPLS

Tunnel

NE2-NE1

Request VLAN

10


Prerequisites l


l

Automatic Laser Shutdown of the optical port on the TDM domain is enabled.



2.


3.


4.

Click Apply.

5.

Create the other VC-4 server trail by referring to Step 1.1-Step 1.4. NOTE


Step 2 Create SDH cross-connections. 1.

Choose Service > SDH Trail > Create SDH Trail from the main menu. In the dialog box that is displayed, set the following trail parameters: l Direction: Bidirectional

Issue 03 (2013-02-20)


240



l Level: VC12 l Other parameters: default settings 2.


3.


4.

Click Apply.




2.


3.


4.


5.

Click Apply.



2.


3.

Click Next and set parameters such as the port attribute and service name. l Parameters for the EFS4 board external ports: – Port: PORT1 – TAG: Tag Aware – Working Mode: Auto-Negotiating l Parameters for the EFS4 board internal ports: – Port: VCTRUNK1 – TAG: Tag Aware l Name: EPL_01

Step 5 Follow the instructions in 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode and configure a tunnel for carrying PWs. Table 6-20 Basic attributes of a tunnel

Issue 03 (2013-02-20)

Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


241




Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1



Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

UNprotected

Table 6-23 Parameters for PWE3 service ports Parameter


Source Port

7-EDQ41-1

Sink Port

3-PEG8-3

Table 6-24 PW parameters

Issue 03 (2013-02-20)

Parameter


PW ID

1

Signaling Type

Static

Forward Label

20

Reverse Label

20 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

242



Parameter


Forward Type

Static Binding

Forward Tunnel

NE2-NE1#1

Reverse Type

Static Binding

Reverse Tunnel

NE1-NE2#1

Encapsulation Type

MPLS

Request VLAN

10



2.


3.


4.


5.


to add the port

l EPL service: – Service Name: EPL_01 – Service Type: EPL l PWE3 service: Issue 03 (2013-02-20)


243



– Service Name: E-Line-1 – Service Type: PWE3 6.

Click OK.

----End


6.5 Configuration Example (Application Scenario 3) The SDH services (including the pure SDH service and EoS service) from the TDM domain are processed on the EoD board. Then, pure SDH services are transmitted to the TDM domain, and EoS services are transmitted to the packet domain.

6.5.1 Networking Diagram By configuring services on the dual-domain bridging board EDQ41, the hybrid services from the line boards (on the local NE or not) are distributed and transmitted to the packet domain and TDM domain. On a cross-domain network as shown in Figure 6-10, NE2 is the intersecting node of the TDM domain and the packet domain. On NE2, the hybrid services from the SL4 board on NE1 are distributed on the EDQ41 board, and are then transmitted to the packet domain and TDM domain. l

NodeB1 receives 2 Mbit/s data services, and NodeB2 receives 2 Mbit/s voice services. Then, the services are transmitted to the TDM domain through NE3.

l

The EDQ41 board distributes the hybrid services from the TDM domain. – The data services from NodeB1 are transmitted to the packet domain, and arrive at RNC1. – The voice services from NodeB2 are transmitted to another TDM domain through the line board, and arrive at RNC2.

Issue 03 (2013-02-20)


244



Figure 6-10 Networking diagram of cross-domain services RNC1 3-PEG8-3

3-PEG8-1 NE1 FE

NodeB1

TDM domain

Packet domain

3-PEG8-2

3-PQ1 E1

3-PEG8-2

7-EDQ41-1

7-SL4

2-EFS4-1

3-PEG8-1

NE3

11-SL4

12-EDQ41-1

NE2 11-SL4

NodeB2

TDM domain

8-SL4 8-SL4

11-SL4

RNC2 NE4

NE NE1

NE2

7-SL4

IP Address

IP Mask

LSR ID

3-PEG8-1

18.1.1.1

255.255.255.252

130.0.0.1

3-PEG8-2

18.1.2.1

255.255.255.252

3-PEG8-1

18.1.1.2

255.255.255.252

3-PEG8-2

18.1.2.2

255.255.255.252

130.0.0.2

NOTE


6.5.2 Service Planning The engineering information of application scenario 3 includes parameters of the services on the TDM domain and the packet domain. As shown in Figure 6-11, application scenario 3 mainly involves the following parameters configure the services from NodeB1 on the TDM domain: l


l


l


Issue 03 (2013-02-20)


245



Figure 6-11 Planning information of configure the services from NodeB1 on TDM domain parameters EDQ41 bound paths EPL service TDM domain

EDQ41 (PORT5)

NodeB1 NE3

NE2



Parameter Planning

Board

2-EFS4

External Port

PORT1

Internal Port

VCTRUNK1

Level

VC12

Bound Path

VC4-4-VC12(1)

Type of Service

EPL

Service Direction

Bidirectional

Source Port

PORT1

Source VLAN

100

Sink Port

VCTRUNK1

Sink VLAN

100

Table 6-26 Parameter planning for binding paths on the EDQ41 board

Issue 03 (2013-02-20)

Parameter

Parameter Planning

Board

7-EDQ41

Configurable Ports

VCTRUNK1

Level

VC12 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

246



Parameter

Parameter Planning

Bound Path

VC4-5-VC12(1)

Table 6-27 Parameter planning for SDH service cross-connections Parameter

Service Planning

Level

VC-12

VC-12

Direction

Bidirectional

Bidirectional

Source Slot

7-SL4-1 (SDH-1)

7-EDQ41-1 (SDH-1)

Source VC4

1

1

Source Timeslot Range (e.g. 1, 3-6)

1

1

Sink Slot

2-EFS4-1 (SDH-1)

7-EDQ41-5 (SDH-5) NOTE 7-EDQ41-5 corresponds to VCTRUNK1.

Sink VC4

1

1


1

1

As shown in Figure 6-12, application scenario 3 mainly involves the following parameters on the TDM domain: l

Parameter planning for SNCP services

l


Figure 6-12 Planning information of configure the services from NodeB2 on TDM domain parameters

TDM domain RNC2

NE3

NE2

SDH service

NodeB2


SDH service SNCP

Issue 03 (2013-02-20)

NE4


SNCP

247



Table 6-28 Parameter planning for SNCP services (optional) Parameter

NE3

NE4

Parameter Value of the Service from NodeB2

Parameter Value of the Service from the RNC

Type of Service

SNCP

SNCP

Service Direction

Bidirectional

Bidirectional

Level

VC-12

VC-12

Hold-off Time(100ms)

0

0

Revertive Mode

Non-Revertive

Non-Revertive

WTR Time (s)

-

-

Working Service

Source Slot

7-SL4-1(SDH-1)

8-SL4-1(SDH-2)

Source VC4

1

1


2

1

Source Slot

11-SL4-1(SDH-1)

11-SL4-1(SDH-2)

Source VC4

1

1


1

1

Sink Slot

3-PQ1(SDH-1)

7-SL4-1(SDH-1)

Sink VC4

1

1

Sink Timeslot Range(e.g.1,3-6)

1

1

Protectio n Service

Table 6-29 Parameter planning for SDH service cross-connections

Issue 03 (2013-02-20)

Parameter

Service Planning

Level

VC-12

VC-12

Direction

Bidirectional

Bidirectional

Source Slot

7-EDQ41-1 (SDH-1)

12-EDQ41-1 (SDH-1)

Source VC4

1

1

Source Timeslot Range (e.g. 1, 3-6)

2

1

Sink Slot

8-SL4-1 (SDH-1)

11-SL4-1 (SDH-1)


248



Parameter

Service Planning

Sink VC4

1

1


1

1



l



Packet domain RNC

NE2

NE1 MPLS tunnel

Table 6-30 Basic attributes of a tunnel

Issue 03 (2013-02-20)

Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


249




Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1



NE1

Service ID

1

1

Service Name

E-Line-1

E-Line-1

Service Direction

UNI-NNI

UNI-NNI

BPDU



MTU (bytes)



Source Port

7-EDQ41-1(PORT1)

3-PEG8-1(PORT1)



Souce VLANs

100

100

Bearer Type

PW

PW

Protection Type

Unprotected

Unprotected

Table 6-33 Parameter planning for PWs

Issue 03 (2013-02-20)

Parameter

Parameter Planning

PW ID

1

PW Signaling Type

Static

PW Type


Direction

Bidirectional Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

250



Parameter

Parameter Planning

PW Ingress Label

20

PW Egress Label

20

Tunnel Type

MPLS

Tunnel

NE2-NE1

Request VLAN

10


Prerequisites l


l

Automatic Laser Shutdown of the optical port on the TDM domain is enabled. NOTE

This topic describes the end-to-end configuration process of cross-domain services. The configuration process for E1 services from NodeB2 is simple and therefore not described here.



2.


3.


4.

Click Apply.

5.

Create the other VC-4 server trail by referring to Step 1.1-Step 1.4. NOTE


Step 2 Create SDH cross-connections. Issue 03 (2013-02-20)


251


1.


Choose Service > SDH Trail > Create SDH Trail from the main menu. In the dialog box that is displayed, set the following trail parameters: l Direction: Bidirectional l Level: VC12 l Other parameters: default settings

2.


3.


4.

Click Apply.




2.


3.


4.


5.

Click Apply.



2.


3.

Click Next and set parameters such as the port attribute and service name. l Parameters for the EFS4 board external ports: – Port: PORT1 – TAG: Tag Aware – Working Mode: Auto-Negotiating l Parameters for the EFS4 board internal ports: – Port: VCTRUNK1 – TAG: Tag Aware l Name: EPL_01

Step 5 Follow the instructions in 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode and configure a tunnel for carrying PWs.

Issue 03 (2013-02-20)


252



Table 6-34 Basic attributes of a tunnel Paramete r

MPLS Tunnel name

MPLS Tunnel ID

Protocol Type

Signalin g Type

Direction

Protected Type

Parameter Planning

NE2_NE1

10

MPLS

Static CR

Bidirectio nal

Unprotect ed


Nod e Type

In Interf ace

In Label

Rever se In Label

Out Interf ace

Out Label

Rever se Out Label

Next Hop

Rever se Next Hop

NE 2

Ingre ss

-

-

101

3PEG81

100

-

18.1.1. 2

-

NE 1

Egres s

3PEG81

100

-

-

101

-

18.1.1. 1



Service Type

ETH

Service ID

1

Service Name

E-Line-1

Protection Type

UNprotected

Table 6-37 Parameters for PWE3 service ports

Issue 03 (2013-02-20)

Parameter


Source Port

7-EDQ41-1

Sink Port

3-PEG8-3


253





PW ID

1

Signaling Type

Static

Forward Label

20

Reverse Label

20

Forward Type

Static Binding

Forward Tunnel

NE2-NE1#1

Reverse Type

Static Binding

Reverse Tunnel

NE1-NE2#1

Encapsulation Type

MPLS

Request VLAN

10



2.


3.


4.


5.


Issue 03 (2013-02-20)


to add the port

254



l EPL service: – Service Name: EPL_01 – Service Type: EPL l PWE3 service: – Service Name: E-Line-1 – Service Type: PWE3 6.

Click OK.

----End


6.6 Testing Cross-domain Services Cross-domain services refer to the services that are transmitted from the TDM domain to the packet domain by using the EoD board. After configuring cross-domain services, you need to test whether the configuration is correct. Based on the functions of the EoD board in cross-domain services, cross-domain services can be applied in the following scenarios: l

Application 1 The EoD board receives and processes the EoS services from the TDM domain and then transmits the services to the packet domain. For details, see 6.3 Configuration Example (Application Scenario 1).

l Issue 03 (2013-02-20)

Application 2 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

255



The SDH line board receives the EoS services from the TDM domain. Then, the EoD board processes the EoS services and transmits them to the packet domain. For details, see 6.4 Configuration Example (Application Scenario 2). l

Application 3 The EoD board receives and processes the SDH services from the TDM domain (including pure SDH services and EoS services) and then transmits the pure SDH services to the TDM domain and the EoS services to the packet domain. For details, see 6.5 Configuration Example (Application Scenario 3).

l

Application 4 When functioning as a common line board, the EoD board receives and processes the SDH services (including pure SDH services and EoS services) from the TDM domain, but does not transmit the services to the packet domain.

You can test cross-domain services by using the following two methods. Test Method

Application Scope

Using the ping commands to test crossdomain service channels

This method is simple because it does not require any instrument or meter. Use this method to check the status of cross-domain service channels.

Using loopbacks to test cross-domain service channels

This method requires the Network Analyzer. Use this method to measure the packet loss ratio on cross-domain service channels.

6.6.1 Using the Ping Commands to Test Cross-domain Services For the cross-domain services, you can connect the test computers at both of the services and use the ping commands to test the cross-domain service channels.

Prerequisites l


l

The services are configured according to actual situations. For details, see 6 Configuring Cross-Domain Services in the Configuration Guide.

Tools, Equipment, and Materials Two computers with Windows operating system installed

Test Connection Diagram NOTE

The methods for testing various cross-domain services are the same. This section describes only a generalpurpose test model.

Figure 6-14 shows how to test the cross-domain service channels.

Issue 03 (2013-02-20)


256



Figure 6-14 Connection diagram for testing cross-domain service channels PC 1 TDM domain

NE3

PC 2

EDQ41

Packet domain

NE2

NE1

NE1 NE2

OptiX OSN 7500 OptiX OSN 3500

NE3

OptiX OSN 1500

Procedure Step 1 Connect the network port of the PC to the Ethernet service port of the equipment according to the previous connection diagram. Step 2 Set the IP addresses for PC 1 and PC 2. The two IP addresses must be set in the same network section. l Set the IP address for PC 1. – IP address: 192.168.0.100 – Subnet mask: 255.255.255.0 l Set the IP address for PC 2. – IP address: 192.168.0.101 – Subnet mask: 255.255.255.0 Step 3 Choose Start > Run on PC 1 to display a dialog box. Enter the ping command: ping 192.168.0.101 -n 20000 -l 64 -t. NOTE

Parameters for the Ping command: l -n Num: transit Num packets to the PC at the opposite end l -l Num: transmit buffer capacity is Num bytes l -t: continuously transmit ping packets

Step 4 Click OK to run the ping command. l A window is displayed to provide the feedback "Reply from 192.168.0.101: bytes=64 time=1ms TTL=255". This information indicates the Ethernet channel is normal. l If the displayed window provides the feedback Request timed out, it indicates that the Ethernet channel is abnormal. Check the network cable connection and the configuration of the Ethernet service. Rectify the fault, and then continue the test.

Issue 03 (2013-02-20)


257



NOTE

The values of time and TTL are associated with the actual test environment. The value discrepancy is normal.

----End

6.6.2 Using Loopbacks to Test Cross-domain Services To test cross-domain service channels, you can perform a loopback on the access side of crossdomain services and test whether packet loss occurs on the convergence side by using a Network Analyzer.

Prerequisites l


l

Cross-domain services are configured according to actual situations. For details, see 6 Configuring Cross-Domain Services in the Configuration Guide.

Tools, Equipment, and Materials Network Analyzer, U2000

Test Connection Diagram Figure 6-15 shows how to test cross-domain service channels. Figure 6-15 Connection diagram for testing cross-domain service channels TDM domain

2-EFS4-1

EDQ41

Packet domain

SmartBits 3-PEG8-3

MAC inloop NE3

NE2

NE1

NE1 NE2

OptiX OSN 7500 OptiX OSN 3500

NE3

OptiX OSN 1500

NOTE

An inloop at the MAC layer is performed at the 2-EFS4-1 port on NE3. A SmartBits is connected to the 3-PEG8-3 port on NE1. In actual situations, you can select different ports at the access node and the convergence node and perform a test similarly.

Issue 03 (2013-02-20)


258



Context

CAUTION l Ensure that only the commissioning engineers are present during the test. l Do not touch optical fibers, wires, or cables without permission.

Procedure Step 1 Connect a SmartBits to the 3-PEG8-3 port on NE1 according to the connection diagram. Step 2 Log in to the U2000. Start the 15-minute and 24-hour performance monitoring for NE1 and NE3. For details, see Enabling, Disabling and Setting Performance Monitoring of the NE. NOTE

The performance monitoring is set to analyze and locate faults that occur during the test.

Step 3 Log in to the U2000. Perform an inloop at the MAC layer on the 2-EFS4-1 port of NE3. For details, see Setting a Loopback on an Ethernet Port. Step 4 Use the SmartBits to transmit and receive packets. NOTE

l Packets with all 0s are regarded as special packets. Therefore, do not use packets of all 0s for testing transmitted and received packets. l When the SmartBits transmits and receives packets for the first time, packet loss occurs due to MAC address learning. Therefore, it is normal that the number of transmitted packets is different from the number of received packets. l In the tests after the first time, if the number of transmitted packets is the same as the number of received packets, the cross-domain service channels are normal. l If packet loss occurs during the tests, troubleshoot the fault and then perform 24-hour tests until the channels pass the tests.

----End

Issue 03 (2013-02-20)


259


7

7 Configuring CES Services

Configuring CES Services

About This Chapter The circuit emulation service (CES) function supports direct access of TDM E1 services to the packet domain. Therefore, the CES function helps achieve smooth evolution from the TDM domain to the packet domain. 7.1 Introduction to CES CES: By using the PWE3 technology, PWE3 packet headers are added to TDM traffic to create circuit emulation services (CES). PWE3 packet headers carry the frame format information, alarm information, signaling information, and synchronization and timing information of the TDM traffic. The encapsulated PW packets are transmitted over the MPLS tunnel on the PSN. After being decapsulated at the PW egress, the TDM circuit switched service traffic is re-created. On a packet switching network, the transmit and receive ends of a CES service maintain clock synchronization by means of adaptive clock recovery (ACR). 7.2 Configuration Flow for the CES Services The configuration flow varies according to the types of the CES services. 7.3 Configuration Example (UNI-UNI CES Services) This topic uses an example to describe how to configure UNI-UNI CES services. 7.4 Configuration Example (UNI-NNI CES Services) This topic uses an example to describe how to configure UNI-NNI CES services. 7.5 Verifying CES Service Configuration After configuring a CES service, you need to verify whether the service configuration is correct.

Issue 03 (2013-02-20)


260



7.1 Introduction to CES CES: By using the PWE3 technology, PWE3 packet headers are added to TDM traffic to create circuit emulation services (CES). PWE3 packet headers carry the frame format information, alarm information, signaling information, and synchronization and timing information of the TDM traffic. The encapsulated PW packets are transmitted over the MPLS tunnel on the PSN. After being decapsulated at the PW egress, the TDM circuit switched service traffic is re-created. On a packet switching network, the transmit and receive ends of a CES service maintain clock synchronization by means of adaptive clock recovery (ACR).

Emulation Mode The OptiX NG-SDH series equipment supports two types of CES services: structure-aware TDM circuit emulation service over packet switched network (CESoPSN) CES and structure-agnostic TDM over packet (SAToP) CES. In the case of CESoPSN CES: l

The equipment senses the frame format, frame alignment mode, and timeslot information in the TDM circuit.

l

The equipment processes the overheads and extracts the payloads in TDM frames. Then, the equipment loads timeslots to the packet payload in a certain sequence. As a result, the services in each timeslot are fixed and visible in packets.

In the case of SAToP CES: l

The equipment does not sense any format in the TDM signal. Instead, it considers TDM signals as bit flows at a constant rate, and therefore the entire bandwidth of TDM signals is emulated.

l

The overheads and payloads in TDM signals are transparently transmitted.

Service Type CES services are classified into UNI-UNI CES services and UNI-UNI CES services by service implementation point. l

UNI-UNI CES services As shown in Figure 7-1, a single OptiX OSN NE completes access of TDM services.

Issue 03 (2013-02-20)


261



Figure 7-1 UNI-UNI CES services

PSN

NE TDM link

BTS

Channelized STM link BSC

l

UNI-NNI CES services As shown in Figure 7-2, the OptiX OSN NEs support UNI-NNI CES services. In the case of a UNI-NNI CES service, the OptiX OSN NEs access customer TDM services through E1 ports or STM-1 ports; CES PWs are created between the OptiX OSN NEs to emulate end-to-end TDM services. Figure 7-2 UNI-NNI CES services NE BTS

NE PSN BSC

NE TDM link PW

BTS

Tunnel

Issue 03 (2013-02-20)


262



7.2 Configuration Flow for the CES Services The configuration flow varies according to the types of the CES services.

7.2.1 Configuration Flow for UNI-UNI CES Services This topic describes the operation tasks for configuring UNI-UNI CES services and the relationships between the operations tasks. Table 7-1 provides the process for configuring UNI-UNI CES services. Figure 7-3 Configuration flow for UNI-UNI CES services Start 1. Create the network Required 2. Configure CES service ports

3. Configure UNIUNI CES services

End

Table 7-1 Configuration flow for UNI-UNI CES services Ste p

Operation

Remarks

1

Creating the network

Create NEs, configure NE data, create optical fibers, and configure clocks.

2

Configuring CES service ports

Required. l 9.2.1 Configuring Channelized STM-1 Ports l 9.2.2 Configuring E1 Ports Use the CES board to support access of base station services.

3

Issue 03 (2013-02-20)

Configuring UNI-UNI CES services

Required. Set the service ID, service name, service source, and service sink.


263



7.2.2 Configuration Flow for the UNI-NNI CES Services This topic describes the operation tasks for configuring UNI-NNI CES services and the relationships between the operations tasks. Table 7-2 provides the process for configuring UNI-NNI CES services. Figure 7-4 Configuration flow for UNI-NNI CES services Start

1. Create the network Required Optional

2. Configure the LSR IDs of NEs 3. Configure the NNIs on the packet domain

4. Configure the MPLS tunnels

5. Configure CES service ports

6. Configure UNI-NNI CES services

End

Table 7-2 Configuration flow for UNI-NNI CES services

Issue 03 (2013-02-20)

St ep

Operation

Remarks

1


Create NEs, configure NE data, create optical fibers, and configure clocks.

2

Configuring the LSR ID

-


264



St ep

Operation

Remarks

3

Configuring the NNI ports on the packet domain

Required. l Set the general attributes of Ethernet ports. l Set the Layer 3 attributes of Ethernet ports, including tunnel enabled status and IP address. This operation task is performed so that the NNI ports on the packet domain can carry tunnels.

4

Configuri ng MPLS tunnels

Configurin g an MPLS Tunnel


Configurin g MPLS OAM

(Optional) The parameters are set as follows: l OAM Status is set to Enabled. l Detection Mode is set to Manual. l Detection Packet Type is set to FFD. l Detection Packet Period(ms) is set to 3.3.

Configurin g MPLS Tunnel APS 5

Configuring CES service ports

(Optional) Set the MPLS tunnel APS parameters according to the service planning information. For details on how to manage MPLS tunnel APS protection groups, see 9.8 Managing MPLS Tunnel APS Protection Groups. Required. l 9.2.1 Configuring Channelized STM-1 Ports l 9.2.2 Configuring E1 Ports Use the CES board to support access of base station services.

6

Configuring UNI-NNI CES services

Required. 1. Create CES services, that is, set the service ID and service name. 2. Set the source and sink information, that is, set the source and sink boards and channels. 3. Configure PWs, that is, set information such as the PW type, Protection Type, PW label, and tunnel type. 4. Set the advanced attributes, including the RTP head, jitter buffer time and packet loading time. NOTE You can selectively configure MPLS PW APS according to the service planning information. MPLS tunnel APS and MPLS PW APS cannot be configured for the same service. Therefore, do not configure MPLS PW APS if you already configure MPLS tunnel APS.

Issue 03 (2013-02-20)


265



7.3 Configuration Example (UNI-UNI CES Services) This topic uses an example to describe how to configure UNI-UNI CES services.

7.3.1 Networking Diagram This topic describes the networking diagram of UNI-UNI CES services. As shown in Figure 7-5, an OptiX OSN 3500 is used to support access of CES services between the two BTSs and the BSC. One CES service is configured between BTS1 and the BSC and one CES service is configured between BTS2 and the BSC. Figure 7-5 Networking diagram of UNI-UNI CES services

23-MD75

BTS1

21-CQ1-1

NE 1

21-CQ1-2

BSC

35-MD75 TDM link BTS2 NOTE

This topic considers the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product.

7.3.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. A UNI-UNI CES service is generally configured to implement access of base station services and transmission of base station services to the BSC. As shown in Figure 7-5, two CES services are configured between the two BTSs and the BSC in this example. Table 7-3 lists the planned parameters of NE1 and their values. Table 7-3 UNI-UNI CES parameters (NE1)

Issue 03 (2013-02-20)

Parameter

Value

NE

NE1

NE1

Service ID

1

2


266



Parameter

Value

Service Name

CES1

CES2

Level

E1

E1

Mode

UNI-UNI

UNI-UNI

Source Board

23-MD75

35-MD75

Source High Channel

-

-

Source Low Channel

1

1

Source 64K Timeslot

-

-

Sink Board

21-CQ1-1

21-CQ1-2

Sink High Channel

VC4-1

VC4-1

Sink Low Channel

1

1

Sink 64K Timeslot

-

-

7.3.3 Configuration Process This topic describes how to configure UNI-UNI CES services on a per-NE basis.

Prerequisites l


l

You must be familiar with the service requirements and service planning information of the example network.

l

The network must be created, the equipment must operate properly, and the equipment must communicate with the NMS normally.

Procedure Step 1 Configure the channelized STM-1 ports, including the BTS-side PDH port and BSC-side channelized STM-1 port. 1.

Configure the BTS-side PDH port. a.

In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree. Then, configure the BTS-side port.

b.

Select 23-N1MD75-(E1-1) and 35-N1MD75-(E1-1), and set associated parameters according to the actual requirements. Table 7-4 BTS-side port

Issue 03 (2013-02-20)

Parameter


Port

23-N1MD75-(E1-1) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

35-N1MD75-(E1-1) 267


c. 2.


Parameter


Name

port1

port2

Port Mode

Layer 1

Layer 1

Frame Format

Unframe

Unframe

Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close.

Configure the BSC-side channelized STM-1 port. a.

In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree. Then, configure the BSC-side port.

b.

Select 21-CQ1-1(PORT-1) and 21-CQ1-2(PORT-2), and set associated parameters according to the actual requirements. Table 7-5 BSC-side port

c.

Parameter


Port

21-CQ1-1(PORT-1)

21-CQ1-2(PORT-2)

Name

port1

port2

Laser Interface Enabling Status

Open

Open

Frame Format

Unframe

Unframe


Step 2 Create the CES1 service. 1.

In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > CES Service Configuration from the Function Tree.

2.

Click New. Set the parameters of CES1 according to the service planning information. Table 7-6 CES1 service parameters

Issue 03 (2013-02-20)

Parameter


Service ID

1

Service Name

CES1

Level

E1

Mode

UNI-UNI

Source Board

23-N1MD75

Source High Channel

-


268


3.


Parameter


Source Low Channel

1

Source 64K Timeslot

-

Sink Board

21-CQ1-1(PORT1-1)

Sink High Channel

VC4-1

Sink Low Channel

1

Sink 64K Timeslot

-


Step 3 Create the CES2 service. 1.

In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > CES Service Configuration from the Function Tree.

2.

Click New. Set the parameters of CES2 according to the service planning information. Table 7-7 CES2 service parameters

3.

Parameter


Service ID

2

Service Name

CES2

Level

E1

Mode

UNI-UNI

Source Board

35-N1MD75

Source High Channel

-

Source Low Channel

1

Source 64K Timeslot

-

Sink Board

21-CQ1-2(PORT1-2)

Sink High Channel

VC4-1

Sink Low Channel

1

Sink 64K Timeslot

-


----End

Issue 03 (2013-02-20)


269



7.4 Configuration Example (UNI-NNI CES Services) This topic uses an example to describe how to configure UNI-NNI CES services.

7.4.1 Networking Diagram This topic describes the networking diagram of UNI-NNI CES services. As shown in Figure 7-6, the service requirements on the network are as follows: l

BTS1, BTS2, and the BSC need to access the PSN through CES boards.

l

BTS1 and BTS2 need to communicate with the BSC. The services on BTS1 and BTS2 need to be isolated from each other.

l

One E1 service from BTS1 and one E1 service from BTS2 need to be transmitted through the 19-MD75 on NE1 to the PSN.

l

E1 services from the BSC need also be transmitted through the 21-CQ1 board on NE1 to the PSN.

Figure 7-6 Networking diagram of UNI-NNI CES services 19-MD75 NE1

3-PEG8-1 3-PEG8-2

BTS1

21-CQ1-1

NE3 PSN BSC 21-CQ1-2 3-PEG8-1 NE 2 19-MD75

3-PEG8-1

BTS2

TDM link PW Tunnel

NOTE

l This section uses the OptiX OSN 3500 as an example to describe the board layout. The methods of configuring other products are the same as the method of configuring the OptiX OSN 3500, except that the board layout may be different. For the slot information, see the Hardware Description of the specific product. l On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. For details on how to configure transit NEs for CES services, see 9.14 Configuring Transit NEs for CES Services.

Issue 03 (2013-02-20)


270



7.4.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data, including the information for planning NNI ports, MPLS tunnels, and services. The OptiX OSN NEs access customer TDM services through TDM ports or channelized STM-1 ports. CES PWs are created between the OptiX OSN NEs to emulate end-to-end TDM services, therefore implementing service transmission between the BTSs and the BSC. Figure 7-6 shows an example network.

Planning NE Parameters Table 7-8 Planning information of NE parameters (NE1, NE2, and NE3) NE

LSR ID

Port

Port IP Address

IP Mask

NE1

130.0.0.1

3-PEG8-1 (PORT-1)

18.0.2.2

255.255.255.25 2

NE2

130.0.0.2

3-PEG8-1 (PORT-1)

18.0.1.1

255.255.255.25 2

NE3

130.0.0.3

3-PEG8-1 (PORT-1)

18.0.2.1

255.255.255.25 2

3-PEG8-2 (PORT-2)

18.0.1.2

255.255.255.25 2

Planning the Tunnel Between NE1 and NE3 Table 7-9 Planning information of tunnel parameters (tunnel between NE1 and NE3)

Issue 03 (2013-02-20)

Parameter

NE1

Tunnel ID

1

2

2

1

Tunnel Name

NE1-NE3#1

NE3-NE1#1

NE3-NE1#1

NE1-NE3#1

Node Type

Ingress

Egress

Ingress

Egress

Bandwidth (kbit/s)

100 Mbit/s

-

100 Mbit/s

-

In Board/Logic Interface Type

-

3-PEG8

-

3-PEG8

In Port

-

1

-

1

In Label

-

17

-

16

Out Board/ Logic Interface Type

3-PEG8

-

3-PEG8

-

NE3


271



Parameter

NE1

NE3

Out Port

1

-

1

-

Out Label

16

-

17

-

Next Hop Address

18.0.2.1

-

18.0.2.2

-

Source Node

-

130.0.0.3

-

130.0.0.1

Sink Node

130.0.0.3

-

130.0.0.1

-

Planning the Tunnel Between NE2 and NE3 Table 7-10 Planning information of tunnel parameters (tunnel between NE2 and NE3)

Issue 03 (2013-02-20)

Parameter

NE2

NE3

Tunnel ID

3

4

4

3

Tunnel Name

NE2-NE3#1

NE3-NE2#1

NE3-NE2#1

NE2-NE3#1

Node Type

Ingress

Egress

Ingress

Egress

Bandwidth (kbit/s)

100 Mbit/s

-

100 Mbit/s

-


-

3-PEG8

-

3-PEG8

In Port

-

1

-

2

In Label

-

19

-

18


3-PEG8

-

3-PEG8

-

Out Port

1

-

2

-

Out Label

18

-

19

-

Next Hop Address

18.0.1.2

-

18.0.1.1

-

Source Node

-

130.0.0.3

-

130.0.0.2

Sink Node

130.0.0.3

-

130.0.0.2

-


272



Planning the CES Service from BTS1 to the BSC Table 7-11 Planning information of the service parameters (UNI-NNI CES service between NE1 and NE3)

Issue 03 (2013-02-20)

Parameter

Value

NE

NE1

NE3

Service ID

1

1

Service Name

CES1

CES1

Level

E1

E1

Mode

UNI-NNI

UNI-NNI

Source Board

19-MD75

21-CQ1-1

Source High Channel

-

VC4-1

Source Low Channel

1

1

Source 64K Timeslot

1-31

1-31

Priority

EF

EF

PW ID

1

1

PW Signaling Type

Static

Static

PW Type

CESoPSN

CESoPSN


20

20


20

20

Tunnel Type

MPLS

MPLS

Tunnel No.

NE1-NE3#1

NE2-NE1#1

Peer LSR ID

130.0.0.3

130.0.0.1

RTP Head

Disabled

Disabled

Jitter Compensation Buffering Time(us)

8000

8000

Packet Loading Time(us)

1000

1000

Ingress Clock Mode

-

-

Egress Clock Mode

-

-

Enable CES Service Alarm Transparent Transmission

Enable

Enable


273



Parameter

Value

Threshold of Entering R Bit Inserting Status

100

100

Threshold of Exiting R Bit Inserting Status

5

5

Sequence Number Mode

Huawei Mode

Huawei Mode

Planning the CES Service from BTS2 to the BSC Table 7-12 Planning information of the service parameters (UNI-NNI CES service between NE2 and NE3)

Issue 03 (2013-02-20)

Parameter

Value

NE

NE2

NE3

Service ID

2

2

Service Name

CES2

CES2

Level

E1

E1

Mode

UNI-NNI

UNI-NNI

Source Board

19-MD75

21-CQ1-2

Source High Channel

-

VC4-1

Source Low Channel

1

1

Source 64K Timeslot

1-31

1-31

Priority

EF

EF

PW ID

2

2

PW Signaling Type

Static

Static

PW Type

CESoPSN

CESoPSN

PW Ingress Label

21

21

PW Egress Label

21

21

Tunnel Type

MPLS

MPLS

Tunnel

NE2-NE3#1

NE3-NE2#1

Peer LSR ID

130.0.0.3

130.0.0.2

RTP Head

Disabled

Disabled


8000

8000


274



Parameter

Value


1000

1000

Ingress Clock Mode

-

-

Egress Clock Mode

-

-


Enable

Enable


100

100


5

5


Huawei Mode

Huawei Mode

7.4.3 Configuration Process (Configuration on a Per-NE Basis) This topic describes how to configure UNI-NNI CES services on a per-NE basis.

Prerequisites l


l


l


l

The clocks must be configured for the NE that receives the CES service. For details on how to configure clocks, see Configuring Clocks.

Procedure Step 1 Configure the LSR IDs of NE1, NE2, and NE3. For details, see 9.4.1 Configuring LSR ID. Table 7-13 Planning information of NE parameters (NE1, NE2, and NE3) NE

LSR ID

NE1

130.0.0.1

NE2

130.0.0.2

NE3

130.0.0.3

Step 2 Configure the NNI ports of NE1, NE2, and NE3 on the packet domain. 1.

Issue 03 (2013-02-20)

In the NE Explorer, select NE1, and then choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the NNI ports. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

275


2.


In the General Attributes tab, select 3-PEG8-1(PORT-1). Right-click the Port Mode filed, and select Layer 3. Set the parameters according to the actual requirements. Click Apply. Set the associated parameters as follows.

3.

Parameter

Value

Remarks

Port Enabled

Enabled

-

Port Mode

Layer 3

The port carries a tunnel.

Working Mode

AutoNegotiation

Set the working modes of the local port and opposite port to be the same.

Max Frame Length (byte)

1620

Set this parameter according to the length of data packets. All the received data packets that exceed the maximum frame length are discarded.

Select 3-PEG8-1(PORT-1) in the Layer 3 Attributes tab. Right-click the Enable Tunnel 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. Set the associated parameters as follows.

4.

Parameter

Value

Remarks

Enable Tunnel

Enabled

-

Specify IP

Manually

Manually indicates that you can set the IP address of the port.

IP Address

18.0.2.2

-

IP Mask

255.255.255.252

-

Navigate to the NE Explorer of NE2 and NE3 separately. Set the parameters associated with each port according to Step a to Step c. Set the basic attributes of each port to be the same as the basic attributes of NE1-3-PEG8-1 (PORT-1). Set the Layer 3 attributes of each port as follows. l NE2-3-PEG8-1(PORT-1) Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.1.1

IP Mask

255.255.255.252

l NE3-3-PEG8-2(PORT-2) Issue 03 (2013-02-20)


276



Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.1.2

IP Mask

255.255.255.252

l NE3-3-PEG8-1(PORT-1) Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.2.1

IP Mask

255.255.255.252

Step 3 Configure the MPLS tunnel between NE1 and NE3 and the MPLS tunnel between NE2 and NE3. For details, see 9.4.3.1 Configuring a Static and Unidirectional MPLS Tunnel in Endto-End Mode. Set the associated parameters as follows. Table 7-14 Planning information of tunnel parameters (tunnel between NE1 and NE3)

Issue 03 (2013-02-20)

Parameter

NE1

Tunnel ID

1

2

2

1

Tunnel Name

NE1-NE3#1

NE3-NE1#1

NE3-NE1#1

NE1-NE3#1

Node Type

Ingress

Egress

Ingress

Egress

PIR(kbit/s)

100 Mbit/s

-

100 Mbit/s

-


-

3-PEG8

-

3-PEG8

In Port

-

1

-

1

In Label

-

17

-

16


3-PEG8

-

3-PEG8

-

Out Port

1

-

1

-

Out Label

16

-

17

-

NE3


277



Parameter

NE1

NE3

Next Hop Address

18.0.2.1

-

18.0.2.2

-

Source Node

-

130.0.0.3

-

130.0.0.1

Sink Node

130.0.0.3

-

130.0.0.1

-

Table 7-15 Planning information of tunnel parameters (tunnel between NE2 and NE3) Parameter

NE2

NE3

Tunnel ID

3

4

4

3

Tunnel Name

NE2-NE3#1

NE3-NE2#1

NE3-NE2#1

NE2-NE3#1

Node Type

Ingress

Egress

Ingress

Egress

Bandwidth (kbit/s)

100 Mbit/s

-

100 Mbit/s

-


-

3-PEG8

-

3-PEG8

In Port

-

1

-

2

In Label

-

19

-

18


3-PEG8

-

3-PEG8

-

Out Port

1

-

2

-

Out Label

18

-

19

-

Next Hop Address

18.0.1.2

-

18.0.1.1

-

Source Node

-

130.0.0.3

-

130.0.0.2

Sink Node

130.0.0.3

-

130.0.0.2

-

Step 4 Configure the CES service ports on NE1, NE2, and NE3. For details, see 9.2.1 Configuring Channelized STM-1 Ports. Step 5 Configure the UNI-NNI CES service between NE1 and NE3 and the UNI-NNI CES service between NE2 and NE3. For details, see 9.13.2 Creating UNI-NNI CES Services on a Per-NE Basis. Set the associated parameters as follows.

Issue 03 (2013-02-20)


278



Table 7-16 Planning information of the service parameters (UNI-NNI CES service between NE1 and NE3)

Issue 03 (2013-02-20)

Parameter

Value

Station

NE1

NE3

Service ID

1

1

Service Name

CES1

CES1

Level

E1

E1

Mode

UNI-NNI

UNI-NNI

Source Board

19-MD75

21-CQ1-1

Source High Channel

-

VC4-1

Source Low Channel

1

1

Source 64K Timeslot

1-31

1-31

Priority

EF

EF

PW ID

1

1

PW Signaling Type

Static

Static

PW Type

CESoPSN

CESoPSN

PW Ingress Label

20

20

PW Egress Label

20

20

Tunnel Type

MPLS

MPLS

RTP Header

Disabled

Disabled


8000

8000


1000

1000

Ingress Clock Mode

-

-

Egress Clock Mode

-

-


Enabled

Enabled


100

100


5

5


Huawei Mode

Huawei Mode


279



Table 7-17 Planning information of the service parameters (UNI-NNI CES service between NE2 and NE3)

Issue 03 (2013-02-20)

Parameter

Value

Station

NE2

NE3

Service ID

2

2

Service Name

CES2

CES2

Level

E1

E1

Mode

UNI-NNI

UNI-NNI

Source Board

19-MD75

21-CQ1-2

Source High Channel

-

VC4-1

Source Low Channel

1

1

Source 64K Timeslot

1-31

1-31

Priority

EF

EF

PW ID

2

2

PW Signaling Type

Static

Static

PW Type

CESoPSN

CESoPSN


21

21


21

21

Tunnel Type

MPLS

MPLS

RTP Header

Disabled

Disabled


8000

8000


1000

1000

Ingress Clock Mode

-

-

Egress Clock Mode

-

-


Enabled

Enabled


100

100


5

5


Huawei Mode

Huawei Mode


280



----End

7.4.4 Configuration Process (in End-to-End Mode) This topic describes how to configure UNI-NNI CES services on a per-NE basis.

Prerequisites l


l


l


l

The clocks must be configured for the NE that receives the CES service. For details on how to configure clocks, see Configuring Clocks.

Procedure Step 1 Configure the LSR IDs of NE1, NE2, and NE3. For details, see 9.4.1 Configuring LSR ID. Table 7-18 Planning information of NE parameters (NE1, NE2, and NE3) NE

LSR ID

NE1

130.0.0.1

NE2

130.0.0.2

NE3

130.0.0.3

Step 2 Configure the NNI ports of NE1, NE2, and NE3 on the packet domain. 1.

In the NE Explorer, select NE1, and then choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Configure the NNI ports.

2.

In the General Attributes tab, select 3-PEG8-1(PORT-1). Right-click the Port Mode filed, and select Layer 3. Set the parameters according to the actual requirements. Click Apply. Set the associated parameters as follows.

Issue 03 (2013-02-20)

Parameter

Value

Remarks

Port Enabled

Enabled

-

Port Mode

Layer 3

The port carries a tunnel.

Working Mode

AutoNegotiation

Set the working modes of the local port and opposite port to be the same.


281


3.


Parameter

Value

Remarks

Max Frame Length (byte)

1620

Set this parameter according to the length of data packets. All the received data packets that exceed the maximum frame length are discarded.

Select 3-PEG8-1(PORT-1) in the Layer 3 Attributes tab. Right-click the Enable Tunnel 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. Set the associated parameters as follows.

4.

Parameter

Value

Remarks

Enable Tunnel

Enabled

-

Specify IP

Manually

Manually indicates that you can set the IP address of the port.

IP Address

18.0.2.2

-

IP Mask

255.255.255.252

-

Navigate to the NE Explorer of NE2 and NE3 separately. Set the parameters associated with each port according to Step a to Step c. Set the basic attributes of each port to be the same as the basic attributes of NE1-3-PEG8-1 (PORT-1). Set the Layer 3 attributes of each port as follows. l NE2-3-PEG8-1(PORT-1) Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.1.1

IP Mask

255.255.255.252

l NE3-3-PEG8-2(PORT-2)

Issue 03 (2013-02-20)

Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.1.2

IP Mask

255.255.255.252


282



l NE3-3-PEG8-1(PORT-1) Parameter

Value

Enable Tunnel

Enabled

Specify IP

Manually

IP Address

18.0.2.1

IP Mask

255.255.255.252

Step 3 Configure the MPLS tunnel between NE1 and NE3 and the MPLS tunnel between NE2 and NE3. For details, see 9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode. NOTE

This topic considers the MPLS tunnel between the NE1 and NE3 as an example. The operations for configuring the MPLS tunnel between NE2 and NE3 are similar to operations for configuring the MPLS tunnel between NE1 and NE3.

1.

Choose Service > Tunnel > Create Tunnel from the Main Menu.

2.

Set the basic information about the MPLS tunnel between NE1 and NE3.

3.

Parameter

Value

Tunnel Name

NE1-NE3

Protocol Type

MPLS

Signaling Type

Static CR

Create Reverse Tunnel

Selected

On the physical topology, double-click NE1 and NE3 to add them and set the corresponding NE roles. Parameter

Value

Auto-Calculate route

Deselected

NE Role

NE1: Ingress NE3: Egress

Issue 03 (2013-02-20)


283


4.


Parameter

Value

Deploy

Selected

Click Details and set the advanced parameters of the forward and reverse MPLS tunnels between NE1 and NE3. Parameter

Value

Tunnel ID

Forward Tunnel: 1 Reverse Tunnel: 2

CIR(kbit/s)

Forward and Reverse Tunnels: 100000

LSP Type

Forward and Reverse Tunnels: E-LSP

EXP

Forward and Reverse Tunnels: None

Out Interface

Forward Tunnel: l NE1: 3-PEG8-1 l NE3: Reverse Tunnel: l NE3:3-PEG8-1 l NE1: -

Out Label

Forward Tunnel: l NE1: 16 l NE3: Reverse Tunnel: l NE3: 17 l NE1: -

In Interface

Forward Tunnel: l NE1: l NE3: 3-PEG8-1 Reverse Tunnel: l NE3: l NE1: 3-PEG8-1

In Label

Forward Tunnel: l NE1: l NE3: 16 Reverse Tunnel: l NE3: l NE1: 17

Issue 03 (2013-02-20)


284



Parameter

Value

Next Hop

Forward Tunnel: l NE1: 18.0.2.1 l NE3: Reverse Tunnel: l NE3: 18.0.2.2 l NE1: -

5.

Refer to Steps Step 3.1 to Step 3.4 and configure the MPLS tunnel between NE2 and NE3. Parameter

Value

Tunnel Name

NE2-NE3

Protocol Type

MPLS

Signaling Type

Static CR


Selected

Auto-Calculate route

Deselected

NE Role

NE2: Ingress NE3: Egress

Deploy

Selected

Tunnel ID

Forward Tunnel: 3 Reverse Tunnel: 4

CIR(kbit/s)


LSP Type


EXP


Out Interface

Forward Tunnel: l NE2: 3-PEG8-1 l NE3: Reverse Tunnel: l NE3: 3-PEG8-2 l NE2: -

Out Label

Forward Tunnel: l NE1: 18 l NE3: Reverse Tunnel: l NE3: 18 l NE1: -

Issue 03 (2013-02-20)


285



Parameter

Value

In Interface

Forward Tunnel: l NE1: l NE3: 3-PEG8-2 Reverse Tunnel: l NE3: l NE1: 3-PEG8-1 Positive Tunnel

In Label

l NE1: l NE3: 19 Reverse Tunnel: l NE3: l NE1: 19 Next Hop

Forward Tunnel: l NE1: 18.0.1.2 l NE3: Reverse Tunnel: l NE3: 18.0.1.1 l NE1: -

Step 4 Configure the CES service ports on NE1, NE2, and NE3. For details, see 9.2.1 Configuring Channelized STM-1 Ports. Step 5 Configure the CES service between NE1 and NE3. For details, see 9.13.3 Creating a CES Service in End-to-End Mode. 1.


2.

Set the basic attributes. Parameter

Value

Service Type

CES

Service ID

1

Service Name

CES1

Protection Type

No Protection

3.

Click Configure Source And Sink. Then, the Configure Source And Sink dialog box is displayed.

4.

Select NE1 as the source NE from Physical Topology on the left. Set the associated parameters and then click OK.

Issue 03 (2013-02-20)


286


5.

6.

7.

Issue 03 (2013-02-20)


Parameter

Value

Board

19-MD75

Port

-

High TimeSlot

-

Low TimeSlot

1

Channelized

Deselected

Select NE3 as the sink NE from Physical Topology on the left. Set the associated parameters and then click OK. Parameter

Value

Board

21-CQ1

Port

1

High TimeSlot

1

Low TimeSlot

1

Channelized

Deselected

64K Timeslot

1-31

Under PW, set the associated parameters. Parameter

Value

Forward Tunnel

NE1-NE3

Reverse Tunnel

NE3-NE1

PW ID

1

Forward Label

16

Reverse Label

16

Click Detail and then set the Advanced PW Parameters. Parameter

Value

Control Word

Use

Control Channel Type

CW

VCCV Verification Mode

Ping

RTP Header

Disabled


8000


287



Parameter

Value


1000


Huawei Mode

Step 6 Configure the CES service between NE2 and NE3. For details, see 9.13.3 Creating a CES Service in End-to-End Mode. 1.


2.

Set the basic attributes. Parameter

Value

Service Type

CES

Service ID

2

Service Name

CES2

Protection Type

Unprotected

3.


4.

Select NE2 as the source NE from Physical Topology on the left. Set the associated parameters and then click OK.

5.

Issue 03 (2013-02-20)

Parameter

Value

Board

19-MD75

Port

-

High TimeSlot

-

Low TimeSlot

1

Channelized

Selected

Select NE3 as the sink NE from Physical Topology on the left. Set the associated parameters and then click OK. Parameter

Value

Board

21-CQ1

Port

2

High TimeSlot

1

Low TimeSlot

1

Channelized

Selected

64K Timeslot

1-31


288


6.

7.


Under PW, set the associated parameters. Parameter

Value

Forward Tunnel

NE2-NE3

Reverse Tunnel

NE3-NE2

PW ID

1

Forward Label

17

Reverse Label

17

Click Detail and then set the Advanced PW Parameters. Parameter

Value

Control Character

Use


CW


Ping

RTP Header

Disabled


8000


1000


Huawei Mode

----End

7.5 Verifying CES Service Configuration After configuring a CES service, you need to verify whether the service configuration is correct.

Prerequisites l


l

CES services must be configured as required. For details, see 7 Configuring CES Services in the Configuration Guide.

Tools, Equipment, and Materials BER tester or SDH analyzer, the U2000

Test Connection Diagram Figure 7-7 shows the connection diagram for testing connectivity of CES service. You can replace the SDH analyzer with a BER tester. Issue 03 (2013-02-20)


289



Figure 7-7 Connection diagram for testing connectivity of CES services Packet domain

Inloop

DDF NE1

NE2

Tx Rx

SDH analyzer

WARNING l Only commissioning engineers are present during the test. l Do not touch the cable, unless necessary.

Procedure Step 1 As shown in Figure 7-7, connect the CES service interface on NE1 to the BER tester. Step 2 Perform an inloop for the UNI that receives CES services on NE2 on the U2000. 1.

In the Main Topology of the U2000, right-click the required NE and then choose NE Explorer from the shortcut menu. The NE Explorer window is displayed.

2.

Select the board that provides CES services.

3.

In the Function Tree, select the type of the interface that receives the CES services. If an E1 interface receives the CES services, choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree. If an SDH interface receives the CES services, choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree.

4.

Click the Advanced Attributes tab and then select the interface to perform a loopback.

5.

Right-click the Loopback Mode field, and then choose Inloop from the shortcut menu.

6.

Click Apply.

Step 3 Perform a 24-hour bit error test.

Issue 03 (2013-02-20)


290



NOTE

Set the coding to HDB3 and pseudo-random binary sequence (PRBS) to 2 15-1 for the signals transmitted by the BER tester. Set the BER tester according to the encapsulation method that the CES services adopt and the frame format that the E1 interface adopts. Set the timeslots on the BER tester consistently with the CES service timeslots. l If the CES services adopt the SATop method, you need to enable the BER tester to transmit unframed signals, double-frame signals, or CRC-4 multiframe signals. l If the CES services adopt the CESoPSN method and the interface adopts the double-frame format, you need to enable the BER tester to transmit double-frame signals. l If the CES services adopt the CESoPSN method and the interface adopts the CRC-4 multiframe format, you need to enable the BER tester to transmit CRC-4 multiframe signals.

Step 4 Test the performance of the CES services. That is, check whether bit errors occur in the CES services in the 24-hour period. Step 5 Check for the alarms associated with the CES services. If there is any, see the Alarms and Performance Events Reference and Troubleshooting to clear the alarms. Step 6 Repeat Step 3 to Step 4 to perform the 24-hour bit error test again. Step 7 Release the inloop that is set on the interface on NE2. For details, see Step 2. Step 8 Reconnect the cable to the CES service interface on NE1. Step 9 Repeat Step 1 to Step 8 to test the CES services on all the other 2 Mbit/s interfaces on NE1 and NE2. Step 10 Repeat Step 1 to Step 9 to test connectivity of the CES services on the other NEs. ----End

Issue 03 (2013-02-20)


291


8

8 Configuring ATM Services

Configuring ATM Services

About This Chapter This section describes how to configure ATM services. NOTE

This section describes how to configure ATM services on the OptiX OSN 7500 II. Procedures for configuring ATM services on other OptiX equipment are similar. The only difference lies in that associated boards may be housed in different slots on different devices. For slots valid for the boards that a product supports, see the Hardware Description of the product.

8.1 Introduction to ATM This section provides the definition of ATM PWE3 and describes its purpose. 8.2 Configuration Flow for the ATM Services This section describes the configuration flows for UNI-UNI ATM services and UNIs-NNI ATM services. 8.3 Configuration Example (UNI-UNI ATM Services) This section uses an example to describe how to plan and configure UNI-UNI ATM services according to network conditions. 8.4 Configuration Example (UNIs-NNI ATM Services) This section uses an example to describe how to plan and configure UNIs-NNI ATM services according to network conditions. 8.5 Verifying ATM Service Configuration Use the ATM OAM function to test the connectivity of UNIs-NNI ATM services to ensure that the ATM services are transmitted normally. This section describes how to test the connectivity of ATM services by performing a loopback (LB) test.

Issue 03 (2013-02-20)


292



8.1 Introduction to ATM This section provides the definition of ATM PWE3 and describes its purpose.

Definition The ATM PWE3 technology emulates the basic behaviors and characteristics of ATM services on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated ATM services can be transmitted on a PSN.

Purpose Aided by the ATM PWE3 technology, conventional ATM networks can be connected by a PSN. Specifically, ATM PWE3 allows transmitting conventional ATM services over a PSN by emulating the ATM services. The networking type of ATM PWE3 can be one-to-one, N-to-one or ATM-TRANS depending on the encapsulation type of ATM PWE3 packets. It is obvious that ATM PWE3 helps to transmit ATM services over the PSN, without adding ATM equipment or changing the configuration of the ATM CE equipment. Figure 8-1 Typical application of ATM PWE3 (in the one-to-one encapsulation mode) PSN PW AC

AC CE1

PE1

LSP

PE2

CE2

ATM PWE3 1-to-1 ATM PWE3 service

Packet transmission equipment

Issue 03 (2013-02-20)

1-to-1 ATM PWE3 service

NodeB


RNC

293



Figure 8-2 Typical application of ATM PWE3 (in the N-to-one encapsulation mode)

CE1 PSN PW AC

AC CE2

PE1

LSP

PE2

CE4

ATM PWE3 N-to-1 ATM PWE3 service

CE3

Packet transmission equipment

N-to-1 ATM PWE3 service

NodeB

RNC

NOTE

The cell encapsulation modes at both ends of a PW must be the same.

8.2 Configuration Flow for the ATM Services This section describes the configuration flows for UNI-UNI ATM services and UNIs-NNI ATM services.

8.2.1 Configuration Flow for UNI-UNI ATM Services This section describes the operation tasks for configuring UNI-UNI ATM services and the relationships between the operations tasks. Figure 8-3 shows the flow for configuring UNI-UNI ATM services.

Issue 03 (2013-02-20)


294



Figure 8-3 Configuration flow for UNI-UNI ATM services Start Required 1. Create the network.

2. Configure ATM policies.

3. Configure ATM ports.

4. Configure UNI-UNI ATM services.

End

Table 8-1 Configuration flow for UNI-UNI ATM services Step

Operation

Remarks

1


Create NEs, configure NE data, and create optical fibers.

2

Configuring ATM policies

The ATM policies are configured for ATM traffic management. For details, see Creating the ATM Policy.

3

Configuring ATM ports

The ATM ports are configured for receiving services from base stations. For details, see 9.15.1 Configuring ATM Interfaces.

4

Configuring UNIUNI ATM services

Set the service ID, service name, and connection type, and configure connections. For details, see 9.15.5 Creating ATM Services on a Per-NE Basis.

8.2.2 Configuration Flow for UNIs-NNI ATM Services This section describes the operation tasks for configuring UNIs-NNI ATM services and the relationships between the operations tasks. Figure 8-4 shows the flow for configuring UNIs-NNI ATM services.

Issue 03 (2013-02-20)


295



Figure 8-4 Configuration flow for UNIs-NNI ATM services Start Required 1. Create the network.

2. Configure the LSR ID.

3. Configure the NNI ports.

4. Configure MPLS tunnels.

5. Configure ATM policies.

6. Configure ATM ports.

7. Configure UNIs-NNI ATM services.

End

Table 8-2 Configuration flow for UNIs-NNI ATM services Step

Operation

Remarks

1


Create NEs, configure NE data, and create optical fibers.

2

Configuring the LSR ID

-

3

Configuring the NNI ports

l Set the general attributes of Ethernet ports.

Config uring MPLS tunnel s


4

Issue 03 (2013-02-20)

Configu ring an MPLS tunnel

l Set the Layer 3 attributes of Ethernet ports, including the tunnel enabled status and IP address.


296


Step

Operation Configu ring MPLS OAM


Remarks (Optional) The parameters are set as follows: l OAM Status is set to Enabled. l Detection Mode is set to Manual. l Detection Packet Type is set to FFD. l Detection Packet Period(ms) is set to 3.3.

Configu ring MPLS tunnel APS 5

Configuring ATM policies

(Optional) Set the MPLS tunnel APS parameters according to the service planning information. For details on how to manage MPLS tunnel APS protection groups, see 9.8 Managing MPLS Tunnel APS Protection Groups. The ATM policies are configured for ATM traffic management. l For details about configuring ATM policy in per-NE mode, see Creating the ATM Policy. l For details about configuring ATM policy profile in end-toend mode, see 9.15.2 Configuring an ATM Policy Profile.

6

Configuring ATM ports

The ATM ports are configured for receiving services from base stations. For details, see 9.15.1 Configuring ATM Interfaces.

7

Configuring UNIs-NNI ATM services

1. Create CES services, that is, set the service ID, service name, service type, and connection type. 2. Configure ATM connections, that is, set the source information, PW ID, sink information, and policies. 3. Configure PWs, that is, set information such as the PW type, PW label, and tunnel type. 4. Configure CoS mappings, that is, set the CoS policy for PWs. l For details about configuring UNIs-NNI ATM services in per-NE mode, see 9.15.5 Creating ATM Services on a PerNE Basis. l For details about configuring UNIs-NNI ATM services in end-to-end mode, see 9.15.4 Creating an ATM Service by Using the Trail Function.

8.3 Configuration Example (UNI-UNI ATM Services) This section uses an example to describe how to plan and configure UNI-UNI ATM services according to network conditions.

8.3.1 Network Diagram This section describes the networking information about the example where R99 services, signaling services, and HSDPA services are transported between a NodeB and an RNC. Issue 03 (2013-02-20)


297



Figure 8-5 shows a network diagram of UNI-UNI ATM services. ATM services are required between the NodeB and the RNC. Connection 1 is used for transmitting R99 services, connection 2 is used for transmitting HSDPA services, and connection 3 is used for transmitting signaling services. The NodeB transmits services to the RNC through NE1. NE1 uses the OptiX OSN 7500 II to receive the services from the NodeB, and transmits the services to the RNC through STM-1. Figure 8-5 Network diagram of UNI-UNI ATM services UNI VCI 100 101 102

VPI 1 1 1

Connection 1 R99 Connection 2 HSDPA Connection 3 Signaling

UNI VPI 70 71 72

IMA 1

Node B

VCI 32 32 32

STM-1

NE 1

RNC

Figure 8-6 NE planning diagram UNI

UNI

35-N1D12E

32-N1AFO1

IMA 1 Node B

STM-1 NE 1

RNC

8.3.2 Service Planning To transport the R99 services, signaling services, and HSDPA services between the NodeB and the RNC, three ATM connections need to be created. The NodeB receives the ATM services through IMA1, and then transmits the services to the RNC. N:1 VCC ATM services containing three connections need to be created. Figure 8-5 shows VPI/VCI switching. The network shown in Figure 8-5 is taken as an example. Table 8-3 lists the parameters planned for NE1. Table 8-3 Parameters planned for NE1

Issue 03 (2013-02-20)

Attribute

Description

Base Station of Service

NodeB


298



Attribute

Description

IMA Group

IMA1

Port Accessing the IMA Group at NodeB

NE1-35-N1D12E-1

Port Connected to RNC

NE1-32-N1AFO1-1

Conn ection 1

Source VPI/VCI

1/100

Sink VPI/VCI

70/32

Conn ection 2

Source VPI/VCI

1/101

Sink VPI/VCI

71/32

Conn ection 3

Source VPI/VCI

1/102

Sink VPI/VCI

72/32

Table 8-4 lists the QoS policies planned for the ATM services. Table 8-4 Service categories and QoS requirements Service Category

ATM Policy

PW Bandwidth

Tunnel Bandwidth

Audio service, which is carried by RTVBR

l Policy ID: 1

4 Mbit/s

30 Mbit/s

l Policy name: RTVBR l Service category: 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 Frame Discarding Flag: Disable l UPC/NPC: Disable

Issue 03 (2013-02-20)


299



Service Category

ATM Policy

PW Bandwidth

Signaling service, which is carried by CBR

l Policy ID: 2

1 Mbit/s

Tunnel Bandwidth

l Policy name: CBR l Service category: CBR l Traffic type: NoClpNoScr l Clp01Pcr(cell/s): 800 l Enable Traffic Frame Discarding Flag: Disable l UPC/NPC: Disable

Data service, which is carried by UBR

l Policy ID: 3

15 Mbit/s

l Policy name: UBR l Service category: UBR l Traffic type: NoTrafficDescriptor l Enable Traffic Frame Discarding Flag: Disable l UPC/NPC: Disable

8.3.3 Configuring an ATM Service on a Per-NE Basis This section describes the process of configuring a UNI-UNI ATM service on a per-NE basis.

Prerequisites l

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

l

You must understand the networking, requirements and service planning of the example.

l

A network must be created.

Procedure Step 1 Configure three ATM policies: CBR, RT-VBR, and UBR. Issue 03 (2013-02-20)


300



1.

Configure the CBR policy. For details, see QoS Configuration Example of the ATM Service 2.

2.

Configure the RT-VBR policy. For details, see QoS Configuration Example of the ATM Service 1.

3.

Configure the UBR policy. For details, see QoS Configuration Example of the ATM Service 3.

Step 2 Configure ATM ports, including NodeB-side ATM ports and RNC-side ATM ports. 1.

Configure NodeB-side ATM ports. a.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree to configure NodeB-side ATM ports.

b.

Select 35-N1D12E-1(PORT-1) and 35-N1D12E-2(PORT-2). Right-click the Port Mode field, and select Layer 2. Set the parameters as required, and click Apply. NOTE

Before setting the port mode, make sure that the port DCN is disabled.

Set relevant parameters as follows: l Port: 35-N1D12E-1(PORT-1), 35-N1D12E-2(PORT-2) l Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) l Port Mode: Layer 2 (The port transmits IMA signals.) l Encapsulation: ATM (default) c.

In the Advanced Attributes tab, set Frame Format and Frame Mode for ports 35N1D12E-1(PORT-1) and 35-N1D12E-2(PORT-2). Click Apply. Set relevant parameters as follows: l Port: 35-N1D12E-1(PORT-1) and 35-N1D12E-2(PORT-2) l Frame Format: CRC-4 Multiframe (Set this parameter to the value same as that of the NodeB.) l Frame Mode: 31

d.

Choose Configuration > Packet Configuration > Interface Management > ATM IMA Management from the Function Tree. Then, click the Binding tab.

e.

In the Binding tab, click Configuration and set the parameters such as Available Boards and Configuration Ports. Then, click OK. Set relevant parameters as follows: l Available Boards: 35-N1D12E (Set this parameter according to the networking plan.) l Configuration Ports: 35-N1D12E-1(PORT-1) (Set this parameter according to the networking plan.) l Available Bound Paths – Level: E1 (Select E1 for an ATM E1 board.) – Direction: Bidirectional (default) – Optical Interface: - (This parameter need not be set for E1.) l Available Resources: 35-N1D12E-1(PORT-1) and 35-N1D12E-2(PORT-2) l Available Timeslots: - (This parameter need not be set for E1.)

Issue 03 (2013-02-20)


301


f.


In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. Set relevant parameters as follows: Set the IMA Protocol Version, IMA Transmit Frame Length, IMA Symmetry Mode, Maximum Delay Between Links, Minimum Number of Active Transmitting Links, and Minimum Number of Active Receiving Links parameters the same as those of the NodeB.

g.

In the ATM Interface Management tab, set the parameters such as Max. VPI and Max. VCI for the port. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI (A UNI port is connected to the client-side equipment and an NNI port is connected to the ATM equipment on a core network.) l ATM Cell Payload Scrambling: Enabled l Loopback: Non-Loopback

2.

Configure RNC-side ATM ports. a.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree to configure RNC-side ATM ports.

b.

In the Layer 2 Attributes tab, select 32-N1AFO1-1(PORT-1), and set the parameters such as Max. VPI and Max. VCI for the port. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI l ATM Cell Payload Scrambling: Enabled l Max. VPI: 255 l Max. VCI: 127 l VCC-Supported VPI Count: 32

Step 3 Configure a UNI-UNI ATM service and add three connections. 1.

Choose Configuration > Packet Configuration > ATM Service Management from the Function Tree.

2.

In the Connection tab, click New. The New ATM Service window is displayed. In the window, configure a UNI-UNI service. Set relevant parameters as follows: l Service ID: 10 l Service Name: ATMService-10 l Service Type: UNI-UNI l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be changed; PVP indicates that only the VPI of the ATM connection can be changed.)

3.

Click the Connection tab and click Add to add connection 1, connection 2, and connection 3. Then, click OK. Set relevant parameters as follows: l Connection 1

Issue 03 (2013-02-20)


302



– Connection Name: Connection 1 – Source Board: 35-N1D12E – Source Port: 1(PORT-1) – Source VPI: 1 (This parameter indicates the VPI information that is transmitted with the service from the NodeB.) – Source VCI: 100 (This parameter indicates the VCI information that is transmitted with the service from the NodeB.) – PW ID: – Sink Board: 32-N1AFO1 – Sink Port: 1(PORT-1) – Sink VPI: 70 (This parameter indicates the VPI information that is transmitted with the service after VPI switching. The sink VPI ranges from 0 to Max. VPI.) – Sink VCI: 32 (This parameter indicates The VCI information that is transmitted with the service after VCI switching. The sink VCI ranges from 32 to Max. VCI.) – Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) – Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) l Connection 2 – Connection Name: Connection 2 – Source Board: 35-N1D12E – Source Port: 1(PORT-1) – Source VPI: 1 – Source VCI: 101 – PW ID: – Sink Board: 32-N1AFO1 – Sink Port: 1(PORT-1) – Sink VPI: 71 – Sink VCI: 32 – Uplink Policy: UBR (Select the UBR policy, because connection 2 is an HSDPA service.) – Downlink Policy: UBR (Select the UBR policy, because connection 2 is an HSDPA service.) l Connection 3 – Connection Name: Connection 3 – Source Board: 35-N1D12E – Source Port: 1(PORT-1) – Source VPI: 1 – Source VCI: 102 – PW ID: – Sink Board: 32-N1AFO1 – Sink Port: 1(PORT-1) Issue 03 (2013-02-20)


303



– Sink VPI: 72 – Sink VCI: 32 – Uplink Policy: CBR (Select the CBR policy, because connection 3 is a signaling service.) – Downlink Policy: CBR (Select the CBR policy, because connection 3 is a signaling service.) ----End

8.4 Configuration Example (UNIs-NNI ATM Services) This section uses an example to describe how to plan and configure UNIs-NNI ATM services according to network conditions.

8.4.1 Network Diagram This section describes the networking information about the example where R99 services, signaling services, and HSDPA services are transported between NodeB1 and the RNC, and between NodeB2 and the RNC. Figure 8-7 shows a network diagram of UNIs-NNI ATM services. 3G R99 services, signaling services, and HSDPA services are required between NodeB1/NodeB2 and the RNC. NE1 accesses the MPLS network formed by Hybrid MSTP equipment. NodeB1 is connected to NE1 through IMA1, and NodeB2 is connected to NE1 through IMA2. VPI/VCI switching is performed on NE1, and VPI/VCI transparent transmission is performed on NE2 and NE3. Between NE1 and NE3, three PWs are used to carry the R99 services, signaling services, and HSDPA services, and one PW carries one category of service. At the remote end, to transparently transmit the ATM services on the MPLS network, NE3 is connected to the RNC through STM-1. NE1 and NE3 are OptiX OSN 7500 IIs, and NE2, NE4, NE5 and NE6 are OptiX OSN 3500s. The ATM services are carried by the working tunnel. The protection tunnel can be created to protect the services that have high real-time requirements. The working tunnel is NE1-NE2-NE3, and the protection tunnel is NE1-NE6-NE5-NE4-NE3.

Issue 03 (2013-02-20)


304



Figure 8-7 Network diagram of UNIs-NNI ATM services

NE5 GE ring on access layer

NE6

NE1

pw1 pw2

NE4

10GE ring on convergence layer

NE3 ATM STM-1

NE2 pw3

IMA1

IMA2

RNC Working Tunnel

NodeB 1

UNI IMA1:

Connection 1 Connection 2 Connection 3

R99 HSDPA Signalling

VPI 1 1 1

R99 HSDPA Signalling

VPI 1 1 1

IMA2:

Protection Tunnel

NNI

NNI

UNI

VCI 100 101 102

VPI

VCI

VPI

VCI

VPI

VCI

50

32

50

32

50

32

51 52

32 32

51 52

32 32

51 52

32 32

VCI 100 101 102

VPI

VCI

VPI

VCI

VPI

VCI

60

32

60

32

60

32

61 62

32 32

61 62

32 32

61 62

32 32

UNI Connection 1 Connection 2 Connection 3

PW

NodeB 2

NNI

UNI

NNI

Figure 8-8 shows the NE planning diagram. Figure 8-8 NE planning diagram 3-PEX2-1(PORT-1) 10.0.3.1 4-PEX2-2(PORT-2) 10.0.3.2

3-PEG8-1(PORT-1) 10.0.4.2

3-PEG8-2(PORT-2) 10.0.4.1

NE5 GE ring on access layer

NE6

3-EG8-2(PORT-2) 10.0.5.1

NE2 3-EG8-1(PORT-1) 10.0.0.1

10GE ring on convergence layer 3-EX2-2(PORT-2) 10.0.1.2

3-PEG8-2(PORT-2) 10.0.0.2 NE1

3-PEG8-1(PORT-1) 10.0.5.2

NE4

4-PEX2-1(PORT-1) 10.0.1.1

3-PEX2-2(PORT-2) 10.0.2.2

NE3

3-EX2-1(PORT-1) 10.0.2.1

32-AFO1-1(PORT-1)

35-D12E RNC Working Tunnel Protection Tunnel

NodeB 1 NodeB 2

Issue 03 (2013-02-20)


305



8.4.2 Service Planning To transport the R99 services, signaling services, and HSDPA services between NodeB1 and the RNC, between NodeB2 and the RNC, three ATM services need to be created. Between NE1 and NE3, the R99 services are carried by PW1, the HSDPA services are carried by PW2, and the signaling services are carried by PW3. Therefore, three ATM services need to be created. At NodeB1 and NodeB2, the R99 services are aggregated, and the signaling services and HSDPA services are received. Therefore, N:1 VCC ATM services containing two connections need to be created. The network shown in Figure 8-7 is taken as an example. Table 8-5 Parameters planned for the NEs NE

LSR ID

Port

Port IP Address

IP Mask

NE1

130.0.0.1

3-EG8-1 (PORT-1)

10.0.0.1

255.255.255.252

3-EG8-2 (PORT-2)

10.0.5.1

255.255.255.252

4-PEX2-1 (PORT-1)

10.0.1.1

255.255.255.252

3-PEG8-2 (PORT-2)

10.0.0.2

255.255.255.252

3-EX2-1 (PORT-1)

10.0.2.1

255.255.255.252

3-EX2-2 (PORT-2)

10.0.1.2

255.255.255.252

3-PEX2-2 (PORT-2)

10.0.2.2

255.255.255.252

3-PEX2-1 (PORT-1)

10.0.3.1

255.255.255.252

4-PEX2-2 (PORT-2)

10.0.3.2

255.255.255.252

3-PEG8-1 (PORT-1)

10.0.4.2

255.255.255.252

3-PEG8-2 (PORT-2)

10.0.4.1

255.255.255.252

3-PEG8-1 (PORT-1)

10.0.5.2

255.255.255.252

NE2

NE3

NE4

NE5

NE6

Issue 03 (2013-02-20)

130.0.0.2

130.0.0.3

130.0.0.4

130.0.0.5

130.0.0.6


306



Table 8-6 Parameters planned for tunnels

Issue 03 (2013-02-20)

Parameter

Working Tunnel

Protection Tunnel

Tunnel ID

100

101

120

121

Name

Working Tunnel-Positive

Working Tunnel-Reverse

Protection Tunnel-Positive

Protection Tunnel-Reverse

Signal Type

Static

Static

Static

Static

Scheduling Type

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 Node Route Information

NE1

NE3

NE1

NE3

l Out Port: 3EG8-1 (PORT-1)

l Out Port: 3EX2-2 (PORT-2)

l Out Port: 3EG8-2 (PORT-2)

l Out Port: 3EX2-1 (PORT-1)

l Out Label: 20

l Out Label: 21

l Out Label: 22

l Out Label: 23


307



Parameter

Working Tunnel

Protection Tunnel

Transit Node Route Information

NE2

NE2

NE6

NE4

l In Port: 3PEG8-2 (PORT-2)

l In Port: 4PEX2-1 (PORT-1)



l In Label: 20

l In Label: 21

l In Label: 22

l In Label: 23

l Out Port: 4PEX2-1 (PORT-1)

l Out Port: 3PEG8-2 (PORT-2)



l Out Label: 30

l Out Label: 31

l Out Label: 32

l Out Label: 33

NE5

NE5



l In Label: 32

l In Label: 33



l Out Label: 42

l Out Label: 43

NE4

NE6



l In Label: 42

l In Label: 43



l Out Label: 52

l Out Label: 53

Egress Node Route Information

NE3

NE1

NE3

NE1

l In Port: 3EX2-2 (PORT-2)

l In Port: 3EG8-1 (PORT-1)

l In Port: 3EX2-1 (PORT-1)

l In Port: 3EG8-2 (PORT-2)

l In Label: 30

l In Label: 31

l In Label: 52

l In Label: 53

Table 8-7 lists the parameters planned for NE1.

Issue 03 (2013-02-20)


308



Table 8-7 Parameters planned for NE1 Attribute

Description

Base Station of Service

NodeB1

NodeB2

IMA Group

IMA1

IMA2

Source Port

35-N1D12E-1(Port-1)

35-N1D12E-2(Port-2)

Service

R99

HSDPA

Signaling

R99

HSDPA

Signaling

Source VPI/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 of Service

PW1

PW2

PW3

PW1

PW2

PW3

PW ID

35

36

37

35

36

37

Table 8-8 lists the parameters planned for NE3. Table 8-8 Parameters planned for NE3 Attribute

Remarks

Service

R99

HSDPA

Signaling

R99

HSDPA

Signaling

Source VPI/VCI

50/32

51/32

52/32

60/32

61/32

62/32

Sink VPI/ VCI

50/32

51/32

52/32

60/32

61/32

62/32

PW of Service

PW1

PW2

PW3

PW1

PW2

PW3

PW ID

35

36

37

35

36

37

Sink Port

32-N1AFO1-1(PORT-1)

Description

Table 8-9 lists the QoS policies planned for the ATM services.

Issue 03 (2013-02-20)


309



Table 8-9 Service categories and QoS requirements Service Category

ATM Policy

Audio service, which is carried by RT-VBR

l Policy ID: 1 l Policy name: RT-VBR l Service category: 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 Frame Discarding Flag: Disable l UPC/NPC: Disable

Signaling service, which is carried by CBR

l Policy ID: 2 l Policy name: CBR l Service category: CBR l Traffic type: NoClpNoScr l Clp01Pcr(cell/s): 800 l Enable Traffic Frame Discarding Flag: Disable l UPC/NPC: Disable

Data service, which is carried by UBR

l Policy ID: 3 l Policy name: UBR l Service category: UBR l Traffic type: NoTrafficDescriptor l Enable Traffic Frame Discarding Flag: Disable l UPC/NPC: Disable

8.4.3 Configuration Process (in End-to-End Mode) This section describes how to configure an ATM service in end-to-end mode.

Prerequisites l


l

You must learn about the networking requirements and service plan described in the example.

l

A network must be created and the IP addresses of ports must be automatically allocated.

Issue 03 (2013-02-20)


310



Procedure Step 1 Set LSR IDs. 1.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > MPLS Management > Basic Configuration from the Function Tree.

2.

Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.

3.

Parameter

Example Value

Principle for Value Selection

LSR ID

NE1: 130.0.0.1

Set this parameter according to the networking plan. In addition, this value is unique on an entire network.

Start of Global Label Space

0

Set this parameter according to the networking plan.

Display the NE Explorers of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. Parameter

Example Value


LSR ID

NE2: 130.0.0.2


NE3: 130.0.0.3 NE4: 130.0.0.4 NE5: 130.0.0.5 NE6: 130.0.0.6 Start of Global Label Space

0


Step 2 Create the working tunnel. 1.


2.

Set the basic information about the working tunnel.

Issue 03 (2013-02-20)

Parameter

Example Value


Tunnel Name

Working Tunnel

Set this parameter according to the service plan.

Protocol Type

MPLS



311


3.


Parameter

Example Value


Signaling Type

Static CR


Service Direction

Unidirectional



Selected

This parameter is selected when a reverse tunnel needs to be created.

Protection Type

1+1


Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add them to the NE list and set the corresponding NE roles. Parameter

Example Value


NE Role

NE1: Ingress

An ingress is the incoming node of a network. In this example, NE1 is an ingress node.

NE2: Transit NE3: Egress

A transit is a pass-through node. In this example, NE2 is a transit node. An egress is the outgoing node of a network. In this example, NE3 is an egress node. Selected

Deploy

4.

Click Details to set the advanced parameters of the reverse tunnel. Click OK. Parameter

Example Value


Tunnel ID

l Forward Tunnel: 100


l Reverse Tunnel: 101

Issue 03 (2013-02-20)

When this parameter is selected, a tunnel is saved on the U2000 and applied to the corresponding NEs.


312



Parameter

Example Value


CIR(Kbit/s)



CBS(byte)



PIR(Kbit/s)



PBS(byte)



MTU (bytes)



LSP Type


Currently, this parameter can be set to E-LSP only.

EXP



Out Interface

Forward Tunnel:

Set this parameter according to the service plan. This parameter needs to be set for only ingress nodes and transit nodes.

l NE1: 3-EG8-1 (PORT-1) l NE2: 4-PEX2-1 (PORT-1) Reverse Tunnel: l NE3: 3-EX2-2 (PORT-2) l NE2: 3-PEG8-2 (PORT-2) Out Label

Forward Tunnel: l NE1: 20 l NE2: 30



Issue 03 (2013-02-20)


313



Parameter

Example Value


In Interface

Forward Tunnel:

Set this parameter according to the service plan. This parameter needs to be set for only egress nodes and transit nodes.

l NE2: 3-PEG8-2 (PORT-2) l NE3: 3-EX2-2 (PORT-2) Reverse Tunnel: l NE2: 4-PEX2-1 (PORT-1) l NE1: 3-EG8-1 (PORT-1) In Label



Reverse Tunnel: l NE2: 21 l NE1: 31 Next Hop

Forward Tunnel: l NE1: 10.0.0.2 l NE2: 10.0.1.2


Reverse Tunnel: l NE3: 10.0.1.1 l NE2: 10.0.0.1

Step 3 Create the protection tunnel. 1.

Create the protection tunnel by referring toStep 2 Set the basic Information as follows:

Issue 03 (2013-02-20)

Parameter

Example Value


Tunnel Name

Protection Tunnel


Protocol Type

MPLS


Signaling Type

Static CR



314



Parameter

Example Value


Service Direction

Unidirectional



Selected


Set the node information as follows: Parameter

Example Value


NE Role

NE1: Ingress


NE6, NE5, NE4: Transit NE3: Egress

A transit is a pass-through node. In this example, NE6, NE5, and NE4 are transit nodes. An egress is the outgoing node of a network. In this example, NE3 is an egress node. Selected

Deploy


Set the route information as follows: Parameter

Example Value


Tunnel ID



l Reverse Tunnel: 121 CIR(Kbit/s)

Issue 03 (2013-02-20)




315



Parameter

Example Value


CBS(byte)



PIR(Kbit/s)



PBS(byte)



MTU (bytes)



LSP Type



EXP



Out Interface

Forward Tunnel:


l NE1: 3-EG8-2 (PORT-2) l NE6: 3-PEG8-2 (PORT-2) l NE5: 4-PEX2-2 (PORT-2) l NE4: 3-PEX2-2 (PORT-2) Reverse Tunnel: l NE3: 3-EX2-1 (PORT-1) l NE4: 3-PEX2-1 (PORT-1) l NE5: 3-PEG8-1 (PORT-1) l NE6: 3-PEG8-1 (PORT-1)

Issue 03 (2013-02-20)


316



Parameter

Example Value


Out Label

Forward Tunnel:


l NE1: 22 l NE6: 32 l NE5: 42 l NE4: 52 Reverse Tunnel: l NE3: 23 l NE4: 33 l NE5: 43 l NE6: 53 In Interface

Forward Tunnel: l NE6: 3-PEG8-1 (PORT-1) l NE5: 3-PEG8-1 (PORT-1)


l NE4: 3-PEX2-1 (PORT-1) l NE3: 3-EX2-1 (PORT-1) Reverse Tunnel: l NE4: 3-PEX2-2 (PORT-2) l NE5: 4-PEX2-2 (PORT-2) l NE6: 3-PEG8-2 (PORT-2) l NE1: 3-EG8-2 (PORT-2) In Label



l NE4: 42 l NE3: 52 Reverse Tunnel: l NE4: 23 l NE5: 33 l NE6: 43 l NE1: 53

Issue 03 (2013-02-20)


317



Parameter

Example Value


Next Hop

Forward Tunnel:


l NE1: 10.0.5.2 l NE6: 10.0.4.2 l NE5: 10.0.3.1 l NE4: 10.0.2.1 Reverse Tunnel: l NE3: 10.0.2.2 l NE4: 10.0.3.2 l NE5: 10.0.4.1 l NE6: 10.0.2.1

Step 4 Configure ports, including NodeB-side ATM ports and RNC-side ATM ports. 1.


In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree to configure NodeB-side ports.

b.

Select the ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8), Right-click the Port Mode field, and select Layer 2. Set the parameters as required, and click Apply. NOTE


Set relevant parameters as follows: l Port: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8) l Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) l Port Mode: Layer 2 (The port transmits IMA signals.) l Encapsulation Type: ATM c.

In the Advanced tab, set Frame Format and Frame Mode for the ports from 35N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8). Click Apply. Set relevant parameters as follows: l Port: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8) l Frame Format: CRC-4 Multiframe (Set this parameter to the value same as that of the NodeB.) l Frame Mode: 31

d.


e.

In the Binding tab, click Configuration and set bound ports for 35-N1D12E-1 (PORT-1) and 35-N1D12E-2(PORT-2). Then, click OK. Set the parameters relevant to 35-N1D12E-1(PORT-1) as follows:

Issue 03 (2013-02-20)


318



l Available Boards: 35-N1D12E (Set this parameter according to the networking plan.) l Configurable Ports: 35-N1D12E-1(PORT-1) (Set this parameter according to the networking plan.) l Available Bound Paths – Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. For this example, the board is an ATM E1 board.) – Direction: Bidirectional (default) – Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. For this example, the path level is E1.) l Available Resources: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-4 (PORT-4) l Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) Set the parameters relevant to 35-N1D12E-2(PORT-2) as follows: l Available Boards: 35-N1D12E (Set this parameter according to the networking plan.) l Configurable Ports: 35-N1D12E-2(PORT-2) (Set this parameter according to the networking plan.) l Available Bound Paths – Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. For this example, the board is an ATM E1 board.) – Direction: Bidirectional (default) – Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. For this example, the path level is E1.) l Available Resources: ports from 35-N1D12E-1(PORT-5) to 35-N1D12E-4 (PORT-8) l Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. The settings of parameters need to be the same as those on the NodeB.

g.

In the ATM Interface Management tab, set the parameters such as Max. VPI and Max. VCI. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI (A UNI port is connected to the client-side equipment and an NNI port is connected to the ATM equipment on a core network.) l ATM Cell Payload Scrambling: Enabled l Loopback: No Loopback

2.


Issue 03 (2013-02-20)

In the NE Explorer, select NE3 and choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree to configure RNC-side ATM ports. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

319


b.


In the Layer 2 Attributes tab, select 32-N1AFO1-1(PORT-1) and set the parameters such as Max. VPI and Max. VCI for the port. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI (A UNI port is connected to the client-side equipment and an NNI port is connected to the ATM equipment on a core network.) l ATM Cell Payload Scrambling: Enabled l Max. VPI: 255 (Set this parameter according to the networking plan. Set Max. VPI to specify the value range of VPI. The VPI ranges from 0 to Max. VPI.) l Max. VCI: 127 (Set this parameter according to the networking plan. Set Max. VCI to specify the value range of VCI. The VCI ranges from 0 to Max. VCI.) l VCC-Supported VPI Count: 32 (Set this parameter according to the networking plan.)

Step 5 Create three UNIs-NNI ATM services. 1.

Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu. Create an R99 service from NE1 to NE3. Table 8-10 Parameters of general attributes

2.

Issue 03 (2013-02-20)

Parameter

Example Value


Service Type

ATM


Service ID

1

A service ID uniquely identifies a service on an entire network.

Service Name

ATMService-R99


Protection Type

Protection-free


Link Type

ATM N-to-1 VCC Cell Transport


Click Configure Source And Sink. A window is displayed. On the Physical Topology in the upper left portion of the window, set NE1 as the source NE and NE3 as the sink NE. Set relevant parameters and click OK.


320



Table 8-11 Parameters of the source node Parameter

Example Value


SAI Type

ATM


Table 8-12 Parameters of the sink node

3.

Parameter

Example Value


SAI Type

ATM


In PW in the lower left portion of the window, set relevant parameters. Table 8-13 PW parameters Parameter

Example Value


Forward Type

Static Binding

l If you set Forward Type to Static Binding, you need to manually specify a tunnel in the Forward Tunnel area. l If you set Reverse Type to Select Policy, you need to set a tunnel priority in the Reverse Tunnel area so that the system selects a tunnel according to the priority.

Forward Tunnel

Issue 03 (2013-02-20)

Tunnel-001



321



Parameter

Example Value


Reverse Type

Static Binding

l If you set Reverse Type to Static Binding, you need to manually specify a tunnel in the Reverse Tunnel area. l If you set Reverse Type to Select Policy, you need to set a tunnel priority in the Reverse Tunnel area so that the system selects a tunnel according to the priority.

4.

Reverse Tunnel

Tunnel-001_Reverse


PW ID

35

A PW ID uniquely identifies a PW on an entire network.

Signaling Type

Static

For a static PW, you need to set Forward Label and Reverse Label.

Encapsulation Type

MPLS


Click ATM Link. In the dialog box that is displayed, set the parameters relevant to the connection. Table 8-14 Parameters for configuring an ATM connection

Issue 03 (2013-02-20)

Parameter

Example Value


Connection Name

Connection1 and Connection2


Role

Working



322



Parameter

Example Value


Source SAI

Connection1: 35N1D12E-1(PORT-1)


Connection2: 35N1D12E-2(PORT-2) Source VPI

Connection1: 1 Connection2: 1

Source VCI


Source ATM Policy

Connection1: RT-VBR Connection2: RT-VBR

This parameter specifies the VPI information carried by the service from a base station. This parameter specifies the VCI information carried by the service from a base station. Connection1 is an R99 service and you need to select the RT-VBR policy for it. Connection2 is an R99 service and you need to select the RT-VBR policy for it.

Connection1: 32N1AFO1-1(PORT-1)

Sink SAI

Connection2: 32N1AFO1-1(PORT-1) Sink VPI


Sink VCI


Issue 03 (2013-02-20)



This parameter specifies the VPI information carried by the service after VPI switching. Max. VPI of an ATM port is 255 according to the plan and therefore the value of the VPI on the sink ranges from 0 to 255. This parameter specifies the VCI information carried by the service after VCI switching. Max. VCI of an ATM port is 127 according to the plan and therefore the value of the VPI on the sink ranges from 32 to 127.

323



Parameter

Example Value


Sink ATM Policy

Connection1: RT-VBR

Connection1 is an R99 service and you need to select the RT-VBR policy for it.

Connection2: RT-VBR

Connection2 is an R99 service and you need to select the RT-VBR policy for it.

5.

Transit VPI

-


Transit VCI

-


Click Advanced and set PW QoS and Advanced PW Attribute. Table 8-15 Parameters of advanced attributes

Issue 03 (2013-02-20)

Parameter

Example Value


Control Word

Must use

On an MPLS PSN, a control word carries the packet information. A control word is the encapsulation packet header that consists of four bytes. A control word can be used to identify the packet sequence or used for bit stuffing.


CW

A CW control word is used to detect the connectivity of a PW.


Ping

The VCCV verification mode is used to detect the connectivity of a PW.

Source ATM CoS Map

1(mapping1)


Sink ATM CoS Map

1(mapping1)



324



Parameter

Example Value


Max. Concatenated Cells Count

10

This parameter specifies the maximum number of ATM cells that can be encapsulated into a packet.

Packet Loading Time (us)

1000


Table 8-16 PW QoS parameters Parameter

Example Value


EXP

1


Bandwidth Limited

Enabled


CIR (kbit/s)

10000

Set the bandwidth based on the service traffic.

PIR (kbit/s)

30000

Set the bandwidth based on the service traffic.

6.

Click OK. The ATMService-R99 service is created successfully.

7.

Create an ATMService-HSDPA service. For details, refer to the preceding steps. Table 8-17 Parameters of general attributes

Issue 03 (2013-02-20)

Parameter

Example Value


Service Type

ATM


Service ID

2


Service Name

ATMService-HSDPA



325



Parameter

Example Value


Protection Type

Protection-free


Link Type




Example Value


SAI Type

ATM


Table 8-19 Parameters of the sink node Parameter

Example Value


SAI Type

ATM


Parameter

Example Value


Forward Type

Static Binding

l If you set Forward Type to Static Binding, you need to manually specify a tunnel in the Forward Tunnel area.


l If you set Forward Type, you need to set a tunnel priority in the Forward Tunnel area so that the system selects a tunnel according to the priority. Issue 03 (2013-02-20)


326



Parameter

Example Value


Forward Tunnel

Tunnel-001


Reverse Type

Static Binding


Reverse Tunnel

Tunnel-001_Reverse


PW ID

36


Signaling Type

Static


Encapsulation Type

MPLS


Table 8-21 Parameters for configuring an ATM connection

Issue 03 (2013-02-20)

Parameter

Example Value


Connection Name



Role

Working



327



Parameter

Example Value


Source SAI



Connection2: 35N1D12E-2(PORT-2) Source VPI


Source VCI


Source ATM Policy

Connection1: UBR Connection2: UBR

This parameter specifies the VPI information carried by the service from a base station. This parameter specifies the VCI information carried by the service from a base station. Connection1 is an HSDPA service and you need to select the UBR policy for it. Connection2 is an HSDPA service and you need to select the UBR policy for it.


Sink SAI



Sink VCI


Issue 03 (2013-02-20)



This parameter specifies the VPI information carried by the service after VPI switching. Max. VPI of an ATM port is 255 according to the plan and therefore the value of the VPI on the sink ranges from 0 to 255. This parameter specifies the VCI information carried by the service after VCI switching. Max. VCI of an ATM port is 127 according to the plan and therefore the value of the VPI on the sink ranges from 32 to 127.

328



Parameter

Example Value


Sink ATM Policy

Connection1: UBR

Connection1 is an HSDPA service and you need to select the UBR policy for it.

Connection2: UBR

Connection2 is an HSDPA service and you need to select the UBR policy for it. Transit VPI

-


Transit VCI

-


Table 8-22 Parameters of advanced attributes

Issue 03 (2013-02-20)

Parameter

Example Value


Control Word

Must use



CW



Ping


Source ATM CoS Map

1(mapping1)


Sink ATM CoS Map

1(mapping1)



20



329



Parameter

Example Value



1000


Table 8-23 PW QoS parameters

8.

Parameter

Example Value


EXP

3


Bandwidth Limited

Enabled


CIR (kbit/s)

10000

Set the bandwidth based on the volume of service traffic.

PIR (kbit/s)

30000


Create an ATMService-Signaling service. For details, refer to the preceding steps. Table 8-24 Parameters of general attributes

Issue 03 (2013-02-20)

Parameter

Example Value


Service Type

ATM


Service ID

3


Service Name

ATMService-Signaling


Protection Type

Protection-free



330



Parameter

Example Value


Link Type




Example Value


SAI Type

ATM


Table 8-26 Parameters of the sink node Parameter

Example Value


SAI Type

ATM


Parameter

Example Value


Forward Type

Static Binding

l If you set Forward Type to Static Binding, you need to manually specify a tunnel in the Forward Tunnel area.


l If you set Forward Type, you need to set a tunnel priority in the Forward Tunnel area so that the system selects a tunnel according to the priority. Forward Tunnel

Issue 03 (2013-02-20)

Tunnel-001


Set this parameter according to the networking plan. 331



Parameter

Example Value


Reverse Type

Static Binding


Reverse Tunnel

Tunnel-001_Reverse


PW ID

37


Signaling Type

Static


Encapsulation Type

MPLS


Table 8-28 Parameters for configuring an ATM connection Parameter

Example Value


Connection Name



Role

Working


Source SAI




Issue 03 (2013-02-20)


332



Parameter

Example Value


Source VPI

Connection1: 1

This parameter specifies the VPI information carried by the service from a base station.

Connection2: 1

Source VCI


Source ATM Policy

Connection1: CBR Connection2: CBR

This parameter specifies the VCI information carried by the service from a base station. Connection1 is a signaling service and you need to select the CBR policy for it. Connection2 is a signaling service and you need to select the CBR policy for it.


Sink SAI



Sink VCI


Sink ATM Policy

Connection1: CBR Connection2: CBR


This parameter specifies the VPI information carried by the service after VPI switching. Max. VPI of an ATM port is 255 according to the plan and therefore the value of the VPI on the sink ranges from 0 to 255. This parameter specifies the VCI information carried by the service after VCI switching. Max. VCI of an ATM port is 127 according to the plan and therefore the value of the VPI on the sink ranges from 32 to 127. Connection1 is a signaling service and you need to select the CBR policy for it. Connection2 is a signaling service and you need to select the CBR policy for it.

Transit VPI

Issue 03 (2013-02-20)

-



333



Parameter

Example Value


Transit VCI

-


Table 8-29 Parameters of advanced attributes

Issue 03 (2013-02-20)

Parameter

Example Value


Control Word

Must use



CW



Ping


Source ATM CoS Map

1(mapping1)


Sink ATM CoS Map

1(mapping1)



20



1000



334



Table 8-30 PW QoS parameters Parameter

Example Value


EXP

3


Bandwidth Limited

Enabled


CIR (kbit/s)

10000


PIR (kbit/s)

30000


----End

8.4.4 Configuration Process (Configuration on a Per-NE Basis) This section describes the process of configuring a UNIs-NNI ATM service on a per-NE basis.

Prerequisites l


l

You must learn about the networking requirements and service plan described in the example.

l

A network must be created.

Procedure Step 1 Set LSR IDs. 1.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > MPLS Management > Basic Configuration from the Function Tree.

2.

Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.

Issue 03 (2013-02-20)

Parameter

Example Value


LSR ID

NE1: 130.0.0.1



335


3.


Parameter

Example Value


Start of Global Label Space

0


Display the NE Explorers of NE2, NE3, NE4, NE5, and NE6 separately and perform the preceding two steps to set the parameters such as LSR ID. Parameter

Example Value


LSR ID

NE2: 130.0.0.2


NE3: 130.0.0.3 NE4: 130.0.0.4 NE5: 130.0.0.5 NE6: 130.0.0.6 Start of Global Label Space

0


Step 2 Configure NNI ports. 1.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree to configure NNI ports.

2.

In the General Attributes tab, select ports 3-EG8-1(PORT-1) and 3-EG8-2(PORT-2). Right-click the Port Mode filed, and select Layer 3. Set the parameters as required, and click Apply. Set relevant parameters 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 opposite port to the same.) l Max Frame Length (byte): 1620 (Set this parameter according to the length of data packets. All packets with a length greater than the maximum frame length are discarded.)

3.

Select the 3-EG8-1(PORT-1) and 3-EG8-2(PORT-2) in the Layer 3 Attributes tab. Rightclick the Enable Tunnel field and select Enabled. Right-click the Specify IP Address field and choose Manually. Then, set the parameters such as IP Address and IP Mask. Click Apply. Set relevant parameters as follows: l Enable Tunnel: Enabled l Specify IP Address: Manually (Manually indicates that you can set the IP address of the port.)

Issue 03 (2013-02-20)


336



l 3-EG8-1(PORT-1) IP Address: 10.0.0.1 l 3-EG8-2(PORT-2) IP Address: 10.0.5.1 l IP Mask: 255.255.255.252 4.

Display the NE Explorers of NE2, NE3, NE4, NE5, and NE6 separately. Perform 2.1 through 2.3 to set parameters for each port. Set relevant parameters as follows: Set parameters for each port the same as for NE1-3-EG8-1(PORT-1). The layer 3 attributes of each port are as follows: NE

Port

IP Address

IP Mask

NE2

4-PEX2-1(PORT-1)

10.0.1.1

255.255.255.252

3-PEG8-2(PORT-2)

10.0.0.2

255.255.255.252

3-EX2-1(PORT-1)

10.0.2.1

255.255.255.252

3-EX2-2(PORT-2)

10.0.1.2

255.255.255.252

3-PEX2-2(PORT-2)

10.0.2.2

255.255.255.252

3-PEX2-1(PORT-1)

10.0.3.1

255.255.255.252

4-PEX2-2(PORT-2)

10.0.3.2

255.255.255.252

3-PEG8-1(PORT-1)

10.0.4.2

255.255.255.252

3-PEG8-2(PORT-2)

10.0.4.1

255.255.255.252

3-PEG8-1(PORT-1)

10.0.5.2

255.255.255.252

NE3

NE4

NE5

NE6

Step 3 Create the working tunnel. 1.


2.

Set the basic information about the working tunnel.

Issue 03 (2013-02-20)

Parameter

Example Value


Tunnel Name

Working Tunnel


Protocol Type

MPLS


Signaling Type

Static CR


Service Direction

Unidirectional



337


3.


Parameter

Example Value



Selected


Protection Type

1+1


Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add them to the NE list and set the corresponding NE roles. Parameter

Example Value


NE Role

NE1: Ingress


NE2: Transit NE3: Egress

A transit is a pass-through node. In this example, NE2 is a transit node. An egress is the outgoing node of a network. In this example, NE3 is an egress node. Selected

Deploy

4.

Click Details to set the advanced parameters of the reverse tunnel. Click OK. Parameter

Example Value


Tunnel ID




Issue 03 (2013-02-20)


CIR(Kbit/s)



CBS(byte)




338



Parameter

Example Value


PIR(Kbit/s)



PBS(byte)



MTU (bytes)



LSP Type



EXP



Out Interface

Forward Tunnel:


l NE1: 3-EG8-1 (PORT-1) l NE2: 4-PEX2-1 (PORT-1) Reverse Tunnel: l NE3: 3-EX2-2 (PORT-2) l NE2: 3-PEG8-2 (PORT-2) Out Label



Forward Tunnel: l NE3: 21 l NE2: 31 In Interface

Forward Tunnel: l NE2: 3-PEG8-2 (PORT-2) l NE3: 3-EX2-2 (PORT-2)


Reverse Tunnel: l NE2: 4-PEX2-1 (PORT-1) l NE1: 3-EG8-1 (PORT-1) Issue 03 (2013-02-20)


339



Parameter

Example Value


In Label

Forward Tunnel:


l NE2: 20 l NE3: 30 Reverse Tunnel: l NE2: 21 l NE1: 31 Next Hop



Reverse Tunnel: l NE3: 10.0.1.1 l NE2: 10.0.0.1

Step 4 Create the protection tunnel. 1.

Create the protection tunnel by referring toStep 3. Set the basic Information as follows: Parameter

Example Value


Tunnel Name

Protection Tunnel


Protocol Type

MPLS


Signaling Type

Static CR


Service Direction

Unidirectional



Selected


Set the node information as follows:

Issue 03 (2013-02-20)


340



Parameter

Example Value


NE Role

NE1: Ingress


NE6, NE5, NE4: Transit NE3: Egress

A transit is a pass-through node. In this example, NE6, NE5, and NE4 are transit nodes. An egress is the outgoing node of a network. In this example, NE3 is an egress node. Selected

Deploy


Set the route information as follows: Parameter

Example Value


Tunnel ID




Issue 03 (2013-02-20)

CIR(Kbit/s)



CBS(byte)



PIR(Kbit/s)



PBS(byte)



MTU (bytes)



LSP Type




341



Parameter

Example Value


EXP



Out Interface

Forward Tunnel:


l NE1: 3-EG8-2 (PORT-2) l NE6: 3-PEG8-2 (PORT-2) l NE5: 4-PEX2-2 (PORT-2) l NE4: 3-PEX2-2 (PORT-2) Reverse Tunnel: l NE3: 3-EX2-1 (PORT-1) l NE4: 3-PEX2-1 (PORT-1) l NE5: 3-PEG8-1 (PORT-1) l NE6: 3-PEG8-1 (PORT-1) Out Label



l NE5: 42 l NE4: 52 Reverse Tunnel: l NE3: 23 l NE4: 33 l NE5: 43 l NE6: 53

Issue 03 (2013-02-20)


342



Parameter

Example Value


In Interface

Forward Tunnel:


l NE6: 3-PEG8-1 (PORT-1) l NE5: 3-PEG8-1 (PORT-1) l NE4: 3-PEX2-1 (PORT-1) l NE3: 3-EX2-1 (PORT-1) Reverse Tunnel: l NE4: 3-PEX2-2 (PORT-2) l NE5: 4-PEX2-2 (PORT-2) l NE6: 3-PEG8-2 (PORT-2) l NE1: 3-EG8-2 (PORT-2) In Label



l NE4: 42 l NE3: 52 Reverse Tunnel: l NE4: 23 l NE5: 33 l NE6: 43 l NE1: 53 Next Hop



l NE5: 10.0.3.1 l NE4: 10.0.2.1 Reverse Tunnel: l NE3: 10.0.2.2 l NE4: 10.0.3.2 l NE5: 10.0.4.1 l NE6: 10.0.2.1

Issue 03 (2013-02-20)


343



Step 5 Configure ports, including NodeB-side ATM ports and RNC-side ATM ports. 1.


In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree to configure NodeB-side ports.

b.

Select the ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8), Right-click the Port Mode field, and select Layer 2. Set the parameters as required, and click Apply. NOTE


Set relevant parameters as follows: l Port: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8) l Name: NodeB ATM (Set the port name as required. The port name distinguishes the port from other ports and helps to query the port.) l Port Mode: Layer 2 (The port transmits IMA signals.) l Encapsulation Type: ATM c.

In the Advanced tab, set Frame Format and Frame Mode for the ports from 35N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8). Click Apply. Set relevant parameters as follows: l Port: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-8(PORT-8) l Frame Format: CRC-4 multiframe (Set this parameter to the value same as that of the NodeB.) l Frame Mode: 31

d.


e.

In the Binding tab, click Configuration and set bound ports for ports 35-N1D12E-1 (PORT-1) and 35-N1D12E-2(PORT-2). Then, click OK. Set the parameters relevant to 35-N1D12E-1(PORT-1) as follows: l Available Boards: 35-N1D12E (Set this parameter according to the networking plan.) l Configurable Ports: 35-N1D12E-1(PORT-1) (Set this parameter according to the networking plan.) l Available Bound Paths – Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. For this example, the board is an ATM E1 board.) – Direction: Bidirectional (default) – Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. For this example, the path level is E1.) l Available Resources: ports from 35-N1D12E-1(PORT-1) to 35-N1D12E-4 (PORT-4) l Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) Set the parameters relevant to 35-N1D12E-2(PORT-2) as follows:

Issue 03 (2013-02-20)


344



l Available Boards: 35-N1D12E (Set this parameter according to the networking plan.) l Configurable Ports: 35-N1D12E-2(PORT-2) (Set this parameter according to the networking plan.) l Available Bound Paths – Level: E1 (Select E1 for an ATM E1 board and VC12-xv for an ATM STM-1 board. For this example, the board is an ATM E1 board.) – Direction: Bidirectional (default) – Optical Interface: - (This parameter need not be set for E1, but need be set for VC12-xv. For this example, the path level is E1.) l Available Resources: ports from 35-N1D12E-1(PORT-5) to 35-N1D12E-4 (PORT-8) l Available Timeslots: - (This parameter need not be set for E1, but need be set for VC12-xv.) f.

In the IMA Group Management tab, double-click the IMA Protocol Enable Status field and select Enabled. Set the other parameters as required. Then, click Apply. The settings of parameters need to be the same as those on the NodeB.

g.

In the ATM Interface Management tab, set the parameters such as Max. VPI and Max. VCI. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI (A UNI port is connected to the client-side equipment and an NNI port is connected to the ATM equipment on a core network.) l ATM Cell Payload Scrambling: Enabled l Loopback: No Loopback

2.


In the NE Explorer, select NE3 and choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree to configure RNC-side ATM ports.

b.

In the Layer 2 Attributes tab, select 32-N1AFO1-1(PORT-1) and set the parameters such as Max. VPI and Max. VCI for the port. Then, click Apply. Set relevant parameters as follows: l Port Type: UNI (A UNI port is connected to the client-side equipment and an NNI port is connected to the ATM equipment on a core network.) l ATM Cell Payload Scrambling: Enabled l Max. VPI: 255 (Set this parameter according to the networking plan. Set Max. VPI to specify the value range of VPI. The VPI ranges from 0 to Max. VPI.) l Max. VCI: 127 (Set this parameter according to the networking plan. Set Max. VCI to specify the value range of VCI. The VCI ranges from 0 to Max. VCI.) l VCC-Supported VPI Count: 32 (Set this parameter according to the networking plan.)

Step 6 Create three UNIs-NNI ATM services.

Issue 03 (2013-02-20)


345



1.

In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > ATM Service Management from the Function Tree. Then, create an R99 service from NE1 to NE3.

2.

Click New. The New ATM Service window is displayed. Then, set Service ID, Service Name, Service Type, and Connection Type. Set relevant parameters as follows: l Service ID: 1 l Service Name: ATMService-R99 l Service Type: UNIs-NNI l Connection Type: PVC (PVC indicates that the VPI and VCI of the ATM connection can be changed; PVP indicates that only the VPI of the ATM connection can be changed.)

3.

Click the Connection tab and click Add. The Configure Connection window is displayed. Add connection 1 and connection 2. Set relevant parameters as follows: l Connection 1 – Connection Name: Connection 1 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-1(PORT-1) – Source VPI: 1 (This parameter indicates the VPI information that is transmitted with the service from the NodeB.) – Source VCI: 100 (This parameter indicates the VCI information that is transmitted with the service from the NodeB.) – PW ID: 35 – Sink Board: – Sink Port: – Sink VPI: 50 (This parameter indicates the VPI information that is transmitted with the service after VPI switching. Max. VPI of the ATM port is planned to be 255, and therefore the Sink VPI ranges from 0 to 255.) – Sink VCI: 32 (This parameter indicates The VCI information that is transmitted with the service after VCI switching. Max. VCI of the ATM port is planned to be 127, and therefore the Sink VCI ranges from 32 to 127.) – Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) – Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 1 is an R99 service.) l Connection 2 – Connection Name: Connection 2 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-2(PORT-2) – Source VPI: 1 – Source VCI: 100 – PW ID: 35

Issue 03 (2013-02-20)


346



– Sink Board: – Sink Port: – Sink VPI: 60 – Sink VCI: 32 – Uplink Policy: RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.) – Downlink Policy: RT-VBR (Select the RT-VBR policy, because connection 2 is an R99 service.) 4.

Click the PW tab and click Add. The Configure PW window is displayed. In the window, set attributes for the PW. Set the parameters related to PW1 as follows: l Basic attributes – PW ID: 35 – PW Signaling Type: Static (Static indicates that ingress and egress labels are manually added.) – PW Type: ATM n to one VCC cell transport (Select ATM n-to-one VCC cell transport if multiple ATM connections are mapped to one PW; select ATM one-toone VCC Cell Mode if one ATM connection is mapped to one PW. For this example, two ATM connections are mapped are mapped to one PW.) – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 – Tunnel Type: MPLS – Tunnel No. : 1 (Tunnel-0001) – Peer LSR ID: 1.0.0.3 (This parameter specifies the LSR ID of the NE terminating the PW.) l Advanced attributes – Control Word: Must use – Control Channel Type: CW (A CW control word is used to detect the connectivity of a PW.) – VCCV Verification Mode: Ping (The VCCV verification mode is used to detect the connectivity of a PW.) – Max. Concatenated Cell Count: 10 (This parameter specifies the maximum number of ATM cells that can be encapsulated into a packet.) – Packet Loading Time (us): 1000 l QoS Ingress – EXP: 1

5.

Click the CoS Mapping tab and set QoS attributes for PW1. Set CoS mapping for PW1 as follows: l PW ID: 35 l CoS Mapping: 1 (Default AtmCosMap)

6.

Issue 03 (2013-02-20)

In the NE Explorer, select NE3. Then, create an ATMService-R99 service by following 6.1 to 6.5. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

347



l Set general attributes for the ATM service as follows: – Service ID: 1 – Service Name: ATMService-R99 – Service Type: UNIs-NNI – Connection Type: PVC l Configure ATM connections as follows: – Connection 1 – Connection Name: Connection 1 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 50 – Source VCI: 32 – PW ID: 35 – Sink Board: – Sink Port: – Sink VPI: 50 – Sink VCI: 32 – Uplink Policy: RT-VBR – Downlink Policy: RT-VBR – Connection 2 – Connection Name: Connection 2 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 60 – Source VCI: 32 – PW ID: 35 – Sink Board: – Sink Port: – Sink VPI: 60 – Sink VCI: 32 – Uplink Policy: RT-VBR – Downlink Policy: RT-VBR l Set the parameters related to PW1 as follows: – Basic attributes – PW ID: 35 – PW Signaling Type: Static – PW Type: ATM n to one VCC cell transport – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 Issue 03 (2013-02-20)


348



– Tunnel Type: MPLS – Tunnel No. : 2 (Tunnel-0002) – Peer LSR ID: 1.0.0.1 – Advanced attributes – Control Word: Must use – Control Channel Type: CW – VCCV Verification Mode: Ping – Max. Concatenated Cell Count: 10 – Packet Loading Time (us): 1000 – QoS Ingress – EXP: 1 l Set CoS mapping for PW1 as follows: – PW ID: 35 – CoS Mapping: 1 (Default AtmCosMap) 7.

Create an ATMService-HSDPA service by following 6.1 to 6.6. Set the parameters related to NE1 as follows: l Set general attributes for the ATM service as follows: – Service ID: 2 – Service Name: ATMService-HSDPA – Service Type: UNIs-NNI – Connection Type: PVC l Configure ATM connections as follows: – Connection 1 – Connection Name: Connection 1 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-1(PORT-1) – 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 – Connection Name: Connection 2 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-2(PORT-2)

Issue 03 (2013-02-20)


349



– Source VPI: 1 – Source VCI: 101 – PW ID: 36 – Sink Board: – Sink Port: – Sink VPI: 61 – Sink VCI: 32 – Uplink Policy: UBR – Downlink Policy: UBR l Set the parameters related to PW2 as follows: – Basic attributes – PW ID: 36 – PW Signaling Type: Static – PW Type: ATM n to one VCC cell transport – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 – Tunnel Type: MPLS – Tunnel No. : 1 (Tunnel-0001) – Peer LSR ID: 1.0.0.3 – Advanced attributes – Control Word: Must use – Control Channel Type: CW – VCCV Verification Mode: Ping – Max. Concatenated Cell Count: 10 – Packet Loading Time (us): 1000 – QoS Ingress – EXP: 3 l Set CoS mapping for PW2 as follows: – PW ID: 36 – CoS Mapping: 1 (Default AtmCosMap) Set the parameters related to NE3 as follows: l Set general attributes for the ATM service as follows: – Service ID: 2 – Service Name: ATMService-HSDPA – Service Type: UNIs-NNI – Connection Type: PVC l Configure ATM connections as follows: – Connection 1 Issue 03 (2013-02-20)


350



– Connection Name: Connection 1 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 51 – Source VCI: 32 – PW ID: 36 – Sink Board: – Sink Port: – Sink VPI: 51 – Sink VCI: 32 – Uplink Policy: UBR – Downlink Policy: UBR – Connection 2 – Connection Name: Connection 2 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 61 – Source VCI: 32 – PW ID: 36 – Sink Board: – Sink Port: – Sink VPI: 61 – Sink VCI: 32 – Uplink Policy: UBR – Downlink Policy: UBR l Set the parameters related to PW2 as follows: – Basic attributes – PW ID: 36 – PW Signaling Type: Static – PW Type: ATM n to one VCC cell transport – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 – Tunnel Type: MPLS – Tunnel No. : 2 (Tunnel-0002) – Peer LSR ID: 1.0.0.1 – Advanced attributes – Control Word: Must use – Control Channel Type: CW – VCCV Verification Mode: Ping Issue 03 (2013-02-20)


351



– Max. Concatenated Cell Count: 10 – Packet Loading Time (us): 1000 – QoS Ingress – EXP: 3 l Set CoS mapping for PW2 as follows: – PW ID: 36 – CoS Mapping: 1 (Default AtmCosMap) 8.

Create an ATMService-Signaling service by following 6.1 to 6.6. Set the parameters related to NE1 as follows: l Set general attributes for the ATM service as follows: – Service ID: 3 – Service Name: ATMService-Signaling – Service Type: UNIs-NNI – Connection Type: PVC l Configure ATM connections as follows: – Connection 1 – Connection Name: Connection 1 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-1(PORT-1) – Source VPI: 1 – Source VCI: 102 – PW ID: 37 – Sink Board: – Sink Port: – Sink VPI: 52 – Sink VCI: 32 – Uplink Policy: CBR – Downlink Policy: CBR – Connection 2 – Connection Name: Connection 2 – Source Board: 35-N1D12E – Source Port: 35-N1D12E-2(PORT-2) – Source VPI: 1 – Source VCI: 102 – PW ID: 37 – Sink Board: – Sink Port: – Sink VPI: 62 – Sink VCI: 32

Issue 03 (2013-02-20)


352



– Uplink Policy: CBR – Downlink Policy: CBR l Set the parameters related to PW2 as follows: – Basic attributes – PW ID: 37 – PW Signaling Type: Static – PW Type: ATM n to one VCC cell transport – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 – Tunnel Type: MPLS – Tunnel No. : 1 (Tunnel-0001) – Peer LSR ID: 1.0.0.3 – Advanced attributes – Control Word: Must use – Control Channel Type: CW – VCCV Verification Mode: Ping – Max. Concatenated Cell Count: 10 – Packet Loading Time (us): 1000 – QoS Ingress – EXP: 0 l Set CoS mapping for PW2 as follows: – PW ID: 37 – CoS Mapping: 1 (Default AtmCosMap) Set the parameters related to NE3 as follows: l Set general attributes for the ATM service as follows: – Service ID: 3 – Service Name: ATMService-Signaling – Service Type: UNIs-NNI – Connection Type: PVC l Configure ATM connections as follows: – Connection 1 – Connection Name: Connection 1 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 52 – Source VCI: 32 – PW ID: 37 – Sink Board: Issue 03 (2013-02-20)


353



– Sink Port: – Sink VPI: 52 – Sink VCI: 32 – Uplink Policy: CBR – Downlink Policy: CBR – Connection 2 – Connection Name: Connection 2 – Source Board: 32-N1AFO1 – Source Port: 32-N1AFO1-1(PORT-1) – Source VPI: 62 – Source VCI: 32 – PW ID: 37 – Sink Board: – Sink Port: – Sink VPI: 62 – Sink VCI: 32 – Uplink Policy: CBR – Downlink Policy: CBR l Set the parameters related to PW2 as follows: – Basic attributes – PW ID: 37 – PW Signaling Type: Static – PW Type: ATM n to one VCC cell transport – PW Direction: Bidirectional – PW Incoming Label: 33 – PW Outgoing Label: 32 – Tunnel Type: MPLS – Tunnel No. : 2 (Tunnel-0002) – Peer LSR ID: 1.0.0.1 – Advanced attributes – Control Word: Must use – Control Channel Type: CW – VCCV Verification Mode: Ping – Max. Concatenated Cell Count: 10 – Packet Loading Time (us): 1000 – QoS Ingress – EXP: 0 l Set CoS mapping for PW2 as follows: – PW ID: 37 Issue 03 (2013-02-20)


354



– CoS Mapping: 1 (Default AtmCosMap) ----End

8.5 Verifying ATM Service Configuration Use the ATM OAM function to test the connectivity of UNIs-NNI ATM services to ensure that the ATM services are transmitted normally. This section describes how to test the connectivity of ATM services by performing a loopback (LB) test.

Prerequisites l


l

An ATM service must be configured. For information on how to configure an ATM service, refer to section 8 Configuring ATM Services in the Configuration Guide.

Tools, Equipment, and Materials U2000

Test Connection Diagram Figure 8-9 shows the connection for testing the connectivity of ATM services. Figure 8-9 Connection diagram for testing the connectivity of ATM services PSN

Inloop

NE1

Inloop

NE2

Procedure Step 1 Set the automatic loopback release function to Disabled for the UNI ports receiving the tested ATM service on NE1 and NE2. 1.

Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function from the Main Menu.

2.

Select NE1 and NE2 from Physical Root and click

3.

Set Auto Disabling to Disabled for SDH Optical/Electrical Interface Loopback of NE1 and NE2.

.

NOTE

When Auto Disabling of SDH Optical/Electrical Interface Loopback on an NE is set to Disabled, the automatic loopback release function is disabled for all SDH optical ports, PDH electrical ports, and ATM IMA groups on the NE.

Issue 03 (2013-02-20)


355



Step 2 Set an inloop for the UNI port (to be tested) receiving the ATM service on NE1 by using the U2000. l If the UNI port receiving the ATM service is an IMA group, do as follows: 1.

On the Main Topology of the U2000, right-click NE1 and choose NE Explorer from the shortcut menu to display the NE Explorer window.

2.

In the NE Explorer window, select NE1 and then choose Configuration > Packet Configuration > Interface Management > ATM IMA Management from the Function Tree.

3.

Click the ATM Interface Management tab and then select the IMA group carrying the tested ATM service.

4.

Set Loopback to Inloop for the IMA group.

5.

Click Apply.

l If the UNI port receiving the ATM service is an AFO1 port, do as follows: 1.

On the Main Topology of the U2000, right-click NE1 and choose NE Explorer from the shortcut menu to display the NE Explorer window.

2.

In the NE Explorer window, select NE1 and then choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree.

3.

Click the Advanced Attributes tab and then select the AFO1 port carrying the tested ATM service.

4.

Set Loopback to Inloop for the AFO1 port.

5.

Click Apply.

Step 3 Set an inloop for the UNI port (to be tested) receiving the ATM service on NE2 with reference to Step 2. Step 4 In the NE Explorer window, select NE1 and then choose Configuration > ATM OAM Management from the Function Tree. Step 5 Click the Remote Loopback Test tab, and set Segment and End Attribute to Endpoint for the ATM service to be tested whose Connection Direction is Source. NOTE

Segment and End Attribute of an ATM service specifies the type of ATM OAM cells transmitted during an LB test. l If Segment and End Attribute is set to Segment point, seg_LB cells are transmitted. l If Segment and End Attribute is set to Endpoint, e-t-e_LB cells are transmitted.

Step 6 Set Loopback Point NE of the tested ATM service to NE2. Step 7 Click Test. After the test is completed, click

to check the LB test information.

NOTE

In Browse Event Logs, check Reporting of LB status information. If Test Result is Succeeded, the tested ATM service is normal. If Test Result is Failed, rectify faults with reference to Troubleshooting.

Step 8 Release the inloops for the UNI ports receiving the ATM service on NE1 and NE2 with reference to Step 2. Step 9 Set Automatic Disabling to Enabled for SDH Optical/Electrical Interface Loopback on NE1 and NE2 with reference to Step 1. ----End Issue 03 (2013-02-20)


356


9

9 Configuration Task Collection

Configuration Task Collection

About This Chapter This topic lists the relevant configuration tasks. 9.1 Configuring an Ethernet Port This topic describes how to set the attributes of an Ethernet port. An Ethernet port can be used to carry Ethernet packets or tunnels, depending on different settings of the port attributes. The attributes of an Ethernet port include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes, and flow control. 9.2 Configuring CES Ports This topic describes how to configure channelized STM-1 ports and E1 ports to support access of CES services. 9.3 Configuring the NNIs Configuring the NNIs is the basis of configuring the packet Ethernet services. 9.4 Configuring an MPLS Tunnel On a PSN network, the multi-protocol label switching (MPLS) tunnel carries PWs where various services are encapsulated. In this manner, data packets can be transparently transmitted between NEs. One MPLS tunnel can carry several PWs. Before configuring a service, you need to configure the MPLS tunnel that carries the service. 9.5 Managing MPLS Tunnels MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. Therefore, it is crucial to properly manage MPLS tunnels. Managing MPLS tunnels involves checking the MPLS tunnel topology, deploying MPLS tunnels, deleting MPLS tunnels, and managing discrete MPLS tunnels. 9.6 Configuring MPLS OAM MPLS OAM effectively detects, confirms, and locates the internal defects of an MPLS network, and thus monitors the network performance. 9.7 Configuring MPLS Tunnel APS MPLS tunnel APS protection is implemented based on the APS protocol. If MPLS tunnel APS is configured, the services are switched from the working tunnel to the protection tunnel after the working tunnel is faulty. 9.8 Managing MPLS Tunnel APS Protection Groups Issue 03 (2013-02-20)


357



MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. MPLS tunnel APS provides protection for MPLS tunnels. Therefore, it is crucial to properly manage MPLS tunnel APS protection groups. Managing MPLS tunnel APS protection groups involves automatically discovering, deploying, modifying, and deleting MPLS tunnel APS protection groups. 9.9 Operation Tasks for Configuring E-Line Services This topic describes how to configure E-Line services, including UNI-UNI E-Line services, ELine services carried by ports, E-Line services carried by PWs, and E-Line services carried by QinQ links. 9.10 Operation Task for Configuring E-LAN Services This topic describes how to configure E-LAN services, including E-LAN services carried by ports, E-LAN services carried by PWs, and E-LAN services carried by QinQ links. 9.11 Configuring E-AGGR Services This topic describes how to configure E-AGGR services, including E-AGGR services carried by ports and E-AGGR services carried by PWs. 9.12 Configuring Transit Nodes for Ethernet Services On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for an Ethernet service. 9.13 Operation Tasks for Configuring CES Services This topic describes the operation tasks for configuring CES services in per-NE mode and endto-end mode on the NMS. 9.14 Configuring Transit NEs for CES Services On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for a CES service. 9.15 Configuring ATM PWE3 Services This section describes the operation tasks for configuring ATM PWE3 services in per-NE mode and end-to-end mode on the NMS. 9.16 Managing PWE3 Services Quality of PWE3 services has significant impacts on customer revenues; stable PWE3 services increase customer revenues. Therefore, it is crucial to properly manage PWE3 services. Managing PWE3 services involves deploying, modifying, and deleting PWE3 services, checking the PWE3 service topology, and managing discrete PWE3 services. 9.17 Managing Composite Services Managing composite services includes automatically discovering and deploying composite services. 9.18 Configuring Address Resolution Dynamic Address Resolution Protocol (ARP) learning is implemented by the dynamic ARP. It automatically maps IP addresses and MAC address, requiring no manual configuration of an ARP table. Generally, dynamic ARP learning is applicable to networks with many NEs. Dynamic ARP protocol packets, however, may significantly affect NE operating. For static ARP configuration, the ARP table, namely, mapping between IP addresses and MAC addresses, is configured manually, but NE operating is not affected by static ARP protocol packets. Static ARP configuration is applicable to small networks with specific NEs and NE ports used. 9.19 Configuring the NE-Level TPID Issue 03 (2013-02-20)


358



When the request VLAN function is enabled, PW-carried Ethernet services function properly only if the TPIDs in the request VLAN tags of the Ethernet services are the same at both ends of a PW. 9.20 Creating a QinQ Link In the case of the QinQ link, a layer of VLAN tag is added to the packets that are accessed over a port, through QinQ encapsulation. Hence, the packets from different VLANs on the user-side network can be encapsulated and then transmitted to the same VLAN on the transport network. In this manner, the VLAN resources on the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ links on the network side. 9.21 Creating a V-UNI Group Creating a V-UNI group involves selecting the V-UNI group members and setting the overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group. 9.22 Managing the Blacklist The blacklist is used to discard the data frame that contains the specified destination MAC address. Managing a blacklist involves configuring disabled MAC addresses.

Issue 03 (2013-02-20)


359



9.1 Configuring an Ethernet Port This topic describes how to set the attributes of an Ethernet port. An Ethernet port can be used to carry Ethernet packets or tunnels, depending on different settings of the port attributes. The attributes of an Ethernet port include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes, and flow control. The application scenario of an Ethernet port depends on the settings of the port attributes. For details, refer to Table 9-1. Table 9-1 Application scenario of an Ethernet port Application Scenario

Port Type

Required Port Attribute

Accessing the Ethernet service

Ethernet port

General attributes, Layer 2 attributes

Carrying the QinQ Link

Ethernet port


Carrying the tunnel

Ethernet port


NOTE

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

Follow the procedure shown in Figure 9-1 to set the attributes of an Ethernet port.

Issue 03 (2013-02-20)


360



Figure 9-1 Procedure for configuring an Ethernet port Carry Ethernet packets

Carry tunnels

Start

Start

Set general attributes

Set general attributes

Set Layer 2 attributes

Set Layer 3 attributes

Set advanced attributes

Set advanced attributes

Configure the flow control

Configure the flow control

End

End

Required

Optional

9.1.1 Setting the General Attributes of Ethernet Interfaces Before you set the Layer 2 and Layer 3 attributes of an Ethernet port, you need to set the general attributes of the corresponding Ethernet port. The general attributes of an Ethernet port define the physical-layer information, such as the port mode, encapsulation type, and maximum frame length.

Prerequisites You must be an NM user with NE administrator authority or higher.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Issue 03 (2013-02-20)


361



Step 2 Click the General Attributes tab. Step 3 Select the board and set the parameters as required. For details about the parameters, see 10.1.1 General Attributes. NOTE

l When Port Mode is set to Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l When Port Mode is set to Layer 3, Encapsulation Type can be set to 802.1Q only. In this case, the port can be used to carry the tunnel.

Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. ----End

9.1.2 Setting the Layer 2 Attributes of Ethernet Ports After the Layer 2 attributes of an Ethernet port are set, the port can be used for connecting to the client-side equipment at the edge of an SDH network or for forwarding Ethernet packets within the SDH network. The Layer 2 attributes of an Ethernet port define the related information about the data link layer.

Prerequisites l


l

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

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Select the port and set the parameters as required. For details about the parameters, see 10.1.3 Layer 2 Attributes. 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 can be set only when Encapsulation Type is 802.1Q.

Step 4 Click Apply. Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. ----End

9.1.3 Setting the Layer 3 Attributes of Ethernet Ports When an Ethernet port is used to carry a tunnel, you need to set the Layer 3 attributes of the Ethernet port. The Layer 3 attributes of an Ethernet port define the related attributes of the network layer. Issue 03 (2013-02-20)


362



Prerequisites l


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 > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Select the board and set the parameters as required. For details about the parameters, see 10.1.4 Layer 3 Attributes. NOTE

When changing the IP address of an port, ensure that the IP address of the port and the IP addresses of the other ports configured with services are not in the same subnet.


9.1.4 Setting the Advanced Attributes of Ethernet Ports You can set the routine maintenance parameters by setting the advanced attributes of Ethernet ports.


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the board and set the parameters as required. For details about the parameters, see 10.1.5 Advanced Attributes. Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. ----End

9.1.5 Configuring the Flow Control When the flow control function is enabled, the Ethernet port sends a PAUSE frame to the opposite end and then the opposite end stops transmitting Ethernet packets, if a congestion occurs on the link. As a result, the congestion is prevented. Issue 03 (2013-02-20)


363




Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Flow Control tab. Step 3 Select the board and set the parameters as required. Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. ----End

9.2 Configuring CES Ports This topic describes how to configure channelized STM-1 ports and E1 ports to support access of CES services.

9.2.1 Configuring Channelized STM-1 Ports When configuring CES services carried by channelized STM-1 ports, you need to set basic attributes and the frame format in the advanced attributes to ensure that the frame format of the channelized STM-1 ports is the same as the service encapsulation format.


Procedure Step 1 In the NE Explorer, select an NE, and then choose Configuration > Packet Configuration > Interface Management > SDH Interface from the Function Tree. Step 2 Click the General Attributes tab and set the parameters according to the actual requirements. For details about the parameters, see 10.6.1 Channelized STM-1 Port.

NOTE

In the case of the OptiX OSN equipment, Port Mode can be set to Layer 1 only. In this case, the OptiX OSN equipment supports access of channelized STM-1 services.

Step 3 After setting the parameters, click Apply. Issue 03 (2013-02-20)


364



Step 4 Optional: Select a port and then check its associated services and logical port in the lower window. Step 5 Click the Advanced Attributes tab and set the parameters according to the actual requirements. For details about the parameters, see 10.6.1 Channelized STM-1 Port.

Step 6 After setting the parameters, click Apply. Step 7 In the NE Explorer, select the CQ1 and choose Configuration > Interface Management > Path Configuration from the Function Tree. Set the parameters according to the actual requirements. Step 8 After setting the parameters, click Apply. ----End

9.2.2 Configuring E1 Ports When configuring CES services carried by E1 ports, you need to set basic attributes and the frame format in the advanced attributes to ensure that the frame format of the E1 ports is the same as the service encapsulation format.


Procedure Step 1 In the NE Explorer, select an NE, and then choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Select a CES board. Step 3 Click the General Attributes tab and set the parameters according to the actual requirements. For details about the parameters, see 10.6.2 E1 Port.

NOTE

In the case of the OptiX OSN equipment, Port Mode can be set to Layer 1 only. In this case, the OptiX OSN equipment supports access of E1 services.

Step 4 After setting the parameters, click Apply. Step 5 Optional: Select a port and then check its associated services and logical port in the lower window. Issue 03 (2013-02-20)


365



Step 6 After setting the parameters, click Apply. Step 7 Click the Advanced Attributes tab and set the parameters according to the actual requirements. For details about the parameters, see 10.6.2 E1 Port.

NOTE

If an E1 port carries a CESoPSN CES service, set Frame Format of the E1 port to Double Frame or CRC-4 Multiframe (recommended value). If an E1 port carries an SAToP CES service, set Frame Format of the E1 port to Unframe. In the case of the OptiX OSN equipment, the CES ACR clock mode can be configured on the NMS. Set CES Encapsulation Clock Mode of an E1 port to Line Clock.

----End

9.3 Configuring the NNIs Configuring the NNIs is the basis of configuring the packet Ethernet services.

9.3.1 Configuring the NNIs for Ethernet Services Carried by Ports Before configuring the Ethernet services that are carried by ports, you need to set basic attributes of the corresponding Ethernet port. The general attributes of an Ethernet port define the physicallayer 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 > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the board and set the parameters as required.

NOTE

l When Port Mode is set to Layer 2, Encapsulation Type can be set to 802.1Q, QinQ or Null. l When Encapsulation Type is set to QinQ, the port identifies the QinQ packets. l When Encapsulation Type is set to 802.1Q, the port identifies the 802.1Q packets. l When Encapsulation Type is set to Null, The port transparently transmits the accessed packets.

Issue 03 (2013-02-20)


366



Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click the Layer 2 Attributes tab. Step 6 Select the board and set the parameters as required. For details about the parameters, see 10.1.3 Layer 2 Attributes.

NOTE

l Tag Aware: The port transparently transmits the data packet with a VLAN ID (that is, the data packet is tagged). If a data packet does not have a VLAN ID (that is, the data packet is untagged), the port discards the data packet. In this case, the Default VLAN ID and VLAN Priority are meaningless. l Access: The port adds the default VLAN ID to the data packet without any VLAN ID (that is, the data packet is untagged). If the data packet has a VLAN ID (that is, the data packet is tagged), the port discards the data packet. l Hybrid: The port adds the default VLAN ID to the data packet without any VLAN ID (that is, the data packet is untagged). If the data packet has a VLAN ID (that is, the data packet is tagged), the port transparently transmits the data packet.


9.3.2 Configuring the NNIs for Ethernet Services Carried by Static MPLS Tunnels To configure the Ethernet services that are carried by static MPLS tunnels, you need to set the attributes related to the port of the static MPLS tunnels.



Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab.

Issue 03 (2013-02-20)


367



Set the general attributes of the port as follows: l Enable Port: Enabled l Port Mode: Layer 3 Set the other parameters as required. Step 3 Click Apply. Step 4 Click the Layer 3 Attributes tab. Step 5 Select the desired port and set Enable Tunnel as Enabled. Set Specify IP to Manually. Set IP Address and IP Mask according to the service planning information. For details about the parameters, see 10.1.4 Layer 3 Attributes. NOTE

l When changing the IP address of the port, ensure that the IP address of this port and the IP addresses of the other ports configured with services are not in the same subnet.


9.3.3 Configuring the NNIs for Ethernet Services Carried by QinQ Links Before configuring Ethernet services that are carried by QinQ links, you need to set the general attributes of the corresponding Ethernet port. The general attributes of an Ethernet port 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 > Packet Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the board and set the parameters as required.

Issue 03 (2013-02-20)


368



NOTE

l When Port Mode is set to Layer 2, Encapsulation Type can be set to QinQ. When Encapsulation Type is set to QinQ, he port identifies the QinQ packets. l In the case of an NNI port, Max Data Packet Size(byte) must be more than 1020. A DCN packet contains a maximum of 1020 bytes. If Max Data Packet Size(byte) is less than 1020, the DCN packets in the receive direction may be lost.


9.4 Configuring an MPLS Tunnel On a PSN network, the multi-protocol label switching (MPLS) tunnel carries PWs where various services are encapsulated. In this manner, data packets can be transparently transmitted between NEs. One MPLS tunnel can carry several PWs. Before configuring a service, you need to configure the MPLS tunnel that carries the service. NOTE

During configuration of unidirectional MPLS tunnels, forward MPLS tunnel and reverse MPLS tunnel are created separately. For a unidirectional forward MPLS tunnel, either its mapping reverse MPLS tunnel or another tunnel can be configured to transmit BDI packets during MPLS OAM configuration; either its mapping reverse MPLS tunnel or another reverse MPLS tunnel can be configured as the protection reverse tunnel during configuration of MPLS tunnel APS. For bidirectional MPLS tunnels, a forward MPLS tunnel is bound with a specific reverse MPLS tunnel. During configuration of MPLS OAM, BDI packets are configured to be transmitted by the reverse MPLS tunnel bound with the forward MPLS tunnel. In addition, only the reverse MPLS tunnel that is bound with the forward MPLS tunnel can be configured as the protection reverse tunnel during configuration of MPLS tunnel APS. Before configuring MPLS tunnels, refer to the number of MPLS tunnels recorded in "Functions and Features" under "Packet Boards" in the Hardware Description.

9.4.1 Configuring LSR ID In the Basic Configuration interface, you can set LSR (Label Switch Router) ID.



Issue 03 (2013-02-20)


369



Precautions NOTE

When planning LSR IDs, adhere to the following principles: l when ASON and packet services coexist, LSR IDs of packet services and node IDs of ASON services must be the same. l An LSR ID can be an IP address of standard class A, B, or C, that is, an IP address within the range from 1.0.0.1 to 223.255.255.254. An LSR ID cannot be a broadcast address (*.*.*.255), multicast address (224.0.0.0 to 239.255.255.255), reserved address (240.0.0.0 to 255.255.255.255), network address (*.*.*.0), zero address (0.*.*.*), or loopback address (127.*.*.*). l The address of the network segment used with priority: 172.16.0.0-172.31.255.255. In this network segment, the number of the available IP address is 1048574 (the 172.16.0.0 and 172.31.255.255 are exceptional). l If the previous network segment address conflicts with the network segment address of the management plane or the DCN network address, use the following network segment address with priority: 10.0.0.0-10.255.255.255. In this network segment, the number of the available IP address is 16777214 (the 10.0.0.0 and 10.255.255.255 are exceptional). l If the previous network segment address is still conflicting, use the following network segment address: 192.168.0.0-192.168.255.255. In this network segment, the number of the available IP address is 65534 (the 192.168.0.0 and 192.168.255.255 are exceptional). l Each NE must have an independent and globally unique LSR ID on a network. l The LSR ID and IP address of an NE must be different from each other and must belong to different network segments. l The LSR ID of an NE and the IP addresses of service ports on the NE must belong to different network segments.

Procedure Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > MPLS Management > Basic Configuration from the Function Tree. Step 2 Set LSR ID. For details about LSR ID, see 10.2.1 Basic Configuration. NOTE

l When the LSR ID is specified for the first time, no warm-reset occurs on the NE. If the specified LSR ID is then changed, a warm-reset occurs on the NE but does not affect services. l If any tunnel exists, do not change the LSR ID.

----End

9.4.2 Configuring an MPLS Tunnel on a Per-NE Basis This topic describes how to configure an MPLS tunnel on a per-NE basis by using the U2000.

9.4.2.1 Configuring a Unidirectional Static MPLS Tunnel on a Per-NE Basis You can configure an end-to-end unicast MPLS tunnel on a per-NE basis. You need to configure the MPLS tunnel on each node that the MPLS tunnel traverses.


You must be an NM user with NE administrator authority or higher. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

370



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.

Procedure Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration > Packet Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Step 2 Click the Static Tunnel tab and click New > Unidirectional Tunnel. Then, the New Unicast Tunnel dialog box is displayed. Step 3 Set the parameters of the forward and reverse MPLS tunnels. For details about the parameters, see 10.2.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis).

Issue 03 (2013-02-20)


371



NOTE

When Node Type is set to Egress, Bandwidth(kbit/s) is the same as the tunnel bandwidth in the Ingress direction and cannot be changed manually. Set Next Hop Address to be the IP address of the port of the next node.

Step 4 Click OK to complete the configuration of the static MPLS tunnel. Step 5 Refer to Steps 1 - 4 to configure the static MPLS tunnels on the intermediate NEs and sink NE. ----End

9.4.2.2 Configuring a Bidirectional Static MPLS Tunnel on a Per-NE Basis You can configure an end-to-end bidirectional MPLS tunnel on a per-NE basis. You need to configure the MPLS tunnel on each node that the MPLS tunnel traverses.

Prerequisites l


l


l


Procedure Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration > Packet Configuration > MPLS Management > Unicast Tunnel Management from Function Tree. Step 2 Click the Static Tunnel tab and click New > Bidirectional Tunnel. Then, the New Unicast Bidirectional Tunnel dialog box is displayed. Step 3 Set the parameters of the bidirectional MPLS tunnels. For details about the parameters, see 10.2.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis).

Issue 03 (2013-02-20)


372



NOTE

l When Node Type is set to Transit, the In port, Out port, Forward In Label, Forward Out Label, Reverse In Label, Reverse Out Label, Forward Next Hop Address, Reverse Next Hop Address, Source Node and Sink Node parameters need to be set for the tunnel. l When Node Type is set to Egress, the In port, Forward In Label, Reverse Out Label, Reverse Next Hop Address and Source Node parameters need to be set for the tunnel.

Step 4 Click OK to complete the configuration of the static MPLS tunnel. Step 5 Refer to Steps 1 - 4 to configure the static MPLS tunnels on the intermediate NEs and sink NE. ----End

9.4.3 Configuring an MPLS Tunnel in an End-to-End Mode This topic describes how to configure an MPLS tunnel in end-to-end mode by using the NMS.

Issue 03 (2013-02-20)


373



9.4.3.1 Configuring a Static and Unidirectional MPLS Tunnel in End-to-End Mode When creating a static and unidirectional MPLS tunnel in end-to-end mode, you select the source NE, sink NE, or transit NE directly in the physical topology and then complete creation of the unidirectional MPLS tunnel on the NMS.

Prerequisites l


l


l

The LSR ID of each NE must be set correctly.

Procedure Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the Create Tunnel window is displayed.

Step 2 Set the basic information about the MPLS tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode). l Protocol Type: MPLS l Signaling Type: Static CR l Select Create Reverse Tunnel. Step 3 Set the information in NE List of the MPLS tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode).

Issue 03 (2013-02-20)


374



NOTE

Before configuring MPLS tunnels by means of automatic route computation, create the Layer 2 links.

1.

Select the source NE, sink NE, and transit NE, and adjust the position of the NE on the entire MPLS tunnel. Three methods can be used to select the source, sink, and transit NEs: l Method 1: In Physical Topology at the upper right, right-click an NE and choose Add. l Method 2: In Physical Topology at the upper right, double-click an NE. l Method 3: a.

Click the Add button and then choose NE from the drop-down menu.

b.

Select an NE from the window that is displayed and then click OK.

NOTE

l You can specify the position of an NE on the entire tunnel by setting NE Role or adjust the position of an NE on the entire tunnel by clicking Up or Down. l Select Deploy to deliver the tunnel configuration data to the NEs.

Step 4 Click the Details button and set the information about the tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode).

Issue 03 (2013-02-20)


375



NOTE

l Click Auto-Assign following the Tunnel ID field box. Then, Tunnel ID is automatically allocated. . Select the output l Click the blank cell under Out Interface of an Ingress node and then click port of the ingress node in the list box that is displayed. Use the same method to select the input and output ports of the transit node and the input port of the egress node. l After the output port label is added at the ingress node and transit node, the next-hop address is generated automatically. l Click Auto-Assign Label at lower right of the window. Then, Out Label of the ingress node, Out Label and In Label of the transit node, and In Label of the egress node are allocated automatically. l After you set the parameters of the forward tunnel, the parameters of the reverse tunnel are generated automatically. Therefore, you need not set the parameters of the reverse tunnel manually.

----End

9.4.3.2 Configuring a Static and Bidirectional MPLS Tunnel in End-to-End Mode When creating a static and bidirectional MPLS tunnel in end-to-end mode, you select the source NE, sink NE, or transit NE directly in the physical topology and then complete creation of the unidirectional MPLS tunnel on the NMS.

Prerequisites l


l


l


Procedure Step 1 Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the Create Tunnel window is displayed.

Issue 03 (2013-02-20)


376



Step 2 Set the basic information about the MPLS tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode). l Protocol Type: MPLS l Signaling Type: Static CR l Select Create Bidirectional Tunnel. Step 3 Set the information in NE List of the MPLS tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode).

NOTE

Before configuring MPLS tunnels by means of automatic route computation, create the Layer 2 links.

1.

Select the source NE, sink NE, and transit NE, and adjust the position of the NE on the entire MPLS tunnel. Three methods can be used to select the source, sink, and transit NEs:

Issue 03 (2013-02-20)


377



l Method 1: In Physical Topology at the upper right, right-click an NE and choose Add. l Method 2: In Physical Topology at the upper right, double-click an NE. l Method 3: a.

Click the Add button and then choose NE from the drop-down menu.

b.

Select an NE from the window that is displayed and then click OK.

NOTE

l You can specify the position of an NE on the entire tunnel by setting NE Role or adjust the position of an NE on the entire tunnel by clicking Up or Down. l Select Deploy to deliver the tunnel configuration data to the NEs.

Step 4 Click the Details button and set the information about the tunnel. For details about the parameters, see 10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode).

NOTE

l Click Auto-Assign following the Tunnel ID field box. Then, Tunnel ID is automatically allocated. l Click the blank cell under Out Interface of an Ingress node and then click . Select the output port of the ingress node in the list box that is displayed. Use the same method to select the input and output ports of the transit node and the input port of the egress node. l After the output port is added at the ingress node and transit node, the next-hop address is generated automatically. l After the input port is added at the egress node and transit node, the reverse next-hop address is generated automatically. l Click Auto-Assign Label at lower right of the window. Then, Out Label and Reverse In Label of the ingress node, In Label, Out Label, Reverse In Label and Reverse Out Label of the transit node, and In Label and Reverse Out Label of the egress node are allocated automatically.

----End

9.5 Managing MPLS Tunnels MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. Therefore, it is crucial to properly manage MPLS tunnels. Managing MPLS tunnels involves checking the MPLS tunnel topology, deploying MPLS tunnels, deleting MPLS tunnels, and managing discrete MPLS tunnels.

Issue 03 (2013-02-20)


378



9.5.1 Searching for MPLS Tunnels A complete MPLS tunnel has its source and sink NEs. An MPLS tunnel that is created on a perNE basis, however, is displayed as a discrete tunnel on the NMS. The tunnel search function on the NMS helps convert a discrete MPLS tunnel to a complete tunnel, therefore facilitating tunnel management. This section describes how to search for MPLS tunnels on the NMS.

Prerequisites l

MPLS tunnels have been created on a per-NE basis. For details on how to create an MPLS tunnel on a per-NE basis, see 9.4.2 Configuring an MPLS Tunnel on a Per-NE Basis.

l


Procedure Step 1 Choose Service > Search for IP Service from the main menu. Step 2 In the dialog box that is displayed, set the tunnel discovery policy.

Step 3 Click Start. Step 4 Click Close. ----End

9.5.2 Checking the MPLS Tunnel Topology MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. This section describes how to check the MPLS tunnel topology to learn configuration information about MPLS tunnels, facilitating tunnel management.

Prerequisites l

MPLS tunnels have been created. For details on how to create an MPLS tunnel, see 9.4 Configuring an MPLS Tunnel. NOTE

Before managing an MPLS tunnel that is created on a per-NE basis, you need to search for the MPLS tunnel. For details on how to search for an MPLS tunnel, see 9.5.1 Searching for MPLS Tunnels.

l Issue 03 (2013-02-20)


379



Procedure Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to MPLS and set Signaling Type to Static CR. Then, click Filter. Query all MPLS tunnels that meet the filter conditions. Step 3 Select the MPLS tunnel whose topology information you need to check and click the Topology tab.

Step 4 In the MPLS tunnel topology view, right-click the NE and choose View Real-Time Performance from the shortcut menu to check the real-time running status of the MPLS tunnel. ----End

9.5.3 Duplicating MPLS Tunnels This section describes how to quickly create MPLS tunnels by using the tunnel duplication function of the NMS.

Prerequisites l



l


Procedure Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to MPLS and set Signaling Type to Static CR. Then, click Filter. Query all MPLS tunnels that meet the filter conditions. Step 3 Select an MPLS tunnel to copy, right-click the tunnel, and choose Copy from the shortcut menu. Step 4 In the Copy Tunnel dialog box that is displayed, set parameters for the duplicated MPLS tunnel.

Issue 03 (2013-02-20)


380



Step 5 Click OK. ----End

9.5.4 Deploying MPLS Tunnels After being created on the NMS, MPLS tunnels are stored on the NMS but not immediately deployed to the corresponding NEs. This section describes how to deploy MPLS tunnels from the NMS to the corresponding NEs.

Prerequisites l



l


Procedure Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu. Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to check all undeployed MSPLS tunnels. Step 3 Select one or more MPLS tunnels to be deployed, right-click the MPLS tunnels, and choose Deploy from the shortcut menu.

NOTE

After an MPLS tunnel is successfully deployed, its Deployment Status is Deployed.

----End Issue 03 (2013-02-20)


381



9.5.5 Deleting MPLS Tunnels After being deployed, MPLS tunnels are stored on the NMS and the corresponding NEs. This section describes how to delete MPLS tunnels from the NMS and corresponding NEs.

Prerequisites l



l


Background Information l

After being deleted from the network side, MPLS tunnels are deleted from the NMS only but still stored on the corresponding NEs. In addition, after being deleted from the network side, MPLS tunnels are displayed as discrete tunnels on the NMS.

l

After being deleted from the NE side, MPLS tunnels are deleted from the corresponding NEs only but still stored on the NMS. In addition, after being deleted from the NE side, MPLS tunnels are displayed as undeployed.

Procedure Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to MPLS and set Signaling Type to Static CR. Then, click Filter. Query all MPLS tunnels that meet the filter conditions. Step 3 Select one or more MPLS tunnels that you need to delete, right-click the tunnels. l Choose Delete from the shortcut menu. l Choose Delete from Network Side from the shortcut menu. l Choose Undeploy from the shortcut menu.

NOTE

l After an MPLS tunnel is successfully deleted from the NE side, its Deployment Status is Undeployed. l If an MPLS tunnel has been configured in an MPLS tunnel APS protection group or has been configured with PWE3 services, you need to delete the MPLS tunnel APS protection group or PWE3 services before deleting the MPLS tunnel.

----End Issue 03 (2013-02-20)


382



9.5.6 Managing Discrete MPLS Tunnels MPLS tunnels without source or sink NEs and MPLS tunnels that are deleted from the network side are displayed as discrete tunnels on the NMS. This section describes how to check discrete MPLS tunnels, facilitating tunnel management.

Prerequisites l



l


Procedure Step 1 Choose Service > Tunnel > Manage Discrete Tunnel from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to MPLS and set Signaling Type to Static CR. Then, click Filter. Query all MPLS tunnels that meet the filter conditions. Step 3 Select an MPLS tunnel and click the Hops Information tab. In the tab page, check the port information and label information about the MPLS tunnel.

Step 4 Optional: Select one or more MPLS tunnels and click Delete. ----End

9.6 Configuring MPLS OAM MPLS OAM effectively detects, confirms, and locates the internal defects of an MPLS network, and thus monitors the network performance.

9.6.1 Configuring the MPLS OAM on a Per-NE Basis Configuring MPLS OAM involves the following operations: enabling the OAM status of the MPLS tunnel, setting the MPLS OAM parameters for the MPLS tunnel, enabling the tunnel CV/ FFD detection function, performing an MPLS Tunnel Ping test, and performing an MPLS Tunnel Traceroute test. Issue 03 (2013-02-20)


383



Prerequisites You must be an NM user with NE administrator authority or higher. An MPLS tunnel must be created.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab. Select Enabled from the drop-down list of OAM Status.

Step 3 Set the parameters. For the details about the parameters, see Tunnel OAM Parameters. NOTE

l Detection Packet Period: When Detection Packet Type is set to CV, Detection Packet Period is 1 s and cannot be changed manually. When Detection Packet Type is set to FFD, Detection Packet Period can be set manually. l Reverse Tunnel: After detecting defects, the egress node sends the BDI packets that carry the defect information over the reverse tunnel to the ingress node, so that the ingress node can learn the defect status in time. l When the Node Type of the Unidirectional tunnel is Egress, you can set the SD Threshold and SF Threshold.

Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Step 5 Click Close. Step 6 Optional: Perform the CV/FFD. Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Start CV/FFD from the drop-down menu. Then, the Operation Result dialog box is displayed, indicating that the operation is successful.

NOTE

When the Node Type of the Unidirectional tunnel is Ingress, the CV/FFD can be enabled.

Step 7 Optional: Perform a ping test. Issue 03 (2013-02-20)


384


1.


Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Ping Test from the drop-down menu. Then, the Ping Test dialog box is displayed.

NOTE

When the Node Type of the tunnel is Ingress, you can perform the ping test.

2.

Set the parameters. For details about the parameters, see Ping Test.

3.

Click Start Test to check the ping test result.

Step 8 Optional: Perform an LSP Traceroute test. 1.

Issue 03 (2013-02-20)

Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Traceroute Test from the drop-down menu. Then, the Traceroute Test dialog box is displayed.


385



NOTE

To support the Traceroute test, the Tunnel Type of the tunnel must be Ingress.

2.

Set the parameters. For details about the parameters, see Traceroute Test.

3.

Click Start Test to check the Traceroute test result.

----End

9.6.2 Configuring MPLS OAM in End-to-End Mode Configuring MPLS OAM involves enabling the OAM status of the tunnel, setting the MPLS OAM parameters of the tunnel, enabling the tunnel CV/FFD check, performing MPLS Tunnel ping test, and performing the MPLS Tunnel Traceroute test.

Prerequisites l


l

The MPLS tunnel must be created.

Procedure Step 1 Choose Service > Tunnel > Manage Tunnel from the Main Menu. Step 2 In the Set Filter Criteria dialog box that is displayed, set the filter conditions and then click Filter. Issue 03 (2013-02-20)


386



NOTE

l You can perform filtering by Tunnel Name, Destination IP Address, or Tunnel IP. l You can also perform filtering by other conditions.

Step 3 In Manage Tunnel, select the MPLS tunnel for which the MPLS OAM needs to be configured. Step 4 Right-click the MPLS tunnel and then choose OAM > Enable OAM from the shortcut menu.

Step 5 Right-click the MPLS tunnel and then choose OAM > Configure OAM from the shortcut menu. For details about the parameters, see Tunnel OAM Parameters. Figure 9-2 Unidirectional Tunnel

Issue 03 (2013-02-20)


387



Figure 9-3 Bidirectional Tunnel

NOTE

When you set these parameters, pay attention the following points: l Detection Packet Period(ms): Detection Packet Period(ms) can only be set to 1000ms when Detection Packet Type is CV. l Detection Packet Period(ms) can be set to several values when Detection Packet Type is FFD. To ensure that the MPLS tunnel APS switching time is shorter than 50 ms, set Detection Packet Period (ms) to 3.3 in this example. l Reverse Tunnel: When the egress node detects a defect, it transmits the BDI packet that carries the defect information to the ingress node through the reverse tunnel. Therefore, the ingress node can learn the defect status in time. l When the Node Type of the Unidirectional tunnel is Egress, you can set the SD Threshold and SF Threshold.


9.7 Configuring MPLS Tunnel APS MPLS tunnel APS protection is implemented based on the APS protocol. If MPLS tunnel APS is configured, the services are switched from the working tunnel to the protection tunnel after the working tunnel is faulty.

Issue 03 (2013-02-20)


388



9.7.1 Configuring MPLS Tunnel APS on a Per-NE Basis You can configure MPLS tunnel APS to protect MPLS tunnels. You can configure a 1+1 or 1:1 MPLS tunnel APS protection group. You need to configure MPLS tunnel APS on the source and sink NEs of the MPLS tunnel.

Prerequisites l


l

The working and protection MPLS tunnels must be created.

l

The MPLS OAM of each MPLS tunnel in the protection group must be enabled. NOTE

The protection MPLS tunnel cannot carry any extra services.

Procedure Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration > Packet Configuration > APS Protection Management from the Function Tree. Step 2 Click New. Then, the New Tunnel Protection Group dialog box is displayed.

Step 3 Set the parameters for the MPLS tunnel protection group. Select the working and protection MPLS tunnels. For details about the parameters, see 10.10.1 Parameters for Configuring MPLS Tunnel APS (on a Per-NE Basis). Issue 03 (2013-02-20)


389



l Protection Type: You can set Protection Type to 1+1 or 1:1. l Switching Mode: You can set Switching Mode to Single-Ended or Dual-Ended. When Protection Type is set to 1:1, Switching Mode can be set to Dual-Ended only. l Revertive Mode: You can set Revertive Mode to Non-Revertive or Revertive. If you set Revertive Mode to Revertive, you can specify the WTR time. l Hold-off Time(100ms): The unit is 100 ms. You can set Hold-off Time(100ms) to be an integer from 0 to 100, namely, 0 to 10 seconds.

CAUTION When creating an APS protection group, you need to set Protocol Status to Disabled. Enable the protocol only after the configuration of the APS protection group is complete on the source and sink NEs. Step 4 Click OK. The MPLS tunnel protection group is configured successfully. NOTE

The bandwidth of the protection MPLS tunnel must be higher than the bandwidth of the working MPLS tunnel. To increase the bandwidth of the working MPLS tunnel after the protection group is created, increase the bandwidth of the protection MPLS tunnel first.

Step 5 Refer to Steps 1-4 to configure the protection group on the sink NE. Step 6 Enable the protocol of the MPLS APS protection group. 1.

IN the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration > Packet Configuration > APS Protection Management from the Function Tree.

2.

Right-click a created APS protection group and choose Start Protocol from the shortcut menu.

3.

A dialog box is displayed, indicating that the operation is successful. Protocol Status of the APS protection group changes to Enabled.

----End

9.7.2 Configuring an MPLS Tunnel APS in End-to-End Mode You can configure MPLS tunnel APS to protect the MPLS tunnel. MPLS tunnel APS can be configured as the 1+1 or 1:1 mode. When configuring MPLS tunnel APS, you need to configure MPLS tunnel APS on both the source NE and the sink NE of the MPLS tunnel.

Prerequisites l


l

The MPLS working and protection tunnels must be created.

l

The MPLS OAM of each MPLS tunnel in the protection group must be enabled. NOTE

The protection tunnel should not carry any extra services.

Issue 03 (2013-02-20)


390



Procedure Step 1 Choose Service > Tunnel > Create Protection Group from the Main Menu. Step 2 In Create Protection Group, set Basic Information of the protection group.

Step 3 Click Add at the lower left of the Create Protection Group window. Select the tunnel in Select Tunnel dialog box that is displayed. NOTE

l When configuring MPLS tunnel APS for unidirectional tunnels, you need to select four tunnels, which function as the Forward Working tunnel, Forward Protection tunnel, Backward Working tunnel, and Backward Protection tunnel. l When configuring MPLS tunnel APS for bidirectional tunnels, you need to select two tunnels, which function as the Working tunnel, and Protection tunnel.

Step 4 In the Tunnels field box, specify the tunnel type. For details about the parameters, see 10.10.2 Parameters for Configuring MPLS Tunnel APS (in End-to-End Mode).

NOTE

l Set four unidirectional tunnels to be the Forward Working tunnel, Forward Protection tunnel, Backward Working tunnel, and Backward Protection tunnel. l Set two bidirectional tunnels to be the Working tunnel, and Protection tunnel.

Step 5 Set the MPLS tunnel APS attributes at the lower right of the window. For details about the parameters, see 10.10.2 Parameters for Configuring MPLS Tunnel APS (in End-to-End Mode).

Issue 03 (2013-02-20)


391



NOTE

l When configuring MPLS tunnel APS on a per-NE mode, set Protocol Status to Disabled. Start the protocol only when MPLS tunnel APS is successfully configured at both ends of the MPLS tunnel. l When configuring MPLS tunnel APS in end-to-end mode, set Protocol Status to Enabled.

Step 6 Click OK. The configuration for MPLS tunnel APS is complete. ----End

9.8 Managing MPLS Tunnel APS Protection Groups MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. MPLS tunnel APS provides protection for MPLS tunnels. Therefore, it is crucial to properly manage MPLS tunnel APS protection groups. Managing MPLS tunnel APS protection groups involves automatically discovering, deploying, modifying, and deleting MPLS tunnel APS protection groups.

9.8.1 Automatically Discovering Protection Groups MPLS tunnels are used to transmit PWE3 services and their quality determines transmission stability of PWE3 services. This section describes how to find MPLS tunnel APS protection groups by using the automatic discovery function of the NMS, facilitating protection group management.

Prerequisites l

MPLS tunnel APS protection groups have been created. For details on how to create an MPLS tunnel APS protection group, see 9.7 Configuring MPLS Tunnel APS.

l


Procedure Step 1 Choose Service > Tunnel > Search for Protection Group from the main menu. Step 2 In the dialog box that is displayed, click Add. In the dialog box that is displayed, select the NE for which you need to configure an MPLS tunnel APS protection group and then click OK.

Step 3 Click OK.

Issue 03 (2013-02-20)


392



NOTE

After protection groups are automatically discovered, the NMS displays a dialog box showing the number of found protection groups.

----End

9.8.2 Deploying MPLS Tunnel APS Protection Groups After being created on the NMS, MPLS tunnel APS protection groups are stored on the NMS but not immediately deployed to the corresponding NEs. This section describes how to deploy MPLS tunnel APS protection groups from the NMS to the corresponding NEs.

Prerequisites l


l


Procedure Step 1 Choose Service > Tunnel > Manage Protection Group from the main menu. Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to check all undeployed MPLS tunnel APS protection groups. Step 3 Select one or more MPLS tunnel APS protection groups to be deployed, right-click the protection groups, and choose Deploy from the shortcut menu.

NOTE

After an MPLS tunnel APS protection group is successfully deployed, its Deployment Status is Deployed.

----End

9.8.3 Ranaming an MPLS Tunnel APS Protection Group Basic information about an MPLS tunnel APS protection group can be represented by an appropriate protection group name. This section describes how to change the name of an MPLS tunnel APS protection group.

Prerequisites l

Issue 03 (2013-02-20)

MPLS tunnel APS protection groups have been created. For details on how to create an MPLS tunnel APS protection group, see 9.7 Configuring MPLS Tunnel APS. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

393


l



Procedure Step 1 Choose Service > Tunnel > Manage Protection Group from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to 1 +1. Then, click Filter. Query all MPLS tunnel APS protection groups that meet the filter conditions. Step 3 Select an MPLS tunnel APS protection group whose name you need to change, and then click Modify.

----End

9.8.4 Deleting MPLS Tunnel APS Protection Groups After being deployed, MPLS tunnel APS protection groups are stored on the NMS and the corresponding NEs. This section describes how to delete MPLS tunnel APS protection groups from the NMS and corresponding NEs.

Prerequisites l


l



After being deleted from the network side, MPLS tunnel APS protection groups are deleted from the NMS only but still stored on the corresponding NEs.

l

After being deleted from the NE side, MPLS tunnel APS protection groups are deleted from the corresponding NEs only but still stored on the NMS.

Procedure Step 1 Choose Service > Tunnel > Manage Protection Group from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to 1 +1. Then, click Filter. Query all MPLS tunnel APS protection groups that meet the filter conditions. Step 3 Select one or more MPLS tunnel APS protection groups that you need to delete, right-click the protection groups. l Choose Delete from the shortcut menu. l Choose Delete from Network Side from the shortcut menu. Issue 03 (2013-02-20)


394



l Choose Undeploy from the shortcut menu.

NOTE

After an MPLS tunnel APS protection group is successfully deleted from the NE side, its Deployment Status is Undeployed.

----End

9.9 Operation Tasks for Configuring E-Line Services This topic describes how to configure E-Line services, including UNI-UNI E-Line services, ELine services carried by ports, E-Line services carried by PWs, and E-Line services carried by QinQ links.

9.9.1 Configuring UNI-UNI E-Line Services In the case of the UNI-UNI E-Line services, different users communicate with each other through the equipment. The Ethernet data packets do not pass the network side, but are transparently transmitted on the user side.

Prerequisites l


l

If a port needs to be occupied exclusively, disable the DCN function of the port. For details, see Configuring the DCN Function of a Port.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click New. Then, the New E-Line Service dialog box is displayed.

Issue 03 (2013-02-20)


395



Step 3 Set the parameters in the dialog box. For details about the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis). NOTE

Set Direction to UNI-UNI. You can set several VLAN values in VLANs. Separate consecutive values with "-" and separate inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10". The OptiX OSN 1500 does not support the setting of MTU (bytes).

Step 4 Optional: Click Configure QoS. Then, the Configure QoS dialog box is displayed. Step 5 Optional: Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color for ports. Click OK. Then, the New E-Line Service dialog box is displayed. NOTE

If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s). Alternatively, you can select the QoS policy directly in Policy.

Step 6 Click OK. Then, the Confirm dialog box is displayed. Step 7 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the OAM-related parameters. NOTE

Before setting the OAM-related parameters, you need to configure the MD first.

----End

Issue 03 (2013-02-20)


396



9.9.2 Configuring UNI-NNI E-Line Services Carried by Ports In the case of the UNI-NNI E-Line services carried by ports, the user data is accessed from a UNI and is then sent to an NNI, which the user data occupies exclusively. In this manner, the point-to-point transparent transmission of the user data is realized.

Prerequisites l


l


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click the UNI tab and click New. Then, the New E-Line Service dialog box is displayed.

Step 3 Set the parameters in the dialog box. For details about the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis). NOTE

l Set Direction to UNI-NNI. l Set Bearer Type to Port. l You can set several VLAN values in VLANs. Separate consecutive values with "-" and separate inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10".

Step 4 Optional: Click Configure QoS. Then, the Configure QoS dialog box is displayed. Step 5 Optional: Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color for ports. Click OK. Then, the New E-Line Service dialog box is displayed.

Issue 03 (2013-02-20)


397



NOTE

If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s). You can also select the QoS policy directly in Policy.

Step 6 Click OK. Then, the Confirm dialog box is displayed. Step 7 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the OAM-related parameters. NOTE


----End

9.9.3 Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis In the case of the UNI-NNI E-Line services carried by PWs, the user data is accessed from a UNI and is then sent to an NNI where the user data is carried by a PW. In this manner, the pointto-point transparent transmission of the user data is realized.

Prerequisites l


l

The MPLS tunnel that carries the PWs must be configured.

l


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from Function Tree. Step 2 Click New. Then, the New E-Line Service dialog box is displayed.

Issue 03 (2013-02-20)


398



Step 3 Set the parameters in the dialog box. For details, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis). NOTE

l Set Direction to UNI-NNI. l Set Bearer Type to PW. l You can set several VLAN values in VLANs. Separate consecutive values with "-" and separate inconsecutive values with ",". For example, The VLAN values may be "1,3,5,8-10". l PRI is optional. If packets need to be forwarded based on Port+VLAN+VLAN PRI, set PRI to an integer ranging from 0 to 7. Value 7 represents the highest priority. l Service Tag Role can be set to User or Service. l User: C-VLAN/S-VLAN tags of packets are used as user VLAN tags, and are processed when the packets are forwarded. l Service: C-VLAN/S-VLAN tags of packets are used as service VLAN tags, and are not processed when the packets are forwarded. l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set Protection Type to PW APS. In this case, you need to configure both the service PW and protection PW to implement MPLS PW APS protection.

Step 4 Click Configure PW. Then, the Configure PW dialog box is displayed. In the dialog box, set the PW-related parameters.

Issue 03 (2013-02-20)


399



NOTE

l You can configure the protection PW only if Protection Type is set to PW APS. l PW Type can be set to Ethernet or Ethernet Tagged Mode. l Ethernet: C-VLAN/S-VLAN tags of packets are encapsulated into PWs without changes, and transparently transmitted to downstream sites. l Ethernet Tagged Mode: A VLAN tag specified by Request VLAN is added to packets. l Set other PW-related parameters according to the planning information.

Step 5 Click OK to close the Configure PW dialog box. Step 6 Click Configure QoS. Then, the Configure QoS dialog box is displayed. Step 7 In the UNI tab, set Policy, Default Forwarding Priority, and Default Packet Relabeling Color for the ingress direction. Step 8 Click OK. Then, the Confirm dialog box is displayed. Step 9 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the OAM-related parameters. NOTE


----End

9.9.4 Configuring E-Line Services Carried by PWs in End-to-End Mode In the case of a UNI-NNI E-Line service carried by PWs, the user data is received by a UNI and is then sent to a PW over an NNI. In this manner, point-to-point transparent transmission of the user data is achieved. This topic describes how to configure the source node, sink node, and PW attributes of UNI-NNI E-Line services carried by PWs on a GUI of the NMS, therefore quickly completing the E-Line service configuration.



400



l


l

If a port needs to be occupied exclusively, you need to disable the DCN function of the port. For details, see Configuring the DCN Function of a Port.

Procedure Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu. Step 2 Set the attributes. For details about the parameters, see 10.3.2 E-Line Service Parameters (Configuration in End-to-End Mode).

NOTE

l You can configure the E-Line service according to the service template. That is, you can select a template or create a service template in the Service Template field. l Set Service Type to ETH. l For rules of setting Protection Type, refer to descriptions about PW protection.

Step 3 Configure the source NE and sink NE of the PWE3 service. For details about the parameters, see 10.3.2 E-Line Service Parameters (Configuration in End-to-End Mode). NOTE

The configuration method is the same for the sink NE and source NE. Therefore, only the example for configuring the source NE is provided as follows.

1.

Under Node List, click Configure Source and Sink. Then, a dialog box is displayed.

2.

Select a source NE from Physical Topology on the left. Select the service access port in the pane on the right and set the associated parameters.

NOTE

l Priority Type is optional. If packets need to be forwarded based on Port+VLAN+VLAN PRI, set Priority Type to 802.1Q. l Priority field is optional. If packets need to be forwarded based on Port+VLAN+VLAN PRI, set Priority field to an integer ranging from 0 to 7. Value 7 represents the highest priority.

Issue 03 (2013-02-20)


401


3.

After setting the parameters, click Add Node.

4.

Refer to Step b and Step c and configure the sink NE.

5.

Click OK.


NOTE

l To configure the source and sink NEs of the PWE3 service, you can also double-click the source and sink NEs in Physical Topology and then set the SAI attributes in the dialog box that is displayed. l When the request VLAN function is enabled for Ethernet services carried by PWs, the TPIDs in the request VLAN tags of the Ethernet services are the same on the source and sink NEs. l When Service Tag is Service and PW Type is Ethernet Tagged Mode, the TPID of the port is the same as the TPID of the NE. Set the TPID of the port first and then the TPID of the NE.

Step 4 Optional: Under Node List, click Configure PW Switch Node to add the switching NE between the source and sink NE. Step 5 Optional: Click Service Topology to check the configured service topology at upper right. Step 6 Under PW, set the basic attributes of the PWs. NOTE

l Double-click the blank box under Forward Tunnel and Reverse Tunnel, click the tunnel that carries the PWs from the list.

, and then select

l The PW ID can be Auto-Assign.

Step 7 Click Detail and then set the advanced attributes of the E-Line service carried by the PW. For details about the parameters, see 10.3.2 E-Line Service Parameters (Configuration in Endto-End Mode). Step 8 Optional: Click the SAI QoS tab and set the QoS of the service access port. Step 9 Optional: Click the PW QoS tab and set the QoS of the PW. Step 10 Optional: Click the Advanced PW Attribute tab and set the parameters associated with the PW. Step 11 Click OK. ----End

9.9.5 Creating UNI-NNI E-Line Services Carried by QinQ Links In the case of the UNI-NNI E-Line services carried by the QinQ link, the user data is accessed from a UNI and is then sent to an NNI where the user data is carried by a QinQ link. Multiple VLANs on the user network are encapsulated in QinQ mode into one VLAN on the transport network. In this manner, the VLAN resources on the transport network are saved.

Prerequisites l


l

The QinQ link must be created for the NNIs.

l

The services carried by the QinQ link do not support the creation of any maintenance point (MP).

Issue 03 (2013-02-20)


402



Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click the UNI tab and then click New. Then, the New E-Line Service dialog box is displayed. Step 3 Set the parameters in the dialog box. For details of the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis).

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 4 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 5 Click the QoS tab and click the QinQ Link tab. Step 6 Select the QoS policy for the ingress and egress directions of the QinQ link. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. NOTE

Before selecting the policy, ensure that the policy is already created. If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s).

Step 7 Click Close, ----End

9.10 Operation Task for Configuring E-LAN Services This topic describes how to configure E-LAN services, including E-LAN services carried by ports, E-LAN services carried by PWs, and E-LAN services carried by QinQ links. Issue 03 (2013-02-20)


403



9.10.1 Configuring E-LAN Services Carried by Ports You can configure various types of E-LAN services by configuring the UNIs and NNIs on the NMS. You can configure the services on the NNI to be carried by ports on the NMS.

Prerequisites l


l


l


l

If a QoS policy is required for configuring the QoS, you must create the QoS policy first.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service Name, and MTU (bytes) in the dialog box. For details about the parameters, see 10.4.1 E-LAN Service Parameters (Configuration on a Per-NE Basis).

NOTE

l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table items are generated through MAC address self-learning. You can also configure the static MAC address forwarding table items manually. When Self-Learning MAC Address is set to Disabled, the bridge does not support MAC address self-learning, and you can configure the static MAC address forwarding table items only manually. l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning. All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding table. IVL indicates independent VLAN learning. The forwarding tables for different VLANs are independent from each other. The MAC address forwarding tables for different VLANs, however, are permitted to contain the same MAC addresses. l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed service packets without any VLAN tags.

Issue 03 (2013-02-20)


404



Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Then, click Close. Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is displayed. For details about the parameters, see 10.4.3 UNI Parameters. Step 5 In the Available Ports list, select the port. Then, click Ports list.

to add the port to the Selected

Step 6 In the Selected Ports list, set VLANs of the port, and then click OK. Step 7 Optional: Click the NNI tab. Click the Port tab. Refer to Steps Step 4- Step 6 to add and configure the NNI port. Then, click OK. For details about the parameters, see 10.3.4 NNI Parameters. Step 8 Click the Split Horizon Group tab and click New. Then, the New Split Horizon Group dialog box is displayed. For details about the parameters, see 10.4.5 Split Horizon Group. Step 9 Set the split horizon group ID and add the port that needs to be added into the split horizon group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box is displayed, indicating 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 Address Detection Lower Threshold(%). For details about the parameters, see 10.4.6 MAC Address Learning Parameters. NOTE

Address Detection Upper Threshold(%) and Address Detection Lower Threshold(%) indicate the upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.

Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames and multicast frames. The default value is broadcast. For details about the parameters, see 10.4.7 Unknown Frame Processing. Step 13 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 14 Optional: Click the QoS tab. Set the QoS parameters. Step 15 Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color of the port. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Then, click Close. Step 16 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and Egress Interface. For details about the parameters, see 10.4.8 Static MAC Address. NOTE

The VLAN ID can be set only when MAC Address Learning Mode is set to IVL.

Step 17 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the OAM-related parameters. For details about the parameters, see 10.3.5 Maintenance Association and 10.3.6 MEP Point. Issue 03 (2013-02-20)


405



NOTE


----End

9.10.2 Creating E-LAN Services Carried by PWs on a Per-NE Basis You can configure various types of E-LAN services by configuring the UNIs and NNIs on the NMS. You can configure the services on the NNI to be carried by PWs on the NMS.

Prerequisites l


l


l

The MPLS tunnel that carries the PWs must be created.

l


l


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service Name and MTU (bytes) in the dialog box. For details about the parameters, see 10.4.1 E-LAN Service Parameters (Configuration on a Per-NE Basis).

Issue 03 (2013-02-20)


406



NOTE

l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table items are generated through MAC address self-learning. You can also configure the static MAC address forwarding table items manually. When Self-Learning MAC Address is set to Disabled, the bridge does not support MAC address self-learning, and you can configure the static MAC address forwarding table items only manually. l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning. All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding table. IVL indicates independent VLAN learning. The forwarding tables for different VLANs are independent from each other. The MAC address forwarding tables for different VLANs, however, are permitted to contain the same MAC addresses. l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed service packets without any VLAN tags. Currently, S-Awared is not supported. l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set Protection Type to PW APS. In this case, you need to configure both the service PW and protection PW to implement MPLS PW APS protection. l When MAC Address Withdrawal is set to Disabled, MAC Address Withdrawal cannot be performed for E-LAN services carried by static PWs.

Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is displayed. For details about the parameters, see 10.4.3 UNI Parameters. Step 5 In the Available Ports list, select the port. Then, click Ports list.


Step 6 In the Selected Ports list, set VLANs of the port, and then click OK. Step 7 Click the NNI tab. Click the PW tab. Click New and set the parameters related to the PW. Then, click OK. For details about the parameters, see 10.3.4 NNI Parameters. Step 8 Click the Split Horizon Group tab. Click New. Then, the New Split Horizon Group dialog box is displayed. For details about the parameters, see 10.4.5 Split Horizon Group. Step 9 Set the split horizon group ID, and add the port that needs to be added into the split horizon group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. 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 Address Detection Lower Threshold(%). For details about the parameters, see 10.4.6 MAC Address Learning Parameters. NOTE


Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Issue 03 (2013-02-20)


407



Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames and multicast frames. The default value is broadcast. For details about the parameters, see 10.4.7 Unknown Frame Processing. Step 13 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 14 Optional: Click the QoS tab. Set the QoS parameters. Step 15 Optional: In the QoS tab, click the PW. Set EXP and LSP Mode. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. NOTE

If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s). You can also select the QoS policy directly in Policy. Before selecting a policy, you need to create the policy first.

Step 16 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and Egress Interface. For details about the parameters, see 10.4.8 Static MAC Address. NOTE


Step 17 Optional: Click the Maintenance Association tab and the MEP Point tab separately to set the OAM-related parameters. For details about the parameters, see 10.3.5 Maintenance Association and 10.3.6 MEP Point. NOTE


----End

9.10.3 Configuring E-LAN Services Carried by PWs in End-to-End Mode This section describes how to create E-LAN services carried by PWs in end-to-end mode.

Prerequisites l


l


l


Procedure Step 1 Choose Service > VPLS Service > Create VPLS Service from the Main Menu. Step 2 Set the parameters in the Basic Attribute tab. For details about the parameters, see 10.4.2 ELAN Service Parameters (Configuration in End-to-End Mode).

Issue 03 (2013-02-20)


408



Step 3 Select the VPLS service nodes. l Method 1: 1.

In "Node List", choose Add > NPE.

2.

In the dialog box that is displayed, select the NEs on which you need to create the VPLS services.

l Method 2: 1.

In Physical Topology, right-click the NEs on which you need to create the VPLS services and choose NPE from the shortcut menu.

Step 4 In "Node List", select an NE and click Detail. Click the VSI Configuration tab and set the VSI parameters in the tab. For details about the parameters, see 10.4.2 E-LAN Service Parameters (Configuration in End-to-End Mode).

Issue 03 (2013-02-20)


409



NOTE

You need to set VSI attributes for all the NEs in "Node List".

Step 5 Click the PW Configuration tab and configure the PWs for carrying the services in the tab. NOTE

l If you set Networking Mode to Full-Mesh VPLS, the NMS automatically creates the PWs between NEs but you need to create the tunnel for carrying the PWs. l If you set Networking Mode to Customized, select all the NEs in "Node List". Then, click Create, and select Bidirectional PW or Unterminated PW as required. In the dialog box that is displayed, set the PW information.

Step 6 Configure the service access ports. 1.

In "Node List", select an NE and click the SAI Configuration tab.

2.

Click Create. In the dialog box that is displayed, select the ports to be added, set the relevant parameters, and click OK.

3.

Click the SAI QoS tab. Select a port. Click Configure and select Global QoS policy Template or QoS CAR Template. In the dialog box that is displayed, set the QoS parameters. NOTE

l Before you set Global QoS policy Template, specify Global QoS Policy. l When setting the QoS parameters of a service access port, you can directly select the service port and set the global QoS policy or QoS CAR parameter.

Step 7 Select Deploy and then click OK. NOTE

l If you deselect Deploy, the service configuration is saved only on the NMS. If you select Deploy, the service configuration is saved on the NMS and deployed to the NEs. By default, Deploy is selected. l If Deploy and Enable are selected, services on the NE side are available only after the services are activated.

----End

9.10.4 Configuring E-LAN Services Carried by QinQ Links You can configure various types of E-LAN services by configuring the UNIs and NNIs on the NMS. You can configure the services on the NNI to be carried by QinQ links on the NMS.

Prerequisites l


l


l


l

If the services need to be carried by a QinQ link, you must configure a QinQ link first.

l


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Issue 03 (2013-02-20)


410



Step 2 Click New. Then, the New E-LAN Service dialog box is displayed. Set Service ID, Service Name, and MTU (bytes) in the dialog box. For details about the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis).

NOTE

l Self-Learning MAC Address can be set to Enabled or Disabled. When Self-Learning MAC Address is set to Enabled, the bridge supports MAC address self-learning and the forwarding table items are generated through MAC address self-learning. You can also configure the static MAC address forwarding table items manually. When Self-Learning MAC Address is set to Disabled, the bridge does not support MAC address self-learning, and you can configure the static MAC address forwarding table items only manually. l MAC Address Learning Mode can be set to SVL or IVL. SVL indicates shared VLAN learning. All VLANs share a MAC address forwarding table. Each MAC address is unique in the forwarding table. IVL indicates independent VLAN learning. The forwarding tables for different VLANs are independent from each other. The MAC address forwarding tables for different VLANs, however, are permitted to contain the same MAC addresses. l Tag Type can be set to C-Awared, S-Awared, or Tag Transparent. C-Awared corresponds to the accessed service packets with one C-VLAN tag. S-Awared corresponds to the accessed service packets with one C-VLAN tag and one S-VLAN tag. Tag Transparent corresponds to the accessed service packets without any VLAN tags. Currently, S-Awared is not supported.

Step 3 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 4 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is displayed. For details about the parameters, see 10.4.1 E-LAN Service Parameters (Configuration on a Per-NE Basis). Step 5 In the Available Ports list, select the port. Then, click Ports list.


Step 6 In the Selected Ports list, set VLANs of the port, and then click OK. Step 7 Click the NNI tab. Step 8 Click the QinQ Link tab. For details about the parameters, see 10.3.4 NNI Parameters. Step 9 Click Add. Then, the QinQ Link Management window is displayed. Step 10 Select a QinQ link ID and click OK. Issue 03 (2013-02-20)


411



Step 11 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close, Step 12 Click the Split Horizon Group tab and click New. Then, the New Split Horizon Group dialog box is displayed. Step 13 Set the split horizon group ID, and add the port that needs to be added into the split horizon group to the Selected Interfaces area box. Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 14 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min), Address Table Specified Capacity, Address Detection Upper Threshold(%), and Address Detection Lower Threshold(%). For details about the parameters, see 10.4.6 MAC Address Learning Parameters. NOTE


Step 15 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 16 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames and multicast frames. The default value is broadcast. For details about the parameters, see 10.4.7 Unknown Frame Processing. Step 17 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. Step 18 Optional: Click the QoS tab. Set the QoS parameters. Step 19 Click the QinQ Link tab. Enable the bandwidth limit and select the QoS policy for the ingress and egress directions of the QinQ link. Click Apply. The Operation Result dialog box is displayed, indicating that the operation is successful. Click Close, NOTE

Before selecting a policy, you need to create the policy first. If you set Bandwidth Limit to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s).

Step 20 Optional: Click the Static MAC Address tab. You can set VLAN ID, MAC Address, and Egress Interface. For details about the parameters, see 10.4.8 Static MAC Address. NOTE




----End

Issue 03 (2013-02-20)


412



9.11 Configuring E-AGGR Services This topic describes how to configure E-AGGR services, including E-AGGR services carried by ports and E-AGGR services carried by PWs.

9.11.1 Configuring E-AGGR Services Carried by Ports The creation of an E-AGGR service can be complete in one interface of the NMS. The equipment supports aggregation of services from multiple ports to one port and aggregation of services carried by multiple PWs on one NNI to one UNI.

Prerequisites l


l


l


Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree. Step 2 Click New. Then, the New E-AGGR Service dialog box is displayed, Set Service ID, Service Name and MTU (bytes). For details about the parameters, see 10.5.1 E-AGGR Service Parameters (on a Per-NE Basis). Step 3 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is displayed. For details about the parameters, see 10.5.3 UNI Parameters. Step 4 In the Available Port list, select the port. Then, click Port list.


NOTE

The port where the E-AGGR service is configured does not support the S-Aware attribute.

Step 5 In the Selected Port list, set 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 sink end can be set. Otherwise, the E-AGGR service cannot be correctly configured.

Step 6 Click the NNI tab. Click the Port tab. Refer to Steps Step 3-Step 5 to add and the NNIs. Then, click OK. For details about the parameters, see 10.5.4 NNI Parameters. Step 7 Select VLAN Forwarding Table Item. Click New. Then, the New VLAN Forwarding Table Item dialog box is displayed. Set the VLAN forwarding attributes. Then, click OK. For details about the parameters, see 10.5.5 VLAN Forwarding Table Item.

Issue 03 (2013-02-20)


413



NOTE

The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN Forwarding Table Item from each source port to sink port.

Step 8 Click OK. Then, the Confirm dialog box is displayed. Close the dialog box. Step 9 Optional: Click the QoS tab. Set the QoS parameters. Step 10 Click the UNI tab. Set Default Forwarding Priority and Default Packet Relabeling Color of the port. NOTE




----End

9.11.2 Creating E-AGGR Services Carried by PWs on a Per-NE Basis On the NMS, the creation of an E-AGGR service can be complete in one interface. The equipment supports the multipoint-to-point service aggregation, and supports the service aggregation from the NNI carried by multiple PWs to one UNI port.

Prerequisites l


l


l


l

If a port needs to be exclusively used, disable the DCN function of the port. For details, see Configuring the DCN Function of a Port.

Issue 03 (2013-02-20)


414



Procedure Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > Ethernet Service Management > E-AGGR Service from the Function Tree. Step 2 Click New. Then, the New E-AGGR Service dialog box is displayed. Set Service ID, Service Name and MTU (bytes). For details about the parameters, see 10.5.1 E-AGGR Service Parameters (on a Per-NE Basis). Step 3 Click the UNI tab and click Configuration. Then, the Configure Port dialog box is displayed. For details about the parameters, see 10.5.3 UNI Parameters. Step 4 In the Available Port list, select the port and click Port list.


NOTE

The port of the E-AGGR service does not support the S-Aware attribute.

Step 5 In the Selected Port list, set Location and VLANs of the port, and then click OK. NOTE

Location can be set to one or multiple source ends or one sink end. The E-AGGR service cannot be correctly configured if Location is set to multiple sink ends.

Step 6 Click the NNI tab. Click the PW tab. Click New and set the related parameters of the PW. Then, click OK. For details about the parameters, see 10.5.4 NNI Parameters. NOTE

l Set PW Signaling Type to Static. l Set PW Type to Ethernet or Ethernet Tagged Mode. l If the MPLS tunnel carrying the PWs is not configured with MPLS tunnel APS, you can set Protection Type to PW APS. In this case, you need to configure both the service PW and protection PW to implement MPLS PW APS protection.

Step 7 Optional: Select VLAN Forwarding Table Item and click New. Then, the New VLAN Forwarding Table Item dialog box is displayed. Set the VLAN forwarding attributes in the dialog box. Then, click OK. For details about the parameters, see 10.5.5 VLAN Forwarding Table Item.

NOTE

The services are forwarded based on VLAN tags. Hence, the VLAN forwarding attributes need to be set for the source and sink ports in VLAN Forwarding Table Item.

Issue 03 (2013-02-20)


415



Step 8 Click OK. Then, the Confirm dialog box is displayed. Close the dialog box. Step 9 Optional: Click the QoS tab. Set the QoS parameters. Step 10 Optional: In the QoS tab, click the PW and set EXP and LSP Mode. NOTE




----End

9.11.3 Creating E-AGGR Services Carried by PWs in End-to-End Mode This topic describes how to create an E-AGGR service carried by PWs in end-to-end mode.

Prerequisites l


l


l

If a port needs to be exclusively used, disable the DCN function of the port. For details, see Configuring the DCN Function of a Port.

Procedure Step 1 Choose Service > E-AGGR Service > Create E-AGGR Service from the Main Menu. Step 2 Set basic attributes for the E-AGGR service. For details about the parameters, see 10.5.2 Parameters for Configuring E-AGGR Services (End-to-End Mode).

Step 3 Configure source/sink NEs and ports that receive services for the E-AGGR service. For details about the parameters, see 10.5.2 Parameters for Configuring E-AGGR Services (End-toEnd Mode). 1.

Issue 03 (2013-02-20)

Click the Node List tab, and choose Add > Source or Add > Sink. Then, a dialog box is displayed.


416



NOTE

l Location can be set to Source or Sink. You can set multiple source ports but only one sink port. If multiple sink ports are set, the configuration of the E-AGGR service will fail. l For an unterminated E-AGGR service (for example, the PE at one end is not managed by the U2000), choose Add > Unterminated to create source and sink NEs.

2.


3.

Configure boards and ports that receive services, and set attributes for the ports in SAI Configuration. Then, click OK.

Step 4 Set basic attributes for the PWs that carry the E-AGGR services. For details about the parameters, see 10.5.2 Parameters for Configuring E-AGGR Services (End-to-End Mode). Click the PW tab, and set basic attributes for the PWs.

Step 5 Optional: Configure the VLAN forwarding table. For details about the parameters, see 10.5.2 Parameters for Configuring E-AGGR Services (End-to-End Mode). 1.

Click the VLAN Forwarding Table tab.

2.

Click Add to set parameters.

Step 6 Optional: Configure bandwidths for the E-AGGR service. In Service Bandwidth, configure bandwidths for the E-AGGR service. Step 7 Optional: Set advanced attributes for the E-AGGR service. 1.

Click Advanced.

2.

In SAI QoS on the right, set QoS parameters for the ports that receive services.

3.

In PW QoS on the right, set QoS parameters for the PWs.

4.

In Advanced PW Attribute on the right, set advanced attributes for the PWs.

Step 8 Select Deploy and Enable in the lower left corner. NOTE

After Deploy is selected, the service configuration data is saved on the NMS side and deployed to the NE side. If you do not select Deploy, the service configuration data is saved on the NMS side but is not deployed to the NE side.

Step 9 Click OK. ----End Issue 03 (2013-02-20)


417



9.12 Configuring Transit Nodes for Ethernet Services On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for an Ethernet service.

9.12.1 Configuring Transit NEs for Ethernet Services Carried by Ports On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for an Ethernet service carried by ports.

Prerequisites l

For the Ethernet service carried by ports, Port Mode is set to Later 2 and Encapsulation Type is set to 802.1Q.

l


l

The Ethernet service carried by ports exclusively occupies the NNI ports on its transit NEs. The DCN function is disabled for the NNI ports. For the method of disabling the DCN function for a port carrying Ethernet services, see Configuring the DCN Function of a Port.

Procedure Step 1 In the NE Explorer, select the required NE from the root list, and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click New. Then, the New E-Line Service dialog box is displayed.

Issue 03 (2013-02-20)


418



Step 3 Set parameters of transit NEs for an Ethernet service. For details about the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis). NOTE

l For transit NEs for an Ethernet service, set Direction to UNI-UNI. l For transit NEs for an Ethernet service, you do not need to set QoS parameters.

Step 4 Click OK. Step 5 Click Query to check the configured Ethernet service. ----End

9.12.2 Configuring Transit NEs for Ethernet Services Carried by PWs On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for an Ethernet service carried by PWs.

Background Information For transit NEs of an Ethernet service carried by PWs, you only need to configure MPLS tunnels whose Node Type is Transit. For details on how to configure an MPLS tunnel, see 9.4 Configuring an MPLS Tunnel.

Issue 03 (2013-02-20)


419



9.12.3 Configuring Transit NEs for Ethernet Services Carried by QinQ Links On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for an Ethernet service carried by QinQ links.

Prerequisites l

For the Ethernet service carried by QinQ links, Port Mode is set to Later 2 and Encapsulation Type is set to QinQ.

l


l

The Ethernet service carried by QinQ links exclusively occupies the NNI ports on its transit NEs. The DCN function is disabled for the NNI ports. For the method of disabling the DCN function for a port carrying Ethernet services, see Configuring the DCN Function of a Port.

Procedure Step 1 In the NE Explorer, select the required NE from the root list, and choose Configuration > Packet Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click New. Then, the New E-Line Service dialog box is displayed.

Step 3 Set parameters of transit NEs for an Ethernet service. For details about the parameters, see 10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis). Issue 03 (2013-02-20)


420



NOTE

l For transit NEs for an Ethernet service, set Direction to UNI-UNI. l For transit NEs for an Ethernet service, you do not need to set QoS parameters.

Step 4 Click OK. Step 5 Click Query to check the configured Ethernet service. ----End

9.13 Operation Tasks for Configuring CES Services This topic describes the operation tasks for configuring CES services in per-NE mode and endto-end mode on the NMS.

9.13.1 Creating UNI-UNI CES Services on a Per-NE Basis When creating a CES service on a per-NE basis, you need to set associated service attributes for the source node and the sink node separately.

Prerequisites l


l

The CES ports must be configured correctly.

Procedure Step 1 In the NE Explorer, select an NE, and then choose Configuration > Packet Configuration > CES Service Configuration from the Function Tree. Step 2 Click New. Set the CES service parameters in the Create CES Service dialog box that is displayed. For details about the parameters, see 10.7.1 Basic Configuration Parameters (UNIUNI).

Issue 03 (2013-02-20)


421



NOTE

l Set Mode to UNI-UNI. l When the CES service mode is UNI-UNI, Configure PW is unavailable. l Set the other parameters according to the network planning information.

Step 3 After the setting, click OK. ----End

9.13.2 Creating UNI-NNI CES Services on a Per-NE Basis If you create a CES service on a per-NE basis, you need to create relevant attributes of the service separately on the source and sink nodes of the service. After the CES service is created, the corresponding PW is automatically created.

Prerequisites l


l

The CES port must be configured. The port mode must set to Layer 1. The frame format must be set if the CES port is a PDH port.

l


Procedure Step 1 In the NE Explorer, select an NE, and then choose Configuration > Packet Configuration > CES Service Configuration from the Function Tree. Step 2 Click New. Set the CES service parameters in the Create CES Service dialog box that is displayed. For details about the parameters, see 10.7.2 Basic Configuration Parameters (UNINNI). Issue 03 (2013-02-20)


422



NOTE

l Set Mode to UNI-NNI. l Set the other parameters according to the network planning information.

Step 3 Click Configure PW. Set the PW parameters in the Create PW dialog box that is displayed. Step 4 Click the General Attributes tab and set the PW parameters of the CES service. For details about the parameters, see 10.7.2 Basic Configuration Parameters (UNI-NNI).

NOTE

l Set PW Signaling Type to Static. l Set the other parameters according to the network planning information.

Step 5 Click the Advanced Attributes tab and set the advanced attributes of the CES service. For details about the parameters, see 10.7.4 Advanced Attributes (UNI-NNI).

Issue 03 (2013-02-20)


423



NOTE

l The packet loading time needs to be set to the same value for the NEs at both ends. l The jitter compensation buffering time needs to be more than two times of the packet loading time.

Step 6 After setting the parameters, click OK. Step 7 Click OK in the Create CES Service dialog box that is displayed. Step 8 Navigate to the NE Explorer of the opposite NE and configure the reverse service according to Step 1 to Step 9. ----End

9.13.3 Creating a CES Service in End-to-End Mode This topic describes how to create CES service channels for transmitting TDM signals in endto-end mode. You can configure the source node, sink node, and PW attributes of a CES service on a GUI of the NMS, therefore quickly completing the CES service configuration.

Prerequisites l


l

The CES service port must be configured. The port mode must set to Layer 1. The frame format and frame mode must be set.

l


Context You need to set the frame format for the UNI port that carries the CES service to be the same as the service encapsulation format. If the encapsulation format of the CES service is CESoPSN, you can set the frame format of the UNI port to CRC-4 multiframe (recommended value) or Double frame. If the encapsulation format of the CES service is SAToP, set frame format of the UNI port to unframed.

Procedure Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the Main Menu. Issue 03 (2013-02-20)


424



Step 2 Set the parameters on the General Attributes tab page. For details about the parameters, see 10.7.5 Parameters for Configuring CES Services (End-to-End Mode).

NOTE

l You can configure the CES service according to the service template. That is, you can select a service template or create a service template in the Service Template field. l Set Service Type to CES. l Set Protection Type to Protection-Free.

Step 3 Select the source and sink NEs of the service. NOTE

The configuration method is the same for the sink NE, source NE, and transit NE. Therefore, only the example for configuring a source NE is provided as follows.

1.


2.

Select a source NE from Physical Topology on the left. Then, the selected NE is displayed in the upper right pane.

3.

All slots and available boards on the NE are displayed in Basic Slot pane. Select the appropriate board according to the service type.

4.

In SAI Configuration, set High TimeSlot and Low TimeSlot.

5.

In SAI Configuration, set the SAI attribute of the CES access port. Click Add Node. Then, the added source and sink NEs are displayed at the bottom of the pane. Then, click OK.

Issue 03 (2013-02-20)


425



Step 4 Optional: Click Configure Source And Sink and then select Unterminated on the left. Set the LSR ID of the unterminated node and click Add Node. Then, the added unterminated source and sink nodes are displayed at the bottom. Then, click OK. NOTE

Unterminated: On a network, if the equipment at one end of a service can be managed by the U2000, and the equipment at the other end of the service is from another vendor and cannot be managed by the U2000, select Unterminated to set the LSR ID of the opposite end of the service.

Step 5 Optional: Click Configure PW Switch Node to add working and protection switching NEs between the source NE and the sink NE.

Issue 03 (2013-02-20)


426



Step 6 Set parameters of the source and sink NEs that are displayed in Node List. To view the topology of a configured service, click the Service Topology tab in the upper-right area. Step 7 Click the PW tab at lower left to set basic attributes of the PW. For details about the parameters, see 10.7.5 Parameters for Configuring CES Services (End-to-End Mode).

NOTE

l The PW ID can be automatically allocated. l Signaling Type can be set to Static automatically or manually. l Forward Label and Reverse Label can be allocated automatically and manually. l Forward Type and Reverse Type support Static Binding. Forward Tunnel needs to be specified manually. l You can also set Forward Tunnel and Reverse Tunnel in Service Topology at upper right. Select the tunnel service between the source NE and the sink NE, select Select Forward Tunnel or Select Reverse Tunnel, and select the tunnel for static binding.

Step 8 Optional: Click Detail. Then, associated information is displayed in the pane at lower right. Issue 03 (2013-02-20)


427



Step 9 Optional: Click the Advanced PW Attribute tab and set the parameters associated with the PW. For details about the parameters, see 10.7.5 Parameters for Configuring CES Services (End-to-End Mode).

NOTE

l The packet loading time needs to be set to the same value for the NEs at both ends. l The jitter compensation buffering time needs to be more than two times of the packet loading time.

Step 10 Select Deploy and then click OK. NOTE

l In this case, If you select Enable, the service configuration is saved on the NMS and deployed to the NEs. If you deselect Deploy, the service configured is saved only on the NMS but not deployed to NEs. By default, Deploy is selected. l When Deploy and Enable are selected, the NE-side tunnel is available only after the tunnel is enabled.

----End

Subsequent Operation After the service is created successfully, the service is displayed in the PWE3 service management window.

9.14 Configuring Transit NEs for CES Services On a live data network, an Ethernet service is added to its source NE, passed through on its transit NEs, and dropped from its sink NE. This section describes how to configure transit NEs for a CES service.

Background Information For transit NEs of a CES service, you only need to configure MPLS tunnels whose Node Type is Transit. For details on how to configure an MPLS tunnel, see 9.4 Configuring an MPLS Tunnel.

9.15 Configuring ATM PWE3 Services This section describes the operation tasks for configuring ATM PWE3 services in per-NE mode and end-to-end mode on the NMS.

9.15.1 Configuring ATM Interfaces By using the E1 board or STM-1 ATM board, the OptiX OSN equipments can receive ATM services on the E1/VC-12, fractional E1, or STM-1 level. Specifically, one E1 channel can carry multiple fractional E1 services. Certain timeslots of the 32 timeslots in an E1 channel can be allocated for the CES services and the others for the ATM services. In this manner, resources are saved and expenditure is cut.


You must be an NM user with NE operator authority or higher. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

428


l


The DCN function of the port that carries ATM IMA services is disabled.

Background Information For the OptiX OSN equipments, Frame Mode of the packets at the PDH interface or SDH interfaces can be 30-timeslot or 31-timeslot. l

When Frame Mode is set to 30, timeslots 1-15 and 17-31 of an E1 frame are used to transport service data.

l

When Frame Mode is set to 31, timeslots 1-31 of an E1 frame are used to transport service data.

When creating an IMA group of the fractional E1 level, create a serial port of the 64K Timeslot level. An IMA group of the E1/VC12 level can be directly created.

Procedure l

Use an E1 board to carry ATM IMA services. – Configure an interface at the Fractional E1 level.

Issue 03 (2013-02-20)

1.

In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree.

2.

In the General Attributes tab, select E1 board. Set the Port Mode to Layer 1, and click Apply.

3.

Click Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Then, click Apply.

4.

Choose Configuration > Packet Configuration > Interface Management > Serial Interface from the Function Tree. Click New in the General Attributes tab, and the New Serial Interface dialog box is displayed.

5.

In the New Serial Interface dialog box, set the Level, Used Board, Used Port, and 64K Timeslot fields, and then click OK. Create serial interfaces of E1 board.


429



6.

Select the created serial interfaces, set Port Mode to Layer 2, and then click Apply.

7.

Choose Configuration > Packet Configuration > Interface Management > ATM IMA Management from the Function Tree. Then, click Configuration in the Binding tab, and the Bound Path dialog box is displayed.

8.

Select the bound board and port, select Fractional E1 for the Level field, and select Available Resources. Then, click Selected Bound Paths.

9.

to add the bound board and port to

Click Apply.

10. In the IMA Group Management tab, select the IMA group. Set the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode according to the network planning. Then, set IMA Protocol Enable Status to Enabled. Click Apply. 11. On the ATM Interface Management tab, click the IMA group. Then, set the parameters such as Port Type, ATM Cell Payload Scrambling for the ports according to the network planning. Click Apply. – Configure an interface at the E1 level. 1.

In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Interface Management > PDH Interface from the Function Tree.

2.

In General Attributes tab, select E1 port. Set Port Mode to Layer 2, and click Apply.

3.

In Advanced Attributes tab, set Frame Format and Frame Mode according to networking planning. Then, click Apply.

4.

Choose Configuration > Packet Configuration > Interface Management > ATM IMA Management from the Function Tree. Then, click Configuration in the Binding tab, and the Bound Path dialog box is displayed.

5.

Select E1 for the Level field for the available bound path, and select ports in Available Resources. Then, click Selected Bound Paths

6. Issue 03 (2013-02-20)

to add the bound board and port to

Click Apply. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

430


l


7.

On the IMA Group Management tab, select the IMA group. Set the parameters such as IMA Transmit Frame Length and IMA Symmetry Mode according to the network planning. Then, set IMA Protocol Enable Status to Enabled. Click Apply.

8.

On the ATM Interface Management tab, click the IMA group. Then, set the parameters such as Port Type, ATM Cell Payload Scrambling for the ports according to the network planning. Click Apply.

Use the STM-1 ATM board to carry the ATM services. 1.

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

2.

In Layer 2 Attributes, select STM-1 port and set the parameters such as VPI/VCI range for the ports according to the network planning. Click Apply.

----End

Result When creating the IMA groups at both ends of the interconnected equipment is complete, you can query the IMA group status on the U2000 to check whether the IMA groups are in proper status. 1.

In the NE Explorer, click an NE and choose Configuration > Packet Configuration > Interface Management > ATM IMA Management from the Function Tree.

2.

In the IMA Group States tab, click Query. Check Near-End Group Status, Far-End Group Status, Number of Transmit Links, and Number of Receive Links. l If Near-End Group Status and Far-End Group Status are displayed as Operational, the negotiation of the IMA groups succeeded. l If Near-End Group Status and Far-End Group Status are displayed as other status, handle the anomaly with reference to Table 9-2.

3.

In the IMA Link Status tab, click Query. Check Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status. l If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Active, it indicates that the IMA link is normal. l If Near-End Receiving Status, Near-End Transmitting Status, Far-End Receiving Status, and Far-End Transmitting Status are displayed as Unusable, it indicates that the IMA link is faulty. For details on the IMA link status parameters, see Table 9-3.

Table 9-2 lists the IMA group status parameters. Table 9-2 IMA group status parameters

Issue 03 (2013-02-20)

Near-End/Far-End Group Status

Description

Suggestion

Not Configured

Displays this state if the IMA group does not exist.

-


431



Near-End/Far-End Group Status

Description

Suggestion

Start-Up

This end is in the Start-Up status and is waiting to be indicated that the far-end is also in the Start-Up status.

Start the IMA protocol for the opposite IMA group and check whether the IMA groups are normal.

Start-Up-ACK

This is a transitional state. When both the near-end and far-end groups start-up, they move to this state.

The IMA groups are in the progress of negotiation. Wait for 500 ms and then check whether the IMA groups are normal.

Config-Aborted

This state is entered when the far-end tries to apply unacceptable configuration parameters.

Check whether the parameter settings are consistent for the IMA groups at both ends. If not, re-set the inconsistent parameters to ensure that all the parameter settings are consistent for the IMA groups at both ends.

Insufficient-Links

The status is displayed when the parameter settings for the IMA groups at both ends are consistent but the link resources are insufficient. In this case, the number of activated links is less than the minimum number of activated links for an IMA group.

When the fault of the IMA link is rectified, check whether the IMA groups are in proper status.

Blocked

The group is blocked. The group can be blocked for maintenance purposes while sufficient links are Active in both transmitting and receiving directions.

-

Operational

The group is not inhibited and has sufficient links in both transmitting and receiving directions.

-

Table 9-3 lists the IMA link status parameters.

Issue 03 (2013-02-20)


432



Table 9-3 IMA link status parameters Receive/Transmit Status

Description

Suggestion

Not In Group

This state is displayed if a link is not included in an IMA group.

-

Unusable

The status is displayed when an IMA link is added to an IMA group but the IMA link is not available because of fault-caused or manual suppression.

When the fault of the IMA link is rectified, check whether the IMA links are in proper status.

Usable

This status indicates that the link is availably and it is displayed when you are waiting for the remote receive link to be activated. In this case, this link is not added to the cyclical transmitting process of the IMA group.

-

Active

This status indicates that the link is activated. If service cells accessed, they can be transmitted. This link is added to the cyclical transmitting process of the IMA group.

-

9.15.2 Configuring an ATM Policy Profile This section describes how to configure a traffic management policy, which can be selected as the traffic management profile for ATM services configured in an end-to-end mode.


Procedure Step 1 Choose Configuration > PTN QoS Profile > ATM Profile from the Main Menu. Step 2 Right-click in ATM Profile and choose Add Global Profile from the shortcut menu.

Issue 03 (2013-02-20)


433



The Create ATM Profile dialog box is displayed. Step 3 Set the ATM policy profile according to network planning information so that it is available for traffic management policy selection during ATM connection creation.

Step 4 Click OK. Step 5 Check and manage the global ATM policy profile in the Details, NE Reference, and NE Unreference tabs. ----End

9.15.3 Configuring an ATM CoS Mapping Profile This section describes how to configure an ATM CoS mapping profile, which can be selected as the ATM CoS mapping for ATM services configured in an end-to-end mode.


Procedure Step 1 Choose Configuration > PTN QoS Profile > ATM CoS Mapping Profile from the Main Menu. Step 2 Select appropriate steps based on the requirement. If...

Then...

You need to change the default global ATM CoS mapping profile

Perform Step 3 and Step 5

Issue 03 (2013-02-20)


434



If...

Then...

You need to create a global ATM CoS mapping profile

Perform Step 6 and Step 8

Step 3 Double-click the Default ATMCosMap profile. The Modify ATM CoS Mapping Profile dialog box is displayed. Step 4 Modify the global ATM CoS mapping profile according to network planning information.

NOTE

l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits. NOTE

The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4. l BE: best effort, applicable to services that do not require special processing.

Step 5 Click OK. Step 6 Right-click in ATM CoS Mapping Profile and choose Add Global Profile from the shortcut menu.

The Create ATM CoS Mapping Profile dialog box is displayed. Step 7 Create a global ATM CoS mapping profile according to network planning information.

Issue 03 (2013-02-20)


435



NOTE

l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits. NOTE

The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4. l BE: best effort, applicable to services that do not require special processing.


9.15.4 Creating an ATM Service by Using the Trail Function This topic describes how to use the trail function to create an ATM PWE3 service tunnel for ATM signal transmission. The trail function allows you to fast configure the source and sink nodes of an ATM service and PW attributes.

Prerequisites l


l

ATM interfaces are configured. If IMA services are transmitted, an IMA group is configured.

l

An ATM policy is configured.

l

An MPLS tunnel is used.

Procedure Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Step 2 Set the parameters on the Attributes tab. Issue 03 (2013-02-20)


436



NOTE

l Use a template to configure a service. Specifically, select a template in the Service Template field or personally create another template. l Set Service Type to ATM. l If you set Protection Type to PW APS Protection, select Single Source and Dual Sink or Dual Source and Single Sink on the Node List. You need to configure one source node and two sink nodes for Single Source and Dual Sink, and two source nodes and one sink node for Dual Source and Single Sink. The two PWs are the working PW and protection PW. In addition, PW APS Protection can be set to Single Source and Single Sink.

Step 3 Select the source and sink NEs for a service. 1.

Click Configure Source And Sink. A dialog box is displayed.

2.

Select a source NE from Physical Root on the left. Then, the selected NE is displayed in the upper right pane.

3.

In the right portion of NE Panel, all slots and available boards of an NE are displayed. According to the required service type, select an appropriate board.

4.

Select an interface.

5.

Set the service access interface attributes. Then, click Add Node. In the lower portion of the window, the new source and sink NEs are displayed, click OK.

6.

Configure the sink NE, protection NE and transit NE with the same method to align with different protection types.

7.

To configure multiple ATM connections for an ATM service at the same time, select multiple ports for an NE in the same way. NOTE

The same configuration method is applicable to the sink NE, transit NE, and source NE. This topic considers the configuration of a source NE as an example.

Step 4 Optional: Click Configure Source And Sink, select the Unterminated in the left, specify the LSR ID of an unterminated node, and click Add Node. In the lower portion of the window, the unterminated source and sink NEs are displayed. Then, click OK. NOTE

On a network, if the equipment at one end of a service can be managed by the U2000, and the equipment at the other end of the service is from another vendor and therefore cannot be managed by the U2000, select Unterminated to set the LSR ID at the opposite end of the service. Currently, the OptiX OSN equipment in the same management domain can be used to configure unterminated trails. If Protection Type is PW APS Protection, the unterminated node cannot be set.

Step 5 Optional: Click Configure PW Switch Node to add working and protection transit NEs between the source NE and sink NE. Step 6 Set parameters for the source and sink NEs that are displayed in Node List. To view the topology of a configured service, click the Service Topology tab in the upper-right area. Step 7 Set parameters in the PW pane in the lower left portion of the window.

Issue 03 (2013-02-20)


437



NOTE

PW ID can be automatically allocated. Signaling Type can only be set to Static. Forward Label and Reverse Label can be assigned automatically or manually. Forward Type and Reverse Type can be set to Static Binding. In this case, manually specify a tunnel in the Forward Tunnel field. You may also set the forward tunnel and reverse tunnel by clicking the Service Topology tab in the upper right area. Right-click a tunnel between the source NE and sink NE, and choose Select Forward Tunnel or Select Reverse Tunnel from the shortcut menu. In the dialog box that is displayed, select the tunnel for static binding.

Step 8 Click ATM Link. In the dialog box that is displayed, add the ATM connection, and set relevant parameters of the ATM connection. NOTE

After you configure VPI/VCI of the source and sink, the U2000 assigns the transit VPI/VCI automatically. On a network consisting of OptiX OSN 7500 II equipment, the transit VPI/VCI can be set to a value different from the VPI/VCI of the source and sink.

Step 9 Optional: Click Detail. A pane is displayed in the lower right area. Step 10 Optional: Click the PW QoS tab to configure the global template of a PW. Alternatively, select one of the templates that are configured in the Global QoS Policy Template field, and set parameters. Step 11 Optional: Click the Advanced PW Attribute tab to set parameters for a PW. Step 12 Optional: If the Protection Type is PW APS Protection, click Protection Parameter to set the protection parameters. Step 13 Select the Deploy check box, and click OK. NOTE

If you clear the Deploy check box, the configuration data information is saved only on the U2000. If you select the Deploy check box, the configuration data information is saved on the U2000 and applied to NEs. By default, the Deploy check box is selected. When you select the Deploy and Enable check boxes, a service is available on NEs only when enabled.

----End

Follow-up Procedure After the service is created successful, the service is displayed in the PWE3 service management window.

9.15.5 Creating ATM Services on a Per-NE Basis This section describes how to create an ATM PWE3 service channel that transports ATM signals on a per-NE basis. The per-NE basis means configuring service attributes at both source and sink ends.

Prerequisites l


l

ATM interfaces are configured. If IMA services are transmitted, configure an IMA group.

l

ATM policies are configured.

Issue 03 (2013-02-20)


438


l


MPLS tunnels are created.


The OptiX OSN equipments transmits services at the E1 level or 64 kbit/s timeslot level. If the services are at the E1 level, all the available timeslots of E1 channels are used to transport services. If the services are at the 64 kbit/s timeslot level, one E1 channel can be used to simultaneously transport ATM services and CES services (certain timeslots allocated for ATM services and others for CES services). In this manner, E1 channels are used flexibly.

l

If the volume of the accessed ATM services is small, one E1 port or several 64 kbit/s timeslots (less than 30 timeslots) can meet access capacity demand. In this case, bind an E1 port or 64 kbit/s timeslots into an IMA group, but do not enable the IMA protocol. Therefore, the IMA group serves as a service access interface.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > ATM Service Management from the Function Tree. Step 2 Click New. The New ATM Service dialog box is displayed. In the dialog box, configure a UNIs-NNI or UNI-UNI service.

Issue 03 (2013-02-20)


439



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

Select UNI-UNI for the service type. Set the connection type as follows. l For a UNI-UNI service, do not set Connection to Port Transparent. l PVP: Only the VPI value of an ATM connection can be changed. l PVC: The VPI and VCI values of an ATM connection can be changed.

2.

Click the Connection tab, and click Add. The Configure Connection dialog box is displayed. In the dialog box, set connection attributes.

NOTE

The Sink VPI value ranges from 0 to Max.VPI, and the Sink VCI value ranges from 32 to Max.VCI.

3.

Click OK.

Step 5 Optional: Create a UNIs-NNI service. 1.

Set ATM-related general attributes. NOTE

Select UNIs-NNI for the service type. Set the connection type as follows. l When Service Type is set to Port Transparent, only one ATM connection can be created and VPI or VCI of the ATM connection cannot be changed. To transparently transmit an ATM service, user ATM cells are encapsulated into PWs as payload without interpretation of ATM cell headers, and are transported to the other end over a transport network. l PVP: Only the VPI value of an ATM connection can be changed. l PVC: The VPI and VCI values of an ATM connection can be changed.

2.

Issue 03 (2013-02-20)

Click the Connection tab, and click Add. The Configure Connection dialog box is displayed. In the dialog box, set connection attributes. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

440



NOTE

For a service to be transparently transmitted, configure only PW attributes, but not VPI/VCI or ATM policy.

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 Basic Attributes tab, and set the general attributes of PW.

5.

Optional: Click the QoS tab, and set the QoS attribute of PW.

6.

Optional: Click the Advanced Attributes tab, and set the advanced attributes of PW. NOTE

l When PW Type is set to ATM n:1, Control Word can be set to either Used required or Not in use. When Control Word is set to Used required, a PW ping test is feasible. l When PW Type is set to ATM 1:1, Control Word must be set to Used required.

7.

Select the CoS Mapping tab, and then the applied CoS mapping policy is displayed by default. NOTE

Configure CoS mapping only after configuring the parameters in the PW tab.

8.

Optional: To change the CoS mapping policy for the service, click CoS Mapping, and click the

9.

button. In the CoS Mapping dialog box, select ATM CoS mapping.

Click OK.

Step 6 In the New ATM Service dialog box, click OK. A dialog box is displayed, indicating that the operation succeeded. Click Close. ----End

9.16 Managing PWE3 Services Quality of PWE3 services has significant impacts on customer revenues; stable PWE3 services increase customer revenues. Therefore, it is crucial to properly manage PWE3 services. Managing PWE3 services involves deploying, modifying, and deleting PWE3 services, checking the PWE3 service topology, and managing discrete PWE3 services. Issue 03 (2013-02-20)


441



9.16.1 Searching for PWE3 Services A complete PWE3 service contains its source and end. If being created on a per-NE basis, PWE3 services are displayed as discrete services on the NMS. After you search for the PWE3 services on the NMS, the discrete PWE3 services are converted to complete PWE3 services. This facilitates future PWE3 service management.

Prerequisites l

PWE3 services have been created on a per-NE basis. For details on how to create PWE3 services on a per-NE basis, see 9.9.3 Configuring UNI-NNI E-Line Services Carried by PWs on a Per-NE Basis.

l

When PWE3 services are created on a per-NE basis, ensure that the PW types are the same; Peer IP of a local NE equals the LSR ID of the opposite NE; the PW outgoing label of a local NE equals the PW incoming label of the opposite NE.

l


Procedure Step 1 Choose Service > Search for IP Service from the main menu. Step 2 In the dialog box that is displayed, set the tunnel discovery policy.

Step 3 Click Start. Step 4 Click Close. ----End

9.16.2 Checking the PWE3 Service Status Quality of PWE3 services has significant impacts on customer revenues; stable PWE3 services increase customer revenues. This section describes how to check the topology information and running status of a PWE3 service, facilitating PWE3 service management.

Prerequisites l

The PWE3 service has been created.

l


Issue 03 (2013-02-20)


442



Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to PW APS. Then, click Filter. Query all PWE3 services that meet the filter conditions. Step 3 Select the PWE3 service whose topology information you need to check and click the Topology tab.

Step 4 In the PWE3 service topology view, right-click the link, and choose View Real-Time Performance from the shortcut menu to check the real-time running status of the PWE3 service. Step 5 In the PWE3 service topology view, right-click the link, and choose View Tunnel from the shortcut menu to check the running status of the tunnel. ----End

9.16.3 Deploying PWE3 Services After being created on the NMS, PWE3 services are stored on the NMS but not immediately deployed to the corresponding NEs. This section describes how to deploy PWE3 services from the NMS to the corresponding NEs.

Prerequisites l


l


Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu. Step 2 In the dialog box that is displayed, set Deployment Status to Undeployed. Click Filter to check all undeployed PWE3 services. Step 3 Select one or more PWE3 services to be deployed, right-click the PWE3 services, and choose Deploy from the shortcut menu.

Issue 03 (2013-02-20)


443



NOTE

After a PWE3 service is successfully deployed, its Deployment Status is Deployed.

----End

9.16.4 Modifying PWE3 Services This section describes how to change values of PWE3 service parameters, such as the service name.

Prerequisites l


l


Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to PW APS. Then, click Filter. Query all PWE3 services that meet the filter conditions. Step 3 Select the PWE3 service whose parameters you need to modify and click Details. In the dialog box that is displayed, change the values of the PWE3 services parameters as required.

----End

Issue 03 (2013-02-20)


444



9.16.5 Deleting PWE3 Services After being deployed, PWE3 services are stored on the NMS and the corresponding NEs. This section describes how to delete PWE3 services from the NMS and corresponding NEs.

Prerequisites l


l



After being deleted from the network side, PWE3 services are deleted from the NMS only but still stored on the corresponding NEs. In addition, after being deleted from the network side, PWE3 services are displayed as discrete services on the NMS.

l

After being deleted from the NE side, PWE3 services are deleted from the corresponding NEs only but still stored on the NMS. In addition, after being deleted from the NE side, PWE3 services are displayed as undeployed.

Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu. Step 2 In the dialog box that is displayed, set filter conditions; for example, set Protocol Type to PW APS. Then, click Filter. Query all PWE3 services that meet the filter conditions. Step 3 Select one or more PWE3 services that you need to delete, right-click the services. l Choose Delete from the shortcut menu. l Choose Delete from Network Side from the shortcut menu. l Choose Undeploy from the shortcut menu.

NOTE

After a PWE3 service is successfully deleted from the NE side, its Deployment Status is Undeployed.

----End

9.16.6 Managing Discrete PWE3 Services This section describes how to find discrete PWE3 services, convert discrete PWE3 services to unterminated services, and delete discrete PWE3 services.


The PWE3 service has been created. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

445


l



Procedure Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the main menu. Step 2 In the dialog box that is displayed, set filter conditions and click Filter. Query all PWE3 services that meet the filter conditions. Step 3 Optional: Convert a PWE3 service to an unterminated service. 1.

Select a PWE3 service and click Convert to Unterminated.

2.

In the dialog box that is displayed, set attributes of the PWE3 service, such as the service name.

NOTE

After a PWE3 service is converted to an unterminated service, its service information is displayed in Manage PWE3 Service.

Step 4 Optional: Select one or more PWE3 services and click Delete Discrete Service. ----End

9.17 Managing Composite Services Managing composite services includes automatically discovering and deploying composite services.

9.17.1 Automatically Discovering Composite Services With the automatically discovering composite service function, you can discover composite services and save them to the NMS. The composite service is composed of services associated with interface connection points or PW connection points.

Prerequisites You must be an NM user with NE administrator authority or higher. Issue 03 (2013-02-20)


446



Procedure Step 1 Choose Service > Composite Service > Search for Composite Service from the Main Menu. Step 2 In the dialog box that is displayed, set the tunnel discovery policy and click Start.

Step 3 After the composite service search is complete, click Close. ----End

9.17.2 Deploying Composite Services After being created on the NMS, Composite services are stored on the NMS but not immediately deployed to the corresponding NEs. This section describes how to deploy Composite services from the NMS to the corresponding NEs.

Prerequisites l

The composite service has been created.

l


Procedure Step 1 Choose Service > Composite Service > Manage Composite Service from the main menu. Step 2 In the dialog box that is displayed, set Deployment Statusto Undeployed. Click Filter to check all undeployed Composite services. Step 3 Select one or more Composite services to be deployed, right-click the Composite services, and choose Deploy from the shortcut menu.

Issue 03 (2013-02-20)


447



NOTE

After a Composite service is successfully deployed, its Deployment Status is Deployed.

----End

9.18 Configuring Address Resolution Dynamic Address Resolution Protocol (ARP) learning is implemented by the dynamic ARP. It automatically maps IP addresses and MAC address, requiring no manual configuration of an ARP table. Generally, dynamic ARP learning is applicable to networks with many NEs. Dynamic ARP protocol packets, however, may significantly affect NE operating. For static ARP configuration, the ARP table, namely, mapping between IP addresses and MAC addresses, is configured manually, but NE operating is not affected by static ARP protocol packets. Static ARP configuration is applicable to small networks with specific NEs and NE ports used.


Procedure Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Create. Then, the Add Address Parse dialog box is displayed.

Step 3 Set the IP address and MAC address for each ARP table item, and then click Apply. For details about the parameters, see 10.13 Parameter Description: Address Parse.

WARNING When configuring the MAC address of each ARP table item, ensure that the first digit of the address is an even number. Step 4 After the setting is complete, click OK.

WARNING Configuring the address resolution refers to creating the static ARP table items. To delete the dynamic ARP table items, click Clear. This operation, however, clears all the contents in the ARP table items and interrupts the services. Hence, exercise caution when performing this operation.

Issue 03 (2013-02-20)


448



NOTE

Click Delete to delete the contents of the static ARP table items.

----End

9.19 Configuring the NE-Level TPID When the request VLAN function is enabled, PW-carried Ethernet services function properly only if the TPIDs in the request VLAN tags of the Ethernet services are the same at both ends of a PW.


Procedure Step 1 In the NE Explorer, select the required NE and then choose Configuration > Packet Configuration > TPID Configuration from the Function Tree. Step 2 Set TPID(Hexadecimal). Step 3 Click Apply. ----End

9.20 Creating a QinQ Link In the case of the QinQ link, a layer of VLAN tag is added to the packets that are accessed over a port, through QinQ encapsulation. Hence, the packets from different VLANs on the user-side network can be encapsulated and then transmitted to the same VLAN on the transport network. In this manner, the VLAN resources on the transport network are saved. Both the E-Line service and E-LAN service can be carried by the QinQ links on the network side.

Prerequisites l


l

The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must be the QinQ mode.

l

If the QoS parameters of the QinQ link need to be set, the QinQ policy must be configured first.

Procedure Step 1 In the NE Explorer, select the NE and choose Configuration > Packet Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Step 2 Click New. Then, 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 and set the QoS-related parameters. For details about the parameters, see 10.12 Parameter Description: QinQ Link Configuration Parameters. Issue 03 (2013-02-20)


449



NOTE

If Bandwidth Limit is set to Enabled, you can set Committed Information Rate(kbit/s) and Peak Information Rate(kbit/s) for the QinQ link. Alternatively, you can select a QoS policy directly in Policy. Before selecting a policy, you need to create the policy first.


9.21 Creating a V-UNI Group Creating a V-UNI group involves selecting the V-UNI group members and setting the overall bandwidth of V-UNI members. The overall bandwidth in the V-UNI group can be restrained by creating the V-UNI group.

Prerequisites l


l

Multiple Ethernet services must be created.

l

The PIR value of the V-UNI group must be set to a value that is higher than or equal to the sum of the CIR values of the V-UNI members.

Procedure Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > Ethernet Service Management > V-UNI Group from the Function Tree. Step 2 Click New. Then, the NEW V-UNI Group dialog box is displayed. Step 3 Set V-UNI Group ID, V-UNI Group Type, PIR(kbit/s), and PBS(byte). Step 4 Select the port to be added. Click to add the port to the Selected Interface list. For details about the parameters, see 10.4.11 V-UNI Group.

Issue 03 (2013-02-20)


450



NOTE

l The ports on an interface board can be configured into the same V-UNI group. l The ports of a V-UNI group must be on the same board.

Step 5 Click OK. Then, the Operation Result dialog box is displayed, indicating that the operation is successful. Click Close. ----End

9.22 Managing the Blacklist The blacklist is used to discard the data frame that contains the specified destination MAC address. Managing a blacklist involves configuring disabled MAC addresses.

Prerequisites l

E-LAN services are configured.

l


Procedure Step 1 Select the created E-LAN service and click the Disabled MAC Address tab. Issue 03 (2013-02-20)


451



Step 2 Click New. Step 3 In the dialog box that is displayed, set VLAN ID and MAC Address.


Issue 03 (2013-02-20)


452


10

10 Parameter Description

Parameter Description

About This Chapter This topic describes the parameters related to the Ethernet services. 10.1 Parameter Description: Attributes of Ethernet Interface The attributes of the Ethernet interface include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control. 10.2 Parameter Description: MPLS This section describes the parameters related to the MPLS management. 10.3 Parameter Description: E-Line Service This topic describes the parameters related to the E—Line service configuration. 10.4 Parameter Description: E-LAN Service This topic describes the parameters related to the E-LAN Service configuration. 10.5 Parameter Description: E-AGGR Service This topic describes the parameters related to the E-AGGR service configuration. 10.6 Parameter Description: CES Port Before configuring a CES service, you must configure the CES port. 10.7 Parameter Description: CES Services This section describes parameters for CES services. 10.8 Parameter Description: ATM/IMA Services This section describes parameters for ATM/IMA services. 10.9 Parameter Description: MPLS OAM The MPLS OAM mechanism can be used to effectively detect, confirm, and locate internal defects that occur on the MPLS layer network, and monitor the network performance. 10.10 Parameter Description: MPLS Tunnel APS This topic describes the parameters related to the MPLS Tunnel APS. 10.11 Parameter Description: Inband DCN In this interface, you can manage DCN. 10.12 Parameter Description: QinQ Link Configuration Parameters Issue 03 (2013-02-20)


453



This topic describes the parameters related to QinQ links. 10.13 Parameter Description: Address Parse This topic describes the parameters, such as ARP List IP, ARP List MAC, and ARP List Type, for configuring the address parse function.

Issue 03 (2013-02-20)


454



10.1 Parameter Description: Attributes of Ethernet Interface The attributes of the Ethernet interface include the general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes and flow control.

10.1.1 General Attributes This topic describes the parameters for configuring the general attributes of an Ethernet port. The parameters include Port Mode, Enable Port, and Encapsulation Type. Table 10-1 lists the parameters for configuring the general attributes of an Ethernet port. Table 10-1 Parameters for configuring the general attributes of an Ethernet port Field

Value

Description

Port

For example, 21-N1PETF8-1 (Port-1)

Indicates the port name.

Name

For example, Port1

User-defines a port name.

Enable Port

Enabled, Disabled.

The Enable Port parameter sets whether the Ethernet port is usable.

Default: Enabled

Click A.1.3 Enable Port (Ethernet Interface) for more information. Layer 2, Layer 3

Port Mode

Selects the working mode of the Ethernet port. Layer 2: The port can access the user-side equipment or carry Ethernet services that use the port exclusively. Layer 3: The port can carry tunnels.

Encapsulation Type

Null, 802.1Q, QinQ Default: For details, see configuration guidelines.

The Encapsulation Type parameter sets the link layer encapsulation type of the port, and specifies the link layer encapsulation type that can be identified by this port. Click A.1.4 Encapsulation Type(Ethernet Interface) for more information.

Issue 03 (2013-02-20)


455



Field

Value

Description

Working Mode

10M Half-Duplex, 10M FullDuplex, Auto-Negotiation, 100M Half-Duplex, 100M Full-Duplex, 1000M FullDuplex, 10G Full-Duplex LAN, 10G Full-Duplex WAN

Set 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 communication mode of a port.

Default: Auto-Negotiation

CAUTION When configuring a service, set Working Mode to the same value if possible for the port and its interconnected port. Otherwise, the service may fail.

Click A.1.5 Working Mode (Ethernet Interface) for more information. Max Frame Length (byte)

For OptiX OSN 3500/7500: 960 to 9600 For other products: 960 to 9000 Default: 1620

The maximum frame length is also the maximum transport unit (MTU). Click A.1.6 Max Frame Length(byte) for an Ethernet Port for more information.

10.1.2 Flow Control This topic describes the parameters, such as autonegotiation and non-autonegotiation, which are used for configuring flow control function of a Packet Ethernet port. Table 10-2 lists the parameters for configuring flow control of a Packet Ethernet port. Table 10-2 Parameters for configuring flow control of a Packet Ethernet port

Issue 03 (2013-02-20)

Field

Value Range

Description

Port

For example: 2-N1PEG8-1 (PORT-1)

Display the port name.


456



Field

Value Range

Description

Non-Autonegotiation Flow Control Mode

Disabled, Enable Symmetric Flow Control, Send Only, Receive Only

If the working mode of the port is Non-Autosensing, you can only choose the NonAutonegotiation Flow Control Mode. l Disabled: The port disables the flow control function (in both the transmit and receive directions). l Enable Symmetric Flow Control: The port transmits flow control frames and also responds to flow control frames. l Send Only: The port only transmits flow control frames. l Receive Only: The port only responds to flow control frames.

Issue 03 (2013-02-20)


457



Field

Value Range

Description

Auto-Negotiation Flow Control Mode

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

If the working mode of the port is Auto-Negotiation, you can only choose the AutoNegotiation Flow Control Mode. l Disabled: Indicates that the flow control function of the port is disabled. (The flow control function at both the transmit and receive directions is disabled.) l Enable Dissymmetric Flow Control: Indicates that the dissymmetric flow control function is enabled in the auto-negotiation state. (The flow control frames can be transmitted, but the received flow control frames are not responded. The flow control mode used is determined by autonegotiation.) l Enable Symmetric Flow Control: Indicates that the symmetric flow control function is enabled in the auto-negotiation state. (The flow control frames can be transmitted, and the received flow control frames are responded. The flow control mode used is determined by autonegotiation.) l Enable Symmetric/ Dissymmetric Flow Control: Indicates that the symmetric/dissymmetric flow control function is enabled in the autonegotiation state. (The flow control mode used is determined by autonegotiation.)

Issue 03 (2013-02-20)


458


Field


Value Range

Description NOTE The GE ports on packet Ethernet boards support the setting of Auto-Negotiation Flow Control Mode, but only receive flow control frames. The ETMC board and the 10GE ports on packet Ethernet boards do not support the setting of Auto-Negotiation Flow Control Mode.

10.1.3 Layer 2 Attributes This topic describes the parameters for configuring the Layer 2 attributes of an Ethernet port. The parameters include QinQ Type Domain, Tag, Default VLAN ID, and VLAN Priority Table 10-3 lists the parameters for configuring the Layer 2 attributes of an Ethernet port. Table 10-3 Parameters for configuring the Layer 2 attributes of an Ethernet port

Issue 03 (2013-02-20)

Field

Value

Description

Port


Displays the port name.

QinQ Type Domain

0x0600 to 0xFFFE

Sets the QinQ type domain.

NOTE For the PEG8, PEX2, PEX1, and EDQ41, this parameter can be set only to 0x88A8.

This parameter is available only when you set Encapsulation Type in General Attributes to QinQ.


459



Field

Value

Description

Tag

Tag Aware, Access, Hybrid

Indicates which type of packets can be processed. Tag Aware: The port transparently transmits the packet with a VLAN ID (tagged). If a packet does not have a VLAN ID (untagged), the port discards this packet. In this case, Default VLAN ID and VLAN Priority are meaningless. Access: The port adds the default VLAN ID to the packet without any VLAN ID (untagged). If the packet has a VLAN ID (tagged), the port discards this packet. Hybrid: The port adds the default VLAN ID to the packet without any VLAN ID (untagged). If the packet has a VLAN ID (tagged), the port transparently transmits the packet. This parameter is unavailable when you set Encapsulation Type in General Attributes to QinQ.

Issue 03 (2013-02-20)


460



Field

Value

Description

Default VLAN ID

1 to 4094

Sets the default VLAN ID of packets that passes through the port. When you set Tag to Access, packets that have a VLAN ID the same as the default VLAN ID are discarded, and packets without a VLAN are tagged with the default VLAN ID and then pass the port. When you set Tag to Hybrid, tagged packets are allowed to pass, and untagged packets are tagged with the default VLAN ID and then pass the port. NOTE If an MPLS tunnel needs to traverse a Layer 2 network, set the VLAN IDs for the tunnels connected to the NNI ports at both ends to the same value according to the VLAN planning requirements on the Layer 2 network.

VLAN Priority

0 to 7

Sets the QoS level. When the network is busy, packets of a higher VLAN priority are processed first and those of a lower VLAN priority may be discarded. 0 indicates the lowest priority and 7 the highest.

10.1.4 Layer 3 Attributes This topic describes the parameters for configuring the Layer 3 attributes of an Ethernet port. The parameters include Enable Tunnel, Specify IP, IP Address, and IP Mask Table 10-4 lists the parameters for configuring the Layer 3 attributes of an Ethernet port. Table 10-4 Parameters for configuring the Layer 3 attributes of an Ethernet port

Issue 03 (2013-02-20)

Field

Value

Description

Port




461



Field

Value

Description

Enable Tunnel

Enabled, Disabled

The Enable Tunnel (Ethernet Interface) parameter sets the MPLS enabling state of the port. When Enable Tunnel is set to Enabled, it indicates that the port can identify and process the MPLS label.

Default: Enabled

Click A.1.7 Enable Tunnel (Ethernet Interface)for more information. Manually, Unspecified

Specify IP

Default: Unspecified

The Specify IP parameter, set by port, indicates the method of specifying the IP address parameter of a specified port. Click A.1.8 Specify IP (Ethernet Interface) for more information.

IP Address

For example, 192.168.0.1

Sets the IP address for the port.

IP Mask

For example, 255.255.255.0

Sets the subnet mask of the port.

10.1.5 Advanced Attributes This topic describes the parameters for configuring the advanced attributes of an Ethernet port. The parameters include Port Physical parameters, MAC Loopback, and Loopback Check Table 10-5 lists the parameters for configuring the advanced attributes of an Ethernet port. Table 10-5 Parameters for configuring the advanced attributes of an Ethernet port

Issue 03 (2013-02-20)

Field

Value

Description

Port




462



Field

Value

Description

Port Physical parameters

For example:

Displays physical parameters of the port.

l Port Enable: Enabled l Working Mode: AutoNegotiation l Non-Autonegotiation Flow Control Mode: Disabled l MAC Loopback: NonLoopback l PHY Loopback: NonLoopback MAC Loopback

Non-Loopback, Inloop, Outloop

Sets the loopback state of the MAC layer.

PHY Loopback


The PHY Loopback parameter indicates the loopback status of the physical layer of an Ethernet port. This parameter is an advanced attribute of the Ethernet port.

Default: Non-Loopback

Click A.1.2 PHY Loopback (Ethernet Interface) for more information. For example, 00-5A-3D-03-4C-1B

MAC Address

Displays the MAC address of the port.

Default: FF-FF-FF-FF-FFFF Transmitting Rate(kbit/s)

For example, 1024

Displays the rate at which packets are transmitted.

Receiving Rate(kbit/s)

For example, 1024

Displays the rate at which packets are received.

Loopback Check

Enabled, Disabled

Sets loop detection.

Default: Disabled

When this function is enabled, the equipment automatically checks whether a loop is generated on the link. If a loop is generated, the related alarm is reported. Currently, the OptiX OSN equipment does not support this function.

Issue 03 (2013-02-20)


463



Field

Value

Description

Loopback Port Block

Enabled, Disabled

Sets the automatic shutdown of the port.

Default: Disabled

When Loopback Check is set to Enabled and Loopback Port Block is set to Enabled, the equipment automatically checks whether a loop is generated on the link. If a loop is generated, the port is automatically shut down to release the loop.

10.2 Parameter Description: MPLS This section describes the parameters related to the MPLS management.

10.2.1 Basic Configuration This topic describe the parameter for basic MPLS configuration. Table 10-6 lists the parameter for basic MPLS configuration. Table 10-6 Parameter for the basic configuration Field

Value

Description

LSR ID


In a PSN network, each NE is allocated with a unique LSR ID.

10.2.2 Parameters for Configuring a Static Tunnel (on a Per-NE Basis) A static tunnel may be unidirectional or bidirectional. Table 10-7 lists the parameters for configuring a static tunnel. Table 10-7 Parameters for configuring a static tunnel

Issue 03 (2013-02-20)

Field

Value Range

Description

Tunnel ID

For example, 1

Displays or specifies the tunnel ID.


464



Field

Value Range

Description

Tunnel Name

For example, name1

Displays or specifies the name of the tunnel.

NOTE The tunnel name contains a maximum of 64 bytes.

Node Type

Ingress, Egress, Transit

Displays the type of a node. l Ingress: ingress node l Egress: egress node l Transit: pass-through node

Direction

Unidirectional, Bidirectional

Displays the direction of the tunnel. For a unidirectional tunnel, Direction is Unidirectional by default. For a bidirectional tunnel, Direction is Bidirectional by default.

Committed Information Rate (Kbit/s)

1024-10000000, Unlimited Default: 4294967295 (FFFFFFFFFF is invalid)

The Committed Information Rate (Kbit/s) parameter specifies the CIR of the queue. The packets whose rates are less than the CIR can be forwarded. When the rate of the packets is not more than the CIR, all messages can be forwarded. If the rate of the packets is more than the CIR, some packets are discarded according to a certain packet discarding policy. Click A.10.26 Committed Information Rate (Kbit/s) for more information.

CBS(bytes)

-

The CBS(byte) parameter specifies the committed burst size. NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

Issue 03 (2013-02-20)


465



Field

Value Range

Description

PIR(kbit/s)

-

The PIR(Kbit/s) parameter specifies the maximum rate of services allowed, also called the peak information rate (PIR). NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

-

PBS(bytes)

The PBS(byte) parameter specifies the peak burst size (PBS). NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.


Slot ID-Board name

Displays or specifies the ingress board or the logic interface type.

In Port

For example, 2(PORT-2)

Displays or specifies the ingress port of the tunnel. This parameter can be set for only the egress node and the transit node.

In Label

For example, 17 NOTE The value ranges from 16 to 32768. For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

Displays and specifies the ingress label of the tunnel. The ingress label must be unique on the entire network. This parameter can be set for only the egress node and the transit node. Ingress label is supported only when the equipment is configured with a unidirectional tunnel.

Forward In Label


Issue 03 (2013-02-20)


Displays or specifies the ingress label of the tunnel. NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Forward Out Label can be set but Forward In Label cannot be set.

466



Field

Value Range

Description

Reverse Out Label

For example, 18

Displays or specifies the egress label of the tunnel.

NOTE The value ranges from 16 to 32768. For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Reverse In Label can be set but Reverse Out Label cannot be set.

Out Board/Logic Interface Type

Slot ID-Board name

Displays or specifies the egress board or the logic interface type.

Out Port


Displays or specifies the egress port of the tunnel. This parameter can be set for only the egress node and the transit node.

Out Label


Displays and specifies the egress label of the tunnel. The egress label must be unique on the entire network. This parameter can be set for only the egress node and the transit node. Egress label is supported only when the equipment is configured with a unidirectional tunnel.

Forward Out Label


Reverse In Label


Issue 03 (2013-02-20)


Displays or specifies the egress label of the tunnel. This function is supported only when the equipment is configured with a bidirectional tunnel.

Displays or specifies the ingress label of the tunnel. Ingress label is supported only when the equipment is configured with a bidirectional tunnel.

467



Field

Value Range

Description

Next Hop Address


Displays or specifies the address of the next hop of the tunnel. This parameter can be set only for the ingress node and transit node. This function is supported only when the equipment is configured with a unidirectional tunnel.

Forward Next Hop Address


Displays or specifies the address of the next hop of the tunnel. This function is supported only when the equipment is configured with a bidirectional tunnel.

Reverse Next Hop Address


Displays or specifies the address of the next hop of the tunnel. NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Forward Next Hop Address can be set but Reverse Next Hop Address cannot be set.

Source Node


Displays or specifies the source node of the tunnel. A source node can be specified only for the egress node and transit node.

Sink Node


Displays or specifies the sink node of the tunnel. A sink node can be specified only for the ingress node and transit node.

Tunnel Type

E-LSP

Displays the tunnel type.

EXP

0, 1, 2, 3, 4, 5, 6, 7, None

The EXP parameter specifies the field in the MPLS packets for identifying the priority of these MPLS packets.

Default: None

Click A.10.30 EXP for more information.

Issue 03 (2013-02-20)


468



Field

Value Range

Description

LSP Mode

Pipe, Uniform

The LSP Mode parameter specifies the mode in which the MPLS network processes packet priorities.

Default: Uniform

Click A.10.31 LSP Mode for more information. -

MTU(bytes)

Specifies the MTU value of MPLS packets. When MTU is 0, there is no restriction on the MPLS MTU. If the MPLS MTU needs to be restricted, the MPLS MTU must be set larger than the MTU of the physical ports where the tunnel is located. NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

10.2.3 Parameters for Configuring a Static Tunnel (End-to-End Mode) This topic describes the parameters, such as the enabling status, label and type, for configuring a static tunnel. Table 10-8 Parameters for configuring a static tunnel Field

Value Range

Description

Tunnel Name

For example, Tunnel 1

Specifies the name of the tunnel.

Reverse Tunnel Name

For example, Tunnel1_RVS

Specifies the name of the Reverse tunnel.

Protocol Type

MPLS

Specifies the protocol type used by the tunnel.

Signaling Type

Static

Specifies the signaling type of the tunnel. This parameter is configurable only when you set Protocol Type to MPLS.

Issue 03 (2013-02-20)


469



Field

Value Range

Description

Remarks

For example, NE(9-7032)NE(9-7037)

Specifies the remarks.


Checked, Unchecked

If Create Reverse Tunnel is checked, a reverse tunnel is created when a forward tunnel is created. If Create Reverse Tunnel is unchecked, only a forward tunnel is created.

Create Bidirectional Tunnel

Sets the value by clicking the check box.

Specifies the tunnel as a bidirectional tunnel.

Checked, Unchecked

If Create Bidirectional Tunnel is checked, a tunnel contains a forward path and a reverse path. No extra port configurations are required.

Sets the value by clicking the check box.

If Create Protection Group is checked, a corresponding tunnel protection group is created when tunnel 1 is created.

Create Protection Group

Checked, Unchecked

Auto Calculate Route

Sets the value by clicking the check box. Checked, Unchecked Default: Checked

Remarks for a specific tunnel facilitate management and maintenance of the tunnel.

If Auto Calculate Route is checked, the system automatically computes the route after you select the source node and sink node and specify the NEs as explicit/inexplicit nodes in the physical topology. NOTE This function is supported only by the OptiX OSN 1500 and the single-slot boards on the OptiX OSN 3500/7500.

Issue 03 (2013-02-20)


470



Field

Value Range

Description

Restriction Bandwidth (Kbit/ s)

1024-1024000, No Limit

Specifies the upper bandwidth limit.

Default: No Limit

When automatically computing a route, the NMS checks whether the computed route meets the requirement of Restriction Bandwidth (Kbit/s). This parameter is available only when Auto Calculate Route is checked. Deploy

Sets the value by clicking the check box. Checked, Unchecked Default: Checked

Enable

Sets the value by clicking the check box. Checked, Unchecked

Saves the tunnel configuration on the NMS and delivers the configuration to NEs during tunnel deployment. Automatically enables the tunnel during tunnel deployment.

Default: Checked

Table 10-9 Parameters for configuring a static tunnel Field

Value Range

Description

Tunnel ID

For example, 1

Displays or specifies the tunnel ID.

Tunnel Name

For example, name1

Displays or specifies the name of the tunnel.

NOTE The tunnel name contains a maximum of 64 bytes.

Node Type


Displays the type of a node. l Ingress: ingress node l Egress: egress node l Transit: pass-through node

Direction

Unidirectional, Bidirectional

Displays the direction of the tunnel. For a unidirectional tunnel, Direction is Unidirectional by default. For a bidirectional tunnel, Direction is Bidirectional by default.

Issue 03 (2013-02-20)


471



Field

Value Range

Description


1024-10000000, Unlimited

The Committed Information Rate (Kbit/s) parameter specifies the CIR of the queue. The packets whose rates are less than the CIR can be forwarded. When the rate of the packets is not more than the CIR, all messages can be forwarded. If the rate of the packets is more than the CIR, some packets are discarded according to a certain packet discarding policy.

Default: 4294967295 (FFFFFFFFFF is invalid)

Click A.10.26 Committed Information Rate (Kbit/s) for more information. -

CBS(bytes)

The CBS(byte) parameter specifies the committed burst size. NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

-

PIR(kbit/s)

The PIR(Kbit/s) parameter specifies the maximum rate of services allowed, also called the peak information rate (PIR). NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

-

PBS(bytes)

The PBS(byte) parameter specifies the peak burst size (PBS). NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.


Issue 03 (2013-02-20)

Slot ID-Board name


Displays or specifies the ingress board or the logic interface type.

472



Field

Value Range

Description

In Port


Displays or specifies the ingress port of the tunnel. This parameter can be set for only the egress node and the transit node.

In Label


Displays and specifies the ingress label of the tunnel. The ingress label must be unique on the entire network. This parameter can be set for only the egress node and the transit node. Ingress label is supported only when the equipment is configured with a unidirectional tunnel.

Forward In Label


Reverse Out Label


Displays or specifies the ingress label of the tunnel. NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Forward Out Label can be set but Forward In Label cannot be set.

Displays or specifies the egress label of the tunnel. NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Reverse In Label can be set but Reverse Out Label cannot be set.

Out Board/Logic Interface Type

Slot ID-Board name

Displays or specifies the egress board or the logic interface type.

Out Port


Displays or specifies the egress port of the tunnel. This parameter can be set for only the egress node and the transit node.

Issue 03 (2013-02-20)


473



Field

Value Range

Description

Out Label

For example, 19

Displays and specifies the egress label of the tunnel. The egress label must be unique on the entire network.


This parameter can be set for only the egress node and the transit node. Egress label is supported only when the equipment is configured with a unidirectional tunnel.

Forward Out Label


Reverse In Label


Next Hop Address


Displays or specifies the egress label of the tunnel. This function is supported only when the equipment is configured with a bidirectional tunnel.

Displays or specifies the ingress label of the tunnel. Ingress label is supported only when the equipment is configured with a bidirectional tunnel.

Displays or specifies the address of the next hop of the tunnel. This parameter can be set only for the ingress node and transit node. This function is supported only when the equipment is configured with a unidirectional tunnel.

Forward Next Hop Address


Displays or specifies the address of the next hop of the tunnel. This function is supported only when the equipment is configured with a bidirectional tunnel.

Issue 03 (2013-02-20)


474



Field

Value Range

Description

Reverse Next Hop Address


Displays or specifies the address of the next hop of the tunnel. NOTE If the OptiX OSN equipment is configured with a bidirectional tunnel, Forward Next Hop Address can be set but Reverse Next Hop Address cannot be set.

Source Node


Displays or specifies the source node of the tunnel. A source node can be specified only for the egress node and transit node.

Sink Node


Displays or specifies the sink node of the tunnel. A sink node can be specified only for the ingress node and transit node.

Tunnel Type

E-LSP

Displays the tunnel type.

EXP

0, 1, 2, 3, 4, 5, 6, 7, None

The EXP parameter specifies the field in the MPLS packets for identifying the priority of these MPLS packets.

Default: None

Click A.10.30 EXP for more information. LSP Mode

Pipe, Uniform Default: Uniform

The LSP Mode parameter specifies the mode in which the MPLS network processes packet priorities. Click A.10.31 LSP Mode for more information.

MTU(bytes)

-

Specifies the MTU value of MPLS packets. When MTU is 0, there is no restriction on the MPLS MTU. If the MPLS MTU needs to be restricted, the MPLS MTU must be set larger than the MTU of the physical ports where the tunnel is located. NOTE This parameter is currently not applicable to a static tunnel configured on a per-NE basis.

Issue 03 (2013-02-20)


475



10.3 Parameter Description: E-Line Service This topic describes the parameters related to the E—Line service configuration.

10.3.1 E-Line Service Parameters (Configuration on a Per-NE Basis) This topic describes the parameters, such as Service Name, Service ID, Direction, and Bearer Type, for configuring an E-Line service. Table 10-10 lists the parameters for configuring an E-Line service. Table 10-10 Parameters for configuring an E-Line service Field

Value

Description

Service ID

For example, 11

Sets and queries the ID of the Ethernet service.

Service Name

For example, test

Sets and queries the name of the Ethernet service.

Source Node

For example, 21N1PETF8-1 (Port-1) (14)

Displays the source node of the E-Line service. The format is Slot number - Board name - Port name (VLAN ID).

Sink Node

For example, PW-0

Displays the sink node of the E-Line service. The sink node can be a port, PW or QinQ link.

Direction

UNI-UNI, UNI-NNI

In the case of the UNI-NNI direction, selects the network-side bearer type as PW Port or QinQ Link.

Service Tag Role

User, Service

Specifies how C-VLAN/S-VLAN tags of packets are processed.

Default: User

l User: C-VLAN/S-VLAN tags of packets are used as user VLAN tags, and are processed when the packets are forwarded. l Service: C-VLAN/S-VLAN tags of packets are used as service VLAN tags, and are not processed when the packets are forwarded. NOTE This parameter is unavailable in V200R011C00,V200R011C01 and V200R011C02.

Issue 03 (2013-02-20)

Source Port

For example, 21N1PETF8-1 (Port-1) (1-2)

Sets and queries the user-side port or networkside port.

Source VLANs

1-4094

Sets one or several VLAN IDs, or does not set any VLAN ID.


476



Field

Value

Description

PRI

0 to 7

UNI-NNI E-Line services can be mapped to different PWs based on Port+VLAN+VLAN PRI. If packets need to be forwarded based on Port+VLAN+VLAN PRI, set PRI to an integer ranging from 0 to 7. Value 7 represents the highest priority.

Default: null

PRI can be set to null, one value, or several values. If PRI is set to several values, separate the values using commas; if PRI is set to an interval, represent the interval in a form like 2-5. l If PRI is set to null, packets are mapped to different PWs based on VLAN IDs. In this case, packets whose PRI is set to a value within the range from 0 to 7 can be carried in the E-Line service. l If PRI is not set to null, packets are mapped to different PWs based on Port+VLAN +VLAN PRI. In this case, one service VLAN ID must be added for the E-Line service. NOTE This parameter is unavailable in V200R011C00,V200R011C01 and V200R011C02.

Bearer Type

Port, PW, QinQ Link Default: -

The Bearer Type (E-Line Service) parameter specifies the bearer type for different types of Ethernet services. The value of this parameter can be set to Port, PW, or QinQ Link. Click A.3.2 Bearer Type (E-Line Service) for more information.

PW ID

QinQ Link ID

Issue 03 (2013-02-20)

1-4294967295

The PW ID parameter identifies the PW.

Default: -

Click A.3.3 PW ID(E-Line Service) for more information.

For example, 5

Selects and displays the QinQ link ID.


477



Field

Value

Description

BPDU

Transparently Transmitted, Not Transparently Transmitted

The BPDU parameter sets whether the service needs transparently transmit the bridge protocol 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 is computed.

Default: Not Transparently Transmitted

MTU(bytes)

NOTE This parameter can be set to Transparently Transmitted or Not Transparently Transmitted for OptiX OSN 3500's N1PEG16 and N1PEX1 boards, and OptiX OSN 1500's Q1PEGS2, R1PEF4F, R1PEFS8, and R1PEGS1 boards, and can be set to only Not Transparently Transmitted for the other OptiX OSN boards.

Click A.3.4 BPDU for more information.

46-9000

The MTU(bytes) parameter indicates the maximum transmitted packet length, which is the length of the packet payload.

Default: 1500

Click A.3.5 MTU(bytes)(E-Line Service) for more information.

10.3.2 E-Line Service Parameters (Configuration in End-to-End Mode) This topic describes the parameters for configuring E-Line services in end-to-end mode. Before creating E-Line services carried by PWs, you need to configure the tunnel for carrying the PWs.

Issue 03 (2013-02-20)


478



Table 10-11 Parameters for configuring PWE3 services Field

Value Range

Description

Service Template

DEFAULT_PWE3_CES_P TN, DEFAULT_PWE3_ETH_P TN

Displays and specifies the PWE3 service template. Service Type varies with Service Template.

NOTE The OptiX OSN equipment does not support the following service templates:

Service Template improves service configuration efficiency.

NOTE This parameter is optional and helps users quickly configure various services. If the parameter value is not specified, subsequent service configuration is not affected.

l DEFAULT_PWE3_ATM_ ROUTER l DEFAULT_PWE3_CES_ ROUTER l DEFAULT_PWE3_ETH_ ROUTER l DEFAULT_PWE3_IWF_ ROUTER l DEFAULT_PWE3_IP_R OUTER

Service Type

ETH, CES NOTE Specifies the required service type based on service configuration. When the equipment is configured with PWE3 Ethernet services, Service Type is set to ETH. When the equipment is configured with PWE3 CES services, Service Type is set to CES.

Service ID

Auto-Assign, or manually enter it. Default: Auto-Assign

Service Name

For example, E-Line-1 NOTE The value of this parameter contains 1 to 64 bytes.

Issue 03 (2013-02-20)


NOTE After you select a service template, a dialog box is displayed, saying After the template is changed, the parameters not contained in the new template may be lost. Are you sure to continue? You can also select Apply the template data to the configured Objects.

Displays and specifies the type of each PWE3 service.

Specifies the ID of each PWE3 service. The service ID is unique on the entire network. Displays and specifies the name of each PWE3 service.

479



Field

Value Range

Description

Protection Type

Protection-Free

Specifies the protection type for the service. If Protection Type is PW Redundancy, you need to select Single Source and Dual Sink from Node List. If Protection Type is PW APS, you need to select Dual Source and Single Sink from Node List. If you select Single Source and Dual Sink, you need to configure one source node and two sink nodes. If you select Dual Source and Single Sink, you need to configure two source nodes and one sink node. One PW functions as the working path and the other PW functions as the protection path.

Description


Displays and specifies the service description.

Customer

-

Displays and specifies the customer to which a service belongs.

Remarks

-

Displays and specifies the service remarks.

Field

Value Range

Description

ID

For example, 1

Displays and specifies the ID of the service access port.

VLAN ID

-

Displays and specifies the VLAN ID of the service access port.

Priority Type

Null, 802.1Q

Specifies the priority type.

Default value: Null

NOTE Setting this parameter is not available in the V200R011C00, V200R011C01, and V200R011C02 versions.

Table 10-12 SAI parameters

Issue 03 (2013-02-20)


480



Field

Value Range

Description

Priority Field

0 to 7

UNI-NNI E-Line services can be mapped into different PWs based on Port+VLAN +VLAN PRI. Set this parameter if packets need to be forwarded based on Port +VLAN+VLAN PRI This parameter takes an integral value ranging from 0 to 7. Value 7 represents the highest priority.

Default value: Null

NOTE l Setting this parameter is not available in the V200R011C00, V200R011C01, and V200R011C02 versions. l This parameter takes effect only when Priority Type is 802.1Q.

Service Tag

User, Service Default value: User

Specifies the way C-VLAN/ S-VLAN tags in user packets are processed. l User: C-VLAN/S-VLAN tags in user packets are used as user VLAN tags, and are processed when the packets are forwarded. l Service: C-VLAN/SVLAN tags in user packets are used as service VLAN tags, and are not processed when the packets are forwarded. NOTE Setting this parameter is not available in the V200R011C00, V200R011C01, and V200R011C02 versions.

Table 10-13 Basic PW parameters

Issue 03 (2013-02-20)

Field

Value Range

Description

Role

Working, Protection

Displays and specifies the role of a PW.


481



Field

Value Range

Description

Source NE

NE-Slot ID-Board-PortHigher order timeslot

Displays and specifies the source NE of a PW.

Sink NE


Displays and specifies the sink NE of a PW.

PW ID

Auto-Assign, or manually enter it.

Displays and specifies the identifier of a PW.

For example, 35 Signaling Type

Static

Displays and specifies the signaling type of a PW. If you set Signaling Type to Static, you need to set the PW ingress label and PW egress label. If you set Signaling Type to Dynamic, the system automatically allocates the PW ingress label and PW egress label.

Forward Label

For example, 20 NOTE The value ranges from 16 to 32768 in step of 2048, and is different from the MPLS tunnel label. For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

Displays and specifies the label that the service carries when entering a PW. l If you set Signaling Type to Dynamic, Forward Label is automatically allocated by the system and cannot be specified manually. l If you set Signaling Type to Static, Forward Label can be automatically allocated or manually specified.

Issue 03 (2013-02-20)


482



Field

Value Range

Description

Reverse Label

For example, 20

Displays and specifies the label that the service carries when leaving a PW.

NOTE The value ranges from 16 to 32768 in step of 2048, and is different from the MPLS tunnel label. For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

l If you set Signaling Type to Dynamic, Reverse Label is automatically allocated by the system and cannot be specified manually. l If you set Signaling Type to Static, Reverse Label can be automatically allocated or manually specified.

Forward Type

Static Binding

Displays and specifies the binding type of a forward tunnel.

Forward Tunnel

For example, NE1-NE2#1

Displays and specifies the name of a forward tunnel. NOTE The OptiX OSN equipment supports only Static Binding.

Reverse Type

Static Binding

Displays and specifies the binding type of a reverse tunnel.

Reverse Tunnel


Displays and specifies the name of a reverse tunnel. NOTE The OptiX OSN equipment supports only Static Binding.

Encapsulation Type

MPLS NOTE If you set Encapsulation Type to MPLS, Tunnel Type may be MPLS, IP, or GRE. If you set Encapsulation Type to UDP, Tunnel Type is IP only.

Displays and specifies the encapsulation type of a PW. NOTE The OptiX OSN equipment supports only one tunnel type, namely, MPLS tunnel.

Table 10-14 Advanced PW parameters

Issue 03 (2013-02-20)

Field

Value Range

Description

PW Trail

-

Displays the trail of a PW.

Direction

Bidirectional

Displays the direction of a PW.


483



Field

Value Range

Description

PW Type

Ethernet, Ethernet Tagged Mode

l Ethernet: C-VLAN/SVLAN tags of packets are encapsulated into PWs without changes, and transparently transmitted to downstream sites.

Default: Ethernet

l Ethernet Tagged Mode: A VLAN tag specified by Request VLAN is added to packets. PWs of different types process their carried services differently. To tag the services carried by a PW, set PW Type to Ethernet Tagged Mode for the PW; otherwise, set PW Type to Ethernet. No Use, Used First

Control Word

Default: -

The Control Word parameter specifies the PW control word usage policy. Click A.8.1 Control Word for more information.


None, CW Default: CW

The Control Channel Type parameter specifies the type of channels for transmitting VCCV packets. Click A.8.2 Control Channel Type for more information.


None, Ping Default: Ping

The VCCV Verification Mode parameter specifies the verification mode of VCCV packets. Click A.8.3 VCCV Verification Mode for more information. NOTE Set this parameter if Control Channel Type is Ping.

Request VLAN

For example, 5 1-4095, Non-specified Default: Non-specified

Issue 03 (2013-02-20)


The Request VLAN parameter specifies the ETH request VLAN. Click A.8.4 Request VLAN for more information.

484



Table 10-15 QoS parameters for service access ports Field

Value Range

Description

Role

For example, Working Source

Displays and specifies the role of a service access port. Based on different protection types, service access ports can function as different roles, for example, working source, working sink, protection source, protection sink, FRR source, and FRR sink.

SAI

-

Displays and specifies a service access port.

Direction

Ingress, Egress

Displays and specifies the direction of a service access port. l Ingress indicates the inbound direction of a service. l Egress indicates the outbound direction of a service.

Bandwidth Limited

Enabled, Disabled

Specifies or displays the bandwidth limit. If you set Bandwidth Limited to Enabled, bandwidth is limited based on the specified CIR, PIR, CBS, and PBS.




Issue 03 (2013-02-20)


485



Field

Value Range

Description

Committed Burst Size (byte)

64-10000000

The Committed Burst Size (byte) parameter specifies the committed burst size.


Click A.10.27 Committed Burst Size (byte) for more information. Peak Information Rate (kbit/ s)

64-10000000 Default: 4294967295 (FFFFFFFFFF is invalid)

The Peak Information Rate (kbit/s) parameter specifies the maximum rate of services allowed by the PIR. Click A.10.28 Peak Information Rate (kbit/s) for more information.

Peak Burst Size (byte)


The Peak Burst Size (byte) parameter specifies the size of the PBS. Click A.10.29 Peak Burst Size (byte) for more information.

Local QoS Policy

-

Displays the QoS policy at the local end.

Default Forwarding Priority

CS6, CS7, EF, AF1, AF2, AF3, AF4, BE, NONE

Displays the service forwarding priority. Different values represent different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Issue 03 (2013-02-20)


486



Field

Value Range

Description

Default Packet Marking Color

Red, Yellow, Green, None

Displays the default packet marking color. Based on the labels carried by packets, different colors are configured for marking the packets. Red packets have the highest priority.

Processing Mode of Green Packet

Discard, Pass, Remark

Specifies the processing mode of packets. l Discard: The packets are discarded. l Pass: The packets are forwarded.

CoS of Green Packet


Displays the service class of the packets marked green. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Green Packet

Issue 03 (2013-02-20)

Green


Sets the color of packets to green.

487



Field

Value Range

Description

Processing Mode of Yellow Packet



CoS of Yellow Packet


Displays the service class of the packets marked yellow. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Yellow Packet

Yellow

Sets the color of packets to yellow.

Processing Mode of Red Packet



Issue 03 (2013-02-20)


488



Field

Value Range

Description

CoS of Red Packet


Displays the service class of the packets marked red. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Red Packet

-

Sets the color of packets to red.

VLAN Range

-

Specifies the VLAN range of packets.

10.3.3 UNI Parameters Setting the UNI parameters for an E-Line service focuses on setting of the VLAN information about UNI ports. Table 10-16 lists the UNI parameters for an E-Line service. Table 10-16 Parameters for a UNI port

Issue 03 (2013-02-20)

Field

Value

Description

Port

For example, 21N1PETF8-1 (port-1) (1-2)

Indicates the UNI port.


489



Field

Value

Description

VLANs

1 to 4094

Queries and configures the VLAN ID. The VLAN ID can be null; or you can set one or more VLAN IDs.


BE, AF1, AF2, AF3, AF4, EF, CS6, CS7, NONE

The Default Forwarding Priority parameter indicates the forwarding priority that the NE sets to the user packets on the V-UNI side by default.

Default: BE

Click A.3.9 Default Forwarding Priority for more information.


The Default Packet Relabeling Color indicates the color that the NE sets to the user packets on the V-UNI side by default.

Default Packet Relabeling Color

Default: Green

Click A.3.10 Default Packet Relabeling Color (E-LAN Service) for more information.

10.3.4 NNI Parameters NNI parameters are used for NNI Ethernet services. According to different service bearer modes, NNI parameters include the parameters that are used for a PW, a port and a QinQ link.

PW Table 10-17 Parameters for a PW

Issue 03 (2013-02-20)

Field

Value Range

Description

PW ID

For example, 123

Specifies the ID of the PW carrying the Ethernet service.

PW Status

Enable, Disable

Specifies or displays the enable status of the PW.

PW Signaling Type

Static

In the case of the static PW, the label is manually allocated. The configuration at the two ends of a PW should be consistent.

PW Type


PWs of different types process the borne services differently. For example, the PW in the Ethernet tagged mode attaches the tag on the services on this PW.

PW Direction

Bidirectional

Specifies the direction of the PW.

PW Encapsulation Type

MPLS

Displays the encapsulation type of the PW.


490



Field

Value Range

Description

PW Ingress Label

The value range varies according to the product.

Specifies this parameter when the PW Signaling Type is set to Static.

l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l Other products: 16 to 32768. PW Egress Label



l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l Other products: 16 to 32768. Peer IP


Specifies the peer IP of the PW.

Tunnel Type

MPLS

Displays the type of the tunnel that carries the PW.

Tunnel No.

Tunnel ID

Selects a created tunnel. If no tunnel is available, creation of a PW fails.

For example, 55 Control Word

No Use, Used First Default: -






Issue 03 (2013-02-20)

Ping, None

Verifies the connectivity of a PW. The VCCV verification mode is a tool used to manually verify the connectivity of a virtual circuit.


491



Field

Value Range

Description

Local Operating Status

Up, Down

Displays the working status of the PW at the local end. Up indicates that the PW works normally. Down indicates that the PW work abnormally.

Remote Operating Status

Up, Down

Displays the working status of the PW at the remote end. Up indicates that the PW works normally. Down indicates that the PW work abnormally.

Competitive Working Status

Up, Down

The Competitive Working Status parameter specifies the running status of a PW. Click A.8.5 Competitive Working Status for more information. NOTE For the OptiX OSN equipment, Static can only be set to Up.

Request VLAN

For example, 5 1-4095, Non-specified

TPID

The Request VLAN parameter specifies the ETH request VLAN.

Default: Non-specified

Click A.8.4 Request VLAN for more information.

0x88A8

Identifies the protocol.

Port Table 10-18 Parameters for an NNI Port Field

Value Range

Description

Port

For example, 21N1PETF8-1(Port-1)

Specifies the network-side port.

QinQ Link Table 10-19 Parameters for a QinQ link

Issue 03 (2013-02-20)

Field

Value Range

Description

QinQ Link ID

For example, 5

Displays the QinQ link ID.

Port

For example, 21N1PETF8-10 (Port-10)

Displays the board and port.

S-Vlan ID

For example, 4

Displays the S-VLAN ID.


492



Field

Value Range

Description

Direction

Ingress, Egress

Displays the direction of the service.

Bandwidth Limit

Enabled, Disabled

Displays the bandwidth limit. When Bandwidth Limit is set to Enabled, you can set Committed Information Rate and Peak Information Rate.


For example, 16000

Displays the committed information rate, which is the guaranteed rate that can be provided to the service.

Committed Burst Size(byte)

-

Displays the committed burst size, which is the maximum flow size allowed for each burst.


For example, 20000

Displays the peak information rate, which is the maximum rate that can be provided for the service.

Maximum Burst Size(byte)

-

Displays the maximum burst size, which is the maximum flow size allowed for each excessive burst.

Policy

Policy ID + Policy Name

Displays the QinQ policy.

For example, 1(policy1)

10.3.5 Maintenance Association The maintenance association (MA) facilitates the connectivity check (CC) of a network that transports services. Table 10-20 lists the parameters for a maintenance association. Table 10-20 Parameters for a maintenance association

Issue 03 (2013-02-20)

Field

Value

Description


1-8 characters

Sets an MD name that is unique in the entire network.


1-8 characters

Sets an MA name that is unique in the same MD.


493



Field

Value

Description

CC Test Transmit Period

3.33ms, 10ms, 100ms, 1s, 10s, 1m, 10m

The source end MEP constructs the CC frames, and then transmits them periodically to the destination MEP. After the destination MEP receives the CCM messages from the source end, the CC check function of the source MEP is directly started. Within a certain period (3.5 times of the transmission period), if the destination MEP does not receive the CC packets from the source end, an alarm is automatically reported. The CC Test Transmit Period parameter indicates the transmission period of the unidirectional connectivity check.

Default: 1s

Click A.6.1 CC Test Transmit Period (Ethernet Service OAM Management) for more information.

10.3.6 MEP Point The MEP point is the edge point in an MA. Table 10-21 lists the parameters for an MEP point. Table 10-21 Parameters for an MEP point

Issue 03 (2013-02-20)

Field

Value

Description


1-8 characters

The name of an MD should be unique in the entire network.


1-8 characters

The name of an MA should be unique in the same MD.

Board

For example, 21N1PETF8

Displays the board where the MEP point is located. The format is Slot number - Board name.

Port


Displays the port where the MEP point is located. Slot number - Board name - Port information

Node


Sets the node as an MEP point.

VLAN

For example, 22

Sets the current VLAN ID of the service.

MEP ID

1-8191

Sets a unique ID for each MP. The ID is required for OAM operations.


494



Field

Value

Description

Direction

Ingress, Egress

Ingress indicates the direction for packets to enter the board. Egress indicates the direction for packets to exit the board.

CC Status

Active, Inactive

Activates or deactivates the CC function of the MEP point.

10.4 Parameter Description: E-LAN Service This topic describes the parameters related to the E-LAN Service configuration.

10.4.1 E-LAN Service Parameters (Configuration on a Per-NE Basis) This topic describes the parameters, such as Service ID and Service Name, for configuring an E-LAN service. Table 10-22 lists the parameters for configuring an E-LAN service. Table 10-22 Parameters for configuring an E-LAN service Field

Value

Description

Service ID

For example, 11


Service Name

For example, test


Tag Type

C-Awared, S-Awared, Tag-Transparent

C-Awared indicates that the learning is based on the C-TAG (client-side VLAN tag). S-Awared indicates that the learning is based on the S-TAG (operator service-layer VLAN tag). S-Awared is valid only when Encapsulation Type is set to QinQ for a port. Tag-Transparent indicates that all Ethernet packets can be transmitted transparently when Encapsulation Type is set to Null for a port.


Issue 03 (2013-02-20)

Enabled, Disabled

Adds self-learnt MAC addresses to the MAC address forwarding table.


495



Field

Value

Description


SVL, IVL

SVL indicates the shared VLAN learning. All VLANs share a MAC address forwarding table. Any MAC address is unique in the forwarding table. IVL indicates the independent VLAN learning. The forwarding tables for different VLANs are independent from each other. It is acceptable that the MAC address forwarding tables for different VLANs have the same MAC address. When Tag Type is set to Tag-Transparent, the parameter value is SVL by default and is not configurable.

64 to 9000

MTU (bytes)

Default: 1500

Available Ports

For example, Port: 21-N1PETF8-1 (Port-1)

Sets the maximum transport unit (MTU). When receiving packets of a length exceeding the MTU, the port segments the packets and transports these segments. If the packets contain a flag indicating that packet segment is not allowed, the port discards the packet. Displays the available ports for configuring the Ethernet service and the VLAN values.

VLANs: 12 Selected Ports

For example, Port: 21-N1PETF8-1 (Port-1)

Displays the selected ports for configuring the Ethernet service and the VLAN values.

VLAN: 12 Available Interfaces

-

Displays the available interfaces for configuring the split horizon group.

Selected Interfaces

-

Displays the selected interfaces for configuring the split horizon group.

10.4.2 E-LAN Service Parameters (Configuration in End-to-End Mode) Before creating E-LAN services carried by PWs, you need to configure the tunnel that carries PWs and configure the VSI attribute of NEs as NPE. This section describes the parameters for configuring E-LAN services in end-to-end mode.

Issue 03 (2013-02-20)


496



Table 10-23 Parameters for the basic VSI attributes Field

Value Range

Description

Service Name

For example, E-LAN

Specifies the name of the ELAN service.

Signal Type

LDP, BGP

Specifies the signaling type. l LDP: indicates the label distribution protocol used for configuring or maintaining PWs. l BGP: indicates the boundary gateway protocol, which is used for signaling exchanges on a mesh network. NOTE For the OptiX OSN equipment, this parameter can be set to only LDP.

Networking Mode

Full-Mesh VPLS, H-VPLS, Daisy Chain, Customized

Specifies the networking mode of Ethernet services. l If Networking Mode is set to Full-Mesh VPLS, only the NPE attribute of an NE can be specified. l If Networking Mode is set to H-VPLS, the NPE or UPE attribute of an NE can be specified. l If Networking Mode is set to Daisy Chain, only the UPE attribute of an NE can be specified. l If Networking Mode is set to Customized, only the PE attribute of an NE can be specified.

Service Type

Issue 03 (2013-02-20)

Service VPLS, Management VPLS


Specifies the VPLS type.

497



Field

Value Range

Description

VSI Type

Service VSI

Displays the service type of the virtual service instance (VSI). Regardless of whether Service Type is set to Service VPLS or Management VPLS, VSI Type is displayed as Service VSI.

VSI Name

For example, VPLS1

Specifies the VPLS service name. VSI: indicates the virtual switching instance. The VSI name on an NE must be unique.

VSI ID

Default: 1042

Specifies the VSI ID. The value can be automatically assigned. After being specified, the value of VSI ID cannot be changed. The IDs of two VSIs on an NE cannot be the same.

MTU (bytes)

46 to 9000 Default: 1500

Specifies the maximum transmission unit (MTU). When the length of a packet received at the port is greater than the preset MTU value, the packet needs to be transmitted fragment by fragment. The packet is discarded if it does not contain the fragmentation tag.

Issue 03 (2013-02-20)


498



Field

Value Range

Description

Tag Type

Tag-Transparent, C-Awared, S-Awared

Specifies the tag type. l C-Awared: receives the service packets that contain C-VLAN tags. l S-Awared: receives the service packets that contain C-VLAN tags and S-VLAN tags. l Tag-Transparent: receives the service packets that do not contain VLAN tags. NOTE For the OptiX OSN equipment, this parameter can be set to only C-Awared.

Table 10-24 Parameters for forwarding control Field

Value Range

Description

MAC Address Learning

Enable, Disable Default: Disable

Specifies whether to enable the MAC address learning function.

Qualify(IVL), Unqualify (SVL)

Specifies the bridge learning mode of E-LAN services.

Learning Mode

l Qualify(IVL): The bridge type is IEEE 802.1q or IEEE 802.1ad. MAC address learning is based on VLANs of the VSI. Each VLAN has its MAC address space. The MAC address space of different VLANs can be overlapped. l Unqualify(IVL): The bridge type is IEEE 802.1d or IEEE 802.1ad. MAC address learning is based on VSIs. Each VSI has an MAC address space. Max.Leant MAC Addresses

Issue 03 (2013-02-20)

Default: 512


Specifies the maximum number of learnt MAC addresses.

499



Field

Value Range

Description

MAC Address Aging

Enable, Disable

Specifies whether to enable the MAC address aging function. After the MAC address aging function is enabled, a MAC address is deleted from the MAC address table if no packets that contain the MAC address are received within a certain period of time.

MAC Address Aging Time

Default: 5

Specifies the aging time of MAC addresses. If the MAC address aging function is enabled, the system deletes a MAC address if no packets that contain the MAC address are received after the aging time expires. If the MAC address aging function is disabled, this parameter is unavailable.

MAC Address Detection Upper Threshold

80% to 100% Default: 95%

Specifies the upper threshold of detected MAC addresses. The value of MAC Address Detection Upper Threshold needs to be greater than the value of MAC Address Detection Lower Threshold. When the number of learnt MAC addresses is greater than the upper threshold, an alarm is reported.

MAC Address Detection Lower Threshold

60% to 100%

Multicast

Broadcast, Discard

Default: 90%

Default: Broadcast Unicast

Broadcast, Discard Default: Broadcast

Enable BPDU Transparent Transmission

Issue 03 (2013-02-20)



Specifies the lower threshold of MAC addresses detection. Specifies how to process unknown multicast packets. Specifies how to process unknown unicast packets. Specifies whether to transparently transmit BPDU packets.

500



Table 10-25 Basic PW parameters Field

Value Range

Description

Role

Working, Protection


Source NE



Sink NE



PW ID




Static


Forward Label



Issue 03 (2013-02-20)


501



Field

Value Range

Description

Reverse Label

For example, 20




Forward Type

Static Binding


Forward Tunnel



Reverse Type

Static Binding


Reverse Tunnel



Encapsulation Type


Issue 03 (2013-02-20)



502



Table 10-26 QoS parameters for service access ports Field

Value Range

Description

Role

For example, Working Source

Displays and specifies the role of a service access port. Based on different protection types, service access ports can function as different roles, for example, working source, working sink, protection source, protection sink, FRR source, and FRR sink.

SAI

-

Displays and specifies a service access port.

Direction

Ingress, Egress

Displays and specifies the direction of a service access port. l Ingress indicates the inbound direction of a service. l Egress indicates the outbound direction of a service.

Bandwidth Limited

Enabled, Disabled

Specifies or displays the bandwidth limit. If you set Bandwidth Limited to Enabled, bandwidth is limited based on the specified CIR, PIR, CBS, and PBS.




Issue 03 (2013-02-20)


503



Field

Value Range

Description


64-10000000

The Committed Burst Size (byte) parameter specifies the committed burst size.


Click A.10.27 Committed Burst Size (byte) for more information. Peak Information Rate (kbit/ s)



Peak Burst Size (byte)



Local QoS Policy

-

Displays the QoS policy at the local end.



Displays the service forwarding priority. Different values represent different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Issue 03 (2013-02-20)


504



Field

Value Range

Description

Default Packet Marking Color


Displays the default packet marking color. Based on the labels carried by packets, different colors are configured for marking the packets. Red packets have the highest priority.

Processing Mode of Green Packet



CoS of Green Packet


Displays the service class of the packets marked green. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Green Packet

Issue 03 (2013-02-20)

Green


Sets the color of packets to green.

505



Field

Value Range

Description

Processing Mode of Yellow Packet



CoS of Yellow Packet


Displays the service class of the packets marked yellow. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Yellow Packet

Yellow

Sets the color of packets to yellow.

Processing Mode of Red Packet



Issue 03 (2013-02-20)


506



Field

Value Range

Description

CoS of Red Packet


Displays the service class of the packets marked red. CoS of packets defines different service classes. l CS6-CS7: indicate the highest service class, mainly applicable to signaling transmission. l EF: indicates expedited forwarding, applicable to services (for example, voice and video services) with low transmission delay and low packet loss rate. l AF1-AF4: indicate assured forwarding, applicable to services that require an assured rate rather than restricted delay or jitter. l BE: applicable to services that do not need special processing.

Color of Red Packet

-

Sets the color of packets to red.

VLAN Range

-

Specifies the VLAN range of packets.

10.4.3 UNI Parameters Setting the UNI parameters for an E-LAN service focuses on setting of the VLAN information about UNI ports. Table 10-27 lists the UNI parameters for an E-LAN service. Table 10-27 Parameters for a UNI port

Issue 03 (2013-02-20)

Field

Value

Description

Port




507



Field

Value

Description

VLANs

1 to 4094


Enabled Broadcast Packet Suppression

Enabled and Disabled

Sets whether to enable the broadcast packet suppression. Enabling the broadcast packet suppression efficiently prevents the broadcast storm and network congestion, and ensures the normal running of services. The E-LAN service supports this parameter.

Broadcast Packet Suppression Threshold

0-100

Configures the threshold of the broadcast packet suppression. The E-LAN service supports this parameter.




Default: BE




Default: 30

When the broadcast packet suppression is enabled, the broadcast packets are suppressed if the following requirement is met: Occupancy rate of the broadcast packet to the bandwidth of the current port > the total bandwidth of the port x the suppression threshold x 1%. A low occupancy rate indicates that the number of broadcast packets that pass through the port is small. If the occupancy rate is 100%, it indicates that the broadcast packets that pass through the port are not suppressed.


Default: Green


10.4.4 NNI Parameters NNI parameters are used for NNI Ethernet services. According to different service bearer modes, NNI parameters include the parameters that are used for a PW, a port and a QinQ link.

Issue 03 (2013-02-20)


508



PW Table 10-28 Parameters for a PW Field

Value Range

Description

PW ID

For example, 123


PW Status

Enable, Disable

Specifies or displays the enable status of the PW.

PW Signaling Type

Static


PW Type



PW Direction

Bidirectional



MPLS


PW Ingress Label



l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l Other products: 16 to 32768. PW Egress Label



l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l Other products: 16 to 32768. Peer IP

Issue 03 (2013-02-20)




509



Field

Value Range

Description

Tunnel Type

MPLS


Tunnel No.

Tunnel ID


For example, 55 Control Word

No Use, Used First Default: -






Ping, None



Up, Down



Up, Down



Up, Down

The Competitive Working Status parameter specifies the running status of a PW. Click A.8.5 Competitive Working Status for more information. NOTE For the OptiX OSN equipment, Static can only be set to Up.

Request VLAN


TPID

Issue 03 (2013-02-20)




0x88A8

Identifies the protocol.


510



Port Table 10-29 Parameters for an NNI Port Field

Value Range

Description

Port


Specifies the network-side port.

QinQ Link Table 10-30 Parameters for a QinQ link Field

Value Range

Description

QinQ Link ID

For example, 5

Displays the QinQ link ID.

Port

For example, 21N1PETF8-10 (Port-10)

Displays the board and port.

S-Vlan ID

For example, 4

Displays the S-VLAN ID.

Direction

Ingress, Egress

Displays the direction of the service.

Bandwidth Limit

Enabled, Disabled

Displays the bandwidth limit. When Bandwidth Limit is set to Enabled, you can set Committed Information Rate and Peak Information Rate.

Issue 03 (2013-02-20)


For example, 16000

Displays the committed information rate, which is the guaranteed rate that can be provided to the service.

Committed Burst Size(byte)

-

Displays the committed burst size, which is the maximum flow size allowed for each burst.


For example, 20000

Displays the peak information rate, which is the maximum rate that can be provided for the service.

Maximum Burst Size(byte)

-

Displays the maximum burst size, which is the maximum flow size allowed for each excessive burst.


511



Field

Value Range

Description

Policy

Policy ID + Policy Name

Displays the QinQ policy.

For example, 1(policy1)

10.4.5 Split Horizon Group A split horizon group is a group of V-UNIs or V-NNIs that do not allow for interconnection at one station. The split horizon group prevents a cycling route and a loop. Table 10-31 lists the parameters for a split horizon group. Table 10-31 Parameters for a split horizon group Field

Value

Description

Split Horizon Group ID

1

The Split Horizon Group ID parameter identifies the split horizon group.

Default: -

Click A.3.11 Split Horizon Group ID(E-LAN Service) for more information. Split Horizon Group Member

For example, PW-100, 21-N1PETF8-1PORT1[90, 100]

The Split Horizon Group Member parameter indicates the logical port member in a split horizon group. Click A.3.12 Split Horizon Group Member (E-LAN Service) for more information.

10.4.6 MAC Address Learning Parameters This topic describes the parameters, such as Aging Ability, Aging Time, and Address Table Specified Capacity, for configuring the MAS address learning function. Table 10-32 lists the parameters for MAC address learning. Table 10-32 Parameters for MAC address learning

Issue 03 (2013-02-20)

Field

Value

Description

Aging Ability

Enabled, Disabled

If no packets of an MAC address listed in the MAC address table are received during a period, the MAC address is deleted from the MAC address table.


512



Field

Value

Description

Aging Time (min)

1-640

Set the Aging Time (min) parameter to set the aging time of the learnt MAC address. The Aging Time (min) parameter indicates that the MAC address is automatically aged after the timing is set.

Default: 5

Click A.3.8 Aging Time (min)(E-LAN Service) for more information. The value range varies according to the product.

Address Table Specified Capacity

Sets the capacity of the MAC address table.

l OptiX OSN 1500: 0 to 32768 l Other products: – In the case of the N4GSCC: 0 to 65536 – In the case of the N6GSCC: 0 to 131072 Address Detection Upper Threshold (%)

80-100

Sets a value of Address Table Specified Capacity to the upper threshold for address detection. The upper threshold needs to be higher than the value of Address Detection Lower Threshold (%). If the number of MAC addresses actually learnt is more than the upper threshold, the FDBSIZEALM_ELAN alarm is generated.

Address Detection Lower Threshold (%)

60-100

Sets a value of Address Table Specified Capacity to the lower threshold for address detection. The lower threshold needs to be lower than the value of Address Detection Upper Threshold (%).


Default: -

The Self-Learning MAC Address (E-LAN Service) parameter indicates that the MAC address is obtained by the board through selflearning. Click A.3.7 Self-Learning MAC Address (ELAN Service) for more information.

10.4.7 Unknown Frame Processing If the MAC address table fails to learn the MAC address of a packet, the MAC address table considers this packet as an unknown frame. Table 10-33 lists the parameters for unknown frame processing. Issue 03 (2013-02-20)


513



Table 10-33 Parameters for unknown frame processing Field

Value

Description

Frame Type

Unicast, Multicast

Displays the type of the received unknown frames.

Handing Mode

Discard, Broadcast

Selects the mode for handling the unknown frames. Discard indicates that unknown frames are directly discarded. Broadcast indicates that unknown frames are broadcast at the forwarding port.

Default: Broadcast

Total

For example, 2

Displays the count of unknown frames.

Selected

For example, 1

Displays the count of selected unknown frames.

10.4.8 Static MAC Address Static MAC addresses refer to a MAC address table manually set for the service. Entries in the MAC address table are not automatically aged. Hence, unnecessary entries need to be manually deleted. Table 10-34 lists the parameters for a static MAC address. For more information, click A.3.6 Static MAC Address (E-LAN Service). Table 10-34 Parameters for a static MAC address Field

Value

Description

VLAN ID

For example, 12

Sets the ID of the service.

MAC Address

For example, 00-e0fc-39-80-34

Sets a static MAC address.

Egress Interface

For example, PW-100

Sets the egress interface, which can be a PW, port or QinQ link.

10.4.9 Maintenance Association The maintenance association (MA) facilitates the connectivity check (CC) of a network that transports services. Table 10-35 lists the parameters for a maintenance association. Table 10-35 Parameters for a maintenance association

Issue 03 (2013-02-20)

Field

Value

Description


1-8 characters



514



Field

Value

Description


1-8 characters



3.33ms, 10ms, 100ms, 1s, 10s, 1m, 10m


Default: 1s


10.4.10 MEP Point The MEP point is the edge point in an MA. Table 10-36 lists the parameters for an MEP point. Table 10-36 Parameters for an MEP point

Issue 03 (2013-02-20)

Field

Value

Description


1-8 characters



1-8 characters


Board



Port



Node



VLAN

For example, 22



515



Field

Value

Description

MEP ID

1-8191


Direction

Ingress, Egress


CC Status

Active, Inactive


10.4.11 V-UNI Group A V-UNI group is a user-side logical interface group, which associates specified interfaces with specified Ethernet services. Table 10-37 lists the parameters for a V-UNI group. Table 10-37 Parameters for a V-UNI group

Issue 03 (2013-02-20)

Field

Value

Description

V-UNI Group ID

For example, 123

Sets and queries the ID of the V-UNI group.

V-UNI Group Type

Ingress, Egress

Ingress indicates the in-coming network direction. Egress indicates the out-going network direction.

CIR (Kbit/s)

-

Sets the committed information rate (CIR).

PIR (kbit/s)

128 to 10000000

Sets the maximum traffic size for each burst. The committed burst size should not exceed the maximum packet length.

CBS (byte)

-

Sets the maximum rate for the service. The peak information rate should not be less than the committed information rate.

PBS (byte)

For example, 500000

Sets the maximum traffic size for the excessive burst. The maximum burst size should not be less than the extra burst buffer size.

Service ID

For example, 12

Sets the ID of the created Ethernet service.

Interface

For example, 21N1PETF8-1(Port14)

Displays the V-UNI interface selected by the service in the format of Slot number - Board name - Port number (VLAN ID).

Selecting Interface

-

Displays the available service IDs and V-UNI interfaces for the service.


516



Field

Value

Description

Selected Interface

-

Displays the selected service ID and V-UNI interface for the service.

10.5 Parameter Description: E-AGGR Service This topic describes the parameters related to the E-AGGR service configuration.

10.5.1 E-AGGR Service Parameters (on a Per-NE Basis) This topic describes parameters, such as Service ID, Service Name, and MTU(bytes), for configuring an E-AGGR service. Table 10-38 lists the parameters for configuring an E-AGGR service. Table 10-38 Parameters for configuring an E-AGGR service Field

Value

Description

Service ID

For example, 11


Service Name

For example, test


MTU (bytes)

64 to 9000

Sets the maximum transport unit (MTU). When receiving packets of a length more than the MTU, the port segments the packets and then transports these segments. If the packets contain a flag indicating that packet division is not allowed, the port discards the packet.

Default: 1500

10.5.2 Parameters for Configuring E-AGGR Services (End-to-End Mode) This topic describes the parameters for configuring E-AGGR services in end-to-end mode. Table 10-39 Basic parameters for E-AGGR services Field

Value Range

Description

Service ID


Specifies the ID of each EAGGR service. The service ID is unique on an NE.

Default: Auto-Assign Service Name

Manually enter it. For example, E-Aggr-1

Issue 03 (2013-02-20)


Displays and specifies the name of each E-AGGR service. 517



Field

Value Range

Description

MTU (bytes)

46 to 9000

Specifies the maximum transport unit (MTU). When a port receives a packet longer than the MTU that is specified for the port, the port slices the packet and transports these slices. If the packet contains a flag indicating that packet slicing is not allowed, the port discards the packet.

Default: 1500

Service Tag

-

Specifies the service tag role. l User: C-VLAN/S-VLAN tags of packets are used as user VLAN tags, and are processed when the packets are forwarded. l Service: C-VLAN/SVLAN tags of packets are used as service VLAN tags, and are not processed when the packets are forwarded. NOTE For E-AGGR services, this parameter cannot be set.

Table 10-40 Parameters in node lists Field

Value Range

Description

Location

Source, Sink

-

Unterminated

Yes, No

Specifies whether a node is an unterminated node. NOTE If a node is not managed by the U2000, the node is an unterminated node.

Node

NE-Slot ID-Board-Port

Displays and specifies the source and sink nodes of a service. NOTE For unterminated nodes, manually enter their IP addresses.

VLAN ID

Issue 03 (2013-02-20)

For example, 20


-

518



Field

Value Range

Description

Priority

0 to 7

Specifies a QoS level. When a network is congested, packets with higher VLAN priorities are processed and packets with lower VLAN priorities may be discarded. Value 0 represents the lowest priority, and value 7 represents the highest priority.

CE

-

Specifies a customer edge, which is directly connected to a provider edge (PE) to receive user-side services.

CE Interface

-

Specifies the CE's port that is connected to a PE.

CE Interface IP Address

-

Specifies the IP address of the CE's port that is connected to a PE.

Field

Value Range

Description

Source NE

NE


Sink NE

NE


PW ID




Default: Auto-Assign Signaling Type

Static

Displays and specifies the signaling type of a PW. If you set Signaling Type to Static, manually specify the PW ingress label and PW egress label. If you set Signaling Type to Dynamic, the system automatically allocates the PW ingress label and PW egress label.

Issue 03 (2013-02-20)


519



Field

Value Range

Description

Forward Label

For example, 20

Displays and specifies the label that the service carries when entering a PW.


l If you set Signaling Type to Dynamic, Forward Label is automatically allocated by the system and cannot be specified manually. l If you set Signaling Type to Static, Forward Label can be automatically allocated or manually specified.

For example, 20

Reverse Label


Displays and specifies the label that the service carries when leaving a PW. l If you set Signaling Type to Dynamic, Reverse Label is automatically allocated by the system and cannot be specified manually. l If you set Signaling Type to Static, Reverse Label can be automatically allocated or manually specified.

Static binding

Forward Type

Displays and specifies the binding type of a forward tunnel. NOTE The OptiX OSN equipment supports only Static binding.

Forward Tunnel


Displays and specifies the name of a forward tunnel.

Reverse Type

Static binding


Reverse Tunnel


Displays and specifies the name of a reverse tunnel. NOTE The OptiX OSN equipment supports only Static binding.

Issue 03 (2013-02-20)


520



Field

Value Range

Description

Encapsulation Type

MPLS

Displays and specifies the encapsulation type of a PW.

NOTE If you set Encapsulation Type to MPLS, Tunnel Type may be MPLS, IP, or GRE. If you set Encapsulation Type to UDP, Tunnel Type is IP only.

NOTE The OptiX OSN equipment supports only MPLS tunnel.

Table 10-42 Parameters in the VLAN forwarding table Field

Value Range

Description

Source SAI


Displays and specifies a source service interface.

Source VLAN ID

1 to 4094

Displays and specifies a source VLAN ID.

PW ID



Default: Auto-Assign Transit VLAN ID

1 to 4094

Displays and specifies a transit VLAN ID.

Sink SAI


Displays and specifies a sink service interface.

Sink VLAN ID

1 to 4094

Displays and specifies a sink VLAN ID.

Table 10-43 Service bandwidth parameters

Issue 03 (2013-02-20)

Field

Value Range

Description

Direction

Forward, Reverse

Specifies the direction of a service.

Bandwidth Enabled

Enabled, Disabled

If you set Bandwidth Enabled to Enabled, bandwidth is limited based on the specified CIR, CBS, PIR, and PBS.


521



Field

Value Range

Description

CIR (kbit/s)

1024-10000000, Unlimited

The Committed Information Rate (Kbit/s) parameter specifies the CIR of the queue. The packets whose rates are less than the CIR can be forwarded. When the rate of the packets is not more than the CIR, all messages can be forwarded. If the rate of the packets is more than the CIR, some packets are discarded according to a certain packet discarding policy.


Click A.10.26 Committed Information Rate (Kbit/s) for more information. 64-10000000

CBS (bytes)


The Committed Burst Size (byte) parameter specifies the committed burst size. Click A.10.27 Committed Burst Size (byte) for more information.

64-10000000

PIR (kbit/s)



64-10000000

PBS (bytes)



10.5.3 UNI Parameters Setting the UNI parameters for an E-Aggr service focuses on setting of the VLAN information about UNI ports. Table 10-44 lists the UNI parameters for an E-Aggr service.

Issue 03 (2013-02-20)


522



Table 10-44 Parameters for a UNI port Field

Value

Description

ID

For example, 1

Displays the ID of the UNI port.

Location

Source, Sink

Displays the location of the UNI port.

Port



VLANs

1 to 4094





Default: BE





Default: Green


10.5.4 NNI Parameters NNI parameters are used for NNI Ethernet services. According to different service bearer modes, NNI parameters include the parameters that are used for a PW or a port.

PW Table 10-45 Parameters for a PW

Issue 03 (2013-02-20)

Field

Value

Description

ID

For example, 1

Displays the sequence of the PWs. This parameter is required for the E-AGGR service.

Location

Source, Sink

Specifies the location of the node on the PW. This parameter is required for the E-AGGR service.

PW ID

For example, 123


PW Status

Enable, Disable

Specifies or displays the enabling status of the PW.


523



Field

Value

Description

PW Signaling Type

Static


PW Type



PW Direction

Bidirectional



MPLS


PW Ingress Label



l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l OptiX OSN 3500: 16 to 32768. PW Egress Label



l OptiX OSN 1500: Only 2048 consecutive values are allowed in the value range from 16 to 32768. l OptiX OSN 3500: 16 to 32768. Peer IP



Tunnel Type

MPLS


Tunnel No.

Tunnel ID


For example, 55

Issue 03 (2013-02-20)


524



Field

Value

Description

Control Word

Preferred Use, No Use

The Control Word parameter specifies the PW control word usage policy.

No Use, Used First


Default: -

Click A.8.1 Control Word for more information.

None, CW

The Control Channel Type parameter specifies the type of channels for transmitting VCCV packets.

Default: CW

Click A.8.2 Control Channel Type for more information. VCCV Verification Mode

Ping, None



Up, Down



Up, Down



Up, Down

The Competitive Working Status parameter specifies the running status of a PW. Click A.8.5 Competitive Working Status for more information. NOTE For the OptiX OSN equipment, Static can be set to only Up.

Request VLAN


TPID

Issue 03 (2013-02-20)




0x88A8

Displays the protocol identification.


525



Port Table 10-46 Parameters for an NNI port Field

Value

Description

ID

For example, 1

Displays the sequence of the PWs. This parameter is required for the E-AGGR service. This parameter is required for the E-AGGR service.

Location

Source, Sink

Specifies the location of the port involved in the service. This parameter is required for the EAGGR service. This parameter is required for the E-AGGR service.

Port


Specifies the network-side port. This parameter is required for the E-AGGR service.

10.5.5 VLAN Forwarding Table Item The VLAN forwarding table item is used for interconnection between the service traffic of source interface and that of the sink interface, and for VLAN switching. Table 10-47 lists the parameters for VLAN forwarding table items. Table 10-47 Parameters for VLAN forwarding table items Field

Value

Description


V-UNI, V-NNI

Set the Source Interface Type parameter to set the source interface type of the VLAN switching table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Default: -

Click A.3.13 Source Interface Type(E-AGGR Service) for more information.

Issue 03 (2013-02-20)

Source Interface

For example, [Port]3PEG16-1(Port-1)

Selects and queries the source interface. If Source Interface Type is set to V-NNI, the sink interface can be a port or PW.

Source VLAN ID

1-4094

Sets and queries the source VLAN ID.


526



Field

Value

Description

Sink Interface Type

V-UNI, V-NNI

Set the Sink Interface Type parameter to set the sink interface type of the VLAN switching table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Default: -

Click A.3.14 Sink Interface Type(E-AGGR Service) for more information. Sink Interface

For example, 3PEG16-1(Port-1)

Selects and queries the sink interface. If Sink Interface Type is set to V-NNI, the sink interface can be a port or PW.

Sink VLAN ID

1-4094

Sets and queries the sink VLAN ID.

10.5.6 Maintenance Association The maintenance association (MA) facilitates the connectivity check (CC) of a network that transports services. Table 10-48 lists the parameters for a maintenance association. Table 10-48 Parameters for a maintenance association Field

Value

Description


1-8 characters



1-8 characters



3.33ms, 10ms, 100ms, 1s, 10s, 1m, 10m


Default: 1s


Issue 03 (2013-02-20)


527



10.5.7 MEP Point The MEP point is the edge point in an MA. Table 10-49 lists the parameters for an MEP point. Table 10-49 Parameters for an MEP point Field

Value

Description


1-8 characters



1-8 characters


Board



Port



Node



VLAN

For example, 22


MEP ID

1-8191


Direction

Ingress, Egress


CC Status

Active, Inactive


10.6 Parameter Description: CES Port Before configuring a CES service, you must configure the CES port.

10.6.1 Channelized STM-1 Port Configuring a channelized STM-1 port includes setting of the parameters such as the encapsulation type of the port, the maximum data packet size, and the enabling status of the laser.

Issue 03 (2013-02-20)


528



Table 10-50 Parameters for the attributes of an SDH port Field

Value Range

Description

Port

For example, 21-CQ1-1 (PORT-1)


Name

For example, port1

Specifies the name of the port specified by the user.

Port Mode

Layer 1

Displays the working mode of the CES port Layer 1 indicates the channelized STM port is currently available. The OptiX OSN equipment currently supports only Layer 1 in Port Mode. In this case, the OptiX OSN equipment can transmit channelized STM-1 services.

Encapsulation Type

Null

Indicates the link layer encapsulation type of the port. It specifies the link layer encapsulation type that can be identified and processed by the port. When Encapsulation Type is set to Null, no link layer encapsulation is available or the link layer encapsulation is not performed. The OptiX OSN equipment currently supports only Layer 1 in Port Mode. For this reason, Encapsulation Type can only be set to Null and cannot be changed.

Channelize

No

Displays whether the port is a channelized port. Channelize refers to the use of the low-speed tributary signals in the STM-N service. One fiber is used to transmit multiple channels of data that are separated from each other. Each channel of data exclusively occupies the bandwidth, in addition to the starting point, terminating point, and monitoring policy.

Issue 03 (2013-02-20)


529



Field

Value Range

Description

Max Data Packet Size (byte)

-

Specifies the maximum size of the packets that can be received by the port. This parameter is currently inapplicable to the OptiX OSN equipment.

Laser Interface Enabling Status

On, Off Default: On

Laser Transmission Distance (m)

Specifies the enabling status of the laser on the port. Displays the transmission distance of the laser on the port. This parameter is currently inapplicable to the OptiX OSN equipment.

Scrambling Capability

-

Suppresses multiple 0s and 1s in the data when the Scrambling Capability is enabled. This parameter is currently inapplicable to the OptiX OSN equipment.

CRC Check Length

-

Specifies the length of the CRC field in the mapping protocol. This parameter is currently inapplicable to the OptiX OSN equipment.

-

Clock Mode

The Clock Mode parameter specifies the re-timing mode of a port. NOTE This parameter is currently inapplicable to an SDH port.

Loopback Mode

Issue 03 (2013-02-20)

Non-loopback, Inloop, Outloop

Specifies the loopback status of the port.

Default: Non-loopback

The loopback mode is used for locating a fault. Outloop is used for testing whether the port module and external fiber or cable of a board are proper. Inloop is used for testing whether the crossconnect unit and service path of the equipment are proper.


530



Field

Value Range

Description

CES Encapsulation Clock Mode

Null, Line Clock Mode, System Clock Mode

Specifies the encapsulation mode of the clock signal on a UNI port on the master side of the CES service.

Default: Null

l Null: The clock signal is not encapsulated in the service packets. l Line Clock Mode: The clock frequency signal extracted on a line port is used as the time stamp, which is encapsulated in the RTP packet header and transmitted to the downstream. l System Clock Mode: The system frequency signal is used as the time stamp, which is encapsulated in the RTP packet header and transmitted to the downstream. CES Encapsulation Clock Poke

-

Specifies the enabling status of the CES encapsulation clock poke. This parameter is currently inapplicable to the OptiX OSN equipment.

Table 10-51 Parameters for an associated service Field

Value Range

Description

Service Type

For example, CES service

Displays the type of the service associated with the port.

Service ID

For example, 20

Displays the ID of the service associated with the port. When you select the value of the service ID, the active window changes to the service management dialog box of the corresponding service type.

Issue 03 (2013-02-20)


531



Field

Value Range

Description

Service Name

For example, CES

Displays the name of the service associated with the port.

Used Resource

For example, 64K Timeslot1-31

Displays the resource used by the service associated with the port.

10.6.2 E1 Port In addition to the general attributes of an E1 port, you need to set the frame format based on the advanced attributes to ensure that the frame format specified for the E1 port is the same as the service encapsulation format. Table 10-52 Parameters for the general attributes of a PDH port Field

Value Range

Description

Port

Slot ID-Board name-Port (Port No.)


Name

For example, Port 1

Enters the port name specified by the user.

Port Mode

Layer 1, Layer 2, Layer 3

Specifies the working mode of the PDH port.

NOTE For the OptiX OSN equipment, Port Mode can be set to only Layer 1.

Encapsulation Type

Null

When this parameter is set to Layer 1, the port can transmit TDM signals. Specifies Encapsulation Type. When Port Mode is set to Layer 1, Encapsulation Type is defaulted to Null and cannot be changed.

Max Data Packet Size (byte)

-

Specifies the maximum size of the packets. NOTE This parameter is not applicable to an E1 port in the CES service.

Issue 03 (2013-02-20)


532



Table 10-53 Parameters for the advanced attributes of a PDH port Field

Value Range

Description

Port

Slot ID-Board name-Port (Port No.)


Frame Format

Unframe, Double Frame, CRC-4 Multiframe

Specifies the frame format.

Line Encoding Format

HDB3

When the E1 port transmits CES services in CESoPSN mode, this parameter can be set to Double Frame or CRC-4 Multiframe. It is recommended that you set this parameter to CRC-4 Multiframe. When the CES services are in SAToP mode, this parameter needs to be set to Unframe. Displays the line encoding format. The HDB3 codes are transmitted on the E1 port.

Clock Mode

Master Mode, Slave Mode, Line Clock Mode Default: Master Mode

The Clock Mode parameter specifies the re-timing mode of a port. Click A.4.4 Clock Mode for more information.

Loopback Mode



Impedance

75 ohm, 120 ohm

Displays the impedance of the port.

NOTE When the OptiX OSN 3500/7500 uses the N1MD75 board, Impedance is set to 75 ohm and cannot be changed. When the N1MD12 board is used, Impedance is set to 120 ohm and cannot be changed.

Frame Mode

-

Specifies the value of the frame mode. The frame modes of the local port and opposite port need to be consistent. NOTE This parameter is not applicable to an E1 port in the CES service.

Issue 03 (2013-02-20)


533



Field

Value Range

Description

CES Encapsulation Clock Mode

Null, Line Clock Mode, System Clock Mode

Queries the encapsulation mode of the clock signal on a UNI port on the master side of the CES service.

Default: Null

l Null: The clock signal is not encapsulated in the service packets. l Line Clock Mode: The clock frequency signal extracted on a line port is used as the time stamp, which is encapsulated in the RTP packet header and transmitted to the downstream. l System Clock Mode: The system frequency signal is used as the time stamp, which is encapsulated in the RTP packet header and transmitted to the downstream. CES Encapsulation Clock Poke

-

Queries the encapsulation time stamp in the CES service. NOTE This parameter is not applicable to an E1 port in the CES service.

Idle Timeslot Recovery Value

-

Queries the recovery value of an idle timeslot in the CES service. NOTE This parameter is not applicable to an E1 port in the CES service.

Table 10-54 Parameters for an associated service

Issue 03 (2013-02-20)

Field

Value Range

Description

Service Type

For example, CES service

Displays the type of the service associated with the port.


534



Field

Value Range

Description

Service ID

For example, 20


Service Name

For example, CES


Used Resource

For example, 64K Timeslot1-31


10.7 Parameter Description: CES Services This section describes parameters for CES services.

10.7.1 Basic Configuration Parameters (UNI-UNI) This topic describes the parameters for configuring and querying the attributes of CES services. Table 10-55 Parameters for configuring and querying the attributes of CES services Field

Value Range

Description

Service ID (e.g.1,3-6)

For example, 1

Displays the ID of the service.

Service Name

For example, CES-1

Displays the name of the CES service.

Level

E1

Displays the level of the received CES service.

Mode

UNI-UNI

Displays the mode of the CES service. UNI-UNI indicates the CES service from the user side to the user side.

Source Board

Slot-Board Name-Port (Port No.)

Specifies the source board of the CES service.

For example, 33CQ1-1(PORT-1)

Issue 03 (2013-02-20)


535



Field

Value Range

Description

Source High Channel

For example, VC4-1

Specifies the source higher order path. For a line port, you need to set the number of the VC-4 path.

Source Low Channel (e.g. 1,3-6)

For example, 1

Specifies the source lower order path. For an E1 port, you need to specify the number of the E1 port; for a line port, you need to set the number of the VC-12 path.

Source 64K Timeslot (e.g. 1,3-6)

For example, 1 to 31

Specifies the source 64 kbit/s timeslot for compression. NOTE You must specify two or more 64 kbit/s timeslots.

Sink Board


Specifies the sink board of the CES service.

For example, 33CQ1-2(PORT-2) Sink High Channel

For example, VC4-1

Specifies the sink higher order path. For a line port, you need to set the number of the VC-4 path.

Sink Low Channel (e.g. 1,3-6)

For example, 1

Sink 64K Timeslot (e.g. 1,3-6)


Specifies the sink lower order path. For an E1 port, you need to specify the number of the E1 port; for a line port, you need to set the number of the VC-12 path. Specifies the source 64 kbit/s timeslot for compression. NOTE You must specify two or more 64 kbit/s timeslots.

10.7.2 Basic Configuration Parameters (UNI-NNI) This topic describes the parameters related to CES services that can be set and queried. Table 10-56 Parameters for the basic information of CES service management

Issue 03 (2013-02-20)

Field

Value Range

Description

Service ID (e.g.1,3-6)

For example, 1

Displays the ID of the service.


536



Field

Value Range

Description

Service Name

For example, CES-1

Displays the name of the CES service.

Level

E1

Displays the level of the received CES service.

Mode

UNI-NNI

Displays the mode of the CES service. UNI-NNI indicates the CES service from the user side to the network side.

Source Board


Specifies the source board of the CES service.

For example, 33CQ1-1(PORT-1) Source High Channel

For example, VC4-1

Specifies the source higher order path. For a line port, you need to set the number of the VC-4 path.

Source Low Channel (e.g. 1,3-6)

For example, 1

Specifies the source lower order path. For an E1 port, you need to specify the number of the E1 port; for a line port, you need to set the number of the VC-12 path.

Source 64K Timeslot (e.g. 1,3-6)


Specifies the source 64 kbit/s timeslot for compression. NOTE You must specify two or more 64 kbit/s timeslots.

Priority

-

Specifies the priority of the UNI. The priority of the UNI can be set to CS6, CS7, AF1, AF2, AF3, AF4, EF, or BE. NOTE This parameter is not applicable to CES services.

Issue 03 (2013-02-20)


537



Field

Value Range

Description

PW Type

CESoPSN, SAToP

Specifies the type of the PW. l CESoPSN: Indicates structureaware TDM circuit emulation service over packet switched network. Timeslot compression can be set. l SAToP: Indicates structureagnostic TDM over packet. Timeslot compression cannot be set.

Protection Mode

Unprotected, PW APS, Slave Protection Pair

Specifies the protection mode of the PW. If the working and protection PWs of multiple PW APS salve protection pairs respectively have the same source and sink with the working and protection PWs of the existing PW APS protection group. The slave protection pairs can be bound with the protection group to share the OAM resources and achieve synchronous detection/switching.

Table 10-57 General attributes of the PW Field

Value Range

Description

PW ID

For example, 1

Specifies the ID of the PW.

PW Signaling Type

Static

The PW Signaling Type parameter specifies the allocation mode (automatic or manual) of ingress and egress nodes of a PW. Click PW Signaling Type for more information.

PW Type

Ethernet, Ethernet Tagged Mode, CESoPSN, SAToP

Displays the type of the PW. l When Service Type is set to Ethernet Service, PW Type can be set to only Ethernet or Ethernet Tagged Mode. l When Service Type is set to CES Service, PW Type can be set to only CESoPSN or SAToP.

PW Direction

Issue 03 (2013-02-20)

Bidirectional

Displays the direction of the PW.


538



Field

Value Range

Description


MPLS

Displays the encapsulation type of the packets on the PW.

PW Ingress Label/Source Port

For example, 17

This parameter needs to be set when PW Signaling Type is set to Static.

NOTE The value ranges from 16 to 32768, in step of 2048. For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

PW Egress Label/Sink Port

For example, 18 NOTE The value ranges from 16 to 32768, in step of 2048.

This parameter needs to be set when PW Signaling Type is set to Static.

For the OptiX OSN 1500, the maximum value is 2048. For the OptiX OSN 3500/7500, the maximum value is 32768.

Tunnel Section Mode

Manually

Specifies the tunnel that carries the PW.

Tunnel Type

MPLS


Tunnel No.

For example, 43

A created tunnel needs to be selected. If no tunnel is available, no PW can be created.

Peer LSR ID


Specifies the LSR ID of the PW at the remote end.

10.7.3 QoS (UNI-NNI) This topic describes the QoS associated parameters used for configuring and querying CES services.

Issue 03 (2013-02-20)


539



Table 10-58 QoS parameters for CES service management Field

Value Range

Description

Attribute

EXP

Displays the QoS attribute. EXP: The value can be set only for the ingress node. The value 7 indicates the highest priority. EXP can be set according to the planning document.

Working PW Ingress Value

0-7, None Default: None

Specifies the value of the working PW ingress.

Working PW Egress Value

-

Specifies the value of the working PW egress.

Protection PW Ingress Value

0-7, None

Specifies the value of the protection PW ingress.

Default: None

NOTE When Protection Type is set to No Protection, this parameter cannot be set.

Protection PW Egress Value

-

Specifies the value of the protection PW egress. NOTE When Protection Type is set to No Protection, this parameter cannot be set.

10.7.4 Advanced Attributes (UNI-NNI) This topic describes the parameters for configuring and querying the advanced attributes of CES services. Table 10-59 Parameters for configuring and querying the advanced attributes of CES services Field

Value Range

Description

RTP Header

Disable, Enable the Huawei RTP, Enable a Standard RTP

The RTP Header parameter specifies whether the RTP header function is enabled.

Default: Disable

Click A.4.2 RTP Headerfor more information.

125-64000

The Jitter Compensation Buffering Time (us) parameter specifies the size of the jitter buffer.

Jitter Compensation Buffering Time (us)

Default: 8000

Click A.4.3 Jitter Compensation Buffering Time (us) for more information.

Issue 03 (2013-02-20)


540



Field

Value Range

Description


125-5000

The Packet Loading Time (us) parameter specifies the packet loading duration.

Default: 1000

Click A.4.1 Packet Loading Time (us) for more information. Ingress Clock Mode

-

Specifies the clock mode for the ingress PW of the CES service. NOTE This parameter is not applicable to PWs.

Egress Clock Mode

-

Specifies the clock mode for the egress PW of the CES service. NOTE This parameter is not applicable to PWs.


Enabled, Disabled Default: Disabled

Specifies whether the alarm information of the CES service can be transparently transmitted. If this function is enabled, the fault on the AC side of the CES service is notified to the remote end. On receiving the fault notification from the network side or the remote end, the local NE inserts the corresponding alarm on the AC side.

Threshold of Entering R bit 1 to 65535 Inserting Status Default: 100

Specifies the threshold of entering R bit inserting status. If the alarm information of the CES service is transparently transmitted and the number of consecutive lost packets crosses the threshold, the logic inserts the R bit to the network side and reports the corresponding alarm.

Threshold of Exiting R bit Inserting Status

1 to 65535 Default: 5

Specifies the threshold of exiting R bit inserting status. If the number of consecutive lost packets crosses the threshold, the logic quits inserting the R bit to the network side and reporting the corresponding alarm.

Issue 03 (2013-02-20)


541



Field

Value Range

Description


Standard Mode, Huawei Mode

Specifies the sequence number mode. l The standard mode is applicable to the network consisting of devices from Huawei and other manufacturers. l The Huawei mode is applicable to the network consisting of only Huawei devices.

Table 10-60 Parameters for the protection group in slave protection pair mode Field

Value Range

Description

Protection Mode

Slave Protection Pair

Displays Protection Mode as Slave Protection Pair.

Protection Group ID

For example, 1

Specifies the ID of the protection group by selecting a resource. The protection group ID needs to be manually specified.

Working PW ID

For example, 10

Displays the ID of the working PW. After Protection Group ID is set, the ID of the working PW is automatically assigned here.

Protection PW ID

For example, 20

Displays the ID of the protection PW. After Protection Group ID is set, the ID of the protection PW is automatically assigned here.

Table 10-61 Parameters for the protection group in PW APS mode Field

Value Range

Description

Protection Type

PW APS

Displays Protection Type as PW APS.

Protection Group ID

For example, 1

Specifies the ID of the protection group by selecting a resource. The protection group ID needs to be manually specified.

Enabling Status

Disabled, Enabled

Specifies whether the protection group is enabled or disabled.

Default: Disabled

Issue 03 (2013-02-20)


542



Field

Value Range

Description

Protection Mode

1+1, 1:1

The Protection Mode parameter specifies the protection type of a PW APS protection group.

Default: 1+1

Click A.9.1 Protection Mode for more information. Working PW ID

-

Displays the ID of the working PW. This parameter cannot be set if Protection Type is set to PW APS.

Protection PW ID

-

Displays the ID of the protection PW. This parameter cannot be set if Protection Type is set to PW APS.

Switchover Mode

Single-ended switching, Dual-ended switching

Displays the switching status of a protection group.

Restoration Mode

Non-Revertive, Revertive

Displays the restoration mode of the PW APS protection group.

Switchover WTR Time (mins)

1 to 12 Default: 1

Specifies the switchover restoration time.

Switchover Delay Time (100ms)

0 to 100

Specifies the switchover delay time.

Default: 0

Table 10-62 Parameters for PW OAM in PW APS mode Field

Value Range

Description

OAM Status

Disabled, Enabled

Specifies the status of PW OAM. l Enabled: The PW OAM can be performed. l Disabled: The PW OAM cannot be performed.

Detection Mode

Auto-Sending, Manual Default: Auto-Sending

Displays or specifies the detection mode. This parameter can be set only for the tunnel in Egress direction. l Manual: The connectivity check (CC) packets are sent at the interval specified by the user. l Auto-Sending: The connectivity check (CC) packets are sent at the interval of packet receiving.

Issue 03 (2013-02-20)


543



Field

Value Range

Description


CV, FFD

Specifies the type of the detection packet.

Default: CV

l CV: The detection packets are sent at a fixed interval. l FFD: The detection packets are sent at the interval specified by the user. Detection Packet Period (ms)

3.3, 10, 20, 50, 100, 200, 500

Displays or specifies the detection packet period. If Detection Packet Type is FFD, this parameter can be set; if Detection Packet Type is CV, the value is always 1000.

LSR ID to Be Received


Specifies the LSR ID to be received.

Transmitted PW ID

For example, 1

Specifies the transmitted PW ID.

10.7.5 Parameters for Configuring CES Services (End-to-End Mode) This topic describes the parameters for configuring CES services in end-to-end mode. Table 10-63 Parameters for configuring PWE3 services Field

Value Range

Description

Service Template

DEFAULT_PWE3_CES_P TN, DEFAULT_PWE3_ETH_P TN

Displays and specifies the PWE3 service template. Service Type varies with Service Template.

NOTE The OptiX OSN equipment does not support the following service templates:

Service Template improves service configuration efficiency.

NOTE This parameter is optional and helps users quickly configure various services. If the parameter value is not specified, subsequent service configuration is not affected.

l DEFAULT_PWE3_ATM_ ROUTER l DEFAULT_PWE3_CES_ ROUTER l DEFAULT_PWE3_ETH_ ROUTER l DEFAULT_PWE3_IWF_ ROUTER l DEFAULT_PWE3_IP_R OUTER

Issue 03 (2013-02-20)


NOTE After you select a service template, a dialog box is displayed, saying After the template is changed, the parameters not contained in the new template may be lost. Are you sure to continue? You can also select Apply the template data to the configured Objects.

544



Field

Value Range

Description

Service Type

ETH, CES

Displays and specifies the type of each PWE3 service.

NOTE Specifies the required service type based on service configuration. When the equipment is configured with PWE3 Ethernet services, Service Type is set to ETH. When the equipment is configured with PWE3 CES services, Service Type is set to CES.

Service ID

Auto-Assign, or manually enter it. Default: Auto-Assign

Service Name


Protection Type

Protection-Free

Specifies the ID of each PWE3 service. The service ID is unique on the entire network. Displays and specifies the name of each PWE3 service.

Specifies the protection type for the service. If Protection Type is PW Redundancy, you need to select Single Source and Dual Sink from Node List. If Protection Type is PW APS, you need to select Dual Source and Single Sink from Node List. If you select Single Source and Dual Sink, you need to configure one source node and two sink nodes. If you select Dual Source and Single Sink, you need to configure two source nodes and one sink node. One PW functions as the working path and the other PW functions as the protection path.

Description


Customer

Issue 03 (2013-02-20)

-


Displays and specifies the service description.

Displays and specifies the customer to which a service belongs.

545



Field

Value Range

Description

Remarks

-

Displays and specifies the service remarks.

Table 10-64 Basic PW parameters Field

Value Range

Description

Role

Working, Protection


Source NE



Sink NE



PW ID




Static


Forward Label



Issue 03 (2013-02-20)


546



Field

Value Range

Description

Reverse Label

For example, 20




Forward Type

Static Binding


Forward Tunnel



Reverse Type

Static Binding


Reverse Tunnel



Encapsulation Type



10.8 Parameter Description: ATM/IMA Services This section describes parameters for ATM/IMA services.

10.8.1 Creating an ATM Service This section describes the parameters for creating an ATM service. Issue 03 (2013-02-20)


547



Table 10-65 lists the parameters for creating an ATM service. Table 10-65 Parameters for creating an ATM service Field

Value

Description

Service ID

1 to 4294967295

Specifies the service ID.

Default: none

Set this parameter according to the planning information.

-

Specifies the service name.

Service Name

Set this parameter according to the planning information. Service Type

UNIs-NNI, UNI-UNI Default: UNIs-NNI

Specifies the type of the ATM service. l UNIs-NNI: This value applies to ATM PWE3 services. The attributes in Connection, PW, and CoS Mapping need to be configured. l UNI-UNI: This value applies to common ATM services. Only the attributes in Connection need to be configured. Set this parameter according to the planning information.

Issue 03 (2013-02-20)


548



Field

Value

Description

Connection Type

PVP, PVC, Port Transparent

Specifies the connection type of the ATM service.

l If Service Type is UNIsNNI, the default value is PVC. l If Service Type is UNI-UNI, the default value is PVP.

l PVP: Only the VPIs of the source and sink are exchanged. l PVC: The VPIs and VCIs of the source and sink are exchanged. For ATM PWE3 services (UNIsNNI): l PVP: This value applies to the N-to-1/1-to-1 VPC encapsulation mode. l PVC: This value applies to the N-to-1/1-to-1 VCC encapsulation mode. Port Transparent: This value applies if all services regardless of their VPIs and VCIs are transparently transmitted. Set this parameter according to the planning information. For details, see A.13.9 Connection Type(Per-NE ATM Service Management).

Protection Type

Unprotected, PW APS, Slave Protection Pair

Specifies the protection type of the PW.

Default: Unprotected

This parameter is available only when Service Type is UNIsNNI. Set this parameter according to the planning information.

10.8.2 Connection This section describes the parameters for creating a connection. Table 10-66 lists the parameters for creating a connection.

Issue 03 (2013-02-20)


549



Table 10-66 Parameters for creating a connection Field

Value

Description

Connection Name

A character string of less than 64 characters, which may contain letters, numbers, Chinese characters, or special symbols.

Specifies a name for an ATM connection. Set this parameter according to the planning information.

Example: 28-N1D12E Source Board

Slot ID-board name Example: 28-N1D12E

Specifies the source board of the ATM service. Set this parameter according to the planning information.

Source Port

Port ID(Port-port ID) Example: 1(Trunk-1)

Specifies the source port of the ATM service. Set this parameter according to the planning information.

Source VPI (example:35,36-39)

Source VCI (example:35,36-39)

ATM UNI cell: 0 to 255 NNI ATM cell: 0 to 4095

Specifies the VPI of the source port of the ATM service.

Default: none


32 to 65535

Specifies the VCI of the source port of the ATM service.

Default: none

This parameter does not need to be set if Connection Type is PVP. Set this parameter according to the planning information. PW ID

1 to 4294967295 Default: none

Specifies the ID of the PW that carries ATM services. Set this parameter according to the planning information.

Sink Board

Slot ID-board name Example: 28-N1D12E

Specifies the sink board of the ATM service. l This parameter does not need to be set if Service Type is UNIs-NNI. l This parameter needs to be set if Service Type is UNI-UNI. Set this parameter according to the planning information.

Issue 03 (2013-02-20)


550



Field

Value

Description

Sink Port

Port ID(port-port ID)

Specifies the sink port of the ATM service.

Example: 1(Trunk-1)

l This parameter does not need to be set if Service Type is UNIs-NNI. l This parameter needs to be set if Service Type is UNI-UNI and its value must be different from that of the source port. Set this parameter according to the planning information. Sink VPI(example: 35,36-39)

Sink VCI(example: 35,36-39)

UNI ATM cell: 0 to 255 NNI ATM cell: 0 to 4095

Specifies the VPI of the sink port of the ATM service.

Default: none


32 to 65535

Specifies the VCI of the sink port of the ATM service.

Default: none

This parameter does not need to be set if Connection Type is PVP. Set this parameter according to the planning information. -

Uplink Policy

Specifies the QoS policy of the uplink ATM connection (from the source direction to the sink direction). For details, see A.13.10 Uplink Policy(Per-NE Configuration for ATM Connections). Set this parameter according to the planning information.

Downlink Policy

-

Specifies the QoS policy of the downlink ATM connection (from the sink direction to the source direction). For details, see A.13.11 Downlink Policy(Per-NE Configuration for ATM Connections). Set this parameter according to the planning information.

Issue 03 (2013-02-20)


551



10.8.3 CoS Mapping This section describes the parameters for CoS mapping. Table 10-67 lists the parameters for CoS mapping. Table 10-67 Parameters for CoS mapping Field

Value

Description

PW ID

-

Displays the ID of the PW that carries services.

CoS Mapping

Mapping Relation ID(Mapping Relation Name)

Specifies the policy for mapping different ATM service classes to CoS priorities. By setting this parameter, different quality levels are provided for different ATM services.

Default: 1(DefaultAtmCosMap)

Set this parameter according to the planning information. For details, see A.13.12 CoS Mapping(Per-NE Configuration for CoS Mapping).

10.8.4 Configuring an ATM Service Class Mapping Table This section describes the parameters for configuring an ATM service class mapping table. Table 10-68 lists the parameters for configuring an ATM service class mapping table. Table 10-68 Parameters for configuring an ATM service class mapping table Field

Value

Description

Mapping Relation ID

2 to 8

Specifies the ID of the ATM service class mapping table.

Default: none

NOTE 1 is the default ID for the ATM service class mapping table.

Set this parameter according to the planning information. Mapping Relation Name

A character string of less than 32 characters, which may contain letters, numbers, and underlines. For example: mapping_1

Issue 03 (2013-02-20)


Specifies the name of ATM service class mapping table. Set this parameter according to the planning information.

552



Field

Value

Description

UBR

BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, CS6, CS7 Default: UBR: BE CBR: EF RT-VBR: AF31 NRT-VBR: AF21 UBR+: AF11 PORT-TRANS: BE

Displays or specifies the PHBs that correspond to different ATM service categories. l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 for eight queues. Different QoS policies are provided for the queues of different PHBs. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits.

CBR RT-VBR NRT-VBR UBR+ PORT-TRANS

NOTE The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4.

l BE: best effort, applicable to services that do not require special processing. Set this parameter according to the planning information.

10.8.5 ATM Policies This section describes the parameters for configuring ATM policies. Table 10-69 lists the parameters for configuring ATM policies.

Issue 03 (2013-02-20)


553



Table 10-69 Parameters for configuring ATM policies Field

Value

Description

Policy ID

1 to 256

Specifies the policy ID of the ATM service.

Default: 1

Set this parameter according to the planning information. Assign automatically

Selected, Not selected Default: Not selected

Specifies whether the ID is automatically assigned. Set this parameter according to the planning information.

Policy Name

Synchronous Signal, Signaling, Voice, Data, Video, or an entered character string

Specifies the policy name of the ATM service. The maximum length of the value is 64 bytes.

Default: Synchronous Signal

NOTE You can select one of the five ATM service policy names from the dropdown list or enter the policy name.


Issue 03 (2013-02-20)


554



Field

Value

Description

Service Type

UBR, CBR, RT-VBR, NRTVBR, UBR+

Specifies the type of the ATM service.

Default: UBR

l The UBR service is characterized by non-realtime applications and many bursts. The UBR service does not specify traffic-related service guarantees. To be specific, the UBR service only requires that the network side provides the service with the best effort. The network side does not provide any assured QoS for the UBR service. In the case of network congestion, the UBR cells are discarded first. l The CBR service requires tightly constrained delay variation and requires that data be transmitted at a constant rate. In addition, the CBR service requests a static amount of bandwidth and the highest priority. The CBR service is characterized by stable traffic and few bursts. l The RT-VBR service requires tightly constrained delay and delay variation. Compared with the CBR service, the RT-VBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be described as bursty. In addition, the RTVBR service does not require a static amount of bandwidth. l Compared with the RTVBR service, the NRT-VBR service does not require tightly constrained delay or delay variation, and is intended for non-real-time applications. l The UBR+ service is supplementary to the UBR service and is intended for

Issue 03 (2013-02-20)


555


Field

Value


Description applications that require assured minimum cell rate, which is indicated by the minimum cell rate (MCR) parameter. The other characteristics of the UBR+ service are the same as the corresponding characteristics of the UBR service. Set this parameter according to the planning information.

Traffic Service

The value range and default value of Traffic Service vary with Service Type. For details, see A.13.13 Traffic Service(ATM Policy).

The Traffic Service parameter specifies the sub-type of a service type. That is, multiple traffic types are available for each type of service. A traffic type specifies the traffic parameters that can be set, the methods of handling cells whose cell loss priority (CLP) values are 0 and 1, and the supported functions (such as cell labeling). Set this parameter according to the planning information. For details, see A.13.13 Traffic Service(ATM Policy).

Clp01Pcr(cell/s)

90-149078 Default: None.

Specifies the peak cell rate of a service whose CLP in the ATM cell header is 1 or 0. Set this parameter according to the planning information. For details, see A.13.14 Clp01Pcr(cell/s)(ATM Policy).

Clp01Scr(cell/s)


Specifies the sustainable cell rate of a service whose CLP in the ATM cell header is 1 or 0. Set this parameter according to the planning information. For details, see A.13.15 Clp01Scr(cell/s)(ATM Policy).

Issue 03 (2013-02-20)


556



Field

Value

Description

Clp0Pcr(cell/s)

90-149078

Specifies the peak cell rate of a service whose CLP in the ATM cell header is 0.

Default: None.

Set this parameter according to the planning information. For details, see A.13.16 Clp0Pcr (cell/s)(ATM Policy). Clp0Scr(cell/s)


Specifies the sustainable cell rate of a service whose CLP in the ATM cell header is 0. Set this parameter according to the planning information. For details, see A.13.17 Clp0Scr (cell/s)(ATM Policy).

Clp01Mcr(cell/s)


Specifies the minimum transmission rate of cells whose CLP in the ATM cell header is 1 or 0. Set this parameter according to the planning information. For details, see A.13.18 Clp01Mcr(cell/s)(ATM Policy).

Max.Cell Burst Size (cell)


Specifies the maximum number of cells that are continuously transmitted on ATM path of a VBR service at a rate of r (SCR < r
Issue 03 (2013-02-20)


557



Field

Value

Description

Cell Delay Variation Tolerance(0.1us)

7 to 13300000

Specifies the burst cell tolerance of an ATM connection.

Default: None.

l The greater the parameter value, the better performance the service for burst cells. If conditions are allowed, you can set CDVT to a large value to minimize packet loss. l If UPC/NPC is enabled, The CDVT recommended that this parameter takes maximum value. For details, see A.13.20 Cell Delay Variation Tolerance (0.1us)(ATM Policy). Discard Traffic Frame

Enabled, Disabled Default: Disabled

Specifies the frame discarding mark in ATM policies. This parameter is effective to AAL5 traffic. It is recommended that this parameter takes the default value.

UPC/NPC

Disabled, Enabled Default: Disabled

The UPC/NPC parameter specifies the user-network interface (UNI) traffic parameters based on usage parameter control (UPC) and network parameter control (NPC). l Disabled: The configured ATM QoS parameters do not take effect. l Enabled: The configured ATM QoS parameters take effect. l It is recommended that this parameter takes Enabled. NOTE On the TNN1AFO1 board, UPC/ NPC cannot be enabled on the downlink ATM connection (from the sink to the source).

For details, see A.13.21 UPC/ NPC(ATM Policy).

Issue 03 (2013-02-20)


558



10.8.6 SDH Interface This section describes parameters for a SDH interface. Table 10-70 Descriptions of the parameters of the general attributes of an SDH port Field

Value

Description

Port

Slot ID-board name-port ID


Example: 36-N1AFO1-1 (PORT-1) Name

Port Mode

-

Displays or specifies the name of the port.

Example: Port1


Layer 2

Specifies the mode of the SDH port. The fixed value is Layer 2. Layer 2 indicates the current ATM STM port.

Encapsulatio n Type

ATM

Indicates the link layer encapsulation type of the port. It specifies the link layer encapsulation type that can be identified and processed by the port. The fixed value is ATM. ATM: The ATM encapsulation is identified and processed.

Channelize

No

Specifies whether the port is channelized. The fixed value is No. No: The port is not channelized.

Max Data Packet Size (bytes)

-

Specifies the maximum packet length. The fixed value is -.

Laser Interface Status

On, Off

Enables or disables the laser.

Default: On

The default value is recommended.

This parameter does not need to be set if Port Mode is Layer 2.

Table 10-71 Descriptions of the parameters for SDH interface Layer 2 Attributes Field

Value

Description

Port



Example: 36-N1AFO1-1 (PORT-1)

Issue 03 (2013-02-20)


559



Field

Value

Description

Port Type

UNI, NNI

Specifies the type of the ATM port.

Default: UNI

l UNI: the port connecting user-side devices. For example, the UNI port applies to the userside port on the common ATM network or to the user-side port of the PE on the PSN network that transmits ATM PWE3 services. l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side port on the common ATM network. Set this parameter according to the planning information.

ATM Cell Payload Scrambling

Enabled, Disabled Default: Enabled

The ATM Cell Payload Scrambling (ATM Interface Management) parameter specifies whether to scramble the payload of cells on asynchronous transfer mode (ATM) links. l ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to Enabled for both end of an ATM link. l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise, packet loss will occur. For details, see A.12.1 ATM Cell Payload Scrambling(ATM Interface Management).

Min. VPI

UNI port: 0-255; NNI port: 0-4095 Default: 0

The Min.VPI parameter specifies the minimum virtual path identifier (VPI) value of the permanent virtual paths (PVPs) and permanent virtual channels (PVCs) that are applicable to a selected board. For details, see A.12.2 Min.VPI(ATM Interface Management).

Max. VPI

UNI port: 0-255; NNI port: 0-4095 Default: 255

Min. VCI

0-65535 Default: 65535

The Max. VPI parameter specifies the maximum virtual path identifier (VPI) value of the permanent virtual paths (PVPs) and permanent virtual channels (PVCs) that are applicable to a selected board. The Min.VCI parameter specifies the minimum virtual channel identifier (VCI) value for permanent virtual channels (PVCs) that are applicable to a selected board. For details, see A.12.3 Min.VCI(ATM Interface Management).

Issue 03 (2013-02-20)


560



Field

Value

Description

Max. VCI

0-65535

The Max VCI parameter specifies the maximum virtual channel identifier (VCI) value for permanent virtual channels (PVCs) that are applicable to a selected board.

Default: 65535

VCCSupported VPI Count

0-256, 65535 Default: 65535

The VCC-Supported VPI Count parameter specifies the number of virtual path identifiers (VPIs) available for a permanent virtual channel (PVC) connection at a port. That is, only the specified number of VPIs can be adopted for establishment of a PVC connection regardless of the specified VPI value. In other circumstances, the specified number of VPIs can be adopted for establishment of a permanent virtual path (PVP) connection. For details, see A.12.4 VCC-Supported VPI Count(ATM Interface Management).

Table 10-72 Descriptions of the parameters for Advanced Attributes of the SDH interface Field

Value

Description

Port



Example: 36-N1AFO1-1 (PORT-1) Laser Transmissio n Distance (m)

-

Scrambling Capability

-

Display the transmission distance of the laser. The fixed value is -. The Hybrid MSTP does not support this parameter. Suppresses multiple 0s and 1s in the data when the Scrambling Capability is enabled. The fixed value is -. The Hybrid MSTP does not support this parameter.

CRC Check Length

-

Specifies the length of the CRC field in the mapping protocol. The fixed value is -. The Hybrid MSTP does not support this parameter.

Clock Mode

-

Specifies the re-timing mode of a port. The fixed value is -. The Hybrid MSTP does not support this parameter.

Issue 03 (2013-02-20)


561



Field

Value

Description

Loopback Mode



Default: Non-loopback

The loopback mode is used for locating a fault. Outloop is used for testing whether the port module and external fiber or cable of a board are proper. Inloop is used for testing whether the cross-connect unit and service path of the equipment are proper. Set this parameter according to the planning information.

10.8.7 IMA Group Management This section describes the parameters for configuring the management of an IMA group. Table 10-73 and Table 10-74 list the parameters for configuring the management of an IMA group. Table 10-73 Parameters for configuring the management of an IMA group Field

Value

Description

VCTRUNK

Slot ID-board nameTrunk ID (Trunk-Trunk ID)

Specifies the ATM TRUNK that is the logical port on the board for carrying ATM services.

For example: 29N1D12E-1(Trunk-1) IMA Protocol Enable Status

Enabled, Disabled

Specifies the IMA protocol enable status.

Default: Disabled

l Set IMA Protocol Enable Status to Enabled if the links bound with the ATM TRUNK require the IMA protocol; otherwise, set this parameter to Disabled. l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound in the ATM TRUNK start running the IMA protocol.

Issue 03 (2013-02-20)


562



Field

Value

Description

Minimum Number of Active Transmitting Links

1-16

The Minimum Number of Active Transmitting Links parameter specifies the lower threshold of active links in the transmit direction in an inverse multiplexing for ATM (IMA) group to maintain proper operation of the IMA group.

Default: 1

l The links of the IMA group can carry services only when the number of activated links in the transmit/receive direction is not smaller than the value of Minimum Number of Active Transmitting Links/Minimum Number of Active Receiving Links. l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must be the same because the N1D12E/N1D75E supports Symmetrical Mode and Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must assume the same value on the two ends of an IMA link. l The default value is recommended. For details, see A.13.4 Minimum Number of Active Transmitting Links(IMA Group Management).

Issue 03 (2013-02-20)


563



Field

Value

Description

Minimum Number of Active Receiving Links

1-16

The Minimum Number of Active Receiving Links parameter specifies the lower threshold of active links in the receive direction in an inverse multiplexing for ATM (IMA) group to maintain proper operation of the IMA group.

Default: 1

l The links of the IMA group can carry services only when the number of activated links in the transmit/receive direction is not smaller than the value of Minimum Number of Active Transmitting Links/Minimum Number of Active Receiving Links. l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must be the same because the N1D12E/N1D75E supports Symmetrical Mode and Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must assume the same value on the two ends of an IMA link. l The default value is recommended. For details, see A.13.5 Minimum Number of Active Receiving Links(IMA Group Management). IMA Protocol Version

1.0, 1.1

Specifies the IMA protocol version.

Default: 1.1

l The parameter IMA Protocol Version must assume the same value on the two ends of an IMA link. l The default value is recommended.

Issue 03 (2013-02-20)


564



Field

Value

Description

IMA Transit Frame Length

32, 64, 128, 256

The IMA Transit Frame Length parameter specifies the length of an inverse multiplexing for ATM (IMA) frame transmitted by the equipment at the local end. That is, this parameter specifies the number of asynchronous transfer mode (ATM) cells in an IAM frame.

Default: 128

l Based on the IMA frame format, the receive end rebuilds the ATM cell stream with the cells arriving from diversely-delayed links. Longer IMA frames result in higher transmission efficiency and occupy more resources. Once a member link fails, the impact on the entire IMA group increases as the length of IMA frames increases. l The parameter IMA Transmit Frame Length must assume the same value on the two ends of an IMA link. l The default value is recommended. For details, see A.13.1 IMA Transit Frame Length. IMA Symmetry Mode

Symmetrical Mode and Symmetrical Operation, Symmetrical Mode and Asymmetrical Operation, Asymmetrical Mode and Asymmetrical Operation Default: Symmetrical Mode and Symmetrical Operation

The IMA Symmetry Mode parameter specifies the configuration and operation mode of inverse multiplexing for ATM (IMA) links in an IMA group. l The N1D12E/N1D75E supports Symmetrical Mode and Symmetrical Operation only. l If the symmetrical mode and symmetrical operation are adopted, the bandwidth of the IMA group is always consistent in the transmit direction and in the receive direction, even when some member links fail. In symmetrical mode: – Bandwidth of the IMA group = min {bandwidth in the transmit direction, bandwidth in the receive direction} – The unidirectional failure of one member link is equivalent to the bidirectional failure of one member link. For details, see A.13.2 IMA Symmetry Mode.

Issue 03 (2013-02-20)


565



Field

Value

Description

Maximum Delay Between Links(ms)

1-120

The Maximum Delay Between Links(ms) parameter specifies the maximum delay tolerance between links in an inverse multiplexing for ATM (IMA) group. That is, this parameter specifies the allowed maximum difference between the maximum delay value and the minimum delay value of all links in an IMA group. If the maximum difference exceeds the specified value, the equipment reports the lODS alarm for a link who has the largest offset value compared with the average delay value of all links in the MA group. Then, the equipment removes the alarmed link from the IMA group.

Default: 25

l If this parameter is set to a value greater than the allowed maximum value, the delay of IMA services may be prolonged and even packet loss may occur; if this parameter is set to a value smaller than the allowed minimum value, a working link will be deleted by mistake. l The parameter Maximum Delay Between Links (ms) must assume the same value on the two ends of an IMA link. l The default value is recommended. For details, see A.13.3 Maximum Delay Between Links(ms)(IMA Group Management). Clock Mode

CTC Mode, ITC Mode Default: CTC Mode

The Clock Mode parameter specifies the clock mode for operations of an inverse multiplexing for ATM (IMA) group. l Clock Mode is set to the same value for the interconnected ends of IMA links. l Set this parameter according to the planning information. For details, see A.13.6 Clock Mode(IMA Group Management).

Table 10-74 Parameters for an associated service Field

Value

Service Type For example: ATM service

Issue 03 (2013-02-20)

Description Displays the type of the service associated with the port.


566



Field

Value

Description

Service ID

For example: 20


Service Name

For example: ATM


Used Resource

-


10.9 Parameter Description: MPLS OAM The MPLS OAM mechanism can be used to effectively detect, confirm, and locate internal defects that occur on the MPLS layer network, and monitor the network performance.

10.9.1 Tunnel OAM Parameters The OAM parameters include Tunnel ID, Tunnel Name, Node Type, OAM Status, and other parameters. Table 10-75 lists the parameters for configuring the OAM function. Table 10-75 Parameters for configuring the OAM function Field

Value

Description

Tunnel ID

For example, 3

Displays the tunnel ID.

Tunnel Name

Character string

Displays the tunnel name.

Node Type


Displays the node type. l Ingress: ingress node l Egress: egress node l Transit: pass-through node

OAM Status

Enabled, Disabled

Sets and displays the OAM status. l Enabled: OAM-related operations can be performed. l Disabled: OAM-related operations cannot be performed.

Issue 03 (2013-02-20)


567



Field

Value

Description

Detection Mode

Auto-Sending, Manual

Sets and displays the detection mode. l Manual: The frequency set by the user is used to test the tunnel connectivity. l Auto-Sending: The frequency of the received packets is used to test the tunnel connectivity.


CV, FFD

Sets the detection packet type on the ingress node. l CV: The detection frequency is always the same and is not configurable. l FFD: The detection frequency is configurable. NOTE If CV is selected, the system sends one CV packet with a length of 74 bit/s at an interval of one second; if FFD is selected, the system sends one FFD packet with a length of 25 bit/s at an interval of 3.3 ms.


3.3, 10, 20, 50, 100, 200, 500

Sets and displays the detection packet period. If Detection Packet Period is set to FFD, the detection packet period is configurable. If Detection Packet Period is set to CV, the detection packet period is always 1000. It is recommended that Detection Packet Period (ms) be set to 3.3 to ensure that the switching duration of MPLS tunnel APS protection is less than 50 ms.

Issue 03 (2013-02-20)

Reverse Tunnel

For example, 3

Selects the reverse tunnel.

CV/FFD Status

Stop, Start

Displays the CV/FFD status.


568



Field

Value

Description

LSP Status

Near-End Available, NearEnd Defect Available, NearEnd Defect Unavailable, Near-End Unavailable, Remote Available, Remote Defect Available, Remote Defect Unavailable, Remote Unavailable, Initialized

Displays the LSP status.

LSP Defect Type

dServer, dLOCV, dTTSI_Mismatch, dTTSI_Mismerge, dExcess, dUnknown, SD, SF, BDI, FDI

Displays the LSP defect type.

Disable LSP Duration (ms)

0-655350

Displays the duration of the disable status of the LSP. Disable LSP Duration indicates the duration when the tunnel is unavailable.

LSP Defect Location


Displays the LSP defect location. LSP Defect Location identifies the location of the defect in the network by using the IP address.

SD Threshold

0-100

Sets and displays the SD threshold. This parameter can be set only for the egress node of the tunnel.

SF Threshold

0-100

Sets and displays the SF threshold. This parameter can be set only for the egress node of the tunnel. SD ≤ SF

Issue 03 (2013-02-20)

Source Node


Displays the source node of the tunnel.

Sink Node


Displays the sink node of the tunnel.


569



10.9.2 Ping Test You need to set parameters for a ping test, starting the ping test, and stopping the ping test when configuring a ping test. Table 10-76 lists the parameters for a ping test. Table 10-76 Parameters for a ping test Field

Value

Description

Packet Count

For example, 3

Sets the count of packets.

EXP Value

0-7

Sets the EXP value. The packet priority increases with the EXP value.

TTL

1-255

Sets the time to live (TTL).

Transmit Interval(10ms)

10-1000

Sets the interval of transmitting packets.

Packet Length

64-1400

Sets the length of packets.

Wait-to-Response Timeout Time(10ms)

50-6000

Sets the wait-to-response timeout time.

Response Mode

No Response, IPv4 UDP Response

Sets the response mode.

Character string

Displays the test result.

Test Result

NOTE This parameters can be currently set to only IPv4 UDP Response. If this parameter is set to No Response, a timeout message is displayed as the test result.

10.9.3 Traceroute Test You need to set the parameters such as Packet Length and Response Mode when configuring the traceroute test. Table 10-77 lists the parameters for configuring the traceroute test. Table 10-77 Parameters for configuring the traceroute test Field

Value

Description

EXP Value

0-7

Sets the EXP value. The packet priority increases with the EXP value.

TTL Issue 03 (2013-02-20)

1-255 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Sets the TTL. 570



Field

Value

Description

Packet Length

84-1400

Sets the length of packets.

Wait-to-Response Timeout Time(10ms)

50-6000

Sets the wait-to-response timeout time.

Response Mode

No Response, IPv4 UDP Response

Sets the response mode.

Character string

Displays the test result.

Test Result

NOTE You can set this parameter to only IPv4 UDP Response. If you set this parameter to No Response, the test result will time out.

10.10 Parameter Description: MPLS Tunnel APS This topic describes the parameters related to the MPLS Tunnel APS.

10.10.1 Parameters for Configuring MPLS Tunnel APS (on a Per-NE Basis) You need to set the necessary parameters when configuring MPLS Tunnel APS. Table 10-78 lists the parameters for configuring MPLS Tunnel APS. Table 10-78 Parameters for configuring MPLS Tunnel APS Field

Value

Description

Protection Group ID

For example, 1

Displays the protection group ID. The system automatically assigns the protection group ID according to the sequence of their creation.

Issue 03 (2013-02-20)

Protection Type

1+1, 1:1

Selects a protection type.

Switching Mode

Single-Ended, Dual-Ended

Specifies the switching policy to be adopted when a tunnel fails.


571



Field

Value

Description

Revertive Mode


Specifies whether the services are switched from the protection Tunnel to the working Tunnel after the working Tunnel is restored. If you set this parameter to Revertive, the services can be switched from the protection Tunnel to the working Tunnel. If you set this parameter to NonRevertive, the services cannot be switched from the protection Tunnel to the working Tunnel.

WTR Time(m)

1 to 12

Specifies the WTR time of the protection group.

Default: 5 Hold-off Time(100ms)

Protocol Status

0 to 100 Default: 0

Specifies the hold-off time of the protection group.

Enabled, Disabled

Specifies the protocol status. If you set the parameter to Enabled, the protection group is available.

Switching Status

Clear, Forced Switching, Manual Switching\(Working to Protection\), Manual Switching\(Protection to Working\), Exercise Switching, Lockout

Indicates the switching status of the protection group.

10.10.2 Parameters for Configuring MPLS Tunnel APS (in End-toEnd Mode) This topic describes the parameters for configuring MPLS tunnel APS protection groups in endto-end mode. Table 10-79 Parameters for configuring MPLS tunnel APS

Issue 03 (2013-02-20)

Field

Value Range

Description

Protection Group ID

For example, Tunnel APS 1

Specifies the name of the protection group.


572



Field

Value Range

Description

Protection Type

1+1, 1:1

Specifies the type of the protection group.

Default: 1+1

l 1:1: A protection tunnel protects a working tunnel. Normally, the working tunnel carries services and the protection tunnel carries protocol packets. When the working tunnel fails, services are switched from the working tunnel to the protection tunnel. l 1+1: A protection tunnel protects a working tunnel. Normally, services are transmitted on both tunnels and selected from either tunnel for reception. When the working tunnel fails, services on the protection tunnel are selected for reception. Switching Mode

Single-Ended, Dual-Ended Default: Single-Ended NOTE When Protection Type is set to 1:1, Switching Mode is defaulted to Dual-Ended and cannot be changed.

Specifies the switching mode of the protection group. l In single-ended switching, if a fault is detected at one end, only the local end switches and the opposite end is not notified for performing a switching. l In dual-ended switching, if a fault is detected at one end, the local end switches and the opposite end is instructed to perform a switching.

Issue 03 (2013-02-20)


573



Field

Value Range

Description

Working Tunnel Type

MPLS Tunnel

Specifies the type of the working tunnel. When configuring MPLS tunnel APS for unidirectional tunnels, you need to select four tunnels, which function as the Forward Working tunnel, Forward Protection tunnel, Backward Working tunnel, and Backward Protection tunnel. For a bidirectional tunnel, you need to select two tunnels, namely, the working tunnel and protection tunnel.

Working Ingress Tunnel ID

For example, 40 (source node: 130.0.0.12; sink node: 75.75.75.75)

Selects the ID of the working ingress tunnel.

Working Ingress Tunnel Name

For example, 1

Displays the name of the working ingress tunnel.

Working Egress Tunnel ID


Selects the ID of the working egress tunnel.

Working Egress Tunnel Name

For example, 1

Displays the name of the working egress tunnel.

Protection Tunnel Type

MPLS Tunnel

Specifies the type of the protection tunnel.

Protection Ingress Tunnel ID


Selects the ID of the protection ingress tunnel.

Protection Ingress Tunnel Name

For example, 1

Displays the name of the protection ingress tunnel.

Protection Egress Tunnel ID


Selects the ID of the protection egress tunnel.

Protection Egress Tunnel Name

For example, 1

Displays the name of the protection egress tunnel.

Protocol Status

Enabled, Disabled

Specifies the protocol status. If you set this parameter to Enabled, the protection group is available.

Issue 03 (2013-02-20)


574



Field

Value Range

Description

Switching Status


Specifies whether the services are switched from the protection tunnel to the working tunnel after the working tunnel is restored. If you set this parameter to Revertive, the services can be switched from the protection tunnel to the working tunnel. If you set this parameter to NonRevertive, the services cannot be switched from the protection tunnel to the working tunnel.

WTR Time(min)

1-12

Specifies the WTR time of the protection group.

Default: 5 Hold-off Time(100ms)

0-100

Specifies the hold-off time of the protection group.

Default: 0

10.11 Parameter Description: Inband DCN In this interface, you can manage DCN.

Tabs Tab

Description

Bandwidth Management

Set the bandwidth used by the DCN. For details, see 10.11.3 Bandwidth Management.

Access Control

Set parameters for the Ethernet port which accesses the NMS information. For details, see 10.11.2 Access Control.

Port Settings

Set parameters for the port that transfers the inter-NE management information. For details, see 10.11.1 Port Settings.

10.11.1 Port Settings This topic describes the parameters, such as Enabled Status, for configuring an in-band DCN port. Table 10-80 lists the parameters for configuring an in-band DCN port. Issue 03 (2013-02-20)


575



Table 10-80 Parameters for configuring an in-band DCN port Field

Value

Description

Port Name

For example, 21-N1ETF8-1 (PORT-1)

Displays the ports used for transmitting management information between NEs.

DCN Enabled Status

Enabled, Disabled

Enables or disables a port.

Default value: Enabled

l Enabled: Management information between NEs can be transmitted through this port. l Disabled: Management information between NEs cannot be transmitted through this port.

OSPF Enabled Status

Enabled, Disabled Default value: Enabled

OPQ LSA Enabled Status

Enabled, Disabled Default value: Enabled

Enables or disables the OSPF protocol. Enables or disables the opaque LSA.

10.11.2 Access Control This topic describes the parameters, such as IP Address and Subnet Mask of a port, for configuring in-band DCN access control. Table 10-81 lists the parameters for configuring in-band DCN access control. Table 10-81 Parameters for configuring in-band DCN access control Field

Value

Description

Port Name

For example, 21-N1PETF8-1 (PORT-1)

Displays the Ethernet port that can receive the NMS information.

Enabled Status

Enabled, Disabled

Enables or disables the port.

Default value: Disabled

l Enabled: The management information of the U2000 can be received through this port. l Disabled: The management information of the U2000 cannot be received through this port.

Issue 03 (2013-02-20)


576



Field

Value

Description

IP Address


Sets the IP address of the port.

Default value: 0.0.0.0 Subnet Mask

For example, 255.255.255.0 Default value: 0.0.0.0

Sets the subnet mask of the port.

10.11.3 Bandwidth Management This topic describes the parameters, such as VLAN ID and Bandwidth (kbps) of a board, for configuring in-band DCN bandwidth management. Table 10-82 lists the parameters for configuring in-band DCN bandwidth management. Table 10-82 Parameters for configuring in-band DCN bandwidth management Field

Value

Description

Ethernet Board VLAN ID

2 to 4094

Sets the VALN ID used by the DCN. Set this parameter when the U2000 and NE are connected by the Ethernet board, or the NEs are connected to each other by the Ethernet board.

Default: 4094

Generally, set this parameter to the default VLAN ID. If the VLAN ID of a service conflicts with the VLAN ID of a DCN channel, you can specify a VLAN ID. The VLAN IDs of all the DCN channels on a network, however, must be the same. Bandwidth (Kbit/s)

64 to 2048 Default: 512

Sets the bandwidth used by the DCN. Set this parameter when the U2000 and NE are connected by the Ethernet board, or the NEs are connected to each other by the Ethernet board.

10.12 Parameter Description: QinQ Link Configuration Parameters This topic describes the parameters related to QinQ links. Issue 03 (2013-02-20)


577



Table 10-83 QinQ link parameters Field

Value Range

Description

QinQ Link ID

For example, 5

Displays or specifies the ID of the QinQ link.

Board

For example, 1-N1PEG8

Displays or specifies the board.

Port


Displays or specifies the port.

S-Vlan ID

For example, 4

Displays or specifies the SVLAN ID.

Bandwidth Limit

Enabled, Disabled

Specifies or displays the bandwidth limit. The committed information rate (CIR) and peak information rate (PIR) can set if Bandwidth Limit is set to Enabled.






The Committed Burst Size (byte) parameter specifies the committed burst size. Click A.10.27 Committed Burst Size (byte) for more information.

Issue 03 (2013-02-20)


578



Field

Value Range

Description

Peak Information Rate (kbit/ s)

64-10000000

The Peak Information Rate (kbit/s) parameter specifies the maximum rate of services allowed by the PIR.


Click A.10.28 Peak Information Rate (kbit/s) for more information. Peak Burst Size (byte)



64 bytes

Policy

Specifies and displays the policy.

10.13 Parameter Description: Address Parse This topic describes the parameters, such as ARP List IP, ARP List MAC, and ARP List Type, for configuring the address parse function. Table 10-84 lists the parameters for configuring the address parse function. Table 10-84 Parameters for configuring the address parse function

Issue 03 (2013-02-20)

Parameter

Value

Description

ARP List IP


Configures the IP address in the ARP list.

ARP List MAC

For example, 1CC4-31-88-1C-C4

Configures the MAC address corresponding to the IP address in the ARP list.

ARP List Type

Static, Dynamic

Displays the type of the ARP list.


579


A List of Parameters

A

List of Parameters

This topic describes all the parameters for configuring and querying the common boards and functions on the U2000. Each parameter is described in terms of the description, impact on the system, values, configuration guidelines, and relationship with other parameters. A.1 Ethernet Port Associated Parameters (Packet Mode) Before configuring an Ethernet service, you need to set the parameters associated with Ethernet ports. A.2 Ethernet Port Associated Parameters (TDM Mode) Before configuring an Ethernet service, you need to configure the relevant parameters for Ethernet ports. A.3 Ethernet Service Associated Parameters (Packet Mode) This topic describes the parameters for configuring Ethernet services. A.4 CES Service Associated Parameters This topic describes the parameters for configuring CES services. A.5 Data Service Associated Parameters (TDM Mode) This topic describes the parameters for configuring Ethernet services and SAN services. A.6 ETH OAM Associated Parameters (Packet Mode) This topic describes the parameters that are used for enabling the ETH-OAM function. A.7 ETH-OAM Associated Parameters (TDM Mode) This topic describes the parameters for configuring the ETH-OAM function. A.8 PW Associated Parameters This topic describes the parameters for configuring PW services. A.9 PW APS Protection Associated Parameters (Packet Mode) This topic describes the parameters for configuring PW APS protection. A.10 HQoS Associated Parameters This topic describes the parameters that are used for enabling the HQoS function. A.11 QoS Associated Parameters This topic describes the parameters for configuring the QoS function A.12 ATM Interface Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM interface. Issue 03 (2013-02-20)


580



A.13 ATM/IMA Services Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM/IMA services. A.14 ATM OAM Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM OAM. A.15 ATM/IMA Associated Parameters (TDM Mode) This topic describes the parameters for configuring the ATM/IMA function. A.16 RPR Associated Parameters This topic describes the parameters for configuring the RPR function. A.17 LAG Associated Parameters (TDM Mode) This topic describes the parameters that are used for enabling the LAG function. A.18 MC-LAG Associated Parameters This topic describes the parameters for configuring MC-LAG protection. A.19 LAG/DLAG Associated Parameters (TDM Mode) This topic describes the parameters for configuring a link aggregation group (LAG) and a distributed link aggregation group (DLAG). A.20 STP/RSTP Associated Parameters This topic describes the parameters for configuring the Spanning Tree Protocol (STP) and the Rapid Spanning Tree Protocol (RSTP). A.21 LCAS Associated Parameters This topic describes the parameters for configuring the LCAS function. A.22 Packet LPT Associated Parameters This topic describes the parameters for configuring the link state pass through (LPT) function in packet services. A.23 LPT Associated Parameters (TDM Mode) This topic describes the parameters for configuring the LPT function. A.24 IGMP Snooping Associated Parameters This topic describes the parameters for configuring the IGMP Snooping function. A.25 Test Frame Associated Parameters This topic describes the parameters for configuring the Ethernet service test function. A.26 Orderwire Associated Parameters This topic describes the parameters for configuring the orderwire function. A.27 Clock Associated Parameters To synchronize the clocks on a network, you need to set the parameters that are associated with clocks. A.28 Protection Associated Parameters This topic describes the parameters for configuring multiplex section protection (MSP), subnetwork connection protection (SNCP), board protection switching (BPS), and path protection switching (PPS). A.29 Other Parameters This topic describes the parameters related to PDH interfaces and SDH interfaces.

Issue 03 (2013-02-20)


581



A.1 Ethernet Port Associated Parameters (Packet Mode) Before configuring an Ethernet service, you need to set the parameters associated with Ethernet ports.

A.1.1 MAC Loopback(Ethernet Interface) Description The MAC Loopback (Ethernet Interface) parameter specifies the MAC loopback state at an Ethernet port. Port loopback setting is applied to locating faults only.

Impact on the System MAC loopback is a function of diagnosing faults. It may affect the services configured at the port. If the loopback state is set to Inloop or Outloop, the services at the port may be interrupted.

Values Valid Values

Default Value


Non-Loopback

The following table lists descriptions of each value. Value

Description

Non-Loopback

Indicates the normal state. If the equipment works normally, you do not need to set the MAC loopback.

Inloop

Loops back the services from the cross-connection side to the cross-connection side within the equipment at the local end.

Outloop

At the local equipment, the incoming services of an Ethernet port are looped back at the MAC layer and output to this Ethernet port.

Configuration Guidelines To set the MAC loopback, decide the loopback direction according to the service direction when you locate the faults.

Relationship with Other Parameters None. Issue 03 (2013-02-20)


582



Related Information Loopb ack Point

Meaning

Diagram

MAC Loopba ck

The Ethernet service is looped from the MAC layer of the Ethernet port.

A.1.2 PHY Loopback(Ethernet Interface) Description The PHY Loopback parameter indicates the loopback status of the physical layer of an Ethernet port. This parameter is an advanced attribute of the Ethernet port.

Impact on the System As a fault diagnosis function, setting PHY loopback affects the services configured on the port. In the case of loopback, services on the port are interrupted.

Values Value Range

Default Value


Non-Loopback

The following table lists descriptions of each value.

Issue 03 (2013-02-20)

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 are looped back at the physical layer and input to this Ethernet port.

Outloop

At the local equipment, the incoming services of an Ethernet port are looped back at the physical layer and output to this Ethernet port.


583



Configuration Guidelines The PHY loopback is mainly used to locate a fault. When setting this parameter, determine the loopback type according to the service flow direction.

Relationship with Other Parameters None.

Related Information Loopb ack Point

Loopback Point

PHY loopbac k

The Ethernet service is looped from the physical layer of the Ethernet port.

Diagram

A.1.3 Enable Port(Ethernet Interface) Description The Enable Port parameter sets whether the Ethernet port is usable.

Impact on the System When services are available on the Ethernet port, setting this port to disabled interrupts the services.

Values Value Range

Default Value

Enabled, Disabled.

Enabled


Issue 03 (2013-02-20)

Value

Description

Enabled

The port is usable.

Disabled

The port is unusable.


584



Configuration Guidelines When a port is used for transmitting services, enable this port first.


A.1.4 Encapsulation Type(Ethernet Interface) Description The Encapsulation Type parameter sets the link layer encapsulation type of the port, and specifies the link layer encapsulation type that can be identified by this port.

Values Value Range

Default Value

Null, 802.1Q, QinQ

For details, see configuration guidelines.


Description

Null

No link layer is available, or the link layer encapsulation is not processed.

802.1Q

In the Layer 2 mode, the encapsulation type of the Ethernet port is 802.1Q by default.

QinQ

When the Ethernet port is used for QinQ Link, the port attribute should be set to Layer 2, and the encapsulation type should be set to QinQ. In addition, QinQ Type Domain of the two interconnected Ethernet ports should be set to the same value.

Configuration Guidelines Currently, the encapsulation type of the Ethernet port can be set. In addition, the encapsulation type can be switched only when the port does not carry services. In the Layer 2 mode, the encapsulation type of the Ethernet port can be Null, 802.1Q, and QinQ. In the Layer 3 mode, the encapsulation type of the Ethernet port, which is fixed to 802.1Q, cannot be set.



585



Related Information For details, see the Port Mode parameter.

A.1.5 Working Mode(Ethernet Interface) Description Set 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 communication mode of a port.

Impact on the System If the working modes of interconnected Ethernet ports are inconsistent, the services are not available or have a severe packet loss problem.

Values Value Range

Default Value

10M Half-Duplex, 10M Full-Duplex, AutoNegotiation, 100M Half-Duplex, 100M FullDuplex, 1000M Full-Duplex, 10G Full-Duplex LAN, 10G Full-Duplex WAN

Auto-Negotiation


Issue 03 (2013-02-20)

Value

Description

10M Half-Duplex

The maximum transmission rate of the port is 10 Mbit/s and the communication mode is half-duplex.

10M Full-Duplex

The maximum transmission rate of the port is 10 Mbit/s and the communication mode is full-duplex.

Auto-Negotiation

The port uses the protocol to automatically specify the best working mode that matches the opposite port for communication.

100M Half-Duplex

The maximum transmission rate of the port is 100 Mbit/s and the communication mode is half-duplex.

100M Full-Duplex


1000M Full-Duplex


10G Full-Duplex LAN

The maximum transmission rate of the port is 10 Gbit/s and the communication mode is full-duplex. The port type is 10G BaseSR/LR/ER/ZR and the port is used as an Ethernet port to connect LAN equipment that functions as the DHCP server.


586



Value

Description

10G Full-Duplex WAN

The maximum transmission rate of the port is 10 Gbit/s and the communication mode is full-duplex. The port type is 10G BaseSW/LW/EW/ZW and the port is used as an SDH port to connect WAN access equipment that functions as the DHCP client host.

Configuration Guidelines The Auto-Negotiation working mode is recommended. If the communication fails and the working mode of the port is set to Auto-Negotiation, you need specify the working mode of the port 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 working mode of the interconnected port should be the same. Otherwise, the communication is not available. In the case of equipment interconnection, set the communication modes of the interconnected ports to full-duplex.


Related Information None.

A.1.6 Max Frame Length(byte) for an Ethernet Port Description The Max Frame Length(byte) parameter sets the maximum length of the data packets allowed to be received by the Ethernet port.

Impact on the System After this parameter is set, all the data packets of a length longer than this parameter are discarded.

Values Value Range

Default Value

64-9600

1620

Configuration Guidelines The maximum data packet length has a filtering mechanism, through which this parameter is set to filter the data packets received on the Ethernet port of a length longer than a certain length. Issue 03 (2013-02-20)


587



When setting this parameter, consider the length of the data packets transmitted from the opposite end. If the parameter value is less than the length of the data packets transmitted from the opposite end, this link cannot normally transmit service packets.

Relationship with Other Parameters l

The maximum data packet length defines the maximum bytes in a packet that is allowed by an Ethernet port. All packets whose packet length is larger than the maximum data packet length will be discarded by the Ethernet port.

l

The service MTU defines the maximum data packet length allowed by a service. All packets whose length is larger than the MTU will be discarded.

l

When both the maximum data packet length and the service MTU are configured, the smaller value takes effect.

A.1.7 Enable Tunnel(Ethernet Interface) Description The Enable Tunnel(Ethernet Interface) parameter sets the MPLS enabling state of the port. When Enable Tunnel is set to Enabled, it indicates that the port can identify and process the MPLS label.

Impact on the System If the MPLS is disabled, the services on the port are interrupted.

Values Value Range

Default Value

Enabled, Disabled

Enabled


Description

Enabled

The MPLS is enabled.

Disabled

The MPLS is disabled.

Configuration Guidelines When the services are configured, the MPLS should not be disabled.



588



Related Information The MPLS is a standard routing and switching technology platform, which supports various high layer protocols and services. The MPLS uses short and fixed-length tags to encapsulate various link layer packets. Based on the IP routing and control protocol, the MPLS provides switching to the connection at the network layer.

A.1.8 Specify IP(Ethernet Interface) Description The Specify IP parameter, set by port, indicates the method of specifying the IP address parameter of a specified port.

Impact on the System The IP address parameter of the port is the prerequisite for MPLS service creation. If the current IP address parameter is invalid, the services cannot be created.

Values Value Range

Default Value

Manually, Unspecified

Unspecified


Description

Manually

Indicates the IP parameter of the specified port. If the IP address parameter is valid, specify an IP address to the current port. If the IP address is invalid, release the IP address of the current port.

Unspecified

Indicates that the IP address of the port is not specified.

Configuration Guidelines None.

Relationship with Other Parameters The IP address parameter can be configured only when the port is in the Layer 3 mode.

Issue 03 (2013-02-20)


589



A.2 Ethernet Port Associated Parameters (TDM Mode) Before configuring an Ethernet service, you need to configure the relevant parameters for Ethernet ports.

A.2.1 Port Attribute (Ethernet Port) Description The Port Attribute (Ethernet Port) parameter specifies the position of a port in the network. Different port attributes support different packets.

Impact on the System The system operation is not affected.

Values Board Name

Valid Values

Default Value

N2EMR0, N2EGR2, N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EFS0, N2EFS0, N1EFS4, N2EFS4, N1EMR0, N2EMR0, N5EFS0

PE, P

PE

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EAS2

UNI, C-Aware, S-Aware

UNI

N1EMS2

PE, P, C-Aware, S-Aware

PE


Issue 03 (2013-02-20)

Value

Description

PE

Indicates Provider Edge (PE), which refers to the edge port of the service provider. A PE port (the default MPLS encapsulation type is invalid) can transmit or receive standard Ethernet packets.

P

Indicates Provider (P), which refers to the port in the core network of the service provider. A P port can transmit or receive the data packets with the MPLS labels (the default TAG attribute is invalid). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

590



Value

Description

UNI

Indicates the interface between CE and PE. This port processes the packets with TAG attributes specified in IEEE 802.1Q. Moreover, this port identifies and processes the VLAN IDs of the received packets according to the supported Tag Aware, Access or Hybrid.

C-Aware

A C-Aware (C-VLAN Aware) port in the network is located in the position as the UNI port at the client access side. This port identifies and processes the VLAN (C-VLAN) in the packets. If the value of QinQ TYPE is valid, this port treats the outer labels of the packets as C-VLAN.

S-Aware

An S-Aware (S-VLAN Aware) port in the network is located in the position as the interface on the network side. This port identifies and processes the VLAN (S-VLAN) in the packets. If the value of QinQ TYPE is valid, this port treats the outer labels of the packets as S-VLAN.

Configuration Guidelines The port attribute depends on the port position in the network and the service. For this reason, select a proper port attribute as required. Generally, select the default value. l

For the MPLS service, select P for the port that transmits or receives packets with MPLS labels.

l

For the QinQ service, select C-Aware or S-Aware for the port. Connecting to the port of the client network, a C-Aware port identifies and processes the packets with C-VLAN labels. Connecting to the port at the network side, an S-Aware port identifies and processes the packets with S-VLAN tags. The configuration examples are described as follows: – Add the S-VLAN tag to the service from Port A to Port B, and remove the S-VLAN tag from the service from Port B to Port A. Then select C-Aware for Port A, and SAware for Port B. – Configure a service from Port A to Port B to transparently transmit the C-VLAN tags at the client side. Then select C-Aware for Ports A and B. – Configure a service from Port A to Port B to transparently transmit the S-VALN tags at the network side. Then select S-Aware for Ports A and B. – Configure a service from Port A to Port B to switch the C-VLAN tags at the client side. Then select C-Aware for Ports A and B. – Configure a service from Port A to Port B to switch the S-VALN tags at the network side. Then select S-Aware for Ports A and B.


Related Information According to the position and role of the equipment in the networking, there are three types of equipment: CE, PE (U-PE & N-PE), and P. Client Edge (CE) indicates the equipment at the Issue 03 (2013-02-20)


591



client side. Provider Edge (PE) indicates the edge equipment at the network side. Provider (P) indicates the intermediate node at the network side.

A.2.2 Enable Port (Ethernet Port Attribute) Description The Enable Port (Ethernet Port Attribute) parameter specifies whether packets can be transmitted or received at an Ethernet port.

Impact on the System If a port is disabled, it cannot transmit or receive packets. In this case, the service is unavailable.

Values Valid Values

Default Value

Enabled, Disabled

Disabled


Description

Enabled

The port can transmit or receive packets.

Disabled

The port cannot transmit or receive packets.

Configuration Guidelines l

If the port does not bear a service, set the port attribute to Disabled.

l

If the port bears services, set the port attribute to Enabled.

A.2.3 Max. Frame Length (Ethernet Port Attribute) Description The Max. Frame Length (Ethernet Port Attribute) parameter specifies the maximum frame length that is supported at an Ethernet port.

Impact on the System If the packet length exceeds the specified maximum frame length, the packets are discarded. Alternatively, the packet length is minimized to the specified frame length. This parameter takes effect only when the packet enters the port rather than when the packet that exits the port.

Issue 03 (2013-02-20)


592



Values Board Name

Valid Values

Default Value

Unit

N1EGS4, N3EGS4

1518-9216, in step length of 2

1522

Byte

N1EMS4, N4EGS4


1522

Byte

N1EFT8, N1EFT8A, R1EFT4


1522

Byte

N1EGT2, N1EAS2, N2EMR0, N2EGR2, N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2


1522

Byte

Configuration Guidelines Set this parameter as required. Generally, select the default value, unless otherwise specified.


A.2.4 Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute) Description The Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow control mode adopted when an Ethernet port works in non-auto-negotiation mode.


Values Valid Values

Default Value

Disabled, Enable Symmetric Flow Control, Send Only, Receive Only

Disable

The following table lists descriptions of each value. Issue 03 (2013-02-20)


593



Value

Description

Disable

Indicates that the port disables the flow control function.

Enable Symmetric Flow Control

Indicates that the port can transmit PAUSE frames and process the received PAUSE frames.

Send Only

Indicates that the port sends the PAUSE frame only.

Receive Only

Indicates that the port can only process the received PAUSE frames.

Configuration Guidelines This parameter is meaningful only when you configure the EPL service. You can select the value as required.


A.2.5 Autonegotiation Flow Control Mode (Ethernet Port Attribute) Description The Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow control mode adopted when an Ethernet port works in auto-negotiation mode.

Impact on the System If the negotiation result is to enable the flow control function, the PAUSE frame is transmitted to the upstream port.

Values Board Name

Valid Values

Default Value

N1EMS4, N1EGS4, N3EGS4, N1EAS2

Enable Symmetric/ Dissymmetric Flow Control


N2EMR0, N2EGR2, N1EFS0, N2EFS0, N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2

Disabled

Disabled

Enable Dissymmetric Flow Control Enable Symmetric Flow Control Enable Symmetric/ Dissymmetric Flow Control

Issue 03 (2013-02-20)


594



Board Name

Valid Values

Default Value

N4EGS4

Disabled


Enable Dissymmetric Flow Control Enable Symmetric Flow Control Enable Symmetric/ Dissymmetric Flow Control


Description

Disabled

Indicates that the port disables the flow control function.

Enable Dissymmetric Flow Control

Indicates that the port only transmits flow control frames, but does not process the received flow control frames.

Enable Symmetric Flow Control

Indicates that the port can transmit PAUSE frames and process the received PAUSE frames.


Indicates that the symmetric/dissymmetric flow control mode is decided by the auto-negotiation result.

Configuration Guidelines For the N1EMS4, N1EGS4, N3EGS4, N1EAS2 boards, this parameter is valid only when you configure the EPL service. Generally, set this parameter to Enable Symmetric/Dissymmetric Flow Control, unless otherwise specified.

A.2.6 MAC Loopback (Ethernet Port Attribute) Description The MAC Loopback (Ethernet Port Attribute) parameter specifies the MAC loopback state at an Ethernet port. Port loopback setting is applied to locating faults only.

Impact on the System MAC loopback is a function of diagnosing faults. It may affect the services configured at the port. If the loopback state is set to Inloop, the services at the port may be interrupted.

Issue 03 (2013-02-20)


595



Values Valid Values

Default Value

Non-Loopback, Inloop

Non-Loopback


Description

Non-Loopback

Indicates the normal state. If the equipment works normally, you do not need to set the MAC loopback.

Inloop




A.2.7 PHY Loopback (Ethernet Port Attribute) Description The PHY Loopback (Ethernet Port Attribute) parameter specifies the PHY loopback state at an Ethernet port. Port loopback setting is applied to locating faults only.

Impact on the System PHY loopback is a function of diagnosing faults. It may affect the services configured at the port. If the loopback state is set to Inloop, the services at the port may be interrupted.

Values Valid Values

Default Value

Non-Loopback, Inloop

Non-Loopback


Issue 03 (2013-02-20)


596



Value

Description

Non-Loopback

Indicates the normal state. If the equipment works normally, you do not need to set the PHY loopback.

Inloop




A.2.8 QinQ Type Area Description The QinQ Type Area parameter indicates the VLAN protocol used by the packet that is transmitted by QinQ. The default value 0x8100 of this parameter is the protocol type that is specified by the related standard. The original equipment of other vendors may use 0x88A8 or 0x9100 to represent the VLAN protocol. To realize the interconnection with the original equipment, the user should set this parameter accordingly.

Impact on the System l

If QinQ Type Area is set to 0x8100 at the local end, QinQ Type Area must be set to 0x8100 at the opposite end. Otherwise, services are unavailable.

l

If QinQ Type Area is set to a value other than 0x8100 from 0x600 to 0xFFFF at the local end, QinQ Type Area must be set to 0x8100 or to the same value at the opposite end. Otherwise, services are unavailable.

Values Value Range

Default Value

0x600-0xFFFF

0x8100

Configuration Guidelines Set this parameter according to the supported value of QinQ Type Area of the opposite equipment.

Issue 03 (2013-02-20)


597



A.2.9 Loop Detection (Ethernet Port Attribute) Description The Loop Detection (Ethernet Port Attribute) parameter specifies the function of reporting the self-loop alarms after one of the following loopback cases is detected. l

For the external physical interface of the board, the transmit direction is connected to the receive direction by a fiber.

l

The two external physical ports on the board are cross-connected to each other through fibers.

l

The cross-connection is created on the same VCTRUNK of the board.

l

The cross-connection is created between different VCTRUNKs of the board.

Impact on the System After the self-loop check function is enabled for a port, the specified self-loop check packets are transmitted from the port. One packet is transmitted each second.

Values Valid Values

Default Value

Enabled, Disabled

Disabled

Configuration Guidelines To check the self-loop port, select Enabled.

Relationship with Other Parameters The loop port shut-down function takes effect only after the loop check function is enabled.

A.2.10 Loop Port Shutdown (Ethernet Port Attribute) Description The Loop Port Shutdown (Ethernet Port Attribute) parameter is set to disable the self-loop port after a self-loop port is detected if the loop port shutdown function is enabled. After the self-loop port is shut down, the self-loop port only transmits or receives the self-loop detection packets rather than any other packets. If the port is not a self-loop port, it starts to work again.

Impact on the System If a port enables the loop port shut-down function, the IEEE 802.3ah protocol blocks the port once the port is detected to be a self-loop port. In this case, the services at the port are interrupted. All the packets based on the upper-level protocol are discarded. Issue 03 (2013-02-20)


598



Values Valid Values

Default Value

Enabled, Disabled

Enabled

Configuration Guidelines To block a self-loop port, select Enabled. Otherwise, select Disabled.

Relationship with Other Parameters The loop port shutdown function takes effect only after the IEEE 802.3ah protocol and the loop detection function are enabled.

A.2.11 Traffic Threshold(Mpbs)(External Ethernet Port Attribute) Description The Traffic Threshold(Mpbs) (External Ethernet Port Attribute) parameter specifies the data flow threshold at external physical ports.

Impact on the System If the data flow at external physical ports is greater than the specified threshold, the FLOW_OVER alarm is generated.

Values Valid Values

Default Value

Unit

0-100 (FE), 0-1000 (GE), in step length of 1

100 (FE), 1000 (GE)

Mbps

Configuration Guidelines Generally, select the value according to the bandwidth.


A.2.12 Broadcast Packet Suppression Threshold (Ethernet Interface Attributes) Description The Broadcast Packet Suppression Threshold(Ethernet Interface Attributes) parameter allocates the specified bandwidth to the broadcast packets. The bandwidth is allocated on the Issue 03 (2013-02-20)


599



basis of the traffic proportion at the port. If the bandwidth allocated to the broadcast packets reaches the specified threshold, the port discards the broadcast data packets that are received.


If less bandwidth is allocated to the broadcast packets, some necessary broadcast services are affected.

l

If excessive bandwidth is allocated to the broadcast packets, excessive broadcast packets may enter the network. Consequently, the network running is affected.

Values Value Range

Default Value

1-10

3

You can set this parameter according to the percentage of the traffic at the port. The value 10 means that the whole bandwidth is allocated to the port.

Configuration Guidelines Generally, use the default value.


A.2.13 Enabling Broadcast Packet Suppression (Ethernet Interface Attributes) Description The Enabling Broadcast Packet Suppression (Ethernet Interface Attributes) parameter specifies whether to enable the function for a port to suppress the broadcast packets and to control the traffic of the broadcast data packets that enter the port. If the broadcast packet suppression function is enabled, and if the broadcast traffic exceeds the specified threshold value, the broadcast packets that enter the port are discarded.

Impact on the System If Enabling Broadcast Packet Suppression is set to Enabled, the port can effectively suppress the traffic of the broadcast packets by using the statistic function of the network processor on the board.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

Enabled, Disabled

Disabled


600



Configuration Guidelines You can set this parameter according to whether to control the traffic of the broadcast packets.


A.2.14 Zero-Flow Monitor (Ethernet Interface Attributes) Description The Zero-Flow Monitor parameter specifies whether the traffic on a port is monitored.

Impact on the System After the zero traffic monitoring function is enabled, the port can report the zero traffic alarm after the state of zero traffic lasts for a certain period. Hence, the user can check whether the service is interrupted due to the fault on the equipment side.

Values Value Range

Default Value

Enabled, Disabled

Disabled


Description

Enabled

The zero traffic monitoring function is enabled on the port.

Disabled

The zero traffic monitoring function is disabled on the port.

Configuration Guidelines Set this parameter according to the actual requirement of the user. Set this parameter to Enabled if the traffic on a port needs to be monitored.

A.2.15 Port Traffic Threshold Time Window(Min) Description The Port Traffic Threshold Time Window(Min) parameter specifies the duration for a VCTRUNK or an IP port to monitor the traffic after the zero traffic monitoring function of the port is enabled. Issue 03 (2013-02-20)


601



Impact on the System If the value of this parameter is too large, the port may fail to report the zero traffic alarm. If the value of this parameter is too small, the jitter due to the zero traffic alarm may occur on the port.

Values Value Range

Default Value

Unit

1-30

0

min

Configuration Guidelines The user can set this parameter according to the actual service requirement.

A.2.16 Jumbo Frame Type Description Jumbo Frame Type specifies the value of the jumbo frame type on an Ethernet port. The jumbo frame indicates the oversized Ethernet frame, whose maximum length is 65535 bytes. The Ethernet service board determines whether the Ethernet frame is a jumbo frame according to the value of the jumbo frame type.


Values Value Range

Default Value

0 to 65535

34928

Configuration Guidelines The value of this parameter must be the same as the value of the accessed jumbo frame type. Otherwise, the Ethernet board does not consider the frame as a jumbo frame.

Relationship with Other Parameters The maximum transmission unit (MTU) parameter is used for the Ethernet port. If the length of Ethernet frames is greater than the length of the jumbo frame, the Ethernet port discards these Ethernet frames. If the length of Ethernet frames is smaller than the length of the jumbo frame but is greater than the MTU, the Ethernet port discards the Ethernet frames whose length is greater than the MTU. If the length of Ethernet frames is smaller than the MTU, the Ethernet port does not discard the received Ethernet frames. Issue 03 (2013-02-20)


602



A.2.17 Default VLAN ID (Ethernet Port Attribute) Description The Default VLAN ID (Ethernet Port Attribute) parameter specifies the default VLAN ID of a port.


Values Valid Values

Default Value

1-4095

1

Configuration Guidelines Allocate the default VLAN ID according to the networking plan of the service carrier.


If Tag is set to Access for a port, packets without VLAN IDs are added with the default VLAN IDs when they enter the port. After these packets are transmitted from the port, their VLAN IDs are peeled off.

l

If Tag is set to Hybrid for a port, packets without VLAN IDs are added with the default VLAN IDs when they enter the port. After these packets are transmitted from the port, the VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these packets are directly transmitted.

l

If Tag is set to Tag Aware for a port, packets without VLAN IDs are discarded before they enter the port. Otherwise, these packets are directly transmitted.

A.2.18 VLAN Priority (Ethernet Port Attribute) Description The VLAN Priority (Ethernet Port Attribute) parameter specifies the priority of the default VLAN ID of a port. It indicates the priority of the service quality.


Values

Issue 03 (2013-02-20)

Valid Values

Default Value

0-7

0


603



Configuration Guidelines Set the VLAN priority according to the service requirements and the allocation of the service carrier.


A.2.19 Entry Detection (Ethernet Port Attribute) Description The Entry Detection (Ethernet Port Attribute) parameter specifies whether to identify the tag labels in the data packets.

Impact on the System The entry detection function can be disabled in the port-based services only. If the entry detection function is disabled, you may fail to configure other VLAN-based services.

Values Valid Values

Default Value

Enabled, Disabled

Enabled


Description

Enabled

The port checks the Tag label. In this case, the Tag attribute of the port is valid.

Disabled

The port does not check the tag label. In this case, the Tag attribute of the port is invalid.


To transmit the data packet transparently, the user can disable the entry detection function.

l

To forward the data packet according to the contents of the data packet, the user can enable the entry detection function.


Issue 03 (2013-02-20)


604



A.2.20 Tag Identifier Description Tag Identifier indicates that the Ethernet port supports IEEE 802.1Q Ethernet packets that contain VLAN tags. You can set three attributes to differentiate the packets from each other so that these packets can be transmitted efficiently.


Values Value Range

Default Value

Access, Tag Aware, Hybrid

Tag Aware

The following table lists the description of each value. Value

Description

Access

A port receives only the packets that do not contain VLAN tags. After receiving the packets, the port adds the default VLAN tag (PVID) to these packets. When the packets are transmitted from the port, the VLAN tags are stripped off the packets.

Tag Aware

A port receives only the packets that contain VLAN tags and discards the packets that do not contain VLAN tags. When the packets are transmitted from the port, they are directly forwarded to the next port.

Hybrid

A port can receive all the packets regardless of VLAN tags. After receiving the packets that do not contain VLAN tags, the port adds the default VLAN tag (PVID) to these packets. When the packets are transmitted from the hybrid port, the egress port determines whether the VLAN tags contained in the packets are the same as the PVID. If yes, the egress port strips the VLAN tags off the packets and then forwards these packets. Otherwise, the egress port directly forwards these packets.

Configuration Guidelines The tag attributes are configured for MAC ports and VCTRUNK ports. Hence, the VCTRUNK ports at both ends of the trunk link can be configured with the tag attributes. In the case of a link, Issue 03 (2013-02-20)


605



the services are available only when the parameters of the tag attributes are the same for the VCTRUNK ports on the source and sink ports. No requirements are proposed for the tag attributes of MAC ports.


If Tag is set to Access for a port, packets without VLAN IDs are added with the default VLAN IDs when they enter the port. After these packets are transmitted from the port, their VLAN IDs are peeled off.

l

If Tag is set to Hybrid for a port, packets without VLAN IDs are added with the default VLAN IDs when they enter the port. After these packets are transmitted from the port, the VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these packets are directly transmitted.

l

If Tag is set to Tag Aware for a port, packets without VLAN IDs are discarded before they enter the port. Otherwise, these packets are directly transmitted.

l

For C-Aware and S-Aware ports, the tag attribute cannot be set.

Related Information Mapping relationship between the packets handled by the port and the tag identifiers Packet Type

Attribute of the Ingress Port

Handling Method

Ethernet packets that contain tags

Tag aware

The port transmits these packets.

Access

The port discards these packets.

Hybrid

The port transmits these packets.

Tag aware

The port discards these packets.

Access

The port transmits these packets after adding the default VLAN ID to these packets.

Hybrid

The port transmits these packets after adding the default VLAN ID to these packets.

Ethernet packets that do not contain tags

A.2.21 Mapping Protocol Description The Mapping Protocol parameter specifies the mapping protocol of the VCTRUNK port. Issue 03 (2013-02-20)


606



Impact on the System The Mapping Protocol parameter of the VCTRUNK is the basic setting of the VCTRUNK port. If the parameter value is different from that of Mapping Protocol for the VCTRUNK of the interconnected equipment, the service is interrupted.

Values Table A-1 shows the value range of each type of board. Table A-1 The mapping protocol supported by each type of board Board Name

Value Range

Default Value

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EFT8, N1EFT8A, N1EGT2, N2EGT2, R1EFT4

l GFP

GFP

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EAS2, N1EFS0A, N1EMS2

GFP

GFP

N2EMR0, N2EGR2

l GFP

GFP

l LAPS l HDLC

l LAPS


Description

GFP

Uses the GFP protocol to encapsulate the data of the VCTRUNK port.

LAPS

Uses the LAPS protocol to encapsulate the data of the VCTRUNK port.

HDLC

Uses the HDLC protocol to encapsulate the data of the VCTRUNK port.

Configuration Guidelines The value of Mapping Protocol for VCTRUNK of the local equipment must be the same as that of Mapping Protocol for the VCTRUNK of the interconnected equipment.


Issue 03 (2013-02-20)


607



A.2.22 Scramble Description The Scramble parameter specifies whether to scramble the payload area of the encapsulation protocol and the scramble mode.

Impact on the System If the value of Scramble for the VCTRUNK of the local equipment is different from that of Scramble for the VCTRUNK of the interconnected equipment, the service is interrupted.

Values Table A-2 shows the value range of each type of board. Table A-2 Scramble supported by each type of board Board Name

Value Range

N4EFS0, N2EFS4, N2EGS2, N1EFT8, N1EFT8A, N1EGT2, R1EFT4, N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EAS2, N1EFS0A, N1EMS2, N5EFS0, N3EFS4, N3EGS2, N2EGT2

l Unscramble

N2EMR0, N2EGR2

Scramble mode[X43+1]

l Scramble mode[X43+1]

Default Value Scramble mode [X43+1]

Scramble mode [X43+1]


Description

Unscramble

Does not scramble the payload area.

Scramble mode[X43+1]

Scrambles the payload area in [X43+1] mode.

Configuration Guidelines The value of Scramble for VCTRUNK must be the same as that of Scramble for the VCTRUNK of the interconnected equipment.

Relationship with Other Parameters For the N4EFS0, N2EFS4, N2EGS2, N1EFT8, N1EFT8A, N1EGT2 or R1EFT4 board, if Mapping Protocol is set to LAPS, Scramble can be set to Unscramble or Scramble mode [X43+1] only. Issue 03 (2013-02-20)


608



A.2.23 Set Inverse Value for CRC Description The Set Inverse Value for CRC parameter specifies whether to set an inverse value for the CRC field of the HDLC or LAPS protocol.

Impact on the System If the value of Set Inverse Value for CRC for the VCTRUNK of the local equipment is different from that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment, the service is interrupted.

Values Value Range

Default Value

Yes, No

Yes


Description

Yes

Sets an inverse value for the CRC field.

No

Does not set an inverse value for the CRC field.

Configuration Guidelines The value of Set Inverse Value for CRC for VCTRUNK of the local equipment must be the same as that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment.

Relationship with Other Parameters This parameter takes effect only when Mapping Protocol is set to LAPS or HDLC.

A.2.24 Check Field Length Description The Check Field Length parameter specifies the length of the CRC field of the mapping protocol.

Impact on the System If Mapping Protocol is set to HDLCor LAPS, and if the value of Check Field Length is different from that for the interconnected VCTRUNKs at the two ends, the service is interrupted. Issue 03 (2013-02-20)


609



Values Table A-3 shows the value range of each type of board. Table A-3 The length of the CRC field supported by each type of board Mapping Protocol

Value Range

Default Value

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2, N1EAS2

GFP

l FCS32

FCS32

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EGT2, N2EGT2

GFP

Board Name

N2EMR0, N2EGR2, N1EGT2, N1EFT8, N1EFT8A, R1EFT4

l No

l FCS32

FCS32

l No LAPS

FCS32

HDLC

FCS32

GFP

l FCS32

FCS32

l No LAPS

FCS32


Description

No

The protocol frame does not contain the CRC field. Only the GFP protocol supports this option.

FCS32

The CRC field of the protocol frame contains 32 bits.

Configuration Guidelines If Mapping Protocol is set to HDLC or LAPS, the value of Check Field Length must be consistent for the interconnected VCTRUNKs at the two ends.

Relationship with Other Parameters If Mapping Protocol is set to HDLC or LAPS, select FCS32 only.

A.2.25 FCS Calculated Bit Sequence Description The FCS Calculated Bit Sequence parameter specifies the sequence of storing the bits in the CRC field of the mapping protocol. Issue 03 (2013-02-20)


610



Impact on the System If the value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment is different from that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected equipment, the service is interrupted.

Values Table A-4 shows the value range of each type of board. Table A-4 FCS calculated bit sequence supported by each type of boards Board Name N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EGT2, N2EGT2

Mapping Protocol

Value Range

Default Value

GFP

Big endian

l Mapping Protocol: GFP l FCS Calculated Bit Sequence: Big endian

l LAPS

Little endian

l HDLC


N2EMR0, N2EGR2

GFP

Big endian


LAPS

Little endian Big endian


N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2, N1EAS2

GFP

Big endian

N1EFT8, N1EFT8A, R1EFT4

l GFP

Big endian

l LAPS

Little endian


l HDLC



Issue 03 (2013-02-20)

Value

Description

Big endian

Stores the FCS field based on Big endian. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

611



Value

Description

Little endian

Stores the FCS field based on Little endian.

Configuration Guidelines The value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment must the same as that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected equipment.


A.2.26 Extension Header Option Description The Extension Header Option parameter specifies whether Mapping Protocol of the GFP protocol supports the extension header.

Impact on the System For the N1EFT8, N1EFT8A, R1EFT4 or N1EAS2 board, if the value of Extension Header Option is inconsistent for the VCTRUNK ports of the interconnected equipment at the two ends, the service is interrupted. Moreover, the FCS_ERR alarm is reported.

Values Table A-5 shows the value range of each type of board. Table A-5 Extension header option supported by each type of board Board Name

Value Range

Default Value

N4EFS0, N2EFS4, N2EGS2, N1EFT8, N1EFT8A, N1EGT2, N2EGT2, R1EFT4, N1EAS2, N2EMR0, N2EGR2

l Yes

No

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N5EFS0, N3EFS4, N3EGS2, N1EFS0A, N1EMS2

No

l No

No



612



Value

Description

Yes

Supports the extension header.

No

Does not support the extension header.

Configuration Guidelines Select the value according to whether the GFP protocol is required to support the extension header.

Relationship with Other Parameters This parameter takes effect only when Mapping Protocol is set to GFP.

A.3 Ethernet Service Associated Parameters (Packet Mode) This topic describes the parameters for configuring Ethernet services.

A.3.1 PW Signaling Type(PW Management) Description The PW Signaling Type (PW Management) parameter can query the signaling type of a PW. The signaling can be of the dynamic or static type. In the case of the dynamic PW, the services are available after the signaling negotiation is successful. In the case of the static PW, the signaling negotiation is not required. Currently, the OptiX OSN equipment supports only the static PW.

Impact on the System This parameter does not affect the system operation.

Values Value Range

Default Value

Static

-

The following table lists the description of each value.

Issue 03 (2013-02-20)

Value

Description

Static

Indicates that the PW is statically created.


613





A.3.2 Bearer Type (E-Line Service) Description The Bearer Type (E-Line Service) parameter specifies the bearer type for different types of Ethernet services. The value of this parameter can be set to Port, PW, or QinQ Link.


Values Value Range

Default Value

Port, PW, QinQ Link

-


Description

PW

The bearer is the PW, and the PW ID needs to be specified.

Port

The bearer is the physical port, and the slot ID and port number needs to be specified.

QinQ Link

The bearer is the QinQ link, and the QinQ link ID needs to be specified.


The bearer of the E-Line service V-NNI can be the PW, port, or QinQ link.

l

The bearer of the E-LAN service V-NNI can be the PW, port, or QinQ link.

l

The bear of the E-AGGR service V-NNI can be the PW or port.

A.3.3 PW ID(E-Line Service) Description The PW ID parameter identifies the PW. Issue 03 (2013-02-20)


614




Values Value Range

Default Value

1-4294967295

-



A.3.4 BPDU Description The BPDU parameter sets whether the service needs transparently transmit the bridge protocol 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 is computed.

Impact on the System If the BPDU transparent transmission identifier of the Ethernet service of an NE is enabled, the port where the service V-UNI resides cannot process the BPDU packets. After the BPDU transparent transmission is enabled, the BPDU packets are transmitted.

Values Value Range

Default Value

Transparently Transmitted, Not Transparently Transmitted



Issue 03 (2013-02-20)

Value

Description

Transparently Transmitted

BPDU packets are transparently transmitted to and processed on the opposite NE instead of being terminated on the local NE.


615



Value

Description



Configuration Guidelines If the BPDU packets need be transparently transmitted to the opposite end of the network, set the BPDU to Transparently Transmitted during the service creation. If the BPDU packets need be processed on the local NE as service packets for computing the network spanning tree, set the BPDU to Not Transparently Transmitted during the service creation.


A.3.5 MTU(bytes)(E-Line Service) Description The MTU(bytes) parameter indicates the maximum transmitted packet length, which is the length of the packet payload.

Impact on the System If the length of the packet payload exceeds the value set by the MTU, the packets are discarded during the forwarding.

Values Value Range

Default Value

Unit

46-9000

1500

Byte

Configuration Guidelines MTU(bytes) 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(bytes) should be set to a value larger than the maximum length of the user packet payload.

Relationship with Other Parameters The value of MTU(bytes) and Max Frame Length(byte) of the port can be separately configured. Issue 03 (2013-02-20)


616



A.3.6 Static MAC Address (E-LAN Service) Description The Static MAC Address parameter indicates the packet forward MAC address that is manually configured for the E-LAN service. This MAC address is not automatically aged. When the destination MAC address is the same as this MAC address, the packets are directly forwarded.


Values Value Range

Default Value

VLAN ID, MAC Address, Egress Interface

-

The following table lists the values of the sub-parameters. Parameter

Value Range

Default Value

VLAN ID

1 to 4094

-

MAC Address

00-00-00-00-00-01 to FFFF-FF-FF-FF-FE

-

Egress Interface

For example, 13N1PEG16-2(Port-2)[10]

-

Configuration Guidelines The static MAC address can be set as a unicast address, rather than as a multicast or broadcast address.


Related Information When the E-LAN service works in IVL mode, packets are forwarded based on the VLAN and MAC address. When the E-LAN service works in SVL mode, packets are forwarded based on the MAC address.

Issue 03 (2013-02-20)


617



A.3.7 Self-Learning MAC Address (E-LAN Service) Description The Self-Learning MAC Address (E-LAN Service) parameter indicates that the MAC address is obtained by the board through self-learning.

Impact on the System Querying the MAC address does not affect the system. Clearing the MAC address clears the original unicast forwarding trails. In this case, the port broadcasts the received packets whose MAC address is the deleted MAC address, and forwards these packets when the port learns the deleted MAC address again.

Values Value Range

Default Value

VLAN ID, MAC Address, Egress Interface

-


Value Range

Default Value

VLAN ID

1-4094

-

MAC Address

00-00-00-00-00-01 to FFFF-FF-FF-FF-FE

-

Egress Interface

For example, 13N1PEG16-2(Port-2)[10]

-


Description

VLAN ID

Indicates the VLAN ID that is learnt by the board.

MAC Address

Indicates the MAC address that is learnt by the board.

Egress Interface

Indicates the egress interface that is learnt by the board.

Configuration Guidelines Configure the parameter according to the service configuration information. Issue 03 (2013-02-20)


618



Relationship with Other Parameters When the E-LAN service works in IVL mode, packets are forwarded based on the VLAN and MAC address. When the E-LAN service works in SVL mode, packets are forwarded based on the MAC address.


A.3.8 Aging Time (min)(E-LAN Service) Description Set the Aging Time (min) parameter to set the aging time of the learnt MAC address. The Aging Time (min) parameter indicates that the MAC address is automatically aged after the timing is set.

Impact on the System When the Aging Time (min) parameter is reset, the MAC addresses learnt before the resetting remains aged according to the original aging time, and the MAC addresses learnt after the resetting are aged according to the current aging time. When the aging time is up, the original unicast E-LAN services are broadcast.

Values Value Range

Default Value

Unit

1-640

5

Minute as the unit and one as the spacing.

Configuration Guidelines Set the aging time of MAC addresses according to the user requirements. The minimum time is one minute.



Issue 03 (2013-02-20)


619



A.3.9 Default Forwarding Priority Description The Default Forwarding Priority parameter indicates the forwarding priority that the NE sets to the user packets on the V-UNI side by default. The OptiX OSN NE forwards and schedules packets according to the priorities of the packets. The forwarding priorities supported by the OptiX OSN NE include CS7, CS6, EF, AF4, AF3, AF2, AF1, and BE (arranged from the highest priority to the lowest).


Values Value Range

Default Value


BE


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.

AF2


AF3


AF4


EF

By default, the user packets on the V-UNI side are set to EF.

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 is set according to the mapping relationship in the DS domain.

Configuration Guidelines CS7: Indicates the highest forwarding priority, for delivering the control packets (very important protocol packets) in the network. CS6: Indicates the priority that is lower than CS7, for delivering the control packets (important protocol packets) in the network. Issue 03 (2013-02-20)


620



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. AF2: Indicates the assured forwarding priority 2, whose forwarding priority is lower than AF3. AF1: Indicates the assured forwarding priority 1, whose forwarding priority is lower than AF2. BE: Indicates the best effort forwarding priority that is the lowest forwarding priority, for the services without QoS in the network.

Relationship with Other Parameters If a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI are forwarded according to Default Forwarding Priority. If the V-UNI ingress policy is used, the packets that do not match the Traffic classification of this policy are forwarded according to Default Forwarding Priority.

A.3.10 Default Packet Relabeling Color(E-LAN Service) Description The Default Packet Relabeling Color indicates the color that the NE sets to the user packets on the V-UNI side by default. On a PTN NE, the packet color indicates the priority for discarding the packet. The packet colors are red, yellow, and green. The red packet has the highest discard priority, and thus is discard first in the case of congestion. The green packet has the lowest discard priority. The yellow packet has the middle discard priority.

Impact on the System None.

Values Value Range

Default Value


Green


Issue 03 (2013-02-20)

Value

Description

Red

The user packets on the V-UNI side are set as red.

Yellow

The user packets on the V-UNI side are set as yellow.

Green

The user packets on the V-UNI side are set as green. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

621



Value

Description

None.

The priority of the user packets on the V-UNI side is set according to the mapping relationship of the DS domain.

Configuration Guidelines The user packets of a higher priority should be marked green. The user packets of a lower priority should be marked red. The user packets of a medium priority should be marked yellow.

Relationship with Other Parameters If a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI are marked according to Default Packet Relabeling Color. If the V-UNI ingress policy is used, the packets that do not match the Traffic classification of this policy should be marked according to Default Packet Relabeling Color.

A.3.11 Split Horizon Group ID(E-LAN Service) Description The Split Horizon Group ID parameter identifies the split horizon group.


Values Split Horizon Group ID Value Range

Default Value

1

-



Related Information None. Issue 03 (2013-02-20)


622



A.3.12 Split Horizon Group Member (E-LAN Service) Description The Split Horizon Group Member parameter indicates the logical port member in a split horizon group.

Impact on the System The member ports added to the same split horizon group cannot communicate with each other.

Values Value Range

Default Value

Slot number - board - port number - VLANs

-

Configuration Guidelines One service can be configured with only one split horizon group.



A.3.13 Source Interface Type(E-AGGR Service) Description Set the Source Interface Type parameter to set the source interface type of the VLAN switching table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Impact on the System Set the source interface type of the E-AGGR service as the same as the opposite logical interface type.

Values Value Range

Default Value

V-UNI, V-NNI

-



623



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.

Configuration Guidelines The logical interface type of the source interface of the VLAN switching table for the E-AGGR service can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, should be of the same type.



A.3.14 Sink Interface Type(E-AGGR Service) Description Set the Sink Interface Type parameter to set the sink interface type of the VLAN switching table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Impact on the System Set the sink interface type of the E-AGGR service same as the opposite logical interface type. Otherwise, the E-AGGR service is not available.

Values Value Range

Default Value

V-UNI, V-NNI

-


Issue 03 (2013-02-20)

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.


624



Configuration Guidelines The logical interface type of the sink interface of the VLAN switching table for the E-AGGR service can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, should be of the same type.



A.4 CES Service Associated Parameters This topic describes the parameters for configuring CES services.

A.4.1 Packet Loading Time (us) Description The Packet Loading Time (us) parameter specifies the packet loading duration. The efficiency of packet loading can be improved after the packet loading time is set.

Impact on the System The packet loading time affects the number of frames of E1 signals in each packet.

Values Value Range

Default Value

Unit

125-5000

1000

us

Configuration Guidelines The value of the packet loading time ranges from 125 to 5000 in steps of 125. The default bandwidth for a PW that transmits an CES service is 3 Mbit/s. If Packet Loading Time (us) is set to 125 or 250, and if RTP Header is set to Enable Huawei RTP or Enable a Standard RTP, the bandwidth for a PW is 4 Mbit/s.

Relationship with Other Parameters The packet loading time is closely related to the jitter compensation buffering time. The jitter compensation buffering time must be greater than double packet loading time. Issue 03 (2013-02-20)


625



Before changing the parameter value of a PW, you need to ensure that the PW is not bound with the service. After the change, you need to bind the PW with the service, and then check whether the parameter value is changed.

Related Information If the default value of the packet loading time is 1000 ms/packet, because the rate of E1 signals is 8000 frames/s, the number of the frames in each packet is: 8000 frames/s * 1000 ms/packet = 8 frames.

A.4.2 RTP Header Description The RTP Header parameter specifies whether the RTP header function is enabled. The RTP header is used to load clock signals. Figure A-1 RPT Header Format 0

1 V

2

3

P

X

4

5

6

CC

7

0 M

1

2

3

4

5

6

7

0

1

2

3

4

PT

5

6

7

0

1

2

3

4

5

6

7

Sequence Number Timestamp

Synchronization Source(SSRC) Identifiers Contributing Source(CSRC) Identifiers

Set Version (V) to 2. Set Padding (P), Header Extension (X), CSRC Count (CC), and Marker (M) to 0. Payload type (PT): l

PT values are allocated to each direction of a PW, and the PT values are in a dynamic value range. The receive and transmit directions of a PW can share a PT value. Different PWs can share a PT value.

l

The PE on the upstream PW puts the allocated PT value in the PT field of the RTP header.

l

The PE on the upstream PW can detect exceptional packets according to the received PT value.

The sequence number must be the same as the serial number in the CESoPSN control word. The timestamp is used for carrying the time information in the network. Two timestamp generation modes are as follows: l

Issue 03 (2013-02-20)

Absolute mode: The TDM circuit can restore clock information and upstream PE sets the timestamp according to the clock. The timestamp is closely related to the serial number. All equipment supporting CESoPSN must support the absolute mode. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

626


l


Differential mode: The PE on the PW receives high-quality synchronization clock source, which is used to generate the timestamp. The timestamp indicates the difference between the common clock source and the TDM circuit clock. The differential mode is optional.

The synchronization source identifiers are used for detecting errored connections.

Impact on the System The adaptive clock recover (ACR) is supported only when the RTP header is enabled.

Values Value Range

Default Value

Disable, Enable the Huawei RTP, Enable a Standard RTP

Disable


Description

Disable

Indicates that the RTP is disabled.

Enable Huawei RTP

Indicates that the Huawei RTP is enabled.

Enable a Standard RTP

Indicates that a standard RTP is enabled.

Configuration Guidelines The default bandwidth for a PW that transmits an CES service is 3 Mbit/s. If Packet Loading Time (us) is set to 125 or 250, and if RTP Header is set to Enable Huawei RTP or Enable a Standard RTP, the bandwidth for a PW is 4 Mbit/s.

Relationship with Other Parameters Before changing the parameter value of a PW, you need to ensure that the PW is not bound with the service. After the change, you need to bind the PW with the service, and then check whether the parameter value is changed.

A.4.3 Jitter Compensation Buffering Time (us) Description The Jitter Compensation Buffering Time (us) parameter specifies the size of the jitter buffer. The jitter compensation buffering time is configured to absorb jitters on the network side.

Impact on the System The jitter compensation buffering time affects the delay of services. Issue 03 (2013-02-20)


627



If the jitter compensation buffering time is set, the subsequent operations are performed after the system has received packets for more than a half of the jitter compensation buffering time.

Values Value Range

Default Value

Unit

125-64000

8000

us

Configuration Guidelines The value of the jitter compensation buffering time ranges from 125 to 64000 in steps of 125.

Relationship with Other Parameters The packet loading time is closely related to the jitter compensation buffering time. The jitter compensation buffering time must be greater than double packet loading time. Before changing the parameter value of a PW, you need to ensure that the PW is not bound with the service. After the change, you need to bind the PW with the service, and then check whether the parameter value is changed.

Related Information The principle of delays on the network side and jitters are as follows. Total delays of CES services include: l

TDM transmission time (can be neglected)

l

Packet encapsulation duration (packet loading duration)

l

Packet processing and forwarding duration

l

Packet transmission duration on Ethernet links

Assume that the interval between the arrival time of packet 1 and packet 2 is T. Encapsulation of packet 1 is completed at t(0). After t1, packet 1 is processed and forwarded to the opposite end. Encapsulation of packet 2 begins at t(0) and is completed after tp. Then, after t2, packet 2 is processed and forwarded to the opposite end. T = (tp + t2) - t1 = tp + (t2 - t1), that is, transmission time difference between packet 1 and 2 equals the sum of packet loading time and transmission time of the packets 1 and 2. The interval between the arrival time of two packets is called jitters on the network side. The more serious the delay jitter on the network side, the more system resource occupied to smooth the jitters. The working principle of the jitter buffer is as follows. The jitter buffer is in the egress direction (from the network side to the TDM side) of the link. Packets are transmitted on the network side and received periodically on the TDM side. The packets received on the network side are burst packets, E1 services received on the TDM side are constant data streams. If the jitter compensation buffering time is set, after the system has received packets for a half of the jitter compensation buffering time, the subsequent operations are performed. The attributes Issue 03 (2013-02-20)


628



of a jitter buffer include depth and delay. When configuring advanced attributes of PW on the NMS, the jitter compensation buffering time is the depth of a jitter buffer. If the depth of a jitter buffer is 8000 ms, the subsequent operations are performed after the jitter buffer has received packets for 4000 ms. Therefore, even the packets from the network side haves jitters, the jitter buffer stabilizes the downstream data streams. The jitter compensation buffering time varies with network conditions. If the delays or jitters of a network are large, the jitter compensation buffering time needs to be set to a greater value, and therefore, the delay of the link is prolonged. If the network-side performance is stable with a fixed delay, the size of the jitter buffer can be adjusted to approach the packet loading time to decrease the delay of the link, In this manner, the delay of the entire link is increased to greater than maximum interval between the arrival time of packet 1 and packet 2.

A.4.4 Clock Mode Description The Clock Mode parameter specifies the re-timing mode of a port. The E1 signal can be output with the 2M clock from cross-connect boards or upstream services, instead of the clock from the internal phase-locked loop, as the reference clock. If the tributary clock is of inferior quality, this parameter is set to use the external clock from the cross-connect board for tributary re-timing.

Impact on the System The clock mode affects the reference clock for outputting E1 signals.

Values Value Range

Default Value

Master Mode, Slave Mode, Line Clock Mode

Master Mode


Description

Master Mode

Indicates that the internal clock is adopted.

Slave Mode

Indicates that the clock from ACR is adopted.

Line Clock Mode

Indicates that the clock from line boards is adopted.

Configuration Guidelines None. Issue 03 (2013-02-20)


629



Relationship with Other Parameters Only the slave mode supports the adaptive clock recover (ACR) function. The parameters of a PW can be modified before the PW is bound with services, but can be verified after the PW is bound with services.

A.5 Data Service Associated Parameters (TDM Mode) This topic describes the parameters for configuring Ethernet services and SAN services.

A.5.1 Operation Type (EPL Service) Description The Operation Type (EPL Service) parameter specifies whether to add, strip, translate or transparently transmit VLAN labels for service packets at a port when Service Type is set to EVPL(QinQ).

Impact on the System After you select an operation type, the system performs the relevant operation.

Values Board Name

Valid Values

Default Value

N1EMS4, N1EGS4, N3EGS4, N4EGS4

l For bidirectional services, the options are as follows:

Add S-VLAN

– Add S-VLAN – Transparently Transmit C-VLAN – Transparently Transmit S-VLAN – Translate C-VLAN – Translate S-VLAN l For unidirectional services, the options are as follows: – Add S-VLAN – Add S-VLAN and C-VLAN – Strip C-VLAN – Strip S-VLAN – Strip S-VLAN and C-VLAN – Transparently transmit C-VLAN – Transparently transmit S-VLAN – Translate C-VLAN – Translate S-VLAN

Issue 03 (2013-02-20)


630



Board Name

Valid Values

Default Value

N1EAS2

l For bidirectional services, the options are as follows:

Add S-VLAN

– Add S-VLAN – Translate S-VLAN – Transparently Transmit S-VLAN – Transparently Transmit C-VLAN l For unidirectional services, the options are as follows: – Add S-VLAN – Strip S-VLAN – Translate S-VLAN – Transparently Transmit S-VLAN – Transparently Transmit C-VLAN


Issue 03 (2013-02-20)

Value

Description

Add S-VLAN

Indicates that the one layer of S-VLAN label is added to the processed packets in the service.

Translate S-VLAN

If the source S-VLAN labels of the packets processed in the service are translated into the sink S-VLAN labels, the source S-VLAN label must be different from the sink S-VLAN label.

Transparently transmit SVLAN

Forwards the service packets according to the port or S-VLAN. After the packets are processed in the service, the S-VLAN labels in the packets are not changed.

Translate C-VLAN

If the source C-VLAN labels of the packets processed in the service are translated into the sink C-VLAN labels, the source C-VLAN labels must be different from the sink C-VLAN labels.

Transparently transmit CVLAN

Forwards the service packets according to the port or C-VLAN. After the packets are processed in the service, the C-VLAN labels in the packet are not changed.

Add S-VLAN and CVLAN

Indicates that the C-VLAN and S-VLAN labels are added to the packets processed in the service.

Strip C-VLAN

Strips the C-VLAN label.

Strip S-VLAN

Strips the S-VLAN label.

Strip S-VLAN and CVLAN

Strips the S-VLAN and C-VLAN labels.


631



Configuration Guidelines Select a proper item according to network planning and service model.


A.5.2 Service Type (EPL Service) Description The Service Type (EPL Service) parameter specifies the Ethernet private line service type.


Values Board Name

Valid Values

Default Value

N1EFT8, N1EFT8A, N1EGT2, N2EGT2, R1EFT4

EPL

EPL

N2EFS4, N3EFS4, N4EFS0, N5EFS0, N2EGS2, N3EGS2, N2EMR0, N2EGR2, N1EFS0A, N1EMS2

EPL, Transit(MPLS), EVPL (MPLS)

EPL

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N1EAS2

EPL, EVPL(QinQ)

EPL


Description

EPL

Indicates the transparent transmission service or the VLAN private line service.

Transit(MPLS)

Indicates the Ethernet virtual private line service of switching MPLS labels.

EVPL(QinQ)

Indicates the Ethernet QinQ virtual private line service.

EVPL(MPLS)

Indicates the Ethernet virtual private line service of adding or deleting MPLS labels.

Configuration Guidelines Select a service type as required. Issue 03 (2013-02-20)


632




A.5.3 Encapsulation Format of P Port (Network Attributes) Description Encapsulation Format of P Port (Network Attributes) indicates that the board supports receiving of data packets in the MPLS encapsulation format and normal Ethernet data packets. The port needs to process different types of packets in different ways, so you need to set the port to a PE port or a P port. The PE port is not configured with the encapsulation format, while the P port is configured with the encapsulation format. The P port indicates a port for connecting the equipment of the network provider, so the P port receives data packets in the MPLS encapsulation format. You can set the packet encapsulation format of the P port by running the configuration command.

Impact on the System If the encapsulation format of the data packet that enters the port is inconsistent with the configured encapsulation format of the port, the data packet is discarded.

Values Value Range

Default Value

MartinioE, stack VLAN

MartinioE


Description

MartinioE

Figure A-2 shows the encapsulation format of MartinioE.

Stack VLAN

Figure A-3 shows the encapsulation format of Stack VLAN.

Configuration Guidelines The user can choose an encapsulation format according to the requirements of the service. Different encapsulation formats support different types of data packets. When the encapsulation format is inconsistent with the type of the receive data packet, the data packet is discarded. When configuring services, the user needs to make sure that the encapsulation format of the port is consistent with the type of the data packet that is transmitted by the interconnected equipment.



633



Related Information Figure A-2 Encapsulation format of MartinioE

DA SA

0x8847

Tunnel

VC

6

2

4

4

6

Ethernet Data N

Figure A-3 Encapsulation format of Stack VLAN

DA SA

0x8100

VLAN

VLAN TAG L3Data

A.5.4 C-VLAN and S-VLAN Description The C-VLAN and S-VLAN parameter specifies the two types of VLAN tags defined in the QinQ service and IEEE 802.1ad. C-VLAN is taken as the client VLAN tag. S-VLAN is taken as the service VLAN tag. C-VLAN Tag (C-TAG) indicates the VLAN tag on the client side, and S-VLAN Tag (S-TAG) indicates the VLAN tag at the service layer of the carrier. DMAC

SMAC

S-VLAN

C-VLAN

Data

FCS

6 bytes

6 bytes

4 bytes

4 bytes

-

4 bytes


Values Valid Values

Default Value

Empty, 1-4095

Empty


Issue 03 (2013-02-20)


634



Value

Description

Empty

Indicates that the port does check the C-VLAN/S-VLAN. The services are forwarded according to the port.

1-4095

Indicates that the port checks the C-VLAN/S-VLAN. The services are forwarded according to the port and C-VLAN/SVLAN.

Configuration Guidelines Select the value according to the network. Generally, select C-VLAN and S-VLAN allocated by the carrier.


A.5.5 VLAN ID (For Creation of Ethernet Virtual Private Lines) Description VLAN ID-- stands for virtual local area network identifier. If port+VLAN is selected in the policy of using a port, you can select different VLAN IDs (1-4095) to represent different Ethernet services.


Values Value Range

Default Value

1 to 4095

-


The value range is relevant to the encapsulation format of the P port (Per-NE configuration). In the case of Martinio E, the value ranges from 16 to 1023. In the case of stack VLAN, the value ranges from 1 to 4095.

l

The VLAN IDs at both ends of a link must be the same. In the case of different Ethernet services, you can set the VLAN ID to different values.

Relationship with Other Parameters This parameter is valid only when you set "Flow Type" to "Port+VLAN". Issue 03 (2013-02-20)


635



A.5.6 MAC Address Aging Time / Aging Time Unit Description The MAC Address Aging Time parameter specifies the valid duration of a dynamically learnt MAC address in the MAC address table. During the specified aging time: l

If no more packets are received from this MAC address, the MAC address is deleted from the MAC address table.

l

If more packets are received from this MAC address, reset the aging time of the MAC address.

The aging time includes two parts: aging time value and aging time unit.

Impact on the System The parameter value may affect the forwarding efficiency of the EPLAN or EVPLAN service. l

Extremely long aging time results in expiration of the MAC address table in the board. In this case, the board makes an incorrect decision to filter or forward packets. Consequently, the forwarding efficiency is affected.

l

Extremely short aging time results in frequent refreshing of the MAC address table. In this case, the destination addresses fail to be found in the MAC address table for the large quantity of received data packets. The board has to broadcast these data packets to all the ports. Consequently, the forwarding efficiency is greatly affected.

Values The value range of the aging time value is as follows: Value Range

Default Value

1-120

5

The value range of the aging time unit is as follows: Value Range

Default Value

Min, Hour, Day

Min

Configuration Guidelines The parameter value may affect the forwarding efficiency of the EPLAN or EVPLAN service. Generally, use the default value. For example, to set the aging time to 20 days, set the aging time to 20, and then set the aging time unit to Day. Issue 03 (2013-02-20)


636




A.5.7 Hub/Spoke (Ethernet LAN Service) Description Hub/Spoke (Ethernet LAN Service) is used to separate packets between the logical ports in the network bridge. In the same VB VLAN filter or plain bridge: l

Communication is available between ports configured with Hub.

l

Communication is available between a port configured with Spoke and a port configured with Hub.

l

Communication is unavailable between ports both configured with Spoke.

Impact on the System If Hub/Spoke is set improperly, services may be interrupted or packets may be forwarded to a wrong user.

Values Value Range

Default Value

Hub, Spoke

Hub

Configuration Guidelines Set this parameter according to the isolation domain range of the user. For example, to make communication available between the headquarters and branch but unavailable between the branches, Hub is set for the headquarters, and Spoke is set for the branches. In this case, communication is available between the headquarters and any one of the branches but unavailable between any two of the branches.


A.5.8 Actual MAC Address Table Capacity (Ethernet LAN Service) Description Actual MAC Address Table Capacity (Ethernet LAN Service) indicates different meanings for different Ethernet service processing boards. Issue 03 (2013-02-20)


637



l

For the N4EFS0 and N2EFS4, this parameter indicates the number of MAC addresses that are dynamically learnt from a VB logical port or VLAN filter. The MAC addresses in the static MAC address table and forbidden MAC addresses are not included.

l

For the N1EMS4, N1EGS4 and N3EGS4, this parameter indicates the number of MAC addresses that are dynamically learnt from a VLAN filter. The MAC addresses in the static MAC address table and forbidden MAC addresses are not included.

l

For the N2EMR0 and N2EGR2, this parameter indicates the number of MAC addresses that are dynamically learnt from a VB logical port. The MAC addresses in the static MAC address table and forbidden MAC addresses are not included.

l

For the N1EAS2, this parameter indicates the number of dynamic MAC addresses that are queried in the VLAN filter.

Impact on the System This parameter is for query only and the system operation is not affected.

Values For example, for the N1EMS4, N1EGS4 and N3EGS4, if the port dynamically learns five MAC addresses, the actual capacity of the MAC address is five.



A.5.9 Specified MAC Address Table Capacity (Ethernet LAN Service) Description Specified MAC Address Table Capacity (Ethernet LAN Service) indicates the maximum number of MAC addresses that are dynamically learnt from the VB logical port or the VLAN filter. In excess of the maximum number, the source MAC address of the packet that enters the logical port is not learnt and the packet is discarded.

Impact on the System When the number of addresses reaches the Specified MAC Address Table Capacity value, the packet that is not listed in the MAC address table is not learnt and forwarded.

Issue 03 (2013-02-20)


638



Values Board Name

Value Range

Default Value

Description

N4EFS0, N2EFS4, N1EFS0A, N1EMS2, N3EFS4, N3EGS2, N5EFS0

l No Limit

No Limit

No Limit indicates that the MAC address capacity is 16384.

l 0-16384

0-16384 indicates the allowable size of the MAC address table, which specifies MAC Address Table Capacity of the VB logical port or VLAN filter. N1EMS4, N1EGS4, N3EGS4, N4EGS4

l No Limit

No Limit

l 0-129535

No Limit indicates that the MAC address capacity is 129535. 0-129535 indicates the allowable size of the MAC address table, which specifies MAC Address Table Capacity of the VLAN filter.

N2EMR0, N2EGR2

l No Limit

No Limit

l 0-65535

No Limit indicates that the MAC address capacity is 65535. 0-65535 indicates the allowable size of the MAC address table, which specifies MAC Address Table Capacity of the VB logical port.

Configuration Guidelines The user can specify this parameter for the VB logical port or VLAN filter as required.

Relationship with Other Parameters For the N4EFS0, N2EFS4, N1EMS4, N1EGS4, N3EGS4, N2EMR0 and N2EGR2, this capacity is related to the number of MAC addresses that are dynamically learnt only. The MAC addresses in the static MAC address table and forbidden MAC addresses are not included. Issue 03 (2013-02-20)


639



A.5.10 Bridge Learning Mode (Ethernet LAN Service) Description Bridge Learning Mode (Ethernet LAN Service) indicates how the bridge learns the MAC address. Bridge Learning Mode is classified into the shared VLAN learning and independent VLAN learning modes. The shared VLAN learning mode indicates learning and forwarding based on the MAC address. The independent VLAN learning mode indicates learning and forwarding based on the VLAN and MAC address.

Impact on the System The independent VLAN learning mode realizes the functions of broadcast packet constraint and virtual workgroup and ensures that the data are transmitted safely on the network. The shared VLAN learning mode indicates the MAC address that is learnt by this VLAN interface is shared by all the other VLAN interfaces, which reduces the safety of data packets.

Values Value Range

Default Value

IVL, SVL

IVL (The bridge type is compliant with IEEE 802.1q or IEEE 802.1ad), SVL (The bridge type is compliant with IEEE 802.1d)


Description

SVL

Indicates that in the shared VLAN learning mode, the bridge learns all the data messages based on the MAC address.

IVL

Indicates that in the independent VLAN learning mode, data packets of different VLAN interfaces are not associated.

Configuration Guidelines The user can set the parameter according to the networking requirements.


Issue 03 (2013-02-20)


640



A.5.11 Self-learning MAC Address (Ethernet LAN Service) Description Self-learning MAC Address (Ethernet LAN Service) indicates the starting MAC address for the batch query in the address table. The starting MAC address can be the first one in the address table, or the one where the last query ends.


Values Value Range

Default Value

First Page, Previous Page, Next Page

First Page


Description

First Page

Indicates physical position 0 in the entire address table. There are at most 20 MAC addresses on every page.

Previous Page

Indicates querying the page that precedes the page where the last query ends.

Next Page

Indicates querying the page that follows this page where the last query ends.

Configuration Guidelines Normally the first page is the one where the first batch query starts, and the one where the second query starts is the next page.


A.5.12 Tunnel Description Tunnel indicates the tunnel ID of this node. a tunnel ID is specified for every new EVPL (MPLS) or Transit (MPLS) service. l

Issue 03 (2013-02-20)

When the port encapsulation format is MartinioE, the Tunnel flag is the outer flag encapsulated in MPLS format that identifies a service with the VC flag. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

641


l


When the encapsulation format of the port is Stack VLAN, the Tunnel flag is the outer flag encapsulated in VMAN format.


Values Board Name

Value Range

Default Value

N5EFS0, N3EGS2, N3EFS4, N2EMR0, N2EGR2, N1EFS0A, N1EMS2

l 0-4095 (Stack VLAN)

-

N2EFS0, N4EFS0, N2EGS2, N2EFS4

l 0-4095 (Stack VLAN)

l 16-1023 (MartinioE) -

l 16-1048575 (MartinioE)

Configuration Guidelines The user can set this parameter within the value range as required. The Tunnel value of different services at the same node, however, cannot be the same.


A.5.13 VC Description VC indicates the VC number of the node. A VC number is specified for every new EVPL (MPLS) service. l

When the port encapsulation format is MartinioE, the VC flag is the inner flag of the MPLS encapsulation format and identifies a service with the tunnel flag.

l

When the port encapsulation format is Stack VLAN, VC is not required.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

16-1023

-


642



Configuration Guidelines You can set this parameter to any value within the value range according to the requirements of the user. The VC values of different services at the same node, however, cannot be the same.


A.5.14 Operation Type(IEEE 802.1ad Bridge) Description The Operation Type parameter specifies the mode that the port on the 802.1ad bridge uses to process the ingress packet.

Impact on the System Different operation types have different effects. Set this parameter according to the actual networking condition.

Values Value Range

Default Value

Add S-VLAN base for Port, Add SVLAN base for Port and C-VLAN, Mount Port, Mount Port and base for Port and S-VLAN

Add S-VLAN base for Port


Description

Add S-VLAN base for Port

Indicates that the S-VLAN is added to all the ingress packets.

Add S-VLAN base for Port and C-VLAN

Indicates that the S-VLAN is added to the packets that carry the specified C-VLAN.

Mount Port

Indicates the port mounting and an arbitrary SVLAN.

Mount Port and base for Port and SVLAN

Indicates the mounting based on port+S-VLAN. In this case, the S-VLAN needs to be specified.

Configuration Guidelines Set this parameter according to the actual requirement of the user. Issue 03 (2013-02-20)


643



A.5.15 Bridge Type Description The Bridge Type parameter is applicable only to the EGS4, EMS4, and EAS2 boards that support the 802.1ad bridge. In the case of the OptiX NG-SDH equipment series of a version earlier than V100R008, you only need to select the bridge mode (pure bridge or virtual bridge) to configure the VB. The 802.1d bridge supports the pure bridge and virtual bridge. To identify the pure bridge and virtual bridge defined previously, VBs are currently classified into three types, namely, 802.1d, 802.1q, and 802.1ad.

Impact on the System Various types of bridges realize different functions and require different configurations. An incorrect selection of the bridge type fails to realize the expected functions.

Values Value Range

Default Value

802.1d, 802.1q, 802.1ad

802.1q


Issue 03 (2013-02-20)

Value

Description

802.1d

The 802.1d bridge is actually the pure bridge defined previously. In contrast with the virtual bridge type supported by the board, the 802.1d bridge forwards data based on the MAC address. When the 802.1d bridge is used, the complex VLAN management is not required and the management that is similar to the Layer 2 switch is easier. A customer and a 802.1d bridge set up the one-to-one relationship. The VLAN is managed by the customer independently, which does not require the cooperation of the carrier.

802.1q

The 802.1q bridge is actually the virtual bridge defined previously. The 802.1q bridge forwards data based on VLAN +MAC. A customer and a VLAN set up the one-to-one relationship. Services of different VLANs are isolated.

802.1ad

The 802.1ad bridge supports the pure bridge and virtual bridge. That is, the 802.1ad bridge forwards data based on VLAN+MAC or the MAC address. The application of the 802.1ad bridge can realize the service switch between the carrier and its users and can isolate services of different users. In addition, the 802.1ad bridge can identify the voice service and data service, which improves the quality of the voice service.


644



Configuration Guidelines Set this parameter according to the actual service condition of the user.

A.5.16 SAN Service Type Description The SAN Service Type parameter specifies the service type at a board service port. This parameter decides the service type, port transmission rate, and communication mode.

Impact on the System If the service type is different from that of the interconnected equipment, the service is unavailable.

Values Valid Values

Default Value

FC service, FCION service, ESCON service, DVB-ASI service, SD-SDI service, HD-SDI service, Invalid service

Invalid service NOTE For the FCION, ESCON, DVB-ASI SD-SDI, and HD-SDI services, each service maps a rate. For the FC service, select FC100 or FC200.


Description

FCION service

Rate: 1.062 Gbit/s

ESCON service

Rate: 200 Mbit/s

DVB-ASI service

Rate: 270 Mbit/s

SD-SDI service

Rate: 270Mbit/s

HD-SDI service

Rate: 1.485Gbit/s

FC service

l FC100 Rate: 1.062 Gbit/s l FC200 Rate: 2.125 Gbit/s

Configuration Guidelines Select a proper service type as required.



645



A.5.17 Concatenation Level (SAN) Description The Concatenation Level (SAN) parameter specifies the VC level that can be bound with a VCTRUNK port.

Impact on the System If the specified service rate exceeds the rate of concatenated VCTRUNKs, the service is unavailable. Otherwise, the service is available, but the bandwidth is wasted. Examples are provided as follows: If the service rate is set to VC4-4C, the FICON, FC100 or FC200 service is unavailable. If the service rate is set to VC4-8C, the FC200 service is unavailable.

Values Valid Value

Default Value

VC4-4C, VC4-8C, VC4-16C

-


To converge DVB-ASI services or ESCON services or SD-SDI services, select VC4-4C.

l

To converge FICON services or FC100 services, select VC4-8C.

l

To converge FC200 services or HD-SDI services, select VC4-16C.


A.5.18 Enabled Flow Control of FC Port Description The Enabled Flow Control of FC Port parameter is valid for the FC100 and FC200 services only. After this parameter is set, the transmission rate is not affected within the distance of 3000 km (for the FC100 service) or 1500 km (for the FC200 service). This parameter specifies whether the distance expansion function is enabled.


Issue 03 (2013-02-20)

If Enabled Flow Control of FC Port is set to Disabled, the service rate in the link is affected when the FC100 or FC200 service is transmitted over a long distance. For example, if the CREDIT value is 20 for the storage equipment, and if the storage equipment is more than 50 km away from the SAN board, the service rate is greatly decreased. When the distance is between 20 km (for the FC200 service) or 40 km (for the FC100 service), the buffer of the storage equipment is used up. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

646



l

If Enabled Flow Control of FC Port is set to Enabled, the service rate in the link is not affected when the FC100 or FC200 service is transmitted in a long distance.

l

If the settings of the equipment are inconsistent at the two ends, the flow control function is disabled, and the service is also unavailable.

Values Valid Values

Default Value

Enabled, Disabled

Enabled


Description

Enabled

Enables the flow control function.

Disabled

Disables the flow control function.

Configuration Guidelines The Enabled Flow Control of FC Port parameter must be consistent with each other for the interconnected equipment at the two ends.


A.5.19 Initial Value of CREDIT at the Client Side Description The Initial Value of CREDIT at the Client Side parameter specifies the initial credit value for the boards at the client side. The value 1 maps the transmission distance of 2 km (for the FC100 service) and 1 km (for the FC200 service).

Impact on the System The FC100 service is transmitted in the link and the transmission distance is 10 km at the client side. l

If the parameter value is less than 5, the service rate in the link is low.

l

If the parameter value is not less than 5, the service rate in the link is close to the line speed.

The FC100 service is transmitted in the link and the transmission distance is 10 km at the client side. l Issue 03 (2013-02-20)

If the parameter value is less than 10, the service rate in the link is low. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

647


l


If the parameter value is not less than 10, the service rate in the link is close to the line speed. NOTE

If the credit value is large, the system is not affected. Generally, set it to the maximum value.

Values Valid Values

Default Value

0-20

20

The value indicates the buffer size.

Configuration Guidelines 1.

The credit values at the client side should be consistent with each other for the interconnected equipment at the two ends. In this case, the uplink rate is consistent with the downlink rate.

2.

This parameter is decided by the transmission distance at the client side. For the FC100 service, the value 0.5 maps the transmission distance of 1 km. For the FC200 service, the value 1 maps the transmission distance of 1 km.

3.

Generally, set it to 20.


A.5.20 Initial Value of CREDIT at the WAN Side Description The Initial Value of CREDIT at the WAN Side parameter specifies the initial credit value for the boards at the WAN side. The value 1 maps the transmission distance of 2 km (for the FC100 service) and 1 km (for the FC200 service).

Impact on the System The FC100 service is transmitted in the link and the transmission distance is 100 km at the client side. l

If the parameter value is less than 50, the service rate in the link is low.

l

If the parameter value is not less than 50, the service rate in the link is close to the line speed.

The FC200 service is transmitted in the link and the transmission distance is 100 km at the client side. l Issue 03 (2013-02-20)

If the parameter value is less than 100, the service rate in the link is low. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

648


l


If the parameter value is not less than 100, the service rate in the link is close to the line speed. NOTE

If the credit value is large, the system is not affected. Generally, set it to the maximum value.

Values Valid Values

Default Value

0-1500

1500

The value indicates the buffer size.

Configuration Guidelines 1.

The credit values at the WAN side need to be consistent with each other for the interconnected equipment at the two ends. In this case, the uplink rate is consistent with the downlink rate.

2.

This parameter is decided by the transmission distance at the WAN side. For the FC100 service, the value 0.5 maps the transmission distance of 1 km. For the FC200 service, the value 1 maps the transmission distance of 1 km.

3.

Generally, set it to 1500.


A.6 ETH OAM Associated Parameters (Packet Mode) This topic describes the parameters that are used for enabling the ETH-OAM function.

A.6.1 CC Test Transmit Period(Ethernet Service OAM Management) Description The source end MEP constructs the CC frames, and then transmits them periodically to the destination MEP. After the destination MEP receives the CCM messages from the source end, the CC check function of the source MEP is directly started. Within a certain period (3.5 times of the transmission period), if the destination MEP does not receive the CC packets from the source end, an alarm is automatically reported. The CC Test Transmit Period parameter indicates the transmission period of the unidirectional connectivity check.

Impact on the System After the CC check is started, a portion of the bandwidth on the port is used. Issue 03 (2013-02-20)


649



Values Value Range

Default Value

3.33ms, 10ms, 100ms, 1s, 10s, 1m, 10m

1s

Configuration Guidelines It is recommended that you use three period values, that is, 3.33 ms for protection switching, 100 ms for performance check, and 1s for connectivity check. The configuration should comply with user requirements. If the fast check is required, set to 3.33 ms. Hence, the fault can be detected quickly. The bandwidth used, however, descends with the period value.

A.6.2 Maintenance Domain Level(Ethernet Service OAM Management) Description The Maintenance Domain Level parameter indicates the level of the maintenance domain (MD). The MD level restricts the usage scope of the OAM.

Impact on the System 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. The OAM packets at a lower MD level are directly discarded.

Values Value Range

Default Value

0-7

4

The following table lists descriptions of each value. You can also define the maintenance scope for an MD level as required.

Issue 03 (2013-02-20)

Value

Description

0

Operator

1

Operator

2

Operator

3

Service Provider

4

Service Provider

5

Customer Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

650



Value

Description

6

Customer

7

Customer

Configuration Guidelines "0" indicates the lowest MD level and "7" the highest MD level. The parameter level defines the maintenance scope of the OAM operations.


Related Information Before setting this parameter, obtain the information about the MD.

A.6.3 CC Status(Ethernet Service OAM Management) Description The CC Status parameter indicates whether the CC check function of this MEP is activated.

Impact on the System If the CC is activated, the bandwidth is used. Otherwise, the bandwidth is not used.

Values Value Range

Default Value

Active, Inactive

Active

Configuration Guidelines If the check is needed, select Active. Otherwise, select Inactive.

A.6.4 Service Name(Ethernet Service OAM Management) Description The Service Name parameter indicates the type of the service to be detected by the OAM during the creation of an MA.

Impact on the System This parameter does not affect the system operation. Issue 03 (2013-02-20)


651



Values Value Range

Default Value

A character string of not more than 64 characters

-



A.6.5 Service Type(Ethernet Service OAM Management) Description The Service Type parameter indicates the type of the service to be detected by the OAM during the creation of an MA.


Values Value Range

Default Value

E-Line, E-LAN, E-AGGR

-


Description

E-Line

Indicates the Ethernet private line service.

E-LAN

Indicates the Ethernet private network service.

E-AGGR

Indicates the Ethernet aggregation service.



652





A.6.6 Activation Status(Ethernet Service OAM Management) Description The Activation Status parameter indicates whether to send the CC packet. The CC packet refers to service connectivity checking packet.

Impact on the System When 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 the remote maintenance association end point (RMEP) is located checks whether the CC packet is received. If the receive end fails to receive the CC packet, the receive end reports corresponding alarms. For example, if the receive ends fails to receive the CC packet within 3.5 cycles, the receive end reports the ETH_CFM_LOC alarm. If the attributes of the received CC packet are inconsistent with the attributes of the packet in the maintenance association (MA) of the maintenance domain (MD), the receive end reports the Mismerge alarm. When the activation status is "Inactive", the NE where the MEP is does not send any CC packet and the NE where the RMEP is does not check for an alarm.

Values Value Range

Default Value

Active, Inactive

Active


Issue 03 (2013-02-20)

Value

Description

Active

Indicates that the NE where the MEP is starts to send the CC packet and the receive end, that is, the NE where the RMEP is checks whether the CC packet is received. If the receive end fails to receive the CC packet, the receive end reports corresponding alarms.

Inactive

Indicates that the NE where the MEP is does not send any CC packet and the NE where the RMEP is does not check for an alarm.


653



Configuration Guidelines The activation status is "Active" after the MEP is created on the NE and the service connectivity can be checked. The activation status can also be set to "Inactive".


Related Information Before setting this parameter, obtain the information about the MD, MA, MEP and RMEP.

A.6.7 Transmitted Packet Count(Ethernet Service OAM Management) Description The Transmitted Packet Count parameter indicates the number of the transmitted loopback message (LBM).


Values Value Range

Default Value

1-255

3

Configuration Guidelines The time taken ascends with the number of transmitted packets.



Issue 03 (2013-02-20)


654



A.6.8 Transmitted Packet Length(Ethernet Service OAM Management) Description The Transmitted Packet Length parameter indicates the length of the transmitted loopback message (LBM).


Values Value Range

Default Value

64-1400

64

Configuration Guidelines The default value is 64. Packets of different lengths may have different connectivity test results.



A.6.9 Transmitted Packet Priority (Ethernet Service OAM Management) Description The Transmitted Packet Priority (Ethernet Service OAM) parameter indicates the VLAN priority in the Ethernet service OAM protocol packets transmitted by the equipment.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

0-7

7


655



Configuration Guidelines Value 0 indicates the lowest priority, and value 7 indicates the highest priority. By default, value 7, the highest priority, is used.



A.6.10 Destination Maintenance Point MAC Address(Ethernet Service OAM Management) Description The Destination Maintenance Point MAC Address parameter indicates the MAC address of the port where the destination maintenance point (MP) is located.


Values Value Range

Default Value

Any valid destination unicast MAC address

-

Configuration Guidelines Indicates the MAC address of the port where the destination MP is located.



A.6.11 Response Maintenance Point ID(Ethernet Service OAM Management) Description The Response Maintenance Point ID parameter identifies the response MP according to the MAC address. Issue 03 (2013-02-20)


656




Values Value Range

Default Value

Indicates the MAC address of the port.

-

Configuration Guidelines Indicates the MAC address of the port where the response MP is located.



A.6.12 Hop Count(Ethernet Service OAM Management) Description The hop count, also called time to live (TTL), is carried with the OAM packets. The Hop Count parameter indicates the connection from the response MP to the source MP. On the trail from the source MP to the destination MP, the hop count for the packets decreases by one when the packets pass through each maintenance intermediate point (MIP). For example, the packets pass through one MIP and reach the response MP, the returned hop count is 1. The maximum value of the Hop Count parameter is 64. If the packets pass through 64 MPs and fail to reach the response MP, the OAM packets are discarded. In this case, value "/" is returned.


Values Value Range

Default Value

1-64, /

/

Configuration Guidelines The Hop Count parameter cannot be set. When the loopback test (LT) is complete, a value is returned. When the OAM packets pass through 64 MPs and fail to reach the response MP, the "/" value is returned. Issue 03 (2013-02-20)


657





A.6.13 Test Result(Ethernet Service OAM Management) Description The Test Result parameter indicates the trail information about the link connection from the source maintenance point to the destination maintenance point during the LT test. If the trail from the source maintenance point to the destination maintenance point cannot be obtained, the operation failure information is reported. If the trail from the source maintenance point to the destination maintenance point transits the intermediate equipment or destination equipment, the operation success information is reported.


Values Value Range

Default Value

Character string

-


A.7 ETH-OAM Associated Parameters (TDM Mode) This topic describes the parameters for configuring the ETH-OAM function.

A.7.1 MP ID (Ethernet OAM) Description The MP ID (Ethernet OAM) specifies the flag that uniquely identifies a maintenance point. The bytes from higher bits to lower bits are respectively described here. The first byte indicates the network number. The second byte indicates the number of the node in the local network. The third and forth bytes indicate the ID of the maintenance point on the network node. The maintenance point ID must be unique in the entire network. Issue 03 (2013-02-20)


658




Values Valid Values

Default Value

00-00-0001 to FF-FF-FF00

00-00-0001

Configuration Guidelines The maintenance point ID must be unique in the entire network. Moreover, the U2000 can check whether the maintenance point ID is duplicate.


A.7.2 Maintenance Point Type (Ethernet OAM) Description The Maintenance Point Type (Ethernet OAM) specifies the maintenance point type defined in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for Maintenance association Intermediate Point.


Values Valid Values

Default Value

MEP, MIP

MEP



Issue 03 (2013-02-20)


659



A.7.3 CC Status (Ethernet OAM) Description The CC Status (Ethernet OAM) parameter specifies whether to activate the connectivity check (CC) function at a maintenance point.

Impact on the System After the CC function is activated, the maintenance point starts the CC. If the check is initially successful, the EX_ETHOAM_CC_LOS alarm is reported if a CC failure occurs later.

Values Valid Values

Default Value

Activate, Inactivate

Inactivate

Configuration Guidelines To start the connectivity check, activate the CC function at a maintenance endpoint. To stop the connectivity check, deactivate the CC function.

Relationship with Other Parameters The CC function can be activated at a maintenance endpoint only.

A.7.4 CC Activate Flag Description The CC Activate Flag parameter specifies whether the CC function is enabled. This function helps users check the link connectivity.

Impact on the System When the CC function is enabled, a CC cell is inserted every second if no user cells are transmitted from the CC source end. In this case, the CC_LOC alarm is reported if no user cells or CC cells are received at the CC sink end within a period ranging from 3s to 4s.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

Deactivate, Source activate, Sink activate, Source + sink activate

Deactivate


660




Description

Deactivate

Indicates that the CC function is disabled.

Source activate

Indicates that the local end with the CC function enabled functions as the source end, that is, the end that initiates the CC test by inserting the CC cell.

Sink activate

Indicates that the local end with the CC function enabled functions as the sink end, that is, the end that determines the normal connectivity by receiving the CC cell.

Source + sink activate

Indicates that the CC function is enabled at the source end and at the sink end. That is, the local end inserts the CC cell to initiate the CC check for the opposite end and receives the CC cell and user cell inserted by the opposite end. In this case, the local end functions as the sink end and source end.

Configuration Guidelines Set this parameter according to the actual requirement of the user.

A.7.5 Test Result (LB and LT Test) Description The Test Result (LB and LT Test) parameter specifies the result derived from the LB or LT test each time.


Values Valid Values

Default Value

Succeeded, Failed

-




661



A.7.6 Responding MP Type (Ethernet LT Test) Description The Responding MP Type (Ethernet LT Test) parameter specifies the type of the responding maintenance point in each LT test.


Values Valid Values

Default Value

MEP, MIP, Unknown

Unknown


Relationship with Other Parameters The responding maintenance point must return the type, which is specified when this maintenance point is created.

A.7.7 Hop Count (Ethernet LT Test) Description The Hop Count (Ethernet LT Test) parameter specifies the number of hops from the maintenance source endpoint to a maintenance intermediate point, namely, the number of responding intermediate points from the maintenance source point to a certain responding point. As shown in Figure A-4, MEP1 and MEP2 are the maintenance endpoints. MIP1, MIP2, MIP3 and MIP4 are the maintenance intermediate points. In this case, the number of hops from MEP1 to MEP2 is 5, and that from MEP1 to MIP3 is 3. Figure A-4 An example of number of hops

Issue 03 (2013-02-20)


662




Values If the value of Hop Count is 2, there are two hops.



A.7.8 Send Mode (Ping Test) Description The Send Mode parameter specifies the transmission mode of the ping packet.


Values Value Range

Default Value

Burst Mode, Continue Mode

Burst Mode


Description

Burst Mode

Indicates that a certain number of ping packets are transmitted at one time.

Continue Mode

Indicates that ping packets are continuously transmitted.

Configuration Guidelines To check whether the link communication is available, set this parameter to Burst Mode to transmit several ping packets at one time. To locate the fault on the link, set this parameter to Continue Mode to continuously transmit ping packets. Issue 03 (2013-02-20)


663



A.7.9 Packet Length (Ping Test) Description The Packet Length (Ping Test) parameter specifies the maximum length of the Ping packets if the Ping operation is initiated at a maintenance endpoint.


Values Valid Values

Default Value

Unit


64

Byte

Configuration Guidelines Set this parameter according to the expected frame length.


A.7.10 Timeout (Ping Test) Description The Timeout (Ping Test) parameter specifies the waiting period in which no response message is received from the opposite end after a maintenance point initiates the Ping test. In this case, the maintenance point regards that the Ping test fails. This waiting period is called the Ping timeout time.

Impact on the System After initiating the Ping test, the maintenance point returns a Ping timeout message if it fails to receive the response message from the opposite end when the Ping timeout time is reached.

Values Valid Values

Default Value

Unit


5

Second

Configuration Guidelines Set this parameter to a lower value if the requirement is high for the response time. Issue 03 (2013-02-20)


664



Set this parameter to a higher value if the requirement is low for the response time.

Relationship with Other Parameters The values of Timeout and Ping Attempts decides the longest duration required to perform the Ping test.

A.7.11 Time To Live Description The Time To Live parameter specifies the time to live. Currently, the Ping or performance test is carried out in the equipment that is directly connected. For this reason, this parameter is always set to 128.


Values Valid Values

Default Value

Unit


5

Second



A.7.12 Delay Description The Delay parameter specifies the hold-off period from the time when packets are transmitted to the time when packets are received in each OAM Ping or performance test.


Values

Issue 03 (2013-02-20)

Valid Values

Default Value

Unit

0-Timeout time

-

ms


665




Relationship with Other Parameters The delay involves the minimum delay and the maximum delay. For details, refer to A.7.14 Max. Delay and A.7.15 Min. Delay.

A.7.13 Average Delay Description The Average Delay parameter specifies the average delay in each OAM Ping or performance test.

Impact on the System This parameter shows the overall responding speed of the opposite end.

Values In each Ping test, set the number of Ping attempts to 4. The actual test results are as follows: For the first Ping attempt, the delay is 100 ms. For the second Ping attempt, the delay is 200 ms. For the third Ping attempt, the delay is 300 ms. The forth Ping attempt fails because of timeout. In this case, the average delay is as follows: Average delay = (100 + 200 + 300) / 3 = 200 ms


Relationship with Other Parameters For the description of Delay, refer to A.7.12 Delay.

A.7.14 Max. Delay Description The Max. Delay parameter specifies the maximum delay in each Ping or performance test.

Impact on the System The system operation is not affected. Issue 03 (2013-02-20)


666



Values Valid Values

Default Value

Unit

0-Timeout time

-

ms



A.7.15 Min. Delay Description The Min. Delay parameter specifies the minimum delay in each Ping or performance test.


Values Valid Values

Default Value

Unit

0-Timeout time

-

ms



A.7.16 Detect Attempts Description The Detect Attempts parameter specifies the detection attempts for performing performance detection defined in IEEE 802.1ag.

Impact on the System If the value of Detection Count is larger, the test result is more accurate in each performance detection test. In this case, more system resources are used, and longer time is consumed. Issue 03 (2013-02-20)


667



Values Valid Values

Default Value

Unit


1

Attempt

Configuration Guidelines Set this parameter to a proper value according to the test accuracy and the system resource used in the test.


A.7.17 Send Direction (Ethernet Test) Description Send Direction (Ethernet Test) indicates the transmit direction of the test packet.


Values Value Range

Default Value

SDH Direction, /

/


Description

SDH Direction, /

Indicates that the test packet is transmitted from the VC trunk port to the SDH side.

/

Indicates that the parameter is invalid.

Relationship with Other Parameters This parameter is valid and displayed as SDH Direction only when Send Mode is set to Burst Mode or Continue Mode. This parameter is displayed as / when Send Mode is set to Disabled. Issue 03 (2013-02-20)


668



A.7.18 Error Frame Monitor Window(ms) Description The Error Frame Monitor Window(ms) parameter specifies the period during which the number of error frames received at the port exceeds the specified upper threshold. In this case, a link event alarm is reported.

Impact on the System After you set the Error Frame Monitor Threshold and Error Frame Monitor Window (ms) parameters, a link event alarm is reported if the actual number of error frames in the link exceeds the specified threshold.

Values Valid Values

Default Value

Unit


1000

ms

Configuration Guidelines Set this parameter according to the actual port rate and the monitoring period. Make sure that the value of Error Frame Monitor Threshold is not greater than the maximum number of frames received at the port within the time specified in Error Frame Monitor Window (ms).

Relationship with Other Parameters To set Error Frame Monitor Window (ms), set Error Frame Monitor Threshold. Moreover, set Port Rate. For details, refer to the description of the Error Frame Period Window (Frame) parameter.

A.7.19 Error Frame Monitor Threshold (Entries) Description The Error Frame Monitor Threshold (Entries) parameter specifies the upper threshold of error frames received at the port. In this case, a link event alarm is reported.

Impact on the System After you set the Error Frame Monitor Threshold and Error Frame Monitor Window (ms) parameters, a link event alarm is reported if the actual number of error frames in the link exceeds the specified threshold.

Issue 03 (2013-02-20)


669



Values Valid Values

Default Value

Unit

1-4294967295 (in step length of 1)

2

Frame

Configuration Guidelines If higher link performance is required, set the threshold to a lower value. Otherwise, set the threshold to a higher value. Make sure that the value of Error Frame Monitor Threshold is not greater than the maximum number of frames received at the port within the time specified in Error Frame Monitor Window (ms).

Relationship with Other Parameters To set Error Frame Monitor Threshold, set Error Frame Monitor Window (ms). Moreover, set Port Rate. For details, refer to the description of the Error Frame Period Window (Frame) parameter.

A.7.20 Error Frame Period Window (Frame) Description The Error Frame Period Window (Frame) parameter specifies the received N frames in which the number of error frames reach the specified upper threshold. In this case, a link event alarm is reported.

Impact on the System After you set the Error Frame Period Window (Frame) and Error Frame Period Threshold (Frame) parameters, a link event alarm is reported if the number of error frames received within a certain period reaches the specified upper threshold.

Values Valid Values

Default Value

Unit

Maxpps/10-Maxpps*60, in step length of 1

Maxpps

Frame

Configuration Guidelines Set this parameter according to the actual data frame transmission rate and the frames. If the data transmission rate is high, set this parameter to a higher value. Otherwise, set this parameter to a lower value. Issue 03 (2013-02-20)


670



Relationship with Other Parameters The value range depends on the port rate.

Related Information Maxpps: indicates the maximum number of frames per second. Specifically, l

If the port rate is 10 Mbit/s, the Maxpps value is 14880.

l


l


l

If the port rate is 10 Gbit/s, the Maxpps value is 14880000.

According to the rule of Maxpps/10 < Error Frame Period Window < Maxpps*60, you know the value range of the Error Frame Period Window (Frame) parameter for a certain port rate.

A.7.21 Error Frame Monitor Threshold (Frame) Description The Error Frame Monitor Threshold (Frame) parameter specifies the received N frames in which the number of error frames reach the specified upper threshold. In this case, a link event alarm is reported.

Impact on the System After you set the Error Frame Period Window (Frame) and Error Frame Period Threshold (Frame) parameters, a link event alarm is reported if the number of error frames received within a certain period reaches the specified upper threshold.

Values Valid Values

Default Value

Unit


1

Frame



A.7.22 Error Frame Second Window(s) Description The Error Frame Second Window(s) parameter specifies the error frame second when any error frames are received at the port within one second. If the error frame seconds within a certain Issue 03 (2013-02-20)


671



time period reach the specified upper threshold, link event alarms are reported. The time period in which error frames are received is called the error frame second window.

Impact on the System After you set the Error Frame Second Window (s) and Error Frame Second Threshold (s) parameters, link event alarms are reported if the actual error frame seconds in the link reach the specified upper threshold.

Values Valid Values

Default Value

Unit


60

Second

Configuration Guidelines Set this parameter according to the monitoring time period. Make sure that the value of Error Frame Second Window (s) is not less than that of Error Frame Second Threshold (s).

Relationship with Other Parameters Set the Error Frame Second Window (s) parameter together with the Error Frame Second Threshold (s) parameter.

A.7.23 Error Frame Second Threshold(s) Description The Error Frame Second Threshold(s) parameter specifies the second during which error frames are received at the port. If the error frame seconds within a certain time period reach the specified upper threshold, a link event alarm is reported. The upper threshold is called the error frame second threshold.

Impact on the System After you set the Error Frame Second Threshold (s) parameter, link event alarms are reported if the actual error frame seconds in the link reach the specified upper threshold.

Values Valid Values

Default Value

Unit


2

Second



672




A.7.24 Enable OAM Protocol Description The Enable OAM Protocol parameter specified whether the end-to-end OAM protocol (namely, the IEEE 802.3ah protocol) is enabled at a port.


Values Valid Values

Default Value

Enabled, Disabled

Disabled



A.7.25 OAM Working Mode Description The OAM Working Mode parameter specifies a negotiation mode defined in IEEE 802.3ah. It involves two modes: Passive and Active.

Impact on the System Before IEEE 802.3ah is enabled, the local and opposite ends fail to negotiate with each other if OMA Working Mode is set to Passive.

Values

Issue 03 (2013-02-20)

Valid Values

Default Value

Active, Passive

Active


673



Value

Description

Active

Indicates that a port actively transmits the IEEE 802.3 ah packets.

Passive

Indicates a port transmits the IEEE 802.3 ah packets to the opposite end only after receiving IEEE 802.3 ah packets from the opposite end.



A.7.26 Remote Alarm Support for Link Event Description The Remote Alarm Support for Link Event parameter specifies whether to report the detected link events (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold) to the opposite end.

Impact on the System After the Remote Alarm Support for Link Event parameter is set to Enabled, link event alarms are displayed in the opposite equipment if any link events occur.

Values Valid Values

Default Value

Enabled, Disabled

Enabled



A.7.27 Unidirectional Operation Description The Unidirectional Operation parameter specifies the hardware capability. If a port fails at the receive end, but can transmit data frames at the transmit end, it has the capability of performing Issue 03 (2013-02-20)


674



unidirectional operations. Otherwise, it does not have the capability of performing unidirectional operations. The unidirectional operation function specified in IEEE 802.3ah refers to whether the hardware performs unidirectional operations if it has the capability of performing unidirectional operations. If the hardware does not have the capability of performing unidirectional operations, the unidirectional operation function specified in IEEE 802.3ah is unavailable.

Impact on the System After the Unidirectional Operation parameter is set to Enabled, IEEE 802.3ah packets are still transmitted to the opposite end if the receive end is faulty.

Values Valid Values

Default Value

Enabled, Disabled

Disabled

Configuration Guidelines If the hardware has the capability of performing unidirectional operations and supports unidirectional software operations, generally, set Unidirectional Operation to Enabled.

Relationship with Other Parameters This parameter depends on whether the port hardware has the capability of performing unidirectional operations.

A.7.28 Loopback Status (OAM Parameter) Description The Loopback Status (OAM Parameter) parameter specifies whether a port on the board is in the loopback state. If yes, the port is in the Initiate Loopback at Local or Respond Loopback of Remote state.


Values

Issue 03 (2013-02-20)

Valid Values

Default Value

Initiate Loopback at Local, Respond Loopback of Remote, Non-Loopback

Non-Loopback


675




Description

Non-Loopback

Indicates that the port is not in the loopback state defined in IEEE 802.3ah.

Initiate Loopback at Local

Indicates that the local end can transmit the loopback packets to the remote end.

Respond Loopback of Remote

Indicates that the local end can respond to the loopback packets from the remote end.



A.8 PW Associated Parameters This topic describes the parameters for configuring PW services.

A.8.1 Control Word Description The Control Word parameter specifies the PW control word usage policy. The control word is the 4-byte encapsulation packet header. The control word is used to identify the packet sequence or function as stuffing bits.


Values Value Range

Default Value

No Use, Used First

-


Issue 03 (2013-02-20)


676



Value

Description

No use

Indicates that the control word is not used.

Used First

Indicates that the control word is recommended.



Related Information Figure A-5 CW structure of CESoPSN 0

1

2

3

4

5

0

0

0

0

L

R

6

7 M

0

1

2

3

FRG

4

5

6

7

0

1

2

3

4

LEN

5

6

7

0

1

2

3

4

5

6

7

3

4

5

6

7

Sequence Number

Figure A-6 CW structure of SAToP 0

1

2

3

4

5

6

7

0

0

0

0

L

R

RSV

0

1

FRG

2

3

4

5

6

7

0

1

2

3

LEN

4

5

6

7

0

1

2

Sequence Number

Compared with the CESoPSN, the M bit is changed into the RSV bit and the RSV bit is set to the value 0 in the SAToP.

A.8.2 Control Channel Type Description The Control Channel Type parameter specifies the type of channels for transmitting VCCV packets. VCCV packets are exchanged between PEs to verify connectivity of PWs. Issue 03 (2013-02-20)


677




Values Value Range

Default Value

None, CW

CW


Description

None

Indicates that the control word is not used to indicate the VCCV control channel information.

CW

Indicates that the control word is used to indicate the VCCV control channel information.



A.8.3 VCCV Verification Mode Description The VCCV Verification Mode parameter specifies the verification mode of VCCV packets.


Values Value Range

Default Value

None, Ping

Ping



678



Value

Description

None

Indicates that the VCCV function is disabled.

Ping

Indicates that the VCCV function is performed in Ping mode.



A.8.4 Request VLAN Description The Request VLAN parameter specifies the ETH request VLAN. When the PW is in Ethernet tagged mode, the PW adds the request VLAN tag to the packets that do not carry any VLAN tag from the opposite end. In the case of static PW, the local equipment adds the VLAN tag to the packets when before PW encapsulation. In the case of the dynamic PW, the opposite equipment adds the VLAN tag to the packets before PW encapsulation if the local equipment cannot add the VLAN tag.


Values Value Range

Default Value

1-4095, Non-specified

Non-specified

Configuration Guidelines When the Request VLAN parameter is set to Non-specified, the packets with tags are transmitted transparently, and the packets without tags are added with 0 VLAN tags.

Relationship with Other Parameters You need to set the PW Type parameter to Ethernet Tagged Mode. Issue 03 (2013-02-20)


679



Before changing the parameter value of a PW, you need to ensure that the PW is not bound with the service. After the change, you need to bind the PW with the service, and then check whether the parameter value is changed.

A.8.5 Competitive Working Status Description The Competitive Working Status parameter specifies the running status of a PW.


Values Value Range

Default Value

Up, Down

Up


Description

Up

The creation of a PW is successful and the PW is working properly.

Down

The creation of a PW fails and the PW cannot work properly.

Configuration Guidelines Dynamic supports Down and Static supports Up.

Relationship with Other Parameters The following table provides the relationship between the queried values of Competitive Working Status, Local Working Status, and Remote Working Status.

Issue 03 (2013-02-20)

Local Working Status

Remote Working Status


Non-Up

Non-Up

Down

Non-Up

Up

Down

Up

Non-Up

Down

Up

Up

Up


680



A.8.6 Associate AC State Description The Associate AC State parameter specifies whether to detect the working status of a pseudo wire (PW) user-network interface (UNI) port (namely, checking whether a fault occurs on a service PW).

Impact on the System If this parameter is set to Enabled, the equipment can detect the working status of a PW UNI port. If a fault on a service PW is detected, the opposite NE reports the MPLS_PW_FDI alarm.

Values Value Range

Default Value

Enabled, Disabled

Disabled


Description

Enabled

Indicates that the equipment can detect the working status of a PW UNI port. If a fault on a service PW is detected, the opposite NE reports the MPLS_PW_FDI alarm.

Disabled

Indicates that the equipment does not detect the working status of a PW UNI port.

Configuration Guidelines When checking whether a fault occurs on a service PW, set this parameter to Enabled.

Relationship with Other Parameters This parameter is available only when the protection type is set to PW APS.


A.8.7 Max.Concatenated Cell Count Description The Max.Concatenated Cell Count parameter specifies the maximum number of concatenated asynchronous transfer mode (ATM) cells. Issue 03 (2013-02-20)


681




Values Value Range

Default Value

1-31

10

Configuration Guidelines If Max.Concatenated Cell Count is set to 1, the concatenation function is disabled.

Relationship with Other Parameters Before changing the settings of PW-related parameters, ensure that the PW is not bound with any services. After changing the settings of PW-related parameters, bind the PW with services before checking whether this parameter is successfully set.

A.9 PW APS Protection Associated Parameters (Packet Mode) This topic describes the parameters for configuring PW APS protection.

A.9.1 Protection Mode Description The Protection Mode parameter specifies the protection type of a PW APS protection group.


Values Value Range

Default Value

1+1, 1:1

1+1


Issue 03 (2013-02-20)


682



Value

Description

1+1

The service is dually transmitted to the working and protection channels at the transmit end and selectively received at the receive end.

1:1

The service is transmitted to the working or protection channel and is received from the working or protection channel based on the status of the protection group.

Configuration Guidelines When you create a protection group in 1:1 protection mode, the protection channel cannot be configured with extra services. For this reason, the actual applications of 1+1 and 1:1 protection groups are the same, except for the configuration.


A.9.2 Protection Mode Description The Protection Mode parameter specifies a protection scheme of services transmitted on pseudo wires (PWs) based on the service network.


Values Value Range

Default Value

PW APS, Slave Protection Pair, Unprotected

No Protection


Issue 03 (2013-02-20)

Value

Description

PW APS

Indicates a network protection mechanism. If the working PW is faulty, services are automatically switched from the working PW to the protection PW.


683



Value

Description

Slave Protection Pair

Adds a slave PW automatic protection switching (APS) protection pair to the existing PW APS protection group for increase of operation, administration and maintenance (OAM) resource utilization if the PW that has the same source and sink needs to be configured with protection.

Unprotected

Indicates that no protection is available for services.

Configuration Guidelines Set this parameter according to the service network. For example: l

For an NE, set this parameter to PW APS.

l

If the working and protection PWs that transmit the existing services on an NE have the same source and sink, set this parameter to Slave Protection Pair.

l

If services do not need to be protected, set this parameter to No Protection.



A.9.3 Switchover Status Description The Switchover Status parameter specifies the current status of a protection group. If protection switching occurs, this parameter also shows the switching causes.


Issue 03 (2013-02-20)


684



Values Value Range

Default Value

Working in working tunnel, Working in protection tunnel, The current status is forcibly locked, Forcibly switching status and working in the protection tunnel, Invalid working tunnel\(because the OAM generates an SF alarm), Invalid protection tunnel\(because the OAM generates an SF alarm), Invalid working tunnel\(because the OAM generates an SD alarm), Invalid protection tunnel\(because the OAM generates an SD alarm), This status is displayed while manually switching to the working tunnel, This status is displayed while manually switching to the protection channel, In restoration mode, the working tunnel does not work and switches to the protection tunnel. Then, the working tunnel works and services automatically switch to the working tunnel. Before WTR reaches, this status remains, The switching is not required, This status is nearly displayed while practising switching, This status is displayed while practising switching, This status is remotely displayed while practising switching.

-


Issue 03 (2013-02-20)

Value

Description

Working in working tunnel

No switching request is received. Services are transmitted on the working tunnel, and the protection tunnel is in standby state.

Working in protection tunnel

No switching request is received. Services are transmitted on the protection tunnel, and the working tunnel is in standby state.

The current status is forcibly locked

Services are transmitted on the working tunnel all the time, and the protection tunnel is in standby state.

Forcibly switching status and working in the protection tunnel

Services are forcibly switched from the working tunnel to the protection tunnel. The working tunnel remains in standby state regardless of whether the protection tunnel is available or not.

Invalid working tunnel\ (because the OAM generates an SF alarm)

The OAM function detects an SF alarm on the working tunnel, indicating that the working tunnel fails. Services are transmitted on the protection tunnel, and the working tunnel is in standby state.

Invalid protection tunnel\(because the OAM generates an SF alarm)

The OAM function detects an SF alarm on the protection tunnel, indicating that the protection tunnel fails. Services are transmitted on the working tunnel, and the protection tunnel is in standby state.

Invalid working tunnel\ (because the OAM generates an SD alarm)

The OAM function detects an SD alarm on the working tunnel, indicating that signal degrade occurs. Services are transmitted on the working tunnel, and the protection tunnel is in standby state.


685


Issue 03 (2013-02-20)


Value

Description

Invalid protection tunnel\(because the OAM generates an SD alarm)

The OAM function detects an SD alarm on the protection tunnel, indicating that signal degrade occurs. Services are transmitted on the protection tunnel, and the working tunnel is in standby state.

This status is displayed while manually switching to the working tunnel

Services are manually switched from the protection tunnel to the working tunnel.

This status is displayed while manually switching to the protection channel

Services are manually switched from the working tunnel to the protection tunnel.

In restoration mode, the working tunnel does not work and switches to the protection tunnel. Then, the working tunnel works and services automatically switch to the working tunnel. Before WTR reaches, this status remains. The switching is not required.

If APS protection is in revertive mode, before being switched from the protection tunnel to the working tunnel, services are in waiting status within the WTR time after the fault on the working tunnel is rectified. The services are currently transmitted on the protection tunnel, and the working tunnel is in standby state.

The switching is not required

If APS protection is in non-revertive mode, services are not switched from the protection tunnel to the working tunnel after the fault on the working tunnel is rectified. The services are currently transmitted on the protection tunnel, and the working tunnel is in standby state.

This status is nearly displayed while practising switching.

The system simulates the condition for triggering a switching action, but does not issue a command to trigger a real switching action. Practicing switching tests APS protection performance of MPLS PWs without interrupting services. The services are currently transmitted on the working tunnel, and the protection tunnel is in standby state.

This status is displayed while practising switching.

The system simulates the condition for triggering a switching action, but does not issue a command to trigger a real switching action. Practicing switching tests APS protection performance of MPLS PWs without interrupting services. The services are currently transmitted on the protection tunnel, and the working tunnel is in standby state.

This status is remotely displayed while practising switching.

A reverse request for protection switching is received. Services are currently transmitted on the working tunnel, and the protection tunnel is in standby state.


686



Value

Description

This status is remotely displayed while practising switching.

A reverse request for protection switching is received. Services are currently transmitted on the protection tunnel, and the working tunnel is in standby state.

Configuration Guidelines Protection switching is triggered when any of the following conditions is met: SF, external switching commands, and WTR expiry.


A.9.4 Protocol Status Description The Protocol Status parameter specifies whether the APS protocol of the current protection group is enabled.


Values Value Range

Default Value

Disabled, Enabled

Disabled


Description

Disabled

Indicates that the APS protocol is disabled.

Enabled

Indicates that the APS protocol is enabled.

Configuration Guidelines If the APS protocol of the local NE is Enabled before the APS protocol of the opposite NE is Enabled, an exception may occur when the opposite NE receives the services. It is recommended that the APS protocol be enabled after the MPLS APS protection group is configured for both ends. When you configure the MPLS APS protection, the default protocol status is Disabled. Issue 03 (2013-02-20)


687




A.9.5 PW Type Description The PW Type parameter is used for identifying the type of a service transmitted over a PW. A PW can transmit multiple types of services.


Values Value Range

Default Value

Ethernet, Ethernet Tag Mode, SATop, CESoPSN

Ethernet


Description

Ethernet

This item is used when an Ethernet service is created. No S_VLAN tag is added to the service packets.

Ethernet Tag Mode

This item is used when an Ethernet service is created. S_VLAN tags are added to the service packets.

SATop

This item is used when a CES service is created. It stands for StructureAgnostic TDM over Packet. In SAToP mode, the equipment does not sense any format in the TDM signals. Instead, it regards TDM signals as bit flows at a constant rate, and therefore the entire bandwidth of TDM signals is emulated. The overheads and payloads in TDM signals are transparently transmitted.

CESoPSN

This item is used when a CES service is created. It stands for Structureaware TDM Circuit Emulation Service over Packet Switched Network. In CESoPSN mode, the equipment senses the frame structures, frame alignment modes, and timeslots in the TDM circuits. The equipment processes the overheads in and extracts the payloads from the TDM frames. Then, the equipment loads timeslots to these payloads in a specific sequence. As a result, the services in each timeslot are fixed and visible in packets.

Configuration Guidelines When creating a PW, select the PW type based on the type of the service bound with the PW. Issue 03 (2013-02-20)


688




A.10 HQoS Associated Parameters This topic describes the parameters that are used for enabling the HQoS function.

A.10.1 Traffic Classification Rule(Policy Management) 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, 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 traffic classification rules) [Match Type : Match Value : Wilcard] & [Match Type : Match Value : Wilcard] &...& [Match Type : Match Value : Wilcard] Or Logical Relation Between Matched Rules: (the matched packets should meet one of the traffic classification rule) [Match Type : Match Value : Wilcard] | [Match Type : Match Value : Wilcard] |...| [Match Type : Match Value : Wilcard]

Configuration Guidelines 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) can contain a maximum of 128 bytes.


Related Information Currently, the equipment cannot identify the IPv6 packets. Issue 03 (2013-02-20)


689



For details on how to set this parameter, see the description of the Match Type, Match Value, Wilcard, and Logical Relation Between Matched Rules parameters.

A.10.2 Match Type(Policy Management) Description Each data packet has many feature values such as the IP address, MAC address, and port number. These feature values can be considered as match types among the traffic classification rules.


Values Value Range

Default Value

Source IP, Destination IP, Source MAC Address, Destination MAC Address, Protocol Type, Source Port, Destination Port, ICMP Packet Type, DSCP Value, IPPrecedence Value, CVlan ID, CVlan priority, SVlan ID, SVlan priority, DEI

-


Description

Source IP

The source IP address is matched. The traffic classification rule that the source IP address matches is in the format 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 is in the format of [Destination IP : Destination IP Value : Wilcard]. For example, [Destination IP : 192.168.1.2 : 0.0.0.0].

Source MAC Address

The source MAC address is matched. The traffic classification rule that the source MAC address matches is in 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].

Issue 03 (2013-02-20)


690


Value

Description

Destination MAC Address

The destination MAC address is matched.


The traffic classification rule that the destination MAC address matches is in the format of [Destination MAC Address : Destination MAC Address Value : Wilcard]. For example, [Destination MAC Address : 00-e0-fc-54-ab-59 : 00-00-00-00-00-00]. The protocol type is matched.

Protocol Type

The traffic classification rule that the protocol type matches is in the format 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 and UDP). The traffic classification rule that the source port matches is in the format of [Source Port : Source Port Value : Wilcard]. For example, [Source Port : 23 : 23].

Destination Port

The destination port is matched (available when the protocol type is TCP and UDP). The traffic classification rule that the destination port matches is in the format of [Destination Port : Destination Port Value : Wilcard]. For example, [Destination Port : 80 : 80].

ICMP Packet Type

The ICMP packet type is matched (available when the protocol type is ICMP). The traffic classification type that the ICMP packet type matches is in the 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 the format of [DSCP Value : Value of DSCP : Wilcard]. For example, [DSCP Value : 7 : 7].

IP-Precedence Value

The IP-Precedence Value is matched. The traffic classification rule that the IP-precedence value matches is in the 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 format of [CVlan ID : CVlan ID Value : Wilcard]. For example, [CVlan ID : 100 : 120].

Issue 03 (2013-02-20)


691


Value

Description

CVlan priority

The CVlan priority is matched.


The traffic classification rule that the CVlan priority matches is in the format 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 format of [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 the format 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 Guidelines To process different service packets accordingly (make ACL for packets, apply different scheduling priorities or discard polices), perform traffic classification for the packets according to the varied feature values of packets. The feature value that can distinguish the packets according to requirements is adopted to classify the packets. For example, user A and user B access to a port. The network should provide services of different QoS for the two users. Hence, the packets of user A and user B should be distinguished at 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.0 and 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.0 and 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 source IP 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]



692



Related Information For the setting of this parameter, see the description of the Traffic Classification Rule, Match Value, Wilcard, and Logical Relation Between Matched Rules parameters.

A.10.3 Match Value(Policy Management) Description The Match Value parameter indicates the value set for a specific match type among the traffic classification rules. If certain bits of the match type value (source IP address, for example) are consistent with the mapping bits of the match value of the traffic classification rule, the packets match with the traffic classification rule.


Values Value Range

Default Value

Source IP, Destination IP, Source MAC Address, Destination MAC Address, Protocol Type, Source Port, Destination Port, ICMP Packet Type, DSCP Value, IPPrecedence Value, CVlan ID, CVlan priority, SVlan ID, SVlan priority, DEI

-


Description

Source IP

Indicates the source IP value when the source IP address matches the traffic classification rule. For example, 192.168.1.1

Destination IP

Indicates the destination IP value when the destination IP address matches the traffic classification rule. For example, 192.168.2.1

Source MAC Address

Indicates the source MAC address value when the source MAC address matches the traffic classification rule. For example, 00-0f-ef-54-aa-00


Indicates the destination MAC address value when the destination MAC address matches the traffic classification rule. For example, 00-0f-ef-54-ab-00

Issue 03 (2013-02-20)


693



Value

Description

Protocol Type

Indicates the protocol type value when the protocol type matches the traffic classification rule. Protocol type range: tcp, udp, icmp, igmp

Source Port

Indicates the source port value when the source port (available when the protocol type is TCP and UDP) matches the traffic classification rule. 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 the traffic classification rule. The destination port value ranges from 0 to 65535.

ICMP Packet Type

Indicates the ICMP packet type value when the ICMP packet type (available whether protocol type is ICMP) matches the traffic classification rule. Value range of ICMP packet type: echo echo-reply fragmentneed-DFset host-redirect host-tos-redirect host-unreachable information-reply information-request net-redirect net-tos-redirect net-unreachable parameter-problem port-unreachable protocol-unreachable reassembly-timeout source-quench source-route-failed timestamp-reply timestamp-request ttl-exceeded

DSCP Value

Indicates the value of DSCP when the DSCP value matches the traffic classification value. The DSCP value ranges from 0 to 63.

Issue 03 (2013-02-20)


694



Value

Description

IP-Precedence Value

Indicates the value of IP-Precedence when the IP-Precedence value matches 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 the traffic classification value. The CVlan ID value ranges from 0 to 4095.

CVlan priority

Indicates the value of CVlan priority when the CVlan priority matches 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 the traffic classification value. The SVlan ID vale ranges from 0 to 4095.

SVlan priority

Indicates the value of SVlan priority when the SVlan priority matches the traffic classification value. The SVlan priority value ranges from 0 to 7.

DEI

Indicates the value of DEI when the DEI matches the traffic classification value. The DEI value can be 0 or 1.

Configuration Guidelines The match value of each match type should be within the valid range.


Related Information For details on how to set this parameter, see the description of the Traffic Classification Rule, Match Type, Wilcard, and Logical Relation Between Matched Rules parameters.

A.10.4 Wildcard(Policy Management) Description The Wildcard parameter indicates that the packets need match only a portion of the match values. The number of digits of the wildcard is consistent with the number of digits of the match value. After the wildcard is converted to the binary format, digit 0 in the match value should be matched, but digit 1 need not be considered. In the user packets, if the value of the digit in the Match Type that the user need consider is equal to the value of the corresponding digit in the match value. In this case, the user packets match the flow classification rule. Otherwise, the user packets do not match the flow classification rule. Issue 03 (2013-02-20)


695



When the wildcard is set to all "0"s, it indicates that the packets should strictly match the match value. NOTE

The digits of the wildcard, user packet match type value, and match type value indicate the digits after the values of the wildcard, user packet match type value, and match type are converted to the binary format.

The following example helps you understand the parameter. l

If the Match Type is Source IP, the match value is 192.168.1.100. In this case, if the wildcard is 0.0.0.255, it indicates that all the packets whose source IP address starting from 192.168.1. comply with the flow classification rule.

l

If the Match Type is CVLAN Priority, the match value is 7 (the corresponding binary value is 111). In this case, if the wildcard is 6 (the corresponding binary value is 110), it indicates that the packets whose CVLAN priorities are 7, 5, 3, and 1 (the corresponding binary values are 111, 101, 011, and 001) comply with the flow classification rule.


Values Value Range

Default Value

Source IP, Destination IP, Source MAC Address, Destination MAC Address, Protocol Type, Source Port, Destination Port, ICMP Packet Type, DSCP Value, IPPrecedence Value, CVLAN ID, CVLAN Priority, SVLAN ID, SVLAN Priority, DEI

-

The following table lists descriptions 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 address matches. For example, 0.0.255.255.

Source MAC Address

Indicates the wildcard value when the source MAC address matches. For example, 00-00-00-00-00-ff.


Indicates the wildcard value when the destination MAC address matches. For example, 00-00-00-00-0f-ff.

Protocol Type Issue 03 (2013-02-20)

Indicates no wildcard. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

696



Match Type

Description

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 value matches. 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 Guidelines The wildcard value of each match type should be within its own valid range. When the wildcard is set to all "0"s, it indicates that the packets should strictly match the match value.


Related Information For details on how to set this parameter, see the description of the Traffic Classification Rule, Match Type, Match Value, and Logical Relation Between Matched Rules parameters.

Issue 03 (2013-02-20)


697



A.10.5 PW Direction(PW Policy) Description In the case of one PW, two directions, that is, the direction of entering the network and the direction of exiting the network, are available. The PW Direction parameter indicates whether the PW processes one direction or two directions.

Impact on the System If the PW is set to unidirectional, the PW processes the packets in only one direction. If the user services are bidirectional, the packets in another direction cannot be processed.

Values Value Range

Default Value

Bidirectional, Unidirectional

-


Description

Bidirectional

The PW processes packets in two directions, that is, the directions of entering and exiting the network.

Unidirectional

The PW processes packets that only enter or only exit the network.

Configuration Guidelines If the PW need to process packets in two directions, that is, the directions of entering and exiting the network, the value should be set to bidirectional. Otherwise, the value should be set to unidirectional. Generally, in the case of the broadcast PW, the value should be set to unidirectional. In the case of unicast PW, the value should be set to bidirectional.

A.10.6 Direction (PW Policy) Description The Direction (PW Policy) parameter indicates the direction for the policy application.


Issue 03 (2013-02-20)


698



Values Value Range

Default Value

Ingress, Egress

-


Description

Ingress

Indicates that the policy application direction is uplink, that is, from the UNI to the NNI.

Egress

Indicates that the policy application direction is downlink, that is, from the NNI to the UNI.


A.10.7 Duplicated Policy Name(PW Policy) Description The Duplicated Policy Name (PW Policy) parameter has the same meaning as the Policy Name parameter and indicates the policy based on which a new policy is created.

Impact on the System You can apply a specified policy to the original policy. As a result, the service scheduling policy of the original policy is changed by duplicating the service scheduling policy of the specified policy.

Values The Duplicated Policy Name parameter should contain letters or numbers or both with a maximum length of 64 characters. The characters \ or / are not contained.

Configuration Guidelines For changing the current policy, you can directly duplicate the existed policy that satisfies the requirement to the current policy. In this case, no extra setting is required for the current policy.

A.10.8 Policy ID(Policy Management) Description The Policy ID (Policy Management) parameter identifies a policy. Issue 03 (2013-02-20)


699




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

QinQ policy

0-2000

WFQ scheduling policy

0-256

Port WRED policy

0-7

Service WRED policy

0-127

Configuration Guidelines The IDs of policies of different types can be repeated, whereas the IDs of policies of the same type must be unique.

A.10.9 Policy Name (Policy Management) Description The Policy Name (Policy Management) parameter specifies the name of a policy and thus identifies a policy. Different policies can have the same policy name.


Values The policy name should contain letters or numbers or both with a maximum length of 64 characters. The characters \ or / are not supported.

Configuration Guidelines Different policies can have the same policy name.

Issue 03 (2013-02-20)


700



A.10.10 QinQ Link ID(QinQ Policy) Description The QinQ Link ID parameter indicates the unique identifier of a QinQ link.


Values Value Range

Default Value

1-4294967295

-

Configuration Guidelines The QinQ Link ID parameter identifies a unique QinQ link. Hence, do not set the same ID for different QinQ links.

A.10.11 Physical Port ID(QinQ Policy) Description The Physical Port ID parameter identifies the physical port that applies the QinQ policy.


Values Slot number - board name - port number (PORT - number).


A.10.12 S-VLAN ID(QinQ Policy) Description The S-VLAN ID parameter is a 12-bit field, indicating the VLAN ID. If a switch supports the 802.1Q protocol, all packets it transmitting contain this 12-bit field. In this case, a packet is identified by its own VLAN. Issue 03 (2013-02-20)


701




Values Value Range

Default Value

1-4094

-

Configuration Guidelines When creating the QinQ, you should define the port and S-LVAN ID. The port and S-LAN ID cannot be occupied by other services. Moreover, the S-LVAN ID must be set within the valid range.

A.10.13 Traffic Classification Bandwidth Sharing(Policy Management) Description Set the Traffic Classification Bandwidth Sharing parameter to enable or disable the traffic classification bandwidth sharing. Flow Classification of V-UNI Ingress Policy includes the preset Committed Information Rate. When packets on multiple V-UNIs that use this policy match this Flow Classification, if Traffic Classification Bandwidth Sharing is enabled, the total bandwidth of these flows is restrained by the CIR set by Flow Classification. If Traffic Classification Bandwidth Sharing is disabled, on each V-UNI, the flows that match Flow Classification are restrained by the CIR set by Flow Classification.


Values Value Range

Default Value

Enabled, Disabled

Disabled


Issue 03 (2013-02-20)

Value

Description

Disabled

It indicates that the traffic classification bandwidth sharing is disabled. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

702



Value

Description

Enabled

It indicates that the traffic classification bandwidth sharing is enabled.

Configuration Guidelines This parameter is set according to service requirements. For example, packets on multiple V-UNIs that use a certain V-UNI Ingress Policy match Flow Classification of this policy. In addition, the service packets of these flows have the same service features, such as the same destination IP address. In this case, if these service packets need share the CIR bandwidth set in Flow Classification of this policy, set Traffic Classification Bandwidth Sharing to Enabled.

Relationship with Other Parameters When configuring Flow Classification of V-UNI Ingress Policy, set Bandwidth Limit to Enabled. In addition, the CIR of Flow Classification should be configured. In this case, Traffic Classification Bandwidth Sharing is valid.

Related Information For the setting of this parameter, see Traffic Classification Rule.

A.10.14 Coloring Mode (V-UNI Ingress Policy) Description The Coloring Mode (V-UNI Ingress Policy) parameter specifies the coloring mode of a certain flow. Therefore, this parameter specifies whether the original color of the packets in this flow is considered when the CAR processing is performed on these packets.


Values Value Range

Default Value

Color-Blind, Chromatic-Sensitive

Color-Blind


Issue 03 (2013-02-20)


703



Value

Description

Color-Blind

Indicates the color blindness mode. The CAR is directly performed for the user packets, which are marked according to the CAR result.

Chromatic-Sensitive

Indicates the color sensitive mode. In this mode, the original color of the packet is considered when the CAR processing is performed. Hence, the green packet is marked green and the red packet is marked red as preference. In addition, after the CAR processing is performed, the result is compared with the original color of the packet and then the packet is marked with the darker color. The darkness of packet colors in a descending order is as follows: red, yellow, and green.

Configuration Guidelines After the upstream DS domain marks the service packets accessed into the local DS domain, on the ingress node of the local DS domain, if the coloration result of the upstream DS domain need be considered, Chromatic-Sensitive is applicable to the Traffic Classification that matches the service packets. Otherwise, Color-Blind is applicable.

Relationship with Other Parameters When the service packets from the upstream DS domain enter the ingress node of the local DS domain, the color of packets is obtained according to the mapping relation between the packet priority and color, which is defined in the local DS domain mapping relation. If Coloring Mode is set to Chromatic-Sensitive, the color of service packets from the upstream DS domain should be restored. Ensure that the mapping relations of the service packets in the upstream DS domain and local DS domain are consistent.

A.10.15 Logical Relation Between Matched Rules(V-UNI Ingress Policy) Description When multiple traffic classification rules are set for a flow, set the Logical Relation Between Matched Rules parameter to specify the logical relations among these traffic classification rules.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

And, Or

And


704




Description

And

The packet matches the flow only when the packet matches each traffic classification rule.

Or

The packet matches the flow when the packet matches one of the traffic classification rules.


Relationship with Other Parameters Before setting the Logical Relation Between Matched Rules parameter, set the Traffic Classification Rule correctly.

A.10.16 Processing Mode(V-UNI Ingress Policy) Description The Processing Mode parameter indicates the processing mode for packets of different colors.


Values Value Range

Default Value

Pass, Discard, Remark

l Green, yellow: Pass l Red: Discard


Issue 03 (2013-02-20)

Value

Description

Pass

Indicates transparently transmitting or directly forwarding the packet.

Discard

Indicates discarding the packet.

Remark

Indicates remarking the packet with a different color.


705



Configuration Guidelines When a network congestion occurs or the color of the packet needs adjusting, packets of different colors can be configured with different processing modes.

A.10.17 AF1 Schedule Weight(%)(WFQ Schedule Policy) Description The QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule the CS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queues according to the weights of the queues > schedule the BE queue. The AF1 Schedule Weight parameter indicates the percentage of the AF1 queue to the weight when the AF1-AF4 queues are scheduled according to the weight.


Values Value Range

Default Value

Unit

1-100

25

%

Configuration Guidelines The bigger the value of the AF1 scheduling weight, the higher is scheduling priority of the AF1 queue. 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 the AF1 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is bigger.

Relationship with Other Parameters The sum of values of AF1, AF2, AF3, and AF4 scheduling weights cannot exceed 100.




706



Values Value Range

Default Value

Unit

1-100

25

%

Configuration Guidelines The bigger the value of the AF2 scheduling weight, the higher is the scheduling priority of the AF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller. Reversely, the smaller the value of the AF2 scheduling weight, the lower is the scheduling priority of the AF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is bigger.

Relationship with Other Parameters The sum of values of the AF2, AF1, AF3, and AF4 scheduling weights cannot exceed 100.



Values Value Range

Default Value

Unit

1-100

25

%


Relationship with Other Parameters The sum of values of the AF3, AF1, AF2, and AF4 scheduling weights cannot exceed 100. Issue 03 (2013-02-20)


707





Values Value Range

Default Value

Unit

1-100

25

%


Relationship with Other Parameters The sum of values of the AF4, AF1, AF2, and AF3 scheduling weights cannot exceed 100.

A.10.21 Discard Lower Threshold (256 bytes) (Service WRED Policy) Description Users can set Discard Lower Threshold and Discard Upper Threshold for a queue. When the length of a queue is less than the specified value of Discard Lower Threshold, the packet is not discarded. When the length of a queue is within the range from the specified value of Discard Lower Threshold to the specified value of Discard Upper Threshold, the weighted random early detection (WRED) mechanism discards packets at random. When the length of a queue is more than the specified value of Discard Upper Threshold, the packet is discarded according to the discard probability that is set by the user.



708



Values Value Range

Default Value

Unit

0-4095

l Red: 1024

256 bytes

l Yellow: 1536 l Green: 2048

Configuration Guidelines When the value of Discard Lower Threshold is smaller, the length of a queue is shorter. The value of Discard Lower Threshold must not be more than the value of Discard Upper Threshold.


A.10.22 Discard Upper Threshold (256 bytes) (Service WRED Policy) Description Users can set Discard Lower Threshold and Discard Upper Threshold for a queue. When the length of a queue is less than the specified value of Discard Lower Threshold, the packet is not discarded. When the length of a queue is within the range from the specified value of Discard Lower Threshold to the specified value of Discard Upper Threshold, the weighted random early detection (WRED) mechanism discards packets at random. When the length of a queue is more than the specified value of Discard Upper Threshold, the packet is discarded according to the discard probability that is set by the user.

Impact on the System If Discard Upper Threshold is set to 0, all the packets in this queue are discarded and thus all the services of this queue are interrupted.

Values Value Range

Default Value

Unit

0-4095

l Red: 3072

256 bytes

l Yellow: 3584 l Green: 4095

Configuration Guidelines The value of Discard Upper Threshold cannot be less than the value of Discard Lower Threshold. Issue 03 (2013-02-20)


709




A.10.23 Discard Probability (%) (Service WRED Policy) Description The Discard Probability (%) (Service WRED Policy) parameter specifies the ratio of the packets that are discarded to the total number of packets in a queue when the length of a queue is more than the specified value of Discard Upper Threshold.


Values Value Range

Default Value

Unit

1-100

100

%

Configuration Guidelines The maximum discard probability can be 100%, which indicates that all the packets in a queue are discarded when the length of the queue is more than the specified value of Discard Upper Threshold.

A.10.24 PHB (Diffserv domain Management) 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 DiffServ domain.


Issue 03 (2013-02-20)


710



Values Value Range

Default Value

BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF, CS6, CS7

The CoS defines different service classes: l CS6-CS7: Highest service classes applicable to transport of the signaling. l EF: Fast forwarding, applicable to the service traffic with the shortest delay and low packet loss ratio, such as the audio service and video service. l AF1-AF4: Applicable to the service traffic that requires a certain rate, but not a certain delay or jitter. l BE: Applicable to the service traffic that does not require special processing.

Configuration Guidelines When the equipment in different DS domains is interconnected, the mapping relationship in the egress direction needs to be configured so that the CoS information can be mapped into the priority bit of the packet.


A.10.25 Packet Type (Diffserv domain Management) Description The Packet Type is used to set the packet type.


Values Value Range

Default Value

cvlan, svlan, mpls-exp, ip-dscp

-



711



Value

Description

cvlan

Specifies the priority information of the C-VLAN packet.

svlan

Specifies the priority information of the S-VLAN packet. When the DEI is disabled, the CoS mapping is performed only according to the priority of the S-VLAN packet. When the DEI is enabled, the DEI bit also indicates the priority. That is, four bits of a packet indicate the priority.

ip-dscp

Specifies the DSCP domain of the IP packet.

mpls-exp

Specifies the EXP information of the MPLS packet.

Configuration Guidelines The value setting depends on the packet type.

A.10.26 Committed Information Rate (Kbit/s) Description The Committed Information Rate (Kbit/s) parameter specifies the CIR of the queue. The packets whose rates are less than the CIR can be forwarded. When the rate of the packets is not more than the CIR, all messages can be forwarded. If the rate of the packets is more than the CIR, some packets are discarded according to a certain packet discarding policy.


Values Value Range

Default Value

Unit

1024-10000000, Unlimited

4294967295 (FFFFFFFFFF is invalid)

kbit/s

Configuration Guidelines The greater CIR, the higher rate of the traffic, and the more packets forwarded. It is recommended that the rate of the packets is not more than the CIR.

Relationship with Other Parameters The CIR is not more than the PIR in each queue. The CIR equals to the PIR in CS7, CS6, and EF queues. Issue 03 (2013-02-20)


712



If the policy is applied to function points, such as PW, port, VUNI, and QINQ, you need to ensure that the sum of the CIRs in the policies applied to the function point is not more than the CIR of the function point.

A.10.27 Committed Burst Size (byte) Description The Committed Burst Size (byte) parameter specifies the committed burst size. When the bandwidth is insufficient, some packets cannot be forwarded. Therefore, a buffer is required to store these packets for forwarding when the bandwidth is sufficient. CBS is the size of the buffer. When the size of the stored packets is less than the CBS, all these packets can be forwarded.


Values Value Range

Default Value

Unit

64-10000000


byte

Configuration Guidelines If the CBS is small, the buffer easily overflows and some packets are discarded when the bandwidth is insufficient. The greater the CBS is, the more packets can be buffered when the bandwidth is insufficient, and the less the packet loss ratio is. The greater the CBS, the more serious the delay jitter when packets are forwarded. For the OptiX OSN equipment, the CBS is reserved and cannot be set.


A.10.28 Peak Information Rate (kbit/s) Description The Peak Information Rate (kbit/s) parameter specifies the maximum rate of services allowed by the PIR.



713



Values Value Range

Default Value

Unit

64-10000000


(kbit/s)

Configuration Guidelines It is recommended that the PIR be not less than the CIR. For the OptiX OSN equipment, the CBS is reserved and cannot be set.


A.10.29 Peak Burst Size (byte) Description The Peak Burst Size (byte) parameter specifies the size of the PBS. When the bandwidth is insufficient and the CBS buffer is full, the packets that cannot be stored in the CBS buffer are stored in the PBS buffer. When the PBS buffer is full, the extra packets are discarded. The packets stored in the PBS buffer may also fail to be forwarded. The packets whose rates are more than the CIR and less than the PIR attempt to preempt the remaining bandwidth. The packets are forwarded only when they preempt the remaining bandwidth.


Values Value Range

Default Value

Unit

64-10000000


byte

Configuration Guidelines Although the packets in the PBS buffer may also fail to be forwarded, the PBS buffer decreases the packet loss ratio. The greater the PBS, the less the packet loss ratio, and the more serious the delay jitter when packets are forwarded. For the OptiX OSN equipment, the CBS is reserved and cannot be set. Issue 03 (2013-02-20)


714




A.10.30 EXP Description The EXP parameter specifies the field in the MPLS packets for identifying the priority of these MPLS packets. E-LSP is used to set the EXP. 77 is the highest priority.


Values Value Range

Default Value

0, 1, 2, 3, 4, 5, 6, 7, None

None


Issue 03 (2013-02-20)

Value

Description

0

The values 0-7 correspond to the eight levels of the CoS policy. The value 0 corresponds to BE.

1

The values 0-7 correspond to the eight levels of the CoS policy. The value 1 corresponds to AF1.

2


3


4


5

The values 0-7 correspond to the eight levels of the CoS policy. The value 5 corresponds to EF.

6

The values 0-7 correspond to the eight levels of the CoS policy. The value 6 corresponds to CS6.

7

The values 0-7 correspond to the eight levels of the CoS policy. The value 7 corresponds to CS7.


715



Configuration Guidelines The higher the value of the EXP parameter, the higher the priority of the packets.


A.10.31 LSP Mode Description The LSP Mode parameter specifies the mode in which the MPLS network processes packet priorities. When a label is allocated to a PW, the CoS policy of the packets may be changed. Therefore, it is necessary to determine whether the CoS policy of the packets needs to be restored when the PW label is stripped from the packets. The LSP Mode parameter specifies whether the CoS policy of the packets needs to be restored.


Values Value Range

Default Value

Pipe, Uniform

Uniform


Description

Pipe

Indicates that the CoS policy of the packets need not to be restored when the tunnel labels are peeled off.

Uniform

Indicates that the CoS policy of the packets need to be restored when the tunnel labels are peeled off.




716



A.11 QoS Associated Parameters This topic describes the parameters for configuring the QoS function

A.11.1 Flow Type (Flow Configuration) Description The Flow Type(Flow Configuration) parameter specifies Flow Type of the flow in the Ethernet data board. This parameter decides the method of binding the service with the flow.

Impact on the System If the Flow Type parameter is set incorrectly, that is, the flow classification method is incorrect, the (Bound CAR or Bound CoS) parameter may fail to meet the expected result. For the effects of CAR and CoS, refer to the relevant description.

Values Board Name

Value Range

Default Value

N1EMS4, N1EGS4, N3EGS4

l Port Flow

Port Flow

l Port+VLAN Flow l Port+SVLAN Flow

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N2EMR0, N2EGR2

l Port Flow

N1EFS0A, N1EMS2, N4EGS4

l Port Flow

Port Flow

l Port+VLAN Flow l Port+VLAN+Priority Port Flow

l Port+VLAN Flow l Port+VLAN+Priority l Port+SVLAN Flow

N1EAS2

l Port Flow

Port Flow

l Port+VLAN Flow l Port+SVLAN Flow l Port+CVLAN+SVLAN Flow


Issue 03 (2013-02-20)

Value

Description

Port Flow

All the packets entering the specified port are regarded as one flow. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

717



Value

Description

Port+VLAN Flow

All the packets that enter the specified port, and whose Tag VID is consistent with the specified VID, are regarded as one flow.

Port+VLAN+Priority

All the packets that enter from the specified port, and whose VLAN Tag VID and priority are consistent with the specified VID and priority, are regarded as one flow.

Port+SVLAN Flow

All the packets that enter from the specified port, and whose SVLAN VID is consistent with the specified VID, are regarded as one flow.

Port+CVLAN+SVLAN Flow

All the packets that enter from the specified port, and whose SVLAN VID and CVLAN VID are consistent with the specified VID, are regarded as one flow.

Configuration Guidelines Based on the required QoS and service type, set a proper value for Flow Type.


A.11.2 Bound CAR (Flow Configuration) Description The Bound CAR (Flow Configuration) parameter specifies the method of binding a flow with a CAR ID and querying the CAR ID bound with the flow. One flow can be bound with one CAR ID only. The CAR takes effect only after the flow is bound with the CAR.

Impact on the System The CAR-based flow rate can take effect only after the flow is bound with the enabled CAR policy.

Values Value Range

Default Value

Created CAR ID

-

Configuration Guidelines The created flow can be bound with the created CAR policy only. For this reason, you can select the value from the created CAR ID. Issue 03 (2013-02-20)


718



Relationship with Other Parameters A flow can be bound with the CAR only after the flow and CAR are created.

A.11.3 Bound CoS (Flow Configuration) Description The Bound CoS (Flow Configuration) parameter specifies the method of binding a flow with a CoS ID and querying the CoS ID bound with the flow. A flow can be bound with one CoS ID only. The CoS policy can be used to divide the packet priority after the flow is bound with the CoS.

Impact on the System The flow packets can be divided into different priorities based on the CoS rules only after the flow is bound with the CoS.

Values Value Range

Default Value

Created CoS ID

-

Configuration Guidelines The created flow can be bound with the created CoS policy only. For this reason, you can select the value from the created CoS ID.

Relationship with Other Parameters A flow can be bound with the CoS only after the flow and CoS are created.

A.11.4 CAR ID (CAR Configuration) Description The CAR ID (CAR Configuration) parameter specifies the ID of a committed access rate (CAR). After a CAR is created, it needs to be specified with a CAR ID.


Values The value ranges for each type of board is as follows: Issue 03 (2013-02-20)


719



Board Name

Value Range

Default Value


1-4095

1

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2, N1EAS2, N2EMR0, N2EGR2

1-2048

1

Configuration Guidelines You can set this parameter to any value within the value range as required. Each CAR has a unique CAR ID.


A.11.5 CAR Enabled/Disabled (CAR Configuration) Description The CAR Enabled/Disabled (CAR Configuration) parameter specifies whether a CAR can limit the traffic volume.

Impact on the System After the CAR is enabled and bound with a flow, the traffic volume of the flow is limited depending on the value of the CAR parameter. If the transmitted traffic is greater than the specified value, the excessive traffic is discarded.

Values Valid Value

Default Value

Enabled, Disabled

Disabled


Issue 03 (2013-02-20)

Value

Description

Disabled

A CAR is created, but does not take effect.

Enabled

A CAR is created, and takes effect.


720



Configuration Guidelines You can set this parameter to Enabled or Disabled, depending on whether the CAR is required to limit the traffic volume.

Relationship with Other Parameters A CAR can limit the traffic of a flow only when it is set to Enabled and bound with a flow.

A.11.6 Committed Information Rate (CAR Configuration) Description The Committed Information Rate (CAR Configuration) parameter specifies the committed information rate (CIR) of the committed access rate (CAR). It specifies the minimum guarantee bandwidth of a flow.

Impact on the System After the CAR is enabled and bound with a flow, the committed bandwidth of the flow is guaranteed. If the traffic volume is greater than the guarantee bandwidth, the transmission of excessive traffic cannot be guaranteed.

Values Board Name

Value Range

Default Value

Unit

N1EAS2

An integer of 0-10485760, in step length of 64

0

kbit/s



0

kbit/s



0

kbit/s

Configuration Guidelines Based on the actual QoS requirement, set a proper value for Committed Information Rate. Generally, the value of Committed Information Rate is not less than the expected average rate for transmitting the flow.

Relationship with Other Parameters You can set Committed Information Rate of a CAR only after creating the CAR. Issue 03 (2013-02-20)


721



A.11.7 Committed Burst Size (CAR Configuration) Description The Committed Burst Size (CAR Configuration) parameter specifies the maximum guaranteed data volume of a flow, which can be transmitted within a certain period.

Impact on the System After the CAR is enabled and bound with a flow, if the volume of burst data in the flow is less than the value of Committed Burst Size, the burst data can be guaranteed for transmission. Otherwise, they cannot be guaranteed for transmission.

Values Board Name

Value Range

Default Value

Unit

N1EAS2

0-2048

0

Kbyte

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N1EFS0A, N1EMS2, N2EMR0, N2EGR2

0-128

0

Kbyte


0-32

0

Kbyte

Configuration Guidelines Based on the actual QoS requirements, set a proper value for Committed Burst Size. Generally, the value of Committed Burst Size is not less than the possible size of expected burst data flow to be transmitted.

Relationship with Other Parameters You can set Committed Burst Size of a CAR only after creating the CAR.

A.11.8 Peak Information Rate (CAR Configuration) Description The Peak Information Rate (CAR Configuration) parameter specifies the peak information rate (PIR) of the committed access rate (CAR). It specifies the allowed maximum rate of a flow.

Impact on the System After the CAR is enabled and bound with a flow, the flow rate is limited according to the peak bandwidth of the CAR parameter. Issue 03 (2013-02-20)


722



If the traffic volume is greater than the value of Peak Information Rate, the excessive traffic is discarded.

Values Board Name

Value Range

Default Value

Unit

N1EAS2


0

kbit/s



0

kbit/s



0

kbit/s

Configuration Guidelines Based on the actual QoS requirement, you can set a proper value for Peak Information Rate. The value of Peak Information Rate should not be less than the guarantee bandwidth. Generally, the value of Peak Information Rate is not greater than the expected maximum rate of transmitting the flow.

Relationship with Other Parameters You can set Peak Information Rate for a CAR only after creating the CAR.

A.11.9 Maximum Burst Size (CAR Configuration) Description The Maximum Burst Size (CAR Configuration) parameter specifies the maximum excessive data volume of a flow, which can be transmitted within a certain period.

Impact on the System After the CAR is enabled and bound with a flow, if the burst data volume of the flow is greater than the value of Maximum Burst Size, the excessive data is discarded.

Issue 03 (2013-02-20)


723



Values Board Name

Value Range

Default Value

Unit

N1EAS2

0-2048

0

kbyte


0-32

0

kbyte


0

0

kbyte

Configuration Guidelines Based on the actual requirement of QoS, you can set a proper value for Maximum Burst Size. Generally, the value of Maximum Burst Size is not greater than the size of burst data flow to be transmitted.

Relationship with Other Parameters You can set Maximum Burst Size of a CAR only after creating the CAR.

A.11.10 CoS ID (CoS Configuration) Description The CoS ID (CAR Configuration) parameter specifies the ID of a class of service (CoS). When a CoS is created, it needs to be specified with a unique CoS ID.


Values The value ranges for each type of board is as follows:

Issue 03 (2013-02-20)

Board Name

Value Range

Default Value

N1EAS2, N3EGS2, N1EMS4, N1EGS4, N3EGS4, N4EGS4

1-65535

1

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N1EFS0A, N1EMS2, N2EMR0, N2EGR2

1-8192

1


724



Configuration Guidelines You can set this parameter to any value in the value range as required. A CoS maps a CoS ID.


A.11.11 CoS Type (CoS Configuration) Description The CoS Type (CoS Configuration) parameter specifies the type of CoS of the flow in the Ethernet data board. This parameter decides the method adopted to classify the flow in the Ethernet data board.

Impact on the System If CoS Type is set incorrectly, packets cannot be correctly dispatched to a proper queue.

Values Board Name

Value Range

Default Value

N1EAS2, N2EFS0, N2EGS2

Simple, VLAN priority

Simple

N1EMS4, N1EGS4, N3EGS4, N4EGS4, N5EFS0, N3EFS4, N3EGS2, N2EMR0, N2EGR2, N1EFS0A, N1EMS2, N2EFS4, N4EFS0

Simple, VLAN priority, IPTOS, DSCP

Simple


Issue 03 (2013-02-20)

Value

Description

Simple

Assigns the CoS Priority based on the flow.

VLAN priority

Assigns the CoS Priority based on the VLAN priority.

IPTOS

Assigns the CoS Priority based on the TOS field in the IP packet header.

DSCP

Assigns the CoS Priority based on the DSCP field in the IP packet header.


725



Configuration Guidelines Based on the requirements of QoS, set a proper value for CoS Type.


A.11.12 CoS Priority (CoS Configuration) Description The CoS Priority (CoS Configuration) parameter classifies packets into different levels based on the CoS type, and maps these packets into different CoS priorities. The packets of higher priorities are first processed.

Impact on the System The packets of higher priorities are transmitted before those of lower priorities. Moreover, better service quality is available.

Values For the CoS of the simple type, follow Table A-6 to set a simple CoS Priority. Table A-6 CoS priority of the simple type Data Board

CoS Parameter

Value Range of CoS Parameter

Value Range of CoS Priority

Default Value of CoS Priority

N4EFS0, N2EFS4, N2EGS2, N1EFS0A, N1EMS2, N1EAS2, N3EGS2, N3EGS4, N4EGS4

Invalid

Invalid

0-7

0

N5EFS0, N1EMS4, N1EGS4

Invalid

Invalid

0-3

0

N3EFS4

Invalid

Invalid

0-1

0

N2EMR0, N2EGR2

Invalid

Invalid

A/B/C

C

For the CoS of the VLAN Priority type, follow Table A-7 to set the mapping from VLAN Priority to CoS Priority. Issue 03 (2013-02-20)


726



Table A-7 CoS priority of the VLAN Priority type Data Board

CoS Parameter




N4EFS0, N2EFS4, N2EGS2, N1EFS0A, N1EMS2

User priority in VLAN

0-7

0-7

Value range of the mapping CoS priority: -

N1EAS2


0-7

0-7

The same as that of VLAN priority

N3EGS2


0-7

0-7

0

N5EFS0, N1EMS4, N1EGS4, N3EGS4, N4EGS4


0-7

0-3

0

N3EFS4


0-7

0-1

0

N2EMR0, N2EGR2


0-7

A/B/C

C

For the CoS of the IPTOS type, follow Table A-8 to set the mapping from IPTOS Priority to CoS Priority. Table A-8 CoS priority of the IPTOS type

Issue 03 (2013-02-20)

Data Board

CoS Parameter




N4EFS0, N2EFS4, N2EGS2, N1EFS0A, N1EMS2, N3EGS2

IPTOS

0000-1111 (in binary)

0-7

0


IPTOS

0000-1111 (in binary)

0-3

0


727



Data Board

CoS Parameter




N3EFS4

IPTOS

0000-1111 (in binary)

0-1

0

N2EMR0, N2EGR2

IPTOS

0000-1111 (in binary)

A/B/C

C

For the CoS of the DSCP type, follow Table A-9 to set the mapping from DSCP Priority to CoS Priority. Table A-9 CoS priority of the DSCP type Data Board

CoS Parameter




N4EFS0, N2EFS4, N2EGS2, N1EFS0A, N1EMS2, N3EGS2

DSCP

000000-111111 (in binary)

0-7

0


DSCP

000000-111111 (in binary)

0-3

0

N3EFS4

DSCP

000000-111111 (in binary)

0-1

0

N2EMR0, N2EGR2

DSCP

000000-111111 (in binary)

A/B/C

C

Configuration Guidelines Based on the requirements, you can map the packets into different queues by setting CoS Priority. If CoS Type is set to VLAN Priority, IPTOS or DSCP, generally, you can map the packets into the proper CoS Priority according to the priority information contained in the packets. At the application layer, if a service (for example, VOIP, video conference, video conferencing call, and video on demand) has higher requirements for QoS, set a higher priority for the service to get better bandwidth and service guarantee. To ensure good bandwidth multiplexing, be sure to avoid a larger ratio of real-time services in the network. For a service (for example, Internet access, E-Mail, and FTP) that has lower requirements for QoS, set a lower priority for the service to provide better bandwidth sharing and contention mechanism. Issue 03 (2013-02-20)


728



For the N1EAS2 board, queue 7 has the absolute priority. That is, if queue 7 is congested, all the queues must wait. Generally, queue 7 is used for the protocol or management packets of light traffic. The remaining bandwidth is allocated in proportion for other queues. Queue 0 has the lowest priority. For a higher priority, no bandwidth is used if no service is available.


A.11.13 Shaping Description Shaping indicates the flow shaping function of all the four queues of every port on the N1EMS4, N1EGS4, N3EGS4. or N4EGS4. This parameter includes the guaranteed bandwidth and capacity of extra burst cache. For the N1EAS2, every port has eight queues, and every queue has flow shaping function. The parameter to set includes the guaranteed bandwidth and peak bandwidth.

Impact on the System If the guaranteed bandwidth of the parameter is excessively high, the shaping effect is not good. If the capacity of extra burst cache is large, more burst packets can be cached but the delay of the cached packets at the port increases.

Values Name

Value Range

Default Value

Port List

l Indicates that every port of the N1EMS4, N1EGS4, N3EGS4, N4EGS4, and N5EFS0 has four queues.

-

l The N1EAS2: Every port has eight queues. Status

l Enabled

Disabled

l Disabled CIR

l The N1EMS4, N1EGS4, N3EGS4 and N4EGS4: An integer between 0-2499968. The step length is 64 and the unit is kbit/s.

0

l The N1EAS2: An integer between 0-10485760. The step length is 64 and the unit is kbit/s. DCBS

l The N1EMS4, N1EGS4, N3EGS4, and N4EGS4: 0-32 (kbyte)

0

l The N1EAS2: Not configurable PIR

l The N1EMS4, N1EGS4 and N3EGS4: Not configurable

0

l The N1EAS2: An integer between 0-10485760. The step length is 64 and the unit is kbit/s. Issue 03 (2013-02-20)


729



Name

Value Range

Default Value

DMBS

l The N1EMS4, N1EGS4 and N3EGS4: Not configurable

0

l The N1EAS2: Not configurable

Configuration Guidelines The user can set this parameter according to the actual bandwidth rate of the output port.


A.12 ATM Interface Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM interface.

A.12.1 ATM Cell Payload Scrambling(ATM Interface Management) Description The ATM Cell Payload Scrambling (ATM Interface Management) parameter specifies whether to scramble the payload of cells on asynchronous transfer mode (ATM) links.

Impact on the System Different settings of this parameter for ports at both ends of an inverse multiplexing for ATM (IMA) link result in unavailable services.

Values Value Range

Default Value

Enabled, Disabled

Enabled

Configuration Guidelines Set this parameter to the same value for the equipment at the local and opposite ends. That is, if scrambling is performed on the payload of cells transmitted by the equipment at the opposite end, the payload of cells transmitted by the equipment at the local end must also be scrambled. Generally, set this parameter to the default value (Enabled).



730



Related Information Scrambling is another type of coding technology that is commonly used for serial link transmission. The purpose of scrambling is to suppress consecutive "1" bits and consecutive "0" bits to facilitate extraction of clock signals from line signals. Line signals are scrambled only. Therefore, the rate of SDH line signals is the same as that of standard signals at SDH electrical interface, and this does not add extra optical power penalty to the laser at the transmit end. An ATM cell is the basic carrier for transmitting ATM information. An ATM cell, which consists of only 53 bytes, is divided into a 5-byte header and a 48-byte payload.

A.12.2 Min.VPI(ATM Interface Management) Description The Min.VPI parameter specifies the minimum virtual path identifier (VPI) value of the permanent virtual paths (PVPs) and permanent virtual channels (PVCs) that are applicable to a selected board.

Impact on the System The VPI value specifies the valid range of VPIs and identifies the number of available VPIs at a port. You can change the number of VPIs to a proper value based on the requirements of the port. Setting this parameter results in re-creation of the deleted connections to the selected board. As a result, service packets are lost.

Values Value Range

Default Value

UNI port: 0-255; NNI port: 0-4095

0

Configuration Guidelines Set this parameter according to the VPI values required for a port. For example, if a port needs to converge 500 PVCs and if each PVC has a unique VPI, 500 VPIs are required for service identification. Therefore, ensure that the offset value between the maximum number of VPIs and the minimum number of VPIs is greater than 500. For the TNN1D75E and TNN1D12E boards, this parameter cannot be set to the minimum number of VPIs. That is, the number of VPIs is not limited. For the TNN1AFO1 board, the sum of the minimum numbers of VPIs of all ports is less than 4096.



731



Related Information The operations on an ATM network are similar to a call connection process. Before a conversation, a virtual channel connection (VCC), which is identified with a VPI/a virtual channel identifier (VCI), must be set up between the source end and the destination end. l

VPI: stands for virtual path identifier.

l

VCI: stands for virtual channel identifier.

l

VP switching: changes only VPI values and transparently transmits VCI values in the switching process.

l

VC switching: changes VPI values and VCI values in the switching process.

l

PVP: stands for permanent virtual path.

l

PVC: stands for permanent virtual channel.

A.12.3 Min.VCI(ATM Interface Management) Description The Min.VCI parameter specifies the minimum virtual channel identifier (VCI) value for permanent virtual channels (PVCs) that are applicable to a selected board.

Impact on the System The VCI value specifies the valid range of VCIs and identifies the number of available VCIs at a port. You can change the number of VCIs to a proper value based on the requirements of the port. Setting this parameter results in re-creation of the deleted connections to the selected board. As a result, service packets are lost.

Values Value Range

Default Value

0-65535

65535

Configuration Guidelines Set this parameter according to the number of VCIs required for a port. For example, if a port needs to converge 500 PVCs and if each PVC has a unique VCI, 500 VCIs are required for service identification. Therefore, ensure that the offset value between the maximum number of VCIs and the minimum number of VCIs is greater than 500. For the TNN1D75E and TNN1D12E boards, this parameter cannot be set to the minimum number of VCIs. That is, the number of VCIs is not limited. This parameter can be set to other values only when the number of VPIs that are applicable to VCCs at a port is not 65535. Issue 03 (2013-02-20)


732




Related Information The operations on an ATM network are similar to a call connection process. Before a conversation, a virtual channel connection (VCC), which is identified with a virtual path identifier (VPI)/a VCI, must be set up between the source end and the destination end. l


l


l


l


l


l


A.12.4 VCC-Supported VPI Count(ATM Interface Management) Description The VCC-Supported VPI Count parameter specifies the number of virtual path identifiers (VPIs) available for a permanent virtual channel (PVC) connection at a port. That is, only the specified number of VPIs can be adopted for establishment of a PVC connection regardless of the specified VPI value. In other circumstances, the specified number of VPIs can be adopted for establishment of a permanent virtual path (PVP) connection.

Impact on the System This parameter limits the number of VPIs that can be used for establishment of a VC connection, and therefore affects allocation of system resources. In practice, you need to set this parameter based on services.

Values Board Name

Value Range

Default Value

TNN1AFO1

0-256, 65535

65535

Configuration Guidelines Set this parameter according to the number of VCIs required for each VPI at a port. For example, if 50 PVCs need to be established at a port and if each PVC has a unique VPI, 50 VPIs are required for service identification. Therefore, set the number of VPIs available for VC switching to 50. The value 65535 indicates that the number of VPIs for establishment of a VC connection is not limited. If any connections are available at a port, this parameter is unavailable. Issue 03 (2013-02-20)


733



Relationship with Other Parameters The number of VPIs for a VCC must be less than the offset value between the maximum number and the minimum number of VPIs.

Related Information The operations on an ATM network are similar to a call connection process. Before a conversation, a virtual channel connection (VCC), which is identified with a VPI/a VCI, must be set up between the source end and the destination end. l


l


l


l


l


l


A.13 ATM/IMA Services Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM/IMA services.

A.13.1 IMA Transit Frame Length Description The IMA Transit Frame Length parameter specifies the length of an inverse multiplexing for ATM (IMA) frame transmitted by the equipment at the local end. That is, this parameter specifies the number of asynchronous transfer mode (ATM) cells in an IAM frame. An IMA frame contains an IMA control protocol (ICP) cell for negotiation of the IMA control protocol and transmission of information.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

32, 64, 128, 256

128


734



Configuration Guidelines The TNN1D75E and TNN1D12E boards support the IMA function. Therefore, set the length of IMA frames to be the same as that of the IMA frames for the interconnected boards. For example, if IMA groups on two NEs are connected to each other, set the length of IMA frames transmitted at both the local and opposite ends to 128.



A.13.2 IMA Symmetry Mode Description The IMA Symmetry Mode parameter specifies the configuration and operation mode of inverse multiplexing for ATM (IMA) links in an IMA group.

Impact on the System Different symmetrical modes determine the unidirectional conductivity of an IMA link (that is, only one receive or transmit direction is available for an IMA link).

Values Value Range

Default Value

Symmetrical Mode and Symmetrical Operation, Symmetrical Mode and Asymmetrical Operation, Asymmetrical Mode and Asymmetrical Operation

Symmetrical Mode and Symmetrical Operation


Issue 03 (2013-02-20)

Value

Description


Indicates that all links in the IMA group are configured with the capabilities of receiving and transmitting services in two directions when you configure an IMA group (in symmetrical configuration mode). If services on a link are simultaneously interrupted in the receive and transmit directions, this link is bidirectionally unavailable (in symmetrical operation mode).


735



Value

Description

Symmetrical Mode and Asymmetrical Operation

Indicates that all links in the IMA group are configured with the capabilities of receiving and transmitting services in two directions when you configure an IMA group (in symmetrical configuration mode). If services on a link are interrupted in one direction but available in the other direction, this link is unidirectionally available (in asymmetrical operation mode).

Asymmetrical Mode and Asymmetrical Operation

Indicates that some links in the IMA group are configured with only the capabilities of receiving and transmitting services in one direction when you configure an IMA group (in asymmetrical configuration mode). If services on a link are interrupted in one direction but available in the other direction, this link is unidirectionally available (in asymmetrical operation mode).

Configuration Guidelines For the TNN1D75E and TNN1D12E boards, this parameter can be set only to Symmetrical Mode and Symmetrical Operation.

Relationship with Other Parameters If IMA Symmetry Mode is set to Symmetrical Mode and Symmetrical Operation, Minimum Number of Active Transmitting Links must be equal to Minimum Number of Active Receiving Links.


A.13.3 Maximum Delay Between Links(ms)(IMA Group Management) Description The Maximum Delay Between Links(ms) parameter specifies the maximum delay tolerance between links in an inverse multiplexing for ATM (IMA) group. That is, this parameter specifies the allowed maximum difference between the maximum delay value and the minimum delay value of all links in an IMA group. If the maximum difference exceeds the specified value, the equipment reports the lODS alarm for a link who has the largest offset value compared with the average delay value of all links in the MA group. Then, the equipment removes the alarmed link from the IMA group.

Impact on the System This parameter determines the allowed maximum difference between the maximum delay value and the minimum delay value of all links. If delay variation of all links in an IMA group is great, set delay tolerance to a large value to avoid removal of a link whose delay value is great from the IMA group. If some links that have great delay values are not removed from the IMA group, Issue 03 (2013-02-20)


736



the transmit and receive rates of the IMA group decrease, and the transmission delay of the IMA group may increase.

Values Value Range

Default Value

1-120

25

Configuration Guidelines Set this parameter properly according to the requirements for link delay and service delay. It is recommended that you take the default value.



A.13.4 Minimum Number of Active Transmitting Links(IMA Group Management) Description The Minimum Number of Active Transmitting Links parameter specifies the lower threshold of active links in the transmit direction in an inverse multiplexing for ATM (IMA) group to maintain proper operation of the IMA group.

Impact on the System

An incorrect setting of this parameter may result in service interruption. If the number of active links in the transmit direction of an IMA group is less than the bandwidth specified for boards but equal to or greater than the specified minimum number of active links, the IMA group functions properly. If the number of active links in the transmit direction of an IMA group is less than the specified minimum number of active links, services of the IMA group are interrupted.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

1-16

1


737



Configuration Guidelines Set the minimum number of active links, depending on the equipment at the opposite end. For example, 10 active links are currently available, the total bandwidth is 20 Mbit/s, and the interconnected equipment requires a minimum of 15 Mbit/s bandwidth. To meet the preceding requirements, set the minimum number of active links to 8. If the minimum number of active links is less than 8, the bandwidth is less than 15 Mbit/s. As a result, services in the IMA group are interrupted. For the TNN1D75E and TNN1D12E boards, configure a maximum of 16 IMA links for an IMA group due to hardware constraints. Therefore, the minimum number of active links in the transmit direction cannot be more than 16.

Relationship with Other Parameters This parameter takes effect only after an IMA group is configured. If the IMA group is enabled, Minimum Number of Active Transmitting Links cannot be set to a value greater than the number of links in the existing IMA group.


A.13.5 Minimum Number of Active Receiving Links(IMA Group Management) Description The Minimum Number of Active Receiving Links parameter specifies the lower threshold of active links in the receive direction in an inverse multiplexing for ATM (IMA) group to maintain proper operation of the IMA group.

Impact on the System An incorrect setting of this parameter may result in service interruption. If the number of active links in the receive direction of an IMA group is less than the bandwidth specified for boards but equal to or greater than the specified minimum number of active links, the IMA group functions properly. If the number of active links in the receive direction of an IMA group is less than the specified minimum number of active links, services in the IMA group are interrupted.

Values Value Range

Default Value

1-16

1

Configuration Guidelines Set the minimum number of active links, depending on the equipment at the opposite end. For the TNN1D75E and TNN1D12E boards, configure a maximum of 16 IMA links for an IMA Issue 03 (2013-02-20)


738



group due to hardware constraints. Therefore, the minimum number of active links in the receive direction cannot be more than 16. You can specify the minimum number of active links based on the actual service transmission. For example, 10 active links are currently available, the total bandwidth is 20 Mbit/s, and the interconnected equipment requires a minimum of 15 Mbit/s bandwidth. To meet the preceding requirements, set the minimum number of active links to 8. If the minimum number of active links is less than 8. the bandwidth is less than 15 Mbit/s. As a result, services in the IMA group are interrupted.

Relationship with Other Parameters This parameter takes effect only after an IMA group is configured. If the IMA group is enabled, the minimum number of active links in the receive direction cannot be set to a value greater than the number of existing links in the IMA group.


A.13.6 Clock Mode(IMA Group Management) Description The Clock Mode parameter specifies the clock mode for operations of an inverse multiplexing for ATM (IMA) group.

Impact on the System In an IMA group, all links can trace the same clock source, and a link can also use a separate clock source. The clock mode of an IMA group determines the method of selecting a clock source in the IMA group for signal transmission.

Values Value Range

Default Value

CTC Mode, ITC Mode

CTC Mode


Issue 03 (2013-02-20)

Value

Description

CTC Mode

Indicates the common transmit clock (CTC) mode in which the same clock source is used for all links in an IMA group.

ITC Mode

Indicates the independent transmit clock (ITC) mode in which the transmit clock on a link in an IMA group is independently derived from a clock source.


739



Configuration Guidelines The clock modes must be the same at both ends of an IMA group.



A.13.7 Near-End Group Status(IMA Group Status) Description The Near-End Group Status parameter displays the status of an inverse multiplexing for ATM (IMA) group at the local end.


Values Value Range

Default Value

Start-Up, Start-Up-ACK, Config-Aborted, Insufficient-Links, Operational

Start-Up


Issue 03 (2013-02-20)

Value Range

Description

Start-Up

Indicates that the equipment at the local end starts up and waits for startup of the equipment at the opposite end.

Start-Up-ACK

Indicates the waiting state of the IMA group, which is displayed after the equipment at the local and opposite ends starts up.

Config-Aborted

Indicates that the parameter settings for the equipment at the local and opposite ends do not match.

Insufficient-Links

Indicates that the parameter settings for the equipment at the local and opposite ends match, but no sufficient link resource is available.


740



Value Range

Description

Operational

Indicates that the IMA group is enabled and sufficient link resources are available.


Relationship with Other Parameters This parameter shows the IMA negotiation status on the NE side. If an IMA group is set to Enabled, the status of the IMA group cannot be queried.


A.13.8 Differential Delay Check Status(IMA Link States) Description The Differential Delay Check Status parameter displays the result returned when you query the statuses of inverse multiplexing for ATM (IMA) links.


Values Value Range

Default Value

Unknown, Valid, Invalid

Unknown


Issue 03 (2013-02-20)

Value

Description

Unknown

Indicates that the delay value of links is not computed. If an IAM group is configured or if the equipment at the local end cannot receive information from links at the opposite end, the delay on links cannot be computed.

Valid

Indicates that the loss of delay synchronization (LODS) alarm is not reported on links.

Invalid

Indicates that the LODS alarm is reported on links.


741






A.13.9 Connection Type(Per-NE ATM Service Management) Description The Connection Type parameter specifies the type of an asynchronous transfer mode (ATM) connection.


Values Value Range

Default Value

PVP, PVC, Port Transparent

UNIs-NNI: PVC, UNI-UNI: PVP


Description

PVP

Transmits services that contain the same virtual path identifier (VPI) but different virtual channel identifiers (VCIs).

PVC

Transmits services that contain the same VPI and VCI.

Port Transparent

Transparently transmits all services regardless of their VPIs and VCIs without establishment of connections.

Configuration Guidelines If services that contain the same VPI need to be converged at a port, set this parameter to PVP. Issue 03 (2013-02-20)


742



If services that contain the same VPI and VCI need to be transmitted, set this parameter to PVC. A permanent virtual channel (PVC) and a permanent virtual path (PVP) are virtual transmission paths, but a PVC is contained in a PVP.


Related Information A PVC and a PVP are virtual transmission paths, but a PVC is contained in a PVP. l


l


l


l


A.13.10 Uplink Policy(Per-NE Configuration for ATM Connections) Description The Uplink Policy parameter specifies the traffic policy ID in a specified direction of an asynchronous transfer mode (ATM) connection. For user-network interface (UNI) - networknetwork interface (NNI) services, the specified direction is from the UNI side to the pseudo wire (PW). For UNI - UNI services, the specified direction is from the source UNI port to the destination UNI port.

Impact on the System Setting the uplink policy of an asynchronous transfer mode (ATM) connection determines the traffic policy (such as scheduling priority, leaky bucket processing, shaping, and UNI scheduling priority) in a specified direction of an ATM connection. An incorrect setting of this parameter may result in packet loss and failed assurance for higher-priority services.

Values Value Range

Default Value

1-256

-

Configuration Guidelines An uplink policy determines the traffic parameters and QoS parameters in a specified direction of an ATM connection. An uplink policy is also used for setting the forwarding priority of QoS parameters of a network, based on the characteristics of data transmitted on the ATM connection. For services that require high transmission quality, select an ATM policy that is preferred to ensure proper data transmission. Issue 03 (2013-02-20)


743





A.13.11 Downlink Policy(Per-NE Configuration for ATM Connections) Description The Downlink Policy parameter specifies the traffic policy ID in a specified direction of an asynchronous transfer mode (ATM) connection. For user-network interface (UNI) - networknetwork interface (NNI) services, the specified direction is from the pseudo wire (PW) to the UNI side. For UNI-UNI services, the specified direction is from the source UNI port to the destination UNI port.

Impact on the System Setting the downlink policy of an ATM connection determines the traffic policy (such as scheduling priority, leaky bucket processing, shaping, and UNI scheduling priority) in a specified direction of an ATM connection. An incorrect setting of this parameter may result in packet loss and failed assurance for higher-priority services.

Values Value Range

Default Value

1-256

None.

Configuration Guidelines A downlink policy determines the traffic parameters and QoS parameters in a specified direction of an ATM connection. A downlink policy is also used for setting the forwarding priority of QoS parameters of a network, based on the characteristics of data transmitted on the ATM connection. For services that require high transmission quality, select an ATM policy that is preferred to ensure proper data transmission.




744



A.13.12 CoS Mapping(Per-NE Configuration for CoS Mapping) Description The CoS Mapping parameter specifies the priories of packets based on the class of service (CoS) for mapping between packets and CoS priorities. For different priorities of packets, different services are available.

Impact on the System Compared with lower-priority packets, higher-priority packets are preferred for transmission in better service-quality mode.

Values Value

Default Value

2-8

1(DefaultAtmCosMap)

Configuration Guidelines The ATM service class mapping table specifies mapping between ATM services and CoS priorities to provide differentiated assurance of service quality. You can adopt the default or user-defined ATM service class mapping table. You can define a maximum of seven ATM service class mapping tables.



A.13.13 Traffic Service(ATM Policy) Description The Traffic Service parameter specifies the sub-type of a service type. That is, multiple traffic types are available for each type of service. A traffic type specifies the traffic parameters that can be set, the methods of handling cells whose cell loss priority (CLP) values are 0 and 1, and the supported functions (such as cell labeling).

Impact on the System A change of QoS parameter settings may result in packet loss. For example, different types of services have different parameters for the traffic type. For a constant bit rate (CBR) service, five traffic types can be configured. In practice, if a small number of burst services whose transmission rate is greater than the peak cell rate (PCR), extra cells are absolutely discarded for the NoClpNoScr traffic type, and therefore services are transiently Issue 03 (2013-02-20)


745



interrupted. For the other four types of services, a certain amount of buffer size is allocated, and the burst services whose transmission rates are greater than the PCR are discarded only when they exceed the buffer size.

Values For different service types, available traffic types are different. Service Type

Value Range

Default Value

CBR

NoClpNoScr

NoClpNoScr

ClpNoTaggingNoScr ClpTaggingNoScr ClpTransparentNoScr NoClpNoScrCdvt rt-VBR

ClpTransparentScr

ClpTransparentScr

NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt nrt-VBR

NoClpScr

NoClpScr

ClpNoTaggingScr ClpTaggingScr UBR

NoTrafficDescriptor

NoTrafficDescriptor

NoClpNoScr NoClpTaggingNoScr NoClpNoScrCdvt UBR+

atmNoTrafficDescriptorMcr

atmNoTrafficDescriptorMcr

atmNoClpMcr atmNoClpMcrCdvt

Configuration Guidelines For CBR services, this parameter is set as follows:

Issue 03 (2013-02-20)


746



Traffic Type

CDVT Supporte d

Handlin g Cells With CLPs Being 0 and 1 Different ly

Cell Labeling Supporte d

PCR Supporte d

MBS Supporte d

SCR Supporte d

NoClpNo Scr

No

No

No

Yes

No

No

ClpNoTag gingNoScr

No

Yes

No

Yes

No

No

ClpTaggin gNoScr

No

Yes

Yes

Yes

No

No

ClpTransp arentNoSc r

Yes

No

No

Yes

No

No

NoClpNo ScrCdvt

Yes

No

No

Yes

No

No

For rt-VBR services, this parameter is set as follows: Traffic Type

CDVT Suppor ted

Handli ng Cells With CLPs Being 0 and 1 Differe ntly

Cell Labelin g Suppor ted

PCR Suppor ted

MCR Suppor ted

MBS Suppor ted

SCR Suppor ted

ClpTran sparentS cr

Yes

No

No

Yes

No

Yes

Yes

NoClpSc rCdvt

Yes

No

No

Yes

No

Yes

Yes

ClpNoT aggingS crCdvt

Yes

Yes

No

Yes

No

Yes

Yes

ClpTaggingScr Cdvt

Yes

Yes

Yes

Yes

No

Yes

Yes

For nrt-VBR services, this parameter is set as follows: Issue 03 (2013-02-20)


747



Traffic Type

CDVT Suppor ted



PCR Suppor ted

MCR Suppor ted

MBS Suppor ted

SCR Suppor ted

NoClpSc r

No

No

No

Yes

No

Yes

Yes

ClpNoT aggingS cr

No

Yes

No

Yes

No

Yes

Yes

ClpTagg ingScr

No

Yes

Yes

Yes

No

Yes

Yes

For UBR services, this parameter is set as follows: Traffic Type

CDVT Suppor ted



PCR Suppor ted

MCR Suppor ted

MBS Suppor ted

SCR Suppor ted

NoTraffi cDescrip tor

No

No

No

No

No

No

No

NoClpN oScr

No

No

No

Yes

No

No

No

NoClpT aggingN oScr

Yes

Yes

Yes

Yes

No

No

No

NoClpN oScrCdv t

Yes

No

No

Yes

No

No

No

For UBR+ services, this parameter is set as follows:

Issue 03 (2013-02-20)


748



Traffic Type

CDVT Suppor ted



PCR Suppor ted

MCR Suppor ted

MBS Suppor ted

SCR Suppor ted

atmNoTr afficDes criptorM cr

No

No

No

No

Yes

No

No

atmNoCl pMcr

No

No

No

Yes

Yes

No

No

atmNoCl pMcrCd vt

Yes

Yes

Yes

Yes

Yes

No

No

NOTE

l CDVT: stands for cell delay variation tolerance. l CLP: stands for cell loss priority in an ATM cell header. l Cell labeling: sets the CLP of a cell that does not comply with the specified traffic parameters to 1. If network congestion occurs, a cell whose CLP is 1 is immediately discarded. Therefore, you need to select a service type based on the network type and service characteristics.

Relationship with Other Parameters This parameter is available only when Service Type is selected.


A.13.14 Clp01Pcr(cell/s)(ATM Policy) Description The Clp01Pcr(cell/s) parameter specifies the peak cell rate of a service whose cell loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0. In this parameter, Pcr stands for peak cell rate, which is the maximum transmission rate of a cell flow.

Impact on the System An incorrect setting of this parameter may result in packet loss. Issue 03 (2013-02-20)


749



Values Value Range

Default Value

Unit

90-149078

None.

Cell/s

Configuration Guidelines The parameter value must be not larger than the physical bandwidth of an ATM port or an inverse multiplexing for ATM (IMA) group. For example, the bandwidth (based on the number of ATM cells) of one E1 in an IAM group is derived from the formula: (30 × 8 × 8000) / (53 × 8) × ((M-1) / M) x (2048 / 2049). l

The expression 30 × 8 × 8000 represents the bandwidth of an E1 service in an IMA group. The value 30 represents 30 of the 32 timeslots in an E1 (if 31 timeslots are used, change the value from 30 to 31.)

l

The expression 53×8 represents the number of bits in an ATM cell.

l

The letter M indicates the frame length of an IMA group. According to the MA protocol, an IMA control protocol (ICP) cell is inserted to every M-1 user cells. An ICP cell, which is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP cell needs to be removed from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell needs to be inserted to every 2048 cells.

l

If the frame length (M) of an IMA group is 128, the maximum number of cells derived from the preceding formula is 4490 (rounded off to an integer). Therefore, the Clp0Pcr value specified for an IMA group in which only one E1 service is available needs to be not more than 4490.

l

If the IMA protocol is disabled for the E1 service, the bandwidth is derived from the formula: (30 × 8 × 8000) / (53 × 8).

l

The expression 30 × 8 × 8000 represents the bandwidth of an E1 service in an IMA group. The value 30 represents 30 of the 32 timeslots in an E1 service in an IMA group. (If only 10 timeslots are used, change the value from 30 to 10.)

l

If the transmission rate at a port of AFO1 is STM-1, the bandwidth (based on the number of ATM cells) is 149760 (rounded off to an integer).


Related Information According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the PCR, and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic.

Issue 03 (2013-02-20)


750



Figure A-7 Dual token bucket model Parameters for a level-1 leaky bucket: PCR CDVT CLP1 CLP0 SCR0

CLP0+1

CLP0+1

CLP0

Conforming cells

Parameters for a level-2 leaky bucket: SCR BT+CDVT Non-conforming cells

Figure A-8 Structure of the ATM UNI cell header in the dual token bucket model

GFC (4)

VPI (4)

VPI (4)

VCI (4) VCI (8)

VCI (4)

PT (3)

CLP (1)

HEC (8)

A.13.15 Clp01Scr(cell/s)(ATM Policy) Description The Clp01Pcr(cell/s) parameter specifies the substainable cell rate of a service whose cell loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0. In this parameter, Scr stands for sustainable cell rate, which is an average cell transmission rate for a long time. Issue 03 (2013-02-20)


751



Impact on the System An incorrect setting of this parameter may result in packet loss.

Values Value Range

Default Value

Unit

90-149078

None.

Cell/s


The expression 30 × 8 × 8000 represents the bandwidth of an E1 service in an IMA group. The value 30 represents 30 of the 32 timeslots in an E1 service in an IMA group (if 31 timeslots are used, change the value from 30 to 31.)

l

The expression 53 × 8 represents the number of bits in an ATM cell.

l

The letter M indicates the frame length of an IMA group. According to the IMA protocol, an ICP cell is inserted to every M-1 user cells. An IMA control protocol (ICP) cell, which is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP cell needs to be removed from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell needs to be inserted to every 2048 cells.

l


l


l


l


Relationship with Other Parameters The parameter value must be not larger than the maximum cell transmission rate.

Related Information According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket limits the SCR. The two-level token buckets adopt the GCRA algorithm to control the traffic. Issue 03 (2013-02-20)


752




CLP0+1

CLP0+1

CLP0

Conforming cells



GFC (4)

VPI (4)

VPI (4)

VCI (4) VCI (8)

VCI (4)

PT (3)

CLP (1)

HEC (8)

A.13.16 Clp0Pcr(cell/s)(ATM Policy) Description The Clp0Pcr(cell/s) parameter specifies the peak cell rate of a service whose cell loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 0. In this parameter, Pcr stands for peak cell rate, which is the maximum transmission rate of a cell flow. Issue 03 (2013-02-20)


753




Values Value Range

Default Value

Unit

90-149078

None.

Cell/s



l


l

The letter M indicates the frame length of an IMA group. According to the IMA protocol, an IMA control protocol (ICP) cell is inserted to every M-1 user cells. An ICP cell, which is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP cell needs to be removed from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell needs to be inserted to every 2048 cells.

l


l


l


l



Related Information According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the PCR, and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic. Issue 03 (2013-02-20)


754




CLP0+1

CLP0+1

CLP0

Conforming cells



GFC (4)

VPI (4)

VPI (4)

VCI (4) VCI (8)

VCI (4)

PT (3)

CLP (1)

HEC (8)

A.13.17 Clp0Scr(cell/s)(ATM Policy) Description The Clp0Scr(cell/s) parameter specifies the substainable cell rate of a service whose cell loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 0. In this parameter, Scr stands for sustainable cell rate, which is an average cell transmission rate for a long time. Issue 03 (2013-02-20)


755




Values Value Range

Default Value

Unit

90-149078

None.

Cell/s


The expression 30 × 8 × 8000 represents the bandwidth of an E1 service in an IMA group. The value 30 represents 30 of the 32 timeslots in an E1 (if 31 timeslots are used, change the value from 30 to 31.)

l


l

The letter M indicates the frame length of an IMA group. According to the IMA protocol, an IMA control protocol (ICP) cell is inserted to every M-1 user cells. An ICP cell, which is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP cell needs to be removed from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell needs to be inserted to every 2048 cells.

l

If the frame length (M) of an IMA group is 128, the maximum number of cells derived from the preceding formula is 4490 (rounded off to an integer). Therefore, the Clp0Pcr value specified for an MA group in which only one E1 service is available needs to be not more than 4490.

l


l


l


Relationship with Other Parameters This parameter value must be not larger than the maximum cell transmission rate.

Related Information According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket limits the SCR. The two-level token buckets adopt the GCRA algorithm to control the traffic. Issue 03 (2013-02-20)


756




CLP0+1

CLP0+1

CLP0

Conforming cells



GFC (4)

VPI (4)

VPI (4)

VCI (4) VCI (8)

VCI (4)

PT (3)

CLP (1)

HEC (8)

A.13.18 Clp01Mcr(cell/s)(ATM Policy) Description The Clp01Mcr(cell/s) parameter specifies the minimum transmission rate of cells whose cell loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0. In this parameter, Mcr stands for the minimum cell rate, which is the minimum transmission rate of a cell flow. Issue 03 (2013-02-20)


757




Values Value Range

Default Value

Unit

566-32664

None.

Cell/s



l


l

The letter M indicates the frame length of an IMA group. According to the IMA protocol, an ICP cell is inserted to every M-1 user cells. An ICP cell, which is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP cell needs to be removed from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell needs to be inserted to every 2048 cells.

l


l


l


l


Relationship with Other Parameters The parameter value must be not larger than the maximum transmission rate of a cell flow.

Related Information According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic. Issue 03 (2013-02-20)


758




CLP0+1

CLP0+1

CLP0

Conforming cells



GFC (4)

VPI (4)

VPI (4)

VCI (4) VCI (8)

VCI (4)

PT (3)

CLP (1)

HEC (8)

A.13.19 Max.Cell Burst Size(cell)(ATM Policy) Description The Max.Cell Burst Size(cell) parameter specifies the maximum number of cells that are continuously transmitted on an asynchronous transfer mode (ATM) path of a variable bit rate (VBR) service at a rate of r (SCR < r

759




Values Value Range

Default Value

Unit

2-200000

None.

cell

Configuration Guidelines The greater the parameter value, the deeper the level-2 token bucket on the ATM path, and the better performance the service for burst cells. Therefore, if conditions are allowed, you can set the maximum burst size to a greater value.


Related Information Token bucket algorithm: The equipment constantly monitors the rate of burst cells. If the rate of burst cells exceeds the specified value (1/I), the equipment computes and accumulates the offset value between the theoretical arrival time of cells and the actual arrival time of cells. If the accumulated offset value is within the specified value (1/I), the equipment considers that the cells are conforming cells. If the accumulated offset value exceeds the specified value (L), the equipment considers that the cells are non-conforming cells, which are handled according to the methods specified in the contract. That is, non-conforming cells are discarded (based on the CLP values or regardless of the CLP values) or added with tagging labels. According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic. l

For a level-1 token bucket, the value I is 1/PCR, and the value L is CDVT. If the rate of burst cells exceeds the specified PCR value, the equipment computes and accumulates the offset value between the theoretical arrival time of cells and the actual arrival time of cells. If the accumulated offset value exceeds the specified value L (the CDTV value for a level-1 token bucket), the cells are discarded.

l

For a level-2 token bucket, the value I is 1/SCR, and the value L is derived from the formula: BT + CDVT. The equipment performs the same operations as those for a level-1 token bucket, except that the parameters are different. The value BT is derived from the formula: (MBS - 1)(1/SCR - 1/PCR).

A.13.20 Cell Delay Variation Tolerance(0.1us)(ATM Policy) Description The Cell Delay Variation Tolerance(0.1us) parameter specifies the burst cell tolerance of an asynchronous transfer mode (ATM) connection. Issue 03 (2013-02-20)


760



In this parameter, CDVT stands for cell delay variation tolerance.

Impact on the System If the actual arrival time of a cell is later than the theoretical arrival time, the cell is considered as a burst cell. The number of burst cells is measured according to the offset value between the actual arrival time and the theoretical arrival time of cells. If the total number of consecutive burst cells exceeds the CDVT value for a token bucket of the service, extra cells are discarded.

Values Value Range

Default Value

Unit

7 to 13300000

None.

0.1us

Configuration Guidelines The greater the parameter value, the better performance the service for burst cells. If conditions are allowed, you can set CDVT to a large value to minimize packet loss.


Related Information Token bucket algorithm: The equipment constantly monitors the rate of burst cells. If the rate of burst cells exceeds the specified value (1/I), the equipment computes and accumulates the offset value between the theoretical arrival time of cells and the actual arrival time of cells. If the accumulated offset value is within the specified value (1/I), the equipment considers that the cells are conforming cells. If the accumulated offset value exceeds the specified value (L), the equipment considers that the cells are non-conforming cells, which are handled according to the methods specified in the contract. That is, non-conforming cells are discarded (based on the cell loss priority (CLP) values or regardless of the CLP values) or added with tagging labels. According to ATM Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic. l

For a level-1 token bucket, the value I is 1/PCR, and the value L is CDVT. If the rate of burst cells exceeds the specified PCR value, the equipment computes and accumulates the offset value between the theoretical arrival time of cells and the actual arrival time of cells. If the accumulated offset value exceeds the specified value L (the CDTV value for a level-1 token bucket), the cells are discarded.

l

For a level-2 token bucket, the value I is 1/SCR, and the value L is derived from the formula: BT + CDVT. The equipment performs the same operations as those for a level-1 token bucket, except that the parameters are different. The value BT is derived from the formula: (MBS - 1)(1/SCR - 1/PCR).

Issue 03 (2013-02-20)


761



A.13.21 UPC/NPC(ATM Policy) Description The UPC/NPC parameter specifies the user-network interface (UNI) traffic parameters based on usage parameter control (UPC) and network parameter control (NPC).


Values Value Range

Default Value

Disabled, Enabled

Disabled

Configuration Guidelines The traffic monitoring function is classified into UPC and NPC by interface position. The UPC function is available for UNI-NNI interfaces, whereas the NPC function is available for NNI-NNI interfaces. The UPC and NPC functions are similar and used for processing nonconforming packets during a communication (for example, the number of burst packets exceeds the specified value). The UPC and NPC functions process packets in three modes: transmitting conforming packets; labeling non-conforming packets (setting the CLP field in the packets to the value 1) and lowering their forwarding priorities; and discarding non-conforming packets immediately.

Relationship with Other Parameters If the UPC and NPC functions are disabled, that is, if the token bucket protocol is disabled, the flow control function does not take effect for services.

Related Information According to asynchronous transfer mode (ATM) Forum, ATM traffic is currently controlled by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate ( PCR), and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic.

Issue 03 (2013-02-20)


762




CLP0+1

CLP0+1

CLP0

Conforming cells


A.14 ATM OAM Associated Parameters (Packet Mode) This topic describes the parameters for configuring ATM OAM.

A.14.1 Connection Direction Description The Connection Direction parameter specifies whether to enable the asynchronous transfer mode (ATM) operation, administration and maintenance (OAM) function at the source or sink end of a connection.


Values Value Range

Default Value

Source, Sink

Source

Configuration Guidelines Select a proper direction of the connection as required at the end where ATM OAM cells are identified and processed. Issue 03 (2013-02-20)


763




Related Information An ATM connection has a source end and a sink end. When setting the segment point and endpoint attributes, specify the direction of the ATM connection. That is, specify whether to set the segment and end attributes for the source or sink end of the ATM connection. Figure A-18 Setting a segment point A segment point is set.

Connection ID = 1

Source end

Sink end NE

After you specify the segment and end points in a direction of an ATM connection for an NE, the NE can identify and process ATM OAM cells in the receive direction of the port where the segment and end points are specified. For example, as shown in Figure A-18, if a segment point is specified for the source end of connection 1, the NE can identify and process ATM OAM cells transmitted between two segment points in the receive direction at the source end.

A.14.2 Segment and End Attribute Description The Segment and End Attribute parameter specifies the type of an operation, administration and maintenance (OAM) maintenance point. For different segment and end attributes, different ranges of asynchronous transfer mode (ATM) OAM cells are processed.


Values Value Range

Default Value

Non segment and Endpoint, Segment point, Endpoint, Segment and Endpoint

Non segment and Endpoint

The following table lists the description of each value. Issue 03 (2013-02-20)


764



Value

Description


Indicates that ATM OAM cells are not terminated.

Endpoint

Identifies, processes, and terminates the ATM OAM cells whose OAM maintenance points are set to the segment attribute.

Segment point

Identifies, processes, and terminates the ATM OAM cells whose OAM maintenance points are set to the end attribute, but identifies and discards the ATM OAM cells whose OAM maintenance points are set to the segment attribute.

Segment and Endpoint

Identifies, processes, and terminates all ATM OAM cells.

Configuration Guidelines According to different OAM maintenance segments, as shown in Figure A-19, set the segment and end attributes properly. Figure A-19 Schematic diagram of a maintenance segment

1 End

2 Seg

3 Inner

4 Inner

5 Seg + End

Segment User 1

End to end

User 2

1.

When enabling the ATM OAM function for a maintenance segment, set the endpoint attribute for the boundary of the maintenance segment. For example, as shown in Figure A-19, separately set the endpoint attribute for points 1 and 2 of the maintenance segment of user 1.

2.

You can divide a maintenance segment into different maintenance sub-segments to facilitate management. When dividing a maintenance area into different maintenance subsegments, set the segment attribute for both ends of a maintenance sub-segment. For example, as shown in Figure A-19, if the sub-segment between points 2 and 5 is considered as a maintenance sub-segment, separately set the segment point attribute for points 2 and 5 of the maintenance sub-segment.

Issue 03 (2013-02-20)


765


3.


When working as an end point and a segment point at the same time, a point needs to be a segment-end point, such as point 5 shown in Figure A-19.


Related Information An ATM connection has a source end and a sink end. When setting the segment point and endpoint attributes, specify the direction of the ATM connection. That is, specify whether to set the segment and end attributes for the source or sink end of the ATM connection. Figure A-20 Setting a segment point A segment point is set.

Connection ID = 1

Source end

Sink end NE

After you specify the segment and end points in a direction of an ATM connection for an NE, the NE can identify and process ATM OAM cells in the receive direction of the port where the segment and end points are specified. For example, as shown in Figure A-20, if a segment point is specified for the source end of connection 1, the NE can identify and process ATM OAM cells transmitted between two segment points in the incoming direction at the source end.

A.14.3 Country Code(Hexadecimal Code) Description The Country Code(Hexadecimal Code) parameter specifies the values of bytes 2 and 3 in the loopback location identifier (LLID).


Values

Issue 03 (2013-02-20)

Value Range

Default Value

[2BYTE]00 00-ff ff

[2BYTE]00 00


766



Configuration Guidelines The binary coded decimal (BCD) is used for a country code. For example, 0x0086 is used for China, 0x0001 for U.S.A., and 0x0044 for U. K. The default value is 0x0000, which is recommended.


Related Information According to ITU-T I.610, an LLID is specified in multiple coding methods and the first byte of the LLID is used to identify the coding method. In the GUI interface of a network management system, an LLID is specified in coding method 2 (the first byte is 0x01) described in ITU-T I.610, and a window is available for setting the other 15 bytes. The sequence and meaning of each filed are described as follows: 2-byte country code (the BCD is defaulted to be 0x0086) + 2-byte network code (the BCD is defaulted to 0x0000) + 11-byte NE code (the first four bytes are defaulted to be an NE ID, and the last seven bytes are defaulted to be 0s)

CAUTION After being specified, an NE code that is different from an NE ID (that is, the first four bytes are not the same as an NE ID, and the other seven bytes are not 0s) remains unchanged regardless of the NE ID.

A.14.4 Network Code(Hexadecimal Code) Description The Network Code(Hexadecimal Code) parameter specifies the values of bytes 4 and 5 in the loopback location identifier (LLID).


Values

Issue 03 (2013-02-20)

Value Range

Default Value

[2BYTE]00 00-ff ff

[2BYTE]00 00


767



Configuration Guidelines The binary coded decimal (BCD) is used for a network code. You can set a network code as required within the specified value range. The default network code is 0x0000. It is recommended that you set the network code to 0x0000.




A.14.5 NE Code(Hexadecimal Code) Description The NE Code(Hexadecimal Code) parameter specifies the values of bytes 6 through 16 in the loopback location identifier (LLID).


Values

Issue 03 (2013-02-20)

Value Range

Default Value

[11BYTE]00 00 00 00 00 00 00 00 00 00 00ff ff ff ff ff ff ff ff ff ff ff

4-byte NE ID + 7-byte 0s


768



Configuration Guidelines If an NE on a network has a unique LLID, set the values of the 11 bytes as required. The first four bytes are defaulted to be a network ID, and the last seven bytes are 0s. It is recommended that you set the network code to the default value.




A.15 ATM/IMA Associated Parameters (TDM Mode) This topic describes the parameters for configuring the ATM/IMA function.

A.15.1 VCTRUNK Port (ATM Bound Path Management) Description The VCTRUNK Port (ATM Bound Path Management) parameter identifies the ATM ports. One VCTRUNK can be bound with multiple SDH timeslots of the same level.


Values For N1ADQ1/N1ADL4 boards: Issue 03 (2013-02-20)


769



Valid Values

Default Value

VCTRUNK1-VCTRUNK16

UNI


Description

VCTRUNK1-4

Indicates the VCTRUNKs that can be bound with VC4-xv only.

VCTRUNK5-16

Indicates the VCTRUNKs that can be bound with VC3-xv or VC4-xv.

For N1IDQ1/N1IDL4 boards: Valid Values

Default Value

VCTRUNK1-VCTRUNK70

UNI


Description

VCTRUNK1-VCTRUNK66


VCTRUNK67VCTRUNK70

Indicates the VCTRUNKs that can be bound with VC4-xv only.

For N1IDQ1A and N1IDL4A boards: Valid Values

Default Value

VCTRUNK1-VCTRUNK98

UNI


Issue 03 (2013-02-20)

Value

Description

VCTRUNK1-VCTRUNK94

Indicates the VCTRUNKs that can be bound with the VC12xv or VC4-xv.


770



Value

Description

VCTRUNK95VCTRUNK98

Indicates the VCTRUNKs that can be bound with the VC4xv only.

Configuration Guidelines Principles of binding internal ports (VCTRUNK): For N1ADQ1 and N1ADL4 boards: Port Number

Binding Level

Path Number

VCTRUNK1-4

VC4-xv

1-4

VCTRUNK5-16

VC4-xv

5-8

VCTRUNK5-16

VC3-xv

13-24

Port Number

Binding Level

Path Number

VCTRUNK1-66

VC4-xv

1-4

VCTRUNK1-66

VC12-xv

1-63

VCTRUNK67-70

VC4-xv

5-8

For N1IDQ1/N1IDL4 boards:

For N1IDQ1A and N1IDL4A boards: Port Number

Binding Level

Path Number

VCTRUNK1-94

VC4-xv

1-4

VCTRUNK1-94

VC12-xv

1-189

VCTRUNK95-98

VC4-xv

5-8

NOTE

For the IDQ1 or IDL4, if the binding level is VC12-xv, 16 ports at the VC-12 level can be bound. The path number is allocated from 1 to 63 on the NMS. For the IDQ1A or IDL4A, if the binding level is VC12-xv, 93 ports at the VC-12 level can be bound. The path number is allocated from 1 to 189 on the NMS.



771



A.15.2 Level (ATM Bound Path Management) Description The Level (ATM Bound Path Management) parameter specifies the VC level that can be bound to VCTRUNK ports. For N1ADQ1/N1ADL4 boards, the level can be VC4-xv or VC3-xv; for N1IDQ1/N1IDL4 boards, the level can be VC4-xv or VC12-xv.

Impact on the System If this parameter is set improperly, the service may fail.

Values For N1ADQ1/N1ADL4 boards: Valid Value

Default Value

VC3-xv, VC4-xv

VC3-xv

For N1IDQ1/N1IDL4 boards: Valid Value

Default Value

l VC12-xv

VC12-xv

l VC4-xv

For N1IDQ1A/N1IDL4A boards: Valid Value

Default Value

VC12-xv, VC4-xv

VC12-xv

Configuration Guidelines Principles of binding internal ports (VCTRUNK): For N1ADQ1 and N1ADL4 boards:

Issue 03 (2013-02-20)

Port Number

Binding Level

Path Number

VCTRUNK1-4

VC4-xv

1-4

VCTRUNK5-16

VC4-xv

5-8


772



Port Number

Binding Level

Path Number

VCTRUNK5-16

VC3-xv

13-24

Port Number

Binding Level

Path Number

VCTRUNK1-66

VC4-xv

1-4

VCTRUNK1-66

VC12-xv

1-63

VCTRUNK67-70

VC4-xv

5-8

For N1IDQ1/N1IDL4 boards:

For N1IDQ1A/N1IDL4A boards: Port Number

Binding Level

Path Number

VCTRUNK1-94

VC4-xv

1-4

VCTRUNK1-94

VC12-xv

1-189

VCTRUNK95-98

VC4-xv

5-8


A.15.3 Direction (ATM Bound Path Management) Description The Direction (ATM Bound Path Management) parameter specifies the direction of a connection to be set up at a VCTRUNK port. The direction can beUplink, Downlink and Bidirectional.

Impact on the System If this parameter is set improperly, only unidirectional communication is achieved in a bidirectional service.

Values

Issue 03 (2013-02-20)

Valid Values

Default Value

Bidirectional, Uplink, Downlink

Bidirectional


773




Description

Uplink

The uplink ATM connection of the port is available. That is, the ATM connection is from the optical interface side to the cross-connection side.

Downlink

The downlink ATM connection of the port is available. That is, the ATM connection is from the cross-connection side to the optical interface side.

Bidirectional

The ATM connection of the port is available bidirectionally.

Configuration Guidelines An end-to-end connection is bound with VCTRUNKs in both directions, because the end-toend ATM connection is bidirectional. A multicast connection can be bound with a VCTRUNK in one direction, because the multicast ATM connection is unidirectional.


A.15.4 Port (ATM Port Management) Description The Port (ATM Port Management) parameter specifies identities of the external and internal ports on the ATM or IMA board.


Values For N1ADQ1 and N1ADL4 boards: Value Range

Default Value

l External ports 1-4

UNI

l Internal ports 1-16



774



Value

Description

External ports 1-4

Indicates the external ports on the N1ADQ1 or N1ADL4 board, which are numbered from 1 to 4 in the top down order. Note that only one external port is available on the N1ADL4 board.

Internal ports 1-4

Indicates the VCTRUNKs that can be bound only with VC4xv.

Internal ports 5-16


For N1IDQ1 and N1IDL4 boards: Value Range

Default Value


UNI



Description

External ports 1-4

Indicates the external ports on the N1IDQ1 or N1IDL4 board, which are numbered from 1 to 4 in the top down order. Note only one external port is available on the N1IDL4 board.

Internal ports 1-66


Internal ports 67-70

Indicates the VCTRUNKs that can be bound only with VC4xv.

For N1IDQ1A and N1IDL4A boards: Value Range

Default Value


UNI



Issue 03 (2013-02-20)


775



Value

Description

External ports 1-4

Indicates the external ports on the N1IDQ1A or N1IDL4A board, which are numbered from 1 to 4 in the top down order. Note that only one external port is available on the N1IDL4A board.

Internal ports 1-94

Indicates the VCTRUNKs that can be bound with the VC12xv or VC4-xv.


Indicates the VCTRUNKs that can be bound only with the VC4-xv.

Configuration Guidelines Principles of binding internal ports (VCTRUNKs): For N1ADQ1 and N1ADL4 boards: Port Number

Binding Level

Path Number

Internal ports 1-4

VC4-xv

1-4

Internal ports 5-16

VC4-xv

5-8

Internal ports 5-16

VC3-xv

13-24

For N1IDQ1 and N1IDL4 boards: Port Number

Binding Level

Path Number

Internal ports 1-66

VC4-xv

1-4

Internal ports 1-66

VC12-xv

1-63


VC4-xv

5-8

For N1IDQ1A and N1IDL4A boards:

Issue 03 (2013-02-20)

Port Number

Binding Level

Path Number

Internal ports 1-94

VC4-xv

1-4

Internal ports 1-94

VC12-xv

1-189


VC4-xv

5-8


776




A.15.5 Port Type (ATM Port Management) Description The Port Type (ATM Port Management) parameter specifies ATM ports, which are classified into UNI and NNI ATM ports. The maximum number of VPI bits in a cell header for a UNI port is different from that for a NNI port.


Values Valid Value

Default Value

UNI, NNI

UNI


Description

UNI

The maximum number of VPI bits is 8.

NNI

The maximum number of VPI bits is 12.

Configuration Guidelines If the number of VPIs received at a port is large (for example, greater than 255), select NNI to increase the number of VPI bits. As a result, more VPIs are available.


A.15.6 Max. VPI Bits Description The Max. VPI Bits parameter specifies the maximum number of available VPIs at a port.

Issue 03 (2013-02-20)


777



Impact on the System The number of VPI bits determines the number of available VPIs. It shows the number of available VPIs at a port. This number can be increased or decreased, depending on the VPIs required at the port.

Values Value Range

Default Value

Unit

UNI port: 1-8

8

bits

NNI port: 1-12

NOTE

The IDQ1A and IDL4A boards do not support this parameter.

Configuration Guidelines Max. VPI Bits refers to the number of bits in the valid VPI fields in a cell header that a port supports. The VPI value and the value of Max. VPI Bits have the following relationship: VPI = 2Bits-1.

Relationship with Other Parameters This parameter is invalid if a service connection is set up at the port.

A.15.7 Max. VCI Bits Description The Max. VCI Bits parameter specifies the maximum number of available virtual channel identifiers (VCIs) at a port.

Impact on the System The number of VCI bits specifies the number of available VCIs. It shows the number of available VCIs at a port. This number can be increased or decreased, depending on the VCIs required at the port.

Values Value Range

Default Value

Unit

6-16

7

bits

NOTE

The IDQ1A and IDL4A boards do not support this parameter.

Issue 03 (2013-02-20)


778



Configuration Guidelines Max. VCI Bits refers to the number of bits in the valid VCI fields in the cell header that a port supports. The VCI value and the value of Max. VCI Bits have the following relationship: VCI = 2Bits-1.

Relationship with Other Parameters This parameter is invalid if a service connection is set up at the port.

A.15.8 Max. VPC Description The Max. VPC parameter specifies the maximum number of permanent virtual paths (PVPs) that can be set up at a port.


Values Value Range

Default Value

Unit

0-4096

224

Piece

NOTE

The N1IDQ1A and N1IDL4A boards do not support this parameter.



A.15.9 Max. VCC Description The Max. VCC parameter specifies the maximum number of permanent virtual connections (PVCs) that can be set up at a port.



779



Values Value Range

Default Value

Unit

1-8192

3072

Piece

NOTE




A.15.10 VPC Configured Description The VPC Configured parameter specifies the number of permanent virtual paths (PVPs) that have been set up at a port.


Values Board Name

Value Range

Default Value

Unit

N1IDQ1A, N1IDL4A

0-4000

0

Number

N1ADQ1, N1ADL4, N1IDQ1, N1IDL4

0-4096

0

Number

For example, two PVPs have been set up and activated at internal port 1. In this case, the number of configured VPCs is 2.




780



A.15.11 VCC Configured Description The VCC Configured parameter specifies the number of PVCs that have been set up at a port.


Values Value Range

Default Value

Unit

0-8192

0

Number

For example, two PVCs have been set up and activated at internal port 1. In this case, the number of configured VCCs is 2.



A.15.12 Number of VPI that Supports VCC Description The Number of VPI that Supports VCC parameter specifies the number of VPIs supporting PVCs at a port. That is, only the VPIs specified by this parameter can be used to set up VC connections, regardless of the number of VPI bits. Other VPIs can be used to set up only VP connections.

Impact on the System Because this parameter specifies the number of VPIs that can be used to set up VC connections, the system resource allocation is affected. Therefore, set this parameter based on the actual service configurations.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

Unit


32

Number


781



NOTE


Configuration Guidelines Set this parameter based on the number of VCIs required for each VPI at each port. For example, if 50 PVCs need to be set up at a port and the VPI is different for each PVC, 50 VPIs are required to differentiate the PVCs. In this case, set the number of VPIs that support VC label switching to 50.

Relationship with Other Parameters This parameter is invalid if a service connection is set up at the port. The value of the Number of VPI that Supports VCC parameter must be smaller than the number of VPIs derived from the MAX. VPI Bits parameter.

A.15.13 UPC/NPC Enabled/Disabled Description The UPC/NPC Enabled/Disabled parameter specifies user parameter control or network parameter control. It indicates whether to enable the flow control function, namely, whether the flow parameters for the connection are valid.

Impact on the System Other service connections at the same port may be affected. For example, a VC-4 port (total bandwidth of 353207 cells/s) involves two connections: variable bit rate (VBR) service and unspecified bit rate (UBR) service. The peak cell rate (PCR) of the VBR service is set to 100000 cells/s, and the UPC/NPC function is enabled. If the transmission rate of the UBR service connection is 253207 cells/s, and if the UPC/NPC function is enabled, the VBR service flow does not exceed the rate of 100000 cells/s. If the VBR service flow exceeds the rate of 100000 cells/s, the excessive cells are discarded. If the UPC/NPC function is disabled, the VBR service is not limited. In this case, the VBR service flow can exceed the rate of 100000 cells/s. The excessive cells preempt the bandwidth of the UBR service, because the VBR service is of higher priority. Consequently, the UBR service cells are discarded.

Values Valid Values

Default Value

Enabled, Disabled

Enabled


Issue 03 (2013-02-20)


782



Value

Description

Enabled

The flow parameters are valid. In this case, the system controls the flow based on the flow parameters, for example, discarding cells or labeling cells.

Disabled

The flow parameters are invalid, except for PCR of the CBR service. In this case, the system provides the guaranteed bandwidth. Moreover, the system grooms the unguaranteed services based on the service priority.

Configuration Guidelines The value is not limited. Instead, it is selected according to the networking environment and the application scenario. Generally, select Enabled for important voice services and signaling services if the flow needs to be strictly controlled. Select Disabled for connectionless services if service burst and grooming are allowed.

A.15.14 Positive UPC/NPC(ATM Service Management) Description The Positive UPC/NPC parameter specifies whether the flow control function is enabled and whether the flow parameters used for setting up a connection function. UPC and NPC stand for user parameter control/network parameter control respectively.

Impact on the System The setting of this parameter for one service connection affects other service connections on the same port. For example, a VC-4 port (with a total bandwidth of 353207 cells/s) has two connections, namely, a VBR service and a UBR service. The PCR of the VBR service is set to 100000 cells/s, and the UPC/NPC function is enabled. If the transmission rate of the UBR service is 253207 cells/s, the rate of the VBR service traffic cannot exceed 100000 cells/s because the UPC/NPC function is enabled. If the rate of the VBR service exceeds 100000 cells/s, the excessive cells are discarded. If the UPC/NPC function is disabled, the VBR service is not limited. In this case, the rate of the VBR service can exceed 100000 cells/s. The excessive cells preempt the bandwidth of the UBR service because the VBR service is of a higher priority. Consequently, the UBR service cells are discarded.

Values Valid Value

Default Value

Enable, Disable

Enable


Issue 03 (2013-02-20)


783



Value

Description

Enable

Indicates that the flow parameters function. In this case, the system controls the flow based on the flow parameters. For example, the system discards cells or labels cells.

Disable

Indicates that the flow parameters does not function. In this case, the system provides the guaranteed bandwidth and schedules the unguaranteed services based on the service priority.

Configuration Guidelines Select a proper value according to the networking environment and application scenario. Generally, set this parameter to Enable for services that require strict flow control. Set this parameter to Disable for services that allow service burst and grooming.

A.15.15 ID (ATM Traffic Management) Description The ID (ATM Traffic Management) parameter specifies a traffic ID. An ID is allocated for each type of traffic.

Impact on the System The value of this parameter is automatically allocated on the U2000. When an ATM connection is configured, services may be discarded or interrupted if the services are allocated with an incorrect ID. The ID is service-specific. For example, when wireless base stations are interconnected, a voice service from the opposite station is of the CBR type. If the UBR service type is selected to set up the connection, some calls may be dropped in case of heavy traffic. The bandwidth is guaranteed for CBR services, but not for UBR services.

Values Value Range

Default Value

1-2048

-

Description This parameter is related to the number of created connections. When a connection is created, a traffic is added to the traffic list. To set up a connection, you can either select a created connection from the ATM traffic table, or input the traffic ID for the created connection.

Configuration Guidelines Select a traffic type required for the connection from the ATM traffic table. Issue 03 (2013-02-20)


784



Relationship with Other Parameters This parameter is valid only when an ATM traffic is created.

A.15.16 Traffic Type (ATM Traffic Management) Description The Traffic Type (ATM Traffic Management) parameter specifies sub-types of a service type. Each service has multiple traffic types. The traffic type specifies the traffic parameters that can be set, for example, processing the cells whose priority is 0 or 1 in different ways, and whether to enable the labeling function.

Impact on the System If this parameter is incorrectly set, some packets may be discarded. Traffic parameters depend on the traffic type. Use the CBR service as an example. The CBR service has two traffic types: NoClpNoScr and NoClpNoScrCdvt. For the NoClpNoScr CBR service, only PCR can be set. For the NoClpNoScrCdvt CBR service, both PCR and CDTV can be set. In practical applications, if there is a small amount of service at a rate higher than the PCR, all excessive cells are discarded for the NoClpNoScr CBR service. Consequently, the service is transiently interrupted. For the NoClpNoScrCdvt CBR service, a buffer space is allocated. When a transient burst event occurs, the cells are not discarded.

Values The following table lists the available traffic types for each service type. Service Type

Traffic Type

Default Value

CBR

l NoClpNoScr

NoClpNoScr

l ClpNoTaggingNoScr l ClpTaggingNoScr l ClpTransparentNoScr l NoClpNoScrCdvt rt-VBR

l ClpTransparentScr

ClpTransparentScr

l NoClpScrCdvt l ClpNoTaggingScrCdvt l ClpTaggingScrCdvt nrt-VBR

l NoClpScr

NoClpScr

l ClpNoTaggingScr l ClpTaggingScr UBR

l NoTrafficDescriptor

NoTrafficDescriptor

l NoClpNoScr l NoClpTaggingNoScr l NoClpNoScrCdvt Issue 03 (2013-02-20)


785



Service Type

Traffic Type

Default Value

UBR+

l NoTrafficDescriptorMcr

NoTrafficDescriptorMcr

l NoClpMcr l NoClpMcrCdvt

Configuration Guidelines For CBR services: Traffic Type

CDVT

Process ing Cells with CLP of 0 and 1 in Differe nt Ways

Labelin g Cells

PCR

MCR

MBS

SCR

NoClpN oScr

Not supporte d

No

No

Not supporte d

Not supporte d

Not supporte d

Not supporte d

ClpNoT aggingN oScr

Not supporte d

Yes

No

Not supporte d

Not supporte d

Not supporte d

Not supporte d

ClpTagg ingNoSc r

Not supporte d

Yes

Yes

Not supporte d

Not supporte d

Not supporte d

Not supporte d

ClpTran sparentN oScr

Supporte d

No

No

Not supporte d

Not supporte d

Not supporte d

Not supporte d

NoClpN oScrCdv t

Supporte d

No

No

Not supporte d

Not supporte d

Not supporte d

Not supporte d

For rt-VBR services:

Issue 03 (2013-02-20)


786



Traffic Type

CDVT


Labelin g Cells

PCR

MCR

MBS

SCR

ClpTrans parentSc r

Supporte d

No

No

Supporte d

Not supporte d

Supporte d

Supporte d

NoClpSc rCdvt

Supporte d

No

No

Supporte d

Not supporte d

Supporte d

Supporte d

ClpNoTa ggingScr Cdvt

Supporte d

Yes

No

Supporte d

Not supporte d

Supporte d

Supporte d

ClpTaggingScrC dvt

Supporte d

Yes

Yes

Supporte d

Not supporte d

Supporte d

Supporte d

For nrt-VBR services: Traffic Type

CDVT


Labelin g Cells

PCR

MCR

MBS

SCR

NoClpSc r

Not supporte d

No

No

Supporte d

Not supporte d

Supporte d

Supporte d

ClpNoTa ggingScr

Not supporte d

Yes

No

Supporte d

Not supporte d

Supporte d

Supporte d

ClpTaggi ngScr

Not supporte d

Yes

Yes

Supporte d

Not supporte d

Supporte d

Supporte d

For UBR services:

Issue 03 (2013-02-20)


787



Traffic Type

CDVT

Processing Cells with CLP of 0 and 1 in Different Ways

Labeli ng Cells

PCR

MCR

MBS

SCR

NoTraff icDescri ptor

Not supporte d

No

No

Not supporte d

Not supporte d

Not supporte d

Not supporte d

NoClpN oScr

Not supporte d

No

No

Support ed

Not supporte d

Not supporte d

Not supporte d

NoClpT aggingN oScr

Support ed

Yes

Yes

Support ed

Not supporte d

Not supporte d

Not supporte d

NoClpN oScrCd vt

Support ed

No

No

Support ed

Not supporte d

Not supporte d

Not supporte d

For UBR+ services: Traffic Type

CDVT

Labeli ng Cells

Processin g Cells with CLP of 0 and 1 in Different Ways

PCR

hether to Suppor t MCR

MBS

SCR

NoTraffi cDescrip torMcr

Not supporte d

No

No

Not supporte d

Support ed

Not supporte d

Not supporte d

NoClpM cr

Not supporte d

No

No

Support ed

Support ed

Not supporte d

Not supporte d

NoClpM crCdvt

Support ed

No

No

Support ed

Support ed

Not supporte d

Not supporte d

Note: Cell labeling means that setting the cell loss priority (CLP) of the cells that do not meet the traffic parameters to 1. In case of network congestion, the cells with CLP of 1 are first discarded. Select a service type based on the network type and service configurations.

Issue 03 (2013-02-20)


788



NOTE

Only the IDQ1A and IDL4A boards support UBR+ services.

Relationship with Other Parameters This parameter is valid only when the Service Type parameter is set.

A.15.17 Service Type (ATM Traffic Management) Description The Service Type (ATM Traffic Management) parameter specifies a service type provided by the ATM technology. Available service types are CBR services, rt-VBR services, nrt-VBR services, UBR services, and UBR+ services. The services of different types differ from each other in the reserved bandwidth, service priority, and transmission delay.

Impact on the System If this parameter is set incorrectly, services may be unavailable, or the cells may be discarded. For example, when a mobile phone makes a call, the call request signal is important and needs to be transmitted in the most reliable CBR service. In such a case, if the UBR service is selected, the call may fail to be connected during the peak hours. For application scenarios for each service type, see "Values" and "Configuration Guidelines" in this topic.

Values Valid Value

Default Value

CBR, rt-VBR, nrt-VBR, UBR, UBR+

-

NOTE

Only the IDQ1A and IDL4A boards support UBR+ services.


Description

CBR

Indicates the constant bit rate. On the user side (namely, for the service applicant), the CBR service is sensitive to the delay variation of the service data flow. For this reason, the network is required to transmit data at a constant rate. On the network side (namely, for the service provider), the CBR service must be allocated with a fixed static bandwidth within the connection period. Moreover, the CBR service must be of the highest priority. The CBR service features stable service data flow. On the user side, data is transmitted periodically at a constant rate. The service burst event seldom occurs. The circuit emulation service and the voice service are typical examples. When applying for the CBR service from the network side, you must specify the PCR parameter.

Issue 03 (2013-02-20)


789


Value

Description

rt-VBR

Indicates the real-time variable bit rate.


The rt-VBR service is sensitive to the delay and delay variation of the data flow. The voice and interactive video services are the typical applications, which are similar to the CBR service. Some burst events are allowed for the rt-VBR service. At different time segments, the data rate may be different at the source end. Moreover, static bandwidth is not allowed for the rt-VBR service on the network side (namely, the service provider). Instead, the rt-VBR service runs in statistical multiplexing mode. When applying for the rt-VBR service from the network side, you must specify the parameters such as peak cell rate (PCR), sustainable cell rate (SCR), maximum burst size (MBS), and cell delay variation tolerance (CDVT). Indicates the non-real-time variable bit rate.

nrt-VBR

Compared with the rt-VBR service, the nrt-VBR service has lower requirements for the real-time feature and it has lower priority than the rt-VBR service when service data is processed on the network side. The other features, such as burstness, statistical multiplexing, and service parameters, are almost the same as those of the rt-VBR service. Indicates the unspecified bit rate.

UBR

The UBR service is also applicable to the scenarios where realtimeness and burst events are not highly required. You can require only the best effort of the network side to provide the service. When applying for the UBR service, you do not need to specify the service quality parameters. The network side does not guarantee the UBR service. In the case of network congestion, the UBR cells are discarded first. Services such as FTP and E-mail are the typical applications of the UBR service. The UBR+ service supports the setting of the MCR parameter. There are UBR+ services on many NodeBs. The UBR+ services are configured with the MCR. When the service rate does not exceed the configured MCR, the normal service transmission is ensured. The features of the UBR+ service other than the MCR are the same as the features of the UBR service.

UBR+

Configuration Guidelines Each service has its application scenario. Moreover, the service may be affected because of the network environment and the interconnected equipment. The following table lists application scenarios for each service type.

Issue 03 (2013-02-20)


790



ATM Service

Service Category

Service Type

Application

CBR

Category A

Voice service

Conference call Audio transmission (broadcast) Audio library Voice mails

Video

Video conference call Video transmission Video on demand

rt-VBR

Category B

Voice service

Voice mails Conference calls based on voice packets

Video

Visual graph and text NTSC TV HDTV TV

nrt-VBR

Category C

Data

Air interface reservation Banking service Frame relay network interconnection

UBR

Category C or D

Data

E-mail service File transmission Database browse Remote terminal access

UBR+

Category C or D

Data

E-mail service File transmission Database browsing Remote terminal access


Issue 03 (2013-02-20)


791



A.15.18 PCR (ATM Traffic Management) Description The PCR (ATM Traffic Management) parameter specifies the peak cell rate (PCR), which indicates the upper threshold of the service rate. That is, if the specified PCR threshold is exceeded because the service rate bursts for a long time, excessive packets are discarded.

Impact on the System If this parameter is set improperly, some cells may be discarded. For example, a wireless base station accesses a voice service, and the CBR service is selected to set up the connection. In such a case, a correct PCR setting is important. If this parameter is set to a small value, the bandwidth is not enough. Calls may fail to be set up and the service is unavailable. If this parameter is set to a large value, other voice services may fail to use the available bandwidth, and some cells are discarded. Consequently, some calls are interrupted.

Values For N1IDQ1A and N1IDL4A boards: Value Range

Default Value

Unit

5-1412828

90

cells/s

For other boards: Valid Values

Default Value

Unit

90-1412828

90

Cells/s

Configuration Guidelines Generally, set PCR according to service configurations on the interconnected equipment. Different services are used in different scenarios. The details are as follows: l

For CBR services, PCR equals the reserved bandwidth. If the UPC/NPC function is enabled, the traffic is controlled according to the PCR value. That is, the excessive packets are discarded.

l

For VBR services, if the UPC/NPC function is enabled, excessive packets are discarded when the service rate exceeds the PCR. If the UPC/NPC function is disabled, this parameter is meaningless. That is, the traffic rate can exceed the specified PCR. In such a case, PCR is set only for the reserved bandwidth computation.

l

For UBR services, the bandwidth depends on the available physical bandwidth of a port. For UBR services, PCR is set to determine the maximum rate only.

Issue 03 (2013-02-20)


792



Relationship with Other Parameters Except for PCR of CBR services, the PCR parameter is valid only when the UPC/NPC function is enabled.

A.15.19 SCR (ATM Traffic Management) Description The SCR (ATM Traffic Management) parameter specifies the sustainable cell rate (SCR). Excessive cells are labeled or discarded, depending on the traffic type.

Impact on the System If this parameter is set improperly, certain cells may be discarded or labeled. For example, SCR is set to label or discard excessive cells. The labeled cells are discarded in the case of congestion. Therefore, SCR is a mechanism of avoiding congestion. For the traffic whose cells are not labeled (see A.15.16 Traffic Type (ATM Traffic Management)), excessive cells are also discarded.

Values For N1IDQ1A and N1IDL4A boards: Value Range

Default Value

Unit

5-1412828

90

cells/s

Value Range

Default Value

Unit

90-1412828

90

cells/s

For other boards:

Configuration Guidelines Generally, set SCR based on service configurations of the interconnected equipment. Different services are deployed in different scenarios. Details are as follows: l

For CBR services, SCR does not need to be set.

l

For UBR services, SCR does not need to be set.

l

For VBR services, there are two cases as follows: – If the UPC/NPC function is enabled and the service rate exceeds the specified PCR, excessive cells are discarded or labeled. – If the UPC/NPC function is disabled, this parameter is meaningless. That is, the service rate can exceed the specified SCR. When this occurs, SCR is set to compute the reserved bandwidth only.

Issue 03 (2013-02-20)


793



Relationship with Other Parameters The SCR parameter is valid only when the UPC/NPC function is enabled.

A.15.20 MBS Description The MBS parameter specifies the maximum number of cells that can be transmitted over the connection and that burst continuously based on the peak cell rate. This parameter is set to increase the capability of a system to respond to transient cell burst events, and to enhance the anti-jitter performance of a service.

Impact on the System The parameter value affects the anti-jitter performance of a service that bursts transiently.

Values Value Range

Default Value

Unit


2

Cells

Configuration Guidelines Generally, set this parameter to a large value to prevent cells from being discarded in case of a transient burst event. The recommended value is 100000.

Relationship with Other Parameters The MBS parameter is valid only when the UPC/NPC function is enabled.

Related Information If the UPC/NPC function is enabled, this parameter allows transient burst of a service. The PCR is similar to a container at constant size. The MBS and cell delay variation tolerance (CDVT) help to increase the container size. When the transient traffic entering the container increases, the increased size of the container takes effect. If the transient traffic keeps increasing, an overflow occurs. l

If this parameter is set for the opposite equipment, set it to the same value for the local equipment.

l

If this parameter is not set for the opposite equipment, set it to the integer part of {1+L/(1/ SCR-1/PCR) } for the local equipment. Letter L indicates the CDVT, representing the maximum tolerance range for a cell to reach the destination in advance if MBS is set to an expected value.

l

If the UPC/NPC function is disabled, this parameter is meaningless.

Issue 03 (2013-02-20)


794



A.15.21 CDVT Description The CDVT parameter specifies the upper threshold of the cell sending interval. This parameter is set to increase the capability of a system to respond to transient cell burst events, and to enhance the anti-jitter performance of a service.

Impact on the System The parameter value affects the anti-jitter performance of a service that bursts transiently. l

If this parameter is set to a small value, certain cells may be discarded in case of a service burst event.

l

If this parameter is set to a large value, the system is not affected. Generally, set it to the maximum value.

Values Value Range

Default Value

Unit

0.7-1330000, in step length of 0.1

0.7

ms

Configuration Guidelines In most cases, set it to the maximum value.

Relationship with Other Parameters The CDVT parameter is valid only when the UPC/NPC function is enabled. For different service types and different traffic types, the CDVT values are different. For details, refer to A.15.16 Traffic Type (ATM Traffic Management).

Related Information Fix the PCR value of the level-1 leaky bucket, and estimate the CDVT value. After passing the level-1 leaky buckets, the data flow is of burst nature, and the average rate is the PCR. Generally, the data traffic is transmitted at intervals of PCR, 0, PCR, 0, and so on. The CDVT value needs to be set to meet the following condition: CDVT<1-424*(MBS-1) (1/SCR-1/PCR) (SCR and PCR are expressed in bit/s. 424 bits / cell = 53 bytes/cell*8 bits/byte)

A.15.22 Open Flow Frame Discarding Flag Description The Open flow frame discarding flag parameter is set for services at the AAL5 layer only. AAL5 is a frame structure at the ATM adaptation layer. In this structure, multiple ATM cells Issue 03 (2013-02-20)


795



are encapsulated into one AAL5 frame to provide functions (for example, signaling and routing) of the upper-layer services. If the AAL5 service bandwidth exceeds the bandwidth on the port or the specified bandwidth, excessive packets are discarded according to the AAL5 data frame. One AAL5 data frame may contain multiple ATM cells.

Impact on the System Other AAL-layer services may be interrupted. For example, if the traffic of other services (such as AAL0 services or AAL2 services) exceeds the bandwidth on the port or the specified bandwidth, the system may discard all the cells because it fails to find the frame trailer of the AAL5 service. Although the service traffic is restored normally, the services cannot be restored.

Values Valid Values

Default Value

Yes, No

No

Configuration Guidelines Select Yes or No based on the encapsulation type at the ATM adaptation layer. Generally, select No. Enable this flag only when the service is at the AAL5 layer. If any service at other adaptation layers is available, do not enable this flag.


A.15.23 Positive Traffic Descriptor Description The Positive Traffic Description parameter specifies the flow used by an ATM connection, in the aspects of service type, flow type, settings of the relevant parameters (PCR, SCR, MBS, and CDVT), and flow frame discarding flag.

Impact on the System Improper setting of this parameter may result in a service loss or service interruption. Different service types are used in different scenarios. Assume that the equipment is interconnected with Node B. If the voice service transmitted from the opposite equipment is of the CBR type and the service created on the local equipment is of the UBR type, the call may drop during traffic peak hours. This is because that the bandwidth for the CBR service is fully guaranteed whereas the bandwidth for a UBR service is not guaranteed. Issue 03 (2013-02-20)


796



Values Value Range

Default Value

1-2048

-

Configuration Guidelines This parameter depends on the created flow. When a flow is created, it is added to the flow table. To set up a connection, you can select a created flow from the flow table, or enter the ID of the created flow.

Relationship with Other Parameters This parameter is valid only when the ATM flow is created.

A.15.24 Connection ID (ATM Service Management) Description The Connection ID (ATM Service Management) parameter specifies IDs of the working and protection links in a protection group.


Values For IDQ1A/IDL4A boards: Value Range

Default Value

1-32768

-

For other boards: Value Range

Default Value

1-8192

-

Configuration Guidelines Set this parameter to a value within the value range.



797



A.15.25 Connection Type (ATM Service Management) Description The Connection Type (ATM Service Management) parameter specifies whether the setup connection is a PVP or a PVC. Each PVC transmits services that are marked with unique VPI and VCI only. Each PVP transmits all services with the same VPI over the connection. That is, the connection transmits all services with different VCIs over the connection with the same VPI, regardless of VCI.


Values Valid Value

Default Value

PVP, PVC

PVC


Description

PVP

Each PVP transmits all services marked with VCI with the same VPI over the connection.

PVC

Each PVC transmits services marked with unique VPI and VCI only.

Configuration Guidelines To converge services of the same VPI at a port, select PVP. To transmit services marked with unique VPI and VCI only, select PVC. As shown in Figure A-21, PVC and PVP are both virtual transmission paths. PVC is, however, contained in PVP. A PVC is a channel, but a PVP is a path. PVCs in the PVP are used to transmit services. Figure A-21 Relation between PVC and PVP

Issue 03 (2013-02-20)


798



A.15.26 Spread Type (ATM Service Management) Description The Spread Type (ATM Service Management) parameter specifies the spread type of the setup connections, including unicast connection (p2p), multicast root connection (p2mpRoot), and multicast leaf connection (p2mpLeaf).


Values Board Name

Valid Value

Default Value

N1IDQ1A, N1IDL4A

p2p

p2p

N1ADL4, N1DQ1, N1IDL4, N1IDQ1

p2p, p2mpRoot, p2mpLeaf

p2p


Description

p2p

Provides an end-to-end connection from one port to another port.

p2mpRoot

Provides a root connection for multicast services from one point to multiple points. The branches of the root connection are the leaf connections, for example, the black lines shown in the figure.

IDQ1

VCTRUNK

VCTRUNK

MAC Port

VCTRUNK

VCTRUNK

VCTRUNK

Issue 03 (2013-02-20)


799



Value

Description

p2mpLeaf

Provides leaf connections for p2mp multicast services. The leaf nodes are multicast over the root connection, for example, the blue lines shown in the figure.

Configuration Guidelines The p2p connection is used for communication from a segment to an end, for example, phone calls and Internet access services. The p2mpRoot and p2mpLeaf connections are used for multicast communication, for example, IPTV services and broadcast services. A unicast service is a bidirectional service, but a multicast service is a unidirectional service. The application scenarios are respectively described in Figure A-22and Figure A-23. Figure A-22 Multicast service

Issue 03 (2013-02-20)


800



Figure A-23 Unicast service

p2p: To set up a point-to-point bidirectional connection, select p2p. p2mpRoot: To set up a p2mp unidirectional multicast connection, set up a root connection for multicast services. In this case, select p2mpRoot. p2mpLeaf: To set up a p2mp unidirectional multicast connection, and to set up leaf connections for multicast services after the root connection is set up, select p2mpLeaf.

Related Information To set up a multicast connection, set up a root connection for multicast services, and then set up multiple leaf connections that have the same source but different sinks. These leaf connections are multicast to different ports (spatial multicast) or the same port (logical multicast). A multicast service is a unidirectional service.

A.15.27 VPI and VCI (ATM Service Management) Description The VPI and VCI (ATM Service Management) parameter indicates virtual path identity and virtual channel identity, which are used to respectively identify virtual paths and virtual channels inside a virtual path. A VPI and a VCI are used to identify a virtual connection. VPI and VCI in the cell header constitute routing information of a cell.

Impact on the System If this parameter is set improperly, services may be unavailable. Figure A-24 shows an example.

Issue 03 (2013-02-20)


801



Figure A-24 Schematic diagram of an example VPI=76 VCI=19,26,39

VPI in 76

VPC ATM Node1

VPI=69 VCI=34,48

VPL

VPI out 53

VPI=53 VCI=19,26,39

VPL

VPI=76 VCI=19,26,39 ATM Node3

VPI in 53

VPI out 76

IN OUT VPI-69 VPI-77 VCI-34 VCI-22 VCI-48 VCI-26

VCC

VPI=77 VCI=22,26

ATM Node2

VPI in 77 22

VPI out 31 33

VPI=31

The sink VPI/VCI of ATM Node1 must be the same as the source VPI/VCI of ATM Node2. (VPI = 77, VCI = 22, 26). Otherwise, ATM Node2 may fail to identify the data (VPI in the cell header is not 53. Alternatively, VCI in the cell header is not 22 or 26) received from ATM Node1. ATM Node2 can identify the cells whose VPI is 77 and whose VCI is 22 or 26 only. In other words, a service between different nodes is transmitted on the basis of the same VPI and VCI.

Values

Issue 03 (2013-02-20)

Parameter Value

Value Range

Default Value

VPI

0-4095

-

Description Switches VPI labels between nodes. Note that values 0-4095 are subject to the maximum configuration. By default, set this parameter to a value ranging from 0 to 255. You can adjust the value range by setting Port Type and Max. VPI Bits. Port resources are specified. If this parameter is set to a large value for a port, set it to a small value for other ports. For the configuration method, refer to Relationship with Other Parameters in this topic.


802



Parameter Value

Value Range

Default Value

VCI

32-65535

-

Description Switches VCI labels between nodes. Note that values 32-65535 are subject to the maximum configuration. By default, set this parameter to a value ranging from 32 to 127 (Max. VCI Bits is 7 bits). You can adjust the value range by setting Max. VCI Bits. Port resources are specified. If this parameter is set to a large value for a port, set it to a small value for other ports. For the configuration method, refer to Relationship with Other Parameters in this topic.

NOTE

For the N1IDQ1A or N1IDL4A board, the value range of the VPI parameter is not determined by setting the Max. VPI Bits parameter. Instead, the actual value range of the VPI parameter is determined by setting it to a specific value range (for example, from 1 to 1000). The value of the VCI parameter ranges from 32 to 65535, and this value range cannot be modified.

Configuration Guidelines This parameter identifies connections only regardless of requirements. Note that the specified VPI must be consistent with the VPI of the downstream or upstream service on the node to ensure that the labels are switched correctly in the case of multipoint transmission. An example is shown in Impact on the System in this topic.

Relationship with Other Parameters The VPI value range depends on Port Type and Max. VPI Bits. l

If Port Type is set to UNI, Max. VPI Bits of the port can be set to 8 only. In this case, set VPI to a value ranging from 0 to 255.

l

If Port Type is set to NNI, Max. VPI Bits of the port can be set to 12. In this case, set VPI to a value ranging from 0 to 4095.

The VCI value range depends on Max. VCI Bits of the port. l

If the value of Max. VCI Bits is increased, set VCI to a larger value range.

l

If Max. VCI Bits is set to 16, set VCI to a value ranging from 32 to 65535.

A.15.28 Positive Service Status(ATM Service Management) Description The Positive Service Status parameter indicates the current status of a positive ATM service. Positive refers to the direction from the source to the sink of an ATM connection.

Issue 03 (2013-02-20)


803



Impact on the System When this parameter is set to Up, the ATM service is normal. Otherwise, the service is interrupted.

Values Valid Value

Default Value

Up, Down

Up


Description

Up

Indicates that the service is normal.

Down

Indicates that the service is interrupted.

Configuration Guidelines There are no specific principles for setting this parameter because it is used for querying.

A.15.29 Positive Service Failure Reason(ATM Service Management) Description The Positive Service Failure Reason parameter indicates the cause of a positive service failure. Positive refers to the direction from the source to the sink of an ATM connection.

Impact on the System When this parameter is set to OK, the service is normal. Otherwise, the service is interrupted.

Values Valid Value

Default Value

OK, LCD, AIS, CCLOC

OK


Issue 03 (2013-02-20)

Value

Description

OK

Indicates that the positive service is normal. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

804



Value

Description

CCLOC

Indicates that the service is interrupted because the user cell or the CC cell is not received within a period ranging from 3s to 4s after the CC sink is configured.

AIS

Indicates that the positive service is interrupted because AIS signals are received.

LCD

Indicates that the positive service is interrupted because LCD is received.

Configuration Guidelines There are no specific principles for setting this parameter because this parameter is used for querying.

A.15.30 Source/Sink Switching Cause Description The Source/Sink Switching Cause parameter specifies a condition that triggers switching of an ATM protection pair.


Values Valid Value

Default Value

Idle, Protection Route Signal Fail, Working Route SF, Non-Revertive, Wait-To-Restore, Manual to Active, Manual to Standby, Freeze, Lockout, Force to Standby

Idle


Issue 03 (2013-02-20)

Value

Description

Idle

Indicates that the working channel and the protection pair are normal.

Protection Route Signal Fail

Indicates that a failure in the working channel triggers switching.

Working Route SF

Indicates that the protection channel fails but switching does not occur.

Force to Standby

Indicates that services are manually switched from the working channel to the protection channel when both channels are normal.


805



Value

Description

Non-Revertive

Indicates that the working channel is restored to normal and the protection channel remains normal. The protection group is in nonrevertive mode.

Wait-To-Restore

Indicates that the working channel is restored to normal and the protection channel remains normal. The protection group is in revertive mode. In this case, services are waiting to be restored to the working channel. The duration of the waiting time is determined by the restoration time of the working channel.

Manual to Active

Indicates that services are switched from the protection channel to the working channel.

Manual to Standby

Indicates that services are switched from the working channel to the protection channel.

Freeze

Indicates that the status of the protection pair is frozen.

Lockout

Indicates the protection lockout of the protection pair.

Configuration Guidelines This parameter is used for querying.

A.15.31 Protection Type (ATM Service Management) Description The Protection Type (ATM Service Management) parameter specifies whether an ATM connection is configured with 1+1 or 1:1 protection.


Values For IDQ1A/IDL4A boards: Valid Value

Default Value

1:1

1:1

For other boards:

Issue 03 (2013-02-20)

Valid Value

Default Value

1+1, 1:1

1+1 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

806



Configuration Guidelines Select a value according to the protection type specified by users.


Related Information 1+1 protection: Uses the dual-fed and selective receiving mechanism. Figure A-25 shows the normal status. Figure A-25 Normal status

Working entity Service data Protection entity

Source node protection domain

Destination node protection domain

Figure A-26 shows the switching status. Figure A-26 Switching status




1:1 Protection: Adopts the redundant connection protection mechanism. Figure A-27 shows the normal status. Figure A-27 Normal status

Working service data Extra service data

Issue 03 (2013-02-20)

Working entity Protection entity


807




Working entity Working service data Extra service data

Protection entity

A.15.32 Switching Direction (ATM Service Management) Description The Switching Direction (ATM Service Management) parameter specifies whether the switching occurs at one end (source or sink), or at both ends (namely, both the source and sink ends) simultaneously.


Values Valid Value

Default Value

Source + Sink, Source, Sink

Sink


If two P2P ATM connections have the same source but different sinks, select Sink.

l

If two P2P ATM connections have the same sink but different sources, select Source.

l

If two P2P ATM connections have different sources and sinks, select Source + Sink.


A.15.33 Switching Status (ATM Service Management) Description The Switching Status (ATM Service Management) parameter specifies the status of an ATM protection group. It identifies whether switching occurs or whether the protection protocol stops.



808



Values Valid Value

Default Value

Stop, Normal, Switch

-


Description

Stop

Indicates that the protection protocol stops or the protection pair is not added.

Normal

Indicates the normal status.

Switch

Indicates the switching status.



A.15.34 Switching Type (ATM Service Management) Description The Switching Type (ATM Service Management) parameter specifies whether a bidirectional ATM connection is switched at both ends when a protection switching event occurs.


Values Valid Value

Default Value

Single-Ended, Dual End

Single-Ended

Configuration Guidelines Select a proper value according to the protection type specified by users. Issue 03 (2013-02-20)


809




Related Information The 1+1 protection is used as an example to describe differences between single-ended protection and dual-ended protection. In single-ended protection, if the working link fails in one direction, services are switched from the working link to the protection link only in this direction. Switching does not occur in another direction. Figure A-29 shows the normal status. Figure A-29 Normal status








Dual-ended protection means that a switching event occurs automatically in another direction if it occurs in one direction. In this case, a bidirectional service is completely switched to the protection link. Figure A-31 shows the normal status. Figure A-31 Normal status

Working service data Extra service data

Issue 03 (2013-02-20)

Working entity Protection entity


810




Working entity Working service data Extra service data

Protection entity

A.15.35 Revertive Mode (ATM Service Management) Description The Revertive Mode (ATM Service Management) parameter specifies whether a service is switched to the original working link after the working link is restored to normal.


Values Valid Value

Default Value

Revertive, Non-Revertive

Revertive

Configuration Guidelines Select a proper value, depending on whether the ATM service needs to be switched to the original working link.


A.15.36 Pause Time(0-100) *100 ms (ATM Service Management) Description The Pause Time(0-100) *100 ms (ATM Service Management) parameter specifies the period from the time when a fault is detected to the time when switching occurs in the ATM protection group. It is used for ATM protection. If a link is restored to normal within the hold-off time, switching does not occur.



811



Values Value Range

Default Value

Unit

(0-100)*100, in step length of 1

100

ms

Configuration Guidelines Select a proper value according to requirements.


A.15.37 WTR Time(0-30min) (ATM Service Management) Description The WTR Time(0-30min) (ATM Service Management) parameter specifies the period from the time when the original working link is restored to normal to the time when services are switched from the protection link back to the original working link.


Values Value Range

Default Value

Unit


12

min

Configuration Guidelines Set this parameter properly based on the actual network conditions.

Relationship with Other Parameters This parameter is valid only when A.15.35 Revertive Mode (ATM Service Management) is set to Revertive.

A.15.38 External Command (ATM Protection Group) Description The External Command (ATM Protection Group) parameter specifies the external command operations in 1+1 or 1:1 protection switching of ATM connections. Issue 03 (2013-02-20)


812



Impact on the System The switching state may be changed. Moreover, some cells may be discarded in the switching process.

Values Value Range

Default Value

Clear, Freeze, Lockout of Protection, Force to Standby, Manual to Active, Manual to Standby, Stop Protection Controller, Start Protection Controller

Clear


Description

Clear

Clears all the external commands.

Freeze

Freezes the protection group. After the Freeze command is issued, the protection group keeps the current state, which is not changed any more.

Lockout of Protection

Locks the protection connection. That is, forcibly switches to the working connection.

Force to Standby

Forcibly switches to the protection connection.

Manual to Active

Manually switches to the working connection.

Manual to Standby

Manually switches to the protection connection.

Stop Protection Controller

Disables the functions of the protection controller.

Start Protection Controller

Enables the functions of the protection controller.

Configuration Guidelines Select the value according to the switching operation to be performed.

Relationship with Other Parameters This parameter is valid only after the protection group is added.

A.15.39 IMA Group Number Description The IMA Group Number parameter specifies that each IMA group is allocated with a unique number for identification. To query the IMA group status and link status, set this parameter. Issue 03 (2013-02-20)


813




Values IDQ1A/IDL4A: Value Range

Default Value

1-93

-

IDQ1/IDL4: Value Range

Default Value

1-32

-

Configuration Guidelines When you create IMA groups, the IMA group number is automatically allocated by the U2000. The number of IMA groups for the IDQ1 or IDL4 cannot be more than 16, and the number of IMA groups for the IDQ1A or IDL4A cannot be more than 93.


A.15.40 IMA Protocol Version Description The IMA Protocol Version parameter specifies the version number of the IMA protocol adopted at the local end. The IMA protocol has two versions: IMA1.0 and IMA1.1.

Impact on the System The IMA protocol version of the interconnected equipment must be consistent. Otherwise, the IMA service may fail to interwork.

Values

Issue 03 (2013-02-20)

Valid Values

Default Value

1.0, 1.1

1.1


814



Configuration Guidelines The IMA protocol version for the interconnected equipment should be consistent at the two ends.


A.15.41 IMA Transmit Frame Length Description The IMA Transmit Frame Length parameter specifies the length of one IMA frame transmitted by the local equipment. That is, how many ATM cells are contained in one IMA frame. An IMA frame can contain 32, 64, 128 or 256 ATM cells. Moreover, each IMA frame contains an IMA control protocol cell (ICP), which is used to negotiate the IMA protocol and to transmit information.

Impact on the System If the value of IMA Transmit Frame Length for the interconnected equipment at one end is inconsistent with that at another end, the IMA negotiation may fail.

Values Valid Values

Default Value

32, 64, 128, 256

128

Configuration Guidelines IMA Transmit Frame Length should be consistent with that of the interconnected board.


A.15.42 IMA Group Configuration Mode Description The IIMA Group Configuration Mode parameter specifies the configuration and working modes of the links in an IMA group. These configuration and working modes are Symmetrical Mode and Symmetrical Operation, Symmetrical Mode and Asymmetrical Operation and Asymmetrical Mode and Asymmetrical Operation.

Impact on the System The configuration decides whether an IMA link is of unidirectional conductivity. For examples, see Principle of Selecting Values. Issue 03 (2013-02-20)


815



Values Valid Values

Default Value

Symmetrical Mode and Symmetrical Operation, Symmetrical Mode and Asymmetrical Operation, Asymmetrical Mode and Asymmetrical Operation



Description


Indicates that each link in an IMA group is configured to be capable of transmitting and receiving packets in two directions (namely, symmetrical mode). When the IMA group works normally, if a link is interrupted in the transmit or receive direction, it is interrupted accordingly in another direction. That is, this link is bidirectionally unavailable (this is called symmetric operation).

Symmetrical Mode and Asymmetrical Operation

Indicates that each link in an IMA group is configured to be capable of transmitting and receiving packets in two directions (namely, symmetrical mode). When the IMA group works normally, if a link is interrupted in the transmit or receive direction, it works normally in another direction. That is, this link is unidirectionally available (this is called asymmetric operation).

Asymmetrical Mode and Asymmetrical Operation

Indicates that each link in an IMA group is configured to be capable of transmitting or receiving packets only in one direction (namely, asymmetrical mode). When the IMA group works normally, if a link is interrupted in the transmit or receive direction, it works normally in another direction. That is, this link is unidirectionally available (this is called asymmetric operation).

Configuration Guidelines Select the value according to the following application scenarios. Figure A-33 shows the asymmetrical mode and symmetrical operation.

Issue 03 (2013-02-20)


816



Figure A-33 Schematic diagram of symmetrical mode and symmetrical operation

Figure A-34 shows the asymmetrical mode and asymmetrical operation. Figure A-34 Schematic diagram of symmetrical mode and asymmetrical operation

Figure A-35 shows the asymmetrical mode and asymmetrical operation.

Issue 03 (2013-02-20)


817



Figure A-35 Schematic diagram of asymmetrical mode and asymmetrical operation

If the two directions of an E1 link in the IMA group are in both transmit or both receive directions, the IMA group fails to negotiate.


A.15.43 Minimum Number of Active Links Description The Minimum Number of Active Links parameter specifies the minimum threshold of the active links required in an IMA group for normal running of the IMA group.

Impact on the System If the parameter value is set improperly, the services may be interrupted. If the number of active links in an IMA group is not less than the value of Minimum Number of Active Links, the IMA group works normally. Otherwise, the services of the IMA group are interrupted.

Values Valid Values

Default Value

0-32

0

Configuration Guidelines Set this parameter according to the minimum number of active links supported by the opposite equipment. Alternatively, set the value according to the actual capability of the services. For example, there are 10 active links, and the total bandwidth is 20 Mbit/s. In this case, the interconnected Issue 03 (2013-02-20)


818



equipment provides the bandwidth of at least 15 Mbit/s. Then set Minimum Number of Active Links to 8. If the number of links is less than 8, the bandwidth is less than 15 Mbit/s. In this case, the services of the IMA group are interrupted.

Relationship with Other Parameters This parameter is valid only after IMA Group is set.

A.15.44 IMA Group Status Description The IMA Group Status parameter specifies the status of the IMA group state machine. By referring to this state, you can diagnose the faults of the IMA group protocol.


Values Valid Values

Default Value

Not Configured, Start-Up, Start-Up-Ack, Config-Aborted, Insufficient-Links, Blocked, Operational

-


Issue 03 (2013-02-20)

Value

Description

Not Configured

Displays this state if the IMA group does not exist.

Start-Up

Displays this state if the IMA group state machine is started at the local end, and waits for being started at the opposite end.

Start-Up-Ack

This is a transitional state. After the IMA group state machine is started at the two ends, the IMA group changes to the Start-up-Ack state.

Config-Aborted

Displays this state if the parameters adopted at the local end do not match those at the opposite end.

Insufficient-Links

Displays this state if the parameters at the local end match those at the opposite end, but the link resources are insufficient.

Blocked

Indicates that the IMA group is blocked. To maintain an IMA group, you can block it.

Operational

Displays this state if the IMA group is not suppressed and the link resources are sufficient.


819





A.15.45 Protocol Mode (IMA1.0 Mode) Description The Protocol Mode parameter indicates the management mode of the IMA 1.0 protocol. The management modes of the IMA 1.0 protocol contain ITU-T mode and European mode.

Impact on the System This parameter affects the negotiation between the two ends of an IMA group. If the configurations of the two ends are different, the negotiation may fail and hence the service is affected.

Values Value Range

Default Value

ITUT Mode, European Mode

ITUT Mode


Description

ITUT Mode

Indicates that the ITU-T mode is used.

European Mode

Indicates that the European mode is used.

Configuration Guidelines The IMA 1.0 management mode cannot interwork with the IMA 1.1 management mode. Ensure that the configurations of the two ends of an IMA group are the same when you select the IMA 1.0 management mode. In addition, IMA Transmit Frame Length must be set to 128; IMA Group Configuration Mode must be set to Symmetrical Mode And Symmetrical Operation.

Issue 03 (2013-02-20)


820



A.15.46 Enable/Disable Cell Payload Scramble Description The Enable/Disable Cell Payload Scramble parameter specifies whether to scramble the payload of the cells in the E1 link.


Values Valid Values

Default Value

Enabled, Disabled

Enabled

Configuration Guidelines Select the value according to the equipment at the opposite end. Generally, select Enabled.


A.15.47 Link Frame Format Description The Link Frame Format parameter specifies whether the frames in the E1 link are in dual frame format or multiframe format.


Values Valid Values

Default Value

E1 Dual Frame, E1 CRC-4 Multiframe

E1 CRC-4 Multiframe


Issue 03 (2013-02-20)


821



Value

Description

E1 Dual Frame

Indicates that an E1 dual frame consists of ITU-T G.704 basic frames (32 bytes form one ITU-T G.704 basic frame), and its name is decided by the frame delimitation method. ITU-T G. 706 specifies the framing method of alternating E1 FAS and E1 NFAS frame flow. For this reason, an E1 dual frame is regarded as a multiframe that consists of two ITU-T G.704 basic frames. An E1 dual frame is formed for delimitation.

E1 CRC-4 Multiframe

Indicates that an E1 CRC-4 multiframe consists of 16 ITU-T G.704 basic frames. An E1 CRC-4 multiframe is defined in ITU-T G.706. It carries the CRC information and the line monitoring information. An E1 CRC-4 multiframe flow is first delimitated in dual frame format. After the dual frame is framed correctly, the CRC-4 multiframe is framed.

Configuration Guidelines Currently, E1 dual frames are almost not used. Instead, E1 CRC-4 multiframes are used in most cases. For this reason, select E1 CRC-4 Multiframe.


A.15.48 Connection Direction (ATM Segment End Attribute) Description The Connection Direction (ATM Segment End Attribute) parameter is based on one node. Figure A-36 shows the forward and backward of node B. Figure A-36 An example of connection direction

A

Forward

B

Backward

C


Issue 03 (2013-02-20)


822



Values Valid Values

Default Value

Forward, Backward

-


Description

Forward

Indicates the direction from the source port to the sink port.

Backward

Indicates the direction from the sink port to the source port.



A.15.49 Segment and End Attribute (ATM Segment End Attribute) Description The Segment and End Attribute (ATM Segment End Attribute) parameter specifies the OAM maintenance point type. For different segment and end attributes, OAM cells are processed in different segments.


Values Valid Values

Default Value

Non segment and Endpoint, Segment point, Endpoint, Segment and Endpoint



Issue 03 (2013-02-20)

Value

Description


Indicates not to terminate OAM cells.


823



Value

Description

Segment point

Indicates terminating OAM cells between two segment points only.

Endpoint

Indicates terminating OAM cells between two end points only.

Segment and Endpoint

Indicates terminating OAM cells between two segment points and between two end points.

Configuration Guidelines According to different OAM maintenance segments, as shown in Figure A-37, set the segment and end point attribute properly. Figure A-37 Schematic diagram of the maintenance segment

1

2

3

4

5

end

seg

inner

inner

seg+end

segment user1

end to end

user2

l

To maintain the entire ATM connection, select Endpoint for the two ends of the connection.

l

To maintain one segment of the entire ATM connection, select Segment point for the two ends of the segment to be maintained.

l

If the endpoint overlaps the segment point, select Segment and Endpoint.

CAUTION l For a protection link that is added into the 1+1 source or 1+1 sink protection group, do not select Segment and Endpoint. Moreover, the CC function cannot be enabled. l For a connection that is added into the protection group, do not select Segment.



824



A.15.50 LLID Description The LLID parameter specifies the loopback location. It contains 15 bytes.


Values Field

Valid Values

Default Value

Description

Country Code (Hexadecimal Code)

2 bytes

[2 bytes] 0000

Indicates the country code.

Network Code (Hexadecimal Code)

2 bytes

[2 bytes] 0000

Indicates the network code.

NE Code (Hexadecimal Code)

11 bytes

4-byte NE ID + 7byte all 0s

Indicates the NE code.

Configuration Guidelines Generally, select the default value.

Related Information Loopback Test: 1.

To start the LB test, issue a command at the initiating point.

2.

For the segment LB test, the loopback point may be the intermediate point or the segment point. Regardless of the destination LLID, the seg-LB cells are captured at the segment point. For this reason, the seg_LB test cannot be carried out across different segment points.

3.

For the end-to-end LB test, the loopback point must be the endpoint rather than the middle point. Likewise, regardless of the destination LLID, the e-t-e_LB cells are captured at the endpoint. For this reason, the e-t-e_LB test cannot also be carried out across different segment points.

LLID: Indicates the coding mode of LLID. In practice, the APC LLID can be set to any value. For the Qx or NE-board interface, the LLID can contain 16 bytes. For the U2000 server and client, the window is designed according to the second codiong mode (0x01) specified in ITU-T I.610. For this reason, you can enter 15 bytes, which consist of 2-byte country code (the default value is 0000 in the case of hexadecimal system), 2-byte network code (the default value is 0000 in the case of BCD code pattern), and 11-byte NE code (by default, the first four bytes indicate the NE ID. Enter 0 for the last seven bytes). If you set the LLID, and if the NE code is different from the NE ID, the LLID does not change although the NE ID is changed. Issue 03 (2013-02-20)


825



A.15.51 Maximum Ingress Bandwidth Description The Maximum Ingress Bandwidth parameter specifies the maximum ingress bandwidth that a port on the ATM board supports.

Impact on the System During service configuration, ensure that total bandwidth of the configured services does not exceed the value of this parameter. Otherwise, the system prompts that the verification fails. If the maximum ingress bandwidth of each optical port on the N1IDQ1 board is 353207 cell/s, the total bandwidth of the configured services at the port should not be greater than 353207 cell/s.

Values Value Range

Default Value

4528-1412828 cell/s

-

Configuration Guidelines The maximum ingress bandwidth of each external optical port on the N1IDQ1 and N1ADQ1 boards is 353207 cell/s. The maximum ingress bandwidth of each external optical port on the N1IDL4 and N1ADL4 boards is 1412828 (353207x4) cell/s. For internal ATM ports, the maximum ingress bandwidth depends on the type of the bound services and number of the services. If VCTRUNK1 is bound with two VC-12s, the maximum ingress bandwidth is 9056 (4528x2) cells/s. If VCTRUNK1 is bound with four VC-4s, the maximum ingress bandwidth is 1412828 (353207x4) cell/s. Plan properly before configuring or using a board to ensure that the ingress bandwidth of each port does not exceed the permitted value range.

A.15.52 Maximum Egress Bandwidth Description The Maximum Egress Bandwidth parameter specifies the maximum egress bandwidth that a port on the ATM board supports.

Impact on the System During service configuration, ensure that the total bandwidth of the configured services does not exceed the value of this parameter. Otherwise, the system prompts that the verification fails. If the maximum egress bandwidth of each optical port on the N1IDQ1 board is 353207 cell/s, the total bandwidth of the configured services at the port should not be greater than 353207 cell/ s. Issue 03 (2013-02-20)


826



Values Value Range

Default Value

4528-1412828 cell/s

-

Configuration Guidelines The maximum egress bandwidth of each external optical port on the N1IDQ1 and N1ADQ1 boards is 353207 cell/s. The maximum egress bandwidth of each external optical port on the N1IDL4 and N1ADL4 boards is 1412828 (353207x4) cell/s. For internal ATM ports, the maximum ingress bandwidth depends on the type of the bound services and number of the services. If VCTRUNK1 is bound with two VC-12s, the maximum egress bandwidth is 9056 (4528x2) cells/s. If VCTRUNK1 is bound with four VC-4s, the maximum egress bandwidth is 1412828 (353207x4) cell/s. Plan properly before configuring or using a board to ensure that the egress bandwidth of each port does not exceed the permitted value range.

A.16 RPR Associated Parameters This topic describes the parameters for configuring the RPR function.

A.16.1 RPR Node ID Description The Node ID parameter indicates the ID of a node in the resilient packet ring (RPR). In the RPR, each node has a unique ID to facilitate RPR management and packet forwarding.


Values Value Range

Default Value

1-255

0

Configuration Guidelines In the same RPR, each node must have a unique ID. IDs of nodes in different RPRs can be allocated separately. When planning a network, you need to uniformly plan IDs for nodes in the RPR. For a new project, node IDs increase in an ascending order in the direction of ring 0. Issue 03 (2013-02-20)


827



After you configure services, node IDs cannot be modified. Otherwise, the following results may be caused: l

Some packets in a service that is forwarded at the local node are lost for up to 50 ms.

l

The service whose destination node is the local node may be unavailable. When this occurs, you need to reconfigure the service according to the new ID of the local node.


A.16.2 RPR Protocol Description The RPR Protocol parameter specifies whether to enable the resilient packet ring (RPR) protocol for a node in the RPR. If the RPR protocol is enabled, you can use the RPR features to forward and protect a service. As a new MAC protocol defined in IEEE 802.17, RPR is designed to optimize the transmission of data packets, and to serve as the Ethernet standard that is fairly shared by the transmission media bandwidth. The RPR technology integrates many advantages, such as high bandwidth usage and multi-service access in the Ethernet network, and wide bandwidth and powerful selfhealing capability in the optical network. As a result, the RPR technology features dual-ring structure, spatial reuse mechanism, flexible granularity of service bandwidth, dynamic sharing and allocation of bandwidth, statistical multiplexing, support for various service levels, automatic identification of network topology, and protection switching based on the source route.

Impact on the System After you switch the status of the RPR protocol, the services forwarded from the node are interrupted transiently. The packets are lost for up to 50 ms. A node whose RPR protocol is disabled cannot add or drop any service.

Values Valid Value

Default Value

Enabled, Disabled

Disabled


Issue 03 (2013-02-20)

Value

Description

Enabled

Enables the RPR protocol. In this case, a node is added to the RPR network.

Disabled

Disables the RPR protocol. In this case, a node is deleted from the RPR network.


828




To configure a RPR network, enable the RPR protocol for all the nodes in the RPR.

l

For a node that adds or drops a service, you must enable the RPR protocol.

l

For a node that does not add or drop a service at the moment, generally, you also need to enable the RPR protocol.

If a node with the RPR protocol disabled needs to add or drop services, enabling the RPR protocol at this moment may result in a service interruption for 50 ms. If a node does not need to add or drop a service, disable the RPR protocol to shorten the time for the node to learn the topology and to minimize service interruption time due to a change in the RPR network topology accordingly. If some services are available in the RPR network, enable or disable the RPR protocol on the node only when you make sure that this operation does not affect any service in the network.

Relationship with Other Parameters Before enabling the RPR protocol, set Node ID for the local node. Otherwise, the RPR protocol cannot be enabled.

A.16.3 RPR Node Protection Slow Timer Value(ms) Description The Protection Slow Timer Value(ms) parameter specifies the three timers in the resilient packet ring (RPR) protocol. The three timers are fast, slow and wait-to-restore (WTR). The fast timer and slow timer specify the interval of transmitting topology protection (TP) messages in an RPR. If any protection information is changed, the fast timer transmits eight TP messages. Then, the changed protection information is advertised to all other nodes in the RPR network at the earliest time. After the fast timer transmits the eight TP messages, the slow timer is used to transmits the TP message so that the bandwidth occupancy is minimized.


Values Board Name

Value Range

Default Value

Unit

N1EMR0

50-10000, in a step length of 50 ms

1000

ms

100-1000, in step length of 100 ms

100

ms

(Not produced any more) N2EGR2, N2EMR0

Issue 03 (2013-02-20)


829



Configuration Guidelines For the slow timer on each node, the default value is the same. Generally, use the default value. If any requirements are proposed by customers, set the slow timer to a proper value, depending on the board software version. The value should not exceed, however, the range allowed in practice.

Relationship with Other Parameters This parameter is valid only when RPR Protocol is set to Enabled.

A.16.4 RPR ATD Timer Value(s) Description The ATD Timer Value(s) parameter specifies the interval of transmitting the attribute discovery (ATD) message. It is also called a topology timing value. After the RPR network is configured, each node in the network actively broadcasts its information using the topology discovery protocol to discover the RPR topology. The information is transmitted through ATD messages and is used with topology and protection (TP) messages to maintain the RPR network topology. TP messages are used to transmit a real-time and urgent topology message. ATD messages are used to transmit a non-real-time topology message.

Impact on the System If the RPR network runs properly, the system operation is not affected after you modify the setting of ATD Timer Value.

Values Value Range

Default Value

Unit


1

Second

Configuration Guidelines Generally, use the default value. If any requirement is proposed by customers, you can set ATD Timer Value to a proper value based on the RPR network status. The value of ATD Timer Value, however, cannot exceed the range allowed in practice.


A.16.5 RPR Protection Mode Description The Protection Mode parameter specifies the protection mode of a node in the RPR network. That is, it specifies how to protect services upon a fault in the RPR network. Three modes are Issue 03 (2013-02-20)


830



available to protect services in the RPR network. For details, see "Related Information" in this topic.

Impact on the System After the setting of Protection Mode is modified, all the services that pass through the node are interrupted for up to 50 ms. If the protection mode is set to Steering, the service interruption time can be less than 50 ms when there are 16 or less nodes on the ring.

Values Valid Value

Default Value

Wrapping, Steering, Wrap and Steering

Steering


Description

Steering

Changes the service route to protect the RPR network. In this case, less bandwidth is used, but more time is taken to respond, and more packets are discarded in case of a switching event.

Wrapping

Switches the loop to protect services in the RPR network. In this case, less time is taken to respond, fewer packets are discarded in case of a switching event, but some bandwidth is wasted.

Wrap and Steering

Switches the loop and changes the service route to protect services in the RPR network. This mode integrates the advantages such as short response time in Wrapping mode and optimized transmission path in Steering mode.

Configuration Guidelines Configure a proper protection mode for every node in the RPR network based on the service characteristics and actual requirements. The protection modes for all the nodes in the same RPR network must be compatible with each other. If not, an alarm is generated and services are not protected in the way as expected by customers. Use the default setting, unless otherwise specified. You can set this parameter based on the compatibility of the protection mode. The Wrapping mode is compatible with the Wrap and Steering mode. The Wrapping mode or the Wrap and Steering mode, however, is incompatible with the Steering mode. For example, you can set Protection Mode to Steering or Wrapping for all the nodes in the RPR network. You can also set Protection Mode to Wrapping for some nodes, and to Wrap and Steering for other nodes. You can also set Protection Mode to Steering for some nodes, and to Wrapping or Wrap and Steering for other nodes. Issue 03 (2013-02-20)


831




Related Information Steering: Steers the loop to protect services in the RPR network. This mode is the default mode for all the nodes. If a part of the RPR is faulty, the information that contains faulty point and fault type is transmitted to each node. The topology is changed accordingly. The source node only needs to directly transmit the data to the destination node based on the new topology. The data that has been transmitted to the faulty point is discarded at the point. In Steering mode, the bandwidth usage is improved to transmit data over an optimal route, but the switching time is long. After the topology becomes stable, you need to determine a new route based on the new topology. Figure A-38 and Figure A-39 respectively shows the network status before a fiber cut and after the Steering mode is adopted for protection. Figure A-38 Network before a fiber cut

Figure A-39 Network after the Steering mode is configured

Node 2 transmits packets to node 6. Normally, the service flow is in the direction of s2 -> s3 > s4 -> s5 -> s6. If the fiber between nodes 3 and 4 is cut, the topology is updated to optimize the route. In this case, the service flow is in the direction of s2 -> s1 -> s7 -> s6. Wrapping: Wraps the route to protect services in the RPR network. This mode is optional. If a point on the RPR ring is faulty, the node close to the faulty point automatically loops back to connect ring 0 with ring 1. In Wrapping mode, the switching time is short to minimize the frame loss resulted from the fault. The bandwidth usage, however, is low. Figure A-40 and Figure A-41 respectively shows the network status before a fiber cut and after the Wrapping mode is adopted for protection. Issue 03 (2013-02-20)


832



Figure A-40 Network before a fiber cut

Figure A-41 Network after the Wrapping mode is configured

Node 2 transmits packets to node 6. Normally, the service flow is in the direction of s2 -> s3 > s4 -> s5 -> s6. If the fiber between nodes 3 and 4 is cut, it is switched on nodes 3 and 4. In this case, the service flow is in the direction of s2 -> s3 -> s2 -> s1 -> s7-> s6 -> s5 -> s4 -> s5 -> s6. Wrap and Steering: Wraps and then steers the route for protection. Wraps and then steers the route for protection. This mode integrates the advantages such as the short response time in the Wrapping mode and the optimal route in the Steering mode. In Wrap and Steering mode, the route is wrapped to avoid loss of more packets, and then the route is steered for protection after the new topology becomes stable.

A.16.6 RPR Hold-off Time(ms) Description The Hold-off Time(ms) parameter specifies the time to wait for switching (namely, hold-off time) after the signal fail (SF) or signal degrade (SD) condition is detected in the RPR network. l

After the time specified in Hold-off Time expires, switching occurs in the RPR network if the SF or SD condition persists.

l

Switching does not occur in the RPR network if the SF or SD condition is cleared.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

Unit

0-200, in a step length of 10

0

ms


833




If no SDH protection scheme (for example, MSP or SNCP) is configured, use the default value to avoid loss of more packets within the hold-off time in the RPR network.

l

If any SDH protection scheme (for example, MSP or SNCP) is configured, make sure that the hold-off time is longer than the time for all the SDH protection switching. For example, the hold-off time is set to 50 ms. In this case, the SDH protection schemes have the priority to be implemented. If the SDH protection schemes fail, the RPR switching is implemented for protection.


A.16.7 RPR Protection Restoration Mode Description The Protection Restoration Mode parameter specifies whether to switch the node to the normal state and to groom the service in the loop as a normal service after a node in the SF/SD state detects that the SF/SD condition is cleared.


If the service in the RPR network is not switched, or if the forced switching (FS) or manual switching (MS) occurs, the system operation is not affected after you modify the setting.

l

In the case of switching based on SF or SD on the node: – If this parameter is set to Enabled, the node switches to the normal state when it has detected that the SF or SD condition is cleared, and grooms the service in the loop as a normal service. During the period of service restoration, some packets are lost for up to 50 ms. – If this parameter is set to Disabled, the node is always in the switching state. In this case, the service is not switched to the working path, no service packets are lost, but the bandwidth utilization is decreased.

Values Valid Value

Default Value

Enabled, Disabled

Enabled


Issue 03 (2013-02-20)

Value

Description

Enabled

If the working path recovers after service switching, the node changes to the normal state and the service is switched back to the working path.


834



Value

Description

Disabled

If the working path recovers after service switching, the node does not change its state. Instead, it keeps in the WTR state all the time and the service is not switched back to the working path.

Configuration Guidelines The node changes to the WTR state only when it recovers from the SD or SF condition. For this reason, this parameter takes effect only when the node recovers from the SD or SF condition, but does not take effect when the node recovers from the FS or MS condition. The default value is Enabled. Use the default value, unless otherwise specified. In this case, although some packets are lost transiently when the link recovers, less bandwidth is used and service forwarding efficiency is improved.


A.16.8 RPR Protection Wait-to-restore(s) Description The Protection Wait-to-restore(s) parameter specifies the time for the RPR network to change to the wait-to-restore state and keep in this state for some time (namely, the protection wait-torestore time). When an RPR network recovers from a fault, it does not immediately switch to the normal state. Instead, it keeps in the switching state. If no fault is detected within the waitto-restore time, the node changes from the WTR state to the normal state, and grooms services in the loop as normal services.

Impact on the System The value of Protection Wait-to-restore determines the time for restoring a service to the normal state. It does not affect the system running.

Values Value Range

Default Value

Unit

0-1440, in a step length of 1

10

Second

Configuration Guidelines Generally, use the default value. If any requirements are proposed by customers, you can set Protection Wait-to-restore to a proper value according to the requirements and RPR network status. The value of Protection Wait-to-restore cannot exceed the range allowed in practice. Issue 03 (2013-02-20)


835



Relationship with Other Parameters This parameter is valid only when RPR Protocol and Protection Restoration Mode are set to Enabled.

A.16.9 RPR Send link weight Description The Send link weight parameter specifies the weight of the send link of an RPR node. It is classified into the weight of the eastern send link and that of the western send link. The weight value is valid only for the services whose priority is B_EIR or C. It is invalid for the services whose priority is A0, A1 or B_CIR. It decides the bandwidth of adding a service whose priority is B_EIR or C to the ring. For the services whose priority is B_EIR or C, the fairness algorithm is used to derive the bandwidth of each service according to the weight value when the RPR is congested. For example, the traffic rate is 1 Gbit/s respectively for services A and B whose priority is C. If services A and B pass an RPR network at a rate of 1 Gbit/s, and if their weight value is in proportion of 7:3, the bandwidth proportion for services A and B is 700 Mbit/s : 300 Mbit/s.

Impact on the System This parameter is invalid if the RPR network is not congested. After the parameter value is modified, the system operation is not affected. If the RPR network is congested, and if the parameter value is changed, the traffic of the services whose priority is B_EIR and C is affected in the RPR network. The greater the weight value, the heavier the traffic added to the RPR.

Values Value Range

Default Value

1-255

1

NOTE

The greater the value, the greater the weight.

Configuration Guidelines Use the default value, unless otherwise specified. That is, if the weight is the same for each node, the bandwidth of the service in the RPR network is consistent. Otherwise, set the weight value based on the required bandwidth. The wight values can be separately set for 0 ring and 1 ring.

Relationship with Other Parameters This parameter is valid only when RPR Protocol is set to Enabled. Issue 03 (2013-02-20)


836



A.16.10 RPR Used and Reserved bandwidth of priority A Description The Used bandwidth of priority A parameter is divided into two parts: reserved bandwidth of priority, which is called A0 bandwidth, and the remaining bandwidth, which is called A1 bandwidth. A0 bandwidth is the allocated reserved bandwidth and cannot be reclaimed by other nodes. Although the local node does not transmit the services whose priority is A, this bandwidth must be reserved. A1 bandwidth is the allocated committed bandwidth and can be reclaimed by the services of other priorities, as shown in Table A-10. Table A-10 RPR service priority Service Priority Prior ity

Applica tion

SubPriority

Bandwi dth Guarant eed or Not

Jitter

Bandwid th Type

Bandwid th SubType

Adopt the Fairne ss Algor ithm or Not

A

Realtime service

A0

Yes

Low

Preallocated

Reserved

No

A1

Yes

Low

Nearreal-time service

B-CIR

Yes

Middle

Preallocated

Reclaimab le

B-EIR

No

Wider

Used randomly

Reclaimab le

Besteffort delivery

C

B

C

Service Quality

Yes

The bandwidth is used for the RPR node whose service priority is A. It limits the traffic of the services whose priority is A in the loop. If the traffic of priority A has the bandwidth that exceeds the A0 bandwidth, they are transmitted by the A1 bandwidth. If the traffic of priority A has the bandwidth that exceeds the A1 bandwidth, it is discarded.

Impact on the System The A0 bandwidth is irreclaimable. The proportion of total A0 bandwidth cannot be extremely large in the RPR network. Otherwise, the bandwidth utilization is affected. If the total A0 bandwidth in the RPR network exceeds the total bandwidth in the RPR network, the services of priority B or C fail to be transmitted because no bandwidth is available in the RPR network.

Values The parameter values for A0 and A1 bandwidth are the same and are as follows:

Issue 03 (2013-02-20)


837



Value Range

Default Value

Unit

0-Maximum bandwidth in a single ring, in step length of 1 Mbps

0

Mbps

Configuration Guidelines The A0 bandwidth can be set within the bandwidth range in the RPR network, but cannot exceed the bandwidth of the services whose priority is A. The proportion of the total A0 bandwidth cannot be extremely large in the RPR network. Otherwise, the bandwidth utilization is decreased. If no service of priority A is available in the RPR network, generally, set the bandwidth to 0 for the service of priority A. If any service of priority A is available, generally, set the A bandwidth to 0, and set the bandwidth to the A1 bandwidth for all the services of priority A.


A.16.11 RPR Used bandwidth of priority B-CIR(Mbps) Description The RPR Used bandwidth of priority B-CIR(Mbps) parameter specifies the committed bandwidth for the nodes whose service priority is A in the RPR network. It is also called the B_CIR bandwidth. If the traffic of priority B has the bandwidth that exceeds the B_CIR bandwidth, it is transmitted by the B_CIR bandwidth.


Values Value Range

Default Value

Unit

0-Maximum bandwidth in a single ring, in step length of 1 Mbps

0

Mbps

Configuration Guidelines You can plan the B_CIR bandwidth for each node in the RPR network based on the transmitted near-real-time service traffic. If no service of priority B is available to the nodes in the RPR network, generally, set the B_CIR bandwidth to 0. The B-CIR bandwidth should not exceed the total bandwidth in the RPR network.

Relationship with Other Parameters This parameter is valid only when RPR Protocol is set to Enabled. Issue 03 (2013-02-20)


838



A.16.12 RPR Circle Name Description The Circle Name parameter specifies the ring number to distinguish the two rings from each other, including 0 Ring and 1 Ring. The RPR network is of a topology that consists of two rings in different directions. The external ring is named Outer Ring (namely, 0 ring), and the internal ring is named Inner Ring (namely, 1 ring). Figure A-42 shows the topology of the RPR network. Figure A-42 Topology of the RPR network S1

0 Ring

S2

1 Ring RPR Network

S0

S3 S5

S4

OptiX NE


Values Value Range

Default Value

0 Ring, 1 Ring

-


Issue 03 (2013-02-20)

Value

Description

0 Ring

Indicates the outer ring of the RPR network.

1 Ring

Indicates the inner ring of the RPR network.


839





A.16.13 RPR Node Reachability Description Reachability indicates the reachability from this node to another RPR node. l

If the reachability of 0 Ring (or 1 Ring) is Reachable, no fault occurs on the link between this node and another node on 0 Ring (or 1 Ring). Services of this node can be directly forwarded to another node on 0 Ring (or 1 Ring).

l

If the reachability of 0 Ring (or 1 Ring) is Unreachable, a fault occurs on the link between this node and another node on 0 Ring (or 1 Ring). Services between this node and another node are unavailable on 0 Ring (or 1 Ring).


Values Value Range

Default Value

Reachable, Unreachable

Unreachable


Description

Reachable

Indicates that the link between this node and another node on 0 Ring (or 1 Ring) is available.

Unreachable

Indicates that the link between this node and another node on 0 Ring (or 1 Ring) is unavailable.




840



A.16.14 RPR Node Hop Description RPR node hop indicates the hop from this node to another RPR node. That is, this parameter indicates the number of nodes from this node to the destination node. Services are transmitted in the shortest path of the ring network by default. That is, after 0 ring hop and 1 ring hop between this node and the destination node are compared, the ring ID with the smallest hop count is chosen as the transmission direction of the service.


Values Value Range

Default Value

0-255

255 (Indicates an invalid hop.)

When a node is unreachable, the value 255 is displayed indicating that the node hop is invalid.



A.16.15 RPR Adjacent node ID Description adjacent node ID indicates adjacent node ID of this node. Every node has two adjacent nodes, that is, East adjacent node ID and West adjacent node ID.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

1-255

-


841





A.16.16 RPR Node Direction Description RPR Node Direction indicates Direction of the RPR node, including East and West to distinct two directions of the node. The RPR network is classified into the dual-ring topology. The outer ring is 0 Ring, and the inner ring is 1 Ring. Figure A-43 shows the ring network topology. Figure A-43 RPR network topology S1 East West 0 Ring

West

S2 East

1 Ring

East

West

RPR Network

S0

S3 S4

S5

West

East West

East West

East

OptiX NE

Every node on the RPR network has two directions. East indicates the transmit direction of 0 Ring and the receive direction of 1 Ring, and West indicates the receive direction of 0 Ring and transmit direction of 1 Ring. Services on 0 Ring are transmitted from West to East, and services on 1 Ring are transmitted from East to West.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

East, West

-


842




Description

East

East of the node indicates the transmit direction of 0 Ring and the receive direction of 1 Ring.

West

West of the node indicates the receive direction of 0 Ring and the transmit direction of 1 Ring.



A.16.17 ECHO Path ID (RPR Node Information) Description The ECHO Path ID parameter specifies the ID of the path used for the ECHO function. The ECHO function is one of the RPR OAM functions. It is used to monitor the connection between two nodes in the RPR network and to locate any fault. For the ECHO function, 16 paths are always available on each node. After you configure the ECHO path ID, a node can initiate the connectivity test for other 16 nodes at the same time.


Values This parameter is for query only. Each node always has 16 ECHO paths, which are numbered from 1 to 16.



A.16.18 ECHO Working Mode (RPR Node Information) Description ECHO Working Mode indicates the working mode of the ECHO channel, used for determining whether the ECHO function the ECHO channel is enabled. Issue 03 (2013-02-20)


843



The RPR OAM function is used for the configuration management, fault management and performance management on the RPR network. The ECHO function is an RPR OAM function, used for connection monitoring and fault localization of the two nodes on the ring network. The ECHO frame is an OAM request or response frame. That is, an ECHO request frame is transmitted from the source address to the destination address. The destination address receives and resolves the request frame, and then transmits an ECHO response frame to the request node. The request node analyzes the link connection situation according to the received response frame.

Impact on the System The value of this parameter has no impact on normal services. After the ECHO function is enabled, the ECHO frame, however, occupies a small amount of bandwidth of the ring network and some CPU resources.

Values Value Range

Default Value

Start, Stop, Clear

Stop


Description

Start

Indicates that the ECHO function of this ECHO channel is enabled. That is, the source node starts to transmit an ECHO request frame to the destination node.

Stop

Indicates that the ECHO function of this ECHO channel is disabled. That is, the source node stops transmitting an ECHO request frame to the destination node.

Clear

Indicates that the statistics information about this ECHO channel is cleared. The statistics information includes the number of ECHO messages that are transmitted, the number of ECHO messages that are processed successfully, the number of ECHO messages that are processed unsuccessfully, and whether the LOC and dLoc alarms are detected.

Configuration Guidelines This parameter is used to determine whether the ECHO function the ECHO channel is enabled. To test the link connectivity between the two nodes, you need to enable the ECHO function of the ECHO channel after configuring the parameters of the channel. After the test, disabling the ECHO function of the ECHO channel to avoid wasting the bandwidth of the ring network and the CPU recourses. You are recommended to disable the ECHO function before clearing the statistics information about the ECHO channel.

Issue 03 (2013-02-20)


844




A.16.19 ECHO Request Loop (RPR Node Information) Description ECHO Request Loop indicates the transmission direction of the ECHO request frame of the ECHO channel.


Values Value Range

Default Value

0 Ring, 1 Ring, Default Directionality

Default Directionality


Description

0 Ring

Indicates transmitting the ECHO request frame from 0 Ring after the ECHO function of the ECHO channel is enabled.

1 Ring

Indicates transmitting the ECHO request frame from 1 Ring after the ECHO function of the ECHO channel is enabled.

Default Directiona lity

Indicates that the protocol automatically chooses the shortest path as the transmit direction of the ECHO request frame.

Configuration Guidelines The ECHO frame is used to test the link connection situation between the two nodes. The user can specify the transmit direction of the ECHO request frame according to the test requirements.

Relationship with Other Parameters This parameter is valid only when Working Mode of the ECHO channel is set to Start.

A.16.20 ECHO Response Loop (RPR Node Information) Description ECHO Request Loop indicates the transmission direction of the ECHO response frame of the ECHO channel. Issue 03 (2013-02-20)


845



Impact on the System The value of this parameter has no impact on normal services. After the ECHO function is enabled, the ECHO frame, however, occupies a small amount of bandwidth of the ring network and some CPU resources.

Values Value Range

Default Value

0 Ring, 1 Ring, Default Directionality, Backward

Default Directionality


Description

0 Ring

Indicates transmitting the ECHO response frame from 0 Ring after the ECHO function of the ECHO channel is enabled.

1 Ring

Indicates transmitting the ECHO response frame from 1 Ring after the ECHO function of the ECHO channel is enabled.

Default Directiona lity

Indicates that the protocol automatically chooses the shortest path as the transmit direction of the ECHO response frame.

Backward

Indicates transmitting the ECHO response frame from the direction that is opposite to the request direction after the ECHO function of the ECHO channel is enabled.

Configuration Guidelines The ECHO frame is used to test the link connection situation between the two nodes. The user can specify the transmit direction of the ECHO response frame according to the test requirements.


A.16.21 ECHO Frame Service Type (RPR Node Information) Description ECHO Frame Service Type indicates the transmission priority of the ECHO frame on the ring network.



846



Values Value Range

Default Value

A0, A1, B, C

A0


Description

A0

Indicates that the ECHO frame is transmitted with priority A0 on the ring network and occupies bandwidth A (including bandwidths A0 and A1).

A1

Indicates that the ECHO frame is transmitted with priority A1 on the ring network and occupies bandwidth A (including bandwidths A0 and A1).

B

Indicates that the ECHO frame is transmitted with priority B on the ring network and occupies bandwidth B (including bandwidths B_CIR and B_EIR).

C

Indicates that the ECHO frame is transmitted with priority C on the ring network and occupies bandwidth C.

Configuration Guidelines The ECHO frame is used to test the link connection situation between the two nodes. The user can specify ECHO Frame Service Type according to the test requirements. For example, to test the connectivity of service A0, the user sets ECHO Frame Service Type to A0.


A.16.22 Is ECHO Path Protected (RPR Node Information) Description Is Path Protected indicates the protection type of the ECHO frame and is used to determine how to handle the ECHO frame in the case of a loop switching. l

When the ECHO frame is set to Yes, if the protection status is set to Wrapping or Wrap and Steering, the ECHO request frame or the response frame that is transmitted in the channel is switched when the frame passes through a node in the protection switching status; if the protection status is set to Steering, the ECHO request frame or the response frame that is transmitted in the channel is discarded when the frame passes through a node in the protection switching status.

l

If the ECHO frame is set to NO, the ECHO request or response frame that is transmitted in the channel is discarded when it passes through a node in the switching status.



847



Values Value Range

Default Value

Yes, No

No


Description

Yes

Indicates the ECHO frame is protected.

No

Indicates the ECHO frame is unprotected.

Configuration Guidelines The user can specify Is Path Protected according to the test requirements.


A.16.23 ECHO T1 Transmit Period (RPR Node Information) Description ECHO T1 Transmit Period indicates the transmit period of the ECHO frame that is tagged with time T1. The ECHO frame is classified into the request frame and response frame. If the user enables an ECHO channel at the NE, an ECHO request frame is transmitted in the channel every T1.

Impact on the System The occupied bandwidth and CPU resources increase with the decrease in the value of T1 Transmit Period.

Values Value Range

Default Value

Unit


100

ms

Configuration Guidelines The user can modify the value of this parameter according to the ring network situation. The modification should not go beyond the value range. Issue 03 (2013-02-20)


848




A.16.24 ECHO T2 Response Time (RPR Node Information) Description ECHO T2 Response Time indicates the response timeout of the ECHO frame that is marked with time T2.

Impact on the System If the node fails to receive the response frame within time T2 after transmitting the ECHO frame, the node reports the dLoc alarm.

Values Value Range

Default Value

Unit


100

ms

Configuration Guidelines The user can modify the value of this parameter according to the ring network situation. The modification should not go beyond the value range.


A.16.25 Number of Echo Messages Received (RPR Node Information) Description Number of Echo Messages Received indicates the number of ECHO messages that the node receives. From the time when the node enables the ECHO function, the parameter value increases by one every time the node receives an ECHO response frame.


Values For example, the value 100 indicates that the node receives 100 ECHO messages. Issue 03 (2013-02-20)


849





A.16.26 Successfully Processed (RPR Node Information) Description Successfully Processed indicates the number of ECHO messages that are successfully processed by the node. The NE starts to count when the ECHO function is enabled at the source node. After the node transmits an ECHO request frame, the parameter value increases by 1 if the node receives a correct ECHO response frame within the specified response time.


Values For example, the parameter value "100" indicates that the node receives 100 ECHO messages that are processed successfully.



A.16.27 Unsuccessfully Processed (RPR Node Information) Description Unsuccessfully Processed indicates the number of ECHO messages that are unsuccessfully processed by the node. The parameter value is counted when the ECHO function is enabled at the source node. After the node transmits an ECHO request frame, the parameter value increases by 1 if the node fails to receive a correct ECHO response frame within the specified response time.


Values For example, the parameter value 100 indicates that the node receives 100 ECHO messages that are processed unsuccessfully. Issue 03 (2013-02-20)


850





A.16.28 dLoc Detected (RPR Node Information) Description dLoc Detected indicates an alarm for a link failure. That is, this parameter specifies that the link communications may be abnormal. This parameter is used to query whether the node detects the dLoc alarm when the ECHO function is enabled at the source node. When the node transmits an ECHO request frame, the node reports the dLoc alarm if the node fails to receive a correct ECHO response frame within time T2. The node clears this dLoc alarm after the node receives a correct ECHO response frame.


Values Value Range

Default Value

Yes, No

No


Description

Yes

Indicates that the node detects the dLoc alarm.

No

Indicates that the node does not detect any dLoc alarm.



Issue 03 (2013-02-20)


851



A.16.29 Loc Detected (RPR Node Information) Description Loc Detected indicates that the link communications is severely abnormal. This parameter is used to query whether the node detects an LOC alarm when the ECHO function is enabled at the source node. When the node detects a dLOC alarm, and if the dLOC alarm persists two seconds, the node reports an LOC alarm. If the node does not receive any dLOC alarm for 10 seconds, the LOC alarm is cleared.


Values Value Range

Default Value

Yes, No

No


Description

Yes

Indicates that the node detects an LOC alarm.

No

Indicates that the node does not detect any LOC alarm.



A.16.30 RPR Node Protection Status Description The RPR Node Protection Status parameter specifies the protection request status of the link in the current direction of the RPR network. The eastern and western RPR nodes respectively have a protection status. After the RPR protocol is enabled for a node, it continuously checks the status of the links in the RPR network. After the RPR protocol checks any protection request status such as signal fail (SF), signal degrade (SD), forced switching (FS) or manual switching (MS), the current direction of the RPR network is set to the proper protection status. In the case of the forced switching or manual switching, if no protection requests are detected or the protection request Issue 03 (2013-02-20)


852



is cleared, this direction of the RPR network is set to IDLE. In the case of SF or SD, if no protection requests are detected or the protection request is cleared, this direction of the RPR network is set to IDLE when the WTR time expires.


Values Value Range

Default Value

Force Switching, SF, SD, Manual Switching, Wait-to-Restore, Idle

Idle


Description

Force Switching

Indicates that the RPR node is in the forced switching status.

SF

Indicates that the RPR node is in the automatic switching status resulted from the signal fail (SF) condition.

SD

Indicates that the RPR node is in the automatic switching status resulted from the signal degrade (SD) condition.

Manual Switching

Indicates that the RPR node is in the manual switching status.

Wait-toRestore

Indicates that the RPR node is in the Wait-to-Restore status.

Idle

Indicates that the RPR node is in the Idle status.

These switching request signals have the priorities from high to low: FS, SF, SD, MS, WTR, IDLE. The FS and SF have the highest and equal priorities. That is, FS and SF can preempt switching signals of each other. The switching signals of higher priorities can preempt the switching signals of lower priorities. The switching schemes whose priority is higher than SF can be used to protect the RPR network at the same time. The switching schemes whose priority is lower than SF should not be used in the RPR network at the same time. The switching request of higher priorities contends the switching request of lower priorities. The RPR node can change to the WTR status only when it recovers from the SD or SF status.


Issue 03 (2013-02-20)


853




A.16.31 RPR Node Switching Status Description The RPR Node Switching Status parameter specifies the switching status of an RPR node. In the eastern and western directions of a node, a switching status is available to show whether the link in the current direction of the RPR network is normal.


Values Value Range

Default Value

Not switched, Switched

Not switched


Description

Not switched

Indicates that the node is not in the switching status in this direction.

Switched

Indicates that the node is in the switching status in this direction.



A.16.32 RPR Node Accumulated Protection Times Description The Accumulated Protection Times parameter specifies the accumulated protection count of a node, which is also called accumulated switching count. The count starts after the RPR protocol is enabled on the node. The count is added by 1 when the switching occurs once. The accumulated protection count in the eastern direction of the node is separate from that in the western direction of the node. Issue 03 (2013-02-20)


854




Values For example, if the displayed value is 10, the accumulated protection count is 10 after the RPR protocol is enabled on the node.



A.16.33 RPR Node Accumulated Protection Time Description The Accumulated Protection Time parameter specifies the accumulated protection time. The count starts after the RPR protocol is enabled on the node. When a switching occurs, the duration from the start time to the end time is recorded. This parameter value is derived from accumulation of all the duration. The accumulated protection time in the eastern direction of the node is separate from that in the western direction of the node.


Values For example, if the displayed value is 10, the accumulated protection duration is 10 seconds after the RPR protocol is enabled on the node.



A.16.34 RPR Node Last Switch Request Description The Last Switch Request parameter specifies the last switching request of a node.



855



Values Value Range

Default Value

Force Switching, Manual Switching, Idle

Idle


Description

Force Switching

Indicates that the last switching request issued to the node is a forced switching.

Manual Switching

Indicates that the last switching request issued to the node is a manual switching.

Idle

Indicates that no switching request is issued to the node. This is the default value.



A.16.35 RPR Switch Request Description RPR Switch Request indicates the type of a protection request that is issued to the node, including Force Switching, Manual Switching and Clear. This operation can be performed on the east node and west node of this node.

Impact on the System When the user issues a switching request to the node, the services that are forwarded by this node are interrupted transiently with a packet loss time less than 50 ms. If the protection mode is set to Steering, the service interruption time can be less than 50 ms when the number of nodes on the ring is not more than 16.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

Force Switching, Manual Switching, Clear

-


856




Description

Force Switching

When adding a node to the ring network, you need to protect the current services. Because the link is normal, a switching cannot be performed automatically but can be performed forcibly only. This protection request is with the highest priority and cannot be preempted by other protection requests on the ring network.

Manual Switching

Indicates performing a switching in 0 Ring or 1 Ring. But services can be switched back when a more severe link failure occurs on the ring network.

Clear

Indicates clearing the forced switching and manual switching.

Configuration Guidelines Usually, the protection request is required only when the network topology changes. The user can determine whether to issue the switching request to the node according to the actual situation. If the user allows the switching request to be preempted by the SF/SD, a manual switching request is issued. Make sure that all switchings at this node are cleared after all the operations are completed.


A.17 LAG Associated Parameters (TDM Mode) This topic describes the parameters that are used for enabling the LAG function.

A.17.1 LAG Type(Link Aggregation Group Management) Description The 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 machine determines whether the port can carry services.

Impact on the System As the LACP protocol is not enabled for the manual LAG, the LAG Type parameter should be set to Manual for the interconnected ports. In addition, the Load Sharing and Revertive Mode parameters should be set as the same for the interconnected ports. Otherwise, the working ports 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, the services are interrupted. Issue 03 (2013-02-20)


857



When a static LAG is initially created, the services are interrupted until the two ends negotiate and determine a port that can carry the services.

Values Value Range

Default Value

Manual, Static

Static


Description

Manual

The LACP protocol is not enabled. The link status, rate, and duplex mode of a port determine whether the port can carry services.

Static

The LACP protocol is enabled and protocol packets are exchanged. The protocol state machine determines whether the port can carry services.

Configuration Guidelines If 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 LAG Type parameter to Static.



A.17.2 Revertive Mode(Link Aggregation Group Management) Description In the case of the link aggregation group (LAG) that does not share the load, the Revertive Mode parameter specifies whether the services are switched after the original working port recovers. Revertive and Non-Revertive are available for this parameter.

Impact on the System If the Revertive Mode parameter is set to Revertive, the services are switched after the port with the highest priority recovers. During the switching, the services are transiently interrupted for not more than 3s. Issue 03 (2013-02-20)


858



Values Value Range

Default Value


Non-Revertive


Description

Revertive

After the original working port recovers, the services are switched to this port.

Non-Revertive

After the original working port recovers, the services are not switched.

Configuration Guidelines To switch the services only when the service-carried port fails, set the Revertive Mode parameter to Non-Revertive. To ensure that only the port with the highest priority carry services whenever the port is fine, set the Revertive Mode parameter to Revertive.

Relationship with Other Parameters The Revertive Mode parameter is valid only when the Load Sharing parameter is set to NonSharing.


A.17.3 Load Sharing(Link Aggregation Group Management) Description The Load Sharing parameter indicates whether multiple ports are allowed to carry the services at the same time when multiple ports in the aggregation group can be used.

Impact on the System In Non-Sharing mode, only the port with the highest priority in the link aggregation group carries the service and the other port functions as backup port. In 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 both ends are same. Otherwise, certain service packets are lost. Issue 03 (2013-02-20)


859



Values Value Range

Default Value

Sharing, Non-Sharing

Non-Sharing


Description

Non-Sharing

Indicates that only one port carries the services. Only one slave port can be configured.

Sharing

Indicates that multiple ports are allowed to carry the services at the same time. A maximum of 15 slave ports can be added.

Configuration Guidelines When manually configuring the aggregation group, configure the load sharing modes at the two ends to the same. Otherwise, certain service packets are lost.



A.17.4 Load Sharing Hash Algorithm(Link Aggregation Group Management) Description The Encapsulation Type parameter indicates the traffic distribution algorithm for different ports in the aggregation group.

Impact on the System If multiple ports in the aggregation group can carry the services, the traffic distribution effect varies with the Hash algorithms configured. If the Hash algorithm is properly configured, the traffic on each port is evenly distributed. Otherwise, the traffic is not evenly distributed, and the port bandwidth cannot be fully used.

Issue 03 (2013-02-20)


860



Values Value Range

Default Value

Automatic, Source MAC, Destination MAC, Source and Destination MACs

Automatic


Description

Automatic

The traffic is distributed among ports according to the source and destination MACs of the packets.

Source MAC

The traffic is distributed among ports according to the source MAC of the packets.

Destination MAC

The traffic is distributed among ports according to the destination MAC of the packets.

Source and Destination MACs

The traffic is distributed among ports according to the source and destination MACs of the packets.

Configuration Guidelines To evenly distribute the traffic on each port as possible, select a proper Hash algorithm according to different packets on the ports.

Relationship with Other Parameters This parameter is valid only when Load Sharing is set to Non-Sharing.

A.17.5 System Priority(Link Aggregation Group Management) 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.

Impact on the System When the LAG at the local end negotiates with the LAG at the opposite end by using the LACP packets, the LAGs can obtain the system priority information of each other. The result computed by the selection logic of the LAG with the higher priority is considered as the common result for both LAGs. If the two LAGs have the same system priority, the system MAC addresses of the two LAGs are compared. The LAG with the lower MAC address is adopted. The system priority increases as the value decreases.

Issue 03 (2013-02-20)


861



Values Value Range

Default Value

0-65535, 1 as the spacing

32768

Configuration Guidelines To adopt the result computed by the selection logic of a static LAG, set a higher system priority for this static LAG.

Relationship with Other Parameters The System Priority (Link Aggregation) parameter is valid only when the LAG Type parameter is set to Static.


A.17.6 Main Port(Link Aggregation Group Management) Description The Main Port parameter indicates the LAG member port available for creating services. Each LAG has only one main port.


Values Value Range

Default Value

For example, 3-PEG16-1(PORT-1)

-

Configuration Guidelines Every Ethernet port on the NE can be used as the main port. The main port and the slave port must be of the same type. The rate of the main port must be the same as the rate of the slave port.



862




A.17.7 Main Port Status(Link Aggregation Group Management) Description The Main Port Status parameter indicates the port status computed by the selection logic for the LAG.

Impact on the System If 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, the service can be loaded on this port.

Values Value Range

Default Value

In Service, Out of Service

Unknown


Description

In Service

Indicates that the port can be added to an LAG and can carry the service.

Out of Service

Indicates that the port cannot be added to an LAG and cannot carry the service.

Configuration Guidelines This parameter is used for query only. No rule is specified for selecting a value.

Relationship with Other Parameters In the case of the static LAG, the LACP protocol is used. The port status depends on the port working 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 the port working mode and port working rate.



863



A.17.8 Port Priority(Link Aggregation Group Management) Description The Port Priority parameter indicates the priority of the Ethernet port. If other attributes, such as the port rate and port working mode, are the same, in the LAG member ports that enable the LACP protocol, the port with a higher priority carries services first. This parameter is invalid for the LAG (manual LAG, for example) that does not run the LACP protocol.


Values Value Range

Default Value

0-65535

32768

Configuration Guidelines The 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 Parameters In a LAG, which port has the priority to carry services is jointly determined by Port Priority and System Priority of the LAG, and is first determined by System Priority. For example, as shown in Figure A-44, the non-load sharing static LAG is created between NE A and NE B. Figure A-44 Non-load sharing static LAG is created between NE A and NE B

NEA

Port 1

Working

Port 1

NEB

Port 2

Port 2 Protection LAGa

Issue 03 (2013-02-20)


LAG b

864



Each port of LAG a and LAG b meets the requirements of carrying services. System Priority of LAG a is higher than System Priority of LAG b. In LAG a, Port Priority of port1 is higher than Port Priority of port2. In LAG b, Port Priority of port2 is higher than Port Priority of port 1. In this case, in LAG a, port1 is the working port, port2 protects port1, and port2 does not share the service traffic. The protection relation in LAG b is the same as the protection relation in LAG a, because System Priority of LAG a is higher than System Priority of LAG b. That is, in LAG b, port1 is the working port, port2 protects port1, and port2 does not share the service traffic, even if Port Priority of port2 is higher than Port Priority of port1 in LAG b.

Related Information For the setting of this parameter, see System Priority.

A.18 MC-LAG Associated Parameters This topic describes the parameters for configuring MC-LAG protection.

A.18.1 Protocol Channel ID Description The Protocol Channel ID parameter specifies the ID of the protocol channel when the MCSP channel is created. This parameter can be allocated automatically.


Values Value Range

Default Value

1-15

-

Configuration Guidelines You need to enter this parameter when creating MCSP channels. This parameter also can be allocated automatically.


Issue 03 (2013-02-20)


865



A.18.2 Hello Packet Sending Interval (s) Description The Hello Packet Sending Interval (s) parameter specifies the interval at which the Hello packets are transmitted to the opposite end to check whether the link is normal.


Values Value Range

Default Value

Unit

1-10

1

Second

Configuration Guidelines This parameter must be set according to the network planning and requirements. Generally, the smaller the value of this parameter, the shorter the interval (s) for transmitting Hello packets to the opposite end, and the faster the speed of detecting whether the link is normal.


A.18.3 Timeout Time (s) Description The Timeout Time (s) parameter is used for checking whether the configuration messages time out. When the value of Timeout Time (s) of received Hello messages exceeds the specified threshold, the opposite end is faulty and the relevant alarm is reported.


Values

Issue 03 (2013-02-20)

Value Range

Default Value

Unit

30-3600

600

Second


866



Configuration Guidelines You need to set this parameter according to the network planning and requirement. This parameter is related to the Hello Interval parameter set on the opposite end. The smaller the value of this parameter, the faster the speed of detecting a fault on the link.


A.19 LAG/DLAG Associated Parameters (TDM Mode) This topic describes the parameters for configuring a link aggregation group (LAG) and a distributed link aggregation group (DLAG).

A.19.1 Port Priority (Link Aggregation) Description The Port Priority (Link Aggregation) parameter specifies the priority of the ports in the link aggregation group of the LACP protocol. The port priority can be set. It indicates the priority level of a port to be aggregated. If a port is of higher priority, this port is preferred to carry the services. If a link aggregation group (for example, manual aggregation group) does not run the LACP protocol, it does not take effect after the port priority is set.

Impact on the System If other conditions (for example, port rate, and port working mode) are the same, a port of higher priority is preferred to carry the services.

Values Valid Values

Default Value


32768

Configuration Guidelines If the value of Port Priority is smaller, the priority is higher. When using a port to carry the services, set Port Priority to a smaller value. Otherwise, set Port Priority to a greater value.

Relationship with Other Parameters The member port state in the link aggregation group is decided according to these parameters, such as port working mode, port working rate, whether the port receives LACP packets, port priority, and LAG priority. Issue 03 (2013-02-20)


867



A.19.2 System Priority (Link Aggregation) Description The System Priority (Link Aggregation) parameter specifies the priority level of a link aggregation group. It may affect the working state of the member ports in the link aggregation group.

Impact on the System When the link aggregation groups at the local and opposite ends negotiate with each other by sending LACP packets, they can get the system priority of the link aggregation groups from each other. The result selected at the end of higher priority is taken as the result for the two ends. If the system priority of the link aggregation group is the same at the two ends, the system MAC addresses are compared. A MAC address is used if it is of lower value. If the value of System Priority is smaller, the system priority of the link aggregation group is higher.

Values Valid Values

Default Value


32768

Configuration Guidelines To take the result selected by the static link aggregation group as the actual value, set System Priority to a smaller value.

Relationship with Other Parameters The member port state in the link aggregation group is decided according to these parameters, such as port working mode, port working rate, whether the port receives LACP packets, port priority, and system priority.

A.19.3 Slave Port (Link Aggregation) Description The Slave Port (Link Aggregation) parameter specifies that a link aggregation group is manually created rather than being automatically created by the system. A link aggregation group contains main ports and slave ports. The slave ports in a link aggregation group are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the link aggregation group.

Impact on the System A main port can be added to the link aggregation group, regardless of the service. A slave port can be, however, added to the link aggregation group only if no services are available. After being added to the link aggregation group, a slave port cannot be configured with any services. Issue 03 (2013-02-20)


868



Values Board Name

Value Range

Default Value

N1EAS2

PORT1-PORT2

-

VCTRUNK1-VCTRUNK34 N1EGS4, N3EGS4, N4EGS4

PORT1-PORT4

-

N1EMS4

PORT1-PORT20

-


Description

Available Slave Ports

Indicates the number of the physical port that can be set to the slave port.

Selected Slave Ports

Indicates the number of the physical port that is already set to the slave port.

Configuration Guidelines Add the relevant slave port to the link aggregation group as required. The maximum number of slave ports differs with the board type. Board

Maximum Number of Slave Ports Sharing

Non-Sharing

N1EAS2

23

1

N1EGS4, N3EGS4, N4EGS4

15

1

N1EMS4

15

1

Relationship with Other Parameters A port can be aggregated only when the maximum frame length is consistent. Moreover, all the ports in the link aggregation group must be on the same processing board or on the relevant interface board.

A.19.4 Status (Link Aggregation) Description The Status (Link Aggregation) parameter specifies the state, which is derived from logical computation, of each member ports in a link aggregation group. Issue 03 (2013-02-20)


869



Impact on the System When a port is not configured with services, this port can be added to a link aggregation group. If this port is in service in this link aggregation group, this port can share the service. If this port is out of service in this link aggregation group, this port cannot share the service. When a port is already configured with services, this port cannot be added to a link aggregation group and cannot share the service.

Values Valid Values

Default Value

Unknown, In Service, Out of Service

Unknown

Value

Description

Unknown

Indicates that the link aggregation group is not queried.

In Service

Indicates that the port can carry the service.

Out of Service

Indicates that the port cannot carry the service.

Configuration Guidelines This parameter is used for query only. No rules are provided for selecting a value.


For static link aggregation, the LACP protocol is used. The member port state in the link aggregation group is decided by these parameters, such as port working mode, port working rate, port priority, and link aggregation group priority.

l

For manual link aggregation, the LCAP protocol is not used. The member port state in the link aggregation group is not related to these parameters, such as port working mode and port working rate.

A.19.5 Branch Port Description The Branch Port parameter specifies that a link aggregation group is created manually rather than automatically. A link aggregation group consists of main ports and branch ports. Branch ports in a link aggregation group are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from a link aggregation group.

Impact on the System Regardless of services, a main port can be added to a link aggregation group. A branch port can be added to a link aggregation group only when it is not configured with any services. After being added to a link aggregation group, a branch port cannot be configured with any services. Issue 03 (2013-02-20)


870



Values Board Name

Valid Values

Default Value

N2EGR2, N2EGS2, N3EGS2

PORT1-PORT2

-

N2EFS4, N3EFS4

PORT1-PORT4

-

N2EFS0, N4EFS0, N5EFS0

PORT1-PORT8

-

N2EMR0

PORT1-PORT13

-

N1EFS0A

PORT1-PORT16

-

N1EMS2

PORT1-PORT18

-


Description

Available Branch Port

Indicates the number of the physical port that can be set to a branch port.

Selected Branch Port

Indicates the number of the physical port that is already set to a branch port.

Configuration Guidelines Add a relevant branch port to a link aggregation group as required.

Relationship with Other Parameters Ports can be added to a link aggregation group only when their physical attributes are consistent with each other, including Working Mode, Flow Control Mode and Max. Packet Length. The link aggregation function can be configured only when the broadcast packet suppression function is disabled. All the ports in a link aggregation group must be on the same processing board or on the relevant interface board.

A.19.6 Load Sharing(Ethernet Link Aggregation) Description The Load Sharing parameter specifies the load sharing mode of an aggregation group.

Impact on the System Different load sharing modes have different effects. In load sharing mode, the ports in the aggregation group can share the service. In load non-sharing mode, only one port in the aggregation group can carry the service and the other port provides protection. Issue 03 (2013-02-20)


871



Values Value Range

Default Value

Sharing, Non-Sharing

Sharing


Description

Sharing

Indicates that the ports in the aggregation group share the service.

Non-Sharing

Indicates that the ports in the aggregation group do not share the service. Only one port in the aggregation group carries the service.

Configuration Guidelines If the bandwidth needs to be increased and several ports need to be enabled to share the service, select the load sharing mode. If only one port needs to carry the service and protection is required for this port, select the load non-sharing mode.

A.19.7 Revertive Mode (DLAG) Description The Revertive Mode (DLAG) parameter specifies whether to switch a service back to the main board that recovers from a fault. l

If the service needs to be switched back to the main board, set Revertive Mode to Revertive.

l

If a service need not be switched back to the main board and is still transmitted at the slave board, set Revertive Mode to Non-Revertive.

Impact on the System If Revertive Mode is set to Revertive, the service is switched back to the main board that recovers from a fault. For each switching event, the transient interruption time of the service is less than three seconds.

Values

Issue 03 (2013-02-20)

Valid Values

Default Value


Revertive


872




To avoid frequent switching and to switch the service only when the working board port fails, select Non-Revertive.

l

If the user requires that the main port carries the service if it works normally, select Revertive.


A.19.8 Main Port Priority (DLAG) Description The Main Port Priority (DLAG) parameter specifies the priority of the main port in a distributed link aggregation group (DLAG). A port of higher priority is preferred to carry the services.

Impact on the System If other conditions (such as port rate and port working mode) are the same, modifying the port priority may cause service switching and interruption.

Values Valid Values

Default Value

0-65535

32768

Configuration Guidelines If the value of Port Priority is smaller, the priority is higher. To enable a port to be preferred to carry the services, set Port Priority to a smaller value. Otherwise, set Port Priority to a greater value. For a DLAG, to enable the main port to be preferred to carry the services, set the priority of the main port in the DLAG higher than that of the slave port.

Relationship with Other Parameters A DLAG uses the LACP. The working state of a member port in a link aggregation group is decided by these parameters such as port working mode, port rate, port priority, and link aggregation group priority. If Revertive Mode is set to Non-Revertive, the set port priority does not take effect.

Issue 03 (2013-02-20)


873



A.19.9 Slave Port Priority (DLAG) Description The Slave Port Priority (DLAG) parameter specifies the priority of the slave port in a DLAG. The priority is specified in the LACP. A port of higher priority is preferred to carry the services.

Impact on the System If other conditions (such as port rate and port working mode) are the same, modifying the port priority may cause service switching and interruption.

Values Valid Values

Default Value

0-65535

32768

Configuration Guidelines If the value of Port Priority is smaller, the priority is higher. To enable a port to be preferred to carry the services, set Port Priority to a smaller value. Otherwise, set Port Priority to a greater value. For a DLAG, to enable the slave port to be preferred to carry the services, set the priority of the slave port in the DLAG higher than that of the main port.

Relationship with Other Parameters A DLAG uses the LACP. The working state of a member port in a link aggregation group is decided by these parameters such as port working mode, port rate, port priority, and link aggregation group priority. If Revertive Mode is set to Non-Revertive, the set port priority does not take effect.

A.20 STP/RSTP Associated Parameters This topic describes the parameters for configuring the Spanning Tree Protocol (STP) and the Rapid Spanning Tree Protocol (RSTP).

A.20.1 Protocol Enabled (Spanning Tree) Description Protocol Enabled (Spanning Tree) indicates whether the spanning tree protocol is enabled on the VB. Issue 03 (2013-02-20)


874



Impact on the System After the protocol is enabled and when the computation of the spanning tree is performed according to the protocol type (STP/RSTP), the network topology changes and services are interrupted temporarily.

Values Value Range

Default Value

Enabled, Disabled

Disabled

Configuration Guidelines The user can set this parameter according to the actual service requirement.

Relationship with Other Parameters This parameter can be set only when the VB is created and Protocol Type is selected.

Related Information The rapid spanning tree protocol (RSTP) can realize all the functions of the spanning tree. Similar to the STP, the RSTP avoids temporary loops. Different from the STP, the RSTP shortens the time delay at the ports from blocking to forwarding, restores the network connectivity more rapidly, and provides better services.

A.20.2 Protocol Type (Spanning Tree Protocol) Description Protocol Type (Spanning Tree) indicates that the Ethernet data board of the OptiX OSN equipment supports two spanning tree protocols, that is, the spanning tree protocol (STP) and the rapid spanning tree Protocol (RSTP). l

The STP is a Layer 2 management protocol that avoids Layer 2 loops by selectively blocking redundant network links and supports the link backup.

l

The RSTP develops from the STP and shortens the convergence time.

Impact on the System If this parameter is changed incorrectly, a network topology oscillation may occur and services are severely affected.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

STP, RSTP

RSTP


875



Configuration Guidelines The RSTP and STP can be configured at the same time. The RSTP is compatible with the STP. It is recommended that you use the default value RSTP.


A.20.3 VB Priority (Bridge Parameters) Description VB Priority (Bridge Parameters) indicates the fixed parameters of the bridge, used for selecting the role of the bridge and computing the topology of the spanning tree. As the value of the parameter decreases, the VB priority increases and the bridge is more likely to be selected as a root bridge.

Impact on the System Changing the value of VB Priority may affect the selection of a root bridge, which may finally affect the entire network topology.

Values Value Range

Default Value


32768

Configuration Guidelines Set this parameter according to what role the user expects the bridge to play in the spanning tree topology.


A.20.4 Max Age(s) Description The Max Age(s) parameter specifies the maximum life cycle of the configuration message. A configuration message contains the message aging time and maximum aging time of the message. The maximum life cycle of the configuration message is equivalent to the maximum aging time of the message.

Impact on the System If the message aging time exceeds the maximum aging time of the message, the received message is discarded and the port that receives the message becomes a designated port. Issue 03 (2013-02-20)


876



Values Value Range

Default Value

Unit

6-40

20

s

Configuration Guidelines When you set the value of this parameter, ensure that the following requirement is met: 2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1)

Relationship with Other Parameters This parameter is related to the Hello Time and Forward Delay parameters. For details, refer to the principles for setting these parameters.

A.20.5 Hello Time(s) (Spanning Tree) Description The Hello Time(s) parameter specifies the transmission period of the message. The bridge time consists of the following parts: forward delay of the bridge, handshake time of the bridge, maximum bridge aging time, and message aging time (0). The Hello Time parameter is equivalent to the bridge handshake time.

Impact on the System This parameter ensures the stable operation of the STP.

Values Value Range

Default Value

Unit

1-10

2

s

Configuration Guidelines When you set the value of this parameter, ensure that the following requirement is met: 2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1)

Relationship with Other Parameters This parameter is related to the Max Age and Forward Delay parameters. For details, refer to the principles for setting these parameters. Issue 03 (2013-02-20)


877



A.20.6 Forward Delay(s) (Spanning Tree) Description The Forward Delay(s) parameter specifies the delay of the port state migration. This parameter is actually a timer that is used by the ports in the listening state and in the learning state to control the migration from the listening state to the learning state and the migration from the learning state to the forwarding state. The timer is started when the port enters the listening state. When the timer expires, the port automatically migrates to the learning state and the timer is started again. When the timer expires the second time, the port automatically migrates to the forwarding state and the timer is stopped.

Impact on the System The restoration time of the service from the learning state to the forwarding state is affected.

Values Value Range

Default Value

Unit

4-30

15

s

Configuration Guidelines When you set the value of this parameter, ensure that the following requirement is met: 2 x (Hello Time + 1) ≤ Max Age ≤ 2 x (Forward Delay - 1).

Relationship with Other Parameters This parameter is related to the Hello Time and Max Age parameters. For details, refer to the principles for setting these parameters.

A.20.7 TxHoldCount(per second) (Spanning Tree) Description The TxHoldCount(per second) parameter enables the transmission state machine of the port to specify the maximum transmission rate of the BPDU packet.

Impact on the System This parameter ensures that the number of the BPDU packets transmitted within a period of hello time does not exceed the preset value.

Issue 03 (2013-02-20)


878



Values Value Range

Default Value

1-10 times/s

6

Configuration Guidelines Set this parameter according to the actual requirement of the user. It is recommended that you use the default value.

A.20.8 Root Path Cost Description Each bridge has the root path cost. The root path cost of the root bridge is equal to 0. In the case of non-root bridges, the root path cost of each bridge is equal to the sum of path cost values of each port on the other bridges that a non-root bridge passes when the bridge receives the frame from the root bridge along the minimum cost path. The path cost of each port can be managed. The network segment in each LAN has the root path cost. The root path cost of the network segment is equal to the root path cost of the bridge whose cost is the smallest among all the bridges that are connected to the network segment through the bridge ports. In this case, the bridge whose cost is the smallest is selected as the designated bridge. If the root path cost values of two or more bridges are the same and the smallest, the bridge with a higher priority is selected as the root bridge. In the case of non-root bridges, the root path cost of each bridge is equal to the sum of path cost values of each port on the other bridges that a non-root bridge passes when the bridge receives the frame from the root bridge along the minimum cost path. That is, the value of the root path cost is the sum of the path cost values of all bridges.

Impact on the System The root path cost can determine the designated bridge and the service flow in the STP.

Values Based on the protocol, the value of this parameter is calculated according to the network topology. This parameter is used for querying.

Configuration Guidelines There are no principles for setting the value of this parameter because this parameter is used for querying.

A.20.9 Hold Count (Spanning Tree) Description The Hold Count parameter indicates the maximum number of BPDUs that are actually transmitted within a period of hello time. Issue 03 (2013-02-20)


879



Impact on the System The system is not affected because this parameter is used to check the counter of the BPDU packet.

Values This parameter is used for querying.

Configuration Guidelines There are no principles for setting the value of this parameter because this parameter is used for querying.

A.20.10 Port ID Description The Port ID parameter contains 16 bits, which show the port priority and the unique port number in the bridge. The first eight bits indicate the port priority, and the later eight bits indicate the port number. The port ID represents the priority in the spanning tree. If the value of the port ID is smaller, the port priority in the bridge is higher. To enable the RSTP to be compatible with the STP, the port priority is represented by eight bits, of which the later four bits are 0 for easy management.

Impact on the System This parameter is for query only. The system is not affected.

Values The parameter value is in decimal system. For example, Port ID = 32769.

Relationship with Other Parameters You can change the parameter value by setting the port priority. In this case, however, the topology of the spanning tree may be rearranged. If the port priority is smaller, the port ID is smaller. When the port priorities are the same, the port ID is smaller if the port number is smaller.

A.20.11 Port Path Cost Description The Port Path Cost parameter is used for computation of the spanning tree state machine. Based on the port path cost, you can compute the root path cost at the port of the switch. Each bridge has a root path cost, namely, the cost of the path from the root bridge to the local bridge. The path cost of each port can be set through the management module. For a root bridge, the root path cost is 0. For Port Path Cost, the recommended values, which are decided by the MAC type and the transmission rate.are shown in Table A-11. The recommended values for RSTP are the same as those for STP. Issue 03 (2013-02-20)


880



Table A-11 Recommended values of the port path cost Parameter

Link Speed

Recommende d value

Recommende d range

Range

Path Cost

<=100 Kb/s

200000000

20000000-2000 00000

1-200000000

1 Mb/s

20000000

2000000-20000 0000

1-200000000

10 Mb/s

2000000

200000-200000 00

1-200000000

100 Mb/s

200000

20000-2000000

1-200000000

1 Gb/s

20000

2000-200000

1-200000000

10 Gb/s

2000

200-20000

1-200000000

100 Gb/s

200

20-2000

1-200000000

1 Tb/s

20

2-200

1-200000000

10 Tb/s

2

1-20

1-200000000

Impact on the System After this parameter is modified, the protocol conducts the computation again based on the modified value. Consequently, the network topology may be changed.

Values Board Name

Value Range

Default Value

N4EFS0, N2EFS4, N2EGS2, N2EMR0, N2EGR2, N1EMS4, N1EGS4, N3EGS4, N1EAS2

1-200000000

l 19 (FE port) l 4 (GE port) l 2 (VCTRUNK, 10 GE and RPR ports)

Configuration Guidelines If the port rate is greater, the port path cost is smaller. Generally, use the default value.


Issue 03 (2013-02-20)


881



A.20.12 Designated Path Cost Description The Designated Path Cost parameter is applicable to the port and is used for the state machine calculation of the spanning tree. Based on the port path cost, you can calculate the root path cost of the port of the switch. The root path cost is equal to 0 in the case of a root bridge. In the case of other bridges, the root path cost of the bridge refers to the path cost from the root bridge to this bridge. The root path cost is the sum of the minimum root path cost of the port on this bridge and the path cost of this port. The path cost of each port can be set through the management module. Table A-12 shows the recommended values of the port path cost. The values are generally related to the MAC type and transmission rate. Table A-12 Recommended values of the port path cost Parameter

Link Speed

Recommende d value

Recommende d range

Range

Path Cost

<=100 Kb/s

200000000

20000000-2000 00000

1-200000000

1 Mb/s

20000000

2000000-20000 0000

1-200000000

10 Mb/s

2000000

200000-200000 00

1-200000000

100 Mb/s

200000

20000-2000000

1-200000000

1 Gb/s

20000

2000-200000

1-200000000

10 Gb/s

2000

200-20000

1-200000000

100 Gb/s

200

20-2000

1-200000000

1 Tb/s

20

2-200

1-200000000

10 Tb/s

2

1-20

1-200000000

Impact on the System This parameter affects the calculation of the root path cost based on the STP and hence affects the service flow in the spanning tree.

Values Value Range

Default Value

1-65535

0



882



Value

Description

1-65535

Indicates the cost required by the transmission of the bridge port.

Configuration Guidelines If the port rate is greater, the designed path cost is smaller. It is recommended that you use the default value.

A.20.13 Designated Root Bridge Priority Description The Designated Root Bridge Priority parameter indicates the priority of the root bridge that is selected based on the STP. The selection is based on the bridge IDs in a network. A bridge ID consists of the priority and MAC address of the bridge. The bridge whose ID is the smallest is selected as the root bridge in this network.

Impact on the System This parameter is used for querying. It indicates the priority of the current root bridge and may change in the case of a spanning tree topology change.

Values Value Range

Default Value

0-65535

32768

Configuration Guidelines There are no specific principles for setting the value of this parameter because this parameter is used for querying.

A.20.14 Designated Bridge Priority(Spanning Tree) Description The Designated Bridge Priority parameter indicates the priority of each bridge during the selection of the root bridge based on the STP. The bridge priority is a part of the bridge ID. A bridge ID consists of the bridge priority and MAC address of the bridge. The bridge whose ID is the smallest is selected as the root bridge in the network.

Impact on the System If the priority of a bridge is higher, the probability is higher that the bridge is selected as the root bridge. Issue 03 (2013-02-20)


883



Values Value Range

Default Value

0-61440

32768

Configuration Guidelines If the value of the parameter is smaller, the priority of the bridge is higher. Set this parameter according to the actual network condition.

A.20.15 Designated Bridge MAC Address (Spanning Tree) Description The Designated Bridge MAC Address parameter indicates the MAC address of a bridge. To ensure that the bridge protocols operate normally, the following requirements should be met: l

The multicast MAC address must be unique and be identified by all the bridges in the LAN. The multicast MAC address identifies the protocol entities of a bridge that is connected to different and individual physical network segments.

l

Each bridge has a unique ID in the entire LAN.

l

Ports on a bridge have port IDs, which are different from each other. Ports IDs of different bridges are different. The values of these IDs can be assigned independently. The values can also be used by other bridges.

l

Each bridge must provide the values of the parameters that are described previously or provide the mechanism for assigning values for these parameters.

Impact on the System The MAC address of a bridge affects the priority of the bridge.

Values Value Range

Default Value

unicast mac address

00-00-00-00-00-00

Configuration Guidelines It is recommended that you use the default value.

A.20.16 Protocol Enabled (Port Parameter of Spanning Tree) Description The Protocol Enabled parameter specifies whether the STP is enabled for a port. The STP is used in the loop network. This protocol realizes routing redundancy by adopting a certain algorithm and breaks the loop network into a loop-free tree network. Hence, the Issue 03 (2013-02-20)


884



application of this protocol can prevent the packets from increasing and cycling in an endless manner in the loop network. The RSTP is developed based on the STP, which transmits spanning tree information through configuration messages and conducts the calculation according to the priorities. The RSTP reduces the delay when the root port and designated port enters the forwarding state to a great extent, and hence reduces the time required for stabilizing the network topology.

Impact on the System The RSTP can realize all the functions of the STP. Compared with the STP, however, the RSTP can restore the connectivity of the network more quickly, which can provide better services for the user. This is because the RSTP reduces the delay when a port migrates from the blocking state to the forwarding state without causing temporary loops.

Values Value Range

Default Value

Enabled, Disabled

Disabled


Description

Enabled

Indicates that the STP is enabled on the local port and that this port is involved in the calculation.

Disabled

Indicates that the STP is disabled on the local port and this port is not involved in the calculation.

Configuration Guidelines Set this parameter according to the networking condition. If the topology calculation requires a VB, enable the STP for this VB. Otherwise, the STP is disabled for all VBs. The STP of a port can be enabled or disabled only after the STP is enabled for a VB.

A.20.17 Admin Edge Attribute Description Edge ports are directly connected to the terminal equipment and are not connected to any bridge in a network. The Admin Edge Attribute parameter is important in the RSTP. The status of these ports does not affect the topology of the entire network, and does not result in any loop. Hence, after the bridge protocol is enabled, these ports can change to the forwarding status without any delay.

Issue 03 (2013-02-20)


885



Impact on the System If you set the ports that are directly connected to the terminal equipment as edge ports, the convergence time of the RSTP is minimized, and the system reliability is enhanced.

Values Value Range

Default Value

Enabled, Disabled

Disabled

Configuration Guidelines You can set this parameter based on the network topology.


A.20.18 Edge Port Status (Spanning Tree) Description The Edge Port Status parameter specifies whether a bridge port is an edge port. Edge ports are directly connected to the terminal equipment and are no longer connected to any bridges. This parameter is important in the RSTP. The status of these ports does not affect the connectivity of the entire network, and does not cause any loops. Hence, these ports can enter the forwarding state without any delay after the bridge starts.

Impact on the System After this parameter is enabled, convergence time of the RSTP is reduced and thus the reliability of the system is improved.

Values Value Range

Default Value

Enabled, Disabled

Disabled


Issue 03 (2013-02-20)

Value

Description

Enabled

Indicates that the edge port function is enabled. In this case, the port can enter the forwarding state directly without any delay during the calculation process of the state machine.

Disabled

Indicates that the edge port function is disabled. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

886



Configuration Guidelines The user can set this parameter according to the network topology to reduce the delay in the case of a state migration of the network edge port.

A.20.19 VB Port Priority Description The VB Port Priority parameter is the key part of the port ID for the spanning tree feature of the OptiX OSN equipment. The port ID consists of the port priority and the unique port number in the bridge. The port number is fixed and cannot be set. The port ID contains 16 bits, of which the first eight bits indicate the port priority and the later eight bits indicate the port number. For computation based on the spanning tree, a port with a smaller specified port priority is preferred as the root port if the other conditions of this port are the same as conditions of the other ports. In the same bridge, if the overhead of the root path is the same for multiple ports, compare the specified bridge IDs, and then compare the specified port IDs.

Impact on the System The priority value of the VB port affects the selection of the root port of the downstream bridge and the selection of the designated port. Consequently, the entire network topology is changed.

Values Value Range

Default Value


128

Configuration Guidelines The value of VB Port Priority must be an integer multiplied by 16. If the value is smaller, the priority is higher. You can set the value based on the requirement of the user.

A.20.20 VB Port Status Description The VB Port Status parameter specifies that a bridge port processes the data packets based on the port status computed by the spanning tree protocol.


Issue 03 (2013-02-20)


887



Values Valid Values

Default Value

Discarding, Forwarding, Learning

Forwarding


Description

Discarding

In this state, the port cannot receive or forward service packets.

Forwarding

In this state, the port can receive and forward service packets.

Learning

In this state, the port can receive but cannot forward service packets. The port learns the source MAC addresses contained in the received service packets so that the port is ready for entering the forwarding state.


A.20.21 Point to Point Attributes(External Ethernet Port Attributes) Description The Point to Point Attributes (External Ethernet Port Attributes) parameter specifies the mode of connecting Ethernet ports to the external equipment. According to this parameter, the spanning tree protocol (STP) decides whether to rapidly transit the port state from discarding to forwarding.

Impact on the System If the connection is in shared media mode and if the port is not defined as an edge port, the STP cannot rapidly transit the port state. After the STP updates the network topology, the service restoration time becomes longer.

Values Valid Values

Default Value

Adaptive connection, Shared media, Link connection

Adaptive connection



888



Value

Description

Adaptive connection

If the port is a full-duplex port or a VCTRUNK port, and if the port has the point-to-point attribute, the port state can be transited rapidly.

Shared media

If the port has the non-point-to-point attribute, the port state cannot be transited rapidly.

Link connection

If the port has the point-to-point attribute, the port state can be transited rapidly.

Configuration Guidelines If the port connection mode is known, select Shared media or Link connection. Otherwise, select Adaptive connection.


A.21 LCAS Associated Parameters This topic describes the parameters for configuring the LCAS function.

A.21.1 Enabling LCAS Description The Enabling LCAS parameter can increase or decrease the SDH network capacity without affecting the service. The capacity is automatically decreased if a member fails, and is automatically increased if the member recovers.

Impact on the System As a bidirectional protocol, the LCAS can work normally only when some bandwidth is available in the bidirectional physical paths. If the bandwidth is available in the unidirectional physical paths only, the LCAS may fail to correctly adjust the bandwidth.

Values Value Range

Default Value

Enabled, Disabled

Disabled



889



Value

Description

Disabled

Disables the LCAS protocol.

Enabled

Enables the LCAS protocol.

Configuration Guidelines You can set Enabling LCAS as required.


A.21.2 LCAS Mode Description The LCAS Mode parameter specifies the sequence for the sink end to respond to the MST and Rs_Ack messages received from the source end.


Values Value Range

Default Value

Huawei Mode, Standard Mode

Huawei Mode


Description

Huawei Mode

Inverts the RS_Ack message, and then transmits the MST message.

Standard Mode

Transmits the MST message, and then Inverts the RS_Ack message.

Configuration Guidelines To set the LCAS mode, follow the principles: l

Issue 03 (2013-02-20)

If the interconnected equipment at the two ends are Huawei equipment, select Huawei Mode. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

890


l


If Huawei equipment is interconnected to a third-party equipment, set the interconnected equipment to the same mode according to the mode supported by the third-party equipment.


A.21.3 Hold off Time(ms) (LCAS) Description The Hold off Time(ms)(LCAS) parameter is also called HO Procedure Timer Duration. It specifies HO Procedure Timer Duration of the LCAS protocol. If the LCAS coexists with another network-level protection scheme (for example, MSP or SNCP), you can set this parameter to postpone the LCAS switching.

Impact on the System The LCAS switching time is affected. For example, if both the MSP and the LCAS are available in a network, set the LCAS hold off time to 2000 ms. If the network fails, only the MSP switching occurs, but the LCAS switching does not occur.

Values Value Range

Default Value

Unit

0, 2000-10000

2000

ms

Configuration Guidelines The User can set this parameter according to the expected hold off time of LCAS switching.

Relationship with Other Parameters This parameter is valid only when Enabling LCAS is set to Enabled.

A.21.4 WTR Time(s) (LCAS) Description The WTR Time(s) parameter is also called WTR Procedure Timer Duration. It specifies WTR Procedure Timer Duration of the LCAS protocol. Set this parameter to avoid impact caused by the alarm jitter on the link status.

Impact on the System The fault recovery time of the LCAS protocol is affected. After the network recovers from a fault, the LCAS protocol can recover only after a WTR duration. Issue 03 (2013-02-20)


891



Values Value Range

Default Value

Unit

0-720

300

Second

Configuration Guidelines The User can set this parameter according to the expected WTR duration of LCAS recovery.


A.21.5 TSD (LCAS) Description The TSD (LCAS) parameter specifies the B3 or BIP error status of a VCTRUNK member. TSD stands for trail signal degrade. When this parameter is set to Enabled and if a VCTRUNK member has excessive B3 or BIP bit errors, the LCAS protocol regards that this member fails and deletes it from the available members. If this parameter is set to Disabled, the LCAS protocol does not monitor the status of the B3 or BIP bit errors of a VCTRUNK member.


Values Value Range

Default Value

Enabled, Disabled

Disabled

Configuration Guidelines You can set whether to enable the TSD as required.


A.21.6 Minimum Number of Members in the Transmit Direction Description When the LCAS is enabled, the LCAS_PLCT alarm is reported if certain members in the transmit direction fail and the number of valid members is smaller than a certain value. The Minimum Issue 03 (2013-02-20)


892



Number of Members in the Transmit Direction parameter specifies the certain number of the valid members in the transmit direction.

Impact on the System When the LCAS is enabled, failure in certain paths does not affect the service in the case of sufficient bandwidths. The user can set this parameter to enable the reporting of the LCAS_PLCT alarm only when the number of the valid members in the transmit direction is smaller than a certain value.

Values Value Range

Default Value

2-256

256


A.22 Packet LPT Associated Parameters This topic describes the parameters for configuring the link state pass through (LPT) function in packet services.

A.22.1 Binding Status Description The Binding Status parameter specifies whether the LP function is bound with a service.


Values Value Range

Default Value

Unbound, Bound

Unbound


Issue 03 (2013-02-20)

Value

Description

Bound

Indicates that the LTP function is already bound with the service. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

893



Value

Description

Unbound

Indicates that the LTP function is not bound with the service.

Configuration Guidelines You need to configure a service before setting the binding status between the LTP function and the service. This parameter is defaulted to Unbound.

Relationship with Other Parameters Before binding a service, you need to enable the LPT function.

A.22.2 Primary Function Point Description The Primary Function Point parameter displays the port ID, board and slot ID of the primary function point. The primary function point is the master mode that operates the LPT protocol and determines the LPT protocol status based on the operating information. The secondary function point senses or transmits the status change information, such as the status change of a port or a remote node. The point-to-multipoint LPT includes a primary function point and multiple second function points, which respectively correspond to the root and leaves in the topology.


Values Value Range

Default Value

Slot ID-Board-Port ID

-


Description

Slot ID-BoardPort ID

Indicates the port ID, board and slot ID of the primary function point.



894




A.22.3 Secondary Function Point Type Description The Secondary Function Point Type parameter specifies the type of the port of the secondary function point when you configure point-to-point LPT.


Values Value Range

Default Value

PW, UNI

-


Description

PW

Indicates the type of the PW on the NNI side.

UNI

Indicates the type of the PW on the UNI side.

Configuration Guidelines In packet mode, LPTs are classified as point-to-point LPT and point-to-multipoint LPT. NEs are classified as Primary Function Point and Secondary Function Point. The Secondary Function Point Type can be set only when you configure the point-to-point LPT.

Relationship with Other Parameters Secondary Function Point Type must match with Primary Function Point Type.

A.22.4 Secondary Function Point Description The Secondary Function Point parameter displays the port, board, and slot ID of the secondary function point. The primary function point is the master node that operates the LPT protocol and determines the LPT protocol status based on the operating information. The secondary function point senses or transmits the status change information, such as the status change of a port or a remote node. Issue 03 (2013-02-20)


895



The point-to-multipoint LPT includes a primary function point and multiple secondary function points, which respectively correspond to the root and leaves in the topology.


Values Value Range

Default Value

Slot ID-Board-Port

-


Description

Slot ID-BoardPort

Indicates the port, board, and slot ID of the secondary function point.



A.22.5 Fault Detection Mode Description The Fault Detection Mode parameter specifies the mode to detect the LPT link status.


Values Value Range

Default Value

LPT OAM, PW OAM

LPT OAM



896



Value

Description

LPT OAM

Indicates that the LPT protocol suite negotiates and determines the LPT link status according to the protocol packets.

PW OAM

Indicates that the LPT protocol suite determines the LPT link status according to the protocol packets and the PW OAM status reported by a certain board. The LPT protocol suite regards that the LPT link is in good status only when both the negotiation status of the protocol packets and the PW OAM status are normal.

Configuration Guidelines If the LPT detection modes differ at both ends, the LPT fails to work normally.

Relationship with Other Parameters You need to enable the PW OAM function before configuring the PW OAM detection mode.

A.22.6 User-Side Port Status Description The User-Side Port Status parameter specifies the status of the laser on the LPT enabling port on the user side.


Values Value Range

Default Value

CLOSE, OPEN

OPEN


Description

OPEN

Indicates that the laser on the LPT enabling port is opened.

CLOSE

Indicates that the laser on the LPT enabling port is closed.

Configuration Guidelines When the LPT protocol works normally, OPEN is displayed. When a fault occurs on the network side, the OptiX OSN equipment shuts down the laser on the local end and reports CLOSE. Issue 03 (2013-02-20)


897



Relationship with Other Parameters None

A.23 LPT Associated Parameters (TDM Mode) This topic describes the parameters for configuring the LPT function.

A.23.1 LPT Description The LPT parameter specifies whether the link state pass through (LPT) function is enabled. The LPT is a technology developed by Huawei to increase the speed of the link state response. Through the LPT protocol, the faults on the service access point and in the intermediate network can be detected and reported.

Impact on the System When the LPT function is enabled, the faults on the service access point and in the intermediate network can be detected and reported. For example, the service access point can be informed of the fault in the intermediate network and thus can handle the fault accordingly (switch the service to the backup link). When the LPT function is disabled, the link fault in the intermediate network is not reported to the service access point.

Values Value Range

Default Value

Yes, No

No


Description

Yes

Indicates that the LPT function is enabled.

No

Indicates that the LPT function is disabled.

Configuration Guidelines Set this parameter according to the actual requirement of the user. Set this parameter to Yes if the LPT function is required.

Issue 03 (2013-02-20)


898



A.23.2 Bearer Mode Description The Bearer Mode parameter specifies the frame format of the LPT protocol packet for transmission. Three bearer modes are available, namely, GFP (HUAWEI), Ethernet, and GFP (CSF).

Impact on the System All the equipment on the service access point and in the intermediate network should use the same LPT bearer mode. Otherwise, the LPT function cannot work normally.

Values Value Range

Default Value

GFP(HUAWEI), Ethernet, GFP(CSF)

GFP(HUAWEI)


Description

GFP(HUAWEI)

Indicates the frame format specially used by Huawei.

Ethernet

Indicates the Ethernet frame format.

GFP(CSF)

Indicates the standard CSF frame format.

Configuration Guidelines Set this parameter according to the actual requirement of the user. Ensure that the configurations of the two interconnected ports are consistent.

A.23.3 Port-Type Port Hold-Off Time(ms) Description The Port-Type Port Hold-Off Time(ms) parameter specifies the interval for the PORT to transmit the LPT fault information after it receives the information.

Impact on the System The greater the hold-off time of the PORT, the slower is the transmission of fault information between networks.

Issue 03 (2013-02-20)


899



Values Value Range

Default Value

Unit

0-100000

0

ms


A.23.4 VCTRUNK Port Hold-off Time(ms) Description The VCTRUNK-Type Port Hold-off Time(ms) parameter specifies the interval for the VCTRUNK port to transmit the LPT fault information after it receives the information.

Impact on the System The greater the hold-off time of the VCTRUNK port, the slower is the transmission of fault information between networks.

Values Value Range

Default Value

Unit

0-100000

0

ms


A.24 IGMP Snooping Associated Parameters This topic describes the parameters for configuring the IGMP Snooping function.

A.24.1 Protocol Enable (IGMP Snooping Protocol) Description IGMP Snooping is a Layer-2 multicast protocol. If the IGMP Snooping is supported, an Ethernet board can detect the IGMP packets that are transmitted between IP multicast routers or switches and IP multicast hosts, and then check the detected IGMP packets. After being successfully checked, these packets are transmitted transparently. An Ethernet board retrieves the registration information of the multicast group from the checked IGMP packets. Moreover, it configures the relevant functions to generate route ports and multicast groups. The multicast service packets are forwarded according to the multicast group information. Issue 03 (2013-02-20)


900



This parameter specifies whether to enable the IGMP Snooping protocol within the specified virtual bridge (VB).


If the IGMP Snooping protocol is enabled, the Ethernet physical port captures and analyzes the received IGMP packets. Then the Ethernet physical port registers the multicast information to generate the router port and the multicast group. Finally the Ethernet physical port transparently transports the packets.

l

If the IGMP Snooping protocol is disabled, the Ethernet physical port does not analyze the received IGMP packets. Instead, the Ethernet physical port broadcasts the IGMP packets as ordinary multicast packets.

Values Valid Values

Default Value

Enabled, Disabled

Disabled


Description

Enabled

If the IGMP Snooping protocol is enabled, multicast groups and router ports can be generated.

Disabled

If the IGMP Snooping protocol is disabled, multicast groups and router ports cannot be generated.


To create and maintain a multicast service, select Enabled.

l

Otherwise, select Disabled.

A.24.2 Multicast Aging Time Description The Multicast Aging Time parameter specifies the aging time of the router port in the multicast group. The time is learnt by the board port. This parameter decides the valid time of the router port in the multicast group. Within the aging time period, if the router port is learnt again, its aging time is reset. Otherwise, when the aging time expires, the relevant router port in the multicast group is aged. After the router port is aged, the whole multicast group is deleted if no other router ports exist in the multicast group.

Impact on the System The parameter value may affect the forwarding efficiency of the EVPLAN service. Issue 03 (2013-02-20)


901



l

If the aging time is long, and if the multicast MAC address table in the board fails to be updated in time, the board forwards the service packets incorrectly. Consequently, the forwarding efficiency is decreased.

l

If the aging time is short, the multicast MAC address table may be updated rapidly. Moreover, a great number of received multicast service packets fail to be found in the MAC address table. Consequently, the board broadcasts these data packets to all the ports. As a result, the forwarding efficiency is also decreased.

Values Valid Values

Default Value

Unit


8

Min

Configuration Guidelines Generally, select the default value, unless otherwise specified. Otherwise, set the value according to the requirements. Do not set the value beyond the range allowed by the board.


A.25 Test Frame Associated Parameters This topic describes the parameters for configuring the Ethernet service test function.

A.25.1 Frames to Send Description Frames to Send indicates the number of test packets to be transmitted. With this parameter enabled, the system transmits a test packet at the intervals of certain period of time until the number of transmitted test packets reaches the specified value.


Values Value Range

Default Value

Unit

0-255

0

Unit

Configuration Guidelines The user can set the number of test packets to be transmitted as required. Issue 03 (2013-02-20)


902



Relationship with Other Parameters This parameter is valid only when Send Mode is set to Burst Mode.

A.25.2 Status Description Status indicates the transmit status of the current test frames at the port. This parameter is displayed as the current test status after you configure Send Mode and Frames to Send and then click Apply.


Values Value Range

Default Value

Sending, Finished Sending

-


Description

Sending

Indicates that the port is currently transmitting the test frames.

Finished Sending

Indicates that the port finishes transmitting the test frames.



A.25.3 Counter of Frames Sent Description Counter of Frames Sent indicates the number of test frames that are transmitted by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of test frames that are transmitted from last time when the parameter value is cleared to this time when the value is queried.

Impact on the System This parameter is for query only and does not affect the system operation. Issue 03 (2013-02-20)


903



Values For example, the parameter value 5indicates that the port transmits five test frames.



A.25.4 Counter of Received Response Test Frame Description Counter of Received Response Test Frame indicates the number of response test frames that are received by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of response test frames that are received from last time when the parameter value is cleared to this time when the value is queried.

Impact on the System This parameter is for query only and does not affect the system operation.

Values For example, the parameter value 5indicates that this port receives five response test frames.



A.25.5 Counter of Test Frames to Receive Description Counter of Test Frames to Receive indicates the number of test frames that are received by the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the total number of test frames that are transmitted from last time when the parameter value is cleared to this time when the value is queried.

Impact on the System This parameter is for query only and does not affect the system operation.

Values For example, the parameter value 5indicates that the port receives five test frames. Issue 03 (2013-02-20)


904





A.25.6 Bearer Mode (Ethernet Test) Description Bearer Mode (Ethernet Test) indicates the transmit path of the test frame. Different bearer modes correspond to different types of test frames. If the bearer mode of the received test frame is inconsistent with the bearer mode of this port, the test frame is discarded directly.


Values Board Name

Value Range

Default Value

N4EFS0, N5EFS0, N2EFS4, N3EFS4, N2EGS2, N3EGS2, N2EGT2, N1EFS0A, N1EMS2, N1EAS2

l /

/

N1EMS4, N1EGS4, N1EFT8, 1EFT8A, N1EGT2, R1EFT4, N3EGS4, N4EGS4

GFP

l GFP l Ethernet GFP


Description

/

Indicates that the bearer mode is unknown.

GFP

Indicates that the test frame is transmitted as a GFP management frame.

Ethernet

Indicates that the test frame is transmitted as an Ethernet frame.

Configuration Guidelines The Bearer Mode values of the test frame at the two ends of the SDH link must be consistent so that the test frame can function properly.



905



A.25.7 Send Mode (Ethernet Test) Description Send Mode(Ethernet Test) is used to set the test frame and the transmit mode of the test frame. The test frame is used for simulating packet transmission to check whether the link is normal.


Values Valid Values

Default Value

Disabled, Burst Mode, Continue Mode

Disabled


Description

Disabled

Indicates the test is not performed.

Burst Mode

Indicates that the system transmits a test frame every one second. The test ends after a specified number of test frames are transmitted.

Continue Mode

Indicates that the system continuously transmits test frames with a frequency of 1 frame per second.

Configuration Guidelines Set this parameter according to the requirements of the test. l

To perform the test continuously, set the parameter to Continue Mode.

l

To stop the test, set the parameter to Disabled.


A.26 Orderwire Associated Parameters This topic describes the parameters for configuring the orderwire function.

Issue 03 (2013-02-20)


906



A.26.1 Call Waiting Time(s) Description The Call Waiting Time(s) parameter specifies the timeout period of searching an orderwire route. If the period of searching an orderwire route exceeds the specified value, the orderwire phone changes to the busy tone status.


Values Valid Values

Default Value

Unit

1-9

9

s

Configuration Guidelines For all the network elements (NEs) that communicate with each other over the orderwire phone, this parameter must be set to the same value. l

If the number of NEs is less than 30, usually, set the value to 5 seconds.

l

If the number of NEs is not less than 30, usually, set the value to 9 seconds.

Generally, set it to the default value (namely, 9 seconds).

A.26.2 Conference Call Description The Conference Call parameter specifies the phone numbers of network-wide orderwire calls.


Values Valid Values

Default Value

100-99999999

999


Issue 03 (2013-02-20)

For orderwire conference calls on each node of the same subnet, the phone number must be the same. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

907



l

The length of an orderwire conference call number can be set as required. The value range is 3-8.

l

The length of an orderwire conference call number must be consistent with that of the addressing call number.


A.26.3 Phone Description The Phone parameter specifies the phone numbers of orderwire addressing calls. An addressing call refers to a point-to-point call.


Values Valid Values

Default Value

100-99999999

101


The phone numbers of orderwire addressing calls cannot be duplicate within the same subnet.

l

The length of an orderwire call number can be set as required. The value range is 3-8. Within the same orderwire network, the length of orderwire call numbers must be consistent for each node.

l

The length of phone numbers used to make orderwire addressing calls must be consistent with that of conference call numbers.

Relationship with Other Parameters If the length of an orderwire phone number is set to another value, the orderwire addressing call number is changed to the default phone number that maps the length. For example, if the length of a phone number is set to contain three digits, the addressing call number is changed to the default number 101. If the length of the phone number is set to contain four digits, the addressing call number is changed to the default number 1001, and the rest may be deduced by analogy.

Issue 03 (2013-02-20)


908



A.26.4 Available Orderwire Port Description The Available Orderwire Port parameter specifies whether the optical interface is used to make orderwire calls.


Values Valid Values

Default Value

Available Orderwire Port

Bid-BidType-PortID


Description

Bid-BidType-PortID

Indicates the available optical interface of a board in a slot, which is used to set orderwire calls. l Bid indicates the slot number of the board used to set orderwire calls. l BidType indicates the name of the board used to set orderwire calls. l PortID indicates the number of the optical interface on the board used to set orderwire calls. For example, to set optical interface 1 on the N2SL16 board in slot 7, select 7-N2SL16-1.


Relationship with Other Parameters For the OptiX NG-SDH V100R003 and later versions, dynamically allocate the orderwire bytes. To make addressing calls or conference calls, add the optical interface from Available Orderwire Port to Selected Orderwire Port.

A.26.5 Available Conference Call Port Description The Available Conference Call Port parameter specifies whether the optical interface is used to make conference calls. Issue 03 (2013-02-20)


909




Values Valid Values

Default Value

Available Orderwire Port

Bid-BidType-PortID


Description

Bid-BidType-PortID

For example, to set optical interface 1 on the N2SL16 board in slot 7, select 7-N2SL16-1.

Configuration Guidelines The NG-SDH equipment supports the function of automatically releasing the ring of an orderwire conference call. For this reason, when the NG-SDH equipment is interconnected to each other, do not set this parameter when you make an orderwire conference call. When the NG-SDH equipment is interconnected to other equipment (for example, the OptiX OSN 9500), you can make orderwire conference calls only after Selected Conference Call Port is selected for the interconnected optical ports.


A.26.6 Subnet No. Length Description The Subnet No. Length parameter specifies the length of the subnet number of the orderwire subnets if the entire network is divided into multiple orderwire subnets.


Values Valid Values

Default Value

1, 2

1



910



Value

Description

1

Indicates that the subnet number contains one digit. Value range: 0-9

2

Indicates that the subnet number contains two digits. Value range: 0-99

Configuration Guidelines Select the value according to the number of orderwire subnets. l

If the number of orderwire subnets is less than 10, set Subnet No. Length to 1.

l

If the number of orderwire subnets is greater than 10, set Subnet No. Length to 2.


A.26.7 Subnet (Subnet No. for the Optical Interface) Description The Subnet (Subnet No. for the Optical Interface) parameter specifies the subnet number of the orderwire phone connected to the optical interface.


Values Valid Values

Default Value

0-99

-

Configuration Guidelines If the subnet number is set to 1, the value range is 0-9. If the subnet number length is set to 2, the value range is 10-99. For the optical ports in the same orderwire subnet, the subnet number must be the same.

Relationship with Other Parameters If the subnet number length is changed, to avoid conflict between the subnet number length and the number length of the subnet connected to the optical port, the system automatically clears all the specified numbers of the subnets connected to the optical port. All the subnet numbers mapping the optical ports are empty. Issue 03 (2013-02-20)


911



A.26.8 No.(F1 Data Port) Description The No. (F1 Data Port) parameter specifies the numbers of the F1 data ports that have the same direction.


Values Valid Values

Default Value

1-88

-


Description

1-60

Supported by the OptiX OSN 3500.

1-88

Supported by the OptiX OSN 7500.

NOTE

The OptiX OSN 1500A and the OptiX OSN 1500B do not support the F1 data ports that have the same direction.



A.26.9 Data Channel (F1 Data Port) Description The Data Channel (F1 Data Port) parameter specifies the uplink and downlink ports that pass through the F1 data.

Impact on the System After the data channel is cancelled, the services that pass through the F1 data port are interrupted. Issue 03 (2013-02-20)


912



Values Valid Values

Default Value

F1, Bid-BidType-PortID

-


Description

F1

Indicates the F1 data port of the NE.

Bid-BidType-PortID

Indicates a port that can be used to set a slot of the F1 data port. For example, to set optical interface 1 on the N2SL16 board in slot 7, select 7-N2SL16-1.

Configuration Guidelines When using the F1 data port, you need to configure its route. That is, set the 64 Kbit/s data being added to or dropped from the NE, or passing through the NE.

Relationship with Other Parameters You can correctly set the F1 data ports that have the same direction only when the F1 port is not set to Transparent ECC Overhead Transmission.

A.26.10 Overhead Byte (Broadcast Data Port) Description The Overhead Byte (Broadcast Data Port) parameter specifies the number of the overhead bytes, which are used to transmit orderwire broadcast data services, in the SDH frame header.


Values Valid Values

Default Value

SERIAL1, SERIAL2, SERIAL3, SERIAL4

SERIAL1



913



Value

Description

SERIAL1

Indicates the S1 byte in the SDH frame header.

SERIAL2


SERIAL3


SERIAL4


Configuration Guidelines Select the value according to the configuration.

Relationship with Other Parameters If the S1 byte, the S2 byte, the S3 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead, the broadcast data port may fail to be set.

A.26.11 Working Mode (Broadcast Data Port) Description The Working Mode (Broadcast Data Port) parameter specifies the working mode of the local interface at which broadcast data services are added or dropped.


Values Value

Valid Values

RS232, RS422

-


Issue 03 (2013-02-20)

Value

Description

RS232

Indicates an asynchronous transmission mode, in which no handshake signal is available. An NE operating in RS232 mode can communicate with an NE operating in RS232 or RS422 mode directly; in this case, data transmission is transparent and the maximum rate is 19.2 kbit/s.

RS422

RS422 port specifications differ from RS232 port specifications only in that an RS422 port can become an RS232 port by means of hardware jumpers.


914



Configuration Guidelines Select the value according to the interface.


A.26.12 Broadcast Data Source (Broadcast Data Port) Description The Broadcast Data Source (Broadcast Data Port) parameter specifies the source of the orderwire broadcast data service.


Values Valid Values

Default Value

No Data, SERIALx, BidBidType-PortID

-


Description

No Data

Clears all the broadcast data services.

SERIALx

Indicates the local broadcast data port. For example, SERIAL1.

Bid-BidType-PortID

Indicates a port that is used to set a slot of the F1 data port. For example, to set optical interface 1 on the N2SL16 board in slot 7, select 7-N2SL16-1.


Relationship with Other Parameters If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead, the broadcast data service may fail to be set. Issue 03 (2013-02-20)


915



A.26.13 Broadcast Data Sink (Broadcast Data Port) Description The Broadcast Data Sink (Broadcast Data Port) parameter specifies the sink of the orderwire broadcast data service.


Values Valid Values

Default Value

SERIALx, Bid-BidTypePortID

-


Description

SERIALx

Indicates the local broadcast data port, for example, SERIAL1.

Bid-BidType-PortID

Indicates a port that is used to set a slot of the F1 data port. For example, to set optical interface 1 on the N2SL16 board in slot 7, select 7-N2SL16-1.


Relationship with Other Parameters If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead, the broadcast data service may fail to be set.

A.27 Clock Associated Parameters To synchronize the clocks on a network, you need to set the parameters that are associated with clocks.

Issue 03 (2013-02-20)


916



A.27.1 External Clock Output Mode Description The External Clock Output Mode parameter sets the output mode of the external clock source to 2 Mbit/s or 2 MHz.

Impact on the System Modifying the output mode of the external clock source may result in switching between clock sources, which may result in bit errors in services.

Values Valid Value

Default Value

l 2 MHz

2 Mbit/s

l 2 Mbit/s


Description

2 MHz

Indicates that the output mode of the external clock source is 2 MHz. That is, the external clock source outputs 2 MHz clock signals.

2 Mbit/s

Indicates that the output mode of the external clock source is 2 Mbit/s.

Configuration Guidelines Input modes of the two channels of external clock signals can be set to 2 MHz or 2 Mbit/s. The default input mode is 2 Mbit/s. In practical application, make sure that the output mode matches the input mode on the receive end.



A.27.2 External Clock Output Timeslot Description The External Clock Output Timeslot parameter sets the timeslot for transmitting the S1 byte of the external clock source. The external clock source transmits the S1 byte through a certain Issue 03 (2013-02-20)


917



timeslot. After starting the SSM protocol, make sure that the timeslot for receiving the S1 byte is consistent with the timeslot for transmitting the S1 byte so that the S1 byte can be received correctly.

Impact on the System When the SSM protocol is enabled on NEs, setting the S1 byte may result in switching between clock sources. This may generate bit errors in services when clock jitters occur.

Values Valid Value

Default Value

l SA4

All versions

l SA5 l SA6 l SA7 l SA8 l All versions


Description

SA4

Indicates that the S1 byte is transmitted through the SA4 timeslot of the external clock port.

SA5


SA6


SA7


SA8


All versions

Indicates that the S1 byte is transmitted through all timeslots of the external clock port.


Relationship with Other Parameters This parameter is valid only when the External Clock Output Mode parameter is set to 2 Mbit/ s. Issue 03 (2013-02-20)


918




A.27.3 External Source Output Threshold Description The External Source Output Threshold parameter sets the output quality threshold for the external clock source. When output quality of the external clock source is inferior to the threshold, the action specified for a 2M phase-locked source failure is invoked to control the external clock source output.


Values Valid Value

Default Value

Threshold Disabled, Not Inferior to G.813 SETS Signal, Not Inferior to G.812 Local Clock Signal, Not Inferior to G.812 Transit Clock Signal, Not Inferior to G.811 Clock Signal

Threshold Disabled


Issue 03 (2013-02-20)

Value

Description

Threshold Disabled

Indicates that the external source quality threshold is disabled.

Not Inferior to G.813 SETS Signal

Indicates that the external clock source becomes invalid when its output quality is inferior to the quality defined in G.813.

Not Inferior to G.812 Local Clock Signal

Indicates that the external clock source becomes invalid when its output quality is inferior to the clock quality of local nodes defined in G.812.

Not Inferior to G.812 Transit Clock Signal

Indicates that the external clock source becomes invalid when its output quality is inferior to the clock quality of transit nodes defined in G.812.

Not Inferior to G.811 Clock Signal

Indicates that the external clock source becomes invalid when its output quality is inferior to the quality defined in G.811.


919



Configuration Guidelines The output quality of the external clock source should not be inferior to the specified quality threshold. Therefore, the quality threshold should be set to a value that is inferior to or equal to the output clock quality of NEs.

Relationship with Other Parameters This parameter is valid only when the Protection Status parameter is set to Start Standard SSM Protocol.


A.27.4 2M Phase-Locked Source Fail Condition Description The 2M Phase-Locked Source Fail Condition parameter sets a failure condition for the 2M phase-locked source.


Values Valid Value

Default Value

l No Failure Condition

No Failure Condition

l AIS l LOF l AIS OR LOF


Issue 03 (2013-02-20)

Value

Description

No Failure Condition

Indicates that no failure condition is set. The 2M phase-lock source remains valid when an AIS or LOF alarm occurs in the external clock signal.

AIS

Indicates that the 2M phase-lock source becomes invalid when an AIS alarm occurs in the external clock signal.

LOF

Indicates that the 2M phase-lock source becomes invalid when an LOF alarm occurs in the external clock signal. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

920



Value

Description

AIS OR LOF

Indicates that the 2M phase-lock source becomes invalid when an AIS or LOF alarm occurs in the external clock signal.

Configuration Guidelines A failure condition can be set as required.



A.27.5 2M Phase-Locked Source Fail Action Description The 2M Phase-Locked Source Fail Action parameter specifies the action to be invoked in the case of a 2M phase-locked source failure. When the reference clock signal for locking external clock output is invalid or the quality if inferior to the threshold, the specific action is invoked to control the external clock output by either shutting down the output or inserting an AIS alarm.


Values Valid Value

Default Value

l Shut Down Output

Shut Down Output

l Send AIS l 2M Output S1 Byte Unavailable


Issue 03 (2013-02-20)

Value

Description

Shut Down Output

Indicates that the external clock signal output is shut down.

Send AIS

Indicates that the external clock sends all "1"s signals.

2M Output S1 Byte Unavailable

Indicated that the S1 byte sent by the external clock is invalid. That is, the external clock sends 0x0f.


921



Configuration Guidelines When the 2M phase-locked source is invalid, the output action can be set as required. When the External Clock Output Mode parameter is set to 2 MHz, the external clock signal output is shut down no matter what action is set.



A.27.6 Clock Source Priority Sequence (1 Is the Highest) Description The Clock source priority sequence(1 is the highest) parameter specifies the priority level of a certain clock source in the system clock priority table.

Impact on the System When the SSM protocol is disabled or the extended SSM protocol is enabled, the current trace clock source may be changed if the clock source priority sequence is changed. As a result, bit errors may occur in the service or the service may be interrupted transiently.

Values Value Range

Default Value

1, 2, 3…

1


Issue 03 (2013-02-20)

Value

Description

1

Indicates that this clock source is at the highest priority level in the system clock priority table.

2

Indicates that this clock source is at the second highest priority level in the system clock priority table.

3

Indicates that this clock source is at the third highest priority level in the system clock priority table.

…

…


922



Configuration Guidelines This parameter specifies the priority level of a certain clock source in the system clock priority table. The value ranges from 1 to N. N represents the total number of clock sources in the system clock priority table. Generally, the internal clock source is at the lowest priority level. For example, there are four clock sources in the system clock priority table: one external clock source, one line clock source, one tributary clock source, and one internal clock source. The priority level of the external clock source is set to 1, the priority level of the line clock source is set to 2, the priority level of the tributary clock source is set to 3 (the priority levels of the external clock source, line clock source, and tributary clock source cannot be the same), and the priority level of the internal clock source is always set to 4. In the actual application, this parameter is set according to the specific networking situation.

A.27.7 Clock Source Threshold Description The Clock Source Threshold parameter indicates the lower quality threshold of 2M external clock source. When the clock quality level of the external clock source that is selected from the 2M phase-locked source priority table is inferior to the threshold, the 2M phase-locked source becomes invalid, and the action specified for 2M phase-locked source failure is invoked to control the external clock source output.


Values Value Range

Default Value

l No Threshold Value

No Threshold Value

l G.813 SETS Signal l G.812 Lock Clock Signal l G.812 Transit Clock Signal l G.811 Clock Signal


Issue 03 (2013-02-20)

Value

Description

No Threshold Value

Threshold disabled

G.813 SETS Signal

Indicates that the lower threshold is not inferior to the G.813 SETS signal.

G.812 Lock Clock Signal

Indicates that the lower threshold is not inferior to the G.812 lock clock signal.


923



Value

Description

G.812 Transit Clock Signal

Indicates that the lower threshold is not inferior to the G.812 transit clock signal.

G.811 Clock Signal

Indicates that the lower threshold is not inferior to the G.811 clock signal.

Configuration Guidelines In actual application, the output quality threshold of external clock source should be determined according to the quality information about the NE clock and the opposite NE.



A.27.8 Protection Status Description The Protection Status parameter indicates the working mode of the clock protocol for a clock subnet.

Impact on the System The algorithm adopted by the system to select a clock source varies with the parameter value.

Values Value Range

Default Value

Start Extended SSM Protocol, Start Standard SSM Protocol, Stop SSM Protocol

Stop SSM Protocol

Configuration Guidelines The protection status of the entire clock subnet should be consistent. To avoid a clock tracing loop on a ring or mesh network, it is recommended that you set this parameter to Start Extended SSM Protocol.



924



Related Information As a mechanism adopted by the synchronous network for synchronization management, the standard SSM protocol is loaded in the lower four bits of the S1 byte. The standard SSM protocol allows nodes to exchange the quality information of clock sources. Hence, the SSM protocol enables the system to automatically select the clock source with the highest priority and also avoids a timing loop. The standard SSM protocol is applicable to interconnection with the equipment of other suppliers. Based on the standard SSM protocol, the extended SSM protocol presents a concept of clock source ID. The higher four bits of the S1 byte indicate a unique clock source ID, which is transmitted with the SSM. When receiving the S1 byte, a node checks the clock source ID to see whether the clock source derives from itself. If the clock source derives from the node, the node considers the clock source as unavailable. In this manner, a clock inter-lock loop is avoided when the clock tracing path is configured as a ring. The extended SSM protocol is applicable to the interconnection of transmission equipment from Huawei. When the SSM protocol is disabled, the clock source is selected according to the priority table.

A.27.9 AIS Alarm Generated Description The AIS Alarm Generated parameter specifies whether an AIS alarm is a condition for triggering the switching of clock sources.


Values Value Range

Default Value

l Yes

No

l No


Issue 03 (2013-02-20)

Value

Description

Yes

Indicates that an AIS alarm is the sufficient condition to trigger clock source switching.

No

Indicates that an AIS alarm is not a condition for triggering clock source switching.


925



Configuration Guidelines It is recommended to set the AIS alarm as the condition for triggering clock source switching in actual application to ensure system performance.



A.27.10 B1 BER Threshold-Crossing Generated Description The B1 BER Threshold-Crossing Generated parameter specifies whether a B1 BER thresholdcrossing alarm is a condition for triggering clock source switching. B1 BER Threshold-Crossing alarm is an index for measuring the performance of clock source signals.


Values Value Range

Default Value

l Yes

No

l No


Description

Yes

Indicates that a B1 BER threshold-crossing alarm is the sufficient condition for triggering clock source switching.

No

Indicates that a B1 BER threshold-crossing alarm is not the condition for triggering clock source switching.

Configuration Guidelines A B1 BER threshold-crossing alarm indicates that the transmitted signal and the clock in the signal are being interfered. Therefore, this parameter can be set as a condition for triggering clock source switching in actual application to ensure system performance. Issue 03 (2013-02-20)


926





A.27.11 B2-EXC Alarm Generated Description The B2-EXC Alarm Generated parameter specifies whether a B2-EXC alarm is a condition for triggering clock source switching. B2-EXC alarm is an index for measuring the performance of clock source signals.


Values Value Range

Default Value

l Yes

No

l No


Description

Yes

Indicates that a B2-EXC alarm is the sufficient condition for triggering clock source switching.

No

Indicates that a B2-EXC alarm is not the condition for triggering clock source switching.

Configuration Guidelines A B2-EXC alarm indicates that the transmitted signal and the clock in the signal are being interfered. Therefore, this parameter can be set as a condition for triggering clock source switching in actual application to ensure system performance.



927




A.27.12 Higher Priority Clock Source Reversion Mode Description The Higher Priority Clock Source Reversion Mode parameter specifies whether to switch from the lower-priority clock source back to the higher-priority clock source after the higherpriority clock source is restored to normal.

Impact on the System If the conditions for clock source switching are excessively strict, jitters may occur in the monitoring results of the clock status. If the auto-revertive mode is selected, the frequent switching of clock sources may affect the service.

Values Value Range

Default Value

l Non-Revertive

Auto-Revertive

l Auto-Revertive


Description

Non-Revertive

Indicates that the higher-priority clock source cannot be selected automatically after it is restored to normal.

Auto-Revertive

Indicates that the higher-priority clock source is selected automatically after it is restored to normal.

Configuration Guidelines If the conditions for clock source switching are properly set and the switching of clock sources can be guaranteed, the Auto-Revertive mode can be selected to improve clock quality. Otherwise, the Non-Revertive mode is recommended to avoid clock jitters.




928



A.27.13 Clock Source WTR Time Description The Clock Source WTR Time parameter specifies the wait-to-restore (WTR) time when the Higher Priority Clock Source Reversion Mode parameter is set to Auto-Revertive. When a clock source is restored to its valid status, the system does not regard it as a valid source immediately but verifies the validity of the clock source in a specific period of time. The system regards the clock source as a valid source only if the clock source remains valid during the specific period of time. This specific period of time is called the WTR time of the clock source.

Impact on the System Insufficient WTR time may result in wrong judgments on clock source restoration and clock status jitters, which may interrupt the service.

Values Value Range

Default Value

0-12

5

Configuration Guidelines The WRT time is counted in minutes. The shorter the WTR time is, the faster the clock is recovered, and the higher the average clock quality is. On the other hand, the shorter the WTR time is, the more likely the clock jitters are caused due to unstable clock signals. Therefore, do not set the WTR time to 0 in actual application.

Relationship with Other Parameters The setting of the WTR time is valid only when the Higher Priority Clock Source Reversion Mode parameter is set to Auto-Revertive.


A.27.14 Switching Status (Clock) Description The Switching Status (Clock) parameter indicates the current switching status of a clock source in the clock priority table.



929



Values Value Range

Default Value

l Normal

Normal

l Forced Switching l Manual Switching


Description

Normal

Indicates that the clock source in the clock priority table is in the normal trace status.

Forced Switching

Indicates that the clock source in the clock priority table is in the forced switching status.

Manual Switching

Indicates that the clock source in the clock priority table is in the manual switching status.




A.27.15 Lock Status (Clock) Description The Lock Status (Clock) parameter indicates the lock status of a clock source in the priority table.


Issue 03 (2013-02-20)


930



Values Value Range

Default Value

l Lock

Unlock

l Unlock


Description

Lock

Indicates that a certain channel of clock source in the priority table is in the lock status where the switching of clock sources is not allowed.

Unlock

Indicates that a certain channel of clock source in the priority table is in the unlock status where the switching of clock sources is allowed.




A.27.16 Clock Source ID Description The Clock Source ID parameter specifies the clock source ID information that is transmitted in the four most significant bits of the overhead S1 byte to avoid timing loops. This parameter works in the extended SSM protocol mode.


Issue 03 (2013-02-20)


931



Values Value Range

Default Value

l 1-15

None

l None.

Configuration Guidelines In actual application where the extended SSM protocol is enabled, the clock source IDs should be set as required by network planning to ensure that the ID is network-wide unique.

Relationship with Other Parameters This parameter is valid only when the extended SSM protocol is enabled.


A.27.17 Synchronous Source Description The Synchronous Source parameter indicates the synchronous clock source that is being traced. The synchronous clock source here refers to a certain clock source contained in the system clock priority table.


Values Value Range

Default Value

Clock Source in System Clock Priority Table

None


Issue 03 (2013-02-20)

Value

Description

Clock Source in System Clock Priority Table

Indicates that the system clock priority table contains the tributary clock sources, line clock sources, external clock sources, and internal clock sources.


932






A.27.18 Synchronous Status Byte Description The Synchronous Status Byte parameter sets the timeslot for carrying SSM information in the external clock source. The SSM information can be received from the external clock port only when a timeslot is set correctly. The timeslot for receiving the S1 byte ranges from SA4 to SA8.

Impact on the System If the synchronous status byte of the external clock source cannot be set correctly as required, the NEs may fail to receive the clock quality information correctly and the NE clock may be out of synchronization.

Values Value Range

Default Value

l SA4

SA4

l SA5 l SA6 l SA7 l SA8


Issue 03 (2013-02-20)

Value

Description

SA4

Indicates that timeslot slot 0 is used for receiving the S1 byte.

SA5


SA6


SA7


SA8



933



Configuration Guidelines The timeslot for receiving the S1 byte is set for external clock source only. The timeslot can be set to SA4, SA5, SA6, SA7 or SA8. The default timeslot is SA6. In actual application, make sure that the specified timeslot for receiving the S1 byte is the timeslot for carrying the SSM information in the external clock source. That is, the specified timeslot for receiving the S1 byte is the transmit timeslot of the opposite NE.



A.27.19 S1 Byte Synchronization Quality Information Description The S1 Byte Synchronization Quality Information parameter indicates the synchronization quality information in the S1 byte that is output by the current traced synchronous source. The S1 byte defined by the ITUT is used to transmit the quality information about the clock sources. It indicates the quality information of 16 types of synchronous sources with bits 5-8 of the S1 byte in the section overhead. With this quality information and certain switching protocols, the automatic protection switching of the synchronization clock can be realized in the synchronous network.


Values Value Range

Default Value

l Synchronous Source Unavailable

None

l Quality Unknown l G.811 Reference Clock l G.812 Transit Clock l G.812 Local Clock l SDH equipment timing source (SETS) signal


Issue 03 (2013-02-20)


934



Value

Description

Synchronous Source Unavailable

Indicates that the SSM protocol is disabled and the S1 byte synchronization quality information output by the synchronous source is not available.

Quality Unknown

Indicates that the SSM protocol is started but the S1 byte synchronization quality information output by the synchronous source is unknown.

G.811 Reference Clock

Indicates that the SSM protocol is started and the S1 byte synchronization quality information output by the synchronous source is the G.811 reference clock.

G.812 Transit Clock

Indicates that the SSM protocol is started and the S1 byte synchronization quality information output by the synchronous source is the G.812 transit clock.

G.812 Local Clock

Indicates that the SSM protocol is started and the S1 byte synchronization quality information output by the synchronous source is the G.812 local clock.

SDH equipment timing source (SETS) signal

Indicates that the SSM protocol is enabled and the S1 byte synchronization quality information output by the synchronous source is the synchronous equipment timing source (SETS) clock.




A.27.20 NE Clock Working Mode Description The NE Clock Working Mode parameter sets the current working mode of the system clock to the normal, holdover or free-run mode.


Issue 03 (2013-02-20)


935



Values Value Range

Default Value

l Normal Mode

-

l Holdover Mode l Free-Run Mode


Description

Normal Mode

Indicates that the NE clock works in the tracing mode. That is, the NE clock traces and locks the working mode of its upper-level clock.

Holdover Mode

Indicates that the NE clock works in the holdover mode. That is, in this mode, the NE clock uses the frequency information that is stored before all timing reference signals are lost as its timing reference.

Free-Run Mode

Indicates that the NE clock works in the free-run mode. That is, the internal oscillator works in this mode when all external timing reference signals are lost.




A.27.21 Clock Source Quality Description The Clock Source Quality parameter specifies the clock source quality information. Such information is extracted from the S1 byte of individual clock sources according to the SSM encoding rules after the SSM protocol is enabled. If the clock quality information cannot be extracted, this parameter needs to be set manually.



936



Values Value Range

Default Value

l Automatic Extraction

Automatic Extraction

l G.811 Clock Signal l G.812 Transit Clock Signal l G.812 Local Clock Signal l G.813 SDH Equipment Timing source (SETS) Signal l Unknown Synchronization Quality


Description

Automatic Extraction

Indicates that the clock quality information is extracted automatically according to the encoding rules compliant with the SSM protocol.

G.811 Clock Signal

Indicates that the clock source quality is manually set to the G.811 clock signal.

G.812 Transit Clock Signal

Indicates that the clock source quality is manually set to the G.812 transit clock signal.

G.812 Local Clock Signal

Indicates that the clock source quality is manually set to the G.812 local clock signal.

G.813 SDH Equipment Timing Indicates that the clock source quality is manually set to the source (SETS) Signal SETS clock signal. Unknown Synchronization Quality

Indicates a message that is set in the negative direction of the selected synchronization source to avoid direct mutual locking of two adjacent NEs.

Configuration Guidelines This parameter is usually set to Automatic Extraction. When the equipment is interconnected to an NE from another manufacturer that complies with a different protocol, the clock source quality can be specified manually.

Relationship with Other Parameters The clock quality information is valid only when the SSM protocol is enabled.

Issue 03 (2013-02-20)


937




A.27.22 S1 Byte Received Description The S1 Byte Received parameter indicates the value of the S1 byte of the current traced source in the system clock priority table.


Values Value Range

Default Value

l SDH equipment timing source (SETS) signal


l G.812 Local Clock l G.812 Transit Clock l G.811 Reference Clock l Synchronous Source Unavailable


Description

SDH equipment timing source (SETS) signal

Indicates that the clock quality of the current traced source is 0x0b.

G.812 Local Clock

Indicates that the clock quality of the current traced source is 0x08.

G.812 Transit Clock





Indicates that the clock quality of the current traced source is 0x0f.



938





A.27.23 Line Port (Clock) Description The Line Port (Clock) parameter specifies the output port of SSM quality information about the line clock source and external clock source available in the existing system. This output port can transmit the quality information about the clock source by sending the S1 byte to the downstream NE.


Values Value Range

Default Value

l Line Clock Source Port

-

l External Clock Source Port


Description

Line Clock Source Port

Indicates that only the port on the line board where both physical board and logical board have been configured properly can be used as the output port of SSM quality information.

External Clock Source Port

Indicates that only the port on the board with external clock interfaces where both physical board and logical board have been configured properly can be used as the output port of SSM quality information.




939



Related Information The standard SSM protocol mode, also called as QL_ENABLE mode in the Recommendation G.781, is a universal switching mode of clock source. In this standard SSM protocol mode, when a clock source becomes invalid, the system automatically traces the clock source of the highest quality in the clock priority table according to the quality information contained in the SSM protocol. If two clock sources are both of the highest quality, the clock source of a higher priority is selected.

A.27.24 Control Status (Clock) Description The Control Status (Clock) parameter specifies whether the line port can transmit the quality information about the clock source by sending the S1 byte to the downstream NE. By setting this parameter, the transmission of the S1 byte through the ports of the clock source can be enabled or disabled.

Impact on the System Modifying the Control Status (Clock) parameter may cause loss of clock quality information transmitted to the downstream NE. Therefore, the clock of the downstream NE may be asynchronous with the clocks of other NEs in the synchronous network.

Values Value Range

Default Value

l Enable

Enable

l Disabled


Description

Enable

Indicates that the transmission of the S1 byte through the corresponding line port is enabled.

Disabled

Indicates that the transmission of the S1 byte through the corresponding line port is disabled.

Configuration Guidelines The Control Status (Clock) parameter can be set to an enabled or disabled status as required. The status is enabled by default. In actual application, if the output clock source on the line board is valid, the transmission of the S1 byte through line port is allowed so that the clocks of the NEs in the entire synchronous network are synchronous. Issue 03 (2013-02-20)


940




Related Information The standard SSM protocol mode, also called QL_ENABLE mode in the G.781, is a universal switching mode of the clock source. In this standard SSM protocol mode, when a clock source becomes invalid, the system automatically traces the clock source of the highest quality in the clock priority table according to the quality information contained in the SSM protocol. If two clock sources are both of the highest quality, the clock source of a higher priority is selected.

A.27.25 Line Port (Clock ID) Description The Line Port (Clock ID) parameter sets clock source ID in the S1 byte for the interconnection and isolation between different clock subnets. In the extended SSM protocol mode, the four most significant bits of the S1 byte are used for identifying the clock source ID to improve the clock protection performance in the SDH network and to effectively avoid the timing loop. The clock source ID is output by the line port only. The external clock cannot output the clock source ID.


Values Value Range

Default Value


-


Description


Indicates that only the port on the line board where both physical board and logical board have been configured properly can be used as the output port of the clock source ID.




941




A.27.26 Enabled Status (Clock ID) Description Then Enabled Status (Clock ID) parameter is used to enable or disable the output of the clock source ID for the interconnection and isolation between different subnets. In the extended SSM protocol mode, the four most significant bits of the S1 byte are used for identifying the clock source ID to improve the clock protection performance in the SDH network and to effectively avoid the timing loop. This parameter is used to enable or disable the output of the clock source ID. The output of the clock source ID by internal clock source cannot be disabled. This parameter is invalid for external clock, because the external clock cannot output the clock source ID.

Impact on the System In a system where the extended SSM protocol is adopted, modifying the Enable Status (Clock ID) parameter may result in clock tracing loop, which may make the originally synchronous clock sources asynchronous.

Values Value Range

Default Value

l Enabled

Enabled

l Disabled.


Description

Enabled

Indicates that the output of clock source ID through corresponding line ports is allowed.

Disabled.

Indicates that the output of clock source ID through corresponding line ports is forbidden.

Configuration Guidelines The Enabled Status (Clock ID) parameter can be set to an enable of disabled status as required. The status is enabled by default. In actual application, as long as the extended SSM protocol is started and the output clock source on the line board is valid, it is allowed to output clock source ID in the four most-significant bits of the S1 byte through line ports. This can ensure clock synchronization among the NEs in the entire synchronous network and prevent the occurrence of timing loops. Issue 03 (2013-02-20)


942



Relationship with Other Parameters There are three working modes of the SSM protocol: the disabled, standard and extended SSM protocol modes. This parameter is valid only when the extended SSM protocol mode is adopted by the current clock of the NEs.


A.27.27 Data Output Method in Holdover Mode Description The Data Output Method in Holdover Mode parameter specifies whether the data is output normally or the latest data is kept when the NE clock is in the holdover mode.


Values Value Range

Default Value

l Normal Data Output Mode

Normal Data Output Mode

l Keep the Latest Data


Description

Normal Data Output Mode

Indicates the normal data output mode. The duration of this output mode is determined by the phase lock. This data output mode can continue for a maximum of 24 hours.

Keep the Latest Data

Indicates that the latest phase-locked data is kept. This data output mode is a forced holdover mode.

Configuration Guidelines The Keep the Latest Data mode is a forced holdover mode. Therefore, the clock accuracy is not high. In actual application, the Normal Data Output mode is recommended.

Relationship with Other Parameters The NE clock can work in three modes: the trace, holdover, and free-run modes. This parameter is valid only when the NE clock is working in the holdover mode. Issue 03 (2013-02-20)


943




A.27.28 Manual Setting of 0 Quality Level Description The Manual Setting of 0 Quality Level parameter specifies the 0 quality level that is not provided in the SSM protocol. Users can add this parsing rule to specify the quality level represented by 0.


Values Value Range

Default Value

l Do Not Use For Synchronization

Do Not Use For Synchronization

l G.811 Reference Clock l G.812 Transit Clock l G.812 Local Clock l SETS Clock l Between G.811 Reference Clock and G.812 Transit Clock l Between G.812 Transit Clock and G.812 Local Clock l Between G.812 Local Clock and synchronous equipment timing source (SETS)


Issue 03 (2013-02-20)

Value

Description

Do Not Use For Synchronization

Indicates a message that is set in the negative direction of the selected synchronization source to avoid direct mutual locking of two adjacent NEs.


Indicates that the clock signal complies with the G.811 protocol.


944



Value

Description

G.812 Transit Clock

Indicates that the transit exchange clock signal complies with the G.812 protocol.

G.812 Local Clock

Indicates that the local office signal complies with the G. 812 protocol.

SETS Clock

Indicates the synchronous equipment timing source (SETS).

Between G.811 Reference Clock and G.812 Transit Clock

Indicates that the specified quality level is inferior to the quality level of the G.811 reference clock signal but is superior to the quality level of the G.812 transit clock signal.

Between G.812 Transit Clock and G.812 Local Clock

Indicates that the specified quality level is inferior to the quality level of the G.812 transit clock signal but is superior to the quality level of the G.812 local clock signal.

Between G.812 Local Clock and synchronous equipment timing source (SETS)

Indicates that the specified quality level is inferior to the quality level of the G.812 local clock signal but is superior to the quality level of the synchronous equipment timing source (SETS) clock signal.

Configuration Guidelines In actual application, this parameter can be set according to the quality information about specific NE clocks.

Relationship with Other Parameters The setting of this parameter is valid only when the SSM protocol is enabled.


A.27.29 Retiming Mode Description The Retiming Mode parameter specifies whether the retiming clock, tributary clock, or crossconnect (external) clock is used.

Impact on the System If the downstream board that corresponds to this board provides the clock source for the downstream NE, the selection of the user affects the precision of the downstream NE.

Issue 03 (2013-02-20)


945



Values Value Range

Default Value

Normal, Retiming Mode of Tributary Clock, Retiming Mode of Cross-Connect Clock

Normal


Description

Normal

Indicates that the retiming clock is not used.

Retiming Mode of Tributary Clock

Indicates that the tributary clock is used as the retiming clock.

Retiming Mode of CrossConnect Clock

Indicates that the cross-connect (external) clock is used as the retiming clock.

Configuration Guidelines Select the proper clock according to the actual networking planning of the user. This parameter is applicable to the PQ1 and PQM boards. When the PQM board functions as the protection board, the function of setting the retiming mode is unavailable.

A.28 Protection Associated Parameters This topic describes the parameters for configuring multiplex section protection (MSP), subnetwork connection protection (SNCP), board protection switching (BPS), and path protection switching (PPS).

A.28.1 Switching Mode (MSP) Description The Switching Mode parameter specifies the switching mode of the linear MSP.


Issue 03 (2013-02-20)


946



Values Value Range

Default Value

Single-Ended Switching, DualEnded Switching

Single-Ended Switching


Description

Single-Ended Switching

Indicates that the transmit end continues to transmit signals to the broken fiber after the switching occurs at the faulty end.

Dual-Ended Switching

Indicates that the transmit end does not transmit signals to the broken fiber after the switching occurs at the transmit end and at the receive end.

Configuration Guidelines In the case of the 1+1 MSP, you can set this parameter to Single-Ended Switching or DualEnded Switching. In the case of the 1:N MSP, you can set this parameter to Dual-Ended Switching only.

A.28.2 Initiation Condition (SNCP) Description The Initiation Condition parameter specifies the condition for monitoring the switching of the SNCP pair.


Values Value Range

Default Value

TIM, EXC, SD, UNEQ

EXC, SD


Issue 03 (2013-02-20)

Value

Description

TIM

Indicates whether the HP_TIM alarm is monitored. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

947



Value

Description

EXC

Indicates whether the B3_EXC alarm is monitored.

SD

Indicates whether the B3_SD alarm is monitored.

UNEQ

Indicates whether the HP_UNEQ alarm is monitored.


A.28.3 Group Type (SNCP) Description The Group Type parameter specifies the grouping type of the SNCP services.

Impact on the System If switching occurs on any of several bound SNCP pairs, switching occurs on all the SNCP pairs.

Values Value Range

Default Value

Null, Virtual Concatenation Grouping

Null


Description

Null Virtual Concatenation Grouping

Indicates that the user needs to bind SNCP pairs.

Configuration Guidelines To bind SNCP pairs, the user needs to set this parameter to Virtual Concatenation Grouping for these SNCP pairs.

Relationship with Other Parameters The levels and attributes of the SNCP pairs to be bound must be the same. In addition, these SNCP pairs should be in the activated state. Issue 03 (2013-02-20)


948



A.28.4 Configure SNCP Tangent Ring Description If an NE is a tangent node on the SNCP ring, you can configure an SNCP group that has the same source but different sinks for the NE after this function is enabled.


Values Value Range

Default Value

Selected, Deselected

Deselected


Description

Selected

Specifies an SNCP group that has the same source but different sinks.

Deselected

Specifies an SNCP group that has the same source and same sink.

Configuration Guidelines When configuring SNCP for a tangent node on the SNCP ring, you can select the Configure SNCP Tangent Ring check box.


A.28.5 Source(Sink)Timeslot Range(e.g.1,3-6) Description The Source(Sink)Timeslot Range(e.g.1,3-6) parameter indicates the timeslot or timeslot range of a configured service.



949



Values The value range varies according to the specified service type. Service Type

Value Range

VC-4

1

VC-3

1 to 3

VC-12

1 to 63

Configuration Guidelines Enter multiple consecutive timeslots in the format of Start timeslot number-End timeslot number. Enter multiple inconsecutive timeslots in the format of ts1, ts2, .... You can enter the timeslots in a combination of the two formats.


A.28.6 Switching Status (BPS) Description The Switching Status (BPS) parameter shows the status of BPS switching.


Values Valid Value

Default Value

Forced Switch Request, Auto Switching, Idle, Unknown

Auto Switching


Issue 03 (2013-02-20)

Value

Description

Forced Switch Request

Indicates that services in a protection group are forcibly switched by using switching commands.

Auto Switching

Indicates the switching status of the protection group, which results from the faulty Ethernet board.

Idle

Indicates that the working and protection boards are normal. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

950



Value

Description

Unknown

Indicates that the switching status is unknown. You can learn about the current status through a query.



A.28.7 Switching Status (PPS) Description The Switching Status (PPS) parameter specifies the status of PPS switching.


Values Value Range

Default Value

Forced Switching(Protection to Working), Forced Switching(Working to Protection), Normal

Normal


Issue 03 (2013-02-20)

Value

Description

Normal

Indicates the status when no switching is required, namely, the normal status.

Forced Switching(Protection to Working)

Forcibly switches the service from the working path to the protection path. The switching is implemented regardless of the status of the protection path, unless the protection path meets the bridging requirement of higher priority.

Forced Switching(Working to Protection)

Forcibly switches the service from the protection path to the working path. The switching is implemented regardless of the status of the working path, unless the working path meets the bridging requirement of higher priority.


951





A.28.8 External Switching Command Type (BPS) Description External Switching Command Type (BPS) indicates forcibly switching services in the BPS protection group to the working board or protection board by running the external switching command.

Impact on the System If the working board and protection board are normal, a forced switching may lead to a transient service interruption. If either one of the working board and protection board is faulty, a forced switching may lead to a service interruption.

Values Value Range

Default Value

Forced Switching to Working, Forced Switching to Protection, Clear Switching

-


Description

Forced Switching to Working

Indicates forcibly switching services from the protection board to working board. This switching neglects the status of the working channel, unless the working channel meets the request of a bridge with a higher priority.

Forced Switching to Protection

Indicates forcibly switching services from the working board to protection board. This switching neglects the status of the protection channel, unless the protection channel meets the request of a bridge with a higher priority.

Clear Switching

Indicates clearing the current switching status.

Configuration Guidelines Set this parameter as required. Issue 03 (2013-02-20)


952




A.28.9 External Switching Command Type (PPS) Description External Switching Command Type (PPS) indicates forcibly switching services in the PPS protection group to the working board or protection board by running the external switching command.

Impact on the System If the working port and protection port are normal, a forcible switching may lead to a transient service interruption. If either one of the working board and protection board is faulty, a forcible switching may lead to a service interruption.

Values Value Range

Default Value

Query Protection Group Status, Forced Switch to Working, Forced Switch to Protection, Manual Switch to Working, Manual Switch to Protection, Lockout of Protection, Clear

-


Issue 03 (2013-02-20)

Value

Description

Query Protection Group Status

Indicates querying the status of the protection group.

Forced Switch to Working

Indicates forcibly switching the service from the protection channel to the working channel. This switching neglects the status of the working channel, unless the working channel meets the request of a bridge with a higher priority.

Forced Switch to Protection

Indicates forcibly switching the service from the working channel to the protection channel. The switching does not consider the status of the protection channel, unless the protection channel runs an external switching command of a higher priority.

Manual Switch to Working

Indicates manually switching the service from the protection channel to the working channel. If the working channel is normal, a switching is triggered. If the working channel fails or is satisfying the switching request of a bridge with a higher priority, a switching is not triggered.


953



Value

Description

Manual Switch to Protection

Indicates manually switching the service from the working channel to the protection channel. If the protection channel is normal, a switching is triggered. If the protection channel fails or is satisfying the switching request of a bridge with a higher priority, a switching is not triggered.

Lockout of Protection

The priority of the lockout of protection is lower than the priority of the forced switching and the priority of the manual switching. The lockout of protection can only lock the current automatic switching status.

Clear

Indicates clearing the current switching status.

Configuration Guidelines Set this parameter as required.


A.29 Other Parameters This topic describes the parameters related to PDH interfaces and SDH interfaces.

A.29.1 E1/T1 Interconnection Description The E1/T1 Interconnection parameter specifies whether the frame structure is checked and indicates the checking mode, in the case of an E1/T1 interconnection.

Impact on the System The local NE and downstream NE are not affected.

Values Value Range

Default Value

Transparent transmission, Interconnection monitored, Interconnection unmonitored

Transparent transmission



954



Value

Description

Transparent transmission

Indicates that the frame structure is transparently transmitted.

Interconnection unmonitored

Indicates that the frame structure is not monitored in the case of an E1/T1 interconnection.

Interconnection monitored

Indicates that the frame structure is monitored in the case of an E1/T1 interconnection.

Configuration Guidelines When the service is of the E1 type, the setting of Interconnection unmonitored and Interconnection monitored is not supported. When the service is of the T1 type, the setting of Transparent transmission is not supported. When the service is changed from T1 to E1, the value of this parameter is automatically changed to Transparent transmission. This parameter is applicable to the PQM board.

A.29.2 T1 Frame Structure Description The T1 Frame Structure parameter specifies whether the structure of the T1 frame is set to Unframed or whether the D4, ESF, SLC96, F4, or M13 frame structure is monitored.


Values Value Range

Default Value

Unframed, D4, ESF, SLC96, F4, M13

Unframed


Issue 03 (2013-02-20)

Value

Description

Unframed

Indicates that the frame format is not monitored in transparent transmission mode.

D4

Indicates the structure of the T1 frame.

ESF


SLC96

Indicates the structure of the T1 frame. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

955



Value

Description

F4


M13


Configuration Guidelines In transparent transmission mode, this parameter is valid when the frame is set to be monitored and the service is of the T1 type. In this case, the frame format is the format of the accessed service. If you need not monitor the frame format when the frame format is monitored, set this parameter to Unframed. In interconnection unmonitored mode, this parameter is valid and used to define the frame format of the output service. In interconnection monitored mode, this parameter is valid. In this case, the port monitors the accessed service and defines the frame format of the output service according to the frame format specified by this parameter. This parameter is applicable to the PQM board.


A.29.3 E1 Frame Structure Description The E1 Frame Structure parameter specifies whether the structure of the E1 frame is set to Framed, Unframed or whether the PCM30, PCM31, PCM30CRC, or PCM31CRC frame format is monitored.


Values Value Range

Default Value

Framed, Unframed, PCM30, PCM31, PCM30CRC, PCM31CRC

Unframed



956



Value

Description

Framed

Indicates that the frame format is monitored in transparent transmission mode.

Unframed

Indicates that the frame format is not monitored in transparent transmission mode.

PCM30

Indicates the structure of the E1 signal. 30 timeslots are available for users, that is, TS1-TS15 and TS17-TS31. Timeslot TS16 is used to transmit signaling. This type of structure does not provide the CRC check.

PCM31

Indicates the structure of the E1 signal. 31 timeslots are available for users, that is, TS1-TS15 and TS17-TS31. Timeslot TS16 does not transmit signaling. This type of structure does not provide the CRC check.

PCM30CRC

Indicates the structure of the E1 signal. 30 timeslots are available for users, that is, TS1-TS15 and TS17-TS31. Timeslot TS16 is used to transmit signaling. This type of structure provides the CRC check.

PCM31CRC

Indicates the structure of the E1 signal. 31 timeslots are available for users, that is, TS1-TS15 and TS17-TS31. Timeslot TS16 does not transmit signaling. This type of structure provides the CRC check.

Configuration Guidelines In transparent transmission mode, this parameter is valid when the frame is set to be monitored and the service is of the E1 type. In this case, the frame format is the format of the accessed service. If you need to monitor the frame format when the frame format is not monitored, set this parameter to Unframed. In interconnection unmonitored mode, this parameter is valid and used to define the frame format of the output service. In interconnection monitored mode, this parameter is valid. In this case, the port monitors the accessed service and defines the frame format of the output service according to the frame format specified by this parameter. This parameter is applicable to the PQM board.


A.29.4 Service Mode Description The Service Mode parameter indicates the actual working mode of the board that supports the M13/E13 function. Issue 03 (2013-02-20)


957




Values Value Range

Default Value

Normal Mode, MUX Mode, Server Mode

Normal Mode


Description

Normal Mode

Indicates that the processing mode of the tributary board is consistent with the processing mode of the board that does not provide the M13/E13 function. For example, in normal mode, the E1 service is added to or dropped from the N2PQ1 board and the cross-connection at the VC-12 level is configured.

MUX Mode

Indicates that three VC-3 cross-connections are configured. E1 signals are received or transmitted on the first 48 channels of the interface board. Each VC-3 cross-connection corresponds to 16 E1 signals.

Server Mode

Indicates that the tributary board does not drop any service, but realizes the conversion between E1 and E3 signals only.

Configuration Guidelines Select a proper value according to the actual requirement of the user. This parameter is applicable to the N2PQ1, R2PD1, N2PQ3, N2PD3, N2PL3, and N2PL3A boards.

A.29.5 Service Type Description The Service Type parameter specifies the service type of PDH signals.


Issue 03 (2013-02-20)


958



Values Value Range

Default Value

E13, M13

E13


Description

E13

Indicates the structure of the PDH frame.

M13

Indicates the structure of the PDH frame.

Configuration Guidelines Set this parameter to E13 when you need to convert E1 signals to E3 signals or convert E3 signals to E1 signals. Set this parameter to M13 when you need to convert T1 signals to T3 signals or convert T3 signals to T1 signals. This parameter is applicable to the N2PQ1, N2PQ3, N2PL3, N2PL3A, N2PD3, and R2PD1 boards that are used on the OptiX NG-SDH equipment series.

A.29.6 Service Frame Format Description The Service Frame Format parameter specifies whether the tributary board monitors the frame format of the signal. This parameter determines whether the frame format of the signal is monitored only, and does not affect services. If the frame format of the service transmitted from the opposite end is inconsistent with the frame format of the service at the local end or if the service transmitted from the opposite end does not have any frame format, a large number of LFA/RFA alarms are reported.

Impact on the System When you set the frame format of the service supported by the board to Unframe, the system is not affected if the framing mode set on the U2000 is inconsistent with the framing mode of the board. When you set the frame format of the service supported by the board to Frame, alarms indicating inconsistent frame formats may be reported on the U2000 if the framing mode set on the U2000 is inconsistent with the framing mode of the board.

Values

Issue 03 (2013-02-20)

Value Range

Default Value

Unframe, Frame

Unframe


959




Description

Unframe

Indicates that the tributary board does not monitor the frame format of the signal.

Frame

Indicates that the tributary board monitors the frame format of the signal.

Configuration Guidelines This parameter is applicable to the N2PQ1, N2PQ3, N2PL3, N2PL3A, N2PD3, and R2PD1 boards that are used on the OptiX NG-SDH equipment series.

A.29.7 Connection Mode (NE Attribute) Description The Connection Mode (NE Attribute) parameter indicates the connection mode between a gateway NE and the U2000. If the gateway NE is connected to the U2000 based on IP, two connection modes are available between them, namely, common mode, and security SSL mode.

Impact on the System The connection mode between the NE and the U2000 determines whether the NE and U2000 can communicate normally and securely with each other.

Values Value Range

Default Value

Common, Security SSL

Common


Issue 03 (2013-02-20)

Value

Description

Common

Indicates that the connection between the NE and the U2000 is not encrypted.

Security SSL

Indicates that the connection between the NE and the U2000 is encrypted.


960



Configuration Guidelines If the communication environment between the NE and the U2000 is secure, the common mode can be used. If the security requirement for the in-between communication is high, the security SSL mode can be used to prevent packet interception.

Relationship with Other Parameters This parameter is valid only when Gateway Type is set to Gateway and Protocol is set to IP.


A.29.8 Enable Tandem Connection at the Source Description The Enable Tandem Connection at the Source parameter specifies whether the tandem connection monitoring (TCM) function at the source end is enabled.


Values Value Range

Default Value

Disabled, Enabled

Disabled


Description

Disabled

Indicates that the TCM function is disabled.

Enabled

Indicates that the TCM function is enabled.

Configuration Guidelines Set this parameter according to the actual requirement of the user. If the TCM function is required, set this parameter to Enabled. Only the N2 board series in the SDH board category support the setting of this parameter because only these boards support the TCM function.



961



A.29.9 APId to be Sent at the Source Description The APId to be Sent at the Source parameter indicates the N1 byte to be sent based on the number of calculated bit errors.

Impact on the System The system is not affected because this function is used for testing.

Values Value Range

Default Value

A 16-byte string

[CRC Check] HuaWei SBS

Configuration Guidelines Set this parameter according to the actual requirement of the user. It is recommended that you use the default value.

A.29.10 Optimize Higher Order Pass-Through Description The Optimize Higher Order Pass-Through parameter indicates that the lower order services that do not necessarily require lower order cross-connection resources can use higher order crossconnections, therefore reducing the usage of lower order cross-connection resources.

Impact on the System If you enable the higher order pass-through optimization function, the services may be interrupted transiently, and the service interruption lasts for 50 ms.

Values Value Range

Default Value

Enabled, Disabled

Disabled


Issue 03 (2013-02-20)


962



Value

Description

Enabled

Indicates that the higher order pass-through optimization function is enabled. In this case, the lower order services that do not necessarily require lower order cross-connection resources can use higher order cross-connections.

Disabled

Indicates that the lower order services occupy lower order cross-connection resources.

Configuration Guidelines If lower order cross-connection resources are insufficient, you can enable the higher order paththrough function to configure more lower order services.


Issue 03 (2013-02-20)


963


B Glossary

B

Glossary

Numerics 2DM

two-way delay measurement

3G

See 3rd Generation.

3R

reshaping, retiming, regenerating

3rd Generation (3G)

The third generation of digital wireless technology, as defined by the International Telecommunications Union (ITU). Third generation technology is expected to deliver data transmission speeds between 144 kbit/s and 2 Mbit/s, compared to the 9.6 kbit/s to 19.2 kbit/s offered by second generation technology.

802.1Q in 802.1Q (QinQ)

A VLAN feature that allows the equipment to add a VLAN tag to a tagged frame. The implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to be transmitted over the service provider's backbone network based on the public VLAN tag. This provides a layer 2 VPN tunnel for customers and enables transparent transmission of packets over private VLANs.

A AAL

See ATM Adaptation Layer.

ABR

See available bit rate.

AC

alternating current

ACH

associated channel header

ACL

See access control list.

ACR

allowed cell rate

ADM

add/drop multiplexer

ADMC

automatically detected and manually cleared

ADSL

asymmetric digital subscriber line

AF

See assured forwarding.

AGC

automatic gain control

AIS

alarm indication signal

Issue 03 (2013-02-20)


964


B Glossary

ALC

See automatic level control.

ALS

See automatic laser shutdown.

AM

See adaptive modulation.

AMI

See alternate mark inversion.

AMU

ATM cell multiplex unit

ANSI

See American National Standards Institute.

APD

See avalanche photodiode.

APS

automatic protection switching

ARP

See Address Resolution Protocol.

ASCII

American Standard Code for Information Interchange

ASK

amplitude shift keying

ATM

asynchronous transfer mode

ATM Adaptation Layer (AAL)

An interface between higher-layer protocols and Asynchronous Transfer Mode (ATM). The AAL provides a conversion function to and from ATM for various types of information, including voice, video, and data.

ATPC

See automatic transmit power control.

AU

See administrative unit.

AUG

See administrative unit group.

AWG

arrayed waveguide grating

Address Resolution Protocol (ARP)

An Internet Protocol used to map IP addresses to MAC addresses. It allows hosts and routers to determine the link layer addresses through ARP requests and ARP responses.

American National Standards Institute (ANSI)

An organization that defines U.S standards for the information processing industry. ANSI participates in defining network protocol standards.

access control list (ACL)

A list of entities, together with their access rights, which are authorized to have access to a resource.

adaptive modulation (AM)

A technology that is used to automatically adjust the modulation mode according to the channel quality. When the channel quality is favorable, the equipment uses a highefficiency modulation mode to improve the transmission efficiency and the spectrum utilization of the system. When the channel quality is degraded, the equipment uses the low-efficiency modulation mode to improve the anti-interference capability of the link that carries high-priority services.

administrative unit (AU)

The information structure which provides adaptation between the higher order path layer and the multiplex section layer. It consists of an information payload (the higher order VC) and an AU pointer which indicates the offset of the payload frame start relative to the multiplex section frame start.

administrative unit group (AUG)

One or more administrative units occupying fixed, defined positions in an STM payload. An AUG consists of AU-4s.

alternate mark inversion (AMI)

A synchronous clock encoding technique which uses bipolar pulses to represent logical 1 values.

Issue 03 (2013-02-20)


965


B Glossary

assured forwarding (AF)

One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF. It is suitable for certain key data services that require assured bandwidth and short delay. For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that exceeds the bandwidth limit, AF degrades the service class and continues to forward the traffic instead of discarding the packets.

automatic laser shutdown (ALS)

A technique (procedure) to automatically shutdown the output power of laser transmitters and optical amplifiers to avoid exposure to hazardous levels.

automatic level control A feature that identifies speech signals and adjusts the sound volume to stay within a (ALC) comfortable range, improving user experience. automatic transmit A method of adjusting the transmit power based on fading of the transmit signal detected power control (ATPC) at the receiver available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible forwarding service and applies to the connections that does not require the real-time quality. It does not provide any guarantee in terms of cell loss or delay. avalanche photodiode (APD)

A semiconductor photodetector with integral detection and amplification stages. Electrons generated at a p/n junction are accelerated in a region where they free an avalanche of other electrons. APDs can detect faint signals but require higher voltages than other semiconductor electronics.

B B-ISDN

See broadband integrated services digital network.

BA

booster amplifier

BBE

background block error

BC

boundary clock

BCD

binary coded decimal

BDI

See backward defect indication.

BE

See best effort.

BER

bit error rate

BFD

See Bidirectional Forwarding Detection.

BGP

Border Gateway Protocol

BIOS

See basic input/output system.

BIP

See bit interleaved parity.

BIP-8

See bit interleaved parity-8.

BIP-X

bit interleaved parity-X

BITS

See building integrated timing supply.

BMC

best master clock

BNC

See bayonet-neill-concelman.

BPDU

See bridge protocol data unit.

BPS

board protection switching

BRAS

See broadband remote access server.

Issue 03 (2013-02-20)


966


B Glossary

BSC

binary synchronous communication

BSS

base station subsystem

BTS

base transceiver station

BWS

backbone wavelength division multiplexing system

Bidirectional Forwarding Detection (BFD)

A fast and independent hello protocol that delivers millisecond-level link failure detection and provides carrier-class availability. After sessions are established between neighboring systems, the systems can periodically send BFD packets to each other. If one system fails to receive a BFD packet within the negotiated period, the system regards that the bidirectional link fails and instructs the upper layer protocol to take actions to recover the faulty link.

backplane

An electronic circuit board containing circuits and sockets into which additional electronic devices on other circuit boards or cards can be plugged.

backward defect indication (BDI)

A function that the sink node of a LSP, when detecting a defect, uses to inform the upstream end of the LSP of a downstream defect along the return path.

basic input/output system (BIOS)

A firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, and system setting information. The BIOS provides hardware setting and control functions for the computer.

bayonet-neillconcelman (BNC)

A connector used for connecting two coaxial cables.

best effort (BE)

A traditional IP packet transport service. In this service, the diagrams are forwarded following the sequence of the time they reach. All diagrams share the bandwidth of the network and routers. The amount of resource that a diagram can use depends of the time it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss ratio, and high reliability.

bit interleaved parity (BIP)

A method of error monitoring. With even parity an X-bit code is generated by equipment at the transmit end over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, and so on. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the Xbit sequences in the covered portion of the signal. The covered portion includes the BIPX.

bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte) (BIP-8) in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0" over each column. Then fill a 1 in the corresponding bit for the result if the number is odd, otherwise fill a 0. bridge protocol data unit (BPDU)

Issue 03 (2013-02-20)

The data messages that are exchanged across the switches within an extended LAN that uses a spanning tree protocol (STP) topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology. The loops are then removed by shutting down selected bridges interfaces and placing redundant switch ports in a backup, or blocked, state.


967


B Glossary

broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as voice. services digital network It currently uses the ATM technology to transmit data over SONNET-based circuits at (B-ISDN) 155 to 622 Mbit/s or higher speed. broadband remote access server (BRAS)

A new type of access gateway for broadband networks. As a bridge between backbone networks and broadband access networks, BRAS provides methods for fundamental access and manages the broadband access network. It is deployed at the edge of network to provide broadband access services, convergence, and forwarding of multiple services, meeting the demands for transmission capacity and bandwidth utilization of different users. BRAS is a core device for the broadband users' access to a broadband network.

building integrated timing supply (BITS)

In the situation of multiple synchronous nodes or communication devices, one can use a device to set up a clock system on the hinge of telecom network to connect the synchronous network as a whole, and provide satisfactory synchronous base signals to the building integrated device. This device is called BITS.

built-in WDM

A function which integrates some simple WDM systems into products that belong to the OSN series. That is, the OSN products can add or drop several wavelengths directly.

C CAR

committed access rate

CAS

See channel associated signaling.

CAS multiframe

A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCM frames. Among the 8 bits of timeslot 16 in the first frame, the first 4 bits are used for multiframe synchronization. The multiframe alignment signal (MFAS) for synchronization is 0000. The last 4 bits are used as the not multiframe alignment signal (NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is used to transmit exchange and multiplexing (E&M) signaling corresponding to each timeslot.

CAU

See client automatic upgrade.

CBR

See constant bit rate.

CBS

See committed burst size.

CC

See continuity check.

CDVT

cell delay variation tolerance

CE

See customer edge.

CES

See circuit emulation service.

CFM

connectivity fault management

CFR

cell fill rate

CGMP

Cisco Group Management Protocol

CIR

committed information rate

CISPR

International Special Committee on Radio Interference

CIST

See Common and Internal Spanning Tree.

CLEI

common language equipment identification

CLNP

connectionless network protocol

CLP

See cell loss priority.

Issue 03 (2013-02-20)


968


B Glossary

CMI

coded mark inversion

CRC

See cyclic redundancy check.

CRC-4 multiframe

A multiframe recommended by ITU-T G.704 and set up based on the first bit of timeslot 0. The CRC-4 multiframe is different from the CAS multiframe in principle and implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4 multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a CRC-4 check block that contains 2048 (256 x 8) bits. Bits C1 to C4 of a check block can check the previous check block.

CSA

Canadian Standards Association

CSES

consecutive severely errored second

CSF

Client Signal Fail

CSMA/CD

See carrier sense multiple access with collision detection.

CSPF

constraint shortest path first

CST

See common spanning tree.

CV

connectivity verification

CW

control word

CWDM

See coarse wavelength division multiplexing.

Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the bridged local area network are simply and fully connected. Coordinated Universal The world-wide scientific standard of timekeeping. It is based upon carefully maintained Time (UTC) atomic clocks and is kept accurate to within microseconds worldwide. carrier sense multiple access with collision detection (CSMA/CD)

Carrier sense multiple access with collision detection (CSMA/CD) is a computer networking access method in which: l

A carrier sensing scheme is used.

l

A transmitting data station that detects another signal while transmitting a frame, stops transmitting that frame, transmits a jam signal, and then waits for a random time interval before trying to send that frame again.

cell loss priority (CLP) A field in the ATM cell header that determines the probability of a cell being dropped if the network becomes congested. Cells with CLP = 0 are insured traffic, which is unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be dropped. channel associated signaling (CAS)

A signaling system in which signaling information is transmitted within a dedicated voice channel. China Signaling System No. 1 is a type of CAS signaling.

circuit emulation service (CES)

A function with which the E1/T1 data can be transmitted through ATM networks. At the transmission end, the interface module packs timeslot data into ATM cells. These ATM cells are sent to the reception end through the ATM network. At the reception end, the interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES technology guarantees that the data in E1/T1 timeslots can be recovered to the original sequence at the reception end.

client automatic upgrade (CAU)

A function that enables a user to automatically detect the update of the client version and upgrade the client. This keeps the version of the client is the same as that of the server.

Issue 03 (2013-02-20)


969


B Glossary

coarse wavelength division multiplexing (CWDM)

A signal transmission technology that multiplexes widely-spaced optical channels into the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM does not support optical amplifiers and is applied in short-distance chain networking.

collision

A condition in which two packets are being transmitted over a medium at the same time. Their interference makes both unintelligible.

committed burst size (CBS)

A parameter used to define the capacity of token bucket C, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.

common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST region (CST) is considered as a switch; therefore, the CST can be considered as their spanning tree generated with STP/RSTP. constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on the constant bandwidth. It is applicable to service connections that depend on precise clocking to ensure undistorted transmission. continuity check (CC)

Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after MEPs transmit Continuity Check Messages (CCMs) periodically.

customer edge (CE)

A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the Service Provider (SP) network. A CE can be a router, switch, or host.

cyclic redundancy check (CRC)

A procedure used in checking for errors in data transmission. CRC error checking uses a complex calculation to generate a number based on the data transmitted. The sending device performs the calculation before transmission and includes it in the packet that it sends to the receiving device. The receiving device repeats the same calculation after transmission. If both devices obtain the same result, it is assumed that the transmission was error free. The procedure is known as a redundancy check because each transmission includes not only data but extra (redundant) error-checking values.

D DC

direct current

DC-C

See DC-return common (with ground).

DC-I

See DC-return isolate (with ground).

DC-return common (with ground) (DC-C)

A power system, in which the BGND of the DC return conductor is short-circuited with the PGND on the output side of the power supply cabinet and also on the line between the output of the power supply cabinet and the electric equipment.

DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with ground) (DC-I) the PGND on the output side of the power supply cabinet and is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment. DCC

See data communications channel.

DCE

data connection equipment

DCM

See dispersion compensation module.

DCN

See data communication network.

DDF

digital distribution frame

DDN

See digital data network.

Issue 03 (2013-02-20)


970


DE

discard eligible

DEI

device emulation interrupt

DHCP

See Dynamic Host Configuration Protocol.

DIP switch

dual in-line package switch

DLAG

See distributed link aggregation group.

DM

See delay measurement.

DNI

dual node interconnection

DRDB

dynamic random database

DSCP

See differentiated services code point.

DSL

See digital subscriber line.

DSLAM

See digital subscriber line access multiplexer.

DTE

See data terminal equipment.

DTMF

See dual tone multiple frequency.

DVB-ASI

digital video broadcast-asynchronous serial interface

DVMRP

See Distance Vector Multicast Routing Protocol.

DWDM

See dense wavelength division multiplexing.

DiffServ

See Differentiated Services.

B Glossary

Differentiated Services An IETF standard that defines a mechanism for controlling and forwarding traffic in a (DiffServ) differentiated manner based on CoS settings to handle network congestion. Distance Vector Multicast Routing Protocol (DVMRP)

An Internet gateway protocol mainly based on the RIP. The protocol implements a typical dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing datagrams with its neighbors.

Dynamic Host A client-server networking protocol. A DHCP server provides configuration parameters Configuration Protocol specific to the DHCP client host requesting, generally, information required by the host (DHCP) to participate on the Internet network. DHCP also provides a mechanism for allocation of IP addresses to hosts. data communication network (DCN)

A communication network used in a TMN or between TMNs to support the data communication function.

data communications channel (DCC)

The data channel that uses the D1–D12 bytes in the overhead of an STM-N signal to transmit information about operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1–D3 are referred to as the 192 kbit/s DCC-R channel. The other DCC channels that are composed of bytes D4–D12 are referred to as the 576 kbit/s DCC-M channel.

data terminal equipment (DTE)

A user device composing the UNI. The DTE accesses the data network through the DCE equipment (for example, a modem) and usually uses the clock signals produced by DCE.

delay measurement (DM)

The time elapsed since the start of transmission of the first bit of the frame by a source node until the reception of the last bit of the loopbacked frame by the same source node, when the loopback is performed at the frame's destination node.

Issue 03 (2013-02-20)


971


B Glossary

dense wavelength division multiplexing (DWDM)

The technology that utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths with specific frequency spacing as carriers, and allows multiple channels to transmit simultaneously in the same fiber.

differentiated services code point (DSCP)

According to the QoS classification standard of the Differentiated Service (Diff-Serv), the type of services (ToS) field in the IP header consists of six most significant bits and two currently unused bits, which are used to form codes for priority marking. Differentiated services code point (DSCP) is the six most important bits in the ToS. It is the combination of IP precedence and types of service. The DSCP value is used to ensure that routers supporting only IP precedence can be used because the DSCP value is compatible with IP precedence. Each DSCP maps a per-hop behavior (PHB). Therefore, terminal devices can identify traffic using the DSCP value.

digital data network (DDN)

A high-quality data transport tunnel that combines the digital channel (such as fiber channel, digital microwave channel, or satellite channel) and the cross multiplex technology.

digital subscriber line (DSL)

A technology for providing digital connections over the copper wire or the local telephone network. DSL performs data communication over the POTS lines without affecting the POTS service.

digital subscriber line access multiplexer (DSLAM)

A network device, usually situated in the main office of a telephone company that receives signals from multiple customer Digital Subscriber Line (DSL) connections and puts the signals on a high-speed backbone line using multiplexing techniques.

dispersion

The maximum error of the local clock compared with the reference clock.

dispersion compensation module (DCM)

A module, which contains dispersion compensation fibers to compensate for the dispersion of transmitting fiber.

distributed link aggregation group (DLAG)

A board-level port protection technology used to detect unidirectional fiber cuts and to negotiate with the opposite end. Once a link down failure occurs on a port or a hardware failure occurs on a board, the services can automatically be switched to the slave board, achieving 1+1 protection for the inter-board ports.

dual tone multiple frequency (DTMF)

In telephone systems, multifrequency signaling in which standard set combinations of two specific voice band frequencies, one from a group of four low frequencies and the other from a group of four higher frequencies, are used.

E E-Aggr

See Ethernet aggregation.

E-LAN

See Ethernet local area network.

E-Line

See Ethernet line.

EBS

See excess burst size.

ECC

See embedded control channel.

EDFA

See erbium-doped fiber amplifier.

EEPROM

See electrically erasable programable read-only memory.

EF

See expedited forwarding.

EFM

Ethernet in the First Mile

Issue 03 (2013-02-20)


972


B Glossary

EFM OAM

Ethernet in the first mile OAM

EIA

See Electronic Industries Alliance.

EIR

See excess information rate.

EMC

See electromagnetic compatibility.

EPD

early packet discard

EPL

See Ethernet private line.

EPLAN

See Ethernet private LAN service.

EPON

See Ethernet passive optical network.

ERPS

Ethernet ring protection switching

ESC

See electric supervisory channel.

ESCON

See enterprise system connection.

ESD

electrostatic discharge

ESN

See equipment serial number.

ETS

European Telecommunication Standards

ETSI

See European Telecommunications Standards Institute.

EVC

Ethernet virtual connection

EVPL

See Ethernet virtual private line.

EVPLAN

See Ethernet virtual private LAN service.

Electronic Industries Alliance (EIA)

An association based in Washington, D.C., with members from various electronics manufacturers. It sets standards for electronic components. RS-232-C, for example, is the EIA standard for connecting serial components.

EoD

See Ethernet over dual domains.

Ethernet

A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/ s. An Ethernet network features high reliability and is easy to maintain.

Ethernet aggregation (E-Aggr)

A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual connection).

Ethernet line (E-Line)

A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual connection).

Ethernet local area network (E-LAN)

A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet virtual connection).

Ethernet over dual domains (EoD)

A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet service transmission across PSN and TDM networks.

Ethernet passive optical network (EPON)

A passive optical network based on Ethernet. It is a new generation broadband access technology that uses a point-to-multipoint structure and passive fiber transmission. It supports upstream/downstream symmetrical rates of 1.25 Gbit/s and a reach distance of up to 20 km. In the downstream direction, the bandwidth is shared based on encrypted broadcast transmission for different users. In the upstream direction, the bandwidth is shared based on TDM. EPON meets the requirements for high bandwidth.

Issue 03 (2013-02-20)


973


B Glossary

Ethernet private LAN service (EPLAN)

A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a dedicated bridge and point-to-multipoint connections.

Ethernet private line (EPL)

A type of Ethernet service that is provided with dedicated bandwidth and point-to-point connections on an SDH, PDH, ATM, or MPLS server layer network.

Ethernet virtual private LAN service (EVPLAN)

A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a shared bridge and point-to-multipoint connections.

Ethernet virtual private line (EVPL)

A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This service is carried over a shared bridge and point-to-point connections.

European Telecommunications Standards Institute (ETSI)

A standards-setting body in Europe. Also the standards body responsible for GSM.

eSFP

enhanced small form-factor pluggable

electric supervisory channel (ESC)

A technology that implements communication among all the nodes and transmission of monitoring data in an optical transmission network. The monitoring data of ESC is introduced into DCC service overhead and is transmitted with service signals.

electrically erasable A type of EPROM that can be erased with an electrical signal. It is useful for stable programable read-only storage for long periods without electricity while still allowing reprograming. EEPROMs memory (EEPROM) contain less memory than RAM, take longer to reprogram, and can be reprogramed only a limited number of times before wearing out. electromagnetic compatibility (EMC)

A condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment.

embedded control channel (ECC)

A logical channel that uses a data communications channel (DCC) as its physical layer, to enable transmission of operation, administration, and maintenance (OAM) information between NEs.

encapsulation

A technology for layered protocols, in which a lower-level protocol accepts a message from a higher-level protocol and places it in the data portion of the lower-level frame. Protocol A's packets have complete header information, and are carried by protocol B as data. Packets that encapsulate protocol A have a B header, an A header, followed by the information that protocol A is carrying. Note that A could equal to B, as in IP inside IP.

enterprise system connection (ESCON)

A path protocol which connects the host with various control units in a storage system. It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.

equalization

A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading.

equipment serial number (ESN)

A string of characters that identify a piece of equipment and ensures correct allocation of a license file to the specified equipment. It is also called "equipment fingerprint".

erbium-doped fiber amplifier (EDFA)

An optical device that amplifies the optical signals. The device uses a short length of optical fiber doped with the rare-earth element Erbium and the energy level jump of Erbium ions activated by pump sources. When the amplifier passes the external light source pump, it amplifies the optical signals in a specific wavelength range.

Issue 03 (2013-02-20)


974


B Glossary

excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode, the traffic control is achieved by the token buckets C and E. Excess burst size is a parameter used to define the capacity of token bucket E, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded. excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the (EIR) actual transmission rate without the safety rate. exercise switching

An operation to check whether the protection switching protocol functions properly. The protection switching is not really performed.

expedited forwarding (EF)

The highest order QoS in the Diff-Serv network. EF PHB is suitable for services that demand low packet loss ratio, short delay, and broad bandwidth. In all the cases, EF traffic can guarantee a transmission rate equal to or faster than the set rate. The DSCP value of EF PHB is "101110".

F FC

See fiber channel.

FCC

Federal Communications Commission

FDD

See frequency division duplex.

FDDI

See fiber distributed data interface.

FDI

See forward defect indication.

FDI packet

See forward defect indication packet.

FDV

See frame delay variation.

FEC

See forwarding equivalence class.

FFD

fast failure detection

FIB

See forward information base.

FICON

See Fiber Connect.

FIFO

See first in first out.

FLR

See frame loss ratio.

FPGA

See field programmable gate array.

FPS

See fast protection switching.

FRR

See fast reroute.

FTN

FEC to NHLFE

FTP

File Transfer Protocol

Fiber Connect (FICON)

A new generation connection protocol which connects the host to various control units. It carries single byte command protocol through the physical path of fiber channel, and provides higher rate and better performance than ESCON.

fast protection switching (FPS)

A type of pseudo wire automatic protection switching (PW APS). When the working PW is faulty, the source transmits services to the protection PW and the sink receives the services from the protection PW. FPS generally works with the interworking function (IWF) to provide end-to-end protection for services.

Issue 03 (2013-02-20)


975


B Glossary

fast reroute (FRR)

A technology which provides a temporary protection of link availability when part of a network fails. The protocol enables the creation of a standby route or path for an active route or path. When the active route is unavailable, the traffic on the active route can be switched to the standby route. When the active route is recovered, the traffic can be switched back to the active route. FRR is categorized into IP FRR, VPN FRR, and TE FRR.

fiber channel (FC)

A high-speed transport technology used to build storage area networks (SANs). Fiber channel can be on the networks carrying ATM and IP traffic. It is primarily used for transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair copper wires and coaxial cables. Fiber channel provides both connection-oriented and connectionless services.

fiber distributed data interface (FDDI)

A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for transmission rates of 100 megabits (100 million bits) per second on networks based on the token ring network.

field programmable gate array (FPGA)

A type of semi-customized circuit used in the application specific integrated circuit (ASIC) field. It is developed on the basis of the programmable components, such as the PAL, GAL, and EPLD. It not only remedies the defects of customized circuits but also overcomes the disadvantage of the original programmable components in terms of the limited number of gate arrays.

first in first out (FIFO) A stack management mechanism. The first saved data is first read and invoked. forward defect indication (FDI)

A packet generated and traced forward to the sink node of the LSP by the node that first detects defects. It includes fields to indicate the nature of the defect and its location. Its primary purpose is to suppress alarms being raised at affected higher level client LSPs and (in turn) their client layers.

forward defect A packet that responds to the detected failure event. It is used to suppress alarms of the indication packet (FDI upper layer network where failure has occurred. packet) forward information base (FIB)

A table that provides information for network hardware (bridges and routers) for them to forward data packets to other networks. The information contained in a routing table differs according to whether it is used by a bridge or a router. A bridge relies on both the source (originating) and destination addresses to determine where and how to forward a packet.

forwarding equivalence A class-based forwarding technology that classifies the packets with the same forwarding class (FEC) mode. Packets with the same FEC are processed similarly on an MPLS network. The division of FECs is flexible, and can be a combination of the source address, destination address, source port, destination port, protocol type, and VPN. frame delay variation (FDV)

A measurement of the variations in the frame delay between a pair of service frames, where the service frames belong to the same CoS instance on a point to point ETH connection.

frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered divided by the total number of service frames during time interval T, where the number of service frames not delivered is the difference between the number of service frames arriving at the ingress ETH flow point and the number of service frames delivered at the egress ETH flow point in a point-to-point ETH connection.

Issue 03 (2013-02-20)


976


frequency division duplex (FDD)

B Glossary

An application in which channels are divided by frequency. In an FDD system, the uplink and downlink use different frequencies. Downlink data is sent through bursts. Both uplink and downlink transmission use frames with fixed time length.

G G-ACH

generic associated channel header

GAL

generic associated channel header label

GCC

general communication channel

GCP

GMPLS control plan

GCRA

generic cell rate algorithm

GFC

generic flow control

GFP

See Generic Framing Procedure.

GMPLS

generalized multiprotocol label switching

GNE

See gateway network element.

GPON

gigabit-capable passive optical network

GPS

See Global Positioning System.

GRE

See Generic Routing Encapsulation.

GSM

See Global System for Mobile Communications.

Generic Framing Procedure (GFP)

A framing and encapsulation method which can be applied to any data type. It has been standardized by ITU-T SG15.

Generic Routing Encapsulation (GRE)

A mechanism for encapsulating any network layer protocol over any other network. GRE is used for encapsulating IP datagrams tunneled through the Internet. GRE serves as a Layer 3 tunneling protocol and provides a tunnel for transparently transmitting data packets.

Global Positioning System (GPS)

A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users.

Global System for Mobile Communications (GSM)

The second-generation mobile networking standard defined by European Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for global mobile phone networks. The standard allows a subscriber to use a phone globally. GSM consists of three main parts: mobile switching subsystem (MSS), base station subsystem (BSS), and mobile station (MS).

gain

The difference between the optical power from the input optical interface of the optical amplifier and the optical power from the output optical interface of the jumper fiber, which expressed in dB.

gateway network element (GNE)

A network element that is used for communication between the NE application layer and the NM application layer.

H HCS

higher order connection supervision

HD

high definition

HD-SDI

See high definition-serial digital interface signal.

Issue 03 (2013-02-20)


977


B Glossary

HDB3

See high density bipolar of order 3 code.

HDLC

High-Level Data Link Control

HDTV

See high definition television.

HEC

See header error control.

HPA

high order path adaptation

HPT

higher order path termination

HQoS

See hierarchical quality of service.

HSDPA

See High Speed Downlink Packet Access.

HSI

high-speed Internet

HSL

See high-level script language.

High Speed Downlink Packet Access (HSDPA)

A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement for asymmetric uplink and downlink transmission of data services. It enables the maximum downlink data service rate to reach 14.4 Mbit/s without changing the WCDMA network topology.

header error control (HEC)

A field within the ATM frame whose purpose is to correct any single bit error in the cell Header and also to detect any multi-bit errors. It actually performs a CRC check in the first four header bits and also at the receiving end.

hierarchical quality of service (HQoS)

A type of QoS that controls the traffic of users and performs the scheduling according to the priority of user services. HQoS has an advanced traffic statistics function, and the administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth can be allocated reasonably through traffic analysis.

high definition television (HDTV)

A type of TV that is capable of displaying at least 720 progressive or 1080 interlaced active scan lines. It must be capable of displaying a 16:9 image using at least 540 progressive or 810 interlaced active scan lines.

high definition-serial digital interface signal (HD-SDI)

High definition video signal transported by serial digital interface.

high density bipolar of A code used for baseband transmissions between telecommunications devices. The order 3 code (HDB3) HDB3 code has the following feature: high capability of clock extraction, no direct current component, error-checking capability, and a maximum of three consecutive zeros. high-level script language (HSL)

A script language. Based on python, the HSL syntax is simple, clear, and extendable.

hot patch

A patch that is used to repair a deficiency in the software or add a new feature to a program without restarting the software and interrupting the service. For the equipment using the built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or queried.

I IAE

incoming alignment error

IANA

See Internet Assigned Numbers Authority.

IC

See integrated circuit.

Issue 03 (2013-02-20)


978


B Glossary

ICC

See ITU carrier code.

ICMP

See Internet Control Message Protocol.

ICP

IMA Control Protocol

IEEE

See Institute of Electrical and Electronics Engineers.

IETF

See Internet Engineering Task Force.

IF

See intermediate frequency.

IGMP

See Internet Group Management Protocol.

IGMP snooping

A multicast constraint mechanism running on a layer 2 device. This protocol manages and controls the multicast group by listening to and analyzing Internet Group Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this manner, the spread of the multicast data on layer 2 network can be prevented efficiently.

IGP

See Interior Gateway Protocol.

ILM

incoming label map

IMA

See inverse multiplexing over ATM.

IN

intelligent network

IP

Internet Protocol

IPA

See intelligent power adjustment.

IPTV

See Internet Protocol television.

IPv4

See Internet Protocol version 4.

IPv6

See Internet Protocol version 6.

IS-IS

See Intermediate System to Intermediate System.

ISDN

integrated services digital network

ISO

International Organization for Standardization

ISP

See Internet service provider.

IST

internal spanning tree

ITC

independent transmit clock

ITU

See International Telecommunication Union.

ITU carrier code (ICC) A code assigned to a network operator/service provider, maintained by the ITU-T Telecommunication Standardization Bureau (TSB). ITU-T

See International Telecommunication Union-Telecommunication Standardization Sector.

Institute of Electrical and Electronics Engineers (IEEE)

A society of engineering and electronics professionals based in the United States but boasting membership from numerous other countries. The IEEE focuses on electrical, electronics, computer engineering, and science-related matters.

Interior Gateway Protocol (IGP)

A routing protocol that is used within an autonomous system. The IGP runs in smallsized and medium-sized networks. The commonly used IGPs are the routing information protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP (EIGRP), and the open shortest path first (OSPF).

Issue 03 (2013-02-20)


979


B Glossary

Intermediate System to A protocol used by network devices (routers) to determine the best way to forward Intermediate System datagram or packets through a packet-based network. (IS-IS) International Telecommunication Union (ITU)

A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R).

International Telecommunication UnionTelecommunication Standardization Sector (ITU-T)

An international body that develops worldwide standards for telecommunications technologies. These standards are grouped together in series which are prefixed with a letter indicating the general subject and a number specifying the particular standard. For example, X.25 comes from the "X" series which deals with data networks and open system communications and number "25" deals with packet switched networks.

Internet Assigned Numbers Authority (IANA)

A department operated by the IAB. IANA delegates authority for IP address-space allocation and domain-name assignment to the NIC and other organizations. IANA also maintains a database of assigned protocol identifiers used in the TCP/IP suite, including autonomous system numbers.

Internet Control Message Protocol (ICMP)

A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, it can let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSI reference model, packet (definition 1).

Internet Engineering Task Force (IETF)

A worldwide organization of individuals interested in networking and the Internet. Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with studying technical problems facing the Internet and proposing solutions to the Internet Architecture Board (IAB). The work of the IETF is carried out by various working groups that concentrate on specific topics such as routing and security. The IETF is the publisher of the specifications that led to the TCP/IP protocol standard.

Internet Group Management Protocol (IGMP)

One of the TCP/IP protocols for managing the membership of Internet Protocol multicast groups. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships.

Internet Protocol television (IPTV)

A system in which video is transmitted in IP packets. Also called "TV over IP", IPTV uses streaming video techniques to deliver scheduled TV programs or video-on-demand (VOD). Unlike transmitting over the air or through cable to a TV set, IPTV uses the transport protocol of the Internet for delivery and requires either a computer and software media player or an IPTV set-top box to decode the images in real time.

Internet Protocol version 4 (IPv4)

The current version of the Internet Protocol (IP). IPv4 utilizes a 32bit address which is assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is written as 4 octets separated by periods and may range from 0.0.0.0 through to 255.255.255.255. Each IPv4 address consists of a network number, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, and the host number is used to address an individual host within the network or subnetwork.

Internet Protocol version 6 (IPv6)

An update version of IPv4, which is designed by the Internet Engineering Task Force (IETF) and is also called IP Next Generation (IPng). It is a new version of the Internet Protocol. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits.

Internet service provider (ISP)

An organization that offers users access to the Internet and related services.

Issue 03 (2013-02-20)


980


B Glossary

integrated circuit (IC)

A combination of inseparable associated circuit elements that are formed in place and interconnected on or within a single base material to perform a microcircuit function.

intelligent power adjustment (IPA)

A mechanism used to reduce the optical power of all the amplifiers in an adjacent regeneration section in the upstream to a safety level if the system detects the loss of optical signals on the link. If the fiber is broken, the device performance degrades, or the connector is not plugged well, the loss of optical signals may occur. With IPA, maintenance engineers will not be hurt by the laser sent out from the slice of broken fiber.

intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF (IF) signal. inverse multiplexing over ATM (IMA)

A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion among links grouped to form a higher bandwidth logical link whose rate is approximately the sum of the link rates.

L L2VPN

Layer 2 virtual private network

L3VPN

Layer 3 virtual private network

LACP

See Link Aggregation Control Protocol.

LACPDU

Link Aggregation Control Protocol data unit

LAG

See link aggregation group.

LAN

See local area network.

LAPD

link access procedure on the D channel

LAPS

Link Access Protocol-SDH

LB

local battery

LC

Lucent connector

LCAS

See link capacity adjustment scheme.

LCK

See Locked signal function.

LCN

local communications network

LDP

Label Distribution Protocol

LED

See light emitting diode.

LER

See label edge router.

LIFO

See last in first out.

LLC

See logical link control.

LLID

local loopback ID

LM

See loss measurement.

LMP

link management protocol

LOC

loss of clock

LOM

loss of multiframe

LOP

loss of pointer

Issue 03 (2013-02-20)


981


B Glossary

LOS

See loss of signal.

LPA

low order path adaptation

LPT

link-state pass through

LSP

See label switched path.

LSR

See label switching router.

LT

linktrace

LVDS

See low voltage differential signal.

Layer 2 switching

A data forwarding method. In a LAN, a network bridge or 802.3 Ethernet switch transmits and distributes packet data based on the MAC address. Since the MAC address is at the second layer of the OSI model, this data forwarding method is called Layer 2 switching.

Link Aggregation Control Protocol (LACP)

A dynamic link aggregation protocol that improves the transmission speed and reliability. The two ends of the link send LACP packets to inform each other of their parameters and form a logical aggregation link. After the aggregation link is formed, LACP maintains the link status in real time and dynamically adjusts the ports on the aggregation link upon detecting the failure of a physical port.

Locked signal function A function administratively locks an MEG end point (MEP) at the server layer, informs (LCK) consequential data traffic interruption to the peer MEP at the client layer, and suppresses the alarm at the client layer. label edge router (LER) A device that sits at the edge of an MPLS domain, that uses routing information to assign labels to datagrams and then forwards them into the MPLS domain. label switched path (LSP)

A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label switching mechanisms. A label-switched path can be chosen dynamically, based on common routing mechanisms or through configuration.

label switching router (LSR)

Basic element of an MPLS network. All LSRs support the MPLS protocol. The LSR is composed of two parts: control unit and forwarding unit. The former is responsible for allocating the label, selecting the route, creating the label forwarding table, creating and removing the label switch path; the latter forwards the labels according to groups received in the label forwarding table.

last in first out (LIFO) A play mode of the voice mails, the last voice mail is played firstly. light emitting diode (LED)

A display and lighting technology used in almost every electrical and electronic product on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and perimeter lighting. LEDs are also used as the light source in multimode fibers, optical mice and laser-class printers.

linear MSP

linear multiplex section protection

link aggregation group An aggregation that allows one or more links to be aggregated together to form a link (LAG) aggregation group so that a MAC client can treat the link aggregation group as if it were a single link. link capacity adjustment scheme (LCAS)

Issue 03 (2013-02-20)

LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitless increase or decrease the capacity of a link to meet the bandwidth needs of the application. It also provides a means of removing member links that have experienced failure. The LCAS assumes that in cases of capacity initiation, increases or decreases, the construction or destruction of the end-to-end path is the responsibility of the network and element management systems.


982


B Glossary

local area network (LAN)

A network formed by the computers and workstations within the coverage of a few square kilometers or within a single building. It features high speed and low error rate. Ethernet, FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/ s (that is, 1 Gbit/s).

logical link control (LLC)

According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper sublayer of the OSI data link layer. The LLC is the same for the various physical media (such as Ethernet, token ring, WLAN).

loss measurement (LM) A method used to collect counter values applicable for ingress and egress service frames where the counters maintain a count of transmitted and received data frames between a pair of MEPs. loss of signal (LOS)

No transitions occurring in the received signal.

low voltage differential A low noise, low power, low amplitude method for high-speed (gigabits per second) data signal (LVDS) transmission over copper wire. M MA

maintenance association

MAC

See Media Access Control.

MADM

multiple add/drop multiplexer

MAN

See metropolitan area network.

MBS

maximum burst size

MCF

message communication function

MCR

minimum cell rate

MD

See maintenance domain.

MDF

See main distribution frame.

MDP

message dispatch process

MDU

See multi-dwelling unit.

ME

See maintenance entity.

MEG

See maintenance entity group.

MEL

maintenance entity group level

MEP

maintenance end point

MFAS

See multiframe alignment signal.

MIB

See management information base.

MIP

maintenance intermediate point

MLD

See multicast listener discovery.

MP

maintenance point

MPLS

See Multiprotocol Label Switching.

MPLS TE

multiprotocol label switching traffic engineering

MPLS TP

See Multiprotocol Label Switching traffic policing.

Issue 03 (2013-02-20)


983


B Glossary

MPLS VPN

See multiprotocol label switching virtual private network.

MPLS-TP

See multiprotocol label switching transport profile.

MS

multiplex section

MSA

multiplex section adaptation

MSB

most significant bit

MSOH

multiplex section overhead

MSP

See multiplex section protection.

MST

See multiplex section termination.

MSTI

See multiple spanning tree instance.

MSTP

See Multiple Spanning Tree Protocol.

MTBF

See mean time between failures.

MTTR

See mean time to repair.

MTU

See maximum transmission unit.

MUX

See multiplexer.

Media Access Control (MAC)

A protocol at the media access control sublayer. The protocol is at the lower part of the data link layer in the OSI model and is mainly responsible for controlling and connecting the physical media at the physical layer. When transmitting data, the MAC protocol checks whether to be able to transmit data. If the data can be transmitted, certain control information is added to the data, and then the data and the control information are transmitted in a specified format to the physical layer. When receiving data, the MAC protocol checks whether the information is correct and whether the data is transmitted correctly. If the information is correct and the data is transmitted correctly, the control information is removed from the data and then the data is transmitted to the LLC layer.

Multiple Spanning Tree Protocol (MSTP)

A protocol that can be used in a loop network. Using an algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed as a tree network. In this case, the proliferation and endless cycling of packets is avoided in the loop network. The protocol that introduces the mapping between VLANs and multiple spanning trees. This solves the problem that data cannot be normally forwarded in a VLAN because in STP/ RSTP, only one spanning tree corresponds to all the VLANs.

Multiprotocol Label Switching (MPLS)

A technology that uses short tags of fixed length to encapsulate packets in different link layers, and provides connection-oriented switching for the network layer on the basis of IP routing and control protocols. It improves the cost performance and expandability of networks, and is beneficial to routing.

Multiprotocol Label Switching traffic policing (MPLS TP)

It is a scheme that supervises the specific traffic entering the communication devices. By policing the speed of traffic that enters the network, it "punishes" the traffic out of the threshold, so the traffic going into network is limited to a reasonable range, protecting the network resources and the interests of the carriers.

main distribution frame (MDF)

A device at a central office, on which all local loops are terminated.

maintenance domain (MD)

The network or the part of the network for which connectivity is managed by connectivity fault management (CFM). The devices in a maintenance domain are managed by a single Internet service provider (ISP).

Issue 03 (2013-02-20)


984


B Glossary

maintenance entity (ME)

An ME consists of a pair of maintenance entity group end points (MEPs), two ends of a transport trail, and maintenance association intermediate points (MIPs) on the trail.

maintenance entity group (MEG)

A MEG consists of MEs that meet the following criteria: l

Exist within the same management edges.

l

Have the same MEG hierarchy.

l

Belong to the same P2P or P2MP connection.

management A type of database used for managing the devices in a communications network. It information base (MIB) comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network. maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies, unit (MTU) depending on the network—576 bytes on X.25 networks, for example, 1500 bytes on Ethernet, and 17,914 bytes on 16 Mbit/s token ring. Responsibility for determining the size of the MTU lies with the link layer of the network. When packets are transmitted across networks, the path MTU, or PMTU, represents the smallest packet size (the one that all networks can transmit without breaking up the packet) among the networks involved. mean time between failures (MTBF)

The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system.

mean time to repair (MTTR)

The average time that a device will take to recover from a failure.

metropolitan area network (MAN)

A network that interconnects users with computer resources in a geographic area or region larger than that covered by even a large LAN but smaller than the area covered by an WAN. The term is applied to the interconnection of networks in a city into a single larger network (which may then also offer efficient connection to a wide area network). It is also used to mean the interconnection of several local area networks by bridging them with backbone lines. The latter usage is also sometimes referred to as a campus network.

mirror

An action to store a copy of a file to another archive site to release the load of the original site, or to provide an archive site closer to the users geographically.

mirroring

The duplication of data for backup or to distribute network traffic among several computers with identical data.

multi-dwelling unit (MDU)

A network access unit used for multi-dwelling units. It provides Ethernet and IP services and optionally VoIP or CATV services; has multiple broadband interfaces on the user side and optionally POTS ports or CATV RF ports. It is mainly applicable to FTTB, FTTC, or FTTCab networks.

multicast listener discovery (MLD)

A protocol used by an IPv6 router to discover the multicast listeners on their directly connected network segments, and to set up and maintain member relationships. On IPv6 networks, after MLD is configured on the receiver hosts and the multicast router to which the hosts are directly connected, the hosts can dynamically join related groups and the multicast router can manage members on the local network.

multiframe alignment signal (MFAS)

A distinctive signal inserted in every multiframe or once in every n multiframes, always occupying the same relative position within the multiframe, and used to establish and maintain multiframe alignment.

Issue 03 (2013-02-20)


985


B Glossary

multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply instance (MSTI) and fully connected active topology for frames classified as belonging to a VLAN that is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to multiple MSTIs. multiplex section protection (MSP)

A function, which is performed to provide capability for switching a signal between and including two multiplex section termination (MST) functions, from a "working" to a "protection" channel.

multiplex section termination (MST)

A function, which is performed to generate the MSOH during the process of forming an SDH frame signal and terminates the MSOH in the reverse direction.

multiplexer (MUX)

Equipment which combines a number of tributary channels onto a fewer number of aggregate bearer channels, the relationship between the tributary and aggregate channels being fixed.

multiprotocol label switching transport profile (MPLS-TP)

A packet transport technology proposed by IETF that combines the packet experience of MPLS with the operational experience of transport networks.

multiprotocol label switching virtual private network (MPLS VPN)

An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label switching (MPLS) technology. It applies the MPLS technology for network routers and switches, simplifies the routing mode of core routers, and combines traditional routing technology and label switching technology. It can be used to construct the broadband Intranet and Extranet to meet various service requirements.

N NAS

network access server

NDF

new data flag

NHLFE

next hop label forwarding entry

NMC

network management center

NNI

network-to-network interface

NPC

See network parameter control.

NPE

network provider edge

NRT-VBR

non-real-time variable bit rate

NRZ

non-return to zero

NRZI

non-return to zero inverted

NSAP

See network service access point.

NSF

non-stop forwarding

NTP

Network Time Protocol

network parameter control (NPC)

During communications, UPC is implemented to monitor the actual traffic on each virtual circuit that is input to the network. Once the specified parameter is exceeded, measures will be taken to control. NPC is similar to UPC in function. The difference is that the incoming traffic monitoring function is divided into UPC and NPC according to their positions. UPC locates at the user/network interface, while NPC at the network interface.

network service access A network address defined by ISO, at which the OSI Network Service is made available point (NSAP) to a Network service user by the Network service provider.

Issue 03 (2013-02-20)


986


B Glossary

O O&M

operation and maintenance

OA

optical amplifier

OADM

See optical add/drop multiplexer.

OAM

See operation, administration and maintenance.

OAMPDU

operation, administration and maintenance protocol data unit

OAU

See optical amplifier unit.

OC

ordinary clock

OCP

optical channel protection

OCS

optical core switching

ODF

optical distribution frame

ODU

See outdoor unit.

OLT

optical line terminal

ONT

See optical network terminal.

ONU

See optical network unit.

OPEX

operating expense

OPU

optical channel payload unit

OSC

See optical supervisory channel.

OSI

See open systems interconnection.

OSN

optical switch node

OSNR

See optical signal-to-noise ratio.

OSPF

See Open Shortest Path First.

OTDR

See optical time domain reflectometer.

OTM

optical terminal multiplexer

OTN

optical transport network

OTU

See optical transponder unit.

OTUk

optical channel transport unit-k

Open Shortest Path First (OSPF)

A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A link state database is constructed with the network topology which is identical on all routers in the area.

open systems interconnection (OSI)

A framework of ISO standards for communication between different systems made by different vendors, in which the communications process is organized into seven different categories that are placed in a layered sequence based on their relationship to the user. Each layer uses the layer immediately below it and provides a service to the layer above. Layers 7 through 4 deal with end-to-end communication between the message source and destination, and layers 3 through 1 deal with network functions.

Issue 03 (2013-02-20)


987


B Glossary

operation, administration and maintenance (OAM)

A group of network support functions that monitor and sustain segment operation, support activities that are concerned with, but not limited to, failure detection, notification, location, and repairs that are intended to eliminate faults and keep a segment in an operational state, and support activities required to provide the services of a subscriber access network to users/subscribers.

optical add/drop multiplexer (OADM)

A device that can be used to add the optical signals of various wavelengths to one channel and drop the optical signals of various wavelengths from one channel.

optical amplifier unit (OAU)

A board that is mainly responsible for amplifying optical signals. The OAU can be used in both the transmitting direction and the receiving direction.

optical network terminal (ONT)

A device that terminates the fiber optical network at the customer premises.

optical network unit (ONU)

A form of Access Node that converts optical signals transmitted via fiber to electrical signals that can be transmitted via coaxial cable or twisted pair copper wiring to individual subscribers.

optical signal-to-noise ratio (OSNR)

The ratio of signal power and noise power in a transmission link. OSNR is the most important index of measuring the performance of a DWDM system. OSNR = signal power/noise power.

optical supervisory channel (OSC)

A technology that uses specific optical wavelengths to realize communication among nodes in optical transmission network and transmit the monitoring data in a certain channel.

optical time domain reflectometer (OTDR)

A device that sends a very short pulse of light down a fiber optic communication system and measures the time history of the pulse reflection to measure the fiber length, the light loss and locate the fiber fault.

optical transponder unit (OTU)

A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength.

orderwire

A channel that provides voice communication between operation engineers or maintenance engineers of different stations.

outdoor unit (ODU)

The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for radio frequency (RF) signals.

P P2MP

point-to-multipoint

P2P

See point-to-point service.

PADR

PPPoE active discovery request

PBS

See peak burst size.

PCB

See printed circuit board.

PCM

See pulse code modulation.

PCR

See peak cell rate.

PDH

See plesiochronous digital hierarchy.

PDU

See power distribution unit.

PE

See provider edge.

PHB

See per-hop behavior.

Issue 03 (2013-02-20)


988


B Glossary

PHP

penultimate hop popping

PIM-DM

Protocol Independent Multicast - Dense Mode

PIM-SM

Protocol Independent Multicast - Sparse Mode

PIR

peak information rate

PLL

See phase-locked loop.

PM

performance monitoring

PMS

Product Management System

POH

path overhead

PON

passive optical network

POS

See packet over SDH/SONET.

PPD

partial packet discard

PPI

PDH physical interface

PPP

Point-to-Point Protocol

PPPoE

Point-to-Point Protocol over Ethernet

PPS

port protection switching

PQ

See priority queuing.

PRBS

See pseudo random binary sequence.

PRC

primary reference clock

PRI

primary rate interface

PSD

See power spectrum density.

PSN

See packet switched network.

PSTN

See public switched telephone network.

PSU

power supply unit

PT

payload type

PTI

payload type indicator

PTN

packet transport network

PTP

See point to point.

PVID

See port default VLAN ID.

PVP

See permanent virtual path.

PW

See pseudo wire.

PWE3

See pseudo wire emulation edge-to-edge.

packet over SDH/ SONET (POS)

A MAN and WAN technology that provides point-to-point data connections. The POS interface uses SDH/SONET as the physical layer protocol, and supports the transport of packet data (such as IP packets) in MAN and WAN.

packet switched network (PSN)

A telecommunications network that works in packet switching mode.

Issue 03 (2013-02-20)


989


B Glossary

packet switching

A network technology in which information is transmitted by means of exchanging packets and the bandwidth of a channel can be shared by multiple connections.

parity check

A method for character level error detection. An extra bit is added to a string of bits, usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or even parity). Both ends of a data transmission must use the same parity. When the transmitting device frames a character, it counts the numbers of 1s in the frame and attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error, may ask for the data to be retransmitted.

peak burst size (PBS)

A parameter that is used to define the capacity of token bucket P, that is, the maximum burst IP packet size when the information is transferred at the peak information rate. This parameter must be larger than 0. It is recommended that PBS should be not less than the maximum length of the IP packet that might be forwarded. See also CIR, CBS, and PIR.

peak cell rate (PCR)

The maximum rate at which an ATM connection can accept cells.

per-hop behavior (PHB)

IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop behaviors (PHB), such as, traffic scheduling and policing. A device in the network should select the proper PHB behaviors, based on the value of DSCP. At present, the IETF defines four types of PHB. They are class selector (CS), expedited forwarding (EF), assured forwarding (AF), and best-effort (BE).

permanent virtual path Virtual path that consists of PVCs. (PVP) phase-locked loop (PLL)

A circuit that consists essentially of a phase detector which compares the frequency of a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with the incoming or reference frequency.

plesiochronous digital hierarchy (PDH)

A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.

point to point (PTP)

A type of service in which data is sent from a single network termination to another network termination.

point-to-point service (P2P)

A service between two terminal users. In P2P services, senders and recipients are terminal users.

port default VLAN ID (PVID)

A default VLAN ID of a port. It is allocated to a data frame if the data frame carries no VLAN tag when reaching the port.

power distribution unit A unit that performs AC or DC power distribution. (PDU) power spectrum density (PSD)

The power layout of random signals in the frequency domain.

printed circuit board (PCB)

A board used to mechanically support and electrically connect electronic components using conductive pathways, tracks, or traces, etched from copper sheets laminated onto a non-conductive substrate.

priority queuing (PQ)

A queue scheduling algorithm based on the absolute priority. According to the PQ algorithm, services of higher priorities are ensured with greater bandwidth, lower latency, and less jitter. Packets of lower priorities must wait to be sent till all packets of higher priorities are sent. In this manner, services of higher priorities are processed earlier than others.

Issue 03 (2013-02-20)


990


provider edge (PE)

B Glossary

A device that is located in the backbone network of the MPLS VPN structure. A PE is responsible for managing VPN users, establishing LSPs between PEs, and exchanging routing information between sites of the same VPN. A PE performs the mapping and forwarding of packets between the private network and the public channel. A PE can be a UPE, an SPE, or an NPE.

pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence (PRBS) values of any of the other elements, similar to real random sequences. pseudo wire (PW)

An emulated connection between two PEs for transmitting frames. The PW is established and maintained by PEs through signaling protocols. The status information of a PW is maintained by the two end PEs of a PW.

pseudo wire emulation An end-to-end Layer 2 transmission technology. It emulates the essential attributes of a edge-to-edge (PWE3) telecommunication service such as ATM, FR or Ethernet in a packet switched network (PSN). PWE3 also emulates the essential attributes of low speed time division multiplexing (TDM) circuit and SONET/SDH. The simulation approximates to the real situation. public switched telephone network (PSTN)

A telecommunications network established to perform telephone services for the public subscribers. Sometimes it is called POTS.

pulse code modulation A method of encoding information in a signal by changing the amplitude of pulses. (PCM) Unlike pulse amplitude modulation (PAM), in which pulse amplitude can change continuously, pulse code modulation limits pulse amplitudes to several predefined values. Because the signal is discrete, or digital, rather than analog, pulse code modulation is more immune to noise than PAM. Q QAM

See quadrature amplitude modulation.

QPSK

See quadrature phase shift keying.

QinQ

See 802.1Q in 802.1Q.

QoS

See quality of service.

quadrature amplitude modulation (QAM)

Both an analog and a digital modulation scheme. It conveys two analog message signals, or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves, using the amplitude-shift keying (ASK) digital modulation scheme or amplitude modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are out of phase with each other by 90° and are thus called quadrature carriers or quadrature components — hence the name of the scheme.

quadrature phase shift A modulation method of data transmission through the conversion or modulation and keying (QPSK) the phase determination of the reference signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are evenly distributed on a circle. On these phases, each QPSK character can perform twobit coding and display the codes in Gray code on graph with the minimum BER. quality of service (QoS) A commonly-used performance indicator of a telecommunication system or channel. Depending on the specific system and service, it may relate to jitter, delay, packet loss ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the transmission system and the effectiveness of the services, as well as the capability of a service provider to meet the demands of users.

Issue 03 (2013-02-20)


991


B Glossary

R RADIUS

See Remote Authentication Dial In User Service.

RAN

See radio access network.

RDI

remote defect indication

RED

See random early detection.

REG

See regenerator.

REI

remote error indication

RIP

See Routing Information Protocol.

RMEP

remote maintenance association end point

RMON

remote network monitoring

RNC

See radio network controller.

ROPA

See remote optical pumping amplifier.

RPR

resilient packet ring

RSOH

regenerator section overhead

RST

regenerator section termination

RSTP

See Rapid Spanning Tree Protocol.

RSVP

See Resource Reservation Protocol.

RSVP-TE

See Resource ReserVation Protocol-Traffic Engineering.

RTN

radio transmission node

RTP

real-time performance

RTS

request to send

Rapid Spanning Tree Protocol (RSTP)

An evolution of the Spanning Tree Protocol, providing for faster spanning tree convergence after a topology change. The RSTP protocol is backward compatible with the STP protocol.

Remote Authentication A networking protocol that provides centralized Authentication, Authorization, and Dial In User Service Accounting (AAA) management for computers to connect and use a network service. (RADIUS) Resource ReserVation Protocol-Traffic Engineering (RSVPTE)

An extension to the RSVP protocol for setting up label switched paths (LSPs) in MPLS networks. The RSVP-TE protocol is used to establish and maintain the LSPs by initiating label requests and allocating label binding messages. It also supports LSP rerouting and LSP bandwidth increasing.

Resource Reservation Protocol (RSVP)

A network control protocol like Internet Control Message Protocol (ICMP) and designed for Integrated Service and used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data.

RoHS

restriction of the use of certain hazardous substances

Routing Information Protocol (RIP)

A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route based on the smallest hop count between source and destination. RIP is a distance vector protocol that routinely broadcasts routing information to its neighboring routers and is known to waste bandwidth.

Issue 03 (2013-02-20)


992


B Glossary

radio access network (RAN)

The network that provides the connection between CPEs and the CN. It isolates the CN from wireless network.

radio network controller (RNC)

A piece of equipment in the RNS which is in charge of controlling the use and the integrity of the radio resources.

random early detection A packet loss algorithm used in congestion avoidance. It discards the packet according (RED) to the specified higher limit and lower limit of a queue so that global TCP synchronization resulting from traditional tail drop can be prevented. real-time variable bit rate (rt-VBR)

A parameter intended for real-time applications, such as compressed voice over IP (VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR), sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source device to transmit in bursts and at a rate that varies with time.

receiver sensitivity

The minimum acceptable value of average received power at point R to achieve a 1 x 10-12 BER (The FEC is open).

reflectance

The ratio of the reflected optical power to the incident optical power.

regenerator (REG)

A piece of equipment or device that regenerates electrical signals.

remote optical pumping amplifier (ROPA)

A remote optical amplifier subsystem designed for applications where power supply and monitoring systems are unavailable. The ROPA subsystem is a power compensation solution to the ultra-long distance long hop (LHP) transmission.

rt-VBR

See real-time variable bit rate.

S SAI

service area identifier

SAN

storage area network

SAToP

Structure-Agnostic Time Division Multiplexing over Packet

SC

square connector

SCR

sustainable cell rate

SD

See signal degrade.

SD-SDI

See standard definition-serial digital interface signal.

SDH

See synchronous digital hierarchy.

SDI

See serial digital interface.

SDP

serious disturbance period

SDRAM

See synchronous dynamic random access memory.

SELV

safety extra-low voltage

SEMF

synchronous equipment management function

SES

severely errored second

SF

See signal fail.

SFP

small form-factor pluggable

SFTP

See Secure File Transfer Protocol.

SHDSL

See single-pair high-speed digital subscriber line.

Issue 03 (2013-02-20)


993


B Glossary

SLA

See service level agreement.

SLIP

See Serial Line Interface Protocol.

SMB

Server Message Block

SMSR

side mode suppression ratio

SNCMP

subnetwork connection multipath protection

SNCP

subnetwork connection protection

SNCTP

subnetwork connection tunnel protection

SNMP

See Simple Network Management Protocol.

SOH

section overhead

SONET

See synchronous optical network.

SP

See service provider.

SPC

soft permanent connection

SPE

See superstratum provider edge.

SPI

SDH physical interface

SRG

See shared risk group.

SRLG

shared risk link group

SSH

See Secure Shell.

SSL

See Secure Sockets Layer.

SSM

See Synchronization Status Message.

SSMB

synchronization status message byte

SSU

synchronization supply unit

STP

Spanning Tree Protocol

Secure File Transfer Protocol (SFTP)

A network protocol designed to provide secure file transfer over SSH.

Secure Shell (SSH)

A set of standards and an associated network protocol that allows establishing a secure channel between a local and a remote computer. A feature to protect information and provide powerful authentication function for a network when a user logs in to the network through an insecure network. It prevents IP addresses from being deceived and plain text passwords from being captured.

Secure Sockets Layer (SSL)

A security protocol that works at a socket level. This layer exists between the TCP layer and the application layer to encrypt/decode data and authenticate concerned entities.

Serial Line Interface Protocol (SLIP)

A protocol that defines the framing mode over the serial line to implement transmission of messages over the serial line and provide the remote host interconnection function with a known IP address.

Issue 03 (2013-02-20)


994


Simple Network Management Protocol (SNMP)

B Glossary

A network management protocol of TCP/IP. It enables remote users to view and modify the management information of a network element. This protocol ensures the transmission of management information between any two points. The polling mechanism is adopted to provide basic function sets. According to SNMP, agents, which can be hardware as well as software, can monitor the activities of various devices on the network and report these activities to the network console workstation. Control information about each device is maintained by a management information block.

Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link. Nodes on an SDH network and a synchronization network acquire upstream clock Message (SSM) information through this message. Then the nodes can perform proper operations on their clocks, such as tracing, switching, or converting to holdoff, and forward the synchronization information to downstream nodes. serial digital interface (SDI)

An interface that transmits data in a single channel in sequence.

service level agreement A service agreement between a customer and a service provider. SLA specifies the (SLA) service level for a customer. The customer can be a user organization (source domain) or another differentiated services domain (upstream domain). An SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. service provider (SP)

An entity that offers service subscriptions to individual subscribers and contracts with carriers to implement services for a specific DN. A service provider may contract with more than one carrier.

shared risk group (SRG)

A group of resources that share a common risk component whose failure can cause the failure of all the resources in the group.

signal degrade (SD)

A signal indicating that associated data has degraded in the sense that a degraded defect condition is active.

signal fail (SF)

A signal indicating that associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active.

single-pair high-speed digital subscriber line (SHDSL)

A symmetric digital subscriber line technology developed from HDSL, SDSL, and HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user terminal through the plain telephone subscriber line and uses trellis coded pulse amplitude modulation (TC-PAM) technology to transmit high-speed data and provide the broadband access service.

span

The physical reach between two pieces of WDM equipment. The number of spans determines the signal transmission distance supported by a piece of equipment and varies according to transmission system type.

standard definitionserial digital interface signal (SD-SDI)

Standard definition video signal transported by serial digital interface.

superstratum provider Core devices that are located within a VPLS full-meshed network. The UPE devices that edge (SPE) are connected with the SPE devices are similar to the CE devices. The PWs set up between the UPE devices and the SPE devices serve as the ACs of the SPE devices. The SPE devices must learn the MAC addresses of all the sites on UPE side and those of the UPE interfaces that are connected with the SPE. SPE is sometimes called NPE.

Issue 03 (2013-02-20)


995


synchronous digital hierarchy (SDH)

B Glossary

A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure.

synchronous dynamic A new type of DRAM that can run at much higher clock speeds than conventional random access memory memory. SDRAM actually synchronizes itself with the CPU's bus and is capable of running at 100 MHz, about three times faster than conventional FPM RAM, and about (SDRAM) twice as fast as EDO DRAM or BEDO DRAM. SDRAM is replacing EDO DRAM in computers. synchronous optical network (SONET)

A high-speed network that provides a standard interface for communications carriers to connect networks based on fiber optical cable. SONET is designed to handle multiple data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but multiples of this base rate go as high as 2.488 Gbit/s.

T TCI

tag control information

TCM

See trellis coded modulation scheme.

TCP/IP

Transmission Control Protocol/Internet Protocol

TDC

tunable dispersion compensator

TDM

See time division multiplexing.

TE

See traffic engineering.

TFTP

See Trivial File Transfer Protocol.

TIM

trail trace identifier mismatch

TLV

See type-length-value.

TM

See terminal multiplexer.

TMN

See telecommunications management network.

TOD

time of day

TPID

tag protocol identifier

TPS

See tributary protection switching.

TST

See Test.

TTI

trail trace identifier

TTSI

See trail termination source identifier.

TUG

tributary unit group

Telnet

A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users to log in to remote systems and use resources as if they were connected to a local system. Telnet is defined in RFC 854.

Issue 03 (2013-02-20)


996


B Glossary

Test (TST)

A function which is used to perform one-way on-demand in-service or out-of-service diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit errors, and so on.

Trivial File Transfer Protocol (TFTP)

A small and simple alternative to FTP for transferring files. TFTP is intended for applications that do not need complex interactions between the client and server. TFTP restricts operations to simple file transfers and does not provide authentication. TFTP is small enough to be contained in ROM to be used for bootstrapping diskless machines.

tail drop

A congestion management mechanism, in which packets arrive later are discarded when the queue is full. This policy of discarding packets may result in network-wide synchronization due to the TCP slow startup mechanism.

telecommunications management network (TMN)

A protocol model defined by ITU-T for managing open systems in a communications network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services.

terminal multiplexer (TM)

A device used at a network terminal to multiplex multiple channels of low rate signals into one channel of high rate signals, or to demultiplex one channel of high rate signals into multiple channels of low rate signals.

throughput

The maximum transmission rate of the tested object (system, equipment, connection, service type) when no packet is discarded. Throughput can be measured with bandwidth.

time division multiplexing (TDM)

A multiplexing technology. TDM divides the sampling cycle of a channel into time slots (TSn, n=0, 1, 2, 3…), and the sampling value codes of multiple signals engross time slots in a certain order, forming multiple multiplexing digital signals to be transmitted over one channel.

traceroute

A program that prints the path to a destination. Traceroute sends a sequence of datagrams with the time-to-live (TTL) set to 1,2, and so on, and uses ICMP time exceeded messages that return to determine routers along the path.

traffic engineering (TE) A technology that is used to dynamically monitor the traffic of the network and the load of the network elements, to adjust in real time the parameters such as traffic management parameters, route parameters and resource restriction parameters, and to optimize the utilization of network resources. The purpose is to prevent the congestion caused by unbalanced loads. trail termination source A TTSI uniquely identifies an LSP in the network. A TTSI is carried in the connectivity identifier (TTSI) verification (CV) packet for checking the connectivity of a trail. If it matches the TTSI received by the sink point, the trail has no connectivity defect. trellis coded modulation scheme (TCM)

A modulation scheme which allows highly efficient transmission of information over band-limited channels such as telephone lines.

tributary protection switching (TPS)

A function that uses a standby tributary processing board to protect N tributary processing boards.

tunnel

A channel on the packet switching network that transmits service traffic between PEs. In VPN, a tunnel is an information transmission channel between two entities. The tunnel ensures secure and transparent transmission of VPN information. In most cases, a tunnel is an MPLS tunnel.

Issue 03 (2013-02-20)


997


type-length-value (TLV)

B Glossary

An encoding type that features high efficiency and expansibility. It is also called CodeLength-Value (CLV). T indicates that different types can be defined through different values. L indicates the total length of the value field. V indicates the actual data of the TLV and is most important. TLV encoding features high expansibility. New TLVs can be added to support new features, which is flexible in describing information loaded in packets.

U UART

universal asynchronous receiver/transmitter

UAS

unavailable second

UAT

See unavailable time event.

UBR

unspecified bit rate

UBR+

Unspecified Bit Rate Plus

UDP

See User Datagram Protocol.

UNI

See user-to-network interface.

UPC

See usage parameter control.

UPE

user-end provider edge

UPI

user payload identifier

UPM

uninterruptible power module

UPS

uninterruptible power supply

UTC

See Coordinated Universal Time.

User Datagram Protocol (UDP)

A TCP/IP standard protocol that allows an application program on one device to send a datagram to an application program on another. User Datagram Protocol (UDP) uses IP to deliver datagram. UDP provides application programs with the unreliable connectionless packet delivery service. There is a possibility that UDP messages will be lost, duplicated, delayed, or delivered out of order. The destination device does not confirm whether a data packet is received.

unavailable time event An event that is reported when the monitored object generates 10 consecutive severely (UAT) errored seconds (SES) and the SESs begin to be included in the unavailable time. The event will end when the bit error ratio per second is better than 10-3 within 10 consecutive seconds. usage parameter control (UPC)

During communications, UPC is implemented to monitor the actual traffic on each virtual circuit that is input to the network. Once the specified parameter is exceeded, measures will be taken to control. NPC is similar to UPC in function. The difference is that the incoming traffic monitoring function is divided into UPC and NPC according to their positions. UPC locates at the user/network interface, while NPC at the network interface.

user-to-network interface (UNI)

The interface between user equipment and private or public network equipment (for example, ATM switches).

V V-NNI

virtual network-network interface

V-UNI

See virtual user-network interface.

Issue 03 (2013-02-20)


998


B Glossary

VB

virtual bridge

VBR

See variable bit rate.

VCC

See virtual channel connection.

VCCV

virtual circuit connectivity verification

VCG

See virtual concatenation group.

VCI

virtual channel identifier

VDSL

very-high-data-rate digital subscriber line

VDSL2

See very-high-speed digital subscriber line 2.

VLAN

virtual local area network

VOA

variable optical attenuator

VP

See virtual path.

VPI

See virtual path identifier.

VPLS

See virtual private LAN service.

VPN

virtual private network

VPWS

See virtual private wire service.

VRRP

See Virtual Router Redundancy Protocol.

VSI

See virtual switch instance.

Virtual Router Redundancy Protocol (VRRP)

A protocol used for multicast or multicast LANs such as an Ethernet. A group of routers (including an active router and several backup routers) in a LAN is regarded as a virtual router, which is called a backup group. The virtual router has its own IP address. The host in the network communicates with other networks through this virtual router. If the active router in the backup group fails, one of the backup routers in this backup group becomes active and provides routing service for the host in the network.

VoIP

See voice over IP.

variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth and is better suited to non real time transfers than to real-time streams such as voice calls. very-high-speed digital An extension of the VDSL technology, which complies with ITU G.993.2, supports subscriber line 2 multiple spectrum profiles and encapsulation modes, and provides short-distance and (VDSL2) high-speed access solutions to the next-generation FTTx access service. virtual channel connection (VCC)

A VC logical trail that carries data between two end points in an ATM network. A pointto-multipoint VCC is a set of ATM virtual connections between two or multiple end points.

virtual concatenation group (VCG)

A group of co-located member trail termination functions that are connected to the same virtual concatenation link

virtual path (VP)

A bundle of virtual channels, all of which are switched transparently across an ATM network based on a common VPI.

virtual path identifier (VPI)

The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which virtual path the cell belongs.

Issue 03 (2013-02-20)


999


B Glossary

virtual private LAN service (VPLS)

A type of point-to-multipoint L2VPN service provided over the public network. VPLS enables geographically isolated user sites to communicate with each other through the MAN/WAN as if they are on the same LAN.

virtual private wire service (VPWS)

A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR, Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN.

virtual switch instance An instance through which the physical access links of VPLS can be mapped to the (VSI) virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge function and can terminate PW. virtual user-network interface (V-UNI)

A virtual user-network interface, works as an action point to perform service classification and traffic control in HQoS.

voice over IP (VoIP)

An IP telephony term for a set of facilities used to manage the delivery of voice information over the Internet. VoIP involves sending voice information in a digital form in discrete packets rather than by using the traditional circuit-committed protocols of the public switched telephone network (PSTN).

W WAN

See wide area network.

WCDMA

See Wideband Code Division Multiple Access.

WDM

wavelength division multiplexing

WEEE

waste electrical and electronic equipment

WFQ

See weighted fair queuing.

WLAN

See wireless local area network.

WRED

See weighted random early detection.

WRR

weighted round robin

WTR

See wait to restore.

Wideband Code Division Multiple Access (WCDMA)

A standard defined by the ITU-T for the third-generation wireless technology derived from the Code Division Multiple Access (CDMA) technology.

wait to restore (WTR)

The number of minutes to wait before services are switched back to the working line.

weighted fair queuing (WFQ)

A fair queue scheduling algorithm based on bandwidth allocation weights. This scheduling algorithm allocates the total bandwidth of an interface to queues, according to their weights and schedules the queues cyclically. In this manner, packets of all priority queues can be scheduled.

weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP detection (WRED) synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio. wide area network (WAN)

A network composed of computers which are far away from each other which are physically connected through specific protocols. WAN covers a broad area, such as a province, a state or even a country.

wireless local area network (WLAN)

A hybrid of the computer network and the wireless communication technology. It uses wireless multiple address channels as transmission media and carriers out data interaction through electromagnetic wave to implement the functions of the traditional LAN.

Issue 03 (2013-02-20)


1000


B Glossary

Z Z interface extension

Issue 03 (2013-02-20)

Extending the analogue subscriber to another place by extending the Z interface.


1001

OptiX OSN 7500 II&7500&3500&1500 Configuration Guide (Packet Transport Domain)(V200R011)

Recommend Documents